OptiX NG WDM Product Maintenance Case Collection 2010-2011

2011

1 Cannot create OCh trail between ND2 boardsError! Bookmark not defined. 2 Configuring the Maximum Packet Size of the LBF Board Fails in the Case of 10 Gbps LAN Services ....Error! Bookmark not defined. 3 SCC board is busy for long time caused report HDLC_FAIL alarm on all the boardError! Bookmark not defined. 1 4 The LINK_ERR Alarm Is Reported Because an Optical Module on the TQX Board Is Faulty.Error! Bookmark not defined. 5 The SSE5OAUC01C Board Reports an IN-POWER-LOW Alarm When the Optical Power Is Normal or High....Error! Bookmark not defined.

Cannot create OCh trail between ND2 boards

OCh creation problem Fiber connection

Fault Type:

Optical Layer Grooming

Keywords:

error Wavelengths at the source and sink of a fiber are mismatched Error code: 1091674142

For X customer, we are implementing a metropolitan NG WDM network with OSN8800 and OSN6800 equipment. We are currently using U2000 V100R003 Phenomenon Description: version When we tried to create the OCh trail, using the WDM trail option in the U20 00 menu, the following message appears: "Fiber connection error. Wavelengths at the source and sink of a fiber are m ismatched. Error code: 1091674142". The equipment doesn't show alarms that could affect the service. We only had this message error, after analyze route: Alarm Information: "Fiber connection error. Wavelengths at the source and sink of a fiber are mismatched. Error code: 1091674142".

The equipment had board optical cross-connections, previously configured in WSM9, or WSMD4 boards. These cross-connections caused conflict with thos Cause Analysis: e created by the trail.

Handling Process:

1.Check the physical route and physical connections of the lambda route. It was OK. 2.Check the logical connections in U2000. It was OK. 3.Check the board optical cross-connection, in the end stations of the OCh t rail: 4.Deactivate and delete all board optical cross-connections in both sides: 5.Try to create the Och trail again, using the WDM trail creation function of U 2000: This time the OCh trail could be created within problems.

Suggestions In this case we could delete all the optical board cross-connections only, be and Summary: -: OCh trail .. U2000
Page 1 of 8

cause the network is on deployment stage.

Configuring the Maximum Packet Size of the LBF Board Fails in the Case of 10 Gbps LAN Services

Fault Type:

Other_Unit

Keywords:

LBF maximum packet size

When the E3LBFS board is configured through the WDM Configuration menu Phenomenon Description: on the iManager T2000, the maximum packet size cannot be configured when 10 Gbit/s LAN services are selected. The default maximum packet size is 1518 bytes.

Null. Alarm Information:

Cause Analysis:

The board does not support configuration of the maximum packet size.

Handling Process:

Consult the relevant experts and obtain the following information: 1. The E2LBF board supports framing mode and transparent transmission mode. When the framing mode is used, the maximum packet size is always 9600 bytes. When the transparent transmission mode is used, the maximum packet size parameter is unavailable. 2. For services at the customer side, the E2LBF board supports transparent transmission mode only. The maximum packet size is unavailable. The E2LBF board transmits the packets sent from the customer side, regardless of the packet size.

Suggestions and Summary:

Though the maximum packet size (1518 bytes) of the E3LBF board is meaningless and brings no influence on services, it might cause misunderstanding of customers. It is recommended that the query of the maximum packet size be canceled in later versions.

-: E3LBFS 1518 . .
Page 2 of 8

Page 3 of 8

SCC board is busy for long time caused report HDLC_FAIL alarm on all the board
System control

Fault Type:

& communication unit

Keywords:

HDLC_FAIL

HDLC_FAIL alarm report frequently at the same time on all the board Phenomenon No traffic effected Description: Please check the attached file

HDLC_FAIL alarm appears on all boards. Alarm meanings Indicates that the emergency channel communication fails, and the SCC reports the alarm. Versions from 5.10.02.20, the SCC starts to support th e alarm. Alarm Information: Alarm Parameter The first parameter is the board number, it indicates the communication between which board and SCC fails. The second parameter is the modul e number; it indicates the module which fails in communication through HDLC.

These HDLC_FAIL alarms report frequently, 1- If one board report this alarm, others will also report because there is only o ne 485 bus, 2- If only the SCC board report HDLC_FAIL, other boards can't detect it, so it w as related to the SCC board 3-if SCC board spend long time to handle other task,(such as backup NE datab Cause Analysis: ase) and have no time to handle the detect message in one minute, then it will report HDLC_FAIL alarm on all the board, 4- So if these alarms only appeared for one minute, and then disappear, we ne ed to do nothing for it, it will not affect the NE function. 5- .If these alarms appeared for a long time, and didn't disappear, we need to re place the SCC board.

Handling Process:

1- We checked the alarm log we found that as parameter the alarm is repor ted on all boards 2- We collect the data using data collector to be analyzes 3- we check the alarms duration
Page 4 of 8

4- If these alarms only appeared for one minute, and then disappear, we ne ed to do nothing for it, it will not affect the NE function.(as this mean SCC board is busy ) 5- .If these alarms appeared for a long time, and didn't disappear, we need to replace the SCC board. Suggestions Suggestions and Summary: So If the HDLC_FAIL alarms only appeared for one minute, then disappear, we need to do nothing for it, it will not affect the NE function. But if these alarms appeared for a long time, and didn't disappear, we need t o replace the SCC board.

-: SCC HDLC_FAIL. HDLC_FAIL , , , NE. , , SCC .

