Split Mode procédure HLR Migration AWCC

Version 01

CS 30 SSNC/CCNCCP 113C/E

Issued by the Siemens TelecommunicationsJohannesburg, South Africa

Copyright Siemens SA 2007

The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved.Technical modifications possible . Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.

_______________________________________________________________SIEMENS

I

Author : Mr Michael Mohapi.

II

The document comprises 37 pages, all pages have issue no 1

This document was edited with Word 2003 and stored at 11/02/2007 on disk under file name Split Mode Procedure HLR Migration AWCC.doc

III

TABLE OF CONTENTS

1 INTRODUCTION 1-1

1.1 Subject of the Description 1-11.2 Processor, Version 1-11.3 Execution Time required 1-21.4 Quality Aspects 1-2

1.4.1 Protection against Electrostatic Discharges 1-21.5 Conventions 1-3

2 BASIC OPERATION 2-1

3 PREREQUISITES 3-1

3.1 Database 3-13.2 Test of the modification 3-13.3 Charging data treatment on SS 3-1

3.3.1 Charging files on CP MDD 3-13.3.2 Charging files on MP MDD (SAMAR handling) 3-2

3.4 LOG-File handling 3-23.5 Emergency 3-23.6 Upgrade Report 3-23.7 Phase 1: Preparation 3-3

3.7.1 Devising a Test Concept 3-33.7.2 Installation of OMT-1 3-33.7.3 Saving current APS 3-43.7.4 Transferring Command Files to MDD and Test of CP 3-43.7.5 Preparation 3-4

3.8 NPC Conversion using SPLIT Tool 3-103.8.1 Basic Overview 3-10

3.9 Delta database incorporation before NPC Change 3-113.10 Test Calls and subscriber displays before NPC change 3-113.11 Processor Splitting 3-11

3.11.1 Subscriber processing originating HLR 3-113.11.2 Splitting the processor 3-123.11.3 SPLIT tool Procedure 3-12

3.12 Confirm the converted Subscriber Data 3-133.13 Phase 4: Cut Over 3-13

3.13.1 Verification of Modification 3-133.14 Handling after cutover 3-16

3.14.1 Configuration of the ATMB 3-163.14.2 Checking System Availability after System Recovery 3-173.14.3 Checking the Call-Processing Functions 3-183.14.4 Activation of the LOG-Function in SSNC 3-19

3.15 Phase 5: Final works 3-193.15.1 Upgrade Report 3-19

IV

4 FALLBACK PROCEDURE 4-1

4.1 Stop the CP 4-14.2 Stop the System Operation 4-14.3 Configuration of the ATMB 4-14.4 Checking System on CP 4-24.5 Activation of BAP-0 and Periphery (if necessary) 4-34.6 Checking System on SSNC 4-34.7 Checking the Call-Processing Functions 4-34.8 Activation of MDD-1 4-34.9 Activation of access control and file security (only for SSNC) 4-44.10 Final tasks 4-4

5 ABBREVIATIONS 5-5

6 REFERENCES 6-1

V

1 INTRODUCTION

1.1 Subject of the Description

Presently AWCC has a Siemens core, ie 2 MSCs integrated with HLRs working on SR11. AWCC is currently using 6-digit Subscriber number (SN) format and 2 digits NDC (70).AWCC requires adding an additional digit to their subscribers MSISDN as follows:

Before AfterNational Prepaid 70 XXXXXX 70 0XXXXXXInternational Prepaid 93 70 XXXXXX 93 70 0XXXXXXNational Postpaid 70 XXXXXX 70 0XXXXXXInternational Postpaid 93 70 XXXXXX 93 70 0XXXXXX

The added digit (0) will be the leading digit of the SN. This digit will be the same for Prepaid subscribers and for Postpaid subs.

Dialling to a AWCC subscriber should follow the new dial plan where the AWCC subscriber will have 7-digit Subscriber number (SN). All dialling rules when dialing a AWCC subscriber will not change except of dialling an additional digit.

It would be possible to dial a AWCC subscriber using the following formats:

1. International format: 00 93 70 0XXXXXX.2. National format (without NDC suppression): 70 0XXXXXX.

It should be also possible for a user to dial using the old dialing scheme, i.e. with 6-digit subscriber SN for a transitional period. In this transitional period, dialling to subscriber can be done using either 6 or 7 digits.

When the transitional period ends, it is only possible to dial with 7 digits. An announcement should play to inform users who dial 6-digit SN that the new numbering plan is implemented and that dialing a AWCC subscriber must dial a 7-digit SN.

1.2 Processor, Version

Processor: CP 113C/E

Version: CS 30 SSNC

1.3 Execution Time required

The time taken for execution of this procedure depends on the size of the modification required.

1.4 Quality Aspects

1.4.1 Protection against Electrostatic Discharges

ESD - Guidelines

Note : Always comply with the ESD guidelines when working with D900.

Summary: Always wear a grounded armband before extracting or inserting modules or cables.

Work on modules should only be performed on suitable, grounded surfaces.

Only use ESD-compliant bags and cases to transport modules.

1.5 Conventions

