Quidway S9300 Terabit Routing Switch V100R006C00SPC800 Upgrade Guide

Quidway S9300 Terabit Routing Switch V100R006C00SPC800
Upgrade Guide
Issue Date
02 2011-12-28
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: Email: http://www.huawei.com support@huawei.com
Issue 02 (2011-12-28)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
Quidway S9300 Terabit Routing Switch Upgrade Guide
About This Document
About This Document

Change History
Changes 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 1.1.3Precautions.
Issue 01 (2011-09-30)
This issue is the first official release.
Issue 02 (2011-12-28)
ii
Contents
Contents
About This Document.......................................................................ii
Issue 02 (2011-12-28)
iii
1 Upgrade Overview
1
Intended 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 Overview
IMPORTANT: Before upgrading, read the corresponding chapters marked . 2. Command Line Upgrade 3. ISSU Upgrad e 4. CSS Upgrad e 5. SPU Upgrad e
Issue 02 (2011-12-28)
1 Upgrade Overview
Intended Upgrade
2. Command Line Upgrade
3. ISSU Upgrad e
4. CSS Upgrad e
5. SPU Upgrad e
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
Issue 02 (2011-12-28)
2 Command Line Upgrade
Command Line Upgrade

1.1 Before You Start
1.1.1 Version Requirements
Table 1.1 Upgrade notes for versions Version S9300 V100R001 versions: S9300 V100R001C02B118 S9300 V100R001C02B125 S9300 V100R001C03SPC001 S9300 V100R002C00 versions: S9300 V100R002C00SPC001 S9300 V100R002C00SPC002 S9300 V100R002C00SPC100 S9300 V100R002C00SPC200 S9300 V100R002C01 version: S9300 V100R002C01 S9300 V100R003C00 S9300 V100R003C00SPC200 S9300 V100R003C01 S9300 V100R003C01SPC100 S9300 V100R006C00SPC300 S9300 V100R006C00SPC500 S9300 V100R006C00SPC600 Upgrade Note These versions can be directly upgraded to S9300V100R006C00SPC800. Some commands will be modified after the upgrade. For details, see the Quidway S9300 V100R006C00SPC800 Release Notes.
1.1.2 Impact of the Upgrade

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.
Issue 02 (2011-12-28)
Impact on the System During the Upgrade

a. Impact on services Services 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 communication The 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 Upgrade

There is no impact on the system after the upgrade.
1.1.3 Precautions
Precautions Before Upgrade
No. 1 2 Description After the device is upgraded from V100R001C03 to V100R002 or a later version, TACACS authentication user rights are lost and need to be reconfigured. V100R006 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 Flash Memory Size : 256 : 8 M bytes M bytes
LPU version information :
... 3 If 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. Before 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.
Issue 02 (2011-12-28)
No. 5
Description When 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.
Before 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. If 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. When 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. After 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. On 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. After 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. The 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.
10
11
12
Issue 02 (2011-12-28)
Precautions Before Degrade

No. 1 Description The 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 localuser aaa level 3 to reconfigure the user level.
1.2 Upgrade Process Overview

Figure a.1 Upgrade flowchart
Start
Prepare for the upgrade
See 2.3
Perform the upgrade
See 2.4
Check if upgrade is successful Yes End
See 2.4.4
No
Roll back to an earlier version See 2.5
Table 1.1 Upgrade schedule Procedure Step Time Required (Minutes) 5 Remarks
Prepare tools and software.
Issue 02 (2011-12-28)
Perform the upgrade
20
1. Back up files. 2. Load the system software. 3. Restart the device.
Verify the upgrade
1.Check the version 2. Check whether configurations are lost. 3. Check whether boards start properly.
Roll back to an earlier version
10
1. Specify the system software of an earlier version for next startup. 2. Restart the device.
1.3 Preparing for the Upgrade

1.3.1 Pre-upgrade Checklist
Table 1.1 lists the items to be checked before the upgrade. Table 1.1 Pre-upgrade checklist No. 1 Item Obtaining Upgrade Reference Documents Obtaining Tools Expected Result The reference documents have been printed or downloaded to your computer. The operation terminal, network cable, serial port cable, and FTP or TFTP software are ready. The target system software (.cc) has been obtained from Huawei. The license files have been obtained from Huawei. The commands in the configuration file meet the target version requirements. The current version meets all the Version Requirements. The MPUs and LPUs are working properly. Keep a record of the status of the board in each slot for future troubleshooting. Actual Result
3 4 5
Obtaining Upgrade Software Obtaining the License File Preparing the Configuration File Verifying the Current Version Verifying the Running Status of the Device
6 7
Issue 02 (2011-12-28)
Setting Up the Upgrade Environment Backing Up CF Card Data
The network to be upgraded has been set up. The 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. Check the remaining space on the CF cards and ensure there is sufficient space for the system software.
10
Checking the Space on the CF Cards
1.3.2 Obtaining Upgrade Reference Documents

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 Guide
1.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.
1.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.
1.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.
Issue 02 (2011-12-28)
1.3.6 Preparing the Configuration File

To batch issue configurations to the device after upgrade, load the latest configuration file to the device.
1.3.7 Verifying the Current Version

Run the display version command in the user view to check the current system software version and ensure that it meets the upgrade requirement.
<Quidway> display version Huawei Versatile Routing Platform Software VRP (R) software, Version 5.70 (S9300 V100R003C01) Copyright (C) 2003-2010 HUAWEI TECH CO., LTD Quidway S9303 Terabit Routing Switch uptime is 0 week, 0 day, 2 hours, 56 minutes
In 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.
1.3.8 Verifying the Running Status of the Device

1. 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.
<Quidway> display device S9303's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2 F48SA Present PowerOn Registered Normal NA 4 MCUA Present PowerOn Registered Normal Slave 5 MCUA Present PowerOn Registered Normal Master PWR1 Present PowerOn Registered Normal NA
If 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. 2. Run the display alarm command in the user view to check the status of the device. Ensure that MPUs and LPUs are working properly.
<Quidway> display alarm all ---------------------------------------------------------------------------Level Date Time Info Warning 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 1.1 describes the alarm severities defined by Huawei.
Issue 02 (2011-12-28) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 9
Table 1.1 Alarm severity description
Issue 02 (2011-12-28)
10
Level 1 2 3 4 5 6
Description Critical Major Minor Warning Cleared Indeterminate
----End
1.3.9 Setting Up the Upgrade Environment

As shown in Figure a.1, 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.
Issue 02 (2011-12-28)
11
Figure a.1 Network diagram for upgrading the system through TFTP or FTP
1.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 1.4.1Loading System Software.
1.3.11 Checking the Space on the CF Cards

1. 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.
<Quidway> dir cfcard:/ Directory of cfcard:/ Idx 0 1 2 3 4 5 6 7 8 9 10 11 Attr -rwdrw-rw-rw-rw-rw-rw-rw-rwdrwdrwdrwSize(Byte) 4 198 524,381 589 333,436 27,455,925 3,241 14,268 Date Time FileName Nov 04 2010 21:44:22 snmpnotilog.txt Nov 04 2010 20:55:32 logfile Nov 04 2010 21:47:36 $_patchstate_a Nov 04 2010 21:48:06 private-data.txt Nov 04 2010 20:55:54 vrpcfg.zip Jan 29 2010 16:54:40 s9300v100r003sph003.pat Nov 04 2010 19:43:18 s9300v100r003c01.cc Apr 08 2010 09:45:04 vrpcfg1.zip May 22 2010 16:09:10 $_patchstate_reboot Sep 21 2010 14:01:00 sysdrv Sep 21 2010 14:01:00 compatible Sep 25 2010 11:55:00 dhcp
Issue 02 (2011-12-28)
12
506,744 KB total (241,808 KB free)
# View the available space on the CF card of the slave MPU.

<Quidway> dir slave#cfcard: Directory of slave#cfcard:/ Idx 0 1 2 3 4 5 6 7 8 9 10 11 Attr -rwdrw-rw-rw-rw-rw-rw-rw-rwdrwdrwdrwSize(Byte) 4 198 524,381 589 333,436 27,455,925 3,241 14,268 Date Nov 04 Nov 04 Nov 04 Nov 04 Nov 04 Jan 29 Nov 04 Apr 08 May 22 Sep 21 Sep 21 Sep 25 Time 21:44:22 20:55:32 21:47:36 21:48:06 20:55:54 16:54:40 19:43:18 09:45:04 16:09:10 14:01:00 14:01:00 11:55:00 FileName snmpnotilog.txt logfile $_patchstate_a private-data.txt vrpcfg.zip s9300v100r002sph003.pat s9300v100r002c00.cc vrpcfg1.zip $_patchstate_reboot sysdrv compatible dhcp
2010 2010 2010 2010 2010 2010 2010 2010 2010 2010 2010 2010
506,744 KB total (241,808 KB free)
More than 65000 KB available memory space is sufficient for the upgrade. 2. 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.
<Quidway> delete cfcard:/vrpcfg1.zip Delete cfcard:/vrpcfg1.zip?[Y/N]:y Info: Deleting file cfcard:/vrpcfg1.zip...succeeded.
# Delete unneeded files from the CF card of the slave MPU.


<Quidway> delete slave#cfcard:/vrpcfg1.zip Delete 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:
<Quidway> undelete cfcard:/vrpcfg1.zip Undelete cfcard:/vrpcfg1.zip?[Y/N]:y %Undeleted file cfcard:/vrpcfg1.zip.
To permanently delete files from the recycle bin, run the following commands:
<Quidway> reset recycle-bin cfcard:/ <Quidway> reset recycle-bin slave#cfcard:/
----End
1.4 Performing the Upgrade

Table 1.1 Upgrade process No. 1 Action Back 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. Check whether the files were loaded. Specify the system software and configuration file for next startup. If a slave MPU is used, the files must be specified on the slave MPU. Command Reference 1.4.1Loading System Software
dir
1.4.2Verifying File Loading 1.4.3Specifying the System Software
startup systemsoftware startup systemsoftware slave-board startup savedconfiguration display startup
Check whether the system software and configuration file specified for next startup are correct. Perform cyclic redundancy check (CRC) check on the system software. Restart the device.
1.4.3Specifying the System Software
check startup crc next
1.4.3Specifying the System Software
reboot
1.4.4Restarting the Device

