No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Port status of EOS board displayed on U2000 mismatch the actual status due to collaboration exception of SCC and NMS

Publication Date:  2012-07-25 Views:  193 Downloads:  0

Issue Description

Customer found the operation status and service of EOS board are ok, but operational status of all Ethernet ports on the U2000 were showing Out Of Service (OOS) even though they were in service. We need to find out why a working port is showing OOS-AUMA instead of IS-NR?

NE:OSN 7500
SCC version:
Board version:SSN2 EGS2 5.50,SSN2 EFS4 1.17
NMS version:U2000 V1R2C01SPC100

Alarm Information


Handling Process

Workaround method:upgrade to the V2R9 or later version, or use T2000 to manage NEs.

Final solution:experts on NMS modify the codes to solve this issue.

Root Cause

V2R8 is a mainstream version, it is steady, it is not possible to break out so many problems at the same time, It is confirmed by R&D that it is not a known issue, we suspect it may be an error caused by NMS.

1. Firstly, we run the EGS2 data collector script on navigator, feedback the result to R&D , after

analyzing it, they found there was no problem in the board.

2. Secondly, ask the experts on NMS to confirm it, they explained the port status displayed on NMS is according to the query result of SCC, so we need go for SCC experts for deepen analysis.

3. We can use “cfg-get-stam” command to query the port status on navigator, for example,

1 29 1 1 1 1 0
Total records :1
Focus on the “ADMIN,AU and LPBK” section, the result could only be 0 and 1 for each section, in this example, SCC would send the 110 to NMS, there are 8 kinds of combination, we define the combination of 110 as “IS-NR” in version V2R8 ,but the NMS display “OOS-AUMA”, so this problem was caused by the collaboration exception of SCC and NMS.

4. Through checking over all the version of MSTP,MSTP+ and DWDM , we get a conclusion as following:

(1) All versions of MSTP+ and NGSDH R8C02 , partly versions of DWDM are consistent with T2000,but opposite with the interface documents.

(2) NGSDH R9 and later version are consistent with U2000, consistent with the interface documents

So this problem was caused by the collaboration exception of SCC and NMS.


See also case in chinese:SC0000678439