ZXA10 C320 V1.2.5 P2T6 Version Upgrade Guide
ZXA10 C320 V1.2.5 P2T6 Version Upgrade Guide
ZXA10 C320 V1.2.5 P2T6 Version Upgrade Guide
File Number:
Version Number:A
Prepared by / Date
Approved by / Date
本文中的所有信息均为中兴通讯股份有限公司内部信息,不得向外传播。
ZXA10 C320 V1.2.5 P2T6 Version Upgrade Guide Internal use only▲
Contents
1. Version Description.....................................................................................................................3
2. Version Upgrade/Roll back.........................................................................................................3
2.1. Upgrade Preparation.......................................................................................................3
2.1.1. Tools....................................................................................................................3
2.1.2. Hardware.............................................................................................................3
2.1.3. Software preparation, data backup and running status checking and recording 3
2.1.4. Configuration checking before version upgrade................................................4
2.2. Upgrade Operation Procedures.......................................................................................4
2.2.1. Set up the environment.......................................................................................4
2.2.2. Running the FTP Server......................................................................................4
2.2.3. Configure the NE................................................................................................4
2.2.4. Download and Synchronize the Version.............................................................7
2.2.5. Version Upgrade................................................................................................10
2.2.6. Confirm the version upgrade success...............................................................11
2.2.7. CPLD upgrade...................................................................................................11
2.3. Rolling back the Version...............................................................................................13
2.3.1. Criterion of whether to roll back the version....................................................13
2.3.2. The method of rolling back the version............................................................13
3. Testing for the upgrade..............................................................................................................13
4. Notes..........................................................................................................................................13
4.1. The Compatibility Issues of C320 V1.2.0 T5 Upgrading to C320 V1.2.0P1T213
4.2. The Compatibility Issues of C320 V1.2.0 P1T2 rolling back to C320 V1.2.0T5
14
5. The versions which to be upgraded need to be coincident.......................................................14
6. Checklist....................................................................................................................................15
1. Version Description
Note.
Ip address : the out-band IP address.
In the mng1 interface, you can modify the out-band IP address, FTP server IP address and the user
name and password consistent with the FTP server.
ZXAN(config-if)#?
boot-password FTP password for boot server
boot-server Specify remote boot server
boot-username FTP username for boot server
config-filename Start config file name
default-gateway Default gateway for boot file download
enable-password Password for enable entrance
end Exit to EXEC mode
exit Exit current configuration mode
imgfile-location Bootup imaging file location
ip Configure ip address
no Negate a command or set its defaults
show Show running system information
shutdown Shutdown port
Note.The in-band/out-band MAC address can be modified in boot mode. The method of entering
the boot mode: restart the NE,the serial port will print: Press ENTER key to stop auto-boot....you
will enter the boot mode if you press enter in 3 seconds time.
ZTE Confidential Proprietary © 2019 ZTE CORPORATION. All rights reserved.
ZXAN#reboot
Confirm to reboot? [yes/no]:y
ZXAN#####
Board name : SMXA
SubCard name : UCDC/1
Boot version : V1.2.0T3
Creation date : 2012-06-06 14:08:02
Pcb version : 110701
Cpld version : V1.3
Serial number :
done.
Mounting file system /log ... done.
[SMXA]/flash/img/>p
[SMXA]/flash/img/>c
Step 2 Synchronize the version files to the slave control board. When the version files have been
downloaded to the master control board, if the slave control board is in standby status, the version
will be synchronized automatically. But if the slave control board is plugged after the version
download or the control board is not in standby status, you may need to use command to
synchronize the image files to it. In the privilege mode(ZXAN#), command sync-file img is
provided to synchronize the version files from master control board to slave control board. For
example.
ZXAN#sync-file img
command ZXAN#show sync-status is provided correspondingly to check the progress of the
synchronization. For example.
ZXAN#sho sync-status
Synchronization status of directory /flash/img/ :
Filename Status
--------------------------------------------------------------------------------
bsp.mvr 100
gtghg.bt 100
gtghg.fw 100
gtghg.mvr 100
gtgoe.bt 100
gtgoe.fw 100
gtgoe.mvr 100
gtgog.bt 100
gtgog.fw 100
gtgog.mvr 100
pm.fw 100
smxa.fw 100
smxa.bt 100
14 files sync OK, Total 14 files
Step 3 Confirm that the synchronization between master and slave control boards is successful.
After the synchronization between the master control board and the slave control board .use the
command show version-saved.master/slave..to check whether the version files are the same or
not between these two boards.
ZXAN#show version-saved master
PhyLoc FileName VerType VerTag BuildTime Length Active
--------------------------------------------------------------------------------
1/1/4 bsp.mvr MVR v1.0 2012-09-27 10:16:13 1212669
1/1/4 gtghg.bt BT V4.0.0 2013-01-30 16:54:16 524288
1/1/4 gtghg.fw FW V1.2.5P2 2013-09-23 01:14:49 78842
1/1/4 gtghg.mvr MVR V1.2.5P2 2013-09-23 01:14:48 4939176
1/1/4 gtgoe.bt BT V1.2.0P1 2012-10-24 14:17:00 387020
1/1/4 gtgoe.fw FW V1.2.5P2 2013-09-23 01:52:53 4298811
1/1/4 gtgoe.mvr MVR V1.2.5P2 2013-09-23 01:52:53 1886523
1/1/4 gtgog.bt BT V4.0.0 2013-03-05 14:11:46 524288
1/1/4 gtgog.fw FW V1.2.5P2 2013-09-23 02:11:58 59946
1/1/4 gtgog.mvr MVR V1.2.5P2 2013-09-23 02:11:57 5193224
1/1/4 etgo.fw FW V1.2.5P2 2013-09-21 23:25:49 1427718
1/1/4 etgo.mvr MVR V1.2.5P2 2013-09-21 23:25:48 5009999
1/1/4 etgod.bt BT V1.2.0 2012-06-14 15:52:36 249604
1/1/4 pm.fw FW V1.2.5P2 2013-09-22 22:22:22 934
1/1/4 smxa.bt BT V4.0.0 2013-09-13 9:34:23 524288
1/1/4 smxa.fw FW V1.2.5P2 2013-09-23 07:34:25 492068
1/1/4 smxa0.mvr MVR V1.2.5P2 2013-09-12 07:02:00 13984601 0
1/1/4 smxa1.mvr MVR V1.2.5P2 2013-09-23 07:34:16 13989282 1
Use the command show version-running to check the running version, and to verify the boot
version is upgraded successfully.
ZXAN#show version-running
PhyLoc FileType VerType VerTag BuildTime VerLength
--------------------------------------------------------------------------------
1/1/1 ETGO MVR V1.2.5P2 2013-08-27 23:36:54 5008113
1/1/1 ETGOD BT V1.2.0 2012-06-14 15:52:36 249604
1/1/3 SMXA MVR V1.2.5P2 2013-08-28 07:15:09 13982546
1/1/3 SMXA BT V4.0.0 2013-08-12 12:00:21 524288
1/1/4 SMXA MVR V1.2.5P2 2013-08-28 07:15:09 13982546
1/1/4 SMXA BT V4.0.0 2013-08-12 12:00:21 524288
1/1/2 GTGOE MVR V1.2.5P2 2013-08-28 01:59:52 1886472
1/1/2 GTGOE FW V1.2.5P2 2013-08-28 01:59:53 4298811
1/1/2 GTGOE BT V1.2.0P1 2012-10-24 14:17:00 387020
Use the command update-boot slotno [slotno id] to upgrade the boot version
ZXAN#update-boot slotno 1
.............................................................................................................................................................
.........................................................[Successfully]
ZXAN#update-boot slotno 2
.............................................................................................................................................................
.........................................................[Successfully]
ZTE Confidential Proprietary © 2019 ZTE CORPORATION. All rights reserved.
Reboot the NE
After upgrading the version and saving configuration, reboot the NE.
ZXAN#write
Building configuration...
..[OK]
ZXAN#reboot
Confirm to reboot? [yes/no]:y
Use command show updatecpld to check whether the CPLD update is set successfully or not.
ZXAN#show updatecpld
Rack Shelf Slot RealType NextResetUpdate LastUpdateResult Version
-----------------------------------------------------------------------------
1 1 1 ETGOD YES SUCCESS V1.5
1 1 2 GTGOE NO SUCCESS V2.2
1 1 3 SMXA NO SUCCESS V1.6
1 1 4 SMXA NO SUCCESS V1.6
“NextResetUpdate” flag is set as “YES”, which means cpld upgrade is set successfully. For
example, all the cards mentioned above will upgrade the CPLD version when the cards are
rebooted.
Reset cards except master control board to upgrade the CPLD version
Reset the cards except master control board to upgrade the CPLD version. When the line card
status is “inservice”.and the slave control card is in “standby” status.you can continue the next
operation.
Note.in this step, you cannot reset the master control board
Command as below:
ZXAN#reset-card slotno 1
Confirm to reset card? [yes/no]:y
Save the configurations and restart the NE
ZXAN#write
Building configuration...
..[OK]
ZXAN#reboot
Confirm to reboot? [yes/no]:y
PS: The NE will swap automatically when the Master Control Card cpld upgrade is in
processing.
Use command show update-cpld to check whether the cpld version is upgraded successfully
or not.
ZXAN#show updatecpld
Rack Shelf Slot RealType NextResetUpdate LastUpdateResult Version
ZTE Confidential Proprietary © 2019 ZTE CORPORATION. All rights reserved.
Reboot the OLT to upgrade the CPLD version of master control boards
PS:
All the result of “Show” Command listed here is only used to specify the steps of
upgrading, which may be different with the official released version. For more detail
information of official released version, please refer to “Specification of Released
Version”.
The detailed CPLD Version listed here may be different with the official released
version. The CPLD version of official released version will be listed in “Specification of
Released Version”
Service Testing . Check whether the customer services are normal, such as Internet, IPTV,
VOIP of ONU.
NM testing . Check that the NM connection is normal, the NM can synchronize and
configure the data, and the alarm can appear in NMS
4. Notes
About upgrading the NE: the .boot, .mvr and .fw version files of the cards must be coincident;
And all of the three files of the online line cards must be downloaded to the control board,
otherwise the line cards may not start appropriately after the upgrade.
The coordinate version of ONT: please refer to the newest distribution list of related ONT.
6. Checklist