IBM® Carrier Grade Server X3650 T
Revision 3.0
48
SysConDevInsert + SysConKeyInsert:
0001 01/20/05 04:28:55 BMC 21 Slot/Connector 00 Inserted 00 [02 08 21]
SysConDevMnt + SysConKeyMnt:
0002 01/20/05 04:28:56 BMC 21 Slot/Connector 00 InsReady 00 [03 08 21]
SysConDevChange + SysConKeyChange:
0005 01/20/05 04:39:57 BMC 21 Slot/Connector 00 Interlock 00 [07 08 21]
SysConDevUnMnt + SysConKeyUnMnt:
0008 01/20/05 04:41:02 BMC 21 Slot/Connector 00 RemReady 00 [04 08 11]
SysConDevRemove + SysConKeyRemove:
0007 01/20/05 04:40:57 BMC 21 Slot/Connector 00 RemRequest 00 [06 08 11]
SysConDevMntFail + SysConKeyMntFail:
000b 01/20/05 04:59:51 BMC 21 Slot/Connector 00 Fault 00 [00 08 11]
12.2.3 SysCon Event Logging and Notification Policies
To enable one or more of the following logging/notification actions for a given event type, the following
entry must be included in with the specific event type/device type section of the policysettings.xml file.
Entry in policysettings.xml Description, requirements, additional XML settings
LogUsingSEL System event log (SEL) (Requires BMC firmware log and IPMI
driver). Severity may be specified as Crit, Major, Minor, or Info.
LogUsingSyslog Linux SysLog Severity may be specified as Emerg, Alert, Crit, Err,
Warning, Notice, Info, or Debug.
AlertUsingSNMP SNMP Trap Notification (requires Net-SNMP). Severity may be
specified as Crit, Major, Minor, or Info.
AlertUsingTAM Telco Alarms Manager LED/Relay activation (Requires TAM
hardware and software). Severity may be specified as Crit, Major, or
Minor.
12.2.4 SysCon Actions on Events
The SysCon service allows three types of actions to take place on any event-type/device-type condition.
The polictsettings.xml allows for the configuration of these actions.
Shutdown/Reboot Action
A shutdown can be specified with a “Shutdown” action or a system reset can be specified with a
“Reboot” action. You can not specify both reboot and shutdown for the same event-type/device-type
combination.
Mount Retry Action
A “Retry” action only applies to the SysConDevUnMnt and SysConKeyUnMnt events. This action
instructs the SysCon daemon to remount the SysCon device (or a SysCon key) if it detects that the state
of the device/key has changed from mounted to unmounted. If used in conjunctions with a
Shutdown/Reboot action, the mount retry will be attempted and the Shutdown/Reboot action will occur in
case of remount failure.
Call Script Action
The “CallScript” instructs the SysCon daemon to call a custom script (which can also be specified for
each event type/device type combination).
12.2.5 SysCon Event/Notification API and Query Languages
Daemon registration and notification services
To Next Page
Loading...
Need help?
General