ZTE ZXR10 5960&5900E V2.09.10 Ethernet Switch Version Upgrade Guide - R1.0 - 560843

ZXR10 5960&5900E
Ethernet
Switch
Upgrade Guide
R1.0
V2.09.10
Version
ZXR10 5960&5900E V2.09.10 Ethernet Switch Version Upgrade Guide
Internal Use On
ly
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORAT ION you agree to the following terms. If you do
not agree to the following terms, please notice that you are not allowed to use this document.
Copyright 2014 ZT E CORPORAT ION. Any rights not expressly granted herein are reserved. This
document contains proprietar y information of ZTE CORPORAT ION. Any reproduction, transfer,
distribution, use or disclosure of this document or any por tion of this document, in any form by any
means, without the prior written consent of ZTE CORPORAT ION is prohibited.
and
are registered trademarks of ZTE CORPORAT ION. ZTEs company name, logo
and product names referenced herein are either trademarks or registered trademar ks of ZTE
CORPORAT ION. Other product and company names mentioned herein may be trademarks or trade
names of their respective ow ners. Without the prior written consent of ZTE CORP ORAT ION or the
third party owner thereof, anyones access to this document should not be construed as granting, by
implication, estopped or otherwise, any license or right to use any mar ks appearing in the document.
The design of this pr oduct complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant countr y (countries).
This document is provided as is and as available. Information contained in this document is subject
to continuous update without further notice due to improvement and update of ZT E CORPORAT IONs
products and technologies.
ZTE CORPORATION
Address:
NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website:
http://dms.zte.com.cn (TSM-Technical Support)
Email:
TSM.Aftersales@zte.com.cn
ZTE Confidential Proprietary
2014 ZTE CORPORATION. All rights reserved.
Internal Use On
ly
Revision History
Product Version
V2.09.10
Document Version
R1.0
Serial Number
Reason for Revi sion

First published
Author
Date
2013-1-11
Document Version
R1.0
Prepared by
Yang Zheng
Reviewed by
Approved by
Huang Zhiyan
II
Applicable to:
Internal Use On
ly
Commissioning and maintenance engineers
Proposal: Before reading this document, you had better have the following knowledge and skills.
SEQ
Knowledge and skill s
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
III
Internal Use On
ly
About This Document

Summary
Chapter
Description
Version Information
Describes software version status .
Upgrade Flow
Introduces software version upgrade flow.
Preparation before Upgrade
Describes preparations before upgrade.
Bootrom Upgrade
Describes bootrom upgrade precautions, upgrade procedures,

emergency handling and bootrom burning steps .
Software Version Upgrade
Describes software version upgrade precautions,

procedures, and inspection & test after upgrade.
Version Rollback
Describes specific rollback steps for different situations .
Frequently Asked Questions
Describes the frequently asked questions .
AppA Usage Guideline for

Common Terminal Software and
FTP Soft ware
upgrade
Describes how to set and use common upgrade software.
IV
Internal Use On
ly
TABLE OF CONTENTS
1
Version Information ............................................................................................ 1
Upgrade Flow ...................................................................................................... 1
3
3.1
3.2
3.3
3.4
3.5
3.5.1
3.5.2
3.6
3.6.1
3.6.2
3.6.3
3.6.4
Preparation before Upgrade .............................................................................. 2

Preparation Records before Upgrade .................................................................. 2
Reading Version Accompanying Documents ....................................................... 3
Preparing Software and Hardware ....................................................................... 3
Setting up an Upgrade Environment .................................................................... 3
Backing up Data.................................................................................................... 4
Backing up Configuration Files ............................................................................. 4
Backing up Version Files ...................................................................................... 5
Checking Running State ....................................................................................... 5
Checking Hardware Running State ...................................................................... 5
Checking System Running State .......................................................................... 6
Checking Services ................................................................................................ 7
Checking FLASH Free Space............................................................................... 7
4
4.1
4.2
4.3
4.4
4.4.1
4.4.2
4.4.3
4.4.4
4.4.5
Bootrom Upgrade ............................................................................................... 8

