Procedure for Lifeline Test in ILT Switch

1 0

24-Mar-2003 06-Mar-2003

M/s.Ericsson Rajesh Jadhav M/s.Ericsson Rajesh Jadhav

Ramrao Nazare Ronak Kaji Ramrao Nazare Ronak Kaji

C Nithiyanantham C Nithiyanantham

Ve r



Made by

Checked by

Approved by

Sr. No. 1.0 Description Page No.




3.0 3.1 3.2

Prerequisites Site Requirement Time schedule for Testing




Steps to be followed in case of problem in Separated CP side.

The Lifeline Procedure is used to assure the integrity of system backups and to test the ability of the switch to reload and recover after an outage. A lifeline should be performed before any major change to the system e.g. Correction implementation, Functional changes, CNA/AS implementation etc. Even if no changes have been done in terms of hardware or software, a lifeline test has to be performed atleast once in six months or after every upgrade.


The lifeline procedure is defined as the test loading of a manual dump to the standby side of the CP and testing it for recovery after small and large restarts. Even though some of the traffic related faults may not be detected by this, the lifeline dump is not switched to Executive side of the CP since this will cause disturbance due to the large restart. The lifeline procedure assures that a fault free system backup dump is available for use in the event of a system stoppage.

3. 0

The exchange should be in parallel operation with A-EX and B-SB WO and free of any major faults. The following printouts are taken to assure the stability of the switch before commencing the procedure.  OPEN a LOG file ”LIFELINE_xxx_ddmm.log”  Alarm List ALLIP;  CP Status DPWSP;  SP Node Status IMMCT:SPG=0; IMCSP; END; EXSLP:SPG=0;  CP Errors and CP Events DIECP; DIRCP; No recent CP errors interrupt for APZ Recorded CP events Check both CP are working . Check there is no major alarms. where xxx= MCN name .

/var/www/apps/conversion/current/tmp/scratch10840/101418793.doc :3


 Group switch state GSSTP;  End Test System END TEST; (End Test System from all Terminals)

In case any problem is encountered during the procedure e.g. Error interrupts, the problems has to be escalated, analysed and the procedure started from the beginning. A log file has to be kept open on all used terminals during the whole procedure.

     

Two AT (Alphanumeric Terminals) other than AT-0 One Blank OD One PSTN / RIM Telephone with NSD facility CPT Cable Life Line Test Procedure document One dedicated Switch Engineer who has reasonable command over AXE.


21.00 Hrs 23.00 Hrs. 00.00 Hrs. 01.00 Hrs. : Start CP Backup by Switch Engineer / NOC : Copy CP Backup to OD (Reference is taken from Mumbai ILT. CP Backup takes about 2 hrs.) : Copy CP Backup from OD to HD of AXE. : CP Separate and loading start.


TEST PROCEDURE  Deactivate Automatic dump function. SYBUE;  Commence manual backup to RELFSW X. SYBUP:FILE=RELFSWX;  Wait for result printout. BACKUP INFORMATION OUTPUT EXECUTED  Mount the Blank optical disk (X-highest defined no.)

/var/www/apps/conversion/current/tmp/scratch10840/101418793.doc :4


 Format the OD :inmct:spg=0; :INMEI:NODE=A or B,IO=od-1,FORMAT=nsr02,vol=TESTbkupDDMM. :end; INMCT: SPG=0; INVOL: NODE=AorB, IO=OD-1; END;  Wait for VOLUME LOADED printout. INMCT: SPG=0; Infip:file=od0a1; End;  Wait for VOLUME LOADED printout.  Copy the backup from HD to OD. SYMTP: FILE1=RELFSW2, DIR=OUT, SPG=0, NODE=AorB, IO2=OD-1;  Wait for result printout. BACKUP INFORMATION FILE CONVERSION SINGLE MEDIA END  Copy the backup from OD to HD. SYMTP: FILE1=RELFSW2, DIR=IN, SPG=0, NODE=AorB, IO2=OD-1;  Wait for result printout. BACKUP INFORMATION FILE CONVERSION SINGLE MEDIA END  Check for successful transfer.  Unload the Optical disk. INMCT: SPG=0; INVOE: NODE=AorB, IO=OD-1; END;  Wait for VOLUME UNLOADED printout.  Check the CP state.

/var/www/apps/conversion/current/tmp/scratch10840/101418793.doc :5


