SNT FAULT:-.

1.) Check the status of SNT: NTSTP:SNT=Snt_name; 2. If state=bloc(ABL), then run test:NTBLI:SNT= ; NTTEI:SNT= ; Case I: No fault found(test sussessful), then deblock it NTBLI:SNT= ;

Case II: If Fault= card faulty, then Jacked-in & Jacked-out the concerned ETC card. Problem still persists, then replace faulty card.

Case III: SNT goes down again & again Jacked-in & Jacked-out the concerned ETC card. Problem still persists, suspected E1 cable faulty. a. Check SNT (E1) cable. Remove cable & then run SNT test. If no fault occurs, it means cable is faulty. b. Connect E1 again. Give loop on E1 for 2-3 hrs at switch end. If SNT fault does nor occurs, remove the loop. If fault occurs now , it means E1 is faulty. c. Give loop from Transport DDF & do the same analysis. Case IV: If fault occurs again even after replacing the card, then a. Check SNT (E1) cable. Remove cable & then run SNT test. If fault no fault occurs, it means cable is faulty.Replace it.

b. Give loop on E1 for 2-3 hrs at switch end. If SNT fault does nor occurs, remove the loop. If fault occurs now , it means E1 is faulty. c. Give loop from Transport DDF & do the same analysis.

3. If blocking of SNT results in "DEVICE USED AS SEMIPERMANENT CONNECTION",which means signalling is defined on this E1 then I. Firstly delete the semipermanent connection. II. Run the SNT test & follow above cases(I, II, III, IV) III. Define the semipermanent connection again after fault gets resolved.

4. If corresponding E1 is not commercially open & transport parameters from our ILT to their Tansport equipment has not been defined yet.Then block SNT & E1. It will be will be deblocked after the E1 gets through.

2.) Volume limit Exdeed:INMCT:SPG=0/1; INVOP; To check volumes defined in switch. INVOP:VOL=CALLVOLUME; To check used size & max limit defined. end;

cholp:fn=tt; cholc:fn=tt,limit=BANS;

3.) URC Clock Fault:CACLP; CAUCP:URC=1; To get IP of clock ***To get rp of snt: EXDCP:SNT= ,subsnt= ; ERRPP:RP= ; ///to get twin RP expop:snt= , subsnt= ; expop:rp= ,em=;

expop:rp= ;

4.) System Restart:System Restart:1. To give restart: Syrei:rank= , expl= ; RANK=small/large/reload EXPL=expl Reason for the restart Expressed as reason-optreason, or reason, where reason Compulsory part CHARG Charging failure HALA HCELL HCOM HDEV Hanging alarm Hanging cell Hanging command Hanging device

HDUMP Hanging dump System Backup Copy) HFUNC Hanging function HSUB Hanging subscriber Other reason

OTHER

PLAN Planned action optreason Optional part String 1-25 characters

2. To check pending restart:

syrtp; e.g <SYRTP;

TIME FOR PENDING RESTART TIME 0300 END Here, TIME shows at the timings at which system will take restart. Now check the reason for this alarm: Syrip survey; TYPE OF RESTART SMALL

SP Node restarted:INMCT:SPG=0/1; IMCSP; end; To clear the alarm from switch:ImMCT:SPG=0/1; IMRDP:NODE=A/B; END;

CASE:- If getting diagnostic error,then SP TRANSIENT FAULT SUPERVISION SPG NODE 1 A FAULT TYPE INTERNAL DIAGNOSTIC ERROR SUSPECTED BOARD(S) CABINET MAG PCB UNIT SPG-1-A SPVM-PODD1 OD FAULT WEIGHT 50

SPG-1-A SPVM-PVSA

50

Perform Diagnosis test: RESUP:SPG= ,node= ; BLSNI:SPG= ,node= ; RESUI:SPG= ,node= ; BLSNE:SPG= ,node= ; EXSLP:SPG=0; (To check SP links status)

SNT Types:SNT 1. 2. 3. 4. 5. 6. Device Type Supports

ETM1UPDDIFOptical(LOT) ET11BT11R2 E1(ETC) UPETN3UPDN3C7 E1(ETC) ETV5GLITSV5 ETPRAGSLIPRAGSPRI LIBAV5GISDN-BRI ECDHEcho Canceller in Pool

7. ECP-

Software Error:On receiving Software Error: 1. To check errors on event : Syrip:survey; 2. For FORLOPP type event: Syrae:rectype=softerr; 3. For APPLERR type event: Syrae:rectype=applerr;

