Drive Slot Sensor For Storage Drive Presence Was Asserted

4/10/2022by admin

trepfipelomafec.netlify.com › Drive Slot Sensor For Storage Drive Presence Was Asserted ▆ ▆ ▆

RE: System Software Event: Drive Slot Sensor, drive fault was asserted. If you connect the drive to another slot of the parent company, I will have to make another RAID-1 arrangement? If so, will I have to reinstall my system again. IPMI disk drive fault and presence sensors—Sends the sensor results to Cisco UCS Manager. Disk drive fault LED control and associated IPMI sensors—Controls disk drive fault LED states (on/off) and relays the states to Cisco UCS Manager. Cisco UCS Manager cannot monitor disk drives in any other blade server or rack-mount server.

Drive Slot Sensor For Storage Drive Fault Was Asserted Dell

Section: Configuration (5)
Asserted

Updated: 2020-09-03
IndexReturn to Main Contents

NAME

freeipmi_interpret_sensor.conf - specify sensor interpretation rules

DESCRIPTION

The/etc/freeipmi//freeipmi_interpret_sensor.confdefines how IPMI sensors should beinterpreted. IPMI based sensors specify a number ofstates/thresholds when they are read. Based on thosestates/thresholds, libraries and tools such as Presence

libfreeipmi(3),libipmimonitoring(3)andipmi-sensors(8)can report if a sensor reading is 'good' or 'bad' via a report of aNOMINAL, WARNING, or CRITICAL state.

Each of the states listed below are (hopefully) descriptive enoughto describe the state conditions that may be set/unset for eachsensor type. For more detailed information on each of theindividual states listed below, please see the IPMI Specification'Sensor and Event Code Tables'.Ipmi-sensors(8)can be used to determine the sensor types and the states/thresholdsthat exist on a system by outputting very verbose output and seeingwhat types of Assertion or Deassertion events are possible.

The possible values for all states/thresholds below are:

Nominal - Signal Nominal reading if state/threshold tripped

Warning - Signal Warning reading if state/treshold tripped

Critical - Signal Critical reading if state/threshold tripped

Not all IPMI sensor types and event types are currently supported. Ifyou would like more to be supported, please e-mail the FreeIPMImailing list.

The default values selected for individual states/thresholds beingtripped are based on best guesses and motherboards being analyzed.If you think they should be changed, please e-mail the FreeIPMImailing list to discuss what the defaults should be.

Most default interpretations can be determined quite easily and canmeet the needs of most users. For example, a reading of'Performance_Met' is normally better than 'Performance_Lags'.However, some sensors can be ambiguous and depend completely on themanufacturer. For example, 'State_Asserted' vs. 'State_Deasserted'are completely at the interpretation of the vendor. Users are advisedto adjust the interpretations below as needed for their machines.

Every group of state conditions below includes a configuration for'No_Event'. This is the condition under which no sensor states/eventshave occurred or are triggered. Under most conditions, a mapping to'Nominal' is preferred. However, under some circumstances, it may beuseful to report something else. For example, if a sensor on aparticular motherboard is required to report a state/event, a nosensor state condition could indicate a broken a sensor. This ishighly dependent on the motherboard.

FORMAT

