O&M Activities
Table of contents
1. Synchron
2. C7 Disturbance
3. ISUP Monitoring
4. IO Maintenance function Node alarm retrieve
5. Charging
6. SAE=36 Treshold Supervision
7. DIP Supervision
8. Lucent BCF
9. STS
10. HLR
11. Pre-paid
12. Emergency area
13. Forign subscriber roaming in the network
14. Hivas felepites
15. Software error
16. Roaming problem
17. CP
18. TRLOG searching
19. IO Maintenance
20. C7 Measurement
21. SAE for Historical supervision
22. ET155
Synchron related commands:
         1. NSSTP;
         2. NSDAP;
         Network synchronization initiate:
         1. NSMDC - Synchronization node
         2. NSCOI
         3. NSDAC
         4. NSMAI
         Nework synchronization change:
         1. NSDAT
         2. NSDAC
         3. NSMAI
         Nework synchronization fault:
         1. NSBLI
         2. NSSTEI
         3. NSFMI
         4. NSBLE
IO Maintenance Function Node alarm retrieve
1. IMMCT:SPG=0 or 1;
2. IMALP:NODE=A or B;
3. END;
OBJTYPE:
HS7SL1:       SAE=163
NBRMSCLST:    SAE=274, MGNMP:MSC=ALL
MSC: SAE=274, MGCVP:VLR=ALL
TRAFFDEST:    SAE=5
LOSSROUTE:    SAE=504
DIP :         SAE=515
EOS:         SAE=9
C7SL1&2 :     SAE=163
COPRVLRST:    SAE=448
LOCAREAST:    SAE=285
Object type modification related to SAE value
1. IMLCT:SPG=0 or 1;
2. SDDOP:OBJTYPE=…,AREA=OPER;
3. SDDOI;
4. SDDOC:OBJTYPE=…,NOBJ=X;
5. SDDOE:EXEC;
6. SDDTI;
7. SDDCI;
8. END;
SAE value settings and Objtype modification
ISUP Monitoring
1. UPMTI:DEV=(IDLE device on the route)
2. TCTDI:BNB=….,DEV=…..;
3. UPMTP:USER=ALL;
4. UPMTE:DEV=…..;
Charging
1. CHOFP:FN=ALL;
2. SAAEP:SAE=500,BLOCK=CHOF;
TT file transfer slow in the MSC. Steps according to this problem
-TT subfile transfer
1. IOBLI:NP= BGW PORT;
2. INFDP;
2. INFSP:FILE=TTFILE00,DEST=…;
2. Check the subfiles (look for subfile transfer failure- this subf. was not transferred to BGW)
3. Dumping from that subfile which was not transferred
4. INFUE:DEST=…,FILE=TTFILE00-XXXX; (azok a szabfajlok amiket az OD -re masoltunk)
5. IOBLE:NP= BGW PORT;
Treshold supervision , SAE=36
1. AFTSP:TEST=110,SAE=36;
2. AFTSS:TEST=110,SAE=36,LIM1=0; Supervision temporary blocking
Subscriber related store data for visiting mobile subscriber
VLR kapacitas pl: 260000 es most 247000 van regisztralva.
Ezert jon az alarm.
SAE=36 NI=2600(*100)=> 260000 a kapacitas
NIU=156(*100)=> 15600 van regisztralva
MGSVP-> number of currently registered and the number of attached from each HLR
A diferencia a kikapcsolt elofizetok szama.
DIP Supervision:
Quality Supervision:
1. DTQSP
ES-    Errored second
SES- Severely errored second
SESL- Severely error second unac. Performance level 0-900
RESL- Errored second unacceptable perf. Level 0-1000
RSESL- Severely errored second unac. Perf.
ESL- Errored second, unac. Perf. Level 0-200
Digital Path Transmission Function Quality
1. DTQUP
UASB2- Present number of unavailable seconds in time interval T2 bidirectional
ESVR- Present number of errored seconds for the unacceptable perf. Level/ Outgoing direction
ES2VR- Present number of errored seconds for the degraded performance level T2/ Outgoing direction
Digital Path Historical Storage Quality
1. DTQDP
ES-      Errored second incoming direction
SES- Severely errored second incoming direction
ESR- Errored second outgoing direction
going direction
STS
Too many STS subfiles:
1. INFUP:FILE=X; - Destination
2. INFIP:FILE=X; and INFSP:FILE=X,DEST=Y;
Ami az INFSP-ben lathato azt NEM szabad torolni!!!
A tobbit, ki lehet torolni
3. INFIR:FILE=X;
Statistic
RPTID=104 - C7 linkset
RPTID=113 - C7SLI
RPTID=106 - Traffic dispersion
RPTID=125 - Traffic route
RPTID=123 - BSC statistic
IMLCT:SPG=0;
SDTDP:RPTID=X,INT=15;
END;
HLR
HLR Capacity
1. SAAEP:SAE=261;
NI=max capacity
NIU=current capacity
2. SAAEP:SAE=501,BLOCK=ASD;
IMSI connected to authentication
NIU=X(*4) - connected
Helyi elofizetok szama mas halozaton vagy a sajat halozatban
1. HGSLP;
Lazy commands
NTSTP:SNT=ET155-0;          SNT STATE
NTCOP:SNT=ET155-0;          SNT DEFINITION
TPSTP:SDIP=0ET155;          SDIP STATE
TPCOP:SDIP=0ET155;          SDIP DEFINITION
PWESP:SNT=ET155-0;          EQUIPMENT PROTECTION STATE
PWNSP:SDIP=0ET155;          NETWORK PROTECTION STATE
PWEPE:SNT=ET155-0;       EQUPIMENT PROTECTION END
PWEPI:SNT=ET155-0,SUBSNT=subsnt,[LOCK]   EQUIPMENT PROTECTION INITIATE
PWFSE:SDIP=0ET155;                   FORCED NETWORK SWITCH END
PWFSI:SDIP=0ET155,MS=ms;             FORCED NETWORK SWITCH INITIATE - LOCK TRAFFIC TO MS
PWMSI:SDIP=0ET155,MS=ms;             MANUAL SWITCH INITIATE
NTDCP:SNT=ET155-0,SUBSNT=subsnt;     DYNAMIC CONNECTION DATA
HOT (MS-0)
                 TSM-A-16            TSM-A-17           TSM-A-18           TSM-A-19
                 TSM-B-16            TSM-B-17           TSM-B-18           TSM-B-19
        LOT (SUBSNT-1)      LOT (SUBSNT-2)      LOT (SUBSNT-3)     LOT (SUBSNT-4)
