Causes for reporting the LASER_MODULE_MISMATCH alarm when the WDM side of the LEX4 board is interconnected with the client side of the LBFS board

11

By default, a colored optical module is configured on the WDM side of the LEX4 board, and the board software will automatically create a logical colored optical module for this WDM-side optical module. During practical application, you need to create the correct logical optical module based on the actual type of physical optical module that is used.

Other related questions:
Causes for the issue that services are still normal at the client-side port on an L4G board where an R_LOS alarm is reported
As to a traditional SDH device, if an optical port reports an R_LOS alarm, the device will check all 1s in the payload of the channel, resulting in service interruptions. Why services of the port are still normal when an L4G board reports an R_LOS alarm on the client side? There are two causes: 1. The first cause is related to OTN principles. When an OTU board detects an R_LOS alarm on the client-side port, the device will not check all 1s in information payload. Instead, it will insert an SF event into its overhead. When the opposite end detects the SF event, the CLIENT_SF indication alarm will be reported. Although the OTU board reports the R_LOS alarm on the client side, the device will still encapsulate the weak signals received at the port. 2. Some boards can still receive valid information even when R_LOS alarms are reported on the client side. The L4G boards from different manufacturing batches use different chips, which have different sensitivity values. For some of them, although optical signal is lower than the preset R_LOS threshold, the received signals are still processed normally due to good quality of the chips.

Transmission distance of the client side of the TN53TSXL board
The client side of the TN53TSXL board is equipped with a fixed optical module, whose transmission distance is 2 km.

Access rate of a WDM-side port on the TMX board
The WDM-side signals of the TMX board are OTU2 signals, and the access rate is 10.71 Gbit/s.

Number of client-side ports on the TTX board
There are 10 physical ports on the client side of the TTX board and the port with the maximum number is RX10/TX10. On the NMS, numbers 1 and 2 have been assigned to IN/OUT ports on line boards. Ports on tributary boards are numbered from 3. TTX is a tributary board and therefore its ports are numbered from 3. In other words, logical port 3 on the NMS corresponds to the RX1/TX1 port.

Cause why an R_LOF alarm is reported when the client-side port of an E7LWF board is set to UNUSE state
Question: Why an R_LOF alarm persists after the client-side port on an E7LWF board is set to the UNUSE state? The product version is V100R003C01B01m. Root cause: None Answer: The current software version of the E7LWF board dynamically updates the list of R_LOF alarm nodes when the optical port is unused. As a result, R-LOF alarms are transiently reported irregularly and cannot be cleared. On an NE of version V100R005 or V100R006, this issue is resolved using the alarm anti-jitter function of the NE. On the live network, upgrade the board software to resolve this issue. Board software version V7.24 in NE version V100R003C01B029 will be released to resolve this issue. Before the board software version is released, set the optical port to the use state to prevent this issue. Suggestion and conclusion: None

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top