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>

Reminder

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

upgrade

Service Interconnection Fails Between the OI2D Board of the OptiX Metro 1000 V3 and the SLO1 Board of the OptiX OSN 3500

Publication Date:  2012-07-25 Views:  49 Downloads:  0
Issue Description
A batch of the OptiX Metro 1000 V3 are added in a local network. Each is connected through the OI2D board integrated in the SCC board to the SL01 board of the OptiX OSN 3500. The hardware version of the OptiX Metro 1000 is 49SCB, and the SCC board version of the OptiX Metro 1000 is 5.37.5.12. The SCC board version of the OptiX OSN 3500 is 5.21.16.13. The equipment commissioning results show that services are unavailable on the Metro 1000. After the services are configured, the corresponding port on the SLO1 board of the OptiX OSN 3500 reports the AU-LOP alarm whereas the Metro 1000 reports plenty of high-order and low-order path far-end unavailable second (UAS) events. 
Alarm Information
AU-LOP 
Handling Process
Emergency measures:
Issue the following two commands from the Navigator to the OptiX Metro 1000 V3 (49SCB) to restore the services (the services are interrupted again if the NE is powered off, and thus you need to issue these two commands again after the NE is powered off):
:optp:5,0,b1,1,11,12,e1,00,00,40,c2,b8,40,ff,ff,5a,10,01,00
:optp:5,0,b1,1,11,12,e1,00,00,c0,c2,b8,40,ff,ff,5a,10,01,00
To thoroughly solve the problem, upgrade the hot patch of version 5.37.05.12 or upgrade the NE software of the OptiX Metro 1000 V3 (49SCB) to 5.37.06.12. 
 
Root Cause
The service interconnection fails for a batch of equipment. Therefore, the equipment is not faulty. Check the configuration data of the equipment. The configuration data is correct. Then collect the relevant information and return the information to the headquarters for further analysis.
The analysis results are as follows: The AU pointer is composed of H1YYH2FF. In general, Huawei equipment detects only the last ten bits of the H1H2 bytes to determine whether to report an AU_LOP alarm. Some other equipment, such as the SLO1 board of the OptiX OSN 3500, exists in the network and also checks the correctness of the YY byte in addition to checking the last ten bits of the H1H2 bytes. If the YY byte is abnormal (not equal to 0x9B), the equipment reports an AU_LOP alarm.
The NE software (version 5.37.05.12) of the OptiX Metro 1000 V3 (49SCB) uses the default termination mode of the SD8901 chip to transparently transmit the YY byte. The YY byte regenerated by the SD8901 chip is 0x00 (not equal to 0x9B). Therefore, the YY byte in the AU pointer cannot be correctly and transparently transmitted to the downstream equipment. When checking the received YY byte, the downstream equipment detects that the YY byte is abnormal and thus reports an AU_LOP alarm and inserts an AIS alarm. Then the services are interrupted.
Therefore, if the OI2D board integrated in the SCC board of the OptiX Metro 1000 V3 (49SCB) is interconnected with the SLO1 board of the OptiX OSN 3500, the service interconnection fails. 
 
Suggestions
Null

END