ZTE ZXR10 5960%265900E V2.09.10 Ethernet Switch Version Upgrade Guide_R1.0_560843

8/10/2019 ZTE ZXR10 5960%265900E V2.09.10 Ethernet Switch Version Upgrade Guide_R1.0_560843

1/42

ZXR10 5960&5900E V2.09.10

Ethernet Switch VersionUpgrade Guide

R1.0


2/42

ZXR10 5960&5900E V2.09.10 Ethernet Switch Version Upgrade Guide Internal Use On

ly

ZTE Confidential Proprietary 2014 ZTE CORPORATION. All rights reserved. I

LEGAL INFORMATION

By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you donot agree to the following terms, please notice that you are not allowed to use this document.

Copyright 2014 ZTE CORPORATION. Any rights not expressly granted herein are reserved. Thisdocument contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,distribution, use or disclosure of this document or any portion of this document, in any form by anymeans, without the prior written consent of ZTE CORPORATION is prohibited.

and are registered trademarks of ZTE CORPORATION. ZTEs company name, logo

and product names referenced herein are either trademarks or registered trademarks of ZTECORPORATION. Other product and company names mentioned herein may be trademarks or tradenames of their respective owners. Without the prior written consent of ZTE CORP ORATION or thethird party owner thereof, anyones access to this document should not be construed as granting, byimplication, estopped or otherwise, any license or right to use any marks appearing in the document.

The design of this product complies with requirements of environmental protection and personalsecurity. This product shall be stored, used or discarded in accordance with product manual, relevantcontract or laws and regulations in relevant country (countries).

This document is provided as is and as available. Information contained in this document is subjectto continuous update without further notice due to improvement and update of ZTE CORPORATIONsproducts and technologies.

ZTE CORPORATION

Address: NO. 55Hi-tech Road SouthShenZhen

P.R.China518057

Website: http://dms.zte.com.cn (TSM-Technical Support)

Email: [email protected]


3/42


ly

ZTE Confidential Proprietary 2014 ZTE CORPORATION. All rights reserved. II

Revision History

Product Version Document Version Serial Number Reason for Revision

V2.09.10 R1.0 First published

Author

Date Document Ver sion Prepared by Reviewed by Approved by

2013-1-11 R1.0 Yang Zheng Huang Zhiyan


4/42


ly

ZTE Confidential Proprietary 2014 ZTE CORPORATION. All rights reserved. III

Applicable to: Commissioning and maintenance engineers

Proposal: Before reading this document, you had better have the following knowledge and skills.

SEQ Knowledge and skills Reference material

1

2

3

Follow-up document: After reading this document, you may need the following information SEQ Reference material Information

1

2

3


5/42


ly

ZTE Confidential Proprietary 2014 ZTE CORPORATION. All rights reserved. IV

About This Document

SummaryChapter Description

1 Version Information Describes software version status .

2 Upgrade Flow Introduces software version upgrade flow.

3 Preparation before Upgrade Describes preparations before upgrade.

4 Bootrom Upgrade Describes bootrom upgrade precautions, upgrade procedures,emergency handling and bootrom burning steps.

5 Software Version Upgrade Describes software version upgrade precautions, upgradeprocedures, and inspection & test after upgrade.

6 Version Rollback Describes specific rollback steps for different situations.

7 Frequently Asked Questions Describes the frequently asked questions.

AppA Usage Guideline forCommon Terminal Software andFTP Software

Describes how to set and use common upgrade software.


6/42


ly

ZTE Confidential Proprietary 2014 ZTE CORPORATION. All rights reserved. V

TABLE OF CONTENTS

1 Version Information ............................................................................................ 1

2 Upgrade Flow ...................................................................................................... 1

3 Preparation before Upgrade .............................................................................. 2 3.1 Preparation Records before Upgrade .................................................................. 2 3.2 Reading Version Accompanying Documents ....................................................... 3 3.3 Preparing Software and Hardware ....................................................................... 3 3.4 Setting up an Upgrade Environment .................................................................... 3

3.5

Backing up Data.................................................................................................... 4

3.5.1 Backing up Configuration Files ............................................................................. 4 3.5.2 Backing up Version Files ...................................................................................... 5 3.6 Checking Running State ....................................................................................... 5 3.6.1 Checking Hardware Running State ...................................................................... 5 3.6.2 Checking System Running State .......................................................................... 6 3.6.3 Checking Services ................................................................................................ 7 3.6.4 Checking FLASH Free Space............................................................................... 7

4 Bootrom Upgrade ............................................................................................... 8 4.1 Precautions ........................................................................................................... 8 4.2 Upgrade Flow ........................................................................................................ 8

4.3 Record of Upgrade Process ................................................................................. 9 4.4 Upgrade Procedure............................................................................................... 9 4.4.1 Deleting Remaining Boot Files ............................................................................. 9 4.4.2 Copying Boot Files .............................................................................................. 10 4.4.3 Upgrading bootrom ............................................................................................. 11 4.4.4 Verifying Upgrade ............................................................................................... 11 4.4.5 Sync of bootrom Zones....................................................................................... 12

5 Software Version Upgrade ............................................................................... 12 5.1 Precautions ......................................................................................................... 12 5.2 Upgrade Flow ...................................................................................................... 12 5.3 Record of Upgrade Process ............................................................................... 13

5.4 Upgrade Procedure............................................................................................. 13 5.4.1 Renaming the Old Version File ........................................................................... 14 5.4.2 Downloading the Target Version File via ftp ...................................................... 14 5.4.3 Checking Boot Mode........................................................................................... 15 5.4.4 Version Backup Function .................................................................................... 15 5.4.5 Restarting the Switch .......................................................................................... 15 5.4.6 Checking Boot Status ......................................................................................... 15 5.4.7 Checking New Version Information .................................................................... 16 5.4.8 Checking Configuration Information ................................................................... 16 5.4.9 Verifying Upgrade ............................................................................................... 17


