Cause why an R_LOF alarm is reported when the client-side port of an E7LWF board is set to UNUSE state


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:
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:

Other related questions:
Difference between the traffic-policy and traffic policy commands
For the traffic policy command, the system view is used to create a traffic policy or enter the view of an existing traffic policy. The traffic-policy command is used to apply a created traffic policy to the interface view or system view.

Setting the Raman board alarm reporting parameter to Enabled
The CRPC01 board supports fiber cut detection. That is, when the CRPC01 board detects an IPA trigger condition, the IPA function will shut down the transmitting laser on the CRPC01 board. This, however, can be achieved only when the following conditions are satisfied: 1. The CRPC01 board is configured as the Raman Amplifier. 2. At least one of the 192.4 THz to 192.1 THz wavelengths is configured in the system. In a system with 50 GHz channel spacing, at least one of the following wavelengths is configured in the system: 192.4 THz, 192.35 THz, 192.3 THz, 192.25 THz, 192.2 THz, 192.15 THz, and 192.1 THz. In a system with 100 GHz channel spacing, at least one of the following wavelengths is configured in the system: 192.4 THz, 192.3 THz, 192.2 THz, and 192.1 THz. 3. Raman Board Alarm Reporting is set to Enabled. 4. Raman Board Threshold (dBm) is set correctly. Note: If wavelengths 192.4THz-192.1THz are not configured in the system, Raman Board Alarm Reporting must be set to Disabled.

Method used to set Shelf Link Mode
Before connecting a subrack, you need to set Shelf Link Mode to be consistent with the actual physical cascading mode the subracks on the U2000 to ensure proper functioning of the subracks and normal communication between subracks on an NE. The procedure is as follows: In the NE Explorer, select the NE and choose Configuration > Shelf Link Management. In the right pane, click the Shelf Link Mode. Double-click the desired NE, and set it to Tree or Ring according to the actual physical cascading mode of the subracks. Click Apply.

Password of the szhw user for newly delivered OSN 8800 T32 devices
The password is Changeme_123.

Values of RESETTYPE in board reset records of Metro 1000 devices
Question: In the output of the :dbms-query:"cfg_brr.dbf",drdb command for querying board reset records, what do values 0, 1, and 2 of the RESETTYPE parameter mean? Answer: The meanings of the parameter values are as follows: 1: cold reset 2: warm reset 0: neither cold reset nor warm reset (The corresponding record is generated by default.)

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