quidway s9300 terabit routing switch v100r006c00spc800 upgrade guide.doc

Contents

Quidway S9300 Terabit Routing SwitchV100R006C00SPC800Upgrade Guide

Issue02

Date2011-12-28

DOCPROPERTY Confidential

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address:Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website:http://www.huawei.com

Email:[email protected]

About This DocumentChange HistoryChanges between document issues are cumulative. The latest document issue contains all the changes made in earlier issues.Issue 02 (2011-12-28)This issue is the second official release, and includes the following changes:Modified section 2.1.3

REF _Ref310931554 \h Precautions.Issue 01 (2011-09-30)This issue is the first official release.Contents

iiAbout This Document

11 Upgrade Overview

32 Command Line Upgrade

32.1 Before You Start

32.1.1 Version Requirements

42.1.2 Impact of the Upgrade

42.1.3 Precautions

62.2 Upgrade Process Overview

72.3 Preparing for the Upgrade

72.3.1 Pre-upgrade Checklist

82.3.2 Obtaining Upgrade Reference Documents

82.3.3 Obtaining Tools

82.3.4 Obtaining Upgrade Software

82.3.5 Obtaining the License File

92.3.6 Preparing the Configuration File

92.3.7 Verifying the Current Version

92.3.8 Verifying the Running Status of the Device

102.3.9 Setting Up the Upgrade Environment

112.3.10 Backing Up CF Card Data

112.3.11 Checking the Space on the CF Cards

132.4 Performing the Upgrade

142.4.1 Loading System Software

212.4.2 Verifying File Loading

212.4.3 Specifying the System Software

232.4.4 Restarting the Device

232.4.5 Activating the License

232.5 Verifying the Upgrade

232.5.1 Verification Checklist

242.5.2 Verifying the Current System Software

242.5.3 Verifying That All the Programs Have Been Upgraded

252.5.4 Verifying Board Registration Status

252.5.5 Verifying Configuration Restoration

252.5.6 Verifying Services

262.6 Rolling Back to an Earlier Version

262.6.1 Rollback Scenarios and Methods

272.6.2 Rollback Process

272.6.3 Specifying the Previous System Software for Next Startup


282.6.5 Verifying the Rollback

293 ISSU Upgrade




293.1.3 Impact on the System During the Upgrade

293.1.4 Impact on the System After the Upgrade

293.2 Precautions


303.3.1 Verifying That MPUs Work in 1:1 Backup Mode

303.3.2 Verifying the CPLD Logic on the MPUs

313.4 (Optional) Checking the ISSU Upgrade Environment

313.5 (Optional) Setting the ISSU Rollback Timer

323.6 Performing the ISSU Upgrade

323.6.1 Running issu check to Upgrade Slave MPU

333.6.2 Running issu start to Perform ISSU

343.6.3 (Optional) Running issu abort to Abort ISSU Upgrade

353.6.4 Running issu switchover to Switch the Control Plane

363.6.5 Running issu confirm to Verify the ISSU Upgrade

363.7 Verifying the ISSU Upgrade







404 CSS Upgrade




414.1.3 Impact on the System After the Upgrade

414.1.4 Precautions




434.3.2 Obtaining Tools


434.3.4 Obtaining the License File


444.3.6 Setting Up the CSS Environment

464.3.7 Backing Up Data

464.4 Performing the CSS Upgrade


464.4.2 Specifying the System Software

474.4.3 Enabling the CSS Function

474.4.4 (Optional) Setting the Management Port Address

484.5 Verifying the CSS Upgrade


494.5.2 Verifying Board Software Version

494.5.3 Verifying Board Registration Status

504.5.4 Verifying Configuration Restoration




514.6.2 Performing Version Rollback


535 SPU Upgrade




545.1.3 Precautions

555.1.4 Upgrade Schedule



555.2.2 Preparing Tools


565.2.4 Checking Network Communication

565.2.5 Connecting to the SPU Using a Network Cable


575.2.7 Checking the SPU Registration Status

585.2.8 Verifying the Running Status of the SPU

585.2.9 Setting Up the Upgrade Environment

595.2.10 Checking the Space on the CF Cards

605.2.11 Backing Up Files

605.2.12 Using SPU as FTP Server

615.2.13 Using SPU as FTP Client

635.3 Upgrade Operations

635.3.1 Method 1: Loading the System Software Through TFTP

645.3.2 Method 2: Loading the System Software Using the SPU as the FTP Server

665.3.3 Method 3: Loading the System Software Through the S9300's MPU

685.3.4 Method 4: Loading the System Software Using the Escape Channel

715.3.5 Method 5: Loading the Upgrade Program Through the BootROM Menu

745.3.6 Checking the Loaded System Software and Starting It

765.3.7 Verifying the Upgrade


775.4 Version Rollback

775.4.1 Rolling Back to an Earlier Version


796 Upgrading the System Software Using the BootROM Menu

1 Upgrade OverviewIMPORTANT: Before upgrading, read the corresponding chapters marked .Intended Upgrade 2. Command Line Upgrade3. ISSU Upgrade4. CSS Upgrade5. SPU Upgrade

Upgrade S9300 V100R001 to S9300 V100R006C00SPC800

Upgrade S9300 V100R002 to S9300 V100R006C00SPC800

Upgrade S9300 V100R003C00, S9300 V100R003C01, V100R003C01SPC100, V100R006C00SPC300, V100R006C00SPC500, or V100R006C00SPC600 to S9300 V100R006C00SPC800, without using ISSU

Upgrade S9300 V100R003C00, S9300 V100R003C01, V100R003C01SPC100, V100R006C00SPC300, V100R006C00SPC500, or V100R006C00SPC600 to S9300 V100R006C00SPC800 using ISSU

Upgrade S9300 V100R003C00, S9300 V100R003C01, V100R003C01SPC100, V100R006C00SPC300, V100R006C00SPC500, or V100R006C00SPC600 to S9300 V100R006C00SPC800 in a CSS, without using ISSU

Upgrade S9300 V100R003&VASP V100R002 to S9300 V100R006&VASP V100R003

Degrade S9300 V100R006&VASP V100R003 to S9300 V100R003&VASP V100R002

2 Command Line Upgrade2.1 Before You Start


Table 2-1 Upgrade notes for versionsVersionUpgrade Note

S9300 V100R001 versions:S9300 V100R001C02B118S9300 V100R001C02B125S9300 V100R001C03SPC001These versions can be directly upgraded to S9300V100R006C00SPC800.Some commands will be modified after the upgrade. For details, see the Quidway S9300 V100R006C00SPC800 Release Notes.

S9300 V100R002C00 versions:S9300 V100R002C00SPC001S9300 V100R002C00SPC002S9300 V100R002C00SPC100S9300 V100R002C00SPC200S9300 V100R002C01 version:S9300 V100R002C01

S9300 V100R003C00S9300 V100R003C00SPC200S9300 V100R003C01S9300 V100R003C01SPC100S9300 V100R006C00SPC300S9300 V100R006C00SPC500S9300 V100R006C00SPC600


Before you upgrade the system software from an earlier version to V100R006C00SPC800, read this section carefully to understand the possible impact of the upgrade on the system.Impact on the System During the Upgradea. Impact on servicesServices are interrupted when the S9300 is restarting. The S9300 with empty configuration will finish restarting within 6 minutes. The restart time required by a configured S9300 depends on the size of the configuration file.b. Impact on network communicationThe S9300 needs to be restarted during the upgrade; therefore, communication between the S9300 and the network management system (NMS) will be interrupted for about six minutes.Impact on the System After the UpgradeThere is no impact on the system after the upgrade.2.1.3 PrecautionsPrecautions Before UpgradeNo.Description

1After the device is upgraded from V100R001C03 to V100R002 or a later version, TACACS authentication user rights are lost and need to be reconfigured.

2V100R006 does not support 8 MB flash memory. If the S9300 has 8 MB flash memory installed before the upgrade, the S9300 may fail to be upgraded to V100R006.

Before the upgrade, run the display version command to check whether 8 MB flash memory is used.

LPU 2 : uptime is 0 week, 0 day, 0 hour, 20 minutes

SDRAM Memory Size : 256 M bytes

Flash Memory Size : 8 M bytesLPU version information :

...

3If you need to specify a patch of V100R006C00SPC800 when upgrading the system software from V100R002 or an earlier version to V100R006C00SPC800, delete the $_patchstate_reboot file before the upgrade. If this file is not deleted, the specified file cannot take effect after the upgrade.

4Before upgrading an earlier version to V100R006, do not run the upgrade all command. Otherwise, the configuration will be lost and the interface board cannot be registered if the battery has no power.