The expected state is CP-A EX and CP-B SB WO. DPWSP;  Check status of SP link. EXSLP: SPG=0;  Separate a link. FCSLI: SPG=0;  Separate a terminal to be used on the SB side. MCLOC: USR=SYSTEM, PSW= INIT; MCDSC: IO=AT- x, SEP=YES; (select the fault free AT where alarms are not routed) EXIT;  Separate the SB side. DPSES; ( AT-EX )

 Check CP state. DPWSP; ( AT-EX )

 Initiate loading using functional change method. FCCPL: FILE= RELFSW2; ( AT-EX )  Wait for result printout.  Watch at counter Display on APZ panel
340 341 342 343 344 345 Loading of subfile R0 Loading of subfile R1 Loading of subfile R2 Loading of subfile R3 Loading of subfile R4 Loading of subfile R5, PS part Loading of subfile R5, RS part Finished, halted after initial loading Finished

( Waiting time based on size of exchange ).

380 390

/var/www/apps/conversion/current/tmp/scratch10840/101418793.doc :6


 CP-SB LOADING FOR FUNCTION CHANGE Wait for SYSTEM START printout. Restart data will come to AT-SB .  Set the System Clock. ( AT-SB )

( AT-EX )

( AT-SB )

CACLS: DATE=yymmdd, DAY=day, TIME=time;

( AT-SB )

 Wait until all alarm printouts are finished, before entering the next command.  Turn ON the Error Interrupt printout. DIEFC: FORM=1; ( AT-SB )

 Start the Application blocks. SYATI; ( AT-SB )

 Wait for APPLICATION BLOCKS STARTED printout.  Check block has become active. LASLP:BLOCK=BT11;  Perform some print commands. ALLIP; PLLDP; ( AT-SB ) ( AT-SB )

 Check CALIM = 9000 for all 12 intervals.  On SB side test Large restart. SYREI: RANK=LARGE; ( 5 Mins.)

 Wait for system to recover. Watch for cyclic restarts. After Restart data connect the AT-SB to seperated CP and wait and check connectivity After 2-3 minutes , If cyclic restart is occurring then it will give ”CP not obtainable”.  On SB side test Small restart. SYREI: RANK= SMALL; ( 5 Mins.)

/var/www/apps/conversion/current/tmp/scratch10840/101418793.doc :7


 Ensure that the restart was definitely Small.  Wait for system to recover. Watch for cyclic restarts.  Check the Store utilisation. SASTP;  Wait for STORE UTILISATION printout. For each row (PS, RS, DS) check that the sum of the first three values (NRWA, NRWF and NRWT) is equal to the last column.  Return CP to parallel operation. RECCI; ( Execute the command at AT-EX )

 Confirm that system is back in normal working state. CP-A EX, CP-B SB WO. DPWSP;  Un-separate the IO used on SB side. IMLCT: SPG=0; MCDSC: IO= AT-x, SEP=NO; END;  Un-separate the CP-SP link. BLSLE: SPG=0, LINK= link; EXSLP: SPG=0;  Rotate the reload files. SYTUC;  Activate the automatic dump function. SYBUI: DISC;  Close the log files. !!! Label the Optical disk with “Passed Reload Test” and store it safely OFFSITE, for use in emergency situations !!!

/var/www/apps/conversion/current/tmp/scratch10840/101418793.doc :8



In normal condition after SYATI , Large Restart and Small Restart, IO contact with Separated CP will remain and Counter value on CP display will not have any Phase number. Case 1:- FCCPL is not taking place : Deblock the SPG link by BLSLE:spg=0,link=1; Again separate the link by FCSLI:SPG=0; Check EXSLP:spg=0; Try FCCPL again. If not successful contact next level. Case 2:- Cyclic Restart. IF IO contact is lost and Counter value is going to phase 44 >> 343….. again to 44 then call TAC immediately . Also check from AT-EX that one CP is working O.K. Ericsson can be contacted in such case to take out more data from SE-FM side. To come out from the situation:From AT-EX give DPHAS and then check from AT-SB through CPT mode the following : MCLOC:USR=SYSTEM, PSW=INIT; PTCOI; PTWSP; Check CP – B is in HA mode. PTCOE; EXIT; Give DPPAI; from AT-EX . Clean up the all related alarms.


Life Line Test Result: Test Conducted on :

/var/www/apps/conversion/current/tmp/scratch10840/101418793.doc :9


Test Result Reason for failure Remedial action

: : :


/var/www/apps/conversion/current/tmp/scratch10840/101418793.doc :10


Sign up to vote on this title
UsefulNot useful