Figure 45 Patches are activated

Memory patch area

RUNNING state

Patch 1 ACTIVE

Patch 2 ACTIVE

Patch 3 ACTIVE

Patch 4 ACTIVE

Patch 5 ACTIVE

Patch 6 DEACTIVE

Patch 7 DEACTIVE

Patch 8 IDLE

After you confirm the ACTIVE patches are running, the patch state becomes RUNNING and they are placed in the RUNNING state after system reboot. For the five patches in Figure 45, if you confirm the first three patches are running, their states change from ACTIVE to RUNNING. At this time, the patch states of the system are as shown in Figure 46.

The patches that are in the RUNNING state are still in the RUNNING state after system reboot.

Figure 46 Patches are running

Memory patch area

Patch 1 RUNNING

Patch 2 RUNNING

Patch 3 RUNNING

Patch 4 ACTIVE

Patch 5 ACTIVE

Patch 6 DEACTIVE

Patch 7 DEACTIVE

Patch 8 IDLE

Configuration prerequisites

Patches are released per switch model. Before patching the system, you need to save the appropriate patch files to the switch’s storage media using FTP or TFTP. When saving the patch files, note that the following rules apply:

The patch files match the switch model and software version. If they are not matched, the hotfix 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 switch 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

120