5When upgrading the switch to V100R006, load V100R006SPH001 or later patches to solve the following problems: In V100R003 and earlier versions, if the administrator account is in user name@domain name format (@ is the domain name delimiter) but the domain does not exist, the user account becomes invalid after the upgrade. If cpcar ttl-expired is configured in S9303 V100R001 and the action is set to drop, or if a cpu-defend policy with the deny ttl-expired rule is configured in S9303 V100R002, OSPF neighbor relationships may be affected after the system is upgraded to V100R003. If the switch has an EC or ED board installed, there is a low probability that the EC or ED board fails to start after the upgrade.

6Before upgrading the system software from S9300 V100R002C00 to S9300 V100R006, check the VRRP configuration. If a VRRP4 group and a VRRP6 group are both configured in the system, ensure that they use different VRIDs.

7If the loopback local swap-mac or loopback remote swap-mac command has been used on an interface in V100R006 or an earlier version to configure MAC swap loopback, run the start command in the interface view after the upgrade; otherwise, the MAC swap loopback configuration will be invalid.

8When the S9300 is upgraded from V100R001 to V100R002 or a later version, the command that configures the whitelist uses a different view. The whitelist function remains unchanged, but the whitelist configuration may be lost. You need to reconfigure the whitelist function.

9After the arp learning dhcp-trigger command is executed on the DHCP relay enabled VLANIF interface in V100R006, the DHCP snooping function must be enabled on the corresponding VLAN or user access interface; otherwise, dynamic ARP entries cannot be generated. In V100R003C01, this command only needs to be executed on the VLANIF interface.

10On S9300 V100R003, the dynamic VLAN and guest VLAN can be configured on any types of interfaces in the configurations of 802.1x authentication and MAC authentication. In V100R006, if the guest VLAN mode is MAC-based, the dynamic VLAN and guest VLAN must be configured on hybrid interfaces. Therefore, before the upgrade, change the interface type to hybrid.

11After the board in the V100R001 or V100R002 version is installed on an S9300 V100R006, board registration duration is about 10 minutes. You can view the upgrade status in the log. Do not remove the board during the upgrade.

12The first start of EC/ED boards after V100R003 or an earlier version is upgraded to V100R006 takes about 5 minutes. The time of later starts will be reduced. The memory chip on the board of V100R006 is optimized; therefore, the system performs calculation and configurations when the board starts for the first time. After V100R006 is returned to V100R003 or an earlier version, the first start also takes a long time.

Precautions Before DegradeNo.Description

1The user level configuration command uses a different format in V100R006 than in V100R002 and earlier versions. For example, the local-user aaa privilege level 3 command in V100R006 should be local-user aaa level 3 in V100R002 and earlier versions. If this command is configured in V100R006, the configuration will be lost after the switch is degraded to V100R002 or an earlier version. Run the local-user aaa level 3 to reconfigure the user level.


Figure 2-2 Upgrade flowchart

Table 2-2 Upgrade scheduleProcedure StepTime Required (Minutes)Remarks

Prepare for the upgrade5Prepare tools and software.

Perform the upgrade201. Back up files.2. Load the system software.3. Restart the device.

Verify the upgrade51.Check the version

2. Check whether configurations are lost.3. Check whether boards start properly.

Roll back to an earlier version101. Specify the system software of an earlier version for next startup.2. Restart the device.


2.3.1 Pre-upgrade Checklist

Table 2-3 lists the items to be checked before the upgrade.Table 2-3 Pre-upgrade checklistNo.ItemExpected ResultActual Result

1Obtaining Upgrade Reference DocumentsThe reference documents have been printed or downloaded to your computer.

2Obtaining ToolsThe operation terminal, network cable, serial port cable, and FTP or TFTP software are ready.

3Obtaining Upgrade SoftwareThe target system software (.cc) has been obtained from Huawei.

4Obtaining the License FileThe license files have been obtained from Huawei.

5Preparing the Configuration FileThe commands in the configuration file meet the target version requirements.

6Verifying the Current VersionThe current version meets all the Version Requirements.

7Verifying the Running Status of the DeviceThe MPUs and LPUs are working properly.Keep a record of the status of the board in each slot for future troubleshooting.

8Setting Up the Upgrade EnvironmentThe network to be upgraded has been set up.

9Backing Up CF Card DataThe key data on the CF card has been backed up. Key data includes the configuration file, license file, and system startup file of the current version.

10Checking the Space on the CF CardsCheck the remaining space on the CF cards and ensure there is sufficient space for the system software.


Contact Huawei technical personnel or visit http://support.huawei.com to obtain the latest documents, including: Quidway S9300 Product Documentation (V100R006C00_04) Quidway S9300 V100R006C00SPC800 Release Notes Quidway S9300 License Application Guide2.3.3 Obtaining Tools

Prepare the following tools before upgrading: Operation terminal, such as a desktop computer or a portable computer Network cable and serial cable FTP server software or TFTP server software for the upgrade

Huawei does not provide the FTP server, TFTP server, or FTP client software. The customer needs to provide this software as required.2.3.4 Obtaining Upgrade Software

To obtain the required upgrade software, contact Huawei technical personnel or visit http://support.huawei.com.The system software of S9300V100R006C00SPC800 is S9300V100R006C00SPC800.cc.2.3.5 Obtaining the License File If the S9300 uses the license of MPLS, IPv6, NQA, or load balancing before the upgrade, the S9300 does not need to apply for the license after the upgrade; otherwise, customers should load the license file. For details about license application and combination operations, see the Quidway S9300 License Application Guide.2.3.6 Preparing the Configuration File

To batch issue configurations to the device after upgrade, load the latest configuration file to the device.


Run the display version command in the user view to check the current system software version and ensure that it meets the upgrade requirement. display versionHuawei Versatile Routing Platform SoftwareVRP (R) software, Version 5.70 (S9300 V100R003C01)Copyright (C) 2003-2010 HUAWEI TECH CO., LTDQuidway S9303 Terabit Routing Switch uptime is 0 week, 0 day, 2 hours, 56 minutesIn the preceding output, S9300 V100R003C01 indicates the version of system software currently running on the S9300. If this is the target version, you do not need to perform the upgrade.2.3.8 Verifying the Running Status of the Device

2. Run the display device command in the user view to check the status of MPUs and LPUs. Ensure that MPUs and LPUs are working properly. display deviceS9303's Device status:Slot Sub Type Online Power Register Alarm Primary- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

2 - F48SA Present PowerOn Registered Normal NA4 - MCUA Present PowerOn Registered Normal Slave5 - MCUA Present PowerOn Registered Normal MasterPWR1 - - Present PowerOn Registered Normal NAIf the boards are working properly, the value of the Online field is Present, the value of the Register field is Registered, and the value of the Alarm field is Normal.

If the value of the Register field is Unregistered, the board has failed to register. If the value of the Alarm field is Abnormal, the board is not operating properly.If you find that some boards cannot be registered or do not work properly, record the board status, and ask Huawei technical personnel whether the boards can be upgraded or must be replaced. After the upgrade is complete, check the status of the boards again.3. Run the display alarm command in the user view to check the status of the device. Ensure that MPUs and LPUs are working properly. display alarm all----------------------------------------------------------------------------

Level Date Time InfoWarning 2010-10-10 13:58:56 FAN board[1/6] is absent.----------------------------------------------------------------------------

If a critical level alarm message is displayed, consult Huawei technical personnel to determine whether the upgrade can be performed. Table 2-4 describes the alarm severities defined by Huawei.

Table 2-4 Alarm severity descriptionLevelDescription

1Critical

2Major

3Minor

4Warning

5Cleared

6Indeterminate

----End2.3.9 Setting Up the Upgrade Environment

As shown in Figure 2-2, the requirements for setting up an environment to upgrade the system through TFTP or FTP are as follows: The RS-232 serial port of the PC is connected to the S9300 console port with a console cable. The FTP or TFTP server is connected to the Ethernet interface on the S9300 MPU through a network cable. The IP addresses of the server and the Ethernet interface of the S9300 are in the same network segment, and the server and the S9300 can ping each other using the two IP addresses. The system software and the license file are stored on the server.

A PC can also function as the server to store the system software and license file. You only need to connect the PC to the Ethernet interface of the S9300 using a network cable.Figure 2-3 Network diagram for upgrading the system through TFTP or FTP

2.3.10 Backing Up CF Card Data

Ensure that the key data stored on the CF card is backed up before upgrade. After the upgrade, load the backup files. Key data includes the configuration file, license file, web file, and system startup file and patch file of the current version.

You can back up data after setting up the upgrade network. For details, see 2.4.1

REF _Ref278480555 \h Loading System Software.2.3.11 Checking the Space on the CF Cards