NETWORK SYNCHRON CABLE
LOCK TRAFFIC TO MS
          ET155-0
                               HOT (MS-1)
          LOT (SUBSNT-5)
                     Redindance cable a TS4B( tetejen- A side)
          Redundance cable a TS4B (tetejen- B side)
SAE- 500 UPD
   500 UPHID !!!!
   515 UPDIP
   529 UPET
SAE- 500 DIPH155!!!
C7 TRAFFIC MEASUREMENT
Lazy commands:
C7TPP:MP=ALL; (MP PRINT)
C7TRP:TRG=ALL; (TRG PRINT)
TRTSP:MP=X; (CHECK RECORDING)
TRIDP:ALL; (CHECK FREE MP)
Define traffic measurement:
C7TRI:TRG=X,LS=ls,SLC=slc;
C7TPI:MP=mp,TRG=trg,IO=OWN;            (IO can be file, own IO terminal or an alpha numeric file)
C7TPI:MP=mp,TRG=trg,IO=FILE;           (TRIDP:ALL; free MP)
C7TPI:MP=mp,TRG=trg,IO=AF-1;
IOAFP:IO1=AF-1; (CHECK WHICH FILE IS USED)
IOFAT:FILE=file; (CHECK THE CONTENT)
TRTSI:MP=mp,NRP=24,RPL=60,DATE=020906,TIME=0000,NDAYS=365;
(MEASUREMENT FOR A YEAR, 24 HOURS)
TRTSI:MP=mp,NRP=1,RPL=30,DATE=date,TIME=time;
(MEASUREMENT once, duration 30 min, start date & start time)
TRTSE:MP=mp;      (STOP MEASUREMENT)
TRTSE:MP=mp,MPE; (DISCONNECT MP)
numeric file)
TRLOG search
IMLCT:SPG=0;
MCSAP:FILE=TRLOGFILE,IO1=(IO/ALL),SDATE=X,STIME=X,EDATE=X,ETIME=X;
END;
Software error
1. SYRIP:SURVEY;
Restart information - CODE (In Alex)
INFO1--> Block number
2. LASLP:BN=X;
3. PCORP:BLOCK=X;
4. SYRIP:EVENT=event,FORM=LARGE;
Investigation of roaming problem
1. Using C7 Event reports
Use command C7GSP in any of the HLR's or the MSC's.
C7ERP:ENUM=131&208;
<C7ERP:ENUM=131&208;
CCITT7 EVENT REPORTING RESULT
ENUM HEADER                                                        BLOCK        DATE
131  UDTS OR XUDTS RECEIVED                                        C7SRM        20327
NI         OPC        CAUSE      MSGTYPE SSN                       TT           NP
2          1220       1          UDTS      8                       0            1
NS1         NS2       NS3        GTIND
4479009     72407
ENUM HEADER                                                        BLOCK        DATE
208 OPERATION TIMEOUT CLASS 1                                      C7TCP        20327
TIMRES     TIMDUR     SPC        SSN         AI                    TT           NP
1          15                    6           18                    0            7
NS1        NS2        NS3        NI          OPCODE1               OPCODE2 LSSN
8613862    2320164    2                                            56      7
(a) ENUM131
1. Check DATE & TIME fields matche with the current timing, where
   DATE:YYMMDD (Y:year M:month D:day)
   TIME :HHMMSSMS (H:hour M:minutes S:seconds MS:milli seconds)
