Notes:

Energy Alarms Q DOES NOT OPEN TT

RBS OUTDOOR ARE NORMALS 2A50 and 2A 22, They are produced
for having connection to the same group of rectifications of
Movilnet... No external electric network, therefore always shows red.
the alarm of Opeando with Baeria
2A-18 DC Voltage out of Range, IF OPENING TT

rlcrp:cell=04841;
rlstp:cell=01234; to see if we have held sectors.
rxcdp:mo=rxotg-139;
rlstc:cell=04841,state=halted;
04842
rxbli:mo=rxots-139-0-1,force;
rxble:mo=rxots-139-0-0&&-7;

Monitoring:
!To view alarms by categories
allip:alcat=ext; We see external alarms.
allip:alcat=apt; we see alarms of physical connections on the nodes.
allip:alcat=apz; we see software alarms.
allip:acl=a1; we see class A1 alarms.
allip:acl=a2; we see class A2 alarms.
we see observation alarms.
we see observation alarms.

dtdip:dip=218rbl2;
rxotg
rxmsp:moty=rxocf;
rxasp:mo=rxotg-139;
dtstp:dip=(DIP)rbl2;
dtqup:dip=178rbl2;
rxmsp:mo=rxotg-139,subord;
rxmsp:moty=rxocf;
rxmfp:mo=rxocf-139;
rxmfp:mo=rxotrx-139-0;

rxmfp:mo=rxotx-139-0;
rxmfp:mo=rxorx-139-0;
To verify the power, and which radio belongs to
what cell....
rxtcp:moty=rxotg,cell=04841; find out the TG
rxtcp:mo=rxotg-#; check the number of cell
rxapp:mo=rxotg-139;
rlstp:cell=05912;
for software loading in radios
rxmop:mo=rxotg-#; check update of the rbs and the basic parameters
rxcdp:mo=rxotg-#; to see the frequency assigned to each sector and state of the tg
complete
rldgp:cell=###; sector in which the cell is defined and the band of
frequency at which each sector operates
rxmop:mo=rxotx-136-0&&-11; To view the configuration of the TRX

TO KNOW THE DIP NUMBERS OF A RBS, THE COMMAND MUST BE EXECUTED

RXAPP=RXOTG-#;

Synchronous digital path supervision

tpcop:sdip=(No)etm2;
tpcop:sdip=all; shows all the DIPs connected to which E1, and to which STM1 of the
red

tpstp:sdip=5etm2; shows the status of each E1, WO, manually blocked or not
defined (UNEQ)... if it is 1900, it can be blocked, but if it is 850 it must be
report
Movilnet must inform about each E1 activation for verification.
that it is not manually blocked.

To check if there are halted sectors (or chg group associated with time slot)
detained) and if there are any, reactivate them again:

rxtcp:mo=rxotg-144;
rlstp:cell=09631;
09631
09632
09633
rlstp:cell=09632;
rlstp:cell=09633;
rxmsp:mo=rxotg-60,subord;
rxmfp:mo=rxocf-60;

IT WILL SHOW THE ASSIGNED DEVICES TO THE RADIOS, DIVIDING ANY DEVICE
BETWEEN 32
THE DIP NUMBER OF 850 AND 1900 WILL BE OBTAINED

===================================================================================
==================
Traffic Test

rxasp:mo=rxotg-36;
rxtcp:mo=rxotg-36;
rlcrp:cell=06711;
rlcrp:cell=06712;
rlcrp:cell=06713;

-------------------
----------------
Important RBS alarms:

!!!!!!!!!!!!!
BTS EXTERNAL-RXOTF-XX;..TF=Time Function..Indicator of problem with signal
Clock/ The network synchronization reference of the PCM is faulty...!!!!
DIP - BLOCK AND UNBLOCK E1
!!!!!!!!!!!!!!
RXOTS-67-8-7, Time Slots Failure.
<rxmfp:mo=rxots-67-8-7;
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT INFORMATION Victor. Taborda, Juan Palma, Joege Bogarin and
Milagros Alvarez, with MBO and CCS. STATISTICS ARE REQUIRED WITH HIGH PRIORITY.
GENERATED IN THESE NODES IN
SINCE A FAILURE OR DEGRADED CONDITION IN THEM DOES NOT GENERATE A VISIBLE ALARM IN COR,
MO BTSSWVER
RXOTS-67-8-7 ERA-G04-R12-V01

RU
0

RUPOSITION

STATE
OPER 00000 60228 20567

EXTERNAL FAULT CODES CLASS 1B

3

END

The TRAU frames (voice/data) coming from the BSC for a specific hour TRU-
slot is missing or damaged. Possible reasons This is more likely to be a
failure in the BSC (for example, no TRA assigned, blocked RBLT devices, T1
it has a lot of errors, there is no connection in the Group-Switch, etc) or in the
A-bis transmission trajectory. It may involve a loop TS test with RXLTI...
Listen
Read phonetically

dtbli:dip=(dip)rbl2;block
dtble:dip=(dip)rbl2;unlock

Elbert Notes

Page for sending notifications

Translation not applicable for the provided URL.
----------------------------
Invalid input. Please provide text for translation.
-----------------------------
Movilnet page

Invalid text for translation.

------------------------------
We called Omar Soler (on duty)
ALARM 562 A2/APT "MSSBT4_TA17035"U 081207 0112
IO-FAULT FOR DATA RECORDING PER CALL
-----------------------------
BSCMBO Alarm

DISTRIBUTED GROUP SWITCH FAULT

(In my personal folder there is a procedure)

from this alarm, review)
---------------------------
The "AP FAULT" alarms

they are informative alarms

that indicate that some process
that was executed in the Node
I present some problem and
we have to check which one it is
that failure. (we can
remove this alarm for the OSS)
---------------------------
!Waiter:
rxasp:moty=rxotg;
rxasp:mo=rxotg-32;
dtstp:dip=40rbl2;
dtstp:dip=253rbl2;
rxmfp:mo=rxocf-40;
rxmfp:mo=rxoTRX-153-1;
rxmfp:mo=rxoRx-146-6;
rxmsp:mo=rxotg-280,subord;
rxtcp:moty=rxotg,cell=06251;
rxmfp:mo=rxotg-82,faulty,subord;
rxapp:mo=rxotg-40;
dtstp:dip=82rblt2&191rblt2;
rxcdp:mo=rxotg-151;
allip; (to see the MSS)
tpstp:sdip=all;
rxmfp:mo=rxotg-82,faulty,subord;
rxmop:mo=rootx-212-0&&-3;
To see if the E1 devices are MBL:
stdep:dev=rblt2-8097&&-8127;

To carry out the tests of external alarms:

ALLIP:ALCAT=EXT;

!For halted a sector:

