Board-side status after alarm suppression is enabled on an OSN 6800 NE


There is no other alarm except R_LOS on an NS2 board on an OSN 6800 NE. Does the running status indicator of the board turn red or green if the R_LOS alarm is suppressed on the NMS? Does the indicator on the system control board turn red or green? Does the indicator on the top of the cabinet turn red or green?
Root cause:
Generally, an NE on which alarm suppression is enabled does not monitor related alarms. The suppressed alarms are not reported on either the U2000 or NE. The indicator status, however, varies according to NE types. The OSN 6800 uses the alm-set-monevent command to configure alarm suppression on a board, and the indicator on the board and the indicator on the system control board turn green after alarm suppression is enabled. The indicator on the top of the cabinet reflects alarms of the system control board and therefore is green.
Suggestion and conclusion:
When alarm suppression is enabled on a board on an NG SDH NE and the NE actually still has alarms, the SRV indicator on the board is red. When alarm suppression is enabled on a board on a Metro 2500+ NE and the board has an alarm, the indicator is green.

Other related questions:
Methods used to set the suppression for OTN NE alarms and query the alarms using command lines
The query command is as follows: alm-cfg-get-monstate: alarm name, 0xff,0,0,'''' For example, by running the alm-cfg-get-monstate:R_LOS,0xff,0,0,''' command, you can query the states of all ports that can report the R_LOS alarm on an NE. The query result is enable or disable. The setting command is as follows: :alm-cfg-set-monstate: alarm name, disable/enable,0xff,0,0,'''' For example, by running the alm-cfg-set-monstate: R_LOS,disable,0xff,0,0,'''' command, you can suppress all the NE ports that report the R_LOS alarm.

Possible cause of the BUS_ERR alarm that is reported on a TDX board after OptiX OSN 6800 is upgraded
The possible cause of the BUS_ERR alarm is that the board mode is incorrect. You are advised to modify the value of the line mode parameter.

Using command lines to suppress alarms for the OSN 6800
For example, to suppress R_LOS alarms on all ports, run the following command: alm-cfg-set-monstate:R_LOS,disable,0xff,0,0,"";

NO_BD_PARA alarm on an OAU board on an OSN 6800 NE
Question: Why an OAU board reports a NO_BD_PARA alarm on an OSN 6800 NE of version V100R003 for which ALC is configured? Root cause: None Answer: ALC is inappropriately configured. As a result, the computed value of a required parameter exceeds the maximum OAU gain (31 dB). There is a bug in the software processing mechanism. Due to this bug, when an OAU board uses the extended gain, the value of computed pump current exceeds the maximum value. As a result, a critical alarm is reported. When the software computes the drop-wavelength parameter table and the computed turning point current exceeds the rated current value, the rated current value is used as the turning point current value. Impact: This issue is not triggered under normal configurations. If this issue is triggered, there is no impact on services or functions, and the issue can be rectified by modifying configurations. Version in which the issue has been resolved: V100R003C02B028

Cause why OSN 6800 NEs report license-related alarms
Question: A customer provides feedback that all system control boards of 48 OSN 6800 NEs report the SYSTEM_DEF_RUNNING alarm one day. One of the NEs also reports the VERIFY_LCS_ERROR alarm. Analysis: 1. A dedicated ASON license file must be loaded to an OSN 6800 NE to enable ASON for the NE. 2. The OSN 6800 NE periodically checks whether the license has been loaded on the system control board. If the ASON license has not been loaded, the SYSTEM_DEF_RUNNING alarm is reported. 3. If the ASON license has been loaded but is about to expire, the NE reports the LICENSE_GOINGTO_EXPIRT alarm. 4. If an incorrect ASON license has been loaded, the NE reports both the SYSTEM_DEF_RUNNING and VERIFY_LCS_ERROR alarms. Root cause: None Answer: 1. Because ASON has not been enabled for the NEs, directly suppress the alarm. If ASON is required later, load a correct license file. 2. Run the license-show-file command to query license information. Suggestion and conclusion: When ASON is not enabled, you are advised to set license-related alarms to be not monitored to avoid customer misunderstanding.

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