The following conventions are used for symbols in the description:

BCT- 0 Command entry on the OMT-0

BCT- 1 Command entry on the OMT-1

BCT- 0/1 Command entry on the OMT-0 or OMT-1

SC/BCT-0 Enter command optionally on OMT-0, OMT-1 or SC

SC Enter command on Switch Commander

PC Enter command on PC

Operator intervention

! Check the requested status

´ Jump with condition

ð Jump without condition

2 BASIC OPERATION

3 PREREQUISITES

3.1 Database

The official database delivered from PITAC must be used.

This procedure must be done by qualified SIEMENS personnel. The handling of customer specific data, especially Billing Data, should be done by O&M personnel of the customer, because of customer specific procedures.

3.2 Test of the modification

A test of the modifications has to be worked out by the customer in accordance with the Siemens TAC.

The test should be performed by TSC1/2 personnel and the results logged.

3.3 Charging data treatment on SS

We have to distinguish between two possible ways of charging saving:

1. The charging data will be hold on the CP – in this case please read carefully chapter 3.3.1 Charging files on CP MDD.

2. The charging data will be hold on the MP by means of SAMAR files – in this case please read carefully chapter 3.3.2 Charging files on MP MDD (SAMAR handling)

3.3.1 Charging files on CP MDD

The strategy for saving the charging data in this configuration is the following:

Transfer of charging data to files on CP MDD-0 before cutover Transfer the charging data from CP-MDD-0 to SC After cutover transfer the charging data from SC to CP MDD-1 Saving the charging data by Billing center

You need to copy back the saved charging files from the SC to the CP MDD after the cut over. From there they can be saved by the billing center in the normal way; only the name is different from the regular charging file name. Please take care that they are allowed to transfer these file (file security settings).

You have to execute the Q3 command for each file:

SC <SEND FILE: SOURCE FILE NAME = . …\SCBase\UserHomeDir\<ntuser>\upgrade\charge\<filename>,DESTINATION FILE NAME=<allowed filename>,TRANSFER TYPE=FTP,COPY MODE= BINARY,FILE WRITING MODE=OVERWRITE;

3.3.2 Charging files on MP MDD (SAMAR handling)

No special handling is necessary, because the files are located on the MP MDD which is not involved in the Split of the CP. The charging data will be saved to MP MDD short before cutover of CP113 by command file.

3.4 LOG-File handling

No LOG-File handling will be supported by this procedure. Therefore, inform the customer that no changes to the Exchange should be done during the execution of this procedure.

All possible changes (hopefully no changes), which are done after the split of the CP will be lost.A recovery up to level ISTART2G can occur in SSNC configuration because of a mismatch in the CP / MP database after cutover.

NO CONFIGURATIONS OF THE EXCHANGE DURING THE EXECUTION OF THIS PROCEDURE ALLOWED!

3.5 Emergency

In case of Emergency call emergency number (24 hours):

3.6 Upgrade Report

After each Upgrade we need a short upgrade report. (use form “D1Rückmeldung_XX.doc”)It has to be submitted via e-mail (see distribution list on the top of the from) and to be put into the IMS directory.

DETAILED DESCRIPTION

3.7 Phase 1: Preparation

3.7.1 Devising a Test Concept

After the modification the new function must be tested. The test concept should be devised in co-operation with the customer.

3.7.2 Installation of OMT-1

If the CP is equipped with only one OMT/BCT (OMT-0) an additional OMT/BCT has to be connected as OMT-1.

You can skip this chapter if both OMT/BCT are connected.

CP113C:

Connect the cable from OMT-1 at IOPUNI-1 plug position 07C281P1.

CP113E:

Connect the cable from OMT-1 at IOPUNI-1 plug position 04C295P1.

BCT-1 <STAT SSP;PLEASE ENTER USERID<userid>PLEASE ENTER CURRENT PASSWORD<password>

! OMT-1 in ACT

SC/BCT <DISP DEVAUT;

DEVICE AUT AUTHORIZATION ----------+-------+------------------------ OMT-00 1 1 OMT-01 1 1

If full device authorization for OMT-1 is not provided:

SC/BCT <MOD DEVAUT: DEV=OMT-01, AUT=1,OAUT=0<CONF OMT: OMT=1, OST=MBL;<CONF OMT: OMT=1, OST=ACT;

SC/BCT <DISP OUTSUP;

OUTPUT SUPPRESSION: DEACTIVATEDOUTPUT DEVICE : 0C00 - 0C01 DEVICE TYPE : APPLICATION ID :

If output suppression is active:

SC/BCT <DACT OUTSUP:LOCDEV=SYSTEMDEVICE-FUOMT;

3.7.3 Saving current APS

The current APS is transferred to MO for safety reasons.

Save the APS according procedure SW216 in manual MMN:SW.

3.7.4 Transferring Command Files to MDD and Test of CP

Command file transfer and PC – MOD connection

_ Insert an MO with CS3.0 command files in MOD-0/1.

<TRANS FILE:FILE=x, VSNS=<vsn-nr>, MODE=CRD, COPMOD=CHAR;

Remove MO from MOD-0/1