4. Check the available space.In the user view, run the dir command to check whether the available space in the CF cards on the master and slave MPUs is sufficient for the system software after upgrade.# View the available space on the CF card of the master MPU. dir cfcard:/Directory of cfcard:/ Idx Attr Size(Byte) Date Time FileName 0 -rw- 4 Nov 04 2010 21:44:22 snmpnotilog.txt 1 drw- - Nov 04 2010 20:55:32 logfile 2 -rw- 198 Nov 04 2010 21:47:36 $_patchstate_a 3 -rw- 524,381 Nov 04 2010 21:48:06 private-data.txt 4 -rw- 589 Nov 04 2010 20:55:54 vrpcfg.zip 5 -rw- 333,436 Jan 29 2010 16:54:40 s9300v100r003sph003.pat 6 -rw- 27,455,925 Nov 04 2010 19:43:18 s9300v100r003c01.cc 7 -rw- 3,241 Apr 08 2010 09:45:04 vrpcfg1.zip 8 -rw- 14,268 May 22 2010 16:09:10 $_patchstate_reboot 9 drw- - Sep 21 2010 14:01:00 sysdrv 10 drw- - Sep 21 2010 14:01:00 compatible 11 drw- - Sep 25 2010 11:55:00 dhcp506,744 KB total (241,808 KB free)# View the available space on the CF card of the slave MPU.

dir slave#cfcard:Directory of slave#cfcard:/ Idx Attr Size(Byte) Date Time FileName 0 -rw- 4 Nov 04 2010 21:44:22 snmpnotilog.txt 1 drw- - Nov 04 2010 20:55:32 logfile 2 -rw- 198 Nov 04 2010 21:47:36 $_patchstate_a 3 -rw- 524,381 Nov 04 2010 21:48:06 private-data.txt 4 -rw- 589 Nov 04 2010 20:55:54 vrpcfg.zip 5 -rw- 333,436 Jan 29 2010 16:54:40 s9300v100r002sph003.pat 6 -rw- 27,455,925 Nov 04 2010 19:43:18 s9300v100r002c00.cc 7 -rw- 3,241 Apr 08 2010 09:45:04 vrpcfg1.zip 8 -rw- 14,268 May 22 2010 16:09:10 $_patchstate_reboot 9 drw- - Sep 21 2010 14:01:00 sysdrv 10 drw- - Sep 21 2010 14:01:00 compatible 11 drw- - Sep 25 2010 11:55:00 dhcp506,744 KB total (241,808 KB free)

More than 65000 KB available memory space is sufficient for the upgrade.5. Delete unneeded files.If the available space on the CF cards is insufficient for the new system software, you must delete unnecessary files to free up space.

Before deleting the system software (with the file name extension .cc), configuration file (with the file name extension .cfg or .zip), license file (with the file name extension .dat), Web file (with the file name extension .web), patch file (with the file name extension .pat), ensure that they are not in use. Run the following commands in the user view to delete the unneeded files from the CF cards on the master and slave MPUs.

Files deleted using the delete command are stored in the recycle bin. To restore these files, run the undelete command. However, files in the recycle bin still occupy CF card space. The reset recycle-bin command permanently deletes all files from the recycle bin.

You can also run the delete/unreserved command to permanently delete all files without placing them in the recycle bin. This command is equivalent to running the delete and reset recycle-bin commands in sequence.

# Delete unneeded files from the CF card of the master MPU. delete cfcard:/vrpcfg1.zipDelete cfcard:/vrpcfg1.zip?[Y/N]:y

Info: Deleting file cfcard:/vrpcfg1.zip...succeeded.# Delete unneeded files from the CF card of the slave MPU. delete slave#cfcard:/vrpcfg1.zipDelete slave#cfcard:/vrpcfg1.zip?[Y/N]:y

Info: Deleting file slave#cfcard:/vrpcfg1.zip...succeeded.To restore the files in the recycle bin, run the following command: undelete cfcard:/vrpcfg1.zipUndelete cfcard:/vrpcfg1.zip?[Y/N]:y

%Undeleted file cfcard:/vrpcfg1.zip.To permanently delete files from the recycle bin, run the following commands: reset recycle-bin cfcard:/ reset recycle-bin slave#cfcard:/----End2.4 Performing the Upgrade

Table 2-5 Upgrade processNo.ActionCommandReference

1Back up key data, then load the new system software, license file, and configuration file to the MPU. If a slave MPU is used, the data needs to be copied to the slave MPU.-2.4.1

REF _Ref278481698 \h \* MERGEFORMAT Loading System Software

2Check whether the files were loaded.dir2.4.2

REF _Ref278481707 \h \* MERGEFORMAT Verifying File Loading

3Specify the system software and configuration file for next startup. If a slave MPU is used, the files must be specified on the slave MPU.startup system-softwarestartup system-software slave-boardstartup saved-configuration2.4.3

REF _Ref278481717 \h \* MERGEFORMAT Specifying the System Software

4Check whether the system software and configuration file specified for next startup are correct.display startup2.4.3


5Perform cyclic redundancy check (CRC) check on the system software.check startup crc next2.4.3


6Restart the device.reboot2.4.4

REF _Ref276716152 \h \* MERGEFORMAT Restarting the Device

7Verify the upgrade.display startupcheck versiondisplay devicedisplay current-configuration2.4.5

REF _Ref278481727 \h \* MERGEFORMAT Activating the License


In the following description, the current system software is S9300V100R003C01.cc, the configuration file is vrpcfg.zip, and the target system software is S9300V100R006C00SPC800.cc.You can use any of the following methods to load the system software: Use the S9300 as the TFTP client. Use the S9300 as the FTP server. Use the S9300 as the FTP client. Use the BootROM menu.The first three methods are recommended. The last method is only used when the S9300 fails to start.

Before the upgrade, use the terminal monitor command to enable the terminal to display logs, traps, and debugging information sent from the information center.Method 1: Use the S9300 as the TFTP Client

No TFTP client software is installed on the S9300; therefore, the customer needs to buy TFTP client software and install it. The TFTP32 program is recommended.1. Configure the TFTP server.Run the TFTP server program on the PC and configure the PC: Click Browse to set the directory for storing the new system software.

The TFTP server address in Server interface is automatically set by the system, for example, 10.164.30.29. However, if the IP address is incorrect you can manually change it.

Do not stop the TFTP server program when you are backing up data.2. Back up the system software, configuration file, and patch files to the TFTP server.Before the backup, check the size of the configuration file. After the backup, compare the size of the original file with the size of the backup file. Ensure that the two files are the same size. dir *.ccDirectory of cfcard:/ Idx Attr Size(Byte) Date Time FileName 0 -rw- 59,455,925 Nov 04 2010 19:43:18 s9300v100r003c01.cc506,744 KB total (240,784 KB free)

dir *.zipDirectory of cfcard:/ Idx Attr Size(Byte) Date Time FileName 0 -rw- 589 Nov 04 2010 20:55:54 vrpcfg.zip506,744 KB total (240,720 KB free) dir *.patDirectory of cfcard:/ Idx Attr Size(Byte) Date Time FileName 0 -rw- 333,436 Jan 29 2010 16:54:40 s9300v100r003sph003.pat506,744 KB total (240,656 KB free)Run the following commands on the S9300 to back up the data. The backup system software is s9300v100r003c01-bak.cc, the backup configuration file is vrpcfg-bak.zip, and the patch file is s9300v100r003sph003-bak.pat. tftp 10.164.30.29 put s9300v100r003c01.cc s9300v100r003c01-bak.ccInfo: Transfer file in binary mode.

Uploading the file to the remote TFTP server. Please wait...|

TFTP: Uploading the file successfully.

27455925 bytes send in 91 seconds. tftp 10.164.30.29 put vrpcfg.zip vrpcfg-bak.zipInfo: Transfer file in binary mode. Uploading the file to the remote TFTP server. Please wait.../ TFTP: Uploading the file successfully. 589 bytes send in 0.01 second. tftp 10.164.30.29 put s9300v100r003sph003.pat s9300v100r003sph003-bak.pat

Info: Transfer file in binary mode.

Uploading the file to the remote TFTP server. Please wait...\

TFTP: Uploading the file successfully.

333436 bytes send in 1 second.3. Obtain the system software of the target version from the server. tftp 10.164.30.29 get S9300V100R006C00SPC800.ccInfo: Transfer file in binary mode. Downloading the file from the remote TFTP server. Please wait.../TFTP: Downloading the file successfully.

52749606 bytes received in 372 seconds.If the message "Downloading the file successfully" is displayed, the system software has been downloaded.4. Obtain the license file from the server. tftp 10.164.30.29 get license.dat


Downloading the file from the remote TFTP server. Please wait...\

TFTP: Downloading the file successfully.

1748 bytes received in 1 second.5. (Optional) Obtain the new configuration file from the server.If the configuration file does not need to be changed after the upgrade, this step is not required. tftp 10.164.30.29 get vrpcfgnew.zip