Precautions ........................................................................................................... 8
Upgrade Flow ........................................................................................................ 8
Record of Upgrade Process ................................................................................. 9
Upgrade Procedure............................................................................................... 9
Deleting Remaining Boot Files ............................................................................. 9
Copying Boot Files .............................................................................................. 10
Upgrading bootrom ............................................................................................. 11
Verifying Upgrade ............................................................................................... 11
Sync of bootrom Zones ....................................................................................... 12
5
5.1
5.2
5.3
5.4
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
5.4.6
5.4.7
5.4.8
5.4.9
Software Version Upgrade ............................................................................... 12

Precautions ......................................................................................................... 12
Upgrade Flow ...................................................................................................... 12
Record of Upgrade Process ............................................................................... 13
Upgrade Procedure............................................................................................. 13
Renaming the Old Version File........................................................................... 14
Downloading the Target Version File via ftp ...................................................... 14
Checking Boot Mode........................................................................................... 15
Version Backup Function .................................................................................... 15
Restarting the Switch .......................................................................................... 15
Checking Boot Status ......................................................................................... 15
Checking New Version Information .................................................................... 16
Checking Configuration Information ................................................................... 16
Verifying Upgrade ............................................................................................... 17
Internal Use On
ly
6
6.1
6.2
6.3
6.4
Version Rollback ............................................................................................... 17

Rollback Application............................................................................................ 17
Failure to Start the Device Normally................................................................... 17
Abnormal Services .............................................................................................. 19
Services Abnormal After V2.8.23C Being Upgraded into V2.09.10................... 19
Frequently Asked Questions........................................................................... 19
AppA
A.1
A.1.1
A.1.2
A.2
A.2.1
A.2.2
A.3
Usage Guideline for Common Terminal Software and FTP Software ........ 20
Terminal Software ............................................................................................... 20
HyperTerminal..................................................................................................... 20
SecureCRT ......................................................................................................... 20
FTP Tool.............................................................................................................. 21
3CDaemon .......................................................................................................... 21
WFTPD................................................................................................................ 22
Araxis merge ....................................................................................................... 23
VI
Internal Use On
ly
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
VII
Internal Use On
ly
Version Information
Tip:
This guide is applicable to engineers who are familiar with data products, have experiences
in 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 5900E
series switches contain multiple product models, as shown in Table 1-1.
Table 1-1
Product Model
Product Series
Product Model
5900E series
ZXR10 5928E, 5928E-FI, 5952E, 5916E
5960 series
ZXR10 5960-32DL, 5960-64DL
The soft ware 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 & boot

file
ZXR10 5960 series
\59E\xls108
Version & boot

file
ZXR10 59E series CPU sub-card is xls108
Note:
The V2.9.10 version supports 5900E xls108 sub-card only. The 5900E device running 8270
sub-card cannot be upgraded to this version. During the version upgrade on site, it may need
to upgrade the bootrom. For detailed information, refer to the release notes.
Internal Use On
ly
Upgrade Flow
Figure 2-1 depicts the upgrade flow of ZXR10 5960&5900E Series switches.
Figure 2-1
Version Upgrade Flow
Start
Preparation before
upgrade
Whether
bootrom needs
to be
upgraded?
Upgrade Bootrom
Version rollback
Upgrade software
version
Upgrade
succeeds?
Y
End
1.

A series of preparations should be made in advance. For detailed information, refer
to 3 Preparation before Upgrade .
2.
Bootrom Upgrade
During the preparation, make clear whether Boot rom upgrade is needed in the
upgrade. If yes, refer to 4 BOOTROM UPGRADE to perform the upgrade.
This process lasts about 5-10 minutes.
3.
Internal Use On
ly
Refer to 5 SOFTWARE VERSION UPGRADE for upgrading the software version. If

the upgrade succeeds, the upgrade is completed; if it fails, roll back to the old
version.
This process lasts about 20 minutes.
4.
Version Rollback
If the version upgrade fails, the version rollback should be performed. Specific
failure situation requires specific rollback procedure. For detailed method, refer to 6
VERSION ROLLBACK.
The rollback lasts about 30 minutes.
Internal Use On
ly

This 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 preparations
before the upgrade.
Prepare it ems according to the Table below, and record whet her each of them has been
completed in every detail.
Table 3-1
Preparation Rec ords before Upgrade

