132
RUNNING state
After you confirm the running of the ACTIVE patches, the patch state becomes RUNNING and they are
placed in the RUNNING state after system reboot. For the five patches in Figure 6, if yo
u confirm running the
first three patches, their states change from ACTIVE to RUNNING. At this time, the patch states of the system
are as shown in Figure 7.
T
he pat
ches that are in the RUNNING state are still in the RUNNING state after system reboot.
Figure 7 Patches are running
Configuration prerequisites
Patches are released per device model. Before patching the system, you must save the appropriate patch files
to the storage media of the device using FTP or TFTP. When saving the patch files, the following rules apply:
• The patch files match the device model and software version. If they are not matched, the hotfixing
operation fails.
• Name a patch file properly. Otherwise, the system cannot locate the patch file and the hotfixing
operation fails. The name is in the format of "patch_PATCH-FLAG suffix.bin." The PATCH-FLAG is
pre-defined and support for the PATCH-FLAG depends on device model. The first three characters of the
version item (using display patch information) represent the PATCH-FLAG suffix. The system searches
the root directory of the storage medium (Flash by default) for patch files based on the PATCH-FLAG. If
there is a match, the system loads patches to or install them on the memory patch area.
Loading and installation are performed on all member devices of an IRF virtual device. Before performing
these operations, save the same patch files to the root directories in the storage media of all member devices.
The following table describes the default patch name for 5820X&5800 Switch Series.
Device PATCH-FLAG
Default
atch name
HP 5820X&5800 Switch Series
PATCH-MPU patch_mpu.bin
PATCH-LPU patch_lpu.bin
To Next Page
Loading...
Need help?
General