14
Issue 02 (2011-12-28)
No. 7
Action Verify the upgrade.
Command display startup check version display device display currentconfiguration
Reference 1.4.5Activating the License
1.4.1 Loading System Software

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.
Issue 02 (2011-12-28)
15
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.
<Quidway> dir *.cc Directory of cfcard:/ Idx 0 Attr -rwSize(Byte) 59,455,925 Date Time Nov 04 2010 19:43:18 FileName s9300v100r003c01.cc
506,744 KB total (240,784 KB free) <Quidway> dir *.zip Directory of cfcard:/ Idx 0 Attr -rwSize(Byte) 589 Date Time Nov 04 2010 20:55:54 FileName vrpcfg.zip
506,744 KB total (240,720 KB free) <Quidway> dir *.pat Directory of cfcard:/ Idx 0 Attr -rwSize(Byte) 333,436 Date Time Jan 29 2010 16:54:40 FileName s9300v100r003sph003.pat
506,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.
<Quidway> tftp 10.164.30.29 put s9300v100r003c01.cc s9300v100r003c01-bak.cc Info: 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. <Quidway> tftp 10.164.30.29 put vrpcfg.zip vrpcfg-bak.zip Info: 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. <Quidway> tftp 10.164.30.29 put s9300v100r003sph003.pat s9300v100r003sph003-ba k.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.
<Quidway> tftp 10.164.30.29 get S9300V100R006C00SPC800.cc Info: 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.
<Quidway> tftp 10.164.30.29 get license.dat Info: Transfer file in binary mode. 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.
<Quidway> tftp 10.164.30.29 get vrpcfgnew.zip Info: Transfer file in binary mode. Downloading the file from the remote TFTP server. Please wait.../ TFTP: Downloading the file successfully. 2757 bytes received in 1 second.
----End
Method 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.
6. 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:/.
<Quidway> system-view [Quidway] ftp server enable Info: Succeeded in starting the FTP server. [Quidway] aaa [Quidway-aaa] local-user S9300 password simple 123456 info: A new user added [Quidway-aaa] local-user S9300 ftp-directory cfcard: [Quidway-aaa] local-user S9300 service-type ftp
The 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. 7. 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 ftp D:\ftp> ftp 10.164.30.20 Connected to 10.164.30.20. 220 FTP service ready. User(10.164.30.20:(none)):S9300 # Enter the user name 331 Password required for s9300. Password: # Enter password 123456 and press enter. The password is displayed in cipher text. 230 User logged in. ftp> binary 200 Type set to I. ftp> get s9300v100r003c01.cc 200 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.zip
Issue 02 (2011-12-28)
18

200 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.pat 200 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. 8. 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.20 Connected 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> binary 200 Type set to I. ftp> put S9300V100R006C00SPC800.cc
You 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.
9. Upload the license file to the S9300.

ftp> put license.dat
10. (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
----End
Issue 02 (2011-12-28)
19
Method 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.
11. 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. 12. 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.
<Quidway> cd cfcard:/ <Quidway> ftp 10.164.30.27 Trying 10.164.30.27 ... Press CTRL+K to abort Connected to 10.164.30.27. 220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user User(10.164.30.27:(none)):S9300 # Enter the user name and press Enter. 331 Give me your password, please Enter password: # Enter the password 123456 and press Enter. The password displayed on the screen is in cipher text. 230 Logged in successfully [ftp] binary 200 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.cc 200 PORT command okay 150 "D:\ftp\s9300v100r003c01-bak.cc" file ready to receive in IMAGE / Binary mod e
Issue 02 (2011-12-28)
20
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 okay 150 "D:\FTP\vrpcfg-bak.zip" file ready to receive in IMAGE / Binary mode 226 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 226 Transfer finished successfully. FTP: 333436 byte(s) sent in 0.322 second(s) 1035.51Kbyte(s)/sec.
13. Obtain the system software of the target version.

[ftp] get S9300V100R006C00SPC800.cc 200 PORT command okay 150 "D:\ftp\ S9300V100R006C00SPC800.CC" file ready to send (52749606 bytes) in IM AGE / Binary mode ................................................................................ ................................................................................ ................................................................................ ................................................................................ ................................................................................ ................................................................ 226 Transfer finished successfully. 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. 14. Obtain the license file.
[ftp] get license.dat
15. (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.zip
16. Close the FTP connection.

[ftp] bye 221 Windows FTP Server (WFTPD, by Texas Imperial Software) says goodbye
----End
Issue 02 (2011-12-28)
21
Method 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 Upgrading the System Software Using the BootROM Menu.
1.4.2 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.
<Quidway> dir cfcard:/ Directory of cfcard:/ Idx Attr Size(Byte) Date Time FileName 0 -rw4 Nov 04 2010 21:44:22 snmpnotilog.txt 1 drw- Nov 04 2010 20:55:32 logfile 2 -rw198 Nov 04 2010 21:47:36 $_patchstate_a 3 -rw524,381 Nov 04 2010 21:48:06 private-data.txt 4 -rw2757 Nov 05 2010 20:55:54 vrpcfgnew.zip 5 -rw333,436 Jan 29 2010 16:54:40 s9300v100r003sph003.pat 6 -rw27,455,925 Nov 04 2010 19:43:18 s9300v100r003c01.cc 7 -rw52,749,606 Nov 05 2010 06:48:54 s9300V100R006C00SPC800.cc 8 -rw1,748 Nov 05 2010 06:09:16 license.dat 9 -rw14,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 dhcp
1.4.3 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.
<Quidway> startup system-software s9300V100R006C00SPC800.cc Info: 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.

<Quidway> 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.

<Quidway> startup system-software s9300V100R006C00SPC800.cc slave-board Info: 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.
<Quidway> display startup MainBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup paf file: Next startup paf file: Startup license file: Next startup license file: Startup patch package: Next startup patch package: SlaveBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup paf file: Next startup paf file: Startup license file: Next startup license file: Startup patch package: Next startup patch package:
cfcard:/s9300v100r003c01.cc cfcard:/s9300v100r003c01.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/vrpcfg.zip cfcard:/vrpcfg.zip default default default default NULL NULL
cfcard:/s9300v100r003c01.cc cfcard:/s9300v100r003c01.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/vrpcfg.zip cfcard:/vrpcfg.zip default default default default NULL 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.
<Quidway> copy vrpcfgnew.cfg slave#cfcard:/ Copy cfcard:/vrpcfgnew.cfg to slave#cfcard:/vrpcfgnew.cfg?[Y/N]:y 100% complete Info: Copied file cfcard:/vrpcfgnew.cfg to slave#cfcard:/vrpcfgnew.cfg...Done. <Quidway> startup saved-configuration vrpcfgnew.cfg Info: Succeeded in setting the configuration for booting system.
3. Perform cyclic redundancy check (CRC) check on the system software.

<Quidway> check startup crc next Warning: This operation will take several minutes! Continue?[Y/N]:y Check startup software CRC .................................................................................. .................................................. ...........................................
Issue 02 (2011-12-28)
23

Info: ok Check startup software CRC in slaveboard............................................. ok
----End
1.4.4 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.
<Quidway> reboot Info: The system is now comparing the configuration, please wait. Warning: Current configuration will be saved to the next startup saved-configura tion file: cfcard:/vrpcfg.zip!Continue?[Y/N]: y System will reboot! Continue?[Y/N]: y
Enter y to restart the system.
1.4.5 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.
<Quidway> copy license.dat slave#cfcard:/ Copy cfcard:/license.dat to slave#cfcard:/license.dat?[Y/N]:y 100% complete| Info: Copied file cfcard:/license.dat to slave#cfcard:/license.dat...Done. <Quidway> license active license.dat
1.5 Verifying the Upgrade

1.5.1 Verification Checklist
Table 1.1 Verification checklist No. 1 Item Verifying the Current System Software Expected Result The current version is the same as the target version. Actual Result
Issue 02 (2011-12-28)
24
Verifying That All the Programs Have Been Upgraded Verifying Board Registration Status Verifying Configuration Restoration Verifying Services
All the software programs have been upgraded. The boards are in the Registered state. No configuration has been lost.
3 4
Services are working normally.
1.5.2 Verifying the Current System Software

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.
<Quidway> display startup MainBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup paf file: Next startup paf file: Startup license file: Next startup license file: Startup patch package: Next startup patch package: SlaveBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup paf file: Next startup paf file: Startup license file: Next startup license file: Startup patch package: Next startup patch package:
cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/vrpcfgnew.zip cfcard:/vrpcfgnew.zip default default default default NULL NULL
cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/vrpcfgnew.zip cfcard:/vrpcfgnew.zip default default default default NULL NULL
1.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.
<Quidway> check version Frame/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. 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. 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.
3.
1.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.
<Quidway> display device S9303's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2 F48SA Present PowerOn Registered Normal NA 4 MCUA Present PowerOn Registered Normal Slave 5 MCUA Present PowerOn Registered Normal Master PWR1 Present PowerOn Registered Normal NA
1.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 1.3.10Backing 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.
1.5.6 Verifying Services

Use either of the following methods to check whether services are working normally after the upgrade.
Issue 02 (2011-12-28)
26
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.
1.6 Rolling Back to an Earlier Version

1.6.1 Rollback Scenarios and Methods
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 1.6.3Specifying the Previous System Software for Next Startup. If the device does not function properly after the upgrade, perform rollback using the BootROM.
Issue 02 (2011-12-28)
27
1.6.2 Rollback Process

Figure a.1 Version rollback flowchart
Start
Specify the startup software
See 2.6.2
Restart the device
See 2.6.3
No Check if rollback is successful Yes End See 2.6.4
1.6.3 Specifying the Previous System Software for Next Startup

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:
<Quidway> startup system-software s9300v100r003c01.cc Info: Succeeded in setting the software for booting system.
Specify the previous system software for next startup on the slave MPU.
<Quidway> startup system-software s9300v100r003c01.cc slave-board Info: Succeeded in setting the software for booting system.
If a new configuration file was used in the upgrade, restore the old configuration file.
<Quidway> startup saved-configuration vrpcfg.cfg Info: 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.
<Quidway> display startup MainBoard: Configured startup system software:
cfcard:/s9300V100R006C00SPC800.cc
Issue 02 (2011-12-28)
28

Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup paf file: Next startup paf file: Startup license file: Next startup license file: Startup patch package: Next startup patch package: SlaveBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup paf file: Next startup paf file: Startup license file: Next startup license file: Startup patch package: Next startup patch package:

cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300v100r003c01.cc cfcard:/vrpcfgnew.zip cfcard:/vrpcfg.zip default default default default NULL NULL
cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300v100r003c01.cc cfcard:/vrpcfgnew.zip cfcard:/vrpcfg.zip default default default default NULL NULL

Run the reboot command to restart the device. When the system restarts, it will be running the previous system software.
<Quidway> reboot Info: The system is now comparing the configuration, please wait. Warning: All the configuration will be saved to the configuration file for the n ext 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]:y
When 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.
1.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 1.5Verifying the Upgrade.
Issue 02 (2011-12-28)
29
3 ISSU Upgrade
ISSU Upgrade
The target version must support the in-service software upgrade (ISSU) function. Only the S9300 V100R003C01 and later versions support the ISSU function.

Before you upgrade the system software, read this section carefully to understand the possible impact of the upgrade on the system.
1.7.3 Impact on the System During the Upgrade
Impact on services
LPUs will be reset during the upgrade, causing a service interruption of about 2 minutes.
Impact on network communication
An 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.
1.7.4 Impact on the System After the Upgrade

1.8 Precautions
No. 1 Description 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.
Issue 02 (2011-12-28)
30
3 ISSU Upgrade

1.9.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.
<Quidway> display device S9306'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 NA 7 SRUA Present PowerOn Registered Normal Master 8 SRUA Present PowerOn Registered Normal Slave PWR1 Present PowerOn Registered Normal NA CMU1 CMUA Present PowerOn Registered Normal Master FAN1 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.
<Quidway> display switchover state Slot 7 HA FSM State(master): realtime or routine backup. Slot 8 HA FSM State(slave): receiving realtime or routine data.
1.9.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.
<Quidway> check version all Frame/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
3 ISSU Upgrade
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.
1.10 (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.
<Quidway> issu precheck system-software s9300V100R006C00SPC800.cc System upgrade type : lossy. System maximum down time : 600 seconds. Interface board compatibility: ---------------------------------------------------------------------------Slot Type SupportStatus MaxDownTime(s) Reason ---------------------------------------------------------------------------1 LPU fast-reboot 600 NULL 2 LPU fast-reboot 600 NULL 3 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.
1.11 (Optional) Setting the ISSU Rollback Timer

You can set the ISSU rollback timer if necessary.
Issue 02 (2011-12-28)
32
3 ISSU Upgrade
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.
<Quidway>issu timer rollback 120
The ISSU rollback timer is activated when the ISSU upgrade starts. By default, the ISSU rollback timer is 120 minutes.
1.12 Performing the ISSU Upgrade

ISSU shortens service interruption time and improves device reliability.
1.12.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 1.1 Description of ISSU check interactive messages Message Warning: The value of the ISSU rollback timer is 120 minutes. The system will begin the ISSU upgrade. Continue? [Y/N]: Description 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.
Issue 02 (2011-12-28)
33
3 ISSU Upgrade
Message Warning: The slave board will be rebooted and check the software compatibility. Continue? [Y/N]:
Description 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.
NOTE This 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.
<Quidway> 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]:y Info: 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]:y Info: 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.
Issue 02 (2011-12-28)
34
3 ISSU Upgrade
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).
1.12.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.
<S9300> display issu state -----------------------------------------------Phase State -----------------------------------------------1.ISSU check finished 2.ISSU start 3.ISSU switchover 4.ISSU confirm -----------------------------------------------The cancel ISSU command : issu abort.
To abort the ISSU upgrade, see 1.12.3(Optional) Running issu abort to Abort ISSU Upgrade. Table 1.1 Description of ISSU start interactive messages Message Info: The lossy ISSU process will start. Continue? [Y/N]: Description 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.
<Quidway> Info: The Info: The Info: The Info: The
issu start Lossy ISSU process will start. Continue? [Y/N]:y system will start lossy ISSU upgrade. system is copying the configuration file... operation of copying the configuration file is complete.
Issue 02 (2011-12-28)
35
3 ISSU Upgrade
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).
1.12.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 1.12.4Running issu switchover to Switch the Control Plane and 1.12.5Running issu confirm to Verify the ISSU Upgrade. If you choose to continue the ISSU upgrade, skip this step and go to section 1.12.4Running issu switchover to Switch the Control Plane.
Table 1.1 Description of ISSU abort interactive messages Message 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]: Description 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.
1.12.4 Running issu switchover to Switch the Control Plane

