ZXCTN 6100 6110 (Agent Version) Upgrade Guide

Internal Use Only▲
ZXCTN 6100 6110

(AGETN Version) Upgrade Guide
(V2011-05)
ZTE CORPORATION
All Rights reserved, No Spreading abroad without Permission of ZTE Page 1 of 27

Revision History
Drafted
Document Version Reviewe Drafted/ Major Modifications
by/Modif Reasons
No. No. d by Modified on (Key Points)
ied by
Zhang
Zhang Bin,
V2010-10 2010-10-29
Lei Zhou
Xiaohui
1) To meet the
industrial standard
CCSA, modify
MPLS-TP OAM
Channel Type to be
7FFA (32762).
Channel Type for
ZTE should be
modified from 7FF8
(32760) to be the
standard value
defined by CCSA. 1. The ChannelType
2) After MPLS-TP
value for global network
interconnection test
for several should be modified
manufacturers, the before upgrade.
different WTR
coordination 2. The interface version
mechanism can for EMS and AGENT
Zhang Xu cause service
V2011-05 2011-5-17 interruption. After should be modified to be
Lei Fuhua
coordination, China V1.12 after upgrade. U3
Mobile requires
each manufacturer cannot be rolled back to
supports WTR long V1.10.
time-out mode
3. The situation of boot
required by 8032
standard. ZTE incompatibility is not
makes the change considered.
according to the
requirement.
3) V1.1P01 issued
on May 25, 2011
designs that the
version (ZXCTN
6100
V1.10.00P1B11)
AGENT adopts
V1.12 to connect
with EMS interface.
Note 1: Fill in this table each time archiving the file.
Note 2: Fill “reasons” and “major modifications” with “N/A” when archiving the document for the first time.


TABLE OF CONTENTS
Chapter 1 Overview...................................................................................................................................7
1.1 Version Issuing Condition......................................................................................................................7
1.2 Analysis for Version Modification and Engineering Upgrade...............................................................8
Chapter 2 Upgrade Preparations...........................................................................................................10

2.1 Preparation for Upgrade Environment.................................................................................................10
2.1.1 Performing MD5 Check for the File..........................................................................................10
2.1.2 Checking Environment Before Upgrade....................................................................................10
2.1.3 Saving Configuration and Backing Up Configuration File.......................................................11
2.2 BOOT Upgrade Preparation.................................................................................................................11
2.2.1 Upgrade Description..................................................................................................................12
2.2.2 Configuring Upgrade Environment to Upload Boot File..........................................................12
2.3 ZAR Upgrade Preparation....................................................................................................................12
2.3.1 Checking Old Version Information............................................................................................12
2.3.2 Configuring Upgrade Environment to Upload and Download ZAR File.................................13
2.3.3 Verifying the Completeness of Uploaded and Downloaded ZAR Files....................................15
2.4 Preparing Agent Database....................................................................................................................15
2.4.1 Create the directory dataset........................................................................................................15
2.4.2 Uploading the InitDataSrcFlag File...........................................................................................16
2.4.3 Checking Whether InitDataSrcFlag File Value Is 2...................................................................17
Chapter 3 Upgrade Operation................................................................................................................18

3.1 Modifying Channel Type for OAM and Delivering it to Device........................................................18
3.2 Upgrade Procedure...............................................................................................................................19
3.2.1 Upgrading BOOT in Hidden Mode...........................................................................................19
3.2.2 Modifying Name of Version File...............................................................................................19
3.2.3 Restarting the Equipment...........................................................................................................21
3.2.4 Synchronizing Data to AGENT.................................................................................................21
3.2.5 Confirming the EMS Interface...................................................................................................21
3.2.6 EMS Data Sync Setting..............................................................................................................22
3.2.7 Deleting Database InitDataSrcFlag............................................................................................22

3.2.8 Globally Enable Control Word...................................................................................................22
Chapter 4 Rollback..................................................................................................................................24
4.1 Normal Rollback..................................................................................................................................24
4.1.1 Configuring Upgrade Environment to Upload Old Boot File...................................................24
4.1.2 Upgrading boot in Hidden Mode...............................................................................................25
4.1.3 Modify version file name for the device....................................................................................25
4.1.4 Device Restart............................................................................................................................25
4.2 Abnormal Rollback..............................................................................................................................25
4.2.1 Replacing boot Version for Next Site........................................................................................25
4.2.2 Modifying Version Name...........................................................................................................26
4.2.3 Device Restart............................................................................................................................26
Chapter 5 Attachments............................................................................................................................27
5.1 Upgrade Guide for Non- AGETN Version...........................................................................................27
5.2 Upgrade Guide from Non-AGENT Version to AGENT Version.........................................................27

