- Released At: 18-11-2019
- Page Views:
- Downloads:
- Table of Contents
- Related Documents
-
Contents
Upgrade restrictions and guidelines
Performing an ISSU in one step
Introduction
H3C data center switches support ISSU in IRF mode. ISSU upgrades the Comware software with a minimum amount of downtime.
ISSU
In-Service Software Upgrade (ISSU) upgrades the Comware software with a minimum amount of downtime. This upgrade method is highly reliable.
Unless otherwise stated, the term "upgrade" refers to both software upgrade and downgrade in ISSU.
The Comware software includes the following types of images: boot image, system image and feature images. You can use ISSU to upgrade the images separately.
You can perform an ISSU in one step or step by step. A one-step ISSU enables you to start and finish an ISSU by using a single command. A step-by-step ISSU requires multiple steps but you can monitor the status and quit or roll back the upgrade during the ISSU.
IRF
The Intelligent Resilient Framework (IRF) technology virtualizes multiple physical devices at the same layer into one virtual fabric to provide data center class availability and scalability. It offers processing power, interaction, unified management, and uninterrupted maintenance of multiple devices.
The IRF technology provides the hardware basis for ISSU.
Upgrade restrictions and guidelines
During an ISSU, follow these restrictions and guidelines:
· Do not perform any of the following tasks:
¡ Reboot the device.
¡ Perform tasks that are irrelevant to the ISSU, such as modifying the configuration and displaying information.
¡ Modify, delete, or rename image files.
· For better service continuity during a step-by-step ISSU, strictly follow the recommended ISSU procedure. Make sure a step is completed before you proceed to the next step.
· You may use issu commands to upgrade all or some of the software images. If you are upgrading only some of the images, make sure the new images are compatible with the images that are not to be upgraded. The upgrade will fail if a conflict exists.
After an ISSU, you must log in to the device again before you can use the changed or added commands.
Preparing for the upgrade
To perform a successful ISSU, make sure all requirements listed in Table 1 are met.
Table 1 Preparation requirements
Item |
Requirements |
Example (key information only) |
IRF |
Verify that all member devices are operating correctly. |
|
Verify that the IRF bridge MAC address is enabled to be permanent or remain unchanged for 12 minutes after the address owner leaves. If not, execute the irf mac-address persistent { always | timer } command. |
||
Verify that all member devices are operating in the same system operating mode. Use the system-working-mode command to change the settings as required. |
||
Verify that all member devices are using the same hardware resource operating mode. Use the hardware-resource command to change the settings as required. |
||
Hardware |
Verify that the CPU usage is lower than the alarm thresholds on each member device. As a best practice, make sure the CPU usage is lower than the recovery threshold. |
|
Verify that the free memory space is more than the alarm thresholds on each member device. As a best practice, make sure the free memory space is more than the normal state threshold. |
||
Verify that all fan trays are in Normal state. |
||
Verify that all power supplies are in Normal state. |
||
Verify that the temperature is lower than the high-temperature warning threshold on each component. |
||
Verify that all ports are forwarding traffic correctly. |
||
Verify that the number of packets with CRC errors is not increasing. |
||
Aggregation |
Identify the number of selected ports and the number of unselected ports |
|
Verify that all member ports in dynamic aggregation groups use the long LACP timeout interval. |
N/A |
|
Services |
Enable GR or NSR for protocols including LDP, RSVP, OSPF, ISIS, BGP, and FSPF. |
N/A |
Disable BFD for protocols including LDP, RSVP, OSPF, ISIS, RIP, BGP, VRRP, and NQA. |
N/A |
|
Version |
Read the software release notes. Make sure ISSU is supported for upgrading the current software version to the new software version. |
N/A |
Performing an ISSU in one step
Network configuration
As shown in Figure 1, configure the two switches to form an IRF fabric. Use ISSU to upgrade the software from Release 2710 to Release 2712. The two software versions are compatible.
Procedure
Configuring the IRF fabric
Logging in to the device
# Log in to the device by using Telnet or the console port.
Configuring IRF member devices
1. Configure Device A:
# Assign member priority 2 to Device A.
<DeviceA> system-view
[DeviceA] irf member 1 priority 2
# Bind FortyGigE 1/1/0/1 to IRF-port 1/1.
[DeviceA] interface FortyGigE 1/1/0/1
[DeviceA-FortyGigE1/1/0/1] shutdown
[DeviceA-FortyGigE1/1/0/1] quit
[DeviceA] irf-port 1/1
[DeviceA-irf-port1/1] port group interface FortyGigE 1/1/0/1
[DeviceA-irf-port1/1] quit
[DeviceA] interface FortyGigE 1/1/0/1
[DeviceA-FortyGigE1/1/0/1] undo shutdown
[DeviceA-FortyGigE1/1/0/1] save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
[DeviceA-FortyGigE1/1/0/1] quit
# Activate the IRF port.
[DeviceA] irf-port-configuration active
[DeviceB] quit
2. Configure Device B:
# Change the ID of Device B from 1 to 2.
[DeviceB] irf member 1 renumber 2
Renumbering the member ID may result in configuration change or loss. Continue?[Y/N]:y
# Reboot Device B.
[DeviceB] reboot
# Assign member priority 1 to Device B.
<DeviceB> system-view
[DeviceB] irf member 1 priority 1
# Bind FortyGigE 2/1/0/1 to IRF-port 2/2.
[DeviceB] interface FortyGigE 2/1/0/1
[DeviceB-FortyGigE2/1/0/1] shutdown
[DeviceB-FortyGigE2/1/0/1] quit
[DeviceB] irf-port 2/2
[DeviceB-irf-port2/2] port group interface FortyGigE 2/1/0/1
[DeviceB-irf-port2/2] quit
[DeviceB] interface FortyGigE 2/1/0/1
[DeviceB-FortyGigE2/1/0/1] undo shutdown
[DeviceB-FortyGigE2/1/0/1] save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
[DeviceB-FortyGigE2/1/0/1] quit
# Activate the IRF port.
[DeviceB] irf-port-configuration active
[DeviceB] quit
Displaying device information
# Display device information.
<DeviceA> display device
Slot Type State Subslot Soft Ver Patch Ver
1/0 LSXM1SUPB1 Master 0 S12508X-AF-2710 None
1/1 NONE Absent 0 NONE None
1/2 NONE Absent 0 NONE None
1/3 LSXM1QGS36HB1 Normal 0 S12508X-AF-2710 None
1/4 NONE Absent 0 NONE None
1/5 NONE Absent 0 NONE None
1/6 NONE Absent 0 NONE None
1/7 NONE Absent 0 NONE None
1/8 NONE Absent 0 NONE None
1/9 NONE Absent 0 NONE None
1/10 NONE Absent 0 NONE None
1/11 NONE Absent 0 NONE None
1/12 NONE Absent 0 NONE None
1/13 NONE Absent 0 NONE None
1/14 LSXM1SFH08D1 Normal 0 S12508X-AF-2710 None
1/15 NONE Absent 0 NONE None
2/0 LSXM1SUPB1 Slave 0 S12508X-AF-2710 None
2/1 NONE Absent 0 NONE None
2/2 NONE Absent 0 NONE None
2/3 LSXM1QGS36HB1 Normal 0 S12508X-AF-2710 None
2/4 NONE Absent 0 NONE None
2/5 NONE Absent 0 NONE None
2/6 NONE Absent 0 NONE None
2/7 NONE Absent 0 NONE None
2/8 NONE Absent 0 NONE None
2/9 NONE Absent 0 NONE None
2/10 NONE Absent 0 NONE None
2/11 NONE Absent 0 NONE None
2/12 NONE Absent 0 NONE None
2/13 NONE Absent 0 NONE None
2/14 LSXM1SFH08D1 Normal 0 S12508X-AF-2710 None
2/15 NONE Absent 0 NONE None
The command output indicates that the two devices have formed an IRF fabric. Chassis 1 is the master and Chassis 2 is the subordinate member. The two members are operating correctly.
Performing an ISSU
Verifying that the member devices have sufficient storage space
# View the amount of free storage space on member devices.
· On the master:
<DeviceA> dir chassis1slot0#flash:/
Directory of flash:
0 -rw- 2901 Jan 01 2011 03:13:38 210235A1UMH1610000122017011911451076132.ak
1 -rw- 120552448 Jan 02 2011 11:37:58 R2710.ipe
2 -rw- 118386 Jan 01 2011 02:43:16 diag_A_B_C_20110101-021505.tar.gz
3 -rw- 104500 Jan 01 2011 00:29:18 diag_H3C_20110101-002803.tar.gz
4 -rw- 113895 Jan 01 2011 01:11:50 diag_TD2+_20110101-011053.tar.gz
5 drw- - Jan 01 2011 00:01:13 diagfile
6 -rw- 512 Jan 01 2011 01:00:05 fd8ef19a214ea12039a2f5ac6ef936fd.cfg
7 -rw- 4086 Jan 02 2011 10:52:18 ifindex.dat
8 -rw- 238 Jan 01 2011 11:05:44 lauth.dat
9 drw- - Jan 01 2011 03:14:28 license
10 drw- - Jan 01 2011 05:18:02 logfile
11 drw- - Jan 01 2011 01:02:09 ovsdb
12 drw- - Jan 01 2011 11:05:58 pkey
13 drw- - Jan 01 2011 11:05:50 pki
14 -rw- 14478336 Jan 01 2011 10:38:36 boot-e2601.bin
15 -rw- 14476288 Jan 01 2011 10:52:24 boot-r2710.bin
16 -rw- 102051840 Jan 01 2011 10:44:11 system-e2601.bin
17 -rw- 106068992 Jan 01 2011 10:57:47 system-r2710.bin
18 drw- - Jan 01 2011 00:01:13 seclog
19 -rw- 15632 Jan 02 2011 10:52:25 startup.cfg
20 -rw- 313105 Jan 02 2011 10:52:26 startup.mdb
21 drw- - Jan 01 2011 03:08:27 test
22 -rw- 163053 Jan 01 2011 10:45:18 test1.tar.gz
23 -rw- 149436 Jan 01 2011 10:46:32 test2.tar.gz
24 dr-- - Jan 01 2011 00:49:46 versionInfo
25 -rw- 3844 Jan 01 2011 03:26:03 vlan.txt
26 -rw- 4214 Jan 01 2011 03:01:40 xinjianshiyan.txt
524288 KB total (170948 KB free)
<DeviceA> dir chassis2slot0#flash:/
Directory of flash:
0 -rw- 2901 Jan 01 2011 03:13:38 210235A1UMH1610000122017011911451076132.ak
1 -rw- 120552448 Jan 02 2011 11:37:58 R2710.ipe
2 -rw- 118386 Jan 01 2011 02:43:16 diag_A_B_C_20110101-021505.tar.gz
3 -rw- 104500 Jan 01 2011 00:29:18 diag_H3C_20110101-002803.tar.gz
4 -rw- 113895 Jan 01 2011 01:11:50 diag_TD2+_20110101-011053.tar.gz
5 drw- - Jan 01 2011 00:01:13 diagfile
6 -rw- 512 Jan 01 2011 01:00:05 fd8ef19a214ea12039a2f5ac6ef936fd.cfg
7 -rw- 4086 Jan 02 2011 10:52:18 ifindex.dat
8 -rw- 238 Jan 01 2011 11:05:44 lauth.dat
9 drw- - Jan 01 2011 03:14:28 license
10 drw- - Jan 01 2011 05:18:02 logfile
11 drw- - Jan 01 2011 01:02:09 ovsdb
12 drw- - Jan 01 2011 11:05:58 pkey
13 drw- - Jan 01 2011 11:05:50 pki
14 -rw- 14478336 Jan 01 2011 10:38:36 boot-e2601.bin
15 -rw- 14476288 Jan 01 2011 10:52:24 boot-r2710.bin
16 -rw- 102051840 Jan 01 2011 10:44:11 system-e2601.bin
17 -rw- 106068992 Jan 01 2011 10:57:47 system-r2710.bin
18 drw- - Jan 01 2011 00:01:13 seclog
19 -rw- 15632 Jan 02 2011 10:52:25 startup.cfg
20 -rw- 313105 Jan 02 2011 10:52:26 startup.mdb
21 drw- - Jan 01 2011 03:08:27 test
22 -rw- 163053 Jan 01 2011 10:45:18 test1.tar.gz
23 -rw- 149436 Jan 01 2011 10:46:32 test2.tar.gz
24 dr-- - Jan 01 2011 00:49:46 versionInfo
25 -rw- 3844 Jan 01 2011 03:26:03 vlan.txt
26 -rw- 4214 Jan 01 2011 03:01:40 xinjianshiyan.txt
524288 KB total (170948 KB free)
The command output shows the amount of free storage space on each member device.
# Compare the sizes of the upgrade image files with the amount of free storage space. If the free storage space is insufficient, continue with the next step to delete unused files to release more storage space.
# Delete unused files on the member devices.
· On the master:
<DeviceA> delete /unreserved chassis1slot0#flash:/r2710.ipe
The file cannot be restored. Delete flash:/r2710.ipe? [Y/N]:y
Deleting the file permanently will take a long time. Please wait...
Deleting file flash:/r2710.ipe... Done.
· On the subordinate member:
<DeviceA> delete /unreserved chassis2slot0#flash:/r2710.ipe
The file cannot be restored. Delete flash:/r2710.ipe? [Y/N]:y
Deleting the file permanently will take a long time. Please wait...
Deleting file flash:/r2710.ipe... Done.
|
NOTE: · The delete /unreserved file command deletes a file permanently. The file cannot be restored. · The delete file command (without /unreserved) moves a file to the recycle bin. The file is still using storage space. To delete the file from the recycle bin, you must execute the reset recycle-bin command in the directory where the file resided. |
Downloading the upgrade file to the master
You can use FTP or TFTP to download the upgrade file. In this example, FTP is used and the device acts as the FTP client. The PC acts as the FTP server.
1. Run the FTP server program on the PC. Configure a user and set the password. Specify the working directory and save the upgrade file to the directory. The IP address of the PC is 2.2.2.2.
|
NOTE: The device is not shipped with an FTP server program. You must purchase and install an FTP server program separately. |
2. Make sure the device and PC can reach each other. (Details not shown.)
3. Download the upgrade file to the root directory of the default file system on the master. In this example, the upgrade file is R2712.ipe.
# Log in to the FTP server from the IRF fabric.
<DeviceA> ftp 2.2.2.2
Connected to 2.2.2.2 (2.2.2.2).
220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user
User (2.2.2.2:(none)):username ---Enter the username.
331 Give me your password, please
Password: ---Enter the password.
230 Logged in successfully
Remote system type is MSDOS.
ftp>
# Set the file transfer mode to binary. The default file transfer mode is binary.
ftp> binary
200 Type is Image (Binary)
# Download upgrade file R2712.ipe to the root directory of the default file system on the master.
ftp> get r2712.ipe
227 Entering Passive Mode (2,2,2,2,7,100)
150 "C:\r2712.ipe " file ready to send (385 bytes) in in IMAGE / Binary mode
226 Transfer finished successfully.
74948608 bytes received in 35.974 seconds (896.00 kbyte/s)
ftp> bye
221 Windows FTP Server (WFTPD, by Texas Imperial Software) says goodbye
Performing an ISSU in one step
1. Verify that the IRF fabric is in Stable state, that is, the State field in the output from the display system stable state command displays Stable.
ISSU state: Init
Compatibility: Unknown
Work state: Normal
Upgrade method: Chassis by chassis
Upgraded chassis: None
Current upgrading chassis: None
Current version list:
boot: 7.1.070, Release 2710
system: 7.1.070, Release 2710
Current software images:
flash:/boot-r2710.bin
flash:/system-r2710.bin
<DeviceA> display system stable state
System state : Stable
Redundancy state : Stable
Chassis Slot CPU Role State
1 0 0 Active Stable
1 3 0 Other Stable
1 14 0 Other Stable
2 0 0 Active Stable
2 3 0 Other Stable
2 14 0 Other Stable
The command output shows that both IRF member devices are in Stable state. You can start an ISSU.
2. Perform a one-step ISSU.
In IRF mode, an ISSU is performed chassis by chassis. Execute the one-step ISSU command on the subordinate member.
<DeviceA> issu one-step file ipe flash:/r2712.ipe chassis 2
This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y
Verifying the file flash:/r2712.ipe on chassis 2 slot 0............Done.
Decompressing file boot-r2712.bin to flash:/boot-r2712.bin....................Done.
Decompressing file system-r2712.bin to flash:/system-r2712.bin.......................................................................................................................................Done.
Decompression completed.
Do you want to delete flash:/r2712.ipe now? [Y/N]:n
This operation might take several minutes, please wait...........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
The command performs the following operations:
a. Perform an reboot upgrade on the subordinate member.
b. Perform a switchover.
c. Perform an reboot upgrade on the original master.
3. Verify that the ISSU is finished.
<DeviceA> display issu state
ISSU state: Init
Compatibility: Unknown
Work state: Normal
Upgrade method: Chassis by Chassis
Upgraded chassis: None
Current upgrading Chassis: None
Current version list:
boot: 7.1.070, Release 2712
system: 7.1.070, Release 2712
Current software images:
flash:/boot-r2712.bin
flash:/system-r2712.bin
If the ISSU state field displays Init, the ISSU is finished.
4. Display device information.
<DeviceA> display device
Slot Type State Subslot Soft Ver Patch Ver
1/0 LSXM1SUPB1 Slave 0 S12508X-AF-2712 None
1/1 NONE Absent 0 NONE None
1/2 NONE Absent 0 NONE None
1/3 LSXM1QGS36HB1 Normal 0 S12508X-AF-2712 None
1/4 NONE Absent 0 NONE None
1/5 NONE Absent 0 NONE None
1/6 NONE Absent 0 NONE None
1/7 NONE Absent 0 NONE None
1/8 NONE Absent 0 NONE None
1/9 NONE Absent 0 NONE None
1/10 NONE Absent 0 NONE None
1/11 NONE Absent 0 NONE None
1/12 NONE Absent 0 NONE None
1/13 NONE Absent 0 NONE None
1/14 LSXM1SFH08D1 Normal 0 S12508X-AF-2712 None
1/15 NONE Absent 0 NONE None
2/0 LSXM1SUPB1 Master 0 S12508X-AF-2712 None
2/1 NONE Absent 0 NONE None
2/2 NONE Absent 0 NONE None
2/3 LSXM1QGS36HB1 Normal 0 S12508X-AF-2712 None
2/4 NONE Absent 0 NONE None
2/5 NONE Absent 0 NONE None
2/6 NONE Absent 0 NONE None
2/7 NONE Absent 0 NONE None
2/8 NONE Absent 0 NONE None
2/9 NONE Absent 0 NONE None
2/10 NONE Absent 0 NONE None
2/11 NONE Absent 0 NONE None
2/12 NONE Absent 0 NONE None
2/13 NONE Absent 0 NONE None
2/14 LSXM1SFH08D1 Normal 0 S12508X-AF-2712 None
2/15 NONE Absent 0 NONE None
The command output shows that the original subordinate member is now the master. The software version has been upgraded from 2710 to 2712.
Performing an ISSU step by step
Network configuration
As shown in Figure 2, configure the two switches to form an IRF fabric. Use ISSU to upgrade the software from Release 2710 to Release 2712. The two software versions are compatible.
Procedure
Configuring the IRF fabric
Logging in to the device
# Log in to the device by using Telnet or the console port.
Configuring IRF member devices
1. Configure Device A:
# Assign member priority 2 to Device A.
<DeviceA> system-view
[DeviceA] irf member 1 priority 2
# Bind FortyGigE 1/1/0/1 to IRF-port 1/1.
[DeviceA] interface FortyGigE 1/1/0/1
[DeviceA-FortyGigE1/1/0/1] shutdown
[DeviceA-FortyGigE1/1/0/1] quit
[DeviceA] irf-port 1/1
[DeviceA-irf-port1/1] port group interface FortyGigE 1/1/0/1
[DeviceA-irf-port1/1] quit
[DeviceA] interface FortyGigE 1/1/0/1
[DeviceA-FortyGigE1/1/0/1] undo shutdown
[DeviceA-FortyGigE1/1/0/1] save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
[DeviceA-FortyGigE1/1/0/1] quit
# Activate the IRF port.
[DeviceA] irf-port-configuration active
[DeviceB] quit
2. Configure Device B:
# Change the ID of Device B from 1 to 2.
[DeviceB] irf member 1 renumber 2
Renumbering the member ID may result in configuration change or loss. Continue?[Y/N]:y
# Reboot Device B.
[DeviceB] reboot
# Assign member priority 1 to Device B.
<DeviceB> system-view
[DeviceB] irf member 1 priority 1
# Bind FortyGigE 2/1/0/1 to IRF-port 2/2.
[DeviceB] interface FortyGigE 2/1/0/1
[DeviceB-FortyGigE2/1/0/1] shutdown
[DeviceB-FortyGigE2/1/0/1] quit
[DeviceB] irf-port 2/2
[DeviceB-irf-port2/2] port group interface FortyGigE 2/1/0/1
[DeviceB-irf-port2/2] quit
[DeviceB] interface FortyGigE 2/1/0/1
[DeviceB-FortyGigE2/1/0/1] undo shutdown
[DeviceB-FortyGigE2/1/0/1] save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
[DeviceB-FortyGigE2/1/0/1] quit
# Activate the IRF port.
[DeviceB] irf-port-configuration active
[DeviceB] quit
Displaying device information
# Display device information.
<DeviceA> display device
Slot Type State Subslot Soft Ver Patch Ver
<DeviceA> display device
Slot Type State Subslot Soft Ver Patch Ver
1/0 LSXM1SUPB1 Master 0 S12508X-AF-2710 None
1/1 NONE Absent 0 NONE None
1/2 NONE Absent 0 NONE None
1/3 LSXM1QGS36HB1 Normal 0 S12508X-AF-2710 None
1/4 NONE Absent 0 NONE None
1/5 NONE Absent 0 NONE None
1/6 NONE Absent 0 NONE None
1/7 NONE Absent 0 NONE None
1/8 NONE Absent 0 NONE None
1/9 NONE Absent 0 NONE None
1/10 NONE Absent 0 NONE None
1/11 NONE Absent 0 NONE None
1/12 NONE Absent 0 NONE None
1/13 NONE Absent 0 NONE None
1/14 LSXM1SFH08D1 Normal 0 S12508X-AF-2710 None
1/15 NONE Absent 0 NONE None
2/0 LSXM1SUPB1 Slave 0 S12508X-AF-2710 None
2/1 NONE Absent 0 NONE None
2/2 NONE Absent 0 NONE None
2/3 LSXM1QGS36HB1 Normal 0 S12508X-AF-2710 None
2/4 NONE Absent 0 NONE None
2/5 NONE Absent 0 NONE None
2/6 NONE Absent 0 NONE None
2/7 NONE Absent 0 NONE None
2/8 NONE Absent 0 NONE None
2/9 NONE Absent 0 NONE None
2/10 NONE Absent 0 NONE None
2/11 NONE Absent 0 NONE None
2/12 NONE Absent 0 NONE None
2/13 NONE Absent 0 NONE None
2/14 LSXM1SFH08D1 Normal 0 S12508X-AF-2710 None
2/15 NONE Absent 0 NONE None
The command output indicates that the two devices have formed an IRF fabric. Chassis 1 is the master and Chassis 2 is the subordinate member. The two members are operating correctly.
Performing an ISSU
Verifying that the member devices have sufficient storage space
# View the amount of free storage space on member devices.
· On the master:
<DeviceA> dir chassis1slot0#flash:/
Directory of flash:
0 -rw- 2901 Jan 01 2011 03:13:38 210235A1UMH1610000122017011911451076132.ak
1 -rw- 120552448 Jan 02 2011 11:37:58 R2710.ipe
2 -rw- 118386 Jan 01 2011 02:43:16 diag_A_B_C_20110101-021505.tar.gz
3 -rw- 104500 Jan 01 2011 00:29:18 diag_H3C_20110101-002803.tar.gz
4 -rw- 113895 Jan 01 2011 01:11:50 diag_TD2+_20110101-011053.tar.gz
5 drw- - Jan 01 2011 00:01:13 diagfile
6 -rw- 512 Jan 01 2011 01:00:05 fd8ef19a214ea12039a2f5ac6ef936fd.cfg
7 -rw- 4086 Jan 02 2011 10:52:18 ifindex.dat
8 -rw- 238 Jan 01 2011 11:05:44 lauth.dat
9 drw- - Jan 01 2011 03:14:28 license
10 drw- - Jan 01 2011 05:18:02 logfile
11 drw- - Jan 01 2011 01:02:09 ovsdb
12 drw- - Jan 01 2011 11:05:58 pkey
13 drw- - Jan 01 2011 11:05:50 pki
14 -rw- 14478336 Jan 01 2011 10:38:36 boot-e2601.bin
15 -rw- 14476288 Jan 01 2011 10:52:24 boot-r2710.bin
16 -rw- 102051840 Jan 01 2011 10:44:11 system-e2601.bin
17 -rw- 106068992 Jan 01 2011 10:57:47 system-r2710.bin
18 drw- - Jan 01 2011 00:01:13 seclog
19 -rw- 15632 Jan 02 2011 10:52:25 startup.cfg
20 -rw- 313105 Jan 02 2011 10:52:26 startup.mdb
21 drw- - Jan 01 2011 03:08:27 test
22 -rw- 163053 Jan 01 2011 10:45:18 test1.tar.gz
23 -rw- 149436 Jan 01 2011 10:46:32 test2.tar.gz
24 dr-- - Jan 01 2011 00:49:46 versionInfo
25 -rw- 3844 Jan 01 2011 03:26:03 vlan.txt
26 -rw- 4214 Jan 01 2011 03:01:40 xinjianshiyan.txt
524288 KB total (170948 KB free)
· On the subordinate member:
<DeviceA> dir chassis2slot0#flash:/
Directory of flash:
0 -rw- 2901 Jan 01 2011 03:13:38 210235A1UMH1610000122017011911451076132.ak
1 -rw- 120552448 Jan 02 2011 11:37:58 R2710.ipe
2 -rw- 118386 Jan 01 2011 02:43:16 diag_A_B_C_20110101-021505.tar.gz
3 -rw- 104500 Jan 01 2011 00:29:18 diag_H3C_20110101-002803.tar.gz
4 -rw- 113895 Jan 01 2011 01:11:50 diag_TD2+_20110101-011053.tar.gz
5 drw- - Jan 01 2011 00:01:13 diagfile
6 -rw- 512 Jan 01 2011 01:00:05 fd8ef19a214ea12039a2f5ac6ef936fd.cfg
7 -rw- 4086 Jan 02 2011 10:52:18 ifindex.dat
8 -rw- 238 Jan 01 2011 11:05:44 lauth.dat
9 drw- - Jan 01 2011 03:14:28 license
10 drw- - Jan 01 2011 05:18:02 logfile
11 drw- - Jan 01 2011 01:02:09 ovsdb
12 drw- - Jan 01 2011 11:05:58 pkey
13 drw- - Jan 01 2011 11:05:50 pki
14 -rw- 14478336 Jan 01 2011 10:38:36 boot-e2601.bin
15 -rw- 14476288 Jan 01 2011 10:52:24 boot-r2710.bin
16 -rw- 102051840 Jan 01 2011 10:44:11 system-e2601.bin
17 -rw- 106068992 Jan 01 2011 10:57:47 system-r2710.bin
18 drw- - Jan 01 2011 00:01:13 seclog
19 -rw- 15632 Jan 02 2011 10:52:25 startup.cfg
20 -rw- 313105 Jan 02 2011 10:52:26 startup.mdb
21 drw- - Jan 01 2011 03:08:27 test
22 -rw- 163053 Jan 01 2011 10:45:18 test1.tar.gz
23 -rw- 149436 Jan 01 2011 10:46:32 test2.tar.gz
24 dr-- - Jan 01 2011 00:49:46 versionInfo
25 -rw- 3844 Jan 01 2011 03:26:03 vlan.txt
26 -rw- 4214 Jan 01 2011 03:01:40 xinjianshiyan.txt
524288 KB total (170948 KB free)
The command output shows the amount of free storage space on each member device.
# Compare the sizes of the upgrade image files with the amount of free storage space. If the free storage space is insufficient, continue with the next step to delete unused files to release more storage space.
# Delete unused files on the member devices.
· On the master:
<DeviceA> delete /unreserved chassis1slot0#flash:/r2710.ipe
The file cannot be restored. Delete flash:/r2710.ipe? [Y/N]:y
Deleting the file permanently will take a long time. Please wait...
Deleting file flash:/r2710.ipe... Done.
· On the subordinate member:
<DeviceA> delete /unreserved chassis2slot0#flash:/r2710.ipe
The file cannot be restored. Delete flash:/r2710.ipe? [Y/N]:y
Deleting the file permanently will take a long time. Please wait...
Deleting file flash:/r2710.ipe... Done.
|
NOTE: · The delete /unreserved file command deletes a file permanently. The file cannot be restored. · The delete file command (without /unreserved) moves a file to the recycle bin. The file is still using storage space. To delete the file from the recycle bin, you must execute the reset recycle-bin command in the directory where the file resided. |
Downloading the upgrade file to the master
You can use FTP or TFTP to download the upgrade file. In this example, FTP is used and the device acts as the FTP client. The PC acts as the FTP server.
1. Run the FTP server program on the PC. Configure a user and set the password. Specify the working directory and save the upgrade file to the directory. The IP address of the PC is 2.2.2.2.
|
NOTE: The device is not shipped with an FTP server program. You must purchase and install an FTP server program separately. |
2. Make sure the device and PC can reach each other. (Details not shown.)
3. Download the upgrade file to the root directory of the default file system on the master. In this example, the upgrade file is R2712.ipe.
# Log in to the FTP server from the IRF fabric.
<DeviceA> ftp 2.2.2.2
Connected to 2.2.2.2 (2.2.2.2).
220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user
User (2.2.2.2:(none)):username ---Enter the username.
331 Give me your password, please
Password: ---Enter the password.
230 Logged in successfully
Remote system type is MSDOS.
ftp>
# Set the file transfer mode to binary. The default file transfer mode is binary.
ftp> binary
200 Type is Image (Binary)
# Download upgrade file R2712.ipe to the root directory of the default file system on the master.
ftp> get r2712.ipe
227 Entering Passive Mode (2,2,2,2,7,100)
150 "C:\r2712.ipe " file ready to send (385 bytes) in in IMAGE / Binary mode
226 Transfer finished successfully.
74948608 bytes received in 35.974 seconds (896.00 kbyte/s)
ftp> bye
221 Windows FTP Server (WFTPD, by Texas Imperial Software) says goodbye
Performing an ISSU step by step
1. Verify that the device is in Stable state, that is, the State field in the output from the display system stable state command displays Stable.
<DeviceA> display issu state
ISSU state: Init
Compatibility: Unknown
Work state: Normal
Upgrade method: Chassis by chassis
Upgraded chassis: None
Current upgrading chassis: None
Current version list:
boot: 7.1.070, Release 2710
system: 7.1.070, Release 2710
Current software images:
flash:/boot-r2710.bin
flash:/system-r2710.bin
<DeviceA> display system stable state
System state : Stable
Redundancy state : Stable
Chassis Slot CPU Role State
1 0 0 Active Stable
1 3 0 Other Stable
1 14 0 Other Stable
2 0 0 Active Stable
2 3 0 Other Stable
2 14 0 Other Stable
The command output shows that both IRF member devices are in Stable state. You can start an ISSU.
2. Upgrade the startup software images and specify the images as the main startup software images on the subordinate member.
In IRF mode, an ISSU is performed chassis by chassis. Start an ISSU from the subordinate member.
<DeviceA> issu load file ipe flash:/r2712.ipe chassis 2
This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y
Verifying the file flash:/r2712.ipe on chassis 2 slot 0...........Done.
Decompressing file boot-r2712.bin to flash:/boot-r2712.bin.....................Done.
Decompressing file system-r2712.bin to flash:/system-r2712.bin...............................................................................................................................................Done.
Decompression completed.
Do you want to delete flash:/r2712.ipe now? [Y/N]:n
Copying file flash:/boot-r2712.bin to chassis2slot0#flash:/boot-r2712.bin.....................................Done.
Copying file flash:/system-r2712.bin to chassis2slot0#flash:/system-r2712.bin.............................................................................................................................................................................................................................................................................Done.
Verifying the file flash:/boot-r2712.bin on chassis 2 slot 0.....Done.
Verifying the file flash:/system-r2712.bin on chassis 2 slot 0.........................Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
flash:/boot-r2712.bin
Running Version New Version
Release 2710 Release 2712
flash:/system-r2712.bin
Running Version New Version
Release 2710 Release 2712
Chassis Slot Upgrade Way
2 0 Reboot
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait.......Done.
3. Verify that the system is in a stable state.
|
IMPORTANT: After executing the issu load command, you must make sure the system enters a stable state before you proceed to the next step. If the system reported an error in the previous step, verify that the system is in a stable state and then use the issu rollback command to roll back the upgrade. |
<DeviceA> display issu state
ISSU state: Loaded
Compatibility: Compatible
Work state: Normal
Upgrade method: Chassis by chassis
Upgraded chassis:
chassis 2
Current upgrading chassis: None
Previous version list:
boot: 7.1.070, Release 2710
system: 7.1.070, Release 2710
Previous software images:
flash:/boot-r2710.bin
flash:/system-r2710.bin
Upgrade version list:
boot: 7.1.070, Release 2712
system: 7.1.070, Release 2712
Upgrade software images:
flash:/boot-r2712.bin
flash:/system-r2712.bin
The command output shows that the ISSU process is in Loaded state (a stable state) and is waiting for a switchover. Chassis 2 has been upgraded from Release 2710 to Release 2712 and Chassis 1 has not.
4. Perform a master/subordinate switchover.
<DeviceA> issu run switchover
Upgrade summary according to following table:
flash:/boot-r2712.bin
Running Version New Version
Release 2710 Release 2712
flash:/system-r2712.bin
Running Version New Version
Release 2710 Release 2712
Chassis Slot Switchover Way
1 0 Master subordinate switchover
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait.......
5. Verify that the system is in a stable state.
|
IMPORTANT: After executing the issu run switchover command, you must make sure the system enters a stable state before you proceed to the next step. If the system reported an error in the previous step, verify that the system is in a stable state and then use the issu rollback command to roll back the upgrade. |
<DeviceA> display issu state
ISSU state: Switchover
Compatibility: Compatible
Work state: Normal
Upgrade method: Chassis by chassis
Upgraded chassis:
chassis 2
Current upgrading chassis: None
Previous version list:
boot: 7.1.070, Release 2710
system: 7.1.070, Release 2710
Previous software images:
flash:/boot-r2710.bin
flash:/system-r2710.bin
Upgrade version list:
boot: 7.1.070, Release 2712
system: 7.1.070, Release 2712
Upgrade software images:
flash:/boot-r2712.bin
flash:/system-r2712.bin
The command output shows that the ISSU process is in Switchover state (a stable state). A master/subordinate switchover is finished and the ISSU process is waiting for a commit operation. Chassis 2 has been upgraded from Release 2710 to Release 2712 and Chassis 1 has not.
6. Upgrade the original master.
<DeviceA> issu commit chassis 1
Upgrade summary according to following table:
flash:/boot-r2712.bin
Running Version New Version
Release 2710 Release 2712
flash:/system-r2712.bin
Running Version New Version
Release 2710 Release 2712
Chassis Slot Upgrade Way
1 0 Reboot
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait......Done.
|
NOTE: The automatic rollback timer starts when you execute the issu run switchover command. By default, the automatic rollback timer is 45 minutes. Please execute the issu commit command before the timer expires. After using this command for one member, wait for the member to restart and join the IRF fabric before using this command for another member. |
7. Verify that the ISSU is finished.
<DeviceA> display issu state
ISSU state: Init
Compatibility: Unknown
Work state: Normal
Upgrade method: Chassis by chassis
Upgraded chassis: None
Current upgrading chassis: None
Current version list:
boot: 7.1.070, Release 2712
system: 7.1.070, Release 2712
Current software images:
flash:/boot-r2712.bin
flash:/system-r2712.bin
If the ISSU state field displays Init, the ISSU is finished.
References
For more information about ISSU, see Fundamentals Configuration Guide.
For more information about IRF, see IRF Configuration Guide.