The configuration options that can be specified in the configurationfile are listed below. Each configuration option must be listed on aseparate line. Arguments for an option are separated by any amount ofwhitespace. Multiple arguments are also separated by whitespace.Comments can be marked by using the pound sign ('#') character, andlines can be continued on the next using backslash (').

OPTIONS

IPMI_OS_Boot_No_EventDefaults to Nominal.IPMI_OS_Boot_A_Boot_CompletedDefaults to Nominal.IPMI_OS_Boot_C_Boot_CompletedDefaults to Nominal.IPMI_OS_Boot_PXE_Boot_CompletedDefaults to Nominal.IPMI_OS_Boot_Diagnostic_Boot_CompletedDefaults to Nominal.IPMI_OS_Boot_CD_ROM_Boot_CompletedDefaults to Nominal.IPMI_OS_Boot_ROM_Boot_CompletedDefaults to Nominal.IPMI_OS_Boot_Boot_Completed_Boot_Device_Not_SpecifiedDefaults to Warning.IPMI_OS_Boot_Base_OS_Hypervisor_Installation_StartedDefaults to Nominal.IPMI_OS_Boot_Base_OS_Hypervisor_Installation_CompletedDefaults to Nominal.IPMI_OS_Boot_Base_OS_Hypervisor_Installation_AbortedDefaults to Warning.IPMI_OS_Boot_Base_OS_Hypervisor_Installation_FailedDefaults to Critical.

IPMI_OS_Critical_Stop_State

The following states correspond to OS Critical Stop sensors that report anassertion or deassertion.

IPMI_OS_Critical_Stop_State_No_Event: Defaults to Nominal.
IPMI_OS_Critical_Stop_State_Deasserted: Defaults to Nominal.
IPMI_OS_Critical_Stop_State_Asserted: Defaults to Critical.

IPMI_Slot_Connector

The following states correspond to Slot Connector sensors w/Slot Connector specific output states.

IPMI_Slot_Connector_No_Event: Defaults to Nominal.
IPMI_Slot_Connector_Fault_Status_Asserted: Defaults to Critical.
IPMI_Slot_Connector_Identify_Status_Asserted: Defaults to Warning.
IPMI_Slot_Connector_Slot_Connector_Device_Installed_Attached: Defaults to Nominal.
IPMI_Slot_Connector_Slot_Connector_Ready_For_Device_Installation: Defaults to Nominal.
IPMI_Slot_Connector_Slot_Connector_Ready_For_Device_Removal: Defaults to Nominal.
IPMI_Slot_Connector_Slot_Power_Is_Off: Defaults to Nominal.
IPMI_Slot_Connector_Slot_Connector_Device_Removal_Request: Defaults to Warning.
IPMI_Slot_Connector_Interlock_Asserted: Defaults to Warning.
IPMI_Slot_Connector_Slot_Is_Disabled: Defaults to Warning.
IPMI_Slot_Connector_Slot_Holds_Spare_Device: Defaults to Nominal.

IPMI_Slot_Connector_Transition_Severity

The following states correspond to Slot Connector sensors that report ondevice severity.

IPMI_Slot_Connector_Transition_Severity_No_Event: Defaults to Nominal.
IPMI_Slot_Connector_Transition_Severity_Transition_To_OK: Defaults to Nominal.
IPMI_Slot_Connector_Transition_Severity_Transition_To_Non_Critical_From_OK: Defaults to Warning.
IPMI_Slot_Connector_Transition_Severity_Transition_To_Critical_From_Less_Severe: Defaults to Critical.
IPMI_Slot_Connector_Transition_Severity_Transition_To_Non_Recoverable_From_Less_Severe: Defaults to Critical.
IPMI_Slot_Connector_Transition_Severity_Transition_To_Non_Critical_From_More_Severe: Defaults to Warning.
IPMI_Slot_Connector_Transition_Severity_Transition_To_Critical_From_Non_Recoverable: Defaults to Critical.
IPMI_Slot_Connector_Transition_Severity_Transition_To_Non_Recoverable: Defaults to Critical.
IPMI_Slot_Connector_Transition_Severity_Monitor: Defaults to Warning.
IPMI_Slot_Connector_Transition_Severity_Informational: Defaults to Nominal.

IPMI_System_ACPI_Power_State

IPMI_System_ACPI_Power_State_No_Event: Defaults to Nominal.
IPMI_System_ACPI_Power_State_S0_G0: Defaults to Nominal.
IPMI_System_ACPI_Power_State_S1: Defaults to Nominal.
IPMI_System_ACPI_Power_State_S2: Defaults to Nominal.
IPMI_System_ACPI_Power_State_S3: Defaults to Nominal.
IPMI_System_ACPI_Power_State_S4: Defaults to Nominal.
IPMI_System_ACPI_Power_State_S5_G2: Defaults to Nominal.
IPMI_System_ACPI_Power_State_S4_S5_Soft_Off: Defaults to Nominal.
IPMI_System_ACPI_Power_State_G3_Mechanical_Off: Defaults to Nominal.
IPMI_System_ACPI_Power_State_Sleeping_in_an_S1_S2_or_S3_States: Defaults to Nominal.
IPMI_System_ACPI_Power_State_G1_Sleeping: Defaults to Nominal.
IPMI_System_ACPI_Power_State_S5_Entered_By_Override: Defaults to Nominal.
IPMI_System_ACPI_Power_State_Legacy_ON_State: Defaults to Nominal.
IPMI_System_ACPI_Power_State_Legacy_OFF_State: Defaults to Nominal.
IPMI_System_ACPI_Power_State_Unspecified: Defaults to Critical.
IPMI_System_ACPI_Power_State_Unknown: Defaults to Critical.

IPMI_Watchdog2

The following states correspond to Watchdog 2 sensors w/Watchdog 2 specific output states.

IPMI_Watchdog2_No_Event: Defaults to Nominal.
IPMI_Watchdog2_Timer_Expired: Defaults to Warning.
IPMI_Watchdog2_Hard_Reset: Defaults to Critical.
IPMI_Watchdog2_Power_Down: Defaults to Critical.
IPMI_Watchdog2_Power_Cycle: Defaults to Critical.
IPMI_Watchdog2_Reserved1: Defaults to Nominal.
IPMI_Watchdog2_Reserved2: Defaults to Nominal.
IPMI_Watchdog2_Reserved3: Defaults to Nominal.
IPMI_Watchdog2_Reserved4: Defaults to Nominal.
IPMI_Watchdog2_Timer_Interrupt: Defaults to Warning.

IPMI_Platform_Alert_State

The following states correspond to Platform Alert sensors that report anassertion or deassertion.

IPMI_Platform_Alert_State_No_Event: Defaults to Nominal.
IPMI_Platform_Alert_State_Deasserted: Defaults to Nominal.
IPMI_Platform_Alert_State_Asserted: Defaults to Critical.

IPMI_Entity_Presence

The following states correspond to Entity Presence sensors w/Entity Presence specific output states.

IPMI_Entity_Presence_No_Event: Defaults to Nominal.
IPMI_Entity_Presence_Entity_Present: Defaults to Nominal.
IPMI_Entity_Presence_Entity_Absent: Defaults to Critical.
IPMI_Entity_Presence_Entity_Disabled: Defaults to Critical.

IPMI_Entity_Presence_Device_Present

The following states correspond to Entity Presence sensors that report ondevice installation.

IPMI_Entity_Presence_Device_Present_No_Event: Defaults to Nominal.
IPMI_Entity_Presence_Device_Present_Device_Removed_Device_Absent: Defaults to Nominal.
IPMI_Entity_Presence_Device_Present_Device_Inserted_Device_Present: Defaults to Nominal.

IPMI_Management_Subsystem_Health

The following states correspond to Management Subsystem Health sensors w/Management Subsystem Health specific output states.

IPMI_Management_Subsystem_Health_No_Event: Defaults to Nominal.
IPMI_Management_Subsystem_Health_Sensor_Access_Degraded_Or_Unavailable: Defaults to Critical.
IPMI_Management_Subsystem_Health_Controller_Access_Degraded_Or_Unavailable: Defaults to Critical.
IPMI_Management_Subsystem_Health_Management_Controller_Off_Line: Defaults to Critical.
IPMI_Management_Subsystem_Health_Management_Controller_Unavailable: Defaults to Critical.
IPMI_Management_Subsystem_Health_Sensor_Failure: Defaults to Critical.
IPMI_Management_Subsystem_Health_FRU_Failure: Defaults to Critical.

IPMI_Battery

The following states correspond to Battery sensors w/Battery specific output states.

IPMI_Battery_No_Event: Defaults to Nominal.
IPMI_Battery_Battery_Low: Defaults to Warning.
IPMI_Battery_Battery_Failed: Defaults to Critical.
IPMI_Battery_Battery_Presence_Detected: Defaults to Nominal.

IPMI_Session_Audit

The following states correspond to Session Audit sensors w/Session_Audit specific output states.

IPMI_Version_Change_No_Event: Defaults to Nominal.
IPMI_Version_Change_Hardware_Change_Detected_With_Associated_Entity: Defaults to Warning.
IPMI_Version_Change_Firmware_Or_Software_Change_Detected_With_Associated_Entity: Defaults to Warning.
IPMI_Version_Change_Hardware_Incompatability_Detected_With_Associated_Entity: Defaults to Critical.
IPMI_Version_Change_Firmware_Or_Software_Incompatability_Detected_With_Associated_Entity: Defaults to Critical.
IPMI_Version_Change_Entity_Is_Of_An_Invalid_Or_Unsupported_Hardware_Version: Defaults to Critical.
IPMI_Version_Change_Entity_Contains_An_Invalid_Or_Unsupported_Firmware_Or_Software_Version: Defaults to Critical.
IPMI_Version_Change_Hardware_Change_Detected_With_Associated_Entity_Was_Successful: Defaults to Nominal.
IPMI_Version_Change_Software_Or_FW_Change_Detected_With_Associated_Entity_Was_Successful: Defaults to Nominal.

IPMI_FRU_State

The following states correspond to FRU State sensors w/FRU State specific output states.

IPMI_FRU_State_No_Event: Defaults to Nominal.
IPMI_FRU_State_FRU_Not_Installed: Defaults to Critical.
IPMI_FRU_State_FRU_Inactive: Defaults to Critical.
IPMI_FRU_State_FRU_Activation_Requested: Defaults to Warning.
IPMI_FRU_State_FRU_Activation_In_Progress: Defaults to Warning.
IPMI_FRU_State_FRU_Active: Defaults to Nominal.
IPMI_FRU_State_FRU_Deactivation_Requested: Defaults to Warning.
IPMI_FRU_State_FRU_Deactivation_In_Progress: Defaults to Warning.
IPMI_FRU_State_FRU_Communication_Lost: Defaults to Critical.

IPMI_OEM

The following configuration options can be used to configure OEMspecific interpretations. Users should be aware that bothIPMI_OEM_Bitmask and IPMI_OEM_Value can be configured foran identical Manufacturer-ID, Product-ID,Event-Reading-Type-Code, and Sensor-Type combination. Allinterpretations rules for a specific combination are iterated throughand the worst resulting sensor state is returned (i.e. Warning <Nominal, Critical < Warning). If no match is found, no sensor stateis returned for the OEM sensor reading.For each of the configuration options below, <Manufacturer-ID>is the numeric IANA manufacturer ID for the manufacturer in question.The <Product-ID> is one or more numeric IDs representing themanufacturer's product. The <Product-ID> can be listed as asingle numeric number (e.g. 1234), a range of IDs separated by a dash(e.g. 12-20), or a list of specific product IDs separted by a plus(e.g. 12+19+22). Both the Manufacturer-ID andProduct-ID can be found usingbmc-info(8).Multiple <Manufacturer-ID> and <Product-ID> pairs can beinput separated by commas.The Event-Reading-Type-Code and Sensor-Type need notbe OEM types. They may be non-OEM types and used to provideinterpretation rules for sensors that may be behaving outside thestandard of the IPMI specification.

IPMI_OEM_Bitmask<Manufacturer-ID>:<Product-ID>,... Event-Reading-Type-CodeSensor-TypeSensor-Event-BitmaskState: IPMI_OEM_Bitmask can be used to configure a state interpretationfor a specific Manufacturer-ID, Product-ID,Event-Reading-Type-Code, and Sensor-Type combination and aspecific bitmask of the Sensor-Event. The state will beaccepted as the sensor interpretation if the inputted bitmask ANDedwith the actual sensor event bitmask reading is true. As a specialcase, the state will be accepted if the inputted bitmask and theactual sensor event bitmask are both 0. In other words, if no eventshappened, an OEM interpretation can be configured for this case byinputing a bitmask of 0x0000.
IPMI_OEM_Value<Manufacturer-ID>:<Product-ID>,... Event-Reading-Type-CodeSensor-TypeSensor-Event-Bitmask-ValueState: IPMI_OEM_Value can be used to configure a state interpretationfor a specific Manufacturer-ID, Product-ID,Event-Reading-Type-Code, and Sensor-Type combination and aspecific value for the Sensor-Event-Bitmask. The state will beaccepted as the sensor interpretation if the inputted bitmask value isequal to the actual sensor event bitmask reading.

FILES

/etc/freeipmi//freeipmi_interpret_sensor.conf Slot

REPORTING BUGS

Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.

COPYRIGHT

This library is free software; you can redistribute it and/or modifyit under the terms of the GNU General Public License as published bythe Free Software Foundation; either version 3 of the License, or (atyour option) any later version.

Index

NAME
DESCRIPTION
FORMAT
OPTIONS
FILES
REPORTING BUGS
COPYRIGHT
SEE ALSO

This document was created byman2html,using the manual pages.

Drive Slot Sensor For Storage Drive Fault Was Asserted Dell

Time: 17:11:55 GMT, September 04, 2020