7/42


ly

ZTE Confidential Proprietary 2014 ZTE CORPORATION. All rights reserved. VI

6 Version Rollback ............................................................................................... 17 6.1 Rollback Application............................................................................................ 17 6.2 Failure to Start the Device Normally ................................................................... 17 6.3 Abnormal Services .............................................................................................. 19 6.4 Services Abnormal After V2.8.23C Being Upgraded into V2.09.10................... 19

7 Frequently Asked Questions ........................................................................... 19

AppA Usage Guideline for Common Terminal Software and FTP Software ........ 20 A.1 Terminal Software ............................................................................................... 20 A.1.1 HyperTerminal..................................................................................................... 20 A.1.2 SecureCRT ......................................................................................................... 20 A.2 FTP Tool.............................................................................................................. 21 A.2.1 3CDaemon .......................................................................................................... 21 A.2.2 WFTPD................................................................................................................ 22 A.3 Araxis merge ....................................................................................................... 23


8/42


ly

ZTE Confidential Proprietary 2014 ZTE CORPORATION. All rights reserved. VII

FIGURES

Figure 2-1 Version Upgrade Flow............................................................................................ 1 Figure 4-1 Bootrom Upgrade Flow .......................................................................................... 8

Figure 5-1 Software Version Upgrade Flow .......................................................................... 12

TABLES

Table 1-1 Product Model.......................................................................................................... 1

Table 3-1 Preparation Records before Upgrade ..................................................................... 2 Table 3-2 Checklist of System Running State......................................................................... 6

Table 4-1 Bootrom Upgrade Process ...................................................................................... 9

Table 5-1 Software Version Upgrade Process ...................................................................... 13


9/42


ly

ZTE Confidential Proprietary 2014 ZTE CORPORATION. All rights reserved. 1

1 Version Information

Tip:

This guide is applicable to engineers who are familiar with data products, have experiencesin data product upgrade, and pass ZTE Data Products Certificate Test-Level I or above.

ZXR10 5960&5900E series switches include 2 product series, among which 5900Eseries switches contain multiple product models, as shown in Table 1-1.

Table 1-1 Product ModelProduct Series Product Model

5900E series ZXR10 5928E, 5928E-FI, 5952E, 5916E

5960 series ZXR10 5960-32DL, 5960-64DL

The software package for ZXR10 5960&5900E Series switches contains many files.Refer to for the list of the files.

Table 1-1 The File List

File Name(Including

Path)

File Type Product Series/Model/Board That It Fits

\5960\ Version &bootfile

ZXR10 5960 series

\59E\xls108 Version &bootfile

ZXR10 59E series CPU sub-card is xls108

Note:

The V2.9.10 version supports 5900E xls108 sub-card only. The 5900E device running 8270sub-card cannot be upgraded to this version. During the version upgrade on site, it may needto upgrade the bootrom. For detailed information, refer to the release notes.


10/42


ly


2 Upgrade FlowFigure 2-1 depicts the upgrade flow of ZXR10 5960&5900E Series switches.

Figure 2-1 Version Upgrade Flow

Start

End

Upgrade softwareversion

Whether bootrom needs

to beupgraded?

Preparation before

upgrade

N

Upgrade BootromY

Upgradesucceeds?

Y

Version rollback N

1. Preparation before Upgrade

A series o f preparations should be made in advance. For detail ed information, referto 3 Preparation before Upgrade .

2. Bootrom Upgrade

During the preparation, make clear whether Bootrom upgrade is needed in theupgrade. If yes, refer to 4 BOOTROM UPGRADE to perform the upgrade.

This process lasts about 5-10 minutes.

3. Software Version Upgrade


11/42


ly


Refer to 5 SOFTWARE VERSION UPGRADE for upgrading the software version. Ifthe upgrade succeeds, the upgrade is completed; if it fails, roll back to the oldversion.

This process lasts about 20 minutes.

4. Version Rollback

If the version upgrade fails, the version rollback should be performed. Specificfailure situation requires specific rollback procedure. For detailed method, refer to 6VERSION ROLLBACK .

The rollback lasts about 30 minutes.


12/42


ly


3 Preparation before UpgradeThis chapter focuses on a series of preparations before the upgrade.

3.1 Preparation Records before Upgrade

To ensure a quick, accurate and safe upgrade, you should make good preparationsbefore the upgrade.

Prepare items according to the Table below, and record whether each of them has beencompleted in every detail.

Table 3-1 Preparation Rec ords before Upgrade

S/N Item Completedor Not

Record of Preparation

1 Read versionaccompanying documents

2 Prepare software andhardware

3 Set up upgradeenvironment

4 Back up configurationinformation

5 Back up version file

6 Check running status ofhardware

7 Check running status ofsystem

8 Check services

9 Check FLASH free space

3.2 Reading Version Accompanying Documents

Download version documents, including version release instruction and version upgradeguide (this document itself); and read them carefully.

1. The Version Release Instruction

Read the Version Release instruction mainly for the following information:

Whether the bootrom needs to be upgraded;


13/42


ly


Whether configuration commands of the target version change;

2. Version Upgrade Guide

Read it to have a good grasp of the precautions and the specific operationprocedure.

3.3 Preparing Software and Hardware

1. Hardware preparation

If possible, prepare spare parts for switches at key nodes and tools necessaryfor the replacement;

Prepare serial console cables and network cables needed; and check whetherthey are usable.

2. Software preparation

Request and download version files according to procedures specified by ZTEand check the file size.

If there are any changes in configuration commands of the target version,current configuration needs to be acquired in advance. Check whether thereare any configuration differences between target version and original version. Ifany, record them, and then compile corresponding configuration commandscript according to the format of the new version.

