Method used to handle the POWER_FAIL alarm on the TN52SCC board


Check the settings of the battery jumper on the TN52SCC board. If the board is not powered by batteries, configure the board power supply status to ensure that the board is powered by batteries. For details how to set the battery jumper, see the Hardware Description.
If the POWER_FAIL alarm is reported by the TN52SCC board, the battery of the board is abnormal (the value of alarm parameter 1 is 0x05).
1. On the NMS, back up the NE configuration data to the database in the flash memory of the TN52SCC board.
2. Check whether the jumper cap is correctly placed over the battery jumper. If it is, check the jumper setting of the battery on the board. If the setting disables the battery from providing power, modify the setting to ensure the SCC board is powered using the battery.
3. If the alarm persists, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is faulty. When this occurs, replace the TN52SCC board.

Other related questions:
Thresholds and handling methods for the BEFFEC alarm reported by the LSC boards on OSN 8800
If the pre-FEC BER of a 100G LSC board at the local site is 4 and the BEFFEC alarm is reported, the processing method is as follows: When the receive optical power of the IN port on the WDM side of the LSC board is normal (PIN: �?6 to 0), the receive light flatness at the local site needs to be adjusted. Ensure that the difference between the receive light flatness values of a 100G wavelength and a 10G wavelength is within 2 dB and decrease the attenuation of the optical port of the 100G wavelength on the transmit-end M40V board at the peer site by 1�? dB. Improve the receive optical power of the 100G wavelength at the local site compared with the receive optical power of other 10G wavelengths to reduce the pre-FEC BER and clear the BEFFEC alarm.

Method used to handle the TEMP_OVER alarm reported by the CXP board
1. Check whether a fan stops running on the fan board. If yes, remove and insert the fan board. If no, go to the next step. 2. Clean the air filter.

Method used to handle the NO_BD_PARA alarm on a CRPC Raman amplifier board
Question: A CRPC board on an OSN 6800 NE reports a NO_BD_PARA alarm, and the alarm parameter is 0x01 0x00 0x01. Analysis: 1. The board software is lost. 2. Board data configurations are incorrect. 3. The board hardware is faulty. Root cause: None Answer: 1. Query the board software information. The board software information can be normally queried, and alarm information indicates that the board software is not lost. 2. Check whether board settings are correct. On the NMS, select the CRPC board and choose Configuration > WDM Interface in the navigation tree. Select By Board/Port (Channel) and click the Advanced Attributes tab. In Fixed Pump Optical Power (dBm), query the pump laser optical power which is -60 dBm. Set it to 24 dBm. Then the NO_BD_PARA alarm is cleared. Suggestions and conclusion: 1. The CRPC board is a Raman amplifier board. The Raman pump optical power is disabled before delivery to avoid personal injury at deployment. Therefore, the queried value is -60 dBm. This value does not meet board requirements, and therefore the NO_BD_PARA alarm is reported. 2. The CRPC board (backward Raman amplifier board) requires that the gain of each wavelength should exceed 10 dB. During deployment commissioning, set the initial pump power value of the board to the recommended value as follows: For a G.652 or G.655 fiber, you are advised to set the optical power to 24 dBm for the first and second pump lasers. For a G.653 fiber, you are advised to set the optical power to 23 dBm for the first pump laser and to 22.5 dBm for the second pump laser.

Method used to handle the PORTSWITCH_FAIL alarm
Question: An OSN 6800 reports a PORTSWITCH_FAIL alarm, and the relevant MCA4 board cannot be normally queried. Analysis: 1. Perform a cold reset on the board on the NMS. The fault persists. 2. Remove and then insert the board onsite. The fault is rectified. Root cause: The board is faulty. Answer: Perform a cold reset on the board on the NMS, or remove and then insert the board onsite. Suggestion and conclusion: None

Method used to handle the PS alarm reported by an unused protection group of a DCP board
Question: The first protection group on a DCP board of a WDM network is used. The second protection group is not used, but the PS switching alarm is reported. What are the methods of monitoring the impact and handling the issue? Once the alarm is masked, the PS alarm of the first protection group is masked. Analysis: 1. BWS 1600G NEs support DCP boards of various versions. The PS alarms of the DCP boards are reported when the optical switches are in the standby state. Because the alarm distinguishes the protection groups according to alarm parameters, PS alarms of the entire board will be not monitored if the alarms are masked. Therefore, the alarms cannot be handled by masking them. 2. Based on the DCP board alarm mechanism, you can clear the PS alarm by setting the second optical switch to active. 3. Because there is no command for directly changing the optical switch status, use the second protection group that is logically configured and lock out the optical switch to the active state. Then the issue is rectified. Answer: 1. Configure two logical OTU boards on the NMS, and configure the second protection group to a wavelength protection group. 2. Issue a lockout command to this new protection group on the NMS. The alarm is cleared. 3. Delete the new logical protection group and OTU board.

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