ALARMES (alterado a 25-07-00)

MGEPP:ID=ALL; Verifies if the AUC is connected

*******************************************************************************************************ALARM INTERFACE FAULTALI FAULT (APZ)

A card in the alarm interface unit is not Ok .In the alarm printout , the PCB is the suspected card .

ALLIP ;ALALP; Check Heck Alarm Interface ConnectionALBLI:ALI = 0; Block the faulty ALI ALBLE:ALI = 0; Deblock the faulty ALI, wait a minuteALLIP ;ALALP; Check Heck Alarm Interface Connection. If STATE =WO end of intervention, Else Step 2

1. Check IO from the printout “ALALP”.IOIOP:IO1=AT-x;If AT is blocked, manually block it and deblock.

IOBLI:IO=AT-x;IOBLE:IO=AT-x;ALALP; If STATE =WO end of intervention. Else Step 3

2. Find the port associated to the AT IMLCT:SPG=0; :MCDVP; :ILNPP:NP=w-x-y-z; If not working “WO” block and deblock the port :ILBLI:NP=w-x-y-z; Block the port :ILBLE:NP=w-x-y-z; Deblock the port :ILNPP:NP=w-x-y-z; :END;

ALBLE:ALI=0;ALALP; Check Heck Alarm Interface Connection

NOTA: If still not working call prevention.

*******************************************************************************************************ANALYSIS DATA FAULT (MSC)

NOTA: A fault was found in the "ROUTING" analyse, "END-OF-SELECTION", ETC.- According to the error code see OPI

ANFAR; Reset the alarm. (só volta a surgir quando ocorrer novamente a mesma falha)

*******************************************************************************************************APPLICATION DETECTED SOFTWARE ERROR (MSC)

SYRIP:SURVEY;SYRAE:RECTYPE=APPLERR; Passivate the stored recovery SW information for all event specified by Type. Cancells the alarm.ALLIP;

******************************************************************************************************...

1

.

AUDIT FUNCTION THRESHOLD SUPERVISION (APZ)

The system supervise the free memory on the main store and the size of data in blocks. This alarm occurs when the real size is over the defined threshold. Example: For the DS memory the threshold is 90%. At 91% the alarm appears.

1) Find the test faulty given in the message AUDIT FUNCTION THRESHOLD SUPERVISION (Number of TEST)

2) Control the real size (field UTIL in the message “MEMORY UTILISATION ALARM LOG” or “FILE UTILISATION ALARM LOG”)

The threshold is defined with LIM1 and LIM2

AFTSP:TEST = …110… , LOG ;

3) Realise a test to control the actual size.AFTSI:TEST = 1xx ; For test 101, 102 and 104 Compares allocated memory area to set thresholdsAFTSI:TEST=110,SAE =…SAE/ALL… , [ BLOCK = Block name ]; Compares SAE utilization to thresholdsFor test 110 ( See SAE and BLOCK with AFTSP) (Warning: Can cause a restart)

If the alarm do not disappear after AFTSI and in case of an A” (major) alarm, it’s not a temporary failure so call the prevention.

Other commands:SASTP; Memory utilisation printSAAEP:SAE=sae; Size alteration print, See alarm “SOFTWARE FILE CONGESTION”SAAEP:SAE=sae,BLOCK=block; If sae 500

******************************************************************************************************BACKUP INFORMATION FAULT

The backup contains all the data to restart the system. Automatically the system copy the main store in files (IOG). The receipt of this alarm indicates a fault and the fault code gives some information about the problem (See documentation)

FC 13 - Make manual dump FC 34 –Manual Dump activated (or automatic dump deactivated). Make sure that no special operations are running on

site (by phone or by some comment in the Alarm list of TMOS). Probably there was a size alteration in the system and a manual backup must be done.

SYBTP; Print out the times at wich automatic output of small and large data dump is to be initiated. SYBFP:FILE; Check the existing backup files.

SYBUE; Deactivate the automatical dump. If it was already deactivated, “Fault Code 23” is givenSYBFP:FILE; SYBUP:FILE=..última file + antiga..; Initiate manual backup –to the oldest fileSYBFP:FILE; To check if the the oldest file is updated.

SYTUC; Rotates the Backup to the newest file. 2 times rotation gives “Fault Code 25”.

SYBUI:DISC; Activates the automatic output for small and large data dumps.

If after these actions the alarm “BACKUP INFORMATION FAULT” remains in the alarm list with “FAULT CODE 13” it means that the system needs to make a “check summing” towards the new Backup Data, now in RELFSW0:

SYBCI:FILE= relfsw0 (Rotated file ); Test to RELFSW0 (already rotated file) Wait for the printout “Backup information Check Executed

******************************************************************************************************....

2

.BLOCKING SUPERVISION (APT)

Each route can be supervised by the function “blocking supervision”. When this alarm appears the number of devices blocked is over the threshold defined. Verify if the SEIZURE QUALITY SUPERVISION, alarm is given. When this alarm is active it is not possible to block the devices, in this case do SEQAR:R=…;

ALLIP ; To find the name of the route blocked

STRSP:R=...Route Name…; To Check the number of devices NBLO = Nb dev blocked NDEV = Nb devices on the routeNIDL = Nb devices free NOCC = Nb calls in progress

EXDRP:DEV=...; Print the physical position, RP=X & ETC=EM

STRDP:R=...,STATE=BLOC&LIBL&SEAL; Print the state of the devices for those in SEAL ( do BLODI – BLODE)

STATE= BLOC BLS= ABL FTYPE=S SEQAR:R=name;BLS= MBL don’t deblock these devicesBLS= CBL the EM is blocked see alarm EM FAULT

STATE =SEAL Go to step 1STATE =LIBL The problem is from the far switch side. Contact the local team or if it is a route within

MSC, BSC, VMS… network check the other side. Go to step 3

1) Check the state of the SNT. To know the SNT use command EXDEPEXDEP : DEV = device code ; Give us the SNT. Use a device blocked faulty . Note the SNT used in the messageNTSTP : SNT = snt’s code ; If state is WO go to step 2.

If not, check the alarm SWITCHING NETWORK TERMINAL FAULT.

2) Check the state of the DIP. The DIP is given in the command NTCOPNTCOP : SNT = snt’s code ; Use the SNT given in the command EXDEP. Note the DIP used in the messageDTSTP : DIP = dip’s code ; if the DIP is ABL it’s why the devices are blocked. Check the Alarm “Digital Path

Fault”. If it is WO go to step 3.

3) Try to block the devices, take them out of service, put in service again, and deblock them.BLODI:DEV= device code ; Bloquear devices You can use a group of devices up to 32 in each command.EXDAE:DEV= device code ; Take the devices out of service. Put the DEV MBL in . PRE-POST SERVICE (channel 0 of each PCM link and SEBU devices cannot be used in these commands)EXDAI:DEV= device code ; Puts the DEVs into serviceBLODE:DEV= device code ; Deblock the devicesSTDEP:DEV= device code ; Confirm the state of the devices

BLORP; Print out the blocked routes

BLURP:R=...; Printout of supervision data for routes

If they are still blocked, verify if the route is in congestion or near it, by comparing the number of idle (NIDL) and occupied (NOCC) devices.STRSP : R = ROUTE ’s name;

NOTA: If congested, call prevention. If not, take a note and call prevention during normal working hours.

*******************************************************************************************************CALLVOLUME

When the alarm “High CallVolume” appears, it is necessary to disconnect the facility “AOC Event Modules” (foi activado no MSC de Alf., o primeiro ficheiro de taxação com esta facilidade activa o Ttfile0264), com o comamdo acima mensionado e avisar a prevenção.

CHEXC:PROP=ECC-65535;

*******************************************************************************************************....

3

CCITT7 DESTINATION INACCESSIBLE (APT)

An entity in the network , not obligatory linked physically to the system, cannot be reached for signalling dialogue.

ALLIP ; If other alarms about RP , EM , SNT, DIP see respective alarms, elseC7RSP:DEST = x-abcd; x-abcd is the destination’s codeC7RAE:DEST = x-abcd; Manual deactivation C7RAI:DEST = x-abcd; Manual activation C7RSP:DEST = x-abcd;

Check also if there is in other network entity some related alarm and take action on that. Further actions according to alarm “CCITT7 SIGNALLING LINK FAILURE”

Otros Comandos:C7LTP:LS = x-abcd; To get the state of the link sets C7LDP:LS = x-abcd; To get the link set devices names STDEP:DEV =dev; The link set device’s name and numberEXSCP:DEV =dev; The data for semipermanent connection if available.C7SPP:SP =x-abcd;C7NCP:SP= x-abcd,SSN=ALL;

*******************************************************************************************************CCITT7 SIGNALLING LINK FAILURE (APT)

A signalling link ( device with semipermanent connection ) is not ok . So it is not able to manage signalling messages .

Watch the link set’s state , the two parts of the semipermanent connection , deactivate then activate the signalling link .

C7LTP : LS =…x-abcd /ALL…; To get the state of all the link set’s signalling links. (Active/restoring=OK)

C7LDP : LS = x-abcd ; To get the name of the semipermanent connected device .EXSCP : DEV = semipermanent connected device ; CSTATE and both SSTATE must be ACT ( active ) .