Chapter 1 Overview
1.1 Version Issuing Condition
 Non-AGENT Versions:
There are two engineering versions for V1.0 of ZXCTN 6100: V1.0B6 and V1.0B8.
There are two issued engineering versions for V1.1 of ZXCTN 6100: V1.1R1P1B2 and
V1.10.00 B6.
 AGENT Versions:
 ZXCTN 6100:
On August 20, 2010, the first engineering version with AGENT ZXCTN 6100
V1.10.00P1B1 was issued.
On September 22, 2010, the second engineering version with AGENT ZXCTN 6100
On October 25, 2010, the third engineering version with AGENT ZXCTN 6100
On May 25, 2011, the fourth engineering version with AGENT ZXCTN 6100
On June 23, 2011, the fifth engineering version with AGENT ZXCTN 6100
V1.10.00P1B12 was released.
On November, 21, 2011, the sixth engineering version with AGENT ZXCTN 6100
On September 5, 2012, the seventh engineering version with AGENT ZXCTN 6100
On October 26, 2012, the eighth engineering version with AGENT ZXCTN 6100
 ZXCTN 6110:
On August 20, 2010, the first engineering version with AGENT ZXCTN 6110 V1.10.00B5
was issued.

On September 22, 2010, the second engineering version with AGENT ZXCTN 6110
V1.10.00B7 was issued.
On October 25, 2010, the third engineering version with AGENT ZXCTN 6110
V1.10.00B8 was issued.
On May 25, 2011, the fourth engineering version with AGENT ZXCTN 6110
On June 24, 2011, the fifth engineering version with AGENT ZXCTN 6110 V1.10.00P1B9
was issued.
From the above versions issued, there are three circumstances for PTN upgrade.
 Upgrade between non-AGENT versions: Take ROS data as valid and relevant
upgrade guides have been issued.
 Upgrade from non-AGENT version to AGENT version: Take AGENT database

instead of ROS database as valid and relevant upgrade guides have been issued. In
May 2011, modifications were made according to the finalized version designed by
V1.1P01. It was updated in June 2011.
 Upgrade between versions with AGENT: Take AGENT database as valid. This guide
is for the upgrade between versions with AGNET. It is updated according to the finalized
version designed by V1.1P01 in May 2011. It was updated in June 2011.
This document focuses on device upgrade. For EMS upgrade, please refer to relevant
upgrade guide for EMS. The upgrade between versions with AGENT is very similar to the
upgrade of the above two cases. Because After-Sales engineers participating PTN
engineering are familiar with them, this document describes the upgrade between versions
with AGENT in brief.
1.2 Analysis for Version Modification and Engineering Upgrade

Version modifications affecting the engineering upgrade between AGENT versions are as
follows.
 For ZXCTN 6100, the BOOT for the version issued on August 20, 2010 is incompatible
with the ones issued later (6110 does not have such a problem).

The version for ZXCTN 6100 issued on August 20, 2010 are only used in Yongchuan,
Chongqing and some other exchange offices; therefore, the upgrade mode for them are a
little different from others.
 Compared with V1.1 version, the finalized version designed by V1.1P1 issued on May
25, 2011 for ZXCTN 6100 and 6110 have the following three differences for upgrade.
1) Modification of ChannelType value: Evaluation shows that each version of the EMS
supports modification to this value. The value should be modified before upgrade.
2) Modification for WTR time-out mode: After evaluation, ZTE plan can the self-adaptation
for WTR short time-out and long time-out. The long time-out for WTR cannot affect
services in existing network during upgrade.
3) Interface between AGENT and EMS adopts V1.12. The earlier AGENT version adopts
V1.10 interface. When upgrading this version, take ROS database as valid. Generally
speaking, two upgrade modes are available according to whether BOOT is compatible.
All in all, the two upgrade modes are recommended according to whether BOOT is
compatible.
When BOOT is incompatible, for example, ZXCTN 6100 has already been upgraded to the
first engineering version with AGENT, upload ZAR file of the new version via FTP. After renaming
ZAR file of the old version, restart the device directly to upgrade, similar to the upgrade from non-
AGENT version to AGENT version. ----This case can be confronted only in few pilot exchange
offices such as Yongchuan, Chongqing.
 The versions issued on June 24, 2011 for ZXCTN 6100 and 6110 are ZXCTN 6100
V1.10.00P1B12 and ZXCTN 6110 V1.10.00P1B9. The differences about upgrade are as
follows.
Upgrade mode for AGENT leading “upgrade restart": The value for InitDataSrcFlag changes.
Use the command more initDataSrcFlag bin to check that the value is 02. After upgrade, all
cable clips are enabled. Then, execute the commands write and sync startrun to agent.
When BOOT is compatible, for example, ZXCTN 6100 has already been upgraded to the
second engineering version with AGENT or the upgrade for ZXCTN 6110 with AGENT
version, adopt the upgrade mode of UPDATEVER, similar to the upgrade between versions with
non-AGENT. However, to meet the requirement of unified 6263 and 9000, adopt direct copy
mode to upgrade. ----This case is suitable for most situations in existing networks home
and abroad.

Chapter 2 Upgrade Preparations

2.1 Preparation for Upgrade Environment
2.1.1 Performing MD5 Check for the File
During release and acquisition of a version, some unexpected factors may cause
the received version inconsistent with the sent version. To verify this, it is
necessary to perform MD5 check for the version. The principle to follow is very
simple: the sender scans the version file to be released by MD5 to generate an
MD5 check code. The receiver receives the version file and the MD5 check code at
the same time. Then, the receiver regenerates MD5 check code of the version file
through the third-party MD5. Compare the two check codes to verify whether wrong
codes occur during transmission. If inconsistent, it means the version file has gone
wrong. Contact the version sender to send again. MD5 check software is for free
which can be downloaded from the internet.
2.1.2 Checking Environment Before Upgrade
(1) Check whether each cable clip of device works normally.

ZXR10#show processor
The boards should be displayed according to the actual hardware device.
(2) Check the operating version information and boot version information.
ZXR10#show version
ZXR10#show bootrom
Check whether BOOT should be upgraded according to the operating version information in
existing network and the issued file for the new version.
Example:
For ZXCTN 6100:
If the operating version in existing network is the first issued version ZXCTN 6100
V1.10.00P1B1, BOOT must be upgraded together.
If the operating version in existing network is the second issued version ZXCTN 6100
V1.10.00P1B2, BOOT cannot be upgraded together.
For ZXCTN 6100, check the version release file and accompanying document to analyze: if
the existing network runs the first released version ZXCTN 6100 V1.10.00P1B1, the
accompanying BOOT must be upgraded together. If the existing network runs the second
released version ZXCTN 6100 V1.10.00P1B2, the BOOT doesn’t need to be upgraded.
For ZXCTN 6110, check the version release file and accompanying document to analyze:
BOOTs of four existing engineering versions are the same.
2.1.3 Saving Configuration and Backing Up Configuration File
If CLI is used for configuration, please execute the command write to ensure that ROS
database and AGENT database are synchronized.
ZXR10#write
Back up the file startrun.da to /flash/cfg/ (start ftp tool on the computer. If the host enables
EMS, use the ftp tool taken by it).
Description:
1. 192.192.1.100 is the IP address for the host.
2. name.dat is the configured name for startrun after backup.
3. The two sysbaks are the username and password of FTP.
4. The root directory for the FTP tool taken by EMS is \NetNumen_T31\ums\ums-svr\
backup\sysmanager\ (if this server is used, the input and output files should be put in this
directory).
ZXR10 #cd cfg
ZXR10 # copy flash /cfg/startrun.dat ftp //192.192.1.100/name.dat@sysbak:sysbak
Start copying file
…….
file copied successfully.
2.2 BOOT Upgrade Preparation

The attachments below show correspondence between boots and versions.

2.2.1 Upgrade Description
For V1.1 and later version, boot files should be uploaded to the directory /system/.
For 61001.1p01B12/6110 1.10p01b9 and later versions, boot upgrade directory is modified into
/FLASH/IMG. This boot supports md5 check and cannot roll back to the old version.
2.2.2 Configuring Upgrade Environment to Upload Boot File
Device used as FTP server
(1) Start ftp-server on the device.

ZXR10 (config)# ftp-server enable
ZXR10 (config)# ftp-server top-directory /system/
ZXR10 (config)# username who password who
(2) Upload the boot file.
Execute the following operation in CMS. Upload boot to /system/ of the device. Pay attention
to the correctness for file name.
2.3 ZAR Upgrade Preparation
2.3.1 Checking Old Version Information
Check old version information.

6100-1#show version

Ensure that the version for the device is the one with AGENT.
2.3.2 Configuring Upgrade Environment to Upload and Download ZAR File
 Method 1: BOOT incompatible
Because boot versions are incompatible, do not use updatever mode to upload the
upgrade version.
In the case of compatible BOOT, the upgrade mode UPDATEVER can be used.
However, to meet the requirement of unified 6263 and 9000, adopt direct copy mode to
upgrade.
Adopt the device as FTP client and configure FTP server.
Description:
2. ZXCTN 6100 V1.10.00P1B3.zar is the latest AGENT device version to be uploaded.
4. The uploaded file is saved in the directory flash/img/ of device and the name is
zxr10p1b3.zar.
directory).
ZXR10#copy ftp: //192.192.1.100/zxr10.zar@sysbak:sysbak flash: //img/zxr10p1b3.zar
Start copying file
.
It takes about 5 minutes to upload device version.
 Method 2: BOOT compatible:
(1) Configure FTP server for PC.
Open FTP program and wftpd32.exe is a green software, which can be used by clicking
without installation. Copy the program to be upgraded to the designated directory in
Windows, such as “C:\”, making full preparation for the designated upgrade file path for
FTP program in future.

Run Wftpd32.exe and set the username, password and file path, such as UserName:
Daniel, Password: 123, HomeDirectory: C:\.
Set username and password.
After setting, click Done to operate the server.
(2) Configure remote upgrade for the device.
ZXR10#updatever config ftpserver 111.168.0.158 username ppc8321 password

ppc8321 filepath zxr10v1.1P1B3.zar
Parameter description:
ftpserver 111.168.0.158 indicates where does the device download version file.
Generally, it is the PC that is operated by the user currently and FTP server should be
enabled on this PC. user ppc8321 password ppc8321 is to set the username and
password used by FTP server to log onto the PC. filepath zxr10v1.1P1B3.zar indicates
the file to be downloaded from PC.
Note:
After configuration, use the command show updatever to check the upgrade
configuration.

zxr10v1.1P1B3.zar requires that the ZAR file name for active and standby versions
in the information by executing the command show updatever cannot be the
same.
(3) Download ZAR file.
ZXR10# updatever download
Existing update-version file will be covered, sure to continue? [yes/no]: y
Start downloading version file
................................................................................
Version file downloaded successfully.
2.3.3 Verifying the Completeness of Uploaded and Downloaded ZAR Files
ZXR10#chkzar /flash/img/zxr10V1.1P1B2.zar
Verifying checksum of zar file ...
...
Verifying checksum of zar file ok.
If the completeness verification of ZAR fails, delete it and upload it again until the
verification is successful. Then, perform the following upgrade.
2.4 Preparing Agent Database
2.4.1 Create the directory dataset
The non-Agent version has no dataset directory. It is necessary to manually

create one under the root directory of flash. For example:
ZXR10#mkdir dataset
ZXR10#dir
Directory of flash:/
attribute size date time
1 drwx 2048 AUG-11-2010 17:03:52 img

2 drwx 2048 AUG-11-2010 17:06:58 cfg
3 drwx 2048 AUG-10-2010 08:59:38 data
4 drwx 2048 AUG-11-2010 17:13:06

dataset
63830016 bytes total (30531584 bytes free)
2.4.2 Uploading the InitDataSrcFlag File
[Note] You must use InitDataSrcFlag file acquired through upgrade application process,
rather than the self-made InitDataSrcFlag. There are failed cases in which upgrade personnel
made the file by him/herself (by creating a windows text, copying the content into it, and renaming
the file into InitDataSrcFlag), and failed the upgrade.
Adopt the device as FTP client and configure FTP server.
Description:
2. InitDataSrcFlag is the file to be uploaded.
4. The uploaded file is saved in the directoryflash/dataset/ of device and the name is
InitDataSrcFlag.
directory).
Example:
6100-1#copy
ftp: //192.192.1.100/InitDataSrcFlag@sysbak:sysbakflash:
/dataset/InitDataSrcFlag
Start copying file
.
6100-1#dir dataset
Directory of flash:/dataset
attribute size date time name
1 drwx 2048 SEP-17-2010 09:13:38 .
2 drwx 2048 SEP-16-2010 22:06:49 ..
3 -rwx 1 SEP-17-2010 09:13:38
InitDataSrcFlag

63830016 bytes total (28725248 bytes free)
2.4.3 Checking Whether InitDataSrcFlag File Value Is 2
Example:

Chapter 3 Upgrade Operation

3.1 Modifying Channel Type for OAM and Delivering it to Device
In the menu of EMS “OAM Upgrade Parameter”, modify the ChannelType of the whole network
devices to 32762, and then deliver it to the devices.
Take U3 as an example:
For the EMS upgrade doesn’t affect the operation of services, it can be performed in daytime. After the
upgrade, ChannelType of the new EMS may be 32760 or 32762 for different versions. Versions that
need to modify the ChannelType value include:
T31 version is V1.20P01B04d (released by the end of May) ---for all T3 versions earlier than this, the
default value is 32760.
U31 V12.11.20 B06 (released on 20, May) ---for all U3 V12.11.20 versions earlier than this, the default
value is 32760.
U31 V12.11.20P01 B01 (released around 16, May) –this is the first version of V12.11.20P01.
In case of upgrading the old 1731 (ChannelType=32760) to new 1731 (ChannelType=32762), this step
(delivering 32762 to the device) is very important, which may result in a momentary interruption of
protection switching services. Therefore,
1) It must be operated during the applied duration from the customer (usually after 00:00
at night) and it cannot be performed at other time (daytime).

2) It must be performed before upgrading BOOT/ZAR.

This operation is finished on EMS. If there is certain special requirement to modify it on device,
execute the command tmpls oam channel-type 32762 mel 7 in global mode. After configuration,
synchronize it with EMS data and the command is as follows.
3.2 Upgrade Procedure
3.2.1 Upgrading BOOT in Hidden Mode
Example:
ZXR10#olleh
ZXR10 (config-increte)#bootrom update
Updating bootrom.....................
Board Type Board Number Status
mec 2 bootrom update
successfully
[ok]
Execute Ctrl+c to exit the hidden mode
ZXR10#show bootrom (confirm boot version and date)
[SMB, panel 1, master]
Bootrom Version : V1.10.00P1B1
Creation Date : 2010/8/13
Update Support : YES
3.2.2 Modifying Name of Version File
Example:
ZXR10#show updatever //check active file name, for example

zxr10.zar
ZXR10#rename zxr10.zar zxr10b6.bak
ZXR10#rename zxr10p1b1.bak zxr10.zar
Check that zxr10.zar file size is consistent with that of locally
stored file.

6100-2#dir
Directory of flash:/img
attribute size date time name
1 drwx 2048 SEP-17-2010 08:47:52 .
2 drwx 2048 SEP-16-2010 22:06:55 ..
3 -rwx 14274143 SEP-14-2010 20:28:52 zxr10b6.bak
4 -rwx 19258557 SEP-14-2010 21:43:20 zxr10.zar
The following describe differences between updatever and copy:
The copy mode is a common way for data products, without version rollback/updatever
functions. In contrast, the updatever mode is featured by: 1) trial run. With this feature, you
can choose to boot from master or slave file next time. 2) automatic rollback/updatever
functions. During trial run (15 minutes after reboot), if not activated, the equipment will roll
back to the old version automatically (boots of new and old versions must be compatible).
For upgrade from a non-agent version to another non-agent version, two modes are
available. R&D team recommends the updatever mode.
For upgrade from a non-agent version to an agent version, colleagues participating
Chongqing upgrade suggests the copy mode because of boot incompatibility and the
possibility of forgetting to activate 15 minutes after reboot.
During the upgrade, for upgrade between non-agent versions, use updatever while for
upgrade from non-agent to agent, use copy. Note the two upgrade modes should be
smoothly integrated, for example:
First, use the updatever mode to upgrade the non-AGENT version:
1)updatever config ftpserver 192.192.192.1 username ppc8321 password ppc8321 filepath
zxr10_v1.zar
2)updatever download
3)reload
4)updatever active
After the above upgrade, if the equipment power is cut unexpectedly or restarted manually,
the equipment will automatically load the file with a personalized name zxr10_v1.zar (the
master file displayed by show updatever).
Then, use the code mode to upgrade the non-AGENT version to AGENT version:

To integrate the two modes, the uploaded AGENT version file such as ZXCTN 6100
V1.1P1B3 must be renamed as zxr10_v1.zar (the old non-agent version zxr10_v1.zar
should be renamed as other). Then, restart the equipment.
For comparison of the two modes, see the attachment below:
3.2.3 Restarting the Equipment
Restart the equipment. For example:
ZXR10#reload
Proceed with reload? [yes/no]:y
The reboot process lasts for about 3 minutes.
3.2.4 Synchronizing Data to AGENT
Run the command show interface-description to check that all line cards are
started. Then, run write and sync startrun to agent. For example:
ZXR10#show interface-discription
ZXR10#write
ZXR10#sync startrun to agent
The sync process lasts for about 3 minutes.
3.2.5 Confirming the EMS Interface
Confirm the EMS interface version. For example:
ZXR10#show nm-version
Network management software version: V1.12
Check that the EMS interface is V1.12
After the EMS upgrade, modify the corresponding version interface to V1.12
through the EMS. When the EMS is able to monitor the equipment normally,
proceed to next step (for EMS modification mode, refer to the EMS upgrade
guide).

3.2.6 EMS Data Sync Setting
Click Device Config>Data Synchronization>Upload, select the option All to

upload. A 6100 takes about 2 minutes to upload data.
3.2.7 Deleting Database InitDataSrcFlag
In practical engineering, the agent database prevails. Thus, after a successful

upgrade, it is necessary to delete InitDataSrcFlag from the flash DATASET
directory.
ZXR10#cd dataset
ZXR10#delete initdatasrcflag
3.2.8 Globally Enable Control Word
Globally enable PW control word function.

[Note] According to Inner Mongol upgrade experiences, make sure to enable PW control
word in Maintenance>OAM Upgrade (T) page. Do not enable PW control word in single NE
configuration.

Chapter 4 Rollback
Rollback is very simple for compatible BOOT. During upgrade, after restarting device, do not
perform updatever activate to activate the version for trial operation. Then, 15 minutes later, the
device rolls back automatically.
Note: ZXCTN6110 SMC BOOT V1.10.00P1B2 and ZXCTN6100 SMB BOOT V1.1 0.00P1B3 support
MD5 check, unable to roll back to the old boot. This boot is compatible with earlier versions. During the
rollback, just roll back version file.
For incompatible BOOT, rollback is similar to the upgrade from non-AGENT to AGENT. The
details are as follows.
4.1 Normal Rollback

When the monitoring is normal, adopt this mode to roll back the version.
4.1.1 Configuring Upgrade Environment to Upload Old Boot File
The device is used as FTP server to upload old boot program.
(1) Start ftp-server on the device.

ZXR10 (config)# ftp-server enable
ZXR10 (config)# ftp-server top-directory /system/
ZXR10 (config)# username who password who
(2) Upload the boot file.
Execute the following operations in CMD and upload boot to /system/ of device.

4.1.2 Upgrading boot in Hidden Mode

ZXR10#olleh
ZXR10 (config-increte)#boot update
Updating bootrom.....................
Board Type Board Number Status
mec 2 bootrom update successfully
[ok]
Exit hidden mode by using Ctrl+c.

ZXR10#show bootrom
Confirm the date for boot version.

6100-1#show bootrom
4.1.3 Modify version file name for the device.

ZXR10#rename zxr10.zar zxr10P1B3.bak
ZXR10#rename zxr10P1B1.bak zxr10.zar
ZXR10#dir img
4.1.4 Device Restart
Restart the device.
ZXR10#reload
It takes about 3 minutes to restart.
4.2 Abnormal Rollback

When the monitoring is abnormal, adopt this mode to roll back the version (it is
recommended to prepare one backup 6100 for emergency).
4.2.1 Replacing boot Version for Next Site
Because the first AGENT version for 6100 is incompatible with boot of later AGENT versions,
once the upgrade restart fails, replace boot chip on site. There are two modes for replacement.
1. Use one 6100 that works normally to write boot remotely. After the writing is
successful, replace boot.

2. Take out boot and write boot again with the writer
4.2.2 Modifying Version Name

ZXR10#rename zxr10.zar zxr10P1B3.bak
ZXR10#rename zxr10P1B1.bak zxr10.zar
ZXR10#dir img
4.2.3 Device Restart
Restart the device.
ZXR10#reload
It takes about 3 minutes to restart.

Chapter 5 Attachments
5.1 Upgrade Guide for Non- AGETN Version
Upgrade guide (for non-AGENT version) written by Chen Jiusong:
Guide written by Liu Hui:
They can be sued for local upgrade.
5.2 Upgrade Guide from Non-AGENT Version to AGENT Version

NULL

ZXCTN 6100 6110 (Agent Version) Upgrade Guide

Uploaded by

Copyright:

Available Formats

ZXCTN 6100 6110 (Agent Version) Upgrade Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZXCTN 6100 6110 (Agent Version) Upgrade Guide

Uploaded by

Copyright:

Available Formats

Internal Use Only▲

ZXCTN 6100 6110

All Rights reserved, No Spreading abroad without Permission of ZTE Page 1 of 27

All Rights reserved, No Spreading abroad without Permission of ZTE Page 2 of 27

All Rights reserved, No Spreading abroad without Permission of ZTE Page 3 of 27

Chapter 2 Upgrade Preparations...........................................................................................................10

Chapter 3 Upgrade Operation................................................................................................................18

3.2.7 Deleting Database InitDataSrcFlag............................................................................................22

All Rights reserved, No Spreading abroad without Permission of ZTE Page 6 of 27

All Rights reserved, No Spreading abroad without Permission of ZTE Page 7 of 27

 Upgrade from non-AGENT version to AGENT version: Take AGENT database

1.2 Analysis for Version Modification and Engineering Upgrade

All Rights reserved, No Spreading abroad without Permission of ZTE Page 8 of 27

All Rights reserved, No Spreading abroad without Permission of ZTE Page 9 of 27

Chapter 2 Upgrade Preparations

2.1.1 Performing MD5 Check for the File

2.1.2 Checking Environment Before Upgrade

(1) Check whether each cable clip of device works normally.

The boards should be displayed according to the actual hardware device.

For ZXCTN 6100:

2.1.3 Saving Configuration and Backing Up Configuration File

1. 192.192.1.100 is the IP address for the host.

2. name.dat is the configured name for startrun after backup.

3. The two sysbaks are the username and password of FTP.

file copied successfully.

2.2 BOOT Upgrade Preparation

All Rights reserved, No Spreading abroad without Permission of ZTE Page 11 of 27

2.2.1 Upgrade Description

2.2.2 Configuring Upgrade Environment to Upload Boot File

Device used as FTP server

(1) Start ftp-server on the device.

(2) Upload the boot file.

2.3 ZAR Upgrade Preparation

2.3.1 Checking Old Version Information

Check old version information.

All Rights reserved, No Spreading abroad without Permission of ZTE Page 12 of 27

2.3.2 Configuring Upgrade Environment to Upload and Download ZAR File

 Method 1: BOOT incompatible

Adopt the device as FTP client and configure FTP server.

1. 192.192.1.100 is the IP address for the host.

2. ZXCTN 6100 V1.10.00P1B3.zar is the latest AGENT device version to be uploaded.

3. The two sysbaks are the username and password of FTP.

It takes about 5 minutes to upload device version.

 Method 2: BOOT compatible:

(1) Configure FTP server for PC.

All Rights reserved, No Spreading abroad without Permission of ZTE Page 13 of 27

Set username and password.

After setting, click Done to operate the server.

(2) Configure remote upgrade for the device.

ZXR10#updatever config ftpserver 111.168.0.158 username ppc8321 password

All Rights reserved, No Spreading abroad without Permission of ZTE Page 14 of 27

(3) Download ZAR file.

ZXR10# updatever download

Existing update-version file will be covered, sure to continue? [yes/no]: y

Start downloading version file

Version file downloaded successfully.

2.3.3 Verifying the Completeness of Uploaded and Downloaded ZAR Files

Verifying checksum of zar file ...

Verifying checksum of zar file ok.

2.4 Preparing Agent Database