4. To get the block name: LASLP:BN= INF1; If INF1= H'E705, then BN=H05E7 (2) Always check SYELP , when you find frequent error or high Error count , If current Error Intensity is not = "0" then report it to TAC ASAP. (3) Also check that is it related to SAE alarms , some times in high traffic , due to Memory problem , system is generating Error. So ALLIP:ALCAT=APZ and DBTSP for SAACTIONS , will give better idea on Errors. (4) In case of multiple Transport failure , system is generating Errors in Access related block , like V5CCH , DLV5 , or some times in UPPHOT also. So judge , Software Errors w.r.t. ALLIP other faults. (5) Always give SYRAE:RECTYPE=SOFTERR , SYRAE:RECTYPE=APPLERR , after you have observed the alarm , it will enable the system to issue a fresh alarm wsyith new time stamp for any new Error . At present we can see that , Software Error alarm is pending for 2-3 days , so you will never come to know fresh errors until you check SYRIP , which is not reported to AMS , So always try to remove the alarm . (6) Try to correlated Erros with traffic type / behavior and with BHCA (PLLDP). (7) You can check SYRIP:LOG , for past errors and compare the present ones.

Size Alteration Alarm:DBTSP:TAB=SAACTIONS; SAAEP:SAE=ALL,BLOCK=; !To check the utilization of NI ! sybue; saali;

saaii:sae=, block=, ni= newni;

Semipermanent Connection Fault:To delete-create semipermanent connection:NTCOP:SNT= STDEP:DEV= EXSCP:DEV= (device with state SEBU) To get details of Semi permanent connection EXSCE:NAME= ,DEV=C7ST24- ; To delete connection

To create it:EXSPI:NAME= EXSSI:DEV1= c7st ; EXSSI:DEV2= updn ; EXSPE; To activate again: EXSCI:NAME= ,DEV=C7ST24- ;

--------------------------------------------------------------------------------------------------<C7LTP:LS=2-2442; CCITT7 LINK SET STATE LS 2-2442 SPID SLC STATE INHIBST FCODE INFO JAMNLD 00 ACTIVE 01 ACTIVE

END <C7LDP:LS=2-2442; CCITT7 LINK SET DATA LS SPID ASP SPID

2-2442

JAMNLD SDL SLI BJAM7P-0/UPDN3-8816 BJAM7P-1/UPDN3-8848

SLC ACL PARMG ST 0 A1 0 C7ST24-148 1 A1 0 C7ST24-172 END <EXSCP:DEV=C7ST24-148;

SEMIPERMANENT CONNECTION DATA NAME BJAM7P-0 CSTATE DISTC MISC ACT 49 1 NUMCH

SIDE1 SSTATE DEV=UPDN3-8816 ACT SIDE2 SSTATE DEV=C7ST24-148 ACT END <EXSCP:DEV=UPDN3-8816;

SEMIPERMANENT CONNECTION DATA NAME BJAM7P-0 CSTATE DISTC MISC ACT 49 1 NUMCH

SIDE1 SSTATE DEV=UPDN3-8816 ACT SIDE2 SSTATE DEV=C7ST24-148 ACT END <EXSCP:DEV=C7ST24-172;

SEMIPERMANENT CONNECTION DATA

NAME BJAM7P-1

CSTATE DISTC MISC ACT 5 1

NUMCH

SIDE1 SSTATE DEV=UPDN3-8848 ACT SIDE2 SSTATE DEV=C7ST24-172 ACT END <EXSCP:DEV=UPDN3-8848;

SEMIPERMANENT CONNECTION DATA NAME BJAM7P-1 CSTATE DISTC MISC ACT 5 1 NUMCH

SIDE1 SSTATE DEV=UPDN3-8848 ACT SIDE2 SSTATE DEV=C7ST24-172 ACT END

RP Fault:exrpp:rp=532; exemp:rp=532,em=all; repri:rp=532; remri:rp=532,pcb="rp2g"; recri:rp=532;

Request Call Procedure:Command to arrange a call via request ILT & to give any desire CLI to B No. Suppose ILT is Ambala & CLI requested is 1713031171.

TCTDI:BO=120,BNB=09835091838,ANB=1713031171,DEV=UPDN32148; CON; END; EXTPI:BNB=02230372400; EXTPE:BNB=02230372400; CTRAIlDEV=UPDN3-2149;

Procedure load supervision:ProbableCause: Performance Degraded Classification.....:Printout: *** ALARM 298 A1/APT "RI1MBMUMB"A 070101 1756 EXCHANGE INPUT LOAD SUPERVISION TDMI REJDO REJDI OFFDO OFFDI REJMH REJML 1 0 15 244 23152 OFFMPL TASK OFFTCAP REJTCAP NOMISC 0 0 END