rlstp:cell=02403; !ves chgrp halted or no
rlstc:cell=11832,state=halted; !stop the entire sector
rlstc:cell=11832,state=active; !to activate the whole sector
rlstc:cell=02403,chgr=1,state=halted; !para halted in channel group
rxtcp:mo=rxotg-140; !to know the cell number of an RBS

To see the errors in the DIP plot

dtqup:dip=154rbl2&215rbl2;
dtqup:dip=271rbl2;

!Commands to reset the components of the base station

rxbli:mo=rxotg-32,subord,force;
rxese:mo=rxotg-32,subord;
relation:mo=rxotg-32,subord;
rxble:mo=rxotg-32,subord;

!RESEARCH ONLY THE CF

rxbli:mo=rxocf-32,force;
rxese:mo=rxocf-32;
rxesi:mo=rxocf-32;
rxble:mo=rxocf-32;

rxbli:mo=rxoTrx-39-3,SUBORD,force;
rxese:mo=rxoTrx-39-3,SUBORD;
relation:mo=rxoTrx-39-3,SUBORD;
rxble:mo=rxoTrx-39-3,SUBORD;

rxbli:mo=rxorx-75-2,force;
rxese:mo=rxorx-75-2;
relation:mo=rxorx-75-2;
rxble:mo=rxorx-131-3;
rxbli:mo=rxots-71-6-0,force;
rxese:mo=rxots-71-6-0;
relationship:mo=rxots-71-6-0;
rxble:mo=rxots-71-6-0;

To clean the errors in the DIP plot.

dtqsr:dip=271rbl2,ses,sf,es;
dtqsr:dip=271rbl2,ses2,sf,es2;
dtqsr:dip=271rbl2,unacc;
dtqsr:dip=271rbl2,degr;

To block the DIP:

dtbli:dip=204rbl2;
dtese:dip=204rbl2;
dtesi:dip=204rbl2;
dtble:dip=204rbl2;

!To see the Chanel groups

rlstp:cell=02681;

To delete the AP alarms in node 'B':

aploc;
alist
acease 8799:0

To delete AP antivirus alarms on node 'A'

telnet (you type the address of the node where the alarm is)
list
acease 8799:0

!To delete alarms from "Seizure quality supervision" in the MSC:

seqip:r=CONTACTV
seqar:r=CNTCTVO;

!To delete alarms of 'MT FAILED AUTHENTICATION'

MGARP; (To observe all users who are making calls)

To view the radio settings:

rxmop:mo=rxoRx-227-0&&-11;
rxmop:mo=rxotx-83-0&-1&-4&-5&-6&-7&-8&-9;

To delete alarms of 'DISTURBANCE SUPERVISION LIMIT REACHED'

WALL

To test the component blocked with the 'BLE'

rxtei:mo=rxotrx-4-2;

To delete Software Error alarm:

survey
syrip:event=16;------ noprint=all;

To see the 'SYNCHRONOUS DIGITAL PATH UNAVAILABLE STATE FAULT'

tpcop:sdip=10etm2;

To clear the "SIGNALLING FAULT SUPERVISION" alarms

faiap:r=all;
faiar:dev=updr-15098;

!To view the call traffic in the 3 sectors

rlcrp:cell=09753;

!EVENT REPORTING THRESHOLD REACHED

ERESP:ENUM=106;
EREAR:ENUM=106;

!ROUTE RESTRICTION ACTIVATED (TO SEE THE BLOCKED ROUTES IN THE MSC)
blorp

!DISTRIBUTED GROUP SWITCH FAULT

GDSTP:UNIT= XM-B-0-2; STATUS OF THE CARD
GDBLI:UNIT= XM-B-0-2; BLOCK DEVICE
GDTEI:UNIT= XM-B-0-2; TEST DEVICE
GDBLE:UNIT= XM-B-0-2; UNLOCK DEVICE

!SIZE ALTERATION DATA FILES CHANGE REQUIRED

We can see the SAE number, the block, and the quantity
stipulated memory expansion.

TO SEE THE ACTIVE ROUTES IN THE CENTRAL

M3RSP:DEST=ALL;
M3ASP;

To delete alarms from Cell Logical

rlsle:cell=02053,sctype=lu;

CHARGING DESTINATION FAULT

afpfti -f rtrtq rtrdest

!command to see the blocked routes when an alarm appears

(Route Restriction Activated)

blorp;

To view alarms by categories

allip:alcat=ext; We see external alarms.
allip:alcat=apt; we see alarms of physical connections in the nodes.
allip:alcat=apz; we see software alarms.
allip:acl=a1; we see class A1 alarms.
allip:acl=a2; we see class A2 alarms.
we see observation alarms.
we see observation alarms.

!AP Commands
aploc;
hostname
state of the AP, side to which it is connected
active node
cluster node
resource status
nelin cluster connected to the APG, those that say failed are for maintenance
APPLICATION DETECTED SOFTWARE ERROR, SOFTWARE ERROR
syrip:survey; We are looking for the field active = yes, then we take the indicated number in
the event field.

syrip:event=(Event Number),noprint=all; To delete the alarm..

log

syelp; intensity of errors that go through the for loop

===================================================================================
================

ABIS PATH
rxapp:mo=rxotg-#; to see the defined devices associated with the dips.
They must be continuous, 32 for each dip.
they start with the TG number*32+1, always
correlatives, otherwise they must be blocked
rxapi:mo=rxotg-#,dev=rbl2-####&&-####,dcp:##&&##; to integrate the dev
missing
rxapr:mo=rxotg-#,dcp=##&&##, to take out channels of
daughter

===================================================================================
================

Hanging External Alarm

allip:alcat=ext;
allip:alcat=ext,fid=yes;
syfip:fid=H'9a9e;
syfip:fid=H'c383;
dip

===================================================================================
================

AP ANTIVIRUS FUNCTION FAULT = Antivirus Registration Failure:

The alarm is due to the antivirus not being able to register via the web.
CESAR WITH 'ACEASE'
===================================================================================
================

AP Fault Processing Fault:

Alarm related to billing files

AP: Indicates problems in billing transfer

Charging Destination Fault:

Indicates that not all of the package was sent

aploc;

afpls -ls rtrtq check which one was not sent

activate the alarm

status

Delete: Confirm that you sent them and delete them.

===================================================================================
==================
Backup CP or Backup Information Fault:

sybfp:file;
The File(2) is displayed since it is the oldest, the backup rotates to the newest.
current that would be the (0)
It will restart to the default "0".

Command log: These are all the changes made at the center

sybue;
sybup:file;
;
sytuc;
sybui;

plldp;

===================================================================================
=========
BLOCKING SUPERVISION

Check the devices of the routes. It is triggered when we see

problem on some route,
EJS: Blocking Supervision. (We see the UPDR)

dev=updr-(Number of updr); Info of the requested UPDR status.

BLODI:DEV=UPDR-ABCD&&-EFGH; BLOCK DEVICES