Run the display issu state command to check whether the ISSU status is Finished.
<S9300> display issu state -----------------------------------------------Phase State ------------------------------------------------
Issue 02 (2011-12-28)
36

1.ISSU check finished 2.ISSU start finished 3.ISSU switchover 4.ISSU confirm ------------------------------------------------
3 ISSU Upgrade
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:
<Quidway> issu switchover 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 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.

<Quidway> issu switchover Info: 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.
<Quidway> display issu switch-result check --------------------------------------------------------Slot Type Result --------------------------------------------------------1 new RTP unknown 1 old RTP unknown 2 old RTP unknown 2 new RTP unknown 3 old RTP unknown 3 new RTP unknown 8 old AMB success ---------------------------------------------------------
Issue 02 (2011-12-28)
37
3 ISSU Upgrade
1.12.5 Running issu confirm to Verify the ISSU Upgrade

Run the display issu state command to check whether the ISSU switchover status is Finished.
<S9300> display issu state -----------------------------------------------Phase State -----------------------------------------------1.ISSU check finished 2.ISSU start finished 3.ISSU switchover finished 4.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.
<Quidway> issu confirm Info: The slave MPU of the new version reboots. After the reboot is complete, the system automatically exits from ISSU.
1.13 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.
<Quidway> display startup MainBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup paf file: Next startup paf file: Startup license file: Next startup license file: Startup patch package: Next startup patch package: SlaveBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup paf file:
cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/vrpcfg.zip cfcard:/vrpcfg.zip default default default default NULL NULL
cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/vrpcfg.zip cfcard:/vrpcfg.zip default
Issue 02 (2011-12-28)
38

Next startup paf file: Startup license file: Next startup license file: Startup patch package: Next startup patch package: default default default NULL NULL
3 ISSU Upgrade
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.
<Quidway> display device S9306'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 NA 7 SRUA Present PowerOn Registered Normal Slave 8 SRUA Present PowerOn Registered Normal Master PWR1 Present PowerOn Registered Normal NA CMU1 CMUA Present PowerOn Registered Normal Master FAN1 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.

1.14.1 Rollback Scenarios and Methods
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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 39
Issue 02 (2011-12-28)
3 ISSU Upgrade
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 Upgrading the System Software Using the BootROM Menu.

Start
Specify the startup software
See 3.8.3
Restart the device
See 3.8.4
1.14.3 Specifying the Previous System Software for Next Startup

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:
<Quidway> startup system-software s9300v100r003c01.cc
Specify the previous system software for next startup on the slave MPU.
<Quidway> startup system-software s9300v100r003c01.cc slave-board
Check whether the system software and configuration file of the earlier version have been specified for next startup.
<Quidway> display startup MainBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file:
cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300V100R006C00SPC800.cc cfcard:/s9300v100r003c01.cc cfcard:/vrpcfg.zip
Issue 02 (2011-12-28)
40

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

Run the reboot command to restart the device. The system will then startup using the previous system software.
<Quidway> reboot Info: The system is now comparing the configuration, please wait. Warning: All the configuration will be saved to the configuration file for the n ext startup:cfcard:/vrpcfg.zip, Continue?[Y/N]:y System will reboot! Continue?[Y/N]:y

The procedure for verifying a version rollback is identical to the procedure for verifying an upgrade. For details, see section 1.13Verifying the ISSU Upgrade1.5.
Issue 02 (2011-12-28)
41
4 CSS Upgrade
CSS Upgrade
Table 1.1 Upgrade notes for versions Version S9300V100R003 version: S9300 V100R003C00 S9300 V100R003C00SPC200 S9300 V100R003C01 S9300 V100R003C01SPC100 S9300 V100R006C00SPC300 S9300 V100R006C00SPC500 Upgrade Note After 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 services Services are interrupted while the S9300s are restarting, and will be restored 10 minutes later. b. Impact on network communication The 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.
1.15.3 Impact on the System After the Upgrade

Issue 02 (2011-12-28)
42
4 CSS Upgrade
1.15.4 Precautions
No. 1 Description 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.
Issue 02 (2011-12-28)
43
4 CSS Upgrade
1.16 Upgrade Process Overview

Figure a.1 Upgrade flowchart
Start
See 4.3
Perform the CSS upgrade
See 4.4
Check if upgrade is successful Yes End
See 4.4.2
No
Roll back to an earlier version See 4.5
Table 1.1 Upgrade schedule Procedure Step Time Required (Minutes) 10 Remarks
1. 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. 1. Load the system software. 2. Restart the device. 1. Check whether configurations are lost. 2. Check whether boards start properly. 1. Specify the system software of an earlier version for next startup. 2. Restart the device.
Perform the upgrade Verify the upgrade Roll back to an earlier version
10 1 10
Issue 02 (2011-12-28)
44
4 CSS Upgrade


Quidway S9300 Product Documentation (V100R006C00_03) Quidway S9300 V100R006C00SPC800 Release Notes
1.17.2 Obtaining Tools


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.

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

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

1. Run the display version command in the user view to view the system software running on the devices. On device 1:
On device 2:
2. 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.
4 CSS Upgrade
On device 1:
<Quidway> display device S9306's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 G48TA Present PowerOn Registered Normal NA 4 X4UXC Present PowerOn Registered Normal NA 5 G48PA Present PowerOn Registered Normal NA 7 SRUA Present PowerOn Registered Normal Slave 8 SRUA Present PowerOn Registered Normal Master PWR1 Present PowerOn Registered Normal NA CMU1 CMUA Present PowerOn Registered Normal Master FAN1 Present PowerOn Registered Normal NA FAN2 Present PowerOn Registered Normal NA <Quidway>
On device 2:
<Quidway> display device S9306's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 G48TA Present PowerOn Registered Normal NA 4 X4UXC Present PowerOn Registered Normal NA 5 G48PA Present PowerOn Registered Normal NA 7 SRUB Present PowerOn Registered Normal Slave 8 SRUB Present PowerOn Registered Normal Master PWR1 Present PowerOn Registered Normal NA CMU1 CMUA Present PowerOn Registered Normal Master FAN1 Present PowerOn Registered Normal NA FAN2 Present PowerOn Registered Normal NA <Quidway>
----End
1.17.6 Setting Up the CSS Environment

The CSS requires the following software and hardware:
Software
The current software version must be S9300 V100R003C00 or a later version. Versions earlier than S9300 V100R003C00, including S9300 V100R001 and S9300 V100R002, do not support the CSS function.
Hardware

Two S9306s, two S9312s, or one S9306 and one S9312 Four SRUs Eight stack cables
Issue 02 (2011-12-28)
46
4 CSS Upgrade
Four stack cards
The S9303 does not support the CSS function. All the SRUs except LE02SRUA VA and LE02SRUB VA support the CSS function. LE02SRUA VA or LE02SRUB VA with a stack card will not start. 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.
Stack Cable Connection

1. Power off the two devices. Install a stack card on each SRU. Then connect the stack cables according to Figure a.1. Figure a.1 Stack cable connection (S9306)
If the cables are incorrectly connected, you need to adjust them. When removing a cable, push the cable gently with one hand, and then pull the handle of the cable with the other hand to remove it. 2. Power on the two devices and wait until the devices startup. 3. Connect the four serial interfaces on the master and slave SRUs of the two S9300s to the operation terminal.
4 CSS Upgrade
----End
1.17.7 Backing Up Data

Ensure that the key data stored on the CF card is backed up before upgrade. Key data includes the configuration file, license file, and system startup file of the current version. It is recommended that these files be transferred to a server or a host by TFTP or FTP. For details, see section 1.4.1Loading System Software.
1.18 Performing the CSS Upgrade

1.18.1 Loading System Software
This operation is not required if you only want to establish a CSS, and do not need to change the system software of the devices. That is, the current startup software and the software for next startup are already the target version.
The latest software s9300V100R006C00SPC800.cc must be loaded to the two devices in the CSS. For details, see section 1.4.1Loading System Software.
1.18.2 Specifying the System Software

The method used to specify system software depends on the device status.
Non-CSS State
If the two devices are in the non-CSS state before the upgrade, perform the following operation on the two devices:
<Quidway> startup system-software cfcard:/s9300V100R006C00SPC800.cc Info: Succeeded in setting the software for booting system.
Copy the system software package on the master SRU from it to the slave SRU.
<Quidway> copy cfcard:/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 <Quidway> startup system-software s9300V100R006C00SPC800.cc slave-board Info: Succeeded in setting the software for booting system
CSS State
If the two devices are in the CSS state, you can upgrade all four SRUs simultaneously using CSS. You have to copy the system software multiple times if use the copy command which is used on a single device. To simplify the operation, use the following command to copy the system software to all the SRUs at one time.
<Quidway> copy s9300V100R006C00SPC800.cc s9300V100R006C00SPC800.cc all
Issue 02 (2011-12-28)
48
4 CSS Upgrade
You can specify the startup software for all SRUs simultaneously by using the following command:
<Quidway> startup system-software s9300V100R006C00SPC800.cc all
1.18.3 Enabling the CSS Function