3.7.5 Preparation

3.7.5.1 Testing the processor units

Check the disk file HF.MCP.HWERROR for sporadic faulty entries and clear if necessary.The following test is started to check the HW status of the CP. If faults are detected by the test, they are to be cleared according to the maintenance manual (MMN:CP).

Full CP redundancy is required.

BCT- 0/1<STAT SSP;

BCT- 0/1<EXECCMDFILE:FILE=CF.30.TESTCP;

3.7.5.2 Checking the System Availability

Interrogation of the status of the CP:SC/BCT <EXEC CMDFILE: FILE=CF.30.SYSTAT;

! Required file states:Update status is normalAll double files are available on both disksAll files for activated charge, IA features are available

! Required states of CP units:BAP-0 = MAS or SPR BAP-1 = SPR or MASCAP-0...9 = ACT (If available)AMP-0 = ACT AMP-1 = ACT (only SSNC)IOC-0 = ACT IOC-1 = ACTCMY-0 = ACT CMY-1 = ACTBCMY-0 = ACT BCMY-1 = ACT (only CP113C)IOPMB-32 = ACT IOPMB-33 = ACTIOPMB-34 = ACT IOPMB-35 = ACT (If available)IOPMB-40 = ACT IOPMB-41 = ACT (CCG)IOPUNI-0 = ACT IOPUNI-1 = ACTIOPTA-0 = ACT IOPTA-1 = ACTIOPLAU-0 = ACT IOPLAU-1 = ACT (X25LINK)LAU-0 = ACT LAU-1 = ACT (X25LINK)MDD-0 = ACT MDD-1 = ACTMOD-0 = ACT MOD-1 = ACTOMT-0 = ACT OMT-1 = ACTCSC-0 = ACT CSC-1 = ACT (If available)X25LINK-0 = ACT X25LINK-1 = ACT (If available)

! Required states of peripheral units:MB: MB-0 in ACT

MB-1 in ACT

SN: SN-0 in ACTSN-1 in STB

CCG: CCG-0 in ACT/STB, CCG-1 in STB/ACT

! Required states of peripheral units:LTG: LTG 0-1 - 3-63 in ACT, CH0/CH1 in ACT or STB

ATM bridge:

AMP WORKING STATE PBI AMPR WORKING STATE PBI--------------+-------------------------+------+----------+------------------------------+----AMP-0 WORKING 8 AMP-1 SPARE 9

or reverse

Interrogation of the status of the SSNC:

SC execute SCN MP.21.SYSTAT

! If admin./operational states are displayed they must show the following states:ADMIN. STATE: UNLOCKEDOPERATIONAL STATE: ENABLED

! Required alarm state:System fully diagnosed without faults and alarms

Check the interrogation results. If the current operating conditions differ from the normal states, appropriate configurations must be made.Clear all problems and remove alarms before continuing.

3.7.5.3 Alarm surveillance for SSNCThe system must be fault free before starting the upgrade activities. All urgent alarms have to be solved before starting upgrade.

Start the Alarm and Message display:

PC START Fault Management SC Alarm and Message Display

Select specific “Usergroup”Select “Available Workspaces”Press “Open”

If any alarms are shown, select the corresponding unit and solve the problem

3.7.5.4 Release of ACC, RPPW and File security For operating the system any time during System Upgrade the access control, RPPW and file security must be deactivated. After Upgrade the original data will be activated again.

SC DISP ACCFG; (Default access must be ALLOW for all entries)

MOD ACCFG: DEFAULT ACCESS=<ALLOW for all entries>;

SC DISP AUTHDEF; (Default authentication must be ALLOW)

MOD AUTHDEF: DEFAULT AUTHENTICATION=ALLOW;

SC DISP FSCFG; (All default accesses must be ALLOW)

MOD FSCFG: DEFAULT ACCESS=<ALLOW for all entries>;

3.7.5.5 Deletion of invalid event destination entriesIn case of faulty recoveries it’s possible that some invalid event destination could be created.These entries have a negative event destination number with 10-digits. Before start saving the APS these event destination have to be deleted. Otherwise the saving of the APS will be stopped with fault report.

However following negative event destination numbers must not be deleted:o Lid Recordo Lid Info

SC DISP EVDEST;CAN EVDEST:EVENT DESTINATION=<10-digits negative number>;

3.7.5.6 Deactivation of CSC and X25 links

During the System Upgrade process, no commands which may disturb correct operation must be entered from the OMC. If an X25 connection is existing, it must be configured to PLA.

! For FTP connection, inform the customer not to use it for configuration of the switch during the upgrade time.

SC/BCT <CONF CSC:CSC=<csc-no>,OST=MBL;<CONF CSC:CSC=<csc-no>,OST=PLA;

<CONF X25LINK:X25LINK=<link-no>,OST=MBL;<CONF X25LINK:X25LINK=<link-no>,OST=PLA;

! If billing records are transferred via X25link, this <link-no> has to stay in ACTbut strictly only for this purpose with no database changes allowed during upgrade.

3.7.5.7 Deactivation of the routine testsSC/BCT <DISP SSPRT;

