Nokia MOP - Troubleshoot For Alarm & Measurement Not Available On NetAct, No Ports 60000 or 60001 Listening On SGSN

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 5

MOP - Troubleshoot for alarm & measurement not arriving on NetAct

Product name Confidentiality level


Flexi Network Server
Product version
NS 3.0 & NS15

Method of Procedure
Troubleshoot for alarm & measurement not arriving on NetAct

(no ports 60000 / 60001 listening on SGSN)

NOKIA
All Rights Reserved

Prepared by: Dody Setya Amijaya Date: 14 July 2016

Verification: Date:

Authorization: Date:

1
MOP - Troubleshoot for alarm & measurement not arriving on NetAct

Revises the record


Revision
Date Description Author
edition

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

Fault management (ALARMS) uses NE3S WS protocol. Performance management


(measurements) uses NE3S WS for platform measurements and XML/FTP for
application measurement transfer.

2. Troubleshoot
Execute per sequence, if switchover not success, then try the next steps.

2.1 Switchover module OMU


a. Display current module status
> ZUSI:OMU;

b. Check status of ports on working OMU


Example below, OMU-0 is Working OMU
> ZQRS:OMU,0;

c. Switchover the OMU from to spare to working


Example below, OMU-0 is Working OMU, make it to spare
> ZUSC:OMU,0:SP;

d. Display current module status


> ZUSI:OMU;

e. Check status of ports on working OMU


Example below, OMU-0 is Working OMU
> ZQRS:OMU,0;

3
MOP - Troubleshoot for alarm & measurement not arriving on NetAct

2.2 Restart NE3S SW PRB on module working OMU


a. Display current module status
> ZUSI:OMU;

b. Check status of ports on working OMU


Example below, OMU-0 is Working OMU, check if there;s port 60000 &
60001 exist & the status
> ZQRS:OMU,0;

c. Check status of NE3S PRB


Example below, OMU-0 is Working OMU
> ZDDS, OMU,0;
0000-MAN> ZSXP:NE3

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

d. Restart NE3S PRB


Example below, OMU-0 is Working OMU, use the ID shown on check status
command on point c.
> ZDDS, OMU,0;
0000-MAN> ZOKR:9C2

e. Check status of ports on working OMU again


Example below, OMU-0 is Working OMU, check if there;s port 60000 &
60001 exist & the status of this port.
> ZQRS:OMU,0;

4
MOP - Troubleshoot for alarm & measurement not arriving on NetAct

2.3 Restart module working OMU (last step if


switchover OMU & restart NE3 PRB not
successfully clear the issue)
a. Display current module status
> ZUSI:OMU;

b. Check status of ports on working OMU


Example below, OMU-0 is Working OMU
> ZQRS:OMU,0;

c. Switchover the OMU from to spare to working


Example below, OMU-0 is Working OMU, restart the working OMU. No
impact to service, need to do re-login after restart.
> ZUSU:OMU,0:C=DSK;

d. Display current module status


> ZUSI:OMU;

e. Check status of ports on working OMU


Example below, OMU-0 is Working OMU
> ZQRS:OMU,0;

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;

You might also like