ONLY IF THE DEVICES ARE
BLOCK ABL
BLODE:DEV=UPDR-ABCD&&-EFGH; UNLOCK DEVICES

tccfp:r=(route ejs=cc6tmco);

blodi:dev=updr-(num of UPDR); It serves to block a UPRD, for example when it is

inhibited.
exdae:dev=updr-(UPDR number); After the UPDR is blocked, we remove the
supervision.
exdai:dev=updr=(UPDR number); We restart supervision in UPDR
blode:dev=updr=(UPDR number); We unlock the UPDR and review it through
stdep is left idle.

NTBLI:SNT=RTDMA-XXXX; (BLOCKS THE RTDMA or E1)

NTBLE:SNT=RTDMA-XXXX; (UNLOCK THE RTDMA or E1)

===================================================================================
=========

Continuity Check
TCCFP:R=XXRUTAXX; Device was verified with alarm

STDEP:DEV=XXX; The device state was validated that had a continuity alarm
check

BLODI:DEV=XXX; It was manually blocked

EXDAE:DEV=XXX; The continuity check was removed

EXDAI:DEV=XXX The device was activated and put back into service.

TCCCI:DEV=XXX; The continuity check is reactivated (becoming operational)

===================================================================================
=========

CP STATE NOT NORMAL

It is when the CPs are separated, due to commands or work on the same one. There is one.
active and one of redundancy

DPWSP; it is verified in CP, the state of CP is observed

Passive: B (RPH-A)
Asset: A (RPH-B)

It is resolved by performing a system backup...

Alarm print example:

CP STATE
MAU
NRM B WO EX/PWO SB/PWO 1
END
<
===================================================================================
=========

AP Commands
aploc;
hostname
state of the AP, side to which it is connected
prcstate -l active node
cluster node
cluster res resource status
cluster nelin connected to the APG, those that say failed are for maintenance

backup of apg
burbackup -o automatic
m to see where the backup is stored
to give everything it has
cd to go back

cd images cd node #
telnet bscccapg40#
mml

===================================================================================
==========

DISTURBANCE SUPERVISION LIMITS REACHED

It refers to the limit of error counters in particular events in
the BSCVAL exceeded, proceeding
to carry out frontline management by deleting the counters. The alarm ceases, so
which proceeds to close the TT.

DUSUP:ENUM=enum number; FOR ALARM SUPERVISION

TO RAISE:ENUM=106;FOR CESAR THE FAILURE

===================================================================================
=========

DISTRIBUTED GROUP SWITCH FAULT

To verify the component

GDBLI:UNIT= unit; LOCK DEVICE

GDTEI: UNIT = unit; TEST DEVICE

GDBLE:UNIT= unit; UNLOCK DEVICE

Then, it is checked again with the GDSTP command;

===================================================================================
==========

EVENT Reporting
A number of such events were reported that exceeded the thresholds.
established. The printout
this indicates that the ENUM (event reporting number) is 1009 and that
additionally, I exceeded the critical threshold.

There are 3 thresholds: TH, TH1, and TH2, associated with the criticality of the alarm.
in other words,
the same alarm can be presented to them, but with lower criticality, if the report of
events exceed the
value established by the TH. In this case, the number of events exceeded TH2.

By observing in the ALEX, and with the commands eresp:enum=1009 and erepp:enum=1009, it
I observe that
this fault is related to events that report GCP (Gateway) message errors
Control Protocol)
and the command erepp tells you which MGW it is. In this case, it is MGWCC2. Additionally
apply it
command erear:enum=1009 to reset the alarm, and it stopped, but
immediately reappeared.

Subsequently, I accessed this MGW and executed the command lh mesc mesc_counters_gcp 0,
(don't know)
a group of 3 GPB cards defined in each MGW) and I noticed that 2 GPBs (General
Purpose Boards
from MGW contains the error GCP_INSUFFICIENT_BANDWIDTH, which seems to indicate that
for certain GCP messages,
there is not enough bandwidth. Then, request the opening of a CSR to
support.

Ultimately, the case slogan would be: critical threshold of number of errors
detected in the MGWCC2, exceeded.
erepp:enum=1009; verify all registered events 1009

check in which MGW there was packet loss

reset the alarm if there is no impact at the moment
erepe:enum=1009;

erepi:enum=1009;

Search for the destination

Cesar alarm

===================================================================================
=========

SEIZURE QUALITY SUPERVISION indicates that the accountants who receive the duration of
less than 60 seconds of the calls, has exceeded the limit. Does not affect service.

all; affected devices

resetting the counters

===================================================================================
=========

SIZE ALTERATION OF DATA FILES SIZE CHANGE REQUIRED

DBTSP:TAB=SAACTIONS; reflects the problems with the size

!!BLOCKING SUPERVISION!!!!!For blocking problems due to route supervision:

EXROP:R=ALL;.... to verify the characteristics of the routes...and if it is the

SI=ISUP4 (Signalization Indication), the route problem is on the extreme side not
Ericsson
When the SI=SCCP it is because the route is related to the RNC.

STRSP:R="ruta"; status de las rutas

EXPEP:R="route";
STDEP:dev=updr-xxx&&-xxx;
b=all,rc#; rc (route name), output of the routes

!!!!!!!!!!!!!!!!!!!!!!!!!!!!
SYNCHRONOUS DIGITAL PATH SUPERVISION
tpcop:sdip=all; shows all the DIPs connected to which E1, and to which STM1 of the
red

tpstp:sdip=4etm2; shows the status of each E1, WO, manually blocked or not
defined (UNEQ)... if it is 1900, it can be blocked, but if it is 850 it must be
report
Movilnet must inform about each E1 activation for verification.
that it is not manually blocked.

===================================================================================
=========

SIGNALLING FAULT ALARMS FOR DEVICES

Show all devices with supervision problems... starting from 14 they are
devices for expansion....
STRSP:R="ruta";
faiap:r=all; to see the origin of the failure
do it:acl=a2; to cease her

===================================================================================
=========

sctp Network Status Change

It is when the state of a succession changes, the switch to which it is in.

standby, and the central is not sending the request to the MGW when this happens
switcheo. this problem will be resolved
with a load of an IAP 26 for the MSC and 23 for the BSC.

Communication is active but works with redundancy.

There is an impact on the Huawei node.
If the ping is not successful to the remote IP, check:
Connection of the Garp with the Backbone of Mvt.

-------
----------------------------------
TRH EXCEEDED
Rahar;
!!!!!!!!!!!!!!!!!!!!!!!!!!!
SCTP NETWORK STATUS CHANGE

Good afternoon EFO.

Below I attach a basic troubleshooting guide for SIGTRAN alarms, from the
point of view of the MSC-S. The diagnosis includes the following:

Know which network elements have the problem.

2) Verify which IPs are involved in this issue.
3) Perform a ping test from the involved MSC-S to the network element
What is the problem.

