ZXR10 5250&5200E&2900E Ethernet Switch Version Upgrade Guide - R1.3

ZXR10 5250&5200E&2900E
R1.3
Ethernet Switch Version
Upgrade Guide
ZXR10 5250&5200E&2900E Ethernet Switch Version Upgrade Guide Internal Use Only
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION 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 2016 ZTE CORPORATION. Any rights not expressly granted herein are
reserved. This document 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 any means, 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 ZTE CORPORATION. Other product and company names mentioned
herein may be trademarks or trade names of their respective owners. Without the prior
written consent of ZTE CORPORATION 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 marks appearing in the document.
The design of this product 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 country
(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 ZTE CORPORATIONs products and technologies.
ZTE CORPORATION
Addres
s:
Websit
e:
Email:
NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
http://dms.zte.com.cn (TSM-Technical Support)
TSM.Aftersales@zte.com.cn
ZTE Confidential Proprietary
2016 ZTE CORPORATION. All rights reserved.
Revision History
Product Version
Document Version
Serial Number
Reason for Revision
R1.0
First published
R1.1
Updated the products
R1.2
R1.3
Author
Date
Document Version
Prepared by
2012-3-2
R1.0
Huang Zhiyan
2013-5-31
R1.1
Huang Zhiyan
2014-4-29
R1.2
Huang Zhiyan
2015-4-19
R1.3
Huang Zhiyan
Reviewed by
Approved by
II
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
III
About This Document

Summary
Chapter
Description
1 Version Information
Describes software versions.
2 Upgrade Flow
Describes software version upgrade flow.
3 Preparation before Upgrade
Describes preparations before upgrade.
4 Bootrom Upgrade
Describes precautions and upgrade procedures for the

bootrom upgrade.
5 Software Version Upgrade
Describes software version upgrade precautions, upgrade

procedures, and inspection & test after upgrade.
6 Version Rollback
Describes version rollback steps.
AppA Usage Guideline for Software

Tools
Describes how to set and use common upgrade software.
IV
TABLE OF CONTENTS
1
Version Information.........................................................................................1
Upgrade Flow...................................................................................................3
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............................................................................5

Preparation Records before Upgrade................................................................5
Reading Version Accompanying Documents......................................................5
Preparing Software and Hardware.....................................................................6
Setting up an Upgrade Environment..................................................................6
Backing up Data.................................................................................................7
Backing up Configuration Files..........................................................................
Backing up Version Files....................................................................................
Checking Running State....................................................................................9
Checking Hardware Running State....................................................................
Checking System Running State.......................................................................
Checking Services...........................................................................................
Checking FLASH Free Space..........................................................................
4
4.1
4.2
4.3
4.3.1
4.3.2
4.3.3
4.3.4
Bootrom Upgrade...........................................................................................11
Upgrade Process.............................................................................................11
Record of Upgrade Process.............................................................................12
Upgrade Procedure..........................................................................................12
Deleting Remaining Boot Files.........................................................................
Downloading New Boot Files...........................................................................
Updating Bootrom............................................................................................
Verifying Upgrade............................................................................................
5
5.1
5.2
5.3
5.4
5.4.1
5.4.2
5.4.3
5.4.4
Software Version Upgrade............................................................................14

Precautions......................................................................................................14
Upgrade Flow...................................................................................................14
Record of Upgrade Process.............................................................................15
Upgrade Procedure..........................................................................................16
Renaming Old Version Files.............................................................................
Downloading Target Version Files....................................................................
Restarting Switches.........................................................................................
Verifying Upgrade............................................................................................
6
6.1
6.2
6.2.1
6.2.2
Version Rollback............................................................................................18
Rollback Application.........................................................................................18
Failure to Boot Devices....................................................................................18
Procedures for Version Upgrade from Network................................................
Version Upgrade in BootManager Mode..........................................................
AppA
A.1
Usage Guideline for Software Tools.............................................................23

Terminal Software............................................................................................23
A.1.1
A.1.2
A.2
A.2.1
A.2.2
A.3
A.3.1
A.3.2
A.4
HyperTerminal..................................................................................................
SecureCRT......................................................................................................
TFTP Tool........................................................................................................ 24
3CDaemon.......................................................................................................
TFTP................................................................................................................
FTP Tool........................................................................................................... 26
3CDaemon.......................................................................................................
WFTPD............................................................................................................
Araxis merge....................................................................................................28
VI
FIGURES
Figure 2-1 Version Upgrade Flow...........................................................................................3
Figure 4-1 Bootrom Upgrade Flow........................................................................................11
Figure 5-1 Software Version Upgrade Flow..........................................................................15
TABLES
Table 1-1 Product Model.........................................................................................................1
Table 1-2 The File List............................................................................................................ 2
Table 3-1 Preparation Records before Upgrade......................................................................5
Table 3-2 Checklist of System Running State.........................................................................9
Table 4-1 Bootrom Upgrade Process....................................................................................11
Table 5-1 Software Version Upgrade Process.......................................................................15
VII
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 5250&5200E&2900E series switches include multiple models of
products, as shown in Table 1 -1.
Table 1-1 Product Model

Product
Model
5250-28SM
5250-28TC/
5250-28TC-H/
5228E-C
5250-52TC/
5250-52TC-H/
5252E-C
5250-28PM/
5250-28PM-H/
5228E-PS
Length
(mm)
442
442
442
442
Width
(mm)
440
220
220
220
Height
(mm)
Port Type
43.6
Dual power
module, AC or
DC
24*1000M SFP, 1*
expansion card,
4*GE SFP, or 4*GE
RJ45
43.6
Single power
module, AC or
DC, supporting
RPS
24*1000M
electrical
ports+2*1000M
combo ports+2GE
SFP
43.6
Single power
module, AC or
DC, supporting
RPS
48*1000M
electrical
ports+2*1000M
combo ports+2GE
SFP
43.6
Support POE
power
supply.Support
802.3at and
802.3af.
Support AC and
RPS.
20*1000M
electrical ports,
+4*1000M combo
ports,1*expansion
card, 4*10GE
SFP+, or 4*GE
SFP, or 4*GE RJ45
5250-52PM/
5250-52PM-H/
5252E-PS
442
440
43.6
5250-28TS-L
442
220
43.6
Power Module
Dual power
module, AC or
DC
Support both AC
and DC. The AC
power
supply
supports DC 380V
input.
The
AC
supports the power-
48*1000M
electrical ports,
1*expansion card,
4*10GE SFP+, or
4*GE SFP, or 4*GE
RJ45
24*1000M
electrical
ports4*GE SFP
Product
Model
5250-28SM
5250-52TS-L
5250-12TC
5250-12PC
5250-28PC
5250-52PC
2910E/
2950-10TC
2910E-PS/
2950-10PC
Length
(mm)
442
442
340
340
442
442
340
340
Width
(mm)
440
220
220
220
440
440
220
220
Height
(mm)
43.6
43.6
43.6
43.6
43.6
43.6
Power Module
Dual power
module, AC or
DC
off alarm.
Support both AC
and DC. The AC
power
supply
supports DC 380V
input.
The
AC
supports the poweroff alarm.
Support both AC
and DC. The AC
power supply
supports DC 380V
input. The AC
Support AC (not
supporting 380V
DC input), not
support RPS
Support AC
(supporting 380V
DC input), support
RPS. The AC
Support AC
(supporting 380V
DC input), support
RPS. The AC
24*1000M SFP, 1*
expansion card,
4*GE SFP, or 4*GE
RJ45
48*1000M
electrical
ports4*GE SFP
8* adaptive
10/100/1000
electrical interfaces.
2*GE electrical
interfaces, 2*GE
optical interfaces
8*adaptive
10/100/1000
electrical interface,
2*GE electrical
interface, 2*GE
optical interfaces
24*1000base-TX
electrical interfaces,
2GE combo, 2 SFP
gigabit optical
interfaces
48*1000base-TX
electrical interfaces,
2GE combo, 2 SFP
gigabit optical
interfaces
43.6
Support both AC
and DC. The AC
power supply
supports DC
380V input. The
AC supports the
power-off alarm.
8*adaptive 10/100
electrical
interfaces, 2*GE
combo interfaces
43.6
Single power
module,
supporting AC
8*100M electrical
ports, supporting
POE; 2*1000M
combo ports
16*100M electrical
ports, supporting
POE; 2*1000M
combo ports
16*100M electrical
2918E-PS/
2950-18PC
442
220
43.6
AC power,
supporting RPS
input. After RPS
input is enabled,
only RPS power
can be received
2918E/
442
220
43.6
Single power
Port Type
Product
Model
Length
(mm)
Width
(mm)
Height
(mm)
Power Module
Port Type
Dual power
module, AC or
DC
24*1000M SFP, 1*
expansion card,
4*GE SFP, or 4*GE
RJ45
2950-18TC
module, AC or
DC
ports; 2*1000M
combo ports
2928E/
2950-28TC
Single power
module, AC or
DC
24*100M electrical
ports; 2*1000M
combo ports;
2*1000M optical
ports
5250-28SM
442
442
440
220
43.6
43.6
2928E-PS/
2950-28PM
442
220
43.6
Single power
module, AC or
DC
24*100M electrical
ports, supporting
POE; 2*1000M
combo ports;
2*1000M optical
ports
2952E/
2950-52TC
442
280
43.6
Single power
module, AC or
DC
48*100M electrical
ports; 4*1000M
optical ports
43.6
Dual power
modules,
interchangeable,
not supporting
RPS
48*adaptive 10/100
electrical
interfaces, with the
extension card of
4*FE SFP, or 4*GE
SFP, or 4*GE RJ45
2952E-PS/
2950-52PM
442
440
The software package for ZXR10 5250&5200E&2900E Series switches

contains many files. Refer to Table 1 -2 for the list of the files.
Table 1-2 The File List

File Type
File Name (Including Path)
Product
Series/Model/Board
That It Fits
zImage
Software version
file
5250&5200E&2900E
series
bootrom.bin
BOOT file
5250&5200E&2900E
series
Upgrade Flow
Figure 2 -1 depicts the upgrade flow of ZXR10 5250&5200E&2900E Series
switches.
Figure 2-1 Version Upgrade Flow
1.
Preparation before Upgrade

Preparations should be made in advance. For detailed information, refer
to 3 Preparation before Upgrade.
2.
Bootrom Upgrade
Before preparation, make clear whether Bootrom 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.
Software Version Upgrade

Refer to 5 SOFTWARE VERSION UPGRADE for upgrading software
versions. 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 15 minutes.
Preparation before Upgrade

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.
Prepare items according to the Table below. Record whether each of them has
been completed and write down the preparation for each item.
Table 3-3 Preparation Records before Upgrade

S/N
3.2
Completed or
Not
Item
Read
version
documents
Prepare software and hardware
Set up upgrade environment
Back up configuration information
Back up version file
Check running status of hardware
Check running status of system
Check services
Check FLASH free space
Record of Preparation
accompanying
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 Release Instruction

Read the Version Release instruction mainly for the following information:
2.
Whether the bootrom needs to be upgraded;
Whether configuration commands of the target version change;
Version Upgrade Guide
Read it to have a good grasp of the precautions and the 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 network 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 whether 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 TFTP tool software necessary for upgrade, and check if it is

usable;
Prepare the tool Araxis merge for comparing pre/post-upgrade

configuration information.
Setting up an Upgrade Environment

ZXR10 5250&5200E&2900E supports both local and remote upgrade.
If the quantity of 5250&5200E&2900E is huge, and workload of upgrade is
heavy, you can use the remote upgrade. The EasyManager tool can be used
in batch remote upgrade. For details, refer to the NetNumen EasyManager
Serviceability Software Package User Manual.
1.
Set up a local upgrade environment

i.
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
attributes:
Bits per Second (baud rate): 9600
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None
After the configuration, make sure that access to the device is available
via the serial port. Next, enable automatic logging function for the
terminal software.
For detailed setting method, refer to A.1 Terminal Software.
ii.
Network Cable Connection

Connect the network port of the PC to the Ethernet port of the
switch via a 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.
iii.
Start the TFTP Server

Refer to A.2 TFTP Tool for how to set common software tools of the
TFTP server.
2.
Set up a remote upgrade environment

i.
Network Cable Connection

Use a network cable to connect the network port of the PC to the
network. Make sure the PC can ping through the switch EMS
address. The PC telnets the IP of the device and can log in it
successfully.
ii.
Start the TFTP Server

It is preferable to implement the version upgrade when the service
traffic is small. For how to set software tools of the TFTP server, refer
to the A.2 TFTP Tool.
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 for the convenience of data restoration after the upgrade.
1.
Check current configuration of the device and save the displayed configuration to
the background server.
zte(cfg)#show running-config
2.
Save the current configuration and make sure that it is saved properly.
zte(cfg)#wr
Saving file, please wait a minute...
Done !
zte(cfg)#
zte(cfg)#con tffs
zte(cfg-tffs)#cd cfg
zte(cfg-tffs)#ls
/cfg/
.
<DIR>
..
<DIR>
startrun.dat
1,945 bytes
255,885,312 bytes free

zte(cfg-tffs)#
3.
Back up the configuration file to the background TFTP server.

Upload the startrun.dat configuration file:
zte(cfg-tffs)#tftp 10.40.188.135 upload
3.5.2
startrun.dat
Backing up Version Files

If the upgrade fails, the old version should be used to restore the operation.
Therefore, it is important to back up the version file.
1.
View current version file on the device.
zte(cfg-tffs)#cd img
zte(cfg-tffs)#ls
/img/
<DIR>
..
<DIR>
zImage
7,573,860 bytes
2.
Back up the version file to the background TFTP server

Upload the version file. Then, find the file in the specified directory. If its
size is the same to that on the device, it means the backup is successful:
zte(cfg-tffs)#tftp 10.40.188.135 upload zImage
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 sure that there is no latent risk.
Execute the commands below to check the device state:
show port
show cpu
show memory
If the port state is normal, and memory and CPU usages are normal, it means
the device is working properly.
The memory is reserved by the software for tasks and protocols in advance.
Normally, it is in range of 50-70%.
The normal CPU usage is below 20%.
3.6.2
Checking System Running State

Check the running state 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 -4. Yet, it is necessary to add or delete some of the
items according to the actual needs on site.
10
Table 3-4 Checklist of System Running State

Item
3.6.3
Command
Display the software

and boot versions of a
system
show version
Display the current

configuration file
show running-config
Display the CPU

usage
show cpu
Display the memory

usage
show memory
Display routing
information
show iproute
Display port status

statistics
show port <port-name/port-list>

brief
Display port traffic

statistics
show port<port-name/port-list>
statistics
Display layer-3 port

information
show ipport
Display MAC
forwarding table
information
show mac
Display ARP table

information
show arp
Display log alarms
show terminal log
Display system time
show date-time
Remark
Checking 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.
3.6.4
Checking FLASH Free Space

Before the upgrade, make sure that enough flash free space is reserved for
the new version. If not enough, delete some useless files.
zte(cfg-tffs)#ls
/img/
.
<DIR>
..
<DIR>
11
zImage
7,573,860 bytes
zte(cfg-tffs)#remove zImage
Enter [Yes] to remove(other keys are [No]):y
Done!
12
Bootrom Upgrade
This chapter covers precautions and upgrade procedures for the bootrom
upgrade. ZXR10 5250&5200E&2900Es BOOT is welded on the PCB
motherboard as a whole and thus its hardware could not be replaced
separately. Therefore, during the upgrade of the bootrom, make sure the
power supply for the device is normal, and no mis-operation occurs.
Please skip this chapter if the bootrom doesnt need to be upgraded.
Note:
The version V2.05.11B19 solves the data bit error on the boot area of the flash.
In engineering, when the equipment is upgraded from V2.05.11B18 or an earlier version to
V2.05.11B19 or a later version, it should be noted that, first upgrade the software version,
then restart the equipment, and then upgrade the bootrom in OAM interface.
For V2.05.11B19 and later versions, there are no such restrictions during the version
upgrade.
4.1
Upgrade Process
Figure 4-2 Bootrom Upgrade Flow
13
4.2
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 -5.
Table 4-5 Bootrom Upgrade Process

S/N
4.3
Step
Delete Remaining Boot Files
Copy Boot Files
Upgrade the Bootrom
Verify Upgrade
Completed or
Not
Record of
Implementation
Upgrade Procedure
Detailed upgrade steps are as follows.
2900E switches cannot upgrade their bootrom from V2.3.11 or V2.3.10 into
V2.05.11, V2.05.12 in BootManager mode. The upgrade must be done in OAM
mode. The V2.05.10,V2.05.11 and V2.05.12 version upgrade support both
OAM and BootManager modes.
4.3.1
Deleting Remaining Boot Files

Before the upgrade, the bootrom file of the old version under img directory
should be deleted.
zte(cfg-tffs)#remove bootrom.bin
Enter [Yes] to remove(other keys are [No]):y
Done!
4.3.2
Downloading New Boot Files

Before the upgrade, it is necessary to download boot file bootrom.bin needed
for the upgrade to the FLASH of the switch. After the downloading, execute
the command ls to check whether the boot file size is consistent with that on
the TFTP server.
zte(cfg-tffs)#tftp 10.40.188.135 download bootrom.bin //10.40.188.135 is TFTP server address
Note:
14
Filename and file size of the boot saved to the FLASH must be correct and identical to that
in the software package.
4.3.3
Updating Bootrom
Execute the command update bootrom to update the bootrom. If no error is
presented, it indicates the update succeeds.
zte(cfg-tffs)#update bootrom
Note:
If you are prompted for update failure, please delete the boot file and re-download a new
boot file and then update it again.
If the update still fails after several attempts of updates, it is necessary to make sure that the
device will not be restarted. The device needs to be replaced manually in the future.
4.3.4
Verifying Upgrade
1.
Make sure that the new version file is included on the flash.
2.
Restart the switch.
After starting the device normally, execute the command show version to
check the boot version after being updated. If the creation time of the new
version boot is shown, it is sure that the bootrom upgrade is successful.
zte(cfg)#show version
ZXR10 Router Operating System Software, ZTE Corporation:
ZXR10 2928E Version Number : 2900E Series V2.05.10.04
Copyright (c) 2001-2012 By ZTE Corporation
Compiled: 09:47:37 Feb 13 2012
System uptime is 0 years 0 days 0 hours 0 minutes 19 seconds
Main processor
: arm926ejs
Bootrom Version
: V1.19
System Memory
Creation Date : Jun 30 2011
: 128 M bytes System Flash : 256 M bytes
EPLD Version (Dno.) : V1.1

PCB Version (Dno.) : V1.0
Startup From
: /img/zImage
Switch's Mac Address: 00.22.93.57.13.1c

Module 0:
ZXR10 2928E; fasteth: 24; gbit: 4;
15
Software Version Upgrade

This chapter examines precautions, upgrade procedures, and inspection &
test after the upgrade.
5.1
5.2
Precautions
1.
Set the auto-logging function of the terminal software before the upgrade for later
analysis of the reason behind the unexpected upgrade failure;
2.
During the process of writing the version into the FLASH, never restart the device
or power it off, otherwise the FLASH may be damaged;
3.
During the process of writing the version into the FLASH, CPU usage will rise,
which is normal.
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
requesting the upgrade, try to collect information as much as possible for
subsequent analysis;
5.
For unexpected situations that cannot be solved, please contact instructors of the
Wired Network Service Center.
Upgrade Flow
Figure 5 -3 depicts the software version upgrade flow.
16
Figure 5-3 Software Version Upgrade Flow
5.3
Record of Upgrade Process

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

S/N
Step
Delete old version files (or

rename them if there is
sufficient space)
Download target version files
Restart switches
Check information of new

versions
Check configuration
information
Verify upgrade
Completed or
Not
Record of
Implementation
17
5.4
Upgrade Procedure
Detailed upgrade steps are as follows.
5.4.1
Renaming Old Version Files

Rename the version file of the device:
zte(cfg-tffs)# rename zImage oldzImage
Delete the old version file if the FLASH cannot accommodate two versions:
zte(cfg-tffs)#remove zImage
5.4.2
Downloading Target Version Files

Download the target version file from the TFTP server to the FLASH of the
switch.
zte(cfg-tffs)#tftp 10.40.188.135 download zImage
After downloading, execute the command ls to check whether the version file
size is consistent with that on the TFTP server.
zte(cfg-tffs)#ls
/img/
.
<DIR>
..
<DIR>
bootrom.bin
zImage
755,036 bytes
9,146,280 bytes
Note:
The name of the target version file saved to the FLASH must be zImage, case sensitive.
5.4.3
Restarting Switches
Execute the command reboot to restart the switch or power if off on site to
restart it again.
The device reboot takes about 5 minutes. During this process, you should
observe status of switch indicators and output information on the serial port.
18
5.4.4
Verifying Upgrade
Items to be verified after the upgrade should be substantially identical to that
before the upgrade, which mainly covers the following parts:
1.
Check the hardware running state

Check whether the system hardware after upgrade works normally and
execute the show command to check running state of ports.
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.
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 the version rollback
chapter to roll back to the old version.
19
Version Rollback
This 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
different rollback steps for different failures.
The device with the new version cannot start normally.

Use the boot via network for rollback. For detailed steps, refer to 6.2.
Services under the new version are abnormal.

Load the old version for rollback. For detailed steps, refer to 5.4.
Note:
If the rollback fails, or an accident occurs, please contact instructors from the Wired Network
Service Center.
6.2
Failure to Boot Devices

If the device cannot start with the new version, you can load the version via
network or upgrade the version in bootmanager mode. Usually the boot via
network is recommended.
6.2.1
Procedures for Version Upgrade from Network

The version boot from the network side loads the version via the tftp.
Set the PC as the tftp server to connect to the service port of the switch;
Start the tftp server;
Restart the switch to enter the boot mode for relevant configuration;
In ordinary mode, execute the command c to set the boot mode to boot
from the network <0>; set the port as port 2 to configure the IP for the
host (PC), IP and mask for the switch.
20
[ZXR10 Boot]: c
boot location [0:Net,1:Flash] : 1
actport
:1
serverip
: 2.2.2.1
netmask
0 //Boot from the network

2 //Select port 2 to interconnect to the tftp server
10.40.89.78
: 255.0.0.0
//IP of the tftp server
255.255.255.0 //The mask of the network where the tftp
server and the client locate

ipaddr
: 2.2.2.2
10.40.89.79
bootfile
: /img/zImage
username
: 111
password
: 111111
MAC
//tftp client IP
//Boot path, ignorable

//tftp mode, ignorable
//tftp mode, ignorable
: 00.22.93.57.13.1c
[ZXR10 Boot]:
After setting boot parameters, type load for loading;
After the Loading is printed, the NIC at the PC side connecting to the
switch changes from
been set up.
into
, which indicates the connection has
[ZXR10 Boot]: load

TFTP from server 10.40.89.78; our IP address is 10.40.89.79
Loading: ####################################################
Uncompressing...........................................................................................................................
...............................................................................................................................................
Done.
The switch's mac address is:00.22.93.57.13.1c
Module 0:
Software Version Number: V2.05.10.04

Software Version Date : Feb 13 2012 09:47:37
Flash file system initializing...
Flash file system initialize passed
Reading config from startrun.dat ...
Execute command from startrun.dat over
************************************************
Welcome to ZXR10 2928E Switch of ZTE Corporation
************************************************
login:
If the boot fails, the system will initiate 5 more connection attempts to
the tftp server. If all the attempts fail again, the system will restart. Now
you should check the network cable, server, port and IP.
Copy the version file after the normal boot;
21
Download the target version file from the TFTP server to the FLASH of the
switch.
zte(cfg-tffs)#tftp 10.40.188.135 download zImage
After the downloading, execute the command ls to check the version file.
Modify the network boot mode;

Because 5250&5200E&2900E in OAM mode cannot modify the boot
mode, after the version boot from the network succeeds and the version
is copied to the flash, it is necessary to restart the device for modifying
the boot mode.
In ordinary mode, use the command c to set the boot mode to local boot
<1>, and restart the device, with the method as follows:
[ZXR10 Boot]: c
actport
:2
serverip
: 10.40.89.78
netmask
//Ignore
//Ignore
: 255.255.255.0
ipaddr
:10.40.89.79
bootfile
: /img/zImage
username
: 111
password
: 111111
MAC
//Ignore
//Ignore
//Ignore
//Ignore
//Ignore
: 00.22.93.57.13.1c
[ZXR10 Boot]: load
6.2.2
//Select boot from network
//Ignore
//Restart the device
Version Upgrade in BootManager Mode

In BootManager mode, the version is loaded through the ftp. This operation is
available on versions V2.05.10, V2.05.11, V2.05.12 only. For 2900E
equipment, due to the differences in the memory handling of the boot file, in
bootmanager mode, the bootrom of V2.3.10 and V2.3.11 versions cannot be
upgraded to that of V2.05.10, V2.05.11, and V2.05.12.
Set the PC as the ftp server to connect to the service port of the switch;
Start the ftp server;
Set boot mode boot parameters;
[ZXR10 Boot]: c
actport
:2
serverip
: 2.2.2.1
1 //Set 1 as local boot

2 //Configure the port on the switch to connect to the FTP
10.40.89.78
//ftp server IP
22
netmask
: 255.0.0.0 255.255.255.0 //The mask of the network where the ftp
server and the client locate

ipaddr
: 10.40.89.79
//ftp client IP
bootfile
: /img/zImage
//Boot path, ignorable
username
: 111
password
: 111111
MAC
target //ftp account

target //ftp password
: 00.22.93.57.13.1c
[ZXR10 Boot]:
Enter the bootmanager mode to delete the old version file;
[ZXR10 Boot]: zte

[BootManager]: cd img
[BootManager]: ls
/img/
bootrom.bin
zImage
755036
9146280
[BootManager]:rm zLmage
Upgrade software version;

In bootmanager mode, enter the management mode to download the
version file. Note that you must go into the img directory for
downloading; otherwise the device cannot start.
[BootManager]: cd img
[BootManager]: ls
/img/
[BootManager]: ftp get zImage
...........................................................................................................................
Ftp get zImage successfully, 9146280 bytes received..
[bootManager]: ls
/img/
bootrom.bin
zImage
755036
9146280
Note:
The above operations must be downloaded from the directory img; otherwise the device
cannot start.
Restart the device to load the version.
[BootManager]: load
23
Uncompressing...........................................................................................................................
................................................................................................................................................
Done.
The switch's mac address is:00.22.93.57.13.1c

Module 0:
Software Version Number: V2.05.10.04

Software Version Date : Feb 13 2012 09:47:37
Flash file system initializing...
Flash file system initialize passed
Reading config from startrun.dat ...
Execute command from startrun.dat over
************************************************
Welcome to ZXR10 2928E Switch of ZTE Corporation
************************************************
login:
24
AppA Usage
Tools
A.1
Guideline
for
Software
Terminal Software
Common terminal software includes HyperTerminal and SecureCRT. 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 enter HyperTerminal
main interface.
5.
If it is necessary to record operation logs, click [Transfer (T)] menu and select [Text
Capture (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.
25
1.
Run the SecureCRT software. The SecureCRT main interface and [connect] dialog
box will pop up.
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 Session> 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 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 <OK> to finish the setting and enter SecureCRT 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.
TFTP Tool
Currently, 5250&5200E&2900E in normal OAM mode only supports the
upload and download through the TFTP. The common TFTP server tools
26
mainly include 3CDaemon and TFTP. It is suggested to use the 3CDaemon

tool for the upload and download. Now, lets have a look at the setting for the
two types of tools about how to set directories for saving version files or
configuration files on the server.
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 TFTP Server]. And
[3CDaemon Configuration] dialog box pops up. Then perform the following
operations:
i.
In the input box below, type directory, e.g. the version directory of Disk E used
for saving version file or configuration file, or click the button on the right of the
input box to select the directory;
ii.
A check mark after <Create directory names in incoming file re> indicates that
this option is selected;
iii.
Click <Application (A)> to finish the setting.
This is shown in AppFigure A -1.
AppFigure A-1 3CDaemon Window
27
A.2.2
TFTP
1.
Run tftp software on the background host.
2.
In the input box <Home Directory>, type directory, e.g. the version directory of Disk
E used for saving version file or configuration file, or click the button on the right of
the input box to select the directory;
3.
Click <Done> to complete the setting.
AppFigure A-2 TFTP Window
A.3
FTP Tool
Common FTP server tools include 3CDaemon and WFTPD. The following will introduce
how to set the two types of software. Items to be set contain:
FTP username/password
Directory on the server used for storing the version file or configuration file
Other software tools share the similar configuration.
A.3.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 following
operations:
28
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.
AppFigure A-3 3Cdaemon Window
A.3.2
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:
i.
Click <New User...> to create a user, such as target, and set a password.
29
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.
iv.
Click <Done> to complete the setting.
This is shown in figure below.
AppFigure A-4 WFTPD Window
A.4
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 You can type a filename here.
2.
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.
30
AppFigure A-5 Araxis merge Window
31

ZXR10 5250&5200E&2900E Ethernet Switch Version Upgrade Guide - R1.3

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZXR10 5250&5200E&2900E Ethernet Switch Version Upgrade Guide - R1.3

Загружено:

Авторское право:

Доступные форматы

ZXR10 5250&5200E&2900E

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

Reason for Revision

Updated the products

Updated the products

Updated the products

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

Applicable to: Commissioning and maintenance engineers

Knowledge and skills

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

About This Document

Describes software versions.

Describes software version upgrade flow.

3 Preparation before Upgrade

Describes preparations before upgrade.

Describes precautions and upgrade procedures for the

5 Software Version Upgrade

Describes software version upgrade precautions, upgrade

Describes version rollback steps.

AppA Usage Guideline for Software

Describes how to set and use common upgrade software.

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

Preparation before Upgrade............................................................................5

Software Version Upgrade............................................................................14

Usage Guideline for Software Tools.............................................................23

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

Table 1-1 Product Model

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

The software package for ZXR10 5250&5200E&2900E Series switches

Table 1-2 The File List

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

Figure 2-1 Version Upgrade Flow

Preparation before Upgrade

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

Software Version Upgrade

ZTE Confidential Proprietary

2016 ZTE CORPORATION. All rights reserved.

Preparation before Upgrade

Preparation Records before Upgrade

Table 3-3 Preparation Records before Upgrade

Prepare software and hardware

Set up upgrade environment

Back up configuration information

Back up version file

Check running status of hardware

Check running status of system

Check FLASH free space

Reading Version Accompanying Documents