Item
S/N
3.2
Completed
or Not
Read
version
accompanying documents
Prepare
hardware
Set
up
environment
Back
up
information
Back up version file
Check running status of

hardware
Check running status of

system
Check services
Check FLASH free space
software
Record of Preparation
and
upgrade
configuration
Reading Version Accompanying Documents

Download version documents, including version release instruction and version upgrade
guide (this document itself); and read them carefully.
1.
The Version Releas e Instruction

Read the Version Release instruction mainly for the following information:
Whether the bootrom needs to be upgraded;
2.
Internal Use On
ly
Whether configuration commands of the target version change;
Version Upgrade Guide

Read it to have a good grasp of the prec autions and t he specific operation
procedure.
3.3
Preparing Software and Hardware

1.
2.
3.4
Hardware preparation
If possible, prepare spare parts for switches at key nodes and tools necessary
for the replacement;
Prepare serial console cables and net work cables needed; and check whether
they are usable.
Software preparation
Request and download version files according to procedures specified by ZTE

and 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 whet her there
are any configuration differences between target version and original version. If
any, record them, and then compile corresponding configuration command
script according to the format of the new version.
Prepare FTP/ TFTP tool software nec essary for upgrade, and check if t hey are
usable;
Prepare t ool Araxis merge for comparing pre/post-upgrade configuration

information.
Setting up an Upgrade Env ironment

1.
Serial Port Connection

Connect a PC to the device via the serial console cable; open HyperTerminal or
other terminal software to configure the serial port attribut es:
Bits per Second (baud rate): 9600
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None
Internal Use On
ly
After the configuration, make s ure that access to the device is available via the
serial port. Next, enable aut omatic logging function for the terminal software.
For detailed setting method, refer to A.1 Terminal Software.
2.
Network Cable Connection

Connect the net work port of the PC to the service port or management port of the
devic e via the network cable. Configure IP addresses from the same subnet for
them 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 in
properly.
3.
Start the FTP Server

Set and start the FTP server software to ensu re 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 the
upgrade in order to restore the data after the upgrade.
1.
Check current configuration of the devic e and save t he dis played configuration to
the 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
drwx
2048
Jan-11-2013
14:11:27
drwx
2048
Jan-01-2000
00:00:24
..
Internal Use On
ly
----
3233
Jan-11-2013
14:11:27
startrun.dat
-rw-
7177
Jul-03-2012
10:21:00
lacpv6.dat
-rw-
8185
Jul-03-2012
08:44:20
mc234.dat
264241152 bytes total (123305269
3.
bytes free)
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 the
copy command is different from that on the 5960 device.
3.5.2
Backing up Version Files

If t he upgrade fails, the old version should be used to restore t he operation. Therefore, it
is important to back up the version file.
1.
View current version file on the device.
ZXR10#dir img
Directory of flash:/img
attribute
size
date
time
name
drwx
2048
Sep-10-2012
16:10:09
drwx
2048
Jan-01-2000
00:00:24
..
-rwx
15990287
Jul-03-2012
15:42:51
16p01.zar
-rwx
16423968
Jun-14-2001
02:16:46
B2.zar
-rwx
16279272
Mar-16-2012
09:25:03
zxr10.zar04
-rwx
16298516
Apr-26-2012
17:30:03
zxr10.zar07
-rw-
17216928
Nov-12-2012
15:39:42
B8.dat
-rwx
16939008
Dec-10-2012
09:36:01
B10.zar
-rwx
16004107
Dec-10-2012
10:54:58
P02.zar
10
-rwx
16003448
Jan-11-2013
13:56:16
zxr10.zar
11
-rwx
642432
264241152 bytes total (123305269
2.
Nov-21-2012
10:24:30
Internal Use On
ly
bootrom.bin
bytes free)
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 t he system hardware before the upgrade is in normal state to make sure
that there is no latent risk.
Efforts should be made to check whether the indicat ors on the panel are in normal state.
The indic ator states below are for your reference.
1.
RUN indicat or
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.
3.
Internal Use On
ly
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 interfac e.
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 related
information for comparison after the upgrade. The main items to be checked are as
shown in Table 3-2. Yet, it is necessary to add or delete some of the items according to
the actual needs on site.
Table 3-2
Checklist of System Running State