At the SIGTRAN level, there are 2 planes (2 VLANs) that interconnect all the
network elements between each other. These are the 520 and the 521. Both the MSC-S and the M-MGw
contain
hosts IP in these 2 plans. You can find them in the following file.
(the file is not complete yet. Once I have it ready, I will send it to you)
update.
I also attach a PowerPoint presentation that graphically contains it.
same as the Excel file.

1) Know which network elements have the problem.

When one of the SIGTRAN interconnection plans fails, the following alarm is
generate in the MSC-S.

O2/APT "MSCMC3_MI221211" 454 090709 2250

SCTP NETWORK STATUS CHANGE

SAID
SCTP1_MGWSFA

RIP
10.23.163.33
It indicates which SAID (SCTP Association ID) is affected (in this case, it is the
of MGWSFA). Then, the RIP (Remote IP Address) is the IP address that the MSC-S sees
fall

2) Verify which IPs are involved in this issue

With the IHALP command, executed as follows, with the affected SAID,
you can see what the IP addresses of the MSC-S (LIP of Local IP's) are
involved
and observe that the RIP of the MGWSFA (in this example) is not active.

IHALP:EPID=ALL; apply it when it occurs in the MGW

<ihalp:said=SCTP1_MGWSFA;
SCTP ASSOCIATION LIST DATA

EPID
SCTP1 IN SERVICE 1024

LIP
10.23.147.6
10.23.147.38

SAID
SCTP1_MGWSFA ASSOCIATE ESTABLISHED 1024 17 PEER

Rest in Peace
10.23.163.1 ACTIVE
10.23.163.33 NOT ACTIVE

We see that the LIP are 10.23.147.6 and 10.23.147.38. These IPs correspond to the
GARP 0 and GARP 1 of the MSC-S in question (each GARP stores an IP host of SIGTRAN).

3) Perform a ping test from the involved MSC-S to the network element.
What is the problem.

Ping tests are performed from each of the GARP to the affected RIP, to
check if there is connectivity. IPPORT indicates from which GARP it will be made
ping.
The syntax would be IP-GARP-2 where GARP is the number of the GARP. In this case, as
It has already been mentioned that they are 0 and 1. Finally, it specifies in quotes which RIP.
It will ping.
Observe the result of the command, and if it says it is not ALIVE, there is a problem.
and a Low criticality TT must be opened. Otherwise, as in the example of
we see that the
The alarm is retained, given that the ping tests were successful.

<ihpri:ipport=ip-0-2,RIP="10.23.163.33";
ORDERED

<

WO MSCMC3_MI22121120A00_V5 AD-150 TIME 090713 1503 PAGE 1

IP PORT PING REQUEST RESULT

IPPORT RIP
10.23.163.33

RESULT
REMOTE IP ADDRESS IS ALIVE

END

WO MSCMC3_MI22121120A00_V5 AD-150 TIME 090713 1503 PAGE 1

<ihpri:ipport=ip-1-2,RIP="10.23.163.33";
ORDERED

<

WO MSCMC3_MI22121120A00_V5 AD-150 TIME 090713 1503 PAGE 1

IP PORT PING REQUEST RESULT

IPPORT
10.23.163.33

RESULT
REMOTE IP ADDRESS IS ALIVE

END

===================================================================================
=============

M3UA ASSOCIATION STATUS CHANGE

ROUTE RESTRICTION ACTIVATED

M3UA DESTINATION INACCESSIBLE

M3RSP:DEST=X-XXXX;
IF SOMETHING APPEARS AS UNAVAILABLE, THE TICKET MUST BE PROCESSED AND ESCALATED TO BACK
OFFICE

===================================================================================
==========

SEIZURE QUALITY SUPERVISION indicates that the accountants who receive the duration of
Less than 60 seconds of calls has exceeded the limit. It does not affect service.

affected routes
Resetting the counters

In MSC:
aploc;
alist
to cease

In BSC:
gdstp;

===================================================================================
=========
Acceptance Tests:
rxasp:mo=rxotg-139;
rxmfp:mo=rxorx-139-0;
rxtcp:mo=rxotg-139;
view adjacent cells to a specific cell
rlcrp:cell=04841; check traffic channels and signaling, indicates
BCCH
rxcdp:mo=rxotg-139; ARFN and TS configuration
cell
04841
04842
rlstc:cell="cell",chgr="chgr",state=active;
rxbli:mo=rxots-139-0-1,force;
rxble:mo=rxots-139-0-0&&-7;
rldep:cell=04841; shows the BSIC
TCH
rlsbp:cell=##; printout of the BCCH of the cell
allip:alcat=ext;

status of the devices

BLOOD
BLODE

rlnrp:cell=cellr=all; to see which are the neighboring cells

===================================================================================
========

OML FAULT
rxbli:mo=rxotg-#,subord,force;
rxese:mo=rxotg-#,subord;
rxesi:mo=rxotg-#,subord;
rxble:mo=rxotg-#,subord;

===================================================================================
=========
BLOCK AND UNBLOCK TRX:
rxbli:mo=rxotrx-83-9,force,subord;
rxese:mo=rxotrx-83-9,subord;
relation:mo=rxotrx-83-9,subord;
rxble:mo=rxotrx-83-9,subord;

_____________________________

BLOCK AND UNBLOCK Time slot:

rxbli:mo=rxots-206-2-5,force;
rxese:mo=rxots-206-2-5;
connection:mo=rxots-206-2-5;
rxble:mo=rxots-206-2-5;

Example note of time slots:

3:20 F/S F/S 1/96 Time Slots GSM El Blanco Maracibo (BSCMBO) / TS Alarms
SYNC FAULT

Impact: 1.04%
3:31 Andres Forero (Back Office Ericsson 0416-608.62.96) is contacted, who indicates
who will attend to the failure and return the call to the COR.

26/09/2010
4:16 Andres Forero(Back Office Ericsson 0416-608.62.96) who indicates that it was resolved
fault, resetting time slot inhibited by error in internal transmission process to
(logical level) of the BTS plot.

8:07: Call the Ericsson Back Office staff Yhanaira Roman, stating that the
the alarm was disabled, a reset was performed on the affected radio, there is no alarm in the
TeMIPClient managers.

COLOR ALARMS

"RP FAULT"/ EYE DEPENDS ON THE NUMBER OF RP ALARMED, THIS IS THE IMPORTANCE OF THIS ALARM,
FOR EXAMPLE, THE RP FAULT, OF RP NRO 27 IS ASSOCIATED WITH A GARP CARD (WHICH
MAEJA TRAFICO), ALTHOUGH
EACH RP IS CONFIGURED WITH A FUNCTION IN THE CENTRAL, THEREFORE IT NEEDS TO BE VERIFIED
WHAT FUNCTION IS PROGRAMMED WITH BACK OFFICE.