If the two devices are in the non-CSS state before the upgrade, perform the following operation on the two devices. Otherwise, you do not need to perform this operation. The CSS function only takes effect after the devices restart; therefore, enter y after you run the css enable command. 1. Set the frame ID of one device to 1 and enable CSS on the device.
[Quidway] set css id 1 Info: CSS config has been changed, need reboot to take effect. [Quidway] css enable Reboot needed to change CSS config. Are you sure this operation and reboot now? [Y/N]y
2. Set the frame ID of the other device to 2 and enable CSS on the device.
[Quidway] set css id 2 Info: CSS config has been changed, need reboot to take effect. [Quidway] css enable Reboot needed to change CSS config. Are you sure this operation and reboot now? [Y/N]y
----End
1.18.4 (Optional) Setting the Management Port Address

If the two devices are in the non-CSS state before the upgrade, perform the following operation on the two devices. Otherwise, you do not need to perform this operation. After the CSS function takes effect, the original management port address is lost; therefore, you cannot Telnet to the devices. Log in to the master SRU of the master switch through the serial port, and set the management port address on the master switch. This example assumes that the management port address is 10.10.10.10/24.
[Quidway] interface ethernet 0/0/0/0 [Quidway-Ethernet0/0/0/0] ip address 10.10.10.10 24
Display information about all devices in the CSS and find the master switch.
<Quidway> display device Chassis 1 (Master Switch) S9306's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 G48TA Present PowerOn Registered Normal NA 4 X4UXC Present PowerOn Registered Normal NA 5 G48PA Present PowerOn Registered Normal NA 7 SRUB Present PowerOn Registered Normal Slave 1 VSTSA Present PowerOn Registered Normal NA 8 SRUB Present PowerOn Registered Normal Master
Issue 02 (2011-12-28)
49

1 VSTSA CMUA Present Present Present PowerOn PowerOn PowerOn Registered Registered Registered Normal Normal Normal
4 CSS Upgrade
NA NA Master
PWR1 CMU1
Chassis 2 (Standby Switch) S9306's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 G48TA Present PowerOn Registered Normal NA 4 X4UXC Present PowerOn Registered Normal NA 5 G48PA Present PowerOn Registered Normal NA 7 SRUA Present PowerOn Registered Normal Slave 1 VSTSA Pre4sent PowerOn Registered Normal NA 8 SRUA Present PowerOn Registered Normal Master 1 VSTSA Present PowerOn Registered Normal NA PWR2 Present PowerOn Registered Normal NA CMU1 CMUA Present PowerOn Registered Normal Master FAN1 Present PowerOn Registered Normal NA FAN2 Present PowerOn Registered Normal NA
1.19 Verifying the CSS Upgrade

1.19.1 Verifying the Current System Software
After restarting the devices, check that the startup software of each SRU is correct.
<Quidway> display startup ====================================================================== 1: -------------------------------------------------------------------1/8 (system master board): 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 -------------------------------------------------------------------1/7 (slave board): 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
Issue 02 (2011-12-28)
50
4 CSS Upgrade
Next startup patch package: NULL ====================================================================== ====================================================================== 2: -------------------------------------------------------------------2/7 (system slave board): 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 -------------------------------------------------------------------2/8 (slave board): 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 ======================================================================
1.19.2 Verifying Board Software Version

After the CSS starts, run the check version command to check the software version of each LPU. All programs should be updated. If any program has not been upgraded, run the upgrade all { startup | filename } [ force ] command in the user view to upgrade them.
<Quidway> check version Frame/Slot Type Content CurVer ExactVer State Upgrade Suggest --------------------------------------------------------------------------------
1.19.3 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.
<Quidway> display device Chassis 1 (Master Switch) S9306's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 G48TA Present PowerOn Registered Normal NA
Issue 02 (2011-12-28)
51

4 5 7 8 PWR1 CMU1 1 1 X4UXC G48PA SRUB VSTSA SRUB VSTSA CMUA Present Present Present Present Present Present Present Present PowerOn PowerOn PowerOn PowerOn PowerOn PowerOn PowerOn PowerOn Registered Registered Registered Registered Registered Registered Registered Registered Normal Normal Normal Normal Normal Normal Normal Normal
4 CSS Upgrade
NA NA Slave NA Master NA NA Master
Chassis 2 (Standby Switch) S9306's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 G48TA Present PowerOn Registered Normal NA 4 X4UXC Present PowerOn Registered Normal NA 5 G48PA Present PowerOn Registered Normal NA 7 SRUA Present PowerOn Registered Normal Slave 1 VSTSA Pre4sent PowerOn Registered Normal NA 8 SRUA Present PowerOn Registered Normal Master 1 VSTSA Present PowerOn Registered Normal NA PWR2 Present PowerOn Registered Normal NA CMU1 CMUA Present PowerOn Registered Normal Master FAN1 Present PowerOn Registered Normal NA FAN2 Present PowerOn Registered Normal NA
1.19.4 Verifying Configuration Restoration

After the device restarts, run the display current-configuration command in any view to check the device configurations. Some configurations may be lost after the CSS is upgraded. Check for lost configurations by comparing the current configuration files with the saved configuration files.
After the CSS is set up, some configurations may be lost. If configurations are lost, run the appropriate commands to establish the original configurations. For an explanation of the differences between commands used on a single device and on a CSS, see the Quidway S9300 V100R006C00SPC800 Release Notes.

Use either of the following methods to check whether services are working normally after the upgrade:
Check whether any table entries are missing, for example, the entries of the routing table, FIB table, and MAC address table and 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.
Issue 02 (2011-12-28)
52
4 CSS Upgrade

Start
Roll back to an earlier version
See 4.6.2
1.20.2 Performing Version Rollback

Rolling Back System Software and Disabling CSS
1. Specify the configuration file used before the upgrade as the startup configuration file.
<Quidway> startup saved-configuration old.cfg chassis 1 <Quidway> startup saved-configuration old.cfg chassis 2
2. Specify the system software used before the upgrade as the startup software.
<Quidway> startup system-software s9300v100r003c01.cc all
3. Run the undo css enable command in the system view to disable the CSS function and restart the device.
<Quidway> system-view Enter system view, return user view with Ctrl+Z. [Quidway]undo css enable all Reboot needed to change CSS config. Are you sure this operation and reboot now? [Y/N]y
----End
Rolling Back System Software and Keeping CSS Enabled

4. Specify the system software used before the upgrade as the startup software.

<Quidway> startup system-software s9300v100r003c01.cc all
4 CSS Upgrade
5. Restart the devices.

<Quidway> reboot
----End

The procedure for verifying a version rollback is identical to the procedure for verifying an upgrade. For details, see section 1.5Verifying the Upgrade. After the rollback, the devices quit the CSS.
<Quidway>display css status Property Item Property Value Frame ID 1 Priority 1 Enable switch Off CSS master force Off CSS status unknown
Issue 02 (2011-12-28)
54
SPU Upgrade
SPU Upgrade
Table 1.1 Version requirements Type S9300 SPU Version S9300 V100R003C01, S9300 V100R006C00 VASP V100R002C00, VASP V100R003C00
Before you upgrade the system software from an earlier version to VASP V100R003C01, read this section carefully to understand the possible impact of the upgrade on the system.
Impact on Services
The S9300 needs to be restarted during the upgrade; therefore, services on the network will be interrupted for about 10 minutes.
Impact on Network Communication

The S9300 needs to be restarted during the upgrade; therefore, communication between the S9300 and the NMS will be interrupted for about 10 minutes.
Impact on the System After the Upgrade

None.
Issue 02 (2011-12-28)
55
SPU Upgrade
1.21.3 Precautions
Communication
Before the upgrade, ensure that network communication is normal and services are running normally.
Version Matching
The versions of the S9300 and the SPU must be the same. To upgrade VASP V100R003, log in to the SPU. Table 1.1 lists the matching versions of SPU and S9300. Table 1.1 Version matching S9300 V100R001/V100R002 (released) V100R003 (released) SPU S9300 V100R001 and V100R002 do not support SPU. V100R002 VASP V100R002 is released together with S9300 V100R003. V100R006 (released) V100R003 VASP V100R003 is released independently.
To upgrade S9300 V100R003 and VASP V100R002 to S9300 V100R006 and VASP V100R003, you have the following options: 1. (Recommended) Specify S9300 V100R006 as the next startup file for the S9300 and VASP V100R003 as the next startup file for the SPU. Restart the S9300. (When you restart the S9300, the SPU automatically restarts.) 2. Specify S9300 V100R006 as the next startup file for the S9300 and restart the S9300. When you restart the S9300, the SPU automatically restarts. After both the S9300 and SPU restart, log in to the SPU and upgrade the SPU to VASP V100R003.
If S9300 V100R003 and VASP V100R003 are used, the SPU automatically degrades its version to V100R002. During the degrade, services are interrupted. Services will be resumed after the degrade is complete. If S9300 V100R006 and VASP V100R002 are used, the SPU can start properly. You can log in to the SPU to upgrade it. During the upgrade, services are interrupted.
NMS
If you upgrade the SPU using the NMS, ensure that the NMS are configured correctly.
Upgrade Tool
Before the upgrade, prepare tools, such as the operation terminal, network cables, serial port cables, and TFTP or FTP software.
Issue 02 (2011-12-28)
56
SPU Upgrade
1.21.4 Upgrade Schedule

Table 1.1 Upgrade schedule Step Time Required (Minutes) 5 15 Remarks
Prepare for the upgrade Perform the upgrade
Prepare tools and software. 1. Back up files. 2. Load the system software. 3. Restart the device.
Verify the upgrade Roll back to an earlier version
1 10
1. Check whether configurations are lost. 2. Check whether boards start properly. 1. Specify the system software of an earlier version for next startup. 2. Restart the device.


Quidway S9300 Product Documentation Quidway S9300 V100R006C00SPC800 Release Notes Quidway S9300 V100R006C00SPC800 Upgrade Guide
1.22.2 Preparing Tools


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. This upgrade guide assumes that the customer has the software.

To obtain the required upgrade software, contact Huawei technical personnel or visit http://support.huawei.com.
Issue 02 (2011-12-28)
57
SPU Upgrade
Table 1.1 Version requirements Type S9300 SPU Version S9300 V100R006C00SPC800 VASP V100R003C00SPC500 VASP V100R003C10SPC500
Among the versions of SPU, only VASP V100R003C10SPC500 supports the IPSec function. C00 is used in the following description.
1.22.4 Checking Network Communication