Item
Command
Display the software

version of a system
show version
Display the boot version

of a system
show bootrom
Display
the
current
configuration file
show running-config
Display the CPU usage
show process
Display
information
show ip route
routing
Display type and number

of route entries
show ip protocol routing summary
Display
statistics
show interface
port
Display
layer-3
information
traffic
port
show mac
Display
ARP
information
show arp
Display alarm information
show logging alarm
Display content of the log
dir data
59E 108 sub-card is

set with two boot
zones
show ip interface brief
Display MAC forwarding

table information
table
Remark
Item
Command
Internal Use On
ly
Remark
file folder
3.6.3
Display OSPF adjacency

state
show ip ospf nei
Display BGP adjacency

state
show ip bgp sum
Display
PIM-SM
adjacency information
show ip pimsm nei
Display multicast routes
show ip mroute
Display MPLS forwarding

table
show mpls for
Display the system clock
show clock
Checking Services
Check running status 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.
3.6.4
Checking FLASH Free Space

Before the upgrade, make sure that enough flash free spac e is reserved for the new
version. If not enough, delet e 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 the
background FTP server, and then deleted from the FLAS H.
1.
Check Flash free space
ZXR10#dir
Directory of flash:/
attribute
size
date
time
name
drwx
2048
Jan-01-2000
00:00:24
drwx
Jan-01-2000
00:00:26
..
----
131072
Jan-01-2000
00:00:24
capture
-rwx
714664
Mar-23-2012
16:09:47
zdbagent
-rwx
309900
Mar-26-2012
10:54:00
ztam
drwx
2048
Sep-10-2012
16:10:09
img
drwx
2048
Jan-04-2013
09:14:38
data
----
393152
Jan-01-2000
00:00:33
record
drwx
2048
Jan-11-2013
14:11:27
cfg
10
drwx
2048
Jan-01-2000
00:00:03
lost+found
264241152 bytes total (123305269 bytes free)
10
2.
Internal Use On
ly
Delet e useless files
ZXR10#cd cfg
ZXR10#dir
Directory of flash:/cfg
attribute
size
date
time
name
drwx
2048
Jan-11-2013
14:11:27
drwx
2048
Jan-01-2000
00:00:24
..
----
3233
Jan-11-2013
14:11:27
startrun.dat
-rw-
7177
Jul-03-2012
10:21:00
lacpv6.dat
-rw-
8185
Jul-03-2012
08:44:20
mc234.dat

ZXR10#delete lacpv6.dat
Are you sure to delete files?[yes/no]:y
Start deleting file
deleting /flash/cfg/lacpv6.dat..
....
file deleted successfully.
11
Internal Use On
ly
Bootrom Upgrade
Please skip this chapter if the boot rom doesnt need to be upgraded.
This chapter covers precautions, upgrade procedures, emergency handling and bootrom
burning proc edures.
4.1
Precautions
ZXR10 5960&5900E switches support live upgrade of the bootrom. In the upgrade, the
following items should be noted:
1.
Never upgrade the boot rom online when CP U utilizations are high;
2.
Never power off the system during the live upgrade of the boot rom, otherwise the
system will be unable to start.
3.
Precautions for the bootrom upgrade are as follows:

i.
The 108CP U sub-cards of 5960 and 5900E are both set with bootrom
master/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 the
bootrom 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 to
start, so as to make sure that the devic e can restore basic operation.
12
4.2
Internal Use On
ly
Upgrade Flow
Figure 4-1
Bootrom Upgrade Flow

Start
Delete the remaining boot file
Copy boot file
Update bootrom
Verify upgrade
End
4.3
Record of Upgrade Process

During the bootrom upgrade, operations should be made step by step. Record the
implementation of each step, as shown in Table 4-1.
Table 4-1
Boot rom Upgrade Proc ess

Step
S/N
4.4
Delete
Files
Remaining
Copy Boot Files
Upgrade the Bootrom
Verify Upgrade
Completed
or Not
Record of Implementation
Boot
Upgrade Procedure
Detailed upgrade steps are as follows.
13
ZXR10 5960&5900E V2.09.10 Ethernet Switch Version Upgrade Gui de
4.4.1
Internal Use On
ly
Deleting Remaining Boot Files