check if the alarm is present or held

BLRPI:RP=Nro,FORCED;block
BLRPE:RP=Nro;unlock
allip:alcat=apz;I check if I cut off
exrpp:rp=all; verify the status of all RPs (THEY MUST BE idle)

Below we indicate the steps to follow to diagnose more

exactly the M3UA Destination Inaccessible alarms.
Case 1: MGW Ericsson connected to BSC Ericsson.
Connect to the MSC that is affected by the alarm.
2) In the AP (remember that to enter the AP it is with aploc;) apply the command
tracert "dir_IP_BSC", where dir_ip_BSC is the IP address of the BSC cluster
to which the affected MGW is connected. This command will indicate all the
hops (IP addresses of nodes) that the packet makes to reach from the BSC,
up to the affected MGW.
The previous result will indicate the last hop or node to which the packet reaches.
and indicates where the link failure exists. Please, you are asked to add this
result in the notification email from you to us.
Case 2: MGW Ericsson connected to Huawei BSC.
SAME steps 1 and 2 of case 1, the difference is that the dir_IP_BSC of the tracert command
it will be 1 value above that of the connected MGW. Eg: the IP address of the SFA MGW
It is 10.23.165.1. The IP address of the Huawei BSC of SFA would be 10.23.165.2.
In case the tracert command indicates that the link failure is after
our MGW (in other words, between our MGW and the Huawei BSC), talk to
NOC staff at Huawei to request additional tests with one of their
Engineers.
Finally, for all these alarms, first check with NOC CDMA if they
there are failures in any of these links, at the Back Bone level.

Below I send you a table with the IP addresses of our nodes.

1- 10.24.21.115 BSCCCS Node A
2- 10.24.21.116 BSCCCS Node B
3- 10.24.21.117 BSCCCS Cluster
4- 10.23.37.115 BSCMBO Node A
5- 10.23.37.116 BSCMBO Node B
6- 10.23.37.117 BSCMBO Cluster
7- 10.24.21.1 MGWCCS
8- 10.22.133.1 MGWBTO
9-10.23.37.1 MGWMBO
10-10.23.53.1 MGWSCR
11-10.24.21.3 MSSCCS Node A
12-10.24.21.4 MSSCCS Node B
13-10.24.21.2 MSSCCS Cluster
14-10.22.133.3 MSSBT4 Node A
15-10.22.133.4 MSSBT4 Node B
16-10.22.133.2 MSSBT4 Cluster
17-10.23.133.1 MGWVAL
18-10.23.149.1 MGWMCY
19-10.22.5.1 MGWPTO
20-10.22.21.1 MGWPLM
21-10.23.5.1 MGWVRA
22-10.22.53.1 MGWLCH
23-10.24.5.1 MGWCC2
24-10.22.165.1 MGWACA
25-10.23.133.115 BSCVAL Node A
26-10.23.133.116 BSCVAL Node B
27-10.23.133.117 BSCVAL Cluster
28-10.24.5.115 BSCCC2 Node A
29-10.24.5.116 BSCCC2 Node B
30-10.24.5.117 BSCCC2 Cluster
31-10.23.165.1 MGWSFA
===================================================================================
=========

===================================================================================
===============

* TEST SYSTEM ACTIVATED

This printout is an alarm printout. It indicates that the
Test System is activated.
This observation alarm is given because the system reacts
differently at system restart when the Test System is
activated.

Here is the information on how to verify IP routes.

1st call all signaling destinations.

m3rsp:dest=all;

this command prints all the signaling destinations, locate

the name of the association that fails.

for example, I am going to do it with MGWCCS.

2-4105 STPCCS AVA SCTP1_STPCCS 1 EN-ACT-AVA

SCTP2_STPCCS 1 EN-ACT-AVA
SCTP3_STPCCS
SCTP4_STPCCS 1 EN-ACT-AVA

and then launch

m3asp:said=SCTP1_STPCCS;
M3UA ASSOCIATION STATUS

SAID
SCTP1_STPCCS ACT
END

this informs you of the IP status of the system you are validating
its operation.

_________________________________________________________________________
seqip:r=cc5tmco;

aploc
alist
acease 8799:0
faiap:r=all;
faisp:r=all;
faise:r=PTOCTVO&PTOCTVI,perm;
faiar:r=ptoctvo&ptoctvi;
mgarp:nlog=all;
mgaar;
aploc
alist
acease 8799:0
dtstp:dip=89rbl2;
rxbli:mo=rxotg-102,subord,force;
rxlti:mo=rxots-87-4-0&&-7;
mo=rxotrx-102-0;
rxese:mo=rxotg-102,subord;
rxmsp:mo=rxotg-102,subord;
relationship:mo=rxotg-102,subord;
rxble:mo=rxotg-102,subord;
rxapp:mo=rxotg-67;
dtstp:dip=233rbl2;
strsp:r=sc2tmco;

blodi:dev=updr-6129;

blode:dev=updr-6129;
stdep:dev=updr-4126;
exrop:r=sc2tmco;
allip:acl=a2;
erepp:enum=1009;
m3rsp:dest=3-3;

rxtcp:moty=rxotg,cell=10831;
rlstc:cell=11832,state=halted;
11832
rlstc:cell=11832,chgr=0,state=halted; For Blocking specific CH-Group
rlcrp:cell=10831;
rapti:lch=18292;
rxbli:mo=rxots-18-9-3,force;
rxble:mo=rxots-18-8-7;
rxcdp:mo=rxotg-58;
rldep:cell=xxxxx;
rxtcp:mo=rxotg-123;
rxapp:mo=rxotg-58;

rxbli:mo=rxotrx-tg-Nrotrx,subord,force;
rxese:mo=rxotrx-tg-Nrotrx,subord;
relationship:mo=relation-tg-Norelation,subord;
rxble:mo=rxotrx-tg-Nrotrx,subord;

Forced load
.... for software loading in radios
rldgp:cell=###; sector in which the cell is defined and the frequency band
for which each sector works
Errors in the CF.

rlcrp:cell=04841;
rlstp:cell=01234; to see if we have halted sectors.
rxcdp:mo=rxotg-139;
rlstc:cell=04841,state=halted;
04842
rxbli:mo=rxots-139-0-1,force;
rxble:mo=rxots-139-0-0&&-7;

===================================================================================
=========

Synchronous Digital Path Fault Supervision

tpcop:sdip=(No)etm2; Check in the STM1(ETM2), the No. of DIP Associated to VC212

alarmed.
dip=all
dtbli:dip=(dip)rbl2;block the dip(at the level of the E1 device)
dtble:dip=(dip)rbl2;unlock
dip=(dip)rbl2;
tpbli:sdip=(No)etm2,lp=vc12-(XX); block from VC12 (related to E1 device)
table:sdip=(No)etm2,lp=vc12-(XX);
(No)
tpqup:sdip=(No)etm2; see errors
tpstp:sdip=(No)etm2;
(No)etm2;