C7LAE:LS=…x-abcd…,SLC=..y/0..; Deactivate the link. C7LTP : LS = x-abcd ; Watch the linkC7LAI : LS = x-abcd , SLC = y/0; Activate the link. – Makes a reset of the alarm, if not OK it appears again.C7LTP : LS = x-abcd ; Watch the link

If after few seconds , the STATE is ACTIVE , it’s ok .Else here are the CHOICES :

There are other alarms on the MSC about this link (DIP , EM , SNT) : Solve them No other alarms and the number of signalling links “active” is > or = to the number of not actives ( “restoring” , “deactive” , “inhibited” ) ones : report to local team at normal working hours No other alarms and the number of signalling links “active” is not > or = to the number of not actives ( “restoring” , “deactive” , “inhibited” ) ones : call prevention.

Otros Comandos: C7RSP : DEST = x-abcd (valor LS); Check if the route in question has a second line of redundancyC7SPP : SP = x-abcd ;C7NCP : SP = x-abcd , SSN = ALL ;DTSTP : DIP = DIP with semipermanent connected device; Check the state of the DIPDTDIP:DIP=...; SNT correspondiente - If DIP=XYUPT33 ==> SNT=UPT33-XYNTSTP : SNT = SNT with semipermanent connected device ; The state of the SNTEXSCP:NAME=..ALL..; See SEMIPERM data (Give us the DEV)EXDEP:DEV=UPD33-...; Find the respective SNT.NTCOP:SNT=...,DIPINF; Information on SNTP, SNTV, DIP y DEVSTDEP : DEV = semipermanent connected device ; Print the state of the devicesEXRPP : RP = controlling SNT or ETC RP number ;EXEMP : RP = controlling SNT or ETC RP number , EM = ALL ;

*******************************************************************************************************....

4

.CELL LOGICAL CHANNELS SEIZURE SUPERVISION (BSC)

RLVAP; Print out the TS´s that have not been used during long time in per cell basis.RLVLP; Print the values off seizure supervision, para TCH y SDCCHRLMSP; Checks if the TS is out of service.RLCRP:CELL=…; Shows the state of the TS´s in the cellRLVLP:CELL=…; Print the values off seizure supervision, para TCH y SDCCHRLVLC:CELL=…,CHTYPE=…; Change the supervision parametersRLVAR:CHTYPE=..TCH..; Reset the buffer that contains the alarm parameterRLVLI:CELL=…,CHTYPE=…; Activates a seizure supervision for these channelsRAPTI:DEV= ou LCH= ou CIC=…; Initiates a tracing of the connections that use this DEV

*******************************************************************************************************CELL LOGICAL CHANNELS AVAILABILITY SUPERVISION (A2 OU A1) (BSC)

- IF it is TF then the station must be down.

Nota: RXETS->RBS200 , RXOTS->RBS2000

RXTCP:MOTY=RXETG,CELL=...; Prints the TG number and the channel groups linkedt to it RXCDP:MO=RX[E/O]TG-...; Shows the MO configuration.

In the case TRX or RX, were blocked then all the associated TS´s are blocked as well,. The order of blocking the MOs is: TG, TF, TRX, RX, TX, TS.

RXMSP:MO=....; Print info on the state of the MO (se os TRX estiverem BLL, estão a carregar)

RXBLI:MO=....; Block the MO (Managed Object)RXLTI:MO=....; Inicia un Loop test to verify the connection between the BSC and the TS of the BTSRXTEI:MO=....; Test MO's RXBLE:MO=....; Deblock MOs

- When the blocked TS´s are unknown:

RLSLP:CELL=...; See if the cell is down or not and how many TCH´s are out of serviceRLCRP:CELL=...; Shows the traffic in the cell. Check the BPC numbers wich are BLOCKRXCDP:MO=RX[E/O]TS-...; Print the TS's and their matching BPCsRXBLI:MO=....,FORCE; Block the TS´sRXBLE:MO=....; Desblock the TS´s

- Some times the alarm does not desappear even if the cell comes upp, then do:

RLSLE:CELL= …; Desactiva la supervision of the alarmRLSLI:CELL= ….; Activa la supervision de la alarma

*******************************************************************************************************CELL RESTRICTION ACTIVATED (BSC)(To see wich cell is HALTED)

RLSTP:CELL = …ALL…, STATE = …HALTED…; Prints out all BTS´s wich are HaltedRLSTP:CELL=ALL; Prints out all cells in the BSC and their current stateRLCRP:CELL=...[+ sector]; Give us the occupation of channels.RLSTC:CELL=...[+ sector],STATE=HALTED; Put the cell out of servoice.RLSTC:CELL=...[+ sector],STATE=ACTIVE; Put the cell in service.

NOTA: Se houver mexidas nos combiners, seguir procedimento. Ter em atenção o hyb. Ficheiros: comb2.txt, comb3.txt

*******************************************************************************************************COMMAND LOG BLOCKED

Verify the Fault Code and follow the OPI.*******************************************************************************************************

5

COMMON CHARGING OUTPUT ERRORThis alarm indicates that the MSC is not able to write the CDR’s (Call Data Records) to the IOG.

Call prevention immediately but follow this procedure without wasting time.

Check the number of used individuals in buffer (NIU). Use this command very often to see the evolution:SAAEP:SAE=500,BLOCK=CHOF; (normal values are between 0 and 40)

1) Check the state of the links between CP and IOG. If anyone is blocked, deblock it.EXSLP:SPG=0;BLSLE:SPG=0,LINK=link; (link =0 or 1)

Look at the buffer again to see if it is decreasing (SAAEP). If not step 2

2) Is there any alarm “INFINITE FILE END WARNING” ?Yes Fault Code 214 execute this step

Fault Code 219 go to step 3No go to step 3

Verify the active subfile and the creation of the next. (NEXTSUB =ACTIVESUB+1). Probably the field NEXTSUB is empty.IOIFP:FILE=TTFILE00;

Verify destinations for charging ( names like: xxxxBILL and xxxxBILL1 ) and print subfile status in FPU for the NEXTSUBfile for both destinations.

INFDP;INFSP:FILE=TTFILE00-yyyy,DEST=dest;

If the NEXTSUBfile exists in FPU remove it.INFUE:FILE=TTFILE00-yyyy;

Check the existence of it in the HD and remove it.INMCT:SPG=0; :INFIP:FILE=TTFILE00-yyyy; :INFIR:FILE=TTFILE00-yyyy; :END;

Verify again NEXTSUB file creation and the evolution of buffer.IOIFP:FILE=TTFILE00;SAAEP:SAE=500,BLOCK=CHOF;

If buffer is decreasing stop procedure. If not go to step 3.

3) Check the TTFILES in use.CHOFP:FN=ALL; Print the state of the files – open/close

If TTFILE02 is blocked, deblock it CHOBE:FN=TT,FILEID=02;If TTFILE02 is closed, open it CHOFI:FN=TT,FILEID=02;

CHOFP:FN=ALL; Muestra el estado de las files – open/close Look at the buffer again to see if it is decreasing (SAAEP).If not decreasing go to step 4

4) Verify if there is any alarm concerning the IOG and take note of the referred node. Alarms like:“SPG not available” “SP node restarted”“SP working state not normal” “SP node Fault”“SP unit fault” “SP node automatically blocked”

Even if there is no alarm, continue this procedure but only in contact with prevention.Verify the state of the IOG

IMMCT:SPG=0; :IMCSP; :END;

Block the stand-by node (sbnode)BLSNI:SPG=0,NODE=sbnode;

Make a restart in Executive node (exnode). SYRSI:SPG=0,NODE=exnode,RANK=SMALL;

You will loose connection for about 5 minutes.Hopefully the problem is solved and the connection will be reestablished.If so, go to step 5.If not, local operation is required.

6

5) Verify buffer again (SAAEP). Check the state of SPG an deblock Stand-by node (sbnode).

IMMCT:SPG=0; :IMCSP; :END;BLSNE:SPG=0,NODE=sbnode; The node will be restarted.

Observe the recovery of the node (it can take 30 minutes or more):IMMCT:SPG=0;:IMCSP;:IMSIP:NODE=sbnode; (The field “STEP” of this printout increase til the value of around

4500 as long as the node updates ) :END;

*******************************************************************************************************CP FAULT (BSC)

This alarm indicates a hardware fault in the central processor. This alarm could be A1, A2 or A3 depending of the gravity.

DPWSP; Check the CP State. The correct state is: MAU=NRM SB=B SBSTATE=WO1º REPCI; Initiates a diagnostic of the CP, print faulty boards list (leva + ou – 15min) REPCE; Terminates the diagnostic2º REMCI:MAG=CPU-A/B,PCB=..MAI..; Prepares the system for the replacement of the faulty board.

- Gives a SYSTEM STATE WARNING3º RECCI; Orders a reparation of the CP +/- half an hour. If it is not succesful escalate to the next level.

Other Commands:EXSLP:SPG=.../ALL; Print SP link stateNSSTP; Print the state of the Clock ReferenceDICEP:REC=BITE/TEMP; Print Bit Error Record/Temporary faultsDIRCP:REC=CP; Print recorded error in CP, diagnostic functions. Se FC4 device is faultyDIRCP; Print error CP

*******************************************************************************************************CPT FAULT (APZ) (É a ligação entre o TMOS e o IOG,)

When CPT FAULT alarm exists, CPT Ports should be blocked and deblocked :

