Reference Guide

Dell OpenManage Client Instrumentation Reference Guide
file:///T|/htdocs/SOFTWARE/smcliins/cli80/EN/refgd/index.htm[10/19/2012 9:56:27 AM]
Note: Alerts are supported only in the standard namespace.
The Distributed Management Task Force (DMTF) has released the Alert Standard Format (ASF), which defines alerting and remote control interfaces that
enable management of networked systems when their operating system is absent. This includes a networked computer that has an inactive or inoperable
operating system or that is in a low-power system sleep state. The ASF specification is available at www.dmtf.org. ASF documentation is provided with Dell
systems that support ASF.
There are three settings in the system BIOS that OMCI allows for configuration:
Off — All ASF 2.0 features are turned off
Alert Only — ASF 2.0 alert is the only feature that is turned on
On — Alerts and remote control are turned on
The system network interface card (NIC) and basic input/output system (BIOS) support ASF 2.0. If the BIOS allows for any ASF 2.0 configuration, then the
BIOS settings are exposed through the Microsoft Windows Management Instrumentation (WMI) by OMCI.
OMCI Alerting
Local alerting involves displaying user messages (this feature is off by default) and writing to the Windows event log. Remote alerting is accomplished through
WMI indications. When OMCI detects an event, it generates an alert, which can be transmitted through the WMI service to a remote management application
that is subscribed to that alert type.
When an alert is generated, OMCI supports three types of notification:
NT event log
Remote
Console (off by default)
In OMCI, each type of event (for example, CurrentProbe, TemperatureProbe, Smart, and so on) that gets logged is provided with an unique event ID number.
The events have unique IDs to allow log scraping; this way you can programmatically look at the event log and determine what OMCI events have occurred.
Table 2-1: Events Polled by OMCI
OMCI Event (Windows Event Log
Number)
Description Severity Level
FanProbe
(1103)
A cooling device has exceeded a minor threshold.
MINOR
DiskSizeIncreased
(2038)
The size of at least one hard drive has increased.
WARNING_DEGRADED
DiskSizeDecreased
(2039)
The size of at least one hard drive has decreased.
WARNING_DEGRADED
CurrentProbe
(1203)
An electrical current probe has exceeded a minor threshold.
MINOR
DiskCapacity
(2034)
One of the hard drives is running out of free space.
In the current version, two user-defined thresholds are used.
An event is generated only when the conditions of both
thresholds are met. The first threshold, expressed as an
absolute value in megabytes, specifies the size of drives to be
monitored. Drives with a capacity smaller than the specified
size are ignored. The second threshold is expressed as a
percentage of the drive size. An event is generated when
available free space on one of the monitored drives falls below
this percentage.
MINOR
EccMemory
(1403)
A memory checksum failure has occurred. MINOR
MemorySizeIncreased
(2032)
The memory size has been increased. WARNING_DEGRADED
MemorySizeDecreased
(2033)
The memory size has been decreased.
WARNING_DEGRADED
NumberOfDisksIncreased
(2030)
A hard drive has been added. WARNING_DEGRADED
NumberOfDisksDecreased
(2031)
A hard drive has been removed. WARNING_DEGRADED
NumberOfProcessorsDecreased
(2036)
A processor has been removed. WARNING_DEGRADED
SMART
(2037)
A hard drive condition has occurred that may eventually lead to a drive failure. MAJOR
ChassisIntrusion
(1253)
System Chassis Intrusion alert. WARNING_DEGRADED
TemperatureProbe
(1054)
A temperature probe has exceeded a critical threshold. CRITICAL
VoltageProbe
(1153)
A voltage probe has exceeded a minor threshold. MINOR
NumberOfProcessorsIncreased
(2035)
Number of processors on the system has increased WARNING_DEGRADED
Sample Scripts and BIOS Settings
WMI Sample Scripts
Getting BIOS Settings
Below is a sample VBScript to get the current list of BIOS Settings on a client system.