Before the upgrade, the bootrom file of the old version under img directory should be
deleted.
ZXR10#cd img
ZXR10#dir
attribute
size
date
time
name
drwx
2048
Sep-10-2012
16:10:09
drwx
2048
Jan-01-2000
00:00:24
..
-rwx
15990287
Jul-03-2012
15:42:51
16p01.zar
-rwx
16423968
Jun-14-2001
02:16:46
B2.zar
-rwx
16279272
Mar-16-2012
09:25:03
zxr10.zar04
-rwx
16298516
Apr-26-2012
17:30:03
zxr10.zar07
-rw-
17216928
Nov-12-2012
15:39:42
B8.dat
-rwx
16939008
Dec-10-2012
09:36:01
B10.zar
-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.bin
Are 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 on
the 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:
14
Internal Use On
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
attribute
size
date
time
name
drwx
2048
Jan-11-2013
14:38:08
drwx
2048
Jan-01-2000
00:00:24
..
-rw-
650144
Jan-11-2013
14:38:10
bootrom.bin
-rwx
15990287
Jul-03-2012
15:42:51
16p01.zar
-rwx
16423968
Jun-14-2001
02:16:46
B2.zar
-rwx
16279272
Mar-16-2012
09:25:03
zxr10.zar04
-rwx
16298516
Apr-26-2012
17:30:03
zxr10.zar07
-rw-
17216928
Nov-12-2012
15:39:42
B8.dat
-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 the
software package.
After copying, execute the dir img command to check whet her the boot file size is
consistent 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

Creation Date
: 2012/1/15
Slave Zone Version

Creation Date
: V3.14
: 2012/1/15
The device boot from slave boot zone this time. ---The currently used zone is the slave
zone.
15
1.
Internal Use On
ly
Enter the implicit mode of the system
ZXR10#olleh
zxr10(config-increte)#
2.
Upgrade the Bootrom
ZXR10(config-increte)#bootrom update
If t he update succeeds, the system will give out a message to indicate that the update is
successful.
Tip:
If it shows that the update fails, please delete the corresponding boot file under the img
directory and recopy a new one to perform the update again. If the upgrade still fails after
several times of attempts, replace bootrom chip of corresponding card manually.
4.4.4
3.
Press ctrl+z to quit the implicit mode
4.
Exit the implicit mode and restart the device.
Verifying Upgrade
After updating the boot, check whet her the boot has been updated:
ZXR10#show bootrom
Creation Date
: 2011/8/5
Master Zone Version : V3.33 -----the zone where the boot should be updated
Creation Date
: 2013/1/11
Slave Zone Version

Creation Date
: V3.14
: 2012/1/12
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 this
example, the currently used zone is slave while the idle zone is master. Hence, it is the
master zone that is updated.
4.4.5
Sync of bootrom Zones

After downloading the soft ware version of the device and starting the switch successfully,
the zone where the boot is not updated will become the idle zone. And then, it is
necessary to update this boot manually.
Enter the implicit mode of the system to update the boot:
16
Internal Use On
ly
ZXR10(config-increte)#bootrom update
After that, check whether the boot of master and slave zones has been updated successfu
lly:
ZXR10#show bootrom
Creation Date
: 2011/8/5
Master Zone Version : V3.33

Creation Date
: 2013/1/11
Slave Zone Version

Creation Date
: V3.33
: 2013/1/11
The device boot from master boot zone this time.
17
Internal Use On
ly

This chapter examines precautions, upgrade procedures, and inspection & test after the
upgrade.
5.1
5.2
Precautions
1.
Set the aut o-logging function of the t erminal software before the upgrade for later
analysis of the reason behind the unexpected upgrade failure;
2.
During the process of writing the version int o the FLASH, never restart the device or
power it off, otherwise the FLAS H may be damaged;
3.
During the process of writing the version into the FLASH, CP U utilization will rise, so
it is forbidden to implement other operations on the de vice.
4.
Troubleshooting principle for unexpected accident is to recover services as soon as

