Table of Contents
Figure 36 Patches are activated
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
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
The patches that are in the RUNNING state are still in the RUNNING state after system reboot.
Figure 37 Patches are running
Configuration prerequisites
Patches are released per device model. Before patching the system, you need to save the appropriate
patch files to the storage media of the device using FTP or TFTP. When saving the patch files, note that
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 the display patch information command) represent the PATCH-FLAG suffix.
The system searches the root directory of the storage medium (Flash by default) for patch files based
Figure
37.
126
Figure
36, if you confirm
- Quick Links:
- Cli Configuration
- Entering the Cli
Hide quick links:
Table of Contents
