Reason for a WAVELEN_OVER alarm reported on the WMU board when physical and logical fiber connections are inconsistent

22

When physical and logical fiber connections are inconsistent, the wavelength locking function triggers a false wavelength adjustment. As a result, a WAVELEN_OVER alarm is reported.

Other related questions:
Excessively large wavelength deviation reported by the WMU boards of OSN 6800
Question: The LSX boards with adjustable DRZ reported the WAVE_LEN_OVER alarm, whereas the ones with NRZ fixed wavelengths did not report the alarm. When an optical spectrum analyzer was used for wavelength testing, the wavelength deviations are within the allowed range. No excessively large wavelength deviation is detected. (OSN 6800 NE version 5.51.3.25, NMS version T2000V2R6) Root cause: None Answer. The wavelengths from the light source of the DRZ adjustable optical modules are controlled by the core temperature without human interference. Wavelength deviation adjustment should not be performed by the software to such modules. V100R003C02B028 does not monitor adjustable optical modules for wavelength deviation, and the deviation threshold was changed from 0.5 GHz to 5 GHz.

Fiber connections on the optical ports of the WMU board
The IN1 and IN2 optical ports on the WMU board separately connect to the MON port on two OA or FIU/ITL boards configured in two different transmit directions for centralized wavelength monitoring.

Whether ODUk SNCP protection switching will fail if logical fiber connections and physical fiber connections are reverse
Yes, ODUk SNCP switching will fail.

Method used to verify the consistency between physical fiber connections and logical fiber connections on Metro 1000
1. The Metro 1000 V2 does not support query for received J0 bytes. You can change the number of J0 bytes to be transmitted at the local end to be different from the number of J0 bytes to be received at the peer end, and then check whether the J0_MM alarm is reported. 2. You can also insert an MS_AIS alarm and check whether the peer end reports the MS_AIS alarm. Exercise caution because this operation will interrupt services.

Reason for the failure to report alarms by boards in a subrack when a large number of SHELF_AREA_POWER_OVER alarms are reported
The SHELF_AREA_POWER_OVER alarm indicates that the nominal power consumption of a subrack section exceeds the specified threshold. This alarm is reported when the total nominal power consumption of boards in a subrack section of an NE is greater than or equal to the power consumption threshold of the subrack section. This alarm is reported on the system control boards, such as SCC and 16XCH/16UXCM. If the alarm is present, the subrack is overloaded. When this occurs, you need to remove boards from the corresponding subrack section as required. If the subrack is running in overloaded state for a long time, the power supply to the subrack may be abnormal or interrupted.

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