Using command lines to suppress alarms for the OSN 6800

(1) The single-site or board optical cross-connections of other wavelengths are successfully created on the NMS. Therefore, the system control board fault or ROAM fault of the optical-layer scheduling board is ruled out. (2) When the cfg-get-e2eoxc:0,0 command is used to query the single-site optical cross-connections, the optical cross-connection of the wavelength on the ROAM is 0000, which is abnormal. The state should be one of active, adding, and deleting. (3) When a command line is used to create the single-site optical cross-connection of the wavelength, the optical cross-connection is successfully created. In addition, the single-site optical cross-connection of the wavelength can also be successfully deleted from the NMS. (4) Check the operation records of the onsite engineer and find that the procedure is as follows: Check the board optical cross-connection of the wavelength à Create the single-site optical cross-connection of the wavelength à Query the board and single-site optical cross-connections of the wavelength. The wavelength is present on both the board optical cross-connection and single-site optical cross-connection. Then, you can delete the board optical cross-connection and verify it. (5) If the board optical cross-connection is deleted using a command line but no verification is performed, services will not be interrupted when the board optical cross-connection is in the deleting state. If a single-site optical cross-connection is created at that time, the board optical cross-connection will become the active state. After the verification command is successfully delivered, the wavelength cannot be found in the board optical cross-connection and it can be queried only in the single-site optical cross-connection. (6) Because the onsite engineer found the wavelength both in the board optical cross-connection and single-site optical cross-connection, the engineer falsely determined that the optical cross-connection was not successfully deleted and then deleted it again. As a result, optical cross-connections on the NE software side are incomplete.

For example, the alm-cfg-set-monstate:R_LOS,disable,0xff,0,0 "" command can be used to suppress all the NE ports reporting the R_LOS alarm.

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.

Question: 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? Analysis: None Root cause: None Answer: 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.

Run the :cfg-get-afbver command to query the model of an OSN 6800 backplane.