possible before locating the failure cause. And meantime, during the period of
upgrade request, try to collect information as much as possible for subsequent
analysis;
5.
For unexpected situations that cannot be solved, please contact instructors of

Customer Service Department of Wired Network Service Center.
Upgrade Flow
Figure 5-1 depicts the software version upgrade flow.
18
Figure 5-1
Internal Use On
ly
Soft ware Version Upgrade Flow

Start
Delete the old version file
Download target version file
Check boot mode
Reboot switch
Check boot status of device
Check new version

information
Check configuration
information
Verify upgrade
End
5.3
Record of Upgrade Process

During the soft ware version upgrade, operations should be made step by step. Record
the implementation for each step, as shown in Table 5-1.
Table 5-1
Software Version Upgrade Process

Step
S/N
1
Rename Old Version File
Download Target Version

File
Check Boot Mode
Completed
or Not
19
Step
S/N
5.4
Restart Switch
Check
Device
Check
New
Information
Check
Information
Verify Upgrade
Boot
Completed
or Not
Status
Internal Use On
ly
of
Version
Configuration
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
Delet e 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 of
the 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
20
Internal Use On
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 whet her t he version file size is
consistent with that on FTP server.
ZXR10#dir
attribute
size
date
time
name
drwx
2048
Jan-11-2013
14:43:32
drwx
2048
Jan-01-2000
00:00:24
..
-rw-
16950384
Jan-11-2013
14:44:25
zxr10.zar
-rwx
16003448
Jan-11-2013
13:56:16
backup.zar
-rw-
650144
Jan-11-2013
14:38:10
bootrom.bin
-rwx
15990287
Jul-03-2012
15:42:51
16p01.zar
-rwx
16423968
Jun-14-2001
02:16:46
B2.zar
-rwx
16279272
Mar-16-2012
09:25:03
zxr10.zar04
-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 it
to the local boot, and save the configuration:
ZXR10(config)#nvram imgfile-location local
ZXR10(config)#exit
ZXR10#write
21
ZXR10 5960&5900E V2.09.10 Ethernet Switch Version Upg rade Guide
5.4.4
Internal Use On
ly
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 file
backup.zar.
5.4.5
Restarting the Switch

Run the command reload to restart the device, or press the power switch at the back of
the 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 should
be enabled to rec ord the upgrade and restart process of the devic e.
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 old
version.
5.4.6
Checking Boot Status

After the device starts successfully, check the status of the indicators and CPU utilization
to make sure that the devic e is running normally.
ZXR10#show processor
PhyMem: Physical memory (megabyte)
Panel
CPU(5s) CPU(1m) CPU(5m)
PhyMem
Buffer
Memory
22
MP(M)
28%
26%
48%
512
0%
Internal Use On
ly
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 is
the 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:</flash/img/zxr10.zar>

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 configuration
information. Compare it with the configuration information backed up before upgrade to
see whether there are any differences.
In case configuration commands for the new version have changed, you should complete
the configuration fast according to configuration commands before the upgrade.
If the configuration information is long, it is recommended to use the Araxis merge to
compare the configuration information aft er and before the upgrade, in order to find the
differenc es effectively and timely.
5.4.9
Verifying Upgrade
Items to be verified after the upgrade should be substantially identical to that before the
upgrade, which mainly covers the following parts:
23
1.
Internal Use On
ly
Check the hardware running state

Check whether the system hardware after upgrade works normally and whether the
panel indicators are in normal status.
2.
Check the system running state

Check the running state information of the system after the upgrade, and compare it
with the information recorded before the upgrade to see whether it is normal. The
main items to be checked are as shown in Table 3 -2. It is necessary to add or delete
some 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 minutes, the upgrade is regarded failed. Refer to Emergency Handling
to roll back to the old version.
24
Internal Use On
ly
Version Rollback
This chapter describes specific rollback steps for diverse situations.
6.1
Rollback Application
If the upgrade fails, you s hould perform the version rollback. You s hould take different
rollback steps for different failures.
The device 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 boot rom version of V2823C. For details, refer to 6.4.
Note:
If the rollback fails, or an accident occurs, please contact instructors from Customer Service
Department.
6.2
Failure to Start the Dev ice Normally