<INHIB SSPRT; If routine tests are globally allowed

3.7.5.8 Setting full command authorizationFull command authorization is required on both OMTs for the change of the Project database. Change the authorization if necessary.

BCT- 0/1<DISP DEVAUT;

TABLE OF DEVICE AUTHORIZATION:DEVICE AUT AUTHORIZATION CLASS----------+-------+-------------------------------------------------OMT-00 1 1OMT-01 1 1

If both OMTs do not have full command authorization, enter the following commands:BCT- 0/1<MOD DEVAUT:DEV=OMT-00, AUT=1, OAUT=0;

<MOD DEVAUT:DEV=OMT-01, AUT=1, OAUT=0;

BCT- 0/1<DISP OUTSUP;<DACT OUTSUP: LOCDEV=SYSTEMDEVICE-FUOMT; if active

Attention: It must be ensured that the Authorization class is sufficient for execution of the procedure.Check that all necessary commands e.g. MOD FILEAUT can be executed.

3.7.5.9 Check Split OptionSC/BCT <DISP SPLITOPT; Split option is reset

<RSET SPLITOPT; If split option is set

3.7.5.10 Lock Routine Check Sum MDD Audit

SC/BCT <DISP MDDAUDIT;<MOD MDDAUDIT: LOCKSTAT=LOCKED; If MDD Audit is ”unlocked”

3.7.5.11 Display and stop Time and Traffic measurement jobs

SC/BCT <DISP CFTJOB;<STOP JOB:JN=<jn>; if jobs lie in upgrade period

<CAN JOB:JN=<jn>, CMDCOD=<xxxxx>; xxxxx ð see DISP CFTJOB

SC/BCT <DISP JOB;<DISP MUSMORD; Mobile traffic measurem. orders

<DISP MUSFICH; Mobile traffic file characteristic

<DISP TRAMORD; Display active meas. orders

<STOP JOB: JN=xx; Stop active meas. orders

<CAN JOB: JN=xx, CMDCOD=xxx; Cancel terminated orders

<DISP TRAFICH; Display status of meas. Orders

If the traffic measurement has been accepted or is active, it must be stopped or cancelled. The TS and MT files must then be saved to MO.

Insert MO in MOD-1.

BCT- 0/1 <INIT MO: MOD=1, VSN=<vsn-nr>, CD=EBC;<TRANS FILE: FILE=<cmdfile>, VSNR=<vsn-nr>, COPMOD=SSWF; <RSET MO: MOD=1;

Saving error symptom files: Save these files for evaluation at a later time.

Saving Single Files on MDD-1MDD-1 is used for booting with the modification, so single files on MDD-0 will get lost. Therefore they have to be transferred to MDD-1 or saved to MO.

SC/BCT <DISP FILE; Interrogation of single files

! Check the result of the “DISP FILE” command to see whether single files are stored on MDD-0. If so, they must be transferred to MDD-1.

SC/BCT <DACT FNS:FNS=<fns>; If necessary

<TRANS FILE:FILE=<single file new name>/<single file old name>,VSNR=VSN001,COPMOD=<mode>;

<DEL FILE:FILE=<single file old name>;

<TRANS FILE:FILE=<single file old name>/<single file new name>,VSNS=VSN001,COPMOD=<mode>,MODE=CRD;

<DEL FILE:FILE=<single file new name>;

<ACT FNS:FNS=<fns>; If necessary

3.7.5.12 Saving of charging data

! Only to be executed in a MSC/VLR!

Before the split of the CP, all charging data are transferred to MDD.

Let the billing center save the charging data collected until now in order to decrease the amount of data to be handled until cut over.

3.7.5.13 Switchover of the LOG file

SC STAT INPLOG;

! "ADMINISTRATIVE STATE": UNLOCKED"OPERATIONAL STATE": ENABLED

Note: If the LOG6 active, the LOG1 has to be saved before the execution of the MOD INPLOGFILE command. Otherwise it will be overwritten.

Saving of LOG file (if necessary):Insert an empty MO into MOD-0 of the SSNC and transfer the logfiles, which were active since the last startup - tested backup generation. The list with the logfiles you should get from the customer. If there is no list available, please copy every logfile.SC

CONFMODMP:SIDE=0,ADMINISTRATIVE STATE=UNLOCKED,LABEL=YES; LIST FILE: DIRECTORY NAME=\LG*; COPYINPLOGFILE:LOG FILE NAME=<LOGFILE>,DEVICE NAME=MOD0; LIST FILE: DIRECTORY NAME=MOD0:\; CONFMODMP:SIDE=0,ADMINISTRATIVE STATE=LOCKED,LABEL=NO;

SC MOD INPLOGFILE: NEW LOGFILE NAME=LOG<n+1>; (e.g. LOG3)

SC LIST FILE: DIRECTORY NAME = \LG*; look for capital letters

The LOG files LG.LOG<n>.A0/A1 are closed, the LOG files LG.LOG<n+1>.A0/A1 opened.

3.8 NPC Conversion using SPLIT Tool

3.8.1 Basic Overview

An overview of the different tasks to be performed is shown below.