Note, if you want to stop the alarm "SYNCHRONOUS DIGITAL PATH FAULT SUPERVISION!"
due to the DIP not being implemented
It must be executed:
dtbli:dip=(dip)rbl2;block the dip(at the level of the E1 device)
tpbli:sdip=(No)etm2,lp=vc12-(XX); block from VC12 (related to device E1)
===================================================================================
=========

M3UA DESTINATION INACCESSIBLE, (In MSC)

m3rsp:dest=all;
m3rsp:dest=(dest);
In MSC:
strdp:r=xxxxxx; Check the devices on the routes. It is triggered when we see a problem.
on some route, EJS: Blocking Supervision.

BLODI:DEV=UPDR-ABCD&&-EFGH; BLOCK DEVICES

ONLY IF THE DEVICES ARE
BLOCK ABL
BLODE:DEV=UPDR-ABCD&&-EFGH; UNLOCK DEVICES

tccfp:r=(route ejs=cc6tmco);
dev=updr-(No updr)

===================================================================================
========

SIZE ALTERATION DATA FILES CHANGE REQUIRED

We can see the SAE number, the block, and the amount.
stipulated memory expansion.

===================================================================================
=========
%%% RP FAULT %%&

BLRPI:RP=175,FORCED;
BLRPE:RP=175;

===================================================================================
=========
SYNCHOROUS DIGITAL PATH SUPERVISION
(Problems with an E1 of a specific STM-1 of the BSC)
SDIP
tpstp:sdip=#etm2;
tpcop:sdip=#etm2;(I VERIFY THE E1s associated with certain STM-1, from the BSC)
take note of the blocked RBL2 (MBL)
dtstp:dip=#diprbl2;
tpbli:sdip=#etm2,lp=vc12-0&&-62;
block all the VC12 included

rxtcp:moty=rxotg,cell=;
indicate the number of tg when we know the Cell ID

RADIO SECTORS
rxmop:mo=rxotg-209;
indicates which sectors the radios belong to
rxmop:mo=rxotrx-209-0;
indicates which sector the radio belongs to

PLOT ERRORS
dtqup:dip=rbl2;
dtqdp:dip=93rbl2;

EXTERNAL ALARMS:
allip:alcat=ext;

STOP SECTORS:
rxtcp:mo=rxotg-;
rlstp:cell=;
rlstc:cell=,state=halted;
rlstc:cell=,state=active;

BLOCK AND UNBLOCK DIP:

dtbli:dip=rbl2;
dtble:dip=rbl2;

DELETE ALARMS (AP FAULT)

aploc;
list
acease 8791:0
mml

BLOCK AND UNBLOCK trx of RBS:

rxbli:mo=rxotrx-83-9,force,subord;
rxese:mo=rxotrx-83-9,subord;
relation:mo=rxotrx-83-9,subord;
rxble:mo=rxotrx-83-9,subord;

DELETE ERRORS IN THE PLOT

dtqsr:dip=all,ses,sf,es;
dtqsr:dip=all,ses2,sf,es2;
dtqsr:dip=all,unacc;
dtqsr:dip=all,degr;

DEVICES ASSIGNED TO THE RADIOS

rxapp:mo=rxotg-;

CELL LOGICAL CHANNEL

rlsle:cell=,sctype=(OL or UL)

CALL TESTS
rxasp:mo=rxotg-;
RXTSP
rlstp:cell=#cellID;
rlstc:cell=#cellID,chgr=#chgr to block
(state=halted)
rlstc:cell=#cellID,state=active;
rlcrp:cell=#cellID;
rapti:lch=31792;

RBS TRAFFIC

RLCRP:CELL= #cell;

CORE ALARMS

MT AUTHENTICATION FAILURE (MSC)

mgarp:nlog=all;
mgaar;

SEIZURE QUALITY SUPERVISION (MSC)

squip:r=all;
seqar:r=#route;

DISTURBANCE SUPERVISION LIMIT REACHED

wall:enum=#;

APPLICATION DETECTED SOFTWARE ERROR

survey
show the active alarms
syrip:log;
show the alarm events
syrip:event=##;
show the event information and delete the alarm
syrip:event=##,noprint=all;
show only the information of the event that was not observed (YES)
syelp
shows the intensity of errors that occur in the for loop

ALARM SIZE ALTERATION DATA FAULT (REQUIREMENT IN MEMORY BLOCK)

dbtsp:tab=saactions;
alarmed memory block number

CHARGING DESTINATION FAULT Y AP FILE PROCESSING FAULT

afpls -ls rtrtq shows which and how many files are held
(FAILED), IF THEY ARE MORE THAN 2 CALL BO (OMAR OR EDUARDO)
release the held file

SIGNALLING FAULT SUPERVISION

faiap:r=all;
faiar:dev=updr-6114;

AUTO-CONFIGURATION OF BOARD NOT POSSIBLE

F/S cards

FAILED AUTOMATIC BACKUP PROCESS

(low)

ALARM EVENT REPORTING THRESHOLD REACHED (Save the Scripts)

erepp:enum=####;
check all registered events ####
eresp:enum=####;
revision
erear:enum=####;
clean counters

SIGNALLING FAULT SUPERVISION

faiap:r=all; to check routes with signal failure associated with this

Alarm, it is advisable to check the route and any Backbone issue.
faiar:r=rutaout&rutain;(resets the supervision alarm for route signaling)

CONTINUITY CHECK FAILURE

tccfp:r=mattmco;
Device with alarm is verified
stdep:dev=###;
The state of the device that was presenting a continuity check alarm is validated.
blodi:dev=###;
Manually block
exdae:dev=###;
Its continuity check (MBL) is removed.
exdai:dev=###;
The device is activated and put back into service.
tccci:dev=###;
Continuity check is activated again (becoming operational)

strdp:r=

BTO 95786;;;Pending scheduled work COR!!!

===================================================================================
=========

===================================================================================
=========

M3RSP:DEST= # REMADDR;

ejm
M3RSP:DEST=3-5;
With this last command, you get the MGW and the Error Code, with this information it is reported to
Back Office

===================================================================================
=========

MT FAILED AUTHENTICATION
MGARP:NLOG=XXXXX or NLOG=ALL;
MGAAR;

===================================================================================
=========

SEIZURE QUALITY SUPERVISION: indicates that the counters that receive the duration of
Less than 60 seconds of the calls has exceeded the limit. It does not affect the service.
affected routes
SEQAR:R=Route node

Review of open numbering

c7gsp:tt=x,np=y,na=z,ns=58426;

sample:
c7gsp:tt=0,np=1,na=4,ns=58426;