Prepare FTP/TFTP tool software necessary for upgrade, and check if they areusable;

Prepare tool Araxis merge for comparing pre/post -upgrade configurationinformation.

3.4 Setting up an Upgrade Environment1. Serial Port Connection

Connect a PC to the device via the serial console cable; open HyperTerminal orother terminal software to configure the serial port attributes:

Bits per Second (baud rate): 9600

Data Bits: 8

Parity: None


14/42


ly


Stop Bits: 1

Flow Control: None

After the configuration, make sure that access to the device is available via theserial port. Next, enable automatic logging function for the terminal software.

For detailed setting method, refer to A.1 Terminal Software .

2. Network Cable Connection

Connect the network port of the PC to the service port or management port of thedevice via the network cable. Configure IP addresses from the same subnet forthem to ensure that the two peers can ping through each other.

The PC telnets the IP address of the device. And the device can be logged inproperly.

3. Start the FTP Server

Set and start the FTP server software to ensure its proper operation.

3.5 Backing up Data

3.5.1 Backing up Configuration Files

Current configuration of the device is so vital that it must be backed up before theupgrade in order to restore the data after the upgrade.

1. Check current configuration of the device and save the displayed configuration tothe background server.

ZXR10#show running-config

2. Save the current configuration and make sure that it is saved properly.

ZXR10#write

Building configuration...

..[OK]

ZXR10#cd cfg

ZXR10#dir

Directory of flash:/cfg

attribute size date time name

1 drwx 2048 Jan-11-2013 14:11:27 .

2 drwx 2048 Jan-01-2000 00:00:24 ..


15/42


ly


3 ---- 3233 Jan-11-2013 14:11:27 startrun.dat

4 -rw- 7177 Jul-03-2012 10:21:00 lacpv6.dat

5 -rw- 8185 Jul-03-2012 08:44:20 mc234.dat

264241152 bytes total (123305269 bytes free)

3. Back up the configuration file to the background FTP server.

Copy the configuration file through the service port:

On 5900E:

ZXR10#copy flash: /cfg/startrun.dat ftp: //169.1.3.12/startrun.dat@ztezte:ztezte

On 5960:

ZXR10#copy root flash/cfg/startrun.dat ftp: //169.1.3.12/startrun.dat@ztezte:ztezte

Copy the configuration file via the management port

On 5900E:

ZXR10#copy flash: /cfg/startrun.dat ftp: mng //169.1.3.12/startrun.dat@ztezte:ztezte

On 5960:

ZXR10#copy root flash/cfg/startrun.dat ftp: mng //169.1.3.12/startrun.dat@ztezte:ztezte

Note:

1. The version that the 5960 device can start to run is V2.09.10.

2. In this document, the 5900E device is upgraded from V2.8.23.C to V2.09.10. Note that thecopy command is different from that on the 5960 device.

3.5.2 Backing up Version Files

If the upgrade fails, the old version should be used to restore the operation. Therefore, itis important to back up the version file.

1. View current version file on the device.

ZXR10#dir img

Directory of flash:/img


1 drwx 2048 Sep-10-2012 16:10:09 .

2 drwx 2048 Jan-01-2000 00:00:24 ..

3 -rwx 15990287 Jul-03-2012 15:42:51 16p01.zar

4 -rwx 16423968 Jun-14-2001 02:16:46 B2.zar

5 -rwx 16279272 Mar-16-2012 09:25:03 zxr10.zar04
mailto:169.1.3.12/startrun.dat@ztezte:zteztemailto:169.1.3.12/startrun.dat@ztezte:zteztemailto:169.1.3.12/startrun.dat@ztezte:zteztemailto:169.1.3.12/startrun.dat@ztezte:ztezte


16/42


ly


6 -rwx 16298516 Apr-26-2012 17:30:03 zxr10.zar07

7 -rw- 17216928 Nov-12-2012 15:39:42 B8.dat

8 -rwx 16939008 Dec-10-2012 09:36:01 B10.zar

9 -rwx 16004107 Dec-10-2012 10:54:58 P02.zar10 -rwx 16003448 Jan-11-2013 13:56:16 zxr10.zar

11 -rwx 642432 Nov-21-2012 10:24:30 bootrom.bin


2. Back up the version file to the background FTP server

Copy the version file through the service port

On 5900E:

ZXR10#copy flash: /img/zxr10.zar ftp: //169.1.3.12/zxr10.zar@ztezte:ztezte

On 5960:

ZXR10#copy root flash/img/zxr10.zar ftp: //169.1.3.12/zxr10.zar@ztezte:ztezte

Copy the version file through the management port

On 5900E:

ZXR10#copy flash: /img/zxr10.zar ftp: mng //169.1.3.12/zxr10.zar@ztezte:ztezte

On 5960:

ZXR10#copy root flash/img/zxr10.zar ftp: mng //169.1.3.12/zxr10.zar@ztezte:ztezte

3.6 Checking Running State

3.6.1 Checking Hardware Running State

Check whether the system hardware before the upgrade is in normal state to make surethat there is no latent risk.

Efforts should be made to check whether the indicators o n the panel are in normal s tate.The indicator states below are for your reference.

1. RUN indicator

Off The main board is faulty.

Flash The main board is working normally.

2. PWR indicator

Constantly on The system power is working normally.

Off The system power is faulty.
mailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:ztezte


17/42


ly


3. LINK/ACT indicator

Flash There are packets being received or sent on the interface.

On A link has been established on this interface.

Off No interconnection is established between this interface and another interface.

4. FDX/COL

On The interface link is in full duplex mode.

Off The interface link is in half duplex mode.

Flash There is a receiving/sending conflict on this interface.

3.6.2 Checking System Running State