2. Check from field NS1 which country code is it Refer to Appendix A
3. Verify the message originator by checking which network signalling point code in the
   fields NI and OPC by using command C7SPP
C7SPP:SP=NI-OPC;
<C7SPP:SP=2-1220;
CCITT7 SIGNALLING POINT DATA
SP         SPPID
2-1033     OWNSP HLR3
2-1220     RIN2
4. Check the existing international routing in our MSC's by using command C7GSP
C7GSP:TT=0, NP=1, NA=4, NS=CC;                  (CC is the country code)
Then get GTRC from the printout and check the GTRC routing by command C7GCP
C7GCP:GTRC=gtrc;
<C7GSP:TT=0,NP=1,NA=4,NS=44;
CCITT7 GLOBAL TITLE SERIES DATA
OPERATING
TT         NP          NA         NS                     GTRC
0          1           4          44                     158
<C7GSP:GTRC=158;
CCITT7 GLOBAL TITLE ROUTING CASE DATA
OPERATING
GTRC       PSP         PTERM      PINTER      PSSN       SSP         STERM        SINTER
158        2-1220      NO         YES                    2-1221      NO           YES
5. Check the subsystem number from field SSN use Appendix C
6. The finally check the Cause of the problem by checking the value of the field CAUSE use Appendix B
Explanation:
This means that we sent an SCCP message to subsystem SSN with global title address
NS1 and NS2. But we received back a message from OPC indicating a failure with reason CAUSE
Open a trouble ticket for the department responsible for node indicated by the signalling point
(b) ENUM 208
1. Check the DATE and TIME fileds matche with the current timing where
   DATE:YYMMDD
   TIME: HHMMSSMS
2. Check from field NS1 which country is it refer to Appendix A
3. Check local subsystem number from field LSSN and the destination subsystem number SSN
   use Appendix C
4. Check what was the operation from the field OPCODE2 use Appendix D
Explanation:
This means that our local node susbsystem LSSN tried to send an SCCP message related to
operation OPCODE2 to destination subsystem SSN with global title address NS1 and NS2.
This operation failed due to timeout so we did not receive any reply to our message.
Check with Gateways support is the signalling links to the destination country are working or not
and inform them about the received errors.
Appendix B - Return Cause for UDTS or XUDT
Value      HEX value              Reason
0          OOOOOOOO               No translation for an address of such nature
1          OOOOOOO1               No translation for this specific address
2          OOOOOO10               Subsystem congestion
3          OOOOOO11               Subsystem failure
4          OOOOO1OO               Unequipped user
5          OOOOO1O1               MTP failure
6          OOOOO11O               Network congestion
7          OOOOO111               Unqualified
8          OOOO1OOO               Error in message transport(only XUDTS)
9          OOOO1OO1               Error in local processing(only XUDTS)
10         OOOO1O1O               Destination can not perform reassambly (only XUDTS)
11         OOOO1O11               SCCP failure
12         OOOO11OO               Hop counter violation
13         OOOO11O1
              TO                  Spare
           11111111
