All rights reserved.

Passing on and copying of this document, use and communication of its contents not permitted without authorization from Alcatel.

Establishment

ALCATEL – LUCENT INDIA LTD. Preventive and corrective guide lines on change of year from 2012 to 2013 ( E10 )

GURGAON

Area Department or service Type

: : :

OCB 283 and 1000 E10 MM OPERATION DIRECTION TECHNICAL NOTE

APPLICATION

R25 and R27

IMPLEMENTATION BY

SITE

01 ED

52 WEEK

Ramesh Parthasarathy APPROVAL

Anil Kumar Saxena ORIGINATOR

History : Ed 01 : Document Creation 20/12/12

Preventive and corrective guide lines on change of year from 2012 to 2013
1

25 link). Check for Critical \Major Alarms in ALAIL . GLR faults especially on SMA1 & SMA2 (where applicable according to configuration) etc. Check that TYJ is appearing as 01 for 01/01/13 to 05/01/13 and 02 for 06/01/13 (Sunday). Latest System Backup should be readily available. 2. like: Ring OOS. 1. use and communication of its contents not permitted without authorization from Alcatel. needed in case of any outage. INTRODUCTION The purpose of this technical note is to check smooth change of year and to control the exchange in the event of high traffic. Also Keep one hard disk Backup ready.TYJ=2: DAT=13-08-15. Station OOS. Secondary memory Degraded.All rights reserved. 4. CDR backup should be taken regularly so as to avoid of any loss because of Exchange Failure (Keep a watch on the X. @ FJFAD: DAT=13-01-26.TYJ=2: Corrective action in case of over loads on New Year day 1. it should not be zero. Passing on and copying of this document. Preventive and corrective guide lines on change of year from 2012 to 2013 2 . @CLXIN: DAT=12-12-31<13-01-06. PROCEDURE 1) Please execute following command on 28th or 29/12/12. 3. 2. 2) Execute following during first week of January.

If there seems to be more load over overloaded PUPE. signaling can be recreated on another PUPE also by changing the TSV.All rights reserved. Call Filtering based on no. Procedure to use ESALA is : Preventive and corrective guide lines on change of year from 2012 to 2013 3 . redistribution of CICs can be done via FLUMO command. 7. These will be effective if implemented in nearby exchanges also to avoid sending of high traffic to your exchange. Block the ckts to the NFSC . use and communication of its contents not permitted without authorization from Alcatel. Call gapping procedures are very useful to control traffic when the overloaded condition is created due to voice traffic after the translational analysis in current Exchange. The distribution can be checked via FLUIL command. This can be implemented using ESALA command. PROCESSING TGPFIL ACC ACH=0201 FIL=FT FILM=15 PROCESSING TGPFIL EXC Call Filtering based on the period using ESALA:This allows to limit the calls to a destination within the specified time period defined in the parameter PER.FIL=FT. there fore the traffic can be distributed equally among all the PUPEs . Check the OCHLA report & find out which NFSC is giving unexpected high traffic. of calls using FILMO:- This will filter "n" calls out of every 8 calls where "n" can range from 1 to 7. Passing on and copying of this document.CEN=1: CEN=1/95-05-22/11 H 22 MN 32/FILTERING CONDITIONS DE FILTRAGE @ACH=201.FILM=15. The NFSC which is creating the problem would be attached to a PUPE going to Overload. 5. but it is always better to break some of the PCMs of the NFSC until it soothes the loaded condition. In case signaling load is suspected to be higher. 6. This can be implemented using FILMO command @FILMO.

NDST=651164<destination name>.FILM=<>.1) Check the ARCIN @ ARCIN: @ ARCH=XATR. make the necessary change by ARCMO. 3) Relate the destination to the MIL. immediately call Alcatel-Lucent TASC team for support . check in TR1 and TR2 also. 5) Applying flter on the entire MIL @ ESALA: @ NDST=651164 <Destination Name>. All rights reserved. PER=(Filtering time in multiple of 100 milli seconds eg:Per=30 means 30 x 100 msec) . NOMS=XR0529. So. Verify that the parameter TRAZ = 1 . 4) Applying filter on a particular ND of the MIL. @ INDMO: @ IND=6511 <MIL>. CONCLUSION The above procedure should help normalizing the load . If you implement it at your exchange.PER= <>. FICH=FIPAM. use and communication of its contents not permitted without authorization from Alcatel. 2) Create Destination @ DSTCR: @ NDST=651164 <destination name>. @ ESALA: @ NDE=6511649 <ND to be filtered>. 3. it must be very clear that these are effective even if nearby exchanges also use similar techniques to avoid sending high traffic to your exchange. If it is not 1 .1 sec >. but in case the condition is not normal. it will avoid sending of high traffic to nearby exchanges. NUM=9.PER=200 <multiple of 0. Passing on and copying of this document. FILM= <film number for feeding Announcement>. --------------------End of document-------------------- Preventive and corrective guide lines on change of year from 2012 to 2013 4 . FORM=EDN.

Sign up to vote on this title
UsefulNot useful