IMLCT:SPG=0;:MCDVP; Shows the AT´s of all the ports.:ILNPP:PORT=ALL; Printout of all the ports. The normal is a port of 64Kbps (PROT -> SDLC/V36 Rate-> 64000, this port

controls the next 4 portss (CPT/SDLC), but it is enough to block the SDLC/V36 to clear the alarm. :ILLBI:NP=1-1-1-3-1; Block Logical Port :ILLBI:NP=1-1-1-3-2; :ILLBI:NP=1-1-1-3-3; :ILLBI:NP=1-1-1-3-4; :ILLBI:PP=1-1-1-3; Block Physical Port

:ILLBE:PP=1-1-1-3; Deblock Physical Port :ILLBE:NP=1-1-1-3-1; Deblock Logical Port :ILLBE:NP=1-1-1-3-2; :ILLBE:NP=1-1-1-3-3; :ILLBE:NP=1-1-1-3-4; : ILNPP:PORT= ..porto especificado.., DETAIL; Print details of the port. :END;

NOTA: Wait a few minutes until the alarm ceases. If the alarm isn't ceased, call PREVENTION.

*******************************************************************************************************DEBLOCKING EMRP

RISPP:EMG=L001,EMRS=0;RIBLE:EMG=L001,EMRS=0;RILTP;

7

*******************************************************************************************************DEBLOCKING EXTERNAL ALARMS (BSC)

EXEDP:EMG=L001,EM=ALL; Saber Nªs dos EXAL0ALRDP:DEV=EXAL0-0&&-31; To know the position ALEXP:DEV=EXAL0-0&&-31; To know the state MBL/CBLBLEAI:DEV=EXAL0-0&&-31; BLOCKING if not MBLBLEAE:DEV=EXAL0-0&&-31; DEBLOCKING the DEV

*******************************************************************************************************DIGITAL PATH FAULT SUPERVISION (APT)

The supervision detected that a physical link , the DIP , is out of order . The problem can take place in the msc, hlr, scp… ( equipments controlling the DIP ) , on the DIP itself or on the other part .

ALLIP ; To see the other alarms. If there are other alarms about controlling equipments ( RP , EM, SNT , ETC ) try to solve them before. Else get more informations about the DIP .

DTSTP:DIP=RIL…; Prints the state of the DIPDTQUP:DIP=...; Prints the quality of the DIP´s that belong to the same ROUTE. DTDIP:DIP=…; To get the associated SNT

RILSP:DEV=RILT-…; State of DEV and associated BTS RILTP:DEV=...; Prints data, the state of the connections and the type of equipment. dos DEV da

interface de transmissão rádioRISPP:EMG=...,EMRS=...; Prints data of the path for the Semi-permanentes connections of the BTS

NTCOP:SNT=..SNT..; To get the associated DEV´sSTDEP:DEV=..DEV´s..; To get the route , to see if a signalling link is present)STRSP:R=route’s name; To know how many devices are busy , free , in and out off order on the route , watch nocc and nidle

In case of no SEBU devices in the SNT and if no physical problem found, you can try to block and deblock then DIP:DTBLI:DIP=dip;DTBLE:DIP=dip;DTSTP:DIP=dip;

- DIP of type TRI: DIP FAULT + BLOCKING SUPERVISION => PCM to the MSC downDTDIP:DIP=RIL123; Print the DEVs associated to the DIP RIBLI:DEV=RILT-123; Block the Device (If the RIL is 123, the RILT- is the same as well)RIBLE:DEV=........; Deblock the device

TSLOT1 -> PCM TSLOT2 -> RTTRADEP:DEV=…; Printout of the devices RHDEV, RXTRA, RALTNTSTP:SNT=…; Printout of the state of the SNT

NOTA: If the blocked device is for synchronization, then OPI: - RADIO INTERFACE SYNCHRONISATION SUPERVISIONNOTA: It is also possible that the fault is located in the ETB, OPI: - RADIO INTERFACE LINE TERMINATE FAULT

*******************************************************************************************************DIGITAL PATH ANAVAIABLE STATE FAULT

DTSTP:DIP=…;DTBLI:DIP=...; Block the DIPDTBLE:DIP=...; Deblock the DIP

*******************************************************************************************************DIGITAL PATH QUALITY SUPERVISION (BSC)

DTSTP:DIP=...; Printout of the state of the DIPDTQUP:DIP=...; Print the DIP´s belonging to same ROUTE to see if they have errorsDTQSR:DIP=...,SF,BFF,DF; Reset the existing errors in the DIP´s i question

…,ES,SES ; …ES2,SES2;

*******************************************************************************************************...

8

.DIP FAULT (BSC)

DTSTP:DIP=RIL.......; Vê o estado do DIP RILSP:DEV=RILT-.....; Estado do DEV e BTS associada RILTP:DEV=RILT-.....; Dados do DEV e BTS associadaDTQUP:DIP=RIL.......; Imprime a qualidade do DIPRISPP:EMG=...,EMRS=0; Ligações SEMIPERMANENTES a uma BTS

TSLOT1 ----------> LINHAS DE 2 Mb TSLOT2 ----------> RTT

*******************************************************************************************************DISTURBANCE SUPERVISION OF TRUNK ROUTES (MSC)

DUDSE:R=.....; Desliga temporáriamente a supervisão da rotaTestar a rota e resolver as falas

DUDAP:R=.....; Printout of Data Disturbance DUDAR:R=.....; Reset an Alarm from the disturbanceDUDIR:R=.....; Volta a ligar a supervisão da rotaDUDAP:R=.....; Printout of Data Disturbance

*******************************************************************************************************DUMP MANUAL (ver Backup Information Fault)