Downloading the file from the remote TFTP server. Please wait.../

TFTP: Downloading the file successfully.

2757 bytes received in 1 second.----EndMethod 2: Use the S9300 as the FTP Server

No FTP server software is installed on the S9300; therefore, the customer needs to buy FTP server software and install it.1. Configure the S9300 as the FTP server.In the following description, the IP address of Ethernet0/0/0 is 10.164.30.20, the FTP user name is S9300, the password of the FTP user is 123456, and the FTP root directory is cfcard:/. system-view[Quidway] ftp server enableInfo: Succeeded in starting the FTP server.

[Quidway] aaa[Quidway-aaa] local-user S9300 password simple 123456info: A new user added[Quidway-aaa] local-user S9300 ftp-directory cfcard:[Quidway-aaa] local-user S9300 service-type ftpThe S9300 configuration files are stored on the CF card; therefore, the FTP root directory is set to cfcard:/. The directory name must be correct because the root directory cannot be changed.2. Back up the system software, configuration file, and patch files.

You can log in to the FTP server (S9300) and back up files by using either of the following methods: Log in to the S9300 using any FTP client program and back up files to the FTP client.In the Address box of the FTP client program, enter the IP address and the FTP root directory of the S9300, and copy the files from the FTP root directory to a directory on the PC. Here, the directory on the PC is D:\ftp. Log in to the S9300 using the operation terminal and back up files to the FTP client.It is recommended that the upgrade program directory and FTP root directory be used as the login directory, for example, D:ftp.

On Windows XP, perform the following operations to start the FTP program: Choose Start > Run. Enter cmd. Enter d:. Enter cd ftp to enter the FTP view.C:\Documents and Settings\Administrator>d:D:\>cd ftpD:\ftp> ftp 10.164.30.20Connected to 10.164.30.20.

220 FTP service ready.

User(10.164.30.20:(none)):S9300 # Enter the user name331 Password required for s9300.Password: # Enter password 123456 and press enter. The password is displayed in cipher text.230 User logged in.

ftp> binary200 Type set to I.

ftp> get s9300v100r003c01.cc200 Port command okay.

150 Opening BINARY mode data connection for s9300v100r003c01.cc.

226 Transfer complete.

ftp: 59455925 bytes received in 20.33Seconds 1350.65Kbytes/sec.

The preceding output indicates the configuration file has been transferred and you can find it in D:\ftp.ftp> get vrpcfg.zip200 Port command okay.

150 Opening ASCII mode data connection vrpcfg.zip

226 Transfer complete.

ftp: 589 bytes received in 0.01Seconds 60Kbytes/sec.The preceding output indicates the configuration file has been transferred and you can find it in D:\ftp.ftp> get s9300v100r003sph003.pat200 Port command okay.150 Opening BINARY mode data connection for s9300v100r003sph003.pat.226 Transfer complete.ftp: 333436 bytes received in 0.25Seconds 1333.74Kbytes/sec.The preceding output indicates the configuration file has been transferred and you can find it in D:\ftp.3. Upload the system software of the target version to the S9300.You can load the system software to the S9300 using either of the following methods: Copy the system software to cfcard:/ on the S9300 using any FTP client program.Similar to file backup, you only need to copy the system software to the FTP server (S9300). Load the system software by running the following commands on your computer.D:\ftp> ftp 10.164.28.20Connected to 10.164.28.20.

220 FTP service ready.

User(10.164.28.20:(none)):S9300 # Enter the user name and press Enter.331 Password required for S9300.

Password: # Enter the password 123456 and press Enter. The password displayed on the screen is in cipher text.230 User logged in.

ftp> binary200 Type set to I.

ftp> put S9300V100R006C00SPC800.ccYou can specify the filename of the loaded upgrade program. If the filename is not specified, the original name is used.200 Port command okay.150 Opening BINARY mode data connection for S9300V100R006C00SPC800.CC.226 Transfer complete.ftp: 52749606 bytes sent in 39.25Seconds 1345.89Kbytes/sec.4. Upload the license file to the S9300.ftp> put license.dat

5. (Optional) Upload the new configuration file to the S9300.If the configuration file does not need to be changed after the upgrade, this step is not required.ftp> put vrpcfgnew.zip

----EndMethod 3: Use the S9300 as the FTP Client

No FTP client software is installed on the S9300; therefore, the customer needs to buy FTP client software and install it.1. Configure the PC as the FTP server.Run an FTP server program on the PC, for example, wftpd32. Choose Security > Users/rights.

Click New User to set the user name and password. Here, the user name is S9300 and the password is 123456. Enter the FTP root directory in the Home Directory text box. Here, the root directory is D:\ftp. Click Done to close the dialog box.Do not stop the FTP server program when you are backing up data.2. Back up the system software, configuration file, and patch files.

The FTP commands on the S9300 are the same as the FTP commands in the DOS system. In this example, the IP address of the FTP server is 10.164.30.27, the FTP user name is S9300, and the password of the FTP user is 123456.

cd cfcard:/ ftp 10.164.30.27Trying 10.164.30.27 ...Press CTRL+K to abortConnected to 10.164.30.27.220 WFTPD 2.0 service (by Texas Imperial Software) ready for new userUser(10.164.30.27:(none)):S9300 # Enter the user name and press Enter.331 Give me your password, pleaseEnter password: # Enter the password 123456 and press Enter. The password displayed on the screen is in cipher text.230 Logged in successfully [ftp] binary200 Type is Image (Binary)

Back up the system software s9300v100r003c01.cc to the FTP server and specify the name of the backup file as s9300v100r003c01-bak.cc. If the name of the backup file is not specified, the original name is used.[ftp] put s9300v100r003c01.cc s9300v100r003c01-bak.cc200 PORT command okay

150 "D:\ftp\s9300v100r003c01-bak.cc" file ready to receive in IMAGE / Binary mode

226 Transfer finished successfully.

FTP: 27455925 byte(s) sent in 21.176 second(s) 1296.55Kbyte(s)/sec.Back up the configuration file vrpcfg.zip to the FTP server and specify the name of the backup file as vrpcfg-bak.zip. If the name of the backup file is not specified, the original name is used.[ftp] put vrpcfg.zip vrpcfg-bak.zip

200 PORT command okay150 "D:\FTP\vrpcfg-bak.zip" file ready to receive in IMAGE / Binary mode226 Transfer finished successfully.FTP: 1387 byte(s) sent in 0.176 second(s) 22.04Kbyte(s)/sec.Back up the patch file s9300v100r002sph003.pat to the FTP server and specify the name of the backup file as s9300v100r002sph003bak.pat. If the name of the backup file is not specified, the original name is used.[ftp] put s9300v100r003sph003.pat s9300v100r003sph003bak.pat

200 PORT command okay

150 "D:\ftp\s9300v100r003sph003bak.pat" file ready to receive in IMAGE / Binary

mode


FTP: 333436 byte(s) sent in 0.322 second(s) 1035.51Kbyte(s)/sec.3. Obtain the system software of the target version.[ftp] get S9300V100R006C00SPC800.cc200 PORT command okay

150 "D:\ftp\ S9300V100R006C00SPC800.CC" file ready to send (52749606 bytes) in IMAGE / Binary mode

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

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

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

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

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

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


FTP: 52749606 byte(s) received in 45.500 second(s) 1117.40Kbyte(s)/sec.

You can specify the filename of the loaded upgrade program. If the filename is not specified, the original name is used.4. Obtain the license file.[ftp] get license.dat

5. (Optional) Obtain the new configuration file.If the configuration file does not need to be changed after the upgrade, this step is not required.[ftp] get vrpcfgnew.zip6. Close the FTP connection.[ftp] bye221 Windows FTP Server (WFTPD, by Texas Imperial Software) says goodbye

----EndMethod 4: Using the BootROM Menu

To use this method, you must be familiar with the S9300 system. You can only use this method when the device is powered on for the first time or when the device fails to start. This method helps you copy the upgrade program faster.To use this method, you need to configure the S9300 as the FTP client and configure the computer as the FTP server.For details on this method, see 6

REF _Ref294794496 \h Upgrading the System Software Using the BootROM Menu.2.4.3 Verifying File Loading