The LINK_ERR Alarm Is Reported Because an Optical Module on the TQX Board Is Faulty

Fault Type:

Data Service Feature

Keywords:

LINK_ERR loopback TQX

There are two channels of point-to-point 10G LAN services between station A and station B. The TQX board is used on the tributary side and the NQ2 board Phenomenon is used on the line side. After a router is connected, it is found that two ends Description: of a channel report the LINK_ERR alarm and the service on the channel is interrupted. The other channel is normal.

LINK_ERR. Alarm Information: 1. The working modes of optical interfaces at the transmit and receive ends are inconsistent. Therefore, the negotiation fails. Cause Analysis: 2. The link is faulty. 3. The cable or optical fiber is incorrectly connected, or the opposite equipment

Page 5 of 8

is faulty. 4. The input optical power of two interconnected Ethernet ports is excessively high or low. 5. The optical interface modes of two interconnected Ethernet ports are inconsistent, or the optical interface mode is inconsistent with the optical fiber mode. 6. The board at the local station is faulty.

Handling Process:

The TQX board does not have the PHY chip, which indicates that the problem is not caused by the working modes of the optical interfaces. Check the optical power. The receive optical power values at two ends of the TQX board are 6.7 dB and 8.1 dB, which are in the normal range. The TQX board does not have Layer 2 chips. In addition, the chip for detecting the Link state is located after the cross-connect chip. After an internal loopback is performed on the NQ2 board, it is found that the LINK_ERR alarm on the TQX board at station A disappears while the alarm persists on the TQX board at station B. Perform a warm reset on the TQX board at station B, the alarm persists. After the module on the third channel is inserted to the second channel on the TQX board at station B, the alarm disappears. Release the internal loopback at two ends, the alarm disappears and the router connection is normal.

Suggestions The TQX board does not have Layer 2 chips. In addition, the chip for and Summary: detecting the Link state is located after the cross-connect chip. You can perform a loopback to locate the problem. -: TQX LINK_ERR. Layer 2 TQX

Page 6 of 8

The SSE5OAUC01C Board Reports an IN-POWER-LOW Alarm When the Optical Power Is Normal or High

Fault Type: Phenomenon Description:

Amplifier_Unit

Keywords:

IN-POWER-LOW

In the OptiX BWS 1600G WDM project, the NE version is 5.08.7.12. The SSE5OAUC01C board in slot 1 on an NE reports an IN-POWER-LOW alarm on optical interfaces 1 and 3, but the actual optical power is normal. The SSE5OAUC01C board in slot 1 on an NE reports an IN-POWER-LOW alarm on optical interfaces 1 and 3.

Alarm Information:

1. The optical power is abnormal or the optical fiber is dirty. 2. The board reports the alarm incorrectly. 3. The board is faulty. Cause Analysis: 4. The optical power threshold set on the board is improper.

Handling Process:

1. Clean the optical fiber and query the input optical power. The query result is that the Rx power on optical interface 1 is -13.2 dB and the Rx power on optical interface 3 is -12.7 dB. The values detected through an optical power meter, command line, and NMS are consistent. Therefore, the actual values are normal. 2. For the performance index of the optical amplifier unit (OAU) in C band on the finished board OptiX WDM SSE5OAUC00, the maximum input is 2 dBm, the output is 20 dBm, the gain range is 16 dB to 25.5 dB, and the range of the input optical power is -32 dBm to 2 dBm. Since the actual values are in the valid ranges, the IN-POWER-LOW alarm should not be reported. 3. Query the LOS threshold of the board. Run the :cfg-get-losth:1,1,1 command, and the returned value is -35 dB. Run the :cfg-get-losth:1,3,1 command, and the returned value is -43.0 dB. Since the input optical power does not exceed the threshold, the IN-POWER-LOW alarm should not be reported. 4. Reset the SCC board. The fault persists. 5. R&D engineers perform the following operations. Run the :cfg-get-almth:1,1,1,lsiop command. The returned value is: lsiop: TH-HIGH is -6.0db, TH-LOW -15db.
Page 7 of 8

Run the :cfg-get-almth:1,3,1,lsiop command. The returned value is: lsiop: TH-HIGH is-6.0db, TH-LOW -13db. According to the symptom, the problem is caused by the alarm threshold. 6. Change the threshold as follows: :nptp:hexbid,13,30,port,0,1,0,90,XX,XX,XX,XX,YY,YY,YY,YY hexbid indicates the slot ID in hexadecimal (parameters in the nptp command are in hexadecimal). port indicates the optical interface number. XX,XX,XX,XX, four bytes in length, indicates the upper threshold in the unit of 0.1 dBm. Negative numbers are represented by complements. YY,YY,YY,YY, four bytes in length, indicates the lower threshold in the unit of 0.1 dBm. Negative numbers are represented by complements. A complement is the sum of the negation of the original number in hexadecimal and 1. A specific threshold is usually set according to the board. It is recommended to follow the principle of 3 dB higher than the sensitivity and 5 dB lower than the overload threshold. For example, assume that the threshold is -13 dB. Because the threshold is in the unit of 0.1, -13 is represented as -13*10=-130. 130 in hexadecimal is 82. Complete the digits in the proper format: 00 00 00 82. The negation is ff ff ff 7d; plus 1; the value is ff ff ff 7e. After the setting, use :cfg-get-almth to query the setting result.

Suggestions and Summary:

In V100R007, alarm thresholds should be consistent. There is a low probability that some thresholds are inconsistent on modules of different vendors.

-: SSE5OAUC01C IN-POWER-LOW. Layer 2 TQX. .

Page 8 of 8