Check the running status of the system before the upgrade and record relatedinformation for comparison after the upgrade. The main items to be checked are asshown in Table 3-2. Yet, it is necessary to add or delete some of the items according tothe actual needs on site.

Table 3-2 Checklis t of System Running State

Item Command RemarkDisplay the softwareversion of a system

show version

Display the boot versionof a s ystem show bootrom

59E 108 sub-card isset with two bootzones

Display the currentconfiguration file

show running-config

Display the CPU usage show process

Display routinginformation

show ip route

Display type and numberof route entries show ip protocol routing summary

Display port trafficstatistics

show interface

Display layer-3 portinformation

show ip inter face brief

Display MAC forwardingtable information

show mac

Display ARP tableinformation

show arp

Display alarm information show logging alarm

Display content of the log dir data


18/42


ly


Item Command Remarkfile folder

Display OSPF adjacencystate

show ip ospf nei

Display BGP adjacencystate

show ip bgp sum

Display PIM-SMadjacency information

show ip pimsm nei

Display multicast routes show ip mroute

Display MPLS forwardingtable

show mpls for

Display the s ystem clock show clock

3.6.3 Checking Services

Check running status of services on the device. Items to be checked can be adjustedaccording to specific services at the sites where the devices are to be upgraded.

The customers should assist in inspecting services and confirm the results.

3.6.4 Checking FLASH Free Space

Before the upgrade, make sure that enough flash free space is reserved for the newversion. If not enough, delete some useless files. If the space is still not enough, the files(such as, log files) not necessary for the running of the system can be backed up to thebackground FTP server, and then deleted from the FLASH.

1. Check Flash free space

ZXR10#dir

Directory of flash:/


1 drwx 2048 Jan-01-2000 00:00:24 .

2 drwx 0 Jan-01-2000 00:00:26 ..

3 ---- 131072 Jan-01-2000 00:00:24 capture4 -rwx 714664 Mar-23-2012 16:09:47 zdbagent

5 -rwx 309900 Mar-26-2012 10:54:00 ztam

6 drwx 2048 Sep-10-2012 16:10:09 img

7 drwx 2048 Jan-04-2013 09:14:38 data

8 ---- 393152 Jan-01-2000 00:00:33 record

9 drwx 2048 Jan-11-2013 14:11:27 cfg

10 drwx 2048 Jan-01-2000 00:00:03 lost+found



19/42


ly


2. Delete useless files

ZXR10#cd cfg

ZXR10#dir

Directory of flash:/cfg


1 drwx 2048 Jan-11-2013 14:11:27 .

2 drwx 2048 Jan-01-2000 00:00:24 ..

3 ---- 3233 Jan-11-2013 14:11:27 startrun.dat

4 -rw- 7177 Jul-03-2012 10:21:00 lacpv6.dat

5 -rw- 8185 Jul-03-2012 08:44:20 mc234.dat


ZXR10#delete lacpv6.datAre you sure to delete files?[yes/no]:y

Start deleting file

deleting /flash/cfg/lacpv6.dat..

....

file deleted successfully.


20/42


ly


4 Bootrom UpgradePlease skip this chapter if the bootrom doesnt need to be upgraded.

This chapter covers precautions, upgrade procedures, emergency handling and bootromburning procedures.

4.1 Precautions

ZXR10 5960&5900E switches support live upgrade of the bootrom. In the upgrade, thefollowing items should be noted:

1. Never upgrade the bootrom online when CPU utilizations are high;

2. Never power off the system during the live upgrade of the bootrom, otherwise thesystem will be unable to start.

3. Precautions for the bootrom upgrade are as follows:

i. The 108CPU sub-cards of 5960 and 5900E are both set with bootrommaster/slave zones.

ii. Update the bootrom of the idle zone.

iii. If the bootrom update fails, do not restart the device directly. Try to upgrade thebootrom a few more times.

iv. After the bootrom upgrade, if the device fails to load the boot file upon restart,then, when the timer expires, the system will switch back to the current zone tostart, so as to make sure that the device can resto re basic operation.


21/42


ly


4.2 Upgrade Flow

Figure 4-1 Bootrom Upgrade Flow

Start

End

Delete the remaining boot file

Copy boot file

Update bootrom

Verify upgrade

4.3 Record of Upgrade Process

During the bootrom upgrade, operations should be made step by step. Record theimplementation of each step, as shown in Table 4-1.

Table 4-1 Bootrom Upgrade Process

S/NStep Completed

or NotRecord of Implementation

1 Delete Remaining BootFiles

2Copy Boot Files

3 Upgrade the Bootrom

4 Verify Upgrade

4.4 Upgrade Procedure

Detailed upgrade steps are as follows.


22/42


ly


4.4.1 Deleting Remaining Boot Files

Before the upgrade, the bootrom file of the old version under img directory should bedeleted.

ZXR10#cd img

ZXR10#dir



1 drwx 2048 Sep-10-2012 16:10:09 .

2 drwx 2048 Jan-01-2000 00:00:24 ..

3 -rwx 15990287 Jul-03-2012 15:42:51 16p01.zar

4 -rwx 16423968 Jun-14-2001 02:16:46 B2.zar

5 -rwx 16279272 Mar-16-2012 09:25:03 zxr10.zar046 -rwx 16298516 Apr-26-2012 17:30:03 zxr10.zar07

7 -rw- 17216928 Nov-12-2012 15:39:42 B8.dat

8 -rwx 16939008 Dec-10-2012 09:36:01 B10.zar

9 -rwx 16004107 Dec-10-2012 10:54:58 P02.zar

10 -rwx 16003448 Jan-11-2013 13:56:16 zxr10.zar

11 -rwx 642432 Nov-21-2012 10:24:30 bootrom.bin


Delete the bootrom file:

ZXR10#delete bootrom.binAre you sure to delete files?[yes/no]:y

Start deleting file

deleting /flash/img/bootrom.bin..

..

file deleted successfully.

4.4.2 Copying Boot Files

Before the upgrade, copy all boot files necessary for the upgrade to the img directory onthe FLASH of the switch.


On 5900E:

ZXR10#copy ftp: //169.1.3.12/bootrom.bin@ztezte:ztezte flash: /img/bootrom.bin

On 5960:

ZXR10#copy ftp: //169.1.3.12/bootrom.bin@ztezte:ztezte root flash/img/bootrom.bin


On 5900E:


23/42


ly


ZXR10#copy ftp: mng //169.1.3.12/bootrom.bin@ztezte:ztezte flash: /img/bootrom.bin

On 5960:

ZXR10#copy ftp: mng //169.1.3.12/bootrom.bin@ztezte:ztezte root flash/img/bootrom.bin

After copying, check the following:

ZXR10#dir



1 drwx 2048 Jan-11-2013 14:38:08 .

2 drwx 2048 Jan-01-2000 00:00:24 ..

3 -rw- 650144 Jan-11-2013 14:38:10 bootrom.bin

4 -rwx 15990287 Jul-03-2012 15:42:51 16p01.zar

5 -rwx 16423968 Jun-14-2001 02:16:46 B2.zar6 -rwx 16279272 Mar-16-2012 09:25:03 zxr10.zar04

7 -rwx 16298516 Apr-26-2012 17:30:03 zxr10.zar07

8 -rw- 17216928 Nov-12-2012 15:39:42 B8.dat

9 -rwx 16939008 Dec-10-2012 09:36:01 B10.zar

10 -rwx 16004107 Dec-10-2012 10:54:58 P02.zar

11 -rwx 16003448 Jan-11-2013 13:56:16 zxr10.zar


Note:

File name of the boot saved to the FLASH must be correct and identical to that in thesoftware package.

After copying, execute the dir img command to check whether the boot file size isconsistent with that on the FTP server.

4.4.3 Upgrading bootrom

Record information of the old boot:

ZXR10#sho bootrom

Common Zone Version : V1.01

Creation Date : 2011/8/5

Master Zone Version : V3.14


Slave Zone Version : V3.14


The device boot from slave boot zone this time. ---The currently used zone is the slave

zone.


24/42


ly


1. Enter the implicit mode of the sys tem

ZXR10#olleh

zxr10(config-increte)#

2. Upgrade the Bootrom

ZXR10(config-increte)#bootrom update

If the update succeeds, the system will give out a message to indicate that the update issuccessful.

Tip:

If it shows that the update fails, please delete the corresponding boot file under the imgdirectory and recopy a new one to perform the update again. If the upgrade still fails afterseveral times of attempts, replace bootrom chip of corresponding card manually.

3. Press ctrl+z to quit the implicit mode

4. Exit the implicit mode and restart the device.

4.4.4 Verifying Upgrade

After updating the boot, check whether the boot has been updated:

ZXR10#show bootrom

Common Zone Version : V1.01


Master Zone Version : V3.33 -----the zone where the boot should be updated




The device boot from slave boot zone this time. ---- The currently used zone is the

slave zone

Note: The command bootrom update is used to update the boot in the idle zone. In thisexample, the currently used zone is slave while the idle zone is master. Hence, it is themaster zone that is updated.

4.4.5 Sync of bootrom Zones

After downloading the software version o f the device and starting the switch successfully,the zone where the boot is not updated will become the idle zone. And then, it isnecessary to update this boot manually.

Enter the implicit mode of the system to update the boot:


25/42


ly


ZXR10(config-increte)#bootrom update

After that, check whether the boot of master and slave zones has been updated successfu

lly:

ZXR10#show bootromCommon Zone Version : V1.01


Master Zone Version : V3.33




The device boot from master boot zone this time.


26/42


ly


5 Software Version UpgradeThis chapter examines precautions, upgrade procedures, and inspection & test after theupgrade.

5.1 Precautions

1. Set the auto-logging function of the terminal software before the upgrade for lateranalysis of the reason behind the unexpected upgrade failure;

2. During the process of writing the version into the FLASH, never restart the device orpower it off, otherwise the FLASH may be damaged;

3. During the process of writing the version into the FLASH, CPU utilization will rise, soit is forbidden to implement other operations on the device.

4. Troubleshooting principle for unexpected accident is to recover services as soon aspossible before locating the failure cause. And meantime, during the period ofupgrade request, try to collect information as much as possible for subsequentanalysis;

5. For unexpected situations that cannot be solved, please contact instructors ofCustomer Service Department of Wired Network Service Center.

5.2 Upgrade Flow

Figure 5-1 depicts the software version upgrade flow.


27/42


ly


Figure 5-1 Software Version Upgrade Flow

Start

End

Check new versioninformation

Check configurationinformation

Verify upgrade

Reboot switch

Check boot status of device

Check boot mode

Delete the old version file

Download target version file

5.3 Record of Upgrade Process

During the software version upgrade, operations should be made step by step. Recordthe implementation for each step, as shown in Table 5-1.

Table 5-1 Software Version Upgrade Process

S/N Step Completedor Not

Record of Implementation

1 Rename Old Version File

2 Download Target VersionFile

3 Check Boot Mode


28/42


ly


S/NStep Completed

or NotRecord of Implementation

4 Restart Switch

5 Check Boot Status ofDevice

6 Check New VersionInformation

7 Check ConfigurationInformation

8 Verify Upgrade

5.4 Upgrade Procedure

Detailed upgrade steps are as follows.

5.4.1 Renaming the Old Version File

Rename the version file of the device:

ZXR10#rename zxr10.zar old.zar

Delete the old version file if the FLASH cannot accommodate two versions:

ZXR10#cd img

ZXR10#delete zxr10.zar

5.4.2 Downloading the Target Version File via ftp

Download the target version file via the FTP server to the IMG directory of the FLASH ofthe switch.

Note:

The name of the target version file saved to the FLASH must be zxr10.zar.


On 5900E:

ZXR10#copy ftp: //169.1.3.12/zxr10.zar@ztezte:ztezte flash: /img/zxr10.zar

On 5960:

ZXR10#copy ftp: //169.1.3.12/zxr10.zar@ztezte:ztezte root flash:/img/zxr10.zar


On 5900E:

ZXR10#copy ftp: mng //169.1.3.12/zxr10.zar@ztezte:ztezte flash: /img/zxr10.zar
mailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:ztezte


29/42


ly


On 5960:

ZXR10#copy ftp: mng //169.1.3.12/zxr10.zar@ztezte:ztezte root flash/img/zxr10.zar

After downloading, execut e command dir img to check whether the version file size isconsistent with that on FTP server.

ZXR10#dir



1 drwx 2048 Jan-11-2013 14:43:32 .

2 drwx 2048 Jan-01-2000 00:00:24 ..

3 -rw- 16950384 Jan-11-2013 14:44:25 zxr10.zar

4 -rwx 16003448 Jan-11-2013 13:56:16 backup.zar

5 -rw- 650144 Jan-11-2013 14:38:10 bootrom.bin

6 -rwx 15990287 Jul-03-2012 15:42:51 16p01.zar

7 -rwx 16423968 Jun-14-2001 02:16:46 B2.zar

8 -rwx 16279272 Mar-16-2012 09:25:03 zxr10.zar04

9 -rwx 16298516 Apr-26-2012 17:30:03 zxr10.zar07

10 -rw- 17216928 Nov-12-2012 15:39:42 B8.dat

11 -rwx 16939008 Dec-10-2012 09:36:01 B10.zar

12 -rwx 16004107 Dec-10-2012 10:54:58 P02.zar


5.4.3 Checking Boot Mode

Check whether the boot mode is the local boot:

ZXR10#show nvram-info

nvram boot-username ztezte

nvram boot-password ztezte

nvram boot-server 169.1.3.12

nvram default-gateway 169.1.3.12

nvram mng-ip-address 169.1.3.124 255.255.255.0

nvram imgfile-location local flash img/zxr10.zar //local refers to local boot while

network means boot from the network

If the boot mode is the boot via network, you can execute relevant command to change itto the local boot, and save the configuration:

ZXR10(config)#nvram imgfile-location local

ZXR10(config)#exit

ZXR10#write
mailto:169.1.3.12/zxr10.zar@ztezte:zteztemailto:169.1.3.12/zxr10.zar@ztezte:ztezte


30/42


ly


5.4.4 Version Backup Function

1. Configure the backup version as the file backup.zar in the IMG directory of the flash:

ZXR10(config)#nvram backup-imgfile img/backup.zar

2. Check configuration information of the backup version:

ZXR10#show nvram-info

nvram boot-username ztezte

nvram boot-password ztezte

nvram boot-server 169.1.3.12

nvram default-gateway 169.1.3.12

nvram mng-ip-address 169.1.3.124 255.255.255.0

nvram imgfile-location local flash img/zxr10.zar

nvram backup-imgfile img/backup.zar

When the device starts, if there is no file zxr10.zar, it will start from the backup filebackup.zar.

5.4.5 Restarting the Switch

Run the command reload to restart the device, or press the power switch at the back ofthe device to restart it.

The device takes about 5 minutes to restart. During the restart, keep a close eye on

status of indicators and output information of serial ports.

Usually, we recommends that during the upgrade & restart, the log record function shouldbe enabled to rec ord the upgrade and restart process of the device.

Note:

If the device cannot start normally, and the reason could not be spotted within 20 minutes,this upgrade is regarded as failed. Refer to emergency handling to roll back to the oldversion.

5.4.6 Checking Boot Status

After the device starts successfully, check the status of the indicators and CPU utilizationto make sure that the device is running normally.

ZXR10#show processor

PhyMem: Physical memory (megabyte)

Panel CPU(5s) CPU(1m) CPU(5m) PhyMem Buffer Memory


31/42


ly


MP(M) 1 28% 26% 48% 512 0% 62.068%

14:53:19 01/11/201

5.4.7 Checking New Version Information

Check current version information on the device and make sure that its version number isthe designated target version number.

ZXR10#show version

ZXR10 Router Operating System Software,ZTE Corporation

ZXR10 ROS Version V4.08.28

ZXR10_5952E Software, Version ZXR10 5900E&5100E V2.09.10B11, RELEASE SOFTWARE

Copyright (c) 2010-2015 by ZTE Corporation

Compiled Jan 9 2013, 16:12:57

System image files are flash:

System uptime is 0 days, 0 hours, 4 minutes

[MPU]

Main processor: XLS108 Processor with 512M bytes of memory

8K bytes of non-volatile configuration memory

256M bytes of processor board System flash (Read/Write)

ROM: System Bootstrap, Version: V0.22 , RELEASE SOFTWARE

Hardware Version: V1.0, CPLD Version: V1.0

System serial: 0, Product Version: V1.2

System temperature(Celsius):50

5.4.8 Checking Configuration Information

Execute the command show running-config to view the current configurationinformation. Compare it with the configuration information backed up before upgrade tosee whether there are any differences.

In case configuration commands for the new version have changed, you should completethe configuration fast according to configuration commands before the upgrade.

If the configuration information is long, it is recommended to use the Araxis merge tocompare the configuration information after and before the upgrade, in order to find thedifferences effectively and timely.

5.4.9 Verifying Upgrade

