Dell Drac 5 User Guide

							Using the DRAC 5 SM-CLP Command Line Interface251
Property Names for Power Supply Sensors
CurrentStateThe current state as reported 
by a sensor
ElementNameThe name of the sensor
OtherSensorTypeDesc
riptionIf the sensortype property 
contains a value of 1 (others), 
this property gives additional 
description about that sensor.
Power consumption sensor. 
for powerconsumption
Amperage sensor. for 
amperage
EnabledStateIndicates if the sensor is 
enabled or disabled.
1=Enabled
Table 13-11. Supported Property Names for Power Supply Sensors
Object Property Description
CIM_NumericSensorSystemCreationClas
sNameThe name of the system creation 
class CIM_ComputerSystem)
SystemNameThe service tag of the system, 
which is a unique identifier of a 
system that exists in the 
enterprise environment
CreationClassNameThe creation class name —
CIM_PowerSupply
DeviceIDThe unique ID for the sensor in 
the system.
pwrsupply 1...n Supported Property Names for Fans, Temperature, Numeric Voltage, Power 
Consumption, and Amperage Sensors
Table 13-10. Sensors 
(continued)
Object Property Description 
						

							252Using the DRAC 5 SM-CLP Command Line Interface
Property Names for Intrusion, Battery, Voltage, and Hardware 
Performance Sensors
TotalOutputPowerThe total power output as shown 
on the DRAC user interface
ElementNameName of the particular sensor.
OperationalStatusCurrent operational status of the 
power supply unit.
HealthStateThe health status of the power 
supply unit.
EnabledStateIndicates if the sensor is enabled 
or disabled
1=Enabled
Table 13-12. Supported Property Names for Intrusion, Battery, Voltage, and Hardware 
Performance Sensors
Object Property Description
CIM_NumericSensorSystemCreation
ClassNameThe name of the system creation class—
CIM_ComputerSystem)
SystemNameThe service tag of the system, which is a 
unique identifier of a system that exists 
in the enterprise environment
CreationClassN
ameThe creation class name —CIM_Sensor
DeviceIDUnique ID for the sensor in the system
Intrusion1…n (for intrusion sensor)
Battery1…n (for battery sensor)
Voltage1…n (for voltage sensor)
Hardware performance sensor1…n (for 
hardware performance sensor)
SensorType1=Other
3=Voltage (for voltage sensor) Table 13-11. Supported Property Names for Power Supply Sensors 
(continued)
Object Property Description 
						

							Using the DRAC 5 SM-CLP Command Line Interface253
PossibleStatesThe possible states for the sensor
{ no intrusion,chassis intrusion, drive 
bay intrusion, I/O card area intrusion, 
processor area intrusion, LAN 
disconnect, unauthorized dock, FAN 
area intrusion } (for the Intrusion 
sensor)
{ absent, low, failed, good } (for 
the Battery sensor)
{ good, bad, unknown } (for the 
Vo l t a g e  s e n s o r )
{  Normal, Others, Thermal 
Protection, Cooling Capacity changed, 
Power Capacity changed, User 
Configuration } (for the Hardware 
Performance sensor)
CurrentStateCurrent state reported by the sensor.
ElementNameThe name of the sensor
OtherSensorTyp
eDescriptionIf the sensortype property contains a 
value of 1 (others), this property gives 
additional description about that sensor.
Chassis intrusion sensor (for Intrusion 
sensor)
CMOS battery sensor (for Battery 
sensor)
Hardware performance sensor (for 
Hardware Performance)
 EnabledStateIndicates if the sensor is enabled or 
disabled
1=Enabled (for all sensors) Table 13-12. Supported Property Names for Intrusion, Battery, Voltage, and Hardware 
Performance Sensors 
(continued)
Object Property Description 
						

							254Using the DRAC 5 SM-CLP Command Line Interface
Property Names for Fan and Power Supply Redundancy Set Sensors
Property Names for Chassis Sensors
Table 13-13. Supported Property Names for Fan and Power Supply Redundancy 
Set Sensors
Object Property Description
CIM_RedundancySetInstanceIDInstance number
RedundancyStatusThe redundancy status.
TypeOfSet3=Load balanced (for fan 
redundancy)
4=Sparing (for Power Supply 
redundancy)
MinNumberNeeded0=Unknown
ElementNameName of the sensor
Table 13-14. Supported Property Names for Chassis Sensors
Object Property Description
CIM_ChassisCreationClassName The name of the creation 
class—CIM_Chassis
PackageType Type of package
3=Chassis
ChassisPackageType Chassis package type
17=Main system chassis
ManufacturerManufacturer
Dell
ModelThe model name of the 
system
ElementNameElement name 
						

							Using the DRAC 5 SM-CLP Command Line Interface255
Property Names for Power Management Service
Using the set verb, you can set the power state of the system. for example, to 
turn on the system if it is off:
set powerstate=2
Table 13-15. Supported Property Names for Power Management Service
Object Property Description
CIM_PowerManagement
ServiceCreationClassN
ameThe name of the creation class—
CIM_PowerManagementService
Name IPMI Power Service
ElementNameDell Server Power Management 
Service
powerstateCurrent power state of the 
system.
2=On
6=Off
Can be set to the following 
values:
2=Power On
6=Power Off
5=Power Reset
9=Powercycle the system 
						

							256Using the DRAC 5 SM-CLP Command Line Interface
