Upgrade

Operators LOGO
ZXUN MGW Upgrade Guide

Revision History
Version Date Author Reviewed by Tested by Remarks
2012-04-
V1.0 Sun Xiaoyong Zhu Qingjun
19
2017 ZTE Corporation. All rights reserved.

Copyright 2012 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.
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 Proprietarily Confidential 2014 ZTE Corporation. All rights reserved I

Contents
1 Overview ........................................................................................................................... 1
1.1 Applicable Scope ..................................................................................................... 1
1.2 Upgrade Components .............................................................................................. 1
1.3 Upgrade Impact........................................................................................................ 1
1.4 Version Changes Affecting Upgrade ....................................................................... 1
1.5 Upgrade Procedure .................................................................................................. 2
2 Upgrade Preparations ..................................................................................................... 3

2.1 Software Preparation ............................................................................................... 3
2.1.1 Preparing Version Files .................................................................................. 3
2.1.2 Copying Version File ...................................................................................... 3
2.1.3 Preparing Other Software .............................................................................. 3
2.2 Hardware Preparation .............................................................................................. 4
2.2.1 Preparing Hardware Tools ............................................................................. 4
2.2.2 Preparing Standby Board ............................................................................... 4
2.3 Document Preparation ............................................................................................. 5
2.4 Upgrade Environment Preparation .......................................................................... 5
2.5 Data Backup ............................................................................................................. 6
2.5.1 Backing up ZIP Data ...................................................................................... 6
2.5.2 Backing up OMM Data and Database-Related Files ..................................... 7
2.6 System Running Status Check ................................................................................ 9
2.7 OMM Server Upgrade ............................................................................................ 14
2.7.1 Starting OMM Server Agent ......................................................................... 14
2.7.2 Starting Firebird Database ........................................................................... 14
2.7.3 Upgrade Procedure ...................................................................................... 15
2.7.4 Starting Cluster Server ................................................................................. 24
2.7.5 Check Whether Version Number is Correct after Upgrade ......................... 25
2.8 Service Upgrade .................................................................................................... 26
2.8.1 Preparing Foreground Upgrade Package .................................................... 26
2.8.2 Powering Off Right OMP Board ................................................................... 27
2.8.3 Deleting Old Version .................................................................................... 28
2.8.4 Backing up ZDB ........................................................................................... 28
2.8.5 Upgrading ZDB............................................................................................. 29
2.8.6 Loading Version Package ............................................................................ 30
II 2014 ZTE Corporation. All rights reserved ZTE Proprietarily Confidential

2.8.7 Enabling Version Package ........................................................................... 31

2.8.8 Querying Foreground Version ...................................................................... 32
2.8.9 Transferring Tables ...................................................................................... 33
2.8.10 Service Test ................................................................................................ 33
2.8.11 Upgrading Standby Board .......................................................................... 33
2.8.12 Manual Block............................................................................................... 33
3 Post-Upgrade Verification ............................................................................................. 34
4 Post-Upgrade Observation ........................................................................................... 35
5 Emergency Recovery .................................................................................................... 36

5.1 Processing Principle............................................................................................... 36
5.2 Rollback Conditions ............................................................................................... 36
5.3 Emergency Recovery Steps .................................................................................. 36
5.3.1 Emergency Recovery of Foreground Boards .............................................. 36
5.3.2 Emergency Recovery of OMM Server ......................................................... 40
5.3.3 Service Verification ...................................................................................... 44
6 Other Matters .................................................................................................................. 44

6.1 Handling Procedure of Exclusion Lock .................................................................. 44
7 References ...................................................................................................................... 45
ZTE Proprietarily Confidential 2014 ZTE Corporation. All rights reserved III
Figures
Figure 3-13 Load Version Package ................................................................................................. 30
Figure 3-14....................................................................................................................................... 30
Figure 5-1 Version Package ............................................................................................................ 38
Tables
Table 1-1 Upgrade Components ....................................................................................................... 1
Table 1-2 Upgrade Impact ................................................................................................................. 1
Table 1-3 Upgrade Procedure (Recommended) ............................................................................... 2
Table 2-1 Preparing Other Software ................................................................................................. 3
Table 2-2 Hardware Preparation ....................................................................................................... 4
Table 2-3 Document List.................................................................................................................... 5
Table 2-4 Environment Preparation .................................................................................................. 5
IV 2014 ZTE Corporation. All rights reserved ZTE Proprietarily Confidential

1 Overview
1.1 Applicable Scope
This document is applicable to ZXUN MGW upgrade and the applicable scope of the
upgrade is listed in the following table:
Source Version Target Version
V4.12.10 V4.13.10
1.2 Upgrade Components
Table 1-1 Upgrade Components
No. Component Upgrade or Not Remarks

1 OMM server Yes
2 Foreground boards Yes
3 Firmware Yes
1.3 Upgrade Impact
Table 1-2 Upgrade Impact

No. Type Content Remarks
During the upgrade of
foreground NEs, all
1 Service impact services of this NE are
interrupted for about
15 minutes.
1.4 Version Changes Affecting Upgrade

None
ZTE Proprietarily Confidential 2014 ZTE Corporation. All rights reserved 1

1.5 Upgrade Procedure
Table 1-3 Upgrade Procedure (Recommended)
Task Operation Required Operation Description

Time Time
Based on Three days Download the version
Software actual site before file and prepare
conditions upgrade patches
Preparations
Based on Three days
Hardware actual site before Hardware requirement
conditions upgrade
1.5 hours
Check alarms, analyze
System Check system
15:00-17:00 logs and performance
Check running status
statistics
ZIP data 10 Back up OMM

20:30-22:30
backup minutes installation program
Data Backing up 20 Back up MGW
Backup OMM data and minutes configuration data,
20:30-22:30
database- performance data and
related files alarm data
Upgrade OMM 1 hour

22:30-23:30 Upgrade OMM server
server
30 Load version, upgrade

Upgrade
minutes 23:30-00:00 database and reset
foreground
Upgrade boards etc
Operation Based on
Test service actual site 00:00-01:00 Test services
conditions
Upgrade the 15 Upgrade the standby

04:00-05:00
standby module minutes module
Based on
Post- Post-upgrade Operations after
actual site 04:00-06:00
Upgrade operation upgrade
conditions
2 2014 ZTE Corporation. All rights reserved ZTE Proprietarily Confidential

2 Upgrade Preparations
2.1 Software Preparation
2.1.1 Preparing Version Files

Version File
No Purpose Note
Content
1 Current version file Used for rollback
New version files are downloaded

from the ZTE support center
2 New version file Used for upgrade
website. Please contact local ZTE
engineers for new version files.
2.1.2 Copying Version File

Copy the version file to be upgraded into a PC (installed with Windows OS) that is
connected to OMM server.
2.1.3 Preparing Other Software

Table 2-1 Preparing Other Software

No Software Purpose Obtained from
OMP emergency Contact service centre for

1 WINE+DTF
recovery the software in advance
Klinux OS Fix OS-related Contact service centre for

2 installation disk faults the software in advance
and its patches
Upload version file Contact service centre for

3 WinScp
the software in advance
Remotely control Contact service centre for

4 VNC viewer
OMM server the software in advance
IE (version Log into the OMM http://it.zte.com.cn/Its/Down

5 number is greater client load/ViewDownInfo.aspx?D
than 6.0) ownLoadID=3408
Modify XML files Contact service centre for

6 XMLspy
the software in advance
Caution:
The XMLspy is the designated software used to modify XML files!
2.2 Hardware Preparation
2.2.1 Preparing Hardware Tools

Debugging tool and standby board must be prepared in advance.
Table 2-2 Hardware Preparation
Tool Name Description
Screwdriver Used to loosen the screws on the board when inserting or

extracting the board
Serial port cable Used for debugging and observing the boot information of
boards such as MP
2.2.2 Preparing Standby Board

Prepare a new GPBB0 board on site; therefore the board can be replaced in time if

there is any board error occurring during upgrade.
2.3 Document Preparation
Table 2-3 Document List
Document Requirement
The upgrade guide of each upgrade NE. Check with the

Upgrade Guide product manager to make sure that the upgrade guide is
the most updated version.
Upgrade Checklist The checklist released together with Upgrade Guide
Release Notes
Service test form for the existing office. It is provided by

Service Test Form
the customer.
Caution:
Please read the documents above carefully beforehand to familiarize yourself with
the upgrade operation.
2.4 Upgrade Environment Preparation
Table 2-4 Environment Preparation

ID Item Content
Password of root for KLINUX OS

1 User and Password
Password of admin for OMM Client
IP address of OMM Server

2 IP Address
IP address of OMP

2.5 Data Backup
2.5.1 Backing up ZIP Data

Log into OMM client as admin user;
Step 1: Query system object set via MML;
Step 2: Execute the following command to back up configuration data and IP

protocol stack data respectively:
BACKUP:OUTPUTPATH="/backup",FILENAME="mgw50v4mgwb18",SETID=1400000&1400
001;
Caution:
The following parameters in the MML above should be modified based on actual
site conditions:
FILENAME: backup file name;
OUTPUTPATH: saving path of the backup files;
SETID: 1400000 represents basic configuration data and 1400001 represents

protocol stack data.
The command screenshot is shown as below:

2.5.2 Backing up OMM Data and Database-Related Files

Step 1: Stop OMM Server and firebird database;
Dual-node operation description:
Open IE and enter IP address of the NEC dual-node software, e.g.,

http://10.44.105.2:29003/. Please modify the IP address according to the actual
condition. After logging in the client, you can enter the operation mode.
If the message No support for JRE 1.5.0 applets found! appears in IE when
logging in, then install the plug-in unit jre-6u19-windows-i586-s.exe on the client.
As shown in the following figure, right-click omm_exec and select Stop to stop the
OMM and firebird database.
Single-node operation description:

[root@localhost /]#cd $ZXHOME
[root@Gcz1-V4MGWngomm]# ./killall.sh //stop OMM server programs
[root@Gcz1-V4MGWngomm]#service firebird stop //stop firebird database
Caution:
$ZXHOME is the environmental variable, and its directory can be viewed by using
the following command. The $ZXHOME in the following parts of this document
carries the same meaning.
[root@Gcz1-V4MGW ~]#echo $ZXHOME
/home/ngomm
Step 2: Back up all files in $ZXHOME into a specified directory
e.g., the files are backed up into /backup:
[root@Gcz1-V4MGW ngomm]#mkdir /backup
[root@Gcz1-V4MGW ngomm]#cp -a $ZXHOME/ /backup/
Step 3: Back up $ZXHOMEDATA/[NE directory]/ into a specified directory
e.g., the directory is backed up into /backup
[root@Gcz1-V4MGW ngomm]#cp -a $ZXHOMEDATA/[NE Directory]/ /backup/
Caution:
NE directory should be based on actual site conditions.
Step 4: Back up $SETUPHOME/SetupVersion.db into a specified directory
e.g., the directory is backed up into /backup

[root@Gcz1-V4MGW ngomm]#cp -a $SETUPHOME/SetupVersion.db /backup/
2.5.3 Cluster OMM

Start omm_exec:
Log into the EC by using the floating IP address on IE, right-click

omm_exec and then click Start in the menu.
2.6 System Running Status Check
1. Check the records of appointed loading operation. If the result shows the appointed
loading version exists, you need to manually deactivate it:
The record check MMLs include:
SHOW APTDPKG
SHOW APTDSPPKG
The deactivation MMLs include:
DEACT APTDPKG
DEACT APTDSPPKG
2. If the master/slave clock shelf is not configured, please configure it.
SET ISSMSSHELF:ISBID=4,SHFTYPE="MASTER";
//In ISBID, fill the EGFS independent board number.

3. Capture call loss for H248G, IPBCP, RTPCONTROL, CSUP, IWF, VMAS and
H245G at different time and back them up for later verification.

4. Save current alarms, history alarms in past two days and the alarms in the
database which have been manually deleted;
To query the alarms in the database which have been manually deleted, firstly
create a New Custom Query, click Other, and then select Manually Cleared
by the Operator in Restoring Type, as the following figures show:
5. View and save the measurement data (as listed below) in the previous one
week via Performance Management, for reference after upgrade:
Rtp Messages Measurement
MAC Port Flow Measurement
MGW Load Measurement
MGW Resource Measurement

H248 Apply Measurement
SCTP Link Measurement
Circuit Switch UP Initialize Measurement
6. View running status of all units and sub-units, and record all blocked units and
sub-units (mainly check MPBA/SDIA/DTIA); the related units and sub-units need
to be blocked after upgrade.
Method: query and record the batch scripts via the following commands before
upgrade:
SHOW UNITSTAT:UNIT=unit ID (for querying unit state);
SHOW SUNITSTAT:UNIT= unit ID,SUNIT= sub-unit ID (for querying sub-unit

state);
SHOW RSCIR:CIRTYPE=" resource type",CIR=unit ID-subunit ID-circuit ID (for

querying resource circuit state);
SHOW ALLLKSTAT (for querying signaling link state);
SHOW ALLSCTPSTAT (for querying SCTP state);
SHOW ALLASPSTAT (for querying ASP state);
SHOW ALLASSTAT (for querying AS state).
7. View and save MGW state, adjacent office state, signaling link group state, and
record AS state, ASP state, SCTP state via Dynamic Management for reference
after upgrade; in addition, after upgrade, manually block what have been
manually blocked before upgrade.
8. Check disk space of the OMM server; make sure the remaining space is greater
than 5G before the upgrade is performed.
9. Check Firebird parameters as per the steps described below; if you find the
value of PAGE_SIZE is 4096, not 8192, contact the support engineers to modify
the parameters after the database is upgraded and runs smoothly for a while.
[root@lcc ~]# cd /home/ngomm_data/ngomm_db/ngmgw_w_6/For example, the N
E is ngmgw_w_6 and it is installed in /home/ngomm

[root@lcc ngmgw_w_6]# /opt/firebird/bin/isql FIREBIRD_CM.FDB -u sysdba -p Comm
2011;
SQL> show database;
Database: /home/ngomm_data/ngomm_db/ngmgw_w_6/FIREBIRD_CM.FDB
Owner: SYSDBA
PAGE_SIZE 4096
Number of DB pages allocated = 145
Sweep interval = 20000
Forced Writes are ON
Transaction - oldest = 296
Transaction - oldest active = 30
Transaction - oldest snapshot = 30
Transaction - Next = 33
ODS = 11.1
Default Character set: NONE
SQL> quit;
10. Check the backup mode of SMP modules on the OMP board. In case it is not
configured as 1+1 active/standby backup mode, you should check whether the
signaling link (TDM and IP) configured on SMP is the load sharing mode.

2.7 OMM Server Upgrade
2.7.1 Starting OMM Server Agent

The setup agent on the server should to be started before upgrade. Firstly, log into
the server and execute the following command to see the agent in MML terminal:
[root@iMG-OMM]#ps -ef | grep setup
root 17713 1 0 06:02 pts/0 00:00:00 ./setup
root 17716 1 0 06:02 pts/0 00:00:00 ./setupserver
root 17754 12367 0 06:02 pts/0 00:00:00 grep setup
If the agent has not been started, go to the installation path: /home/installagent and
execute run.sh to start the agent.
[root@iMG-OMM /]#cd $SETUPHOME/..
[root@iMG-OMMinstallagent]# ./run.sh
Start setup
OK
After the setup is OK, confirm whether the agent is started.
[root@iMG-OMMinstallagent]#ps-ef | grep setup
root 17713 1 0 06:02 pts/0 00:00:00 ./setup
root 17716 1 0 06:02 pts/0 00:00:00 ./setupserver
root 17754 12367 0 06:02 pts/0 00:00:00 grep setup
2.7.2 Starting Firebird Database

The firebord database should be running normally. Execute the following command
to start firebird database:

[root@iMG-OMMinstallagent]# service firebird start
Starting Firebird server [default] server has been successfully started
[ OK ]
2.7.3 Upgrade Procedure

Step 1: Enter IP address of the server in IE; the port number is 8000; for example,
http://10.44.103.56:8000
Step 2: The login window appears. Log in as root user, type password and then click
OK;
Step 3: Select the NE to be upgraded and click Update;

Step 4: The following window appears. Click Click here to import;
Step 5: In the following window, click Browse and choose the target version;

Step 6: Go to the path of target version file and choose the version file; the file name
is similar to the one appears in the following figure:
Step 7: Click OK after you finish choosing the version file;

Step 8: Upload File starts;
Step 9: After Importing package finishes, click Back to main;

Step 10: In the following window, select the version upgrade package which has
been imported;
After selecting the target version, the prompt information which you have to update
the agent server appears if the agent version needs to be upgraded. Otherwise, go
to Step 14 directly;

Step 12: Click the prompt information to enter the automatic update process, in the
following window
Step 13: The agent shall restart automatically after the upgrade is finished. Wait for
about one minute and then log in again to start the next operation step;
Step 14: If the agent does not need to be upgraded, the following window shall
appear after selecting the target version. Click in the window

Step 15: Click to confirm the upgrade information;
Step 16: Click ;

Step 17: The disk space information is displayed. Click to go to the next step.
Step 18: The upgrade starts.

Step 19: After the upgrade is finished, click in the following window;
Step 20: Click in the top right corner, and the following dialogue box shall
appear; click OK.

2.7.4 Starting Cluster Server

Step 1. Start omm_exec: right-click omm_exec and click Start to start the OMM
execution.
Step 2. Click OK in the pop-up window;

Step 3. Start fb_mon_exec: right-click fb_mon_exec and click Start to start the
operation (if fb_mon_exec does not exist, you do not need to perform this step);
then, click OK in the pop-up window.
Step 4. Start swd_mon_exec: right-click swd_mon_exec and click Start to start

the operation (if fb_mon_exec does not exist, you do not need to perform this
step); then, click OK in the pop-up window.
2.7.5 Check Whether Version Number is Correct after Upgrade

The command is as follows:
ZTE:> interversion

Command (No.2): interversion
APP Version COMM Version
-----------------------------------
ZXCS-MGW V4.12.10 B14 COMMV4.11.20 P1.B5
-----------------------------------
1 Record(s)
Executed command successful (elapsed 0s).
2.8 Service Upgrade

Service upgrade means upgrade of the foreground boards and independent boards.
For upgrade procedure of independent boards, please refer to Chapter two in
ZXUN-MGW V4.12.10_ Transformation to Independent Switching Board and
Upgrade Description.doc.
2.8.1 Preparing Foreground Upgrade Package

Use WinSCP to copy version package files to <$ZXHOME/[NE
directory]/cnvmverfile> of OMM server:

Note:
1. In general, $ZXHOME is /home/ngomm.
2. An example of [NE directory] is ngmgw_w_50. 50 is office number;
3. Version package files are appropriate version directories, e.g., all files and
directories in ZXUN-MGWV4.13.10.P2.B6\MGW\package and mgwboot_pp.pkg in
ZXUN-MGWV4.13.10.P2.B6\FIRMWARE
2.8.2 Powering Off Right OMP Board

On IE client interface, choose Data Configuration > Physical Configuration >
Hardware Management > Shelf > Blade > Blade Operation Info:
BOARD EPOWER ONOFF:CMMID=1,SLOT=10,OPT="POWEROFF";
Caution:
The active module on OMP board shall be switched over to left board before
power-off.

2.8.3 Deleting Old Version

Step 1: On IE client interface, choose Maintenance Management > Version
Management > Version Maintenance;
Step 2: Execute the <Delete Useless Package on OMP> command;
DEL USELESSPKG;
Step 3: After confirming the command is successful by seeing the result in the
operation record, continue with the next operation step.
2.8.4 Backing up ZDB

Step 1: Execute the data backup command:
UPG ONETIME:MODE="BACKUP";

Step 2: Back up ZDB files on foreground board:
[root@Gcz1-V4MGW ngomm]#mkdir /backup/zdb
[root@Gcz1-V4MGW ngomm]#cp -a $ZXHOME/ngmgw_w_31/server/data/zdb/upgrade
_onetime/31/backup/zdb
Note:
31 in ngmgw_w_31 should be replaced with the actual number used on site.
2.8.5 Upgrading ZDB

Step 1: Execute the data upgrade command (only one upgrade operation is allowed
in the upgrade procedure):
UPG ONETIME

Note:
ZDB upgrade procedure includes two sub-steps, which are executed in an

automatic manner:
1. Generate ZDB files of new version on OMM server;
2. Transfer ZDB files of new version to the OMP board.
2.8.6 Loading Version Package
Step 1: Click on the client interface to show all

commands, and then choose Maintenance Management > Version Management >
Version Maintenance.
Step 2: Execute the command of Load Version Package;
LOAD PKG:TYPE="LOAD"&"ACTIVE";
Figure 2-1 Load Version Package
Step 3: After the following dialogue box appears, click Yes.
Figure 2-2

Step 4: Confirm the version loading state.
After the command is executed, see the operation record; if success is displayed
and there is no error log in the information window, it indicates version loading
succeeded.
Step 5: Choose Maintenance Management > Version Management > Version

Query, and then click Query OMP Default Package;
SHOW DFTPKG;
Check the result in operation record by seeing the version number with highest
priority and last date is the target one.
2.8.7 Enabling Version Package

Execute the command of Enable Package, as shown in the following figure:
ENABLE PKG

The following dialogue box appears after the command is executed. Click Yes in the
box:
Important!
After the command is executed, all boards can be reset automatically and new
version can be powered on and run, hence the services can be interrupted.
2.8.8 Querying Foreground Version

Choose MML Terminal > Maintenance Management > Version Management >
Version Query, and execute the Show Running Package (SHOW RUNPKG)
command, to query the version currently running and the version has been
upgraded to the target one.
SHOW RUNVER;
Caution
This operation can be executed only after all foreground boards have been started
successfully; it normally takes 20 minutes for all boards to start.

2.8.9 Transferring Tables

Execute the SYNA command to transfer all tables
SYNA:STYPE="ALL";
2.8.10 Service Test
2.8.10.1 Basic Service Test
Test basic services according to Service Test Form.
2.8.10.2 Verifying New Functions and Solved Problems
Perform the verification according to the test cases in Release Notes.
2.8.11 Upgrading Standby Board

Upgrade of the standby board can performed after the test succeeds.

BOARD EPOWER ONOFF:CMMID=1,SLOT=10,OPT="POWERON";
2.8.12 Manual Block

Block all units and sub-units which are in block state before upgrade;
Block all signaling links, SCTPs, ASs and ASPs which are in block state before
upgrade.

3 Post-Upgrade Verification
Perform the switchover test.

4 Post-Upgrade Observation
Observe the system within 24 hours after upgrade to see whether the system
running status, basic services, alarm information, failure observation, main
performance data and CDR are normal.
During the following day after upgrade, collect the performance statistics every hour
and analyze important data to confirm the index does not decrease compared with
that before upgrade. Later, observe the data for a period of half day or full day and
then gradually the system can be maintained in a normal way.

5 Emergency Recovery
5.1 Processing Principle

During the upgrade, if one of the following problems cannot be solved before 4:00,
immediately report it to the project person-in-charge, related chief engineer in the
product support department and the customers person-in-charge. After getting the
permission, start the rollback procedure:
The problems encountered during the upgrade cannot be solved, or they

can only be solved after the specified period for the upgrade;
Service problems occur after the upgrade operation.
5.2 Rollback Conditions
Data backup is completed on OMM server before upgrade;
Foreground ZDB has been backed up
5.3 Emergency Recovery Steps
5.3.1 Emergency Recovery of Foreground Boards

If the left board has been upgraded but the right board is not, implement the rollback
steps being described in 5.3.1.1;
If both left and right boards have been upgraded, implement the rollback steps being
described in 5.3.1.2;
Perform simple service verification test after the foreground resumes working, and
the complete verification test shall start only after the background is recovered.
5.3.1.1 Rollback with Standby OMP not Upgraded
Step 1: Powering off the left board


BOARD EPOWER ONOFF:CMMID=1,SLOT=9,OPT="POWEROFF";
Step 2: Powering on the right board

Hardware Management > Shelf > Blade > Blade Operation Info
Step 3: Execute the command of Enable Package on OMM after OMP is powered
on
Choose Maintenance Management > Version Management > Version

Maintenance, and then the command of Enable Package:
ENABLE PKG;
The foreground automatically restarts. Then, choose Maintenance Management >

Version Management > Version Query, and then click Query Default Package:
SHOW DFTPKG;
Check the result in the Upload Message window by seeing whether the version
number with highest priority is correct.
Step 4: Service Test
Perform service test after rollback.

Step 5: Powering on the left board
If the services are confirmed to be normal, then power on the left board after the
rollback is successful.

5.3.1.2 Rollback with Standby OMP Upgraded
Step 1: Version Query
Choose Maintenance Management > Version Management > Version Query,

and then click Query Default Package:
SHOW DFTPKG;
The loading record can be shown in Upload Message, as shown below:
Figure 5-1 Version Package
Step 2: Activate Old Version

Maintenance, and then click Activate Package:

ACT PKG:PKGID=1078725126,PKGNAME="SBCJ_X86_GPB.pkg";
Caution
All versions with number 4.12.10.B6 should be activated. Please note that 4.11.10.
B11 here serves as an example, and is the original version number (before
upgrade) which needs to be activated. The activation command can be executed in
sequence: one time for one version only.
Step 3: Rollback ZDB
Execute <UPG ONETIME> to rollback ZDB:
UPG ONETIME:MODE="FALLBACK";
Important!
When executing this step, make sure that the ZDB file in the default foreground
ZDB backup path is consistent with the ZDB file that is manually backed up in 2.8.4
in terms of size and time.
In the example in 2.8.4:
Default path: $ZXHOME/ngmgw_w_31/server/data/zdb/upgrade_onetime/31
Backup path: /backup/zdb
If not consistent, overwrite the ZDB file in the default path with the ZDB file backed
up.
Step 4: Enable Version

Maintenance, and then click Enable Package:
ENABLE PKG
Important!
The foreground board resets automatically after the enable command is executed.

Step 5: Check foreground board version
After the foreground board is started, choose Maintenance Management >

Version Management > Version Query, and then click Query Default Package:
SHOW DFTPKG
Check the result in the Upload Message window by seeing whether the version
number with highest priority is correct.
Step 6: Service Test
Test services after rollback
5.3.2 Emergency Recovery of OMM Server

Only one option should be performed between DB file recovery and ZIP backup
recovery.
It is recommended that you should give the priority in using the mode of DB file
recovery; in case it fails, use ZIP backup recovery.
5.3.2.1 Automatic Rollback via OMM Interface
Caution:
The version number in this chapter is for your reference only (not the real
version number on site).
Step 1: Enter IP address of the server in IE; the port number is 8000; for example,
http://10.44.102.158:8000.
Step 2: If the agent has already been started, the login window appears. Log in as
root user, type password and then click OK. Refer to 2.7.1 for Starting Agent

Step 3: Select the NE and click Rollback.
Step 4: The following window appears.
Step 5: Click OK.

Step 6: After the rollback is finished, click on the right.
Step 7: After the OMM is started, transfer all tables.
5.3.2.2 ZIP Backup Recovery
Step 1: Stop all services of OMM
Dual-node operation description:

Right-click omm_exec and click Stop to stop the OMM execution, as shown in
the following figure:
Single-node operation description
[root@localhost /]#cd /home/ngomm
[root@localhostngomm]#./killall.sh
Step 2: Recover the backup files
Delete all files in $ZXHOME/
[root@Gcz1-V4MGW ngomm]#rm -rf $ZXHOME/
Copy the directory backed up in 2.5.2 to $ZXHOME
[root@Gcz1-V4MGW ngomm]#cp -a /backup/ngomm/ $ZXHOME/
Step 3: Start OMM server
Dual-node operation description
Right-click omm_exec and click Start to start the OMM execution.
Single-node operation description
[root@localhost /]#cd /home/ngomm

[root@localhostngomm]# ./run.sh
Step 4: Execute the following command to restore ZIP data backed up in

2.5.1
RESTORE:FILENAME="/backup/mgw50v4mgwb18";
Step 5: Transfer all tables
5.3.3 Service Verification

Implement detailed service verification after the background OMM is restored.
6 Other Matters
6.1 Handling Procedure of Exclusion Lock
Phenomenon:
When executing the SHOW USERLOCK command, if the following error information
appears, it indicates that the exclusion lock has been enabled.
Command (No.5): SHOW USERLOCK
Executed command failed (elapsed 0.13s). Reason: Command[SHOW USERLOCK] appl
y for lock[] error.
Exclusion lock: This lock is the lock with highest priority; so once it is enabled,
executing all other data configuration commands shall fail.
Solution:
At present, configure the parameters as follows to clear the lock:
CLIS SET:LOCKCLEAR=TRUE

7 References
None

Upgrade

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Upgrade

Caricato da

Copyright:

Formati disponibili

Operators LOGO

ZXUN MGW Upgrade Guide

2017 ZTE Corporation. All rights reserved.

ZTE Proprietarily Confidential 2014 ZTE Corporation. All rights reserved I

2 Upgrade Preparations ..................................................................................................... 3

II 2014 ZTE Corporation. All rights reserved ZTE Proprietarily Confidential

2.8.7 Enabling Version Package ........................................................................... 31

3 Post-Upgrade Verification ............................................................................................. 34

4 Post-Upgrade Observation ........................................................................................... 35

5 Emergency Recovery .................................................................................................... 36

6 Other Matters .................................................................................................................. 44

IV 2014 ZTE Corporation. All rights reserved ZTE Proprietarily Confidential

1.1 Applicable Scope

Source Version Target Version

1.2 Upgrade Components

Table 1-1 Upgrade Components

No. Component Upgrade or Not Remarks

2 Foreground boards Yes

1.3 Upgrade Impact

Table 1-2 Upgrade Impact

1.4 Version Changes Affecting Upgrade

ZTE Proprietarily Confidential 2014 ZTE Corporation. All rights reserved 1

1.5 Upgrade Procedure

Table 1-3 Upgrade Procedure (Recommended)

Task Operation Required Operation Description

ZIP data 10 Back up OMM

Upgrade OMM 1 hour

30 Load version, upgrade

Upgrade the 15 Upgrade the standby

2 2014 ZTE Corporation. All rights reserved ZTE Proprietarily Confidential

2.1 Software Preparation

2.1.1 Preparing Version Files

1 Current version file Used for rollback

New version files are downloaded

2.1.2 Copying Version File

2.1.3 Preparing Other Software

ZTE Proprietarily Confidential 2014 ZTE Corporation. All rights reserved 3

No Software Purpose Obtained from

OMP emergency Contact service centre for

Klinux OS Fix OS-related Contact service centre for

Upload version file Contact service centre for

Remotely control Contact service centre for

IE (version Log into the OMM http://it.zte.com.cn/Its/Down

Modify XML files Contact service centre for

The XMLspy is the designated software used to modify XML files!

2.2 Hardware Preparation

2.2.1 Preparing Hardware Tools

Table 2-2 Hardware Preparation

Tool Name Description

Screwdriver Used to loosen the screws on the board when inserting or

2.2.2 Preparing Standby Board

4 2014 ZTE Corporation. All rights reserved ZTE Proprietarily Confidential

there is any board error occurring during upgrade.

2.3 Document Preparation

Table 2-3 Document List

The upgrade guide of each upgrade NE. Check with the

Upgrade Checklist The checklist released together with Upgrade Guide

Service test form for the existing office. It is provided by

2.4 Upgrade Environment Preparation

Table 2-4 Environment Preparation

Password of root for KLINUX OS

IP address of OMM Server

ZTE Proprietarily Confidential 2014 ZTE Corporation. All rights reserved 5

2.5 Data Backup