Before performing an ISSU, use the display version comp-matrix command to view the ISSU method in the Upgrade Way field. Table 1 shows a matrix of ISSU types and ISSU methods.

Table 1 Matrix of ISSU types and ISSU methods

ISSU type	ISSU method displayed in Upgrade Way
Compatible	· Service Upgrade · File Upgrade · ISSU Reboot · Reboot
Incompatible	Incompatible upgrade

ISSU type

ISSU method displayed in Upgrade Way

Compatible

· Service Upgrade

· File Upgrade

· ISSU Reboot

· Reboot

Incompatible

Incompatible upgrade

Prerequisites

The examples in this document were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

This document assumes that you have basic knowledge of ISSU.

General configuration restrictions and guidelines

To ensure a successful ISSU, complete the following tasks before performing an ISSU:

· Identify availability of ISSU:

¡ Read the software release notes to identify support of the device for ISSU.

¡ To perform sequential upgrade for switching fabrics, make sure the device has a minimum of two switching fabric modules.

¡ To perform an ISSU reboot upgrade, make sure the device does not have interface cards with 512 MB of memory.

· Verify the device operating status:

¡ Use the display device command to verify that no cards are in Fault state.

¡ Use the display mdc command to verify that all MDCs are in active state.

· Use the dir command to verify that the MPUs have sufficient storage space for the upgrade images. If the storage space is not sufficient, delete unused files.

· For service continuity during ISSU, configure the following feature settings:

Feature	Setting requirements
GR/NSR	Enable GR or NSR for protocols including LDP, RSVP, OSPF, ISIS, BGP, and FSPF.
BFD	Disable BFD for protocols including LDP, RSVP, OSPF, ISIS, RIP, BGP, VRRP, and NQA.
Ethernet link aggregation	Use the long LACP timeout interval (the lacp period short command is not configured) on all member ports in dynamic aggregation groups.
IRF	Configure IRF bridge MAC persistence as follows: · Compatible upgrade—Configure the irf mac-address persistent timer or irf mac-address persistent always command. · Incompatible upgrade—Configure the irf mac-address persistent always command if the bridge MAC address is the MAC address of the device for which you want to execute the issu load command.

· Log in to the device through the console port.

If you use Telnet or SSH, you might be disconnected from the device before the ISSU is completed.

During an ISSU, follow these restrictions and guidelines:

· In a multiuser environment, make sure no other administrators access the device while you are performing the ISSU.

· Do not perform any of the following tasks during an ISSU:

¡ Reboot, add, or remove cards.

¡ Execute commands that are irrelevant to the ISSU.

¡ Modify, delete, or rename image files.

Example: Performing a compatible ISSU (in standalone mode)

Network requirements

As shown inFigure 1, the device and the TFTP server can reach each other. The device has two MPUs: active MPU in slot 0 and standby MPU in slot 1.

Perform a compatible ISSU on the device to upgrade the HTTP feature from r0201 to r0202.

Figure 1 Network diagram

Software version used

This configuration example was created and verified on S12500-CMW710-R7328P02.

Configuration restrictions and guidelines

When you perform a compatible ISSU, follow these restrictions and guidelines:

· You only need to download images to the active MPU. The system prompts whether to copy the images to the standby MPU during the upgrade.

· To ensure service continuity, upgrade the standby MPU prior to the active MPU.

Configuration procedures

# Download the new image file http-r0202.bin from the TFTP server.

<Device> tftp 2.2.2.2 get http-r0202.bin

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 256k 100 256k 0 0 764k 0 --:--:-- --:--:-- --:--:-- 810k

# Display active software images.

<Device> display install active

Active packages on slot0:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0201.bin

Active packages on slot 1:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0201.bin

Active packages on slot 2:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0201.bin

Active packages on slot 3:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0201.bin

# Display version compatibility information and identify the ISSU method.

<Device> display version comp-matrix file feature flash:/http-r0202.bin

Feature image: flash:/http-r0202.bin

Version:

7.1.045-r0202

Version Compatibility List:

7.1.045-r0201

7.1.045-r0202

Version Dependency System List:

7.1.045-r0201

7.1.045-r0202

Slot Upgrade Way

0 File Upgrade

0.1 File Upgrade

1 File Upgrade

1.1 File Upgrade

2 File Upgrade

3 File Upgrade

Influenced service according to following table on slot 0:

flash:/http-r0202.bin

HTTP

Influenced service according to following table on slot 1:

flash:/http-r0202.bin

HTTP

The output shows that the running version r0201 is in the version compatibility list. A file upgrade is recommended. The HTTP module will be rebooted during the ISSU.

# Set the automatic rollback timer to 120 minutes (the default is 45 minutes).

<Device> system-view

[Device] issu rollback-timer 120

<Device> quit

# Upgrade the HTTP image for the standby MPU.

<Device> issu load file feature flash:/http-r0202.bin slot 1

This operation will delete the rollback point information and ISSU log information

for the previous upgrade and get unsaved configuration lost. Continue? [Y/N]:y

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 File Upgrade

1.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Verify that the upgrade operation is completed on the standby MPU (ISSU status is loaded).

<Device> display issu state

ISSU state: loaded

Compatibility: Compatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot: None

Current upgrading slot:

slot 1

Previous version list:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0201.bin

Upgrade version list:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

# Perform an active/standby switchover.

<Device> issu run switchover

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

0 Active standby process switchover

0.1 Active standby process switchover

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Upgrade the original active MPU.

<Device> issu commit slot 0

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

0 Service Upgrade

0.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Verify that the ISSU process is completed (the ISSU status is Init).

<Device> display issu state

ISSU state: Init

Compatibility: Compatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot: None

Current version list:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Current software images:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Verifying the configuration

# Verify that the HTTP feature has been upgraded to r0202.

<Device> display install active

Active packages on slot 0:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Active packages on slot 1:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Active packages on slot 2:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Active packages on slot 3:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Configuration files

The system does not save the commands used in the configuration procedures to a configuration file.

Example: Performing an incompatible ISSU (in standalone mode)

Network requirements

As shown in Figure 2, the device and the TFTP server can reach each other. The device has two MPUs: active MPU in slot 0 and standby MPU in slot 1.

Perform an incompatible ISSU on the device to upgrade the HTTP feature from r0201 to r0202.

Figure 2 Network diagram

Software version used

This configuration example was created and verified on S12500-CMW710-R7328P02.

Configuration restrictions and guidelines

When you perform the incompatible ISSU, follow these restrictions and guidelines:

· You only need to download images to the active MPU. The system prompts whether to copy the images to the standby MPU during the upgrade.

· To ensure service continuity, upgrade the standby MPU prior to the active MPU.

Configuration procedures

# Download the new image file http-r0202.bin from the TFTP server.

<Device> tftp 2.2.2.2 get http-r0202.bin

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 256k 100 256k 0 0 764k 0 --:--:-- --:--:-- --:--:-- 810k

# Display active software images.

<Device> display install active

Active packages on slot 0:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0201.bin

Active packages on slot 1:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0201.bin

Active packages on slot 2:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0201.bin

Active packages on slot 3:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0201.bin

# Display version compatibility information and identify the ISSU method.

<Device> display version comp-matrix file feature flash:/http-r0202.bin

Feature image: flash:/http-r0202.bin

Version:

7.1.045-r0202

Version compatibility list:

7.1.045-r0202

Version dependency system list:

7.1.045-r0201

7.1.045-r0202

Incompatible upgrade.

The output shows that the two versions are incompatible (the running version r0201 is not in the version compatibility list). The upgraded MPU will reboot to use the new image.

# Upgrade the HTTP image for the standby MPU.

<Device> issu load file feature flash:/http-r0202.bin slot 1

This operation will delete the rollback point information and ISSU log information for the previous upgrade and get unsaved configuration lost. Continue? [Y/N]:y

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 Reboot

1.1 Reboot

Upgrading software images to incompatible versions. Continue? [Y/N]: y

# Verify that the upgrade operation is completed on the standby MPU (ISSU status is loaded).

<Device> display issu state

