Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Modification Record
Draft by/ Draft/modi
Version Reviewe Reason for
Document No. modified fication Main modified points
No. d by modifications
by date
Zhu Tao
None V1.0 2009-4-30
Changfei Minjuan
Contents
1 VERSION INFORMATION........................................................................................................1
2 UPGRADE FLOW....................................................................................................................2
4 BOOTROM UPGRADE...........................................................................................................10
6 VERSION ROLLBACK...........................................................................................................20
1 VERSION INFORMATION
Notes:
This document is applicable to engineers who pass ZTE Data Products Certificate Test-Level I
or above, are familiar with data products and have experience in data product upgrading.
ZXR10 5900&5200 Series switch includes two product series, each with multiple product
models, as shown in Table 1.1.
Currently, the main version available for ZXR10 5900&5200 Series switch is V2.8.02.A.
Notes:
Upon upgrading version on site, please check the Version Release Note for whether it is
necessary to upgrade Bootrom or not.
There are multiple files in ZXR10 5900&5200 Series switch software version compressed
package; refer to Table 1.2 for file list.
2 UPGRADE FLOW
Fig 2.1 depicts the upgrade flow of ZXR10 5900&5200 Series switch.
Start the
upgrade
Make preparation
before upgrade
Does bootrom
need to be Y Upgrade Bootrom
upgraded?
N
Upgrade the
software version
Does the
Roll back the
upgrade N
version
succeed?
Y
The upgrade is
completed
It is required that a series of preparation work should be done before upgrade. For detailed
information, see 3 Preparation before Upgrade.
2. Bootrom Upgrade
In the preparation phase before upgrade, it should confirm whether Bootrom upgrade is needed
in the upgrade to be implemented; if so, refer to 4 Bootrom Upgrade to perform upgrade.
Refer 5 Software Version Upgrade for upgrading the software version. If the upgrade is
successful, the upgrade is completed; if failed, perform version rollback.
4. Version Rollback
If the version upgrade fails, it needs to perform version rollback. Specific failure situation
requires specific rollback step. For detailed method, see 6 Version Rollback.
Keep a record of whether the preparation work is done and the detailed preparation according to
Table 1.1 before upgrade.
Read the Version Release Note mainly for the following information:
Read it to have a good grasp of notification items and detailed operation steps in version
upgrade.
When conditions permit, prepare spare parts for switches in key nodes and tools required
by the replacement;
Prepare serial console cable and network cable necessary for upgrade; and check if they
are usable.
8. Software Preparation
Apply and download version files necessary for upgrade according to the flow specified by
ZTE and check the file size;
If there is any change in the configuration commands of the target version, it will need to
acquire current configuration in advance; record it if there is any difference between
configuration of target version and that of the original version, and edit corresponding
configuration command script on the basis of the format of the new version;
Prepare FTP/TFTP tool software necessary for upgrade, and check if they are usable;
Prepare tool software Araxis merge for comparing configuration information before and
after upgrade.
Connect PC with device via serial console cable; open HyperTerminal or other terminal
software and configure serial port attribute:
– Data Bits: 8
– Parity: None
– Stop Bits: 1
After the configuration, verify that the device can be accessed via serial port and open automatic
ZTE Corporation Copyright Reserved, No Spreading Abroad unless Permitted 5
ZXR10 5900&5200 Series SwitchV2.8.02A Version Upgrade Guide For Internal Use Only▲
Connect network port of PC with service port of device or management port via network cable;
configure IP address of same network segment on both sides to ensure the two peers can ping
through each other.
Telnet the IP address of the device from PC to ensure it can access the device normally.
Set and start FTP server software to ensure the running is normal. See 8.2 FTP Tool for the
setting of common FTP server tool software.
12. Check current device configuration and save the displayed configuration information to the
background server
ZXR10#show running-config
13. Save current configuration and verify that the saving is successful.
ZXR10#write
Building configuration...
..[OK]
ZXR10#dir cfg
Directory of flash:/cfg
Being OFF indicates the interface has no connection with any other interface
20. FDX/COL
Flashing indicates there is a conflict in sending and receiving packets on this interface
Services checking needs cooperation from the customer and the check result will be subject to
their confirmation.
ZXR10#delete zxr10.old
Are you sure to delete files?[yes/no]:y
Start deleting file
deleting /flash/img/zxr10.old
..
file deleted successfully.
ZXR10#
4 BOOTROM UPGRADE
Please skip this chapter if it doesn’t need to upgrade bootrom.
This chapter introduces notification items, upgrade steps, upgrade failure emergency response
and bootrom programming steps in the process of upgrading bootrom.
23. Do not upgrade bootrom online when CPU utilizations of line cards are high.
24. It is forbidden to power off during the live upgrade of bootrom, or the system will fail to
boot up.
Update bootrom
Notes:
Filenames of Boot saved to FLASH must be correct and identical to that in the compression
package of software version.
After copying, execute command dir img to check if the boot file size is consistent with that on
FTP server.
If the update succeeds, the system will prompt that the update is successful.
Notes:
If it prompts the update fails upon upgrading the bootrom, please delete the corresponding boot
file under img directory and recopy a new one and then perform update again. If the upgrade
still fails after several times of attempts, replace bootrom chip of corresponding card manually.
28. If the upgrade fails after several times of attempts, replace bootrom chip of corresponding
device manually.
29. When an exception occurs, for example, the power fails during the bootrom is being
upgraded, or it prompts the bootrom is upgraded successfully but the fails to be started, it
needs to replace bootrom chip of corresponding card manually.
The location of each bootrom chip on the card is marked in red in the attachment.
5900&5200
boot.JPG
Programming
BootRom.rar
31. During the process of writing the version into FLASH, forbid to restart the device or
power off, otherwise FLASH may be damaged;
32. During the process of writing the version into FLASH, CPU utilization will rise, so it is
forbidden to implement other actions on the device.
33. The troubleshooting principle for unexpected upgrade failure is that recover services as
soon as possible and then locate the failure reasons; Meantime, during the period of
upgrade application, try to collect information as much as possible for subsequent analysis;
34. For unexpected situations that cannot be solved, please contact instructors of Data
Customer Service Department.
Delete the old version file if FLASH can not accommodate two versions:
ZXR10#cd img
ZXR10#delete zxr10.zar
Notes:
The name of the target version file saved to FLASH must be zxr10.zar.
After downloading, execute command dir img to check if the version file size is consistent with
that on FTP server.
If it shows as boot via network, execute command to change mode to local boot, and save the
configuration:
ZXR10(config)#nvram imgfile-location local
ZXR10(config)#write
Building configuration...
..[OK]
ZXR10(config)#exit
ZXR10#write
It needs about 5 minutes to boot up the device. During this process, observe indicator status and
output information of serial port.
Generally, it is suggested that, during the upgrade and reboot process, enable the logging of the
HyperTerminal to record the upgrade and reboot process.
Notes:
If the device cannot boot up normally, and causes cannot be located within 20 minutes, it
indicates the upgrade fails. Refer to Upgrade Failure Emergency Response to roll back to the
old version.
[MPU]
Main processor: PowerPC MPC8270 Processor with 128M bytes of memory
512K bytes of non-volatile configuration memory
16M bytes of processor board System flash (Read/Write)
ROM: System Bootstrap, Version: V1.10 , RELEASE SOFTWARE
Hardware Version: V1.3, CPLD Version: V1.2
System serial: 20097
ZXR10#
As for commands whose parameters needs to be modified in new version, configure these
commands with configuration commands prepared before upgrade.
As for extremely lengthy configuration information, it is recommended to use tool Araxis merge
to compare the configuration information after and before the upgrade so that to find the
configuration loss effectively and timely. See 8.3 Araxis merge for the method of using tool
Araxis merge.
Check if the system hardware after upgrade works normally and if the panel indicator is in
normal status.
Check the running status information of the system after upgrade, and compare it with the
information recorded before upgrade to see if it is normal. The main items to be checked are as
shown in 20(1)Table 1.1; yet, it needs to add or delete some of the items according to the
commissioning of practical service.
Check the running status of services carried on the device. The items to be checked can be
adjusted according to services enabled at site where devices are upgraded.
Services checking needs cooperation from the customer and the check result will be subject to
their confirmation.
Notes:
In case the services are abnormal and it is the problem of the device, if causes cannot be located
within 20 minutes, it indicates the upgrade fails. Refer to Upgrade Failure Emergency
Response to roll back to the old version.
6 VERSION ROLLBACK
This chapter introduces specific rollback steps under diverse situations.
Apply boot via network to roll back. For detailed steps, see 6.2.
Directly roll back to the old version for rebooting. For detailed steps, see 6.3.
Notes:
If the rollback fails, or abnormal condition occurs, please contact instructors of Data Customer
Service Department.
Reboot the device and press any key to enter boot mode during the countdown period, and then
modify boot parameters.
Copyright (c) 2005 by NanJing Institute of ZTE, Inc.
Compiled Aug 6 2008, 09:23:31
3
[ZXR10 Boot]: c
Reboot the device in boot mode, and the system downloads the original version from the
background FTP server automatically.
[ZXR10 Boot]: @ //Reboot the device
After rebooting the switch, check if it is the original version number and if the services are
normal.
After the device and services are verified to work normally, delete the new version file copied to
img directory of FLASH during the upgrade, and modify the name of the original version file to
zxr10.zar.
ZXR10#copy ftp: //168.1.64.64/zxr10.zar@target:target flash: /img/zxr10.zar
Change the boot mode from boot via network to local boot:
ZXR10(config)#nvram imgfile-location local
ZXR10(config)#exit
ZXR10#write
44. Delete the new version file copied to img directory of FLASH in the process of upgrading,
and modify the name of the old version file to zxr10.zar.
ZXR10#delete zxr10.zar
ZXR10#rename old.zar zxr10.zar
Notes:
Since FLASH has no sufficient space and the old version file has been deleted before upgrade, it
needs to recopy the old version file to FLASH. For detailed steps, see 5.4.2.
After rebooting the switch, check if it is the original version number and if the services are
normal.
Port Attribute
8.1.1 HyperTerminal
The HyperTerminal is usually used for serial port connection. The following introduces the
setting for it.
48. Type the name of the connection in <Name> of [Connection Description] dialog box, click
<OK>, and you will be presented with a [Connect To] dialog box.
49. Select the COM port in <Connect using> option of [Connect To] dialog box for the host to
connect the device, click the OK button, and [COM Properties] dialog box pops up.
50. 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.
51. If it needs to record operation log, click [Transfer (T)] menu, select [Capture Text (C)], and
[Capture Text] dialog box pops up. Select log file in the dialog box and click <Start> to
finish the setting.
8.1.2 SecureCRT
SecureCRT is commonly used for serial port connection and telnet connection.
52. Run SecureCRT software, and 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.
53. Click the third button <New Session> in the tool bar of [Connect] dialog box to establish a
new session, and [Session Options] dialog box will pop up.
Protocol: serial
Port: COM port used for the host to connect the device
Data bits: 8
Parity: None
Stop bits: 1
Protocol: telnet
Port: 23
Click <OK> to finish the parameter setting and enter SecureCRT main interface.
55. If it needs to record operation log, click [File] menu, select [Log Session], and [Select Log
File] dialog box pops up. Select log file in the dialog box and click <Save (S)> to finish
the setting.
FTP username/password
Directory used for saving version file or configuration file on the server
8.2.1 3CDaemon
56. Run 3CDaemon software in the background host.
57. Open [FTP Server] module on the left, click [Configure FTP Server], and [3CDaemon
Configuration] dialog box pops up. Then perform the following operations:
(2) Click <Set/Change user’s password> button and set the password;
(3) Type directory, e.g. IMG directory of Disk D used for saving version file or configuration
file in the input box below, or click the button on the right of the input box to select
catalog;
(4) Select Login, Download and Upload in the list below <This user can:>;
8.2.2 WFTPD
58. Run wftpd software in the background host.
59. Click menu item [Security], select [User/Rights…], and [User/Rights Security Dialog]
(1) Click <New User...> to create a user, such as target, and set a password.
(2) Select user name "target" in the <User Name> drop-down box.;
(3) Input a directory to save version file and configuration file in the <Home Directory> input
box, such as, the IMG directory on Disk D.
61. Run Araxis merge software, and 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”.
62. Click the button <...> on the right of each input box respectively, select two documents that
needs to be compared, and the selected documents are displayed on two sides of the main
interface, and the different places are clearly marked.