CLI Guide
There are four parameters in the name=value pair component of the omcong system events command:
• Source
• Type
• Severity
• Index
Source
At present, source=snmptraps is a required name=value pair because SNMP is currently the only supported source of event notication for
the system’s components.
omconfig system events source=snmptraps
or
omconfig servermodule events source=snmptraps
Type
Type refers to the name of the component(s) involved in the event. The following table displays the valid parameters for system event
types.
Table 72. System Event Type Parameters
name=value pair Description
type=accords Congures events for AC power cords.
type=battery Congures events for battery.
type=all Congures events for all device types.
type=fanenclosures Congures events for fan enclosures.
type=fans Congures events for fans.
type=intrusion Congures events for chassis intrusion.
type=log Congures events for logs.
type=memory Congures events for memory.
type=powersupplies Congures events for power supplies.
type=redundancy Congures events for redundancy.
type=systempower Congures events for system power.
type=temps Congures events for temperatures.
type=volts Congures events for voltages.
type=systempeakpower Congures events for system peak power.
type=removableashmedia Congures events for removable ash media.
Severity
In the context of conguring events, severity determines how severe an event is, before Server Administrator noties 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
114
Omcong Managing Components Using The Instrumentation Service