Run the dir command on the S9300 to verify that the upgrade program file exists and that the file size is the same as the size of the file on the FTP or TFTP server. Then, specify the loaded upgrade program as the new startup program. dir cfcard:/Directory of cfcard:/ Idx Attr Size(Byte) Date Time FileName 0 -rw- 4 Nov 04 2010 21:44:22 snmpnotilog.txt 1 drw- - Nov 04 2010 20:55:32 logfile 2 -rw- 198 Nov 04 2010 21:47:36 $_patchstate_a 3 -rw- 524,381 Nov 04 2010 21:48:06 private-data.txt 4 -rw- 2757 Nov 05 2010 20:55:54 vrpcfgnew.zip 5 -rw- 333,436 Jan 29 2010 16:54:40 s9300v100r003sph003.pat6 -rw- 27,455,925 Nov 04 2010 19:43:18 s9300v100r003c01.cc7 -rw- 52,749,606 Nov 05 2010 06:48:54 s9300V100R006C00SPC800.cc8 -rw- 1,748 Nov 05 2010 06:09:16 license.dat 9 -rw- 14,268 May 22 2010 16:09:10 $_patchstate_reboot 10 drw- - Sep 21 2010 14:01:00 sysdrv 11 drw- - Sep 21 2010 14:01:00 compatible 12 drw- - Sep 25 2010 11:55:00 dhcp2.4.4 Specifying the System Software

1. Specify the system software for next startup.Configure the loaded system software as the startup program of the master MPU.

startup system-software s9300V100R006C00SPC800.ccInfo: Succeeded in setting the software for booting system.

If a slave MPU is used, you must copy the system software to the slave MPU and specify the startup software for the slave MPU. Copy the new system software to the slave MPU. copy s9300V100R006C00SPC800.cc slave#cfcard:/Copy cfcard:/ s9300V100R006C00SPC800.cc to slave#cfcard:/ s9300V100R006C00SPC800.cc?[Y/N]:y

100% complete\

Info: Copied file cfcard:/s9300V100R006C00SPC800.cc to slave#cfcard:/ s9300V100R006C00SPC800.cc...Done.Specify the startup software for the slave MPU. startup system-software s9300V100R006C00SPC800.cc slave-boardInfo: Succeeded in setting the software for booting system.Run the display startup command to verify that the specified startup software is the newly loaded system software. display startup

MainBoard: Configured startup system software: cfcard:/s9300v100r003c01.cc Startup system software: cfcard:/s9300v100r003c01.cc Next startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup saved-configuration file: cfcard:/vrpcfg.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: default Next startup paf file: default Startup license file: default Next startup license file: default Startup patch package: NULL Next startup patch package: NULL

SlaveBoard: Configured startup system software: cfcard:/s9300v100r003c01.cc Startup system software: cfcard:/s9300v100r003c01.cc Next startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup saved-configuration file: cfcard:/vrpcfg.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: default Next startup paf file: default Startup license file: default Next startup license file: default Startup patch package: NULL Next startup patch package: NULL

2. (Optional) Specify the configuration file for next startup.If a new configuration file is used, specify the new configuration file for next startup. If you do not specify the new configuration file, the old configuration file will be used after the upgrade.

If a slave MPU is used, copy the new configuration file to the slave MPU using the following commands. Ensure that the configuration files used on the master and slave MPUs are the same after restarting. copy vrpcfgnew.cfg slave#cfcard:/

Copy cfcard:/vrpcfgnew.cfg to slave#cfcard:/vrpcfgnew.cfg?[Y/N]:y100% completeInfo: Copied file cfcard:/vrpcfgnew.cfg to slave#cfcard:/vrpcfgnew.cfg...Done. startup saved-configuration vrpcfgnew.cfgInfo: Succeeded in setting the configuration for booting system.3. Perform cyclic redundancy check (CRC) check on the system software. check startup crc nextWarning: This operation will take several minutes! Continue?[Y/N]:yCheck startup software CRC....................................................................................................................................

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

Info: okCheck startup software CRC in slaveboard.............................................ok

----End2.4.5 Restarting the Device

Run the reboot command to restart the device. Enter y to save the current configuration, which will be loaded when the system restarts. Generally, you will save the current configurations before restarting; however if the system will be using a new, modified configuration file, saving the configuration is unnecessary. In this case, enter n to discard the current configuration and the system will use the specified system software and configuration file during the next startup.

rebootInfo: The system is now comparing the configuration, please wait.Warning: Current configuration will be saved to the next startup saved-configuration file: cfcard:/vrpcfg.zip!Continue?[Y/N]: ySystem will reboot! Continue?[Y/N]: yEnter y to restart the system.2.4.6 Activating the License

After a license file is loaded to the device, you must activate it; otherwise, the license will not take effect.

If a slave MPU is used, copy the license file to the slave MPU, and activate it on the slave MPU. copy license.dat slave#cfcard:/Copy cfcard:/license.dat to slave#cfcard:/license.dat?[Y/N]:y100% complete|Info: Copied file cfcard:/license.dat to slave#cfcard:/license.dat...Done. license active license.dat2.5 Verifying the Upgrade

2.5.1 Verification Checklist

Table 2-6 Verification checklistNo.Item Expected Result Actual Result

1Verifying the Current System SoftwareThe current version is the same as the target version.

2Verifying That All the Programs Have Been UpgradedAll the software programs have been upgraded.

3Verifying Board Registration StatusThe boards are in the Registered state.

4Verifying Configuration Restoration No configuration has been lost.

5Verifying ServicesServices are working normally.


After the reboot, run the display version command in any view to check the version of the system software. As shown in the following display, the information in bold indicates the current version on the S9300. Verify that the current version matches the target version; otherwise, verify the upgrade procedure, and perform the upgrade again. display startup MainBoard: Configured startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup system software: cfcard:/s9300V100R006C00SPC800.cc Next startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup saved-configuration file: cfcard:/vrpcfgnew.zip Next startup saved-configuration file: cfcard:/vrpcfgnew.zip Startup paf file: default Next startup paf file: default Startup license file: default Next startup license file: default Startup patch package: NULL Next startup patch package: NULL

SlaveBoard: Configured startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup system software: cfcard:/s9300V100R006C00SPC800.cc Next startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup saved-configuration file: cfcard:/vrpcfgnew.zip Next startup saved-configuration file: cfcard:/vrpcfgnew.zip Startup paf file: default Next startup paf file: default Startup license file: default Next startup license file: default Startup patch package: NULL Next startup patch package: NULL

2.5.3 Verifying That All the Programs Have Been Upgraded

Run the check version command in the user view to check whether all the software programs have been upgraded. If any program has not been upgraded, run the upgrade all { startup | filename } [ force ] command in the user view to upgrade them.

check versionFrame/Slot Type Content CurVer ExactVer State Upgrade Suggest--------------------------------------------------------------------------------

1. If None is displayed in the Upgrade Suggest column, all programs match the target version and you do not need to upgrade them. If Must is displayed, you must upgrade the programs. If Recommend is displayed, the program version is later than the target version. You can use the current program version because software versions are backward compatible. It is recommended that you degrade the program version to the target version to ensure version matching.2. When you upgrade or degrade the system version to V100R003 or V100R006, the system automatically updates the BootROM version. When you upgrade or degrade the system version to V100R001 or V100R002, run the upgrade all { startup | filename } [ force ] command in the user view to manually upgrade the BootROM. The CPLD can be upgraded only when the MPU is in slave state.3. If a device is upgraded to the latest version from V100R001 or V100R002, the CANBUS_SDR field of the slave MPU displays Incompatible. This state (Incompatible) does not affect services and is cleared after the slave MPU becomes the master MPU.2.5.4 Verifying Board Registration Status

Run the display device command in any view to check the registration status of the boards. All the boards should be in the Registered state. display deviceS9303's Device status:Slot Sub Type Online Power Register Alarm Primary- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

2 - F48SA Present PowerOn Registered Normal NA4 - MCUA Present PowerOn Registered Normal Slave5 - MCUA Present PowerOn Registered Normal MasterPWR1 - - Present PowerOn Registered Normal NA2.5.5 Verifying Configuration Restoration

After the reboot, run the display current-configuration command in any view to check the configuration of the S9300.You can also run the compare configuration command in the user view to compare the new configuration file with the configuration file saved in the storage device.

If no new configuration file is loaded to the S9300, view the configuration file of S9300 V100R006C00SPC800 upgraded from S9300 V100R001, S9300 V100R002, or S9300 V100R003. Compare the configuration file with that backed up in section 2.3.10

REF _Ref279154114 \h Backing Up CF Card Data. If the new configuration file contains all the items in the old configuration file, no configuration is lost. The new configuration file contains more information than the old one because some default configurations are added to S9300 V100R003C00. For the configuration differences, see the Quidway S9300 Terabit Routing Switch V100R006C00SPC800 Release Notes.2.5.6 Verifying Services

Use either of the following methods to check whether services are working normally after the upgrade.

Do not run the save command before you ensure that all services are working normally.

Check whether any table entries are missing, for example, the entries of the routing table, FIB table, and MAC address table. Check whether the service traffic volume remains the same after the upgrade. Confirm with the network management administrator that services are working normally and that essential servers, such as the NMS and NetStream servers are functioning properly.2.6 Rolling Back to an Earlier Version