ISSU state: loaded

Compatibility: Incompatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot: None

Current upgrading slot:

slot 1

Previous version list:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0201.bin

Upgrade version list:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

# Upgrade the HTTP image for the active MPU.

<Device> issu run switchover

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

0 Reboot

0.1 Reboot

Upgrading software images to incompatible versions. Continue? [Y/N]: y

# Verify that the ISSU process is completed (the ISSU status is Init).

<Device> display issu state

ISSU state: Init

Compatibility: Incompatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot: None

Current version list:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Current software images:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Verifying the configuration

# Verify that the HTTP feature has been upgraded to r0202.

<Device> display install active

Active packages on slot 0:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Active packages on slot 1:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Active packages on slot 2:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Active packages on slot 3:

flash:/boot-r2111.bin

flash:/system-r2111.bin

flash:/http-r0202.bin

Configuration files

The system does not save the commands used in the configuration procedures to a configuration file.

Example: Performing a compatible ISSU (in IRF mode)

Network requirements

As shown in Figure 3, the two-chassis IRF fabric and the TFTP server can reach each other. Each IRF member has one MPU in slot 0 and one MPU in slot 1. The MPU in slot 0 of the master is the global active MPU.

Perform a compatible ISSU on the IRF to upgrade the boot and system images from R2111 to R2112.

Figure 3 Network diagram

Software version used

This configuration example was created and verified on S12500-CMW710-R7328P02.

Configuration restrictions and guidelines

When you perform the compatible ISSU, follow these restrictions and guidelines:

· You only need to download images to the global active MPU. The system prompts whether to copy the images to the global standby MPUs during the upgrade.

· To ensure service continuity, upgrade the subordinate member prior to the master. On a dual-MPU single-chassis IRF fabric, upgrade the standby MPU prior to the active MPU.

Configuration procedures

# Download the new image file test.ipe from the TFTP server to the master. The file includes the boot image file boot-R2112.bin and the system image file system-R2112.bin.

<Master> tftp 2.2.2.2 get test.ipe

# Display current software images.

<Master> display install active

Active packages on chassis 1 slot 0:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 1 slot 0.1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 1 slot 1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 1 slot 1.1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 2 slot 0:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 2 slot 0.1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 2 slot 1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 2 slot 1.1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

# Display version compatibility information and identify the ISSU method.

<Master> display version comp-matrix file ipe flash:/test.ipe

Verifying image file.......Done.

Boot image: BOOT-R2112.bin

Version:

7.1.045P99

System image: SYSTEM-R2112.bin

Version:

7.1.045-R2112

Version compatibility list:

7.1.045-R2112

7.1.045-R2111

Version dependency boot list:

7.1.045P99

1 0 Service Upgrade

1 0.1 ISSU Reboot

1 1 Service Upgrade

1 1.1 ISSU Reboot

2 0 Service Upgrade

2 0.1 ISSU Reboot

2 1 Service Upgrade

2 1.1 ISSU Reboot

The output shows that the two versions are compatible and the ISSU reboot method is recommended.

# Set the rollback timer to 120 minutes (the default is 45 minutes).

<Master> system-view

[Master] issu rollback-timer 120

<Master> quit

# Upgrade the subordinate member.

<Master> issu load file ipe flash:/test.ipe chassis 2

This operation will delete the rollback point information for the previous upgra

de and maybe get unsaved configuration lost. Continue? [Y/N]:y

Verifying image file.......Done.

flash:/BOOT-R2112.bin already exists on chassis 2

flash:/SYSTEM-R2112.bin already exists on chassis 2

Decompressing file BOOT-R2112.bin to flash:/BOOT-R2112.b

in...........................................Done.

Decompressing file SYSTEM-R2112.bin to flash:/SYSTEM-R211

2.bin...........................................................................

................................................................................

.......................Done.

Upgrade summary according to following table:

flash:/BOOT-R2112.bin

Running Version New Version

Release 2111P01 Feature com

flash:/SYSTEM-R2112.bin

Running Version New Version

Release 2111P01 Feature com

Chassis Slot Upgrade Way