Items to be verified after the upgrade should be substantially identical to that before theupgrade, which mainly covers the following parts:


32/42


ly


1. Check the hardware running state

Check whether the system hardware after upgrade works normally and whether thepanel indicators are in normal status.

2. Check the sys tem running state

Check the running state information of the system after the upgrade, and compare itwith the information recorded before the upgrade to see whether it is normal. Themain items to be checked are as shown in Table 3-2. It is necessary to add or deletesome of them according to the actual situations.

3. Check services

Check running state of services on the device. Items to be checked can be adjusted

according to specific services at the sites where the devices are to be upgraded.

The customers should assist in inspecting services and confirm the results.

Note:

In case the services are abnormal and are caused by the device itself, but the causes could not be located within 20 m inutes, the upgrade is regarded failed. Refer to Emergency Handling to roll back to the old version.


33/42


ly


6 Version RollbackThis chapter describes specific rollback steps for diverse situations.

6.1 Rollback Application

If the upgrade fails, you should perform the version rollback. You should take differentrollback steps for different failures.

The de vice with new version cannot start normally.

Use boot via network to roll back. For detailed steps, refer to 6.2 .

Services under new version are abnormal.

Roll back to the old version to restart the device. For detailed steps, refer to 6.3 .

Roll back to the old version if the upgrade from V2823 C to V2.09.10 fails.Roll back to the old bootrom version of V2823C. For details, refer to 6.4 .

Note:

If the rollback fails, or an accident occurs, please contact instructors from Customer ServiceDepartment.

6.2 Failure to Start the Device Normally

If the device cannot start with the new version, the upgrade is thought failed. You can rollback to the original version step by step.

1. Turn on its power switch to restart the device.

2. Modify the version boot mode to the boot via network

ZXR10 5960&5900E allows the boot via network through management port. Beforethat, make sure that the connection between the port and FTP server is live.

Restart the device. Press any key to enter the boot mode during the countdownperiod, and then modify boot parameters.

ZXR10 Switch System Bootstrap

ZXR10 5952E-ELEC System BootRom Version: V0.22


34/42


ly


Creation date: Jan 7 2013, 09:00:43

Copyright (c) 2013 by ZTE Corporation.

Hit any key to stop auto-boot: 0[boot]: c

'.' = clear field; '-' = go to previous field; '^' = quit

Boot Location [0:Net,1:Flash] : 0 //0 means boot from the network

Client IP : 169.1.3.124 //The port number or mng interface

address

Netmask : 255.255.255.0 //The mask of a network segment

Server IP : 169.1.3.12 //The address of the background FTP

server

Gateway IP : 169.1.3.12 //The gateway address is the interfaceaddress of port number

FTP User : ztezte //The FTP username is ztezte

FTP Password : //The password of the username ztezte

Bootfile : zxr10.zar //The network boot path

Enable Password : //A default value

[boot]:

3. Restart the switch

Restart the device in boot mode. The system downloads the old version from thebackground FTP server automatically.

[boot]: b

Boot Location [0:Net,1:Flash] : 0

Client IP : 169.1.3.124

Netmask : 255.255.255.0

Server IP : 169.1.3.12

Gateway IP : 169.1.3.12

FTP User : ztezte

FTP Password :Bootfile : zxr10.zar

Enable Password :

MAC Address : 00.00.00.00.11.00

4. Verify rollback

After restarting the switch, check whether the version number is the old versionnumber and whether the services are normal.

5. Copy the version to the FLASH


35/42


ly


After making sure that the device and services work normally, delete the versionwith a problem during the upgrade, and write the normal version file to the directoryimg of flash.


On 5900E:

ZXR10#copy ftp: //169.1.3.12/zxr10.zar@ztezte:ztezte flash: /img/ zxr10.zar

On 5960:

ZXR10#copy ftp: //169.1.3.12/zxr10.zar@ztezte:ztezte root flash/img/ zxr10.zar


On 5900E:

ZXR10#copy ftp: mng //169.1.3.12/zxr10.zar@ztezte:ztezte flash: /img/zxr10.zar

On 5960:

ZXR10#copy ftp: mng //169.1.3.12/zxr10.zar@ztezte:ztezte root flash/img/zxr10.zar

6. Modify the version boot mode to local boot

Change the boot mode from boot via network to local boot:

ZXR10(config)#nvram imgfile-location local

ZXR10(config)#exit

ZXR10#write

6.3 Abnormal ServicesIf the device starts normally with the new version, but the services run abnormally, thenthe upgrade is regarded failed. Roll back to the old version according to the followingsteps.

1. Delete the new version file that is copied to the img directory of FLASH during theupgrade, and modify the name of the old version file to zxr10.zar.

ZXR10#delete zxr10.zar

ZXR10#rename old.zar zxr10.zar

Note:

Since the FLASH has no sufficient space and the old version file has been deleted beforeupgrade, it is necessary to recopy the old version file to FLASH. For detailed steps, see 5.4.2 .

2. Execute the command reload to restart the switch

3. Verify the rollback


36/42


ly


After restarting the switch, check whether the version number is the old versionnumber and whether the services are normal.

6.4 Services Abnormal After V2.8.23C BeingUpgraded into V2.09.10

After the onsite devices are upgraded from V2.8.23C to V2.09.10, if the services becomeabnormal, it is necessary to roll back the software version and bootrom version.

In this scenario, the rollback procedures are slightly different from the upgradeprocedures. To go back to the V2.8.23C, first roll back the bootrom version and then thesoftware version. Follow the steps below for rollback.

1. Delete the new version file copied to the IMG directory of the flash during theupgrade, and rename the old version file as zxr10.zar.

2. Copy the boot file of the old version file to the flash, degrade the bootrom of thedevic e. For how to degrade the bootrom, refer to 4 Bootrom Upgrade.