Rollback scenarios: The upgrade was successful and the device is functioning properly, but the new system software does not meet service requirements. The device does not function properly after the upgrade.

Rollback methods: If the device functions properly after the upgrade, perform rollback using the command line, as described in section 2.6.3

REF _Ref279154952 \h Specifying the Previous System Software for Next Startup. If the device does not function properly after the upgrade, perform rollback using the BootROM.2.6.2 Rollback Process

Figure 2-4 Version rollback flowchart


Assume that the system software of the earlier version is s9300v100r003c01.cc. Run the following command to specify the previous system software for next startup, according to your own system: startup system-software s9300v100r003c01.ccInfo: Succeeded in setting the software for booting system.Specify the previous system software for next startup on the slave MPU. startup system-software s9300v100r003c01.cc slave-boardInfo: Succeeded in setting the software for booting system.If a new configuration file was used in the upgrade, restore the old configuration file. startup saved-configuration vrpcfg.cfgInfo: Succeeded in setting the configuration for booting system.Check whether the system software and configuration file of the earlier version have been specified for next startup. display startup MainBoard: Configured startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup system software: cfcard:/s9300V100R006C00SPC800.cc Next startup system software: cfcard:/s9300v100r003c01.cc Startup saved-configuration file: cfcard:/vrpcfgnew.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: default Next startup paf file: default Startup license file: default Next startup license file: default Startup patch package: NULL Next startup patch package: NULL

SlaveBoard: Configured startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup system software: cfcard:/s9300V100R006C00SPC800.cc Next startup system software: cfcard:/s9300v100r003c01.cc Startup saved-configuration file: cfcard:/vrpcfgnew.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: default Next startup paf file: default Startup license file: default Next startup license file: default Startup patch package: NULLNext startup patch package: NULL


Run the reboot command to restart the device. When the system restarts, it will be running the previous system software. rebootInfo: The system is now comparing the configuration, please wait.

Warning: All the configuration will be saved to the configuration file for the next startup:cfcard:/vrpcfg.zip, Continue?[Y/N]:y

Now saving the current configuration to the slot 5 .

Info: Save the configuration successfully.

System will reboot! Continue?[Y/N]:yWhen the system asks you whether to save the configuration: If an earlier V100R006 version is rolled back to a later V100R006 version, enter y.

If the version is rolled back to an earlier R version, for example, from V100R006C00SPC800 to V100R001, V100R002, or V100R003, enter n.

After rolling back the version from V100R006C00SPC800 to V100R001, V100R002, or V100R003, the commands may have changed. For command differences, see the Quidway S9300 V100R006C00SPC800 Release Notes.

When S9300V100R006C00SPC800 is rolled back to S9300V100R001, the rollback lasts about 10 minutes because the BootROM needs to be updated.2.6.5 Verifying the Rollback

The procedure for verifying a version rollback is identical to the procedure for verifying an upgrade. For details, see section 2.5

REF _Ref278480979 \h Verifying the Upgrade.3 ISSU Upgrade3.1 Before You Start


The target version must support the in-service software upgrade (ISSU) function. Only the S9300 V100R003C01 and later versions support the ISSU function.3.1.2 Impact of the Upgrade

Before you upgrade the system software, read this section carefully to understand the possible impact of the upgrade on the system.3.1.3 Impact on the System During the Upgrade

Impact on servicesLPUs will be reset during the upgrade, causing a service interruption of about 2 minutes. Impact on network communicationAn active/standby switchover will occur during the upgrade. As a result, communication on the Ethernet port of the MPU will be interrupted for about 30s.3.1.4 Impact on the System After the Upgrade

There is no impact on the system after the upgrade.3.2 Precautions

No.Description

1 Before the upgrade, collect device information, interface information, version information, configuration file, and all routing table, FIB table, and MAC address table information.After the upgrade, collect the same information again and compare it with the previous information to check whether the device operates and transmits services properly.


3.3.1 Verifying That MPUs Work in 1:1 Backup Mode

Before starting the ISSU upgrade, ensure that two MPUs are installed on the device, working in 1:1 redundancy backup mode. When performing the ISSU upgrade, you must upgrade the system software of the slave MPU, perform an active/standby switchover, and then upgrade the system software of the original master MPU.

Verify that the network interfaces of the master MPU and slave MPU are connected with a network cable. Run the display device command to check the status of MPUs and LPUs. Ensure that MPUs and LPUs are working properly and the MPUs work in 1:1 redundancy backup mode. display deviceS9306's Device status:Slot Sub Type Online Power Register Alarm Primary- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1 - G24SA Present PowerOn Registered Normal NA

2 - G24SC Present PowerOn Registered Normal NA

3 - F48SA Present PowerOn Registered Normal NA7 - SRUA Present PowerOn Registered Normal Master

8 - SRUA Present PowerOn Registered Normal SlavePWR1 - - Present PowerOn Registered Normal NACMU1 - CMUA Present PowerOn Registered Normal MasterFAN1 - - Present PowerOn Registered Normal NA

FAN2 - - Present PowerOn Registered Normal NA

If the value of the Register field is Unregistered, the board has failed to register. If the value of the Alarm field is Abnormal, the board is not working properly.

Run the display switchover state command in the user view to check the status of the master and slave MPUs. Ensure that the MPUs are in the real-time backup state. display switchover stateSlot 7 HA FSM State(master): realtime or routine backup.Slot 8 HA FSM State(slave): receiving realtime or routine data.3.3.2 Verifying the CPLD Logic on the MPUs

Run the check version all command in the user view to check the complex programmable logic device (CPLD) logic versions on the MPUs. Ensure that the CPLD logic version of the MPUs is compatible with the software version. check version allFrame/Slot Type Content CurVer ExactVer State Upgrade Suggest--------------------------------------------------------------------------------

1/7 MPU cpld0 0x1001.3014 0x1001.3014 Compatible None

1/8 MPU cpld0 0x1001.3014 0x1001.3014 Compatible None

When the values of CurVer and ExactVer fields are the same and the State value is Compatible, the logic version of the MPUs matches the software version.

If the logic version does not match the software version, check whether the MPUs support the ISSU function. Currently, only the LE01MCUA VER.A board does not support the ISSU function.

The CPLD logic on the MPUs should be updated automatically. If it does not update automatically, contact Huawei technical personnel. After the CPLD logic has been updated, restart the MPUs.After the MPUs have restarted, check again whether the CPLD logic version of the MPUs matches the software version. The ISSU upgrade can be performed only when these versions match.3.4 (Optional) Checking the ISSU Upgrade Environment

Before the ISSU upgrade, check whether the current version of system software supports the ISSU function. You must ensure that the hardware and software are compatible with the current version. Hardware compatibility check, also called resource check, is performed to determine whether the LPU supports ISSU.

Software compatibility check is performed to determine the ISSU modes supported by each service module.

The following operation has no impact on the system and will not cause the slave MPU to restart. You can perform the operation at any time except during the ISSU upgrade.Run the issu precheck system-software system-file command in the user view. issu precheck system-software s9300V100R006C00SPC800.ccSystem upgrade type : lossy.System maximum down time : 600 seconds.Interface board compatibility:----------------------------------------------------------------------------

Slot Type SupportStatus MaxDownTime(s) Reason----------------------------------------------------------------------------

1 LPU fast-reboot 600 NULL2 LPU fast-reboot 600 NULL3 LPU fast-reboot 600 NULL----------------------------------------------------------------------------

View the SupportStatus field: If the value is fast-reboot, the ISSU upgrade will be quick. If the value is common-reboot, the LPU does not support the fast reboot function; therefore, the ISSU upgrade will be slow.3.5 (Optional) Setting the ISSU Rollback Timer

You can set the ISSU rollback timer if necessary.

You must finish the ISSU upgrade before the rollback timer expires; otherwise, the ISSU upgrade will fail.Run the issu timer rollback time command in the user view to set the ISSU rollback timer.issu timer rollback 120

The ISSU rollback timer is activated when the ISSU upgrade starts. By default, the ISSU rollback timer is 120 minutes.3.6 Performing the ISSU Upgrade

ISSU shortens service interruption time and improves device reliability.3.6.1 Running issu check to Upgrade Slave MPU

Run the issu check system-software system-file command to perform ISSU check.Once the command is run, the system enters the ISSU check phase. In this phase, the system checks reports on which ISSU modes are supported. ISSU check has the following impacts on the system:

The slave MPU restarts with the new version of system software and becomes the new master MPU.

The system view cannot be accessed.

The ISSU rollback timer is activated. The ISSU upgrade must be finished before the timer expires; otherwise, the ISSU upgrade will fail.Table 3-7 Description of ISSU check interactive messages

MessageDescription