2 0 Service Upgrade

2 0.1 ISSU Reboot

2 1 Service Upgrade

2 1.1 ISSU Reboot

Upgrading software images to compatible versions. Continue? [Y/N]: y

# After the subordinate member restarts up, verify that the upgrade operation is completed on the member (ISSU status is Loaded).

<Master> display issu state

ISSU state: Loaded

Compatibility: Compatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 1

Current upgrading chassis: None

Previous version list:

boot: 7.1.045P22, Release 2111P01

system: 7.1.045, Release 2111P01

Previous software images:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Upgrade version list:

boot: 7.1.045P99, Feature com

system: 7.1.045, Feature com

Upgrade software images:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

# Perform a master/subordinate switchover.

<Master> issu run switchover

Upgrade summary according to following table:

flash:/BOOT-R2112.bin

Running Version New Version

Release 2111P01 Feature com

flash:/SYSTEM-R2112.bin

Running Version New Version

Release 2111P01 Feature com

Chassis Slot Switchover Way

1 0 Active standby process switchover

1 0.1 Active standby process switchover

Upgrading software images to compatible versions. Continue? [Y/N]:y

# Verify that the switchover operation is completed (the ISSU status is Switchover).

<Master> display issu state

ISSU state: Switchover

Compatibility: Compatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 1

Current upgrading chassis: None

Previous version list:

boot: 7.1.045P22, Release 2111P01

system: 7.1.045, Release 2111P01

Previous software images:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Upgrade version list:

boot: 7.1.045P99, Feature com

system: 7.1.045, Feature com

Upgrade software images:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

# Upgrade the original master.

<Master> issu commit chassis 1

This operation will delete the rollback point information for the previous upgra

de and maybe get unsaved configuration lost. Continue? [Y/N]:y

Verifying image file.......Done.

flash:/BOOT-R2112.bin already exists on chassis 1

flash:/SYSTEM-R2112.bin already exists on chassis 1

Decompressing file BOOT-R2112.bin to flash:/BOOT-R2112.b

in...........................................Done.

Decompressing file SYSTEM-R2112.bin to flash:/SYSTEM-R2112

.bin..........................................................................

................................................................................

.......................Done.

Upgrade summary according to following table:

flash:/BOOT-R2112.bin

Running Version New Version

Release 2111P01 Feature com

flash:/SYSTEM-R2112.bin

Running Version New Version

Release 2111P01 Feature com

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 ISSU Reboot

1 1 Service Upgrade

1 1.1 ISSU Reboot

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Verify that the ISSU process is completed (the ISSU status is Init).

<Master> display issu state

ISSU state: Init

Compatibility: Compatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis: None

Current upgrading chassis: None

Current version list:

boot: 7.1.045P99, Feature com

system: 7.1.045, Feature com

Current software images:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Verifying the configuration

# Verify that the boot and system images have been upgraded to R2112.

<Master> display install active

Active packages on chassis 1 slot 0:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 1 slot 0.1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 1 slot 1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 1 slot 1.1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 2 slot 0:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 2 slot 0.1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 2 slot 1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 2 slot 1.1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Configuration files

The system does not save the commands used in the configuration procedures to a configuration file.

Example: Performing an incompatible ISSU (in IRF mode)

Network requirements

As shown in Figure 4, the two-chassis IRF fabric and the TFTP server can reach each other. Each IRF member has one MPU in slot 0 and one MPU in slot 1. The MPU in slot 0 of the master is the global active MPU.

Perform an incompatible ISSU on the IRF to upgrade the boot and system images from R2111 to R2112.

Figure 4 Network diagram

Software version used

This configuration example was created and verified on S12500-CMW710-R7328P02.

Configuration restrictions and guidelines

When you perform the incompatible ISSU, follow these restrictions and guidelines:

· You only need to download images to the global active MPU. The system prompts whether to copy the images to the global standby MPUs during the upgrade.

· To ensure service continuity, upgrade the subordinate member prior to the master. On a dual-MPU single-chassis IRF fabric, upgrade the standby MPU prior to the active MPU.

Configuration procedures