During the upgrade, software packages need to be downloaded using the FTP or TFTP software. Therefore, check the IP address of Ethernet0/0/0 before the upgrade to ensure that the SPU communicates with the operation terminal properly. 1. Connect the SPU to the operation terminal with a serial cable. 2. Run the following commands in any view:
<SPU>display ip interface brief *down: administratively down !down: FIB overload down (l): loopback (s): spoofing The number of interfaces that is The number of interfaces that is The number of interfaces that is The number of interfaces that is Interface Ethernet0/0/0 NULL0
UP in Physical is 2 DOWN in Physical is 0 UP in Protocol is 2 DOWN in Protocol is 0 IP Address/Mask 10.137.144.191/24 unassigned Physical up up Protocol up up(s)
If an IP address is displayed following Ethernet0/0/0, Ethernet0/0/0 has an IP address. Ensure that the operation terminal can ping this IP address successfully. If no IP address is displayed, run the following command to configure one. The IP address and mask must meet the customer's requirement.
<SPU>system-view Enter system view, return user view with Ctrl+Z. [SPU]interface Ethernet0/0/0 [SPU-Ethernet0/0/0]ip address 10.137.137.5 24
----End
1.22.5 Connecting to the SPU Using a Network Cable

You can connect to an SPU in either of the following ways:
Connect a PC to the Ethernet port of the SPU using a network cable. Ping the SPU from the PC. If the ping is successful, communication with the SPU is normal. Connect a PC to Ethernet0/0/0 on the S9300's MPU using a network cable. Ping the SPU
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 58
Issue 02 (2011-12-28)
SPU Upgrade
from the PC. If the ping is successful, communication with the SPU is normal.

Check the current system software version and determine whether it needs to be upgraded. 1. Run the display version command in the user view of the SPU.
<SPU>display version Huawei Versatile Routing Platform Software VRP (R) software, Version 5.70 (VASP V100R003C00SPC300) Copyright (C) 2003-2011 HUAWEI TECH CO., LTD VASP Terabit Routing Switch uptime is 0 week, 0 day, 22 hours, 10 m inutes SPU 0: uptime is 0 week, 0 day, 22 hours, 9 minutes SDRAM Memory Size : 640 M bytes Flash Memory Size : 64 M bytes NVRAM Memory Size : 512 K bytes CF Card1 Memory Size : 496 M bytes SPU version information : 1. 2. 3. 4. 5. 6. PCB MAB Board CPLD1 BootROM BootLoad Version Version Type Version Version Version : : : : : : LE02VAMPA VER.B 0 VAMPA 102 106 104
If the field in bold is the same as the target version, upgrade is not required.
----End
1.22.7 Checking the SPU Registration Status

Check the registration status of the SPU: 1. Run the display device in the user view.
<SPU>display device S9300 SPU's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0 VAMPA Present PowerOn Registered Normal Master
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 running properly.
If a board fails to register or run properly, contact Huawei engineers. Ensure that all boards are running properly before the upgrade. ----End
Issue 02 (2011-12-28)
59
SPU Upgrade
1.22.8 Verifying the Running Status of the SPU

1. Run the display alarm all command in the user view. Ensure that the SPU is running properly.
<SPU> display alarm all --------------------------------------------------------------------Level Date Time Info Warning 2011-04-11 15:22:22
If alarms are displayed, contact Huawei engineers to confirm whether the system software can be upgraded. ----End
1.22.9 Setting Up the Upgrade Environment

As shown in Figure a.1, 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 of with a console cable. The FTP or TFTP server is connected to the SPU's Ethernet port with a network cable. The IP addresses of the server and the SPU's Ethernet port are in the same network segment. The system software is 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 SPU using a network cable.
Issue 02 (2011-12-28)
60
SPU Upgrade
Figure a.1 Network diagram for upgrading the system through TFTP or FTP
Network
RS-232 serial port Console Console cable PC SPU Ethernet port
Server
1.22.10 Checking the Space on the CF Cards

Before the upgrade, ensure that the CF card has sufficient space to store the upgrade software package. Do as follows to check the available space on the CF card: 1. Log in to the SPU and run the following command in the user view:
<SPU> dir cfcard:/ Directory of cfcard:/ Idx 0 1 2 3 Attr -rw-rw-rw-rwSize(Byte) Date Time FileName 22,064,779 Jan 01 1980 00:00:10 S9300v100r003c01.cc 198 Feb 24 2009 13:23:30 $_patchstate_a 2,955 Feb 15 2009 08:44:24 vrpcfg1.zip 4,495 Feb 15 2009 08:49:38 config.zip
506,744 KB total (484,671 KB free)
The available space (field in bold) must be larger than the size of the software package. If the available space is insufficient, delete unnecessary files to free up space by running the following commands: delete cfcard:/<file name> //Delete file to recycle bin reset recycle-bin cfcard:/ //Clear recycle bin
----End
Issue 02 (2011-12-28)
61
SPU Upgrade
1.22.11 Backing Up Files

Back up the key data stored in the CF card before the upgrade. After the upgrade, load the backup files. Table 1.1 Files need to be backed up File Type Configuration file System software File Name vrpcfg.zip S9300v100r003c01.cc Remarks Configuration file used for the current startup System software used for the current startup
The file names may vary according to the actual situation. This example assumes that the configuration file name is vrpcfg.zip and the system software package name is S9300v100r003c01.cc.
To back up files, you can use the SPU as an FTP server or FTP client.
1.22.12 Using SPU as FTP Server

This section assumes that the IP address of Ethernet0/0/0 on the SPU is 10.164.28.20, the FTP user name is vasp, the password is 123456, the FTP working directory is cfcard:/, the IP address of the PC is 10.164.28.21, and the backup directory is d:/ftp.
1. Log in to the SPU and configure it as the FTP server.

<SPU> system-view [SPU] ftp server enable Info: Succeeded in starting the FTP server. [SPU]aaa [SPU-aaa] local-user S9300 password simple 123456 [SPU-aaa] local-user S9300 ftp-directory cfcard:/ [SPU-aaa] local-user S9300 service-type ftp
2. Choose Start > Run on the PC and type cmd in the box. Figure a.1 cmd
Issue 02 (2011-12-28)
62
SPU Upgrade
3. Access D:\ftp>.
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Administrator>d: D:\ftp>
This section assumes that the ftp folder has been created and the software package has been saved in the folder.
4. Log in to the FTP server to back up files.

D:\ftp> ftp 10.164.28.20 Connected to 10.164.28.20. 220 FTP service ready. User(10.164.28.20:(none)): vasp # Enter the user name 331 Password required for user name. Password: # Enter 123456 and press Enter. The password is displayed in cipher text. 230 User logged in. ftp> binary 200 Type set to I. ftp> get <backup file> 200 Port command okay. 150 Opening binary mode data connection for <backup software>.cc 226 Transfer complete. ftp: 40254 bytes received in 52 Seconds 40254 Kbytes/sec. ftp> get vrpcfg.zip 200 Port command okay. 150 Opening binary mode data connection vrpcfg.zip 226 Transfer complete. FTP: 143694 byte(s) received in 0.897 second(s) 160.19Kbyte(s)/sec.
5. Search for the backup files in D:\ftp to check whether the files are backed up successfully. ----End
1.22.13 Using SPU as FTP Client

Connect and configure the operation terminal (serial port terminal or Telnet client) of the SPU.
For details on how to configure a PC as the FTP server, see the instruction of the FTP software. This section only provides an example. The actual operation may vary according to the FTP software.
1. Configure the FTP server program on the PC.
Issue 02 (2011-12-28)
63
SPU Upgrade
Figure a.1 FTP software
2. Choose Security > Users /rights in Figure a.1 to display the following dialog box.
Click New User to set the user name and password. Here, the user name is VASP and the password is 123456. Enter the FTP working directory in the Home Director text box. Here, the working directory is D:\ftp. Do not stop the FTP server program during backup. 3. Back up the system software and configuration file. The FTP commands on the SPU are the same as the FTP commands in the DOS system. In this example, the IP address of the FTP server is 10.164.28.20, the FTP user name is vasp, and the password of the FTP user is 123456. The IP address of the PC is 10.164.28.21.
<SPU> cd cfcard: <SPU> ftp 10.164.30.21 Trying 10.164.30.21 ... Press CTRL+K to abort Connected to 10.164.30.21. 220220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user User(100.1.1.4:(none)):VASP # Enter the user name and press Enter. 331 Give me your password, please
Issue 02 (2011-12-28)
64
SPU Upgrade
Enter password: # Enter 123456 and press Enter. The password is displayed in cipher text. 230 Logged in successfully 230 Logged in successfully [ftp] binary 200 Type is Image (Binary) [ftp] put <Software package name> <backup software package name> 200 PORT command okay 150 "D:\FTP\<backup software package name>.cc" file ready to receive in Binary mode 226 Transfer finished successfully. FTP: 40521 byte(s) sent in 0.176 second(s) 22.04Kbyte(s)/sec.
4. Back up the configuration file.

[ftp] put vrpcfg.zip vrpcfg-bak.zip 200 PORT command okay 150 "D:\FTP\vrpcfg-bak.zip" file ready to receive in Binary mode 226 Transfer finished successfully. FTP: 1024 byte(s) sent in 0.176 second(s) 22.04Kbyte(s)/sec.
5. Log in to the FTP server (PC) to check whether the files are backed up successfully. ----End
1.23 Upgrade Operations

The following sections provide four methods to upgrade the SPU system software. Select a method according to the actual situation.
1.23.1 Method 1: Loading the System Software Through TFTP

Before the upgrade, configure the TFTP program. The operation procedure is not provided here. Ensure that the upgrade software package has been saved in the specified directory on the FTP server.
1. Connect and configure the operation terminal (serial port terminal or Telnet client) of the SPU. The TFTP32 program is recommended. 2. Configure the TFTP server. Run the TFTP server on the PC and configure the TFTP server. Click Browse and set Current Directory to the directory of the backup file. Set Server Interface to the IP address of the TFTP server, for example, 10.164.30.29. The IP address of the server interface is usually displayed automatically.
Issue 02 (2011-12-28)
65
SPU Upgrade
Figure a.1 TFTP program
Do not interrupt the TFTP program when you are transferring files. 3. Find the upgrade software package in d:\tftpd32i on the FTP server. 4. Log in to the SPU and download the system software and configuration file from the TFTP server.
<SPU> tftp 10.164.30.29 get <software package name> Info: Transfer file in binary mode. Downloading the file from the remote TFTP server. Please wait.../ TFTP: Downloading the file successfully.45021 bytes received in 93 seconds.
If the message "Downloading the file successfully" is displayed, the system software has been downloaded. ----End
1.23.2 Method 2: Loading the System Software Using the SPU as the FTP Server
1. Configure the operation terminal. Connect and configure the operation terminal (serial port terminal or Telnet client) of the SPU. If the FTP client can ping the IP address of Ethernet0/0/0 on the SPU, the connection between the FTP client and the SPU is normal. If the FTP client is connected to a network interface of an LPU, the FTP client should be able to ping the IP address of the network interface. If the ping fails, check the network connectivity. 2. Configure the SPU as the FTP server.