OFFMPH

PLLDP; to check processor load. SYELP; to check error intensity. IOSTP; IO subsystems status print. IOTRE:IO= ; to end transfer to/from selected IO device. CHOLP:FN=TT; CHARGING OUTPUT LIMIT, PRINT CHOLC:FN=TT,LIMIT=all/ bans; CHARGING OUTPUT LIMIT CHANGE AFTSP:SAE=ALL,TEST=110; EXSLP:SPG=ALL;

Procedure to Handle Group Switch Fault:Procedure to handle Group Switch Fault Refer FT No :- 946902 , Mumbai ILT-2 GSSTP:TSM=TSM-B-132; GSSTP:TSM=TSM-B-133; GSBLI:TSM=TSM-B-132;

GSBLI:TSM=TSM-B-133; GSTEI:TSM=TSM-B-132; GSTEI:TSM=TSM-B-133; If the fault is not clearing after initiating the repair check function then you need to ask the Field Enginner to provide reset to the affected TS4B hardware. Each TS4B card contains 4 TSMs, hence we need to block the the EM/s corresponding to the entire card. To identify the EM/RP corresponding to this TSM, we need to take the entire printout i.e. EXEMP:RP=ALL,EM=ALL; After locating the EM/RP, we need to block the concerned EM/s through BLEMI:EM=9,RP=65,RPT=65; (In this case) BLEMI:EM=11,RP=65,RPT=65; (In this case) BLEMI:EM=13,RP=65,RPT=65; (In this case) BLEMI:EM=15,RP=65,RPT=65; (In this case) After blocking the EM/RP configuration, we need to intimate the field Engineer about the location of the board through EXPOP: TSM=TSM-B-132; (In this case) EXPOP: TSM=TSM-B-133; (In this case) Put the LED ON by TEBIC:RP=65,LED=ON; Initate SARPI:RP=65; For precautionary measure so that system takes a note of the hardware changes. Ask the field Enginner to reset the hardware. After completion of the activity by the field Engineer, deblock the hardware in the reverse fashion & check whether the fault is rectified. If not then follow the entire process & ask the Engineer to replace the hardware.

Commands to capture call charging:-

The following commands are used for capturing the Charging file related data from different ILTs. To check any existing old file in the system inmct:spg=0; infip:file=ttfile00; end; To see status of file reported to FPU infsp:file=ttfile00,dest=XXX; Dest u will get from infup:file=ttfile00; To see latest active CDR file ioifp:file=ttfile00;

Alarm Clearance:For A1 alarms : 1.V5-GS DATA LINK FAILURE --------- Please correct the definition at DLC end. 2. INFINITE SEQUENTIAL FILE NOT OPEN ---------- TTFILE02 define for emergency use so no action require. For A2 alarms: 1. Most of the alarms are related to PRI . ( Layer2 fault & DIP fault ). --------- Please check if PRI is not in use than block the DIP & Devices to clear the alarm . 2. GENERIC ACCESS MANAGER SIGNALLING CHANNEL CONNECTION FAULT ----------------- To clear the alarm spare SNT needs to be define for that follow-up with NHQ O&M to raise proper SO. 3.DIGITAL PATH QUALITY SUPERVISION ----------- no action required as quality supervision alarm automatically reset at 00:00 hrs daily. For A3 alarm : 1. DIGITAL PATH UNAVAILABLE STATE FAULT ----------- You can clear this alarm by blocking of DIP if DIP is not in use. URC Clock fault:CACLP; CAUCP:URC=1; To get IP of clock Volume limit Exceeded.:-

INMCT:SPG=0/1; INVOP; To check volumes defined in switch. INVOP:VOL=CALLVOLUME; To check used size & max limit defined. end;

cholp:fn=tt; cholc:fn=tt,limit=BANS; System Restarted:-System Restart:1. To give restart: Syrei:rank= , expl= ; RANK=small/large/reload EXPL=expl Reason for the restart Expressed as reason-optreason, or reason, where reason Compulsory part CHARG Charging failure HALA HCELL HCOM HDEV Hanging alarm Hanging cell Hanging command Hanging device

HDUMP Hanging dump System Backup Copy) HFUNC Hanging function HSUB Hanging subscriber

OTHER

Other reason

PLAN Planned action optreason Optional part String 1-25 characters

2. To check pending restart: syrtp; e.g <SYRTP;

TIME FOR PENDING RESTART TIME 0300 END Here, TIME shows at the timings at which system will take restart. Now check the reason for this alarm: Syrip survey; TYPE OF RESTART SMALL