Contents

Introduction· 1

Prerequisites· 1

Example: Patching software· 1

Network configuration· 1

Applicable hardware and software versions· 1

Restrictions and guidelines· 2

Procedures· 2

Verifying the configuration· 2

Configuration files· 3

 

Introduction

This document provides software patching examples that use ISSU install commands.

Prerequisites

The configuration 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.

Example: Patching software

Network configuration

As shown in Figure 1, the two-chassis IRF fabric and the TFTP server can reach each other. The IRF members are running CMW710-SYSTEM-R1110P01, and they have not been patched before.

Use the patch image file CMW710-SYSTEM-R1110P01H04.bin to fix bugs without rebooting the members.

Figure 1 Network diagram

 

Applicable hardware and software versions

The following matrix shows the hardware and software versions to which this configuration example is applicable:

 

Hardware	Software version
S6520X-HI switch series S6520X-EI switch series	Supported in Release 1110P01
S6520X-SI switch series S6520-SI switch series S5000-EI switch series MS4600 switch series	Supported in Release 1110P01

 

Restrictions and guidelines

When you patch software for a centralized IRF device, follow these restrictions and guidelines:

·     The first time you install patch images, you must start with the master. For subsequent patch installations, you must start with the subordinate members.

·     The patch image version must match the device model and Comware version. For example, to fix bugs in CMW710-SYSTEM-R1110P01, you must use CMW710-SYSTEM-R1110P01H04.bin.

Procedures

# Download the patch image file CMW710-SYSTEM-R1110P01H04.bin from the TFTP server to the root directory of the flash memory on the master.

<Sysname> tftp 2.2.2.2 get CMW710-SYSTEM-R1110P01H04.bin

Press CTRL+C to abort.

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

                                 Dload  Upload   Total   Spent    Left  Speed

100 25.2M    0 25.2M    0     0   210k      0 --:--:--  0:02:02 --:--:--  209k

# Activate the patch images on the master first and then on the subordinate member. This sequence is used because no patch images have been activated on the IRF fabric.

<Sysname> install activate patch flash:/CMW710-SYSTEM-R1110P01H04.bin slot 1

This operation maybe take several minutes, please wait.............Done.

<Sysname> install activate patch flash:/CMW710-SYSTEM-R1110P01H04.bin slot 2

This operation maybe take several minutes, please wait.............Done.

The patch images take effect immediately after they are activated.

# For the patch images to take effect after a reboot, commit the software changes.

<Sysname> install commit

Verifying the configuration

# Verify that the patch images have been activated successfully.

<Sysname> display install active

Active packages on slot 1:

  flash:/CMW710-BOOT-R1110P01.bin

  flash:/CMW710-SYSTEM-R1110P01.bin

  flash:/CMW710-SYSTEM-R1110P01H04.bin

Active packages on slot 2:

  flash:/CMW710-BOOT-R1110P01.bin

  flash:/CMW710-SYSTEM-R1110P01.bin

  flash:/CMW710-SYSTEM-R1110P01H04.bin

# Verify that the patch image file has been added to the main startup software image list so the images can take effect after a reboot.

<Sysname> display install committed

Committed packages on slot 1:

  flash:/CMW710-BOOT-R1110P01.bin

  flash:/CMW710-SYSTEM-R1110P01.bin

  flash:/CMW710-SYSTEM-R1110P01H04.bin

Committed packages on slot 2:

  flash:/CMW710-BOOT-R1110P01.bin

  flash:/CMW710-SYSTEM-R1110P01.bin

  flash:/CMW710-SYSTEM-R1110P01H04.bin

Configuration files

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