SYBFP:FILE=…; Printout das files e respectiva dataSYBUP:FILE=RELFSWn; n=n mais antigo, sempre a file mais antigaSYBFP:FILE; verificar se a file RELFSWn tem a data de hojeSYTUC; Troca as files de posição (roda o backup manual)SYBFP:FILE; Vê o estado das files do backup (RELFSW0 – 1ª file tem a data de hoje SYBUI:DISC; Activar o dump automático, se houver o FaultC.22 é porque já estavaSYBTP; DUMP times

*******************************************************************************************************EM FAULT (APZ)

This alarm indicates a hardware fault in the Extension Module.

ALLIP ; List the alarm and note the faulty EM (message EM FAULT)EXEMP:RP=..225..,EM=..3 ou ALL..; Verificar o estado do "EM".

STATE = MBL Manually blocked for maintenance activities. Consult the local team= CBL An RP is blocked. See action RP FAULT in first= ABL Automatic blocked. Se o "EM" estiver "AB" reparar o "EM"

REPRI:RP=..225..,EM=..3..; Reparação do EM respectivo. Wait for the message RP DIAGNOSISREMRI:RP=..225..,PCB=EMBINTERFACE,EM=..3..; Intervenão manualRECRI:RP=..225..,EM=..3..; Teste da reparaçãoEXEMP: RP=..225..,EM=..3..; Printa o estado do "EM”

Nota: State must be WO ( Working). If not WO call the prevention. Control with ALLIP that the alarm has disappeared.

*******************************************************************************************************EMG. CONTROL DOWN (BSC)

- Verificar se a estação está em baixo:RLCRP:CELL=.....: Imprime todos os tipos de canais disponíveisRLSLP:CELL=.....; Imprime todos os canais disponíveis e seus LVA'S

- (2 Mbit Down)------------->

EXEGP:EMG=...; Printout of data for indicated EMG`S **BL**EXEPP:EMG=...,EM=ALL; Eestado dos EM'S associados ao EMG e indicação do PREXCLP:EQM=CLC-...; Printout of data for signaling **SEAL**EXRPP:RP=...; Printout for an RP **WO**

9

RISPP:EMG=L097..,EMRS=0; Printout das ligações semipermanentes, se **BLOCK**, telefonar PTRISPP:EMG=ALL,PRI=1; Temos todas as RBSC e respectivas cascatasDTSTP:DIP=RIL... (ALL); Vê o estado do DIP e testa quando se faz um LOOP para teste

NOTA: O DIP usado é o primeiro que aparece no comando RISPP, dip de entrada.RILSP:DEV=RILT-213; Printout do DIP fault

- Se CLC esta CBL ------------------>

BLRPI:RP=..68..; Blocking a RPBLRPE:RP=..68..; Deblocking a RPBLCLI:EQM=CLC-...; Blocking a control Signalling LinkBLCLE:EQM=CLC-...; Deblocking a control Signalling Link

- Se é indicado o STC então seguir OPI – RP FAULT.- Se é indicado o STR então seguir OPI - EMG FAULT.- Se é indicado falha no "SYSTEM LINE" Então deve-se ver alarmes SNT ou DIP.

LOOP RILTP:DEV=RILT-338; DEV de saída, no RISPP da RBSC, Tslot2=DIP1 na BD da BTS DTSTP:DIP=RIL338; Vê o estado do DIP. (ABL, para o DIP2 da BTS está CBL) DTQUP:DIP=RIL1634; Verifica os erros da linha RXMSP:MO=RXETF-115; FAIL, BLOCDepois do LOOP

DTSTP:DIP=RIL1338; Vê o estado do DIP, se estiver WO, o prob. está do LOOP prá frente, entre a RBSC e a BSC está tudo bem.

Verificar as ETB´s DTSTP:DIP=RILT-…; Vê o estado do DIP2 da DB RILSP:EMG=…,EMRS=0; Printa estado das ETB´s :DEV=…; RIBLI:EMG=…,EMRS=0; Bloquear a ETB RILTP:DEV=RILT-…; Type equipamentoPara o EMRS RISTP:EMG=…,EMRS=…; Rádio Interface Radio selector status printA estação não sobe, só o EMG está BL RECEI:EMG=…,STR=…; RECEI:EMG=…,EMRP=0-A;

*******************************************************************************************************EMG FAULT (BSC)

RECEI:EMG=L001,STR=A; TESTE, se FC=46 e st=Cblock, fazer EXEGP:EMG=L001; se alguns ,STR=B; ou ,EMRP=0-A; CLC´s BL, a linha está em baixo.

REPEI:EMG=L001,STR=A; Print localization of faultREPEI:EMG=L001,EMRP=0-A; Testa a 1ª linha, se FC98 no PCM, se faultRLCRP:CELL=L001A; Verifica se a estação está a processar tráfegoRLSLP:CELL=L001A; Vê se a célula caiu ou não e quantos TS´s tem for a de serviçoEXEPP:EMG=L001,EM=ALL; Printout do estado dos EM´s deste EMG e tipo de processadorEXEGP:EMG=L001; Printa o estado do EMGEXCLP:EQM=CLC-5; Printout of Data for signalling linkRISTP:EMG=L001,EMRS=0; Estado do EMRS, controla o TSW, se BLSTATE=ABLRISBLI:EMG=…,EMRS=0; Bloqueia o EMRS=0 da EMGRISBLE:EMG=…,EMRS=0; Desbloqueia o EMRS=0 da EMGBLEEE:EMG=L001,EM=0; Desbloquear o EM do EMGBLCLE:EQM=CLC-5; Deblock of control signalling linkEXEPP:EMG=L001,EM=0; Printa o estado/type dos devicesREMEI:EMG=L166,MAG=STR-A,PCB=…; Repair funcionEXSCP:NAME=..ALL..; Print das Semi Permanentes Connections

*******************************************************************************************************EXTERNAL ALARM RECEIVER BLOCKED/FAULT (BSC)

ALRDP:DEV=.....; Printout of alarm receiver for BTS

10

EXEDP:EMG=L001,EM=ALL ou 0; Saber Nº´s dos EXAL0ALEXP:DEV=.....; Printout Blocking Designation, Device Pointer BLEAI:DEV=.....; Manual Blocking Designation, Device Pointer BLEAE:DEV=.....; Manual Deblocking Designation, Device PointerALRDP:DEV=.....; Printout of alarm receiver for BTSALEXP:DEV=.....; Printout of alarm data for alarm receivers

*******************************************************************************************************FREQUENCY HOPPING

- Se os TS tiverem com freq. HOP (LMO=840), desligar a freq. Hopping e voltar a ligar

RLCRP:CELL=… + sec; Visualização dos canais de tráfegoRLCHC:CELL=… + sec,HOP=OFF; Desliga a Freq. Hop.RLCHC:CELL=… + sec,HOP=TCH; Liga a Freq. Hop.RLCPP:CELL=…; Mostra-nos os valores das potênciasRLCLP:CELL=…; Mostra os TS que estão fora de serviçoRXTCP:MOTY=RX[E/O]TG,CELL=... + sec; Mostra o Grupo de Canais ligados ao TG RXCDP:MO=RX[E/O]TG-...; Imprime o estado dos TS, RX e TX

NOTA: Atenção, que este procedimento manda a célula “abaixo” momentaneamente*******************************************************************************************************FTAM PORT BLOCKED (MSC)

IMLCT:SPG=0 ou 1;ILNPP; Printout dos enderecos dos portosILBLI:NP=...; Bloqueia o portoILTEI:NP=...; TestaILBLE:NP=...; Desbloqueia portoEND;*******************************************************************************************************GROUP SWITCH FAULT (APT)

This alarm indicates a hardware fault in the GSS. The GSS includes 3 different parts following:TSM Time Switch Module SPM Space switch Module CLM Clock switch Module

In the GSS the module SPM and TSM are parallels ( 2 different plans). For example there is the TSM= 21 on the plan A and B.

1) Print the alarm list. If there are many alarms GROUP SWITCH FAULT call the prevention and stop this procedure

2) Analyse the alarm GROUP SWITCH FAULT and the value of TCASEA) TCASE = 3 or 4 Call PreventionB) TCASE = 1 or 2 Continue in step 3

3) Print the state of the different modulesGSSTP ; Printout of Group Switch test pathGSSTP:TSM=…; :SPM=…; :CLM=…; Mostra o estado, e a razão do estado do GS, da unidade respectivaSe for um SNT: NTBLE:SNT=…; Desbloqueia a SNT

4) Print the state of the module faulty given in the message GROUP SWITCH MODULEGSSTP :TSM = TSM-x-yy ; Print for TSM x = A or B Plan yy = Numbering of TSMGSSTP : SPM = SPM-x-y-z ; Print for SPM x= A or B plan y=row number 0-3 z=column number 0-3GSSTP : CLM-a ; a = 0,1 or 2

State: WO WorkingCBL EM blocked ( Do first the alarm EM FAULT)MBL Blocked manually ( See with the local team)SPM Blocked by SPM ( Repair the SPM in first)ABL Go step 5SNT Blocked by the SNT ( see alarm SWITCHING NETWORK TERMINAL FAULT)

5) Block the module faulty. If it’s a CLM module call the prevention and stop this procedureGSBLI :TSM=TSM-x-yy ; :SPM=SPM-x-y-z ; :CLM-a; For TSM, SPM ou CLM

Check that the module is blocked manually ( STATE = MBL)

11

6) Test the module faultyGSTEI:TSM=TSM-x-yy ; :SPM=SPM-x-y-z ; :CLM-a; For TSM, SPM ou CLM

Wait the message GROUP SWITCH UNIT TEST RESULT

A) Result = NO FAULTS FOUNDThe test is OK. Unblock the module

GSBLE :TSM=TSM-x-yy ; :SPM=SPM-x-y-z ; :CLM-a; For TSM, SPM ou CLM Check the state of the module. STATE must be WO (Working). Other cases call the preventionGSSTP :TSM=TSM-x-yy ; :SPM=SPM-x-y-z ; :CLM-a; For TSM, SPM ou CLM

B) Result = List of suspected boards. Call the prevention. End of the procedure

Outros Comandos:GSREP; Printout which automaticaly blocked unit is to be repaireGSCVP; Printa o estado do CLM control valueGSDSP:TSM=…; :SPM=…; :CLM=…; Printa os contadores estatísticos, disturbance

*******************************************************************************************************HEARTBEAT FAILURE (MSC) (BSC)

- O Canal lógico e permanente que envia o sinal periódico e espontâneo para o OMC,indicando que o comutador AXE está em funcionamento, está desligado.

ALHBE; Desliga o canal lógico de "Heart Beat"ALHBI; Liga o canal lógico de "Heart Beat"ALLIP; Print de todos os alrmes (só para confirmar que o canal está OK)

*******************************************************************************************************HLR AUTHENTICATION DATA REQUEST FAULT (MSC)

HGALP:NLOG=…(ALL); Imprime os dados das requisições de Aut. Falhadas HGALR; Faz desaparecer o alarme

- Analisar as falhas

*******************************************************************************************************I/O BLOCKED (APZ)

An Input/Output device (printer , alphanumeric terminal ) is not ok (paper , power…) . It cannot be used to get printouts from the msc or send it data . The problem can be located in the controlling msc’s equipements (RP, SP, LU) , in a part of the link or in the I/O . A Manually Blocked I/O is not a faulty I/O .

ALLIP ; To get informat. about the I/O and others alarms. If there are others alarms (RP, SP or LU), solve them first.IOBLI : IO = AT-x ; To block the I/O. The alarm A2 is transformed in an O2 alarm .IOBLE : IO = AT-x ; To unblock the I/O. Wait a minuteIOIOP : IO1 = ALL;ALLIP ; If the A2 alarm is back , and if it is not a strategic port report it to local team .

Outros Comandos:IMLPT: SPG= 0 ; :MCDVP ; :END ;

*******************************************************************************************************INFINITE FILE END WARNING (MSC) (+ abaixo á outra versão)

- When an infinite sequential file is full or connot be accessed, next file = active file + 1

SAAEP:SAE=500,BLOCK=CHOF;IOIFP; Printout da file que originou o alarme, a últimaINMCT:SPG=1; ou 0; INVOP; Printout dos volumes

12

INVOP:VOL=…; Check if the volume is fullEND; INFUP:FILE=TTFILE04; Verificar se a file pertence à FPU (File Process Utility) INFUP; Check if the file is processed by FPU INFSP:FILE=TTFILE04-0001,DEST=FTAM,ORDER=ALL/FIRST (file+velha)/last;

Print file attributes for infinite sequencial file IOIFP; Print file attributes of the infinite sequential IOIFC:FILE=SMSCA; Mudar os atributos (+ ou – 15 min) INFSP:FILE=SMSCA; INMIT:SPG=0; ou INMCT:SPG=1; INFIP:FILE=TTFILE04; Printout dos tributos da file – a última do prinout IOIFPEND;INFUP:FILE=TTFILE04; Verificar se a file pertence à FPUINFUP; Check if the file is processed by FPUINFSP:FILE0TTFILE04-0001,DEST=FTAM,ORDER=ALL/FIRST (file+velha)/LAST;INFUE:FILE0TTFILE04-0001,DEST=FTAM; Removes the definition of the indicated file

Remover a fileIOIFP; Vê a file em questão, e se o “NEXT SUB” não tiver a file seguinte, fazer o INFIR… para a file

seguinte (e pode ser também para as 5 seguintes)INMCT:SPG=0; INFIR:FILE=SMSCA-00(02); Remove the file from the FMS-system

\ file sempre a seguir á active SUB

END;

Tranfer file to external mediumINMIT:SPG=0; INFET:FILE1=SMSCA-0002,FILE2=IO; Copy an internal file, file1=source, from HD to…??END;

Transfer file internallyINMIT:SPG=0; INFIT:FILE1=TTFILE04,FILE2=SMSCA-0003; Copy data from one file to anotherEND;

Remove fileINMIT:SPG=0; INFET:FILE=SMSCA-0002; Remove the file from the FMS-systemEND;

Verify if that file is accessibleIOFAT:FILE=SMSCA; Executes output of a specified file

ALLIP; Verificar se ainda existe o alarme

RESUMINDO: Nome da file

IOIFP:FILE=CPLOAD; Da file em alarme, ver qual a file activa, n.INFSP:FILE=CPLOAD,DEST=TMOS;INMCT:SPG=0;INFIP:FILE=CPLOAD;END;INFUE:FILE=CPLOAD-00xy; xy=n+1 será a file seguinte, DESPROTEGER a fileINMCT:SPG=0;INFIR:FILE=CPLOAD-00xy; Apagar a respectiva fileEND;IOIFP:FILE=CPLOAD; Quando a file xy aparecer aqui e tivermos nextsub, OK

*******************************************************************************************************

13

.

INFINIT FILE END WARNING (MSC) (+ acima á outra versão)

COMMON CHARGING OUTPUT ERROR COMMON CHARGING OUTPUT CONGESTION

TT FILE 00 - SPG0 TT FILE 01 - SPG0 TT FILE 02 - SPG1 TT FILE 03 - SPG1

SAAEP:SAE=500,BLOCK=CHOF; - Este buffer tem um limite de 3000 ou mais e quando encher perde-se charging (verificar qual a TT file que está 01 no SPG.)

- Mudança do charging para o SPG0.CHOFP:FN=ALL;CHOFI:FN=TT,FILEID=00;

- A partir desta altura o tollticketing estará a ser escrito na TTfile00 que está no SPG0SAAEP:SAE=500,BLOCK=CHOF;

- Para verificar que os call records estão a ser escritos e o valor do NIU desce para valores baixos (de 1 a 20)CHOBI:FN=TT,FILEID=04; Este comando fecha (bloqueia) a TTfile que está cheia

Tomar nota das horas da ocorrência e do nº das subfiles:IOIFP:FILE=TTFILE04 e IOIFP:FILE=TTFILE00

ALERTAR A PREVENÇÃO E EM CASO DE DIFICULDADES NA ERICSSONPARA A PREVENÇÃO: (DAQUI PARA BAIXO)

- Alerta as operações do MIS de que vão receber bandas em relação ao periodo de tempo em que o tollticketing estiver no SPG0.

QUANDO O PROBLEMA ESTIVER RESOLVIDO,

CHOBE:FN=TT,FILEID=04; Ou outra TTfile (a que estiver cheia no SPG-1 (TT file 02 ou 03))CHOFE:FN=TT,FILEID=00;SAAEP:SAE=500,BLOCK=CHOF; Para verificar que os call records estão a ser escritos e o valor do NIU continua em valores

baixos (de 1 a 20).

- Alertar o MIS para iniciar a recolha e confirmarem que está tudo bem também no processamento dos ficheiros.

IOIFE:FILE=TTFILE00; No fim para fechar a ultima subfile activa antes de fazer a ultima banda no SPG0 (feito pelo OMC).

*******************************************************************************************************LINE UNIT BLOCKED (MSC) (BSC)

IMLIT:SPG=1; Entra na sessão de sub-comandos com o SPG1 ILBLI:LU=17-1-2; Bloqueia a unidade ou o device especificado ILBLE:LU=17-1-2; Desbloqueia a unidade ou o device especificadoEND; Termina a sessão de comunicacão com o SP

*******************************************************************************************************MT FAILED AUTHENTICATION (MSC)

- Quando o primeiro evento é guardado na lista de registos de falha de autenticação :

MGARP:NLOG=10...(ALL); Imprime a lista de detalhes das falhas de autenticação MGAAR; Faz desaparecer o alarme (reset)

14

NOTA: Analisar o resultado da Impressão

*******************************************************************************************************MT GSM INTERWORKING SUBUNIT FAULT

GIWU GIWSU0 01END

- Podemos ver alguma coisa com os seguintes comandos:MGGOP:GIWU=ALL,GIWSU=ALL;STRSP=ALL;STRDP:GIWU1I,STATE=SEAL&LIBL█BLODI:DEV=MIWULT-15&-16; Bloquea os devices

- Fazer reset manual na placa e teste.

BLODE:DEV=MIWULT-15&-16; Desbloqueia os devices

- Reportar a situação à prevenção.

*******************************************************************************************************MT IMEI SUPERVISION LOG FAULT (MSC)

- O alarme e gerado quando o primeiro resultado de confirmacao de IMEI, e deve ser guardado na lista de registos correspondente (BLACK, GREY, UNKNOWN):

MGSAR:LOG=BLACK;MGSGP:LOG=BLACK,NLOG=ALL;

*******************************************************************************************************NETWORK SYNCRONIZATION FAULT (APT)

A clock reference was lost due to some kind of disturbance. Importante: O DIP tem de estar a trabalhar

NSDAP; (:NOP) Printa todos os Clock-reference na área operacional (NOP-no operac. Area)NSSTP; Check CLOCK-Reference state. If the faulty is a DIP check if it is working and it’s quality.DTSTP:DIP=dip; Printa o estado do DIPDTQUP:DIP=dip; If not working or excessive error rate, take action on DIP before continuing

NSBLI:RCM=RCM; …:CLM=…; …:DIP=...; Bloqueia o DIP, RCM ou CLMNSTEI:RCM=RCM; …:CLM=…; …:DIP=...; Testa o DIP, RCM ou CLMNSBLE:RCM=RCM;…:CLM=…; …:DIP=...; Desbloqueia o DIP, RCM ou CLMNSSTP; Check CLOCK-Reference state. Takes sometime in state UPD (updating)

*******************************************************************************************************NM ROUTE ASR SUPERVISION (MSC)

STRSP:R=…Porto2o…; Para ver as congestões (% overflow)

*******************************************************************************************************PBX ALARMS

STRDP:R=PBX…,STATE= SEAL&BLOCK&LIBL; Mostra o estadoBLODI:DEV=BT…; Bloqueia o DEVBLODE:DEV=BT…; Desbloqueia o DEV

*******************************************************************************************************

15

.

.

PORT BLOCKED (APZ)

One of the places for communication with externals equipements ( billing centre , I/O ) is not ok . The problem can come from the msc’ equipment , from the link or the externals equipments . The CP decides then to block the PORT . A Manually BLocked PORT is not faulty .

ALLIP; Para ter inform. sobre o PORT. Se houver outros alarmes (RP, SP or LU), tentar resolve-los primeiro.IMLCT: SPG = 0 ; :ILNPP:NP=a-b-c-d; Se o RATE=2400 é impressora :ILBLI : NP = a-b-c-d ; To block the port manually :ILBLE : NP = a-b-c-d ; To deblock the port manually :END ;

NOTA: If the alarm back and it is not a strategic port, report it on normal working hours, else call PREVENTION .

*******************************************************************************************************PVC SET UP FAILURE

- Lost communication with IOG, check LU and NP state

IMLCT:SPG=0; : ILLUP; Print LU state : ILNPP; Print NP state : ILBLI:LU=…; Bloqueia a LU : ILBLI:NP=…; Bloqueia o NP : ILBLE:LU=…; Desbloqueia a LU : ILBLE:NP=…; Desbloqueia o NP : END;

*******************************************************************************************************RADIO CONTROL X-CEIVER ADMINISTRATION (TRANSCEIVER GROUP FAULT) (BSC)

RXTSP:TGN=TGL008A,TEI=0;RXMSP:MO=..............;RXTEI:TGN=TGL008A,TEI=0,TRXC;

*** ou ***RXCDP:MO=…;RXMSP:MO=…;RXBLI:MO=…;RXTEI:MO=…; Order para ver o Printout: selecionar no CH, Log Search… (esq)

Commando: RXTEI, clicar Cmd & Resp Search.

*******************************************************************************************************RADIO INTERFACE SYNCHRONIZATION SUPERVISION

RICDP:EMG=..V047..,MRS=0; Contador que analiza erros do contador MRS (processor que comuta linhas ou entradas na BTS)

NOTA: Logo a seguir a este comando, os erros ficam a zero (o comando faz print e reset dos erros ao mesmo tempo)

*******************************************************************************************************RADIO X-CEIVER ADMINISTRATION MANAGED OBJECT FAULT (BSC)

RXMDP:MO=…; Dá os devices RXCTRD associados a este TSRXMSP:MO=....; Imprime informacao do estado do MORXBLI:MO=....; Bloqueia o MO (Managed Object)RXLTI:MO=....; Inicia teste de Loop para verificar a ligacao entre a BSC e o TS da BTS; RXTEI:MO=....; Testa MO's da BTSRXBLE:MO=....; Desbloqueia o MO

16

RXMSP:MO=....; Imprime informação do estado do MO, LMO=2000 não vê a BTSRXMFP:MO=…; Dá o fault code (ver a lista de FC)

- Se com o RXBLI/RXBLE não resultar, fazer (para RBS200): (RXETS = RBS200 RXOTS = RBS2000) só p/ RBS200 só p/ RBS2000

NOTA: Para RBS2000, a hierarquia é: TS, TX, RX, TRX, TF, IS, CF, TG, e desbloquear é o inverso. Raramente tem de se lhe mexer

RXBLI:MO=…; Bloquear por esta ordem: TS, TX, RX, TRX, TF, TG RXESE:MO=…; Tira(r) de serviço por esta ordem: TS, TX, RX, TRX, TF, TG RXESI:MO=…; Coloca(r) ao serviço por esta ordem (inverso): TG, TF, TRX, RX, TX, TS RXBLE:MO=…; Desbloqueia(r) por esta ordem (inverso): TG, TF, TRX, RX, TX, TS RXMSP:MO=RXETRX-…; Só quando estiver OPER e quando o resto está desbloqueado

- Se LMO=2000, LTS blocked due to sychronization fault in BTS e Fault= TS SYNC FAULT RXBLI:MO=RXETS-…; Bloqueia RXESE:MO=RXETS-…; Tira de serviço RXMDP:MO=RXETS-…&&-…; Dá os DEV RXCTRD associadod a estes TS RXTBI:DEV=RXCTRD-2971&&-2975,FORCE; (2971 e o SEBU deste grupo) RXTEI:MO=RXETS-…; Testar o MO RXTBE:DEV=RXCTRD-2971&&-2975; RXESI:MO=RXETS-…; Coloca ao serviço RXBLE:MO=RXETS-…; Desbloqueia

- Se os TS com LMO=0040, só falta sincronizarem RLCFP:CELL=…; Ver as frequências da célula e freq HOP

- Se os TS tiverem com freq. HOP (LMO=840), desligar a freq. Hopping e voltar a ligar RLCHC:CELL=…,HOP=OFF; Desliga a Freq. Hop. RLCHC:CELL=…,HOP=TCH; Liga a Freq. Hop. RLCPP:CELL=…; Mostra-nos os valores das potências RLCLP:CELL=…; Mostra os TS que estão fora de serviço RXTCP:MOTY=RX[E/O]TG,CELL=...; Mostra o Grupo de Canais ligados ao TG RXCDP:MO=RX[E/O]TG-...; Imprime o estado dos TS, RX e TX

*******************************************************************************************************RADIO X-CEIVER ADMINISTRATION TRANSCODER / RATE ADAPTOR FAULT (BSC)

NTSTP:SNT=RXCTRD-…; Estado do SNTRABLE:DETY=RXCTRD; Desliga o bloco de supervisão respectivoNTCOP:SNT=RXCTRS-94; Ver o DEV Assignados ao SNTSTDEP:DEV=RXCTRD-3010&&-3039; Print Devices State DetailsRRTBI:DEV=RXTRA-310&&-3039,FORCE; Bloqueia de 5 em 5 todos os DEV do tipo RTT da placa em questão BLODI:DEV=…; Bloqueia os DEV especificados (se necessário) BLODE:DEV=…; Desbloqueia os DEV especificadosRRTBE:DEV=RXTRA-3010&&-3039; Desbloqueia todos os DEV do tipo RTT da placa em questão STDEP:DEV=RXCTRD-3010&&-3039; Print devices state detailsRABLI:DETY=RXCTRD; Liga o bloco de supervisão respectivoEXEMP:RP=…,EM=ALL;RADRP:DEV=RXCTRD-1762; Printout dos DEV do RP e EMRADEP:DEV=…; Printout devices in BSCRXMDP:MO=RXETS-…&&-…; Dá os devices RXCTRD associados a estes TS

*******************************************************************************************************REMOTE INTERFACE LINE TERMINAL FAULT (BSC)

RICSP:EMG=…,EMRS=0; Print state for sync. inletsRIBLI:DEV=RILT-912; Bloqueia o DEVRITTI:DEV=RILT-912; Testa a função do DEVRIBLE:DEV=RILT-912; Desbloqueia o DEV

Fault Code:2 "DEVICE" bloqueado pelo EMRS3 Erro de "Restart"

10 Indicacao de alarme recebida11 Falha de alimentacao

17

4 Processador do "DEVICE" com defeito5 Perda de sinal6 Perda de alinhamento de trama7 BER demasiado elevado8 ALL1 indicado9 AIS (ALARM INDICATION SIGNAL)

12 "DEVICE SPEECH BUS FAULT" (Perda de 2Mbit/s)13 "DEVICE SPEECH BUS FAULT" (Perda de sincronismo de trama)14 Falha de paridade (PCM-DEVBIC)15 Falha de paridade (DEVBIC-PCM)16 Falha de paridade ("RATE ADAPTION"- Adaptacao de debito)17 Outras falhas de "HARDWARE"

*******************************************************************************************************RESTART MANUAL

SYREI:RANK=…; Ordena reinicialização do sistemaSYRIP:LOG=…; Ordena impressão do LOG information de recuperação do SWSYRIP:SURVEY; Verificar se existe alguma inform. de SW de recuperação a ser introd.SYRIP:EVENT=18; Imprime informação do restart e/ou informação erros de SWSYRAE; Termina acções de recuperação

*******************************************************************************************************ROUTE RESTRICTION ACTIVED

BLORP; Print das rotas fora de serviço

*******************************************************************************************************RP FAULT (APZ)

This alarm indicates a hardware fault in the regional processor.

BLRPI:RP=65; Se ABL ou BLOCKBLRPE:RP=65;

ALLIP ; List the alarm and note the faulty RP ( message RP FAULT)EXRPP:RP=65;REPRI : RP = xx ; Perform a diagnostic of the RP faulty

TEST RESULT = PASSED The fault could be temporary so you can control the repair and unblock the RP. TEST RESULT = FAULT It must be necessary to change some boards, try to do the repair check.

REMRI:RP=65,PCB=..STCP..;RECRI : RP = xx ; The TEST RESULT must be PASSED in the message RP REPAIREXRPP : RP = xx/ALL ; State of RP. A state different of WO is not normal so call the prevention

Outros Comandos:DIRRP : RP = ALL ; Print error RPBLRPE:RP=65;EXRPP:RP=65;EXEMP:RP=65,EM=ALL; BLEMI:RP=65,EM=0;FCRWS:RP=65,WS=SEP; Fazer de seguida BLRPE: RP=…; ao RP que ficar MBLBLEME:RP=65,EM=0;

DPECR:RP=65,CM=ALL; Atenção, pode provocar restart

*******************************************************************************************************SEIZURE QUALITY SUPERVISION (BSC)

- Função faz o check do ratio entre “normal calls” e chamadas com anormal “seizure time”

SEQIP:R=ALL; Lista os DEV. Que originam este alarme para um par de rotas- Caso seja necessário, testar os devicesSEQAP:R=…(ALL); Ver a data existenteSEQSE:R=…; Se necessário desligar temporáriamente a supervisãoSTDEP:DEV=...; Printa o estado do deviceBLODI:DEV=…; Bloqueia os devices especificados,

Testar os devices “test of junktores (AJ e BJ)”“” Key set receiver (KR)“” Incoming trunk (IT)“” Outgoing trunk (OT)

18

BLODE:DEV=…; Desbloqueia os devices especificadosSEQAP:DEV=…; :R=…(ALL); Ver a data existenteSEQAC:DEV=...; Alteracao da data se necessarioSEQAR:DEV=…; :R=…(ALL); Reset dos alarmes especificados

- TESTAR OS DEVICES E REPARAR AS FALHAS: OPI "TEST OF AJ/BJ, KR, IT, OT, BT AND RT.

SEQIR:R=ROTA; Volta a activar a supervisão "SEIZURE QUALITY"*******************************************************************************************************SEIZURE SUPERVISION (MSC)

Nota: Existem devices, ou devices de uma dada rota, que não foram usados durante o período de supervisão.

SETAR; Faz desaparecer o alrmeSETIP:R=r; Mostra todos os devices da rota, que não foram usadosSETIP:RNSD; Aa rotas com devices não usados

- Se existem devices com falha fazer (o que vem a seguir), se Não (1):

BLODI:DEV=dev; Bloqueia o/os devicesBLODE:DEV=dev; Desbloqueia os devices

- Testa-se e repara-se as falhas ("TEST O BOTHWAY TRUNK (BT)" AND TEST OF IWU DEVICE")- Em caso de existir algum device com falha, fazer:

SETRE:R=r; Desligar temporáriamente a supervisão do uso de devices se não puder ser repsrad no período de supervisão.

- Espera-se até a falha desaparecer

SETIR:R=r; Volta-se a ligar a supervisão para os devices (1) - SETAP:R=r; Lista dados acerca da supervisão de uso de devicesSETAC:R=r; Alterar dados da supervisão se necessário (só a pedido da prevenção)

*******************************************************************************************************SEIZURE SUPERVISION OF DEVICES IN BSC (BSC)

NOTA: Um tipo de Device é dado como nunca sendo utilisado ou como permanentemente ocupado, durante o último período de supervisão.

RASAP; Mostra Devices "NUNCA USADOS" ou "PERMANENT. OCUPADOS"RAPTI:DEV=…; “” :LCH=…; Trace of faulty devices …“CALL PATH TRACING" “” :CIC=…; RASAR:DETY=RALT; Ordena um "RESET" ao alarme(S)RASSP:DETY=RALT; Mostra todos os dados de "SEIZURE SUPERV." por tipo de device.

*******************************************************************************************************SEIZURE SUPERVISION OF LOGICAL CHANNELS

RLVAP; Printout os seizure supervision of alarm object channelRLVLP:CELL=…+sec; Printout of supervision dataRLVAR:CHTYPE=…; Sempre BUSY ou IDLE

*******************************************************************************************************SEIZURE SUPERVISION OF TRUNK ROUTES (on route) (MSC)

STRSP:R=......; Indica o nº de DEV. na rotaSTRDP:R=......,STATE=SEAL&BLOC&LIBL; Print Devices State Details, "BUSY, BLOC or LIBL"

(ver SEIZURE QUALITY SUPERVISION)Se o BLS=ABL e o FTYPE=S quer dizer que estes DEV estão sempre ocupados (cheios de sinalização), ficando neste estado fazer: SEQAR:R=..rota..; …DEV=..dev que estão ABL..;

19

SETIP; Printout of not seized devicesSETIR:R=PBX01O;SEQAR:DEV=....; Reseting for specified alarm ceasing

*******************************************************************************************************..SEMI PERMANENT CONNECTION

EXSCP:NAME= ..MATTD-1..; Dá-nos o Dev associado a esta rotaEXDEP:DEV=..UPD-1..; Dá-nos o SNT

Se o Dev for “RBLT…,” o comando a dar é (Deve-se ver o “DEV 1”)RADEP:DEV=..RBLT…;

NTCOP:SNT=..UPET-0..; Dá-nos o DIPDTSTP:DIP=..OUPET33..; Vê o estado do DIPSTDEP:DEV=..OUPET33..;

*******************************************************************************************************SIGNALLING FAULT SUPERVISION (MSC)

- Existem Devices de sinalização que estão bloqueados

FAIAP:R=ALL; To see the route and/or the class of alarms for the faulty devices

- If there are faulty devices then do: FAISP:R=…; :ACL=alarm class; Dados da supervisão nas rotas de sinalizaçãoFAISE:R=...; :ACL=alarm class; Desliga temporáriamente a supervisão de falha de sinalisação para a rotaSTDEP:DEV=…; Checking signalling fault alarm for devicesBLODI:DEV=…; Bloqueia os DEVBLODE:DEV=…; Desbloqueia os DEVFAIAR:DEV=DEV; Apaga-se todos os alarmes dos DevicesFAIAP:R=...; :ACL=alarm class; Ver a rota e/ou a classe de alarmes para devices com falha FAISI:R=...; :ACL=alarm class; Volta-se a ligar a supervisã

*******************************************************************************************************SLEEPING CELL

RLCFP:CELL=…+sec; Printout das frequências da célulaRLCRP:CELL=…+sec; Printa estado dos canais (Busy or not)

- Tirar as estatísticas desta célula (válido para peíodos de: INT=5min,15min,30min,1h e MÁX 24h)

IMLIT:SPG=0; : SDTDP:RPTID=101,INT=…; Mostra as estatísticas de todas as células daquela BSC : SDTDP:RPTID=101,INT=…,OBJTYPE=CLTCHF,OBJ=..célula+sec..; Mostra as estatísticas para a célula

escolhida : END;RLSTC:CELL=…+sec,STATE=HALTED; Tira a célula de serviçoRLSTC:CELL=…+sec,STATE=ACTIVE; Coloca a célula ao serviço

*******************************************************************************************************SMALL RESTART IS PENDING (APZ)

For further information about the restart see RESTART SYSTEM. In some cases the system decide to delay an automatic restart depending of the block’s category. For the alarm SMALL RESTART IS PENDING there are 3 possibilities :

Ordered a restart small immediately. Change the time of the restart Cancelled the restartIt’s necessary to call the prevention to decide which action can be done, but you need to control that the switch is

working fine (complaints of the subscribers ?)

For information only some commands about this problem.

20

SYRTP ; List the time of the scheduled restartSYRTS : RANK = SMALL , CANCEL ; Cancel the restartSYREI : RANK = SMALL ; Ordered the restart

*******************************************************************************************************SYSTEM RESTART (APZ)

To prevent some software error the system can do a restart automatically. The restart has a restart rank. The restart rank is one of the following:

- RESTART SMALL : duration 1 minute. The calls cannot established- RESTART LARGE : Duration 1 minute. The calls cannot established and the calls in progress are cut off- RESTART RELOAD : Idem LARGE but duration between 1 and 10 minutes.

The restart RELOAD is the most critical. After a restart the system indicates that with the alarm SYSTEM RESTART

CACLP; Check the clock of the system and verify that DATE and TIME are OKSYRIP:SURVEY; Print restart information. Check the type of the restart (Small, large or reload)

The last restart has the field ACTIVE = YES (and note the number of EVENT)In case of reloads or escalating restarts (cyclic or small followed by a large) call PREVENTION immediately. In case

of isolated small or large restarts call PREVENTION in the morning to inform if it occurs during the night.

SYRIP : EVENT = xx; ..,FORM = LARGE ; xx : event number get from the SYRIP Print the restart information

NOTA: Collect the printout in a file to send to the local team for the trouble report.

After System RestartC7LTP:LS=ALL; Link stateGSSTP; GS state/TSM, clock stateNSSTP; Reference clock stateDPWSP; CP state

No MSC:ALLIP; Check the alarm list and Verificar se existem alarmes A1. Verificar o CP. C7LTP:LS=ALL; Link stateSTRSP:R=ALL; Device state surveyEXDRP:R=route;STRDP:R=…; Device state detailsSTDEP:DEV=MALT-…; Devices for a specific route

*******************************************************************************************************SOFTWARE ERROR (MSC) (Avisar Prevenção do OMC em questão)

SYRIP:SURVEY; Print dos FORLOOP´sSYRAE:RECTYPE=SOFTERR; Fazer um Reset ao Software ErrorALLIP; ATENÇÃO: á 3ª vez que isto é feito pode provocar um RESTART

*******************************************************************************************************SOFTWARE FILE CONGESTION (APT)

A SAE ( Size Alteration Event ) from a functionnal block ( charging of communication , recording of subscriber … ) is using all its allocated individuals ( memory ) . So its specific function cannot be used once more .

COFDP; Printout das files partecipantes e seu tamanhoCOFLP; Identify the SAE and the block. Para visualisar os detalhes do LOG de congestão

Nota: If it’s SAE 500 , BLOCK=CHOF call PREVENTION IMMEDIATELY and refer to actions on alarm “COMMON CHARGING OUTPUT ERROR”.

The NCONG indicates how many individuals had missed. Get more informations.SAAEP:SAE = x ; ( if x <500 ) Print do bloco em questãoSAAEP:SAE = x , BLOCK = name of block ; ( if x >499 ). Valor no momento: NIU ocupado; NI Máx a ocupar

SAAII:BLOCK=..HSD..,SAE=..786..,NI=..5000..; Altera o valor do NI (Number of Individuals) para ter maior capacidade de guardar ficheiros (só mediante pedido da prevenção)

COFAR ; Remove the alarm. If the congestion comes again , call PREVENTIONCOFLR; Apaga o registo do LOG

21

Nota: Depois de se alterar o SAE, o DUMP automático fica desligado, logo é necessário fazer o DUMP manual (que terá de ser bem defenido e testado devido à alteração do SAE).

*******************************************************************************************************SP NODE RESTARTED (MSC) (BSC) (ou se não existir actualização da alarm list)

SP TRACE SYSTEM INACTIVE (MSC) (BSC)

IMMCT:SPG=0; Entra para linha de SubComandos do SP : IMCSP; Verifica o estado do IOG 11 : IMSIP:NODE=B; Printout do estado do nó, em alarmeEND; TerminaBLSNI:SPG=0,NODE=B; Bloqueia o nó do respectivo SPG do IOGBLSNE:SPG=O,NODE=A; Desbloqueia o nóIMMCT:SPG=0; Entra para linha de SubComandos do SP IMCSP; Ir verificando se o nó entra em Updating IMRDP:NODE=B,FORM=LARGE; Reset do alarme, no Printout estará toda a informaçãoEND;

TEST SYSTEM; Deve aparecer o alarme TEST SYSTEM ACTIVEDEND TEST; Caso não apareça o alarme, fazer um restart no IOG, falar c/ prevenção

SYRSI:SPG=0,NODE=B,RANK=SMALL; Node é o que esta SB no Printout do IMCSP- Se o nó continuar isolado, fazer um reset na placa de CPU.

*******************************************************************************************************SP NODE FAULT (APZ)

This alarm indicates a hardware fault in the IOG. L’IOG has 2 nodes. Normally one node is working and the other is standby. When this alarm arrives it’s mean that one node is blocked automatically. IOG manages the entire IO interface, files, HD, OD etc…

IMMCT : SPG = 0 ; Entra para linha de SubComandos do SP. : IMCSP ; Verifica o estado do IOG 11 : IMSIP:NODE=B; Printout do estado do nó, em alarme : END ;

The node faulty is BLOCKED in the message NODE CONFIGURATION STATUSRESUP:SPG=..0..,NODE=..x..; x é o node Blocked. Ordena o Printout da lista das placas suspeitas de erro

Print the last events on the node faulty. FRDATE = date of alarm SP NODE FAULT. FRTIME = 2 hours before the message SP NODE FAULT

DISFP : SPG = 0 , NODE = x ,FRDATE = YYMMDD , FRTIME = HHMM ;RESUI : SPG = 0 , NODE = x ; Use the node faulty for NODE. Perform a test of the node faultyTEST RESULT = OK No faults found. TEST RESULT not OK Call the prevention to reset the IOG and to change boardsBLSNE : SPG = 0 , NODE = x ; x is the node faulty. Unblock the node

NOTA: Wait the message NODE DEBLOCKING EXECUTED (duration 10 minutes to 1 hour)ALLIP ; If the alarm SP NODE FAULT has not disappeared call the prevention

*******************************************************************************************************SP TRANSIENT FAULTS (MSC)

INMCT:SPG=0; :IMCSP; Ver qual o Node com problemas :END; BLSNI:SPG=0,NODE=A;RESUI:SPG=0,NODE=A;BLSNE:SPG=0,NODE=A;INMCT:SPG=0; :IMCSP; Ver se o State passou a reloading :END;IMLIT:SPG=0; :IMTLP:NODE=A; :IMTLR:NODE=A;

22

:END;INMCT:SPG=0; :IMCSP; Ver se o state passou a Updating Loading :END;

*******************************************************************************************************SP UNIT FAULT (APZ)

This alarm indicates a hardware fault in the IOG. The IOG has 2 nodes. Normally one node is working and the other is standby. When this alarm arrives it’s mean that one node is faulty. IOG manage the entire IO interfaces, files, HD, OD etc.

IMMCT : SPG = 0 ; Check the state of the IOG. : IMCSP ; : END ;Check the state of the node faulty in the message NODE CONFIGURATION STATUS

STATE= BLOCKED STATE = Different of BLOCKED You need to block the nodeBLSNI : SPG = 0 , NODE = y ; y is the NODE’s value from the

Message SP UNIT FAULTIMMCT : SPG = 0 ; The node faulty must be BLOCKED : IMCSP ; : END ;RESUP : SPG = 0 , NODE = x ; x is the node marked BLOCKED (A or B). Print the list of the boards faultyRESUI : SPG = 0 , NODE = x ; Use the node faulty for NODE. Perform a test of the node faulty

TEST RESULT = OK No faults found continue with interventionTEST RESULT not OK Call the prevention for direct intervention

BLSNE : SPG = 0 , NODE = x ; Deblock the node. x is the faulty nodeNota: Wait the message NODE DEBLOCKING EXECUTED (duration 10 minutes to 1 hour)ALLIP ; If the alarm SP NODE FAULT has not disappeared call the prevention

*******************************************************************************************************SUPERVISION OF LOGICAL CHANNELS AVAILABILITY (BSC)

RLSLP:CELL=L067A;RXTCP:CELL=L067A,MOTY=RXETG;RXTLP:MO=RXETG-90; Caso não saber a CélulaRXMSP/..BLI/..BLE:MO=RXETX-90-0-0&&-7; RADIO X - CEIVER ADMINISTRATION

*******************************************************************************************************SWITCHING NETWORK TERMINAL BLOCKED/FAULT (APT)

A link between an ETC and the GROUP SWITCH is down . The DIP connected to the ETC cannot be used . Get informations about the chain : SNT , ETC , DIP , DEVICES is necessary before testing the SNT .

NTSTP:SNT=...; Switching Network Terminal StateNTCOP:SNT=...; Ver DEV assignados ao SNTSTDEP:DEV=..&&..; A SEBU state for a dev indicates that a semipmt. connetion exists. Take note of the route nameBLODI:DEV=…&&…; Bloqueia TRA devicesNTBLI:SNT=...; Blocking of Switching Network TerminalNTTEI:SNT=...; Testar o SNT, se passar o teste, desbloquear o SNTNTBLE:SNT=...; Desbloquear o Switching Network Terminal (SNT)BLODE:DEV=…&&…; Desbloquear os RXTRA individuaisNTSTP:SNT=...; Printout Switching Network Terminal StateDTSTP:DIP=..DIP..;STRSP:R=name of route; Test Result = Faulty verify the occupation of the route to decide if this is a service

affecting situation. If so, call PREVENTION.

- Quando é uma ligação com semi-permanentes não é possível bloquear directamente o SNT:NTSTP:SNT=ETRBLT-51; Switching Network Terminal StateEXEGP:EMG=L196; Verificar o estado do EMG e qual é o Control-linkEXCLP:EQM=CLC-40; Verificar o estado do CLC e qual o canal atribuídoRADEP:DEV=RBLT-1648; Confirmar o SNT como semi-permanenteBLCLI:EQM=CLC-40; Bloquear o CLCEXCLE:EQM=CLC-40; Desdefinir o Control Signalling LinkEXCLP:EQM=CLC-40; Verificar o estado do CLC e qual o canal atribuídoNTBLI:SNT=ETRBLT-51; BLOCKING OF SWITCHING NETWORK TERMINAL

23

NTBLE:SNT=ETRBLT-51; DEBLOCKING OF SWITCHING NETWORK TERMINALNTSTP:SNT=ETRBLT-51; SWITCHING NETWORK TERMINAL STATEEXCLI:EQM=CLC-40,DEV=RBLT-1648; Definir o Control Signalling LinkBLCLE:EQM=CLC-40; Desbloquear o CLCEXCLP:EQM=CLC-40; Verificar o estado do CLC e qual o canal atribuídoNTSTP:SNT=ETRBLT-51; SWITCHING NETWORK TERMINAL STATE*******************************************************************************************************TRANCODER RATE ADAPTOR FAULT (BSC)

RADRP:DEV=…;EXEMP:RP=…,EM=ALL;NTCOP:SNT=RXCTRS-94; Ver DEV assignados ao SNTSTDEP:DEV=RXTRA; Check TRA state, must be ABLRRTBI:DEV=RXTRA-310&&-3039,FORCE; Bloqueia os DEV RXTRABLODI:DEV=RXTRA-94; Bloqueia TRA devicesBLODE:DEV=RXTRA-94; Desbloquear os RXTRA individuaisRRTBE:DEV=RXTRA-310&&-3039; Desbloqueia os DEV RXTRA

- Se não estiver Working:RADEP:DEV=RXTRA; Ver SNTNTSTP:SNT=SNT; Ver o estado do SNT

- Se estiver a Trabalhar:DPECS:RP=...,CM=EM; 2 Vezes separa o RP (pode provocar "SYSTEM RESTART)

*******************************************************************************************************VOLUME LIMIT EXCEEDED (APZ)

A volume is like a partition on the IOG’s hard disk . The alarm means that the memory space used in the volume passed over the predefined threshold .

INMCT:SPG=0; : INVOP; Volume attributes internal : INVOP:VOL=..EXCHVOLUME..; Do volume onde estão as Ttfiles, calcular % de ocupação

(usedsize / totsize x 100 = < 90%), senão apagar subfiles mais antigas : INFIP:VOL= EXCHVOLUME; Printout das files incluidas neste volume, a última é a activa : END;

NOTA: Se aparecer o CALLVOLUME, muita atenção e cuidado, trata-se do $ Taxação $ da Telecel.

INMCT:SPG=0; : INVOP; Volume attributes internal : INVOP:VOL=CALLVOLUME; Do volume onde estão as Ttfiles, calcular % de ocupação

(usedsize / totsize x 100 = < 90), senão apagar subfiles mais antigas : INFIP:VOL=CALLVOLUME; Printout files incluidas neste volume, a última é a activa : INFIP:FILE=TTFILE0x; Printout das subfiles da Ttfile activa, as primeiras são as mais velhas : END;

IOIFP; Sequencia da rotação das subfilesINFSP:FILE=TTFILE0x,DEST=CHARGING04; Escolher as primeiras 10 para apagar (as + velhas)INFSP:FILE= TTFILE0x-abcd,DEST=CHARGING04; Por cada subfile, ver se tem startime=data

Ex: (hoje é Stoptime de Dumptapel)INFDP:DEST=CHARGING04;INFSP:FILE=TTFILE0x,DEST=CHARGING04;INFSP:FILE= TTFILE0x-abcd,DEST=CHARGING04;

- Para cada file que se remover:INFUE:FILE= TTFILE0x-abcd; INMCT:SPG=1; : INFIR:FILE=TTFILE0x-abcd; : END;

24

NOTA: Notify prevention during the day. During the night wait a minute a check the used size again to see if it is growing. If so, call PREVENTION. If it is stable, notify PREVENTION in the morning.

25