===================================================================================
=========

EVENT REPORTING THRESHOLD REACHED

EREPP:ENUM= # ENUM;
ejm
EREPP:ENUM=1009;

allip:alcat=apz;
alcat=apt, alc=a1
erepp:enum=all;
erepe:enum=all;
erepi:enum=all;
eraer:enum=all;
ERESP:ENUM=xxxx;
EREAR:ENUM=xxxx;

M3RSP:DEST= # REMADDR;
ejm
M3RSP:DEST=3-5;

/ \
rc...
ANRSP:RC=+ +[,NOP]; To verify overflow routes...
ALL

===================================================================================
=========

===================================================================================
=========

===================================================================================
=========

M3UA DESTINATION INACCESSIBLE, (In MSC)

m3rsp:dest=all;
m3rsp:dest=(dest);

===================================================================================
=========

AP commands
aploc;
hostname
AP state, side it is connected to
active node
cluster node
cluster resources resource status
cluster nelin connected to the APG, those that say failed are under maintenance

backup of apg
burbackup -o automatic
m to see where the backup is stored
give everything that you have
cd to return

cd images cd node #
telnet bscccapg40#
mml

_________
Switch internal port 0 fault = Fault in SXB card of MGWxxx subrack
This card is the redundancy of the communication that exists between the Main Subrack.
and the Subrack 6 (OETM-Optional Exchange Terminal Module Subrack
0%
When the MO InternalLink Group is at the top, it means that the Main
The subrack can still communicate with the OETM. There is only redundancy impairment.

_______

PDH RNCI in MGWxxx = Degradation in service quality of MGWxxx frame

It reflects a possible degradation of service quality due to frame loss.
traffic, due to connection problems at the remote end, backbone Mvt.
There is no service disruption as traffic remains on the E1s, with quality.
degraded
VOICE COMPONENT

_________

===================================================================================
=========================
ceasing in the MGW and in the remote side optical fiber of the raising all
Maturin out of service

Backbone IP towards PTO, I raise the signaling. The E1s that go from the are observed.
Central point towards Maturin outside, there is a problem on the remote side, that is,
remote node not responding, maturin cdma and gsm F/S.
The communication in Maturin for national long distance and CDMA, the GSM has already lifted.
interruptions of sistran towards the umg of Maturin.

===================================================================================
==========

ROUTE RESTRICTION ACTIVATED

Just as it appears in the ALEX when placing the heading of this alarm in the search engine, the
this is due to a route being blocked administratively. To observe
Which routes are blocked, use the command BLORP;

In MSSMA4, it is an interconnection route between this MSC-S and the MSC-S of LCH that still
this is in the development phase (project):

<BLORP;
BLOCKED ROUTES
ROUTE BLT
LC3BICO 2
END

Similarly, for MSSMC3 it is a connection route between this MSC-S and the
MSC-S of LCH (project):

<BLORP;
BLOCKED ROUTES
ROUTE BLT
LC3BICO 2
END

===================================================================================
=============
CELL LOGICAL CHANNEL AVAILABILITY SUPERVISION

Step to follow for the verification of the alarms

Allip:acl=a1; ! CELL LOGICAL CHANNEL AVAILABILITY SUPERVISION ( BCCH & SDCCH

)!
ALlip:acl=a2; ! CELL LOGICAL CHANNEL AVAILABILITY SUPERVISION (TCH FR)
!
Allip:acl=a3; ! CELL LOGICAL CHANNEL AVAILABILITY SUPERVISION ( TCH Hr )
!

2- Check if the alarms are activated

<rlslp:cell=14441;
CELL SUPERVISION OF LOGICAL CHANNEL AVAILABILITY DATA

CELL
14441 UL

ACTIVE
NO BCCH 1 A1 1
8 A1 16
TCH
TCH
TCH FR 3 14 A2 5
TCH HR 1 28 A3 10
TCH HR 3 28 A3 10
CBCH 0 A3 0

CELL
14441 OL

ACTIVE
YES BCCH 0 A3 0
0
TCH FR 1 16 A2 16
TCH FR 2 16 A2 16
TCH
TCH HR 1 32 A3 32
TCH HR 3 32 A3 32
CBCH 0 A3 0
END

Note: The last column that is in green is the information provided by the headquarters.
the amounts of BCCH & SDCCH and TCH active, these numbers that you have must
match with the LVA, if it is not there, an alarm will be generated the example we have
It is defined for two radios 850 but they are not active, we have a CHGR=halted.
we need to change the supervision of this sector below is sent to you the
What are the alarms A1, A2, and A3?

Supervision is deactivated because it is alarmed and is activated again.

the following command is disabled

rlsle:cell=,sctype=(OL or UL)
and then follow the other steps...

4 parameters of activation of supervision

!SCTYPE UL!
14441
RLSLC:CELL=14441,SCTYPE=UL, LVA=8 ,ACL=a1, CHTYPE=SDCCH;

RLSLC:CELL=14441,SCTYPE=UL,CHTYPE=TCH,CHRATE=FR,SPV=1,LVA=5, ACL=A2;
RLSLC:CELL=14441,SCTYPE=UL,CHTYPE=TCH,CHRATE=FR,SPV=2,LVA=5, ACL=A2;
RLSLC:CELL=14441,SCTYPE=UL,CHTYPE=TCH,CHRATE=FR,SPV=3,LVA=5,ACL=A2;

RLSLC:CELL=14441,SCTYPE=UL,CHTYPE=TCH,CHRATE=HR,SPV=1,LVA=10, ACL=A3;
RLSLC:CELL=14441,SCTYPE=UL,CHTYPE=TCH,CHRATE=HR,SPV=3,LVA=10, ACL=A3;

!SCTYPE OL!

RLSLC:CELL=14441,SCTYPE=Ol,CHTYPE=TCH,CHRATE=fR,SPV=1,LVA=16, ACL=A2;
RLSLC:CELL=14441,SCTYPE=Ol,CHTYPE=TCH,CHRATE=fR,SPV=2,LVA=16, ACL=A2;
RLSLC:CELL=14441,SCTYPE=Ol,CHTYPE=TCH,CHRATE=fR,SPV=3,LVA=16, ACL=A2;

RLSLC:CELL=14441,SCTYPE=Ol,CHTYPE=TCH,CHRATE=hR,SPV=1,LVA=32, ACL=A3;
RLSLC:CELL=14441,SCTYPE=Ol,CHTYPE=TCH,CHRATE=hR,SPV=3,LVA=32, ACL

5- Check if both supervision are activated in case it has 1900 radios

Reactivate supervision, Active must be set to YES, with the following

commands:

RLSLI:CELL=14441,SCTYPE=UL;
RLSLI:CELL=14441,SCTYPE=OL;

Note: It is important that if you reset the alarm, you activate it again with the
command RLSLI
The way to know it is 1900 is when it does not specify that CHTYPE
this in UL( 850 ) and OL (1900).
If the BTS does not have a 1900 radio, the 'CHTYPE' is not defined and does not appear.
nothing under its column

6-Review the changes that were made with the command

RLSLP:CELL=14441;

7- These alarms may appear if there is a transmission problem, if it is not

generating traffic due to call drop in the BTs (at the bottom of the email
it has other specifications).

8- Check again that the changes have been made and activated the
supervision with the command

RLSLP:CELL=14441;
CELL SUPERVISION OF LOGICAL CHANNEL AVAILABILITY DATA

CELL
14441 UL

ACTIVE
YES BCCH 1 A1 1
8 A1 16
TCH FR 1 5 A2 5
TCH FR 2 5 A2 5
TCH
TCH HR 1 10 A3 10
TCH HR 3 10 A3 10
CBCH 0 A3 0

CELL
14441 OL

ACTIVE
YES BCCH 0 A3 0
0
TCH FR 1 16 A2 16
TCH FR 2 16 A2 16
TCH FR 3 16 A2 16
TCH HR 1 32 A3 32
TCH HR 3 32 A3 32
CBCH 0 A3 0
END

In the case of 1900, the BCCH and SDCCH values must be ZERO as they do not have them.
control and signaling channels, these radios are OL depending on the control and
signaling of the 850.(UL)

NOTE: If you have any questions, please contact a BO staff member for assistance.
explain the procedure, verify the type of failure that generates this alarm.
Please remember to activate the alarm again in case it needs to be reset.
because this helps us to verify the functioning and behavior of the
BTS radios and maintain good service to the network.

********************************Bypass PREPAID SERVERS************

***OBSERVING NORMAL STATE RBTOBTO(9MIN3=302) and RBTCCS(9MIN2=301)***

EXROP:R=9MIN3;
EXROP:R=9MIN2;

Activation RBTOBTO(9MIN3=309) and RBTCCS(9MIN2=309)*******

EXRBC:R=9MIN3,BO=309;
EXRBC:R=9MIN2,BO=309;
EXROP:R=9MIN3;
EXROP:R=9MIN2;

Deactivation RBTOBTO(9MIN3=302) and RBTCCS(9MIN2=301)*****

EXRBC:R=9MIN3,BO=302;
EXRBC:R=9MIN2,BO=301;
EXROP:R=9MIN3;
EXROP:R=9MIN2;

!I am sending you a table with the IP Addresses of our nodes.

1- 10.24.21.115 BSCCCS Node A
2- 10.24.21.116 BSCCCS Node B
3- 10.24.21.117 BSCCCS Cluster
4- 10.23.37.115 BSCMBO Node A
5- 10.23.37.116 BSCMBO Node B
6- 10.23.37.117 BSCMBO Cluster
7- 10.24.21.1 MGWCCS
8- 10.22.133.1 MGWBTO
9-10.23.37.1 MGWMBO
10-10.23.53.1 MGWSCR
11-10.24.21.3 MSSCCS Node A
12-10.24.21.4 MSSCCS Node B
13-10.24.21.2 MSSCCS Cluster
14-10.22.133.3 MSSBT4 Node A
15-10.22.133.4 MSSBT4 Node B
16-10.22.133.2 MSSBT4 Cluster
17-10.23.133.1 MGWVAL
18-10.23.149.1 MGWMCY
19-10.22.5.1 MGWPTO
20-10.22.21.1 MGWPLM
21-10.23.5.1 MGWVRA
22-10.22.53.1 MGWLCH
23-10.24.5.1 MGWCC2
24-10.22.165.1 MGWACA
25-10.23.133.115 BSCVAL Node A
26-10.23.133.116 BSCVAL Node B
27-10.23.133.117 BSCVAL Cluster
28-10.24.5.115 BSCCC2 Node A
29-10.24.5.116 BSCCC2 Node B
30-10.24.5.117 BSCCC2 Cluster
31-10.23.165.1 MGWSFA
32- 10.23.149.7 MSSMC3 Node A
33- 10.23.149.8 MSSMC3 Node B
34-10.23.149.6 MSSMC3 Cluster
35-10.23.37.7 MSSMA4 Node A
36-10.23.37.8 MSSMA4 Node B
37-10.23.37.6 MSSMA4 Cluster
38- 10.22.53.7 MSSLC3 Node A
39- 10.22.53.8 MSSLC3 Node B
40- 10.22.53.6 MSSLC3 Cluster
OSS 10.24.21.18
--------------------------

Route Information
TMC..................Roaming CDMA
CTV..................Route to PSTN (CANTV)
PP5..................Service *5
PP21.................Service *21
611..................Service *611
BSC..................Path to BSC

SDIP

TPBLI:SDIP=xETM2,LP=VC12-X; (BLOCK VC12 ASSOCIATED WITH ETM2)

dip=all,state=mbl;
dtble:dip=(dip)rbl2;block
dtbli:dip=(dip)rbl2;unlock
dtdip:dip=(dip)rbl2;
(No)etm2;
tpble:sdip=(No)etm2,lp=vc12-(XX);
tpstp:sdip=(No)etm2;

tpqup:sdip=(No)etm2; Find out....

tpstp:sdip=(No)etm2;
(No)etm2

allip:alcat=ext; We see external alarms.

allip:alcat=apt; we see alarms of physical connections in the nodes.
allip:alcat=apz; we see software alarms.
allip:acl=a1; we see class A1 alarms.
allip:acl=a2; we see alarms of class A2.
we see observation alarms.
we see observation alarms.

M3UA DESTINATION INACCESSIBLE, (In MSC or BSC)

m3rsp:dest=all;
m3rsp:dest=(dest); WITH THIS COMMAND IT IS VERIFIED IF IT IS ACTIVE OR INACTIVE
ELEMENTS
m3asp;

EXAMPLEm3rsp:dest=(dest)

destination=3-4169;
M3UA ROUTING DATA

DEST
3-4169 MSSMC3 AVA SCTP1_STPCCS3 1 EN-ACT-AVA
SCTP2_STPCCS3 1 EN-ACT-AVA
1
1
END

M3UA WITHOUT AFFECTATION

<

RP FAULT

allip:alcat=apz; I check if the alarm is present or held

BLRPI:RP=Nro,FILTERED;block
BLRPE:RP=Nro;unlock
allip:alcat=apz;I verify if I cease
exrpp:rp=all;verify the state of all RPs (THEY MUST BE idle)

General Data:

Steps to open the alarm tool in case of OSS failure:

1) Open the folder in efo called Winfiol

efo/winfiol

and Copy alarms

2) Go to my documents/Winfiol/ChnFiles paste alarms

3) open the alarm tool/shortcut in efo

4) open alarm channels for each of the equipment

Chanel-Open-click on each alarm

Contacts