Академический Документы
Профессиональный Документы
Культура Документы
Revision History
Version Date Author Reviewed by Tested by Remarks
2012-04-
V1.0 Sun Xiaoyong Zhu Qingjun
19
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
7 References ...................................................................................................................... 45
ZTE Proprietarily Confidential 2014 ZTE Corporation. All rights reserved III
ZXUN MGW Upgrade Guide
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
1 Overview
This document is applicable to ZXUN MGW upgrade and the applicable scope of the
upgrade is listed in the following table:
V4.12.10 V4.13.10
3 Firmware Yes
1.5 hours
Check alarms, analyze
System Check system
15:00-17:00 logs and performance
Check running status
statistics
Based on
Post- Post-upgrade Operations after
actual site 04:00-06:00
Upgrade operation upgrade
conditions
2 Upgrade Preparations
Caution:
Serial port cable Used for debugging and observing the boot information of
boards such as MP
Document Requirement
Release Notes
Caution:
Please read the documents above carefully beforehand to familiarize yourself with
the upgrade operation.
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:
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.
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.
/home/ngomm
Caution:
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
SET ISSMSSHELF:ISBID=4,SHFTYPE="MASTER";
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:
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:
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.
2011;
Database: /home/ngomm_data/ngomm_db/ngmgw_w_6/FIREBIRD_CM.FDB
Owner: SYSDBA
PAGE_SIZE 4096
Transaction - Next = 33
ODS = 11.1
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.
If the agent has not been started, go to the installation path: /home/installagent and
execute run.sh to start the agent.
[root@iMG-OMMinstallagent]# ./run.sh
Start setup
OK
[ OK ]
Step 2: The login window appears. Log in as root user, type password and then click
OK;
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 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 17: The disk space information is displayed. Click to go to the next step.
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.
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.
ZTE:> interversion
-----------------------------------
-----------------------------------
1 Record(s)
Note:
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
Caution:
The active module on OMP board shall be switched over to left board before
power-off.
DEL USELESSPKG;
Step 3: After confirming the command is successful by seeing the result in the
operation record, continue with the next operation step.
UPG ONETIME:MODE="BACKUP";
_onetime/31/backup/zdb
Note:
UPG ONETIME
Note:
LOAD PKG:TYPE="LOAD"&"ACTIVE";
Figure 2-2
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.
SHOW DFTPKG;
Check the result in operation record by seeing the version number with highest
priority and last date is the target one.
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.
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.
SYNA:STYPE="ALL";
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
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.
Step 3: Execute the command of Enable Package on OMM after OMP is powered
on
ENABLE PKG;
SHOW DFTPKG;
Check the result in the Upload Message window by seeing whether the version
number with highest priority is correct.
If the services are confirmed to be normal, then power on the left board after the
rollback is successful.
SHOW DFTPKG;
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.
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.
If not consistent, overwrite the ZDB file in the default path with the ZDB file backed
up.
ENABLE PKG
Important!
The foreground board resets automatically after the enable command is executed.
SHOW DFTPKG
Check the result in the Upload Message window by seeing whether the version
number with highest priority is correct.
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.
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
Right-click omm_exec and click Stop to stop the OMM execution, as shown in
the following figure:
[root@localhostngomm]#./killall.sh
[root@localhostngomm]# ./run.sh
RESTORE:FILENAME="/backup/mgw50v4mgwb18";
6 Other Matters
Phenomenon:
When executing the SHOW USERLOCK command, if the following error information
appears, it indicates that the exclusion lock has been enabled.
Exclusion lock: This lock is the lock with highest priority; so once it is enabled,
executing all other data configuration commands shall fail.
Solution:
CLIS SET:LOCKCLEAR=TRUE
7 References
None