Procedure for the NPC Conversion using Split Tool

Step 1Delta database incorporation before NPC Change

Step 2Test Calls and subscriber displays before NPC Change

Step 4Using SPLIT Tool to do mass update of HLR database

Step 3Processor Splitting

Step 5Confirm the converted Subscriber Data

Step 6Perform Istart2 (Reload of Data only)

3.9 Delta database incorporation before NPC Change

A delta database must be incorporated in all MSC/VLR/HLR’s before starting the actual NPC change. This delta database must have no influence on the current active database and only becomes active after the cutover. The delta database includes code points for routing to the MIC Loop, Interrogation, Handover and Call Forwarding. In addition, a Global Title Rule (SPGTRUL) is required in all MSC/VLR’s, which is needed for locating the HLR with the Subscriber Number.

3.10 Test Calls and subscriber displays before NPC change

A Test Concept (SOW) must be defined with all possible call scenarios, which will be impacted by the NPC change. These Test calls must be performed and the results documented. In addition, the charging tickets for these test calls should be saved and kept for analysis by the charging experts. Another important requirement is that a set of reference subscribers be defined, which must incorporate the NPC and SN number range in the HLR. This command file must consist of the commands to display the SS Data of the selected reference subscribers. This reference subscriber command file must be executed now and the results saved in order to compare with results after the NPC change.

3.11 Processor Splitting

Originating-HLR Destination-HLRP30305-X1118-U406-01-7618 4-16

3.11.1 Subscriber processing originating HLR

The destination CP113 is split into two subsystems, SS and NSS, with BAP-0 as master.<STAT SSP;! BAP-0 = MAS BAP-1 = SPR

<COM BAP; if BAP-0 = SPR

Note: If the COMBAP command is rejected due to a hanging job, an NSTART1 must be performed.

The SCIs stay blocked until the Cutover has been executed! If you leave them unblocked you’ll loose all SCIs from this moment on because they are entered in the CMY/MDD on the SS, but the tool reads the subscriber database from the MDD on the NSS. The CMD file blocks and activates all SCI relevant command, please check/adapt the file according to the current status in your network.

3.11.2 Splitting the processor

<EXEC CMDFILE:FILE=CF.30.BLKSCI;<SET SPLITOPT; Setting Split Option in SS<MOD LOGFILE: FILE=<xxx>; Switching over to logfile xxxName of new Logfile: ____________ (for CCNC only)

<SPLIT SSP: TEST=N, SUP=N, APSCHG=Y;The following message is displayed on the OMT-0 (example):NON-SWITCHING UNITS--------------------------------------------------------------BAP-1 BCMY-1 CMY-1 IOC-1 IOPMB-1IOPMB-33 IOPMB-35 IOPMB-41 IOPMB-43 IOPMDD-1IOPMTD-1 IOPSCDV-1 IOPTA-1 MDD-1 MTD-1OMT-1 CSC-1 ......

Originating-HLRP30305-X1118-U406-01-7618

Press BOOT key at BAP-1

The Display at the MP (BAP 1) changes to track point A925 (IPL menu). If the track point is exceeded, the boot key must be pressed again immediately !Installation recovery side-1 (NSS):FOR;;INS;IOC-1;530XXXXX; (for CS3.0)<cPLEASE ENTER USERID<<userid>PLEASE ENTER CURRENT PASSWORD<password><START FCP;<START OM;<START SFGSW;<START CSWD;<ACT HLRCHP; Note: wait for execution long time jobPress BOOT key at BAP-1FOR;; STOP;

3.11.3 SPLIT tool Procedure

Execute the SPLIT tool Procedure. Following the attached Readme.txt

3.12 Confirm the converted Subscriber Data

Refer to the output of the Split Message"Change of subscriber data ended successfully".

3.13 Phase 4: Cut Over

3.13.1 Verification of Modification

Only Data Base changes can be verified at this stage (Installation Recovery) by TSC1/2 personnel. Functional test can be performed after cut over.

´ Have the results been properly documented?

YES: ð continue with the next section

The SS is stopped and on NSS System Recovery ISTART2 is started.

BCT-1 < RSET SPLITOPT;

Before you start the system from side 1, it’s time now to look for the Side 0 (SS) and stop the System:

SC STAT ATMB;

ATMB 1 0 = Unlocked / Enabled 1 = Unlocked / Disabled

SC DISPGENCPMP: VSN=MDD, Device Name=MDD;

SC CONFATMB:ATMB=1, Admin. State=LOCKED, Hazard check=NO;STAT ATMB;

ATMB 1 0 = Locked / Disabled 1 = Locked / Disabled

Press the BOOT key on BCMY-0(CP113C) / CMYE-0(CP113E)

!! S Y S T E M I N T E R R U P T I O N !!

BCT-0 ;STOP;

! INITIAL START STOPPED

Switch off power from BAP-0 Switch off power from MDD-0

Press the BOOT key on BCMY-1(CP113C) / CMYE-1(CP113E)

BCT-1 FORMAT;;MAN;IOC-1;35xxxxxx;DATA;

At this point the MBD-0 must also be reset.

