Problem and solution when a BBU fault alarm is reported and the alarm indicator is red

0

You can perform the following operations when a BBU fault alarm is reported and the alarm indicator is red:
Check the SES log and search keyword invalid OnlineTest (the online BBU test fails).
If the keyword exists, verify the BBU type in the SES log.
If the product name of BBU is HSCB1-62, the BBUs are BYD BBUs which may cause the problem. Replace BYD BBUs with SCUD BBUs (pay attention to the change during replacement).

Other related questions:
Problem and solution when the controller enclosure alarm indicator is on but no alarm is reported on the storage system
You can perform the following operations when the controller enclosure alarm indicator is on but no alarm is reported on the storage system: 1. Fault location and rectification a. Log in to the storage system and check whether alarm information is reported. b. Query the SES log and confirm the cause and last time when the alarm indicator is on. c. Check the SES and message log to find why the indicator is on. 2. Fault Diagnosis a. Search start led(0x0) (off) and (0x1) (on) in the SES log. Verify the last time when the alarm indicator is on. b. Check in the historical alarms whether the alarm is recovered when the indicator is on. c. Analyze turn-off and turn-on records in the message logs of controllers A and B. Search keyword light. d. If the alarm is recovered and the controller does not send a turn-off command, send the command manually. 3. Solution Send the mml:dev sesstartlight 0 command to the controller whose indicator is turned on and then not off. Note: The controller enclosure alarm indicator follows the same rule as the disk indicator does that the same indicator is turned on and then off. The above method is only applicable to the situation where the controller enclosure alarm indicator is on.

Indication of the red alarm indicator on the Metro 1000
If the alarm indicator on the Metro 1000 is steady red, a critical alarm is generated. You need to check it on the NMS.

Solution when the power alarm indicator is steady on
Solution when the power alarm indicator is steady on: 1. Locating procedure: The power alarm indicator is controlled by the PSU hardware, but not the software. If the power alarm indicator is steady on, causes may be as follows: a. The power supply is normal but the switch on the power plane is turned off. b. The PSU hardware is faulty. 2. Solution: a. The switch on the power plane is turned off. Log in to the storage's OSM management page and check whether related alarms are reported. If no related alarms (PSU or fan) are reported and you can query information about fans and two PSUs on the OSM page, check whether switches on power planes are switched off (you can check whether switches on power planes of controller A and B are the same). If switches on power planes are switched off, turn them on. b. PSUs are faulty. If switches on power planes are switched on, internal hardware of PSUs is faulty. In this case, you need to change PSUs.

Problem and solution when the BBU is blinking green and orange alternately
You can perform the following operations when the BBU is blinking green and orange alternately as follows: A BBU indicator blinking green indicates that the BBU is being charged, whereas a BBU indicator blinking orange indicates that the BBU is discharging. The possible cause is that the early-version storage system software carries out online tests at low power consumption, and the tests fail. Check event information to see if the insufficient BBU power alarm is reported repeatedly. Check the SES logs for online testing results. Note: DisChar indicates the discharging current. 16 indicates that the current value is 1.6 A. If the value ranges from 10 to 20 (1 A to 2 A) and the version of the storage system software is earlier than V100R001C01SPC013 (R1) and V100R002C00SPC004 (R2), the cause of this fault is that the system software carries out online tests frequently due to test failures at low power consumption. Troubleshooting Check the version of the system software. If the version is V100R001C00CSPC012 or an earlier version, upgrade it to V100R001C00CSPC013 or a later version.

Cause why the alarm indicator of the OTU board is red even after the HARD_ERR alarm is suppressed
Question: An OTU board on an OSN 6800 NE reports a HARD_ERR or HARD_BAD alarm. After the alarm is suppressed on the T2000, the board indicator on the T2000 is still red. When other alarms are suppressed and there is no additional alarm on the board, the board indicator is green. Analysis: The HARD_ERR and HARD_BAD alarms are at the hardware maintenance level. In general, the alarms indicate board hardware faults and the boards need to be replaced. Therefore, the alarm indicator is still on even when the HARD_ERR and HARD_BAD alarms are suppressed to instruct onsite engineers to replace the boards. Root cause: None Answer: The OSN 6800 is designed in this manner to instruct onsite engineers to replace faulty boards.

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