<SPU> system-view [SPU] ftp server enable Info: Succeeded in starting the FTP server. [SPU]aaa [SPU-aaa] local-user vasp password simple 123456 [SPU-aaa] local-user vasp ftp-directory cfcard:/ [SPU-aaa] local-user vasp service-type ftp
SPU Upgrade
3. Choose Start > Run on the PC and type cmd in the box. Figure a.1 cmd
4. Access D:\ftp>.
Microsoft Windows XP [version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Administrator>d: D:\> ftp
This section assumes that the ftp folder has been created and the software package has been saved in the folder.
5. Upload the software package to the SPU from the FTP client.
Access the FTP working directory on the PC. In this example, the FTP working directory is D:\ftp, the IP address of the FTP server (SPU) is 10.164.28.20, the FTP user name is vasp, and the password of the FTP user is 123456.
D:\ftp> ftp 10.164.28.20 Connected to 10.164.28.20. 220 FTP service ready. User(10.164.28.20:(none)):vasp # Enter the user name and press Enter. 331 Password required for user name. Password: # Enter 123456 and press Enter. The password is displayed in cipher text. 230 User logged in. ftp> binary 200 Type is I ftp> put <software package name> 200 Port command okay. 150 Opening Binary mode data connection for <software package name> 226 Transfer complete.
Issue 02 (2011-12-28)
67

ftp: 45021 sent in 52 Seconds 45021 Kbytes/sec.
SPU Upgrade
----End
1.23.3 Method 3: Loading the System Software Through the S9300's MPU
You can load the system software to the S9300's MPU, and then load the system software from the MPU to the SPU. You must familiarize yourself with the S9300 system before using this method. This method can be used when you cannot log in to the SPU through Telnet. 1. Save the system software package to the CF card on the S9300's MPU. 2. Log in to the MPU through Telnet and check that the SPU has registered successfully.
<S9300>display device S9312's Device status: Slot Sub Type Online Power Register - - - - - - - - - - - - - - - - - - - - - - 6 VAMPA Present PowerOn Registered 11 G48TD Present PowerOn Registered 14 SRUA Present PowerOn Registered
Alarm Primary - - - - - - - - Normal NA Normal NA Normal Master
In this example, the SPU is installed in slot 6.
3. Configure the S9300 as the FTP server. Set the FTP user name to S9300, the password to 123456, and the FTP working directory to cfcard:/.
<S9300> system-view [S9300] ftp server enable Info: Succeeded in starting the FTP server. [S9300]aaa [S9300-aaa] local-user S9300 password simple 123456 [S9300-aaa] local-user S9300 ftp-directory cfcard:/ [S9300-aaa] local-user S9300 service-type ftp
4. Create a VLANIF interface on the MPU. VLAN 60 used in the following example is a VLAN that has not been created before. Change the VLAN according to the actual situation.
<S9300>system-view [S9300]vlan 60 [S9300-vlan60]quit [S9300]interface Vlanif 60 [S9300-Vlanif60]ip address 60.1.1.1 24 [S9300-Vlanif60]quit [S9300]interface XGigabitEthernet 6/0/0 [S9300-XGigabitEthernet6/0/0]port link-type trunk [S9300-XGigabitEthernet6/0/0]port trunk allow-pass vlan 60 [S9300-XGigabitEthernet6/0/0]quit
5. Log in to the SPU from the MPU and add the interface on the SPU to the VLAN.
<S9300>spu connect slot 6
Issue 02 (2011-12-28)
68

****************************************************** * Slot 6 output to mainboard * ****************************************************** Press Ctrl+D to quit
SPU Upgrade
Press Enter to access the serial port of the SPU. Add the interface on the SPU to the VLAN.
[SPU]interface XGigabitEthernet 0/0/1.60 [SPU-XGigabitEthernet0/0/1.60]ip address 60.1.1.2 24 [SPU-XGigabitEthernet0/0/1.60]control-vid 60 dot1q-termination [SPU-XGigabitEthernet0/0/1.60]dot1q termination vid 60 [SPU-XGigabitEthernet0/0/1.60]arp broadcast enable [SPU-XGigabitEthernet0/0/1.60]quit
If the SPU version is V100R003 and service type is WLAN, perform the following configurations:
[SPU]display service-type Current board service type is :WLAN. # Set the service type to WLAN Next startup board service type is :WLAN. [SPU]vlan 60 [SPU-vlan60]quit [SPU]interface Vlanif 60 [SPU-Vlanif60]ip address 60.1.1.2 24 [SPU]interface XGigabitEthernet 0/0/1 [SPU-XGigabitEthernet0/0/1]port link-type trunk [SPU-XGigabitEthernet0/0/1]port trunk allow-pass vlan 60 [SPU-XGigabitEthernet0/0/1]quit
6. Load the system software from the MPU.

<SPU>cd cfcard: <SPU>ftp 60.1.1.1 Trying 60.1.1.1 Press CTRL+K to abort Connected to 60.1.1.1. 220 FTP service ready. User(60.1.1.1:(none)):S9300 331 Password required for vasp. Enter password: 230 User logged in. [ftp] binary 200 Type is Image (Binary) [ftp] get <Software package name> 200 Port command okay. 150 Opening Binary mode data connection for <Software package name> 226 Transfer finished successfully. FTP: 143694 byte(s) received in 0.897 second(s) 160.19Kbyte(s)/sec.
The preceding information indicates that the file has been transferred successfully and you can find the file in D:\ftp. 7. Close the FTP connection.
[ftp] bye 221 Windows FTP Server (WFTPD, by Texas Imperial Software) says goodbye
Issue 02 (2011-12-28)
69
SPU Upgrade
----End
1.23.4 Method 4: Loading the System Software Using the Escape Channel
This method is used only when the SPU fails to start. This method applies to S9300 V100R006 or a later version. S9300 V100R001, V100R002, and V100R003 do not support this method. Load the SPU upgrade software to the S9300's MPU, and then specify the startup system software for the SPU. 1. Check the current S9300 software version. The version must be V100R006 or a later version.
<S9300>display version Huawei Versatile Routing Platform Software VRP (R) software, Version 5.70 (S9300 V100R006C00SPC800) 006C Copyright (C) 2003-2011 HUAWEI TECH CO., LTD Quidway S9306 Terabit Routing Switch uptime is 0 week, 0 day, 0 hour, 31 minutes BKP 0 version information: 1. PCB Version : LE01BAKH VER.A 2. Support PoE : No 3. Board Type : BAKH 4. MPU Slot Quantity : 2 5. LPU Slot Quantity : 6 MPU 7(Master) : uptime is 0 week, 0 day, 0 hour, 30 minutes SDRAM Memory Size : bytes Flash Memory Size : bytes NVRAM Memory Size : 512 K bytes CF Card1 Memory Size : bytes MPU version information : 1. PCB Version : LE02SRUA VER.A 2. MAB Version : 1 3. Board Type : SRUA 4. CPLD1 Version : 101 5. BootROM Version : 3 6. BootLoad Version : 102 LPU 1 : uptime is 0 week, 0 day, 0 hour, 23 minutes SDRAM Memory Size : bytes Flash Memory Size : bytes LPU version information : 1. PCB Version : LE48V VER.B 2. MAB Version : 0 3. Board Type : G48TA 4. BootROM Version : 131 5. BootLoad Version : 141
512 64 977
M M M
256 16
M M 02G
Issue 02 (2011-12-28)
70

LPU 4 : uptime is 0 week, 0 day, 0 hour, 22 minutes SDRAM Memory Size : bytes Flash Memory Size : bytes LPU version information : 1. PCB Version : LE02VAMPA VER.B 2. MAB Version : 0 3. Board Type : VAMPA 4. CPLD1 Version : 102 5. BootROM Version : 131 6. BootLoad Version : 104 Tcam version information : 1. Tcam size : bits M CMU 9(Master) : uptime is 0 week, 0 day, 0 hour, 29 minutes CMU version information : 1. PCB Version : LE02CMUA VER.A 2. MAB Version : 0 3. Board Type : CMUA <S9300>
SPU Upgrade
640 64
M M
18
2. Save the SPU's system software package to the CF card of the S9300's MPU.
In this example, the SPU's system software package is VASP_V100R003.cc.
<S9300>dir Directory of cfcard:/ Idx 0 1 2 3 4 5 Attr -rwdrw-rw-rw-rw-rwSize(Byte) 13,800 2,148 280 23,849,161 51,293,568 Date Jan 13 Apr 14 Apr 08 Jan 13 Feb 25 Mar 13 Time(LMT) 11:36:20 14:53:56 09:31:30 11:36:22 00:14:40 17:22:50 FileName $_patchstate_a logfile vrpcfg.zip $_patch_rollback_state VASP_V100R003.cc S9300V100R006.cc
2010 2011 2011 2010 2011 2011
1,000,672 KB total (187,680 KB free)
3. Check the slot ID of the SPU.

Run the display device command to find the SPU's slot ID. If the Type field of a board is VAMPA, the board is the SPU.
As shown in the following command output, the SPU is in slot 4.

<S9300>display device S9306's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 G48TA Present PowerOn Registered NA 4 VAMPA Present PowerOn Registered NA 7 SRUA Present PowerOn Registered Normal Master PWR1 Present PowerOn Registered NA CMU1 CMUA Present PowerOn Registered Normal Master FAN1 Present PowerOn Registered NA
Normal Normal Normal Normal
Issue 02 (2011-12-28)
71

FAN2 Present PowerOn Registered NANormal
SPU Upgrade
4. Specify the startup system software package for the SPU.

<S9300>spu-startup system-software cfcard:/ VASP_V100R003.cc slot 4 Info: Succeeded in setting the spu-software for booting system.
In this example, the SPU is in slot 4. If you have multiple SPUs to upgrade on an S9300, run the following command:
<S9300>spu-startup system-software cfcard:/ VASP_V100R003.cc all Info: Succeeded in setting the spu-software for booting system.
5. Reset the SPU.
The reset command can restart any board on the S9300. Verify the slot ID of the SPU to be upgraded. Resetting an incorrect board will interrupt services. In this example, the SPU's slot ID is 4. Enter the actual SPU's slot ID when running the reset command.
<S9300>reset slot 4 Caution!!! Confirm to reset slot 4 ? [Y/N]:y INFO: The board[4] reset success!
Enter Y to reset the SPU in slot 4. 6. After the SPU completes resetting, verify the SPU information.
<S9300>display spu-information 1/4 SPU version information : V100R003C00 Current board service type: WLAN Next startup board service type: WLAN Startup system software: cfcard:/ VASP_V100R003.cc Next startup system software: cfcard:/ VASP_V100R003.cc Startup saved-configuration file: cfcard:/vrpcfg.cfg Next startup saved-configuration file: cfcard:/vrpcfg.cfg
7. Run the display sup-startup command to check whether the startup system software is that specified in step 4. If so, run the undo spu-startup command to cancel it. If the specified startup system software is not canceled, the SPU always start with this system software even if the SPU is upgraded again.
<S9300>display spu-startup [1/4] Spu-Startup system software: cfcard:/VASP_V100R003.cc <S9300>undo spu-startup
----End
Issue 02 (2011-12-28)
72
SPU Upgrade
1.23.5 Method 5: Loading the Upgrade Program Through the BootROM Menu
This method is not recommended because the upgrade procedure is complicated. Use this method only when the SPU cannot start. The S9300's MPU version and the SPU version must match; otherwise, the SPU cannot start.
The version rollback operation using BootROM menu is similar to the upgrade operation using BootROM menu. The SPU target version must match the S9300 version.
To upgrade the system software using the BootROM menu, you must configure the SPU as the FTP client and connect the operation terminal to the SPU through the serial port. The operation terminal communicates with the SPU through the HyperTerminal. 1. Run the FTP program on the operation terminal or PC and specify the path of the system software. Create the FTP user vasp and set the password of the FTP user to 123456. 2. Restart the S9300. When the S9300 is powered on, the computer or operation terminal connected to the S9300 displays the following information:
**************************************************** * * * Ethernet Switch Bootload, Ver 104 * * * **************************************************** Copyright(C) 2003-2011 by HUAWEI TECHNOLOGIES CO., LTD. Creation date: Apr 29 2011, 16:43:31 PCB Version CPU L2 Cache CPU Clock Speed BUS Clock Speed Memory Type Memory Size Memory Speed : : : : : : : LE02MCUA VER.B 128KB 700MHz 133MHz DDR2 SDRAM 640MB 667MHz
CF Card Init...............................................................Done Press Ctrl+B to enter Boot Menu... 3
3. Press Ctrl+B within 3 seconds.

password:
The initial password is 9300 or 7800, and you can change the password. If three wrong passwords are entered consecutively, the system restarts.
When the correct password is entered, the following BootROM menu is displayed:
MAIN MENU 1. Boot with default mode 2. Boot from Flash # Restart the system in default mode. # Restart the system through the Flash
Issue 02 (2011-12-28)
73

memory. 3. Boot from CFCard 4. Enter serial submenu 5. Enter ethernet submenu interface. 6. Modify Flash description area memory. 7. Modify bootrom password 8. Reboot Enter your choice(1-8): _
SPU Upgrade
# Restart the system through the CF card. # Enter the submenu of the serial port. # Enter the submenu of the Ethernet # Modify the description of the Flash # Change the password of the BootROM menu. # Restart the system.
4. Enter 5 to display the submenu of the Ethernet interface.

ETHERNET 1. 2. 3. 4. 5. SUBMENU
Download file to SDRAM through ethernet interface and boot Download file to Flash through ethernet interface Download file to CFCard through ethernet interface Modify ethernet interface parameter Return to main menu
Be sure to modify parameter before downloading! Enter your choice(1-5):
5. Enter 4 to set the parameters of the Ethernet interface.

Note: Two protocols for download, tftp & ftp. You can modify the flags following the menu. tftp--0x80, ftp--0x0. '.' = clear field; '-' = go to previous field; ^D = quit
boot device : eth1 processor number : 0 host name : host file name : vaspv100r003c00.cc # Name of the system software to be loaded inet on ethernet (e) : 192.168.1.1:ffffff00 inet on backplane (b): 192.168.1.1 host inet (h) : 192.168.1.2 # IP address of the FTP server gateway inet (g) : user (u) : vasp # FTP user name ftp password (pw) (blank = use rsh): 123456 # FTP login password flags (f) : 0x0 target name (tn) : octeon startup script (s) : other (o) :
Here, the name of the system software to be loaded is vaspv100r003c00.cc, the IP address of the FTP server is 192.168.1.2, the FTP user name is vasp, and the password of the FTP user is 123456. Set these parameters according to the actual situation. You do not need to change the values of the other parameters. 6. Enter 3 to download the system software to the CF card.
Issue 02 (2011-12-28)
74
SPU Upgrade
boot device : unit number : processor number : host name : file name : inet on ethernet (e) : inet on backplane (b): host inet (h) : gateway inet (g) : user (u) : ftp password (pw) : flags (f) : target name (tn) :
eth1 1 0 host vaspv100r003c00.cc 192.168.1.1:ffffff00 192.168.1.1 192.168.1.2 vasp 123456 0x0 octeon
Loading...................................Done! Please type a new file name for saving it. Press return key to save it named " vaspv100r003c00.cc". Check disk space Writing file.............................................................................. ..............................Done
7. Enter 5 to return to the main menu.

Be sure to modify parameter before downloading! Enter your choice(1-5): Enter 6 to configure the loaded system software as the startup program. MAIN MENU 1. Boot with default mode # Restart the system in default mode. 2. Boot from Flash # Restart the system through the Flash memory. 3. Boot from CFCard # Restart the system through the CF card. 4. Enter serial submenu # Enter the submenu of the serial port. 5. Enter ethernet submenu # Enter the submenu of the Ethernet interface. 6. Modify Flash description area # Modify the description of the Flash memory. 7. Modify bootrom password # Change the password of the BootROM menu. 8. Reboot # Restart the system. Enter your choice(1-8): Modify flash description area Please select booting device. Press ENTER directly for no change or input your choice.
Issue 02 (2011-12-28)
75

1: Flash, 2: CF Card Current booting device: 2, your choice: 2 the CF card.
SPU Upgrade
# Start the system through
Current booting File Name: cfcard:/ vaspv100r003c00.cc, Press ENTER directly for no change. Or, please input the file name (e.g. vaspv100r003c00.cc): vaspv100r003c00.cc Enter the name of the upgrade program.
The expected booting file: cfcard:/ vaspv100r003c00.cc. Are you sure? Yes or No(Y/N)y # Enter y to confirm the change of the startup program. Writing descriptor to flash...OK! Writing backup descriptor to flash...OK!
8. Select 8 to restart the SPU. ----End
1.23.6 Checking the Loaded System Software and Starting It

Run the dir command to check whether the loaded file exists and whether the size of the file is the same as the size of the file on the server. 1. Log in to the SPU and run the following command in the user view:
<SPU> dir Directory of cfcard:/ Idx Attr Size(Byte) Date Time FileName -rw22,064,779 Mar 26 2009 12:33:14 vaspv100r003.cc 1 -rw2,955 Feb 15 2009 08:44:24 vrpcfg1.zip 2 -rw40,886 Feb 24 2009 13:19:42 c02b118sph001.pat 3 -rw26,144,280 Mar 23 2009 13:54:12 vaspv100r003c00.cc
506,744 KB total (463,528 KB free)
2. Configure the loaded system software as the next startup software.

<SPU> startup system-software <new software package name>
Check the next startup system software. If the next startup system software is the loaded system software, the upgrade program has been loaded successfully.
<SPU> display startup MainBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup patch package: Next startup patch package:
cfcard:/vaspv100r003.cc cfcard:/vaspv100r003.cc cfcard:/ <new software package name> cfcard:/vrpcfg.zip cfcard:/vrpcfg.zip cfcard:/c02sph001.pat cfcard:/c02sph001.pat
Issue 02 (2011-12-28)
76
SPU Upgrade
If VASP V100R002 is upgraded to VASP V100R003, the total length of the version file name and drive name cannot be longer than 48 characters; otherwise, the SPU cannot start after the upgrade. For example, cfcard:/vaspv100r003.cc contains 23 characters.
<SPU>save The current configuration will be written to the device. Are you sure to continue?[Y/N]y Now saving the current configuration to the slot 13. Save the configuration successfully.
3. Log in to the MPU and perform the operations in steps 1 and 2 to determine whether the MPU and SPU versions match.
VASP V100R003 matches S9300 V100R006. After the SPU is upgraded to VASP V100R003, the system software for next startup is VASP V100R003. Therefore, the system software for next startup on the S9300 must be S9300 V100R006. If the versions do not match, the SPU cannot start. 4. Restart the SPU.
If the versions match, you do not need to restart the MPU.
Log in to the SPU to restart it.

<SPU>reboot Info: The system is now comparing the configuration, please wait. Warning: All the configuration will be saved to the configuration file for the n ext startup:cfcard:/vrpcfg.zip, Continue?[Y/N]:y Now saving the current configuration to the slot 13 . Info: Save the configuration successfully. System will reboot! Continue?[Y/N]:y Info: system is rebooting,please wait...
Enter y to restart the SPU.

If the versions do not match, specify the matched system software for next startup on the S9300.
Restart the MPU. The SPU will restart automatically.

<S9300>reboot Info: The system is now comparing the configuration, please wait. Warning: All the configuration will be saved to the configuration file for the n ext startup:cfcard:/vrpcfg.zip, Continue?[Y/N]:y Now saving the current configuration to the slot 7 . Info: Save the configuration successfully. System will reboot! Continue?[Y/N]:y Warning: The SPU will be reset and configurations that have not been saved will be lost. Continue?[Y/N]:y Info: system is rebooting,please wait...
Issue 02 (2011-12-28)
77
SPU Upgrade
Enter y to restart the MPU. ----End
1.23.7 Verifying the Upgrade

1. After the SPU restarts, log in to the SPU to check whether the startup program is in the new version.
<SPU> display startup MainBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup patch package: Next startup patch package:
cfcard:/vaspv100r003c00.cc cfcard:/vaspv100r003c00.cc cfcard:/vaspv100r003c00.cc cfcard:/vrpcfg.zip cfcard:/vrpcfg.zip cfcard:/NULL cfcard:/NULL
2. Run the display device command in any view to check the registration status of the boards. The boards should be in Normal state.
<SPU>display device S9300 SPU's Device status: Slot Sub Type Online Power Register Alarm Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13 VAMPA Present PowerOn Registered Normal Master
3. Run the display version command in any view to check whether the SPU uses the new version.
<SPU>dis version Huawei Versatile Routing Platform Software VRP (R) software, Version 5.70 (VASP V100R003C00SPC500) Copyright (C) 2003-2011 HUAWEI TECH CO., LTD VASP SPU uptime is 0 week, 0 day, 1 hour, 33 minutes SPU 0 : uptime is 0 week, 0 day, SDRAM Memory Size : 640 M Flash Memory Size : 64 M NVRAM Memory Size : 512 K CF Card1 Memory Size : 486 M SPU version information : 1. PCB Version : LE02VAMPA 2. MAB Version : 0 3. Board Type : VAMPA 4. CPLD1 Version : 102 5. BootROM Version : 106 6. BootLoad Version : 104 1 hour, 31 minutes bytes bytes bytes bytes VER.B
4. Check whether all configurations are restored. After the device restarts, run the display current-configuration command in any view to check the configuration of the SPU. 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.
Issue 02 (2011-12-28)
78
SPU Upgrade
If no configuration data is lost, the following information is displayed:

<SPU> compare configuration Info:The current configuration is the SAME as the saved configuration!
If any configuration data is lost, the following information is displayed:

<SPU> compare configuration Warning: The current configuration is not the same as the saved configuration. ====== Current configuration line 21 ====== arp anti-attack check user-bind alarm threshold 80 dhcp snooping enable dhcp snooping user-bind autosave cfcard:/hh.tbl ====== Saved configuration line 21 ====== dhcp snooping enable # igmp-snooping enable # efm enable # assign resource-mode 1 slot 1 assign resource-mode 1 slot 2
----End

Use either of the following methods to verify services after the upgrade:
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 all services are working properly.
1.24 Version Rollback

1.24.1 Rolling Back to an Earlier Version
This example assumes that the versions are rolled back to VASP V100R002 and S9300 V100R003.
Load the system software S9300V100R003.CC to the SPU using the method in 1.23.1, 1.23.2, or 1.23.3. Ensure that the S9300V100R003.CC file also exists on the S9300's MPU.
1. Log in to the S9300 and specify s9300v100r003.cc for next startup.

< S9300> startup system-software S9300V100R003.CC
2. Check whether the system software for next startup is s9300v100r003.cc.

<S9300> display startup MainBoard:
Issue 02 (2011-12-28)
79

Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup patch package: Next startup patch package:
SPU Upgrade
cfcard:/S9300v100r006c00.cc cfcard:/S9300v100r006c00.cc cfcard:/S9300V100R003.cc cfcard:/vrpcfg.zip cfcard:/vrpcfg.zip cfcard:/sph001.pat cfcard:/sph001.pat
3. Restart the S9300. The SPU will restart automatically with the vaspv100r002.cc file.
<S9300> reboot Info: The system is now comparing the configuration, please wait. Warning: Current configuration will be saved to the next startup saved-configura tion file: cfcard:/vrpcfg.zip!Continue?[Y/N]: y/n System will reboot! Continue?[Y/N]:y
To roll back the version to an earlier C version of VASP V100R003 enter y. Then the system restarts. To roll back to VASP V100R001 or V100R002, it is recommended that you enter n. Then the system restarts without saving configuration.
After the versions are rolled back to S9300V100R003&VASPV100R002, the S9300 also saves the configurations of SPU when saving its own configurations. However, after the versions are rolled back to S9300V100R006&VASPV100R003, the S9300 does not save the configurations of SPU, and you must save them manually. ----End

The procedure for verifying a version rollback is identical to the procedure for verifying an upgrade. For details, see section 1.23.7Verifying the Upgrade.
Issue 02 (2011-12-28)
80
Upgrading the System Software Using the BootROM Menu

This section describes how to upgrade the system software using the BootROM menu when the system software fails to start.
Background Information
This method is not recommended because the upgrade procedure is complicated. Only use this method when the system software will not start. To upgrade the system software using the BootROM menu, you must configure the S9300 as the FTP client and connect the operation terminal to the S9300 through the serial port. The operation terminal communicates with the S9300 through HyperTerminal. The operation terminal, which functions as the FTP server, must be directly connected to the management interface of the S9300, or communicate with the management interface in the same network segment. This section describes the S9312 upgrade process. You can upgrade the S9303 and the S9306 in the same way.
Procedure
1. Run the FTP program on the operation terminal or PC and specify the path of the system software. Create the FTP user 9300 and set the password of the FTP user to 123456.
The IP address of the configuration terminal or PC (IP address of the FTP server) and the IP address of the S9300's management interface must be on the same network segment.
2. Restart the S9312. When the S9312 is powered on, the operation terminal displays the following information:
Input Ctrl + y to Select Debug Console: Bootrom Version ......................................................... Ver B L2 Cache Test Start..........................................................OK BIOS Creation Date ...................................... May 11 2011, 12:01:57
Issue 02 (2011-12-28)
81
BoardType is...........................................................00000008 Bootbus init.................................................................OK DDR DRAM init................................................................OK Start Memory Test ? ('t' or 'T' is test):skip Copying Uncompressed Data from Rom to Ram .................................Done Uncompressing Data from Rom to RAM ........................................Done Initializing Flash Module .......................................Done Starting...
The S9312 starts the basic BootROM menu, and then checks the extended BootROM menu. The following is the extended BootROM menu:
**************************************************** * * * Ethernet Switch Bootload, Ver 121 * * * **************************************************** Copyright(C) 2003-2011 by HUAWEI TECHNOLOGIES CO., LTD. Creation date: May 4 2011, 13:35:26 PCB Version CPU L2 Cache CPU Clock Speed BUS Clock Speed Memory Type Memory Size Memory Speed : : : : : : : LE02SRUB VER.B 128KB 700MHz 133MHz DDR2 SDRAM 1024MB 667MHz
CF Card Init...............................................................Done Press Ctrl+B to enter Boot Menu... 1
If an error occurs during the BootROM upgrade, the system displays the basic BootROM menu. In this case, abort the upgrade and contact Huawei technical personnel. The following is the basic BootROM menu:
Update BIOS menu(ver004) Creation date: Feb 2 2009 14:48:04 1. Update base BIOS through serial interface 2. Update extend BIOS through serial interface 3. Modify serial interface parameter 4. Boot extend BOIS system 5. Reboot Enter your choice(1-5):
3. Press Ctrl+B within 1 seconds.

password:
4. Enter the extended BootROM password to display the main BootROM menu.
Issue 02 (2011-12-28)
82
The initial password is 9300 or 7800. You can set the password. If three wrong passwords are entered consecutively, the system restarts.
When the correct password is entered, the following BootROM menu is displayed:
MAIN MENU 1. Boot with default mode # The system starts by using the default booting device and startup software specified in option 6. You do not need to configure the basic BootROM or extended BootROM. 2. Boot from Flash # The system starts by using the default system software in the flash memory. You do not need to configure the basic BootROM or extended BootROM. The default system software is specified in option 6. If you load the system software to the flash memory by selecting option 5, the loaded system software will be used as the new startup software. 3. Boot from CFCard # The system starts by using the default system software in the CF card. You do not need to configure the basic BootROM or extended BootROM. The default system software is specified in option 6. If you load the system software to the CF card by selecting option 5, the loaded system software will be used as the new startup software. 4. Enter serial submenu # In the serial submenu, you can download files through the serial interface or modify the serial interface parameters. 5. Enter ethernet submenu # In the Ethernet submenu, you can download files through the Ethernet interface or modify the Ethernet interface parameters. 6. Modify Flash description area # You can change the default booting device (flash memory or CF card) and the default startup software. 7. Modify bootrom password # You can change the password of the BootROM menu. 8. Reboot # The system starts by using the default booting device and system software specified in option 6. You need to configure the basic BootROM and extended BootROM.
Enter your choice(1-8): _
When the system restarts, it automatically uses the default booting device and system software set in option 6 even if you have specified the startup mode of option 1, 2, or 3. After you load the system software using option 5, you are advised to specify the default booting device and system software in option 6, and then select option 8 to restart the system.
5. Enter 5 to enter the Ethernet submenu.

ETHERNET 1. 2. 3. 4. SUBMENU
Download file to SDRAM through ethernet interface and boot Download file to Flash through ethernet interface Download file to CFCard through ethernet interface Modify ethernet interface parameter
Issue 02 (2011-12-28)
83

5. Return to main menu
6. Enter 4 to set the parameters of the Ethernet interface.

Note: Two protocols for download, tftp & ftp. You can modify the flags following the menu. tftp--0x80, ftp--0x0. '.' = clear field; '-' = go to previous field; ^D = quit
boot device : eth1 # Press Enter directly. It does not need to be set. processor number : 0 # Press Enter directly. It does not need to be set. host name : host # Press Enter directly. It does not need to be set. file name : S9300v100r003c01.ccs9300V100R006C00SPC800.cc # Enter the name of the system software to be loaded. inet on ethernet (e) : 192.168.1.1:ffffff00 # Enter the IP address of the management interface on the MPU. The subnet mask does not need to be set. inet on backplane (b): 192.168.1.1 # Press Enter directly. It does not need to be set. host inet (h) : 192.168.1.2 # Enter the IP address of the FTP server. gateway inet (g) : 0 # Press Enter directly. It does not need to be set. user (u) : 9300 # Enter the FTP user name. ftp password (pw) (blank = use rsh): 123456 # Enter the FTP password. flags (f) : 0x0 # Press Enter directly. It does not need to be set. target name (tn) : octeon # Press Enter directly. It does not need to be set. startup script (s) : # Press Enter directly. It does not need to be set. other (o) : # Press Enter directly. It does not need to be set.
Here, the name of the system software to be loaded is s9300V100R006C00SPC800.cc, the IP address of the FTP server is 192.168.1.2, the FTP user name is 9300, and the password of the FTP user is 123456. You can modify the parameter settings according to your needs.
The parameter values can contain only letters, numerals, underlines, and periods. Spaces cannot be used.
7. Enter 3 to download the system software to the CF card.

Be sure to modify parameter before downloading! Enter your choice(1-5): 3 boot device : unit number : processor number : host name : file name : inet on ethernet (e) : inet on backplane (b): host inet (h) : gateway inet (g) : user (u) : ftp password (pw) : flags (f) : target name (tn) : eth1 1 0 host s9300V100R006C00SPC800.cc 192.168.1.1:ffffff00 192.168.1.1 192.168.1.2 9300 123456 0x0 octeon
Issue 02 (2011-12-28)
84
Loading...................................Done! Please type a new file name for saving it. Press return key to save it named " s9300V100R006C00SPC800.cc". Check disk space Writing file.............................................................................. ..............................Done
8. Enter 5 to return to the main menu.

Be sure to modify parameter before downloading! Enter your choice(1-5): 5
9. Enter 6 to configure the loaded system software as the startup program.

1. 2. 3. 4. 5. 6. 7. 8. MAIN MENU Boot with default mode Boot from Flash Boot from CFCard Enter serial submenu Enter ethernet submenu Modify Flash description area Modify bootrom password Reboot
Enter your choice(1-8):6 Modify flash description area Please select booting device. Press ENTER directly for no change or input your choice. 1: Flash, 2: CF Card Current booting device: 2, your choice: 2 # Start from the CF card. Current booting File Name: cfcard:/ S9300v100r003c01.cc, Press ENTER directly for no change. Or, please input the file name (e.g. S9300v100r003c01.cc): s9300V100R006C00SPC800.cc # Enter the name of the new startup program. The expected booting file: cfcard:/ s9300V100R006C00SPC800.cc. Are you sure? Yes or No(Y/N)y # Enter y to confirm the startup program. Writing descriptor to flash...OK! Writing backup descriptor to flash...OK!
10. In the main menu, select 8 to restart the S9300.

----End
Issue 02 (2011-12-28)
86

Quidway S9300 Terabit Routing Switch V100R006C00SPC800 Upgrade Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Quidway S9300 Terabit Routing Switch V100R006C00SPC800 Upgrade Guide

Uploaded by

Copyright:

Available Formats

Quidway S9300 Terabit Routing Switch V100R006C00SPC800

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

2. Command Line Upgrade

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

2 Command Line Upgrade

Command Line Upgrade

1.1.2 Impact of the Upgrade

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

2 Command Line Upgrade

Impact on the System During the Upgrade

Impact on the System After the Upgrade

LPU version information :

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

2 Command Line Upgrade

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

2 Command Line Upgrade

Precautions Before Degrade

1.2 Upgrade Process Overview

Prepare for the upgrade

Perform the upgrade

Check if upgrade is successful Yes End

Roll back to an earlier version See 2.5

Prepare for the upgrade

Prepare tools and software.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

2 Command Line Upgrade

Perform the upgrade

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

Verify the upgrade

Roll back to an earlier version

1.3 Preparing for the Upgrade

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

2 Command Line Upgrade

Setting Up the Upgrade Environment Backing Up CF Card Data

Checking the Space on the CF Cards

1.3.2 Obtaining Upgrade Reference Documents

1.3.3 Obtaining Tools

1.3.4 Obtaining Upgrade Software

1.3.5 Obtaining the License File

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Quidway S9300 Terabit Routing Switch Upgrade Guide

2 Command Line Upgrade

1.3.6 Preparing the Configuration File