If the device cannot start with the new version, the upgrade is thought failed. You can roll
back 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 net work through management port. Before
that, 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 countdown
period, and then modify boot parameters.
ZXR10 Switch System Bootstrap

ZXR10 5952E-ELEC System BootRom Version: V0.22
25
Creation date: Jan
Internal Use On
ly
7 2013, 09:00:43
Copyright (c) 2013 by ZTE Corporation.

Hit any key to stop auto-boot:
[boot]: c
'.' = clear field;
'-' = go to previous field;
'^' = quit
Boot Location [0:Net,1:Flash] : 0

Client IP
//0 means boot from the network
: 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
: 169.1.3.12
//The gateway address is the interface
server
Gateway IP
address of port number
FTP User
: ztezte
//The FTP username is ztezte
FTP Password
//The password of the username ztezte
Bootfile
: zxr10.zar
Enable Password
//The network boot path
//A default value
[boot]:
3.
Restart the switch

Restart the device in boot mode. The system downloads the old version from the
background 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 s witch, check whet her t he version number is the old version
number and whether the servic es are normal.
5.
Copy the version to the FLAS H
26
Internal Use On
ly
After making sure that the device and services work normally, delete the version
with a problem during the upgrade, and writ e the normal version file to the directory
img 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 Serv ices

If the device starts normally with the new version, but the services run abnormally, then
the upgrade is regarded failed. Roll back to the old version according to the following
steps.
1.
Delet e the new version file that is copied to the img directory of FLASH during the
upgrade, 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 before
upgrade, 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
27
Internal Use On
ly
After restarting the s witch, check whet her t he version number is the old version
number and whether the servic es are normal.
6.4
Serv ices Abnormal After

Upgraded into V2.09.10
V2.8.23C
Being
After the onsite devices are upgraded from V2.8.23C to V2.09.10, if the services become
abnormal, it is necessary to roll back the software version and bootrom version.
In this scenario, the rollback procedures are slightly different from the upgrade
procedures. To go back to the V2.8. 23C, first roll back the bootrom version and then the
software version. Follow the steps below for rollback.
1.
Delet e the new version file copied to the IMG directory of the flash during the
upgrade, 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 the
devic 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 the
inter-version upgrade or degrade.
28
Internal Use On
ly
Frequently Asked Questions

This 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 implement
sophisticated operations, nor view t he content on the FLAS H, for they will affect the
writing. During the process of write imgfile, never power off, otherwise the FLASH
may 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 could
not start normally.
3.
Q: When an accident occurs, what information needs being collected for further
analysis?
A: Printing information on the serial port, alarming information on the device and
basic 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 are
in.
4.
Q: In the process of V 2.8.23B being upgraded into V 2.8.23C, after the Boot rom
online upgrade is finished, you can find the version ID doesnt change while the
creation time changes by executing the show bootrom command.
A: This problem is the data reading problem in the bootrom updat e of the V2.8.23B.
It has no influence on the bootrom version update. You can check the bootrom state
after the device is restarted to see whether the bootrom updat e is successful.
29
Internal Use On
ly
AppA Usage Guideline for Common Terminal

Software and FTP Software
Terminal Software
A.1
Common terminal soft ware includes HyperTerminal and Sec ureCRT. Here, we will
introduce how to set the two types of software. Items to be set contain:
A.1.1
Port attribute
Automatic logging function
HyperTerminal
The HyperTerminal is usually used for the serial port connection. The following describes
the setting for it.
A.1.2
1.
Click [Start>Programs>Accessories>Communications>HyperTerminal] in the