Reset the module MBDCG on MBD-0, 04C223 Switch on power from BAP-0

System messages:##### RECOVERY PROGRESS MESSAGE : B264 ##### RECOVERY LEVEL : ISTART2 START OF DIGIT TABLE DOWNLOADING 17:44:59

##### RECOVERY PROGRESS MESSAGE : B274 ##### RECOVERY LEVEL : ISTART2 START OF LTU DATA DOWNLOADING 17:45:41

##### RECOVERY PROGRESS MESSAGE : B284 ##### RECOVERY LEVEL : ISTART2 START OF LTG PORTDATA DOWNLOADING 17:45:44

##### RECOVERY PROGRESS MESSAGE : B2A4 ##### RECOVERY LEVEL : ISTART2 START OF LTG ACTIVATION 17:45:47

##### RECOVERY PROGRESS MESSAGE ##### DLU / V5IF PORT DATA DOWNLOADING START 1. DLU / V5IF 17:46:02

##### RECOVERY PROGRESS MESSAGE ##### DLU / V5IF PORT DATA DOWNLOADING START 7. DLU / V5IF 17:46:07

##### RECOVERY PROGRESS MESSAGE : B3E4 ##### RECOVERY LEVEL : ISTART2 END OF LTG LOADING 17:46:15

SYSTEM - RECOVERY INFORMATION

REASON : REQUIRED MANUAL START

DATE : xx-xx-xxTIME : xx:xx:xxUNIT : BAPM

REQUESTED LEVEL : ISTART2EXECUTED LEVEL : ISTART2EXECUTED ACTION(S) : MEMORY HAS BEEN INITIALIZED LTGS RELOADED WITH DATA

CALL PROCESSING STARTED: xx:xx:xxRECOVERY DURATION : xxx SECONDS

APS GENERATION : 35xxxxxx

STATISTICS : ERROR COUNTER : THRESHOLD : INTERVAL : SEC

EXCEPTIONS : CONFIGURATION FAILURES OF PERIPHERAL UNITS========== DURING RECOVERY

UNIT UNIT UNIT UNIT UNIT---- ---- ---- ---- ----

´ Recovery successful ?

YES: well donego on with the procedure

NO: ðdon’t paniccontinue with chapter 5. Fallback Procedure

3.14 Handling after cutover

3.14.1 Configuration of the ATMB

Check that system is up again:

SC/BCT-1 <STAT SSP;

PLEASE ENTER USERID<userid>PLEASE ENTER CURRENT PASSWORD<password>

SC STAT ATMB;

ATMB 1 0 = Locked / Disabled 1 = Locked / Disabled

ATMB 2 0 = Unlocked / Enabled 1 = Unlocked / Enabled

ATMB 3 0 = Unlocked / Enabled 1 = Unlocked / Enabled

SC CONFATMB:ATMB=1, Admin. State=UNLOCKED, Hazard check=NO;

SC STAT ATMB;

ATMB 1 0 = Unlocked / Enabled 1 = Unlocked / Enabled

ATMB 2 0 = Unlocked / Enabled 1 = Unlocked / Enabled

ATMB 3 0 = Unlocked / Enabled 1 = Unlocked / Enabled

Start Call through test

The call test can be started now. It will be executed by MTC – Touch staff. The same call test as performed in before the cutover must be repeated. The results must be logged appropriate and compared, there should be no differences.

SC/BCT-1 <ACTHLRUPD: VLRISD = X; Activation of a map message ‘RESET’ to all VLR’s

3.14.2 Checking System Availability after System Recovery

SC/BCT-1 <EXEC CMDFILE: FILE=CF.21.SYSTAT;

! Required states of CP units:BAP-0 = SPR BAP-1 = MASCAP-0..9 = ACT (If available)AMP-0 = ACT AMP-1 = ACT (only SSNC)IOC-0 = ACT IOC-1 = ACTCMY-0 = ACT CMY-1 = ACTBCMY-0 = ACT BCMY-1 = ACT (only CP113C)IOPMB-32 = ACT IOPMB-33 = ACTIOPMB-34 = ACT IOPMB-35 = ACTIOPMB-36 = ACT IOPMB-37 = ACTIOPMB-38 = ACT IOPMB-39 = ACTIOPMB-40 = ACT IOPMB-41 = ACT (CCG)IOPUNI-0 = ACT IOPUNI-1 = ACTIOPTA-0 = ACT IOPTA-1 = ACT

! Required states of CP units:IOPLAU-0 = ACT IOPLAU-1 = ACT (X25LINK)LAU-0 = ACT LAU-1 = ACT (X25LINK)MDD-0 =*MBL/UNA MDD-1 = ACTMOD-0 = ACT MOD-1 = ACTOMT-0 = ACT OMT-1 = ACTCSC-0 = PLA CSC-1 = PLA (If available)X25LINK-0 = PLA X25LINK-1 = PLA (If available)

! Required states of peripheral units:MB: MB-0 in ACT

MB-1 in ACT

SN: SN-0 in ACTSN-1 in STB

CCG: CCG-0 in ACT/STB, CCG-1 in STB/ACT