3. Run the command reload to restart the switch.

4. Restart the old version to confirm whether the device is started normally.

5. Verify the rollback.

Note:

To ensure the stability of the two systems, use the matched bootrom versions during theinter-version upgrade or degrade.


37/42


ly


7 Frequently Asked QuestionsThis chapter describes the frequently asked questions during the upgrade.

1. Q: What shall be noted when using write imgfile ?

A: During write imgfile , CPU utilization may be high. In this case, do not implementsophisticated operations, nor view the content on the FLASH, for they will affect thewriting. During the process of write imgfile , never power off, otherwise the FLASHmay be damaged.

2. Q: Why not recommend powering off to restart?

A: The burst current may impair some components in the board, so the board couldnot start normally.

3. Q: When an accident occurs, what information needs being collected for furtheranalysis?

A: Printing information on the serial port, alarming information on the de vice andbasic information on the device when the services become abnormal. Furthermore,if the device fails to start normally, note which status the indicators on the card arein.

4. Q: In the process of V2.8.23B being upgraded into V2.8.23C, after the Bootromonline upgrade is finished, you can find the version ID doesnt change while thecreation time changes by executing the show bootrom command.

A: This problem is the data reading problem in the bootrom update of the V2.8.2 3B.It has no influence on the bootrom version update. You can check the bootrom stateafter the device is restarted to see whether the bootrom update is successful.


38/42


ly


AppA Usage Guideline for Common TerminalSoftware and FTP Software

A.1 Terminal Software

Common terminal software includes HyperTerminal and SecureCRT. Here, we willintroduce how to set the two types of software. Items to be set contain:

Port attribute

Automatic logging function

A.1.1 HyperTerminal

The HyperTerminal is usually used for the serial port connection. The following describesthe setting for it.

1. Click [Start>Programs>Accessories>Communications>HyperTerminal] in theoperating system. The HyperTerminal main interface and [Connection Description]dialog box pop up.

2. Type the name of the connection in of [Connection Description] dialog box,and click . The [Connect To] dialog box will be presented.

3. Select the COM port in option of [Connect To] dialog box for thehost to connect to the device and click the OK. [COM Properties] dialog box popsup.

4. Click in dialog box, modify as required, click to finish the setting and enter HyperTerminalmain interface.

5. If it is necessary to record operation logs, click [Transfer (T)] menu and select [TextCapture (C)]. Then the [Text Capture] dialog box pops up. Select log file in thedialog box and click to finish the setting.

A.1.2 SecureCRT

SecureCRT is commonly used for the serial port connection and telnet connection.

1. Run the SecureCRT software. The SecureCRT main interface and [connect] dialogbox will pop up.


39/42


ly


If [connect] dialog box is closed, you can click the first button on the toolbar of the main interface or select [Connect] in [File] menu to open it.

2. Click the third button on the tool bar of [Connect] dialog box toestablish a new session. [Session Options] dialog box will pop up.

3. Set Connection parameters in [Session Options] dialog box:

i. Configuration of serial port connection

Name: the name of the connection

Protocol: serial

Port: COM port used for the host to connect the device

Baud rate: baud rate of the device, usually 9600 or 115200

Data bits: 8

Parity: None

Stop bits: 1

ii. Configuration for the telnet connection

Name: the name of the connection

Protocol: telnet

Hostname: IP address of the device to be connected

Port: 23

Click to finish the setting and enter SecureCRT main interface.

4. If it is necessary to record operation logs, click [File] menu, and select [Log Session]. And the corresp onding dialog box pops up. Select the log file in the dialog box and

click to finish the setting.

A.2 FTP Tool

Common FTP server tools include 3CDaemon and WFTPD. The following will introducehow to set the two types of software. Items to be set contain:

FTP username/password

Directo ry on the server used for storing the version file or configuration file


40/42


ly


Other software tools share the similar configuration.

A.2.1 3CDaemon

1. Run 3CDaemon software on the background host.

2. Open [FTP Server] module on the left, click [Configure FTP Server]. And[3CDaemon Configuration] dialog box pops up. Then perform the followingoperations:

i. Type username, e.g. target in the above input box;

ii. Click to set the password ;

iii. In the input box below, type directory, e.g. IMG directory of Disk D used forsaving version file or configuration file, or click the button on the right of theinput box to select the directory;

iv. Select Login, Download and Upload in the list below ;

v. Click to finish the setting.

This is shown in AppendixPic A-1.

AppFigure A-1 3CDaemon Window


41/42


ly


A.2.2 WFTPD

1. Run wftpd software on the background host.

2. Click [Security] in the menu, select [Use r/Rights]. And [User/Rights SecurityDialog] dialog box pops up. Then perform the following operations:

i. Click to create a user, such as target, and set a password.

ii. Select user name "target" in the drop-down box;

iii. Type in a directory in the box, such as, the IMG directory onDisk D to save version file and configuration file.

3. Click to complete the setting.


AppFigure A-2 WFTPD Window

A.3 Araxis merge

Araxis merge is a file comparison tool. During the version upgrade, it is commonly usedto compare configurations after and before upgrade.

The Araxis merge is very easy to use.

1. Run the Araxis merge. Then the main interface pops up. We can see the maininterface is divided into two parts: left and right. Each part has an input box,displaying You can type a filename here.


42/42


ly

2. Click the button on the right of each input box respect ively, and select two filesthat needs to be compared. The selected files are displayed o n the two sides of themain interface, and the different places are clearly marked.


AppFigure A-3 Araxis merge Window

ZTE ZXR10 5960%265900E V2.09.10 Ethernet Switch Version Upgrade Guide_R1.0_560843

Documents

Transcript of ZTE ZXR10 5960%265900E V2.09.10 Ethernet Switch Version Upgrade Guide_R1.0_560843