User's Manual

108 omconfig: Managing Components Using the Instrumentation Service
Typ e
Type refers to the name of the component(s) involved in the event.
Table 4-25 shows the valid parameters for system event types.
Severity
In the context of configuring events, severity determines how severe an event
must be before Server Administrator notifies you of the event for a
component type. When there are multiple components of the same type in
the same system chassis, you can specify whether you want to be notified for
event severity according to the number of the component by using the
index=
<n> parameter. Table 4-26 shows the valid severity parameters.
Table 4-25. System Event Type Parameters
name=value pair Description
type=accords Configures events for AC power cords.
type=battery Configures events for battery.
type=all Configures events for all device types.
type=fanenclosures Configures events for fan enclosures.
type=fans Configures events for fans.
type=intrusion Configures events for chassis intrusion.
type=log Configures events for logs.
type=memory Configures events for memory.
type=powersupplies Configures events for power supplies.
type=redundancy Configures events for redundancy.
type=systempower Configures events for system power.
type=temps Configures events for temperatures.
type=volts Configures events for voltages.
Table 4-26. System Event Severity Parameters
Command Result Description
omconfig system events type=
<component name> severity=info
or
omconfig servermodule events type=
<component name> severity=info
Enables notification
for informational,
warning, and critical
events.
Least restrictive form of event
notification.
omconfig system events type=
<component name> severity=warning
or
omconfig servermodule events type=
<component name> severity=warning
Enables notification
for warning and critical
events.
Omits informational event
notification, for example, when
a component returns to normal
status.