operating system. The HyperTerminal main interface and [Connection Description]
dialog box pop up.
2.
Type the name of the connection in <Name> of [Connection Description] dialog box,
and click <OK>. The [Connect To] dialog box will be presented.
3.
Select the COM port in <Connect using> option of [Connect To] dialog box for the
host to connect to the device and click the OK. [COM Properties] dialog box pops
up.
4.
Click <Restore Defaults (R)> in <COM Properties> dialog box, modify <Bits per
second (B )> as required, click <OK> to finish the setting and ent er HyperTerminal
main interface.
5.
If it is nec essary to record operation logs, click [Trans fer (T)] menu and select [Text
Capt ure (C)]. Then the [Text Capture] dialog box pops up. Select log file in the
dialog box and click <Start> to finish the setting.
SecureCRT
SecureCRT is commonly used for the serial port connection and telnet connection.
1.
Run the S ecureCRT software. The SecureCRT main interface and [connect] dialog
box will pop up.
30
Internal Use On
ly
If [connect] dialog box is closed, you can click the first button <Connect> on the tool
bar of the main interface or select [Connect] in [File] menu to open it.
2.
Click the third button <New S ession> on the tool bar of [ Connect] dialog box to
establish 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 devic e
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 <OK> to finish the setting and enter Sec ureCRT main interface.
4.
A.2
If it is necessary to record operation logs, click [File] menu, and select [Log Session].
And the corresponding dialog box pops up. Select the log file in the dialog box and
click <Save (S)> to finish the setting.
FTP Tool
Common FTP server tools include 3CDaemon and WFTPD. The following will introduce
how to set the two types of soft ware. Items to be set contain:
FTP username/password
Directory on the server used for storing the version file or configuration file
31
Internal Use On
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 b ox pops up. Then perform the following
operations:
i.
Type username, e.g. target in the above input box;
ii.
Click <Set/Change users password> to set the password;
iii.
In the input box below, type directory, e.g. IMG directory of Disk D used for
saving version file or configuration file, or click the button on the right of the
input box to select the directory;
iv.
Select Login, Download and Upload in the list below < This user can:>;
v.
Click <Application (A)> to finish the setting.
This is shown in AppendixPic A-1.
AppFigure A-1
3CDaemon Window
32
A.2.2
Internal Use On
ly
WFTPD
1.
Run wftpd software on the background host.
2.
Click [Security] in the menu, select [User/Rights]. And [User/Rights Security

Dialog] dialog box pops up. Then perform the following operations:
3.
i.
Click <New Us er...> to create a user, such as target, and set a password.
ii.
Select user name "target" in the <User Name> drop-down box;
iii.
Type in a directory in the <Home Directory> box, such as, the IMG directory on
Disk D to save version file and configuration file.
Click <Done> to complete the setting.
AppFigure A-2
A.3
WFTP D Window
Araxis merge
Araxis merge is a file comparison tool. During the version upgrade, it is commonly used
to 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 main
interface is divided into two parts: left and right. Each part has an input box,
displaying Y ou can type a filename here.
33
2.
Internal Use On
ly
Click the button <...> on the right of each input box respectively, and select two files
that needs to be compared. The selected files are displayed on the two sides of the
main interface, and the different places are clearly marked.
AppFigure A-3
Araxis merge Window
34

ZTE ZXR10 5960&5900E V2.09.10 Ethernet Switch Version Upgrade Guide - R1.0 - 560843

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ZTE ZXR10 5960&5900E V2.09.10 Ethernet Switch Version Upgrade Guide - R1.0 - 560843

Transféré par

Droits d'auteur :

Formats disponibles

ZXR10 5960&5900E

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

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

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

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

Reason for Revi sion

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

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

Commissioning and maintenance engineers

Knowledge and skill s

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

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

About This Document

Describes software version status .

Introduces software version upgrade flow.

Preparation before Upgrade

Describes preparations before upgrade.

Describes bootrom upgrade precautions, upgrade procedures,

Software Version Upgrade

Describes software version upgrade precautions,

Describes specific rollback steps for different situations .

Frequently Asked Questions

Describes the frequently asked questions .

AppA Usage Guideline for

ZTE Confidential Proprietary

Describes how to set and use common upgrade software.

2014 ZTE CORPORATION. All rights reserved.

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

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

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

Preparation before Upgrade .............................................................................. 2

Bootrom Upgrade ............................................................................................... 8

Software Version Upgrade ............................................................................... 12

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

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

Version Rollback ............................................................................................... 17

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

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

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

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

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

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

ZXR10 5960-32DL, 5960-64DL

The File List

Product Series/Model/Board That It Fits

Version & boot

ZXR10 5960 series

Version & boot

ZXR10 59E series CPU sub-card is xls108

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

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

Version Upgrade Flow

Preparation before Upgrade

Software Version Upgrade

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.