Enclosure events
The following table lists the events that are created for the Enclosure component.
| Event | Event Type |
Severity | Call Home | Details |
|---|---|---|---|---|
| adapter_bios_notavail | STATE_CHANGE | WARNING | no | Message: The BIOS level of adapter {0} is not available. |
| Description: The BIOS level of the adapter is not available. A BIOS update might solve the problem. | ||||
| Cause: The mmlsfirmware -Y command reports no information about the BIOS firmware level. | ||||
| User Action: Issue the mmlsfirmware command. For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. Follow the maintenance procedures for updating the BIOS firmware. If the issue persists, then contact IBM support. | ||||
| adapter_bios_ok | STATE_CHANGE | INFO | no | Message: The BIOS level of adapter {0} is correct. |
| Description: The BIOS level of the adapter is correct. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| adapter_bios_wrong | STATE_CHANGE | WARNING | no | Message: The BIOS level of adapter {0} is wrong. |
| Description: The BIOS level of the adapter is not correct. The BIOS firmware needs an update. | ||||
| Cause: The mmlsfirmware -Y command reports that the BIOS firmware is not up to date. | ||||
| User Action: Issue the mmlsfirmware command. For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. Follow the maintenance procedures for updating the BIOS firmware. If the issue persists, then contact IBM support. | ||||
| adapter_firmware_notavail | STATE_CHANGE | WARNING | no | Message: The firmware level of adapter {0} is not available. |
| Description: No or insufficient information about the adapter firmware is available. An update might solve the problem. | ||||
| Cause: The mmlsfirmware -Y command reports no information about the adapter firmware level. | ||||
| User Action: Issue the mmlsfirmware command. For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. Follow the maintenance procedures for updating the adapter firmware. Contact IBM support if you cannot solve the problem. | ||||
| adapter_firmware_ok | STATE_CHANGE | INFO | no | Message: The firmware level of adapter {0} is correct. |
| Description: The firmware level of the adapter is correct. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| adapter_firmware_wrong | STATE_CHANGE | WARNING | no | Message: The firmware level of adapter {0} is wrong. |
| Description: The firmware level of the adapter is not correct. The adapter firmware needs an update. | ||||
| Cause: The mmlsfirmware -Y command reports that a wrong firmware level for the adapter. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. Follow the maintenance procedures for updating the adapter firmware. | ||||
| current_failed | STATE_CHANGE | ERROR | no | Message: Current sensor {0} measured wrong current. |
| Description: A current sensor might be broken and should be replaced. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that a current sensor has measured a wrong current. | ||||
| User Action: Issue the mmlsenclosure all -L command to get more details. If the problem persists, then contact IBM support. | ||||
| current_ok | STATE_CHANGE | INFO | no | Message: currentSensor {0} is OK. |
| Description: The currentSensor state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| current_warn | STATE_CHANGE | WARNING | no | Message: Current sensor {0} might be facing an issue. |
| Description: A current sensor has measured a value outside the warning limits. | ||||
| Cause: The mmlsenclosure all -L -Y command reports a warning about a current sensor. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| dcm_drawer_open | STATE_CHANGE | WARNING | no | Message: DCM {0} drawer is open. |
| Description: The Drawer Control Module (DCM) drawer is open. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the DCM drawer is open. | ||||
| User Action: Close the DCM drawer. | ||||
| dcm_failed | STATE_CHANGE | WARNING | no | Message: DCM {0} is FAILED. |
| Description: The Drawer Control Module (DCM) state is FAILED. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the DCM is FAILED. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| dcm_not_available | STATE_CHANGE | WARNING | no | Message: DCM {0} is not available. |
| Description: The Drawer Control Module (DCM) is not installed or not responding. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the DCM component is not available. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| dcm_ok | STATE_CHANGE | INFO | no | Message: DCM {id[1]} is OK. |
| Description: The DCM state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| dimm_config_mismatch | STATE_CHANGE_EXTERNAL | ERROR | no | Message: Enclosure has an inconsistent DIMM configuration. |
| Description: Inconsistent DIMM configuration. | ||||
| Cause: The DIMMs in the enclosure do not fit to each other. | ||||
| User Action: Verify that all DIMMs in all canisters have the same specification (size, speed, etc). The event can be manually cleared by using the mmhealth event resolve dimm_config_mismatch command. | ||||
| dimm_config_ok | STATE_CHANGE_EXTERNAL | INFO | no | Message: Enclosure has a correct DIMM configuration. |
| Description: The DIMM configuration is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| door_failed | STATE_CHANGE | ERROR | no | Message: Door {0} state is FAILED. |
| Description: The door state is reported as failed. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the door is in the failed state. | ||||
| User Action: Run the mmlsenclosure all -L command to see further details. | ||||
| door_is_absent | STATE_CHANGE | ERROR | no | Message: Door {0} state is absent. |
| Description: The door state is reported as absent. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the door is absent. | ||||
| User Action: Install the enclosure door. Verify the door state by using the mmlsenclosure all -L command. For more help, contact IBM support. | ||||
| door_is_open | STATE_CHANGE | ERROR | no | Message: Door {0} state is open. |
| Description: The door state is reported as open. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the door is open. | ||||
| User Action: Close the enclosure door. Verify the door state by using the mmlsenclosure all -L command. | ||||
| door_ok | STATE_CHANGE | INFO | no | Message: Door {0} is OK. |
| Description: The door state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| drawer_failed | STATE_CHANGE | ERROR | no | Message: Drawer {0} state is FAILED. |
| Description: The drawer state is reported as FAILED. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the drawer is in FAILED state. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| drawer_ok | STATE_CHANGE | INFO | no | Message: Drawer {0} is OK. |
| Description: The drawer state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| drive_firmware_notavail | STATE_CHANGE | WARNING | no | Message: The firmware level of drive {0} is not available. |
| Description: Zero or insufficient information about the drive firmware is available. An update might solve the problem. | ||||
| Cause: The mmlsfirmware -Y command reports that no information about the drive firmware level. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. Follow the maintenance procedures for updating the drive firmware. If the issue persists, then contact IBM support. | ||||
| drive_firmware_ok | STATE_CHANGE | INFO | no | Message: The firmware level of drive {0} is correct. |
| Description: The firmware level of the drive is correct. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| drive_firmware_wrong | STATE_CHANGE | WARNING | no | Message: The firmware level of drive {0} is wrong. |
| Description: The firmware level of the drive is not correct. The drive firmware needs an update. | ||||
| Cause: The mmlsfirmware -Y command reports that the drive firmware is not up to date. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. Follow the maintenance procedures for updating the drive firmware. If the issue persists, then contact IBM support. | ||||
| enclosure_data | STATE_CHANGE | INFO | no | Message: Enclosure data is found. |
| Description: The enclosure data is available. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| enclosure_firmware_notavail | STATE_CHANGE | WARNING | no | Message: The firmware level of enclosure {0} is not available. |
| Description: Zero or insufficient information about the enclosure firmware is available. An update might solve the problem. | ||||
| Cause: The mmlsfirmware -Y command does not report any information about the enclosure firmware level. | ||||
| User Action: Issue the mmlsfirmware command. If the issue persists, then contact IBM support. | ||||
| enclosure_firmware_ok | STATE_CHANGE | INFO | no | Message: The firmware level of enclosure {0} is correct. |
| Description: The firmware level of the enclosure is correct. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| enclosure_firmware_unknown | STATE_CHANGE | WARNING | no | Message: The firmware level of enclosure {0} is unknown. |
| Description: The enclosure firmware is of an unknown version. An update might solve the problem. | ||||
| Cause: The mmlsfirmware -Y command does not report any enclosure firmware information. | ||||
| User Action: Issue the mmlsfirmware command. For more information on how to update the enclosure firmware, see the IBM Storage Scale: Problem Determination Guide of the relevant system. If the issue persists, then contact IBM support if you cannot solve the problem. | ||||
| enclosure_firmware_wrong | STATE_CHANGE | WARNING | no | Message: The firmware level of enclosure {0} is wrong. |
| Description: The firmware level of the enclosure is not up to date. The enclosure firmware needs an update. | ||||
| Cause: The mmlsfirmware -Y command reports that the enclosure firmware is not up to date. | ||||
| User Action: Issue the mmlsfirmware command. If the warning message persists, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| enclosure_found | INFO_ADD_ENTITY | INFO | no | Message: Enclosure {0} is found. |
| Description: A GNR enclosure, which is listed in the IBM Storage Scale configuration, was detected. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| enclosure_needsservice | STATE_CHANGE | WARNING | no | Message: Enclosure {0} needs service. |
| Description: The enclosure needs service. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the enclosure needs service. | ||||
| User Action: For more information, contact IBM support. | ||||
| enclosure_ok | STATE_CHANGE | INFO | no | Message: Enclosure {0} is OK. |
| Description: The enclosure state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| enclosure_unknown | STATE_CHANGE | WARNING | no | Message: Enclosure state {0} is unknown. |
| Description: The enclosure state is unknown. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the enclosure was not detected. | ||||
| User Action: Restart the system monitor by issuing the mmsysmoncontrol restart command. | ||||
| enclosure_vanished | INFO_DELETE_ENTITY | INFO | no | Message: Enclosure {0} has vanished. |
| Description: A GNR enclosure, which was previously listed in the IBM Storage Scale configuration, is no longer detected. This can be a valid situation. | ||||
| Cause: A GNR enclosure, which was previously listed in the IBM Storage Scale configuration, is no longer found. | ||||
| User Action: Run the mmlsenclosure all -L command to verify that all expected enclosures exist in the listing of the IBM Storage Scale configuration. | ||||
| esm_absent | STATE_CHANGE | WARNING | no | Message: ESM {0} is absent. |
| Description: The Environmental Service Module (ESM) is absent or not installed. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the ESM module is absent. | ||||
| User Action: Check whether the ESM is installed and operational. For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| esm_failed | STATE_CHANGE | WARNING | service ticket | Message: ESM {0} is FAILED. |
| Description: The Environmental Service Module (ESM) state is FAILED. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the ESM has failed. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| esm_ok | STATE_CHANGE | INFO | no | Message: ESM {0} is OK. |
| Description: The ESM state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| expander_absent | STATE_CHANGE | WARNING | no | Message: Expander {0} is absent. |
| Description: The expander is absent. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the expander is absent. | ||||
| User Action: Verify that the expander is correctly installed. | ||||
| expander_failed | STATE_CHANGE | ERROR | no | Message: Expander {0} is FAILED. |
| Description: The expander state is reported as FAILED. | ||||
| Cause: The mmlsenclosure all -L -Y command reports the expander has failed. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| expander_ok | STATE_CHANGE | INFO | no | Message: Expander {0} is OK. |
| Description: The expander state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| fan_absent | STATE_CHANGE | WARNING | service ticket | Message: Fan {0} is absent. |
| Description: A fan is absent. | ||||
| Cause: The mmlsenclosure all -L command reports that a fan is absent. | ||||
| User Action: Check the enclosure. Insert or replace fan. If the problem remains, then contact IBM support. | ||||
| fan_failed | STATE_CHANGE | WARNING | service ticket | Message: Fan {0} state is FAILED. |
| Description: A fan state is FAILED. | ||||
| Cause: The mmlsensclosure all -L command reports that a fan state is FAILED. | ||||
| User Action: Replace the fan. Contact IBM support for a service action. | ||||
| fan_fault_indicated | STATE_CHANGE | WARNING | service ticket | Message: Fan {0} has a fault. |
| Description: A fan has a fault. | ||||
| Cause: The mmlsenclosure all -L command reports that a fan has a fault. | ||||
| User Action: For more information, issue the mmlsenclosure all -L command. Check the enclosure, and insert or replace the fan as needed. If the problem remains, then contact IBM support. | ||||
| fan_ok | STATE_CHANGE | INFO | no | Message: Fan {0} is OK. |
| Description: Fan state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| fan_speed_high | STATE_CHANGE | WARNING | service ticket | Message: Fan {0} speed is too high. |
| Description: Fan speed is out of tolerance because it is too high. | ||||
| Cause: The mmlsensclosure all -L -Y command reports that the fan speed is too high. | ||||
| User Action: For more information, check the enclosure cooling module LEDs for fan faults. | ||||
| fan_speed_low | STATE_CHANGE | WARNING | service ticket | Message: Fan {0} speed is too low. |
| Description: Fan speed is out of tolerance because it is too low. | ||||
| Cause: The mmlsensclosure all -L -Y command reports that the fan speed is too low. | ||||
| User Action: For more information, check the enclosure cooling module LEDs for fan faults. | ||||
| no_enclosure_data | STATE_CHANGE | WARNING | no | Message: Enclosure data and enclosure state information cannot be queried. |
| Description: Correct enclosure details cannot be queried. | ||||
| Cause: The mmlsenclosure all -L -Y command has failed to report any enclosure data, or the data is inconsistent. | ||||
| User Action: Run the mmlsenclosure all -L command to check for any enclosure issues. You must also verify that the pemsmod is loaded by issuing the 'lsmod' command. | ||||
| power_high_current | STATE_CHANGE | WARNING | service ticket | Message: Power supply {0} reports high current. |
| Description: The DC power supply current is greater than the threshold. | ||||
| Cause: The mmlsenclosure all -L -Y command reports high current for a power supply. | ||||
| User Action: Issue the mmlsenclosure all -L -Y command to check the details. For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| power_high_voltage | STATE_CHANGE | WARNING | service ticket | Message: Power supply {0} reports high voltage. |
| Description: The DC power supply voltage is greater than the threshold. | ||||
| Cause: The mmlsenclosure all -L -Y command returns high voltage for a power supply. | ||||
| User Action: Issue the mmlsenclosure all -L command to check the details. For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| power_no_power | STATE_CHANGE | WARNING | no | Message: Power supply {0} has no power. |
| Description: The power supply has no power. It might be switched off or has no input AC. | ||||
| Cause: The hardware monitor reports that power is not being supplied to the power supply. | ||||
| User Action: Ensure that the power supply is switched on or connected to AC. Check cable. | ||||
| power_supply_absent | STATE_CHANGE | WARNING | no | Message: Power supply {0} is missing. |
| Description: A power supply is missing or absent. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that a power supply is absent. | ||||
| User Action: Check whether the power supply is installed and operational. For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| power_supply_config_mismatch | STATE_CHANGE_EXTERNAL | ERROR | service ticket | Message: Enclosure has an inconsistent power supply configuration. |
| Description: Inconsistent power supply configuration. | ||||
| Cause: The power supplies in the enclosure do not fit to each other. | ||||
| User Action: Verify that all power supplies in all canisters have the same specification. The event can be manually cleared by using the mmhealth event resolve power_supply_config_mismatch command. | ||||
| power_supply_config_ok | STATE_CHANGE_EXTERNAL | INFO | no | Message: Enclosure has a correct power supply configuration. |
| Description: The power supply configuration is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| power_supply_failed | STATE_CHANGE | WARNING | service ticket | Message: Power supply {0} is FAILED. |
| Description: A power supply has failed. | ||||
| Cause: The hardware monitor reports that a power supply has failed. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| power_supply_off | STATE_CHANGE | WARNING | no | Message: Power supply {0} is off. |
| Description: A power supply is off. | ||||
| Cause: The hardware monitor reports that the power supply is turned off. | ||||
| User Action: Make sure that the power supply continues to get power, such as power cable is plugged-in. However, if the problem persists, see IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| power_supply_ok | STATE_CHANGE | INFO | no | Message: Power supply {0} is OK. |
| Description: The power supply state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| power_switched_off | STATE_CHANGE | WARNING | no | Message: Power supply {0} is switched off. |
| Description: A power supply is switched off. | ||||
| Cause: The hardware monitor reports that a power supply is switched off. The requested on-bit is off, which means that the power supply is not manually switched on or is missing by setting the requested on-bit. | ||||
| User Action: Switch on the power supply and check whether it is operational. For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| sideplane_failed | STATE_CHANGE | ERROR | no | Message: Sideplane {0} has failed. |
| Description: A failure of the sideplane is reported. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that the sideplane has failed. | ||||
| User Action: For more information, see the IBM Storage Scale: Problem Determination Guide of the relevant system. | ||||
| sideplane_ok | STATE_CHANGE | INFO | no | Message: Sideplane {0} is OK. |
| Description: The sideplane state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| temp_bus_failed | STATE_CHANGE | WARNING | service ticket | Message: Temperature sensor {0} I2C bus has failed. |
| Description: Temperature sensor I2C bus has failed. | ||||
| Cause: The mmlsenclosure all -L Y command reports that the bus of a temperature sensor has failed. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| temp_high_critical | STATE_CHANGE | WARNING | no | Message: Temperature sensor {0} measured a high temperature value. |
| Description: The measured temperature has exceeded the high critical threshold. | ||||
| Cause: The mmlsenclosure all -L -Y command reports a critical high temperature for a sensor. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| temp_high_warn | STATE_CHANGE | WARNING | no | Message: Temperature sensor {0} has measured a high temperature value. |
| Description: The measured temperature has exceeded the high warning threshold. | ||||
| Cause: The mmlsenclosure all -L -Y command reports a high temperature for a sensor. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| temp_low_critical | STATE_CHANGE | WARNING | no | Message: Temperature sensor {0} has measured a temperature is less than the low critical value. |
| Description: The measured temperature is less than the lower critical threshold. | ||||
| Cause: The mmlsenclosure all -L -Y command reports a critical low temperature for a sensor. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| temp_low_warn | STATE_CHANGE | WARNING | no | Message: Temperature sensor {0} has measured temperature is less than the low warning value. |
| Description: The measured temperature is less than the lower warning threshold. | ||||
| Cause: The mmlsenclosure all -L -Y command reports a temperature is less than the low warning threshold. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| temp_sensor_failed | STATE_CHANGE | WARNING | service ticket | Message: Temperature sensor {0} has failed. |
| Description: A temperature sensor might be broken. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that a temperature sensor has failed. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| temp_sensor_ok | STATE_CHANGE | INFO | no | Message: Temperature sensor {0} is OK. |
| Description: The temperature sensor state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| voltage_bus_failed | STATE_CHANGE | WARNING | service ticket | Message: Voltage sensor {0} communication with the I2C bus has failed. |
| Description: The voltage sensor cannot communicate with the I2C bus. | ||||
| Cause: The mmlsenclosure all -L -Y command reports a bus failure for a voltage sensor. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| voltage_high_critical | STATE_CHANGE | WARNING | no | Message: Voltage sensor {0} measured a high voltage value. |
| Description: The voltage has exceeded the actual high critical threshold for at least one sensor. | ||||
| Cause: The mmlsenclosure all -L -Y command reports high critical voltage for a sensor. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| voltage_high_warn | STATE_CHANGE | WARNING | no | Message: Voltage sensor {0} has measured a high voltage value. |
| Description: The voltage has exceeded the actual high warning threshold for at least one sensor. | ||||
| Cause: The mmlsenclosure all -L -Y command reports high voltage for a sensor. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| voltage_low_critical | STATE_CHANGE | WARNING | no | Message: Voltage sensor {0} has measured a critical low voltage value. |
| Description: The voltage has fallen under the lower critical threshold. | ||||
| Cause: The mmlsenclosure all -L -Y command reports critical low voltage for a sensor. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| voltage_low_warn | STATE_CHANGE | WARNING | no | Message: Voltage sensor {0} has measured a low voltage value. |
| Description: The voltage has fallen under the lower warning threshold. | ||||
| Cause: The mmlsenclosure all -L -Y command reports critical low voltage for a sensor. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| voltage_sensor_failed | STATE_CHANGE | WARNING | service ticket | Message: Voltage sensor {0} is FAILED. |
| Description: A voltage sensor might be broken. | ||||
| Cause: The mmlsenclosure all -L -Y command reports that a voltage sensor state is FAILED. | ||||
| User Action: Issue the mmlsenclosure all -L command. If the warning message persists, then contact IBM support. | ||||
| voltage_sensor_ok | STATE_CHANGE | INFO | no | Message: Voltage sensor {0} is OK. |
| Description: The voltage sensor state is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A |