Property Names for Power Capability
Table 13-16. Supported Property Names for Power Capability
Object Property Description
CIM_PowerManagement
CapabilitiesInstanceID Unique instance ID for the 
power capabilities
PowerChangeCapa
bilities3=Power State Settable
ElementNameDell Server Power Management 
Service
PowerStatesSupp
orted2=Power On
6=Power Off
5=Power Reset
9=Powercycle the system 
						

							Monitoring and Alert Management257
14
Monitoring and Alert Management
This section explains how to monitor the DRAC 5 and procedures to 
configure your system and the DRAC 5 to receive alerts.
Configuring the Managed System to Capture the Last Crash Screen
Before the DRAC 5 can capture the last crash screen, you must configure the 
managed system with the following prerequisites.
1
Install the managed system software. For more information about installing 
the managed system software, see the 
Server Administrator Users Guide.
2Run a supported Microsoft Windows operating system with the Windows 
automatically reboot feature deselected in the 
Windows Startup and 
Recovery Settings
.
3Enable the Last Crash Screen (disabled by default).
To enable using local RACADM, open a command prompt and type the 
following commands:
racadm config -g cfgRacTuning -o 
cfgRacTuneAsrEnable 1
4
Enable the Auto Recovery timer and set the Auto Recovery action to 
Reset, Po w e r  O ff, or Po w e r  C y cl e. To configure the Auto Recovery timer, 
you must use Server Administrator or IT Assistant. 
For information about how to configure the 
Auto Recovery timer, see the 
Server Administrator Users Guide. To ensure that the last crash screen can 
be captured, the 
Auto Recovery timer must be set to 60 seconds or greater. 
The default setting is 480 seconds.
The last crash screen is not available when the 
Auto Recovery action is set 
to 
Shutdown or Po w e r  C y c l e if the managed system is powered off. 
						

							258Monitoring and Alert Management
Disabling the Windows Automatic Reboot Option
To ensure that the DRAC 5 Web-based interface last crash screen feature 
works properly, disable the Automatic Reboot option on managed systems 
running the Microsoft Windows Server 2003 and Windows 2000 Server 
operating systems.
Disabling the Automatic Reboot Option in Windows Server 2003
1Open the Windows Control Panel and double-click the System icon.
2Click the Advanced tab.
3Under Startup and Recovery, click Settings.
4Deselect the Automatically Reboot check box.
5Click OK twice.
Disabling the Automatic Reboot Option in Windows 2000 Server
1Open the Windows Control Panel and double-click the System icon.
2Click the Advanced tab.
3Click the Startup and Recovery... button.
4Deselect the Automatically Reboot check box.
Configuring Platform Events
Platform event configuration provides a mechanism for configuring the 
remote access device to perform selected actions on certain event messages. 
These actions include reboot, power cycle, power off, power reduction, and 
triggering an alert (Platform Events Trap [PET] and/or e-mail).
The filterable Platform Events include the following:
•Fan Probe Failure
• Battery Probe Warning
• Battery Probe Failure
• Discrete Voltage Probe Failure
• Temperature Probe Warning
• Temperature Probe Failure
• Chassis Intrusion Detected 
						

							Monitoring and Alert Management259
• Redundancy Degraded
• Redundancy Lost
• Processor Warning
• Processor Failure
• Processor Absent
• PS/VRM/D2D Warning
• PS/VRM/D2D Failure
• Power Supply Absent
• Hardware Log Failure
• Automatic System Recovery
• System Power Probe Warning
• System Power Probe Failure
When a platform event occurs (for example, a fan probe failure), a system 
event is generated and recorded in the System Event Log (SEL). If this event 
matches a platform event filter (PEF) in the Platform Event Filters list in the 
Web-based interface and you have configured this filter to generate an alert 
(PET or e-mail), then a PET or e-mail alert is sent to a set of one or more 
configured destinations. 
If the same platform event filter is also configured to perform an action (such 
as rebooting the system), the action is performed.
Configuring Platform Event Filters (PEF)
Configure your platform event filters before you configure the platform event 
traps or e-mail alert settings. 
Configuring PEF Using the Web User Interface
1Log in to the remote system using a supported Web browser. See 
Accessing the Web-Based Interface on page 48.
2Click the Alert Management tab and then click Platform Events.
3Enable global alerts. 
aClick Alert Management and select Platform Events.
bSelect the Enable Platform Event Filter Alert check box. 
						

							260Monitoring and Alert Management
4Under Platform Events Filters Configuration, select the Enable Platform 
Event Filter alerts 
check box and then click Apply Changes. 
5Under Platform Event Filters List, click a filter that you want to 
configure.
6In the Set Platform Events page, make the appropriate selections and then 
click 
Apply Changes.
 NOTE: Generate Alert must be enabled for an alert to be sent to any valid, 
configured destination (PET or e-mail).
Configuring PEF Using the RACADM CLI
1Enable PEF.
Open a command prompt, type the following command, and press 
:
racadm config -g cfgIpmiPef -o cfgIpmiPefEnable -i 
1 1
where 1 and 1 are the PEF index and the enable/disable selection, 
respectively.
The PEF index can be a value from 1 through 17. The enable/disable 
selection can be set to 1 (Enabled) or 0 (Disabled). 
For example, to enable PEF with index 5, type the following command:
racadm config -g cfgIpmiPef -o cfgIpmiPefEnable -i 
5 1
2
Configure your PEF actions.
At the command prompt, type the following command and press 
:
racadm config -g cfgIpmiPef -i  -o 
cfgIpmiPefAction 
where the  values bits are as follows:
•
 value bit 0 – 1 = enable alert action, 0 = disable alert
•
 value bit 1 – 1 = power off; 0 = no power off
•
 value bit 2 – 1 = reboot; 0 = no reboot