LTG: LTG 0-1 through 0-63 in ACT, CH0/CH1 in STB /ACTLTG 1-1 through 1-63 in ACT, CH0/CH1 in STB /ACTLTG 2-1 through 2-63 in ACT, CH0/CH1 in STB /ACTLTG 3-1 through 3-63 in ACT, CH0/CH1 in STB /ACTLTGs 4,5,....31-1 through 4,5,....31-63 in PLA dependent on DETYPE

DLU: DLUC-0,1 in ACT

ATM bridge:

AMP WORKING STATE PBI AMPR WORKING STATE PBI----------+---------------------------+------+----------+--------------------------+----AMP-0 WORKING 8 AMP-1 SPARE 9

or reverse

3.14.3 Checking the Call-Processing Functions

After determining the system status, a quick check of the call-processing functions should be carried out.

´ System operation successful ?

YES: well donego on with the procedure

NO: ðdon’t paniccontinue with chapter 5. Fallback procedure

3.14.4 Activation of the LOG-Function in SSNC

SC STAT INPLOG

! "ADMINISTRATIVE STATE":LOCKED"OPERATIONAL STATE": ENABLED

SC SET INPLOG: LOG FILE NAME" = LOG<n+1>;

! This command generates a Master-, MML-, Q3-Binary- and Text-File

SC STAT INPLOG

! "ADMINISTRATIVE STATE":UNLOCKED"OPERATIONAL STATE": ENABLED

3.15 Phase 5: Final works

3.15.1 Upgrade Report

Now it is time to give a short Upgrade Report to Munich (it is mandatory).

Following information is required:

name of caller telephone number of caller country where the Upgrade was executed customer / project Exchange ID outage time during cutover problems during Upgrade no/yes (if yes short description)

END OF PROCEDURE

4 FALLBACK PROCEDURE

If you have to execute a fallback, before execution of the fallback procedure contact immediately Upgrade Emergency in Munich for further advice.

4.1 Stop the CP

SC/BCT-1 <STAT SSP;

UNIT OST UNIT OST UNIT OST------------+----- ------------+----- ------------+-----BAP-0 SPR BAP-1 MAS CAP-0 ACT

<COMBAP; // if necessary

<CONF BAP:BAP=0,OST=MBL;

SC STAT ATMB; ATMB 1 0 = Locked / Enabled

1 = Locked / EnabledIf not Locked then:

SC CONFATMB:ATMB=1, Admin. State=LOCKED, Hazard check=NO;STAT ATMB;

ATMB 1 0 = Locked / Disabled 1 = Locked / Disabled

Switch off power from BAP-0 Press BOOT key on BCMY-1(CP113C)/CMYE-1(CP113E)

BCT-1 ;STOP;

! INITIAL START STOPPED

Switch off power from MDD-1

4.2 Stop the System Operation

SC STAT ATMB; ATMB 1 0 = Locked / Disabled

1 = Locked / Disabled ATMB 2 0 = Unlocked / Enabled

1 = Unlocked / Enabled ATMB 3 0 = Unlocked / Enabled

1 = Unlocked / Enabled

Switch on power from MDD-0 // wait 30 sec.

Press BOOT key on BCMY-1(CP113C)/CMYE-1(CP113E)

BCT-1 FORMAT;;MAN;IOC-0;35xxxxxx;DATA;

At this point the MBD-1 must also be reset.

Reset the module MBDCG on MBD-1, 05C223

Switch on power from BAP-0

4.3 Configuration of the ATMB

Check that system is up again:

SC/BCT-0 <STAT SSP;

PLEASE ENTER USERID<userid>PLEASE ENTER CURRENT PASSWORD<password>

SC STAT ATMB;

ATMB 1 0 = Locked / Disabled1 = Locked / Disabled

ATMB 2 0 = Unlocked / Enabled1 = Unlocked / Enabled

ATMB 3 0 = Unlocked / Enabled1 = Unlocked / Enabled

SC CONFATMB:ATMB=1, Admin. State=UNLOCKED, Hazard check=NO;

SC STAT ATMB;

ATMB 1 0 = Unlocked / Enabled1 = Unlocked / Enabled

ATMB 2 0 = Unlocked / Enabled1 = Unlocked / Enabled

ATMB 3 0 = Unlocked / Enabled1 = Unlocked / Enabled

4.4 Checking System on CP

Check Split Option:

SC/BCT-0 <DISP SPLITOPT;<RSET SPLITOPT; // if necessary

SC/BCT-0 <EXEC CMDFILE: FILE=CF.21.SYSTAT;

! Required states of CP units:BAP-0 = SPR BAP-1 = MASCAP-0..9 = ACT (If available)AMP-0 = ACT AMP-1 = ACT (only SSNC)IOC-0 = ACT IOC-1 = ACTCMY-0 = ACT CMY-1 = ACTBCMY-0 = ACT BCMY-1 = ACT (only CP113C)IOPMB-32 = ACT IOPMB-33 = ACTIOPMB-34 = ACT IOPMB-35 = ACTIOPMB-36 = ACT IOPMB-37 = ACTIOPMB-38 = ACT IOPMB-39 = ACTIOPMB-40 = ACT IOPMB-41 = ACT (CCG)IOPUNI-0 = ACT IOPUNI-1 = ACTIOPTA-0 = ACT IOPTA-1 = ACT