Appendix C - Subsystem Description
SSN        Description
0          All SSN
1          SCCP Management
2          SSF
4          OMAP
6          HLR
7          VLR
8          MSC-GMSC
10         AUC
128      HLR
146      SCF
222      FNR
224      HLR-RED
251      SSF
252      SCF
253      FNR
254      BSC
Appendix D - MAP Operations' codes Discription
OPCODE   MAP Operation
2        Update Location
3        Cancel Location
4        ProvideRoamingNumber
7        InsertSubscriberData
8        Delete Subscriber Data
9        SendParameters
10       Register Supplementary Service
11       Erase Supplementary Service
12       Activate Supplementary Service
13       Deactivate Supplementary Service
14       Interrogate Supplementary Service
17       Register Password
18       Get Password
19       Process Unstructured SS Data
21       Process Access Signalling
22       Send Routing Information
28       Perform Handover
37       Reset
38       Forward Check SS Indication
43       Check IMEI
45       Send Routing Information for Short Message
46       Forward Short Message
47       ReportSM Delivery Status
50       Activate Trace Mode
51       Deactivate Trace Mode
54       Begin Subscriber Activity
55       Send Identification
56       Send Authentication Info
57       Restore Data
59       Process Unstructured SS Request
60       Unscructured SS Request
61       Unscructured SS Notify
63       Inform Service Centre
64       Alert Service Centre
66       Ready for Short Message
67       Purge MS
68       Prepare Handover
TIME
91629300
NA
4
TIME
85820600
NA
4
            SSSN      LSH
                      YES
AUSE use Appendix B
h reason CAUSE
nalling point OPC
number SSN
working or not
Hivas felepites                                              2
                                                       HLR
                             4 MSRN
                                          IMSI
PSTN                           5          IMSI                   MSRN
PLMN                GMSC
                        1      MSRN
                                                       MSC        MGRSP
                                                   6             IMSI-->MSRN
                                                       MTE(MSRN)
1. Pre analysis     2. HLR --> where is the subscriber           3. IMSI-->MSRN   4. BO=8 EXROP:R=0G
B tabla analysis
RC --> GRI route
5. MSC - Ha az MSRN idetartozik akkor MTE.             6. MSRN MTE
Ha nem akkor RC a masik MSC fele.
4. BO=8 EXROP:R=0GRI3;
Pre-paid
Pre-paid call
BO=20
OICK=10 - Each pre-paid subs. has this parameter.
ANBSP:B=20-0(OICK=10)(SZAM); Modified
ANBSP:B=310-(SZAM); RC
ANRSP:RC=X;
EXROP:DETY=MIN;
EA
1. MGCEP:CELL=ALL;
2. ANBSP:B=89-0(EA);
Forign subscriber connected to our network
1. MGTRP:MSISDN=X; (In one of the MSC)
2. MGSLP:IMSI=X; (Subscriber profile- services)
3. MGSSP:IMSI=X;
4. MGSRE:IMSI=X; (VLR Reset)
CP fault
1. DIRCP;
2. DPHIP; - Check HW before the intervention
3. DIRRP:RP=X;
Lucent BCF/ nincsen hivas a BSC-bol
1. Test system;
2. PRINT VAR MRRM 363;
H'16B=H'000A - Ez a jo beallitas
Ha nem akkor SET VAR
3. SET VAR MRRM 363=10;
END TEST;
IMLCT:SPG=0;
SDTDP:RPTID=104,INT=15; - C7 link check towards BSC
END;
IO Maintenance
IMLCT:SPG=0;
ILROP:ROT=ALL;
ILNPP:PORT=1-1-3-1;
MCDVP;
ILDAP:ODA=ALL;
ILRCP:RC=ALL;
ILDNP:DEST=ALL;
ILIRP:IPADDR=ALL;
ILNAP:NAME=ALL;
ILPCP;
END;
C7 Disturbance
1. UPDSP
2. UPDBP
C7 Disturbance alarm handling
1. UPDBP
2. UPDRI:SP=X,SI=ISUP4,DTYPE=3&&5&7&&11; - Initiate dist. Measuremnt
3. Wait 5 minutes
4. UPDBP
5. If faultless than UPDSE:SP=X,SI=ISUP4;
6. UPDSI:SP=X,THR=20,SI=ISUP4,DTYPE=3&&5&7&&11;
7. UPDRE:SP=X,SI=ISUP4;