HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
![Page 119
107
To load a patch file:
Step Command
1. Enter system view.
system-view
2. Load the patch file on from the storage media (the
Flash) to the specified memory patch area. patch load slot
slot-number [ file patch-package ]
Activating patches
After you activate a patch, the patch takes effect and is in the test-run stage. After the switch is reset or
rebooted, the patch becomes invalid.
I f yo u fi n d t h a t a n AC T I V E p a t c h c a u s e s a n e r ro r, re b o ot the...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-118.png "Page 119
107
To load a patch file:
Step Command
1. Enter system view.
system-view
2. Load the patch file on from the storage media (the
Flash) to the specified memory patch area. patch load slot
slot-number [ file patch-package ]
Activating patches
After you activate a patch, the patch takes effect and is in the test-run stage. After the switch is reset or
rebooted, the patch becomes invalid.
I f yo u fi n d t h a t a n AC T I V E p a t c h c a u s e s a n e r ro r, re b o ot the...")
![Page 120
108
Step Command
1. Enter system view. system-view
2. Stop running patches.
patch deactive [ patch-number ] slot slot-number
Deleting patches
Deleting patches only removes the patches from the memory patch area, and does not delete them from
the storage media. The patches turn to IDLE state after this operation. Af ter a patch is deleted, the system
runs the way it did before it was installed with the patch.
In an IRF fabric, HP recommends that you uninstall all patches by using the...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-119.png "Page 120
108
Step Command
1. Enter system view. system-view
2. Stop running patches.
patch deactive [ patch-number ] slot slot-number
Deleting patches
Deleting patches only removes the patches from the memory patch area, and does not delete them from
the storage media. The patches turn to IDLE state after this operation. Af ter a patch is deleted, the system
runs the way it did before it was installed with the patch.
In an IRF fabric, HP recommends that you uninstall all patches by using the...")
![Page 122
110
boot-loader file soft-version2.bin slot all main
This command will set the boot file of the specified board. Continue? \
[Y/N]:y
The specified file will be used as the main boot file at the next reboot on slot
1!
The specified file will be used as the main boot file at the next reboot on slot
2!
# Reboot the switch. The software version is upgraded now.
reboot
3. Verify the configuration:
# Use the display version command to check if the upgrade is successful. (Details not shown.)...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-121.png "Page 122
110
boot-loader file soft-version2.bin slot all main
This command will set the boot file of the specified board. Continue? \
[Y/N]:y
The specified file will be used as the main boot file at the next reboot on slot
1!
The specified file will be used as the main boot file at the next reboot on slot
2!
# Reboot the switch. The software version is upgraded now.
reboot
3. Verify the configuration:
# Use the display version command to check if the upgrade is successful. (Details not shown.)...")
![Page 123
111
# Install the patch.
system-view
[IRF] patch install flash:
Patches will be installed. Continue? [Y/N]:y
Do you want to continue running patches after reboot? [Y/N]:y
Installing patches........
3. Verify the configuration:
# After the installation is complete, use the display patch information command to verify whether
the patches are installed succes sfully. (Details not shown.)](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-122.png "Page 123
111
# Install the patch.
system-view
[IRF] patch install flash:
Patches will be installed. Continue? [Y/N]:y
Do you want to continue running patches after reboot? [Y/N]:y
Installing patches........
3. Verify the configuration:
# After the installation is complete, use the display patch information command to verify whether
the patches are installed succes sfully. (Details not shown.)")
109 Figure 48 Network diagram Configuration procedure 1. Configure the TFTP server (the configuration varies with server vendors): # Obtain the system software image and configurat ion file through legitimate channels, such as the official website of HP, agents, and technical staff. Save these files under the TFTP server’s working path for the access of the TFTP clients. 2. Configure the members of the IRF fabric: # Download file new-config.cfg on the TFTP server to the master. tftp 2.2.2.2 get new-config.cfg .. File will be transferred in binary mode Downloading file from remote TFTP server, please wait..... TFTP: 917 bytes received in 1 second(s) File downloaded successfully. # Download file new-config.cfg to the subordinate switch with the member ID of 2. tftp 2.2.2.2 get new-config.cfg slot2#flash:/new-config.cfg # Download file soft-version2.bin on the TFTP server to the master and subordinate switch. tftp 2.2.2.2 get soft-version2.bin ... File will be transferred in binary mode Downloading file from remote TFTP server, please wait............ TFTP: 10058752 bytes received in 141 second(s) File downloaded successfully. tftp 2.2.2.2 get soft-version2.bin slot2#flash:/soft-version2.bin \ # Specify file new-config.cfg as the startup configuration file for all members of the IRF fabric. startup saved-configuration new-config.cfg main Please wait ... Setting the master board ... ... Done! Setting the slave board ... Slot 2: Set next configuration file successfully # Specify file soft-version2.bin as the system software image to be used at the next boot of all members of the IRF fabric.
110 boot-loader file soft-version2.bin slot all main This command will set the boot file of the specified board. Continue? \ [Y/N]:y The specified file will be used as the main boot file at the next reboot on slot 1! The specified file will be used as the main boot file at the next reboot on slot 2! # Reboot the switch. The software version is upgraded now. reboot 3. Verify the configuration: # Use the display version command to check if the upgrade is successful. (Details not shown.) Hotfix configuration example Network requirements The IRF fabric in Figure 49 comprises two member switches , the ma ster and subordinate switch. The software running on the member switches has a bug. The patch files patch_mpu.bin and patch_lpu.bin are saved on the TFTP server. The IRF fabric and TFTP server can reach each other. From the IRF fabric, use TFTP to download the patch files and then hotfix the software on the fabric. Figure 49 Network diagram Configuration procedure 1. Configure the TFTP server (the configuration varies with server vendors): • Enable the TFTP server function. (Details not shown.) • Save the patch files patch_mpu.bin and patch_lpu.bin to the directory of TFTP server. (Details not shown.) 2. Configure the IRF fabric: # Before upgrading the software, use the save command to save the current system configuration. (Details not shown.) # Examine the free space of the Flash on the switch. If the free space is not sufficient for the patch files, delete unused files to release enough space. (Details not shown.) # Load the patch files patch_mpu.bin and patch_lpu.bin from the TFTP server to the root directory of the masters storage media. tftp 2.2.2.2 get patch_mpu.bin tftp 2.2.2.2 get patch_lpu.bin # Load the patch files patch_mpu.bin and patch_lpu.bin from the TFTP server to the root directory of the subordinate switchs storage media. tftp 2.2.2.2 get patch_mpu.bin slot2#flash:/patch_mpu.bin tftp 2.2.2.2 get patch_lpu.bin slot2#flash:/patch_lpu.bin TFTP server 2.2.2.2/24Internet 1.1.1.1/24 IRF Master (Member_ID=1) Subordinate (Member_ID=2) Note: The orange line represents the IRF link.
111 # Install the patch. system-view [IRF] patch install flash: Patches will be installed. Continue? [Y/N]:y Do you want to continue running patches after reboot? [Y/N]:y Installing patches........ 3. Verify the configuration: # After the installation is complete, use the display patch information command to verify whether the patches are installed succes sfully. (Details not shown.)
112 Performing ISSU This chapter describes how to use the In-Service Software Upgrade (ISSU) feature to upgrade software. The ISSU feature is available only on the HP 5500-EI switch. ISSU overview ISSU enables software upgrade and ensures continuous packet forwarding. As shown in Figure 50, t o ensure high availability for user networks, cross-device link aggregation is configured on the IRF member switches at the distribution layer so that every three physical links with the same color between the IRF member switches and acce ss switches are aggregated as one logical link. In this scenario, you can use ISSU to upgrade system software of each IRF member switch to ensure non-stop forwarding or reduce down time for users connected to Switch A, Switch B, and Switch C. Figure 50 IRF network diagram ISSU upgrade procedure ISSU follows a strict procedure, as shown in Figure 51. IRF SwitchA SwitchBSwitchC SwitchD SwitchE 1 23 4 56 78 1: GE1/0/1 2: GE1/0/2 3: GE1/0/39 7: GE3/0/1 8: GE3/0/2 9: GE3/0/3 Switch F 4: GE2/0/1 5: GE2/0/2 6: GE2/0/3 1 2 3 12 3 12 3 1: GE1/0/1 2: GE1/0/2 3: GE1/0/3 1: GE1/0/1 2: GE1/0/2 3: GE1/0/3 1: GE1/0/1 2: GE1/0/2 3: GE1/0/3 UsersUsersUsers Core Aggregation Group 1 Aggregation Group 2 Aggregation Group 3
113 Figure 51 ISSU flow chart IMPORTANT: • Do not modify the current configuration, plug or un plug cables connected to IRF ports, or delete or modify the system software image during ISSU. Otherwise, the upgrade might fail. • To u p g ra d e syst e m s of t wa re of I R F m e m b er swi tc h e s t h rou g h I SSU, m a ke s u re t h e m e m b e r swi tc h e s fo rm a ring topology. ISSU states During the ISSU process, you can use the display issu state command to display the ISSU state of the IRF fabric, including whether the new system software image is compatible with the current system software image, and the adopted ISSU method.
114 Table 19 ISSU state description State Remarks Init (Initial state) No ISSU starts or an ISSU upgrade has completed. Load A subordinate switch is being upgraded or has been upgraded. To stop the loading process, perform a manual or automatic roll back to revert system software to its original version. Switchover The master is being rebooted to trigger a new master election. Accept The ISSU has been accepted. To stop the loading process, you have to perform a manual roll back to revert system software to its original version. The automatic roll back function is not available in this state. Commit At least one member switch has not been upgr aded to the new version. In this state, neither manual nor automatic rollback can be performed. System software version rollback The HP 5500-EI switch series supports version rollback during ISSU. When ISSU fails to proceed on an IRF member switch (for example, the new system software image file is broken) , you can use this feature to revert system software to the previous version. The HP 5500-EI switches support the following version rollback methods. Automatic rollback When you reboot the specified subordinate switch with the issu load command, the system automatically creates a configurable version rollback timer. During ISSU for a compatible version, if you do not execute the issu accept command on the specified subordinate switch or the issu commit command on any other member switch before the rollback timer expires, the system automatically stops the upgrade and rolls back the system software image of the upgraded IRF member switches to the previous version. During ISSU for an incompatible version, if you do not execute the issu run switchover command to upgrade all the IRF member switches that have not been upgraded in one operation before the rollback timer expires, the system automatically rolls back the system software image of all the upgraded IRF member switches to the previous version. For information about compatible and incompatible ISSU methods, see Displaying version co mpatibility . Manual rollback You can use the issu rollback command to roll back the system software image of an IRF member switch to the previous version. Whether manual rollback can be performed depends on the ISSU state. For more information, see Tabl e 19. Performing an ISSU This section describes how to perform an ISSU. ISSU upgrade task list
115 Task Remarks Downloading the new system software image to the Flash of all the IRF member switches Required. ISSU upgrade prerequisites Required. Displaying version compatibility Required. Performing an ISSU for a compatible version Required. Use either approach. Performing an ISSU for an incompatible version If you do not execute the issu run switchover command before the rollback timer expires, the ISSU upgrade ends automatically, the software reverts to the previous version, and the MPUs resume their former roles. The issu run switchover command deletes the rollback timer. After this command is executed, no manual or automatic rollback can be performed for the upgrade. Setting the ISSU version rollback timer Optional. Performing a manual version rollback Optional. Displaying and maintaining ISSU Optional. ISSU upgrade prerequisites Task Command Remarks Save the current configuration. save Before performing ISSU, make sure that the current configuration of the IRF fabric has been saved to the configuration file. Display the running status of each IRF member switch. display device Before performing ISSU, make sure that all the member switches of the IRF fabric are in normal state. Display the information about system software. display boot-loader Before performing an ISSU upgrade, make sure that the system software image of all the IRF member switches is identical, which means the version, name, and directory of the system software image are the same. Display the roles of IRF member switches. display irf N/A Display information about the files in the Flash. dir Before performing an ISSU upgrade, make sure that the new and current system software images exist in the Flash of each IRF member switch, and they are saved in the same directory.
116 Displaying version compatibility Before performing an ISSU upgrade, check the version compatibility between the new and current system software images, to determine whether ISSU can be performed, and which ISSU method is adopted. After downloading and saving the new system soft ware image, select an ISSU upgrade method according to one of the following version compatibility check results: • Compatible —The running system software image is compatible with the new system software image. You can use the compatible ISSU method to upgrade system software of the IRF fabric. For more information, see . • Incompatible —The current running system software image is incompatible with the new system software image. You can use the incompatible ISSU method to upgrade system software of the IRF fabric. For more information, see Pe r fo rm i n g a n I SSU f or an incompatible version. • Unknown— The current and new system software images ha ve big differences, or the current system software image does not support ISSU. You cannot upgrade system software through ISSU. To display version compatibility: Step Command 1. Enters system view. system-view 2. Check whether the new system software image is compatible with the current system software image. display version comp-matrix file upgrading-filename Performing an ISSU for a compatible version Use the display version comp-matrix file upgrading-filename command to view the versions of the new and current system software images. If the new system software image is compatible with the current system software image, use this task for ISSU. IMPORTANT: Before performing compatible ISSU, make sure that the priorities of the current master switch and the specified subordinate switch are higher than other IR F member switches so that the specified subordinate switch can be elected as the new master after the mast er is rebooted. Otherwise, modify the priorities of the current master switch and the specified subordinate switch with the irf member member-id priority priority command. To perform an ISSU for a compatible version: Step Command Remarks 1. Enter system view. system-view N/A 2. Upgrade the specified subordinate switch (the new master after the upgrade). issu load file upgrading-filename slot slot-number slot-number is the member ID of the subordinate switch. The specified subordinate switch reboots with the new system software image when this command is executed. Perform the next operation after the subordinate switch is rebooted.
117 Step Command Remarks 3. Reboot the master current manually. issu run switchover slot slot-number With this command executed: • The master reboots with the current system software image, and becomes a subordinate switch after reboot. • The subordinate switches of the IRF fabric perform master election. The winner (the subordinate switch specified with the issu load command) becomes the new master. The slot-number provided in this command must be the same as that specified in the issu load command. Perform the next operation after the reboot process is completed. 4. Accept the ISSU. issu accept slot slot-number Optional By default, the rollback timer is 45 minutes. If you do not execute the issu accept command on the specified subordinate switch or you do not execute the issu commit command on any other member switch before the rollback timer expires, the sy stem automatically stops the ISSU process and reverts to the previous software version. The slot-number argument provided in this command must be the same as that specified in the issu load command. When this command is executed, the rollback timer becomes invalid and system software cannot be automatically rolled back. 5. Upgrade an IRF member switch that has not been upgraded. issu commit slot slot-number This command upgrades one IRF member switch at a time. If the IRF fabric has three or more than three member switches, repeat this command to upgrade them one by one. When all the IRF member switches reboot with the new system software image, the ISSU process completes. The roles of some IRF member switches change after an ISSU upgrade. If you do not execute the issu accept or issu commit command on the specified IRF member switch before the specified rollback timer expires, the system automatically stops the ISSU process and reverts to the previous software version. After executing the issu commit command, you cannot perform version rollback with the issu rollback command. Performing an ISSU for an incompatible version Use the display version comp-matrix file upgrading-filename command to view the versions of the new and current system software images. If they are incompatible, use this task for ISSU.
118 IMPORTANT: To upgrade system software of the IRF fabric thro ugh ISSU when the new and current system software image versions are incompatible, make sure that th e multi-active detection (MAD) function has been configured for the IRF fabr ic. Otherwise, duplicate IRF fabrics wi ll coexist after the new master (the subordinate switch specified with the issu load command) is rebooted, causing network faults. To perform an ISSU for an incompatible version: Step Command Remarks 1. Enters system view. system-view N/A 2. Upgrade the specified subordinate switch (the new master after the upgrade). issu load file upgrading-filename slot slot-number force slot-number is the member ID of the subordinate switch. After this command is executed, the specified subordinate switch (the new master after the upgrade) reboots with the new system software image, and stays in the Recover state after reboot. Perform the next operation after the reboot process completes. 3. Upgrade all the IRF member switches that have not been upgraded in one operation. issu run switchover slot slot-number The slot-number argument provided in this command must be the same as that specified in the issu load command. When this command is executed, all the IRF member switches except the specified subordinate switch (the new master) are upgraded to the new version, and the ISSU process completes after reboot. If you do not execute the issu run switchover command before the rollback timer expires, the ISSU upgrade ends automatically, the software reverts to the previous version, and the MPUs resume their former roles. The issu run switchover command deletes the rollback timer. Afte r this command is executed, no manual or automatic rollback can be performed for the upgrade. Setting the ISSU version rollback timer Step Command Remarks 1. Enters system view. system-view N/A 2. Set the rollback timer. issu rollback-timer minutes Optional. By default, the rollback timer is 45 minutes. During an ISSU upgrade process, if you modify the rollback timer after executing the issu load command, the new rollback timer does not take effect for this ISSU process. Performing a manual version rollback