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

Reminder

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

upgrade
Knowledge Base

Why LQM2 boards don't report to OSS all crossconnection correctly with ANY configuration

Publication Date:  2012-07-25  |   Views:  142  |   Downloads:  0  |   Author:  Edmond  |   Document ID:  EKB0000548898

Contents

Issue Description

There are not cross-connections were found on port 202 on the lqm2 board in slot 5 of ne ldci.-now80lh1800-1 when the getallcrossconnections cobba interface was used to query cross-connection data. however, cross-connections were found on the u2000 client.
layer rate 104 (lr_och_data_unit_1) was not found on port 202 on the lqm2 board in slot 5 of ne ldci.-now80lh1800-1 when the getallsupportedptps cobba interface was used to query port information.
U2000 Version;u2000 v100r001c00 spc003.

Alarm Information

NBI can not get cross-connections and layer rate from U2000.

Handling Process

Check the "wdm service managerment" to confirm whether can get wdm cross-connection configuration for 202  port.
result: u2000 has report  the cross-connection configuration but there are two bidirectional corss-connection,
one is for 5-lqm2-202(lp2/lp2)-1, the other is for 5-lqm2-202(lp2/lp2)-2.
according to the original lqm2 mode, the channel "2" is a hidden channel, that is lqm2 current woking
mode is 2lqm
as a result, odu-1 rate layer 104 and relevant client cross-connections for port 202 on the lqm2 board
were not found.
This is a bug of U2000 which the version is earlier than v100r001cp0302 which  the lqm2 board is set to the 2lqm mode.
The U2000V1R1C00CP0311 has solve the problem.

Root Cause

1. U2000 self has not cross-connection.
2. The cross-connection is not correct.
3. U2000 report the cross-conection information successful but NBI interface report fail.
4. NBI report information successful but OSS fail to recive it due to wrong configuration in OSS.

Check the "WDM Service Managerment" to confirm whether can get WDM Cross-Connection Configuration for 202  port.
Result: U2000 has report  the cross-connection configuration but there are two bidirectional corss-connection,
one is for 5-LQM2-202(LP2/LP2)-1, The other is for 5-lqm2-202(lp2/lp2)-2.
According to the original LQM2 mode, the channel "2" is a hidden channel, That is LQM2 current woking
mode is 2LQM
as a result, odu-1 rate layer 104 and relevant client cross-connections for port 202 on the lqm2 board
were not found.

Suggestions

 1. For NBI issue, we must locate which section that the problem generate.
 2. Once we meet this interface issue of board information, We need learning how the board work in different applications.