Professional Documents
Culture Documents
Nokia MOP - Troubleshoot For Alarm & Measurement Not Available On NetAct, No Ports 60000 or 60001 Listening On SGSN
Nokia MOP - Troubleshoot For Alarm & Measurement Not Available On NetAct, No Ports 60000 or 60001 Listening On SGSN
Nokia MOP - Troubleshoot For Alarm & Measurement Not Available On NetAct, No Ports 60000 or 60001 Listening On SGSN
Method of Procedure
Troubleshoot for alarm & measurement not arriving on NetAct
NOKIA
All Rights Reserved
Verification: Date:
Authorization: Date:
1
MOP - Troubleshoot for alarm & measurement not arriving on NetAct
2
MOP - Troubleshoot for alarm & measurement not arriving on NetAct
1. Purpose
The MOP is utilized to check & troubleshoot issue related with alarm &
measurement not arrived on NetAct. Normally there will be port 60000 & 60001
open on OMU SGSN to communicate with netact.
<ZQRS:OMU,<working index>;
tcp4 0 0 *.60001 *.* LISTEN
tcp4 0 0 *.60000 *.* LISTEN
2. Troubleshoot
Execute per sequence, if switchover not success, then try the next steps.
3
MOP - Troubleshoot for alarm & measurement not arriving on NetAct
Sample output, take note of the ID, usually NE3S have ID 9C2:
ID NAME LDT ATTR BP MP SI HGC MQ EH IS LP HP
9C2 NE3SAG 3718 (G1763) 1007 31 50 0014 0003 FFFF 01 00 50 50
HGR:0001 PRC:00C8 0FFF 50 50
HGR:0002 PRC:0001 0FFF 50 50
HGR:0003 PRC:0001 0FFF 50 50
4
MOP - Troubleshoot for alarm & measurement not arriving on NetAct
3. Fallback Procedure
a. Put the module status back as before
Example below, OMU-0 is initially Working OMU, now OMU-1 is working.
Make it to spare
> ZUSC:OMU,1:SP;