Warning: The value of the ISSU rollback timer is 120 minutes. The system will begin the ISSU upgrade. Continue? [Y/N]: If you enter y, the system starts the ISSU check. If you enter n, the system stops executing the issu check command and exits the ISSU.

Warning: The slave board will be rebooted and check the software compatibility. Continue? [Y/N]: If you enter y, the slave MPU restarts with the new version of system software. Generally, the restart process lasts 2 minutes. After the slave MPU restarts, the system will check for software compatibility.

If you enter n, the system stops executing the issu check command and exits the ISSU.NOTEThis message is displayed when you upgrade the software to a C version of the current R version.

Warning: The slave board will be rebooted and generate the configuration file. Continue? [Y/N]: If you enter y, the slave MPU restarts with the new version of system software. Generally, the restart process lasts 2 minutes. After the slave MPU restarts, the system generates the configuration file.

If you enter n, the system stops executing the issu check command and exits the ISSU.NOTE This message is displayed when you upgrade the software to a new R version. When you upgrade the software to a later R version, the system directly uses the lossy ISSU mode. After the slave MPU restarts, the system immediately generates the configuration file, and does not check for software compatibility.

In the following example, the previous system software is s9300v100r003c01.cc and the new system software is s9300V100R006C00SPC800.cc. issu check system-software s9300V100R006C00SPC800.cc

Warning: The value of the ISSU rollback timer is 120 minutes. The system will begin the ISSU upgrade. Continue? [Y/N]:yInfo: The system is comparing compatibility ID...Info: The system is checking the hardware compatibility...Warning: The slave board will be rebooted and check the software compatibility. Continue? [Y/N]:yInfo: The slave board is rebooting in cfcard:/s9300V100R006C00SPC800.cc...Info: The new AMB is registered.Info: The system is generating the configuration file...Info: The system supports Lossy ISSU.Info: Any of the following operations can be performed as required:

1. View detailed information about ISSU check result by using the display command (display issu check-result).2. The ISSU rollback timer can be configured before ISSU start by using the command (issu timer rollback). The default value of the timer is 120 minutes.3. To start ISSU, Run the command (issu start). Otherwise, the system will roll back to the old version after the ISSU timer time out.

4. To roll back the system to the old version immediately, run the command (issu abort).3.6.2 Running issu start to Perform ISSU

Run the display issu state command to view the current ISSU status. When the ISSU check is in the Finished state, run the issu start command in the user view to perform the ISSU upgrade. display issu state------------------------------------------------

Phase State------------------------------------------------

1.ISSU check finished2.ISSU start -3.ISSU switchover -4.ISSU confirm -------------------------------------------------

The cancel ISSU command : issu abort.To abort the ISSU upgrade, see 3.6.3

REF _Ref278481021 \h (Optional) Running issu abort to Abort ISSU Upgrade.Table 3-8 Description of ISSU start interactive messages

MessageDescription

Info: The lossy ISSU process will start. Continue? [Y/N]: If you enter y, the system starts the lossy ISSU upgrade.

If you enter n, the system stops executing the issu start command and waits for the next command.

To continue the upgrade, run the issu start command before the ISSU rollback timer expires.

To abort the upgrade, run the issu abort command.

If you do not run the issu start or issu abort command, the system rolls back and exits the ISSU when the ISSU rollback timer expires.

issu startInfo: The Lossy ISSU process will start. Continue? [Y/N]:yInfo: The system will start lossy ISSU upgrade.Info: The system is copying the configuration file...Info: The operation of copying the configuration file is complete.Info: The system is preparing resources...Info: The resource preparation is complete.Info: The system is preparing for batch backup...Info: The preparation for batch backup is complete.Info: The system is busy with phase 1 batch backup...Info: Phase 1 batch backup is complete.Info: The system is busy with configuration recovery of the new AMB...Info: Configuration recovery of the new AMB is complete.Info: The system is busy with phase 2 batch backup...Info: Phase 2 batch backup is complete.Info: Configuration of interface boards is recovering...Info: Configuration recovery of interface boards is complete.Info: The system is busy with phase 3 batch backup...Info: Phase 3 batch backup is complete.Info: The system is in real-time backup phase. Please check the backup status before performing the ISSU switchover (Command: display issu backup state; issu switchover).3.6.3 (Optional) Running issu abort to Abort ISSU Upgrade

If you want to abort the ISSU upgrade, run the issu abort command. If you choose to abort you do not need to perform the operations in sections 3.6.4

REF _Ref278481042 \h Running issu switchover to Switch the Control Plane and 3.6.5

REF _Ref278481051 \h Running issu confirm to Verify the ISSU Upgrade. If you choose to continue the ISSU upgrade, skip this step and go to section 3.6.4

REF _Ref278481042 \h Running issu switchover to Switch the Control Plane.Table 3-9 Description of ISSU abort interactive messagesMessageDescription

Warning: The ISSU will be aborted, the system will roll back to the old version, and the new AMB will be rebooted. This operation will take 10 minutes. Continue? [Y/N]: If you enter y, the system aborts the ISSU upgrade and rolls back to the previous version. The new master MPU restarts with the previous version.

If you enter n, the system stops executing the issu abort command and continues the ISSU upgrade.

3.6.4 Running issu switchover to Switch the Control Plane

Run the display issu state command to check whether the ISSU status is Finished. display issu state------------------------------------------------

Phase State------------------------------------------------

1.ISSU check finished2.ISSU start finished3.ISSU switchover -4.ISSU confirm -------------------------------------------------

Switching the control plane will interrupt the Telnet connection for 30s. After the interruption, press Enter to log back in.The following is an example: issu switchoverInfo: The system will check the ready mode of all modules first. Please wait...Info: The check for the switchover between forwarding planes starts...Info: The check for the switchover on slot 7 succeeded.Info: The check for the switchover between forwarding planes is complete.Info: The switchover between the forwarding planes starts...Warning: The connect of telnet will be down, please retry after 30 seconds.Info: The system will check the ready mode of all modules first. Please wait...Info: The check for the switchover between forwarding planes starts...Info: The check for the switchover on slot 7 succeeded.Info: The check for the switchover on slot 8 succeeded.Info: The check for the switchover between forwarding planes is complete.Info: The switchover between the forwarding planes starts...Info: The switchover on slot 7 succeeded.Info: The switchover on slot 8 succeeded.Warning: The connect of telnet will be down, please retry after 30 seconds.Log in to the new master MPU through Telnet. issu switchoverInfo: Data smoothing is complete.Info: Aging starts...Info: The aging of slot 7 succeeded.Info: The aging of slot 8 succeeded.Info: The switchover is complete. Please confirm the operation of the ISSU upgrade by using the command (issu confirm).

When switching the control plane, run the display issu state command to view the current ISSU status.To view the operation results, you can run the display issu switch-result { check | prepare | age } command when you perform ISSU precheck and prepare the switchover. If the switchover is failed, this command can display the cause.

display issu switch-result check---------------------------------------------------------

Slot Type Result---------------------------------------------------------

1 new RTP unknown

1 old RTP unknown2 old RTP unknown2 new RTP unknown3 old RTP unknown3 new RTP unknown8 old AMB success

---------------------------------------------------------

3.6.5 Running issu confirm to Verify the ISSU Upgrade

Run the display issu state command to check whether the ISSU switchover status is Finished. display issu state------------------------------------------------

Phase State------------------------------------------------

1.ISSU check finished2.ISSU start finished3.ISSU switchover finished4.ISSU confirm -------------------------------------------------

After the active/standby switchover, the system is still in ISSU state since the ISSU flag bits have not been deleted. (You can run the display issu state command to confirm the ISSU status). Run the issu confirm command to verify that the original master MPU restarts with the new system software. After the original MPU restarts, the ISSU flag bits will be deleted and the system will function normally. issu confirmInfo: The slave MPU of the new version reboots. After the reboot is complete, the system automatically exits from ISSU.

3.7 Verifying the ISSU Upgrade

Verifying the Current System Software

After you run the issu confirm command, the original master MPU restarts with the new system software and registers to the new master MPU. Verify that the current startup software on both the master and slave MPUs is the target version. display startup

MainBoard: Configured startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup system software: cfcard:/s9300V100R006C00SPC800.cc Next startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup saved-configuration file: cfcard:/vrpcfg.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: default Next startup paf file: default Startup license file: default Next startup license file: default Startup patch package: NULL Next startup patch package: NULL

SlaveBoard: Configured startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup system software: cfcard:/s9300V100R006C00SPC800.cc Next startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup saved-configuration file: cfcard:/vrpcfg.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: default Next startup paf file: default Startup license file: default Next startup license file: default Startup patch package: NULL Next startup patch package: NULL

Verifying Board Registration Status

