Software Version Upgrade

V1.0 Softswitch-ZXSS10

CN

Content

Upgrade Planning and Report

Upgrade Procedure

Issue Resolving

How to deal with emergency issue

Content

Upgrade Planning and Report

Upgrade Procedure

Issue Resolving

How to deal with emergency issue

WWW
Why to upgrade the version
New function implementation or BUG fixing

What is a version upgrade

Replace the old version with new version

hoW to do the version upgrade

Change version files and database format

Version Upgrade Planning

New Requirement of Function or Software bug Get confirmation from HQ of the version upgrade Version date e.t.c Negotiate the operation with customer and determine the date Ask support from related department. (Network service department of DIV I / Network service department of R&D / Test department or R&D Solution discussion before implementation and registration Implementation Report the result internally and to customer
5

Registration on internal system

http://10.41.213.64/zte_pub/desk/main.asp Get the support person list and method of contact number

Content

Upgrade Planning and Report

Upgrade Procedure
Issue Resolving
How to deal with emergency issue

General Procedure

ZXSS10 SS1B version upgrade procedure

1Preparation and Backup 2Background upgrade 3Foreground upgrade 4Preliminary test<ZTE and Operator>

5Version Rollback
6Preliminary Test 7Watch over the traffic and Report

Preparation and Backup

Read and inspect the Guide carefully

Environment preparation and working status

confirmation

Related Software Inspection

Backup the important Alarms

Backup the Data and Programs

10

Background Upgrade
Stop the app service. Keep Oracle running Running Script Upgrade Background
Database Structure Upgrade Script Upgrade of Man-Machine Command APP Program upgrade

Start the APP service

Upload files for both master and standby computers, execute SQL script and start all.out app service on the master computer.

11

Foreground upgrade
Preparations
All.out App service is running normally

Install new Client of SS1b version

Related Data Configuration Data Backup Changing the Load Method of dbconfig.ini File Uploading Foreground Version Preparing Domain Division Configuration File Check Version Number by 1229 Command

12

Foreground upgrade
Upgrade Procedure
Upgrade mode Start-up Operation Upgrade New-domain Board Changeover CSN Board Upgrade Old-domain Board

Stop upgrade mode operation

13

Preliminary Test
Preliminary Test after Version Upgrade
Check whether GUI can connect to SS foreground normally View whether there are abnormal alarms, such as data dictionary is

loaded unsuccessfully.
Check whether the memory of each board is enough for use. If the office has SIP user or Other SS or AS, use 5400: module No.

to view whether SIP task of the active and standby boards where SIP is located is normal.
Open the command navigation tree and use the 1231 command to

check the CPU occupancy of SC, SPC, SSN and NIC boards
Attempt calls using all types of terminals processed by SPC and SC

board to see whether calls can be completed.

If all the above is ok, ask the maintenance person on duty of perator to make a full scope Test of service.
14

Version Rollback
Rollback Process of Background
Rollback of Database stop drop create import

Rollback of Man-machine Command Script

Rollback of Billing file Rollback of app service replace and start

Rollback of Foreground Version

man-machine command script file (*.INI) Replace the new version program of SC etc. Switch gateway to peer SoftSwitch manually

Restart the whole shelf

15

Preliminary Test after Rollback

Same with the previous preliminary test after version upgrade

16

Content

Upgrade Planning and Report

Upgrade Procedure
Issue Resolving
How to deal with emergency issue

17

Issue Resolving
Common Issues during the version upgrade
Errors occurred the implementation. Some boards cant start and run normally. Calls cant established. Some offices or some trunk groups/trunks are abnormal. Alarms

18

Method and Principal

Restoration of service in shortest time Comparing the issue scope with previous situation before upgrade Analyzing and dealing with the issue by ourselves Reporting to related person on duty for support if we cant fix in short time Reporting to related team leader and line manager (and higher level manager if need) to get more support and to reduce the potential risk of complain from the customer Timely report the progress of issue situation and push the person in charge to speed up until the issue is resolved Provide Issue Resolving Report
19

Report the Result

Feedback the result of upgrade on internal system Notice the result to related person (PM/Director/CTO) Report the result of upgrade to customer Notice the result to support persons/department

20

Q&A

21

univ.zte.com.cn

22