! Required states of CP units:IOPLAU-0 = ACT IOPLAU-1 = ACT (X25LINK)LAU-0 = ACT LAU-1 = ACT (X25LINK)MDD-0 = ACT MDD-1 =*MBL/UNAMOD-0 = ACT MOD-1 = ACTOMT-0 = ACT OMT-1 = ACTCSC-0 = PLA CSC-1 = PLA (If available)X25LINK-0 = PLA X25LINK-1 = PLA (If available)

! Required states of peripheral units:MB: MB-0 in ACT

MB-1 in ACT

SN: SN-0 in ACTSN-1 in STB

CCG: CCG-0 in ACT/STB, CCG-1 in STB/ACT

LTG: LTG 0-1 through 0-63 in ACT, CH0/CH1 in ACT/STBLTG 1-1 through 1-63 in ACT, CH0/CH1 in ACT/STBLTG 2-1 through 2-63 in ACT, CH0/CH1 in ACT/STBLTG 3-1 through 3-63 in ACT, CH0/CH1 in ACT/STBLTGs 4,5,....31-1 through 4,5,....31-63 in PLA dependent on DETYPE

ATM bridge:

AMP WORKING STATE PBI AMPR WORKING STATE PBI----------+---------------------------+------+-----------+----------------------------+------AMP-0 WORKING 8 AMP-1 SPARE 9

or reverse

4.5 Activation of BAP-0 and Periphery (if necessary)

SC/BCT-0 <STAT SSP;<CONF BAP:BAP=0,OST=MBL; If BAP-0 is not active

<CONF BAP:BAP=0,OST=SPR; If BAP-0 is not active

<CONF MB:MB=1,OST=ACT;<CONF SN:SN=1,OST=ACT;

4.6 Checking System on SSNC

Interrogation of the status of the SSNC:

SC execute SCN MP.21.SYSTAT

! If admin./operational states are displayed they must show the following states:ADMIN. STATE: UNLOCKEDOPERATIONAL STATE: ENABLED

If the current operating conditions differ from those above , appropriate configurations must be made. Clear all problems and remove alarms before continuing.

4.7 Checking the Call-Processing Functions

After determining the system status, a quick check of the call-processing functions should be carried out, see test concept in chapter.

4.8 Activation of MDD-1

SC/BCT-0 <CONF MDD:MDD=1,OST=MBL;

Switch on power to the MDD-1 Take 30 secs. for disk booting into consideration

<CONF MDD:MDD=1, OST=ACT;

Wait for message:"SYCHRONIZING FROM MDD-0 TO MDD-1: FINISHED"

“ALL DOUBLE FILES SYNCHRONIZED.”

SC/BCT-0 <DISP MDDAUDIT;<MOD MDDAUDIT:LOCKSTAT=UNLOCKED; If MDD audit is locked

4.9 Activation of access control and file security (only for SSNC)

Activate the access control and file security again.

SC DISP ACCFG;MOD ACCFG: DEFAULT ACCESS=<DENY for all entries>;

SC DISP AUTHDEF;MOD AUTHDEF: DEFAULT AUTHENTICATION=DENY;

SC DISP FSCFG;MOD FSCFG: DEFAULT ACCESS=<DENY for all entries>;

4.10 Final tasks

Activation of CSC and X25 links:

SC/BCT-0 <CONF CSC:CSC=<csc-no>,OST=MBL;<CONF CSC:CSC=<csc-no>,OST=ACT

<CONF X25LINK:X25LINK=<link-no>,OST=MBL;<CONF X25LINK:X25LINK=<link-no>,OST=ACT

Ativation of the routine tests:

SC/BCT-0 <DISP SSPRT;<ALLOW SSPRT; If routine tests are globally allowed

SC STAT INPLOG

! "ADMINISTRATIVE STATE":LOCKED"OPERATIONAL STATE": ENABLED

SC SET INPLOG: LOG FILE NAME" = LOG<n+1>;

! This command generates a Master-, MML-, Q3-Binary- and Text-File

SC STAT INPLOG

! "ADMINISTRATIVE STATE":UNLOCKED"OPERATIONAL STATE": ENABLED

END OF FALLBACK

5 ABBREVIATIONS

AC Authentification Center

APS Application program system

CP Coordination processor

EXCHID Exchange identifier

HLR Home Location Register

MML Man-Machine Language

NSS Non-switching system

OMC Operation and Maintenance Center

VLR Visitor Location Register

VSN-NO Magnetic optical disk name (volume serial number)

SS Switching system

6 REFERENCES

/1/ Maintenance ManualMMN:SW 216

/2/ Modification in billing, Feature or Project database in a SSNC live Switch(MSC/VLR/HLR) - P30305-X1118-U234-01-7618

8. Change Requests From Name :

Project :

Date :

Code number:

Title:

Author:

No. Page Line Suggested change(s)