The customer reports that they mistakenly deactivate a certain cross-connect wavelength on the WSMD4 of the OptiX OSN 6800. After they reactivate the optical cross-connection, the interrupted service does not recover.
The NE software version is 18.104.22.168, and the WSMD4 version is 1.11.
The L4G of the peer NE reports an R_LOS alarm.
1) Run the :cfg-get-intraoxc:0,0; command to query the optical cross-connection on the NE. The optical cross-connection is found, indicating that the optical cross-connection service at the wavelength is issued to the NE.
2) Replace the WSMD4. The fault persists.
3) Apply a self-loop on the L4G, and the R_LOS alarm clears.
4) At this point, it is suspected that deactivating and then reactivating the service on the WSMD4 may have impact on the optical power. Query the output power of the WSD4, and the query result shows that the power is relatively low. After a check of the WSMD4, it is found that the default attenuation of the WSMD4 for adding this wavelength is 20 dB. After a consultation with the customer, it is found that the original attenuation value is 10 dB. Then, change the attenuation value to 10 dB. The fault is rectified.
5) According to feedback from R&D personnel, the WSMD4 of the OptiX OSN 6800 blocks all the wavelengths during power-on by default with the attenuation set to 20 dB. After a certain cross-connect wavelength is deactivated, the default attenuation is restored. In this case, you need to properly change the attenuation value again after reactivating the wavelength.
1) After the customer deactivates the wavelength of the WSMD4, the R_LOS alarm is generated and does clear. The fault may be caused by the factor that the optical cross-connection is not issued to the NE.
2) The WSMD4 is faulty.
3) The peer L4G is faulty.
1) Be sure not to cause such a problem during maintenance or configuration of the optical cross-connection on the WSMD4 to prevent any impact on the optical power.