# Download the new image file test.ipe from the TFTP server to the master. The file includes the boot image file boot-R2112.bin and the system image file system-R2112.bin.

<Device> tftp 2.2.2.2 get test.ipe

# Display current software images.

<Master> display boot-loader

Active packages on chassis 1 slot 0:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 1 slot 0.1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 1 slot 1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 1 slot 1.1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 2 slot 0:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 2 slot 0.1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 2 slot 1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Active packages on chassis 2 slot 1.1:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

# Display version compatibility information and identify the ISSU method.

<Master> display version comp-matrix file ipe flash:/test.ipe

Verifying image file........Done.

Boot image: BOOT-R2112.bin

Version:

7.1.045P99

System image: SYSTEM-R2112.bin

Version:

7.1.045-R2112

Version compatibility list:

7.1.045-R2112

Version dependency boot list:

7.1.045P99

Incompatible upgrade.

The output shows that the two versions are incompatible and a reboot is required during the ISSU.

# Upgrade the subordinate member.

<Master> issu load file ipe flash:/test.ipe chassis 2

This operation will delete the rollback point information for the previous upgra

de and maybe get unsaved configuration lost. Continue? [Y/N]:y

Verifying image file.......Done.

flash:/BOOT-com.bin already exists on chassis 2

flash:/SYSTEM-com.bin already exists on chassis 2

Decompressing file BOOT-R2112.bin to flash:/BOOT-R2112.b

in...........................................Done.

Decompressing file SYSTEM-R2112.bin to flash:/SYSTEM-R211

2.bin...........................................................................

................................................................................

.......................Done.

Upgrade summary according to following table:

flash:/BOOT-R2112.bin

Running Version New Version

Release 2111P01 Feature com

flash:/SYSTEM-R2112.bin

Running Version New Version

Release 2111P01 Feature com

Chassis Slot Upgrade Way

2 0 Reboot

2 0.1 Reboot

2 1 Reboot

2 1.1 Reboot

Upgrading software images to compatible versions. Continue? [Y/N]: y

# After the subordinate member restarts up, verify that the upgrade operation is completed on the member (ISSU status is Loaded)

<Master> display issu state

ISSU state: Loaded

Compatibility: Incompatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 1

Current upgrading chassis: None

Previous version list:

boot: 7.1.045P22, Release 2111P01

system: 7.1.045, Release 2111P01

Previous software images:

flash:/BOOT-R2111.bin

flash:/SYSTEM-R2111.bin

Upgrade version list:

boot: 7.1.045P99, Feature com

system: 7.1.045, Feature com

Upgrade software images:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

# Perform a master/subordinate switchover to complete the ISSU process.

<Master> issu run switchover

Upgrade summary according to following table:

flash:/BOOT-R2112.bin

Running Version New Version

Release 2111P01 Feature com

flash:/SYSTEM-R2112.bin

Running Version New Version

Release 2111P01 Feature com

Chassis Slot Upgrade Way

1 0 Active standby process switchover

1 0.1 Active standby process switchover

1 1 Active standby process switchover

1 1.1 Active standby process switchover

Upgrading software images to incompatible versions. Continue? [Y/N]: y

# Verify that the ISSU process is completed (the ISSU status is Init).

<Master> display issu state

ISSU state: Init

Compatibility: Incompatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis: None

Current upgrading chassis: None

Current version list:

boot: 7.1.045P99, Feature com

system: 7.1.045, Feature com

Current software images:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Verifying the configuration

# Verify that the boot and system images have been upgraded to R2112.

<Master> display install active

Active packages on chassis 1 slot 0:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 1 slot 0.1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 1 slot 1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 1 slot 1.1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 2 slot 0:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 2 slot 0.1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 2 slot 1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Active packages on chassis 2 slot 1.1:

flash:/BOOT-R2112.bin

flash:/SYSTEM-R2112.bin

Configuration files

The system does not save the commands used in the configuration procedures to a configuration file.

01-Fundamentals Configuration Examples

Configuration restrictions and guidelines

Configuration files

Network requirements

Configuration restrictions and guidelines

Network requirements

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us