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+.
119 Step Command Remarks 1. Enters system view. system-view N/A 2. Perform a manual version rollback. issu rollback slot slot-number Optional By default, automatic rollback is performed to revert to the previous version. The slot-number argument provided in this command must be the same as that specified in the issu load command. Displaying and maintaining ISSU Task Command Remarks Display information about the rollback timer. display issu rollback-timer [ | { begin | exclude | include } regular-expression ] Available in any view Display the ISSU state. display issu state Available in any view Display version compatibility information. display version comp-matrix [ file upgrading-filename ] Available in any view
120 ISSU upgrade example Network status As shown in Figure 52, a c c e s s l aye r swi t c h e s Swi t c h A , Swi t c h B , a n d Swi t c h C c o n n e c t t o u s e r n e t wo r k s . D i s t r i b u t i o n l a y e r s w i t c h e s S w i t c h D , S w i t c h E, a n d S w i t c h f o r m a n I R F f a b r i c . T h e m e m b e r I D o f t h e m a s t e r is 1, and those of the subordinate switches are 2 and 3 respectively. To ensure high availability, configure cross-device link aggregation using the following guidelines so that every three physical links with the same color between the IRF member switches and access switches are aggregated as one logical link: • On the IRF fabric, create three dynamic aggregation groups. Ports in aggregation group 1 connect to Switch A, ports in aggregation group 2 connect to Switch B, and ports in aggregation group 3 connect to Switch C. • On Switch A, create aggregation group 1 that corresponds to aggregation group 1 on the IRF fabric. • On Switch B, create aggregation group 2 that corresponds to aggregation group 2 on the IRF fabric. • On Switch C, create aggregation group 3 that corresponds to aggregation group 3 on the IRF fabric. Network requirements The current system software image on each IRF member switch is soft-version1.bin. The new system software image soft-version2.bin is saved on the TFTP server. The IP address of the IRF fabric is 1.1.1.1/24, and that of the TFTP server is 2.2.2.2/24. The IRF fabric and the TFTP server can reach each other. Use ISSU to upgrade system software of the IRF member switches to avoid traffic interruption.
121 Figure 52 Network diagram Upgrade procedure Configuring link aggregation 1. Configure the IRF fabric: # Create three dynamic aggregation groups 1, 2, and 3. system-view [IRF] interface bridge-aggregation 1 [IRF-Bridge-Aggregation1] link-aggregation mode dynamic [IRF-Bridge-Aggregation1] quit [IRF] interface bridge-aggregation 2 [IRF-Bridge-Aggregation2] link-aggregation mode dynamic [IRF-Bridge-Aggregation2] quit [IRF] interface bridge-aggregation 3 [IRF-Bridge-Aggregation3] link-aggregation mode dynamic [IRF-Bridge-Aggregation3] quit # Add ports GigabitEthernet 1/0/1, GigabitEthernet 2/0/1, and GigabitEthernet 3/0/1 that connect to Switch A to aggregation group 1. [IRF] interface GigabitEthernet 1/0/1 [IRF-GigabitEthernet1/0/1] port link-aggregation group 1 [IRF-GigabitEthernet1/0/1] quit 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
122 [IRF] interface GigabitEthernet 2/0/1 [IRF-GigabitEthernet2/0/1] port link-aggregation group 1 [IRF-GigabitEthernet2/0/1] quit [IRF] interface GigabitEthernet 3/0/1 [IRF-GigabitEthernet3/0/1] port link-aggregation group 1 [IRF-GigabitEthernet3/0/1] quit # Add ports GigabitEthernet 1/0/2, GigabitEthernet 2/0/2, and GigabitEthernet 3/0/2 that connect to Switch B to aggregation group 2. [IRF] interface GigabitEthernet 1/0/2 [IRF-GigabitEthernet1/0/2] port link-aggregation group 2 [IRF-GigabitEthernet1/0/2] quit [IRF] interface GigabitEthernet 2/0/2 [IRF-GigabitEthernet2/0/2] port link-aggregation group 2 [IRF-GigabitEthernet2/0/2] quit [IRF] interface GigabitEthernet 3/0/2 [IRF-GigabitEthernet3/0/2] port link-aggregation group 2 [IRF-GigabitEthernet3/0/2] quit # Add ports GigabitEthernet 1/0/3, GigabitEthernet 2/0/3, and GigabitEthernet 3/0/3 that connect to Switch C to aggregation group 3. [IRF] interface GigabitEthernet 1/0/3 [IRF-GigabitEthernet1/0/3] port link-aggregation group 3 [IRF-GigabitEthernet1/0/3] quit [IRF] interface GigabitEthernet 2/0/3 [IRF-GigabitEthernet2/0/3] port link-aggregation group 3 [IRF-GigabitEthernet2/0/3] quit [IRF] interface GigabitEthernet 3/0/3 [IRF-GigabitEthernet3/0/3] port link-aggregation group 3 [IRF-GigabitEthernet3/0/3] quit 2. Configure Switch A: # Create dynamic aggregate interface 1. system-view [SwitchA] interface bridge-aggregation 1 [SwitchA-Bridge-Aggregation1] link-aggregation mode dynamic [SwitchA-Bridge-Aggregation1] quit #Add ports GigabitEthernet 1/0/1, GigabitEther net 1/0/2, and GigabitEthernet 1/0/3 that connect to IRF member switches to aggregation group 1 (corresponding to aggregate interface 1). [SwitchA] interface GigabitEthernet 1/0/1 [SwitchA-GigabitEthernet1/0/1] port link-aggregation group 1 [SwitchA-GigabitEthernet1/0/1] quit [SwitchA] interface GigabitEthernet 1/0/2 [SwitchA-GigabitEthernet1/0/2] port link-aggregation group 1 [SwitchA-GigabitEthernet1/0/2] quit [SwitchA] interface GigabitEthernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] port link-aggregation group 1 [SwitchA-GigabitEthernet1/0/3] quit 3. Configure Switch B: # Create dynamic aggregate interface 2.
123 system-view [SwitchB] interface bridge-aggregation 2 [SwitchB-Bridge-Aggregation2] link-aggregation mode dynamic [SwitchB-Bridge-Aggregation2] quit #Add ports GigabitEthernet 1/0/1, GigabitEthernet 1/0/2, and GigabitEthernet 1/0/3 that connect to IRF member switches to aggregation group 2 (corresponding to aggregate interface 2). [SwitchB] interface GigabitEthernet 1/0/1 [SwitchB-GigabitEthernet1/0/1] port link-aggregation group 2 [SwitchB-GigabitEthernet1/0/1] quit [SwitchB] interface GigabitEthernet 1/0/2 [SwitchB-GigabitEthernet1/0/2] port link-aggregation group 2 [SwitchB-GigabitEthernet1/0/2] quit [SwitchB] interface GigabitEthernet 1/0/3 [SwitchB-GigabitEthernet1/0/3] port link-aggregation group 2 [SwitchB-GigabitEthernet1/0/3] quit 4. Configure Switch C: # Create dynamic aggregate interface 3. system-view [SwitchC] interface bridge-aggregation 3 [SwitchC-Bridge-Aggregation3] link-aggregation mode dynamic [SwitchB-Bridge-Aggregation3] quit # Add ports GigabitEthernet 1/0/1, GigabitEthernet 1/0/2, and GigabitEthernet 1/0/3 that connect to IRF member switches to aggregation group 3 (corresponding to aggregate interface 3). [SwitchC] interface GigabitEthernet 1/0/1 [SwitchC-GigabitEthernet1/0/1] port link-aggregation group 3 [SwitchC-GigabitEthernet1/0/1] quit [SwitchC] interface GigabitEthernet 1/0/2 [SwitchC-GigabitEthernet1/0/2] port link-aggregation group 3 [SwitchC-GigabitEthernet1/0/2] quit [SwitchC] interface GigabitEthernet 1/0/3 [SwitchC-GigabitEthernet1/0/3] port link-aggregation group 3 [SwitchC-GigabitEthernet1/0/3] quit Configuring the TFTP server Obtain the new system software image through a legal channel, and save the file to the working directory of the TFTP server so that the TFTP client can access the file. The working directory varies with TFTP server models. Downloading the new system software image # Download system software image soft-version2.bin to the root directory of the Flash of each IRF member 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.
124 copy soft-version2.bin slot2#flash:/ copy soft-version2.bin slot3#flash:/ Checking all IRF member switches before the ISSU upgrade 1. Check the running status of all IRF member switch es. If the running state of a member switch is abnormal, the ISSU upgrade cannot be performed. display device Slot 1 SubSNo PortNum PCBVer FPGAVer CPLDVer BootRomVer AddrLM Type State\ 0 28 REV.C NULL 002 CC1 IVL MAIN Norma\ l 1 2 REV.A NULL NULL NULL IVL 2*10GE Norma\ l Slot 2 SubSNo PortNum PCBVer FPGAVer CPLDVer BootRomVer AddrLM Type State\ 0 28 REV.C NULL 002 CC1 IVL MAIN Norma\ l 2 2 REV.A NULL NULL NULL IVL 2*10GE Norma\ l Slot 3 SubSNo PortNum PCBVer FPGAVer CPLDVer BootRomVer AddrLM Type State\ 0 28 REV.C NULL 002 CC1 IVL MAIN Norma\ l 3 2 REV.A NULL NULL NULL IVL 2*10GE Norma\ l The output shows that all IRF member switches are in normal state. 2. Check whether the current system software images on IRF member switches are the same. If not, the ISSU upgrade cannot be performed. display boot-loader Slot 1 The current boot app is: flash:/soft-version1.bin The main boot app is: flash:/soft-version1.bin The backup boot app is: flash:/ Slot 2 The current boot app is: flash:/soft-version1.bin The main boot app is: flash:/soft-version1.bin The backup boot app is: flash:/ Slot 3 The current boot app is: flash:/soft-version1.bin The main boot app is: flash:/soft-version1.bin The backup boot app is: flash:/ The output shows that the current system software image file on each IRF member switch is soft-version1.bin . 3. View the role of each IRF member switch. display irf Switch Role Priority CPU-Mac Description *+1 Master 10 0023-8927-ad54 ----- 2 Slave 9 0023-8927-afdc ----- 3 Slave 1 0023-89d9-3223 ----- -------------------------------------------------- * indicates the device is the master. + indicates the device through which the user logs in.
125 The Bridge MAC of the IRF is: 0023-8927-ad53 Auto upgrade : yes Mac persistent : 6 min Domain ID : 0 The output shows the following information: { The member ID and the priority of the master is 1 and 10 respectively { The member ID and the priority of one subordinate switch is 2 and 9 respectively { The member ID and the priority of the other subordinate switch is 3 and 1 respectively During the ISSU upgrade process, you must se lect subordinate switch 2 as the specified subordinate switch. Before performing compatible ISSU, make sure the priorities of the master switch and the specified subordinate switch are higher than other IRF memb er switches so that the specified subordinate switch can be elected as the new master after the master is rebooted. Otherwise, modify the priorities of the master switch and the specified subordinate switch with the irf member member-id priority priority command. 4. Check whether the new system software image has been saved in the Flash of each IRF member switch. If not, the ISSU up grade cannot be performed. # Verify whether the new system software image soft-version2.bin has been saved to the Flash of the master. dir Directory of flash:/ 0 -rw- 6085 May 29 2010 11:38:45 config.cfg 1 -rw- 10518 Apr 26 2011 12:45:05 logfile.log 2 -rw- 12397691 Apr 26 2011 14:24:11 soft-version1.bin 3 -rw- 13308645 Apr 26 2011 14:13:46 soft-version2.bin 4 drw- - Apr 26 2011 12:00:33 seclog 5 -rw- 287 Apr 26 2011 12:19:52 system.xml 31496 KB total (5981 KB free) The output shows that the new system software im age has been saved to the Flash of the master. # Verify whether the new system software image soft-version2.bin has been saved to the Flash of subordinate switch 2. dir slot2#flash:/ Directory of slot2#flash:/ 0 -rw- 6085 May 29 2010 11:38:45 config.cfg 1 -rw- 10518 Apr 26 2011 12:45:05 logfile.log 2 -rw- 12397691 Apr 26 2011 14:24:11 soft-version1.bin 3 -rw- 13308645 Apr 26 2011 14:13:46 soft-version2.bin 4 drw- - Apr 26 2011 12:00:33 seclog 5 -rw- 287 Apr 26 2011 12:19:52 system.xml 31496 KB total (5981 KB free) The output shows that the new system software im age has been saved to the Flash of subordinate switch 2.
126 # Verify whether the new system software image soft-version2.bin has been saved to the Flash of subordinate switch 3. dir slot3#flash:/ Directory of slot3#flash:/ 0 -rw- 6085 May 29 2010 11:38:45 config.cfg 1 -rw- 10518 Apr 26 2011 12:45:05 logfile.log 2 -rw- 12397691 Apr 26 2011 14:24:11 soft-version1.bin 3 -rw- 13308645 Apr 26 2011 14:13:46 soft-version2.bin 4 drw- - Apr 26 2011 12:00:33 seclog 5 -rw- 287 Apr 26 2011 12:19:52 system.xml 31496 KB total (5981 KB free) The output shows that the new system software im age has been saved to the Flash of subordinate switch 3. 5. Save the current configuration. save The current configuration will be written to the device. Are you sure? [\ Y/N]:y Please input the file name(*.cfg)[flash:/config.cfg] (To leave the existing filename unchanged, press the enter key): flash:/config.cfg exists, overwrite? [Y/N]:y Validating file. Please wait.... Saved the current configuration to mainboard device successfully. Slot 2: Save next configuration file successfully. Slot 3: Save next configuration file successfully. Configuration is saved to device successfully. The output shows that the current configuration has been saved to the configuration file of each IRF member switch. Viewing the version compatibility # Check whether the current and new system software images are compatible. display version comp-matrix file soft-version2.bin • If they are compatible, the output is like the following: Number of Matrices in Table = 1 Matrix for HP 5500-EI Running Version: version1 Version Compatibility List: version2 (Compatible) The output shows that the new and current ve rsions are fully compatible. You can use the compatible ISSU upgrade method. For more information, see Performing compatible ISSU u pgrade . • If the two versions are incompatible, the output is like the following: Number of Matrices in Table = 1
127 Matrix for HP 5500-EI Running Version: version1 Version Compatibility List: version2 (Incompatible) The output shows that the two versions are inco mpatible. You must use the incompatible ISSU method. For more information, see Performing incompatible ISSU upgrade . Performing compatible ISSU upgrade # Upgrade the specified subordinate switch (the ne w master after the upgrade), which is subordinate switch 2 in this example. system-view [IRF] issu load file soft-version2.bin slot 2 This command will begin ISSU, and the specified board will reboot and be\ upgraded. Please save the current running configuration first; otherwise, the configurati\ on may be lost.Continue? [Y/N]:y # After the reboot of subordinate switch 2, check whether the system software image of salve switch 2 is soft-version2.bin . [IRF] display boot-loader Slot 1 The current boot app is: flash:/soft-version1.bin The main boot app is: flash:/soft-version1.bin The backup boot app is: flash:/ Slot 2 The current boot app is: flash:/soft-version2.bin The main boot app is: flash:/soft-version2.bin The backup boot app is: flash:/ Slot 3 The current boot app is: flash:/soft-version1.bin The main boot app is: flash:/soft-version1.bin The backup boot app is: flash:/ The output shows that the system software image of subordinate switch 2 is soft-version2.bin. # Reboot the master manually. [IRF] issu run switchover slot 2 Master will reboot, switch the specified board to master and update the line card. Continue? [Y/N]:y I n t h i s exa m p l e, t h e m e m b e r I D o f t h e m a s t e r i s 1. After reboot, the master becomes a subordinate switch in the IRF fabric. Then the subordinate switches perform a role election, and salve 2 becomes the new master because the priority of subordinate switch 2 is higher than that of subordinate switch 3. # Accept the ISSU upgrade and delete the rollback timer. [IRF] issu accept slot 2 # Upgrade switch 1 and switch 3. [IRF] issu commit slot 1 The specified board will reboot and be upgraded. Continue? [Y/N]:y [IRF] issu commit slot 3 The specified board will reboot and be upgraded. Continue? [Y/N]:y
128 Then the ISSU upgrade process completes and the system software images of all IRF member switches have been upgraded to the new version. # Verify whether the current system software images on the IRF member switches are soft-version2.bin. [IRF] display boot-loader Slot 1 The current boot app is: flash:/soft-version2.bin The main boot app is: flash:/soft-version2.bin The backup boot app is: flash:/ Slot 2 The current boot app is: flash:/soft-version2.bin The main boot app is: flash:/soft-version2.bin The backup boot app is: flash:/ Slot 3 The current boot app is: flash:/soft-version2.bin The main boot app is: flash:/soft-version2.bin The backup boot app is: flash:/ Performing incompatible ISSU upgrade 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. # Upgrade the specified subordinate switch (the ne w master after the upgrade), which is subordinate switch 2 in this example. system-view [IRF] issu load file soft-version2.bin slot 2 This command will begin ISSU, and the specified board will reboot and be\ upgraded. Please save the current running configuration first; otherwise, the configurati\ on may be lost.Continue? [Y/N]: y # After the reboot of subordinate switch 2, reboot and upgrade all IRF member switches that have not been upgraded. [IRF] issu run switchover slot 2 Master will reboot, switch the specified board to master and update the line card. Continue? [Y/N]:y Then, the ISSU upgrade process completes and the system software images of all IRF member switches have been upgraded to the new version. # Verify whether the current system software images on the IRF member switches are soft-version2.bin. [IRF] display boot-loader Slot 1 The current boot app is: flash:/soft-version2.bin The main boot app is: flash:/soft-version2.bin The backup boot app is: flash:/ Slot 2 The current boot app is: flash:/soft-version2.bin