Run the display device command in any view to check the registration status of the boards. The boards should be in the Registered state. display deviceS9306's Device status:Slot Sub Type Online Power Register Alarm Primary- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1 - G24SA Present PowerOn Registered Normal NA

2 - G24SC Present PowerOn Registered Normal NA

3 - F48SA Present PowerOn Registered Normal NA7 - SRUA Present PowerOn Registered Normal Slave8 - SRUA Present PowerOn Registered Normal Master

PWR1 - - Present PowerOn Registered Normal NACMU1 - CMUA Present PowerOn Registered Normal MasterFAN1 - - Present PowerOn Registered Normal NA

FAN2 - - Present PowerOn Registered Normal NA

Verifying Configuration Restoration

After the device restarts, run the display current-configuration command in any view to check device configurations. To compare the new configuration file with the configuration file saved in the storage device, run the compare configuration command in the user view.Verifying Services

Check whether services are working normally by using either of the following methods: Check whether any table entries are missing, for example, the entries of the routing table, FIB table, and MAC address table. Check whether the service traffic volume remains the same after the upgrade. Ask network management personnel to verify services are working normally.3.8 Rolling Back to an Earlier Version


Rollback scenarios: The upgrade was successful and the device is functioning properly, but the new system software does not meet service requirements. The device does not function properly after the upgrade.Rollback methods: If the device functions properly after the upgrade, perform rollback by using the command line. If the device does not function properly after the upgrade, perform rollback using the BootROM.This section describes the rollback method using command line. For details on this method, see chapter 6

REF _Ref294794496 \h Upgrading the System Software Using the BootROM Menu.3.8.2 Rollback Process

Figure 3-5 Version rollback flowchart


The following instructions assume that the previous system software is version s9300v100r003c01.cc. Run the following command to specify the previous system software for next startup, according to your own system: startup system-software s9300v100r003c01.ccSpecify the previous system software for next startup on the slave MPU. startup system-software s9300v100r003c01.cc slave-boardCheck whether the system software and configuration file of the earlier version have been specified for next startup. display startup

MainBoard: Configured startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup system software: cfcard:/s9300V100R006C00SPC800.cc Next startup system software: cfcard:/s9300v100r003c01.cc Startup saved-configuration file: cfcard:/vrpcfg.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: default Next startup paf file: default Startup license file: default Next startup license file: default Startup patch package: NULL Next startup patch package: NULL

SlaveBoard: Configured startup system software: cfcard:/s9300V100R006C00SPC800.cc Startup system software: cfcard:/s9300V100R006C00SPC800.cc Next startup system software: cfcard:/s9300v100r003c01.cc Startup saved-configuration file: cfcard:/vrpcfg.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: default Next startup paf file: default Startup license file: default Next startup license file: default Startup patch package: NULL Next startup patch package: NULL3.8.4 Restarting the Device

Run the reboot command to restart the device. The system will then startup using the previous system software. rebootInfo: The system is now comparing the configuration, please wait.

Warning: All the configuration will be saved to the configuration file for the next startup:cfcard:/vrpcfg.zip, Continue?[Y/N]:y

System will reboot! Continue?[Y/N]:y3.8.5 Verifying the Rollback

The procedure for verifying a version rollback is identical to the procedure for verifying an upgrade. For details, see section 3.7

REF _Ref294535651 \h Verifying the ISSU Upgrade

REF _Ref278481144 \n \h 2.5 .4 CSS Upgrade4.1 Before You Start


Table 4-10 Upgrade notes for versionsVersionUpgrade Note

S9300V100R003 version:S9300 V100R003C00S9300 V100R003C00SPC200S9300 V100R003C01S9300 V100R003C01SPC100S9300 V100R006C00SPC300S9300 V100R006C00SPC500After the upgrade, adjust the configurations related to the changed commands according to the Quidway S9300 V100R006C00SPC800 Release Notes.


Before you upgrade the system software to a version that supports the cluster switching system (CSS) feature, read this section carefully to understand the possible impact of the upgrade on the system.Impact on the System During the Upgrade

a. Impact on servicesServices are interrupted while the S9300s are restarting, and will be restored 10 minutes later.

b. Impact on network communicationThe S9300s need to be restarted during the upgrade; therefore, communication between the S9300s and the network management system (NMS) will be interrupted for about 10 minutes.4.1.3 Impact on the System After the Upgrade

There is no impact on the system after the upgrade.4.1.4 Precautions

No.Description

1 Before the upgrade, collect device information, interface information, version information, configuration file, and all routing table, FIB table, and MAC address table information.After the upgrade, collect the same information again and compare it with the previous information to check whether the CSS operates and transmits services properly.The S9306 and S9312 support the CSS function but the S9303 does not.

All the SRUs except LE02SRUA VA and LE02SRUB VA support the CSS function. The two SRUs on a device must be identical models. That is, an SRUA and an SRUB cannot be installed on the same device.The size of memory space on all SRUs must be identical. If the size of the slave SRUs memory space is smaller than the size of the master SRUs memory space, the slave SRU cannot register.The software can only be rolled back to V100R006 or V100R003, but cannot be rolled back to V100R001 or V100R002.

The SRU equipped with a stack card cannot start in the V100R001 or V100R002 version. To roll back it to V100R001 or V100R002, remove the stack card first.


Figure 4-6 Upgrade flowchart

Table 4-11 Upgrade scheduleProcedure StepTime Required (Minutes)Remarks

Prepare for the upgrade101. Check that the stack cables and stack cards are installed properly and that the required tools and software are ready.2. Back up key files on the CF card.

Perform the upgrade101. Load the system software.2. Restart the device.

Verify the upgrade11. Check whether configurations are lost.2. Check whether boards start properly.

Roll back to an earlier version101. Specify the system software of an earlier version for next startup.2. Restart the device.



Contact Huawei technical personnel or visit http://support.huawei.com to obtain the latest documents, including: Quidway S9300 Product Documentation (V100R006C00_03) Quidway S9300 V100R006C00SPC800 Release Notes4.3.2 Obtaining Tools

Prepare the following tools before upgrading: Operation terminal, such as a desktop computer or a portable computer Network cable and serial cable FTP server software or TFTP server software for the upgrade (the S9300s function as the clients)

Huawei does not provide the FTP server, TFTP server, or FTP client software. The customer needs to provide this software as required.4.3.3 Obtaining Upgrade Software

To obtain the required upgrade software, contact Huawei technical personnel or visit http://support.huawei.com.4.3.4 Obtaining the License File

If the license needs to be updated, purchase a new license from the local Huawei office.4.3.5 Verifying the Current Version

2. Run the display version command in the user view to view the system software running on the devices.

On device 1: display versionHuawei Versatile Routing Platform SoftwareVRP (R) software, Version 5.70 (S9300 V100R003C01)Copyright (C) 2003-2010 HUAWEI TECH CO., LTDQuidway S9306 Terabit Routing Switch uptime is 0 week, 0 day, 2 hours, 56 minutesOn device 2: display versionHuawei Versatile Routing Platform SoftwareVRP (R) software, Version 5.70 (S9300 V100R003C01)Copyright (C) 2003-2010 HUAWEI TECH CO., LTDQuidway S9306 Terabit Routing Switch uptime is 0 week, 0 day, 2 hours, 56 minutes3. Run the display device command in the user view to check the status of the SRUs and LPUs. Ensure that the SRUs and LPUs are working properly.On device 1: display deviceS9306's Device status:Slot Sub Type Online Power Register Alarm Primary- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1 - G48TA Present PowerOn Registered Normal NA4 - X4UXC Present PowerOn Registered Normal NA5 - G48PA Present PowerOn Registered Normal NA7 - SRUA Present PowerOn Registered Normal Slave8 - SRUA Present PowerOn Registered Normal MasterPWR1 - - Present PowerOn Registered Normal NACMU1 - CMUA Present PowerOn Registered Normal MasterFAN1 - - Present PowerOn Registered Normal NAFAN2 - - Present PowerOn Registered Normal NA

On device 2: display deviceS9306's Device status:Slot Sub Type Online Power Register Alarm Primary- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1 - G48TA Present PowerOn Registered Normal NA4 - X4UXC Present PowerOn Registered Normal NA5 - G48PA Present PowerOn Registered Normal NA7 - SRUB Present PowerOn Registered Normal Slave8 - SRUB Present PowerOn Registered Normal MasterPWR1 - - Present PowerOn Registered Normal NACMU1 - CMUA Present PowerOn Registered Normal MasterFAN1 - - Present PowerOn Registered Normal NAFAN2 - - Present Po

quidway s9300 terabit routing switch v100r006c00spc800 upgrade guide.doc

Documents

upgrade software

upgrade overview

upgrade environment

huawei trademarks

document issues

latest document issue

upgrade process overview

preupgrade checklist