Events Reference PDF

IBM Systems
IBM Systems Director
Events Reference
Version 6.1.1
GC30-4172-02

IBM Systems
IBM Systems Director
Events Reference
Version 6.1.1
GC30-4172-02
Note
Before using this information and the product it supports, read the information in “Notices” on
page 289.
© Copyright IBM Corporation 1999, 2010.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Conventions and terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Publications and related information . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Web resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
How to send your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Chapter 1. Hardware platform events . . . . . . . . . . . . . . . . . . . . . . . 1

IBM BladeCenter and System x platform-specific events . . . . . . . . . . . . . . . . . . . . 18
CIM events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MPA events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
IBM Power platform-specific events . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Computer System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Fibre Channel Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Optical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
PCI Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Physical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
USB Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
IBM System Storage platform-specific events . . . . . . . . . . . . . . . . . . . . . . . . 154
Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
RAID Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Storage Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Storage Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Storage Volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
PET events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
PET > Environmental. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
PET > Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
PET > Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
PET > System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
SNMP events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
ibmSystemMIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
ibmSystemRaid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Chapter 2. IBM Systems Director tasks, software, and operating system events. . . . 209
Director > Director Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Director > Director Agent > Process Monitors . . . . . . . . . . . . . . . . . . . . . . 209
Director > Director Agent > Resource Monitors . . . . . . . . . . . . . . . . . . . . . . 211
Director > Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Director > Scheduler > Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Director > Scheduler > System . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
IBM Systems Director Program events . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Agent events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Automation Event Actions events . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Status events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
System Configuration events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Virtualization events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Director > Correlation > Common Agent events . . . . . . . . . . . . . . . . . . . . . . . 232
Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
© Copyright IBM Corp. 1999, 2010 iii

CIM > Windows NT Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
CIM > Windows NT Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
CIM > Windows Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Windows Event Log events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Chapter 3. Sources of events in an IBM Systems Director environment . . . . . . . 235

CIM event sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
The MPA event source in IBM Systems Director, version 5.10 and later . . . . . . . . . . . . . . . 235
PET event source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
ibmSystemMIB event source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Chapter 4. Extended details and variable-binding information . . . . . . . . . . . 237

Extended details for CIM events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Extended details for HMC CIM events . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Extended details for the Director > Director Agent events . . . . . . . . . . . . . . . . . . . 237
Extended details for the IBM Systems Director Program > Security events . . . . . . . . . . . . . . 238
Extended details for MPA events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Extended details for PET events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Variable-binding information for IBM Systems Director SNMP events . . . . . . . . . . . . . . . 239
Chapter 5. CIM indications in IBM Systems Director . . . . . . . . . . . . . . . . 241

IBM_MgmtHwLogStatus CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 241
IBMx_AutomaticServerRestartEvent CIM indication . . . . . . . . . . . . . . . . . . . . . 242
IBMPSG_ChassisEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 242
IBMPSG_DASDBackplaneEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . 243
IBMPSG_ErrorLogEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 243
IBMPSG_FanEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
IBMPSG_GenericFanEvent CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . 244
IBMPSG_GenericVoltageEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . 245
IBMPSG_LeaseExpirationEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . 245
IBMPSG_MemoryPFEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 246
IBMPSG_NetworkAdapterFailedEvent CIM indication. . . . . . . . . . . . . . . . . . . . . 246
IBMPSG_NetworkAdapterOfflineEvent CIM indication . . . . . . . . . . . . . . . . . . . . 247
IBMPSG_NetworkAdapterOnlineEvent CIM indication . . . . . . . . . . . . . . . . . . . . 247
IBMPSG_PFAEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
IBMPSG_PowerSupplyEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 248
IBMPSG_ProcessorPFEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 249
IBMPSG_RedundantNetworkAdapterEvent CIM indication . . . . . . . . . . . . . . . . . . . 249
IBMPSG_RedundantNetworkAdapterSwitchbackEvent CIM indication . . . . . . . . . . . . . . . 250
IBMPSG_RedundantNetworkAdapterSwitchoverEvent CIM indication . . . . . . . . . . . . . . . 250
IBMPSG_RemoteLoginEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 251
IBMPSG_SMARTEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 251
IBMPSG_SPPowerSupplyEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . 251
IBMPSG_StorageEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Adjusting disk-space event threshold values on Linux systems . . . . . . . . . . . . . . . . . 253
Adjusting disk-space event threshold values on Windows systems . . . . . . . . . . . . . . . 253
IBMPSG_TemperatureEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 254
IBMPSG_VoltageEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 254
IBMPSG_WarrantyExpirationEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . 255
ADPT_ArrayFlashCopyComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . 255
ADPT_ArrayFlashCopyDetected CIM indication. . . . . . . . . . . . . . . . . . . . . . . 255
ADPT_ArrayFlashCopyFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 256
ADPT_ArrayRebuildComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . 256
ADPT_ArrayRebuildDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . 256
ADPT_ArrayRebuildFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 257
ADPT_ArraySyncComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 257
ADPT_ArraySyncDetected CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . 257
ADPT_ArraySyncFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 258
ADPT_CompactionComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 258
ADPT_CompactionDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 258
iv IBM Systems Director Events Reference

ADPT_CompactionFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 259
ADPT_CompressionComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . 259
ADPT_CompressionDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 259
ADPT_CompressionFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 260
ADPT_ConfigFail CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
ADPT_ControllerAdded CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 260
ADPT_ControllerBadStripes CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 261
ADPT_ControllerBatteryOvertemp CIM indication . . . . . . . . . . . . . . . . . . . . . . 261
ADPT_ControllerBatteryTempNormal CIM indication . . . . . . . . . . . . . . . . . . . . . 261
ADPT_ControllerFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 262
ADPT_ControllerFailover CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 262
ADPT_ControllerMismatchedVersions CIM indication . . . . . . . . . . . . . . . . . . . . . 262
ADPT_ControllerReplaced CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . 263
ADPT_CopyBackComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 263
ADPT_CopyBackDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 263
ADPT_CopyBackFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 264
ADPT_DeadBattery CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
ADPT_DeadBatteryCache CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 264
ADPT_DecompressionComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . 265
ADPT_DecompressionDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . 265
ADPT_DecompressionFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 265
ADPT_DefunctDrive CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 266
ADPT_DefunctDriveFRU CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 266
ADPT_DefunctReplaced CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 266
ADPT_DriveAdded CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
ADPT_DriveClearComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 267
ADPT_DriveClearDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 267
ADPT_DriveClearFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 268
ADPT_DriveRemoved CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 268
ADPT_DriveVerifyComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 268
ADPT_DriveVerifyDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 269
ADPT_DriveVerifyFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 269
ADPT_EnclosureFail CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . . 269
ADPT_EnclosureFanFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 270
ADPT_EnclosureFanInstalled CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 270
ADPT_EnclosureFanOK CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 270
ADPT_EnclosureFanRemoved CIM indication . . . . . . . . . . . . . . . . . . . . . . . 271
ADPT_EnclosureOK CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
ADPT_EnclosurePowerSupplyFail CIM indication . . . . . . . . . . . . . . . . . . . . . . 271
ADPT_EnclosurePowerSupplyInstalled CIM indication . . . . . . . . . . . . . . . . . . . . 272
ADPT_EnclosurePowerSupplyOK CIM indication . . . . . . . . . . . . . . . . . . . . . . 272
ADPT_EnclosurePowerSupplyRemoved CIM indication . . . . . . . . . . . . . . . . . . . . 272
ADPT_EnclosureTempFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 273
ADPT_EnclosureTempOK CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 273
ADPT_ExpansionComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 273
ADPT_ExpansionDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 274
ADPT_ExpansionFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 274
ADPT_FlashCopyComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 274
ADPT_FlashCopyDetected CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . 275
ADPT_FlashCopyFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 275
ADPT_InitComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
ADPT_InitDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
ADPT_InitFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
ADPT_LogicalDriveAdded CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 276
ADPT_LogicalDriveBlocked CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 277
ADPT_LogicalDriveCritical CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 277
ADPT_LogicalDriveCriticalPeriodic CIM indication. . . . . . . . . . . . . . . . . . . . . . 277
ADPT_LogicalDriveOffLine CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 278
ADPT_LogicalDriveOK CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 278
ADPT_LogicalDriveRemoved CIM indication. . . . . . . . . . . . . . . . . . . . . . . . 278
ADPT_LogicalDriveUnblocked CIM indication . . . . . . . . . . . . . . . . . . . . . . . 279
Contents v
ADPT_MigrationComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 279
ADPT_MigrationDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 279
ADPT_MigrationFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 280
ADPT_NoControllers CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 280
ADPT_PFADrive CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
ADPT_PFADriveFRU CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 281
ADPT_PollingFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
ADPT_RebuildComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 281
ADPT_RebuildDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 282
ADPT_RebuildFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
ADPT_SyncComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 282
ADPT_SyncDetected CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . . 283
ADPT_SyncFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
ADPT_TestEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
ADPT_UnsupportedDrive CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 284
LSI_RAID_HS_Fail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
LSI_RAID_LD_Degraded CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 284
LSI_RAID_LD_Offline CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 285
LSI_RAID_LD_Optimal CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . 285
LSI_RAID_PD_Fail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
LSI_RAID_PD_HS CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
LSI_RAID_PD_PartOf_LD_Add CIM indication . . . . . . . . . . . . . . . . . . . . . . . 286
LSI_RAID_PD_PartOf_LD_Fail CIM indication . . . . . . . . . . . . . . . . . . . . . . . 286
LSI_RAID_RbldComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 287
LSI_RAID_RbldFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
LSI_RAID_RbldStart CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . . 287
LSI_RAID_SMART_Error CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 288
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
vi IBM Systems Director Events Reference

About this publication
This publication provides reference information for commands available in IBM®
Systems Director. These commands fall into two broad categories:
v Commands used to perform IBM Systems Director tasks. These commands are
implemented using the IBM Systems Director command-line interface, IBM
Systems Director.
v Commands used to configure, start, or stop IBM Systems Director and database.
These commands are entered directly on the command line when the action
should be performed.
Conventions and terminology

These notices are designed to highlight key information:
Note: These notices provide important tips, guidance, or advice.
Important: These notices provide information or advice that might help you avoid
inconvenient or difficult situations.
Attention: These notices indicate possible damage to programs, devices, or data.

An attention notice appears before the instruction or situation in which damage
can occur.
Publications and related information

You can view the same content in the IBM Systems Director Information Center as
PDF documents. To view a PDF file, you need Adobe Acrobat Reader, which can
be downloaded for free from the Adobe Web site at http://get.adobe.com/reader/.
Information centers and topic collections

v IBM Systems
http://publib.boulder.ibm.com/eserver/
View the IBM Systems information center landing page, which provides
integrated information for multiple IBM Systems products.
v IBM Systems Director
http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp
Updated periodically, the IBM Systems Director topic collection contains the
most up-to-date documentation available for IBM Systems Director.
v IBM Systems Director plug-ins
publib.boulder.ibm.com/infocenter/systems/index.jsp
View the IBM Systems information center for information about how to install
and use plug-ins that extend the functionality of IBM Systems Director.
v IBM Systems Director Upward Integration Modules (UIMs)
publib.boulder.ibm.com/infocenter/systems/topic/uims/fqs0_main.html
Read the IBM Systems Director Upward Integration Modules (UIM) topic
collection to learn about how to install and use upward integration modules and
© Copyright IBM Corp. 1999, 2010 vii

management packs that enable non-IBM workgroup and enterprise-management
products to interpret and display data that is provided by Common Agent and
Platform Agent.
v IBM Systems Director API Licensing
http://www.ibm.com/vrm/4api1
View the license information regarding use of IBM Systems Director APIs and
their associated documentation. Fill out the form to request API access. After
your information is reviewed, you will be contacted with additional information
regarding access to and use of the APIs.
Publications
APAR Readme 6.2.0
Provides information about APARs fixed in IBM Systems Director version
6.2.0.
Release Notes® 6.2.0 and Release Notes 6.2.1
Provides information about hardware requirements for running IBM
Systems Director components, supported IBM Systems Director hardware,
operating systems, databases, and workgroup and enterprise
systems-management software.
Hardware and Software Support Guide
Provides information about hardware requirements for running IBM
Systems Director components, supported IBM Systems Director hardware,
operating systems, databases, and workgroup and enterprise
systems-management software.
Planning, Installation, and Configuration Guide for AIX®
Provides detailed instructions to install and configure each component of
IBM Systems Director on system running AIX using the standard
installation option.
Planning, Installation, and Configuration Guide for IBM i
IBM Systems Director on system running IBM i using the Standard
Planning, Installation, and Configuration Guide for Linux on Power Systems™
IBM Systems Director on system running Linux for Power Systems using
the Standard installation option.
Planning, Installation, and Configuration Guide for Linux on x86
IBM Systems Director on system running Linux for System x® using the
Standard installation option.
Planning, Installation, and Configuration Guide for Linux on System z®
IBM Systems Director on system running Linux for System z using the
Standard installation option.
Planning, Installation, and Configuration Guide for Windows
IBM Systems Director on system running Windows using the Standard
viii IBM Systems Director Events Reference

Systems Management Guide
Provides detailed instructions for using the Web interface and managing
systems and resources in your environment.
Troubleshooting Guide
Provides information about problems and how to solve them, and
strategies for troubleshooting common problems.
Events Reference
Provides information about IBM Systems Director events, including the
event type, description, severity, and extended details.
Commands Reference
Provides detailed information about the systems management
command-line interface (smcli) commands, and other commands that can
be run directly from the command line, including configuring the database,
and starting and stopping IBM Systems Director.
Hardware Command Line User's Guide
Provides information about installing and using the Hardware Command
Line (formerly known as the IBM Management Processor Command-Line
Interface). Command output in this release might vary from command
output in previous releases.
White papers and briefs

ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03006usen/
XBW03006USEN.PDF
This paper provides a detailed overview of the changes in IBM Systems Director
V6.1, including the new Web interface, security features, operating system
agents, integrated plug-ins and additional plug-ins that can be separately
installed.
v Value Proposition for IBM Systems Director
ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03007usen/
XBW03007USEN.PDF
This paper describes the challenges of operational management for enterprise
server installations and the value provided IBM Systems Director.
v Managing IBM Power Servers with IBM Systems Director 6.1
www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH
&appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN
&attachment=POW03011USEN.PDF
Provides information about managing the virtualization and consolidation on
Power systems using IBM Systems Director.
v IBM Systems Director 6.1 Migration Tips
www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH
&appname=STGE_XB_XB_USEN_&htmlfid=XBW03009USEN
&attachment=XBW03009USEN.PDF
Provides information about migrating data when upgrading your environment
from IBM Director V5.20 to IBM Systems Director V6.1.
v Performance Tuning and Scaling Guide for IBM Systems Director 6.2
http://www-01.ibm.com/support/
docview.wss?uid=nas7cd6a96f49d05f608862577420075ca9a&aid=1
About this publication ix

Provides information about how to plan, implement, configure, and use an IBM
Systems Director Server to manage a large configuration with optimal
performance. The Performance Tuning and Scaling Guide also contains
information about the following topics:
– Running IBM Systems Director plug-ins, such as IBM Systems Director Active
Energy Manager® and IBM Scalable Systems Manager
– Integration with Tivoli® products
– Implementing High Availability (HA)
IBM Redbooks® publications
www.ibm.com/redbooks/
You can also search this Web page for documents that focus on IBM Systems
Director and specific IBM hardware; such documents often contain
systems-management material. The following book is available for IBM Systems
Director V6.1:
Implementing IBM Systems Director 6.1
Tip: Be sure to note the date of publication and to determine the version of IBM
Systems Director software to which the Redbooks publication refers.
Further information
Also see the following resources for further information about IBM Systems
Director:
v For alerts, discussions, news, parts and product information, and specific
troubleshooting workarounds for IBM Systems Director, see the Support &
downloads Web site at http://www.ibm.com/support/us/en/.
Tip: To locate the information that you need, enter Systems Director in the
Search field and click Search. You can then narrow your results by document
type or product category, or use additional search terms.
v For white papers, technotes, tips, and other documents related to IBM Systems
Director, see the Techdocs Web site at http://w3.ibm.com/support/techdocs/
atsmastr.nsf/Web/Techdocs.
Tip: To locate the information that you need, either select the categories that you
want to search or select UNMARKED to search all categories. Then enter
Systems Director in the for: field and click Search.
v For solutions to all types of situations that other customers have encountered,
see the IBM Systems Director customer forum at www.ibm.com/
developerworks/forums/forum.jspa?forumID=759.
Web resources
Listed here are the Web sites and information center topics that relate to IBM
Systems Director.
Web sites
www.ibm.com/systems/management/director/
x IBM Systems Director Events Reference

View the IBM Systems Director Web site on ibm.com® which provides links to
downloads and documentation for all currently supported versions of IBM
Systems Director.
v IBM Systems Director Downloads
www.ibm.com/systems/management/director/downloads/
View the IBM Systems Director Downloads Web site on ibm.com which provides
links to download code IBM Systems Director, IBM Systems Director plug-ins,
and IBM Systems Director upward integration modules.
v IBM Systems Director Documentation and Resources
www.ibm.com/systems/management/director/resources/
View the IBM Systems Director Documentation and Resources Web site on
ibm.com which provides links to product documentation, redbooks, redpapers,
white papers, and learning modules related to IBM Systems Director, IBM
Systems Director plug-ins, and IBM Systems Director upward integration
modules.
v IBM Systems Director Upward Integration
www.ibm.com/systems/management/director/upward/
View the IBM Systems Director Upward Integration Web site on ibm.com which
provides more information about IBM Systems Director upward integration
modules created by IBM and other companies. IBM Systems Director UIMs
enable third-party workgroup and enterprise systems-management products to
interpret and display data that is provided by IBM Systems Director Platform
Agent managed system.
v IBM Systems Director Best Practices Wiki
www.ibm.com/developerworks/wikis/display/WikiPtype/
IBM+Systems+Director+Best+Practices+Wiki
View updated documentation and best practices for IBM Systems Director on
various systems.
v IBM Servers
www.ibm.com/servers/
View the IBM Servers Web site to learn about IBM Systems server and storage
products.
v IBM ServerProven®
www.ibm.com/servers/eserver/serverproven/compat/us/
View the IBM ServerProven Web site to learn about hardware compatibility of
IBM System x and BladeCenter® systems with IBM applications and middleware,
including IBM Systems Director.
Forums
www.ibm.com/developerworks/forums/forum.jspa?forumID=759
View the IBM Systems Director forum Web site on ibm.com to discuss
product-related issues pertaining to IBM Systems Director, IBM Systems Director
UIMs, and IBM Systems Director extensions. This Web site includes a link for
obtaining the forum using a Rich Site Summary (RSS) feed.
v IBM Systems Director SDK
www.ibm.com/developerworks/forums/dw_esforums.jspa
View the IBM Systems Director SDK forum Web site to discuss issues pertaining
to the IBM Systems Director Software Development Kit (SDK). This Web site
includes a link for obtaining the forum using a Rich Site Summary (RSS) feed.
About this publication xi

v IBM Systems
www.ibm.com/developerworks/forums/dw_esforums.jsp
View the IBM Systems forums Web site on ibm.com to learn about various
forums that are available to discuss technology-related and product-related
issues pertaining to IBM Systems hardware and software products. This Web site
includes a link for obtaining the forum using a Rich Site Summary (RSS) feed.
How to send your comments

Your feedback is important in helping to provide the most accurate and highest
quality information.
If you have any comments about this book or any other IBM Systems Director
publication, go to the IBM Systems Director information center Web site at
http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp. There you
will find the feedback page where you can enter and submit comments.
xii IBM Systems Director Events Reference

Chapter 1. Hardware platform events
IBM Systems Director introduces a new set of event types that categorize all
possible events by the hardware or devices in your systems-management
environment.
v For a hardware events severity-level name and number cross reference, see
Table 1.
v For events that can be generated by multiple hardware platforms, including IBM
BladeCenter and System x systems, see Table 2.
v For events that are specific to IBM Power Systems, see “IBM Power
platform-specific events.”
v For events that are specific to IBM System Storage®, see “IBM System Storage
platform-specific events.”
Use the following table to map event severity-level names to numbers.

Table 1. Severity level name-number cross reference
Severity level name Severity number
Unknown 0, 1
Informational, Harmless 2
Warning 3
Minor 4
Critical 5, 6
Fatal 7
Using your Web browser Find in page feature, use the following table to look up
events by their IBM Director 5.20 name. The link provided displays the version
5.20 event documentation that still applies to the new version 6.1 event.
Table 2. Hardware-platform events cross reference
IBM Systems Director 6.1 event name
Note: The name shown also is the click path to
IBM Director 5.20 event name view this event in the Event Filter Builder tree.
CIM > System > Service Event Managed Resource > Managed System Resource >
Logical Resource > System > Computer System >
Operational Condition > Resolution
Operational Condition > Warning
Operational Condition > Minor
Operational Condition > Critical
Operational Condition > Fatal
© Copyright IBM Corp. 1999, 2010 1

Table 2. Hardware-platform events cross reference (continued)
CIM > System > Temperature Managed Resource > Managed System Resource >
CIM > System > Voltage Managed Resource > Managed System Resource >
CIM > System > Life Cycle Managed Resource > Managed System Resource >
Life Cycle > Virtual server has been created.
Life Cycle > Virtual server has been deleted.
Life Cycle > Host has been added.
Life Cycle > Host has been deleted.
CIM > System > Power State Managed Resource > Managed System Resource >
Power State > Virtual server has been started.
Power State > Virtual server has been shut down.
Power State > Host has been powered on.
Power State > Host has been powered off.
CIM > System > IP Change Managed Resource > Managed System Resource >
IP Address Changed > IP Address has been
changed.
CIM > System > RAID > RAID Drive Removed Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Media Access
Device > Disk Drive > RAID Subsystem Life
Cycle > Removed
CIM > System > RAID > RAID Drive Added Managed Resource > Managed System Resource >
Device > Disk Drive > RAID Subsystem Life
Cycle > Added
2 IBM Systems Director Events Reference

CIM > System > RAID > RAID Unsupported Managed Resource > Managed System Resource >
Drive Logical Resource > Logical Device > Media Access
Device > Disk Drive > RAID Subsystem
Configuration > Unsupported Drive
v CIM > System > RAID > RAID PFA Drive Managed Resource > Managed System Resource >
v CIM > System > RAID > RAID PFA Drive FRU Device > Disk Drive > RAID Subsystem
Operational Condition > Predictive Failure
Analysis (PFA)
CIM > System > RAID > RAID Drive Clear Managed Resource > Managed System Resource >
Detected Logical Resource > Logical Device > Media Access
Device > Disk Drive > RAID Subsystem Drive
Clear > Detected
CIM > System > RAID > RAID Drive Clear Fail Managed Resource > Managed System Resource >
Clear > Failed
CIM > System > RAID > RAID Drive Clear Managed Resource > Managed System Resource >
Complete Logical Resource > Logical Device > Media Access
Clear > Completed
CIM > System > RAID > RAID Sync Detected Managed Resource > Managed System Resource >
Synchronization > Detected
CIM > System > RAID > RAID Sync Fail Managed Resource > Managed System Resource >
Synchronization > Failed
CIM > System > RAID > RAID Sync Complete Managed Resource > Managed System Resource >
Synchronization > Completed
CIM > System > RAID > RAID Drive Verify Managed Resource > Managed System Resource >
Detected Logical Resource > Logical Device > Media Access
Verify > Detected
CIM > System > RAID > RAID Drive Verify Fail Managed Resource > Managed System Resource >
Verify > Failed
CIM > System > RAID > RAID Drive Verify Managed Resource > Managed System Resource >
Complete Logical Resource > Logical Device > Media Access
Verify > Completed
CIM > System > RAID > RAID Controller Added Managed Resource > Managed System Resource >
RAID Controller > RAID Subsystem Life Cycle >
Added
CIM > System > RAID > RAID Controller Managed Resource > Managed System Resource >
Replaced Logical Resource > System > Computer System >
RAID Controller > RAID Subsystem Life Cycle >
Replaced
CIM > System > RAID > RAID Config Fail Managed Resource > Managed System Resource >
RAID Controller > RAID Subsystem
Configuration > Failed
Chapter 1. Hardware platform events 3

CIM > System > RAID > RAID No Controllers Managed Resource > Managed System Resource >
Configuration > No Controllers
CIM > System > RAID > RAID Controller Managed Resource > Managed System Resource >
Mismatched Versions Logical Resource > System > Computer System >
Configuration > Mismatched Versions
v CIM > System > RAID > RAID Controller Fail Managed Resource > Managed System Resource >
v CIM > System > RAID > RAID Polling Fail RAID Controller > RAID Subsystem Operational
v CIM > System > RAID > RAID Controller Bad Condition > Failed
Stripes
CIM > System > RAID > RAID Controller Failover Managed Resource > Managed System Resource >
RAID Controller > RAID Subsystem Operational
Condition > Failover
CIM > System > RAID > RAID Test Event Managed Resource > Managed System Resource >
RAID Controller > RAID Subsystem Operational
Condition > Test
v CIM > System > RAID > RAID Enclosure Fail Managed Resource > Managed System Resource >
v CIM > System > RAID > RAID Enclosure OK RAID Controller > RAID Subsystem Enclosure >
Failed
CIM > System > Host Bus Adapter Managed Resource > Managed System Resource >
RAID Controller > RAID Subsystem Adapter >
Status
CIM > System > RAID > RAID Logical Drive OK Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Storage
Extent > Logical Disk > RAID Subsystem Logical
Drive > OK
v CIM > System > RAID > RAID Logical Drive Managed Resource > Managed System Resource >
Critical Logical Resource > Logical Device > Storage
v CIM > System > RAID > RAID Logical Drive Drive > Critical
Critical Periodic
CIM > System > RAID > RAID Logical Drive Managed Resource > Managed System Resource >
Blocked Logical Resource > Logical Device > Storage
Drive > Blocked
Unblocked Logical Resource > Logical Device > Storage
Drive > Unblocked
Added Logical Resource > Logical Device > Storage
Drive > Added
Removed Logical Resource > Logical Device > Storage
Drive > Removed

v CIM > System > RAID > RAID Logical Drive Managed Resource > Managed System Resource >
Off Line Logical Resource > Logical Device > Storage
v CIM > System > RAID > RAID Logical Drive Drive > Offline
Offline
CIM > System > RAID > RAID Array Rebuild Managed Resource > Managed System Resource >
Detected Logical Resource > Logical Device > Storage
Extent > Logical Disk > RAID Subsystem Array
Rebuild > Detected
CIM > System > RAID > RAID Array Rebuild Fail Managed Resource > Managed System Resource >
Rebuild > Failed
CIM > System > RAID > RAID Array Rebuild Managed Resource > Managed System Resource >
Complete Logical Resource > Logical Device > Storage
Rebuild > Completed
CIM > System > RAID > RAID Array Sync Managed Resource > Managed System Resource >
Synchronization > Detected
CIM > System > RAID > RAID Array Sync Fail Managed Resource > Managed System Resource >
Synchronization > Failed
CIM > System > RAID > RAID Array Sync Managed Resource > Managed System Resource >
Synchronization > Completed
CIM > System > RAID > RAID Migration Managed Resource > Managed System Resource >
Extent > Logical Disk > RAID Subsystem
Migration > Detected
CIM > System > RAID > RAID Migration Fail Managed Resource > Managed System Resource >
Migration > Failed
CIM > System > RAID > RAID Migration Managed Resource > Managed System Resource >
Migration > Completed
CIM > System > RAID > RAID Compression Managed Resource > Managed System Resource >
Compression > Detected
CIM > System > RAID > RAID Compression Fail Managed Resource > Managed System Resource >
Compression > Failed
CIM > System > RAID > RAID Compression Managed Resource > Managed System Resource >
Compression > Completed
CIM > System > RAID > RAID Decompression Managed Resource > Managed System Resource >
Decompression > Detected

Fail Logical Resource > Logical Device > Storage
Decompression > Failed
Decompression > Completed
CIM > System > RAID > RAID FlashCopy Managed Resource > Managed System Resource >
FlashCopy > Detected
CIM > System > RAID > RAID FlashCopy Fail Managed Resource > Managed System Resource >
FlashCopy > Failed
CIM > System > RAID > RAID FlashCopy Managed Resource > Managed System Resource >
FlashCopy > Completed
CIM > System > RAID > RAID Compaction Managed Resource > Managed System Resource >
Compaction > Detected
CIM > System > RAID > RAID Compaction Fail Managed Resource > Managed System Resource >
Compaction > Failed
CIM > System > RAID > RAID Compaction Managed Resource > Managed System Resource >
Compaction > Completed
CIM > System > RAID > RAID Expansion Managed Resource > Managed System Resource >
Expansion > Detected
CIM > System > RAID > RAID Expansion Fail Managed Resource > Managed System Resource >
Expansion > Failed
CIM > System > RAID > RAID Expansion Managed Resource > Managed System Resource >
Expansion > Completed
CIM > System > RAID > RAID Copyback Managed Resource > Managed System Resource >
Copyback > Detected
CIM > System > RAID > RAID Copyback Fail Managed Resource > Managed System Resource >
Copyback > Failed
CIM > System > RAID > RAID Copyback Managed Resource > Managed System Resource >
Copyback > Completed

CIM > System > RAID > RAID Init Detected Managed Resource > Managed System Resource >
Initialization > Detected
CIM > System > RAID > RAID Init Fail Managed Resource > Managed System Resource >
Initialization > Failed
CIM > System > RAID > RAID Init Complete Managed Resource > Managed System Resource >
Initialization > Completed
v CIM > System > RAID > RAID Defunct Drive Managed Resource > Managed System Resource >
v CIM > System > RAID > RAID Defunct Drive Extent > Logical Disk > RAID Subsystem Defunct
FRU Drive > Detected
CIM > System > RAID > RAID Defunct Replaced Managed Resource > Managed System Resource >
Extent > Logical Disk > RAID Subsystem Defunct
Drive > Replaced
v CIM > System > RAID > RAID Dead Battery Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Battery >
v CIM > System > RAID > RAID Dead Battery Operational Condition > Failed
Cache
CIM > System > RAID > RAID Controller Battery Managed Resource > Managed System Resource >
Overtemp Logical Resource > Logical Device > Battery >
Temperature > High
CIM > System > RAID > RAID Controller Battery Managed Resource > Managed System Resource >
Temp Normal Logical Resource > Logical Device > Battery >
Temperature > Normal
CIM > System > RAID > RAID Enclosure Fan Managed Resource > Managed System Resource >
Removed Logical Resource > Logical Device > Fan > RAID
Subsystem Life Cycle > Removed
CIM > System > RAID > RAID Enclosure Fan Managed Resource > Managed System Resource >
Installed Logical Resource > Logical Device > Fan > RAID
Subsystem Life Cycle > Added
CIM > System > RAID > RAID Enclosure Fan Fail Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Fan > RAID
Subsystem Operational Condition > Failed
CIM > System > RAID > RAID Enclosure Fan OK Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Fan > RAID
Subsystem Operational Condition > OK
CIM > System > RAID > RAID Enclosure Temp Managed Resource > Managed System Resource >
Fail Logical Resource > Logical Device > Sensor >
Numeric Sensor > Temperature Sensor > High
CIM > System > RAID > RAID Enclosure Temp Managed Resource > Managed System Resource >
OK Logical Resource > Logical Device > Sensor >
Numeric Sensor > Temperature Sensor > Normal
CIM > System > RAID > RAID Enclosure Power Managed Resource > Managed System Resource >
Supply Removed Logical Resource > Logical Device > Power
Supply > RAID Subsystem Life Cycle > Removed
Supply Installed Logical Resource > Logical Device > Power
Supply > RAID Subsystem Life Cycle > Added

Supply Fail Logical Resource > Logical Device > Power
Supply > RAID Subsystem Operational Condition
> Failed
Supply OK Logical Resource > Logical Device > Power
Supply > RAID Subsystem Operational Condition
> OK
MPA > Unknown Managed Resource > Managed System Resource >
Unknown > Unknown
MPA > Component > Chassis > Configuration Managed Resource > Managed System Resource >
Physical Resource > Physical Package > Physical
Frame > Chassis > Operational Condition >
Configuration Error
v MPA > Component > Chassis > Maximum Managed Resource > Managed System Resource >
Cooling Physical Resource > Physical Package > Physical
Frame > Chassis > Operational Condition >
v MPA > Component > Chassis > Failed Temperature
v MPA > Component > Chassis > Cooling
Capacity
MPA > Component > Bus > Communication Managed Resource > Managed System Resource >
Physical Resource > Physical Package > Physical
Frame > Chassis > Operational Condition > Bus
Communication Failure
MPA > Component > Chassis > Direct Serial Managed Resource > Managed System Resource >
Attach Module > Disabled Physical Resource > Physical Package > Physical
Frame > Chassis > Open Fabric Manager >
Deactivated
MPA > Component > Blade Server > Removed Managed Resource > Managed System Resource >
Physical Resource > Physical Connector > Slot >
Life Cycle > Removed
MPA > Component > Blade Server > Inserted Managed Resource > Managed System Resource >
Life Cycle > Added
MPA > Component > Blade Server > Incompatible Managed Resource > Managed System Resource >
Operational Condition > Configuration Error
v MPA > Component > Blade Server > Managed Resource > Managed System Resource >
Insufficient Power Physical Resource > Physical Connector > Slot >
Operational Condition > Power State Changed
v MPA > Component > Blade Server > Over
Power Budget
MPA > Component > Blade Server > VPD Managed Resource > Managed System Resource >
Operational Condition > Not Recognized
MPA > Component > Blade Server > Throttled Managed Resource > Managed System Resource >
Operational Condition > Throttled
MPA > Component > Blade Server > Managed Resource > Managed System Resource >
Communication Physical Resource > Physical Connector > Slot >
Operational Condition > Communication Error
MPA > Component > Blade Server > Capacity on Managed Resource > Managed System Resource >
Demand Physical Resource > Physical Connector > Slot >
Capacity On Demand > Activated

MPA > Component > Service Processor > Managed Resource > Managed System Resource >
Removed Logical Resource > System > Computer System >
Hardware Control Point > Service Processor > Life
Cycle > Removed
MPA > Component > Service Processor > Inserted Managed Resource > Managed System Resource >
Hardware Control Point > Service Processor > Life
Cycle > Added
Network Stack Logical Resource > System > Computer System >
Hardware Control Point > Service Processor >
Operational Condition > Network Stack Started
MPA > Component > Service Processor > Restart Managed Resource > Managed System Resource >
Operational Condition > Restarted
v MPA > Component > Service Processor > Managed Resource > Managed System Resource >
Mismatch Logical Resource > System > Computer System >
v MPA > Component > Service Processor > Operational Condition > Configuration Error
Duplicate IP Address
v MPA > Component > Service Processor >
Configuration
Communication Logical Resource > System > Computer System >
Operational Condition > Blade Server Baseboard
Management Controller (BMC) Communication
Error
v MPA > Component > Service Processor > Managed Resource > Managed System Resource >
Failover Logical Resource > System > Computer System >
v MPA > Component > Service Processor > Active Operational Condition > Failover
v MPA > Component > Service Processor >
Inactive
Redundancy Logical Resource > System > Computer System >
Operational Condition > Redundancy
MPA > Component > Service Processor > Test Managed Resource > Managed System Resource >
Operational Condition > Test
v CIM > System > IPMI Log Managed Resource > Managed System Resource >
v MPA > Component > Service Processor > Log Hardware Control Point > Service Processor >
Hardware Log > Threshold
Out-of-Band > Enabled Logical Resource > System > Computer System >
Out-Of-Band Connection > Activated
Out-of-Band > Disabled Logical Resource > System > Computer System >
Out-Of-Band Connection > Deactivated

Out-of-Band > Port Logical Resource > System > Computer System >
Out-Of-Band Connection > Port Changed
MPA > Component > Service Processor > Secure Managed Resource > Managed System Resource >
Out-of-Band > Enabled Logical Resource > System > Computer System >
Secure Out-Of-Band Connection > Activated
Out-of-Band > Disabled Logical Resource > System > Computer System >
Secure Out-Of-Band Connection > Deactivated
Out-of-Band > Port Logical Resource > System > Computer System >
Secure Out-Of-Band Connection > Port Changed
MPA > Component > Service Processor > User Managed Resource > Managed System Resource >
Account > Inactive Logical Resource > System > Computer System >
User Account > Deactivated
MPA > Component > Service Processor > User Managed Resource > Managed System Resource >
Account > Active Logical Resource > System > Computer System >
User Account > Activated
Password > Change Required Logical Resource > System > Computer System >
User Account > Password Change Required
CIM > System > System Enclosure Managed Resource > Managed System Resource >
Server > Operational Condition > Intrusion
MPA > Component > Server > Configuration Managed Resource > Managed System Resource >
Server > Operational Condition > Configuration
Error
CIM > System > Automatic Server Restart Managed Resource > Managed System Resource >
Server > Operational Condition > Automatic
Server Restart
MPA > Component > Server Managed Resource > Managed System Resource >
Server > Operational Condition > Reset
MPA > Component > Server > Power > Disabled Managed Resource > Managed System Resource >
Server > Operational Condition > Power Disabled
MPA > Component > Server > Power > Disabled Managed Resource > Managed System Resource >
Server > Operational Condition > Power Enabled
MPA > Component > Server > Power > Hibernate Managed Resource > Managed System Resource >
Server > Operational Condition > Hibernate
MPA > Component > Server > Power > Standby Managed Resource > Managed System Resource >
Server > Operational Condition > Standby

MPA > Component > Server > Power > Restart Managed Resource > Managed System Resource >
Server > Operational Condition > Restarted
MPA > Component > Server > Power > Off Managed Resource > Managed System Resource >
Server > Operational Condition > Powered Off
MPA > Component > Server > Power > On Managed Resource > Managed System Resource >
Server > Operational Condition > Powered On
MPA > Component > Server > State Managed Resource > Managed System Resource >
Server > Operational Condition > State Change
MPA > Component > BIOS > Corrupted Managed Resource > Managed System Resource >
Server > Operational Condition > BIOS Corrupted
MPA > Component > BIOS > Fault Managed Resource > Managed System Resource >
Server > Operational Condition > BIOS Fault
MPA > Component > SMP Expansion Module > Managed Resource > Managed System Resource >
Disabled Logical Resource > System > Computer System >
Server > Operational Condition > SMP Expansion
Module Disabled
v CIM > System > PFA Managed Resource > Managed System Resource >
v MPA > Component > PFA Server > Operational Condition > Predictive
Failure Analysis (PFA)
CIM > System > Error Log Managed Resource > Managed System Resource >
Server > Operational Condition > Log
MPA > Server Watchdog > Boot Managed Resource > Managed System Resource >
Server > Deployment > Boot Failure
MPA > Server Watchdog > POST Managed Resource > Managed System Resource >
Server > Deployment > POST Failure
MPA > Server Watchdog > OS Managed Resource > Managed System Resource >
Server > Deployment > FailedOs
MPA > Server Watchdog > Loader Managed Resource > Managed System Resource >
Server > Deployment > Load Failure
MPA > Platform Managed Resource > Managed System Resource >
Server > Scalable Partition > Alerts
Server > Scalable Partition > Logical Partition
State Change
Server > Scalable Partition > Physical Partition
Mode Change
CIM > System > Lease Expiration Managed Resource > Managed System Resource >
Server > Asset > Lease Expired

CIM > System > Warranty Expiration Managed Resource > Managed System Resource >
Server > Asset > Warranty Expired
MPA > Component > Multiplexer Expansion Managed Resource > Managed System Resource >
Module > Removed Logical Resource > Logical Device > Logical
Module > Multiplexer Card Module > Life Cycle
> Removed
Module > Inserted Logical Resource > Logical Device > Logical
Module > Multiplexer Card Module > Life Cycle
> Added
Module > Failed Logical Resource > Logical Device > Logical
Module > Multiplexer Card Module > Operational
Condition > Failed
MPA > Component > Alarm Panel > Removed Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Logical
Module > Alarm Panel Module > Life Cycle >
Removed
MPA > Component > Alarm Panel > Inserted Managed Resource > Managed System Resource >
Module > Alarm Panel Module > Life Cycle >
Added
MPA > Component > Alarm Panel > Power > Off Managed Resource > Managed System Resource >
Module > Alarm Panel Module > Power > Off
MPA > Component > Alarm Panel > Power > On Managed Resource > Managed System Resource >
Module > Alarm Panel Module > Power > On
MPA > Component > Clock Module > Removed Managed Resource > Managed System Resource >
Module > Clock Module > Life Cycle > Removed
MPA > Component > Clock Module > Inserted Managed Resource > Managed System Resource >
Module > Clock Module > Life Cycle > Added
MPA > Component > Clock Module > Power > Managed Resource > Managed System Resource >
Off Logical Resource > Logical Device > Logical
Module > Clock Module > Power > Off
MPA > Component > Clock Module > Power > Managed Resource > Managed System Resource >
On Logical Resource > Logical Device > Logical
Module > Clock Module > Power > On
MPA > Component > I/O Interposer > Removed Managed Resource > Managed System Resource >
Module > Input/Output (I/O) Module > Life
Cycle > Removed
MPA > Component > I/O Interposer > Inserted Managed Resource > Managed System Resource >
Module > Input/Output (I/O) Module > Life
Cycle > Added
Attach Module > Removed Logical Resource > Logical Device > Logical
Module > Baggage Cart Module > Life Cycle >
Removed

Attach Module > Inserted Logical Resource > Logical Device > Logical
Module > Baggage Cart Module > Life Cycle >
Added
MPA > Component > VRM > Configuration Managed Resource > Managed System Resource >
Module > Voltage Regulator Module (VRM) >
Configuration > Change
MPA > Component > VRM > Failed Managed Resource > Managed System Resource >
Module > Voltage Regulator Module (VRM) >
Operational Condition > Failed
MPA > Component > Media Tray > Failed Managed Resource > Managed System Resource >
Module > Media Tray Module > Operational
Condition > Failed
MPA > Component > Media Tray > Temperature Managed Resource > Managed System Resource >
Unavailable Logical Resource > Logical Device > Logical
Module > Media Tray Module > Temperature >
Not Available
MPA > Component > Concurrent KVM > Failed Managed Resource > Managed System Resource >
Module > Keyboard, Video, Mouse (KVM)
Module > Operational Condition > Failed
MPA > Component > Front Panel > Failed Managed Resource > Managed System Resource >
Module > Front Panel Module > Operational
Condition > Failed
CIM > System > Processor Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Processor >
Life Cycle > Removed
CIM > System > Processor Managed Resource > Managed System Resource >
Life Cycle > Added
v MPA > Component > CPU > Configuration Managed Resource > Managed System Resource >
v MPA > Component > CPU > Absent Operational Condition > Configuration Error
MPA > Component > CPU > Failed Managed Resource > Managed System Resource >
CIM > System > Processor PFA Managed Resource > Managed System Resource >
Operational Condition > Predictive Failure
Analysis (PFA)
MPA > Component > I/O Module > Removed Managed Resource > Managed System Resource >
Switch > Life Cycle > Removed
MPA > Component > I/O Module > Inserted Managed Resource > Managed System Resource >
Switch > Life Cycle > Added
v MPA > Component > I/O Module > Power > Managed Resource > Managed System Resource >
Off Logical Resource > System > Computer System >
Switch > Power > Off
v MPA > Component > I/O Module > Power >
Timeout

MPA > Component > I/O Module > Power > On Managed Resource > Managed System Resource >
Switch > Power > On
MPA > Component > I/O Module > Managed Resource > Managed System Resource >
Configuration Logical Resource > System > Computer System >
Switch > Operational Condition > Configuration
Change
MPA > Component > I/O Module > Mismatch Managed Resource > Managed System Resource >
Switch > Operational Condition > Configuration
Error
MPA > Component > I/O Module > Power > Managed Resource > Managed System Resource >
Disabled Logical Resource > System > Computer System >
Switch > Operational Condition > Not Recognized
v MPA > Component > I/O Module > Insufficient Managed Resource > Managed System Resource >
Power Logical Resource > System > Computer System >
Switch > Operational Condition > Power State
v MPA > Component > I/O Module > Fuse Changed
v MPA > Component > I/O Module > Over
Current
v MPA > Component > I/O Module > Failed Managed Resource > Managed System Resource >
v MPA > Component > I/O Module > POST Switch > Operational Condition > Failed
MPA > Component > I/O Module > Redundancy Managed Resource > Managed System Resource >
Switch > Operational Condition > Redundancy
v MPA > Component > I/O Module > Stacking > Managed Resource > Managed System Resource >
Activated Logical Resource > System > Computer System >
Switch > Operational Condition > Stacking
v MPA > Component > I/O Module > Stacking >
Deactivated
MPA > Component > I/O Module > Zoning Managed Resource > Managed System Resource >
Switch > Operational Condition > Zoning
MPA > Component > I/O Module > Managed Resource > Managed System Resource >
Communication Logical Resource > System > Computer System >
Switch > Operational Condition > Communication
Error
v MPA > Component > Fan > Removed Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Fan > Life
v MPA > Component > Fan Pack > Removed Cycle > Removed
v MPA > Component > Fan > Inserted Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Fan > Life
v MPA > Component > Fan Pack > Inserted Cycle > Added
MPA > Component > Fan > Configuration Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Fan >
Operational Condition > Configuration Error
CIM > System > Fan Managed Resource > Managed System Resource >
Operational Condition > Threshold
v MPA > Component > Fan > Failed Managed Resource > Managed System Resource >
v MPA > Component > Fan Pack > Failed Operational Condition > Failed

v MPA > Component > Fan > PFA Managed Resource > Managed System Resource >
v MPA > Component > Fan Pack > PFA Operational Condition > Predictive Failure
Analysis (PFA)
MPA > Component > DASD > Removed Managed Resource > Managed System Resource >
Device > Disk Drive > Life Cycle > Removed
MPA > Component > DASD > Inserted Managed Resource > Managed System Resource >
Device > Disk Drive > Life Cycle > Added
MPA > Component > DASD > Configuration Managed Resource > Managed System Resource >
Device > Disk Drive > Operational Condition >
Configuration Error
v CIM > System > DASD Backplane Managed Resource > Managed System Resource >
v CIM > System > SMART Drive Device > Disk Drive > Operational Condition >
v MPA > Component > DASD > Failed Failed
MPA > Component > DASD > PFA Managed Resource > Managed System Resource >
Device > Disk Drive > Operational Condition >
Predictive Failure Analysis (PFA)
CIM > System > Disk Space Low Managed Resource > Managed System Resource >
Device > Disk Drive > Available Percentage >
Disk Space
MPA > Component > Power Supply > Removed Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Power
Supply > Life Cycle > Removed
MPA > Component > Power Supply > Inserted Managed Resource > Managed System Resource >
Supply > Life Cycle > Added
v MPA > Component > Power Supply > Managed Resource > Managed System Resource >
Configuration Logical Resource > Logical Device > Power
Supply > Operational Condition > Configuration
v MPA > Component > Power Supply > Absent Error
v CIM > System > Power Supply Managed Resource > Managed System Resource >
v MPA > Component > Power Supply > Failed Supply > Operational Condition > Failed
MPA > Component > Power Supply > PFA Managed Resource > Managed System Resource >
Supply > Operational Condition > Predictive
CIM > System > Memory Managed Resource > Managed System Resource >
Physical Resource > Physical Component > Chip
> Physical Memory > Life Cycle > Removed
CIM > System > Memory Managed Resource > Managed System Resource >
> Physical Memory > Life Cycle > Added
MPA > Component > DIMM > Absent Managed Resource > Managed System Resource >
> Physical Memory > Operational Condition >
Configuration Error

CIM > System > Memory PFA Managed Resource > Managed System Resource >
Predictive Failure Analysis (PFA)
MPA > Component > DIMM > Failed Managed Resource > Managed System Resource >
Failed
MPA > Component > DIMM > Disabled Managed Resource > Managed System Resource >
Deactivated
MPA > Component > Management Module Managed Resource > Managed System Resource >
Interposer > Removed Physical Resource > Physical Connector >
ManagementModule > Life Cycle > Removed
MPA > Component > Management Module Managed Resource > Managed System Resource >
Interposer > Inserted Physical Resource > Physical Connector >
ManagementModule > Life Cycle > Added
MPA > Component > Battery > Removed Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Battery > Life
Cycle > Removed
MPA > Component > Battery > Removed Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Battery > Life
Cycle > Added
MPA > Component > Battery > Unreliable Managed Resource > Managed System Resource >
Operational Condition > Not Reliable
MPA > Component > Battery > Failed Managed Resource > Managed System Resource >
MPA > Component > RAID > Failed Managed Resource > Managed System Resource >
RAID Controller > Operational Condition > Failed
MPA > Component > Storage Module > Removed Managed Resource > Managed System Resource >
Storage Subsystem > Life Cycle > Removed
MPA > Component > Storage Module > Inserted Managed Resource > Managed System Resource >
Storage Subsystem > Life Cycle > Added
v MPA > Component > Storage Module > Failed Managed Resource > Managed System Resource >
v MPA > Component > Storage Module > Storage Subsystem > Operational Condition >
Insufficient Cooling Failed
v MPA > Component > Storage Module >
Insufficient Power
MPA > Component > USB > Removed Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Controller >
USB Controller > Life Cycle > Removed
MPA > Component > USB > Inserted Managed Resource > Managed System Resource >
USB Controller > Life Cycle > Added
MPA > Component > USB > Over Current Managed Resource > Managed System Resource >
USB Controller > Operational Condition > Over
Current

MPA > Component > Power Subsystem > Over Managed Resource > Managed System Resource >
Power Logical Resource > System > Administration
Domain > Power Domain > Operational
Condition > Power Exceeded
Current Logical Resource > System > Administration
Condition > Over Current
MPA > Component > Power Subsystem > Low Managed Resource > Managed System Resource >
Fuel Logical Resource > System > Administration
Condition > Low Fuel
Subscription Logical Resource > System > Administration
Condition > Over Power Subscription
MPA > Component > Power Subsystem > Managed Resource > Managed System Resource >
Mismatched Power Supplies Logical Resource > System > Administration
Condition > Configuration Error
MPA > Component > Power Subsystem > Managed Resource > Managed System Resource >
Redundancy Logical Resource > System > Administration
Condition > Redundancy
CIM > System > Network Adapter Managed Resource > Managed System Resource >
Physical Resource > Physical Package > Card >
Life Cycle > Network interface card (NIC)
Removed
Life Cycle > Network interface card (NIC) Added
Operational Condition > Network interface card
(NIC) Offline
(NIC) Online
(NIC) Failed
MPA > Component > I/O Board > Failed Managed Resource > Managed System Resource >
Operational Condition > I/O Board Failure
MPA > Component > Processor Board > Failed Managed Resource > Managed System Resource >
Operational Condition > Processor Board Failure
MPA > Component > Expansion Card > Failed Managed Resource > Managed System Resource >
Operational Condition > Daughter Card Failure

v CIM > System > Redundant Network Adapter Managed Resource > Managed System Resource >
Failover Physical Resource > Physical Package > Card >
v CIM > System > Redundant Network Adapter (NIC) Failover
SwitchBack
v CIM > System > Redundant Network Adapter
SwitchOver
MPA > Component > Blade Expansion Unit > Managed Resource > Managed System Resource >
Failed Physical Resource > Physical Package > Blade
Expansion Unit > Operational Condition > Blade
Expansion Unit Failed
v CIM > System > Voltage Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Sensor >
v MPA > Environmental > Voltage Numeric Sensor > Voltage Sensor > Out Of Range
v CIM > System > Temperature Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Sensor >
v MPA > Environmental > Temperature Numeric Sensor > Temperature Sensor > High
IBM BladeCenter and System x platform-specific events

The events listed in this section are specific for the IBM BladeCenter and System x
hardware platforms. In IBM Director 5.20, these were called the CIM and MPA
events. In IBM Systems Director 6.1, the CIM and MPA events are still used, but
are mapped to hardware component categories. Use the Hardware-platform event
cross-reference table to find the 5.20 event name and its equivalent 6.1 event name.
CIM events
The CIM events occur when a change in state is detected for IBM Systems Director
components and features as well as hardware in an IBM Systems Director
environment. For detailed event types, expand the CIM node in the Event Filter
Builder tree.
Details
If you select the CIM check box in the Event Filter Builder tree, the event filter will
process all of the event types that are specified in the CIM subtree.
Event type Event text Severity Category Extended details
CIM Not applicable Not Not None
applicableapplicable
CIM > System

The System events occur when a change in the state of a Platform Agent managed
system or Common Agent managed system managed system is detected. These
events also occur when a change in the state of a Hardware Management Console
(HMC) is detected.
Details
The CIM > System event types use a standard set of extended details.

If you select the System check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the System subtree.
System Not applicable Not Not None
CIM > System > Automatic Server Restart:
The Automatic Server Restart event occurs when the operating system locks up
and no longer responds. Subsequently, a system restart (reboot) begins. This event
is supported on servers with Intelligent Platform Management Interface (IPMI).
Resolution
No resolution. This event is informative only.
Details
Additional
extended
Event type Event text Severity Category details
Automatic The last system restart was due to the Warning Alert None
Server Restart automatic server restart hardware.
Automatic The last system restart was not due to Informational Resolution None
Server Restart the automatic server restart hardware.
CIM > System > DASD Backplane:
The DASD Backplane event occurs when the Remote Supervisor Adapter detects
that the state of the system hard disk drive changes with respect to its availability.
Resolution
Replace the specified hard disk drive that has failed. If necessary, restore your data
from a backup.
Note: After correcting the hardware error, you must clear this event manually.
Details
Additional extended
DASD Drive drive has reported a fault. This Critical Alert None
Backplane event must be cleared manually.
where drive is the affected hard disk

drive.
CIM > System > Disk Space Low:
The Disk Space Low event occurs when the state of system hard disk drive space
changes with respect to user-defined levels of hard disk drive space remaining. By
default, the warning level is 5% remaining and critical level is 3% remaining.

Resolution
v If the severity is Critical or Warning: Remove files from the specified hard disk
or lower the minimum threshold.
v If the category is Resolution: The error has been resolved. This event is
informative only.
Details
Additional
extended
Disk Space Low Logical drive name fell below threshold Critical Alert None
of threshold MB. The current value is
value MB.
where:
v name is the affected logical drive.
v threshold is the critical threshold
value.
v value is the amount of current disk
space available.
Disk Space Low Logical drive name fell below threshold Warning Alert None
of threshold MB. The current value is
value MB.
where:
v threshold is the warning threshold
value.
v value is the amount of current disk
space available.
Disk Space Low Logical drive name free space is normal. Informational Resolution None
The current value is value MB.
where name is the affected logical drive

and value is the amount of current disk
space available.
Disk Space Low Logical drive name status could not be Unknown Resolution None
determined.
where name is the affected logical drive.
CIM > System > Error Log:
The Error Log event occurs when the Remote Supervisor Adapter detects that its
error log is at 75% or 100% of its capacity.
Resolution
If the severity is Warning: Back up and clear the system-management processor

event log.

Details
Additional extended
Error Log The system management processor error Warning Alert None
log is 75% full. This event must be
cleared manually.
Error Log The system management processor error Warning Alert None
log is full. This event must be cleared
manually.
CIM > System > Fan:
The Fan event occurs when the state of a system fan has changed with respect to
the manufacturer-defined revolutions per minute (rpm) values. This event is sent
when a fan stops, is removed, or is not performing optimally.
Resolution
v If the severity is Critical: Replace the specified fan that has failed.
informative only.
Details
Additional
extended
Fan Fan Sensor number fell below threshold Critical Alert None
of threshold rpm. The current value is
speed rpm.
where:
v number is the affected fan sensor.
v threshold is the critical fan threshold
value.
v speed is the current fan speed.
Note: This event must be cleared
manually.
Fan Fan Sensor number reports normal. Informational Resolution None
where number is the affected fan sensor.
CIM > System > Host Bus Adapter:
The Host Bus Adapter events occur when a QLogic Fibre Channel Host Bus
Adapter detects a change in its state or configuration.
Event source
CIM > System > Host Bus Adapter event types are generated by the QLogic Fibre
Channel Host Bus Adapter.
Details
For information about these events, see the QLogic Fibre Channel Host Bus
Adapter documentation.

CIM > System > IP Change:
The IP Change event occurs when a change in an IP address used by the HMC is
detected.
Resolution
Details
The CIM > System event types for HMC use a standard set of extended details.
Event type Event text Severity Category Additional extended details
IP Change The IP Address associated with HMC number Informational Alert v Description indicates the
has changed. type of event.
where number identifies the HMC. v OldIPAddress indicates the
previous IP address used
by the HMC.
v NewIPAddress indicates the
new IP address used by
the HMC.
CIM > System > IVM Unconfigured:
The IVM Unconfigured event occurs when an IVM becomes unconfigured.

Typically, this occurs when a user migrates an IVM-managed system to HMC
management.
Resolution
Details
IVM Unconfigured IVM is not configured. Informational Alert None
CIM > System > IPMI Log:
The IPMI Log event occurs when the system-management processor error log is
75% full or full. This event is supported on servers with Intelligent Platform
Management Interface (IPMI).
Resolution
To correct this problem, reduce the number of events in the event log. You can
clear the event log using the BIOS configuration utility on the server or remotely
using the OSA SMBridge utility. See the documentation for your server or the IBM
Redbooks publication IBM eServer™ xSeries® and BladeCenter Server Management
(SG24-6495).

Details
Additional extended
IPMI Log The system management processor error Warning Alert None
log is 75% full. This event must be
cleared manually.
IPMI Log The system management processor error Warning Alert None
log is full. This event must be cleared
manually.
CIM > System > Lease Expiration:
The Lease Expiration event occurs when the system lease expiration date has been
reached with respect to the value configured for the date in the Asset ID task.
Resolution
v If the severity is Warning: The lease has expired.
informative only.
Details
The date value is provided by the Asset ID task. The Lease page in the Asset ID
task includes the End Date field where you can set the lease expiration date. The
date is stored in the IBMPSG_Lease.LeaseEndDate CIM property that is monitored
at regular poll intervals. A CIM indication is generated when the system CIMOM
starts and when a state change is detected relative to the internal poll interval.
Additional extended
Lease Expiration The lease on system has expired. Warning Alert None
It expired on date.
where system is the affected

system and date is the lease
expiration date.
Lease Expiration The lease on system is normal. It Informational Resolution None
will expire on date.

system and date is the lease
expiration date.
CIM > System > Life Cycle:
The Life Cycle event occurs when an LPAR is created or deleted on a system
managed by the Hardware Management Console (HMC). The event also occurs
when a CEC is managed by the HMC or removed from management by the HMC.
Resolution

Details
Additional extended
Life Cycle LPAR name has been created. Minor Alert LifeCycleEvent indicates
whether the CEC was
where name identifies the LPAR created. added or removed from
management by the HMC.
Life Cycle LPAR name has been deleted. Minor Alert LifeCycleEvent indicates
whether the CEC was
where name identifies the deleted LPAR. added or removed from
management by the HMC.
Life Cycle CEC cec is now managed by HMC hmc. Minor Alert LifeCycleEvent indicates
whether the CEC was
where cec identifies the CEC and hmc identifies the added or removed from
HMC. management by the HMC.
Life Cycle CEC cec is no longer managed by HMC hmc. Minor Alert LifeCycleEvent indicates
whether the CEC was
where cec identifies the CEC and hmc identifies the added or removed from
HMC. management by the HMC.
CIM > System > Memory:
The Memory event occurs when the currently available memory in a system
changes with respect to availability due to a modification during a system shut
down.
Resolution
v If the severity is Critical: Replace the specified DIMM that is failing or has
failed.
informative only.
Details
Additional extended
Memory Memory configuration reduced Critical Alert None
from previous MB to current MB.
where previous is the previous

memory size and current is the
current memory size.
Memory Memory configuration increased Informational Resolution None
from previous MB to current MB.

memory size and current is the
current memory size.
CIM > System > Memory PFA:
The Memory PFA event occurs when a dual inline memory module (DIMM) in a
system is about to fail.

Resolution
failed.
informative only.
Details
Additional extended
Memory PFA Memory device identified as Critical Alert None
memory in bank slot is predicting
an imminent failure.
where slot is the affected memory

slot.
Memory PFA Memory device identified as Informational Resolution None
memory in bank slot is not
predicting a failure.
where slot is the affected memory

slot.
CIM > System > Network Adapter:
The Network Adapter events occur when a network interface card (NIC) in a
system fails, goes offline, or goes online.
Resolution
v If the severity is Critical or Warning: Replace the specified NIC that has failed.
informative only.
Details
If you select the Network Adapter check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the Network
Adapter subtree.
Additional extended
Network Not applicable Not Not v DeviceID is the ID
Adapter applicableapplicable for the component
if there are more
than one of the
same component
and you are trying
to fix a particular
instance.
v Resolution
provides
information that
can help resolve a
hardware problem
in the server.

You can choose to select specific event types that are displayed under the Network
Adapter node in the Event Filter Builder tree. The event filter will process only the
event types that you select.
Additional extended
Failed The network adapter failed. Critical Alert v DeviceID is the ID
for the component
if there are more
than one of the
same component
and you are trying
to fix a particular
instance.
v Resolution provides
information that
can help resolve a
hardware problem
in the server.
Offline The network adapter is offline. Warning Alert v DeviceID is the ID
for the component
if there are more
than one of the
same component
and you are trying
to fix a particular
instance.
information that
can help resolve a
hardware problem
in the server.
Online The network adapter is online. Informational Resolution v DeviceID is the ID
for the component
if there are more
than one of the
same component
and you are trying
to fix a particular
instance.
information that
can help resolve a
hardware problem
in the server.
CIM > System > PFA:
The PFA event occurs when the Remote Supervisor Adapter detects that a
component in a system is about to fail.
Resolution
Identify and replace the component that is generating the Predictive Failure
Analysis event.

Details
Additional extended
PFA Predictive Failure Detected. Please check Critical Alert None
the system management processor error
log for more information. This event
must be cleared manually.
CIM > System > Power State:
The Power State event occurs when a change in the power state of a CEC or LPAR
is detected.
Resolution
Details
Note: For this event, the AlertingManagedElement attribute is set to the object
path of the ComputerSystem instance.
Additional extended
Power State LPAR name has been powered on. Minor Alert PowerState identifies the
power state of the system
where name identifies the affected LPAR. using one of the following
values:
v 1 = Full Power
v 2 = Power Save - Low
Power Mode
v 3 = Power Save -
Standby
v 4 = Power Save - Other
v 5 = Power Cycle
v 6 = Power Off
v 7 = Hibernate
v 8 = Soft Off
Power State LPAR name has been powered off. Minor Alert PowerState identifies the
values:
v 1 = Full Power
Power Mode
v 3 = Power Save -
Standby
v 5 = Power Cycle
v 6 = Power Off
v 7 = Hibernate
v 8 = Soft Off

Additional extended
Power State CEC name has been powered on. Minor Alert PowerState identifies the
values:
v 1 = Full Power
Power Mode
v 3 = Power Save -
Standby
v 5 = Power Cycle
v 6 = Power Off
v 7 = Hibernate
v 8 = Soft Off
Power State CEC name has been powered off. Minor Alert PowerState identifies the
values:
v 1 = Full Power
Power Mode
v 3 = Power Save -
Standby
v 5 = Power Cycle
v 6 = Power Off
v 7 = Hibernate
v 8 = Soft Off
CIM > System > Power Supply:
The Power Supply event occurs when the state of a system power supply changes
with respect to its availability.
Resolution
v If the severity is Critical: Replace the specified power supply that has failed.
v If the severity is Warning: Check the power supply and line cord. Replace the
power supply if required.
informative only.
Details
Additional extended
Power Supply PowerSupply device identified as Critical Alert None
PowerSupply number reports
critical state with possible loss of
redundancy.
where number is the affected

power supply.

Additional extended
Power Supply PowerSupply device identified as Critical Alert None
PowerSupply number has failed.
This event must be cleared
manually.

power supply.
Power Supply PowerSupply device identified as Warning Alert None
PowerSupply number has lost AC
power and loss of standby power
is imminent.

power supply.
Power Supply PowerSupply device identified as Informational Resolution None
PowerSupply number reports
normal.

power supply.
CIM > System > Processor:
The Processor event occurs when microprocessors were removed or added during
the last system shut down
Resolution
v If the severity is Critical: Replace the specified processor that is failing or has
failed.
informative only.
Details
Additional extended
Processor Processor configuration reduced Critical Alert None
from previous CPU to current
CPU.

number of microprocessors
(CPUs) and current is the current
number of microprocessors.
Processor Processor configuration increased Informational Resolution None
from previous CPU to current
CPU.

number of microprocessors
(CPUs) and current is the current
number of microprocessors.
CIM > System > Processor PFA:
The Processor PFA event occurs when the processor is about to fail.

Resolution
failed.
informative only.
Details
Additional extended
Processor PFA Processor device identified as Critical Alert None
processor in slot slot is predicting
where slot is the affected

processor slot.
Processor PFA Processor device identified as Informational Resolution None
processor in slot slot is not
where slot is the affected

processor slot.
CIM > System > RAID:
The RAID events occur when a change in the state of a Platform Agent managed
system or Common Agent managed system that includes a RAID configuration is
detected.
Resolution
Not applicable
Details
If you select the RAID check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the System subtree.
Event type Event text Severity Category Extended attributes
RAID Not applicable Not Not None
CIM > System > RAID > RAID Array FlashCopy Complete:
The RAID Array FlashCopy® Complete event occurs when a RAID FlashCopy
operation is completed on a specified array in a RAID configuration. This event
can be generated by ServeRAID options.
Resolution

Details
Additional
Event type Event text Severity Category extended details
RAID Array FlashCopy with backup Informational Resolution None
FlashCopy complete: array.
Complete
where array is the affected array.
CIM > System > RAID > RAID Array FlashCopy Detected:
The RAID Array FlashCopy Detected event occurs when a RAID FlashCopy
operation is in progress on a specified array in a RAID configuration. This event
Resolution
Details
Event Additional extended
type Event text Severity Category details
RAID FlashCopy in progress: array. InformationalResolution None
Array
FlashCopy where array is the affected array.
Detected
CIM > System > RAID > RAID Array FlashCopy Fail:
The RAID Array FlashCopy Fail event occurs when a RAID FlashCopy operation
fails on a specified array in a RAID configuration. This event can be generated by
ServeRAID options.
Resolution
The FlashCopy operation failed because a hardware error occurred. The specified
logical drive might be offline.
If the source logical drive is offline, replace the failed hard disk drives and restore
the data from tape backup. If the target logical drive is offline, replace the failed
hard disk drives. FlashCopy operations will not work when the source or target
logical drives are offline.
If the source or target logical drives are not offline, complete the following steps:
1. Verify that the controller, cables, and hard disk drives are installed correctly.
2. Verify that there is power to the hard disk drives.
3. Retry the command.
4. If the command still fails, restart the server and retry the command.
5. If the problem persists, contact your service representative.

Details
Event type Event text Severity CategoryAdditional extended details
RAID Array FlashCopy with backup failed: array Critical Alert None
FlashCopy [error]
Fail
where array is the affected array and
error is the error code.
CIM > System > RAID > RAID Array Rebuild Complete:
The RAID Array Rebuild Complete event occurs when a RAID rebuild operation is
completed on a specified array in a RAID configuration. This event can be
generated by ServeRAID options and integrated SCSI controllers with RAID
capabilities (LSI 1064 controllers).
Resolution
Details
RAID Rebuild complete: array Informational Resolution None
Array
Rebuild where array is the affected array.
Complete
CIM > System > RAID > RAID Array Rebuild Detected:
The RAID Array Rebuild Detected event occurs when a RAID rebuild operation is
in progress on a specified array in a RAID configuration. This event can be
Resolution
Details
RAID Rebuilding: array Informational Resolution None
Array
Rebuild where array is the affected array.
Detected
CIM > System > RAID > RAID Array Rebuild Fail:
The RAID Array Rebuild Fail event occurs when a RAID rebuild operation fails on
a specified array in a RAID configuration. This event can be generated by
ServeRAID options and integrated SCSI controllers with RAID capabilities (LSI
1064 controllers).

Resolution
A hardware error occurred. To correct the error, complete the following steps:
Details
RAID Array Rebuild failed: array [error] Critical Alert None
Rebuild Fail
CIM > System > RAID > RAID Array Sync Complete:
The RAID Array Sync Complete event occurs when a RAID synchronization
operation is completed on a specified array in a RAID configuration. This event
Resolution
Details
RAID Synchronize complete: array InformationalResolution None
Array
Sync where array is the affected array.
Complete
CIM > System > RAID > RAID Array Sync Detected:
The RAID Array Sync Detected event occurs when a RAID synchronization
operation is in progress on a specified array in a RAID configuration. This event
Resolution
Details
RAID Synchronizing: array Informational Resolution None
Array
Sync where array is the affected array.
Detected

CIM > System > RAID > RAID Array Sync Fail:
The RAID Array Sync Fail event occurs when a RAID synchronization operation
fails on a specified array in a RAID configuration. This event can be generated by
ServeRAID options.
Resolution
A hardware error occurred. Verify that the specified logical drive is not offline or
critical (that is, one hard disk drive that is offline in a RAID level-1, 1E, 5, 5E, 10,
1E0, or 50 logical drive). If the logical drive is critical, replace the failed hard disk
drive. If the logical drive is offline, replace the failed hard disk drives and restore
the data from tape backup.
If the source or target logical drives are not offline or critical, complete the
following steps:
Details
RAID Array Synchronize failed: array [error] Critical Alert None
Sync Fail
CIM > System > RAID > RAID Compaction Complete:
The RAID Compaction Complete event occurs when a RAID compaction operation
is completed on a specified logical drive in a RAID configuration. This event can
be generated by ServeRAID options.
Resolution
Details
RAID Compaction complete: drive Informational Resolution None
Compaction
Complete where drive is the affected logical drive.
CIM > System > RAID > RAID Compaction Detected:
The RAID Compaction Detected event occurs when a RAID compaction operation
is in progress on a specified logical drive in a RAID configuration. This event can

Resolution
Details
RAID Compacting: drive Informational Resolution None
Compaction
Detected where drive is the affected logical drive.
CIM > System > RAID > RAID Compaction Fail:
The RAID Compaction Fail event occurs when a RAID compaction operation fails
on a specified logical drive in a RAID configuration. This event can be generated
by ServeRAID options.
Resolution
A hardware error occurred. Determine if one or more hard disk drives that are part
of the specified logical drive have failed. If such a failure has occurred, restore the
data from a tape backup. Otherwise, complete the following steps:
Details
Additional
extended
RAID Compaction Compaction failed: drive [error] Critical Alert None
Fail
where drive is the affected logical
drive and error is the error code.
CIM > System > RAID > RAID Compression Complete:
The RAID Compression Complete event occurs when a RAID compression

operation is completed on a specified logical drive in a RAID configuration. This
event can be generated by ServeRAID options.
Resolution
Details
RAID Compression complete: drive Informational Resolution None
Compression

CIM > System > RAID > RAID Compression Detected:
The RAID Compression Detected event occurs when a RAID compression

operation is in progress on a specified logical drive in a RAID configuration. This
Resolution
Details
RAID Compressing: drive Informational Resolution None
Compression
CIM > System > RAID > RAID Compression Fail:
The RAID Compression Fail event occurs when a RAID compression operation
fails on a specified logical drive in a RAID configuration. This event can be
generated by ServeRAID options.
Resolution
Details
RAID Compression failed: drive [error] Critical Alert None
Compression
Fail where drive is the affected logical drive
and error is the error code.
CIM > System > RAID > RAID Config Fail:
The RAID Config Fail event occurs when a RAID controller configuration cannot
be read. This event can be generated by ServeRAID options.
Resolution

5. If the problem persists, complete the following steps:
a. Restore to factory-default settings.
b. Recreate the configuration.
Details
RAID Error getting controller configuration. Critical Alert None
Config Fail
CIM > System > RAID > RAID Controller Added:
The RAID Controller Added event occurs when a specified RAID controller is
added to a system. This event can be generated by ServeRAID options.
Resolution
Details
RAID A controller has been added to the Informational Resolution None
Controller system: controller.
Added
where controller is the added controller.
CIM > System > RAID > RAID Controller Bad Stripes:
The RAID Controller Bad Stripes event occurs when one or more logical drives
contain at least one bad stripe. This event can be generated by ServeRAID options.
Resolution
The Bad Stripe Table (BST) provides a means of recovering most data on a logical
drive after multiple hardware errors prevent access to a logical drive stripe. An
entry in the BST indicates that the data contained in a stripe has been lost.
While many conditions can produce a Bad Stripe Table entry, the most common
cause is an error accessing one of the stripe units within a stripe of a critical logical
drive. A single stripe unit failure is correctable and recoverable but two or more
failures within the same redundant RAID stripe are not.
For example, in a critical RAID-5 array, in which one of the drives in the array is
defunct, a stripe will be marked bad with an entry in the BST if a non-recoverable
media error occurs when accessing one of the other drives of the array.
After an entry is logged in the BST, the controller will return an error code to the
driver whenever the host system tries to access a Logical Block Address (LBA)
within the affected stripe. This is one immediate indication that some part of the
logical drive is unusable.
Note: It is not possible to correlate the bad stripe with a specific file in the
operating system.

To resolve this error, complete the following steps:
v Check the event logs to identify the affected logical drives.
v Because the data has been lost, the only way to recover from this condition is to
complete the following steps:
1. Delete the array.
2. Recreate the array and its logical drives.
3. Restore the data from backup media.
Note: The alternative is to take the entire logical drive offline, thus resulting in
the loss of all data contained on that logical drive.
To minimize the risk of lost data, schedule frequent periodic backups.
Details
RAID One or more logical drives contain a Warning Alert None
Controller bad stripe: controller.
Bad Stripes
where controller is the controller for the
affected logical drives.
CIM > System > RAID > RAID Controller Battery Overtemp:
The RAID Controller Battery Overtemp event occurs when the battery on a
specified RAID controller has exceeded its temperature threshold. This event can
Resolution
Battery temperature has exceeded 50 degrees Celsius. To resolve this error,

1. Verify that the controller is installed correctly.
2. Verify that the server has adequate ventilation.
3. If the problem persists, the battery might have failed or the server might
require service. Contact your service representative.
Details
RAID The battery has exceeded normal Warning Alert None
Controller operating temperature: controller.
Battery
Overtemp where controller is the affected
controller.
CIM > System > RAID > RAID Controller Battery Temp Normal:
The RAID Controller Battery Temp Normal event occurs when the battery on a
specified RAID controller has a normal temperature. This event can be generated
Resolution

Details
RAID The battery operating temperature is Informational Resolution None
Controller normal: controller.
Battery
Temp where controller is the affected controller.
Normal
CIM > System > RAID > RAID Controller Fail:
The RAID Controller Fail event occurs when a specified RAID controller fails. This
Resolution
Details
RAID Commands are not responding: Critical Alert None
Controller controller.
Fail
where controller is the affected
controller.
CIM > System > RAID > RAID Controller Failover:
The RAID Controller Failover event occurs when a specified RAID controller fails
over and the passive controller in the failover pairing is now active. This event can
Resolution
Details
RAID A controller failover was detected: Critical Alert None
Controller controller.
Failover
where controller is the controller that
failed.
CIM > System > RAID > RAID Controller Mismatched Versions:

The RAID Controller Mismatched Versions event occurs when the versions of the
BIOS, firmware, and driver for a specified RAID controller do not match. This
Resolution
Upgrade to the latest version of the RAID BIOS, firmware, and device driver.
Details
RAID Version mismatch detected: controller. Warning Alert None
Controller The BIOS (version version), Firmware
Mismatched (version version), and Driver (version
Versions version) are not a matched set and are
not compatible.

controller and version is the version of
the affected RAID code.
CIM > System > RAID > RAID Controller Replaced:
The RAID Controller Replaced event occurs when a specified controller is replaced
in a RAID configuration. This event can be generated by ServeRAID options.
Resolution
Details
RAID A controller has been replaced in the Informational Resolution None
Controller system: controller.
Replaced
controller.
CIM > System > RAID > RAID Copyback Complete:
The RAID Copyback Complete event occurs when a copy-back operation is

completed on a specified logical drive in a RAID configuration. This event can be
Resolution
Details
RAID Copy back complete: location. Informational Resolution None
Copyback
Complete where location is the affected controller
and array.

CIM > System > RAID > RAID Copyback Detected:
The RAID Copyback Detected event occurs when a copy-back operation is in

progress on a specified logical drive in a RAID configuration. This event can be
Resolution
Details
RAID Copy back in progress: location. Source: Informational Resolution None
Copyback Channel channel, SCSI ID id. Target:
Detected Channel channel, SCSI ID id.
where:
v location is the affected controller and
array
v channel is the specified channel
v id is the specified SCSI ID
CIM > System > RAID > RAID Copyback Fail:
The RAID Copyback Fail event occurs when a copy-back operation fails on a
specified logical drive in a RAID configuration. This event can be generated by
ServeRAID options.
Resolution
A hardware error occurred. To resolve this error, complete the following steps:
4. If the problem persists, replace the specified drive.
Details
RAID Copy back failed: location [error]. Critical Alert None
Copyback
Fail where location is the affected controller
and array and error is the error code.
CIM > System > RAID > RAID Dead Battery:
The RAID Dead Battery event occurs when the battery fails on a specified
controller. This event can be generated by ServeRAID options.

Resolution
To resolve this problem, complete the following steps:

1. Verify that the battery on the battery-backup cache device is installed properly.
2. If the problem persists, replace the battery.
Details
RAID Dead The battery-backup cache device needs Critical Alert None
Battery a new battery: controller.

controller.
CIM > System > RAID > RAID Dead Battery Cache:
The RAID Dead Battery Cache event occurs when the battery-backup cache fails on
a specified controller. This event can be generated by ServeRAID options.
Resolution
The battery-backup cache device is installed improperly or is defective. To resolve

this error, complete the following steps:
1. Verify that the battery-backup cache device is installed properly.
2. If the battery-backup cache device is installed properly but is defective, contact
your service representative.
Details
RAID Dead The battery-backup cache device is Critical Alert None
Battery defective: controller. Error code: error.
Cache
controller and error is the error code.
CIM > System > RAID > RAID Decompression Complete:
The RAID Decompression Complete event occurs when a RAID decompression

operation is completed on a specified logical drive in a RAID configuration.This
Resolution
Details
Additional extended
RAID Decompression complete: drive. Informational Resolution None
Decompression
Complete where drive is the affected logical
drive.

CIM > System > RAID > RAID Decompression Detected:
The RAID Decompression Detected event occurs when a RAID decompression

operation is in progress on a specified logical drive in a RAID configuration.This
Resolution
Details
Additional extended
RAID Decompressing: drive. Informational Resolution None
Decompression
CIM > System > RAID > RAID Decompression Fail:
The RAID Decompression Fail event occurs when a RAID decompression

operation fails on a specified logical drive in a RAID configuration.This event can
Resolution
Details
RAID Decompression failed: drive [error]. Critical Alert None
Decompression
CIM > System > RAID > RAID Defunct Drive:
The RAID Defunct Drive event occurs when a specified hard disk drive fails in a
RAID configuration. This event can be generated by ServeRAID options and
integrated SCSI controllers with RAID capabilities (LSI 1020, 1030, and 1064
controllers).
Resolution
A hardware error occurred. To resolve the error, complete one of the following
steps:
v If the specified hard disk drive is part of an array, refer to the event pertaining
to the logical drives in that array for additional information.

v If the specified hard disk drive is not part of an array, contact your service
representative.
Details
RAID Defunct drive: location. Critical Alert None
Defunct
Drive where location is the affected controller
and port.
CIM > System > RAID > RAID Defunct Drive FRU:
The RAID Defunct Drive FRU event occurs when a specified hard disk drive with
the provided field-replaceable unit (FRU) number fails in a RAID
configuration.This event can be generated by ServeRAID options.
Resolution
steps:
representative.
Details
RAID Defunct drive: location (FRU Part # Critical Alert None
Defunct FRU).
Drive FRU
where location is the affected controller
and port and FRU is the FRU number
of the hard disk drive.
RAID Defunct drive - I/O subsystem error: Critical Alert None
Defunct location (FRU Part # FRU).
Drive FRU
and port and FRU is the FRU number
of the hard disk drive.
CIM > System > RAID > RAID Defunct Replaced:
The RAID Defunct Replaced event occurs when a specified defunct hard disk drive
has been set to the hot-spare state in a RAID configuration.This event can be
Resolution

Details
RAID A drive is set to hot-spare: location Informational Resolution None
Defunct (error).
Replaced
and port and error is the error code.
CIM > System > RAID > RAID Drive Added:
The RAID Drive Added event occurs when a specified hard disk drive is added to
a RAID configuration.This event can be generated by ServeRAID options and
integrated SCSI controllers with RAID capabilities (LSI 1064 controllers).
Resolution
Details
Additional extended
RAID Physical drive added: location. InformationalResolution None
Drive
Added where location is the affected controller
and port.
CIM > System > RAID > RAID Drive Clear Complete:
The RAID Drive Clear Complete event occurs when a RAID clear operation is
completed on a specified hard disk drive in a RAID configuration.This event can
Resolution
Details
Additional extended
RAID Clear complete: drive. InformationalResolution None
Drive
Clear where drive is the affected hard disk
Complete drive.
CIM > System > RAID > RAID Drive Clear Detected:
The RAID Drive Clear Detected event occurs when a RAID clear operation is in
progress on a specified hard disk drive in a RAID configuration.This event can be
Resolution

Details
Additional extended
Event type Event text Severity Category attributes
RAID Clearing: drive. InformationalResolution None
Drive
Clear where drive is the affected hard disk
Detected drive.
CIM > System > RAID > RAID Drive Clear Fail:
The RAID Drive Clear Fail event occurs when a RAID clear operation fails on a
specified hard disk drive in a RAID configuration.This event can be generated by
ServeRAID options.
Resolution
A hardware error occurred. To resolve the error, complete the following steps:
5. If the command still fails, replace the specified drive.
Details
RAID Drive Clear failed: drive [error]. Critical Alert None
Clear Fail
drive and error is the error code.
CIM > System > RAID > RAID Drive Removed:
The RAID Drive Removed event occurs when a specified hard disk drive is
removed from a RAID configuration.This event can be generated by ServeRAID
options.
Resolution
Details
Additional extended
RAID Physical drive removed: location. InformationalResolution None
Drive
Removed where location is the affected controller
and port.
CIM > System > RAID > RAID Drive Verify Complete:

The RAID Drive Verify Complete event occurs when a RAID verify operation is
completed on a specified hard disk drive in a RAID configuration.
Resolution
Details
Additional extended
RAID Verify complete: drive. Informational Resolution None
Drive
Verify where drive is the affected hard disk
Complete drive.
CIM > System > RAID > RAID Drive Verify Detected:
The RAID Drive Verify Detected event occurs when a RAID verify operation is in
progress on a specified hard disk drive in a RAID configuration. This event can be
Resolution
Details
RAID Verifying: drive. InformationalResolution None
Drive
Verify where drive is the affected hard disk
Detected drive.
CIM > System > RAID > RAID Drive Verify Fail:
The RAID Drive Verify Fail event occurs when a RAID verify operation fails on a
specified hard disk drive in a RAID configuration. This event can be generated by
ServeRAID options.
Resolution
following steps:

Details
RAID Drive Verify failed: drive. Critical Alert None
Verify Fail
drive.
CIM > System > RAID > RAID Enclosure Fail:
The RAID Enclosure Fail event occurs when an enclosure has failed on a specified
controller and channel in a RAID configuration. This event can be generated by
ServeRAID options.
Resolution
Details
RAID Enclosure device is not responding: Critical Alert None
Enclosure location.
Fail
where location is the controller and
channel that the affected enclosure is
attached to.
CIM > System > RAID > RAID Enclosure Fan Fail:
The RAID Enclosure Fan Fail event occurs when a specified enclosure fan fails on
a specified controller and channel in a RAID configuration. This event can be
Resolution
A hardware error occurred. Verify that the fan in the enclosure device is installed
correctly. If it is, complete the following steps:
5. If the problem persists, replace the specified fan.

Details
RAID Enclosure fan fan is malfunctioning: Critical Alert None
Enclosure location.
Fan Fail
where fan is the affected fan and
location is the controller and channel
that the affected enclosure is attached
to.
CIM > System > RAID > RAID Enclosure Fan Installed:
The RAID Enclosure Fan Installed event occurs when a specified enclosure fan is
installed on a specified controller and channel in a RAID configuration. This event
Resolution
Details
The ServeRAID Agent sends these events for IBM Systems Director to indicate that
a change has occurred in the ServeRAID subsystem.
Additional extended
RAID Enclosure fan fan has been installed: InformationalResolution None
Enclosure location.
Fan
Installed where fan is the affected fan and location
is the controller and channel that the
affected enclosure is attached to.
CIM > System > RAID > RAID Enclosure Fan OK:
The RAID Enclosure Fan OK event occurs when a specified enclosure fan is
functioning correctly on a specified controller and channel in a RAID
configuration. This event can be generated by ServeRAID options.
Resolution
Details
Additional extended
RAID Enclosure fan fan is now operational: InformationalResolution None
Enclosure location.
Fan OK
where fan is the affected fan and location
is the controller and channel that the
CIM > System > RAID > RAID Enclosure Fan Removed:

The RAID Enclosure Fan Removed event occurs when a specified enclosure fan is
removed on a specified controller and channel in a RAID configuration. This event
Resolution
Details
RAID Enclosure fan fan has been removed: Warning Alert None
Enclosure location.
Fan
Removed where fan is the affected fan and
location is the controller and channel
that the affected enclosure is attached
to.
CIM > System > RAID > RAID Enclosure OK:
The RAID Enclosure OK event occurs when an enclosure is functioning correctly

on a specified controller and channel in a RAID configuration. This event can be
Resolution
Details
Additional extended
RAID Enclosure device is responding: location. InformationalResolution None
Enclosure
OK where location is the controller and
attached to.
CIM > System > RAID > RAID Enclosure Power Supply Fail:
The RAID Enclosure Power Supply Fail event occurs when the specified enclosure
power supply fails in a RAID configuration. This event can be generated by
ServeRAID options.
Resolution
A hardware error occurred. Verify that the power supply in the enclosure device is
installed correctly. If it is, complete the following steps:
5. If the problem persists, replace the specified power supply.

Details
RAID Enclosure power supply supply is Critical Alert None
Enclosure malfunctioning: location.
Power
Supply Fail where supply is the affected power
supply and location is the controller
and channel that the affected enclosure
is attached to.
CIM > System > RAID > RAID Enclosure Power Supply Installed:
The RAID Enclosure Power Supply Installed event occurs when a specified
enclosure power supply is installed in a RAID configuration. This event can be
Resolution
Details
type Event text Severity Category attributes
RAID Enclosure power supply supply has been InformationalResolution None
Enclosure installed: location.
Power
Supply where supply is the affected power
Installed supply and location is the controller and
attached to.
CIM > System > RAID > RAID Enclosure Power Supply OK:
The RAID Enclosure Power Supply OK event occurs when a specified enclosure
power supply is functioning correctly in a RAID configuration. This event can be
Resolution
Details
Additional extended
RAID Enclosure power supply supply is now Informational Resolution None
Enclosure operational: location.
Power
OK supply and location is the controller and
attached to.
CIM > System > RAID > RAID Enclosure Power Supply Removed:

The RAID Enclosure Power Supply Removed event occurs when a specified
enclosure power supply is removed from a RAID configuration. This event can be
Resolution
Details
RAID Enclosure power supply supply has Warning Alert None
Enclosure been removed: location.
Power
Removed supply and location is the controller
and channel that the affected enclosure
is attached to.
CIM > System > RAID > RAID Enclosure Temp Fail:
The RAID Enclosure Temp Fail event occurs when an enclosure temperature
exceeds a normal range on a specified controller in a RAID configuration. This
Resolution
A hardware error occurred. Verify that the fans in the enclosure device are installed
correctly and working. If they are, complete the following steps:
Details
RAID Enclosure temperature is out of the Critical Alert None
Enclosure normal range: location.
Temp Fail
attached to.
CIM > System > RAID > RAID Enclosure Temp OK:
The RAID Enclosure Temp OK event occurs when an enclosure temperature is

within a normal range on a specified controller in a RAID configuration. This
Resolution

Details
Additional extended
RAID Enclosure temperature is in the normal InformationalResolution None
Enclosure range: location.
Temp OK
attached to.
CIM > System > RAID > RAID Expansion Complete:
The RAID Expansion Complete event occurs when a RAID expansion operation is
Resolution
Details
Additional extended
RAID Expansion complete: drive. InformationalResolution None
Expansion
CIM > System > RAID > RAID Expansion Detected:
The RAID Expansion Detected event occurs when a RAID expansion operation is
in progress on a specified logical drive in a RAID configuration. This event can be
Resolution
Details
RAID Expanding: drive. InformationalResolution None
Expansion
CIM > System > RAID > RAID Expansion Fail:
The RAID Expansion Fail event occurs when a RAID expansion operation fails on
a specified logical drive in a RAID configuration. This event can be generated by
ServeRAID options.

Resolution
Details
RAID Expansion failed: drive [error]. Critical Alert None
Expansion
CIM > System > RAID > RAID > FlashCopy Complete:
The RAID FlashCopy Complete event occurs when a RAID FlashCopy operation is
Resolution
Details
Additional extended
RAID FlashCopy with backup complete: drive. InformationalResolution None
FlashCopy
CIM > System > RAID > RAID > FlashCopy Detected:
The RAID FlashCopy Detected event occurs when a RAID FlashCopy operation is
Resolution
Details
RAID FlashCopy in progress: drive. InformationalResolution None
FlashCopy
CIM > System > RAID > RAID > FlashCopy Fail:

The RAID FlashCopy Fail event occurs when a RAID FlashCopy operation fails on
ServeRAID options.
Resolution
logical drive might be offline. If the source logical drive is offline, replace the failed
hard disk drives and restore the data from tape backup. If the target logical drive
is offline, replace the failed hard disk drives. FlashCopy operations will not work
when the source or target logical drives are offline.
Details
RAID FlashCopy with backup failed: drive Critical Alert None
FlashCopy [error].
Fail
where drive is the affected logical drive
CIM > System > RAID > RAID Init Complete:
The RAID Init Complete event occurs when a RAID initialization operation is
Resolution
Details
Additional extended
RAID Init Clear complete: drive. InformationalResolution None
Complete
where drive is the affected logical drive.
CIM > System > RAID > RAID Init Detected:
The RAID Init Detected event occurs when a RAID initialization operation is in
Resolution

Details
RAID Init Clearing: drive. InformationalResolution None
Detected
CIM > System > RAID > RAID Init Fail:
The RAID Init Fail event occurs when a RAID initialization operation fails on a
ServeRAID options.
Resolution
A hardware error occurred. Verify that the specified logical drive is not offline. If
the logical drive is offline, replace the failed hard disk drives and restore the data
from tape backup. If the specified logical drive is not offline, complete the
following steps:
Details
RAID Init Initialize failed: drive. Critical Alert None
Fail
where drive is the affected logical
drive.
CIM > System > RAID > RAID Logical Drive Added:
The RAID Logical Drive Added event occurs when a specified logical drive is
added in a RAID configuration. This event can be generated by ServeRAID
options.
Resolution
Details
Additional extended
RAID Added logical drive: drive. Size data. InformationalResolution None
Logical
Drive where drive is the affected logical drive
Added and data is the size and RAID level of
that logical drive.
CIM > System > RAID > RAID Logical Drive Blocked:

The RAID Logical Drive Blocked event occurs when a specified logical drive is in
the blocked state. This event can be generated by ServeRAID options.
Resolution
When the RAID controller performs a rebuild operation on an array, it reconstructs

the data that was stored in RAID level-1 and RAID level-5 logical drives. However,
the RAID controller cannot reconstruct the data that was stored in any RAID
level-0 logical drives in that array. The data in the RAID level-0 logical drives is
blocked when The RAID controller detects that the array is valid, but the data
might be damaged.
To resolve this error, unblock the logical drive after the rebuild is complete. Restore
the data from tape.
Details
RAID Logical drive is blocked: drive. Critical Alert None
Logical
Drive where drive is the affected logical
Blocked drive.
CIM > System > RAID > RAID Logical Drive Critical:
The RAID Logical Drive Critical event occurs when a specified logical drive is in
the critical state. This event can be generated by ServeRAID options.
Resolution
A hard disk drive is defunct in the specified logical drive. The data on this logical
drive is at risk. If another hard disk drive fails, the data might be lost.
Complete one of the following actions:

v If a rebuild operation is in progress, wait until the rebuild is complete.
v If a rebuild operation is not in progress, replace the failed hard disk drive with a
new hard disk drive. After the hard disk drive is replaced, a rebuild operation
will start automatically. See the troubleshooting chapter of the IBM ServeRAID
User's Reference.
Details
RAID Logical drive is critical: drive. Warning Alert None
Logical
Drive where drive is the affected logical
Critical drive.
CIM > System > RAID > RAID Logical Drive Critical Periodic:
The RAID Logical Drive Critical Periodic event occurs when a periodic scan
detects that one or more logical drives are in a critical state. This event can be

Resolution

User's Reference
Details
RAID Periodic scan found one or more Warning Alert None
Logical critical logical drives: drive. Repair as
Drive soon as possible to avoid data loss.
Critical
Periodic where drive is the affected logical
drive.
CIM > System > RAID > RAID Logical Drive Off Line:
The RAID Logical Drive Off Line event occurs when a specified logical drive is in
the offline state. This event can be generated by ServeRAID options and integrated
SCSI controllers with RAID capabilities (LSI 1064 controllers).
Resolution
A hardware error occurred. Contact your service representative.
Details
RAID Logical drive is offline: drive. Critical Alert None
Logical
Drive Off where drive is the affected logical
Line drive.
CIM > System > RAID > RAID Logical Drive OK:
The RAID Logical Drive OK event occurs when a specified logical drive is
functioning correctly. This event can be generated by ServeRAID options.
Resolution
Details
Additional extended
RAID Logical drive is normal: drive. InformationalResolution None
Logical
Drive OK where drive is the affected logical drive.

CIM > System > RAID > RAID Logical Drive Removed:
The RAID Logical Drive Removed event occurs when a specified logical drive has
been removed from a RAID configuration. This event can be generated by
ServeRAID options.
Resolution
Details
Additional extended
RAID Deleted logical drive: drive. InformationalResolution None
Logical
Drive where drive is the affected logical drive.
Removed
CIM > System > RAID > RAID Logical Drive Unblocked:
The RAID Logical Drive Unblocked event occurs . when a specified logical drive is
in the unblocked state. This event can be generated by ServeRAID options.
Resolution
Details
Additional extended
RAID Unblocked logical drive: drive. InformationalResolution None
Logical
Drive where drive is the affected logical drive.
Unblocked
CIM > System > RAID > RAID Migration Complete:
The RAID Migration Complete event occurs when a RAID logical-drive migration
is completed on a specified logical drive in a RAID configuration. This event can
Resolution
Details
Additional extended
RAID Migration complete: drive. InformationalResolution None
Migration
CIM > System > RAID > RAID Migration Detected:

The RAID Migration Detected event occurs when a RAID logical-drive migration is
Resolution
Details
Additional extended
RAID Migrating: drive. InformationalResolution None
Migration
CIM > System > RAID > RAID Migration Fail:
The RAID Migration Fail event occurs when a RAID logical-drive migration fails
on a specified logical drive in a RAID configuration. This event can be generated
Resolution
Details
RAID Migration failed: drive [error]. Critical Alert None
Migration
CIM > System > RAID > RAID No Controllers:
The RAID No Controllers event occurs when no RAID controllers are detected.
This event can be generated by ServeRAID options.
Resolution
Details
Additional extended
RAID No No controllers were found in this InformationalResolution None
Controllers system

CIM > System > RAID > RAID PFA Drive:
The RAID PFA Drive event occurs when a Predictive Failure Analysis (PFA) is
detected on a specified hard disk drive in a RAID configuration. This event can be
Resolution
The hard disk drive is going to fail. Contact your service representative.
Details
RAID PFA PFA detected for drive: drive. Warning Alert None
Drive
drive.
CIM > System > RAID > RAID PFA Drive FRU:
The RAID PFA Drive FRU event occurs when a Predictive Failure Analysis (PFA) is
detected on a specified hard disk drive with a specified field-replaceable unit
(FRU) number in a RAID configuration. This event can be generated by ServeRAID
options.
Resolution
Details
RAID PFA PFA detected for drive: drive (FRU). Warning Alert None
Drive FRU
drive and FRU is the FRU number of
that drive.
CIM > System > RAID > RAID Polling Fail:
The RAID Polling Fail event occurs when a specified controller fails to respond to
background polling commands. This event can be generated by ServeRAID
options.
Resolution

Details
RAID Background polling commands are not Warning Alert None
Polling Fail responding: controller. Result codes:
error.

controller and error is the error code.
CIM > System > RAID > RAID Rebuild Complete:
The RAID Rebuild Complete event occurs when a RAID rebuild operation is
Resolution
Details
Additional extended
RAID Rebuild complete: drive. Informational Resolution None
Rebuild
CIM > System > RAID > RAID Rebuild Detected:
The RAID Rebuild Detected event occurs when a RAID rebuild operation is in
Resolution
Details
RAID Rebuilding: drive. Informational Resolution None
Rebuild
CIM > System > RAID > RAID Rebuild Fail:
The RAID Rebuild Fail event occurs when a RAID rebuild operation fails on a
ServeRAID options.
Resolution

Details
RAID Rebuild failed: drive [error]. Critical Alert None
Rebuild Fail
CIM > System > RAID > RAID Sync Complete:
The RAID Sync Complete event occurs when a RAID synchronization operation is
Resolution
Details
Additional extended
RAID Sync Synchronize complete: drive. InformationalResolution None
Complete
CIM > System > RAID > RAID Sync Detected:
The RAID Sync Detected event occurs when a RAID synchronization operation is
capabilities (LSI 1020 and 1030 controllers).
Resolution
Details
Additional extended
RAID Synchronizing: drive. Informational Resolution None
Sync
CIM > System > RAID > RAID Sync Fail:
The RAID Sync Fail event occurs when a RAID synchronization operation fails on
ServeRAID options and integrated SCSI controllers with RAID capabilities (LSI
1020 and 1030 controllers).

Resolution
If the specified logical drive is not offline or critical, complete the following steps:
Details
RAID Sync Synchronize failed: drive [error]. Critical Alert None
Fail
CIM > System > RAID > RAID Test Event:
The RAID Test Event event occurs when a RAID test event is generated. This event
Resolution
Details
Additional extended
RAID Test This is a test event. InformationalAlert None
Event
CIM > System > RAID > RAID Unsupported Drive:
The RAID Unsupported Drive event occurs when an unsupported hard disk drive
is detected in a RAID configuration. This event can be generated by ServeRAID
options.
Resolution
Replace the specified hard disk drive with a hard disk drive model that is
supported by IBM RAID options.

Details
RAID Possible non-warranted physical drive Warning Alert None
Unsupported found: drive.
Drive
drive.
CIM > System > Redundant Network Adapter Failover:
The Redundant Network Adapter Failover event occurs when the state of a system
network interface card (NIC) changes with respect to its redundancy. There are
certain limitations of the NIC that cannot be compensated for between a
switchover and a switchback.
Resolution
Check the network connection.
Details
Additional extended
Redundant A network interface card (NIC) failover Warning Alert None
Network has occurred. This requires a teamed
Adapter configuration.
Failover
CIM > System > Redundant Network Adapter Switchback:
The Redundant Network Adapter Switchback event occurs when the primary
network interface card (NIC) is restored in a teamed NIC configuration.
Resolution
The error has been resolved. This event is informative only.
Details
Additional extended
Redundant Onboard NIC has Switched Back Normal Alert None
Network
Adapter
Switchback
Redundant NIC in PCI Bus bus Slot slot has Normal Alert None
Network Switched Back
Adapter
Switchback where bus is the affected bus and slot is
the affected slot.
Redundant NIC in PCI Slot slot has Switched Back Normal Alert None
Network
Adapter where slot is the affected slot.
Switchback

Additional extended
Redundant NIC has Switched Back Normal Alert None
Network
Adapter
Switchback
CIM > System > Redundant Network Adapter Switchover:
The Redundant Network Adapter Switchover event occurs when the primary
network interface card (NIC) fails in a teamed NIC configuration and the standby
NIC becomes the active NIC.
Resolution
Details
Additional extended
Redundant Onboard NIC has Switched Over Warning Alert None
Network
Adapter
Switchover
Redundant NIC in PCI Bus bus Slot slot has Warning Alert None
Network Switched Over.
Adapter
Switchover where bus is the affected bus and slot is
the affected slot.
Redundant NIC in PCI Slot slot has Switched Over. Warning Alert None
Network
Adapter where slot is the affected slot.
Switchover
Redundant NIC has Switched Over Warning Alert None
Network
Adapter
Switchover
CIM > System > Remote Login:
The Remote Login event occurs when an end-user or application has logged in to
the Web interface of the Remote Supervisor Adapter.
Resolution
Details
Additional extended
Remote Login The system management processor has Warning Alert None
been accessed via a remote login. This
event must be cleared manually.

CIM > System > Server Power Supply:
The Server Power Supply event occurs when the state of a system power supply
changes with respect to its availability.
Resolution
v If the severity is Critical or Warning: Check the power supply and line cord.
Replace the power supply if required.
informative only.
Details
Additional extended
Server Power PowerSupply device identified as Critical Alert None
Supply PowerSupply number reports
critical state with possible loss of
redundancy.

power supply.
Server Power PowerSupply device identified as Critical Alert None
Supply PowerSupply number has failed.
This event must be cleared
manually.

power supply.
Server Power PowerSupply device identified as Warning Alert None
Supply PowerSupply number has lost AC
power and loss of standby power
is imminent.

power supply.
Server Power PowerSupply device identified as Informational Resolution None
Supply PowerSupply number reports
normal.

power supply.
CIM > System > Service Event:
The Service Event event occurs when a change in the hardware status of a CEC or
LPAR managed by the HMC is detected or when a miscellaneous serviceable
hardware error on a IBM Power managed system running AIX is resolved.
For IBM Power servers running AIX, when a miscellaneous serviceable hardware
error is fixed by an IBM Customer Engineer, a Service Event occurs to indicate that
a problem in a particular hardware resource has been fixed. The CIM > System >
System Event event occurs when a miscellaneous serviceable hardware error is
detected.
Resolution
v If the category is Resolution: No resolution. This event is informative only.

v If the severity is Warning: For the HMC, contact your service representative to
correct the problem and close the open problem report in “Service Focal Point.”
Details
Service Event Note: This text varies depending on the Warning Alert None
Service Event that is received on the HMC.
The provided text is a description of that
Service Event occurrence.
Service Event Note: This text varies depending on the Informational Resolution None
Service Event that is received on the HMC.
Service Event Note: This text varies depending on the Informational Resolution None
IBM Power hardware resource that is fixed.
CIM > System > SMART Drive:
The SMART Drive event occurs when the state of an IDE or SCSI hard disk drive
that complies with the self-monitoring, analysis, and reporting technology
(SMART) changes with respect to its availability. For physical drives in a RAID
configuration managed by an integrated SCSI controller with RAID capabilities
(LSI 1020 or 1030), this event is generated when a PFA (Predictive Failure Analysis)
error is detected.
Resolution
v If the severity is Critical: Replace the specified hard disk drive that is failing or
has failed.
informative only.
Details
Additional extended
SMART Drive Device device identified as Critical Alert None
physical drive drive is predicting
where Device is IDE, SCSI, or

Unknown and drive is the affected
SMART drive.
SMART Drive Device device identified as Informational Resolution None
physical drive drive is not
where Device is IDE, SCSI, or

Unknown and drive is the affected
SMART drive.
CIM > System > System Enclosure:

The System Enclosure event occurs when the state of a system chassis (enclosure)
changes, such as when the cover is removed from the system.
Resolution
v If the severity is Critical: Make sure that the chassis cover is closed.
informative only.
Details
Additional extended
System System Enclosure Sensor reported Critical Alert None
Enclosure intrusion detection.
System System Enclosure Sensor reports Informational Resolution None
Enclosure normal.
CIM > System > System Event:
The System Event event occurs when a miscellaneous serviceable hardware error is
detected on a IBM Power managed object running AIX. Miscellaneous hardware
errors are those that are not generated by the following CIM > System events: Fan,
Memory, Network Adapter, Power Supply, Processor, Storage, Temperature, and
Voltage.
Resolution
Contact your service representative.
Note: The event generated by the resolution of this problem is CIM > System >
Service Event. The extended detail EventID for the Service Event event is set to the
same value as the extended detail EventID for the CIM > System > System Event
event.
Details
The CIM > System > System Event event type uses a standard set of extended
details.
Additional extended
System Event Note: This text varies depending on the error that Varies Alert None
has occurred on the AIX managed object. The depending
provided text is a description of that System Event on the error.
occurrence.
CIM > System > Temperature:
The Temperature event occurs when the state of a system temperature sensor
changes with respect to a manufacturer-defined or user-defined threshold.
Resolution
v If the severity is Critical or Warning: Identify the cause of the temperature
increase. If necessary, increase the cooling capacity.

informative only.
Details
Additional extended
Temperature Temperature Sensor number Critical Alert None
exceeded the manufacturer
defined threshold of threshold
Celsius. The current value is
current Celsius.
where:
v number is the affected
temperature sensor.
v threshold is the
manufacturer-defined threshold
value.
v current is the current
temperature reading.
Temperature Temperature Sensor number Critical Alert None
exceeded the user defined
threshold of threshold Celsius. The
current value is current Celsius.
where:
temperature sensor.
v threshold is the user-defined
threshold value.
Temperature Temperature Sensor number Warning Alert None
exceeded the manufacturer
defined threshold of threshold
Celsius. The current value is
current Celsius.
where:
temperature sensor.
v threshold is the
manufacturer-defined threshold
value.
Temperature Temperature Sensor number Warning Alert None
exceeded the user defined
threshold of threshold Celsius. The
current value is current Celsius.
where:
temperature sensor.
v threshold is the user-defined
threshold value.
Temperature Temperature Sensor number Informational Resolution None
reports normal.

temperature sensor.

CIM > System > Voltage:
The Voltage event occurs when the state of a system voltage sensor changes with
respect to a manufacturer-defined threshold.
Resolution
v If the severity is Critical: Identify the cause of the voltage problem. Make sure
that the power supply is working. If necessary, replace the power supply.
informative only.
Details
Additional extended
Voltage Voltage Sensor number fell below Critical Alert None
threshold of threshold Volts. The
current value is current Volts.
where:
v number is the affected voltage
sensor.
v threshold is the threshold value.
v current is the current voltage
reading.
Voltage Voltage Sensor number exceeded Critical Alert None
threshold of threshold Volts. The
current value is current Volts.
where:
v number is the affected voltage
sensor.
v current is the current voltage
reading.
Voltage Voltage Sensor number reports Informational Resolution None
normal.

voltage sensor.
CIM > System > Warranty Expiration:
The Warranty Expiration event occurs when the system warranty expiration date
has been reached with respect to the value configured for the date while using the
Asset ID task.
Resolution
v If the severity is Warning: The warranty has expired.
informative only.
Details
The date value in the event text is provided by the Asset ID task. The Warranty
page in the Asset ID task includes the End Date field where you can set the lease

expiration date. The date is stored in the IBMPSG_Warranty.EndDate CIM property
that is monitored at regular poll intervals. A CIM indication is generated when the
system CIMOM starts and when a state change is detected relative to the internal
poll interval.
Additional extended
Warranty The warranty on system has Warning Alert None
Expiration expired. It expired on date.

system and date is the warranty
expiration date.
Warranty The warranty on system is normal. Informational Resolution None
Expiration It will expire on date.

system and date is the warranty
expiration date.
MPA events
MPA event types occur when a service processor or management module detect a
change in the system state. The event types can indicate a change in the state of
the system components, the system environmental values, system configuration,
system startup, or the scalable platforms and nodes. For detailed event types,
expand the MPA node in the Event Filter Builder tree.
Details
If you select the MPA check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the MPA subtree.
MPA Not applicable Not Not None
MPA > Component

The Component event types occur when a service processor or management
module detects that the state of a system component has changed. For detailed
event types for system components, expand the Component node in the Event
Filter Builder tree.
Details
These MPA event types use the following set of extended details:
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
For detailed information about these event types, see “Extended details for MPA
events.” Some MPA event types have additional extended details. These event
types list the details in the Additional extended details column.

If you select the Component check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Component
subtree.
Component Not applicable Not Not None
MPA > Component > Alarm Panel:
The Alarm Panel events occur when a service processor or management module
detects that the alarm panel has been inserted or removed.
Resolution
Event type Resolution
Inserted No resolution. This event is informative only.
Power > Off No resolution. This event is informative only.
Power > On No resolution. This event is informative only.
Removed No resolution. This event is informative only.
Details
Note: These events are generated by BladeCenter management modules only.
v Firmware code
v Sender UUID
v Source UUID
events.” Some event types have additional extended details. These event types list
the details in the Additional extended details column.
If you select the Alarm Panel check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Alarm Panel
subtree.
Alarm Panel Not applicable Not Not None
You can choose to select specific event types that are displayed under the Alarm
Panel node in the Event Filter Builder tree. The event filter will process only the
Inserted An alarm panel module InformationalAlert None
was inserted.
Power Not applicable Not Not None
applicable applicable
Power > Off An alarm panel module Warning Alert None
was powered off.

Power > On An alarm panel module InformationalAlert None
was powered on.
Removed An alarm panel module Warning Alert None
was removed.
MPA > Component > Battery:
The Battery events occur when a service processor or management module detects
that the state of a RAID controller or SAS switch battery has changed.
Resolution
Failed v If the severity is Critical: Make sure the battery cable is connected correctly. If
necessary, replace the battery.
informative only.
Installed No resolution. This event is informative only.
Unreliable Replace the affected battery.
Details
Note: These events are generated by service processors and BladeCenter

management modules.
v Firmware code
v Sender UUID
v Source UUID
If you select the Battery check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the Battery subtree.
Battery Not applicable Not Not None
You can choose to select specific event types that are displayed under the Battery
node in the Event Filter Builder tree. The event filter will process only the event
types that you select.
Failed A RAID battery failure Critical Alert Component indicates the affected
was detected. BladeCenter Expansion Module.
Failed A RAID battery has InformationalResolution Component indicates the affected
recovered from a failure. BladeCenter Expansion Module.

Failed A SAS switch module Critical Alert Component indicates the affected
battery backup unit SAS switch module.
failure was detected.
Failed A SAS switch module InformationalResolution Component indicates the affected
battery backup unit has SAS switch module.
recovered from a failure
condition.
Installed A SAS switch module Warning Alert Component indicates the affected
battery backup unit has SAS switch module.
been installed.
Removed A SAS switch module Warning Alert Component indicates the affected
battery backup unit was SAS switch module.
removed or is not
present.
Unreliable The system clock battery Warning Alert Component indicates the affected
is unreliable. SAS switch module.
MPA > Component > BIOS:
The BIOS events occur when a service processor or management module detects
that the state of the system BIOS has changed.
Resolution
v If the severity is Critical: Reseat the blade server and reflash the baseboard
management controller (BMC) firmware.
v If the severity is Warning: Reflash the BIOS firmware.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
If you select the BIOS check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the BIOS subtree.
BIOS Not applicable Not Not None

You can choose to select specific event types that are displayed under the BIOS
Corrupted The primary BIOS is Warning Alert None
corrupted. The system
will attempt to start
using the backup BIOS.
Corrupted The BIOS is no longer InformationalResolution None
corrupted.
Failed The IPMI BIOS has Critical Alert None
failed due to unspecified
errors. You must
manually clear this
event.
MPA > Component > Blade Expansion Unit:
The Blade Expansion Unit events occur when a service processor or management
module detects that the state of a blade expansion unit has changed.
Resolution
v If the severity is Critical: Make sure the Blade Expansion Unit is installed
correctly. If necessary, replace the unit.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Source UUID
If you select the Blade Expansion Unit check box in the Event Filter Builder tree,
the event filter will process all of the event types that are specified in the Blade
Expansion Unit subtree.
Blade Not applicable Not Not None
Expansion applicableapplicable
Unit
You can choose to select specific event types that are displayed under the Blade
Expansion Unit node in the Event Filter Builder tree. The event filter will process
only the event types that you select.

Failed A blade expansion unit Critical Alert None
Failed A blade expansion unit InformationalResolution None
has recovered from a
failure.
MPA > Component > Blade Server:
The Blade Server events occur when a management module detects that the state
of a blade server has changed.
Resolution
Event type Severity
Capacity on Demand No resolution. This event is informative only.
> Enabled
Communication v If the severity is Critical: Contact the IBM Technical Support center.
informative only.
Incompatible v If the severity is Critical: Remove the blade server from the chassis and
install it in a chassis that supports it.
informative only.
Insufficient Power v If the severity is Critical: Increase the power capacity to the chassis by
inserting more power supplies or replacing existing power supplies with
units that supply more power.
informative only.
Over Power Budget v If the severity is Minor: Increase the power capacity to the chassis by
informative only.
Throttled No resolution. This event is informative only.
VPD v If the severity is Critical: Contact the IBM Technical Support center.
informative only.
Details
v Firmware code
v Sender UUID
v Source UUID

If you select the Blade Server check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Blade Server
subtree.
Blade Server Not applicable Not Not None
You can choose to select specific event types that are displayed under the Blade
Server node in the Event Filter Builder tree. The event filter will process only the
Capacity on Not applicable Not Not None
Demand applicable applicable
Capacity on A blade server with a InformationalAlert None
Demand > Standby Capacity on
Enabled Demand feature was
enabled.
CommunicationThe management Critical Alert Unit identifies the affected blade
module failed to server.
communicate with a
blade server.
CommunicationThe management InformationalResolution Unit identifies the affected blade
module successfully server.
communicated with a
blade server after a
previous failure.
Incompatible A blade server is Critical Alert Unit identifies the affected blade
incompatible with the server.
chassis.
Incompatible A blade server InformationalResolution None
compatibility issue has
been resolved.
Inserted A blade server was InformationalAlert Unit identifies the affected blade
inserted. server.
Insufficient A blade server cannot Critical Alert Unit identifies the affected blade
Power power on because there server.
is insufficient power.
Insufficient A blade server has InformationalResolution Unit identifies the affected blade
Power sufficient power to server.
power on.
Over Power The management Minor Alert Unit identifies the affected blade
Budget module instructed a server.
blade server to power
off because it exceeded
the power budget.
Over Power A blade server was InformationalResolution Unit identifies the affected blade
Budget allowed to power on server.
because it no longer
exceeds the power
budget.
Removed A blade server was Warning Alert Unit identifies the affected blade
removed. server.
Throttled A blade server is InformationalAlert Unit identifies the affected blade
throttled. server.
Throttled A blade server is no InformationalResolution Unit identifies the affected blade
longer throttled. server.

VPD The blade server vital Critical Alert Unit identifies the affected blade
product data (VPD) server.
could not be read. The
blade server will not be
allowed to power on.
VPD The blade server vital InformationalResolution Unit identifies the affected blade
product data (VPD) was server.
read successfully.
MPA > Component > Bus:
The Bus events occur when a service processor detects that the state of a bus has
changed.
Resolution
v If the severity is Critical: Contact the IBM Technical Support center.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Source UUID
If you select the Bus check box in the Event Filter Builder tree, the event filter will
process all of the event types that are specified in the Bus subtree.
Bus Not applicable Not Not Bus identifies the affected bus.
You can choose to select specific event types that are displayed under the Bus
Event type Event text Severity Category Additional extended attributes
CommunicationA failure occurred while Critical Alert Bus identifies the affected bus.
attempting to
communicate with a
device.
CommunicationSuccessfully InformationalResolution Bus identifies the affected bus.
communicated with a
device after a previous
failure.

CommunicationOne or more blades are Critical Alert Bus identifies the affected bus.
isolated from the
management bus.
CommunicationOne or more blades are InformationalResolution Bus identifies the affected bus.
no longer isolated from
the management bus.
MPA > Component > Chassis:
The Chassis events occur when a management module detects that the state of a
BladeCenter chassis has changed. For detailed event types and their resolutions,
expand the Chassis node in the Event Filter Builder tree.
Resolution
Configuration v If the severity is Minor:
– If the Issue extended detail is blade_power, insert a power supply into the
specified power domain of the chassis or move the blade server to another
power domain.
– If the Component extended detail is processor_blade, switch_module, or
switch_to_storage, remove the specified blade server or I/O module that
is causing the configuration mismatch.
informative only.
Cooling Capacity v If the severity is Critical or Warning: Replace the failed or missing chassis
cooling devices.
informative only.
Direct Serial Attach No resolution. This event is informative only.
Module > Inserted
Direct Serial Attach No resolution. This event is informative only.
Module > Removed
Failed v If the Issue extended detail is no_fans, replace all blowers in the chassis.
v If the Issue extended detail is all_ps_over_temp, replace any failed blowers
and fan packs. If necessary, add more cooling capacity.
Maximum Cooling v If the severity is Warning: Contact the IBM Technical Support center.
informative only.
Details
v Firmware code
v Sender UUID
v Source UUID
If you select the Chassis check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the Chassis subtree.

Chassis Not applicable Not Not v Issue is one of the following strings:
applicableapplicable – all_ps_over_temp indicates that all
of the power supplies have
exceeded their temperature
thresholds and the fans are
running at full speed.
– blade_power indicates that a blade
server was inserted into a bay that
is not receiving power.
– no_fans indicates that none of the
fans are functional.
v switch_module indicates that an I/O
module is not compatible with the
management module configuration.
v switch_to_storage indicates that an
I/O module is not compatible with
the storage module configuration.
You can choose to select specific event types that are displayed under the Chassis
Configuration A blade server was Minor Alert v Issue is set to blade_power.
inserted into a bay that
is not receiving power. v Power Domain identifies the
Note: The Configuration BladeCenter chassis power
events occur when a domain into which the blade
management module server was inserted. A
detects that the state of BladeCenter chassis is divided
a BladeCenter chassis into two power domains. Power
configuration has supplies 1 and 2 provide power
changed. to the first domain; Power
supplies 3 and 4 provide power
to the second domain.
Configuration A chassis configuration InformationalResolution v Issue is set to blade_power.
issue was resolved.
v Power Domain identifies the
BladeCenter chassis power
domain into which the blade
server was inserted. A
BladeCenter chassis is divided
into two power domains. Power
to the first domain; Power
to the second domain.
Configuration A blade server is not Minor Alert v Component is set to
compatible with the I/O processor_blade.
module configuration.
v Unit identifies the affected blade
server.
Configuration A chassis configuration InformationalResolution v Component is set to
issue was resolved. processor_blade.
v Unit identifies the affected blade
server.
Configuration An I/O module is not Minor Alert v Component is set to
compatible with the switch_module.
blade server
configuration. v Unit identifies the affected I/O
module.

compatible with the switch_module.
management module
module.
issue was resolved. switch_module.
v Unit identifies the affected I/O
module.
compatible with the switch_to_storage.
storage module
module.
issue was resolved. switch_to_storage.
module.
Cooling Chassis cooling capacity Critical Alert None
Capacity is reduced and
insufficient to support
blade operations. Blades
will be shutdown.
Cooling Chassis cooling capacity Warning Alert None
Capacity is reduced. Loss of an
additional chassis
cooling device will
cause blades to
shutdown.
Cooling Chassis cooling is now InformationalResolution None
Capacity sufficient to support
blade operations.
Direct Serial A Direct Serial Attach InformationalAlert
Attach Module has been
Module > inserted.
Inserted
Direct Serial A Direct Serial Attach Warning Alert
Attach Module has been
Module > removed.
Removed
Failed There are no working Critical Alert Issue is set to no_fans.
fans.
Failed All power supplies have Critical Alert Issue is set to all_ps_over_temp.
exceeded the
temperature thresholds
and the fans are running
at full speed.
Maximum The ambient Warning Alert None
Cooling temperature cannot be
read. Blowers will run at
full speed.
Maximum The ambient InformationalResolution None
Cooling temperature can now be
read. Blowers will run at
normal speed.
MPA > Component > Clock Module:

The Clock Module events occur when a service processor or management module
detects that the state of a Clock Module has changed.
Resolution
Details
v Firmware code
v Sender UUID
v Source UUID
If you select the Clock Module check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Clock Module
subtree.
Clock Module Not applicable Not Not None
You can choose to select specific event types that are displayed under the Clock
Module node in the Event Filter Builder tree. The event filter will process only the
Inserted A clock module was InformationalAlert Unit identifies the affected clock
inserted. module.
Power > Off A clock module was Warning Alert Unit identifies the affected clock
powered off. module.
Power > On A clock module was InformationalAlert Unit identifies the affected clock
powered on. module.
Removed A clock module was Warning Alert Unit identifies the affected clock
removed. module.
MPA > Component > Concurrent KVM:
The Concurrent KVM events occur when a service processor or management

module detects that a concurrent keyboard, video, mouse (KVM) card has failed or
recovered from a failure.

Resolution
v If the severity is Critical: Make sure the Concurrent KVM is seated correctly
within the blade server. If necessary, replace the card.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Source UUID
If you select the Concurrent KVM check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the Concurrent
KVM subtree.
Concurrent Not applicable Not Not None
KVM applicableapplicable
You can choose to select specific event types that are displayed under the
Concurrent KVM node in the Event Filter Builder tree. The event filter will
process only the event types that you select.
Failed A concurrent KVM card Critical Alert None
Failed A concurrent KVM card InformationalResolution None
has recovered from a
failure.
MPA > Component > CPU:
The CPU events occur when a service processor or management module detects
that the state of a microprocessor (CPU) has changed.
Resolution
Absent Replace the microprocessor.
Configuration v If the severity is Critical or Warning: Reconfigure the microprocessors. See
the system documentation for configuration information.
informative only.

Failed v If the severity is Critical: If the event text states that the microprocessor has
been disabled, replace the microprocessor.
informative only.
v Otherwise, monitor the microprocessor for further problems; if the problems
persist, replace the microprocessor.
Details

management modules.
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
If you select the CPU check box in the Event Filter Builder tree, the event filter will
process all of the event types that are specified in the CPU subtree.
CPU Not applicable Not Not Unit identifies the affected
applicableapplicablemicroprocessor.
You can choose to select specific event types that are displayed under the CPU
Absent No CPUs were detected Critical Alert Unit identifies the affected
in a system. microprocessor.
Configuration The CPU configuration Warning Alert Unit identifies the affected
prohibits CPU from microprocessor.
operating at maximum
speed.
Configuration The CPU configuration InformationalResolution Unit identifies the affected
no longer prohibits CPU microprocessor.
from operating at
maximum speed.
Configuration The CPU configuration Critical Alert Unit identifies the affected
is invalid. microprocessor.
Configuration The CPU configuration InformationalResolution Unit identifies the affected
is valid. microprocessor.
Configuration A CPU mismatch was Critical Alert Unit identifies the affected
detected. microprocessor.
Configuration No CPU mismatches InformationalResolution Unit identifies the affected
were detected. microprocessor.

Failed A CPU fault occurred. Critical Alert Unit identifies the affected
microprocessor.
Failed A CPU internal error Critical Alert Unit identifies the affected
was detected and the microprocessor.
CPU has been disabled.
The system has been
restarted.
Failed A CPU has been Critical Alert Unit identifies the affected
disabled due to microprocessor.
unspecified errors. You
must manually clear this
event.
was detected, probably microprocessor.
due to a bus timeout.
The system has been
restarted. You must
manually clear this
event.
was detected and the microprocessor.
CPU has been disabled.
The system has been
restarted. You must
manually clear this
event.
was detected. The microprocessor.
system has been
restarted. You must
manually clear this
event.
Failed A CPU is now operating InformationalResolution Unit identifies the affected
normally. microprocessor.
MPA > Component > DASD:
The hard disk drive (DASD) events occur when a service processor or management
module detects that the state of a hard disk drive has changed.
Resolution
Configuration v If the severity is Critical: Reconfigure the hard disk drives into a valid
configuration. See the system documentation for configuration information.
informative only.
Failed v If the severity is Critical or Minor: Replace the specified hard disk drive that
is failing or has failed.
informative only.
PFA v If the severity is Critical: Replace the affected hard disk drive before it fails.
informative only.

Details

management modules.
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
If you select the DASD check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the DASD subtree.
DASD Not applicable Not Not None
You can choose to select specific event types that are displayed under the DASD
Configuration The hard disk drive Critical Alert None
configuration is invalid.
Configuration The hard disk drive InformationalResolution None
configuration is valid.
Failed A hard disk drive has Minor Alert v SCSI ID identifies the target hard
failed. disk drive by SCSI ID.
v Storage Module indicates the
storage module index where the
drive is located.
v Unit identifies the target hard
disk drive by physical location.
Failed A hard disk drive has Critical Alert v SCSI ID identifies the target hard
failed. You must disk drive by SCSI ID.
manually clear this
event. v Storage Module indicates the
drive is located.
Failed A hard disk drive is InformationalResolution v SCSI ID identifies the target hard
now operating normally. disk drive by SCSI ID.
drive is located.

Inserted A hard disk drive was InformationalResolution v SCSI ID identifies the target hard
inserted. disk drive by SCSI ID.
drive is located.
PFA A hard disk drive PFA Critical Alert v SCSI ID identifies the target hard
condition was detected. disk drive by SCSI ID.
drive is located.
PFA A hard disk drive has InformationalResolution v SCSI ID identifies the target hard
recovered from a PFA disk drive by SCSI ID.
condition.
drive is located.
Removed No Hot Spare Drive is Warning Alert v SCSI ID identifies the target hard
detected on a blade disk drive by SCSI ID.
server.
drive is located.
Removed A hard disk drive was Warning Alert v SCSI ID identifies the target hard
removed. disk drive by SCSI ID.
drive is located.
MPA > Component > DIMM:
The DIMM events occur when a service processor or management module detects
that the state of a dual inline memory module (DIMM) has changed.
Resolution
Absent Install the missing memory modules.
Disabled Determine which DIMM has failed and replace it.
Failed v If the severity is Critical or Minor: Determine which DIMM has failed and
replace it.
informative only.

Details

management modules.
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
If you select the DIMM check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the DIMM subtree.
DIMM Not applicable Not Not None
You can choose to select specific event types that are displayed under the DIMM
Absent No memory modules Critical Alert None.
were detected in a blade
server.
Disabled A memory device has Warning Alert Unit identifies the affected DIMM.
been disabled.
Failed A DIMM has failed. Minor Alert Unit identifies the affected DIMM.
Failed A DIMM has failed. Critical Alert Unit identifies the affected DIMM.
Failed A DIMM has reported a Minor Alert Unit identifies the affected DIMM.
correctable ECC error.
Failed A DIMM has generated Minor Alert Unit identifies the affected DIMM.
a PFA alert.
Failed An error has occurred Critical Alert Unit identifies the affected DIMM.
due to an invalid DIMM
configuration.
Failed A DIMM has exceeded a Critical Alert Unit identifies the affected DIMM.
critical temperature
threshold.
Failed A DIMM has recovered InformationalResolution Unit identifies the affected DIMM.
from a previous error.
MPA > Component > Expansion Card:
The Expansion Card events occur when a service processor or management

module detects that the state of a high-speed expansion card has changed.

Resolution
v If the severity is Critical: Make sure the Blade Expansion Unit is installed
correctly. If necessary, replace the unit.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Source UUID
If you select the Expansion Card check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the Expansion
Card subtree.
Expansion Not applicable Not Not None
Card applicableapplicable
Expansion Card node in the Event Filter Builder tree. The event filter will process
Failed A high-speed expansion Critical Alert None
card failure was
detected.
Failed A high-speed expansion InformationalResolution None
card has recovered from
a failure.
MPA > Component > Fan:
The Fan events occur when a service processor or management module detects
that the state of a fan has changed.
Resolution
Configuration v If the severity is Critical: Reconfigure the fans into a valid configuration. See
the system documentation for configuration information.
informative only.
Failed v If the severity is Critical: Replace the specified fan that has failed.
informative only.

PFA v If the severity is Warning: Replace the specified fan that has failed.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
If you select the Fan check box in the Event Filter Builder tree, the event filter will
process all of the event types that are specified in the Fan subtree.
Fan Not applicable Not Not None
You can choose to select specific event types that are displayed under the Fan node
in the Event Filter Builder tree. The event filter will process only the event types
that you select.
Configuration The fan configuration is Critical Alert None
not valid.
Configuration The fan configuration is InformationalResolution None
valid.
Failed A fan failed. Critical Alert v Component identifies the affected
component, such as a power
supply, with which the affected
fan is associated. This attribute
provides information only if the
fan is associated with a
component.
v Unit identifies the affected fan.
Failed A fan failed. You must Critical Alert None
manually clear this
event.

Failed A fan is now InformationalResolution v Component identifies the affected
functioning correctly. component, such as a power
supply, with which the affected
fan is associated. This attribute
provides information only if the
fan is associated with a
component.
v Unit identifies the affected fan.
Inserted A fan was inserted. InformationalResolution Unit identifies the affected fan.
PFA A PFA alert associated Warning Alert Unit identifies the affected fan.
with a fan occurred.
PFA A fan is now InformationalResolution Unit identifies the affected fan.
functioning correctly.
Removed A fan was removed. Warning Alert Unit identifies the affected fan.
MPA > Component > Fan Pack:
The Fan Pack events occur when a management module detects that the state of a
fan pack has changed.
Resolution
Failed v If the severity is Critical: Replace the specified fan pack.
informative only.
PFA v If the severity is Warning: Replace the specified fan pack.
informative only.
Details
v Firmware code
v Sender UUID
v Source UUID
If you select the Fan Pack check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the Fan Pack subtree.
Fan Pack Not applicable Not Not None

You can choose to select specific event types that are displayed under the Fan Pack
Failed A fan pack has failed. Critical Alert Unit indicates the affected fan pack.
Failed A fan pack is now InformationalResolution Unit indicates the affected fan pack.
Inserted A fan pack was inserted. InformationalAlert Unit indicates the affected fan pack.
PFA A fan pack has Warning Alert Unit indicates the affected fan pack.
generated a Predictive
alert.
PFA A fan pack is now InformationalResolution Unit indicates the affected fan pack.
Removed A fan pack was Warning Alert Unit indicates the affected fan pack.
removed.
MPA > Component > Front Panel:
The Front Panel events occur when a service processor or management module
detects that the state of a system front panel cable connection has changed.
Resolution
v If the severity is Critical: Make sure the front panel cable for the server is
connected correctly.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Source UUID
If you select the Front Panel check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Front Panel
subtree.
Front Panel Not applicable Not Not None
You can choose to select specific event types that are displayed under the Front
Panel node in the Event Filter Builder tree. The event filter will process only the

Failed The front panel cable is Critical Alert None
not connected to the
system board.
Failed The front panel cable is InformationalResolution None
connected to the system
board.
MPA > Component > I/O Board:
The I/O Board events occur when a service processor or management module
detects that the state of a blade-server I/O board has changed.
Resolution
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Source UUID
If you select the I/O Board check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the I/O Board subtree.
I/O Board Not applicable Not Not None
You can choose to select specific event types that are displayed under the I/O
Board node in the Event Filter Builder tree. The event filter will process only the
Failed A blade-server I/O Critical Alert None
board failure was
detected.
Failed A blade-server I/O InformationalResolution None
board has recovered
from a failure.
MPA > Component > I/O Interposer:
The I/O Interposer events occur when a service processor or management module
detects that the state of an I/O Interposer has changed.
Resolution
Details
v Firmware code
v Sender UUID
v Source UUID
If you select the I/O Interposer check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the I/O Interposer
subtree.
I/O Not applicable Not Not None
Interposer applicableapplicable
Interposer node in the Event Filter Builder tree. The event filter will process only
the event types that you select.
Inserted An I/O interposer InformationalAlert Unit identifies the affected I/O
module was inserted. interposer.
Removed An I/O interposer Warning Alert Unit identifies the affected I/O
module was removed. interposer.
MPA > Component > I/O Module:
The I/O Module events occur when a management module detects that the state of
an I/O module (such as a switch) has changed.
Resolution
Communication v If the severity is Critical: Contact the IBM Technical Support center.
informative only.
Configuration No resolution. This event is informative only.
Failed v If the severity is Critical: Replace the specified I/O module.
informative only.

Fuse v If the severity is Warning: Replace the I/O module fuse.
informative only.
informative only.
Mismatch The switches in an I/O bay pair (bays 1 and 2 or bays 3 and 4) are not the
same, for example, one bay contains a SAS switch and the other bay contains
an Ethernet switch. Replace the incompatible switch with a compatible switch
or move the incompatible switch to another I/O bay pair.
Over Current The switch is exceeding the power requirement of the slot. Either the switch or
the power supply is faulty. Replace the faulty component.
POST v If the severity is Critical or Warning: See the I/O module documentation.
informative only.
Power > Disabled The switch power is disabled because it is not recognized by the management
module. Replace the affected switch with a supported switch model.
Power > Timeout To resolve this problem, complete the following steps:
1. Attempt to power down the SAS RAID controller module again.
2. Check the Activity LED on the battery backup unit.
v If the LED is on, reseat the SAS RAID controller module.
v If the LED is off, wait a few minutes to see of the light will turn off.
Attention: Removing the SAS RAID controller module while the LED is
on can result in data loss.
Redundancy v If the severity is Minor: If a position has been vacated, insert an I/O module
of the same type into that position. Otherwise, replace the failed I/O module.
informative only.
Stacking > Activated No resolution. This event is informative only.
Stacking > No resolution. This event is informative only.
Deactivated
Zoning No resolution. This event is informative only.
Details
v Firmware code
v Sender UUID
v Source UUID

If you select the I/O Module check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the I/O Module
subtree.
I/O Module Not applicable Not Not Unit identifies the affected I/O module.
CommunicationThe SAS I/O module Critical Alert Unit identifies the affected I/O
TCP connection to the module.
AMM has been lost.
CommunicationThe SAS I/O module InformationalResolution Unit identifies the affected I/O
TCP connection to the module.
AMM has been restored.
Configuration The I/O module IP InformationalAlert v IP Address 1 is the IP address
configuration changed. being used by the BladeCenter
I/O module.
module.
Configuration The I/O module NAT InformationalAlert v IP Address 1 is the IP address
configuration was being used by the BladeCenter
activated. I/O module.
module.
Configuration The I/O module NAT InformationalAlert v IP Address 1 is the IP address
configuration was being used by the BladeCenter
activated with IP filter I/O module.
rules.
module.
Configuration An I/O module has InformationalAlert Unit identifies the affected I/O
enabled Protected Mode module.
control of IP
configuration.
control of external ports.
control of external
management.
control of reset
configuration to
defaults.
Configuration An I/O module has Warning Alert Unit identifies the affected I/O
control without the
Management Module's
permission.

Configuration An I/O module's Warning Alert Unit identifies the affected I/O
Protected Mode module.
permission and MM
configured permission
are mismatched.
Failed An I/O module has Critical Alert Unit identifies the affected I/O
failed. module.
Failed An I/O module InformationalResolution Unit identifies the affected I/O
recovered from a failure. module.
Fuse An I/O module fuse is Warning Alert Unit identifies the affected I/O
open. Power module.
redundancy has been
lost for this module.
Fuse An I/O module fuse is InformationalResolution Unit identifies the affected I/O
no longer open. module.
Inserted An I/O module was InformationalAlert Unit identifies the affected I/O
inserted. module.
Insufficient An I/O module cannot Critical Alert Unit identifies the affected I/O
Power power on because there module.
is insufficient power.
Insufficient An I/O module has InformationalResolution Unit identifies the affected I/O
Power sufficient power to module.
power on.
Mismatch An I/O module Minor Alert Unit identifies the affected I/O
mismatch was detected. module.
Mismatch An I/O module InformationalResolution Unit identifies the affected I/O
mismatch has been module.
resolved.
Over Current A monitored current has Critical Alert Unit identifies the affected I/O
exceeded the rating of module.
the I/O module.
Over Current A monitored current is InformationalResolution Unit identifies the affected I/O
now below the rating of module.
the I/O module.
POST I/O module POST Warning Alert Unit identifies the affected I/O
completed with errors. module.
POST I/O module POST InformationalResolution Unit identifies the affected I/O
completed without module.
errors after a previous
failure.
POST I/O module POST timed Critical Alert Unit identifies the affected I/O
out. module.
POST I/O module POST InformationalResolution Unit identifies the affected I/O
completed after a module.
previous timeout.
Power Not applicable Not Not Unit identifies the affected I/O
applicable applicable module.
Power > Power has been denied Critical Alert Unit identifies the affected I/O
Disabled to an I/O module module.
because it cannot be
identified.
Power > Off An I/O module was Warning Alert Unit identifies the affected I/O
powered off. module.
Power > On An I/O module was InformationalAlert Unit identifies the affected I/O
powered on. module.

Power > An I/O module Warning Alert Unit identifies the affected I/O
Timeout powerdown request module.
timed out.
Redundancy I/O module redundancy Minor Alert Unit identifies the affected I/O
was lost. module.
Redundancy I/O module redundancy InformationalResolution Unit identifies the affected I/O
was restored. module.
Removed An I/O module was Warning Alert Unit identifies the affected I/O
removed. module.
Stacking > Switch stacking has InformationalAlert Unit identifies the affected I/O
Activated been activated on an module.
I/O module.
Stacking > Switch stacking has InformationalAlert Unit identifies the affected I/O
Deactivated been deactivated on an module.
I/O module.
Zoning The SAS I/O module InformationalAlert Unit identifies the affected I/O
zone configuration has module.
been changed. You must
manually clear this
event.
Zoning All zoning has been Warning Alert Unit identifies the affected I/O
disabled for a SAS I/O module.
module. You must
manually clear this
event.
Zoning No active zone Warning Alert Unit identifies the affected I/O
configuration found for module.
a SAS I/O module. You
event.
Zoning An attempt to change Warning Alert Unit identifies the affected I/O
the SAS I/O module module.
zone configuration has
failed. You must
manually clear this
event.
MPA > Component > Management Module Interposer:
The Management Module Interposer events occur when a service processor or

management module detects that the state of a management module interposer has
changed.
Resolution
Details
v Firmware code
v Sender UUID

v Source UUID
If you select the Management Module Interposer check box in the Event Filter
Builder tree, the event filter will process all of the event types that are specified in
the Management Module Interposer subtree.
Management Not applicable Not Not None
Module applicableapplicable
Interposer
Management Module Interposer node in the Event Filter Builder tree. The event
filter will process only the event types that you select.
Inserted A management module InformationalAlert Unit identifies the affected
interposer was inserted. management module interposer.
Removed A management module Warning Alert Unit identifies the affected
interposer module was management module interposer.
removed.
MPA > Component > Media Tray:
The Media Tray events occur when a service processor or management module
detects that the state of a media tray has changed.
Resolution
Failed Replace the specified media tray.
Temperature v If the severity is Critical: Replace the specified media tray.
Unavailable v If the category is Resolution: The error has been resolved. This event is
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Source UUID

If you select the Media Tray check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Media Tray
subtree.
Media Tray Not applicable Not Not None
You can choose to select specific event types that are displayed under the Media
Tray node in the Event Filter Builder tree. The event filter will process only the
Failed A media tray failure was Critical Alert Unit identifies the affected media
detected. tray.
Temperature The media tray Warning Alert Unit identifies the affected media
Unavailable temperature cannot be tray.
read.
Temperature The media tray InformationalResolution Unit identifies the affected media
Unavailable temperature can now be tray.
read.
MPA > Component > Multiplexer Expansion Module:
The Multiplexer Expansion Module events occur when a service processor or

management module detects that the state of a multiplexer expansion module has
changed.
Resolution
Failed Replace the specified multiplexer expansion module.
Details
v Firmware code
v Sender UUID
v Source UUID
If you select the Multiplexer Expansion Module check box in the Event Filter
Builder tree, the event filter will process all of the event types that are specified in
the Multiplexer Expansion Module subtree.

Multiplexer Not applicable Not Not None
Expansion applicableapplicable
Module
Multiplexer Expansion Module node in the Event Filter Builder tree. The event
Failed A multiplexer expansion Critical Alert Unit identifies the affected
module failure was multiplexer expansion module.
detected.
Inserted A multiplexer expansion InformationalAlert Unit identifies the affected
module has been multiplexer expansion module.
inserted.
Removed A multiplexer expansion Warning Alert Unit identifies the affected
module has been multiplexer expansion module.
removed.
MPA > Component > PFA:
The PFA events occur when a service processor or management module detects a
Predictive Failure Analysis (PFA) alert. The service processor event log provides
more information about the PFA alert.
Resolution
v If the severity is Warning: Identify and replace the component that is generating
the Predictive Failure Analysis event.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
PFA A PFA alert occurred. Warning Alert None
Check the service
processor event log for
more information.

PFA A PFA alert occurred. Warning Alert None
Check the service
more information. You
event.
PFA The problem that InformationalResolution None
generated a PFA alert
was resolved. Check the
service processor event
log for more
information.
MPA > Component > Power Subsystem:
The Power Subsystem events occur when a service processor or management

module detects that the state of a power subsystem has changed.
Resolution
Low Fuel v If the severity is Minor: Increase the power capacity by inserting more power
supplies or replacing existing power supplies with units that supply more
power.
informative only.
Mismatched Power v If the severity is Minor: Replace one of the power supplies in the specified
Supplies power domain so that both power supplies are of the same type.
informative only.
Over Current Identify the cause of the over power problem. Make sure that the power supply
is working properly. If necessary, replace the power supply.
Over Power Identify the cause of the over power problem. Make sure that the power supply
is working properly. If necessary, replace the power supply.
Over Subscription v If the severity is Minor or Warning: Increase the power capacity by inserting
more power supplies or replacing existing power supplies with units that
supply more power.
informative only.
Redundancy v If the severity is Minor: Increase the power capacity by inserting more power
supplies or replacing existing power supplies with units that supply more
power.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number

v Source UUID
If you select the Power Subsystem check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the Power
Subsystem subtree.
Subsystem applicableapplicable
You can choose to select specific event types that are displayed under the Power
Subsystem node in the Event Filter Builder tree. The event filter will process only
Low Fuel The server is in a Minor Alert None
low-fuel state.
Low Fuel The server recovered InformationalResolution None
from a low-fuel state.
Mismatched Mismatched power Minor Alert Power Domain identifies the affected
Power supplies were detected. BladeCenter chassis power domain.
Supplies A BladeCenter chassis is divided
supplies 1 and 2 provide power to
the first domain; Power supplies 3
and 4 provide power to the second
domain.
Mismatched No mismatched power InformationalResolution Power Domain identifies the affected
Power supplies were detected. BladeCenter chassis power domain.
Supplies A BladeCenter chassis is divided
domain.
Over Current The server load Minor Alert None
exceeded the capacity of
the power subsystem.
You must manually
clear this event.
Over Power A power bus has Critical Alert v Bus identifies the affected bus.
exceeded 240 voltage
amps. You must v Voltage Sensor identifies the
manually clear this affected voltage sensor.
event.
Over One power supply is Warning Alert Power Domain identifies the affected
Subscription not sufficient to power BladeCenter chassis power domain.
all blade servers at peak A BladeCenter chassis is divided
performance. Throttling into two power domains. Power
might occur. supplies 1 and 2 provide power to
domain.

Over One power supply is InformationalResolution Power Domain identifies the affected
Subscription sufficient to power all BladeCenter chassis power domain.
blade servers at peak A BladeCenter chassis is divided
performance. into two power domains. Power
domain.
Over One power supply is Minor Alert Power Domain identifies the affected
Subscription not sufficient to power BladeCenter chassis power domain.
all blade servers. A A BladeCenter chassis is divided
power failure might into two power domains. Power
result in an immediate supplies 1 and 2 provide power to
shutdown. the first domain; Power supplies 3
domain.
Over One power supply is InformationalResolution Power Domain identifies the affected
Subscription sufficient to power all BladeCenter chassis power domain.
blade servers. A BladeCenter chassis is divided
domain.
Redundancy Power redundancy was Minor Alert Power Domain identifies the affected
lost. BladeCenter chassis power domain.
A BladeCenter chassis is divided
domain.
Redundancy Power redundancy was Minor Alert There are no extended details for
lost. You must manually this event type.
clear this event.
Redundancy Power redundancy was InformationalResolution Power Domain identifies the affected
restored. BladeCenter chassis power domain.
A BladeCenter chassis is divided
domain.
MPA > Component > Power Supply:
The Power Supply events occur when a service processor or management module
detects that the state of a power supply has changed.
Resolution
Absent The power supply is faulty. Replace the power supply.
Configuration v If the severity is Critical: Reconfigure the power supplies into a valid
configuration. See the system documentation for configuration information.
informative only.
Failed v If the severity is Critical: Replace the specified power supply that has failed.
informative only.

PFA Replace the affected power supply before it fails.
Details

management modules.
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
If you select the Power Supply check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Power Supply
subtree.
Power Supply Not applicable Not Not Unit identifies the affected power
applicableapplicablesupply.
You can choose to select specific event types that are displayed under the Power
Supply node in the Event Filter Builder tree. The event filter will process only the
Absent No power supplies were Critical Alert None
detected in a system.
Configuration The power supply Critical Alert None
Configuration The power supply InformationalResolution None
configuration is valid.
Configuration A monitored power Minor Alert None
capping level has
changed.
Configuration A monitored power Minor Alert None
control cap has changed.

Failed A power supply has Critical Alert v Reason is one of the following
failed. strings:
– current
– dc
– epow
– voltage
– voltage_over
– voltage_under
v Unit identifies the affected power
supply.
v Voltage Sensor identifies the faulty
voltage sensor by voltage.
Failed A power supply has Critical Alert v Unit identifies the affected power
failed. You must supply.
manually clear this
event.
Failed A power supply has lost Critical Alert Unit identifies the affected power
its AC/DC input or is supply.
out of range.
Failed A power supply is now InformationalResolution v Reason is one of the following
functioning properly. strings:
– current
– dc
– epow
– voltage
– voltage_over
– voltage_under
v Unit identifies the affected power
supply.
v Voltage Sensor identifies the faulty
voltage sensor by voltage.
Failed A power supply fan has Critical Alert Unit identifies the affected power
failed. supply.
Failed A power supply fan is InformationalResolution Unit identifies the affected power
now functioning supply.
correctly.
Inserted A power supply was InformationalResolution Unit identifies the affected power
inserted. supply.
PFA A PFA alert occurred. Critical Alert Unit identifies the affected power
Check the service supply.
more information.
Removed A power supply was Warning Alert Unit identifies the affected power
removed. supply.
MPA > Component > Processor Board:
The Processor Board events occur when a service processor or management

module detects that the state of a blade server processor board has changed.
Resolution
v If the severity is Critical: Make sure the Processor Board is connected correctly. If
necessary, replace the Processor Board.
informative only.

Details
v Firmware code
v Sender UUID
v Source UUID
If you select the Processor Board check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the Processor
Board subtree.
Processor Not applicable Not Not None
Board applicableapplicable
Processor Board node in the Event Filter Builder tree. The event filter will process
Failed A blade server processor Critical Alert None
board failure was
detected.
Failed A blade server processor InformationalResolution None
board has recovered
from a failure.
MPA > Component > RAID:
The RAID events occur when a service processor or management module detects
that the state of a RAID controller or hard disk drive has changed.
Resolution
v If the severity is Critical: Verify that the RAID controller, cables, and physical
drives are installed correctly. If the problem persists, replace the RAID controller
or the Blade Expansion Unit.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Source UUID

If you select the RAID check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the RAID subtree.
RAID Not applicable Not Not None
You can choose to select specific event types that are displayed under the RAID
Failed A RAID failure was Critical Alert Component indicates the Blade
detected. Expansion Module with the
affected RAID configuration.
Failed RAID has recovered InformationalResolution Component indicates the Blade
from a failure. Expansion Module with the
affected RAID configuration.
Failed A ZSS/Drive-Array Critical Alert Component indicates the Blade
configuration error was Expansion Module with the
detected. affected RAID configuration.
Failed A ZSS/Drive-Array has InformationalResolution Component indicates the Blade
recovered from a Expansion Module with the
configuration error. affected RAID configuration.
MPA > Component > Server:
The Server events occur when a service processor or management module detects
that the state of a server has changed.
Resolution
Configuration v If the severity is Minor: Make sure that the PCI planar and ASM interconnect
configurations are valid. See the system documentation for configuration
information.
informative only.
Power > Disabled v If the severity is Critical: Make sure that the power jumper is present and
that the latest firmware for the power controller is installed.
informative only.
Power > Hibernate No resolution. This event is informative only.
Power > Restart No resolution. This event is informative only.
Power > Stand By No resolution. This event is informative only.
State No resolution. This event is informative only.

Details
Note: Unless stated otherwise, the following events are generated by service
processors and BladeCenter management modules.
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
If you select the Server check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the Server subtree.
Server Not applicable Not Not None
You can choose to select specific event types that are displayed under the Server
Configuration The ASM interconnect Minor Alert Issue is set to rs485.
Note: This event is
generated by service
processors only.
Configuration The PCI Planar/ASM Minor Alert Issue is set to pci/rs485.
interconnect
Note: This event is
processors only.
Configuration A server configuration InformationalResolution v Issue is one of the following
issue was resolved. strings:
Note: This event is – rs485
generated by service – pci/rs485
processors only.
Power > A server cannot be Critical Alert None
Disabled powered on because the
power jumper is not
present.
Disabled powered on because it is
incompatible with the
power controller
firmware.

Disabled powered on because it
cannot communicate
with the power
controller.
Power > A server now can be InformationalResolution None
Disabled powered on.
Power > Power has been denied Critical Alert None
Disabled to a blade because it
cannot be identified.
Power > A blade server is InformationalAlert None
Hibernate entering power
hibernate mode.
Power > Off The server is powering Warning Alert None
off.
Power > Off The server is powering Warning Alert
off.
Power > On The server is powering InformationalAlert None
on.
Power > The server is restarting. Minor Alert
Restart You must manually
clear this event.
Power > The server is restarting. Warning Alert None
Restart You must manually
clear this event.
Power > A blade server is InformationalAlert None
Standby entering power standby
mode.
State A server changed state. InformationalAlert New State is one of the following
Note: This event is strings:
generated by service v off
processors only. v in_post
v post_error
v flash
v booting_os
v in_os
v reset
v on
State Local power control for Minor Alert
a blade server has been
enabled.
State Local power control for InformationalAlert
a blade server has been
disabled.
State Local power control for Minor Alert
all blade servers has
been enabled.
State Local power control for InformationalAlert
all blade servers has
been disabled.
MPA > Component > Service Processor:
The Service Processor events occur when a service processor detects that its state
has changed or a management module detects that its state, or the state of another
management module in the same chassis, has changed.

Resolution
Active No resolution. This event is informative only.
Communication v If the severity is Critical or Warning: Contact the IBM Technical Support
center.
informative only.
Configuration Configure the service processor to send events to IBM Systems Director Server.
Duplicate IP Address v If the severity is Warning: Update the configuration with an IP address that
is not already in use.
informative only.
Failover v If the severity is Minor: If the event text refers to a network loss, check and
fix the network connection to the redundant management module. If the
event text refers to an I2C bus error, contact IBM Technical support.
informative only.
Inactive No resolution. This event is informative only.
Log v If the severity is Minor or Warning: Clear the service processor event log.
informative only.
Mismatch v If the severity is Warning: Both management module slots in a BladeCenter
chassis are filled, but the management modules are incompatible models.
Both management modules must be the same model in a BladeCenter
chassis. Remove one management module and replace it with a management
module that matches the remaining management module.
informative only.
Network Stack No resolution. This event is informative only.
Out-of-band > No resolution. This event is informative only.
Disabled
Out-of-band > No resolution. This event is informative only.
Enabled
Out-of-band > Port No resolution. This event is informative only.
Password > Change v If the severity is Warning: Change the service processor login password.
Required v If the category is Resolution: The error has been resolved. This event is
informative only.
Redundancy v If the severity is Minor: If a position has been vacated, insert a service
processor into that position. Otherwise, replace the failed service processor.
informative only.
Restart No resolution. This event is informative only.
Secure Out-of-band No resolution. This event is informative only.
> Disabled
> Enabled
> Port
Test No resolution. This event is informative only.
User Account > No resolution. This event is informative only.
Active
Disabled

Inactive
Details
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
If you select the Service Processor check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the Service
Processor subtree.
Service Not applicable Not Not None
Processor applicableapplicable
You can choose to select specific event types that are displayed under the Service
Processor node in the Event Filter Builder tree. The event filter will process only
Active A management module Warning Alert Unit identifies the affected
assumed control of the management module.
chassis.
Note: These events are
generated by
BladeCenter
management modules
only.
CommunicationThe management Critical Alert None
module cannot
communicate with a
blade server baseboard
management controller
(BMC).
generated by
BladeCenter
management modules
only.

CommunicationThe management Critical Alert None
module failed to
communicate with a
blade server.
generated by
BladeCenter
management modules
only.
CommunicationThe management InformationalResolution None
module successfully
communicated with a
blade server after a
previous failure.
generated by
BladeCenter
management modules
only.
Configuration IBM Systems Director Warning Alert None
Server failed to assign a
default alert
configuration to the
service processor.
Duplicate IP A duplicate IP address Warning Alert None
Address has been detected on a
service processor.
Duplicate IP No duplicate IP InformationalResolution None
Address addresses have been
detected.
Failover A network loss caused a Minor Alert None
failover to the
redundant management
module. You must
manually clear this
event.
Note: This event is
generated by
BladeCenter
management modules
only.
Failover The loss of a logical Minor Alert None
network link has
occurred. You must
manually clear this
event.
Note: This event is
generated by
BladeCenter
management modules
only.
Failover An I2C bus failure Minor Alert None
caused a failover to the
redundant management
module.
Note: This event is
generated by
BladeCenter
management modules
only.

Failover A management module InformationalResolution None
failover event was reset
by a management
module reset or by
removal of the failed
management module.
Note: This event is
generated by
BladeCenter
management modules
only.
Inactive A management module InformationalResolution Unit identifies the affected
has relinquished control management module.
of the chassis.
Inserted A service processor was InformationalAlert Unit identifies the affected service
inserted. processor.
Log The service processor Minor Alert None
event log is full.
Log The service processor Minor Alert None
event log is full. You
event.
Log The service processor Warning Alert None
event log is 75% full.
Log The service processor Warning Alert None
event log is 75% full.
You must manually
clear this event.
Log The service processor InformationalResolution None
event log was cleared.
Mismatch A management module Warning Alert None
mismatch was detected.
Mismatch No management module InformationalResolution None
mismatches were
detected.
Network The service processor InformationalAlert v IP Address 1 is the IP address
Stack network stack started. used by network interface 1
(external interface on the
BladeCenter management
module).
v IP Address 2 is the IP address
used by network interface 2
(external interface on the
BladeCenter management
module).
Out-of-band Not applicable Not Not None
Out-of-band The service processor InformationalAlert None
> Disabled out-of-band connection
was disabled.
Out-of-band The service processor InformationalAlert None
> Enabled out-of-band connection
was enabled.

Out-of-band The port number InformationalAlert Port identifies the new port
> Port changed for the service number.
processor out-of-band
connection.
Note: This event is
processors only.
Password Not applicable Not Not None
Password > A service processor user Warning Alert Unit identifies the affected service
Change password is about to processor.
Required expire.
Password > A service processor Warning Alert Unit identifies the affected service
Change login password has processor.
Required expired.
Change login password is processor.
Required required.
Change login password does not processor.
Required meet complexity
requirements.
Password > A service processor InformationalResolution Unit identifies the affected service
Change login password change processor.
Required is no longer required.
Redundancy Service processor Minor Alert None
redundancy was lost.
Redundancy Service processor InformationalResolution None
redundancy was
restored.
Removed A service processor was Warning Alert Unit identifies the affected service
removed. processor.
Restart The service processor InformationalAlert None
restarted.
Note: This event is
processors only.
Secure Not applicable Not Not None
Out-of-band applicable applicable
Secure The service processor InformationalAlert None
Out-of-band secure out-of-band
> Disabled connection was disabled.
Secure The service processor InformationalAlert None
Out-of-band secure out-of-band
> Enabled connection was enabled.
Secure The port number InformationalAlert Port identifies the new port
Out-of-band changed for the service number.
> Port processor secure
out-of-band connection.
Note: This event is
processors only.
Test The service processor InformationalAlert None
sent a test event.
User Account Not applicable Not Not None
User Account A service processor user InformationalAlert None
> Active account has been
activated.

User Account A service processor user Warning Alert None
> Disabled account has been
disabled.
User Account A service processor user Warning Alert None
> Inactive account has been
deactivated.
MPA > Component > SMP Expansion Module:
The SMP Expansion Module events occur when a service processor detects that the
state of an SMP Expansion Module has changed.
Resolution
Details
Note: This event is generated by service processors only.
v Firmware code
v Sender UUID
v Source UUID
If you select the SMP Expansion Module check box in the Event Filter Builder
tree, the event filter will process all of the event types that are specified in the SMP
Expansion Module subtree.
SMP Not applicable Not Not Unit identifies the affected SMP
Expansion applicableapplicableexpansion module.
Module
You can choose to select specific event types that are displayed under the SMP
Expansion Module node in the Event Filter Builder tree. The event filter will
Disabled An SMP Expansion Critical Alert Unit identifies the affected SMP
Module was disabled. expansion module.
Disabled An SMP Expansion InformationalResolution Unit identifies the affected SMP
Module recovered after expansion module.
being disabled.
MPA > Component > Storage Module:
The Storage Module events occur when a service processor or management

module detects that the state of a Storage Module has changed.

Resolution
Failed v If the severity is Critical: Replace the specified storage module.
informative only.
Insufficient Cooling v If the severity is Critical: Identify the cause of the temperature increase. If
necessary, increase the cooling capacity. Increase the power capacity to the
chassis by inserting more power supplies or replacing existing power
supplies with units that supply more power.
informative only.
informative only.
Details

management modules.
v Firmware code
v Sender UUID
v Source UUID
If you select the Storage Module check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the Storage
Module subtree.
Storage Not applicable Not Not None
Module applicableapplicable
You can choose to select specific event types that are displayed under the Storage
Failed A storage module has Critical Alert Unit identifies the affected storage
failed. module.
Failed A storage module has InformationalResolution Unit identifies the affected storage
recovered from a module.
previous failure.
Inserted A storage module was InformationalAlert Unit identifies the affected storage
inserted. module.

Insufficient A storage module Critical Alert Unit identifies the affected storage
Cooling cannot power on module.
because there is
insufficient cooling.
Insufficient A storage module can InformationalResolution Unit identifies the affected storage
Cooling now power on because module.
there is now sufficient
cooling.
Insufficient A storage module Critical Alert Unit identifies the affected storage
Power cannot power on module.
because there is
insufficient power.
Insufficient A storage module can InformationalResolution Unit identifies the affected storage
Power now power on because module.
sufficient power has
been restored.
Removed A storage module was Warning Alert Unit identifies the affected storage
removed. module.
MPA > Component > USB:
The USB events occur when a service processor or management module detects
that the state of a USB device has changed.
Resolution
Over Current v If the severity is Warning: Identify the cause of the over current problem.
Make sure that the power supply is working properly. If necessary, replace
the power supply.
Details

management modules.
v Firmware code
v Sender UUID
v Source UUID
If you select the USB check box in the Event Filter Builder tree, the event filter will
process all of the event types that are specified in the USB subtree.
USB Not applicable Not Not None

You can choose to select specific event types that are displayed under the USB
Inserted A USB device was InformationalResolution None
inserted.
Over Current A monitored current has Warning Alert None
exceeded the rating of
the USB hub.
Over Current A monitored current is InformationalResolution None
now below the rating of
the USB hub.
Over Current A monitored current has Warning Alert None
exceeded the rating of
the USB port.
Over Current A monitored current is InformationalResolution None
now below the rating of
the USB port.
Removed A USB device was Warning Alert None
removed.
MPA > Component > VRM:
The VRM events occur when a service processor or management module detects
that the state of a voltage regulator module (VRM) has changed.
Resolution
Configuration v If the severity is Critical: See the system documentation for configuration
information.
informative only.
Failed v If the severity is Critical: Contact the IBM Technical Support center.
informative only.
Details
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID

If you select the VRM check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the VRM subtree.
VRM Not applicable Not Not None
You can choose to select specific event types that are displayed under the VRM
Configuration The voltage regulator Critical Alert None
module configuration is
not valid.
Note: This event is
processors only.
Configuration The voltage regulator InformationalResolution None
module configuration is
valid.
Note: This event is
processors only.
Failed A voltage regulator Critical Alert Unit identifies the affected voltage
module failed. regulator module.
Failed A voltage regulator Critical Alert None
module failed. You must
manually clear this
event.
Failed A voltage regulator InformationalResolution Unit identifies the affected voltage
module is now working regulator module.
correctly.
MPA > Environmental

The Environmental events occur when a service processor or management module
detects that the state of a system temperature or voltage sensor has changed with
respect to a manufacturer-defined or user-defined threshold. For detailed event
types, expand the Environmental node in the Event Filter Builder tree.
Resolution
Temperature v If the severity is Critical or Warning: Identify the cause of the temperature
informative only.
Voltage v If the severity is Critical or Minor: Identify the cause of the voltage problem.
Make sure that the power supply is working. If necessary, replace the power
supply. The board on which the error occurred might also need to be
replaced.
informative only.

Details
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID
If you select the Environmental check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the
Environmental subtree.
Environmental Not applicable Not Not Side identifies the affected side of an
applicableapplicableRXE-100 Remote Expansion Enclosure.
This extended detail is present only
with event types that are generated for
this enclosure. The enclosure contains
twelve PCI slots that are divided into
two sets of six. Each set can be
configured to belong to the same server
or two different servers.
Environmental node in the Event Filter Builder tree. The event filter will process

Temperature A monitored Critical Alert v Side identifies the affected side of
temperature has an RXE-100 Remote Expansion
exceeded the threshold. Enclosure. This extended detail is
present only with event types
that are generated for this
enclosure. The enclosure contains
twelve PCI slots that are divided
into two sets of six. Each set can
be configured to belong to the
same server or two different
servers.
v Temperature Sensor is one of the
following strings:
– ambient
– Blade Expansion Unit
– CPU
– DASD
– exhaust
– I/O module
– memory
– power supply
– service processor
– voltage regulator
v Unit identifies the affected
sensor. This attribute is
applicable if there is more than
one component of the same type.
For example, if the server has
two CPUs, Unit identifies
whether the event information is
for the first or second CPU.
Temperature A monitored Critical Alert There are no extended details for
temperature has this event type.
exceeded the threshold.
You must manually
clear this event.
Note: This event type
can be generated by:
v IBM Director Agent
for NetWare, version
5.10.
v Service processors
that are configured to
send out-of-band
events using the IBM
Systems Director over
LAN selection.

Temperature A monitored Warning Alert v Side identifies the affected side of
temperature has an RXE-100 Remote Expansion
exceeded the threshold. Enclosure. This extended detail is
servers.
following strings:
– ambient
– CPU
– DASD
– exhaust
– I/O module
– memory
– power supply
Temperature A monitored InformationalResolution v Side identifies the affected side of
temperature is now an RXE-100 Remote Expansion
within the applicable Enclosure. This extended detail is
range. present only with event types
servers.
following strings:
– ambient
– CPU
– DASD
– exhaust
– I/O module
– memory
– power supply

Temperature A monitored Critical Alert v Entity ID identifies the type of
temperature is now device to which the affected
within the applicable temperature sensor is associated,
range. using an ID based on the IPMI
Note: This event is standard.
generated by
management modules v Entity Instance identifies the
on behalf of IBM instance number of the affected
BladeCenter JS21 blade device. For example, if a server
servers. has two processors, Entity
Instance identifies whether the
event information is for
processor 1 or processor 2.
Temperature A monitored Warning Alert v Entity ID identifies the type of
generated by
Temperature A monitored InformationalResolution v Entity ID identifies the type of
generated by

Voltage A monitored voltage is Critical Alert v Component is one of the
operating outside the following strings:
applicable range. – Blade Expansion Unit
– CPU Board
– IO card
– system
– voltage regulator module
v Side identifies the affected side of
an RXE-100 Remote Expansion
Enclosure. This extended detail is
servers.
v Threshold is one of the following
values: high or low. The value
identifies whether the voltage
exceeded a high threshold or fell
below a low threshold.
v Voltage Sensor identifies the
faulty voltage sensor:
– 12V Standby
– 5V Standby
– 3.3V Standby
– 2.5 Standby
– 1.8V Standby
– 1.5V Standby
– 1.2V Standby
– 5V PCI
– 3.3V PCI
– 18V
– 12V
– 5V
– 3.3V
– 2.5V
– 1.8V
– 1.6V
– 1.5V
– 1.3V
– 1.25V
– 1.2V
– 1V
– -5V
– -12V

Voltage A monitored voltage is Critical Alert There are no extended details for
operating outside the this event type.
applicable range. You
event.
Note: This event type
can be generated by:
v IBM Director Agent
for NetWare, version
5.10.
v Service processors
that are configured to
send out-of-band
events using the IBM
Systems Director over
LAN selection.

Voltage A monitored voltage is Minor Alert v Component is one of the
operating outside the following strings:
– CPU Board
– IO card
– system
servers.
– 12V Standby
– 5V Standby
– 3.3V Standby
– 2.5 Standby
– 1.8V Standby
– 1.5V Standby
– 1.2V Standby
– 5V PCI
– 3.3V PCI
– 18V
– 12V
– 5V
– 3.3V
– 2.5V
– 1.8V
– 1.6V
– 1.5V
– 1.3V
– 1.25V
– 1.2V
– 1V
– -5V
– -12V

Voltage A monitored voltage is InformationalResolution v Component is one of the
now within the following strings:
– CPU Board
– IO card
– system
servers.
– 12V Standby
– 5V Standby
– 3.3V Standby
– 2.5 Standby
– 1.8V Standby
– 1.5V Standby
– 1.2V Standby
– 5V PCI
– 3.3V PCI
– 18V
– 12V
– 5V
– 3.3V
– 2.5V
– 1.8V
– 1.6V
– 1.5V
– 1.3V
– 1.25V
– 1.2V
– 1V
– -5V
– -12V
Voltage A monitored voltage is Critical Alert v Entity ID identifies the type of
operating outside the device to which the affected
applicable range. temperature sensor is associated,
Note: This event is using an ID based on the IPMI
generated by standard.
management modules
on behalf of IBM v Entity Instance identifies the
BladeCenter JS21 blade instance number of the affected
servers. device. For example, if a server
has two processors, Entity

Voltage A monitored voltage is Minor Alert v Entity ID identifies the type of
management modules
Voltage A monitored voltage is InformationalResolution v Entity ID identifies the type of
management modules
MPA > Miscellaneous

The Miscellaneous events occur when an IPMI baseboard management controller
reports a problem or information that IBM Systems Director does not associate
with another MPA event type.
Resolution
Details
v Sensor Label
v Sensor Number
v Source UUID
Miscellaneous Miscellaneous event Varies Alert None
occurred. depending
on the
service
processor
that sends
the event.

Miscellaneous Miscellaneous event Varies Resolution None
occurred. depending
on the
service
processor
that sends
the event.
MPA > Platform

The Platform events occur when a service processor detects that the state of the
scalable nodes that are part of a scalable partition or scalable node has changed.
Resolution
For resolution information, see the IBM Scalable Systems Manager version 4.20
Installation and User's Guide.
Details
For detailed information about these events, see the IBM Scalable Systems Manager
version 4.20 Installation and User's Guide.
MPA > Server WatchDog

The Server WatchDog events occur when a service processor or management
module detects that a system has failed to power on and start from the network,
the bootstrap loader program failed to run, operating system timeout settings were
exceeded, or system POST has failed.
Resolution
Boot v If the severity is Critical: Determine why the server failed to start and correct
the problem. See the system documentation for configuration information.
Restart the server.
informative only.
Loader Determine why the operating system failed to load and correct the problem.
See the operating-system documentation. Restart the server.
OS Determine why the operating system failed and correct the problem. See the
operating-system documentation. Restart the server.
POST Determine why POST failed and correct the problem. See the system
documentation for configuration information. Restart the server.
Details
v Firmware code
v Sender UUID
v Sensor Label
v Sensor Number
v Source UUID

If you select the Server WatchDog check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the Server
WatchDog subtree.
Server Not applicable Not Not None
WatchDog applicableapplicable
You can choose to select specific event types that are displayed under the Server
WatchDog node in the Event Filter Builder tree. The event filter will process only
Boot The server failed to Critical Alert None
start.
Boot The server failed to Critical Alert None
start. You must
manually clear this
event.
Boot The server started InformationalResolution None
successfully after a
previous failure.
Loader The loader timeout was Critical Alert None
exceeded. You must
manually clear this
event.
Note: This event is
processors only.
OS The OS timeout was Critical Alert None
exceeded. You must
manually clear this
event.
POST The system POST failed. Critical Alert None
You must manually
clear this event.
MPA > Unknown

The Unknown events occur when a service processor detects an unknown
problem. Typically, the service processor event log provides more information.
Resolution
Check the service processor event log for more information. For information about
checking the service processor event log, see the service processor documentation.
For IBM Systems Director, contact IBM Technical Support and notify them that the
value in the Firmware code extended detail included on this event is not mapping
to an appropriate MPA event.

Details
v Firmware code
v Sender UUID
v Source UUID
Unknown Unknown event. Check Warning Alert None
the service processor
event log for more
information.
Unknown Unknown recovery InformationalResolution None
event. Check the service
more information.
IBM Power platform-specific events

The events listed in this section are specific for the IBM Power hardware platform.
Computer System
These events are generated when a change in the operating condition of a
computer system or its components is detected.
Note: IBM Power events can be generated by systems running AIX, Linux on IBM
Power, HMC, and IVM.
To view these events in the Event Filter Builder tree, expand Managed Resource >
Managed System Resource > Logical Resource > System > Computer System
Conditions
Notes:
1. Events with the condition type Operational Condition are generated by IBM
Director Agent version 5.20 for AIX.
2. For IBM Director Agent version 5.20 for Linux on Power, none of these events
are generated for in-band communication.
Pre-6.1 event type
Condition type Condition value Severity Event availability name
Life Cycle LPAR Created Minor IBM Power CIM > System >
out-of-band Life Cycle
Life Cycle LPAR Deleted Minor IBM Power CIM > System >
Life Cycle CEC Added Minor IBM Power CIM > System >
Life Cycle CEC Deleted Minor IBM Power CIM > System >

Pre-6.1 event type
Power State LPAR Running Minor IBM Power CIM > System >
out-of-band Power State
Power State LPAR Shutdown Minor IBM Power CIM > System >
Power State CEC Powered On Minor IBM Power CIM > System >
Power State CEC Powered Off Minor IBM Power CIM > System >
IP Address Changed IP Address has been Minor IBM Power CIM > System >
changed out-of-band IP Change
Operational Informational Informational IBM Power CIM > System >
Condition in-band and Service Event
out-of-band
Operational Warning Warning IBM Power CIM > System >
out-of-band
Operational Minor Minor IBM Power CIM > System >
out-of-band
Operational Critical Critical IBM Power CIM > System >
out-of-band
Operational Fatal Fatal IBM Power CIM > System >
out-of-band
External Resolution Informational IBM Power CIM > System >
Environment in-band and Service Event
out-of-band
External Non-error or Informational IBM Power CIM > System >
Environment Informational Event in-band and Service Event
out-of-band
External Predictive Error, Warning IBM Power CIM > System >
Environment bypassed with in-band and Service Event
degraded performance out-of-band
(deferred service
action is required)
External Predictive Error, fault Warning IBM Power CIM > System >
Environment might be corrected in-band and Service Event
after platform restart out-of-band
(service action might
be required if system
restart does not fix
problem
External Predictive Error, Minor IBM Power CIM > System >
Environment degraded in-band and Service Event
performancer; fault out-of-band
might be corrected
after platform restart,
degraded performance
problem)

Pre-6.1 event type
External Predictive Error, loss Minor IBM Power CIM > System >
Environment of redundancy (a in-band and Service Event
deferred service or out-of-band
repair action is
required to restore
redundancy; the loss
of redundancy might
or might not impact
performance)
External Predictive Error, Minor IBM Power CIM > System >
Environment general (deferred in-band and Service Event
service action is out-of-band
required)
External Unrecoverable Error, Minor IBM Power CIM > System >
Environment bypassed with loss of in-band and Service Event
function (deferred out-of-band
service action
required)
redundancy and out-of-band
performance (deferred
service action
required)
redundancy (deferred out-of-band
service action
required)
Environment bypassed with in-band and Service Event
(deferred service
action required)
Environment general (service action in-band and Service Event
required immediately) out-of-band
External Error on diagnostic Minor IBM Power CIM > System >
Environment test in-band and Service Event
out-of-band
Host Resolution Informational IBM Power CIM > System >
in-band and Service Event
out-of-band
Host Non-error or Informational IBM Power CIM > System >
Informational Event in-band and Service Event
out-of-band
Host Predictive Error, Warning IBM Power CIM > System >
bypassed with in-band and Service Event
(deferred service
action is required)
Host Predictive Error, fault Warning IBM Power CIM > System >
might be corrected in-band and Service Event
problem

Pre-6.1 event type
Host Predictive Error, Minor IBM Power CIM > System >
degraded in-band and Service Event
might be corrected
problem)
Host Predictive Error, loss Minor IBM Power CIM > System >
of redundancy (a in-band and Service Event
repair action is
required to restore
of redundancy might
or might not impact
performance)
Host Predictive Error, Minor IBM Power CIM > System >
general (deferred in-band and Service Event
required)
Host Unrecoverable Error, Minor IBM Power CIM > System >
bypassed with loss of in-band and Service Event
service action
required)
service action
required)
service action
required)
(deferred service
action required)
general (service action in-band and Service Event
Host Error on diagnostic Minor IBM Power CIM > System >
test in-band and Service Event
out-of-band
I/O Adapter Resolution Informational IBM Power CIM > System >
out-of-band
I/O Adapter Non-error or Informational IBM Power CIM > System >
out-of-band

Pre-6.1 event type
I/O Adapter Predictive Error, Warning IBM Power CIM > System >
(deferred service
action is required)
I/O Adapter Predictive Error, fault Warning IBM Power CIM > System >
problem
I/O Adapter Predictive Error, Minor IBM Power CIM > System >
might be corrected
problem)
I/O Adapter Predictive Error, loss Minor IBM Power CIM > System >
repair action is
required to restore
of redundancy might
or might not impact
performance)
I/O Adapter Predictive Error, Minor IBM Power CIM > System >
required)
I/O Adapter Unrecoverable Error, Minor IBM Power CIM > System >
service action
required)
service action
required)
service action
required)
(deferred service
action required)

Pre-6.1 event type
I/O Adapter Error on diagnostic Minor IBM Power CIM > System >
out-of-band
I/O Subsystem Resolution Informational IBM Power CIM > System >
out-of-band
I/O Subsystem Non-error or Informational IBM Power CIM > System >
out-of-band
I/O Subsystem Predictive Error, Warning IBM Power CIM > System >
(deferred service
action is required)
I/O Subsystem Predictive Error, fault Warning IBM Power CIM > System >
problem
I/O Subsystem Predictive Error, Minor IBM Power CIM > System >
might be corrected
problem)
I/O Subsystem Predictive Error, loss Minor IBM Power CIM > System >
repair action is
required to restore
of redundancy might
or might not impact
performance)
I/O Subsystem Predictive Error, Minor IBM Power CIM > System >
required)
I/O Subsystem Unrecoverable Error, Minor IBM Power CIM > System >
service action
required)
service action
required)
service action
required)

Pre-6.1 event type
(deferred service
action required)
I/O Subsystem Error on diagnostic Minor IBM Power CIM > System >
out-of-band
Operational Resolution Informational IBM Power CIM > System >
out-of-band
Operational Informational (The Informational IBM Power CIM > System >
Condition error log entry is in-band and Service Event
informational and was out-of-band
not the result of an
error.)
Operational Temporary (Indicates Informational IBM Power CIM > System >
Condition that the condition was in-band and Service Event
recovered from after a out-of-band
number of
unsuccessful attempts.
This error type is also
used to record
informational entries,
such as data transfer
statistics for DASD
devices.)
Operational Pending (Loss of Warning IBM Power CIM > System >
Condition availability of a device in-band and Service Event
or component is out-of-band
imminent.)
Operational Performance (The Warning IBM Power CIM > System >
Condition performance of the in-band and Service Event
device or component out-of-band
has degraded to below
an acceptable level.)
Operational Unknown (It is not Warning IBM Power CIM > System >
Condition possible to determine in-band and Service Event
the severity of the out-of-band
error.)
Operational Permanent (Condition Minor IBM Power CIM > System >
Condition that could not be in-band and Service Event
recovered from. Error out-of-band
types with this value
are usually the most
severe errors and are
more likely to mean
that you have a
defective hardware
device or software
module. Error types
other than Permanent
usually do not
indicate a defect, but
they are recorded so
that they can be
analyzed by the
diagnostics.)

Pre-6.1 event type
Other Subsystem Resolution Informational IBM Power CIM > System >
out-of-band
Other Subsystem Non-error or Informational IBM Power CIM > System >
out-of-band
Other Subsystem Predictive Error, Warning IBM Power CIM > System >
(deferred service
action is required)
Other Subsystem Predictive Error, fault Warning IBM Power CIM > System >
problem
Other Subsystem Predictive Error, Minor IBM Power CIM > System >
might be corrected
problem)
Other Subsystem Predictive Error, loss Minor IBM Power CIM > System >
repair action is
required to restore
of redundancy might
or might not impact
performance)
Other Subsystem Predictive Error, Minor IBM Power CIM > System >
required)
Other Subsystem Unrecoverable Error, Minor IBM Power CIM > System >
service action
required)
service action
required)
service action
required)

Pre-6.1 event type
(deferred service
action required)
Other Subsystem Error on diagnostic Minor IBM Power CIM > System >
out-of-band
Platform Firmware Resolution Informational IBM Power CIM > System >
out-of-band
Platform Firmware Non-error or Informational IBM Power CIM > System >
out-of-band
Platform Firmware Predictive Error, Warning IBM Power CIM > System >
(deferred service
action is required)
Platform Firmware Predictive Error, fault Warning IBM Power CIM > System >
problem
Platform Firmware Predictive Error, Minor IBM Power CIM > System >
might be corrected
problem)
Platform Firmware Predictive Error, loss Minor IBM Power CIM > System >
repair action is
required to restore
of redundancy might
or might not impact
performance)
Platform Firmware Predictive Error, Minor IBM Power CIM > System >
required)
Platform Firmware Unrecoverable Error, Minor IBM Power CIM > System >
service action
required)

Pre-6.1 event type
service action
required)
service action
required)
(deferred service
action required)
Platform Firmware Error on diagnostic Minor IBM Power CIM > System >
out-of-band
Power Supply Resolution Informational IBM Power CIM > System >
out-of-band
Power Supply Non-error or Informational IBM Power CIM > System >
out-of-band
Power Supply Predictive Error, Warning IBM Power CIM > System >
(deferred service
action is required)
Power Supply Predictive Error, fault Warning IBM Power CIM > System >
problem
Power Supply Predictive Error, Minor IBM Power CIM > System >
might be corrected
problem)
Power Supply Predictive Error, loss Minor IBM Power CIM > System >
repair action is
required to restore
of redundancy might
or might not impact
performance)

Pre-6.1 event type
Power Supply Predictive Error, Minor IBM Power CIM > System >
required)
Power Supply Unrecoverable Error, Minor IBM Power CIM > System >
service action
required)
service action
required)
service action
required)
(deferred service
action required)
Power Supply Error on diagnostic Minor IBM Power CIM > System >
out-of-band
Surveillance Error Resolution Informational IBM Power CIM > System >
out-of-band
Surveillance Error Non-error or Informational IBM Power CIM > System >
out-of-band
Surveillance Error Predictive Error, Warning IBM Power CIM > System >
(deferred service
action is required)
Surveillance Error Predictive Error, fault Warning IBM Power CIM > System >
problem
Surveillance Error Predictive Error, Minor IBM Power CIM > System >
might be corrected
problem)

Pre-6.1 event type
Surveillance Error Predictive Error, loss Minor IBM Power CIM > System >
repair action is
required to restore
of redundancy might
or might not impact
performance)
Surveillance Error Predictive Error, Minor IBM Power CIM > System >
required)
Surveillance Error Unrecoverable Error, Minor IBM Power CIM > System >
service action
required)
service action
required)
service action
required)
(deferred service
action required)
Surveillance Error Error on diagnostic Minor IBM Power CIM > System >
out-of-band
Ethernet Port
These events are generated when a change in the operating condition of an
Ethernet port is detected.
Note: IBM Power events can be generated by systems running AIX, HMC, and
IVM.
Managed System Resource > Logical Resource > Logical Device > Logical Port >
Network Port > Ethernet Port

Conditions
Event Pre-6.1 event
Condition type Condition value Severity availability type name 1
Operational Condition Resolution Informational IBM Power CIM > System
in-band and > Service Event
out-of-band
Operational Condition Informational (The error Informational IBM Power CIM > System
log entry is in-band and > Service Event
error.)
Operational Condition Temporary (Indicates Informational IBM Power CIM > System
that the condition was in-band and > Service Event
number of unsuccessful
attempts. This error type
is also used to record
statistics for DASD
devices.)
Operational Condition Pending (Loss of Warning IBM Power CIM > System
availability of a device in-band and > Service Event
imminent.)
Operational Condition Performance (The Warning IBM Power CIM > System
performance of the in-band and > Service Event
Operational Condition Unknown (It is not Warning IBM Power CIM > System
possible to determine in-band and > Service Event
the severity of the error.) out-of-band
Operational Condition Permanent (Condition Minor IBM Power CIM > System
that could not be in-band and > Service Event
types with this value are
usually the most severe
errors and are more
likely to mean that you
have a defective
hardware device or
software module. Error
types other than
Permanent usually do
not indicate a defect, but
that they can be
analyzed by the
diagnostics.)
1
Before IBM Systems Director 6.1, these events were generated by AIX systems only.
Fan
These events are generated when a change in the operating condition of a fan is
detected.

Managed System Resource > Logical Resource > Logical Device > Fan
Conditions
Condition type Condition value Severity Event availability
Operational Condition Resolution Informational IBM Power in-band
and out-of-band
Operational Condition Non-error or Informational Informational IBM Power in-band
Event and out-of-band
Operational Condition Predictive Error, bypassed Warning IBM Power in-band
with degraded performance and out-of-band
(deferred service action is
required)
Operational Condition Predictive Error, fault might Warning IBM Power in-band
be corrected after platform and out-of-band
restart (service action might
be required if system restart
does not fix problem
Operational Condition Predictive Error, degraded Minor IBM Power in-band
performancer; fault might be and out-of-band
corrected after platform
restart, degraded performance
(service action might be
required if system restart does
not fix problem)
Operational Condition Predictive Error, loss of Minor IBM Power in-band
redundancy (a deferred and out-of-band
service or repair action is
required to restore
redundancy; the loss of
redundancy might or might
not impact performance)
Operational Condition Predictive Error, general Minor IBM Power in-band
(deferred service action is and out-of-band
required)
Operational Condition Unrecoverable Error, Minor IBM Power in-band
bypassed with loss of and out-of-band
function (deferred service
action required)
redundancy and performance
(deferred service action
required)
redundancy (deferred service
action required)
bypassed with degraded and out-of-band
performance (deferred service
action required)
Operational Condition Unrecoverable Error, general Minor IBM Power in-band
(service action required and out-of-band
immediately)
Operational Condition Error on diagnostic test Minor IBM Power in-band
and out-of-band

Fibre Channel Port
These events are generated when a change in the operating condition of a fibre
channel port is detected.
IVM.
Network Port > Fibre Channel Port
Conditions
Event Pre-6.1 event
out-of-band
error.)
statistics for DASD
devices.)
imminent.)
errors and are more
have a defective
hardware device or
types other than
that they can be
analyzed by the
diagnostics.)

Event Pre-6.1 event
1
Memory
These events are generated when a change in the operating condition of memory is
detected.
Managed System Resource > Logical Resource > Logical Device > Storage Extent >
Memory
Conditions
and out-of-band
required)
not fix problem)
required to restore
required)
action required)
required)

action required)
action required)
immediately)
and out-of-band
Optical Drive
These events are generated by a change in the operating condition of a CD-ROM
drive or DVD drive devices is detected.
IVM.
Managed System Resource > Logical Resource > Logical Device > Media Access
Device > Optical Drive
Conditions
Event Pre-6.1 event
out-of-band
error.)
statistics for DASD
devices.)
imminent.)

Event Pre-6.1 event
errors and are more
have a defective
hardware device or
types other than
that they can be
analyzed by the
diagnostics.)
1
PCI Device
These events are generated by PCI devices such as serial adapters, Topspin
InfiniBand adapters, iSCSI TCP/IP Offload Engine, SCSI enclosures, SCSI adapters,
and USB diskette drives.
IVM.
Managed System Resource > Logical Resource > Logical Device > Controller > PCI
Controller > PCI Device
Conditions
Event Pre-6.1 event
out-of-band
error.)
statistics for DASD
devices.)

Event Pre-6.1 event
imminent.)
errors and are more
have a defective
hardware device or
types other than
that they can be
analyzed by the
diagnostics.)
1
Physical Volume
These events are generated when a change in the operating condition of an IDE
Disk and SCSI Disk devices is detected.
IVM.
Device > Physical Volume
Conditions
IDE Disk
SCSI Disk
Event Pre-6.1 event

out-of-band
error.)

Event Pre-6.1 event
statistics for DASD
devices.)
imminent.)
errors and are more
have a defective
hardware device or
types other than
that they can be
analyzed by the
diagnostics.)
1
Processor
These events are generated when a change in the operating condition of a
processor is detected.
Managed System Resource > Logical Resource > Logical Device > Processor
Conditions
and out-of-band

required)
not fix problem)
required to restore
required)
action required)
required)
action required)
action required)
immediately)
and out-of-band
USB Port
These events are generated when a change in the operating condition of a USB
port is detected.
IVM.

Network Port > USB Port
Conditions
Event Pre-6.1 event
out-of-band
error.)
statistics for DASD
devices.)
imminent.)
errors and are more
have a defective
hardware device or
types other than
that they can be
analyzed by the
diagnostics.)
1
IBM System Storage platform-specific events

The events listed in this section are specific for the IBM System Storage hardware
platform.

Battery
These events are generated when a change in the state of a RAID controller battery
or SAS switch battery is detected.
Managed System Resource > Logical Resource > Logical Device > Battery
Conditions
Condition type Condition value Severity Hardware platform
Connectivity Connected Informational Storage
Connectivity Disconnected Informational Storage
Life Cycle Added Informational Storage
Life Cycle Removed Warning Storage
Battery Status Events Battery Started Charging Informational Storage
Battery Status Events Battery Stopped Charging Informational Storage
Battery Status Events Battery Started Discharging Informational Storage
Battery Status Events Battery Stopped Discharging Informational Storage
Battery Conditioning Battery Started Conditioning Informational Storage
Event
Battery Conditioning Battery Stopped Informational Storage
Event Conditioning
Disk Drive
These events are generated when a change in the state of a hard disk drive is
detected.
Device > Disk Drive
Conditions
Condition type Condition value Severity
Operation Disabled Informational
Operation Enabled Informational
Operational Condition Configuration Error Informational
Operational Condition CRC Error Informational
Operational Condition Failed Informational
Operational Condition Parity Error Informational
Operational Condition Predictive Failure Analysis (PFA) Informational
Disk Drive Power Events Power On Informational
Disk Drive Power Events Power Off Informational
Disk Drive Mounting Events Mount as Global Spare Informational
Disk Drive Mounting Events Unmount Global Spare Informational
Disk Drive Mounting Events Mount as Local Spare Informational
Disk Drive Mounting Events Unmount Local Spare Informational
Disk Drive Software Events Firmware Updated Informational
Disk Drive Software Events Firmware Update Failed Critical

RAID Controller
These events are generated when a change in the state of a RAID controller is
detected.
Managed System Resource > Logical Resource > System > Computer System >
RAID Controller
Conditions
Connectivity Connected Informational
Connectivity Disconnected Informational
Operational Condition Battery Dead Informational
Operational Condition Config Dead Informational
Operational Condition Polling Dead Informational
Operational Condition Failed Informational
Operational Condition OK Informational
Storage Pool
These events are generated when a change in the state of a storage pool is
detected.
Collection > Resource Pool > Storage Pool
Conditions
Life Cycle Created Informational
Life Cycle Modified Informational
Life Cycle Deleted Informational
Storage Subsystem
These events are generated when a change in the state of a Storage Module is
detected.
Storage Subsystem
Conditions
Condition type Condition value Severity Hardware platform
Operational Condition Battery Dead Warning Storage
Operational Condition Failed Critical Storage
Operational Condition OK Informational Storage
Operational Condition Degraded Critical Storage
Software Firmware Update Failed Critical Storage
Software Firmware Updated Informational Storage

Storage Volume
These events are generated when a change in the state of a storage volume is
detected.
Managed System Resource > Logical Resource > Logical Device > Storage Extent >
Storage Volume
Conditions
Life Cycle Created Informational
Life Cycle Change Informational
Life Cycle Deleted Informational
Operational Condition Bad Block Informational
Operational Condition Corrected Redundancy Warning
Connectivity Bad Unmount Critical
Connectivity Mapping Conflict Warning
Connectivity Mapping Overlap Warning
Connectivity Storage Volume Mapped Informational
Connectivity Volume Conflict Critical
Switch
These events are generated when a change in the state of an I/O module (such as
a switch) is detected.
Switch
Conditions
Operational Condition Critical Critical
Operational Condition OK Informational
Operational Condition Warning Warning
PET events
Platform Event Trap (PET) events are generated by systems with Alert Standard
Format (ASF) or an IPMI baseboard management controller. The PET events
provide advance warning of possible system failures.
Details
Note: For detailed information about Platform Event Traps, see the following
documentation:
v Intel Intelligent Platform Management Interface Specification Version 1.5, dated June
1, 2004.
v Intel IPMI Platform Event Trap Specification Version 1.0, dated December 7, 1998.

For IBM Director 5.20 or later, ASF configuration is no longer supported. However,
any managed systems that you have previously configured in your IBM Systems
Director environment will still generate PET events and IBM Systems Director will
receive those events.
If a system has an IPMI baseboard management controller, both a PET event and
an equivalent MPA event are sent to IBM Systems Director Server. Because the
MPA event provides more information and is easier to read, it is recommended
that you create event-action plans with event filters for the MPA event types.
If you select the PET check box in the Event Filter Builder tree, the event filter will
process all of the event types that are specified in the PET subtree.
PET Not applicable Not Not None
PET > Environmental

The Environmental event occurs when a change in the state of the system
environment is detected. In the IBM Systems Director environment, the
Environmental event types are associated with the state of the sensors that detect
changes in a system environment. For detailed event types, expand the
Environmental node in the Event Filter Builder tree.
Details
If you select the Environmental check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the
Environmental subtree. You can choose to select specific event types that are
displayed under the Environmental node in the Event Filter Builder tree. The event
Environmental Not applicable Not Not Standard set of PET event type
applicableapplicableextended details
PET > Environmental > Sensor

The Sensor events occur when a change in the state of an environmental sensor is
detected.
Details
If you select the Sensor check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the Sensor subtree.
Sensor Not applicable Not Not Standard set of PET event type
You can choose to select specific event types that are displayed under the Sensor

Note: The severity for some of these event types is determined by the Event
Severity extended detail.
Case Case intrusion Set by Alert Standard set of PET event type
Intrusion information the extended details
Event
Severity
attribute.
Case Case intrusion Harmless ResolutionStandard set of PET event type
Intrusion information extended details
Current Current information Set by Alert Standard set of PET event type
the extended details
Event
Severity
attribute.
Current Current information Harmless ResolutionStandard set of PET event type
extended details
Fan Fan information for Set by Alert Standard set of PET event type
device device. the extended details
Event
where device is the value Severity
provided by the Entity attribute.
Instance extended detail.
Fan Fan information for Harmless ResolutionStandard set of PET event type
device device. extended details
where device is the value

provided by the Entity
Fan Device device inserted. Set by Alert Standard set of PET event type
where device is the value Event
provided by the Entity Severity
Instance extended detail. attribute.
Fan Device device has been Harmless ResolutionStandard set of PET event type
inserted. extended details

Fan Device device has been Set by Alert Standard set of PET event type
removed. the extended details
Event
Fan Device device has been Harmless ResolutionStandard set of PET event type
removed. extended details

Power Supply Power supply Set by Alert Standard set of PET event type
information the extended details
Event
Severity
attribute.
Power Supply Power supply Harmless ResolutionStandard set of PET event type
information extended details

Power Supply Redundancy has been Set by Alert Standard set of PET event type
lost. the extended details
Event
Severity
attribute.
Power Supply Redundancy has been Harmless ResolutionStandard set of PET event type
lost. extended details
degraded. the extended details
Event
Severity
attribute.
degraded. extended details
regained. the extended details
Event
Severity
attribute.
regained. extended details
Temperature Temperature information Set by Alert Standard set of PET event type
Event
Severity
attribute.
Temperature Temperature information Harmless ResolutionStandard set of PET event type
extended details
Voltage Voltage information for Set by Alert Standard set of PET event type
device device. the extended details
Event
Voltage Voltage information for Harmless ResolutionStandard set of PET event type
device device. extended details

PET > Firmware

The Firmware events occur when a change in the state of the system firmware is
detected. In the IBM Systems Director environment, the Firmware event types are
associated with the state of the BIOS. For detailed event types, expand the
Firmware node in the Event Filter Builder tree.
Details
If you select the Firmware check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Firmware subtree.
Firmware node in the Event Filter Builder tree. The event filter will process only

Firmware Not applicable Not Not Standard set of PET event type
PET > Firmware > BIOS

The BIOS events occur when a change in the state of the system BIOS is detected.
Details
If you select the BIOS check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the BIOS subtree.
BIOS Not applicable Not Not Standard set of PET event type
You can choose to select specific event types that are displayed under the BIOS
Progress System firmware Set by Alert Standard set of PET event type
progress information the extended details
Event
Severity
attribute.
Progress System firmware Harmless ResolutionStandard set of PET event type
progress information extended details
Progress The system firmware Set by Alert Standard set of PET event type
encountered an error in the extended details
POST. Event
Severity
attribute.
Progress The system firmware Harmless ResolutionStandard set of PET event type
encountered an error in extended details
POST.
Progress The system boot has Set by Alert Standard set of PET event type
started. the extended details
Event
Severity
attribute.
Progress The system boot has Harmless ResolutionStandard set of PET event type
started. extended details
Progress The system firmware Set by Alert Standard set of PET event type
has hung. the extended details
Event
Severity
attribute.
Progress The system firmware Harmless ResolutionStandard set of PET event type
has hung. extended details

PET > Hardware
The Hardware events occur when a change in the state of a hardware component
is detected. Hardware components include cables and interconnects, network
connections, hard disk drives, timers, and other modules.
Details
If you select the Hardware check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Hardware subtree.
Hardware Not applicable Not Not Standard set of PET event type
Hardware node in the Event Filter Builder tree. The event filter will process only
Cable/ The device is not Set by Alert Standard set of PET event type
Interconnect present. the extended details
Event
Severity
attribute.
Cable/ The device is not Harmless ResolutionStandard set of PET event type
Interconnect present. extended details
Cable/ The device is present. Set by Alert Standard set of PET event type
Interconnect the extended details
Event
Severity
attribute.
Cable/ The device is present. Harmless ResolutionStandard set of PET event type
Interconnect extended details
Drive bay Device device has been Set by Alert Standard set of PET event type
removed. the extended details
Event
Drive bay Device device has been Harmless ResolutionStandard set of PET event type
removed. extended details

Drive bay The state of device device Set by Alert Standard set of PET event type
has changed to critical. the extended details
Event

Drive bay The state of device device Harmless ResolutionStandard set of PET event type
has changed to critical. extended details

Drive bay Device device has been Set by Alert Standard set of PET event type
inserted. the extended details
Event
Drive bay Device device has been Harmless ResolutionStandard set of PET event type
inserted. extended details

Drive bay The state of device device Set by Alert Standard set of PET event type
has changed to OK. the extended details
Event
Drive bay The state of device device Harmless ResolutionStandard set of PET event type
has changed to OK. extended details

Module/ The device is not Set by Alert Standard set of PET event type
Board present. the extended details
Event
Severity
attribute.
Module/ The device is not Harmless ResolutionStandard set of PET event type
Board present. extended details
Module/ The device is present. Set by Alert Standard set of PET event type
Board the extended details
Event
Severity
attribute.
Module/ The device is present. Harmless ResolutionStandard set of PET event type
Board extended details
Monitor The state of the Set by Alert Standard set of PET event type
ASIC/IC system-management the extended details
module has changed to Event
critical. Severity
attribute.
Monitor The state of the Harmless ResolutionStandard set of PET event type
ASIC/IC system-management extended details
module has changed to
critical.
Network The network connection Set by Alert Standard set of PET event type
is offline. the extended details
Event
Severity
attribute.
Network The network connection Harmless ResolutionStandard set of PET event type
is offline. extended details

has degraded. the extended details
Event
Severity
attribute.
has degraded. extended details
is online. the extended details
Event
Severity
attribute.
is online. extended details
Watchdog 1 The watchdog timer has Set by Alert Standard set of PET event type
expired. the extended details
Event
Severity
attribute.
Watchdog 1 The watchdog timer has Harmless ResolutionStandard set of PET event type
expired. extended details
Watchdog 2 The timer has expired. Set by Alert Standard set of PET event type
Event
Severity
attribute.
Watchdog 2 The timer has expired. Harmless ResolutionStandard set of PET event type
extended details
PET > System

The System events occur when a change in the state of a system is detected. In the
IBM Systems Director environment, the System event types are associated with the
state of the operating system. For detailed event types, expand the System node in
the Event Filter Builder tree.
Details
will process all of the event types that are specified in the System subtree. You can
choose to select specific event types that are displayed under the System node in
the Event Filter Builder tree. The event filter will process only the event types that
you select.
System Not applicable Not Not Standard set of PET event type
PET > System > OS

The OS events occur when a change in the state of the operating system is
detected.
Details
If you select the OS check box in the Event Filter Builder tree, the event filter will
process all of the event types that are specified in the OS subtree.

OS Not applicable Not Not Standard set of PET event type
You can choose to select specific event types that are displayed under the OS node
in the Event Filter Builder tree. The event filter will process only the event types
that you select.
Boot The operating system Set by Alert Standard set of PET event type
has failed to start (boot). the extended details
Event
Severity
attribute.
Boot The operating system Harmless ResolutionStandard set of PET event type
has failed to start (boot). extended details
Boot No media or device can Set by Alert Standard set of PET event type
be started (booted). the extended details
Event
Severity
attribute.
Boot No media or device can Harmless ResolutionStandard set of PET event type
be started (booted). extended details
Operation The operating system Set by Alert Standard set of PET event type
has hung. the extended details
Event
Severity
attribute.
Operation The operating system Harmless ResolutionStandard set of PET event type
has hung. extended details
Operation > Heartbeat information Harmless ResolutionStandard set of PET event type
Heartbeat extended details
SNMP events
The SNMP events represent SNMP traps that are generated by the SNMP agents,
software programs, and IBM hardware. A subset of the SNMP events are generated
by Platform Agent and Common Agent.
Event source
SNMP traps are generated by the SNMP agents that are installed on the SNMP
devices being managed by IBM Systems Director Server. IBM Systems Director
receives the SNMP traps and converts them into the SNMP event types that are
displayed in the Event Filter Builder tree. See each event type for details about its
source.
Details
When you compile MIB files, they contain the trap definition of the traps that are
displayed in the Event Filter Builder.

Note: You must load the MIB files into memory in order to view the SNMP event
types in the Event Filter Builder tree. For more information, see “Selecting MIB
files to load into memory.”
The event types available in the Event Filter Builder tree can vary depending on
which MIB files you have loaded into memory and what products provided the
MIB file. The IBM Systems Director information center provides information about
the ibmSystemMIB and ibmServeRAIDMIB event types. For other SNMP event
types under the iso node, see the MIB file that contains these SNMP traps.
The trap definitions can conform to either SNMP v1 or SNMP v2. The exact
subnode under which the traps are displayed depends on which branch of the
standard MIB the traps’ MIB is under: experimental, mgmt, private, or snmpV2.
Trap definitions from most MIBs, are displayed under the private subnode
(SNMP.iso.org.internet.private). Traps defined in the standard MIBs, such as MIB II,
are displayed under the mgmt subnode (SNMP.iso.org.internet.mgmt).
If you select the SNMP check box in the Event Filter Builder tree, the event filter
will process all of the events that are specified in the SNMP subtree. You can
choose to select specific event types that are displayed under the SNMP node in
the Event Filter Builder tree. The event filter will process only the events that you
select.
ibmSystemMIB
The ibmSystemMIB events provide information about system subcomponent
failures and warranty and lease status. For detailed events, expand the
ibmSystemMIB node in the Event Filter Builder tree.
Details
The full path for this event type in the Event Filter Builder tree is:
SNMP > iso > org > dod > internet > private > enterprises > ibm > ibmProd >
director > ibmSystem > ibmSystemMIB
If you select the ibmSystemMIB check box in the Event Filter Builder tree, the
event filter will process all of the events that are specified in the ibmSystemMIB
subtree. You can choose to select specific event types that are displayed under the
ibmSystemMIB node in the Event Filter Builder tree. The event filter will process
only the events that you select.
ibmSystemTrapChassis
The ibmSystemTrapChassis event occurs when the state of a system chassis
(enclosure) changes, such as when the cover is removed from the system.
Resolution
v If the severity is Critical: Make sure that the chassis cover is closed.
v If the severity is Harmless: The error has been resolved. This event is
informative only.
Details
Event type Event text Severity
ibmSystemTrapChassis System Enclosure Sensor reported intrusion detection. Critical
ibmSystemTrapChassis System Enclosure Sensor reports normal. Harmless

ibmSystemTrapDASDBackplane
The ibmSystemTrapDASDBackplane event occurs when the Remote Supervisor
Adapter detects that the state of the system hard disk drive changes with respect
to its availability.
Resolution
Replace the specified hard disk drive that has failed. If necessary, restore your data
from a backup.
Details
ibmSystemTrapDASDBackplane
Drive drive has reported a fault. This event must be cleared Critical
manually.
where drive is the affected hard disk drive.
ibmSystemTrapErrorLog
The ibmSystemTrapErrorLog event occurs when the Remote Supervisor Adapter
detects that its error log is at 75% or 100% of its capacity.
Resolution
If the severity is Warning: Back up and clear the system-management processor

event log.
Details
ibmSystemTrapErrorLog The system management processor error log is 75% full. This Warning
ibmSystemTrapErrorLog The system management processor error log is full. This Warning
ibmSystemTrapFan
The ibmSystemTrapFan event occurs when the state of a system fan has changed
with respect to the manufacturer-defined revolutions per minute (rpm) values. This
event is sent when a fan stops, is removed, or is not performing optimally.
Resolution
v If the severity is Critical: Replace the specified fan that has failed.
informative only.

Details
ibmSystemTrapFan Fan Sensor number fell below threshold of threshold rpm. The Critical
current value is speed rpm.
where:
v threshold is the critical fan threshold value.
Note: This event must be cleared manually.

ibmSystemTrapFan Fan Sensor number reports normal. Harmless
ibmSystemTrapGenericFan
The ibmSystemTrapGenericFan event occurs when the Remote Supervisor Adapter
or ASM processor detects that the state of a system fan has changed with respect
to its manufacturer-defined revolutions per minute (rpm) thresholds but the precise
fan instance cannot be determined.
Resolution
Replace the failed fan.
Details
ibmSystemTrapGenericFan Fan Sensor number fell below threshold of threshold rpm. The Critical
current value is speed rpm.
where:
v threshold is the critical fan threshold value.
Note: This event must be cleared manually.
ibmSystemTrapGenericFan Fan Sensor number reports normal. Harmless
ibmSystemTrapGenericVoltage
The ibmSystemTrapGenericVoltage event occurs when the Remote Supervisor
Adapter or the ASM processor detects that the state of a system voltage sensor has
changed with respect to a manufacturer-defined threshold but the precise voltage
sensor cannot be determined.
Resolution
Identify the cause of the voltage problem. Make sure that the power supply is
working. If necessary, replace the power supply.

Details
Voltage Sensor number fell below threshold of threshold Volts. Critical
The current value is current Volts.
where:
v number is the affected voltage sensor.
v current is the current voltage reading.
Voltage Sensor number exceeded threshold of threshold Volts. Critical
where:
Voltage Sensor number reports normal. Harmless
where number is the affected voltage sensor.
ibmSystemTrapLeaseExpiration
The ibmSystemTrapLeaseExpiration event occurs when the system lease expiration
date has been reached with respect to the value configured for the date in the
Asset ID task.
Resolution
v If the severity is Warning: The lease has expired.
informative only.
Details
The date value is provided by the Asset ID task. The Lease page in the Asset ID
task includes the End Date field where you can set the lease expiration date. The
date is stored in the IBMPSG_Lease.LeaseEndDate CIM property that is monitored
at regular poll intervals. A CIM indication is generated when the system CIMOM
starts and when a state change is detected relative to the internal poll interval. If
you have set SNMP trap forwarding, the CIM indication is converted to an SNMP
event.
The lease on system has expired. It expired on date. Warning
where system is the affected system and date is the lease

expiration date.
The lease on system is normal. It will expire on date. Harmless
where system is the affected system and date is the lease

expiration date.
ibmSystemTrapMemoryPF
The ibmSystemTrapMemoryPF event occurs when a dual inline memory module
(DIMM) in a system is about to fail.

Resolution
failed.
informative only.
Details
ibmSystemTrapMemoryPF Memory device identified as memory in bank slot is Critical
predicting an imminent failure.
where slot is the affected memory slot.

ibmSystemTrapMemoryPF Memory device identified as memory in bank slot is not Harmless
where slot is the affected memory slot.
ibmSystemTrapMgmtHwLogStatus
The ibmSystemTrapMgmtHwLogStatus event occurs when the system-management
processor error log is 75% full or full. This event is supported on servers with
Intelligent Platform Management Interface (IPMI).
Resolution
To correct this problem, reduce the number of events in the event log. You can
clear the event log using the BIOS configuration utility on the server or remotely
using the OSA SMBridge utility. See the documentation for your server or the IBM
Redbooks publication IBM eServer xSeries and BladeCenter Server Management
(SG24-6495).
Details
ibmSystemTrapMgmtHwLogStatus The system management processor error log is 75% Harmless
full. This event must be cleared manually.
ibmSystemTrapMgmtHwLogStatus The system management processor error log is full. Harmless
This event must be cleared manually.
ibmSystemTrapNetworkAdapterFailed
The ibmSystemTrapNetworkAdapterFailed event occurs when a network interface
card (NIC) in a system has failed.
Resolution
Replace the specified NIC that has failed.
Details
ibmSystemTrapNetworkAdapterFailed
The network adapter failed. Critical
ibmSystemTrapNetworkAdapterOffline
The ibmSystemTrapNetworkAdapterOffline event occurs when a network interface
card (NIC) in a system goes offline.

Resolution
Details
ibmSystemTrapNetworkAdapterOffline
The network adapter is offline. Warning
ibmSystemTrapNetworkAdapterOnline
The ibmSystemTrapNetworkAdapterOnline event occurs when the state of a
system network interface card (NIC) changes from offline to online.
Resolution
Details
ibmSystemTrapNetworkAdapterOnline
The network adapter is online. Harmless
ibmSystemTrapPFA
The ibmSystemTrapPFA event occurs when the Remote Supervisor Adapter detects
that a component in a system is about to fail.
Resolution
Identify and replace the component that is generating the Predictive Failure
Analysis event.
Details
ibmSystemTrapPFA Predictive Failure Detected. Please check the system Critical
management processor error log for more information. This
ibmSystemTrapPowerSupply
The ibmSystemTrapPowerSupply event occurs when the state of a system power
supply changes with respect to its availability.
Resolution
informative only.

Details
PowerSupply device identified as PowerSupply number Critical
reports critical state with possible loss of redundancy.
where number is the affected power supply.

PowerSupply device identified as PowerSupply number has Critical
failed. This event must be cleared manually.

PowerSupply device identified as PowerSupply number has Warning
lost AC power and loss of standby power is imminent.

PowerSupply device identified as PowerSupply number Harmless
reports normal.
ibmSystemTrapProcessorPF
The ibmSystemTrapProcessorPF event occurs when the processor is about to fail.
Resolution
failed.
informative only.
Details
ibmSystemTrapProcessorPFProcessor device identified as processor in slot slot is Critical
predicting an imminent failure.
where slot is the affected processor slot.

ibmSystemTrapProcessorPFProcessor device identified as processor in slot slot is not Harmless
where slot is the affected processor slot.
ibmSystemTrapRedundantNIC
The ibmSystemTrapRedundantNIC event occurs when the state of a system
network interface card (NIC) changes with respect to its redundancy. There are
certain limitations of the NIC that cannot be compensated for between a
switchover and a switchback.
Resolution
Details
ibmSystemTrapRedundantNIC
A network interface card (NIC) failover has occurred. This Warning
requires a teamed configuration.

ibmSystemTrapRedundantNICSwitchback
The ibmSystemTrapRedundantNICSwitchback event occurs when the primary
network interface card (NIC) is restored in a teamed NIC configuration.
Resolution
Details
Onboard NIC has Switched Back Warning
NIC in PCI Bus bus Slot slot has Switched Back Warning
where bus is the affected bus and slot is the affected

slot.
NIC in PCI Slot slot has Switched Back Warning
where slot is the affected slot.

NIC has Switched Back Warning
ibmSystemTrapRedundantNICSwitchover
The ibmSystemTrapRedundantNICSwitchover event occurs when the primary
network interface card (NIC) fails in a teamed NIC configuration and the standby
NIC becomes the active NIC.
Resolution
Details
Onboard NIC has Switched Over Warning
NIC in PCI Bus bus Slot slot has Switched Over Warning
where bus is the affected bus and slot is the affected

slot.
NIC in PCI Slot slot has Switched Over Warning
where slot is the affected slot.

NIC has Switched Over Warning
ibmSystemTrapRemoteLogin
The ibmSystemTrapRemoteLogin event occurs when an end-user or application has
logged in to the Web interface of the Remote Supervisor Adapter.
Resolution

Details
ibmSystemTrapRemoteLogin
The system management processor has been accessed via a Warning
remote login. This event must be cleared manually.
ibmSystemTrapSMART
The ibmSystemTrapSMART event occurs when the state of an IDE or SCSI hard
disk drive that complies with the self-monitoring, analysis, and reporting
technology (SMART) changes with respect to its availability.
Resolution
v If the severity is Critical: Replace the specified hard disk drive that is failing or
has failed.
informative only.
Details
ibmSystemTrapSMART Device device identified as physical drive drive is predicting Critical
where Device is IDE, SCSI, or Unknown and drive is the

affected SMART drive.
ibmSystemTrapSMART Device device identified as physical drive drive is not Harmless
where Device is IDE, SCSI, or Unknown and drive is the

affected SMART drive.
ibmSystemTrapSPPowerSupply
The ibmSystemTrapSPPowerSupply event occurs when the Advanced Systems
Management processor (ASM processor) detects that the state of the system power
supply changes with respect to its availability. This is sent from servers that do not
have a power backplane and do not support a recovery severity or alert type.
Resolution
informative only.
Details
ibmSystemTrapSPPowerSupply PowerSupply device identified as PowerSupply number Critical
reports critical state with possible loss of redundancy.

ibmSystemTrapSPPowerSupply PowerSupply device identified as PowerSupply number Critical
has failed. This event must be cleared manually.

ibmSystemTrapSPPowerSupply PowerSupply device identified as PowerSupply number Warning
has lost AC power and loss of standby power is
imminent.

ibmSystemTrapSPPowerSupply PowerSupply device identified as PowerSupply number Harmless
reports normal.
ibmSystemTrapStorage
The ibmSystemTrapStorage event occurs when the state of system hard disk drive
space changes with respect to user-defined levels of hard disk drive space
remaining. By default, the warning level is 5% remaining and critical level is 3%
remaining.
Resolution
v If the severity is Critical or Warning: Remove files from the specified hard disk
or lower the minimum threshold.
informative only.
Details
ibmSystemTrapStorage Logical drive name fell below threshold of threshold MB. The Critical
current value is value MB.
where:
v threshold is the critical threshold value.
v value is the amount of current disk space available.
ibmSystemTrapStorage Logical drive name fell below threshold of threshold MB. The Warning
current value is value MB.
where:
v threshold is the warning threshold value.
v value is the amount of current disk space available.
ibmSystemTrapStorage Logical drive name free space is normal. The current value is Harmless
value MB.
where name is the affected logical drive and value is the

amount of current disk space available.
ibmSystemTrapStorage Logical drive name status could not be determined. Unknown
where name is the affected logical drive.
ibmSystemTrapTemperature
The ibmSystemTrapTemperature event occurs when the state of a system
temperature sensor changes with respect to a manufacturer-defined or user-defined
threshold.
Resolution
v If the severity is Critical or Warning: Identify the cause of the temperature

informative only.
Details
ibmSystemTrapTemperatureTemperature Sensor number exceeded the manufacturer Critical
defined threshold of threshold Celsius. The current value is
current Celsius.
where:
v number is the affected temperature sensor.
v threshold is the manufacturer-defined threshold value.
v current is the current temperature reading.
ibmSystemTrapTemperatureTemperature Sensor number exceeded the user defined Critical
threshold of threshold Celsius. The current value is current
Celsius.
where:
v threshold is the user-defined threshold value.
ibmSystemTrapTemperatureTemperature Sensor number exceeded the manufacturer Warning
defined threshold of threshold Celsius. The current value is
current Celsius.
where:
v threshold is the manufacturer-defined threshold value.
ibmSystemTrapTemperatureTemperature Sensor number exceeded the user defined Warning
threshold of threshold Celsius. The current value is current
Celsius.
where:
v threshold is the user-defined threshold value.
ibmSystemTrapTemperatureTemperature Sensor number reports normal. Harmless
where number is the affected temperature sensor.
ibmSystemTrapVoltage
The ibmSystemTrapVoltage event occurs when the state of a system voltage sensor
changes with respect to a manufacturer-defined threshold.
Resolution
v If the severity is Critical: Identify the cause of the voltage problem. Make sure
that the power supply is working. If necessary, replace the power supply.
informative only.

Details
ibmSystemTrapVoltage Voltage Sensor number fell below threshold of threshold Volts. Critical
where:
ibmSystemTrapVoltage Voltage Sensor number exceeded threshold of threshold Volts. Critical
where:
ibmSystemTrapVoltage Voltage Sensor number reports normal. Harmless
where number is the affected voltage sensor.
ibmSystemTrapWarrantyExpiration
The ibmSystemTrapWarrantyExpiration event occurs when the system warranty
expiration date has been reached with respect to the value configured for the date
while using the Asset ID task.
Resolution
v If the severity is Warning: The warranty has expired.
informative only.
Details
The date value in the event text is provided by the Asset ID task. The Warranty
page in the Asset ID task includes the End Date field where you can set the lease
expiration date. The date is stored in the IBMPSG_Warranty.EndDate CIM property
that is monitored at regular poll intervals. A CIM indication is generated when the
system CIMOM starts and when a state change is detected relative to the internal
poll interval. If you have set SNMP trap forwarding, the CIM indication is
converted to an SNMP event.
The warranty on system has expired. It expired on date. Warning
where system is the affected system and date is the

warranty expiration date.
The warranty on system is normal. It will expire on date. Harmless
where system is the affected system and date is the

warranty expiration date.
ibmSystemTrapxAutomaticServerRestart
The ibmSystemTrapxAutomaticServerRestart event occurs when the operating
system locks up and no longer responds. Subsequently, a system restart (reboot)
begins. This event is supported on servers with Intelligent Platform Management
Interface (IPMI).

Resolution
Details
The last system restart was due to the automatic Warning
server restart hardware.
The last system restart was not due to the automatic Harmless
server restart hardware.
ibmSystemRaid
The ibmSystemRaid events provide information about RAID subcomponent
failures and the status of RAID operations such as synchronization, logical-drive
migration, rebuild, compaction, compression, expansion, verify, and more. For
detailed events, expand the ibmSystemRaid node in the Event Filter Builder tree.
Details
The full path for this event type in the Event Filter Builder tree is:
SNMP > iso > org > dod > internet > private > enterprises > ibm > ibmProd >
ibmServer > ibmSystem > ibmSystemMIB > ibmSystemRAID >
ibmSystemRAIDTrap
If you select the ibmSystemRaid check box in the Event Filter Builder tree, the
event filter will process all of the events that are specified in the ibmSystemRaid
subtree. You can choose to select specific event types that are displayed under the
ibmSystemRaid node in the Event Filter Builder tree. The event filter will process
only the events that you select.
The MIB file for the ibmSystemRaid event types, IBM-SYSTEM-RAID-MIB.mib, is

in the install_root/proddata/snmp directory, where install_root is the root directory of
your IBM Systems Director Server installation. Note that this path uses the
backslash (\) to delimit the directory; depending on the system that you are using,
you might be required to enter the path using the forward slash (/).
ibmSystemRaidArrayFlashCopyComplete
The ibmSystemRaidArrayFlashCopyComplete event occurs when a RAID
FlashCopy operation is completed on a specified array in a RAID configuration.
Resolution
Details
ibmSystemRaidArrayFlashCopyComplete
FlashCopy with backup complete: array. Harmless

ibmSystemRaidArrayFlashCopyDetected
The ibmSystemRaidArrayFlashCopyDetected event occurs when a RAID
FlashCopy operation is in progress on a specified array in a RAID configuration.
Resolution
Details
ibmSystemRaidArrayFlashCopyDetected
FlashCopy in progress: array. Harmless
ibmSystemRaidArrayFlashCopyFail
The ibmSystemRaidArrayFlashCopyFail event occurs when a RAID FlashCopy
operation fails on a specified array in a RAID configuration.
Resolution
logical drive might be offline.
If the source logical drive is offline, replace the failed hard disk drives and restore
the data from tape backup. If the target logical drive is offline, replace the failed
hard disk drives. FlashCopy operations will not work when the source or target
logical drives are offline.
Details
ibmSystemRaidArrayFlashCopyFail FlashCopy with backup failed: array [error] Critical
where array is the affected array and error is the error

code.
ibmSystemRaidArrayRebuildComplete
The ibmSystemRaidArrayRebuildComplete event occurs when a RAID rebuild
operation is completed on a specified array in a RAID configuration.
Resolution

Details
ibmSystemRaidArrayRebuildComplete
Rebuild complete: array. Harmless
ibmSystemRaidArrayRebuildDetected
The ibmSystemRaidArrayRebuildDetected event occurs when a RAID rebuild
operation is in progress on a specified array in a RAID configuration.
Resolution
Details
ibmSystemRaidArrayRebuildDetected
Rebuilding: array. Harmless
ibmSystemRaidArrayRebuildFail
The ibmSystemRaidArrayRebuildFail event occurs when a RAID rebuild operation
fails on a specified array in a RAID configuration.
Resolution
Details
ibmSystemRaidArrayRebuildFail Rebuild failed: array [error] Critical

code.
ibmSystemRaidArraySyncComplete
The ibmSystemRaidArraySyncComplete event occurs when a RAID
synchronization operation is completed on a specified array in a RAID
configuration.
Resolution

Details
ibmSystemRaidArraySyncComplete Synchronize complete: array. Harmless
ibmSystemRaidArraySyncDetected
The ibmSystemRaidArraySyncDetected event occurs when a RAID synchronization
operation is in progress on a specified array in a RAID configuration.
Resolution
Details
ibmSystemRaidArraySyncDetected Synchronizing: array. Harmless
ibmSystemRaidArraySyncFail
The ibmSystemRaidArraySyncFail event occurs when a RAID synchronization
operation fails on a specified array in a RAID configuration.
Resolution
following steps:
Details
ibmSystemRaidArraySyncFail Synchronize failed: array [error] Critical

code.
ibmSystemRaidCompactionComplete
The ibmSystemRaidCompactionComplete event occurs when a RAID compaction
operation is completed on a specified logical drive in a RAID configuration.

Resolution
Details
ibmSystemRaidCompactionCompleteCompaction complete: drive. Harmless
ibmSystemRaidCompactionDetected
The ibmSystemRaidCompactionDetected event occurs when a RAID compaction
operation is in progress on a specified logical drive in a RAID configuration.
Resolution
Details
ibmSystemRaidCompactionDetectedCompacting: drive. Harmless
ibmSystemRaidCompactionFail
The ibmSystemRaidCompactionFail event occurs when a RAID compaction
operation fails on a specified logical drive in a RAID configuration.
Resolution
Details
ibmSystemRaidCompactionFail Compaction failed: drive [error] Critical
where drive is the affected logical drive and

ibmSystemRaidCompressionComplete
The ibmSystemRaidCompressionComplete event occurs when a RAID compression
Resolution

Details
ibmSystemRaidCompressionComplete
Compression complete: drive. Harmless
ibmSystemRaidCompressionDetected
The ibmSystemRaidCompressionDetected event occurs when a RAID compression
Resolution
Details
ibmSystemRaidCompressionDetected
Compressing: drive. Harmless
ibmSystemRaidCompressionFail
The ibmSystemRaidCompressionFail event occurs when a RAID compression
Resolution
Details
ibmSystemRaidCompressionFail Compression failed: drive [error]. Critical
where drive is the affected logical drive and error is the

error code.
ibmSystemRaidConfigFail
The ibmSystemRaidConfigFail event occurs when a RAID controller configuration
cannot be read.
Resolution
A hardware error occurred. To correct the problem, complete the following steps:

5. If the problem persists, complete the following steps:
a. Restore to factory-default settings.
b. Recreate the configuration.
Details
ibmSystemRaidConfigFail Error getting controller configuration. Critical
ibmSystemRaidControllerAdded
The ibmSystemRaidControllerAdded event occurs when a specified RAID
controller is added to a system.
Resolution
Details
ibmSystemRaidControllerAdded A controller has been added to the system: controller Harmless
where controller is the added controller.
ibmSystemRaidControllerBadStripes
The ibmSystemRaidControllerBadStripes event occurs when one or more logical
drives contain at least one bad stripe.
Resolution
The Bad Stripe Table (BST) provides a means of recovering most data on a logical
drive after multiple hardware errors prevent access to a logical drive stripe. An
entry in the BST indicates that the data contained in a stripe has been lost.
While many conditions can produce a Bad Stripe Table entry, the most common
cause is an error accessing one of the stripe units within a stripe of a critical logical
drive. A single stripe unit failure is correctable and recoverable but two or more
failures within the same redundant RAID stripe are not.
For example, in a critical RAID-5 array, in which one of the drives in the array is
defunct, a stripe will be marked bad with an entry in the BST if a non-recoverable
media error occurs when accessing one of the other drives of the array.
After an entry is logged in the BST, the controller will return an error code to the
driver whenever the host system tries to access a Logical Block Address (LBA)
within the affected stripe. This is one immediate indication that some part of the
logical drive is unusable.
Note: It is not possible to correlate the bad stripe with a specific file in the
operating system.
To resolve this error, complete the following steps:

v Check the ServeRAID Manager event logs to identify the affected logical
drive(s).
v Because the data has been lost, the only way to recover from this condition is to
1. Delete the array.
2. Recreate the array and its logical drives.
3. Restore the data from backup media.
Note: The alternative is to take the entire logical drive offline, thus resulting in
the loss of all data contained on that logical drive.
To minimize the risk of lost data, be sure to schedule frequent periodic backups.
Details
ibmSystemRaidControllerBadStripesOne or more logical drives contain a bad stripe: Warning
controller
where controller is the controller for the affected logical

drives.
ibmSystemRaidControllerBatteryOvertemp
The ibmSystemRaidControllerBatteryOvertemp event occurs when the battery on a
specified RAID controller has exceeded its temperature threshold.
Resolution
Battery temperature has exceeded 50 degrees Celsius. To resolve this error,

1. Verify that the controller is installed properly.
2. Verify that the server has adequate ventilation.
3. If the problem persists, the battery might have failed or the server might
require service. Contact your service representative.
Details
ibmSystemRaidControllerBatteryOvertemp
The battery has exceeded normal operating Warning
temperature: controller
where controller is the affected controller.
ibmSystemRaidControllerBatteryTempNormal
The ibmSystemRaidControllerBatteryTempNormal event occurs when the battery
on a specified RAID controller has a normal temperature.
Resolution

Details
ibmSystemRaidControllerBatteryTempNormal
The battery operating temperature is normal: Harmless
controller
ibmSystemRaidControllerFail
The ibmSystemRaidControllerFail event occurs when a specified RAID controller
fails.
Resolution
A hardware error occurred. To correct the problem, complete the following steps:
Details
ibmSystemRaidControllerFail Commands are not responding: controller Critical
ibmSystemRaidControllerFailover
The ibmSystemRaidControllerFailover event occurs when a specified RAID
controller fails over and the passive controller in the failover pairing is now active.
Resolution
Details
ibmSystemRaidControllerFailover A controller failover was detected: controller Critical
where controller is the controller that failed.
ibmSystemRaidControllerReplaced
The ibmSystemRaidControllerReplaced event occurs when a specified controller is
replaced in a RAID configuration.
Resolution

Details
ibmSystemRaidControllerReplaced A controller has been replaced in the system: controller Harmless
ibmSystemRaidCopyBackComplete
The ibmSystemRaidCopyBackComplete event occurs when a copy-back operation
is completed on a specified logical drive in a RAID configuration.
Resolution
Details
ibmSystemRaidCopyBackComplete Copy back complete: location. Harmless
where location is the affected controller and array.
ibmSystemRaidCopyBackDetected
The ibmSystemRaidCopyBackDetected event occurs when a copy-back operation is
in progress on a specified logical drive in a RAID configuration.
Resolution
Details
ibmSystemRaidCopyBackDetectedCopy back in progress: location. Source: Channel channel, Harmless
SCSI ID id. Target: Channel channel, SCSI ID id.
where
v location is the affected controller and array
v channel is the specified channel
v id is the specified SCSI ID
ibmSystemRaidCopyBackFail
The ibmSystemRaidCopyBackFail event occurs when a copy-back operation fails
on a specified logical drive in a RAID configuration.
Resolution

Details
ibmSystemRaidCopyBackFail Copy back failed: location [error] Critical
where location is the affected controller and array and

ibmSystemRaidDeadBattery
The ibmSystemRaidDeadBattery event occurs when the battery fails on a specified
controller.
Resolution
To resolve this problem, complete the following steps:

1. Verify that the battery on the battery-backup cache device is installed properly.
2. If the problem persists, replace the battery.
Details
ibmSystemRaidDeadBattery The battery-backup cache device needs a new battery: Critical
controller
ibmSystemRaidDeadBatteryCache
The ibmSystemRaidDeadBatteryCache event occurs when the battery-backup cache
fails on a specified controller.
Resolution
The battery-backup cache device is installed improperly or is defective. To resolve

this error, complete the following steps:
1. Verify that the battery-backup cache device is installed properly.
2. If the battery-backup cache device is installed properly but is defective, contact
your service representative.
Details
ibmSystemRaidDeadBatteryCache The battery-backup cache device is defective: controller. Critical
Error code: error
where controller is the affected controller and error is

the error code.
ibmSystemRaidDecompressionComplete
The ibmSystemRaidDecompressionComplete event occurs when a RAID
decompression operation is completed on a specified logical drive in a RAID
configuration.
Resolution

Details
ibmSystemRaidDecompressionComplete
Decompression complete: drive. Harmless
ibmSystemRaidDecompressionDetected
The ibmSystemRaidDecompressionComplete event occurs when a RAID
decompression operation is in progress on a specified logical drive in a RAID
configuration.
Resolution
Details
ibmSystemRaidDecompressionDetected
Decompressing: drive. Harmless
ibmSystemRaidDecompressionFail
The ibmSystemRaidDecompressionFail event occurs when a RAID decompression
Resolution
Details
ibmSystemRaidDecompressionFail Decompression failed: drive [error] Critical

error code.
ibmSystemRaidDefunctDrive
The ibmSystemRaidDefunctDrive event occurs when a specified hard disk drive
fails in a RAID configuration.
Resolution
steps:

representative.
Details
ibmSystemRaidDefunctDrive Defunct drive: location. Critical
where location is the affected controller and port.
ibmSystemRaidDefunctDriveFRU
The ibmSystemRaidDefunctDriveFRU event occurs when a specified hard disk
drive with the provided field-replaceable unit (FRU) number fails in a RAID
configuration.
Resolution
steps:
representative.
Details
ibmSystemRaidDefunctDriveFRU Defunct drive: location (FRU Part # FRU). Critical
where location is the affected controller and port and

FRU is the FRU number of the hard disk drive.
ibmSystemRaidDefunctReplaced
The ibmSystemRaidDefunctReplaced event occurs when a specified defunct hard
disk drive has been set to the hot-spare state in a RAID configuration.
Resolution
Details
ibmSystemRaidDefunctReplaced Defunct drive: location (error). Harmless
where location is the affected controller and port and

ibmSystemRaidDriveAdded
The ibmSystemRaidDriveAdded event occurs when a specified hard disk drive is
added to a RAID configuration.

Resolution
Details
ibmSystemRaidDriveAdded Physical drive added: location Harmless
ibmSystemRaidDriveClearComplete
The ibmSystemRaidDriveClearComplete event occurs when a RAID clear operation
is completed on a specified hard disk drive in a RAID configuration.
Resolution
Details
ibmSystemRaidDriveClearCompleteClear complete: drive. Harmless
ibmSystemRaidDriveClearDetected
The ibmSystemRaidDriveClearDetected event occurs when a RAID clear operation
is in progress on a specified hard disk drive in a RAID configuration.
Resolution
Details
ibmSystemRaidDriveClearDetected Clearing: drive. Harmless
ibmSystemRaidDriveClearFail
The ibmSystemRaidDriveClearFail event occurs when a RAID clear operation fails
on a specified hard disk drive in a RAID configuration.
Resolution
5. If the command still fails, replace the specified drive.

Details
ibmSystemRaidDriveClearFail Clear failed: drive [error] Critical
where drive is the affected hard disk drive and error is

the error code.
ibmSystemRaidDriveRemoved
The ibmSystemRaidDriveRemoved event occurs when a specified hard disk drive
is removed from a RAID configuration.
Resolution
Details
ibmSystemRaidDriveRemoved Physical drive removed: location. Harmless
ibmSystemRaidDriveVerifyComplete
The ibmSystemRaidDriveVerifyComplete event occurs when a RAID verify
operation is completed on a specified hard disk drive in a RAID configuration.
Resolution
Details
ibmSystemRaidDriveVerifyCompleteVerify complete: drive. Harmless
ibmSystemRaidDriveVerifyDetected
The ibmSystemRaidDriveVerifyDetected event occurs when a RAID verify
operation is in progress on a specified hard disk drive in a RAID configuration.
Resolution
Details
ibmSystemRaidDriveVerifyDetected Verifying: drive. Harmless

ibmSystemRaidDriveVerifyFail
The ibmSystemRaidDriveVerifyFail event occurs when a RAID verify operation
fails on a specified hard disk drive in a RAID configuration.
Resolution
following steps:
Details
ibmSystemRaidDriveVerifyFail Verify failed: drive. Critical
ibmSystemRaidEnclosureFail
The ibmSystemRaidEnclosureFail event occurs when an enclosure has failed on a
specified controller and channel in a RAID configuration.
Resolution
Details
ibmSystemRaidEnclosureFail Enclosure device is not responding: location Critical
where location is the controller and channel that the

ibmSystemRaidEnclosureFanOK
The ibmSystemRaidEnclosureFanOK event occurs when a specified enclosure fan is
functioning correctly on a specified controller and channel in a RAID
configuration.

Resolution
Details
ibmSystemRaidEnclosureFanOK Enclosure fan fan is now operational: location Harmless
where fan is the affected fan and location is the

controller and channel that the affected enclosure is
attached to.
ibmSystemRaidEnclosureOK
The ibmSystemRaidEnclosureOK event occurs when an enclosure is functioning
correctly on a specified controller and channel in a RAID configuration.
Resolution
Details
ibmSystemRaidEnclosureOK Enclosure device is responding: location Harmless
where location is the controller and channel that the

ibmSystemRaidExpansionComplete
The ibmSystemRaidExpansionComplete event occurs when a RAID expansion
Resolution
Details
ibmSystemRaidExpansionComplete Expansion complete: drive. Harmless
ibmSystemRaidExpansionDetected
The ibmSystemRaidExpansionDetected event occurs when a RAID expansion
Resolution

Details
ibmSystemRaidExpansionDetected Expanding: drive. Harmless
ibmSystemRaidExpansionFail
The ibmSystemRaidExpansionFail event occurs when a RAID expansion operation
fails on a specified logical drive in a RAID configuration.
Resolution
Details
ibmSystemRaidExpansionFail Expansion failed: drive [error]. Critical

error code.
ibmSystemRaidFanFail
The ibmSystemRaidFanFail event occurs when a specified enclosure fan fails on a
Resolution
A hardware error occurred. Verify that the fan in the enclosure device is installed
properly. If it is, complete the following steps:
5. If the problem persists, replace the specified fan.
Details
ibmSystemRaidFanFail Enclosure fan fan is malfunctioning: location Critical
where fan is the affected fan and location is the controller and
channel that the affected enclosure is attached to.
ibmSystemRaidFanInstalled
The ibmSystemRaidFanInstalled event occurs when a specified enclosure fan is
installed on a specified controller and channel in a RAID configuration.
Resolution
Details
ibmSystemRaidFanInstalled Enclosure fan fan has been installed: location Harmless
where fan is the affected fan and location is the controller and
channel that the affected enclosure is attached to.
ibmSystemRaidFanRemoved
The ibmSystemRaidFanInstalled event occurs when a specified enclosure fan is
removed on a specified controller and channel in a RAID configuration.
Resolution
Details
ibmSystemRaidFanRemoved Enclosure fan fan has been removed: location Warning
where fan is the affected fan and location is the controller

and channel that the affected enclosure is attached to.
ibmSystemRaidFlashCopyComplete
The ibmSystemRaidFlashCopyComplete event occurs when a RAID FlashCopy
Resolution
Details
ibmSystemRaidFlashCopyComplete FlashCopy with backup complete: drive. Harmless
ibmSystemRaidFlashCopyDetected
The ibmSystemRaidFlashCopyDetected event occurs when a RAID FlashCopy
Resolution

Details
ibmSystemRaidFlashCopyDetected FlashCopy in progress: drive. Harmless
ibmSystemRaidFlashCopyFail
The ibmSystemRaidFlashCopyFail event occurs when a RAID FlashCopy operation
Resolution
logical drive might be offline. If the source logical drive is offline, replace the failed
hard disk drives and restore the data from tape backup. If the target logical drive
is offline, replace the failed hard disk drives. FlashCopy operations will not work
when the source or target logical drives are offline.
Details
ibmSystemRaidFlashCopyFailFlashCopy with backup failed: drive [error]. Critical
where drive is the affected logical drive and error is the error
code.
ibmSystemRaidInitComplete
The ibmSystemRaidInitComplete event occurs when a RAID initialization
Resolution
Details
ibmSystemRaidInitComplete Clear complete: drive. Harmless
ibmSystemRaidInitDetected
The ibmSystemRaidInitDetected event occurs when a RAID initialization operation
is in progress on a specified logical drive in a RAID configuration.

Resolution
Details
ibmSystemRaidInitDetected Clearing: drive. Harmless
ibmSystemRaidInitFail
The ibmSystemRaidInitFail event occurs when a RAID initialization operation fails
Resolution
A hardware error occurred. Verify that the specified logical drive is not offline. If
the logical drive is offline, replace the failed hard disk drives and restore the data
from tape backup. If the specified logical drive is not offline, complete the
following steps:
Details
ibmSystemRaidInitFail Initialize failed: drive. Critical
ibmSystemRaidLogicalDriveAdded
The ibmSystemRaidLogicalDriveAdded event occurs when a specified logical drive
is added in a RAID configuration.
Resolution
Details
ibmSystemRaidLogicalDriveAdded Added logical drive: drive. Size data. Harmless
where drive is the affected logical drive and data is the

size and RAID level of that logical drive.
ibmSystemRaidLogicalDriveBlocked
The ibmSystemRaidLogicalDriveBlocked event occurs when a specified logical
drive is in the blocked state.

Resolution
When the RAID controller performs a rebuild operation on an array, it reconstructs

the data that was stored in RAID level-1 and RAID level-5 logical drives. However,
the RAID controller cannot reconstruct the data that was stored in any RAID
level-0 logical drives in that array. The data in the RAID level-0 logical drives is
blocked when the RAID controller detects that the array is valid, but the data
might be damaged.
To resolve this error, unblock the logical drive after the rebuild is complete. Restore
the data from tape.
Details
ibmSystemRaidLogicalDriveBlockedLogical drive is blocked: drive. Critical
ibmSystemRaidLogicalDriveCritical
The ibmSystemRaidLogicalDriveCritical event occurs when a specified logical drive
is in the critical state.
Resolution

User's Reference.
Details
ibmSystemRaidLogicalDriveCritical Logical drive is critical: drive. Warning
ibmSystemRaidLogicalDriveCriticalPeriodic
The ibmSystemRaidLogicalDriveCriticalPeriodic event occurs when a periodic scan
detects that one or more logical drives are in a critical state.
Resolution


User's Reference.
Details
ibmSystemRaidLogicalDriveCriticalPeriodic
Periodic scan found one or more critical logical Warning
drives: drive. Repair as soon as possible to avoid
data loss.
ibmSystemRaidLogicalDriveOffLine
The ibmSystemRaidLogicalDriveOffLine event occurs when a specified logical
drive is in the offline state.
Resolution
A hardware error occurred. Contact your service representative.
Details
ibmSystemRaidLogicalDriveOffLine Logical drive is offline: drive. Critical
ibmSystemRaidLogicalDriveOK
The ibmSystemRaidLogicalDriveOK event occurs when a specified logical drive is
Resolution
Details
ibmSystemRaidLogicalDriveOK Logical drive is normal: drive. Harmless
ibmSystemRaidLogicalDriveRemoved
The ibmSystemRaidLogicalDriveRemoved event occurs when a specified logical
drive has been removed from a RAID configuration.
Resolution

Details
ibmSystemRaidLogicalDriveRemoved
Deleted logical drive: drive. Harmless
ibmSystemRaidLogicalDriveUnblocked
The ibmSystemRaidLogicalDriveUnblocked event occurs when a specified logical
drive is in the unblocked state.
Resolution
Details
ibmSystemRaidLogicalDriveUnblocked
Unblocked logical drive: drive. Harmless
ibmSystemRaidMigrationComplete
The ibmSystemRaidMigrationComplete event occurs when a RAID logical-drive
migration is completed on a specified logical drive in a RAID configuration.
Resolution
Details
ibmSystemRaidMigrationComplete Migration complete: drive. Harmless
ibmSystemRaidMigrationDetected
The ibmSystemRaidMigrationDetected event occurs when a RAID logical-drive
migration is in progress on a specified logical drive in a RAID configuration.
Resolution
Details
ibmSystemRaidMigrationDetected Migrating: drive. Harmless
ibmSystemRaidMigrationFail
The ibmSystemRaidMigrationFail event occurs when a RAID logical-drive
migration fails on a specified logical drive in a RAID configuration.

Resolution
Details
ibmSystemRaidMigrationFailMigration failed: drive [error] Critical
code.
ibmSystemRaidNoControllers
The ibmSystemRaidNoControllers event occurs when no RAID controllers are
detected.
Resolution
Details
ibmSystemRaidNoControllersNo controllers were found in this system Harmless
ibmSystemRaidPFADrive
The ibmSystemRaidPFADrive event occurs when a Predictive Failure Analysis
(PFA) is detected on a specified hard disk drive in a RAID configuration.
Resolution
Details
ibmSystemRaidPFADrive PFA detected for drive: drive. Warning
ibmSystemRaidPFADriveFRU
The ibmSystemRaidPFADriveFRU event occurs when a Predictive Failure Analysis
(PFA) is detected on a specified hard disk drive with a specified field-replaceable
unit (FRU) number in a RAID configuration.
Resolution

Details
ibmSystemRaidPFADriveFRUPFA detected for drive: drive (FRU). Warning
where drive is the affected hard disk drive and FRU is the
FRU number of that drive.
ibmSystemRaidPollingFail
The ibmSystemRaidPollingFail event occurs when a specified controller fails to
respond to background polling commands.
Resolution
Details
ibmSystemRaidPollingFail Background polling commands are not responding: controller. Warning
Result codes: error
where controller is the affected controller and error is the

error code.
ibmSystemRaidPowerSupplyFail
The ibmSystemRaidPowerSupplyFail event occurs when the specified enclosure
power supply fails in a RAID configuration.
Resolution
A hardware error occurred. Verify that the power supply in the enclosure device is
installed properly. If it is, complete the following steps:
5. If the problem persists, replace the specified power supply.
Details
ibmSystemRaidPowerSupplyFail Enclosure power supply supply is malfunctioning: Critical
location
where supply is the affected power supply and location

is the controller and channel that the affected
enclosure is attached to.

ibmSystemRaidPowerSupplyInstalled
The ibmSystemRaidPowerSupplyInstalled event occurs when a specified enclosure
power supply is installed in a RAID configuration.
Resolution
Details
ibmSystemRaidPowerSupplyInstalledEnclosure power supply supply has been installed: Harmless
location

ibmSystemRaidPowerSupplyOK
The ibmSystemRaidPowerSupplyOK event occurs when a specified enclosure
power supply is functioning correctly in a RAID configuration.
Resolution
Details
ibmSystemRaidPowerSupplyOK Enclosure power supply supply is now operational: Harmless
location

ibmSystemRaidPowerSupplyRemoved
The ibmSystemRaidPowerSupplyRemoved event occurs when a specified enclosure
power supply is removed from a RAID configuration.
Resolution
Details
ibmSystemRaidPowerSupplyRemoved
Enclosure power supply supply has been removed: Warning
location

ibmSystemRaidRebuildComplete
The ibmSystemRaidRebuildComplete event occurs when a RAID rebuild operation
is completed on a specified logical drive in a RAID configuration.

Resolution
Details
ibmSystemRaidRebuildComplete Rebuild complete: drive. Harmless
ibmSystemRaidRebuildDetected
The ibmSystemRaidRebuildDetected event occurs when a RAID rebuild operation
is in progress on a specified logical drive in a RAID configuration.
Resolution
Details
ibmSystemRaidRebuildDetected Rebuilding: drive. Harmless
ibmSystemRaidRebuildFail
The ibmSystemRaidRebuildComplete event occurs when a RAID rebuild operation
Resolution
Details
ibmSystemRaidRebuildFail Rebuild failed: drive [error]. Critical
code.
ibmSystemRaidSyncComplete
The ibmSystemRaidSyncComplete event occurs when a RAID synchronization
Resolution

Details
ibmSystemRaidSyncCompleteSynchronize complete: drive. Harmless
ibmSystemRaidSyncDetected
The ibmSystemRaidSyncDetected event occurs when a RAID synchronization
Resolution
Details
ibmSystemRaidSyncDetectedSynchronizing: drive. Harmless
ibmSystemRaidSyncFail
The ibmSystemRaidSyncFail event occurs when a RAID synchronization operation
Resolution
If the specified logical drive is not offline or critical, complete the following steps:
Details
ibmSystemRaidSyncFail Synchronize failed: drive [error] Critical
code.
ibmSystemRaidTempFail
The ibmSystemRaidTempFail event occurs when an enclosure temperature exceeds
a normal range on a specified controller in a RAID configuration.

Resolution
A hardware error occurred. Verify that the fans in the enclosure device are installed
properly and working. If they are, complete the following steps:
Details
ibmSystemRaidTempFail Enclosure temperature is out of the normal range: location Critical
where location is the controller and channel that the affected

ibmSystemRaidTempOK
The ibmSystemRaidTempOK event occurs when an enclosure temperature is within
a normal range on a specified controller in a RAID configuration.
Resolution
Details
ibmSystemRaidTempOK Enclosure temperature is in the normal range: location Harmless
where location is the controller and channel that the affected

ibmSystemRaidTestEvent
The ibmSystemRaidTestEvent event occurs when a RAID test event is generated.
Resolution
Details
ibmSystemRaidTestEvent This is a test event. Harmless
ibmSystemRaidUnsupportedDrive
The ibmSystemRaidUnsupportedDrive event occurs when an unsupported hard
disk drive is detected in a RAID configuration.
Resolution
Replace the specified hard disk drive with a hard disk drive model that is
supported by IBM RAID controllers.

Details
ibmSystemRaidUnsupportedDrive Possible non-warranted physical drive found: drive. Warning
ibmSystemRaidVersionMismatch
The ibmSystemRaidVersionMismatch event occurs when the versions of the BIOS,
firmware, and driver for a specified RAID controller do not match.
Resolution
Upgrade to the latest version of the RAID BIOS, firmware, and device driver.
Details
ibmSystemRaidVersionMismatch Version mismatch detected: controller. The BIOS Warning
(version version), Firmware (version version), and
Driver (version version) are not a matched set and are
not compatible.
where controller is the affected controller and version is

the version of the affected RAID code.

Chapter 2. IBM Systems Director tasks, software, and
operating system events
This section describes events that are generated by IBM Systems Director tasks,
other software, or operating systems.
Director > Director Agent

The Director Agent event occurs when a change in the state of Common Agent is
detected. For detailed event types, expand the Director Agent node in the Event
Filter Builder tree.
Important: When you create resource monitors, their events are displayed under a
second copy of the Director > Director Agent node.
Details
The Director > Director Agent event types use a standard set of extended details:
v Duration
v Monitor Resource
v Threshold Name
Some Director > Director Agent event types have additional extended details.
These event types list the details in the Additional extended details column.
If you select the Director Agent check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the Director
Agent subtree. You can choose to select specific event types that are displayed
under the Director Agent node in the Event Filter Builder tree. The event filter will
Director Not applicable Not Not None
Agent applicableapplicable
Director > Director Agent > Process Monitors

The Process Monitors events occur when an application process that you are
monitoring has failed; a scheduled job has been completed successfully or with
errors; or a target system has completed a job successfully or with errors.
Details
Process Monitor event types are published and then displayed dynamically in the
Event Filter Builder window when you:
v Configure a process monitor and specify event generation in the Process
Monitors window.
v Schedule a job and specify event generation on the Options page in the Run
window.
v Duration

v Monitor Resource
v Threshold Name
Process Note: The event text Varies Alert v Actual Value is the current reading of
Monitors varies depending on the depending the monitored resource at the time the
monitor that you create. on the event is sent.
threshold
set for v Threshold Value is the configured value
the you assigned in the Above or Equal
monitor. or Below or Equal field of the
Threshold Configuration window.
Director > Director Agent > Process Monitors > Process Alert
The Process Alert events occur when an application process that you are
monitoring has started, stopped, or failed to start; a scheduled job has been
completed successfully or with errors; or a target system has completed a job
successfully or with errors.
Details
v Duration
v Monitor Resource
v Threshold Name
If you select the Process Alert check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Process Alert
subtree, including the dynamically created events that you selected to generate in
the Scheduler or Process Monitor task.
Process Alert Note: The event text Varies Alert v Actual Value is the current reading of
varies depending on the depending the monitored resource at the time the
threshold
You can choose to select specific event types that are displayed under the Process
Alert node in the Event Filter Builder tree. The event filter will process only the

Additional extended
Process Process Failed to Start → Critical Alert v Actual Value is the
Failed to Monitor 'PMON:process_name current reading of the
Start Fail' Changed:'process_name has monitored resource at
changed values for 0:00:00. the time the event is
New value reported is "1". sent.
where process_name is the name v Threshold Value is the
of the affected process. configured value you
assigned in the Above
or Equal or Below or
Equal field of the
Threshold
Configuration window.
Process Process Start → Monitor Informational Alert v Actual Value is the
Started 'PMON:process_name Start' current reading of the
Changed:'process_name has monitored resource at
Equal field of the
Threshold
Process Process Terminated → Monitor Warning Alert v Actual Value is the
Terminated 'PMON:process_name Stop' current reading of the
Changed:'process_name has monitored resource at
Equal field of the
Threshold
Director > Director Agent > Resource Monitors

The Resource Monitors events occur when the state of a resource that you are
monitoring has changed in respect to the settings you selected when creating the
resource monitor; a scheduled job has been completed successfully or with errors;
or a target system has completed a job successfully or with errors.
Details
Resource Monitor event types are published and then displayed dynamically in the
Event Filter Builder window when you:
v Configure a resource monitor and specify event generation in the System
Threshold window.
v Schedule a job and specify event generation on the Options page in the Run
window.
v Duration
v Monitor Resource
v Threshold Name
Chapter 2. IBM Systems Director tasks, software, and operating system events 211
Resource Note: The event text Varies Alert v Actual Value is the current reading of
Monitors varies depending on the depending the monitored resource at the time the
threshold
Director > Scheduler

The Scheduler events occur when a scheduled job succeeds or fails; or a scheduled
job is completed or fails on a target system. For detailed event types, expand the
Scheduler node in the Event Filter Builder tree.
Details
The Director > Scheduler > System event types use a standard set of extended
details:
v Client Status
v Job Activation Time
v Job Current Task ID
v Job Current Subtask ID
v Job Current Task Name
v Job ID
If you select the Scheduler check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Scheduler subtree.
Scheduler node in the Event Filter Builder tree. The event filter will process only
Scheduler Note: The event text Not Not None
varies depending on the applicableapplicable
job that you schedule.
Director > Scheduler > Job

The Job events occur when a scheduled job is successful or if it fails. For detailed
event types, expand the Job node in the Event Filter Builder tree.
Details
The Director > Scheduler > Job event types use a standard set of extended details:
v Job ID
If you select the Job check box in the Event Filter Builder tree, the event filter will
process all of the event types that are specified in the Job subtree. You can choose
to select specific event types that are displayed under the Job node in the Event
Filter Builder tree. The event filter will process only the event types that you select.

Job Not applicable Not Not None
Director > Scheduler > Job > Error

The Error events occur when a scheduled job has failed.
Details
If you select the Error check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the Error subtree.
Error Not applicable Not Not None
You can choose to select specific event types that are displayed under the Error
Note: The Note: The name of the Warning Alert None
name of the scheduled job.
scheduled
job.
Director > Scheduler > Job > Success

The Success events occur when a scheduled job has succeeded.
Details
If you select the Success check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the Success subtree.
Success Not applicable Not Not None
You can choose to select specific event types that are displayed under the Success
Note: The Note: The name of the Informational Resolution None
scheduled
job.
Director > Scheduler > System

The System events occur when a scheduled job is completed or fails on a target
system. For detailed event types, expand the System node in the Event Filter
Builder tree.
Details
The Director > Scheduler > System event types use a standard set of extended
details:
v Client Status
v Job Current Task ID
v Job Current Subtask ID
v Job Current Task Name
v Job ID
will process all of the event types that are specified in the System subtree. You can
choose to select specific event types that are displayed under the System node in
the Event Filter Builder tree. The event filter will process only the event types that
you select.
System Not applicable Not Not None
Director > Scheduler > System > Error

The Error events occur when a scheduled job fails on a target system.
Details
If you select the Error check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the Error subtree.
Error Not applicable Not Not None
You can choose to select specific event types that are displayed under the Error
Note: The Note: The name of the Warning Alert None
scheduled
job.
Director > Scheduler > System > Success

The Success events occur when a scheduled job is completed on a target system.
Details
If you select the Success check box in the Event Filter Builder tree, the event filter
will process all of the event types that are specified in the Success subtree.
Success Not applicable Not Not None

You can choose to select specific event types that are displayed under the Success
Note: The Note: The name of the InformationalAlert None
scheduled
job.
IBM Systems Director Program events

The Director events are generated when a change in the state is detected for IBM
Systems Director Server, Common Agent, a plug-in, or monitored resources and
application processes. For detailed event types, expand the IBM Systems Director
Program node in the Event Filter Builder tree.
These events are processed by the Log All Events event automation plan. The Log
All Events event automation plan adds the event to the IBM Systems Director
event log, and can be modified to include additional event actions for these event
types. In contrast, other event types on which you want to filter on must be added
to an event automation plan manually.
Agent events
These events are generated when Common Agent 6.1 or IBM Director Agent 5.20
starts or stops on a managed system.
Condition Condition
type value Severity Category Event text Extended details
OperationalStarted Informational
Alert The core agent has started. None
Condition
OperationalStopped Informational
Alert The core agent has stopped. None
Condition
Automation Event Actions events

These events are generated by the automation manager plug-in from IBM Systems
Director Server.
Alarm event
These events are generated when an event automation plan is triggered that
includes the “Timed alarm that generates an event” event action. When you
customize this event action, you create a customized event that is generated after a
timer has expired.
Note: This event replaces the Director > Alarm Triggered event in IBM Director
5.20.
Condition Condition
type value Severity Category Event text Extended details
OperationalInvoke Varies Alert Note: The event text varies None
Condition depending depending on how you
on how customize the event.
you
customize
the event.
Note: The event type varies depending on how you customize the event.
Security
The Security events are generated by IBM Systems Director Server when a change
in the state of a user accessing IBM Systems Director Server is detected.
Agent condition type

This event is generated when you discover and attempt to access an instance of
Common Agent that is managed by an agent manager that is not registered with
IBM Systems Director Server.
Condition
value Severity Category Event text Extended details
Access Informational Alert Agent accessInfo is managed by an agent None
Requested manager which is either already
registered to this server and not active or
not registered to this server at all. Failing
request access.
where accessInfo identifies the agent.
Logging On condition type

These events are generated when a user fails to log on to IBM Systems Director
Server. Failure to log on can include providing an incorrect user ID or password,
using a user ID that has been disabled, or attempting to log on using a user ID
that is already logged on.
The Director > Console event types use a standard set of extended details:
v Address
v User ID
Some Director > Console event types have additional extended details. These event
Condition Additional extended Pre-6.1 event
value Severity Category Event text attributes type name
Disabled Warning Alert Logon to server by User ID None Director >
User ID User ID from Address failed Console >
(Disabled User ID) Logon Failure
> Disabled
Where User ID and Address User ID
are the values provided by
the extended details.

Condition Additional extended Pre-6.1 event
value Severity Category Event text attributes type name
Expired Warning Alert Logon to server by User ID None Director >
Password User ID from Address failed Console >
(Expired Password) Logon Failure
> Expired
Where User ID and Address Password
Failure Warning Alert None
Incorrect Warning Alert Logon to server by User ID None Director >
Password User ID from Address failed Console >
(Bad Password) Logon Failure
> Bad
Where User ID and Address Password
Incorrect Warning Alert Logon to server by User ID None Director >
User ID User ID from Address failed Console >
(Bad User ID) Logon Failure
> Bad User
Where User ID and Address ID
User ID Warning Alert None
Locked
Out
User ID Session condition type

These events are generated when an IBM Systems Director user ID logs on to or
off from IBM Systems Director Server.
The Director > Console event types use a standard set of extended details:
v Address
v User ID
Some Director > Console event types have additional extended details. These event
Condition Pre-6.1 event
value Severity Category Event text Extended details type name
User ID InformationalAlert User logged off. v Description is the long Director >
Logged name of the user ID. For Console >
Off example, if a user ID is User Logoff
“maddie”, then the
description is
“systemname\\Madison
Lucas” where systemname
is the name of the system.
v Locale is the locale of the
system where IBM Systems
Director Web interface was
started.
v User Name is the user
name of the user who
logged off.
Condition Pre-6.1 event
value Severity Category Event text Extended details type name
User ID InformationalAlert User logged on. v Description is the long Director >
Logged name of the user ID. For Console >
On example, if a user ID is User Logon
“maddie”, then the
description is
“systemname\\Madison
Lucas” where systemname
is the name of the system.
v Locale is the locale of the
system where IBM Systems
Director Web interface was
started.
v User Name is the user
name of the user who
logged on.
Status events
These events are generated by the status manager plug-in from IBM Systems
Director Server.
Status Type condition type
These events are generated when the initial status of a resource has been gathered.
Initial status can be gathered in the following situations:
v When the resource is initially discovered and access is granted
v When the resource is restarted
v Any time the access state of the resource is changed to Unlock
Condition
Initial Varies Alert Initial Status Gathered None
Status depending
on the
problem
status
associated
with the
resource.
System Configuration events

These events are generated by the configuration manager plug-in from IBM
Systems Director Server.
Note: These events replace the Configuration Manager events in IBM Director 5.20.
Configuration Plan condition type
These events are generated when a configuration plan is deployed for a system
configuration.

Condition
Deployed Informational Alert The configuration plan has v planID is the identifier of
been fully deployed. the affected plan.
v resourceID is the identifier
of the affected target
resource.
v planName is the name
associated with the affected
plan.
Deployed Warning Alert The configuration plan has v planID is the identifier of
been partially deployed. the affected plan.
resource.
plan.
Deployed Critical Alert The configuration plan v planID is the identifier of
fully failed to be deployed. the affected plan.
resource.
plan.
Configuration Template condition type
These events are generated when a configuration template is deployed for a system
configuration.
Condition
Deployed Critical Alert The target for the v templateID is the identifier
configuration template of the affected template.
is offline.
resource.
v deviceID is the identifier of
the affected target device.
v templateName is the name
template.
Deployed Critical Alert The target for the v templateID is the identifier
configuration template of the affected template.
is locked.
resource.
template.
Condition
Deployed Critical Alert Configuration Manager v templateID is the identifier
general failure: see the of the affected template.
TWGRas.log file.
resource.
template.
Deployed Critical Alert The configuration v templateID is the identifier
template failed to be of the affected template.
deployed.
resource.
template.
Deployed Informational Alert The configuration v templateID is the identifier
template has been fully of the affected template.
deployed.
resource.
template.
Deployed Informational Alert An empty configuration v templateID is the identifier
was applied. of the affected template.
resource.
template.
Updates
The Updates events are generated by the update manager plug-in.

Compliance Task State condition type
These events are generated by different states of the compliance task.
Condition
value Severity Category Event text Extended attributes
Check Informational Alert Update Compliance Policy v Edit Compliance Policy is
Modified Changed a list of updates or
Note: This event is generated update groups that were
when a compliance policy is added to or edited in a
edited or removed by a user. system or system group
compliance policy.
Compliance is automatically
v Remove Compliance Policy
reevaluated when a policy is
is a list of updates or
created or removed from a
update groups that were
system or system group.
removed from a system
or system group
If the compliance policy is on a compliance policy.
system group, an event is
generated for each system in the
group, that is, the group
members are the source for their
respective event and the event
details are the same for each
event within that system group.
Task Failed Warning Alert Compliance Failed v Compliance Relationship
Note: This event is generated if Check Failed indicates
the update Compliance task the managed resource
failed for a compliance flow. which is the system
processed by a
relationship platform
extension. The values
are the updates that
failed the check.
v Compliance Failed
indicates the managed
resource which is the
system that failed the
policy validation.
v Compliance Failed
indicates general failure
in the task processing
has occurred. The
managed resource that
generates this event is
the IBM Systems
Director management
server. The detail
provided is the localized
message from an
exception.
Installation condition type

These events are generated by the installation of an update. The managed resource
that generates these events is the target system on which the installation is
performed.
Condition
Failed Warning Alert Install Failed Updates is an array of
Note: This event is generated names of the updates that
when the Install task fails. The have failed to install.
failure can be in any stage of
the installation: download,
distribute or install.
Successful Informational Alert Install Successful Updates is an array of
after an Install task completes have installed successfully.
successfully.
Uninstall condition type

These events are generated by the uninstall of an update. The managed resource
that generates these events is the target system on which the uninstallation is
performed.
Condition
value Severity Category Event text Extended attributes
Failed Warning Alert Uninstall Failed Updates is an array of
when the Uninstall task fails. have failed to uninstall.
Successful Informational Alert Uninstall Successful Updates is an array of
after the Uninstall task have uninstalled
completes successfully. successfully.
Update Operation State condition type

These events are generated by different states of the update operation. The
managed resource that generates these events is the IBM Systems Director
management server.
Condition
Check for Warning Alert Check for Updates Failed Check for Updates Failed
Updates Note: This event is generated provides a localized
Failed when the Check for Updates exception message that
task fails because no updates are describes the failure.
available.
Check for Warning Alert Check for Updates Failed Updates is an array of
Updates Note: This event is generated names of the updates that
Failed when the Check for Updates have failed to download, if
task fails, for example, when it is available.
unable to connect to the
download provider.
Distribute Warning Alert Installation Staging of Updates Updates is an array of
Updates Failed names of the updates that
Failed Note: This event is generated have failed to be
when the Distribute task fails. distributed.
Download Warning Alert Download Updates Failed Updates is an array of
Updates Note: This event is generated names of the updates that
Failed when the Download task fails. have failed to download.

Condition
New Informational Alert New Updates Found Severity indicates the
Updates Note: This event is generated severity of the most critical
Found when metadata for a new update.
update is found. If, in the Check
for Updates task, multiple new
updates are found, the event is
generated only once.
Virtualization events
The Virtualization events are generated by the virtualization manager plug-in.
Using your Web browser Find in page feature, use the following table to lookup
events by their IBM Director 5.20 name. The link provided displays the version
5.20 event documentation that still applies to the new version 6.1 event.
Table 3. Virtualization event cross reference
IBM Systems Director 6.1 event names
IBM Director 5.20 event names view this event in the Event Filter Builder tree.
No legacy events are mapped to this USMi Event Managed Resource > Managed System Resource >
Type. Logical Resource > System > Administration
Domain > Farm > Virtual Farm Events > Virtual
farm created
This event does not apply to VMware

VirtualCenter.
farm deleted
This event is not supported.

Domain > Farm > Virtual Farm Events > Host
added to virtual farm

VirtualCenter.
Domain > Farm > Virtual Farm Events > Host
removed from virtual farm

VirtualCenter.
farm renamed

VirtualCenter.
Table 3. Virtualization event cross reference (continued)
Domain > Farm > Relocation Manager Events >
Virtual server relocation started
This event applies to hosts managed by Hardware

Management Console or Integrated Virtualization
Manager.
Virtual Server relocation failed

Manager.
Virtual server relocation complete

Manager.
v CIM > Director Agent Events > VMware > Managed Resource > Managed System Resource >
Alert Indication Logical Resource > System > Computer System >
Server > ESXi Operational Condition >
v CIM > Director Agent Events > Ipmi > Alert
Indication
This event does not exist in IBM Director 5.20. IBM Systems Director Program > Virtualization >
Resource Monitor > CPU Utilization % > Critical -
High
Resource Monitor > CPU Utilization % > Warning
- High
Resource Monitor > CPU Utilization % > Normal
Resource Monitor > CPU Utilization % > Critical -
Low
Resource Monitor > CPU Utilization % > Warning
- Low
Resource Monitor > Memory (MB) > Critical -
High
Resource Monitor > Memory (MB) > Warning -
High
Resource Monitor > Memory (MB) > Normal
Resource Monitor > Memory (MB) > Critical -
Low
Resource Monitor > Memory (MB) > Warning -
Low

Resource Monitor > Processors > Critical - High
Resource Monitor > Processors > Warning - High
Resource Monitor > Processors > Normal
Resource Monitor > Processors > Critical - Low
Resource Monitor > Processors > Warning - Low
Resource Monitor > Entitled Processing Units >
Critical - High
Warning - High
Normal
Critical - Low
Warning - Low
This event does not exist in IBM Director 5.20. Managed Resource > Managed System Resource >
Server > Virtualization Services > Unavailable
VSM > Virtual Server > Task Failed Managed Resource > Managed System Resource >
Server > Virtualization Services > Failed
VSM > Virtual Server > State > Powered On Managed Resource > Managed System Resource >
Server > Power > A virtual server has been
powered on.
VSM > Virtual Server > State > Powered Off Managed Resource > Managed System Resource >
powered off.
VSM > Virtual Server > State > Suspended Managed Resource > Managed System Resource >
suspended.
VSM > Virtual Server > State > Resumed Managed Resource > Managed System Resource >
resumed.
VSM > Host > Task Failed. Managed Resource > Managed System Resource >
Server > Power > CmdFailed
VSM > Virtual Server > Created Managed Resource > Managed System Resource >
Server > Life Cycle > A virtual server was created.
VSM > Virtual Server > Deleted Managed Resource > Managed System Resource >
Server > Life Cycle > A virtual server was deleted.
VSM > Virtual Server > Relocation > Started Managed Resource > Managed System Resource >
Server > Relocation > Virtual server relocation has
been initiated for {0}.
This event applies to the following host

environments: VMware VirtualCenter, VMware
ESX Server, Microsoft Virtual Server.
VSM > Virtual Server > Relocation > Completed Managed Resource > Managed System Resource >
Server > Relocation > Virtual server relocation has
completed.
This event applies to the following host

environments: VMware VirtualCenter, VMware
ESX Server, Microsoft Virtual Server.
VSM > Virtual Server > Relocation > Failed Managed Resource > Managed System Resource >
Server > Relocation > Virtual server relocation
failed for {0}. Failure cause: {1}.
This event does not exist in IBM Director 5.20. Managed Resource > Settings > Resource
Allocation Settings > Changes > Changed
VSM > Host > Started Managed Resource > Managed System Resource >
Logical Resource > Service > Virtualization
Services > The hypervisor service on this host has
been started.
VSM > Host > Stopped Managed Resource > Managed System Resource >
Services > The hypervisor service on this host has
been stopped.
This event does not exist in IBM Director 5.20. Managed Resource > Managed System Resource >
Services > The host is not available.
VSM > Host > Maintenance Managed Resource > Managed System Resource >
Services > Host Maintenance
Services > The command did not complete
successfully.
VSM > Virtual Server > State > Reset Managed Resource > Managed System Resource >
restarted.
VSM > Virtual Server > State > Pending Managed Resource > Managed System Resource >
Server > Power > A virtual server has a question
pending.
Server > Power > The command did not complete
successfully.

Server > Life Cycle > The command did not
complete successfully.
Server > Relocation > The command did not
complete successfully.
VSM > Agent Extension > Status Change Managed Resource > Managed System Resource >
Logical Resource > Service Access Point > Remote
Service Access Point > Virtualization Services >
IBM Systems Director Virtualization Manager
Agent has changed status.
Logical Resource > Service Access Point > Remote
Service Access Point > Virtualization Services >
The command did not complete successfully.
VSM > Virtual Farm > Created Managed Resource > Managed System Resource >
Logical Resource > System > Administration
Domain > Farm > Life Cycle > A virtual farm has
been created.
This event applies to VMware VirtualCenter only.

VSM > Virtual Farm > Deleted Managed Resource > Managed System Resource >
been deleted.

VSM > Virtual Farm > Host Added Managed Resource > Managed System Resource >
Domain > Farm > Life Cycle > A host was added
to a virtual farm.

VSM > Virtual Farm > Host Removed Managed Resource > Managed System Resource >
Domain > Farm > Life Cycle > A host was
removed from a virtual farm.

VSM > Virtual Farm > Renamed Managed Resource > Managed System Resource >
been renamed.

Domain > Farm > Life Cycle > The command did
not complete successfully.

VSM > Virtual Server > Attribute Changed Managed Resource > Settings > Resource
Allocation Settings > Changes > Machine
Attribute
VSM > Virtual Server > Task Failed Managed Resource > Settings > Resource
Allocation Settings > Changes > The command
did not complete successfully.
Host events
This topic defines the host events provided by virtualization manager.
The following table defines the host events that are provided by virtualization
manager.
Table 4. Host events
Event Additional Target resource for Event trigger Description
subcategory event event automation
subcategory plan
Agent Status Change Depends on the Virtualization The following scenarios are examples of such
Extension virtualization manager events:
manager subagent: subagent v Virtualization manager subagent is not
v Platform detects a running or the virtualization application is
manager status change not installed.
(virtualization for the
v Virtualization manager subagent and the
manager platform
virtualization application are installed, but
subagent for manager or
they are not communicating properly with
VMware the host.
each other.
VirtualCenter)
v The platform manager or host is ready for
v Host use. For platform managers, this means that
(virtualization IBM Systems Director has authenticated with
manager VMware VirtualCenter server. For hosts, this
subagents for means that Microsoft Virtual Server services
VMware ESX are started.
Server and
v (VMware VirtualCenter only) The platform
Microsoft
manager requires a connection.
Virtual Server)
Note: When encryption is enabled on a
managed system, this event is not logged after
the IBM Systems Director service is restarted.
This issue affects all event action plans that
rely on events for agent status. In this scenario,
the expected results will not occur.
Host Started Host Virtualization (Microsoft Virtual Server only) Microsoft
manager Virtual Server services are started on a host.
subagent
detects that
Microsoft
Virtual Server
has started on
a host.

Table 4. Host events (continued)
Event Additional Target resource for Event trigger Description
subcategory plan
Stopped Host Virtualization (Microsoft Virtual Server only) Microsoft
manager Virtual Server services are stopped on a host.
subagent
detects that
Microsoft
Virtual Server
has been
stopped on a
host.
Platform Manager events

This topic defines the platform manager events provided by virtualization
manager.
The following table defines the platform manager events that are provided by
virtualization manager.
Table 5. Platform manager events
Event Additional Target resource Event trigger Description
subcategory event for event
subcategory automation plan
Agent Status Depends on the Virtualization The following scenarios are examples of such
Extension Change virtualization manager events:
manager subagent: subagent v Virtualization manager subagent is not
v Platform detects a status running or the virtualization application is
manager change for the not installed.
(virtualization platform
v Virtualization manager subagent and the
manager manager or the
virtualization application are installed, but
subagent for host.
they are not communicating properly with
VMware each other.
VirtualCenter)
v The platform manager or host is ready for
v Host use. For platform managers, this means that
(virtualization IBM Systems Director has authenticated with
manager VMware VirtualCenter server or VMware
subagents for ESX Server. For hosts, this means that
VMware ESX Microsoft Virtual Server services are started.
Server and
v (VMware VirtualCenter only) The platform
Microsoft
manager requires a connection.
Virtual Server)
Note: When encryption is enabled on a
managed system, this event is not logged after
the IBM Systems Director service is restarted.
This issue affects all event action plans that rely
on events for agent status. In this scenario, the
expected results will not occur.
Virtual Server events

This topic defines the virtual server events provided by virtualization manager.
The following table defines the virtual server events that are provided by
Table 6. Virtual server events
Event Additional Target object Event trigger Description
subcategory automation
plan
Attribute Virtual server The value of the Virtualization manager has changed the value of
Changed CPU Count or the attributes for the number of CPUs or the
the Memory memory size for a virtual server. Virtualization
Size attribute manager updates this attribute information in
for a virtual both IBM Systems Director and the associated
server is virtualization application.
changed.
Created Virtual server A virtual server IBM Systems Director displays the virtual server
is created. in the Web interface.
Deleted Virtual server A virtual server IBM Systems Director no longer displays the
is deleted. virtual server in the Web interface.
Relocation Started Virtual server A virtual server Virtualization manager has started the relocation
has started of a virtual server from one host to another.
relocation from
one host to
another.
Completed Virtual server A virtual server Virtualization manager has completed the
has completed relocation of a virtual server from one host to
relocation from another.
one host to
another.
State Pending Virtual server The state of a The associated virtualization application requires
virtual server the user to answer a question before the state
has changed to change will continue. To resolve a pending state,
pending. use the Start Vendor Software task to start the
management interface for the virtual server; then,
resolve any open questions.
Powered off Virtual server The state of a A virtual server is turned off.
virtual server
has changed to
turned off.
Powered on Virtual server The state of a A virtual server is turned on.
virtual server
has changed to
turned on.
Reset Virtual server The state of a A virtual server is restarted.
virtual server
has changed to
restarted.
Resumed Virtual server The state of a A virtual server resumes operations after being
virtual server in the suspended state.
has changed
from suspended
to turned on.
Suspended Virtual server The state of a A virtual server is suspended.
virtual server
has changed to
suspended.

Table 6. Virtual server events (continued)
Event Additional Target object Event trigger Description
subcategory automation
plan
Task Failed Virtual server An operation on A power or relocation operation failed for a
a virtual server virtual server.
has failed to
complete
successfully.
Virtual Farm events

This topic defines the virtual server farm events provided by virtualization
manager.
The following table defines the virtual farm events that are provided by
Table 7. Virtual farm events
Event Additional Target object for Event trigger Description
subcategory plan
Virtual Farm Created Virtual Farm Virtualization (VMware VirtualCenter only) IBM Systems
manager Director displays a virtual farm in the Web
subagent for interface.
VMware
VirtualCenter
detects that a
virtual farm is
created.
Deleted Virtual Farm Virtualization (VMware VirtualCenter only) IBM Systems
manager Director no longer displays a virtual farm in the
subagent for Web interface.
VMware
VirtualCenter
detects that a
virtual farm is
deleted.
Host Added Virtual Farm Virtualization IBM Systems Director displays a host nested
manager beneath the virtual farm.
subagent Note: (VMware VirtualCenter only) When this
detects that a event occurs, a host object is displayed only when
host is added the managed system that represents the host has
to a virtual already been discovered by IBM Systems Director.
farm.
Host Virtual Farm Virtualization IBM Systems Director no longer displays a host
Removed manager nested beneath the virtual farm.
subagent
detects that a
host is
removed from
a virtual farm.
Table 7. Virtual farm events (continued)
Event Additional Target object for Event trigger Description
subcategory plan
Renamed Virtual Farm Virtualization (VMware VirtualCenter only) IBM Systems
manager Director displays the new name for the virtual
subagent for farm.
VMware
VirtualCenter
detects that a
virtual farm is
renamed.
Director > Correlation > Common Agent events

The Correlation events occur as a result of a specialized task called “Agent to
Blade-Correlation and Event Generation.” This task is available only in the Event
Action Plan Builder. When you create an event action plan and use the “Start a
task on the system that generated the event” event action, one of the tasks that you
can select for this event action is “Agent to Blade-Correlation and Event
Generation.” This task determines the UUID of a BladeCenter chassis or blade
server in your BladeCenter installation and provides the UUID to you by way of
the Correlation event.
Details
This is a customized event. The customization settings are in the

ChassisID.properties file that is located in the install_root classes\com\ibm\sysmgt\
chassis directory, where install_root is the root directory of your IBM Systems
Director installation. Note that this path uses the backslash (\) to delimit the
directory; depending on the system that you are using, you might be required to
enter the path using the forward slash (/).
If you select the Correlation check box in the Event Filter Builder tree, the event
filter will process all of the event types that are specified in the Correlation subtree.
Correlation Not applicable Not Not None
Correlation node in the Event Filter Builder tree. The event filter will process only
Common Not applicable Not Not None
Agent applicable applicable
Common Correlate Common Varies Varies None
Agent > Agent to its blade server depending depending
Blade Server - and generate event. on how on how
Chassis Note: This text is the you you
default text supplied in customizedcustomized
the ChassisID.properties the the
file. You can customize event. event.
this text.

Operating System
These events are generated when a change in connectivity to Common Agent is
detected.
Managed System Resource > Logical Resource > System > Operating System
Conditions
Condition Condition
type value Severity Category Event text Pre-6.1 event type name
Connectivity Offline Informational
Alert System system is offline. Director > Topology >
where system is the Offline
managed object with the
affected installation of
Common Agent.
Connectivity Online Informational
Alert System system is online. Director > Topology >
where system is the Online
managed object with the
affected installation of
Common Agent.
CIM > Windows NT Event Log

The Windows NT Event Log events are generated by IBM Systems Director Server
when it receives events from the Windows operating system. If an IBM Systems
Director environment does not include any systems running Windows, these
events are not available.
These CIM event types map to the Windows Event Log events in the IBM Systems
Director Event Filter Builder tree. For more information about the Windows event
log, see the Windows event log documentation.
CIM > Windows NT Service

The Windows NT Service events are generated by IBM Systems Director Server
when it receives events from the Windows operating system. If an IBM Systems
Director environment does not include any systems running Windows, these
events are not available.
CIM > Windows Registry

The Windows Registry events are generated by IBM Systems Director Server when
it receives events from the Windows operating system. If an IBM Systems Director
environment does not include any systems running Windows, these events are not
available.
Windows Event Log events
The Windows event log events are generated by the Windows operating system. If
IBM Systems Director Server does not discover any Common Agent managed
systems (including the management server that IBM Systems Director Server is
installed on) running Microsoft Windows, these event types are not present in the
Event Filter Builder tree.
In the Event Filter Builder tree, the Windows Event Log node expands to display
three nodes:
v Application
v Security
v System
Note: Additional nodes might be displayed when you expand the Windows Event
Log node. Whether these nodes are present depends on the managed systems
discovered by IBM Systems Director Server and their Windows registry settings.
These nodes map to the three folders displayed under the Event Log folder in the
Windows Registry Editor.
Note: To view these folders in the Windows Registry Editor, complete the
following steps:
1. Type regedit on a command line to start the Windows Registry Editor.
2. Click My Computer > HKEY_LOCAL_MACHINE > System >
CurrentControlSet > Services > Eventlog.
Microsoft has requirements for how an application provides its events to the
Windows event log. If an application fails to meet these requirements, IBM
Systems Director cannot map the application Windows events to the IBM Systems
Director Event Filter Builder tree. Application Windows events that can be mapped
are displayed under the System node of the Event Filter Builder tree. Some of the
requirements that must be met include providing a DLL that contains the event
description. Windows event properties include an event ID. The event ID maps to
the event description that is contained in the DLL.
Note: To view Windows event properties, including the event ID, complete the
following steps:
1. From the Windows desktop, click Start > Control Panel > Administrative
Tools.
2. In the Administrative Tools window, double-click Event Viewer
3. To open the Event Properties window, double-click an event. The event ID is
displayed as well as the source of the event.
Details
If you select the Windows Event Log check box in the Event Filter Builder tree, the
event filter will process all of the event types that are specified in the Windows
Event Log subtree. Expand this subtree to select specific event types or categories
of event types.

Chapter 3. Sources of events in an IBM Systems Director
environment
IBM Systems Director can use a number of sets of events. These events are
generated in different ways. Understanding how an event is generated can help
you decide which events can provide the information you need. Using this
information, you can build an event action plan to automate your
system-management work.
CIM event sources

CIM event types are generated by IBM Systems Director components and features,
hardware, and hardware options.
CIM > System
CIM indications are generated by managed systems that have either Platform
Agent or Common Agent installed. IBM Systems Director Server converts the CIM
indications into the CIM event types.
For HMC, the CIMOM generates CIM indications that IBM Systems Director
Server converts into CIM event types.
For IBM Power managed system running AIX, the CIMOM running on the IBM
Power managed system generates CIM indications that IBM Systems Director
Server converts into CIM event types.
Note: (Platform Agent managed systems with ServeRAID controllers only) In

order for the management server to receive CIM events from the system, you must
install the ServeRAID Manager program (Standalone Edition).
The MPA event source in IBM Systems Director, version 5.10 and later
MPA events are not generated by Platform Agent or Common Agent as they were
in previous versions of IBM Systems Director. MPA events are generated only by
IBM Systems Director Server when it receives out-of-band notifications from IBM
service processors and BladeCenter management modules.
Note: This information does not apply to IBM Director for NetWare, version 5.10
or 5.20.
You must configure the service processors and management modules in your
system-management environment to send notifications to IBM Systems Director
Server. IBM Systems Director attempts to perform this configuration automatically
when a system or chassis is discovered. If the configuration cannot be performed
(often because the service processor or management module is already configured
to send events to the maximum number of destinations), IBM Systems Director
generates an event to indicate this fact.

PET event source
PET events are not generated by Platform Agent or Common Agent. PET events
are out-of-band events received by IBM Systems Director Server from systems with
Alert Standard Format (ASF) or an IPMI baseboard management controller (BMC).
You must configure such systems in your system-management environment in

order for IBM Systems Director Server to receive PET events. For systems with an
IPMI BMC, see “Preparing to install IBM Systems Director on a System x server”
for information about configuring the controller to send notifications to IBM
Systems Director Server.
Notes:
1. IBM Director 5.20 or later does not support ASF configuration. However, IBM
Systems Director can receive PET events from ASF managed systems that were
configured to send events in an earlier version of IBM Systems Director.
2. Not all ASF systems generate all of the PET events.
ibmSystemMIB event source

ibmSystemMIB event types are generated by Common Agent. IBM Systems
Director uses CIM indications to communicate hardware information. If you have
configured your IBM Systems Director environment to use SNMP traps, IBM
Systems Director converts the CIM indications into the ibmSystemMIB SNMP
traps. For information about configuring your IBM Systems Director environment
to use SNMP traps, see “Configuring SNMP trap forwarding.”
To support SNMP, the Common Agent includes a CIM client that is called the
Common Agent SNMP agent. It translates the CIM-indication data into SNMP
format and exports the SNMP data to SNMP clients, such as HP OpenView and
Tivoli NetView® Upward Integration Modules (UIMs). When you configure your
IBM Systems Director environment to use SNMP traps, the Common Agent SNMP
agent is registered with the operating system and any queries involving the
Common Agent enterprise OID are forwarded to the Common Agent SNMP agent
for processing.
When an SNMP client sends a Get request, the Common Agent SNMP agent
receives the request and queries the CIM server on the target managed system.
Then, the CIM server performs the following steps:
1. Translates the SNMP request to a CIM client request
2. Converts the SNMP variable that is the subject of the request to a CIM instance
and property
3. Translates the CIM response to an SNMP response
4. Returns the response to the SNMP client
While the Common Agent SNMP agent is installed and registered, it creates and
forwards SNMP traps to any configured alert destinations. and you cannot stop the
forwarding of the SNMP traps. Unwanted SNMP traps must be filtered out by the
listening event server.

Chapter 4. Extended details and variable-binding information
Some implementations of IBM Systems Director event types use extended details to
provide additional information about the occurrence that generated an event.
Note: PET and SNMP trap event types use variable bindings.
In this documentation, each event lists any extended details that they have. Some
sets of events use the same extended details and they are defined in the following
sections. If an event has additional extended details, they are documented with the
affected event.
Extended details for CIM events

The CIM event types use the following standard set of extended details.
v AlertingManagedElement is the system component that is affected by the alert.
v Category is one of the following hardware event categories defined by the
Hardware Status task:
– Communications
– Device
– Environmental
– Security
v EventID provides the component node labels in the interface for the Hardware
Status task.
v EventTime is a reserved extended detail.
v ProviderName is a reserved extended detail.
Extended details for HMC CIM events

The CIM event types for HMC use the following standard set of extended details.
v AlertingManagedElement is the CIM object path of the system that generated the
event
v EventID provides the component node labels in the interface for the Hardware
Status task.
v EventTime provides the date and time that the event was generated. This value is
based on the local date and time of the system that generated the event.
v SenderUUID is the UUID of the HMC that sent the event.
Extended details for the Director > Director Agent events

The Director > Director Agent events use a standard set of extended attributes.
v Duration is the configured value that you assigned in the Minimum Duration
field of the Threshold Configuration window.
v Monitor Resource is the type of monitor configured with a threshold.
v Threshold Name is the name that you assigned to the threshold.

Extended details for the IBM Systems Director Program > Security
events
The IBM Systems Director Program > Security events use a standard set of
extended details.
v Address is the TCP/IP address or host name for the browser system that failed to
log on.
v User ID is the user ID of the user who failed to log on.
Extended details for MPA events

The MPA events use extended details to provide information about a state change
detected by a service processor or management module.
Most MPA events use some or all of the following extended details; however, the
availability of certain extended details will vary depending on the system from
which an event is generated. For example, events generated by an IPMI baseboard
management controller (BMC) does not provide the Sensor Label and Sensor
Number extended details.
v Firmware code is a 32-bit code that the service processor sends IBM Systems
Director Server to indicate what has occurred. This attribute is useful when
troubleshooting a problem with the assistance of IBM service representatives.
v Sender UUID is the universally unique identifier (UUID) of the physical system
that sent the event, or the UUID of the BladeCenter chassis if its management
module sent the event. Typically, the Sender UUID and Source UUID are the
same system. However, the sending physical system can be different from the
source system of the event. For example, a BladeCenter chassis (sender) sends
events for the blade servers (source) that it contains. Similarly, a server (sender)
sends events for an attached RXE-100 expansion unit (source).
v Sensor Label identifies the purpose of the affected sensor. This extended detail is
provided only when the event is generated by an IPMI baseboard management
controller.
v Sensor Number identifies the affected sensor. This extended detail is provided
only when the event is generated by an IPMI baseboard management controller.
v Source UUID is the universally unique identifier of the source physical system.
The source system is the source of the event, but not necessarily the sender of
the event. See Sender UUID for more information.
Extended details for PET events

All PET events use the same standard set of extended details (variable bindings).
Note: For detailed information about these extended details (variable bindings),
see the following documentation:
v Intel Intelligent Platform Management Interface Specification Version 1.5, dated June
1, 2004.
v Intel IPMI Platform Event Trap Specification Version 1.0, dated December 7, 1998.
v Entity identifies the affected system component, such as a, microprocessor,
system board, or power supply.
v Entity Instance identifies the affected instance of the system component, such as
power supply 1 and power supply 2.
v Event Data provides additional event information as specified by a combination
of the Event Type and Event Source extended details.

v Event Severity identifies the severity of the event. See the IPMI Specification for
defined values.
v Event Source Type identifies the class of device or type of software that originated
the event. This can be different than the device or type of software that sends
the trap. See the IPMI Specification for defined values.
v Event Type identifies what type of transition or state triggered the event.
v GUID identifies the GUID for the system.
v Language Code identifies, in combination with the OEM Custom Field extended
detail, the language that any strings are in.
Note: Language is different than character set. Character sets are specified as
ASCII or Unicode.
v Local Timestamp identifies the local time of the system, as a number of seconds.
v Manufacturer ID identifies the manufacturer ID using private enterprise IDs.
v OEM Custom Field provides customized information and can be used in
combination with the Language Code extended detail.
v Offset indicates which particular event occurred for a given Event Type.
v Sensor Device identifies the instance of the device that contains the sensor that
generated the event.
v Sensor Number uniquely identifies this sensor among all the sensors monitored
by this sensor device.
v Sensor Type identifies the types of events the event sensor is monitoring, such as
temperature, voltage, current, BIOS, POST, processor, and fan. Sometimes
referred to as the Event Sensor Type in the IPMI and PET Specifications.
v Sequence ID identifies whether the event trap is new or retransmitted. The
function of this field is specific to the trap source type.
v System ID identifies the particular system, product model, in combination with
the Manufacturer ID extended detail.
v Trap Source Type identifies the class of the device or software that originated the
trap on the network. See the IPMI Specification for defined values.
v UTC Offset identifies the coordinated universal time (UTC) offset in minutes.
Variable-binding information for IBM Systems Director SNMP events

The IBM Systems Director SNMP events use the following variables in the
variable-binding pairs.
For the values that are bound to these variables for each event type, see the
IBM-SYSTEM-TRAP-MIB.mib file in the install_root/proddata/snmp directory, where
install_root is the root directory of your IBM Systems Director Server installation.
Note that this path uses the backslash (\) to delimit the directory; depending on
the system that you are using, you might be required to enter the path using the
forward slash (/).
Table 8. IBM Systems Director SNMP event variable-binding information
Variable Syntax Definition (description)
OID Not The SNMPv1-standard OID defined in enterprise 'director'.
applicable
Identifier String The internal ID for this event type.
SourceObjectPath String The CIM device ID value for the system whose intrusion state is
being monitored. All IBM Systems Director SNMP events are
translated from CIM indicators.
Chapter 4. Extended details and variable-binding information 239

Table 8. IBM Systems Director SNMP event variable-binding information (continued)
Variable Syntax Definition (description)
TargetObjectPath String The CIM device ID value for the system whose intrusion state is
being monitored. All IBM Systems Director SNMP events are
translated from CIM indicators.
Severity Uint 16 The possible severities are critical, warning, or normal. Available
severities vary depending on the event. See each event for its
available severities.
Description String General information about what hardware scenario generates the
event.
TimeStamp Datetime The date and time when the state change occurred for the
component. A GMT-standard timestamp is used. For example:
20030416155614.000000-240.
Component Uint 16 The physical PCI slot number or the onboard port number of the
NIC.

Chapter 5. CIM indications in IBM Systems Director
CIM indications are the fundamental means that IBM Systems Director receives
hardware and system information. Depending on how your system-management
environment is implemented, IBM Systems Director converts the CIM indications
into events or other appropriate vehicles for communicating information to end
consumers.
IBM Systems Director converts CIM indications for use by the following end
consumers:
v IBM Systems Director events
v IBM Systems Director Web interface (including, but not limited to, the Problems
column in Navigate Resources, the Scoreboard available from the Health
Summary, and the Problems task available from the navigation pane)
v Microsoft System Center Operations Manager 2007 (alerts)
v Microsoft Operations Manager 2005 (alerts)
v Microsoft System Management Server (SMS) (native events)
v Microsoft Windows (event log event ID)
v SNMP
v Tivoli Enterprise Console® (native events)
v Tivoli Enterprise Console (SNMP events)
Note: The CA Unicenter, HP OpenView, and Tivoli NetView Upward Integration

Modules (UIMs) use SNMP traps.
IBM_MgmtHwLogStatus CIM indication

This CIM indication is generated when the system-management processor error log
is 75% full or full. This event is supported on servers with Intelligent Platform
Management Interface (IPMI).
End consumer Critical severity Warning severity Normal severity
IBM Systems Not applicable Not applicable CIM > System > IPMI
Director event Log
IBM Systems Not applicable Not applicable Not applicable
Director Web
interface
Microsoft Not applicable Not applicable Other
Operations
Manager 2005 alert
Microsoft SMS Not applicable Not applicable Not applicable
native events
Microsoft Not applicable Not applicable 33
Windows event
log event ID
SNMP Not applicable Not applicable ibmSystemTrapMgmt–
HwLogStatus
Tivoli Enterprise Not applicable Not applicable IBM_MgmtHwLogStatus
Console native
event

Tivoli Enterprise Not applicable Not applicable Not applicable
Console SNMP
event
IBMx_AutomaticServerRestartEvent CIM indication

This CIM indication is generated when the operating system locks up and no
longer responds. Subsequently, a system restart (reboot) begins. This event is
supported on servers with Intelligent Platform Management Interface (IPMI).
IBM Systems Not applicable CIM > System > CIM > System >
Director event Automatic Server Restart Automatic Server Restart
IBM Systems Not applicable Not applicable Not applicable
Director Web
interface
Microsoft Not applicable Not applicable Not applicable
Operations
Manager 2005 alert
Microsoft SMS Not applicable Not applicable Not applicable
native events
Microsoft Not applicable 36 36
Windows event
log event ID
SNMP Not applicable ibmSystemTrapxAutomatic ibmSystemTrapxAutomatic
ServerRestart ServerRestart
Console native
event
Console SNMP
event
IBMPSG_ChassisEvent CIM indication

This CIM indication is generated when the state of a system chassis (enclosure)
changes, such as when the cover is removed from the system.
IBM Systems CIM > System > System Not applicable CIM > System > System
Director event Enclosure Enclosure
IBM Systems Not applicable No symbol displayed
Director Web
interface
Microsoft Security Event Security Event Security Event

Operations
Manager 2005 alert
Microsoft SMS IBM_UMS_AGENT_ IBM_UMS_AGENT_ IBM_UMS_AGENT_
native events CHASSIS_ERROR_ CHASSIS_WARNING_ CHASSIS_INFO_
(Message ID
50040)
Microsoft 4 Not applicable 4
Windows event
log event ID
SNMP ibmSystemTrapChassis Not applicable ibmSystemTrapChassis

Tivoli Enterprise IBMPSG_ChassisEvent IBMPSG_ChassisEvent IBMPSG_ChassisEvent
Console native
event
Tivoli Enterprise UMS_ChassisIntruded Not applicable UMS_ChassisInPlace
Console SNMP
event
IBMPSG_DASDBackplaneEvent CIM indication

This CIM indication is generated when the Remote Supervisor Adapter detects that
the state of the system hard disk drive changes with respect to its availability.
IBM Systems Director CIM > System > DASD Not applicable Not applicable
event Backplane
IBM Systems Director Not applicable Not applicable Not applicable
Web interface
Microsoft Operations Storage Event Storage Event Storage Event
Manager 2005 alert
Microsoft SMS native IBM_UMS_AGENT_ IBM_UMS_AGENT_ IBM_UMS_AGENT_
events (Message ID DASDBACKPLANE_ DASDBACKPLANE_ DASDBACKPLANE_
50300) ERROR_ WARNING_ INFO_
Microsoft Windows 30 Not applicable Not applicable
event log event ID
SNMP ibmSystemTrapDASDBackplane
Not applicable Not applicable
Tivoli Enterprise IBMPSG_DASDBackplaneEvent
Console native event
Tivoli Enterprise UMS_DASDBackplaneEvent
Console SNMP event
IBMPSG_ErrorLogEvent CIM indication

its error log is at 75% or 100% of its capacity.
IBM Systems Director Not applicable CIM > System > Error Not applicable
event Log
Web interface
Microsoft Operations Other Event Other Event Other Event
Manager 2005 alert
events (Message ID ERRORLOG_ERROR_ ERRORLOG_WARNING_ ERRORLOG_INFO_
50240)
Microsoft Windows 24 24 Not applicable
event log event ID
SNMP Not applicable ibmSystemTrapErrorLog Not applicable
Tivoli Enterprise IBMPSG_ErrorLogEvent IBMPSG_ErrorLogEvent Not applicable
Tivoli Enterprise UMS_ErrorLogEvent UMS_ErrorLogEvent Not applicable
Console SNMP event
Chapter 5. CIM indicators 243

IBMPSG_FanEvent CIM indication
This CIM indication is generated when the state of a system fan has changed with
respect to the manufacturer-defined revolutions per minute (rpm) values. This
event is sent when a fan stops, is removed, or is not performing optimally.
IBM Systems Director CIM > System > Fan Not applicable CIM > System > Fan
event
IBM Systems Director Not applicable No symbol displayed
Web interface
Microsoft Operations Fan Event Fan Event Fan Event

Manager 2005 alert
events (Message ID FAN_ERROR_ FAN_WARNING_ FAN_INFO_
50050)
Microsoft Windows 5 5 5
event log event ID
SNMP ibmSystemTrapFan Not applicable ibmSystemTrapFan
Tivoli Enterprise IBMPSG_FanEvent IBMPSG_FanEvent IBMPSG_FanEvent
Tivoli Enterprise UMS_FanOutOfOrder Not applicable UMS_FanOperational
Console SNMP event
IBMPSG_GenericFanEvent CIM indication

This CIM indication is generated when the Remote Supervisor Adapter or ASM
processor detects that the state of a system fan has changed with respect to its
manufacturer-defined revolutions per minute (rpm) thresholds but the precise fan
instance cannot be determined.
IBM Systems Director CIM > System > Fan Not applicable Not applicable
event
IBM Systems Director Not applicable Not applicable
Web interface
Microsoft Operations Fan Event Fan Event Fan Event

Manager 2005 alert
events (Message ID GENERICFAN_ERROR_ GENERICFAN_WARNING_
GENERICFAN_INFO_
50310)
event log event ID
SNMP ibmSystemTrapGenericFan Not applicable Not applicable
Tivoli Enterprise IBMPSG_GenericFanEvent Not applicable Not applicable
Tivoli Enterprise UMS_GenericFanEvent Not applicable Not applicable
Console SNMP event

IBMPSG_GenericVoltageEvent CIM indication
This CIM indication is generated when the Remote Supervisor Adapter or the ASM
processor detects that the state of a system voltage sensor has changed with
respect to a manufacturer-defined threshold but the precise voltage sensor cannot
be determined.
IBM Systems Director CIM > System > Voltage Not applicable Not applicable
event
Web interface
Microsoft Operations Voltage Event Voltage Event Voltage Event

Manager 2005 alert
events (Message ID GENERICVOLTAGE_ GENERICVOLTAGE_ GENERICVOLTAGE_
50320) ERROR_ WARNING_ INFO_
event log event ID
SNMP ibmSystemTrapGenericVoltage
Tivoli Enterprise IBMPSG_GenericVoltageEvent
Tivoli Enterprise UMS_GenericVoltageEvent Not applicable Not applicable
Console SNMP event
IBMPSG_LeaseExpirationEvent CIM indication

This CIM indication is generated when the system lease expiration date has been
reached with respect to the value configured for the date in the Asset ID task.
IBM Systems Director Not applicable CIM > System > Lease CIM > System > Lease
event Expiration Expiration
Web interface

Manager 2005 alert
events (Message ID LEASE_ERROR_ LEASE_WARNING_ LEASE_INFO_
50130)
Microsoft Windows Not applicable 13 13
event log event ID
SNMP Not applicable ibmSystemTrapLeaseExpiration
Tivoli Enterprise IBMPSG_LeaseExpirationEvent
IBMPSG_LeaseExpirationEvent
IBMPSG_LeaseExpirationEvent
Tivoli Enterprise UMS_LeaseExpiredCritical UMS_LeaseExpiredWarningUMS_LeaseExpiredNormal
Console SNMP event

IBMPSG_MemoryPFEvent CIM indication
This CIM indication is generated when a dual inline memory module (DIMM) in a
system is about to fail.
IBM Systems Director CIM > System > Not applicable CIM > System >
event Memory PFA Memory PFA
Web interface
Microsoft Operations Memory Event Memory Event Memory Event

Manager 2005 alert
events (Message ID MEMORYPFA_ERROR_ MEMORYPFA_WARNING_MEMORYPFA_INFO_
50190)
Microsoft Windows 19 Not applicable 19
event log event ID
SNMP ibmSystemTrapMemoryPF Not applicable ibmSystemTrapMemoryPF
Tivoli Enterprise IBMPSG_MemoryPFEvent IBMPSG_MemoryPFEvent IBMPSG_MemoryPFEvent
Tivoli Enterprise UMS_MemoryPFCritical UMS_MemoryPFWarning UMS_MemoryPFNormal
Console SNMP event
IBMPSG_NetworkAdapterFailedEvent CIM indication

This CIM indication is generated when a network interface card (NIC) in a system
has failed.
IBM Systems Director CIM > System > Not applicable Not applicable
event Network Adapter >
Failed
Web interface
Microsoft Operations Network Event Network Event Network Event

Manager 2005 alert
events (Message ID NETWORKADAPTER NETWORKADAPTER NETWORKADAPTER
50260) FAILED_ERROR_ FAILED_WARNING_ FAILED_INFO_
Microsoft Windows Not applicable 26 Not applicable
event log event ID
SNMP ibmSystemTrapNetwork Not applicable Not applicable
AdapterFailed
Tivoli Enterprise Not applicable IBMPSG_NetworkAdapter Not applicable
Console native event FailedEvent
Tivoli Enterprise Not applicable UMS_NetworkAdapter Not applicable
Console SNMP event FailedEvent

IBMPSG_NetworkAdapterOfflineEvent CIM indication
This CIM indication is generated when a network interface card (NIC) in a system
goes offline.
IBM Systems Director Not applicable CIM > System > Not applicable
Offline
Web interface

Manager 2005 alert
50270) OFFLINE_ERROR_ OFFLINE_WARNING_ OFFLINE_INFO_
event log event ID
SNMP Not applicable ibmSystemTrapNetwork Not applicable
AdapterOffline
Tivoli Enterprise Not applicable IBMPSG_NetworkAdapter Not applicable
Console native event OfflineEvent
Tivoli Enterprise Not applicable UMS_NetworkAdapter Not applicable
Console SNMP event OfflineEvent
IBMPSG_NetworkAdapterOnlineEvent CIM indication

This CIM indication is generated when the state of a system network interface card
(NIC) changes from offline to online.
IBM Systems Director Not applicable Not applicable CIM > System >
Online
Web interface
Manager 2005 alert
50280) ONLINE_ERROR_ ONLINE_WARNING_ ONLINE_INFO_
Microsoft Windows Not applicable Not applicable 28
event log event ID
SNMP Not applicable Not applicable ibmSystemTrapNetwork
AdapterOnline
Tivoli Enterprise Not applicable Not applicable IBMPSG_NetworkAdapter
Console native event OnlineEvent
Tivoli Enterprise Not applicable Not applicable UMS_NetworkAdapter
Console SNMP event OnlineEvent

IBMPSG_PFAEvent CIM indication
a component in a system is about to fail.
IBM Systems Director CIM > System > PFA Not applicable Not applicable
event
Web interface

Manager 2005 alert
Microsoft SMS native IBM_UMS_AGENT_ IBM_UMS_AGENT_ IBM_UMS_AGENT_PFA_INFO_
events (Message ID PFA_ERROR_ PFA_WARNING_
50210)
event log event ID
SNMP ibmSystemTrapPFA Not applicable Not applicable
Tivoli Enterprise IBMPSG_PFAEvent Not applicable Not applicable
Tivoli Enterprise UMS_PFAEvent Not applicable Not applicable
Console SNMP event
IBMPSG_PowerSupplyEvent CIM indication

This CIM indication is generated when the state of a system power supply changes
with respect to its availability.
IBM Systems Director CIM > System > Server Not applicable CIM > System > Server
event Power Supply Power Supply
Web interface
Microsoft Operations Power Supply Event Power Supply Event Power Supply Event
Manager 2005 alert
events (Message ID POWERSUPPLY_ERROR_ POWERSUPPLY_WARNING_
POWERSUPPLY_INFO_
50230)
event log event ID
SNMP ibmSystemTrapPowerSupply
Not applicable ibmSystemTrapPowerSupply
Tivoli Enterprise IBMPSG_PowerSupplyEvent
IBMPSG_PowerSupplyEvent
IBMPSG_PowerSupplyEvent
Tivoli Enterprise UMS_PowerSupplyCritical UMS_PowerSupplyWarningUMS_PowerSupplyNormal
Console SNMP event

IBMPSG_ProcessorPFEvent CIM indication
This CIM indication is generated when the processor is about to fail.
IBM Systems Director CIM > System > Not applicable CIM > System >
event Processor PFA Processor PFA
Web interface
Microsoft Operations Processor Event Processor Event Processor Event

Manager 2005 alert
events (Message ID PROCESSORPF_ERROR_ PROCESSORPF_WARNING_
PROCESSORPF_INFO_
50180)
event log event ID
SNMP ibmSystemTrapProcessorPFNot applicable ibmSystemTrapProcessorPF
Tivoli Enterprise IBMPSG_ProcessorPFEventIBMPSG_ProcessorPFEventIBMPSG_ProcessorPFEvent
Tivoli Enterprise UMS_ProcessorPFCritical UMS_ProcessorPFWarning UMS_ProcessorPFNormal
Console SNMP event
IBMPSG_RedundantNetworkAdapterEvent CIM indication

This CIM indication is generated when the state of a system network interface card
(NIC) changes with respect to its redundancy. There are certain limitations of the
NIC that cannot be compensated for between a switchover and a switchback.
event
Web interface

Manager 2005 alert
events (Message ID REDUNDANTNETWORK REDUNDANTNETWORK REDUNDANTNETWORK
50150) ADAPTER_ERROR_ ADAPTER_WARNING_ ADAPTER_INFO_
event log event ID
SNMP Not applicable ibmSystemTrapRedundantNIC
Not applicable
Tivoli Enterprise Not applicable IBMPSG_RedundantNetwork
Not applicable
Console native event AdapterEvent
Tivoli Enterprise Not applicable UMS_RedundantNetwork Not applicable
Console SNMP event AdapterEvent

IBMPSG_RedundantNetworkAdapterSwitchbackEvent CIM indication
This CIM indication is generated when the primary network interface card (NIC) is
restored in a teamed NIC configuration.
IBM Systems Director Not applicable Not applicable CIM > System >
event Redundant Network
Adapter Switchback
IBM Systems Director Not applicable Not applicable No symbol displayed
Web interface
Manager 2005 alert
50170) ADAPTERSWITCHBACK_ADAPTERSWITCHBACK_ADAPTERSWITCHBACK_
ERROR_ WARNING_ INFO_
Microsoft Windows Not applicable Not applicable 17
event log event ID
SNMP Not applicable Not applicable ibmSystemTrapRedundant
NICSwitchback
Tivoli Enterprise Not applicable Not applicable IBMPSG_RedundantNetwork
Console native event AdapterSwitchbackEvent
Tivoli Enterprise Not applicable Not applicable UMS_RedundantNetwork
Console SNMP event AdapterSwitchback
IBMPSG_RedundantNetworkAdapterSwitchoverEvent CIM indication

This CIM indication is generated when the primary network interface card (NIC)
fails in a teamed NIC configuration and the standby NIC becomes the active NIC.
IBM Systems Director Not applicable CIM > System > Not applicable
event Redundant Network
Adapter Switchover
Web interface

Manager 2005 alert
50160) ADAPTERSWITCHOVER_ ADAPTERSWITCHOVER_ ADAPTERSWITCHOVER_
ERROR_ WARNING_ INFO_
event log event ID
SNMP Not applicable ibmSystemTrapRedundant Not applicable
NICSwitchover
Tivoli Enterprise Not applicable IBMPSG_RedundantNetworkNot applicable
Console native event AdapterSwitchoverEvent
Tivoli Enterprise Not applicable UMS_RedundantNetwork Not applicable
Console SNMP event AdapterSwitchover

IBMPSG_RemoteLoginEvent CIM indication
This CIM indication is generated when an end-user or application has logged in to
the Web interface of the Remote Supervisor Adapter.
IBM Systems Director Not applicable CIM > System > Remote Not applicable
event Login
Web interface
Microsoft Operations Security Event Security Event Security Event
Manager 2005 alert
events (Message ID REMOTELOGIN_ERROR_ REMOTELOGIN_ REMOTELOGIN_INFO_
50250) WARNING_
event log event ID
SNMP Not applicable ibmSystemTrapRemoteLogin
Not applicable
Tivoli Enterprise Not applicable IBMPSG_RemoteLoginEvent
Not applicable
Tivoli Enterprise Not applicable UMS_RemoteLoginEvent Not applicable
Console SNMP event
IBMPSG_SMARTEvent CIM indication

This CIM indication is generated when the state of an IDE or SCSI hard disk drive
that complies with the self-monitoring, analysis, and reporting technology
(SMART) changes with respect to its availability.
IBM Systems Director CIM > System > SMART CIM > System > SMART CIM > System > SMART
event Drive Drive Drive
Web interface

Manager 2005 alert
events (Message ID SMART_ERROR_ SMART_WARNING_ SMART_INFO_
50090)
event log event ID
SNMP ibmSystemTrapSMART Not applicable Not applicable
Tivoli Enterprise IBMPSG_SMARTEvent IBMPSG_SMARTEvent IBMPSG_SMARTEvent
Tivoli Enterprise UMS_SMARTCritical UMS_SMARTWarning UMS_SMARTNormal
Console SNMP event
IBMPSG_SPPowerSupplyEvent CIM indication

This CIM indication is generated when the Advanced Systems Management
processor (ASM processor) detects that the state of the system power supply
changes with respect to its availability. This is sent from servers that do not have a
power backplane and do not support a recovery severity or alert type.

event
Web interface
Microsoft Operations Power Supply Event Power Supply Event Power Supply Event
Manager 2005 alert
events (Message ID SPPOWERSUPPLY_ERROR_
SPPOWERSUPPLY_ SPPOWERSUPPLY_INFO_
50130) WARNING_
event log event ID
SNMP Not applicable ibmSystemTrapSPPower Not applicable
Supply
Tivoli Enterprise IBMPSG_SP_PowerSupply IBMPSG_SP_PowerSupply IBMPSG_SP_PowerSupply
Console native event Event Event Event
Tivoli Enterprise UMS_SPPowerSupplyEventUMS_SPPowerSupplyEventUMS_SPPowerSupplyEvent
Console SNMP event
IBMPSG_StorageEvent CIM indication

This CIM indication is generated when the state of system hard disk drive space
changes with respect to user-defined levels of hard disk drive space remaining. By
default, the warning level is 5% remaining and critical level is 3% remaining.
Notes:
v The CA Unicenter, HP OpenView, and Tivoli NetView Upward Integration
Modules (UIMs) use SNMP traps.
v This event type is independent of all RAID and other storage-related events.
IBM Systems Director CIM > System > Disk CIM > System > Disk CIM > System > Disk
event Space Low Space Low Space Low
IBM Systems Director No symbol displayed
Web interface

Manager 2005 alert
events (Message ID STORAGE_ERROR_ STORAGE_WARNING_ STORAGE_INFO_
50070)
Microsoft Windows 20 20 Not applicable
event log event ID
SNMP ibmSystemTrapStorage ibmSystemTrapStorage ibmSystemTrapStorage
Tivoli Enterprise IBMPSG_StorageEvent IBMPSG_StorageEvent IBMPSG_StorageEvent
Tivoli Enterprise UMS_StorageVeryLow UMS_StorageLow UMS_StorageNormal
Console SNMP event

Adjusting disk-space event threshold values on Linux
systems
If necessary, you can adjust the default threshold values for disk-space events on
systems running Linux. This enables you to control at what point warning and
critical messages are displayed.
To adjust the threshold values for disk-space events, complete the following steps:
1. Run the following command to stop the CIM server service:
/etc/init.d/cimserverd stop.
2. Use a text editor to edit the /opt/ibm/director/cimom/data/disk.dat file.
Adjust the following threshold values as needed:
/.IBMPSG_LogicalDisk.Period=30
/.IBMPSG_LogicalDisk.WarningThreshold=5
/.IBMPSG_LogicalDisk.CriticalThreshold=3
where Period is the time (in minutes) between checks, WarningThreshold is the
percentage of disk space remaining for the warning message to display, and
CriticalThreshold is the percentage of disk space remaining for the critical
message to display.
3. Save your changes and close the file.
4. Run the following command to start the CIM server service:
/etc/init.d/cimserverd start.
Adjusting disk-space event threshold values on Windows

systems
If necessary, you can adjust the default threshold values for disk-space events on
systems running Windows. This enables you to control at what point warning and
critical messages are displayed.
To adjust the threshold values for disk-space events, complete the following steps:
1. Run the following command to stop the CIM server service: net stop winmgmt.
2. Use a text editor to edit the <Director install location>\cimom\data\
disk.dat file, where <Director install location> is the location of the IBM Systems
Director installation. Adjust the following threshold values as needed:
/.IBMPSG_LogicalDisk.Period=30
/.IBMPSG_LogicalDisk.WarningThreshold=5
/.IBMPSG_LogicalDisk.CriticalThreshold=3
where Period is the time (in minutes) between checks, WarningThreshold is the
percentage of disk space remaining for the warning message to display, and
CriticalThreshold is the percentage of disk space remaining for the critical
message to display.
3. Save your changes and close the file.
4. Run the following command to start the CIM server service: net start winmgmt.
You might need to restart your agent system for the changes to take effect.

IBMPSG_TemperatureEvent CIM indication
This CIM indication is generated when the state of a system temperature sensor
changes with respect to a manufacturer-defined or user-defined threshold.
IBM Systems Director CIM > System > CIM > System > CIM > System >
event Temperature Temperature Temperature
IBM Systems Director No symbol displayed
Web interface
Microsoft Operations Temperature Event Temperature Event Temperature Event

Manager 2005 alert
events (Message ID TEMPERATURE_ERROR_ TEMPERATURE_ TEMPERATURE_INFO_
50020) WARNING_
event log event ID
SNMP ibmSystemTrapTemperatureibmSystemTrapTemperatureibmSystemTrapTemperature
Tivoli Enterprise IBMPSG_TemperatureEventIBMPSG_TemperatureEventIBMPSG_TemperatureEvent
Tivoli Enterprise UMS_TemperatureCriticallyOut
UMS_TemperatureOutOfRange
UMS_TemperatureNormal
Console SNMP event OfRange
IBMPSG_VoltageEvent CIM indication

This CIM indication is generated when the state of a system voltage sensor
changes with respect to a manufacturer-defined threshold.
IBM Systems Director CIM > System > Voltage Not applicable CIM > System > Voltage
event
Web interface
Microsoft Operations Voltage Event Voltage Event Voltage Event

Manager 2005 alert
events (Message ID VOLTAGE_ERROR_ VOLTAGE__WARNING_ VOLTAGE__INFO_
50030)
event log event ID
SNMP ibmSystemTrapVoltage Not applicable ibmSystemTrapVoltage
Tivoli Enterprise IBMPSG_VoltageEvent IBMPSG_VoltageEvent IBMPSG_VoltageEvent
Tivoli Enterprise UMS_VoltageCriticallyOutOf
UMS_VoltageOutOfRange UMS_VoltageNormal
Console SNMP event Range

IBMPSG_WarrantyExpirationEvent CIM indication
This CIM indication is generated when the system warranty expiration date has
been reached with respect to the value configured for the date while using the
Asset ID task.
IBM Systems Director Not applicable CIM > System > CIM > System >
event Warranty Expiration Warranty Expiration
Web interface

Manager 2005 alert
events (Message ID LEASE_ERROR_ LEASE_WARNING_ LEASE_INFO_
50140)
Microsoft Windows Not applicable 14 14
event log event ID
SNMP Not applicable ibmSystemTrapWarranty ibmSystemTrapWarranty
Expiration Expiration
Tivoli Enterprise IBMPSG_WarrantyExpiration
IBMPSG_WarrantyExpiration
IBMPSG_WarrantyExpiration
Console native event Event Event Event
Tivoli Enterprise UMS_WarrantyExpired UMS_WarrantyExpired UMS_WarrantyExpired
Console SNMP event Critical Warning Normal
ADPT_ArrayFlashCopyComplete CIM indication

This CIM indication is generated when a RAID FlashCopy operation is completed
on a specified array in a RAID configuration.
End consumer Normal severity
IBM Systems Director event CIM > System > RAID > RAID Array FlashCopy Complete
Microsoft Operations Manager 2005 alert RAID Event
Microsoft SMS native events (Message IBM_UMS_AGENT_STORAGERAIDHEALTH_INFO
ID 50210)
Microsoft Windows event log event ID 20
SNMP ibmSystemRaidArrayFlashCopyComplete
Tivoli Enterprise Console native event ADPT_ArrayFlashCopyComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidArrayFlashCopyComplete
ADPT_ArrayFlashCopyDetected CIM indication

This CIM indication is generated when a RAID FlashCopy operation is in progress
on a specified array in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Array FlashCopy Detected
ID 50210)
SNMP ibmSystemRaidArrayFlashCopyDetected

Tivoli Enterprise Console native event ADPT_ArrayFlashCopyDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidArrayFlashCopyDetected
ADPT_ArrayFlashCopyFail CIM indication

This CIM indication is generated when a RAID FlashCopy operation fails on a
specified array in a RAID configuration.
End consumer Critical severity
IBM Systems Director event CIM > System > RAID > RAID Array FlashCopy Fail
Microsoft SMS native events (Message IBM_UMS_AGENT_STORAGERAIDHEALTH_ERROR
ID 50210)
SNMP ibmSystemRaidArrayFlashCopyFail
Tivoli Enterprise Console native event ADPT_ArrayFlashCopyFail
Tivoli Enterprise Console SNMP event ibmSystemRaidArrayFlashCopyFail
ADPT_ArrayRebuildComplete CIM indication

This CIM indication is generated when a RAID rebuild operation is completed on
a specified array in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Array Rebuild Complete
ID 50210)
SNMP ibmSystemRaidArrayRebuildComplete
Tivoli Enterprise Console native event ADPT_ArrayRebuildComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidArrayRebuildComplete
ADPT_ArrayRebuildDetected CIM indication

This CIM indication is generated when a RAID rebuild operation is in progress on
IBM Systems Director event CIM > System > RAID > RAID Array Rebuild Detected
ID 50210)
SNMP ibmSystemRaidArrayRebuildDetected
Tivoli Enterprise Console native event ADPT_ArrayRebuildDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidArrayRebuildDetected

ADPT_ArrayRebuildFail CIM indication
This CIM indication is generated when a RAID rebuild operation fails on a
specified array in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Array Rebuild Fail
ID 50210)
SNMP ibmSystemRaidArrayRebuildFail
Tivoli Enterprise Console native event ADPT_ArrayRebuildFail
Tivoli Enterprise Console SNMP event ibmSystemRaidArrayRebuildFail
ADPT_ArraySyncComplete CIM indication

This CIM indication is generated when a RAID synchronization operation is
completed on a specified array in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Array Sync Complete
ID 50210)
SNMP ibmSystemRaidArraySyncComplete
Tivoli Enterprise Console native event ADPT_ArraySyncComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidArraySyncComplete
ADPT_ArraySyncDetected CIM indication

This CIM indication is generated when a RAID synchronization operation is in
progress on a specified array in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Array Sync Detected
ID 50210)
SNMP ibmSystemRaidArraySyncDetected
Tivoli Enterprise Console native event ADPT_ArraySyncDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidArraySyncDetected

ADPT_ArraySyncFail CIM indication
This CIM indication is generated when a RAID synchronization operation fails on
IBM Systems Director event CIM > System > RAID > RAID Array Sync Fail
ID 50210)
SNMP ibmSystemRaidArraySyncFail
Tivoli Enterprise Console native event ADPT_ArraySyncFail
Tivoli Enterprise Console SNMP event ibmSystemRaidArraySyncFail
ADPT_CompactionComplete CIM indication

This CIM indication is generated when a RAID compaction operation is completed
IBM Systems Director event CIM > System > RAID > RAID Compaction Complete
ID 50210)
SNMP ibmSystemRaidCompactionComplete
Tivoli Enterprise Console native event ADPT_CompactionComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidCompactionComplete
ADPT_CompactionDetected CIM indication

This CIM indication is generated when a RAID compaction operation is in
progress on a specified logical drive in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Compaction Detected
ID 50210)
SNMP ibmSystemRaidCompactionDetected
Tivoli Enterprise Console native event ADPT_CompactionDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidCompactionDetected

ADPT_CompactionFail CIM indication
This CIM indication is generated when a RAID compaction operation fails on a
specified logical drive in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Compaction Fail
ID 50210)
SNMP ibmSystemRaidCompactionFail
Tivoli Enterprise Console native event ADPT_CompactionFail
Tivoli Enterprise Console SNMP event ibmSystemRaidCompactionFail
ADPT_CompressionComplete CIM indication

This CIM indication is generated when a RAID compression operation is
completed on a specified logical drive in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Compression Complete
ID 50210)
SNMP ibmSystemRaidCompressionComplete
Tivoli Enterprise Console native event ADPT_CompressionComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidCompressionComplete
ADPT_CompressionDetected CIM indication

This CIM indication is generated when a RAID compression operation is in
IBM Systems Director event CIM > System > RAID > RAID Compression Detected
ID 50210)
SNMP ibmSystemRaidCompressionDetected
Tivoli Enterprise Console native event ADPT_CompressionDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidCompressionDetected

ADPT_CompressionFail CIM indication
This CIM indication is generated when a RAID compression operation fails on a
IBM Systems Director event CIM > System > RAID > RAID Compression Fail
ID 50210)
SNMP ibmSystemRaidCompressionFail
Tivoli Enterprise Console native event ADPT_CompressionFail
Tivoli Enterprise Console SNMP event ibmSystemRaidCompressionFail
ADPT_ConfigFail CIM indication

This CIM indication is generated when a RAID controller configuration cannot be
read.
IBM Systems Director event CIM > System > RAID > RAID Config Fail
ID 50210)
SNMP ibmSystemRaidConfigFail
Tivoli Enterprise Console native event ADPT_ConfigFail
Tivoli Enterprise Console SNMP event ibmSystemRaidConfigFail
ADPT_ControllerAdded CIM indication

This CIM indication is generated when a specified RAID controller is added to a
system.
IBM Systems Director event CIM > System > RAID > RAID Controller Added
ID 50210)
SNMP ibmSystemRaidControllerAdded
Tivoli Enterprise Console native event ADPT_ControllerAdded
Tivoli Enterprise Console SNMP event ibmSystemRaidControllerAdded

ADPT_ControllerBadStripes CIM indication
This CIM indication is generated when one or more logical drives contain at least
one bad stripe.
End consumer Warning severity
IBM Systems Director event CIM > System > RAID > RAID Controller Bad Stripes
Microsoft SMS native events (Message IBM_UMS_AGENT_STORAGERAIDHEALTH_WARNING
ID 50210)
SNMP ibmSystemRaidControllerBadStripes
Tivoli Enterprise Console native event ADPT_ControllerBadStripes
Tivoli Enterprise Console SNMP event ibmSystemRaidControllerBadStripes
ADPT_ControllerBatteryOvertemp CIM indication

This CIM indication is generated when the battery on a specified RAID controller
has exceeded its temperature threshold.
IBM Systems Director event CIM > System > RAID > RAID Controller Battery
Overtemp
ID 50210)
SNMP ibmSystemRaidControllerBatteryOvertemp
Tivoli Enterprise Console native event ADPT_ControllerBatteryOvertemp
Tivoli Enterprise Console SNMP event ibmSystemRaidControllerBatteryOvertemp
ADPT_ControllerBatteryTempNormal CIM indication

This CIM indication is generated when the battery on a specified RAID controller
has a normal temperature.
IBM Systems Director event CIM > System > RAID > RAID Controller Battery Temp
Normal
ID 50210)
SNMP ibmSystemRaidControllerBatteryTempNormal
Tivoli Enterprise Console native event ADPT_ControllerBatteryTempNormal
Tivoli Enterprise Console SNMP event ibmSystemRaidControllerBatteryTempNormal

ADPT_ControllerFail CIM indication
This CIM indication is generated when a specified RAID controller fails.
IBM Systems Director event CIM > System > RAID > RAID Controller Fail
ID 50210)
SNMP ibmSystemRaidControllerFail
Tivoli Enterprise Console native event ADPT_ControllerFail
Tivoli Enterprise Console SNMP event ibmSystemRaidControllerFail
ADPT_ControllerFailover CIM indication

This CIM indication is generated when a specified RAID controller fails over and
the passive controller in the failover pairing is now active.
IBM Systems Director event CIM > System > RAID > RAID Controller Failover
ID 50210)
SNMP ibmSystemRaidControllerFailover
Tivoli Enterprise Console native event ADPT_ControllerFailover
Tivoli Enterprise Console SNMP event ibmSystemRaidControllerFailover
ADPT_ControllerMismatchedVersions CIM indication

This CIM indication is generated when the versions of the BIOS, firmware, and
driver for a specified RAID controller do not match.
IBM Systems Director event CIM > System > RAID > RAID Controller Mismatched
Versions
ID 50210)
SNMP ibmSystemRaidVersionMismatched
Tivoli Enterprise Console native event ADPT_ControllerMismatchedVersions
Tivoli Enterprise Console SNMP event ibmSystemRaidControllerMismatchedVersions

ADPT_ControllerReplaced CIM indication
This CIM indication is generated when a specified controller is replaced in a RAID
configuration.
IBM Systems Director event CIM > System > RAID > RAID Controller Replaced
ID 50210)
SNMP ibmSystemRaidControllerReplaced
Tivoli Enterprise Console native event ADPT_ControllerReplaced
Tivoli Enterprise Console SNMP event ibmSystemRaidControllerReplaced
ADPT_CopyBackComplete CIM indication

This CIM indication is generated when a copy-back operation is completed on a
IBM Systems Director event CIM > System > RAID > RAID CopyBack Complete
ID 50210)
SNMP ibmSystemRaidCopyBackComplete
Tivoli Enterprise Console native event ADPT_CopyBackComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidCopyBackComplete
ADPT_CopyBackDetected CIM indication

This CIM indication is generated when a copy-back operation is in progress on a
IBM Systems Director event CIM > System > RAID > RAID CopyBack Detected
ID 50210)
SNMP ibmSystemRaidCopyBackDetected
Tivoli Enterprise Console native event ADPT_CopyBackDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidCopyBackDetected

ADPT_CopyBackFail CIM indication
This CIM indication is generated when a copy-back operation fails on a specified
logical drive in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID CopyBack Fail
ID 50210)
SNMP ibmSystemRaidCopyBackFail
Tivoli Enterprise Console native event ADPT_CopyBackFail
Tivoli Enterprise Console SNMP event ibmSystemRaidCopyBackFail
ADPT_DeadBattery CIM indication

This CIM indication is generated when the battery fails on a specified controller.
IBM Systems Director event CIM > System > RAID > RAID Dead Battery
ID 50210)
SNMP ibmSystemRaidDeadBattery
Tivoli Enterprise Console native event ADPT_DeadBattery
Tivoli Enterprise Console SNMP event ibmSystemRaidDeadBattery
ADPT_DeadBatteryCache CIM indication

This CIM indication is generated when the battery-backup cache fails on a
specified controller.
IBM Systems Director event CIM > System > RAID > RAID Dead Battery Cache
ID 50210)
SNMP ibmSystemRaidDeadBatteryCache
Tivoli Enterprise Console native event ADPT_DeadBatteryCache
Tivoli Enterprise Console SNMP event ibmSystemRaidDeadBatteryCache

ADPT_DecompressionComplete CIM indication
This CIM indication is generated when a RAID decompression operation is
IBM Systems Director event CIM > System > RAID > RAID Decompression Complete
ID 50210)
SNMP ibmSystemRaidDecompressionComplete
Tivoli Enterprise Console native event ADPT_DecompressionComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidDecompressionComplete
ADPT_DecompressionDetected CIM indication

This CIM indication is generated when a RAID decompression operation is in
IBM Systems Director event CIM > System > RAID > RAID Decompression Detected
ID 50210)
SNMP ibmSystemRaidDecompressionDetected
Tivoli Enterprise Console native event ADPT_DecompressionDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidDecompressionDetected
ADPT_DecompressionFail CIM indication

This CIM indication is generated when a RAID decompression operation fails on a
IBM Systems Director event CIM > System > RAID > RAID Decompression Fail
ID 50210)
SNMP ibmSystemRaidDecompressionFail
Tivoli Enterprise Console native event ADPT_DecompressionFail
Tivoli Enterprise Console SNMP event ibmSystemRaidDecompressionFail

ADPT_DefunctDrive CIM indication
This CIM indication is generated when a specified hard disk drive fails in a RAID
configuration.
IBM Systems Director event CIM > System > RAID > RAID Defunct Drive
ID 50210)
SNMP ibmSystemRaidDefunctDrive
Tivoli Enterprise Console native event ADPT_DefunctDrive
Tivoli Enterprise Console SNMP event ibmSystemRaidDefunctDrive
ADPT_DefunctDriveFRU CIM indication

This CIM indication is generated when a specified hard disk drive with the
provided field-replaceable unit (FRU) number fails in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Defunct Drive FRU
ID 50210)
SNMP ibmSystemRaidDefunctDriveFRU
Tivoli Enterprise Console native event ADPT_DefunctDriveFRU
Tivoli Enterprise Console SNMP event ibmSystemRaidDefunctDriveFRU
ADPT_DefunctReplaced CIM indication

This CIM indication is generated when a specified defunct hard disk drive has
been set to the hot-spare state in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Defunct Replaced
ID 50210)
SNMP ibmSystemRaidDefunctReplaced
Tivoli Enterprise Console native event ADPT_DefunctReplaced
Tivoli Enterprise Console SNMP event ibmSystemRaidDefunctReplaced

ADPT_DriveAdded CIM indication
This CIM indication is generated when a specified hard disk drive is added to a
RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Drive Added
ID 50210)
SNMP ibmSystemRaidDriveAdded
Tivoli Enterprise Console native event ADPT_DriveAdded
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveAdded
ADPT_DriveClearComplete CIM indication

This CIM indication is generated when a RAID clear operation is completed on a
specified hard disk drive in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Drive Clear Complete
ID 50210)
SNMP ibmSystemRaidDriveClearComplete
Tivoli Enterprise Console native event ADPT_DriveClearComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveClearComplete
ADPT_DriveClearDetected CIM indication

This CIM indication is generated when a RAID clear operation is in progress on a
IBM Systems Director event CIM > System > RAID > RAID Drive Clear Detected
ID 50210)
SNMP ibmSystemRaidDriveClearDetected
Tivoli Enterprise Console native event ADPT_DriveClearDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveClearDetected

ADPT_DriveClearFail CIM indication
This CIM indication is generated when a RAID clear operation fails on a specified
hard disk drive in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Drive Clear Fail
ID 50210)
SNMP ibmSystemRaidDriveClearFail
Tivoli Enterprise Console native event ADPT_DriveClearFail
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveClearFail
ADPT_DriveRemoved CIM indication

This CIM indication is generated when a specified hard disk drive is removed
from a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Drive Removed
ID 50210)
SNMP ibmSystemRaidDriveRemoved
Tivoli Enterprise Console native event ADPT_DriveRemoved
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveRemoved
ADPT_DriveVerifyComplete CIM indication

This CIM indication is generated when a RAID verify operation is completed on a
IBM Systems Director event CIM > System > RAID > RAID Drive Verify Complete
ID 50210)
SNMP ibmSystemRaidDriveVerifyComplete
Tivoli Enterprise Console native event ADPT_DriveVerifyComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveVerifyComplete

ADPT_DriveVerifyDetected CIM indication
This CIM indication is generated when a RAID verify operation is in progress on a
IBM Systems Director event CIM > System > RAID > RAID Drive Verify Detected
ID 50210)
SNMP ibmSystemRaidDriveVerifyDetected
Tivoli Enterprise Console native event ADPT_DriveVerifyDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveVerifyDetected
ADPT_DriveVerifyFail CIM indication

This CIM indication is generated when a RAID verify operation fails on a specified
hard disk drive in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Drive Verify Fail
ID 50210)
SNMP ibmSystemRaidDriveVerifyFail
Tivoli Enterprise Console native event ADPT_DriveVerifyFail
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveVerifyFail
ADPT_EnclosureFail CIM indication

This CIM indication is generated when an enclosure has failed on a specified
controller and channel in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Enclosure Fail
ID 50210)
SNMP ibmSystemRaidEnclosureFail
Tivoli Enterprise Console native event ADPT_EnclosureFail
Tivoli Enterprise Console SNMP event ibmSystemRaidEnclosureFail

ADPT_EnclosureFanFail CIM indication
This CIM indication is generated when a specified enclosure fan fails on a specified
controller and channel in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Enclosure Fan Fail
ID 50210)
SNMP ibmSystemRaidFanFail
Tivoli Enterprise Console native event ADPT_EnclosureFanFail
Tivoli Enterprise Console SNMP event ibmSystemRaidFanFail
ADPT_EnclosureFanInstalled CIM indication

This CIM indication is generated when a specified enclosure fan is installed on a
IBM Systems Director event CIM > System > RAID > RAID Enclosure Fan Installed
ID 50210)
SNMP ibmSystemRaidFanInstalled
Tivoli Enterprise Console native event ADPT_EnclosureFanInstalled
Tivoli Enterprise Console SNMP event ibmSystemRaidFanInstalled
ADPT_EnclosureFanOK CIM indication

This CIM indication is generated when a specified enclosure fan is functioning
IBM Systems Director event CIM > System > RAID > RAID Enclosure Fan OK
ID 50210)
SNMP ibmSystemRaidEnclosureFanOK
Tivoli Enterprise Console native event ADPT_EnclosureFanOK
Tivoli Enterprise Console SNMP event ibmSystemRaidEnclosureFanOK

ADPT_EnclosureFanRemoved CIM indication
This CIM indication is generated when a specified enclosure fan is removed on a
IBM Systems Director event CIM > System > RAID > RAID Enclosure Fan Removed
ID 50210)
SNMP ibmSystemRaidFanRemoved
Tivoli Enterprise Console native event ADPT_EnclosureFanRemoved
Tivoli Enterprise Console SNMP event ibmSystemRaidFanRemoved
ADPT_EnclosureOK CIM indication

This CIM indication is generated when a specified enclosure fan is functioning
IBM Systems Director event CIM > System > RAID > RAID Enclosure OK
ID 50210)
SNMP ibmSystemRaidEnclosureOK
Tivoli Enterprise Console native event ADPT_EnclosureOK
Tivoli Enterprise Console SNMP event ibmSystemRaidEnclosureOK
ADPT_EnclosurePowerSupplyFail CIM indication

This CIM indication is generated when the specified enclosure power supply fails
in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Enclosure Power Supply
Fail
ID 50210)
SNMP ibmSystemRaidPowerSupplyFail
Tivoli Enterprise Console native event ADPT_EnclosurePowerSupplyFail
Tivoli Enterprise Console SNMP event ibmSystemRaidPowerSupplyFail

ADPT_EnclosurePowerSupplyInstalled CIM indication
This CIM indication is generated when a specified enclosure power supply is
installed in a RAID configuration.
Installed
ID 50210)
SNMP ibmSystemRaidPowerSupplyInstalled
Tivoli Enterprise Console native event ADPT_EnclosurePowerSupplyInstalled
Tivoli Enterprise Console SNMP event ibmSystemRaidPowerSupplyInstalled
ADPT_EnclosurePowerSupplyOK CIM indication

functioning correctly in a RAID configuration.
OK
ID 50210)
SNMP ibmSystemRaidPowerSupplyOK
Tivoli Enterprise Console native event ADPT_EnclosurePowerSupplyOK
Tivoli Enterprise Console SNMP event ibmSystemRaidPowerSupplyOK
ADPT_EnclosurePowerSupplyRemoved CIM indication

removed from a RAID configuration.
Removed
ID 50210)
SNMP ibmSystemRaidPowerSupplyRemoved
Tivoli Enterprise Console native event ADPT_EnclosurePowerSupplyRemoved
Tivoli Enterprise Console SNMP event ibmSystemRaidPowerSupplyRemoved

ADPT_EnclosureTempFail CIM indication
This CIM indication is generated when an enclosure temperature exceeds a normal
range on a specified controller in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Enclosure Temp Fail
ID 50210)
SNMP ibmSystemRaidTempFail
Tivoli Enterprise Console native event ADPT_EnclosureTempFail
Tivoli Enterprise Console SNMP event ibmSystemRaidTempFail
ADPT_EnclosureTempOK CIM indication

This CIM indication is generated when an enclosure temperature is within a
normal range on a specified controller in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Enclosure Temp OK
ID 50210)
SNMP ibmSystemRaidTempOK
Tivoli Enterprise Console native event ADPT_EnclosureTempOK
Tivoli Enterprise Console SNMP event ibmSystemRaidTempOK
ADPT_ExpansionComplete CIM indication

This CIM indication is generated when a RAID expansion operation is completed
IBM Systems Director event CIM > System > RAID > RAID Expansion Complete
ID 50210)
SNMP ibmSystemRaidExpansionComplete
Tivoli Enterprise Console native event ADPT_ExpansionComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidExpansionComplete

ADPT_ExpansionDetected CIM indication
This CIM indication is generated when a RAID expansion operation is in progress
IBM Systems Director event CIM > System > RAID > RAID Expansion Detected
ID 50210)
SNMP ibmSystemRaidExpansionDetected
Tivoli Enterprise Console native event ADPT_ExpansionDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidExpansionDetected
ADPT_ExpansionFail CIM indication

This CIM indication is generated when a RAID expansion operation fails on a
IBM Systems Director event CIM > System > RAID > RAID Expansion Fail
ID 50210)
SNMP ibmSystemRaidExpansionFail
Tivoli Enterprise Console native event ADPT_ExpansionFail
Tivoli Enterprise Console SNMP event ibmSystemRaidExpansionFail
ADPT_FlashCopyComplete CIM indication

This CIM indication is generated when a RAID FlashCopy operation is completed
IBM Systems Director event CIM > System > RAID > RAID FlashCopy Complete
ID 50210)
SNMP ibmSystemRaidFlashCopyComplete
Tivoli Enterprise Console native event ADPT_FlashCopyComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidFlashCopyComplete

ADPT_FlashCopyDetected CIM indication
This CIM indication is generated when a RAID FlashCopy operation is in progress
IBM Systems Director event CIM > System > RAID > RAID FlashCopy Detected
ID 50210)
SNMP ibmSystemRaidFlashCopyDetected
Tivoli Enterprise Console native event ADPT_FlashCopyDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidFlashCopyDetected
ADPT_FlashCopyFail CIM indication

This CIM indication is generated when a RAID FlashCopy operation fails on a
IBM Systems Director event CIM > System > RAID > RAID FlashCopy Fail
ID 50210)
SNMP ibmSystemRaidFlashCopyFail
Tivoli Enterprise Console native event ADPT_FlashCopyFail
Tivoli Enterprise Console SNMP event ibmSystemRaidFlashCopyFail
ADPT_InitComplete CIM indication

This CIM indication is generated when a RAID initialization operation is
IBM Systems Director event CIM > System > RAID > RAID Init Complete
ID 50210)
SNMP ibmSystemRaidInitComplete
Tivoli Enterprise Console native event ADPT_InitComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidInitComplete

ADPT_InitDetected CIM indication
This CIM indication is generated when a RAID initialization operation is in
IBM Systems Director event CIM > System > RAID > ServeRAID Init Detected
ID 50210)
SNMP ibmSystemRaidInitDetected
Tivoli Enterprise Console native event ADPT_InitDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidInitDetected
ADPT_InitFail CIM indication

This CIM indication is generated when a RAID initialization operation fails on a
IBM Systems Director event CIM > System > RAID > RAID Init Fail
ID 50210)
SNMP ibmSystemRaidInitFail
Tivoli Enterprise Console native event ADPT_InitFail
Tivoli Enterprise Console SNMP event ibmSystemRaidInitFail
ADPT_LogicalDriveAdded CIM indication

This CIM indication is generated when a specified logical drive is added in a RAID
configuration.
IBM Systems Director event CIM > System > RAID > RAID Logical Drive Added
ID 50210)
SNMP ibmSystemRaidLogicalDriveAdded
Tivoli Enterprise Console native event ADPT_LogicalDriveAdded
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveAdded

ADPT_LogicalDriveBlocked CIM indication
This CIM indication is generated when a specified logical drive is in the blocked
state.
IBM Systems Director event CIM > System > RAID > RAID Logical Drive Blocked
ID 50210)
SNMP ibmSystemRaidLogicalDriveBlocked
Tivoli Enterprise Console native event ADPT_LogicalDriveBlocked
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveBlocked
ADPT_LogicalDriveCritical CIM indication

This CIM indication is generated when a specified logical drive is in the critical
state.
IBM Systems Director event CIM > System > RAID > RAID Logical Drive Critical
ID 50210)
SNMP ibmSystemRaidLogicalDriveCritical
Tivoli Enterprise Console native event ADPT_LogicalDriveCritical
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveCritical
ADPT_LogicalDriveCriticalPeriodic CIM indication

This CIM indication is generated when a periodic scan detects that one or more
logical drives are in a critical state.
IBM Systems Director event CIM > System > RAID > RAID Logical Drive Critical
Periodic
ID 50210)
SNMP ibmSystemRaidLogicalDriveCriticalPeriodic
Tivoli Enterprise Console native event ADPT_LogicalDriveCriticalPeriodic
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveCriticalPeriodic

ADPT_LogicalDriveOffLine CIM indication
This CIM indication is generated when a specified logical drive is in the offline
state.
IBM Systems Director event CIM > System > RAID > RAID Logical Drive Off Line
ID 50210)
SNMP ibmSystemRaidLogicalDriveOffLine
Tivoli Enterprise Console native event ADPT_LogicalDriveOffLine
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveOffLine
ADPT_LogicalDriveOK CIM indication

This CIM indication is generated when a specified logical drive is functioning
correctly.
IBM Systems Director event CIM > System > RAID > RAID Logical Drive OK
ID 50210)
SNMP ibmSystemRaidLogicalDriveOK
Tivoli Enterprise Console native event ADPT_LogicalDriveOK
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveOK
ADPT_LogicalDriveRemoved CIM indication

This CIM indication is generated when a specified logical drive has been removed
from a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Logical Drive Removed
ID 50210)
SNMP ibmSystemRaidLogicalDriveRemoved
Tivoli Enterprise Console native event ADPT_LogicalDriveRemoved
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveRemoved

ADPT_LogicalDriveUnblocked CIM indication
This CIM indication is generated when a specified logical drive is in the unblocked
state.
IBM Systems Director event CIM > System > RAID > RAID Logical Drive Unblocked
ID 50210)
SNMP ibmSystemRaidLogicalDriveUnblocked
Tivoli Enterprise Console native event ADPT_LogicalDriveUnblocked
Tivoli Enterprise Console SNMP event ibmSystemRaidDriveUnblocked
ADPT_MigrationComplete CIM indication

This CIM indication is generated when a RAID logical-drive migration is
IBM Systems Director event CIM > System > RAID > RAID Migration Complete
ID 50210)
SNMP ibmSystemRaidMigrationComplete
Tivoli Enterprise Console native event ADPT_MigrationComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidMigrationComplete
ADPT_MigrationDetected CIM indication

This CIM indication is generated when a RAID logical-drive migration is in
IBM Systems Director event CIM > System > RAID > RAID Migration Detected
ID 50210)
SNMP ibmSystemRaidMigrationDetected
Tivoli Enterprise Console native event ADPT_MigrationDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidMigrationDetected

ADPT_MigrationFail CIM indication
This CIM indication is generated when a RAID logical-drive migration fails on a
IBM Systems Director event CIM > System > RAID > RAID Migration Fail
ID 50210)
SNMP ibmSystemRaidMigrationFail
Tivoli Enterprise Console native event ADPT_MigrationFail
Tivoli Enterprise Console SNMP event ibmSystemRaidMigrationFail
ADPT_NoControllers CIM indication

This CIM indication is generated when no RAID controllers are detected.
IBM Systems Director event CIM > System > RAID > RAID No Controllers
ID 50210)
SNMP ibmSystemRaidNoControllers
Tivoli Enterprise Console native event ADPT_NoControllers
Tivoli Enterprise Console SNMP event ibmSystemRaidNoControllers
ADPT_PFADrive CIM indication

This CIM indication is generated when a Predictive Failure Analysis (PFA) is
detected on a specified hard disk drive in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID PFA Drive
ID 50210)
SNMP ibmSystemRaidPFADrive
Tivoli Enterprise Console native event ADPT_PFADrive
Tivoli Enterprise Console SNMP event ibmSystemRaidPFADrive

ADPT_PFADriveFRU CIM indication
detected on a specified hard disk drive with a specified field-replaceable unit
(FRU) number in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID PFA Drive FRU
ID 50210)
SNMP ibmSystemRaidPFADriveFRU
Tivoli Enterprise Console native event ADPT_PFADriveFRU
Tivoli Enterprise Console SNMP event ibmSystemRaidPFADriveFRU
ADPT_PollingFail CIM indication

This CIM indication is generated when a specified controller fails to respond to
background polling commands.
IBM Systems Director event CIM > System > RAID > RAID Polling Fail
ID 50210)
SNMP ibmSystemRaidPollingFail
Tivoli Enterprise Console native event ADPT_PollingFail
Tivoli Enterprise Console SNMP event ibmSystemRaidPollingFail
ADPT_RebuildComplete CIM indication

a specified logical drive in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Rebuild Complete
ID 50210)
SNMP ibmSystemRaidRebuildComplete
Tivoli Enterprise Console native event ADPT_RebuildComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidRebuildComplete

ADPT_RebuildDetected CIM indication
IBM Systems Director event CIM > System > RAID > RAID Rebuild Detected
ID 50210)
SNMP ibmSystemRaidRebuildDetected
Tivoli Enterprise Console native event ADPT_RebuildDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidRebuildDetected
ADPT_RebuildFail CIM indication

IBM Systems Director event CIM > System > RAID > RAID Rebuild Fail
ID 50210)
SNMP ibmSystemRaidRebuildFail
Tivoli Enterprise Console native event ADPT_RebuildFail
Tivoli Enterprise Console SNMP event ibmSystemRaidRebuildFail
ADPT_SyncComplete CIM indication

This CIM indication is generated when a RAID synchronization operation is
IBM Systems Director event CIM > System > RAID > RAID Sync Complete
ID 50210)
SNMP ibmSystemRaidSyncComplete
Tivoli Enterprise Console native event ADPT_SyncComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidSyncComplete

ADPT_SyncDetected CIM indication
This CIM indication is generated when a RAID synchronization operation is in
IBM Systems Director event CIM > System > RAID > RAID Sync Detected
ID 50210)
SNMP ibmSystemRaidSyncDetected
Tivoli Enterprise Console native event ADPT_SyncDetected
Tivoli Enterprise Console SNMP event ibmSystemRaidSyncDetected
ADPT_SyncFail CIM indication

This CIM indication is generated when a RAID synchronization operation fails on
IBM Systems Director event CIM > System > RAID > RAID Sync Fail
ID 50210)
SNMP ibmSystemRaidSyncFail
Tivoli Enterprise Console native event ADPT_SyncFail
Tivoli Enterprise Console SNMP event ibmSystemRaidSyncFail
ADPT_TestEvent CIM indication

This CIM indication is generated when a RAID test event is generated.
IBM Systems Director event CIM > System > RAID > RAID Test Event
ID 50210)
SNMP ibmSystemRaidTestEvent
Tivoli Enterprise Console native event ADPT_TestEvent
Tivoli Enterprise Console SNMP event ibmSystemRaidTestTrap

ADPT_UnsupportedDrive CIM indication
This CIM indication is generated when an unsupported hard disk drive is detected
in a RAID configuration.
IBM Systems Director event CIM > System > RAID > RAID Unsupported Drive
ID 50210)
SNMP ibmSystemRaidUnsupportedDrive
Tivoli Enterprise Console native event ADPT_UnsupportedDrive
Tivoli Enterprise Console SNMP event ibmSystemRaidUnsupportedDrive
LSI_RAID_HS_Fail CIM indication

This CIM indication is generated when a hot-spare drive has failed in a RAID
configuration. This indication can be generated by integrated SCSI controllers with
RAID capabilities (LSI 1064 controllers).
IBM Systems Director event CIM > System > RAID > RAID Hot Spare Failed
ID 50210)
SNMP ibmSystemRaidLsiHSFail
Tivoli Enterprise Console native event LSI_RAID_HS_Fail
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiHSFail
LSI_RAID_LD_Degraded CIM indication

This CIM indication is generated when a logical drive has been degraded in a
RAID configuration. This indication can be generated by integrated SCSI
controllers with RAID capabilities (LSI 1064 controllers).
IBM Systems Director event CIM > System > RAID > RAID Logical Drive Degraded
ID 50210)
SNMP ibmSystemRaidLsiLDDegraded
Tivoli Enterprise Console native event LSI_RAID_LD_Degraded
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiLDDegraded

LSI_RAID_LD_Offline CIM indication
This CIM indication is generated when a specified logical drive is in the offline
state. This indication can be generated by integrated SCSI controllers with RAID
IBM Systems Director event CIM > System > RAID > RAID Logical Drive Off Line
ID 50210)
SNMP ibmSystemRaidLsiLDOffline
Tivoli Enterprise Console native event LSI_RAID_LD_Offline
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiLDOffline
LSI_RAID_LD_Optimal CIM indication

This CIM indication is generated when a specified logical drive is functioning
correctly. This indication can be generated by integrated SCSI controllers with
RAID capabilities (LSI 1064 controllers).
IBM Systems Director event CIM > System > RAID > RAID Logical Drive Optimal
ID 50210)
SNMP ibmSystemRaidLsiLDOptimal
Tivoli Enterprise Console native event LSI_RAID_LD_Optimal
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiLDOptimal
LSI_RAID_PD_Fail CIM indication

This CIM indication is generated when a specified hard disk drive fails in a RAID
configuration. This indication can be generated by integrated SCSI controllers with
RAID capabilities (LSI 1020, 1030, and 1064 controllers).
IBM Systems Director event CIM > System > RAID > RAID Defunct Drive
ID 50210)
SNMP ibmSystemRaidLsiPDFail
Tivoli Enterprise Console native event LSI_RAID_PD_Fail
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiPDFail

LSI_RAID_PD_HS CIM indication
This CIM indication is generated when a physical drive has been made a hot-spare
drive in a RAID configuration. This indication can be generated by integrated SCSI
IBM Systems Director event CIM > System > RAID > RAID Hot Spare Added
ID 50210)
SNMP ibmSystemRaidLsiPDHS
Tivoli Enterprise Console native event LSI_RAID_PD_HS
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiPDHS
LSI_RAID_PD_PartOf_LD_Add CIM indication

This CIM indication is generated when a specified hard disk drive is added to a
RAID configuration. This indication can be generated by integrated SCSI
IBM Systems Director event CIM > System > RAID > RAID Drive Added
ID 50210)
SNMP ibmSystemRaidLsiPDPartOfLDAdd
Tivoli Enterprise Console native event LSI_RAID_PD_PartOf_LD_Add
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiPDPartOfLDAdd
LSI_RAID_PD_PartOf_LD_Fail CIM indication

This CIM indication is generated when a physical drive fails in a logical drive. This
indication can be generated by integrated SCSI controllers with RAID capabilities
(LSI 1064 controllers).
IBM Systems Director event CIM > System > RAID > RAID Part of Logical Drive Failed
ID 50210)
SNMP ibmSystemRaidLsiPDPartOfLDFail
Tivoli Enterprise Console native event LSI_RAID_PD_PartOf_LD_Fail
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiPDPartOfLDFail

LSI_RAID_RbldComplete CIM indication
a specified array in a RAID configuration. This indication can be generated by
IBM Systems Director event CIM > System > RAID > RAID Array Rebuild Complete
ID 50210)
SNMP ibmSystemRaidLsiRbldComplete
Tivoli Enterprise Console native event LSI_RAID_RbldComplete
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiRbldComplete
LSI_RAID_RbldFail CIM indication

specified array in a RAID configuration. This indication can be generated by
IBM Systems Director event CIM > System > RAID > RAID Array Rebuild Fail
ID 50210)
SNMP ibmSystemRaidLsiRbldFail
Tivoli Enterprise Console native event LSI_RAID_RbldFail
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiRbldFail
LSI_RAID_RbldStart CIM indication

a specified array in a RAID configuration. This indication can be generated by
IBM Systems Director event CIM > System > RAID > RAID Array Rebuild Detected
ID 50210)
SNMP ibmSystemRaidLsiRbldStart
Tivoli Enterprise Console native event LSI_RAID_RbldStart
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiRbldStart

LSI_RAID_SMART_Error CIM indication
detected on a specified hard disk drive in a RAID configuration. This indication
can be generated by integrated SCSI controllers with RAID capabilities (LSI 1064
controllers).
IBM Systems Director event CIM > System > RAID > RAID PFA Drive
ID 50210)
SNMP ibmSystemRaidLsiSMARTError
Tivoli Enterprise Console native event LSI_RAID_SMART_Error
Tivoli Enterprise Console SNMP event ibmSystemRaidLsiSMARTError

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation

Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
MW9A/050
5600 Cottle Road
San Jose, CA 95193
U.S.A.
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol (® or ™), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this
information was published. Such trademarks may also be registered or common

law trademarks in other countries. A current list of IBM trademarks is available on
the Web at “Copyright and trademark information” at www.ibm.com/legal/
copytrade.shtml.
Java is a trademark of Sun Microsystems, Inc. in the United States, other countries,
or both.
Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in

the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of

others.
Notices 291
Index
A CIM events (continued)
Power Supply 28
Agent events 215 Processor 29
Agent Extension event 228, 229 Processor PFA 30
agent manager 216 RAID 30
AIX events RAID Array FlashCopy Complete 30
Service Event 67 RAID Array FlashCopy Detected 31
System Event 69 RAID Copyback Complete 40
alarm panel 73 RAID Copyback Detected 41
Alert Standard Format 157, 236, 238 RAID Copyback Fail 41
array RAID Dead Battery 42
FlashCopy 30, 31, 178, 179, 255, 256 RAID Dead Battery Cache 42
rebuild 32, 33, 179, 180, 256, 257, 287 RAID Decompression Complete 42
synchronization 33, 34, 180, 181, 257, 258 RAID Decompression Detected 43
Asset ID task 23, 71, 169, 177, 245, 255 RAID Decompression Fail 43
Attribute Changed event 230 RAID Defunct Drive 43
automatic server restart 19, 178, 242 RAID Defunct Drive FRU 44
Automation Event Actions events 215 RAID Defunct Replaced 44
automation manager plug-in RAID Drive Added 45
events 215 RAID Drive Clear Complete 45
RAID Drive Clear Detected 45
RAID Drive Clear Fail 46
B RAID Drive Removed 46
bad stripe 37, 184, 261 RAID Drive Verify Complete 47
battery 42, 74, 188, 264 RAID Drive Verify Detected 47
Battery events 155 RAID Drive Verify Fail 47
battery-backup cache 42, 188, 264 RAID Enclosure Fail 48
BIOS 75, 160 RAID Enclosure Fan Fail 48
blade expansion unit 76 RAID Enclosure Fan Installed 49
BladeCenter RAID Enclosure Fan OK 49
events 80, 218 RAID Enclosure Fan Removed 50
products 77 RAID Enclosure OK 50
bootstrap loader program 131 RAID Enclosure Power Supply Fail 50
RAID Enclosure Power Supply Installed 51
RAID Enclosure Power Supply OK 51
C RAID Enclosure Power Supply Removed 52
RAID Enclosure Temp Fail 52
CA Unicenter 241 RAID Enclosure Temp OK 52
chassis (See also enclosure) 166, 242 RAID Expansion Complete 53
ChassisID.properties file 232 RAID Expansion Detected 53
CIM events RAID Expansion Fail 54
Automatic Server Restart 19 RAID FlashCopy Complete 54
DASD Backplane 19 RAID FlashCopy Detected 54
Disk Space Low 20 RAID FlashCopy Fail 55
Error Log 20 RAID Init Detected 55
extended details 237 RAID Init Fail 56
Fan 21 RAID Logical Drive Added 56
Host Bus Adapter 21 RAID Logical Drive Blocked 57
IP Change 22 RAID Logical Drive Critical 57
IPMI Log 22 RAID Logical Drive Critical Periodic 58
IVM Unconfigured 22 RAID Logical Drive Off Line 58
Lease Expiration 23 RAID Logical Drive OK 58
Life Cycle 23 RAID Logical Drive Removed 59
Memory 24 RAID Logical Drive Unblocked 59
Memory PFA 25 RAID Migration Complete 59
Network Adapter 25 RAID Migration Detected 60
Network Adapter Failed 25 RAID Migration Fail 60
Network Adapter Offline 25 RAID No Controllers 60
Network Adapter Online 25 RAID PFA Drive 61
overview 18 RAID PFA Drive FRU 61
PFA 26 RAID Polling Fail 61
Power State 27

CIM events (continued) CIM indications (continued)
RAID Rebuild Complete 62 ADPT_ControllerBatteryOvertemp 261
RAID Rebuild Detected 62 ADPT_ControllerBatteryTempNormal 261
RAID Rebuild Fail 62 ADPT_ControllerFail 262
RAID Sync Complete 63 ADPT_ControllerFailover 262
RAID Sync Detected 63 ADPT_ControllerMismatchedVersions 262
RAID Sync Fail 64 ADPT_ControllerReplaced 263
RAID Test Event 64 ADPT_CopyBackComplete 263
RAID Unsupported Drive 64 ADPT_CopyBackDetected 263
Redundant Network Adapter Failover 65 ADPT_CopyBackFail 264
Redundant Network Adapter Switchback 65 ADPT_DeadBattery 264
Redundant Network Adapter Switchover 66 ADPT_DeadBatteryCache 264
Remote Login 66 ADPT_DecompressionComplete 265
Server Power Supply 67 ADPT_DecompressionDetected 265
ServeRAID Array FlashCopy Fail 31 ADPT_DecompressionFail 265
ServeRAID Array Rebuild Complete 32 ADPT_DefunctDrive 266
ServeRAID Array Rebuild Detected 32 ADPT_DefunctDriveFRU 266
ServeRAID Array Rebuild Fail 33 ADPT_DefunctReplaced 266
ServeRAID Array Sync Complete 33 ADPT_DriveAdded 267
ServeRAID Array Sync Detected 33 ADPT_DriveClearComplete 267
ServeRAID Array Sync Fail 34 ADPT_DriveClearDetected 267
ServeRAID Compaction Complete 34 ADPT_DriveClearFail 268
ServeRAID Compaction Detected 35 ADPT_DriveRemoved 268
ServeRAID Compaction Fail 35 ADPT_DriveVerifyComplete 268
ServeRAID Compression Complete 35 ADPT_DriveVerifyDetected 269
ServeRAID Compression Detected 36 ADPT_DriveVerifyFail 269
ServeRAID Compression Fail 36 ADPT_EnclosureFail 269
ServeRAID Config Fail 36 ADPT_EnclosureFanFail 270
ServeRAID Controller Added 37 ADPT_EnclosureFanInstalled 270
ServeRAID Controller Bad Stripes 37 ADPT_EnclosureFanOK 270
ServeRAID Controller Battery Overtemp 38 ADPT_EnclosureFanRemoved 271
ServeRAID Controller Battery Temp Normal 38 ADPT_EnclosureOK 271
ServeRAID Controller Fail 39 ADPT_EnclosurePowerSupplyFail 271
ServeRAID Controller Failover 39 ADPT_EnclosurePowerSupplyInstalled 272
ServeRAID Controller Mismatched Versions 40 ADPT_EnclosurePowerSupplyOK 272
ServeRAID Controller Replaced 40 ADPT_EnclosurePowerSupplyRemoved 272
Service Event 67 ADPT_EnclosureTempFail 273
SMART Drive 68 ADPT_EnclosureTempOK 273
source 235 ADPT_ExpansionComplete 273
System 18 ADPT_ExpansionDetected 274
System Enclosure 69 ADPT_ExpansionFail 274
System Event 69 ADPT_FlashCopyComplete 274
Temperature 69 ADPT_FlashCopyDetected 275
Voltage 71 ADPT_FlashCopyFail 275
Warranty Expiration 71 ADPT_InitComplete 275
Windows NT Event Log 233 ADPT_InitDetected 276
Windows NT Service 233 ADPT_InitFail 276
Windows Registry 233 ADPT_LogicalDriveAdded 276
CIM indications ADPT_LogicalDriveBlocked 277
ADPT_ArrayFlashCopyComplete 255 ADPT_LogicalDriveCritical 277
ADPT_ArrayFlashCopyDetected 255 ADPT_LogicalDriveCriticalPeriodic 277
ADPT_ArrayFlashCopyFail 256 ADPT_LogicalDriveOffLine 278
ADPT_ArrayRebuildComplete 256 ADPT_LogicalDriveOK 278
ADPT_ArrayRebuildDetected 256 ADPT_LogicalDriveRemoved 278
ADPT_ArrayRebuildFail 257 ADPT_LogicalDriveUnblocked 279
ADPT_ArraySyncComplete 257 ADPT_MigrationComplete 279
ADPT_ArraySyncDetected 257 ADPT_MigrationDetected 279
ADPT_ArraySyncFail 258 ADPT_MigrationFail 280
ADPT_CompactionComplete 258 ADPT_NoControllers 280
ADPT_CompactionDetected 258 ADPT_PFADrive 280
ADPT_CompactionFail 259 ADPT_PFADriveFRU 281
ADPT_CompressionComplete 259 ADPT_PollingFail 281
ADPT_CompressionDetected 259 ADPT_RebuildComplete 281
ADPT_CompressionFail 260 ADPT_RebuildDetected 282
ADPT_ConfigFail 260 ADPT_RebuildFail 282
ADPT_ControllerAdded 260 ADPT_SyncComplete 282
ADPT_ControllerBadStripes 261 ADPT_SyncDetected 283

CIM indications (continued) controller (continued)
ADPT_SyncFail 283 replaced 40, 186, 263
ADPT_TestEvent 283 copyback 40, 41, 187, 263, 264
ADPT_UnsupportedDrive 284 Correlation events 232
conversion 18, 166, 235, 236 Created event
IBM_MgmtHwLogStatus 241 virtual farm 231
IBMPSG_ChassisEvent 242 virtual server 230
IBMPSG_DASDBackplaneEvent 243
IBMPSG_ErrorLogEvent 243
IBMPSG_FanEvent 244
IBMPSG_GenericFanEvent 244
D
decompression 42, 43, 188, 189, 265
IBMPSG_GenericVoltageEvent 245
Deleted event
IBMPSG_LeaseExpirationEvent 245
virtual farm 231
IBMPSG_MemoryPFEvent 246
virtual server 230
IBMPSG_NetworkAdapterFailedEvent 246
DIMM 24, 25, 88, 170, 246
IBMPSG_NetworkAdapterOfflineEvent 247
Director events
IBMPSG_NetworkAdapterOnlineEvent 247
See also IBM Systems Director Program events
IBMPSG_PFAEvent 248
Director Agent 237
IBMPSG_PowerSupplyEvent 248
Error 213, 214
IBMPSG_ProcessorPFEvent 249
extended details 237
IBMPSG_RedundantNetworkAdapterEvent 249
Job 212
IBMPSG_RedundantNetworkAdapterSwitchback-
Process Alert 210
Event 250
Process Failed to Start 210
IBMPSG_RedundantNetworkAdapterSwitchover-
Process Monitors 209
Event 250
Process Started 210
IBMPSG_RemoteLoginEvent 251
Process Terminated 210
IBMPSG_SMARTEvent 251
Resource Monitors 211
IBMPSG_SPPowerSupplyEvent 252
Scheduler 212
IBMPSG_StorageEvent 252
Success 213, 214
IBMPSG_TemperatureEvent 254
System 214
IBMPSG_VoltageEvent 254
Director task events 209
IBMPSG_WarrantyExpirationEvent 255
Disk Drive events 155
IBMx_AutomaticServerRestartEvent 242
disk space 253
LSI_RAID_HS_Fail 284
LSI_RAID_LD_Degraded 284
LSI_RAID_LD_Offline 285
LSI_RAID_LD_Optimal 285 E
LSI_RAID_PD_Fail 285 enclosure
LSI_RAID_PD_HS 286 BladeCenter chassis 80
LSI_RAID_PD_PartOf_LD_Add 286 fail 48, 193, 269
LSI_RAID_PD_PartOf_LD_Fail 286 OK 50, 194, 271
LSI_RAID_RbldComplete 287 system 69, 166, 242
LSI_RAID_RbldFail 287 temperature 52, 207, 273
LSI_RAID_RbldStart 287 enclosure fan
LSI_RAID_SMART_Error 288 fail 48, 195, 270
overview 241 installed 49, 196, 270
clear 45, 46, 191, 267, 268 OK 49, 194, 270
Clock Module 83 removed 50, 196, 271
Common Agent enclosure power supply
events 209, 215 fail 50, 203, 271
request access 216 installed 51, 204, 272
compaction 34, 35, 182, 258, 259 OK 51, 204, 272
compression 35, 36, 182, 183, 259, 260 removed 52, 204, 272
Computer System events 133 environmental
Configuration Manager events events 69, 71, 121, 158, 168, 175, 176, 245, 254
See System Configuration error log 20, 22, 167, 170, 241, 243
configuration manager plug-in Ethernet port 144
events 218 event
Console events CIM 18
See Security events MPA 72
controller MPA source 235
added 37, 184, 260 PET 157, 236
fail 39, 186, 262 SNMP 165
failover 39, 186, 262 source 235
mismatched versions 40, 208, 262 Windows Event Log 234
none 60, 202, 280 event actions
polling 61, 203, 281 testing 215
Index 295
event actions (continued) Host Stopped event 229
Timed alarm that generates an event 215 HP OpenView 241
events
Agent 215
Automation Event Actions 215
disk space 253
I
I/O board 94
Status 218
I/O Interposer 95
System Configuration 218
I/O module 95
expansion 53, 54, 194, 195, 273, 274
IBM Director Agent
expansion card 90
events 215
extended details
IBM Systems Director events
CIM 237
CIM indications 241
Director 237
IBM Systems Director Program events
IBM Systems Director Program 238
Agent 215
MPA 238
Automation Event Actions 215
overview 237
extended details 238
PET 238
overview 215
SNMP 239
Security 216, 217, 238
Status 218
System Configuration 218
F Updates 221, 222
failover 39, 186, 262 IBM-SYSTEM-RAID-MIB.mib 178
fan 21, 90, 167, 168, 244 IBM-SYSTEM-TRAP-MIB.mib 166
Fan events 145 initialization 55, 56, 197, 198, 275, 276
fan pack 92 IPMI 22, 170, 241
Fibre Channel Port events 147
files
ChassisID.properties 232
IBM-SYSTEM-RAID-MIB.mib 178
J
job 209, 210, 211, 212, 213, 214
IBM-SYSTEM-TRAP-MIB.mib 166
FlashCopy 30, 31, 54, 55, 178, 179, 196, 197, 255, 256, 274, 275
front panel 93
FRU 44, 61, 190, 202, 266, 281 K
KVM 84
H
hard disk drive L
added 45, 191, 267, 286 lease expiration 23, 169, 245
clear 45, 46, 191, 267, 268 legal notices 289
defunct 43, 189, 266, 285, 286 logging on failure 216
defunct FRU 44, 190, 266 Logical device events
hot spare 44, 190, 266, 284, 286 processor 152
nonwarranted 64, 207, 284 logical drive
PFA 61, 202, 280, 281, 288 added 56, 198, 276
removed 46, 192, 268 blocked 57, 199, 277
SMART 68, 174, 251 critical 57, 58, 199, 277
state change 19, 86, 167, 243 degraded 284
storage low 20, 175, 252 expansion 53, 54, 194, 195, 273, 274
unsupported 64, 207, 284 FlashCopy 54, 55, 196, 197, 274, 275
verify 47, 192, 193, 268, 269 initialization 55, 56, 197, 198, 275, 276
hardware migration 59, 60, 201, 202, 279, 280
failure events 26, 102, 162, 171, 248 offline 58, 200, 278, 285
status OK 58, 200, 278, 285
CIM indications 241 rebuild 62, 205, 281, 282
icons 241 removed 59, 200, 278
Hardware Console Point 22 unblocked 59, 201, 279
hardware events 1 logoff 216, 217
BladeCenter 18 logon 216, 217
Power 133
Storage 155
System x 18
Hardware Management Console 18, 22, 23, 27, 67, 237
M
managed systems
Host Added event 231
state change 18, 30
Host Bus Adapter events 21
management module events 73, 74, 75, 76, 77, 79, 80, 83, 84,
Host Removed event 231
86, 88, 90, 92, 93, 94, 95, 99, 100, 101, 102, 103, 105, 107, 108,
Host Started event 228
109, 112, 118, 119, 120, 121, 131

management module interposer 99 NIC 25, 65, 66, 170, 171, 172, 173, 246, 247, 249, 250
Media Access Device events nonwarranted hard disk drive 64, 207, 284
Physical Volume 151
media tray 100
memory 24, 25, 88, 170, 246
Memory events 148
O
operating system
MIB file 165, 166, 178
state change 164
microprocessor 29, 30, 84, 172, 249
operating system events 209
Microsoft Operations Manager 2005 241
Operating System events 233
Microsoft System Center Operations Manager 241
Optical Drive events 149
Microsoft System Management Server 241
migration 59, 60, 201, 202, 279, 280
mismatched versions 40, 208, 262
monitoring 209, 210, 211 P
MPA events PCI Device events 150
Alarm Panel 73 PET events
Battery 74 BIOS 161
BIOS 75 Boot 164
Blade Expansion Unit 76 Cable/Interconnect 162
Blade Server 77 Case Intrusion 158
Bus 79 Current 158
Chassis 80 Drive bay 162
Clock Module 83 Environmental 158
Component 72 extended details 238
Concurrent KVM 84 Fan 158
Configuration 80 Firmware 160
CPU 84 Hardware 162
DASD 86 Heartbeat 164
DIMM events 88 Module/Board 162
Environmental 121 Monitor ASIC/IC 162
Expansion Card 90 Network 162
extended details 238 Operation 164
Failed 80 OS 164
Fan 90 overview 157
Fan Pack 92 Power Supply 158
Front Panel 93 Progress 161
I/O Board 94 Sensor 158
I/O Interposer 95 System 164
I/O module 95 Temperature 158
Management Module Interposer 99 Voltage 158
Media Tray 100 Watchdog 162
Miscellaneous 130 PFA 25, 26, 30, 61, 102, 170, 171, 172, 202, 246, 248, 249, 280,
Multiplexer Expansion Module 101 281, 288
overview 72 Physical Volume 151
PET events 157 Platform Event Trap 157, 236
PFA 102 polling 61, 203, 281
Platform 131 POST failed 131
Power Subsystem 103 power supply 28, 67, 105, 171, 174, 248, 252
Power Supply 105 Process Monitors events 209, 210
Processor Board 107 processor 30, 152
RAID 108 processor board 107
Server 109 pSeries events
Server WatchDog 131 IP Change 22
Service Processor 112 Life Cycle 23
SMP Expansion Module 117 Power State 27
source 235 System Event 67, 69
Storage Module 118
Unknown 132
USB 119
VRM 120
Q
QLogic products 21
multiplexer expansion module 101
N R
RAID 108
network adapter 25, 65, 66, 170, 171, 172, 173, 246, 247, 249,
RAID Controller events 156
250
network device 95
Index 297
RAID events RAID events (continued)
array synchronization 63, 64, 205, 206, 282, 283
FlashCopy 30, 31, 178, 179, 255, 256 temperature 52, 207, 273
rebuild 32, 33, 179, 180, 256, 257, 287 test event 64, 207, 283
synchronization 33, 34, 180, 181, 257, 258 rebuild 32, 33, 62, 179, 180, 205, 256, 257, 281, 282, 287
battery 38, 42, 188, 261, 264 redundant NIC 65, 66, 172, 173, 249, 250
battery-backup cache 42, 188, 264 relocating virtual servers
compaction 34, 35, 182, 258, 259 events 230
compression 35, 36, 182, 183, 259, 260 remote login 66, 173, 251
configuration 36, 183, 260 Remote Supervisor Adapter
controller remote login 66, 173, 251
added 37, 184, 260 Renamed event
bad stripe 37, 184, 261 virtual farm 232
battery 38, 185, 261 request access 216
fail 39, 186, 262 resource monitors 209
failover 39, 186, 262 Resource Monitors events 211
mismatched versions 40, 208, 262
none 60, 202, 280
polling 61, 203, 281
replaced 40, 186, 263
S
scalable partition events 131
copyback 40, 41, 187, 263, 264
Scalable Systems Manager 131
decompression 42, 43, 188, 189, 265
scheduled job 209, 210, 211
enclosure
Scheduler events 212, 213, 214
fail 48, 193, 269
Security
OK 50, 194, 271
events 216, 217
temperature 52, 207, 273
server
enclosure fan
automatic restart 19, 178, 242
fail 48, 195, 270
service processors
installed 49, 196, 270
events 73, 74, 75, 76, 79, 83, 84, 86, 88, 90, 92, 93, 94, 95,
OK 49, 194, 270
99, 100, 101, 102, 103, 105, 107, 108, 109, 112, 117, 118, 119,
removed 50, 196, 271
120, 121, 130, 131, 132
enclosure power supply
MPA events 72, 235
fail 50, 203, 271
remote login 66, 173, 251
installed 51, 204, 272
SMART drive 68, 174, 251
OK 51, 204, 272
SMP Expansion Module 117
removed 52, 204, 272
SNMP events
expansion 53, 54, 194, 195, 273, 274
CIM indications 241
hard disk drive
ibmSystemMIB 166, 236
added 45, 191, 267, 286
ibmSystemRaid 178
clear 45, 46, 191, 267, 268
ibmSystemRaidArrayFlashCopyComplete 178
defunct 43, 189, 266, 285, 286
ibmSystemRaidArrayFlashCopyDetected 179
defunct FRU 44, 190, 266
ibmSystemRaidArrayFlashCopyFail 179
hot spare 44, 190, 266, 284, 286
ibmSystemRaidArrayRebuildComplete 179
PFA 61, 202, 280, 281, 288
ibmSystemRaidArrayRebuildDetected 180
removed 46, 192, 268
ibmSystemRaidArrayRebuildFail 180
unsupported 64, 207, 284
ibmSystemRaidArraySyncComplete 180
verify 47, 192, 193, 268, 269
ibmSystemRaidArraySyncDetected 181
initialization 55, 56, 197, 198, 275, 276
ibmSystemRaidArraySyncFail 181
logical drive 40, 41, 42, 43, 53, 54, 187, 188, 189, 194, 195,
ibmSystemRaidCompactionComplete 182
263, 264, 265, 273, 274
ibmSystemRaidCompactionDetected 182
added 56, 198, 276
ibmSystemRaidCompactionFail 182
blocked 57, 199, 277
ibmSystemRaidCompressionComplete 182
critical 57, 58, 199, 277
ibmSystemRaidCompressionDetected 183
degraded 284
ibmSystemRaidCompressionFail 183
FlashCopy 54, 55, 196, 197, 274, 275
ibmSystemRaidConfigFail 183
initialization 55, 56, 197, 198, 275, 276
ibmSystemRaidControllerAdded 184
migration 59, 60, 201, 202, 279, 280
ibmSystemRaidControllerBadStripes 184
offline 58, 200, 278, 285
ibmSystemRaidControllerBatteryOvertemp 185
OK 58, 200, 278, 285
ibmSystemRaidControllerBatteryTempNormal 185
rebuild 62, 205, 281, 282
ibmSystemRaidControllerFail 186
removed 59, 200, 278
ibmSystemRaidControllerFailover 186
synchronization 63, 64, 205, 206, 282, 283
ibmSystemRaidControllerReplaced 186
unblocked 59, 201, 279
ibmSystemRaidCopyBackComplete 187
migration 59, 60, 201, 202, 279, 280
ibmSystemRaidCopyBackDetected 187
overview 178
ibmSystemRaidCopyBackFail 187
polling 61, 203, 281
ibmSystemRaidDeadBattery 188
rebuild 62, 205, 281, 282
ibmSystemRaidDeadBatteryCache 188

SNMP events (continued) SNMP events (continued)
ibmSystemRaidDecompressionComplete 188 ibmSystemTrapMemoryPF 170
ibmSystemRaidDecompressionDetected 189 ibmSystemTrapMgmtHwLogStatus 170
ibmSystemRaidDecompressionFail 189 ibmSystemTrapNetworkAdapterFailed 170
ibmSystemRaidDefunctDrive 189 ibmSystemTrapNetworkAdapterOffline 171
ibmSystemRaidDefunctDriveFRU 190 ibmSystemTrapNetworkAdapterOnline 171
ibmSystemRaidDefunctReplaced 190 ibmSystemTrapPFA 171
ibmSystemRaidDriveAdded 191 ibmSystemTrapPowerSupply 171
ibmSystemRaidDriveClearComplete 191 ibmSystemTrapProcessorPF 172
ibmSystemRaidDriveClearDetected 191 ibmSystemTrapRedundantNIC 172
ibmSystemRaidDriveClearFail 191 ibmSystemTrapRedundantNICSwitchback 173
ibmSystemRaidDriveRemoved 192 ibmSystemTrapRedundantNICSwitchover 173
ibmSystemRaidDriveVerifyComplete 192 ibmSystemTrapRemoteLogin 173
ibmSystemRaidDriveVerifyDetected 192 ibmSystemTrapSMART 174
ibmSystemRaidDriveVerifyFail 193 ibmSystemTrapSPPowerSupply 174
ibmSystemRaidEnclosureFail 193 ibmSystemTrapStorage 175
ibmSystemRaidEnclosureFanOK 194 ibmSystemTrapTemperature 175
ibmSystemRaidEnclosureOK 194 ibmSystemTrapVoltage 176
ibmSystemRaidExpansionComplete 194 ibmSystemTrapWarrantyExpiration 177
ibmSystemRaidExpansionDetected 194 ibmSystemTrapxAutomaticServerRestart 178
ibmSystemRaidExpansionFail 195 overview 165
ibmSystemRaidFanFail 195 source 236
ibmSystemRaidFanInstalled 196 variable binding 239
ibmSystemRaidFanRemoved 196 software events 209
ibmSystemRaidFlashCopyComplete 196 State events 230
ibmSystemRaidFlashCopyDetected 196 Status
ibmSystemRaidFlashCopyFail 197 events 218
ibmSystemRaidInitComplete 197 Status events 218
ibmSystemRaidInitDetected 198 status manager plug-in
ibmSystemRaidInitFail 198 events 218
ibmSystemRaidLogicalDriveAdded 198 storage events
ibmSystemRaidLogicalDriveBlocked 199 battery 155
ibmSystemRaidLogicalDriveCritical 199 disk drive 155
ibmSystemRaidLogicalDriveCriticalPeriodic 199 RAID controller 156
ibmSystemRaidLogicalDriveOffLine 200 storage pool 156
ibmSystemRaidLogicalDriveOK 200 storage subsystem 156
ibmSystemRaidLogicalDriveRemoved 200 storage volume 157
ibmSystemRaidLogicalDriveUnblocked 201 switch 157
ibmSystemRaidMigrationComplete 201 Storage Module 118
ibmSystemRaidMigrationDetected 201 Storage Pool events 156
ibmSystemRaidMigrationFail 202 Storage Subsystem events 156
ibmSystemRaidNoControllers 202 Storage Volume events 157
ibmSystemRaidPFADrive 202 switch 95
ibmSystemRaidPFADriveFRU 202 Switch events 157
ibmSystemRaidPollingFail 203 synchronization 33, 34, 63, 64, 180, 181, 205, 206, 257, 258,
ibmSystemRaidPowerSupplyFail 203 282, 283
ibmSystemRaidPowerSupplyInstalled 204 System Configuration
ibmSystemRaidPowerSupplyOK 204 events 218
ibmSystemRaidPowerSupplyRemoved 204 System p events
ibmSystemRaidRebuildComplete 205 IP Change 22
ibmSystemRaidRebuildDetected 205 IVM Unconfigured 22
ibmSystemRaidRebuildFail 205 Life Cycle 23
ibmSystemRaidSyncComplete 205 Power State 27
ibmSystemRaidSyncDetected 206 System Event 67, 69
ibmSystemRaidSyncFail 206 System x
ibmSystemRaidTempFail 207 events 218
ibmSystemRaidTempOK 207
ibmSystemRaidTestEvent 207
ibmSystemRaidUnsupportedDrive 207
ibmSystemRaidVersionMismatch 208
T
Task Failed event 231
ibmSystemTrapChassis 166
temperature 69, 175, 254
ibmSystemTrapDASDBackplane 167
testing event actions 215
ibmSystemTrapErrorLog 167
Timed alarm that generates an event 215
ibmSystemTrapFan 167
timeout settings 131
ibmSystemTrapGenericFan 168
Tivoli Enterprise Console
ibmSystemTrapGenericVoltage 168
native events 241
ibmSystemTrapLeaseExpiration 169
SNMP events 241
Index 299
Tivoli NetView 241
Topology event
See Agent events
Topology events
See Operating System events
trademarks 290
U
Update Manager events
See Updates
Updates
events 221, 222
Upward Integration Modules 166, 236
USB 119
USB Port events 153
user
logoff 216, 217
logon 216, 217
V
variable binding 237, 238, 239
verify 47, 192, 193, 268, 269
voltage 71, 168, 176, 245, 254
W
warranty expiration 71, 177, 255
Web interface status icons 241
web resources x
Windows
Event Log events 233, 234, 241
Event Log ID 241
events 233, 234, 241

Printed in USA
GC30-4172-02

Events Reference PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Events Reference PDF

Hochgeladen von

Copyright:

Verfügbare Formate

© Copyright IBM Corporation 1999, 2010.

Chapter 1. Hardware platform events . . . . . . . . . . . . . . . . . . . . . . . 1

© Copyright IBM Corp. 1999, 2010 iii

Chapter 3. Sources of events in an IBM Systems Director environment . . . . . . . 235

Chapter 4. Extended details and variable-binding information . . . . . . . . . . . 237

Chapter 5. CIM indications in IBM Systems Director . . . . . . . . . . . . . . . . 241

iv IBM Systems Director Events Reference

vi IBM Systems Director Events Reference

Conventions and terminology

Note: These notices provide important tips, guidance, or advice.

Attention: These notices indicate possible damage to programs, devices, or data.

Publications and related information

Information centers and topic collections

© Copyright IBM Corp. 1999, 2010 vii

viii IBM Systems Director Events Reference

White papers and briefs

About this publication ix

IBM Redbooks® publications

x IBM Systems Director Events Reference

About this publication xi

How to send your comments

xii IBM Systems Director Events Reference

Use the following table to map event severity-level names to numbers.

© Copyright IBM Corp. 1999, 2010 1

2 IBM Systems Director Events Reference

Chapter 1. Hardware platform events 3

4 IBM Systems Director Events Reference

Chapter 1. Hardware platform events 5

6 IBM Systems Director Events Reference

Chapter 1. Hardware platform events 7

8 IBM Systems Director Events Reference

Chapter 1. Hardware platform events 9

10 IBM Systems Director Events Reference

Chapter 1. Hardware platform events 11

12 IBM Systems Director Events Reference

Chapter 1. Hardware platform events 13

14 IBM Systems Director Events Reference

Chapter 1. Hardware platform events 15

16 IBM Systems Director Events Reference

Chapter 1. Hardware platform events 17

IBM BladeCenter and System x platform-specific events

CIM > System

18 IBM Systems Director Events Reference

CIM > System > Automatic Server Restart:

No resolution. This event is informative only.

CIM > System > DASD Backplane:

where drive is the affected hard disk

CIM > System > Disk Space Low:

Chapter 1. Hardware platform events 19

where name is the affected logical drive

where name is the affected logical drive.

CIM > System > Error Log:

If the severity is Warning: Back up and clear the system-management processor

20 IBM Systems Director Events Reference

CIM > System > Fan:

where number is the affected fan sensor.

CIM > System > Host Bus Adapter:

Chapter 1. Hardware platform events 21

No resolution. This event is informative only.

CIM > System > IVM Unconfigured:

The IVM Unconfigured event occurs when an IVM becomes unconfigured.

No resolution. This event is informative only.

CIM > System > IPMI Log: