Software Version Upgrade

8/13/2019 Software Version Upgrade

1/22

CN

Software Version Upgrade

V1.0

Softswitch-ZXSS10


2/22

2

Content

Upgrade Planning and Report

Upgrade Procedure

Issue Resolving

How to deal with emergency issue


3/22

3

Content


Upgrade Procedure

Issue Resolving



4/22

4

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


5/22

5

Version Upgrade Planning

New Requirement of Function or Software bug

Get confirmation from HQ of the version upgradeVersion

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


6/22

Registration on internal system

http://10.41.213.64/zte_pub/desk/main.asp

Get the support person list and method of contact number

6
http://10.41.213.64/zte_pub/desk/main.asphttp://10.41.213.64/zte_pub/desk/main.asp


7/227

Content


Upgrade Procedure

Issue Resolving



8/228

General Procedure


9/229

ZXSS10 SS1B version upgrade procedure

1Preparation and Backup

2Background upgrade

3Foreground upgrade

4Preliminary test

5Version Rollback

6Preliminary Test

7Watch over the traffic and Report


10/2210

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


11/2211

Background Upgrade

Stop the appservice. 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.


12/22


13/2213

Foreground upgrade

Upgrade Procedure

Upgrade mode Start-up Operation

Upgrade New-domain Board

Changeover CSN Board

Upgrade Old-domain Board

Stop upgrade mode operation


14/2214

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 d uty o f

perator to m ake a ful l sco pe Test of serv ice.


15/2215

Version Rollback

Rollback Process of Background

Rollback of Databasestop drop create import

Rollback of Man-machine Command Script

Rollback of Billing file

Rollback of app servicereplace 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


16/2216

Preliminary Test after Rollback

Same with the previous preliminary test after version upgrade


17/2217

Content


Upgrade Procedure

Issue Resolving



18/2218

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


19/2219

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


20/2220

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


21/2221

Q&A


22/22

22univ.zte.com.cn

Documents

Software Version Upgrade