Fqo0 BK Events Ref

IBM Systems
IBM Systems Director

Events Reference
Version 6.3.0
GC30-4172-03
IBM Systems
Events Reference
Version 6.3.0
GC30-4172-03
Note
Before using this information and the product it supports, read the information in Notices on
page 289.
Copyright IBM Corporation 1999, 2011.
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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
How to send your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Chapter 1. Hardware platform events . . . . . . . . . . . . . . . . . . . . . . . 1
IBM BladeCenter and System x platform-specific events . . . . . . . . . . . . . . . . . . . . 18
CIM events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MPA events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
IBM Power platform-specific events . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Computer System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Fan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Fibre Channel Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Optical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
PCI Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Physical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
USB Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
IBM System Storage platform-specific events . . . . . . . . . . . . . . . . . . . . . . . . 150
Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
RAID Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Storage Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Storage Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Storage Volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
PET events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
PET > Environmental. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
PET > Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
PET > Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
PET > System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
SNMP events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
ibmSystemMIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
ibmSystemRaid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
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 . . . . . . . . . . . . . . . . . . . . . . . 231
Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Copyright IBM Corp. 1999, 2011 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 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 . . . . . . . . . . . . . . . . . . . . . . . 252
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. . . . . . . . . . . . . . . . . . . . . . . 256
ADPT_ArrayFlashCopyFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 256
ADPT_ArrayRebuildComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . 256
ADPT_ArrayRebuildDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . 257
ADPT_ArrayRebuildFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 257
ADPT_ArraySyncComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 257
ADPT_ArraySyncDetected CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . 258
ADPT_ArraySyncFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 258
ADPT_CompactionComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 258
ADPT_CompactionDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 259
iv IBM Systems Director Events Reference
ADPT_CompactionFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 259
ADPT_CompressionComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . 259
ADPT_CompressionDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 260
ADPT_CompressionFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 260
ADPT_ConfigFail CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
ADPT_ControllerAdded CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 261
ADPT_ControllerBadStripes CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 261
ADPT_ControllerBatteryOvertemp CIM indication . . . . . . . . . . . . . . . . . . . . . . 261
ADPT_ControllerBatteryTempNormal CIM indication . . . . . . . . . . . . . . . . . . . . . 262
ADPT_ControllerFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 262
ADPT_ControllerFailover CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 262
ADPT_ControllerMismatchedVersions CIM indication . . . . . . . . . . . . . . . . . . . . . 263
ADPT_ControllerReplaced CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . 263
ADPT_CopyBackComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 263
ADPT_CopyBackDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 264
ADPT_CopyBackFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 264
ADPT_DeadBattery CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
ADPT_DeadBatteryCache CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 265
ADPT_DecompressionComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . 265
ADPT_DecompressionDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . 265
ADPT_DecompressionFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 266
ADPT_DefunctDrive CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 266
ADPT_DefunctDriveFRU CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 266
ADPT_DefunctReplaced CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 267
ADPT_DriveAdded CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
ADPT_DriveClearComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 267
ADPT_DriveClearDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 268
ADPT_DriveClearFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 268
ADPT_DriveRemoved CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 268
ADPT_DriveVerifyComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 269
ADPT_DriveVerifyDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 269
ADPT_DriveVerifyFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 269
ADPT_EnclosureFail CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . . 270
ADPT_EnclosureFanFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 270
ADPT_EnclosureFanInstalled CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 270
ADPT_EnclosureFanOK CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 271
ADPT_EnclosureFanRemoved CIM indication . . . . . . . . . . . . . . . . . . . . . . . 271
ADPT_EnclosureOK CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . . 271
ADPT_EnclosurePowerSupplyFail CIM indication . . . . . . . . . . . . . . . . . . . . . . 272
ADPT_EnclosurePowerSupplyInstalled CIM indication . . . . . . . . . . . . . . . . . . . . 272
ADPT_EnclosurePowerSupplyOK CIM indication . . . . . . . . . . . . . . . . . . . . . . 272
ADPT_EnclosurePowerSupplyRemoved CIM indication . . . . . . . . . . . . . . . . . . . . 273
ADPT_EnclosureTempFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 273
ADPT_EnclosureTempOK CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 273
ADPT_ExpansionComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 274
ADPT_ExpansionDetected CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . 274
ADPT_ExpansionFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 274
ADPT_FlashCopyComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 275
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 . . . . . . . . . . . . . . . . . . . . . . . . 276
ADPT_LogicalDriveCritical CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 277
ADPT_LogicalDriveCriticalPeriodic CIM indication. . . . . . . . . . . . . . . . . . . . . . 277
ADPT_LogicalDriveOffLine CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 277
ADPT_LogicalDriveOK CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . 278
ADPT_LogicalDriveRemoved CIM indication. . . . . . . . . . . . . . . . . . . . . . . . 278
ADPT_LogicalDriveUnblocked CIM indication . . . . . . . . . . . . . . . . . . . . . . . 278
Contents v
ADPT_MigrationComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . 279
ADPT_MigrationDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 279
ADPT_MigrationFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 279
ADPT_NoControllers CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 280
ADPT_PFADrive CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
ADPT_PFADriveFRU CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 280
ADPT_PollingFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
ADPT_RebuildComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 281
ADPT_RebuildDetected CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 281
ADPT_RebuildFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
ADPT_SyncComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 282
ADPT_SyncDetected CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . . 282
ADPT_SyncFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
ADPT_TestEvent CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
ADPT_UnsupportedDrive CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 283
LSI_RAID_HS_Fail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
LSI_RAID_LD_Degraded CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 284
LSI_RAID_LD_Offline CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . 284
LSI_RAID_LD_Optimal CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . 285
LSI_RAID_PD_Fail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
LSI_RAID_PD_HS CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
LSI_RAID_PD_PartOf_LD_Add CIM indication . . . . . . . . . . . . . . . . . . . . . . . 286
LSI_RAID_PD_PartOf_LD_Fail CIM indication . . . . . . . . . . . . . . . . . . . . . . . 286
LSI_RAID_RbldComplete CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 286
LSI_RAID_RbldFail CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
LSI_RAID_RbldStart CIM indication. . . . . . . . . . . . . . . . . . . . . . . . . . . 287
LSI_RAID_SMART_Error CIM indication . . . . . . . . . . . . . . . . . . . . . . . . . 287
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
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
publib.boulder.ibm.com/infocenter/director/pubs/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
http://publib.boulder.ibm.com/infocenter/director/pubs/topic/extensions/
extensionparent.html
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, 2011 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://publib.boulder.ibm.com/infocenter/director/devsdk/index.jsp
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
Release Notes
6.3.3
Provides an easy reference to planning, install and troubleshooting
information for IBM Systems Director
IBM Systems Director Planning Guide
Provides planning information, including hardware requirements for
running IBM Systems Director components, supported IBM Systems
Director hardware, operating systems, databases, and workgroup and
enterprise systems-management software.
PDF files for installing IBM Systems Director Server
Provides detailed instructions to prepare for, install, and configure the IBM
Systems Director Server.
PDF files for installing IBM Systems Director agents
Provides detailed instructions to prepare for and install IBM Systems
Director agents on your managed systems, as well as, prepare for agentless
managed systems.
PDF files for upgrading and migrating IBM Systems Director Server
Provides detailed instructions to upgrade and migrate the IBM Systems
Director Server.
PDF files for upgrading and migrating IBM Systems Director agents
Provides detailed instructions to upgrade and migrate IBM Systems
Director agents.
IBM Systems Director Systems Management Guide
Provides detailed instructions for using the Web interface and managing
systems and resources in your environment.
IBM Systems Director Troubleshooting Guide
Provides information about problems and how to solve them, and
strategies for troubleshooting common problems.
IBM Systems Director Events Reference
Provides information about IBM Systems Director events, including the
event type, description, severity, and extended details.
IBM Systems Director 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.
White papers and briefs
viii IBM Systems Director Events Reference
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 Performance Tuning and Scaling Guide for IBM Systems Director 6.3
Hardware requirements for running IBM Systems Director Server
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
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
See Searching knowledge bases for more resources for further information about
IBM Systems Director.
Web resources
Listed here are the websites and information center topics that relate to IBM
Systems Director.
Websites
www.ibm.com/systems/management/director/
View the IBM Systems Director website on ibm.com
which provides links to

downloads and documentation for all currently supported versions of IBM
Systems Director.
v IBM Systems Director Downloads
About this publication ix
www.ibm.com/systems/management/director/downloads/
View the IBM Systems Director Downloads website 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 website on
ibm.com which provides links to product documentation, Redbooks, redpapers,
white papers, and learning modules that are 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/software/director/downloads/integration.html
View the IBM Systems Director Upward Integration website on ibm.com which
provides more information about IBM Systems Director upward integration
modules that are 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
https://www.ibm.com/developerworks/mydeveloperworks/wikis/
home?lang=en#/wiki/W3e8d1c956c32_416f_a604_4633cd375569/page/Best
%20Practices
View updated documentation and best practices for IBM Systems Director on
various systems.
v IBM Servers
www.ibm.com/servers/
View the IBM Servers website to learn about IBM Systems server and storage
products.
v IBM ServerProven
www.ibm.com/servers/eserver/serverproven/compat/us/
View the IBM ServerProven website to learn about hardware compatibility of
IBM System x
and BladeCenter
systems with IBM applications and

middleware, including IBM Systems Director.
Forums
v IBM Systems Director Forum (System x, System z
, Power Systems
)
www.ibm.com/developerworks/forums/forum.jspa?forumID=759
View the IBM Systems Director Forum website on ibm.com to discuss
product-related issues that pertain to IBM Systems Director, IBM Systems
Director UIMs, and IBM Systems Director extensions. This website includes a
link for obtaining the forum by using a Rich Site Summary (RSS) feed.
v IBM Systems Director 6.x SDK Forum
www.ibm.com/developerworks/forums/forum.jspa?forumID=1852&start=0
View the IBM Systems Director 6.x SDK Forum website to discuss issues that
pertain to the IBM Systems Director Software Development Kit (SDK). This
website includes a link for obtaining the forum by using a Rich Site Summary
(RSS) feed.
v IBM Systems Forums
www.ibm.com/developerworks/forums/dw_esforums.jsp
x IBM Systems Director Events Reference
View the IBM Systems Forums website on ibm.com to learn about various
forums that are available to discuss technology-related and product-related
issues that pertain to IBM Systems hardware and software products. This
website includes a link for obtaining the forum by 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
publib.boulder.ibm.com/infocenter/director/pubs/index.jsp. There you will find
the feedback page where you can enter and submit comments.
About this publication xi
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 Director 5.20 event name
IBM Systems Director 6.1 event name
Note: The name shown also is the click path to
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, 2011 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
Drive
Managed Resource > Managed System Resource >
Device > Disk Drive > RAID Subsystem
Configuration > Unsupported Drive
v CIM > System > RAID > RAID PFA Drive
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
Detected
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
Complete
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
Detected
Verify > Detected
CIM > System > RAID > RAID Drive Verify Fail Managed Resource > Managed System Resource >
Verify > Failed
CIM > System > RAID > RAID Drive Verify
Complete
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
Replaced
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
Mismatched Versions
Configuration > Mismatched Versions
v CIM > System > RAID > RAID Controller Fail
v CIM > System > RAID > RAID Polling Fail
v CIM > System > RAID > RAID Controller Bad
Stripes
RAID Controller > RAID Subsystem Operational
Condition > Failed
CIM > System > RAID > RAID Controller Failover Managed Resource > Managed System Resource >
Condition > Failover
CIM > System > RAID > RAID Test Event Managed Resource > Managed System Resource >
Condition > Test
v CIM > System > RAID > RAID Enclosure Fail
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
Critical
Critical Periodic
Drive > Critical
CIM > System > RAID > RAID Logical Drive
Blocked
Drive > Blocked
Unblocked
Drive > Unblocked
Added
Drive > Added
Removed
Drive > Removed
Off Line
Offline
Drive > Offline
CIM > System > RAID > RAID Array Rebuild
Detected
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
Complete
Rebuild > Completed
CIM > System > RAID > RAID Array Sync
Detected
Synchronization > Detected
CIM > System > RAID > RAID Array Sync Fail Managed Resource > Managed System Resource >
Synchronization > Failed
CIM > System > RAID > RAID Array Sync
Complete
Synchronization > Completed
CIM > System > RAID > RAID Migration
Detected
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
Complete
Migration > Completed
CIM > System > RAID > RAID Compression
Detected
Compression > Detected
CIM > System > RAID > RAID Compression Fail Managed Resource > Managed System Resource >
Compression > Failed
CIM > System > RAID > RAID Compression
Complete
Compression > Completed
CIM > System > RAID > RAID Decompression
Detected
Decompression > Detected
Fail
Decompression > Failed
Complete
Decompression > Completed
CIM > System > RAID > RAID FlashCopy
Detected
FlashCopy > Detected
CIM > System > RAID > RAID FlashCopy Fail Managed Resource > Managed System Resource >
FlashCopy > Failed
CIM > System > RAID > RAID FlashCopy
Complete
FlashCopy > Completed
CIM > System > RAID > RAID Compaction
Detected
Compaction > Detected
CIM > System > RAID > RAID Compaction Fail Managed Resource > Managed System Resource >
Compaction > Failed
CIM > System > RAID > RAID Compaction
Complete
Compaction > Completed
CIM > System > RAID > RAID Expansion
Detected
Expansion > Detected
CIM > System > RAID > RAID Expansion Fail Managed Resource > Managed System Resource >
Expansion > Failed
CIM > System > RAID > RAID Expansion
Complete
Expansion > Completed
CIM > System > RAID > RAID Copyback
Detected
Copyback > Detected
CIM > System > RAID > RAID Copyback Fail Managed Resource > Managed System Resource >
Copyback > Failed
CIM > System > RAID > RAID Copyback
Complete
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
v CIM > System > RAID > RAID Defunct Drive
FRU
Extent > Logical Disk > RAID Subsystem Defunct
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
v CIM > System > RAID > RAID Dead Battery
Cache
Logical Resource > Logical Device > Battery >
Operational Condition > Failed
CIM > System > RAID > RAID Controller Battery
Overtemp
Temperature > High
CIM > System > RAID > RAID Controller Battery
Temp Normal
Temperature > Normal
CIM > System > RAID > RAID Enclosure Fan
Removed
Logical Resource > Logical Device > Fan > RAID
Subsystem Life Cycle > Removed
CIM > System > RAID > RAID Enclosure Fan
Installed
Subsystem Life Cycle > Added
CIM > System > RAID > RAID Enclosure Fan Fail Managed Resource > Managed System Resource >
Subsystem Operational Condition > Failed
CIM > System > RAID > RAID Enclosure Fan OK Managed Resource > Managed System Resource >
Subsystem Operational Condition > OK
CIM > System > RAID > RAID Enclosure Temp
Fail
Logical Resource > Logical Device > Sensor >
Numeric Sensor > Temperature Sensor > High
CIM > System > RAID > RAID Enclosure Temp
OK
Numeric Sensor > Temperature Sensor > Normal
CIM > System > RAID > RAID Enclosure Power
Supply Removed
Logical Resource > Logical Device > Power
Supply > RAID Subsystem Life Cycle > Removed
Supply Installed
Supply > RAID Subsystem Life Cycle > Added
Supply Fail
Supply > RAID Subsystem Operational Condition
> Failed
Supply OK
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
Cooling
v MPA > Component > Chassis > Failed
v MPA > Component > Chassis > Cooling
Capacity
Frame > Chassis > Operational Condition >
Temperature
MPA > Component > Bus > Communication Managed Resource > Managed System Resource >
Frame > Chassis > Operational Condition > Bus
Communication Failure
MPA > Component > Chassis > Direct Serial
Attach Module > Disabled
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 >
Insufficient Power
v MPA > Component > Blade Server > Over
Power Budget
Operational Condition > Power State Changed
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 >
Communication
Operational Condition > Communication Error
MPA > Component > Blade Server > Capacity on
Demand
Capacity On Demand > Activated
MPA > Component > Service Processor >
Removed
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
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 >
Mismatch
Duplicate IP Address
Configuration
Communication
Operational Condition > Blade Server Baseboard
Management Controller (BMC) Communication
Error
Failover
v MPA > Component > Service Processor > Active
Inactive
Operational Condition > Failover
Redundancy
Operational Condition > Redundancy
MPA > Component > Service Processor > Test Managed Resource > Managed System Resource >
Operational Condition > Test
v CIM > System > IPMI Log
v MPA > Component > Service Processor > Log
Hardware Log > Threshold
Out-of-Band > Enabled
Out-Of-Band Connection > Activated
Out-of-Band > Disabled
Out-Of-Band Connection > Deactivated
Out-of-Band > Port
Out-Of-Band Connection > Port Changed
MPA > Component > Service Processor > Secure
Out-of-Band > Enabled
Secure Out-Of-Band Connection > Activated
Out-of-Band > Disabled
Secure Out-Of-Band Connection > Deactivated
Out-of-Band > Port
Secure Out-Of-Band Connection > Port Changed
MPA > Component > Service Processor > User
Account > Inactive
User Account > Deactivated
MPA > Component > Service Processor > User
Account > Active
User Account > Activated
Password > Change Required
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 >
Disabled
Server > Operational Condition > SMP Expansion
Module Disabled
v CIM > System > PFA
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
Module > Removed
Logical Resource > Logical Device > Logical
Module > Multiplexer Card Module > Life Cycle
> Removed
Module > Inserted
Module > Multiplexer Card Module > Life Cycle
> Added
Module > Failed
Module > Multiplexer Card Module > Operational
Condition > Failed
MPA > Component > Alarm Panel > Removed Managed Resource > Managed System Resource >
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 >
Off
Module > Clock Module > Power > Off
MPA > Component > Clock Module > Power >
On
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
Module > Baggage Cart Module > Life Cycle >
Removed
Attach Module > Inserted
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) >
MPA > Component > Media Tray > Failed Managed Resource > Managed System Resource >
Module > Media Tray Module > Operational
Condition > Failed
MPA > Component > Media Tray > Temperature
Unavailable
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
v MPA > Component > CPU > Absent
MPA > Component > CPU > Failed Managed Resource > Managed System Resource >
CIM > System > Processor PFA Managed Resource > Managed System Resource >
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 >
Off
v MPA > Component > I/O Module > Power >
Timeout
Switch > Power > Off
MPA > Component > I/O Module > Power > On Managed Resource > Managed System Resource >
Switch > Power > On
MPA > Component > I/O Module >
Configuration
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 >
Disabled
Switch > Operational Condition > Not Recognized
v MPA > Component > I/O Module > Insufficient
Power
v MPA > Component > I/O Module > Fuse
v MPA > Component > I/O Module > Over
Current

Switch > Operational Condition > Power State
Changed
v MPA > Component > I/O Module > Failed
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 >
Activated
v MPA > Component > I/O Module > Stacking >
Deactivated
Switch > Operational Condition > Stacking
MPA > Component > I/O Module > Zoning Managed Resource > Managed System Resource >
Switch > Operational Condition > Zoning
MPA > Component > I/O Module >
Communication
Switch > Operational Condition > Communication
Error
v MPA > Component > Fan > Removed
v MPA > Component > Fan Pack > Removed
Logical Resource > Logical Device > Fan > Life
Cycle > Removed
v MPA > Component > Fan > Inserted
v MPA > Component > Fan Pack > Inserted
Logical Resource > Logical Device > Fan > Life
Cycle > Added
MPA > Component > Fan > Configuration Managed Resource > Managed System Resource >
Logical Resource > Logical Device > Fan >
CIM > System > Fan Managed Resource > Managed System Resource >
Operational Condition > Threshold
v MPA > Component > Fan > Failed
v MPA > Component > Fan Pack > Failed
v MPA > Component > Fan > PFA
v MPA > Component > Fan Pack > PFA
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
v CIM > System > SMART Drive
v MPA > Component > DASD > Failed
Failed
MPA > Component > DASD > PFA Managed Resource > Managed System Resource >
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 >
Supply > Life Cycle > Removed
MPA > Component > Power Supply > Inserted Managed Resource > Managed System Resource >
Supply > Life Cycle > Added
v MPA > Component > Power Supply >
Configuration
v MPA > Component > Power Supply > Absent
Supply > Operational Condition > Configuration
Error
v CIM > System > Power Supply
v MPA > Component > Power Supply > Failed
Supply > Operational Condition > Failed
MPA > Component > Power Supply > PFA Managed Resource > Managed System Resource >
Supply > Operational Condition > Predictive
Failure Analysis (PFA)
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
Interposer > Removed
Physical Resource > Physical Connector >
ManagementModule > Life Cycle > Removed
MPA > Component > Management Module
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
v MPA > Component > Storage Module >
Insufficient Cooling
v MPA > Component > Storage Module >
Insufficient Power
Storage Subsystem > Operational Condition >
Failed
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
Power
Logical Resource > System > Administration
Domain > Power Domain > Operational
Condition > Power Exceeded
Current
Condition > Over Current
MPA > Component > Power Subsystem > Low
Fuel
Condition > Low Fuel
Subscription
Condition > Over Power Subscription
MPA > Component > Power Subsystem >
Mismatched Power Supplies
Condition > Configuration Error
MPA > Component > Power Subsystem >
Redundancy
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
Failover
SwitchBack
SwitchOver
(NIC) Failover
MPA > Component > Blade Expansion Unit >
Failed
Physical Resource > Physical Package > Blade
Expansion Unit > Operational Condition > Blade
Expansion Unit Failed
v CIM > System > Voltage
v MPA > Environmental > Voltage
Numeric Sensor > Voltage Sensor > Out Of Range
v CIM > System > Temperature
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 applicable Not applicable None
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
applicable
Not
applicable
None
Note: IBM Systems Director supports only the following sensors for Platform
Agent managed operating systems:
v Ambient Temp
v CPU 1-2
v DIMM 1-16
v Fan 1-4 Tach
v Planar 12V, 3.3V, 5V, and VBAT
v Power Supply 1-2
v PCH Temp
v Riser 1A-2A Temp
v Zone 1-2 Temp
v Mezz Card Temp
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
Event type Event text Severity Category
Additional
extended
details
Automatic
Server Restart
The last system restart was due to the
automatic server restart hardware.
Warning Alert None
Automatic
Server Restart
The last system restart was not due to
the automatic server restart hardware.
Informational Resolution None
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
details
DASD
Backplane
Drive drive has reported a fault. This
event must be cleared manually.
where drive is the affected hard disk
drive.
Critical Alert None
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 details
Disk Space Low Logical drive
name fell below
threshold 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.
Critical Alert None
Additional
extended details
name fell below
threshold of
threshold MB.
The current
value is value
MB.
where:
v name is the
affected
logical drive.
v threshold is the
warning
threshold
value.
v value is the
amount of
current disk
space
available.
Warning Alert None
name free space
is normal. The
current value is
value MB.
where name is
the affected
logical drive and
value is the
amount of
current disk
space available.
name status
could not be
determined.
where name is
the affected
logical drive.
Unknown Resolution None
CIM > System > Event Log:
The Event 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 details
Event Log The system
management
processor error
log is 75% full.
This event must
be cleared
manually.
Warning Alert None
Event Log The system
management
processor error
log is full. This
event must be
cleared
manually.
Warning Alert None
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
details
Fan Fan Sensor number fell below threshold
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.
Critical Alert None
Fan Fan Sensor number reports normal.
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
has changed.
where number identifies the HMC.
Informational Alert
v Description indicates the
type of event.
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
details
IPMI Log The system management processor error
log is 75% full. This event must be
cleared manually.
Warning Alert None
IPMI Log The system management processor error
log is full. This event must be cleared
manually.
Warning Alert None
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.
Lease Expiration The lease on system has expired. It expired
on date.
where system is the affected system and date
is the lease expiration date.
Warning Alert None
Lease Expiration The lease on system is normal. It will expire
on 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
details
Life Cycle LPAR name has been created.
where name identifies the LPAR created.
Minor Alert LifeCycleEvent indicates
whether the CEC was
added or removed from
management by the HMC.
Life Cycle LPAR name has been deleted.
where name identifies the deleted LPAR.
whether the CEC was
Life Cycle CEC cec is now managed by HMC hmc.
where cec identifies the CEC and hmc identifies the
HMC.
whether the CEC was
Life Cycle CEC cec is no longer managed by HMC hmc.
where cec identifies the CEC and hmc identifies the
HMC.
whether the CEC was
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
Memory Memory configuration reduced from
previous MB to current MB.
where previous is the previous memory size
and current is the current memory size.
Critical Alert None
Memory Memory configuration increased from
previous MB to current MB.
where previous is the previous 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
Memory PFA Memory device identified as memory in
bank slot is predicting an imminent failure.
where slot is the affected memory slot.
Critical Alert None
Memory PFA Memory device identified as memory in
bank slot is not predicting a failure.
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 Minor: 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
details
Network Adapter Not applicable Not
applicable
Not
applicable
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.
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.
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.
information that can help
resolve a hardware
Offline The network adapter is offline. Minor Alert
instance.
resolve a hardware
Online The network adapter is online. Informational Resolution
instance.
resolve a hardware
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
details
PFA Predictive Failure Detected. Please check
the system management processor error
log for more information. This event
must be cleared manually.
Critical Alert None
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
details
Power State LPAR name has been powered on.
where name identifies the affected LPAR.
Minor Alert PowerState identifies the
power state of the system
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.
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 on.
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
details
Power State CEC name has been powered off.
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
Power Supply PowerSupply device identified as
PowerSupply number reports critical state
with possible loss of redundancy.
where number is the affected power supply.
Critical Alert None
PowerSupply number has failed. This event
Critical Alert None
PowerSupply number has lost AC power
and loss of standby power is imminent.
Warning Alert None
PowerSupply number reports normal.
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
Processor Processor configuration reduced from
previous CPU to current CPU.
where previous is the previous number of
microprocessors (CPUs) and current is the
current number of microprocessors.
Critical Alert None
Processor Processor configuration increased from
previous CPU to current CPU.
where previous is the previous 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 details
Processor PFA Processor device
identified as
processor in slot
slot is predicting
an imminent
failure.
where slot is the
affected
processor slot.
Critical Alert None
Processor PFA Processor device
identified as
processor in slot
slot is not
predicting a
failure.
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
applicable
Not
applicable
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 extended
details
RAID Array FlashCopy
Complete
FlashCopy with backup complete: array.
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
RAID Array
FlashCopy
Detected
FlashCopy in progress: array.
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
Additional
extended details
RAID Array
FlashCopy Fail
FlashCopy with
backup failed:
array [error]
where array is
the affected
array and error is
the error code.
Critical Alert None
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 Array
Rebuild
Complete
Rebuild complete: array
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 Array
Rebuild
Detected
Rebuilding: array
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
Additional
extended details
RAID Array
Rebuild Fail
Rebuild failed:
array [error]
where array is
the affected
array and error is
the error code.
Critical Alert None
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 Array
Sync
Complete
Synchronize complete: array
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 Array
Sync
Detected
Synchronizing: array
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
Sync Fail
Synchronize failed: array [error]
where array is the affected array and error is the
error code.
Critical Alert None
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
Compaction complete: drive
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
Compaction
Detected
Compacting: 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
details
RAID Compaction
Fail
Compaction failed: drive [error]
where drive is the affected logical
drive and error is the error code.
Critical Alert None
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
Compression complete: drive
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
Compression
Detected
Compressing: drive
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
Fail
Compression failed: drive [error]
where drive is the affected logical drive and error is
the error code.
Critical Alert None
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 Config
Fail
Error getting controller configuration. Critical Alert None
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
Controller
Added
A controller has been added to the system:
controller.
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
Controller Bad
Stripes
One or more logical drives contain a bad stripe:
controller.
where controller is the controller for the affected
logical drives.
Warning Alert None
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
Controller
Battery
Overtemp
The battery has exceeded normal operating
temperature: controller.
where controller is the affected controller.
Warning Alert None
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
Controller
Battery
Temp
Normal
The battery operating temperature is normal:
controller.
CIM > System > RAID > RAID Controller Fail:
The RAID Controller Fail event occurs when a specified RAID controller fails. This
Resolution
Details
RAID
Controller Fail
Commands are not responding: controller.
Critical Alert None
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
Controller
Failover
A controller failover was detected: controller.
where controller is the controller that failed.
Critical Alert None
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
Controller
Mismatched
Versions
Version mismatch detected: controller. The BIOS
(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.
Warning Alert None
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
Controller
Replaced
A controller has been replaced in the system:
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
Copyback
Complete
Copy back complete: location.
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
Copyback
Detected
Copy back in progress: location. Source: Channel
channel, 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
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
Copyback Fail
Copy back failed: location [error].
where location is the affected controller and array
and error is the error code.
Critical Alert None
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
Battery
The battery-backup cache device needs a new
battery: controller.
Critical Alert None
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
Battery Cache
The battery-backup cache device is defective:
controller. Error code: error.
where controller is the affected controller and error
is the error code.
Critical Alert None
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
RAID
Decompression
Complete
Decompression complete: 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
RAID
Decompression
Detected
Decompressing: drive.
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
Fail
Decompression failed: drive [error].
the error code.
Critical Alert None
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
Defunct drive: location.
where location is the affected controller and port.
Critical Alert None
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 FRU
Defunct drive: location (FRU Part # FRU).
where location is the affected controller and port
and FRU is the FRU number of the hard disk
drive.
Critical Alert None
RAID Defunct
Drive FRU
Defunct drive - I/O subsystem error: location (FRU
Part # FRU).
and FRU is the FRU number of the hard disk
drive.
Critical Alert None
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
Defunct
Replaced
A drive is set to hot-spare: location (error).
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
RAID Drive
Added
Physical drive added: location.
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
RAID Drive
Clear
Complete
Clear complete: drive.
where drive is the affected hard disk 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
attributes
RAID Drive
Clear
Detected
Clearing: 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 Fail
Clear failed: drive [error].
where drive is the affected hard disk drive and
error is the error code.
Critical Alert None
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
RAID Drive
Removed
Physical drive removed: location.
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
RAID Drive
Verify
Complete
Verify 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 Drive
Verify
Detected
Verifying: 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 Fail
Verify failed: drive.
Critical Alert None
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 Fail
Enclosure device is not responding: location.
where location is the controller and channel that
the affected enclosure is attached to.
Critical Alert None
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
Fail
Enclosure fan fan is malfunctioning: location.
where fan is the affected fan and location is the
controller and channel that the affected enclosure
is attached to.
Critical Alert None
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.
RAID
Enclosure Fan
Installed
Enclosure fan fan has been installed: location.
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
RAID
Enclosure Fan
OK
Enclosure fan fan is now operational: location.
attached to.
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
Removed
Enclosure fan fan has been removed: location.
controller and channel that the affected enclosure
is attached to.
Warning Alert None
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
RAID
Enclosure OK
Enclosure device is responding: location.
where location is the controller and channel that the
affected enclosure is 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
Fail
Enclosure power supply supply is malfunctioning:
location.
where supply is the affected power supply and
location is the controller and channel that the
Critical Alert None
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
Additional extended
attributes
RAID
Enclosure
Power
Supply
Installed
Enclosure power supply supply has been installed:
location.
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
RAID
Enclosure
Power Supply
OK
Enclosure power supply supply is now operational:
location.
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
Removed
Enclosure power supply supply has been removed:
location.
Warning Alert None
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
Temp Fail
Enclosure temperature is out of the normal range:
location.
where location is the controller and channel that
the affected enclosure is attached to.
Critical Alert None
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
RAID
Enclosure
Temp OK
Enclosure temperature is in the normal range:
location.
CIM > System > RAID > RAID Expansion Complete:
The RAID Expansion Complete event occurs when a RAID expansion operation is
Resolution
Details
Additional extended
attributes
RAID
Expansion
Complete
Expansion complete: drive.
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
Expansion
Detected
Expanding: drive.
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 Fail
Expansion failed: drive [error].
the error code.
Critical Alert None
CIM > System > RAID > RAID > FlashCopy Complete:
The RAID FlashCopy Complete event occurs when a RAID FlashCopy operation is
Resolution
Details
RAID
FlashCopy
Complete
FlashCopy with backup complete: drive.
CIM > System > RAID > RAID > FlashCopy Detected:
The RAID FlashCopy Detected event occurs when a RAID FlashCopy operation is
Resolution
Details
RAID
FlashCopy
Detected
FlashCopy in progress: drive.
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 Fail
FlashCopy with backup failed: drive [error].
the error code.
Critical Alert None
CIM > System > RAID > RAID Init Complete:
The RAID Init Complete event occurs when a RAID initialization operation is
Resolution
Details
RAID Init
Complete
Clear complete: drive.
CIM > System > RAID > RAID Init Detected:
The RAID Init Detected event occurs when a RAID initialization operation is in
Resolution
Details
RAID Init
Detected
Clearing: drive.
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 Fail Initialize failed: drive.
Critical Alert None
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
RAID Logical
Drive Added
Added logical drive: drive. Size data.
where drive is the affected logical drive 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 Blocked
Logical drive is blocked: drive.
Critical Alert None
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 Critical
Logical drive is critical: drive.
Warning Alert None
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 Logical
Drive Critical
Periodic
Periodic scan found one or more critical logical
drives: drive. Repair as soon as possible to avoid
data loss.
Warning Alert None
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 Off Line
Logical drive is offline: drive.
Critical Alert None
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
attributes
RAID Logical
Drive OK
Logical drive is normal: 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
RAID Logical
Drive
Removed
Deleted logical drive: drive.
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
attributes
RAID Logical
Drive
Unblocked
Unblocked logical drive: drive.
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
RAID
Migration
Complete
Migration complete: drive.
CIM > System > RAID > RAID Migration Detected:
The RAID Migration Detected event occurs when a RAID logical-drive migration is
Resolution
Details
Additional extended
attributes
RAID
Migration
Detected
Migrating: drive.
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 Fail
Migration failed: drive [error].
the error code.
Critical Alert None
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
attributes
RAID No
Controllers
No controllers were found in this system Informational Resolution None
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
Drive
PFA detected for drive: drive.
Warning Alert None
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
Drive FRU
PFA detected for drive: drive (FRU).
where drive is the affected hard disk drive and
FRU is the FRU number of that drive.
Warning Alert None
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 Polling
Fail
Background polling commands are not
responding: controller. Result codes: error.
where controller is the affected controller and error
is the error code.
Warning Alert None
CIM > System > RAID > RAID Rebuild Complete:
The RAID Rebuild Complete event occurs when a RAID rebuild operation is
Resolution
Details
RAID Rebuild
Complete
Rebuild complete: drive.
CIM > System > RAID > RAID Rebuild Detected:
The RAID Rebuild Detected event occurs when a RAID rebuild operation is in
Resolution
Details
RAID
Rebuild
Detected
Rebuilding: drive.
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
Fail
Rebuild failed: drive [error].
the error code.
Critical Alert None
CIM > System > RAID > RAID Sync Complete:
The RAID Sync Complete event occurs when a RAID synchronization operation is
Resolution
Details
Additional extended
attributes
RAID Sync
Complete
Synchronize complete: drive.
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
RAID Sync
Detected
Synchronizing: drive.
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 Fail Synchronize failed: drive [error].
the error code.
Critical Alert None
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
attributes
RAID Test
Event
This is a test event. Informational Alert None
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
Unsupported
Drive
Possible non-warranted physical drive found:
drive.
Warning Alert None
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
details
Redundant
Network
Adapter
Failover
A network interface card (NIC) failover
has occurred. This requires a teamed
configuration.
Warning Alert None
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
details
Redundant
Network
Adapter
Switchback
Onboard NIC has Switched Back Normal Alert None
Redundant
Network
Adapter
Switchback
NIC in PCI Bus bus Slot slot has
Switched Back
where bus is the affected bus and slot is
the affected slot.
Normal Alert None
Redundant
Network
Adapter
Switchback
NIC in PCI Slot slot has Switched Back
where slot is the affected slot.
Normal Alert None
Redundant
Network
Adapter
Switchback
NIC has Switched Back Normal Alert None
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
details
Redundant
Network
Adapter
Switchover
Onboard NIC has Switched Over Minor Alert None
Redundant
Network
Adapter
Switchover
Switched Over.
where bus is the affected bus and slot is
the affected slot.
Minor Alert None
Redundant
Network
Adapter
Switchover
NIC in PCI Slot slot has Switched Over.
Minor Alert None
Redundant
Network
Adapter
Switchover
NIC has Switched Over Minor Alert None
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 details
Remote Login The system
management
processor has
been accessed
via a remote
login. This event
must be cleared
manually.
Warning Alert None
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
Server Power Supply PowerSupply device identified as
PowerSupply number reports critical state
with possible loss of redundancy.
Critical Alert None
PowerSupply number has failed. This event
Critical Alert None
PowerSupply number has lost AC power
and loss of standby power is imminent.
Warning Alert None
PowerSupply number reports normal.
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
.
Note: The Create Serviceable Event task on an HMC will not send an event to the
Director Management server. If the event is not related to any Central Electronics
Complex (CEC) or logical partition, the HMC CIM does not respond with the
event notification. The event will not be sent to any CIM client application. When
creating a serviceable event on the HMC, it is a simulated event that is not related
to a CEC or logical partition.
Details
Service Event Note: This text varies depending on the
Service Event that is received on the HMC.
The provided text is a description of that
Service Event occurrence.
Warning Alert None
Service Event that is received on the HMC.
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
SMART Drive Device device identified as physical drive
drive is predicting an imminent failure.
where Device is IDE, SCSI, or Unknown and
drive is the affected SMART drive.
Critical Alert None
SMART Drive Device device identified as physical drive
drive is not predicting a failure.
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
System Enclosure System Enclosure Sensor reported intrusion
detection.
Critical Alert None
System Enclosure System Enclosure Sensor reports normal. Informational Resolution None
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
details
System Event Note: This text varies depending on the error that
has occurred on the AIX managed object. The
provided text is a description of that System Event
occurrence.
Varies
depending
on the error.
Alert None
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 details
Temperature Temperature
Sensor number
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.
Critical Alert None
Sensor number
exceeded the
user defined
threshold of
threshold Celsius.
The current
value is current
Celsius.
where:
v number is the
affected
temperature
sensor.
v threshold is the
user-defined
threshold
value.
v current is the
current
temperature
reading.
Critical Alert None
Additional
extended details
Sensor number
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.
Warning Alert None
Sensor number
exceeded the
user defined
threshold of
threshold Celsius.
The current
value is current
Celsius.
where:
v number is the
affected
temperature
sensor.
v threshold is the
user-defined
threshold
value.
v current is the
current
temperature
reading.
Warning Alert None
Sensor number
reports normal.
where number is
the affected
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
Voltage Voltage Sensor number fell below 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.
Critical Alert None
Voltage Voltage Sensor number exceeded threshold
of threshold Volts. The current value is
current Volts.
where:
Critical Alert None
Voltage Voltage Sensor number reports normal.
where number is the affected 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.
Warranty Expiration The warranty on system has expired. It
expired on date.
is the warranty expiration date.
Warning Alert None
Warranty Expiration The warranty on system is normal. It will
expire on 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
applicable
Not
applicable
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
applicable
Not
applicable
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
applicable
Not
applicable
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 was
inserted.
Informational Alert None
Power Not applicable Not applicable Not
applicable
None
Power > Off An alarm panel module was
powered off.
Warning Alert None
Power > On An alarm panel module was
powered on.
Removed An alarm panel module was
removed.
Warning Alert None
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
applicable
Not
applicable
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 was
detected.
Critical Alert Component indicates the affected BladeCenter
Expansion Module.
Failed A RAID battery has recovered
from a failure.
Informational Resolution Component indicates the affected BladeCenter
Expansion Module.
Failed A SAS switch module battery
backup unit failure was
detected.
Critical Alert Component indicates the affected SAS switch
module.
Failed A SAS switch module battery
backup unit has recovered from
a failure condition.
Informational Resolution Component indicates the affected SAS switch
module.
Installed A SAS switch module battery
backup unit has been installed.
Warning Alert Component indicates the affected SAS switch
module.
Removed A SAS switch module battery
backup unit was removed or is
not present.
module.
Unreliable The system clock battery is
unreliable.
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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the BIOS
Corrupted The primary BIOS is corrupted.
The system will attempt to start
using the backup BIOS.
Warning Alert None
Corrupted The BIOS is no longer
corrupted.
Failed The IPMI BIOS has failed due
to unspecified errors. You must
manually clear this event.
Critical Alert None
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 Expansion
Unit
Not applicable Not
applicable
Not
applicable
None
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 failure
was detected.
Critical Alert None
Failed A blade expansion unit 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
> 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.
Event type Severity
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
applicable
Not
applicable
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
Demand
Not applicable Not
applicable
Not
applicable
None
Capacity on
Demand >
Enabled
A blade server with a Standby
Capacity on Demand feature
was enabled.
Communication The management module failed
to communicate with a blade
server.
Critical Alert Unit identifies the affected blade server.
Communication The management module
successfully communicated
with a blade server after a
previous failure.
Informational Resolution Unit identifies the affected blade server.
Incompatible A blade server is incompatible
with the chassis.
Incompatible A blade server compatibility
issue has been resolved.
Inserted A blade server was inserted. Informational Alert Unit identifies the affected blade server.
Insufficient Power A blade server cannot power on
because there is insufficient
power.
Insufficient Power A blade server has sufficient
power to power on.
Over Power
Budget
The management module
instructed a blade server to
power off because it exceeded
the power budget.
Minor Alert Unit identifies the affected blade server.
Over Power
Budget
A blade server was allowed to
power on because it no longer
exceeds the power budget.
Removed A blade server was removed. Warning Alert Unit identifies the affected blade server.
Throttled A blade server is throttled. Informational Alert Unit identifies the affected blade server.
Throttled A blade server is no longer
throttled.
VPD The blade server vital product
data (VPD) could not be read.
The blade server will not be
allowed to power on.
VPD The blade server vital product
data (VPD) was 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
applicable
Not
applicable
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
Communication A failure occurred while
attempting to communicate
with a device.
Critical Alert Bus identifies the affected bus.
Communication Successfully communicated
with a device after a previous
failure.
Informational Resolution Bus identifies the affected bus.
Communication One or more blades are isolated
from the management bus.
Critical Alert Bus identifies the affected bus.
Communication One or more blades are no
longer isolated from the
management bus.
Informational Resolution Bus identifies the affected 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
Module > Inserted
Direct Serial Attach
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
applicable
Not
applicable
v Issue is one of the following strings:
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 inserted
into a bay that is not receiving
power.
Note: The Configuration events
occur when a management
module detects that the state of
a BladeCenter chassis
configuration has changed.
Minor Alert
v Issue is set to blade_power.
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
supplies 1 and 2 provide power to the first
domain; Power supplies 3 and 4 provide
power to the second domain.
Configuration A chassis configuration issue
was resolved.
Informational Resolution
v Issue is set to blade_power.
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
supplies 1 and 2 provide power to the first
domain; Power supplies 3 and 4 provide
power to the second domain.
Configuration A blade server is not
compatible with the I/O
module configuration.
Minor Alert
v Component is set to processor_blade.
v Unit identifies the affected blade server.
was resolved.
v Component is set to processor_blade.
v Unit identifies the affected blade server.
Configuration An I/O module is not
compatible with the blade
server configuration.
Minor Alert
v Component is set to switch_module.
v Unit identifies the affected I/O module.
compatible with the
management module
configuration.
Minor Alert
was resolved.
compatible with the storage
module configuration.
Minor Alert
v Component is set to switch_to_storage.
was resolved.
v Component is set to switch_to_storage.
Cooling Capacity Chassis cooling capacity is
reduced and insufficient to
support blade operations.
Blades will be shutdown.
Critical Alert None
Cooling Capacity Chassis cooling capacity is
reduced. Loss of an additional
chassis cooling device will
cause blades to shutdown.
Warning Alert None
Cooling Capacity Chassis cooling is now
sufficient to support blade
operations.
Direct Serial
Attach Module >
Inserted
A Direct Serial Attach Module
has been inserted.
Informational Alert
Direct Serial
Attach Module >
Removed
A Direct Serial Attach Module
has been removed.
Warning Alert
Failed There are no working fans. Critical Alert Issue is set to no_fans.
Failed All power supplies have
exceeded the temperature
thresholds and the fans are
running at full speed.
Critical Alert Issue is set to all_ps_over_temp.
Maximum
Cooling
The ambient temperature
cannot be read. Blowers will
run at full speed.
Warning Alert None
Maximum
Cooling
The ambient 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
applicable
Not
applicable
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 inserted. Informational Alert Unit identifies the affected clock module.
Power Not applicable Not
applicable
Not
applicable
None
Power > Off A clock module was powered
off.
Warning Alert Unit identifies the affected clock module.
Power > On A clock module was powered
on.
Informational Alert Unit identifies the affected clock module.
Removed A clock module was removed. Warning Alert Unit identifies the affected clock 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
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 KVM Not applicable Not
applicable
Not
applicable
None
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 failure
was detected.
Critical Alert None
Failed A concurrent KVM card has
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
applicable
Not
applicable
Unit identifies the affected microprocessor.
You can choose to select specific event types that are displayed under the CPU
Absent No CPUs were detected in a
system.
Critical Alert Unit identifies the affected microprocessor.
Configuration The CPU configuration
prohibits CPU from operating
at maximum speed.
Warning Alert Unit identifies the affected microprocessor.
Configuration The CPU configuration no
longer prohibits CPU from
operating at maximum speed.
Informational Resolution Unit identifies the affected microprocessor.
Configuration The CPU configuration is
invalid.
Configuration The CPU configuration is valid. Informational Resolution Unit identifies the affected microprocessor.
Configuration A CPU mismatch was detected. Critical Alert Unit identifies the affected microprocessor.
Configuration No CPU mismatches were
detected.
Failed A CPU fault occurred. Critical Alert Unit identifies the affected microprocessor.
Failed A CPU internal error was
detected and the CPU has been
disabled. The system has been
restarted.
Failed A CPU has been disabled due
to unspecified errors. You must
detected, probably due to a bus
timeout. The system has been
restarted. You must manually
clear this event.
detected and the CPU has been
disabled. The system has been
clear this event.
detected. The system has been
clear this event.
Failed A CPU is now operating
normally.
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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the DASD
Configuration The hard disk drive
configuration is invalid.
Critical Alert None
Configuration The hard disk drive
configuration is valid.
Failed A hard disk drive has failed. Minor Alert
v SCSI ID identifies the target hard 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 failed.
You must manually clear this
event.
Critical Alert
by SCSI ID.
physical location.
Failed A hard disk drive is now
operating normally.
by SCSI ID.
physical location.
Inserted A hard disk drive was inserted. Informational Resolution
by SCSI ID.
physical location.
PFA A hard disk drive PFA
condition was detected.
Critical Alert
by SCSI ID.
physical location.
PFA A hard disk drive has recovered
from a PFA condition.
by SCSI ID.
physical location.
Removed No Hot Spare Drive is detected
on a blade server.
Warning Alert
by SCSI ID.
physical location.
Removed A hard disk drive was
removed.
Warning Alert
by SCSI ID.
physical location.
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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the DIMM
Absent No memory modules were
detected in a blade server.
Critical Alert None.
Disabled A memory device has been
disabled.
Warning Alert Unit identifies the affected DIMM.
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
correctable ECC error.
Minor Alert Unit identifies the affected DIMM.
Failed A DIMM has generated a PFA
alert.
Minor Alert Unit identifies the affected DIMM.
Failed An error has occurred due to
an invalid DIMM configuration.
Critical Alert Unit identifies the affected DIMM.
Failed A DIMM has exceeded a critical
temperature threshold.
Critical Alert Unit identifies the affected DIMM.
Failed A DIMM has recovered from a
previous error.
Informational Resolution Unit identifies the affected DIMM.
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 Card Not applicable Not
applicable
Not
applicable
None
Expansion Card node in the Event Filter Builder tree. The event filter will process
Failed A high-speed expansion card
failure was detected.
Critical Alert None
Failed A high-speed expansion 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
applicable
Not
applicable
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 not
valid.
Critical Alert None
Configuration The fan configuration is valid. Informational Resolution None
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
Failed A fan is now functioning
correctly.
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.
Inserted A fan was inserted. Informational Resolution Unit identifies the affected fan.
PFA A PFA alert associated with a
fan occurred.
Warning Alert Unit identifies the affected fan.
PFA A fan is now functioning
correctly.
Informational Resolution Unit identifies the affected fan.
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
applicable
Not
applicable
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 functioning
correctly.
Informational Resolution Unit indicates the affected fan pack.
Inserted A fan pack was inserted. Informational Alert Unit indicates the affected fan pack.
PFA A fan pack has generated a
Predictive Failure Analysis
(PFA) alert.
Warning Alert Unit indicates the affected fan pack.
PFA A fan pack is now functioning
correctly.
Informational Resolution Unit indicates the affected fan pack.
Removed A fan pack was removed. Warning Alert Unit indicates the affected fan pack.
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
applicable
Not
applicable
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 not
connected to the system board.
Critical Alert None
Failed The front panel cable is
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
applicable
Not
applicable
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 board
Critical Alert None
Failed A blade-server I/O board has
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 Interposer Not applicable Not
applicable
Not
applicable
None
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 module was
inserted.
Informational Alert Unit identifies the affected I/O interposer.
Removed An I/O interposer module was
removed.
Warning Alert Unit identifies the affected I/O 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 >
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
applicable
Not
applicable
Unit identifies the affected I/O module.
Communication The SAS I/O module TCP
connection to the AMM has
been lost.
Critical Alert Unit identifies the affected I/O module.
Communication The SAS I/O module TCP
connection to the AMM has
been restored.
Informational Resolution Unit identifies the affected I/O module.
Configuration The I/O module IP
configuration changed.
Informational Alert
v IP Address 1 is the IP address being used by
the BladeCenter I/O module.
Configuration The I/O module NAT
configuration was activated.
Informational Alert
Configuration The I/O module NAT
configuration was activated
with IP filter rules.
Informational Alert
Configuration An I/O module has enabled
Protected Mode control of IP
configuration.
Informational Alert Unit identifies the affected I/O module.
Protected Mode control of
external ports.
Protected Mode control of
external management.
Protected Mode control of reset
configuration to defaults.
Protected Mode control without
the Management Module's
permission.
Warning Alert Unit identifies the affected I/O module.
Configuration An I/O module's Protected
Mode permission and MM
configured permission are
mismatched.
Failed An I/O module has failed. Critical Alert Unit identifies the affected I/O module.
Failed An I/O module recovered from
a failure.
Fuse An I/O module fuse is open.
Power redundancy has been
lost for this module.
Fuse An I/O module fuse is no
longer open.
Inserted An I/O module was inserted. Informational Alert Unit identifies the affected I/O module.
Insufficient Power An I/O module cannot power
on because there is insufficient
power.
Insufficient Power An I/O module has sufficient
power to power on.
Mismatch An I/O module mismatch was
detected.
Minor Alert Unit identifies the affected I/O module.
Mismatch An I/O module mismatch has
been resolved.
Over Current A monitored current has
exceeded the rating of the I/O
module.
Over Current A monitored current is now
below the rating of the I/O
module.
POST I/O module POST completed
with errors.
without errors after a previous
failure.
POST I/O module POST timed out. Critical Alert Unit identifies the affected I/O module.
after a previous timeout.
Power Not applicable Not
applicable
Not
applicable
Unit identifies the affected I/O module.
Power > Disabled Power has been denied to an
I/O module because it cannot
be identified.
Power > Off An I/O module was powered
off.
Power > On An I/O module was powered
on.
Power > Timeout An I/O module powerdown
request timed out.
Redundancy I/O module redundancy was
lost.
Minor Alert Unit identifies the affected I/O module.
Redundancy I/O module redundancy was
restored.
Removed An I/O module was removed. Warning Alert Unit identifies the affected I/O module.
Stacking >
Activated
Switch stacking has been
activated on an I/O module.
Stacking >
Deactivated
Switch stacking has been
deactivated on an I/O module.
Zoning The SAS I/O module zone
configuration has been
changed. You must manually
clear this event.
Zoning All zoning has been disabled
for a SAS I/O module. You
must manually clear this event.
Zoning No active zone configuration
found for a SAS I/O module.
event.
Zoning An attempt to change the SAS
I/O 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
Module
Interposer
Not applicable Not
applicable
Not
applicable
None
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
interposer was inserted.
Informational Alert Unit identifies the affected management
module interposer.
Removed A management module
interposer module was
removed.
Warning Alert Unit identifies the affected management
module interposer.
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
Unavailable
v If the severity is Critical: Replace the specified media tray.
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
applicable
Not
applicable
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
detected.
Critical Alert Unit identifies the affected media tray.
Temperature
Unavailable
The media tray temperature
cannot be read.
Warning Alert Unit identifies the affected media tray.
Temperature
Unavailable
The media tray temperature can
now be read.
Informational Resolution Unit identifies the affected media tray.
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
Expansion
Module
Not applicable Not
applicable
Not
applicable
None
Multiplexer Expansion Module node in the Event Filter Builder tree. The event
Failed A multiplexer expansion
module failure was detected.
Critical Alert Unit identifies the affected multiplexer
expansion module.
Inserted A multiplexer expansion
module has been inserted.
Informational Alert Unit identifies the affected multiplexer
expansion module.
Removed A multiplexer expansion
module has been removed.
Warning Alert Unit identifies the affected multiplexer
expansion module.
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. Check the
service processor event log for
more information.
Warning Alert None
more information. You must
Warning Alert None
PFA The problem that 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
Supplies
v If the severity is Minor: Replace one of the power supplies in the specified
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.
Power Subsystem Not applicable Not
applicable
Not
applicable
None
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 low-fuel state. Minor Alert None
Low Fuel The server recovered from a
low-fuel state.
Mismatched
Power Supplies
Mismatched power supplies
were detected.
Minor Alert Power Domain identifies the affected
BladeCenter chassis power domain. A
BladeCenter chassis is divided into two
power domains. Power supplies 1 and 2
provide power to the first domain; Power
supplies 3 and 4 provide power to the second
domain.
Mismatched
Power Supplies
No mismatched power supplies
were detected.
Informational Resolution Power Domain identifies the affected
domain.
Over Current The server load exceeded the
capacity of the power
subsystem. You must manually
clear this event.
Minor Alert None
Over Power A power bus has exceeded 240
voltage amps. You must
Critical Alert
v Bus identifies the affected bus.
v Voltage Sensor identifies the affected voltage
sensor.
Over Subscription One power supply is not
sufficient to power all blade
servers at peak performance.
Throttling might occur.
Warning Alert Power Domain identifies the affected
domain.
Over Subscription One power supply is sufficient
to power all blade servers at
peak performance.
domain.
Over Subscription One power supply is not
sufficient to power all blade
servers. A power failure might
result in an immediate
shutdown.
Minor Alert Power Domain identifies the affected
domain.
Over Subscription One power supply is sufficient
to power all blade servers.
domain.
Redundancy Power redundancy was lost. Minor Alert Power Domain identifies the affected
domain.
Redundancy Power redundancy was lost.
event.
Minor Alert There are no extended details for this event
type.
Redundancy Power redundancy was
restored.
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
applicable
Not
applicable
Unit identifies the affected power supply.
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
detected in a system.
Critical Alert None
Configuration The power supply
Critical Alert None
Configuration The power supply
Configuration A monitored power capping
level has changed.
Minor Alert None
Configuration A monitored power control cap
has changed.
Minor Alert None
Failed A power supply has failed. Critical Alert
v Reason is one of the following 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 failed. You
Critical Alert
Failed A power supply has lost its
AC/DC input or is out of
range.
Critical Alert Unit identifies the affected power supply.
Failed A power supply is now
functioning properly.
v Reason is one of the following strings:
current
dc
epow
voltage
voltage_over
voltage_under
sensor by voltage.
Failed A power supply fan has failed. Critical Alert Unit identifies the affected power supply.
Failed A power supply fan is now
functioning correctly.
Informational Resolution Unit identifies the affected power supply.
Inserted A power supply was inserted. Informational Resolution Unit identifies the affected power supply.
more information.
Critical Alert Unit identifies the affected power supply.
Removed A power supply was removed. Warning Alert Unit identifies the affected power 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 Board Not applicable Not
applicable
Not
applicable
None
Processor Board node in the Event Filter Builder tree. The event filter will process
Failed A blade server processor board
Critical Alert None
Failed A blade server processor 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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the RAID
Failed A RAID failure was detected. Critical Alert Component indicates the Blade Expansion
Module with the affected RAID configuration.
Failed RAID has recovered from a
failure.
Informational Resolution Component indicates the Blade Expansion
Failed A ZSS/Drive-Array
configuration error was
detected.
Critical Alert Component indicates the Blade Expansion
Failed A ZSS/Drive-Array has
recovered from a configuration
error.
Informational Resolution Component indicates the Blade Expansion
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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the Server
Configuration The ASM interconnect
Note: This event is generated
by service processors only.
Minor Alert Issue is set to rs485.
Configuration The PCI Planar/ASM
interconnect configuration is
invalid.
Minor Alert Issue is set to pci/rs485.
Configuration A server configuration issue
was resolved.
v Issue is one of the following strings:
rs485
pci/rs485
Power Not applicable Not applicable Not
applicable
None
Power > Disabled A server cannot be powered on
because the power jumper is
not present.
Critical Alert None
because it is incompatible with
the power controller firmware.
Critical Alert None
because it cannot communicate
with the power controller.
Critical Alert None
Power > Disabled A server now can be powered
on.
Power > Disabled Power has been denied to a
blade because it cannot be
identified.
Critical Alert None
Power >
Hibernate
A blade server is entering
power hibernate mode.
Power > Off The server is powering off. Warning Alert None
Power > Off The server is powering off. Warning Alert
Power > On The server is powering on. Informational Alert None
Power > Restart The server is restarting. You
Minor Alert
Power > Restart The server is restarting. You
Warning Alert None
Power > Standby A blade server is entering
power standby mode.
State A server changed state.
Informational Alert New State is one of the following strings:
v off
v in_post
v post_error
v flash
v booting_os
v in_os
v reset
v on
State Local power control for a blade
server has been enabled.
Minor Alert
State Local power control for a blade
server has been disabled.
Informational Alert
State Local power control for all
blade servers has been enabled.
Minor Alert
State Local power control for all
blade servers has been disabled.
Informational Alert
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 >
Disabled
Out-of-band >
Enabled
Out-of-band > Port No resolution. This event is informative only.
Password > Change
Required
v If the severity is Warning: Change the service processor login password.
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
> Disabled
Secure Out-of-band
> Enabled
Secure Out-of-band
> Port
Test No resolution. This event is informative only.
User Account >
Active
User Account >
Disabled
User Account >
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 Processor Not applicable Not
applicable
Not
applicable
None
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
assumed control of the chassis.
Note: These events are
generated by BladeCenter
management modules only.
Warning Alert Unit identifies the affected management
module.
cannot communicate with a
blade server baseboard
management controller (BMC).
Critical Alert None
Communication The management module failed
to communicate with a blade
server.
Critical Alert None
successfully communicated
with a blade server after a
previous failure.
Configuration IBM Systems Director Server
failed to assign a default alert
configuration to the service
processor.
Warning Alert None
Duplicate IP
Address
A duplicate IP address has been
detected on a service processor.
Warning Alert None
Duplicate IP
Address
No duplicate IP addresses have
been detected.
Failover A network loss caused a
failover to the redundant
management module. You must
by BladeCenter management
modules only.
Minor Alert None
Failover The loss of a logical network
link has occurred. You must
modules only.
Minor Alert None
Failover An I2C bus failure caused a
failover to the redundant
management module.
modules only.
Minor Alert None
Failover A management module failover
event was reset by a
management module reset or
by removal of the failed
management module.
modules only.
Inactive A management module has
relinquished control of the
chassis.
Informational Resolution Unit identifies the affected management
module.
Inserted A service processor was
inserted.
Informational Alert Unit identifies the affected service processor.
Log The service processor event log
is full.
Minor Alert None
is full. You must manually clear
this event.
Minor Alert None
is 75% full.
Warning Alert None
is 75% full. You must manually
clear this event.
Warning Alert None
was cleared.
Mismatch A management module
mismatch was detected.
Warning Alert None
Mismatch No management module
mismatches were detected.
Network Stack The service processor network
stack started.
Informational Alert
v IP Address 1 is the IP address 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 applicable Not
applicable
None
Out-of-band >
Disabled
The service processor
out-of-band connection was
disabled.
Out-of-band >
Enabled
The service processor
enabled.
Out-of-band >
Port
The port number changed for
the service processor
out-of-band connection.
Informational Alert Port identifies the new port number.
Password Not applicable Not applicable Not
applicable
None
Password >
Change Required
A service processor user
password is about to expire.
Warning Alert Unit identifies the affected service processor.
Password >
Change Required
A service processor login
password has expired.
Password >
Change Required
password is required.
Password >
Change Required
password does not meet
complexity requirements.
Password >
Change Required
password change is no longer
required.
Informational Resolution Unit identifies the affected service processor.
Redundancy Service processor redundancy
was lost.
Minor Alert None
Redundancy Service processor redundancy
was restored.
Removed A service processor was
removed.
Restart The service processor restarted.
Secure
Out-of-band
Not applicable Not applicable Not
applicable
None
Secure
Out-of-band >
Disabled
The service processor secure
disabled.
Secure
Out-of-band >
Enabled
The service processor secure
enabled.
Secure
Out-of-band >
Port
The port number changed for
the service processor secure
out-of-band connection.
Informational Alert Port identifies the new port number.
Test The service processor sent a test
event.
User Account Not applicable Not applicable Not
applicable
None
User Account >
Active
account has been activated.
User Account >
Disabled
account has been disabled.
Warning Alert None
User Account >
Inactive
account has been deactivated.
Warning Alert None
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 Expansion
Module
Not applicable Not
applicable
Not
applicable
Unit identifies the affected SMP expansion 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 Module
was disabled.
Critical Alert Unit identifies the affected SMP expansion
module.
Disabled An SMP Expansion Module
recovered after being disabled.
Informational Resolution Unit identifies the affected SMP expansion
module.
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 Module Not applicable Not
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the Storage
Failed A storage module has failed. Critical Alert Unit identifies the affected storage module.
Failed A storage module has recovered
from a previous failure.
Informational Resolution Unit identifies the affected storage module.
Inserted A storage module was inserted. Informational Alert Unit identifies the affected storage module.
Insufficient
Cooling
A storage module cannot power
cooling.
Critical Alert Unit identifies the affected storage module.
Insufficient
Cooling
A storage module can now
power on because there is now
sufficient cooling.
Insufficient Power A storage module cannot power
power.
Critical Alert Unit identifies the affected storage module.
Insufficient Power A storage module can now
power on because sufficient
power has been restored.
Removed A storage module was
removed.
Warning Alert Unit identifies the affected storage 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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the USB
Inserted A USB device was inserted. Informational Resolution None
exceeded the rating of the USB
hub.
Warning Alert None
below the rating of the USB
hub.
exceeded the rating of the USB
port.
Warning Alert None
below the rating of the USB
port.
Removed A USB device was removed. Warning Alert None
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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the VRM
Configuration The voltage regulator module
configuration is not valid.
Critical Alert None
Configuration The voltage regulator module
Failed A voltage regulator module
failed.
Critical Alert Unit identifies the affected voltage regulator
module.
Failed A voltage regulator module
failed. You must manually clear
this event.
Critical Alert None
Failed A voltage regulator module is
now working correctly.
Informational Resolution Unit identifies the affected voltage regulator
module.
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
applicable
Not
applicable
Side identifies the affected side of an RXE-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 temperature has
exceeded the threshold.
Critical Alert
v Side identifies the affected side of an
RXE-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.
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.
exceeded the threshold. You
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.
Critical Alert There are no extended details for this event
type.
exceeded the threshold.
Warning Alert
strings:
ambient
CPU
DASD
exhaust
I/O module
memory
power supply
service processor
voltage regulator
Temperature A monitored temperature is
now within the applicable
range.
strings:
ambient
CPU
DASD
exhaust
I/O module
memory
power supply
service processor
voltage regulator
range.
by management modules on
behalf of IBM BladeCenter JS21
blade servers.
Critical Alert
v Entity ID identifies the type of device to
which the affected temperature sensor is
associated, using an ID based on the IPMI
standard.
v Entity Instance identifies the instance
number of the affected device. For example,
if a server has two processors, Entity
Instance identifies whether the event
information is for processor 1 or processor
2.
range.
blade servers.
Warning Alert
standard.
2.
range.
blade servers.
standard.
2.
Voltage A monitored voltage is
operating outside the applicable
range.
Critical Alert
v Component is one of the following strings:
CPU Board
IO card
system
voltage regulator module
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.
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
range. 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.
Critical Alert There are no extended details for this event
type.
range.
Minor Alert
CPU Board
IO card
system
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 now
within the applicable range.
CPU Board
IO card
system
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
range.
blade servers.
Critical Alert
standard.
2.
range.
blade servers.
Minor Alert
standard.
2.
range.
blade servers.
standard.
2.
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
Additional
extended details
Miscellaneous Miscellaneous
event occurred.
Varies
depending on
the service
processor that
sends the event.
Alert None
Miscellaneous Miscellaneous
event occurred.
Varies
depending on
the service
processor that
sends the event.
Resolution None
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 WatchDog Not applicable Not
applicable
Not
applicable
None
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 start. Critical Alert None
Boot The server failed to start. You
Critical Alert None
Boot The server started successfully
after a previous failure.
Loader The loader timeout was
exceeded. You must manually
clear this event.
Critical Alert None
OS The OS timeout was exceeded.
event.
Critical Alert None
POST The system POST failed. You
Critical Alert None
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
Additional
extended details
Unknown Unknown event.
Check the
service processor
event log for
more
information.
Warning Alert None
Unknown Unknown
recovery event.
Check the
service processor
event log for
more
information.
IBM Power platform-specific events
The events listed in this section are specific for the IBM Power hardware platform.
There are two types of hardware events: Firmware and device events. Firmware
events originate from the Computer System, Fan, Memory and Processor. Device
events originate from Ethernet port, Fibre Channel port, Optical disk, PCI device,
physical volume, and USB port.
All firmware events that are shown on the IBM Systems Director console are
cleared when Systems Director receives a resolution event from the agent or from
the Hardware Management Console (HMC) or Integrated Virtualization Manager
(IVM). The resolution event corresponds to a REPLACED_FRU entry in the AIX
error log or Linux on Power servicelog or on the HMC or IVM.
Device events do not have a corresponding resolution event. These events need to
be cleared manually on Systems Director server. For instructions, see this topic:
Deleting a Power Systems status set entry.
The list of possible events follows:
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 Systems, none of these
events are generated for in-band communication.
Condition type Condition value Severity Event availability
Pre-6.1 event type
name
Life Cycle LPAR Created Minor IBM Power
out-of-band
CIM > System >
Life Cycle
Life Cycle LPAR Deleted Minor IBM Power
out-of-band
CIM > System >
Life Cycle
Life Cycle CEC Added Minor IBM Power
out-of-band
CIM > System >
Life Cycle
Life Cycle CEC Deleted Minor IBM Power
out-of-band
CIM > System >
Life Cycle
Power State LPAR Running Minor IBM Power
out-of-band
CIM > System >
Power State
Power State LPAR Shutdown Minor IBM Power
out-of-band
CIM > System >
Power State
Power State CEC Powered On Minor IBM Power
out-of-band
CIM > System >
Power State
Power State CEC Powered Off Minor IBM Power
out-of-band
CIM > System >
Power State
IP Address Changed IP Address has been
changed
Minor IBM Power
out-of-band
CIM > System >
IP Change
Operational
Condition
Informational Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Operational
Condition
Warning Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Operational
Condition
Minor Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Operational
Condition
Critical Critical IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Operational
Condition
Fatal Fatal IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
Resolution Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
Non-error or
Informational Event
Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
Predictive Error,
bypassed with
degraded performance
(deferred service
action is required)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
Predictive Error, fault
might be corrected
after platform restart
(service action might
be required if system
restart does not fix
problem
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
External
Environment
Predictive Error,
degraded
performancer; fault
might be corrected
after platform restart,
problem)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
Predictive Error, loss
of redundancy (a
deferred service or
repair action is
required to restore
redundancy; the loss
of redundancy might
or might not impact
performance)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
Predictive Error,
general (deferred
service action is
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
Unrecoverable Error,
bypassed with loss of
function (deferred
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
redundancy and
performance (deferred
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
redundancy (deferred
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
bypassed with
(deferred service
action required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
general (service action
required immediately)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
External
Environment
Error on diagnostic
test
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Host Resolution Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Host Non-error or
Informational Event
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
Host Predictive Error,
bypassed with
(deferred service
action is required)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Host Predictive Error, fault
might be corrected
problem
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
degraded
performancer; fault
might be corrected
problem)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Host Predictive Error, loss
of redundancy (a
deferred service or
repair action is
required to restore
of redundancy might
or might not impact
performance)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
general (deferred
service action is
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Host Unrecoverable Error,
function (deferred
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
redundancy and
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
bypassed with
(deferred service
action required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
Host Error on diagnostic
test
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Adapter Resolution Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Adapter Non-error or
Informational Event
in-band and
out-of-band
CIM > System >
Service Event
I/O Adapter Predictive Error,
bypassed with
(deferred service
action is required)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Adapter Predictive Error, fault
might be corrected
problem
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
degraded
performancer; fault
might be corrected
problem)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Adapter Predictive Error, loss
of redundancy (a
deferred service or
repair action is
required to restore
of redundancy might
or might not impact
performance)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
general (deferred
service action is
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Adapter Unrecoverable Error,
function (deferred
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
redundancy and
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
bypassed with
(deferred service
action required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Adapter Error on diagnostic
test
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Subsystem Resolution Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Subsystem Non-error or
Informational Event
in-band and
out-of-band
CIM > System >
Service Event
I/O Subsystem Predictive Error,
bypassed with
(deferred service
action is required)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Subsystem Predictive Error, fault
might be corrected
problem
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
degraded
performancer; fault
might be corrected
problem)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Subsystem Predictive Error, loss
of redundancy (a
deferred service or
repair action is
required to restore
of redundancy might
or might not impact
performance)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
general (deferred
service action is
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Subsystem Unrecoverable Error,
function (deferred
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
redundancy and
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
bypassed with
(deferred service
action required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
I/O Subsystem Error on diagnostic
test
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Operational
Condition
Resolution Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Operational
Condition
Informational (The
error log entry is
informational and was
not the result of an
error.)
in-band and
out-of-band
CIM > System >
Service Event
Operational
Condition
Temporary (Indicates
that the condition was
recovered from after a
number of
unsuccessful attempts.
This error type is also
used to record
informational entries,
such as data transfer
statistics for DASD
devices.)
in-band and
out-of-band
CIM > System >
Service Event
Operational
Condition
Pending (Loss of
availability of a device
or component is
imminent.)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Operational
Condition
Performance (The
performance of the
device or component
has degraded to below
an acceptable level.)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Operational
Condition
Unknown (It is not
possible to determine
the severity of the
error.)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
Operational
Condition
Permanent (Condition
that could not be
recovered from. Error
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.)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Other Subsystem Resolution Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Other Subsystem Non-error or
Informational Event
in-band and
out-of-band
CIM > System >
Service Event
Other Subsystem Predictive Error,
bypassed with
(deferred service
action is required)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Other Subsystem Predictive Error, fault
might be corrected
problem
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
degraded
performancer; fault
might be corrected
problem)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Other Subsystem Predictive Error, loss
of redundancy (a
deferred service or
repair action is
required to restore
of redundancy might
or might not impact
performance)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
general (deferred
service action is
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
Other Subsystem Unrecoverable Error,
function (deferred
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
redundancy and
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
bypassed with
(deferred service
action required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Other Subsystem Error on diagnostic
test
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Platform Firmware Resolution Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Platform Firmware Non-error or
Informational Event
in-band and
out-of-band
CIM > System >
Service Event
Platform Firmware Predictive Error,
bypassed with
(deferred service
action is required)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Platform Firmware Predictive Error, fault
might be corrected
problem
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
degraded
performancer; fault
might be corrected
problem)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
Platform Firmware Predictive Error, loss
of redundancy (a
deferred service or
repair action is
required to restore
of redundancy might
or might not impact
performance)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
general (deferred
service action is
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Platform Firmware Unrecoverable Error,
function (deferred
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
redundancy and
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
bypassed with
(deferred service
action required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Platform Firmware Error on diagnostic
test
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Power Supply Resolution Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Power Supply Non-error or
Informational Event
in-band and
out-of-band
CIM > System >
Service Event
Power Supply Predictive Error,
bypassed with
(deferred service
action is required)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Power Supply Predictive Error, fault
might be corrected
problem
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
degraded
performancer; fault
might be corrected
problem)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Power Supply Predictive Error, loss
of redundancy (a
deferred service or
repair action is
required to restore
of redundancy might
or might not impact
performance)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
general (deferred
service action is
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Power Supply Unrecoverable Error,
function (deferred
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
redundancy and
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
bypassed with
(deferred service
action required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Power Supply Error on diagnostic
test
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Surveillance Error Resolution Informational IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Surveillance Error Non-error or
Informational Event
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
Surveillance Error Predictive Error,
bypassed with
(deferred service
action is required)
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Surveillance Error Predictive Error, fault
might be corrected
problem
Warning IBM Power
in-band and
out-of-band
CIM > System >
Service Event
degraded
performancer; fault
might be corrected
problem)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Surveillance Error Predictive Error, loss
of redundancy (a
deferred service or
repair action is
required to restore
of redundancy might
or might not impact
performance)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
general (deferred
service action is
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Surveillance Error Unrecoverable Error,
function (deferred
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
redundancy and
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
service action
required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
bypassed with
(deferred service
action required)
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
Pre-6.1 event type
name
Surveillance Error Error on diagnostic
test
Minor IBM Power
in-band and
out-of-band
CIM > System >
Service Event
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
Condition type Condition value Severity
Event
availability
Pre-6.1 event
type name
1
Operational Condition Resolution Informational IBM Power
in-band and
out-of-band
CIM > System
> Service Event
Operational Condition Informational (The error
log entry is
error.)
in-band and
out-of-band
CIM > System
> Service Event
Operational Condition Temporary (Indicates
number of unsuccessful
attempts. This error type
is also used to record
statistics for DASD
devices.)
in-band and
out-of-band
CIM > System
> Service Event
Operational Condition Pending (Loss of
or component is
imminent.)
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
Operational Condition Performance (The
performance of the
device or component
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
Operational Condition Unknown (It is not
the severity of the error.)
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
Event
availability
Pre-6.1 event
type name
1
Operational Condition Permanent (Condition
that could not be
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.)
Minor IBM Power
in-band and
out-of-band
CIM > System
> Service Event
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
Operational Condition Resolution Informational IBM Power in-band
and out-of-band
Operational Condition Non-error or Informational
Event
Informational IBM Power in-band
and out-of-band
Operational Condition Predictive Error, bypassed
with degraded performance
(deferred service action is
required)
Warning IBM Power in-band
and out-of-band
Operational Condition Predictive Error, fault might
be corrected after platform
restart (service action might
be required if system restart
does not fix problem
and out-of-band
Operational Condition Predictive Error, degraded
performancer; fault might be
corrected after platform
restart, degraded performance
(service action might be
required if system restart does
not fix problem)
Minor IBM Power in-band
and out-of-band
Operational Condition Predictive Error, loss of
redundancy (a deferred
service or repair action is
required to restore
redundancy; the loss of
redundancy might or might
not impact performance)
and out-of-band
Operational Condition Predictive Error, general
required)
and out-of-band
Operational Condition Unrecoverable Error,
function (deferred service
action required)
and out-of-band
redundancy and performance
(deferred service action
required)
and out-of-band
redundancy (deferred service
action required)
and out-of-band
bypassed with degraded
performance (deferred service
action required)
and out-of-band
Operational Condition Unrecoverable Error, general
(service action required
immediately)
and out-of-band
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
availability
Pre-6.1 event
type name
1
in-band and
out-of-band
CIM > System
> Service Event
log entry is
error.)
in-band and
out-of-band
CIM > System
> Service Event
Event
availability
Pre-6.1 event
type name
1
statistics for DASD
devices.)
in-band and
out-of-band
CIM > System
> Service Event
or component is
imminent.)
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
performance of the
device or component
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
that could not be
errors and are more
have a defective
hardware device or
types other than
that they can be
analyzed by the
diagnostics.)
Minor IBM Power
in-band and
out-of-band
CIM > System
> Service 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
Event
and out-of-band
required)
and out-of-band
and out-of-band
not fix problem)
and out-of-band
required to restore
and out-of-band
required)
and out-of-band
action required)
and out-of-band
required)
and out-of-band
action required)
and out-of-band
action required)
and out-of-band
immediately)
and out-of-band
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
availability
Pre-6.1 event
type name
1
in-band and
out-of-band
CIM > System
> Service Event
log entry is
error.)
in-band and
out-of-band
CIM > System
> Service Event
statistics for DASD
devices.)
in-band and
out-of-band
CIM > System
> Service Event
or component is
imminent.)
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
performance of the
device or component
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
that could not be
errors and are more
have a defective
hardware device or
types other than
that they can be
analyzed by the
diagnostics.)
Minor IBM Power
in-band and
out-of-band
CIM > System
> Service Event
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
availability
Pre-6.1 event
type name
1
in-band and
out-of-band
CIM > System
> Service Event
log entry is
error.)
in-band and
out-of-band
CIM > System
> Service Event
statistics for DASD
devices.)
in-band and
out-of-band
CIM > System
> Service Event
or component is
imminent.)
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
performance of the
device or component
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
that could not be
errors and are more
have a defective
hardware device or
types other than
that they can be
analyzed by the
diagnostics.)
Minor IBM Power
in-band and
out-of-band
CIM > System
> Service Event
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
availability
Pre-6.1 event
type name
1
in-band and
out-of-band
CIM > System
> Service Event
log entry is
error.)
in-band and
out-of-band
CIM > System
> Service Event
statistics for DASD
devices.)
in-band and
out-of-band
CIM > System
> Service Event
or component is
imminent.)
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
performance of the
device or component
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
Event
availability
Pre-6.1 event
type name
1
that could not be
errors and are more
have a defective
hardware device or
types other than
that they can be
analyzed by the
diagnostics.)
Minor IBM Power
in-band and
out-of-band
CIM > System
> Service Event
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
Event
and out-of-band
required)
and out-of-band
and out-of-band
not fix problem)
and out-of-band
required to restore
and out-of-band
required)
and out-of-band
action required)
and out-of-band
required)
and out-of-band
action required)
and out-of-band
action required)
and out-of-band
immediately)
and out-of-band
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
availability
Pre-6.1 event
type name
1
in-band and
out-of-band
CIM > System
> Service Event
log entry is
error.)
in-band and
out-of-band
CIM > System
> Service Event
Event
availability
Pre-6.1 event
type name
1
statistics for DASD
devices.)
in-band and
out-of-band
CIM > System
> Service Event
or component is
imminent.)
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
performance of the
device or component
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
Warning IBM Power
in-band and
out-of-band
CIM > System
> Service Event
that could not be
errors and are more
have a defective
hardware device or
types other than
that they can be
analyzed by the
diagnostics.)
Minor IBM Power
in-band and
out-of-band
CIM > System
> Service Event
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
Event
Battery Started Conditioning Informational Storage
Battery Conditioning
Event
Battery Stopped
Conditioning
Informational Storage
Disk Drive
These events are generated when a change in the state of a hard disk drive is
detected.
Device > Disk Drive
Conditions
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
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 applicable Not applicable 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
applicable
Not
applicable
Standard set of PET event type
extended 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 applicable Not applicable Standard set of
PET event type
extended details
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
Intrusion
Case intrusion
information
Set by
the Event
Severity
attribute.
Alert Standard set of PET event type
extended details
Case
Intrusion
Case intrusion
information
Harmless Resolution Standard set of PET event type
extended details
Current Current information Set by
the Event
Severity
attribute.
extended details
Current Current information Harmless Resolution Standard set of PET event type
extended details
Fan Fan information for
device device.
where device is the value
provided by the Entity
Instance extended detail.
Set by
the Event
Severity
attribute.
extended details
Fan Fan information for
device device.
extended details
Fan Device device inserted.
Set by
the Event
Severity
attribute.
extended details
Fan Device device has been
inserted.
extended details
removed.
Set by
the Event
Severity
attribute.
extended details
removed.
extended details
Power
Supply
Power supply
information
Set by
the Event
Severity
attribute.
extended details
Power
Supply
Power supply
information
extended details
Power
Supply
Redundancy has been
lost.
Set by
the Event
Severity
attribute.
extended details
Power
Supply
Redundancy has been
lost.
extended details
Power
Supply
Redundancy has been
degraded.
Set by
the Event
Severity
attribute.
extended details
Power
Supply
Redundancy has been
degraded.
extended details
Power
Supply
Redundancy has been
regained.
Set by
the Event
Severity
attribute.
extended details
Power
Supply
Redundancy has been
regained.
extended details
Temperature Temperature information Set by
the Event
Severity
attribute.
extended details
Temperature Temperature information Harmless Resolution Standard set of PET event type
extended details
Voltage Voltage information for
device device.
Set by
the Event
Severity
attribute.
extended details
Voltage Voltage information for
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 applicable Not applicable Standard set of
PET event type
extended details
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 applicable Not applicable Standard set of
PET event type
extended details
You can choose to select specific event types that are displayed under the BIOS
Progress System firmware
progress
information
Set by the Event
Severity
attribute.
Alert Standard set of
PET event type
extended details
Progress System firmware
progress
information
Harmless Resolution Standard set of
PET event type
extended details
Progress The system
firmware
encountered an
error in POST.
Set by the Event
Severity
attribute.
PET event type
extended details
Progress The system
firmware
encountered an
error in POST.
PET event type
extended details
Progress The system boot
has started.
Set by the Event
Severity
attribute.
PET event type
extended details
Progress The system boot
has started.
PET event type
extended details
Progress The system
firmware has
hung.
Set by the Event
Severity
attribute.
PET event type
extended details
Progress The system
firmware has
hung.
PET event type
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
applicable
Not
applicable
Standard set of PET event type extended
details
Hardware node in the Event Filter Builder tree. The event filter will process only
Cable/
Interconnect
The device is not
present.
Set by the
Event
Severity
attribute.
Alert Standard set of PET event type extended
details
Cable/
Interconnect
The device is not
present.
Harmless ResolutionStandard set of PET event type extended
details
Cable/
Interconnect
The device is present. Set by the
Event
Severity
attribute.
details
Cable/
Interconnect
The device is present. Harmless ResolutionStandard set of PET event type extended
details
Drive bay Device device has
been removed.
where device is the
value provided by
the Entity Instance
extended detail.
Set by the
Event
Severity
attribute.
details
been removed.
where device is the
value provided by
the Entity Instance
extended detail.
details
Drive bay The state of device
device has changed to
critical.
where device is the
value provided by
the Entity Instance
extended detail.
Set by the
Event
Severity
attribute.
details
critical.
where device is the
value provided by
the Entity Instance
extended detail.
details
been inserted.
where device is the
value provided by
the Entity Instance
extended detail.
Set by the
Event
Severity
attribute.
details
been inserted.
where device is the
value provided by
the Entity Instance
extended detail.
details
OK.
where device is the
value provided by
the Entity Instance
extended detail.
Set by the
Event
Severity
attribute.
details
OK.
where device is the
value provided by
the Entity Instance
extended detail.
details
Module/
Board
The device is not
present.
Set by the
Event
Severity
attribute.
details
Module/
Board
The device is not
present.
details
Module/
Board
The device is present. Set by the
Event
Severity
attribute.
details
Module/
Board
The device is present. Harmless ResolutionStandard set of PET event type extended
details
Monitor
ASIC/IC
The state of the
system-management
module has changed
to critical.
Set by the
Event
Severity
attribute.
details
Monitor
ASIC/IC
The state of the
system-management
module has changed
to critical.
details
Network The network
connection is offline.
Set by the
Event
Severity
attribute.
details
Network The network
connection is offline.
details
Network The network
connection has
degraded.
Set by the
Event
Severity
attribute.
details
Network The network
connection has
degraded.
details
Network The network
connection is online.
Set by the
Event
Severity
attribute.
details
Network The network
connection is online.
details
Watchdog 1 The watchdog timer
has expired.
Set by the
Event
Severity
attribute.
details
Watchdog 1 The watchdog timer
has expired.
details
Watchdog 2 The timer has
expired.
Set by the
Event
Severity
attribute.
details
Watchdog 2 The timer has
expired.
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.
applicable
Not
applicable
Standard set of PET event type
extended details
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 applicable Not applicable Standard set of
PET event type
extended details
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 has
failed to start
(boot).
Set by the Event
Severity
attribute.
PET event type
extended details
Boot The operating
system has
failed to start
(boot).
PET event type
extended details
Boot No media or
device can be
started (booted).
Set by the Event
Severity
attribute.
PET event type
extended details
Boot No media or
device can be
started (booted).
PET event type
extended details
Operation The operating
system has
hung.
Set by the Event
Severity
attribute.
PET event type
extended details
Operation The operating
system has
hung.
PET event type
extended details
Operation >
Heartbeat
Heartbeat
information
PET event type
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.
Platform considerations
On Linux on System x, Linux on Power Systems, and AIX onIBM Power, the
SNMP service is included with the Platform Agent. IBM Director Agent uses the
'dirsnmpd' SNMP service to accomplish these tasks:
v Forward events over SNMP to other management platforms, such as HP
OpenView Network Node Manager, Tivoli, or SNMP managers.
v Send events to the IBM Director Server by using SNMP traps.
When Common Agent is installed on a system, the SNMP service might be
optional because the agent forwards all events to the IBM Director Server. SNMP is
required to manageIBM servers that have Common Agent installed on them if
either of the following is true:
v Upward integration is configured on any environment that needs IBM Director
Agent to use SNMP to report events.
v Platform Agent must use SNMP traps to report events to IBM Director Server.
The 'dirsnmpd' SNMP service uses these configuration files:
v Linux on System x: /etc/snmpd.conf
v Linux on Power Systems, and AIX onIBM Power: /etc/snmpdv3.conf
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
where drive is the affected hard disk
drive.
Critical
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
current value is speed rpm.
where:
v threshold is the critical fan threshold value.
Note: This event must be cleared manually.
Critical
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
current value is speed rpm.
where:
v threshold is the critical fan threshold value.
Note: This event must be cleared manually.
Critical
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
ibmSystemTrapGenericVoltage Voltage Sensor number fell below
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.
Critical
ibmSystemTrapGenericVoltage Voltage Sensor number exceeded
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.
Critical
ibmSystemTrapGenericVoltage Voltage Sensor number reports
normal.
where number is the affected voltage
sensor.
Harmless
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.
ibmSystemTrapLeaseExpiration The lease on system has expired. It
expired on date.
where system is the affected system
and date is the lease expiration date.
Warning
ibmSystemTrapLeaseExpiration The lease on system is normal. It will
expire on date.
and date is the lease expiration date.
Harmless
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
predicting an imminent failure.
Critical
ibmSystemTrapMemoryPF Memory device identified as memory in bank slot is not
predicting a failure.
Harmless
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%
full. This event must be cleared manually.
Harmless
ibmSystemTrapMgmtHwLogStatus The system management processor error log is full.
This event must be cleared manually.
Harmless
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
ibmSystemTrapNetworkAdapterOfflineThe 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
management processor error log for more information. This
Critical
ibmSystemTrapPowerSupply
The ibmSystemTrapPowerSupply event occurs when the state of a system power
supply changes with respect to its availability.
Resolution
informative only.
Details
ibmSystemTrapPowerSupply PowerSupply device
identified as PowerSupply
number reports critical state
with possible loss of
redundancy.
where number is the affected
power supply.
Critical
number has failed. This event
power supply.
Critical
number has lost AC power
and loss of standby power is
imminent.
power supply.
Warning
number reports normal.
power supply.
Harmless
ibmSystemTrapProcessorPF
The ibmSystemTrapProcessorPF event occurs when the processor is about to fail.
Resolution
failed.
informative only.
Details
ibmSystemTrapProcessorPF Processor device identified as
processor in slot slot is
predicting an imminent
failure.
where slot is the affected
processor slot.
Critical
ibmSystemTrapProcessorPF Processor device identified as
processor in slot slot is not
where slot is the affected
processor slot.
Harmless
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 requires a teamed
configuration.
Warning
ibmSystemTrapRedundantNICSwitchback
The ibmSystemTrapRedundantNICSwitchback event occurs when the primary
network interface card (NIC) is restored in a teamed NIC configuration.
Resolution
Details
Switchback
Onboard NIC has Switched Back Warning
Switchback
Switched Back
where bus is the affected bus and slot
is the affected slot.
Warning
Switchback
NIC in PCI Slot slot has Switched
Back
Warning
Switchback
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
Switchover
Onboard NIC has Switched Over Warning
Switchover
Switched Over
where bus is the affected bus and slot
is the affected slot.
Warning
Switchover
NIC in PCI Slot slot has Switched
Over
Warning
Switchover
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 remote login. This
event must be cleared
manually.
Warning
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
an imminent failure.
where Device is IDE, SCSI, or Unknown and drive is the
affected SMART drive.
Critical
ibmSystemTrapSMART Device device identified as physical drive drive is not
where Device is IDE, SCSI, or Unknown and drive is the
affected SMART drive.
Harmless
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
ibmSystemTrapSPPowerSupplyPowerSupply device
number reports critical state
with possible loss of
redundancy.
power supply.
Critical
number has failed. This event
power supply.
Critical
number has lost AC power
and loss of standby power is
imminent.
power supply.
Warning
number reports normal.
power supply.
Harmless
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
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.
Critical
ibmSystemTrapStorage Logical drive name fell below threshold of threshold MB. The
current value is value MB.
where:
v name is the affected logical drive.
v threshold is the warning threshold value.
v value is the amount of current disk space available.
Warning
ibmSystemTrapStorage Logical drive name free space is normal. The current value is
value MB.
where name is the affected logical drive and value is the
amount of current disk space available.
Harmless
ibmSystemTrapStorage Logical drive name status could not be determined.
where name is the affected logical drive.
Unknown
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
ibmSystemTrapTemperature Temperature Sensor number
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.
Critical
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.
Critical
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.
Warning
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.
Warning
reports normal.
temperature sensor.
Harmless
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.
The current value is current Volts.
where:
Critical
ibmSystemTrapVoltage Voltage Sensor number exceeded threshold of threshold Volts.
The current value is current Volts.
where:
Critical
ibmSystemTrapVoltage Voltage Sensor number reports normal.
where number is the affected voltage sensor.
Harmless
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.
ibmSystemTrapWarrantyExpiration The warranty on system has expired.
It expired on date.
and date is the warranty expiration
date.
Warning
ibmSystemTrapWarrantyExpiration The warranty on system is normal. It
will expire on date.
and date is the warranty expiration
date.
Harmless
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
ibmSystemTrapxAutomaticServer
Restart
The last system restart was due to
the automatic server restart
hardware.
Warning
ibmSystemTrapxAutomaticServer
Restart
The last system restart was not due
to the automatic server restart
hardware.
Harmless
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]
where array is the affected array and error is the error
code.
Critical
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]
code.
Critical
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]
code.
Critical
ibmSystemRaidCompactionComplete
The ibmSystemRaidCompactionComplete event occurs when a RAID compaction
operation is completed on a specified logical drive in a RAID configuration.
Resolution
Details
ibmSystemRaidCompactionComplete Compaction 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]
where drive is the affected logical drive and
Critical
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
ibmSystemRaidCompression
Detected
Compressing: drive.
Harmless
ibmSystemRaidCompressionFail
The ibmSystemRaidCompressionFail event occurs when a RAID compression
Resolution
Details
ibmSystemRaidCompressionFail Compression failed: drive [error].
where drive is the affected logical drive and error is the error code.
Critical
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
where controller is the added controller.
Harmless
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:
controller
where controller is the controller for the affected logical
drives.
Warning
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 temperature: controller
Warning
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: controller
Harmless
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
where controller is the controller that failed.
Critical
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.
where location is the affected controller and array.
Harmless
ibmSystemRaidCopyBackDetected
The ibmSystemRaidCopyBackDetected event occurs when a copy-back operation is
in progress on a specified logical drive in a RAID configuration.
Resolution
Details
ibmSystemRaidCopyBackDetected Copy back in progress: location. Source: Channel channel, 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
Harmless
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]
where location is the affected controller and array and
Critical
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:
controller
Critical
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.
Error code: error
where controller is the affected controller and error is
the error code.
Critical
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]
where drive is the affected logical drive and error is the
error code.
Critical
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
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).
where location is the affected controller and port and
FRU is the FRU number of the hard disk drive.
Critical
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).
where location is the affected controller and port and
Harmless
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]
where drive is the affected hard disk drive and error is
the error code.
Critical
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
ibmSystemRaidDriveVerifyComplete Verify 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
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
attached to.
Harmless
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
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].
where drive is the affected logical drive and error is the
error code.
Critical
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
where fan is the affected fan and location is the controller and
channel that the affected enclosure is attached to.
Critical
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
where fan is the affected fan and location is the controller and
channel that the affected enclosure is attached to.
Harmless
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
where fan is the affected fan and location is the controller
and channel that the affected enclosure is attached to.
Warning
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
ibmSystemRaidFlashCopyFail FlashCopy with backup
failed: drive [error].
where drive is the affected
logical drive and error is the
error code.
Critical
ibmSystemRaidInitComplete
The ibmSystemRaidInitComplete event occurs when a RAID initialization
Resolution
Details
ibmSystemRaidInitCompleteClear 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.
where drive is the affected logical drive and data is the
size and RAID level of that logical drive.
Harmless
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
ibmSystemRaidLogicalDrive
CriticalPeriodic
Periodic scan found one or more
critical logical drives: drive. Repair as
soon as possible to avoid data loss.
drive.
Warning
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
ibmSystemRaidLogicalDriveOffLineLogical drive is offline: drive.
Critical
ibmSystemRaidLogicalDriveOK
The ibmSystemRaidLogicalDriveOK event occurs when a specified logical drive is
functioning correctly.
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.
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
ibmSystemRaidMigrationFail Migration failed: drive [error]
logical drive and error is the
error code.
Critical
ibmSystemRaidNoControllers
The ibmSystemRaidNoControllers event occurs when no RAID controllers are
detected.
Resolution
Details
ibmSystemRaidNoControllers No 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
ibmSystemRaidPFADriveFRU PFA detected for drive: drive (FRU).
where drive is the affected hard disk drive and FRU is the FRU number of
that drive.
Warning
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.
Result codes: error
where controller is the affected controller and error is the
error code.
Warning
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:
location
where supply is the affected power supply and location
is the controller and channel that the affected
enclosure is attached to.
Critical
ibmSystemRaidPowerSupplyInstalled
The ibmSystemRaidPowerSupplyInstalled event occurs when a specified enclosure
power supply is installed in a RAID configuration.
Resolution
Details
ibmSystemRaidPowerSupplyInstalled Enclosure power supply supply has
been installed: location
where supply is the affected power
supply and location is the controller
and channel that the affected
Harmless
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:
location
where supply is the affected power supply and location
is the controller and channel that the affected
Harmless
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: location
where supply is the affected power
supply and location is the controller
and channel that the affected
Warning
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].
where drive is the affected logical drive and error is the error
code.
Critical
ibmSystemRaidSyncComplete
The ibmSystemRaidSyncComplete event occurs when a RAID synchronization
Resolution
Details
ibmSystemRaidSyncComplete Synchronize complete: drive.
logical 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]
where drive is the affected logical drive and error is the error
code.
Critical
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
where location is the controller and channel that the affected
Critical
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
where location is the controller and channel that the affected
Harmless
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
(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.
Warning
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
Agent
Not applicable Not
applicable
Not
applicable
None
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 Launch
Job window.
v Duration
v Monitor Resource
v Threshold Name
Process
Monitors
Note: The event text
varies depending on the
monitor that you create.
Varies
depending
on the
threshold
set for
the
monitor.
Alert
v Actual Value is the current reading of
the monitored resource at the time the
event is sent.
v Threshold Value is the configured value
you assigned in the Above or Equal
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
depending
on the
threshold
set for
the
monitor.
Alert
event is sent.
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
details
Process
Failed to
Start
Process Failed to Start
Monitor 'PMON:process_name
Fail' Changed:'process_name has
changed values for 0:00:00.
New value reported is "1".
where process_name is the name
of the affected process.
Critical Alert
v Actual Value is the
current reading of the
monitored resource at
the time the event is
sent.
v Threshold Value is the
configured value you
assigned in the Above
or Equal or Below or
Equal field of the
Threshold
Configuration window.
Process
Started
Process Start Monitor
'PMON:process_name Start'
Changed:'process_name has
Informational Alert
sent.
Equal field of the
Threshold
Process
Terminated
Process Terminated Monitor
'PMON:process_name Stop'
Changed:'process_name has
Warning Alert
sent.
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 Launch
Job window.
v Duration
v Monitor Resource
v Threshold Name
Chapter 2. IBM Systems Director tasks, software, and operating system events 211
Resource
Monitors
Note: The event text
Varies
depending
on the
threshold
set for
the
monitor.
Alert
event is sent.
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
job that you schedule.
Not
applicable
Not
applicable
None
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
applicable
Not
applicable
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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the Error
Note: The
name of the
scheduled
job.
Note: The name of the
scheduled job.
Warning Alert None
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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the Success
Note: The
name of the
scheduled
job.
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.
applicable
Not
applicable
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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the Error
Note: The
name of the
scheduled
job.
scheduled job.
Warning Alert None
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
applicable
Not
applicable
None
You can choose to select specific event types that are displayed under the Success
Note: The
name of the
scheduled
job.
scheduled job.
InformationalAlert None
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 type Condition value Severity Category Event text Extended details
Operational
Condition
Started Informational Alert The core agent
has started.
None
Operational
Condition
Stopped Informational Alert The core agent
has stopped.
None
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
type
Condition
value Severity Category Event text Extended details
Operational
Condition
Invoke Varies
depending
on how
you
customize
the event.
Alert Note: The event text varies
depending on how you
customize the event.
None
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
Access
Requested
Informational Alert Agent accessInfo is managed by an agent
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.
None
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
value Severity Category Event text
Additional extended
attributes
Pre-6.1 event
type name
Disabled
User ID
Warning Alert Logon to server by User ID
User ID from Address failed
(Disabled User ID)
Where User ID and Address
are the values provided by
the extended details.
None Director >
Console >
Logon Failure
> Disabled
User ID
Condition
value Severity Category Event text
Additional extended
attributes
Pre-6.1 event
type name
Expired
Password
(Expired Password)
None Director >
Console >
Logon Failure
> Expired
Password
Failure Warning Alert None
Incorrect
Password
(Bad Password)
None Director >
Console >
Logon Failure
> Bad
Password
Incorrect
User ID
(Bad User ID)
None Director >
Console >
Logon Failure
> Bad User
ID
User ID
Locked
Out
Warning Alert None
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
type name
User ID
Logged
Off
InformationalAlert User logged off.
v Description is the long
name of the user ID. For
example, if a user ID is
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.
Director >
Console >
User Logoff
Condition
Pre-6.1 event
type name
User ID
Logged
On
InformationalAlert User logged on.
v Description is the long
name of the user ID. For
example, if a user ID is
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.
Director >
Console >
User Logon
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
Status
Varies
depending
on the
problem
status
associated
with the
resource.
Alert Initial Status Gathered None
System Configuration events
These events are generated by the configuration manager plug-in from IBM
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
been fully deployed.
v planID is the identifier of
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
been partially deployed.
the affected plan.
resource.
plan.
Deployed Critical Alert The configuration plan
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
configuration template
is offline.
v templateID is the identifier
of the affected template.
resource.
v deviceID is the identifier of
the affected target device.
v templateName is the name
template.
Deployed Critical Alert The target for the
configuration template
is locked.
resource.
template.
Condition
Deployed Critical Alert Configuration Manager
general failure: see the
TWGRas.log file.
resource.
template.
Deployed Critical Alert The configuration
template failed to be
deployed.
resource.
template.
Deployed Informational Alert The configuration
template has been fully
deployed.
resource.
template.
Deployed Informational Alert An empty configuration
was applied.
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
Modified
Informational Alert Update Compliance Policy
Changed
when a compliance policy is
edited or removed by a user.
Compliance is automatically
reevaluated when a policy is
created or removed from a
system or system group.
If the compliance policy is on a
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.
v Edit Compliance Policy is
a list of updates or
update groups that were
added to or edited in a
system or system group
compliance policy.
v Remove Compliance Policy
is a list of updates or
update groups that were
removed from a system
or system group
compliance policy.
Task Failed Warning Alert Compliance Failed
Note: This event is generated if
the update Compliance task
failed for a compliance flow.
v Compliance Relationship
Check Failed indicates
the managed resource
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
when the Install task fails. The
failure can be in any stage of
the installation: download,
distribute or install.
Updates is an array of
names of the updates that
have failed to install.
Successful Informational Alert Install Successful
after an Install task completes
successfully.
have installed 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
when the Uninstall task fails.
have failed to uninstall.
Successful Informational Alert Uninstall Successful
after the Uninstall task
completes successfully.
have uninstalled
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
Updates
Failed
Warning Alert Check for Updates Failed
when the Check for Updates
task fails because no updates are
available.
Check for Updates Failed
provides a localized
exception message that
describes the failure.
Check for
Updates
Failed
Warning Alert Check for Updates Failed
when the Check for Updates
task fails, for example, when it is
unable to connect to the
download provider.
have failed to download, if
available.
Distribute
Updates
Failed
Warning Alert Installation Staging of Updates
Failed
when the Distribute task fails.
have failed to be
distributed.
Download
Updates
Failed
Warning Alert Download Updates Failed
when the Download task fails.
have failed to download.
Condition
New
Updates
Found
Informational Alert New Updates Found
when metadata for a new
update is found. If, in the Check
for Updates task, multiple new
updates are found, the event is
generated only once.
Severity indicates the
severity of the most critical
update.
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 Director 5.20 event names
IBM Systems Director 6.1 event names
No legacy events are mapped to this USMi Event
Type.
Domain > Farm > Virtual Farm Events > Virtual
farm created
This event does not apply to VMware
VirtualCenter.
Type.
farm deleted
This event is not supported.
Type.
Domain > Farm > Virtual Farm Events > Host
added to virtual farm
VirtualCenter.
Type.
Domain > Farm > Virtual Farm Events > Host
removed from virtual farm
VirtualCenter.
Type.
farm renamed
VirtualCenter.
Table 3. Virtualization event cross reference (continued)
Type.
Domain > Farm > Relocation Manager Events >
Virtual server relocation started
This event applies to hosts managed by Hardware
Management Console or Integrated Virtualization
Manager.
Type.
Virtual Server relocation failed
Manager.
Type.
Virtual server relocation complete
Manager.
v CIM > Director Agent Events > VMware >
Alert Indication
v CIM > Director Agent Events > Ipmi > Alert
Indication
Server > ESXi Operational Condition >
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.
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.
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 >
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
subcategory
Additional
event
subcategory
Target resource for
event automation
plan
Event trigger Description
Agent
Extension
Status Change Depends on the
virtualization
manager subagent:
v Platform
manager
(virtualization
manager
subagent for
VMware
VirtualCenter)
v Host
(virtualization
manager
subagent for
VMware ESX
Server )
Virtualization
manager
subagent
detects a
status change
for the
platform
manager or
the host.
The following scenarios are examples of such
events:
v Virtualization manager subagent is not
running or the virtualization application is
not installed.
v Virtualization manager subagent and the
virtualization application are installed, but
they are not communicating properly with
each other.
v The platform manager or host is ready for
use. For platform managers, this means that
IBM Systems Director has authenticated with
VMware VirtualCenter server.
v (VMware VirtualCenter only) The platform
manager requires a connection.
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.
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
subcategory
Additional
event
subcategory
Target resource
for event
automation plan
Agent
Extension
Status
Change
Depends on the
virtualization
manager subagent:
v Platform
manager
(virtualization
manager
subagent for
VMware
VirtualCenter)
v Host
(virtualization
manager
subagent for
VMware ESX
Server)
Virtualization
manager
subagent
detects a status
change for the
platform
manager or the
host.
The following scenarios are examples of such
events:
v Virtualization manager subagent is not
running or the virtualization application is
not installed.
v Virtualization manager subagent and the
virtualization application are installed, but
they are not communicating properly with
each other.
v The platform manager or host is ready for
use. For platform managers, this means that
IBM Systems Director has authenticated with
VMware VirtualCenter server or VMware
ESX Server.
v (VMware VirtualCenter only) The platform
manager requires a connection.
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
subcategory
Additional
event
subcategory
Target object
for event
automation
plan
Attribute
Changed
Virtual server The value of the
CPU Count or
the Memory
Size attribute
for a virtual
server is
changed.
Virtualization manager has changed the value of
the attributes for the number of CPUs or the
memory size for a virtual server. Virtualization
manager updates this attribute information in
both IBM Systems Director and the associated
virtualization application.
Created Virtual server A virtual server
is created.
IBM Systems Director displays the virtual server
in the Web interface.
Deleted Virtual server A virtual server
is deleted.
IBM Systems Director no longer displays the
virtual server in the Web interface.
Relocation Started Virtual server A virtual server
has started
relocation from
one host to
another.
Virtualization manager has started the relocation
of a virtual server from one host to another.
Table 6. Virtual server events (continued)
Event
subcategory
Additional
event
subcategory
Target object
for event
automation
plan
Completed Virtual server A virtual server
has completed
relocation from
one host to
another.
Virtualization manager has completed the
relocation of a virtual server from one host to
another.
State Pending Virtual server The state of a
virtual server
has changed to
pending.
The associated virtualization application requires
the user to answer a question before the state
change will continue. To resolve a pending state,
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
virtual server
has changed to
turned off.
A virtual server is turned off.
Powered on Virtual server The state of a
virtual server
has changed to
turned on.
A virtual server is turned on.
Reset Virtual server The state of a
virtual server
has changed to
restarted.
A virtual server is restarted.
Resumed Virtual server The state of a
virtual server
has changed
from suspended
to turned on.
A virtual server resumes operations after being
in the suspended state.
Suspended Virtual server The state of a
virtual server
has changed to
suspended.
A virtual server is suspended.
Task Failed Virtual server An operation on
a virtual server
has failed to
complete
successfully.
A power or relocation operation failed for a
virtual server.
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
subcategory
Additional
event
subcategory
Target object for
event automation
plan
Virtual Farm Created Virtual Farm Virtualization
manager
subagent for
VMware
VirtualCenter
detects that a
virtual farm is
created.
(VMware VirtualCenter only) IBM Systems
Director displays a virtual farm in the Web
interface.
Deleted Virtual Farm Virtualization
manager
subagent for
VMware
VirtualCenter
detects that a
virtual farm is
deleted.
Director no longer displays a virtual farm in the
Web interface.
Host Added Virtual Farm Virtualization
manager
subagent
detects that a
host is added
to a virtual
farm.
IBM Systems Director displays a host nested
beneath the virtual farm.
Note: (VMware VirtualCenter only) When this
event occurs, a host object is displayed only when
the managed system that represents the host has
already been discovered by IBM Systems Director.
Host
Removed
Virtual Farm Virtualization
manager
subagent
detects that a
host is
removed from
a virtual farm.
IBM Systems Director no longer displays a host
nested beneath the virtual farm.
Renamed Virtual Farm Virtualization
manager
subagent for
VMware
VirtualCenter
detects that a
virtual farm is
renamed.
Director displays the new name for the virtual
farm.
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.
Additional
extended details
Correlation Not applicable Not applicable Not applicable None
Correlation node in the Event Filter Builder tree. The event filter will process only
Additional
extended details
Common Agent Not applicable Not applicable Not applicable None
Common Agent
> Blade Server -
Chassis
Correlate
Common Agent
to its blade
server and
generate event.
Note: This text
is the default
text supplied in
the
ChassisID.properties
file. You can
customize this
text.
Varies
depending on
how you
customized the
event.
Varies
depending on
how you
customized the
event.
None
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 type Condition value Severity Category Event text
Pre-6.1 event
type name
Connectivity Offline Informational Alert System system is
offline. where
system is the
managed object
with the affected
installation of
Common Agent.
Director >
Topology >
Offline
Connectivity Online Informational Alert System system is
online. where
system is the
managed object
with the affected
installation of
Common Agent.
Director >
Topology >
Online
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 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
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
applicable
The SNMPv1-standard OID defined in enterprise 'director'.
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 Resource Explorer, 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
Director event
Not applicable Not applicable CIM > System > IPMI
Log
IBM Systems
Director Web
interface
Not applicable Not applicable Not applicable
Microsoft
Operations
Manager 2005 alert
Not applicable Not applicable Other
Microsoft SMS
native events
Microsoft
Windows event
log event ID
Not applicable Not applicable 33
SNMP Not applicable Not applicable ibmSystemTrapMgmt
HwLogStatus
Tivoli Enterprise
Console native
event
Not applicable Not applicable IBM_MgmtHwLogStatus
Tivoli Enterprise
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
Director event
Not applicable CIM > System >
Automatic Server Restart
CIM > System >
Automatic Server Restart
IBM Systems
Director Web
interface
Microsoft
Operations
Manager 2005 alert
Microsoft SMS
native events
Microsoft
Windows event
log event ID
Not applicable 36 36
SNMP Not applicable ibmSystemTrapxAutomatic
ServerRestart
ibmSystemTrapxAutomatic
ServerRestart
Tivoli Enterprise
Console native
event
Tivoli Enterprise
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
Director event
CIM > System > System
Enclosure
Not applicable CIM > System > System
Enclosure
IBM Systems
Director Web
interface
Not applicable No symbol displayed
Microsoft
Operations
Manager 2005 alert
Security Event Security Event Security Event
Microsoft SMS
native events
(Message ID
50040)
IBM_UMS_AGENT_
CHASSIS_ERROR_
IBM_UMS_AGENT_
CHASSIS_WARNING_
IBM_UMS_AGENT_
CHASSIS_INFO_
Microsoft
Windows event
log event ID
4 Not applicable 4
SNMP ibmSystemTrapChassis Not applicable ibmSystemTrapChassis
Tivoli Enterprise
Console native
event
IBMPSG_ChassisEvent IBMPSG_ChassisEvent IBMPSG_ChassisEvent
Tivoli Enterprise
Console SNMP
event
UMS_ChassisIntruded Not applicable UMS_ChassisInPlace
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 event CIM > System > DASD
Backplane
Not applicable Not applicable
IBM Systems Director Web
interface
Microsoft Operations
Manager 2005 alert
Storage Event Storage Event Storage Event
Microsoft SMS native
events (Message ID 50300)
IBM_UMS_AGENT_
DASDBACKPLANE_
ERROR_
IBM_UMS_AGENT_
DASDBACKPLANE_
WARNING_
IBM_UMS_AGENT_
DASDBACKPLANE_
INFO_
Microsoft Windows event
log event ID
30 Not applicable Not applicable
SNMP ibmSystemTrapDASD
Backplane
Tivoli Enterprise Console
native event
IBMPSG_DASD
BackplaneEvent
SNMP event
UMS_DASDBackplaneEvent Not applicable Not applicable
IBMPSG_ErrorLogEvent CIM indication
its error log is at 75% or 100% of its capacity.
event
Not applicable CIM > System > Error
Log
Not applicable
Web interface
Manager 2005 alert
Other Event Other Event Other Event
events (Message ID
50240)
IBM_UMS_AGENT_
ERRORLOG_ERROR_
IBM_UMS_AGENT_
ERRORLOG_WARNING_
IBM_UMS_AGENT_
ERRORLOG_INFO_
Microsoft Windows
event log event ID
24 24 Not applicable
SNMP Not applicable ibmSystemTrapErrorLog Not applicable
Tivoli Enterprise
Console native event
IBMPSG_ErrorLogEvent IBMPSG_ErrorLogEvent Not applicable
Chapter 5. CIM indicators 243
Tivoli Enterprise
Console SNMP event
UMS_ErrorLogEvent UMS_ErrorLogEvent Not applicable
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.
event
CIM > System > Fan Not applicable CIM > System > Fan
Web interface
Manager 2005 alert
Fan Event Fan Event Fan Event
events (Message ID
50050)
IBM_UMS_AGENT_
FAN_ERROR_
IBM_UMS_AGENT_
FAN_WARNING_
IBM_UMS_AGENT_
FAN_INFO_
Microsoft Windows
event log event ID
5 5 5
SNMP ibmSystemTrapFan Not applicable ibmSystemTrapFan
Tivoli Enterprise
IBMPSG_FanEvent IBMPSG_FanEvent IBMPSG_FanEvent
Tivoli Enterprise
Console SNMP event
UMS_FanOutOfOrder Not applicable UMS_FanOperational
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 event CIM > System > Fan Not applicable Not applicable
interface
Manager 2005 alert
Fan Event Fan Event Fan Event
IBM_UMS_AGENT_
GENERICFAN_ERROR_
IBM_UMS_AGENT_
GENERICFAN_WARNING_
IBM_UMS_AGENT_
GENERICFAN_INFO_
log event ID
SNMP ibmSystemTrapGenericFan Not applicable Not applicable
native event
IBMPSG_GenericFanEvent Not applicable Not applicable
SNMP event
UMS_GenericFanEvent Not applicable Not applicable
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 event CIM > System > Voltage Not applicable Not applicable
interface
Manager 2005 alert
Voltage Event Voltage Event Voltage Event
IBM_UMS_AGENT_
GENERICVOLTAGE_
ERROR_
IBM_UMS_AGENT_
GENERICVOLTAGE_
WARNING_
IBM_UMS_AGENT_
GENERICVOLTAGE_
INFO_
log event ID
SNMP ibmSystemTrapGeneric
Voltage
native event
IBMPSG_Generic
VoltageEvent
SNMP event
UMS_GenericVoltageEvent Not applicable Not applicable
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 event Not applicable CIM > System > Lease
Expiration
CIM > System > Lease
Expiration
interface
Manager 2005 alert
Microsoft SMS native events
(Message ID 50130)
IBM_UMS_AGENT_
LEASE_ERROR_
IBM_UMS_AGENT_
LEASE_WARNING_
IBM_UMS_AGENT_
LEASE_INFO_
log event ID
SNMP Not applicable ibmSystemTrapLeaseExpiration ibmSystemTrapLeaseExpiration
native event
IBMPSG_LeaseExpirationEvent IBMPSG_LeaseExpirationEvent IBMPSG_LeaseExpirationEvent
SNMP event
UMS_LeaseExpiredCritical UMS_LeaseExpiredWarning UMS_LeaseExpiredNormal
IBMPSG_MemoryPFEvent CIM indication
This CIM indication is generated when a dual inline memory module (DIMM) in a
system is about to fail.
event
CIM > System >
Memory PFA
Memory PFA
Web interface
Manager 2005 alert
Memory Event Memory Event Memory Event
events (Message ID
50190)
IBM_UMS_AGENT_
MEMORYPFA_ERROR_
IBM_UMS_AGENT_
MEMORYPFA_WARNING_
IBM_UMS_AGENT_
MEMORYPFA_INFO_
Microsoft Windows
event log event ID
19 Not applicable 19
SNMP ibmSystemTrapMemoryPF Not applicable ibmSystemTrapMemoryPF
Tivoli Enterprise
IBMPSG_MemoryPFEvent IBMPSG_MemoryPFEvent IBMPSG_MemoryPFEvent
Tivoli Enterprise
Console SNMP event
UMS_MemoryPFCritical UMS_MemoryPFWarning UMS_MemoryPFNormal
IBMPSG_NetworkAdapterFailedEvent CIM indication
This CIM indication is generated when a network interface card (NIC) in a system
has failed.
event
CIM > System >
Network Adapter >
Failed
Web interface
Manager 2005 alert
Network Event Network Event Network Event
events (Message ID
50260)
IBM_UMS_AGENT_
NETWORKADAPTER
FAILED_ERROR_
IBM_UMS_AGENT_
NETWORKADAPTER
FAILED_WARNING_
IBM_UMS_AGENT_
NETWORKADAPTER
FAILED_INFO_
Microsoft Windows
event log event ID
Not applicable 26 Not applicable
SNMP ibmSystemTrapNetwork
AdapterFailed
Tivoli Enterprise
Not applicable IBMPSG_NetworkAdapter
FailedEvent
Not applicable
Tivoli Enterprise
Console SNMP event
Not applicable UMS_NetworkAdapter
FailedEvent
Not applicable
IBMPSG_NetworkAdapterOfflineEvent CIM indication
This CIM indication is generated when a network interface card (NIC) in a system
goes offline.
event
Network Adapter >
Offline
Not applicable
Web interface
Manager 2005 alert
events (Message ID
50270)
IBM_UMS_AGENT_
NETWORKADAPTER
OFFLINE_ERROR_
IBM_UMS_AGENT_
NETWORKADAPTER
OFFLINE_WARNING_
IBM_UMS_AGENT_
NETWORKADAPTER
OFFLINE_INFO_
Microsoft Windows
event log event ID
SNMP Not applicable ibmSystemTrapNetwork
AdapterOffline
Not applicable
Tivoli Enterprise
Not applicable IBMPSG_NetworkAdapter
OfflineEvent
Not applicable
Tivoli Enterprise
Console SNMP event
Not applicable UMS_NetworkAdapter
OfflineEvent
Not applicable
IBMPSG_NetworkAdapterOnlineEvent CIM indication
This CIM indication is generated when the state of a system network interface card
(NIC) changes from offline to online.
event
Not applicable Not applicable CIM > System >
Network Adapter >
Online
Web interface
Manager 2005 alert
events (Message ID
50280)
IBM_UMS_AGENT_
NETWORKADAPTER
ONLINE_ERROR_
IBM_UMS_AGENT_
NETWORKADAPTER
ONLINE_WARNING_
IBM_UMS_AGENT_
NETWORKADAPTER
ONLINE_INFO_
Microsoft Windows
event log event ID
SNMP Not applicable Not applicable ibmSystemTrapNetwork
AdapterOnline
Tivoli Enterprise
Not applicable Not applicable IBMPSG_NetworkAdapter
OnlineEvent
Tivoli Enterprise
Console SNMP event
Not applicable Not applicable UMS_NetworkAdapter
OnlineEvent
IBMPSG_PFAEvent CIM indication
a component in a system is about to fail.
event
CIM > System > PFA Not applicable Not applicable
Web interface
Manager 2005 alert
events (Message ID
50210)
IBM_UMS_AGENT_
PFA_ERROR_
IBM_UMS_AGENT_
PFA_WARNING_
IBM_UMS_AGENT_PFA_INFO_
Microsoft Windows
event log event ID
SNMP ibmSystemTrapPFA Not applicable Not applicable
Tivoli Enterprise
IBMPSG_PFAEvent Not applicable Not applicable
Tivoli Enterprise
Console SNMP event
UMS_PFAEvent Not applicable Not applicable
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 event CIM > System > Server
Power Supply
Not applicable CIM > System > Server
Power Supply
interface
Manager 2005 alert
Power Supply Event Power Supply Event Power Supply Event
IBM_UMS_AGENT_
POWERSUPPLY_ERROR_
IBM_UMS_AGENT_
POWERSUPPLY_WARNING_
IBM_UMS_AGENT_
POWERSUPPLY_INFO_
log event ID
23 23 23
SNMP ibmSystemTrapPowerSupply Not applicable ibmSystemTrapPowerSupply
native event
IBMPSG_PowerSupplyEvent IBMPSG_PowerSupplyEvent IBMPSG_PowerSupplyEvent
SNMP event
UMS_PowerSupplyCritical UMS_PowerSupplyWarning UMS_PowerSupplyNormal
IBMPSG_ProcessorPFEvent CIM indication
This CIM indication is generated when the processor is about to fail.
IBM Systems Director event CIM > System > Processor PFA Not applicable CIM > System > Processor PFA
interface
Manager 2005 alert
Processor Event Processor Event Processor Event
(Message ID 50180)
IBM_UMS_AGENT_
PROCESSORPF_ERROR_
IBM_UMS_AGENT_
PROCESSORPF_WARNING_
IBM_UMS_AGENT_
PROCESSORPF_INFO_
log event ID
18 Not applicable 18
SNMP ibmSystemTrapProcessorPF Not applicable ibmSystemTrapProcessorPF
native event
IBMPSG_ProcessorPFEvent IBMPSG_ProcessorPFEvent IBMPSG_ProcessorPFEvent
SNMP event
UMS_ProcessorPFCritical UMS_ProcessorPFWarning UMS_ProcessorPFNormal
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.
IBM Systems Director event Not applicable Not applicable Not applicable
interface
Manager 2005 alert
IBM_UMS_AGENT_
REDUNDANTNETWORK
ADAPTER_ERROR_
IBM_UMS_AGENT_
REDUNDANTNETWORK
ADAPTER_WARNING_
IBM_UMS_AGENT_
REDUNDANTNETWORK
ADAPTER_INFO_
log event ID
SNMP Not applicable ibmSystemTrapRedundant
NIC
Not applicable
native event
Not applicable IBMPSG_Redundant
Network AdapterEvent
Not applicable
SNMP event
Not applicable UMS_RedundantNetwork
AdapterEvent
Not applicable
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 event Not applicable Not applicable CIM > System > Redundant
Network Adapter
Switchback
interface
Not applicable Not applicable No symbol displayed
Manager 2005 alert
IBM_UMS_AGENT_
REDUNDANTNETWORK
ADAPTERSWITCHBACK_
ERROR_
IBM_UMS_AGENT_
REDUNDANTNETWORK
ADAPTERSWITCHBACK_
WARNING_
IBM_UMS_AGENT_
REDUNDANTNETWORK
ADAPTERSWITCHBACK_
INFO_
log event ID
SNMP Not applicable Not applicable ibmSystemTrapRedundant
NICSwitchback
native event
Not applicable Not applicable IBMPSG_RedundantNetwork
AdapterSwitchbackEvent
SNMP event
Not applicable Not applicable UMS_RedundantNetwork
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 event Not applicable CIM > System > Redundant
Network Adapter
Switchover
Not applicable
interface
Manager 2005 alert
IBM_UMS_AGENT_
REDUNDANTNETWORK
ADAPTERSWITCHOVER_
ERROR_
IBM_UMS_AGENT_
REDUNDANTNETWORK
ADAPTERSWITCHOVER_
WARNING_
IBM_UMS_AGENT_
REDUNDANTNETWORK
ADAPTERSWITCHOVER_
INFO_
log event ID
SNMP Not applicable ibmSystemTrapRedundant
NICSwitchover
Not applicable
native event
Not applicable IBMPSG_RedundantNetwork
AdapterSwitchoverEvent
Not applicable
SNMP event
Not applicable UMS_RedundantNetwork
AdapterSwitchover
Not applicable
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 event Not applicable CIM > System > Remote
Login
Not applicable
interface
Manager 2005 alert
Security Event Security Event Security Event
IBM_UMS_AGENT_
REMOTELOGIN_ERROR_
IBM_UMS_AGENT_
REMOTELOGIN_
WARNING_
IBM_UMS_AGENT_
REMOTELOGIN_INFO_
log event ID
SNMP Not applicable ibmSystemTrapRemoteLogin Not applicable
native event
Not applicable IBMPSG_RemoteLoginEvent Not applicable
SNMP event
Not applicable UMS_RemoteLoginEvent Not applicable
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.
event
CIM > System > SMART
Drive
Drive
Drive
Web interface
Manager 2005 alert
events (Message ID
50090)
IBM_UMS_AGENT_
SMART_ERROR_
IBM_UMS_AGENT_
SMART_WARNING_
IBM_UMS_AGENT_
SMART_INFO_
Microsoft Windows
event log event ID
9 9 9
SNMP ibmSystemTrapSMART Not applicable Not applicable
Tivoli Enterprise
IBMPSG_SMARTEvent IBMPSG_SMARTEvent IBMPSG_SMARTEvent
Tivoli Enterprise
Console SNMP event
UMS_SMARTCritical UMS_SMARTWarning UMS_SMARTNormal
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.
IBM Systems Director event Not applicable Not applicable Not applicable
interface
Manager 2005 alert
Power Supply Event Power Supply Event Power Supply Event
IBM_UMS_AGENT_
SPPOWERSUPPLY_ERROR_
IBM_UMS_AGENT_
SPPOWERSUPPLY_
WARNING_
IBM_UMS_AGENT_
SPPOWERSUPPLY_INFO_
log event ID
SNMP Not applicable ibmSystemTrapSPPower
Supply
Not applicable
native event
IBMPSG_SP_PowerSupply
Event
Event
Event
SNMP event
UMS_SPPowerSupplyEvent UMS_SPPowerSupplyEvent UMS_SPPowerSupplyEvent
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 IBMPSG_StorageEvent CIM indication is not available in Platform Agent version
6.x. When using Platform Agent version 6.x, this CIM indication is not generated
even when the system hard disk drive space meets the low disk condition.
Instead, use a custom monitor view to monitor a low disk condition. For more
information, see Scenario: Using a custom monitor view in an event automation
plan to report disk data by using drive letter names.
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.
event
CIM > System > Disk
Space Low
CIM > System > Disk
Space Low
CIM > System > Disk
Space Low
Web interface
No symbol displayed
Manager 2005 alert
events (Message ID
50070)
IBM_UMS_AGENT_
STORAGE_ERROR_
IBM_UMS_AGENT_
STORAGE_WARNING_
IBM_UMS_AGENT_
STORAGE_INFO_
Microsoft Windows
event log event ID
20 20 Not applicable
SNMP ibmSystemTrapStorage ibmSystemTrapStorage ibmSystemTrapStorage
Tivoli Enterprise
IBMPSG_StorageEvent IBMPSG_StorageEvent IBMPSG_StorageEvent
Tivoli Enterprise
Console SNMP event
UMS_StorageVeryLow UMS_StorageLow UMS_StorageNormal
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:
Note: This function is unavailable when using Platform Agent version 6.x. Instead,
use a custom monitor view to monitor a low disk condition. For more information,
see Scenario: Using a custom monitor view in an event automation plan to report
disk data by using drive letter names.
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:
Note: This function is unavailable when using Platform Agent version 6.x. Instead,
use a custom monitor view to monitor a low disk condition. For more information,
see Scenario: Using a custom monitor view in an event automation plan to report
disk data by using drive letter names.
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 event CIM > System >
Temperature
CIM > System >
Temperature
CIM > System >
Temperature
interface
No symbol displayed
Manager 2005 alert
Temperature Event Temperature Event Temperature Event
IBM_UMS_AGENT_
TEMPERATURE_ERROR_
IBM_UMS_AGENT_
TEMPERATURE_
WARNING_
IBM_UMS_AGENT_
TEMPERATURE_INFO_
log event ID
2 2 2
SNMP ibmSystemTrapTemperature ibmSystemTrapTemperature ibmSystemTrapTemperature
native event
IBMPSG_TemperatureEvent IBMPSG_TemperatureEvent IBMPSG_TemperatureEvent
SNMP event
UMS_Temperature
CriticallyOut OfRange
UMS_Temperature
OutOfRange
UMS_TemperatureNormal
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 event CIM > System > Voltage Not applicable CIM > System > Voltage
interface
Manager 2005 alert
Voltage Event Voltage Event Voltage Event
(Message ID 50030)
IBM_UMS_AGENT_
VOLTAGE_ERROR_
IBM_UMS_AGENT_
VOLTAGE__WARNING_
IBM_UMS_AGENT_
VOLTAGE__INFO_
log event ID
3 Not applicable 3
SNMP ibmSystemTrapVoltage Not applicable ibmSystemTrapVoltage
native event
IBMPSG_VoltageEvent IBMPSG_VoltageEvent IBMPSG_VoltageEvent
SNMP event
UMS_VoltageCriticallyOutOf
Range
UMS_VoltageOutOfRange UMS_VoltageNormal
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 event Not applicable CIM > System > Warranty
Expiration
CIM > System > Warranty
Expiration
interface
Manager 2005 alert
(Message ID 50140)
IBM_UMS_AGENT_
LEASE_ERROR_
IBM_UMS_AGENT_
LEASE_WARNING_
IBM_UMS_AGENT_
LEASE_INFO_
log event ID
SNMP Not applicable ibmSystemTrapWarranty
Expiration
ibmSystemTrapWarranty
Expiration
native event
IBMPSG_WarrantyExpiration
Event
Event
Event
SNMP event
UMS_WarrantyExpired Critical UMS_WarrantyExpired Warning UMS_WarrantyExpired 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 ID 50210) IBM_UMS_AGENT_STORAGERAIDHEALTH_INFO
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
Microsoft SMS native events (Message
ID 50210)
IBM_UMS_AGENT_STORAGERAIDHEALTH_INFO
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
ID 50210)
IBM_UMS_AGENT_STORAGERAIDHEALTH_ERROR
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
Microsoft SMS native events (Message 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
ID 50210)
IBM_UMS_AGENT_STORAGERAIDHEALTH_WARNING
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 Tivoli Enterprise Console
native event
Tivoli Enterprise Console SNMP event ibmSystemRaidFlashCopyComplete
ADPT_FlashCopyDetected CIM indication
This CIM indication is generated when a RAID FlashCopy operation is in progress
native event
Tivoli Enterprise Console SNMP event ibmSystemRaidFlashCopyDetected
ADPT_FlashCopyFail CIM indication
This CIM indication is generated when a RAID FlashCopy operation fails on a
native event
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 > Tivoli Enterprise Console native
event
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 character set (DBCS) information,
contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 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
Dept. LRAS/Bldg. 903
11501 Burnet Road
Austin, TX 78758-3400
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.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
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.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
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
Agent Extension event 228, 229
AIX events
Service Event 67
System Event 69
alarm panel 74
Alert Standard Format 153, 236, 238
array
FlashCopy 31, 32, 177, 255, 256
rebuild 32, 33, 178, 256, 257, 286, 287
synchronization 34, 179, 257, 258
Asset ID task 24, 72, 165, 175, 245, 255
Attribute Changed event 229
automatic server restart 19, 176
B
bad stripe 38, 182, 261
battery 42, 75, 186, 264
Battery events 150
battery-backup cache 42, 186, 265
BIOS 76, 156
blade expansion unit 77
BladeCenter
events 80
products 77
bootstrap loader program 126
C
chassis (See also enclosure) 163, 242
ChassisID.properties file 232
CIM events
Automatic Server Restart 19
DASD Backplane 19
Disk Space Low 20
Event Log 21
extended details 237
Fan 22
Host Bus Adapter 23
IP Change 23
IPMI Log 24
IVM Unconfigured 23
Lease Expiration 24
Life Cycle 25
Memory 25
Memory PFA 26
Network Adapter 26
Network Adapter Failed 26
Network Adapter Offline 26
Network Adapter Online 26
overview 18
PFA 27
Power State 28
Power Supply 29
Processor 30
Processor PFA 30
RAID 31
RAID Array FlashCopy Complete 31
RAID Array FlashCopy Detected 31
CIM events (continued)
RAID Copyback Complete 41
RAID Copyback Detected 41
RAID Copyback Fail 42
RAID Dead Battery 42
RAID Dead Battery Cache 42
RAID Decompression Complete 43
RAID Decompression Detected 43
RAID Decompression Fail 43
RAID Defunct Drive 44
RAID Defunct Drive FRU 44
RAID Defunct Replaced 45
RAID Drive Added 45
RAID Drive Clear Complete 46
RAID Drive Clear Detected 46
RAID Drive Clear Fail 46
RAID Drive Removed 47
RAID Drive Verify Complete 47
RAID Drive Verify Detected 47
RAID Drive Verify Fail 48
RAID Enclosure Fail 48
RAID Enclosure Fan Fail 49
RAID Enclosure Fan Installed 49
RAID Enclosure Fan OK 49
RAID Enclosure Fan Removed 50
RAID Enclosure OK 50
RAID Enclosure Power Supply Fail 50
RAID Enclosure Power Supply Installed 51
RAID Enclosure Power Supply OK 51
RAID Enclosure Power Supply Removed 52
RAID Enclosure Temp Fail 52
RAID Enclosure Temp OK 52
RAID Expansion Complete 53
RAID Expansion Detected 53
RAID Expansion Fail 53
RAID FlashCopy Complete 54
RAID FlashCopy Detected 54
RAID FlashCopy Fail 55
RAID Init Detected 55
RAID Init Fail 56
RAID Logical Drive Added 56
RAID Logical Drive Blocked 57
RAID Logical Drive Critical 57
RAID Logical Drive Critical Periodic 57
RAID Logical Drive Off Line 58
RAID Logical Drive OK 58
RAID Logical Drive Removed 59
RAID Logical Drive Unblocked 59
RAID Migration Complete 59
RAID Migration Detected 59
RAID Migration Fail 60
RAID No Controllers 60
RAID PFA Drive 61
RAID PFA Drive FRU 61
RAID Polling Fail 61
RAID Rebuild Complete 62
RAID Rebuild Detected 62
RAID Rebuild Fail 62
RAID Sync Complete 63
RAID Sync Detected 63
RAID Sync Fail 63
CIM events (continued)
RAID Test Event 64
RAID Unsupported Drive 64
Redundant Network Adapter Failover 65
Redundant Network Adapter Switchback 65
Redundant Network Adapter Switchover 65
Remote Login 66
Server Power Supply 66
ServeRAID Array FlashCopy Fail 32
ServeRAID Array Rebuild Complete 32
ServeRAID Array Rebuild Detected 33
ServeRAID Array Rebuild Fail 33
ServeRAID Array Sync Complete 34
ServeRAID Array Sync Detected 34
ServeRAID Array Sync Fail 34
ServeRAID Compaction Complete 35
ServeRAID Compaction Detected 35
ServeRAID Compaction Fail 35
ServeRAID Compression Complete 36
ServeRAID Compression Detected 36
ServeRAID Compression Fail 37
ServeRAID Config Fail 37
ServeRAID Controller Added 37
ServeRAID Controller Bad Stripes 38
ServeRAID Controller Battery Overtemp 39
ServeRAID Controller Battery Temp Normal 39
ServeRAID Controller Fail 40
ServeRAID Controller Failover 40
ServeRAID Controller Mismatched Versions 40
ServeRAID Controller Replaced 41
Service Event 67
SMART Drive 68
source 235
System 18
System Enclosure 68
System Event 69
Temperature 69
Voltage 72
Warranty Expiration 72
Windows NT Event Log 233
Windows NT Service 233
Windows Registry 233
CIM indications
ADPT_ArrayFlashCopyComplete 255
ADPT_ArrayFlashCopyDetected 256
ADPT_ArrayFlashCopyFail 256
ADPT_ArrayRebuildComplete 256
ADPT_ArrayRebuildDetected 257
ADPT_ArrayRebuildFail 257
ADPT_ArraySyncComplete 257
ADPT_ArraySyncDetected 258
ADPT_ArraySyncFail 258
ADPT_CompactionComplete 258
ADPT_CompactionDetected 259
ADPT_CompactionFail 259
ADPT_CompressionComplete 259
ADPT_CompressionDetected 260
ADPT_CompressionFail 260
ADPT_ConfigFail 260
ADPT_ControllerAdded 261
ADPT_ControllerBadStripes 261
ADPT_ControllerBatteryOvertemp 261
ADPT_ControllerBatteryTempNormal 262
ADPT_ControllerFail 262
ADPT_ControllerFailover 262
ADPT_ControllerMismatchedVersions 263
ADPT_ControllerReplaced 263
CIM indications (continued)
ADPT_CopyBackComplete 263
ADPT_CopyBackDetected 264
ADPT_CopyBackFail 264
ADPT_DeadBattery 264
ADPT_DeadBatteryCache 265
ADPT_DecompressionComplete 265
ADPT_DecompressionDetected 265
ADPT_DecompressionFail 266
ADPT_DefunctDrive 266
ADPT_DefunctDriveFRU 266
ADPT_DefunctReplaced 267
ADPT_DriveAdded 267
ADPT_DriveClearComplete 267
ADPT_DriveClearDetected 268
ADPT_DriveClearFail 268
ADPT_DriveRemoved 268
ADPT_DriveVerifyComplete 269
ADPT_DriveVerifyDetected 269
ADPT_DriveVerifyFail 269
ADPT_EnclosureFail 270
ADPT_EnclosureFanFail 270
ADPT_EnclosureFanInstalled 270
ADPT_EnclosureFanOK 271
ADPT_EnclosureFanRemoved 271
ADPT_EnclosureOK 271
ADPT_EnclosurePowerSupplyFail 272
ADPT_EnclosurePowerSupplyInstalled 272
ADPT_EnclosurePowerSupplyOK 272
ADPT_EnclosurePowerSupplyRemoved 273
ADPT_EnclosureTempFail 273
ADPT_EnclosureTempOK 273
ADPT_ExpansionComplete 274
ADPT_ExpansionDetected 274
ADPT_ExpansionFail 274
ADPT_FlashCopyComplete 275
ADPT_FlashCopyDetected 275
ADPT_FlashCopyFail 275
ADPT_InitComplete 275
ADPT_InitDetected 276
ADPT_InitFail 276
ADPT_LogicalDriveAdded 276
ADPT_LogicalDriveBlocked 276
ADPT_LogicalDriveCritical 277
ADPT_LogicalDriveCriticalPeriodic 277
ADPT_LogicalDriveOffLine 277
ADPT_LogicalDriveOK 278
ADPT_LogicalDriveRemoved 278
ADPT_LogicalDriveUnblocked 278
ADPT_MigrationComplete 279
ADPT_MigrationDetected 279
ADPT_MigrationFail 279
ADPT_NoControllers 280
ADPT_PFADrive 280
ADPT_PFADriveFRU 280
ADPT_PollingFail 281
ADPT_RebuildComplete 281
ADPT_RebuildDetected 281
ADPT_RebuildFail 282
ADPT_SyncComplete 282
ADPT_SyncDetected 282
ADPT_SyncFail 283
ADPT_TestEvent 283
ADPT_UnsupportedDrive 283
conversion 18, 162, 235, 236
IBM_MgmtHwLogStatus 241
IBMPSG_ChassisEvent 242
CIM indications (continued)
IBMPSG_DASDBackplaneEvent 243
IBMPSG_ErrorLogEvent 243
IBMPSG_FanEvent 244
IBMPSG_GenericFanEvent 244
IBMPSG_GenericVoltageEvent 245
IBMPSG_LeaseExpirationEvent 245
IBMPSG_MemoryPFEvent 246
IBMPSG_NetworkAdapterFailedEvent 246
IBMPSG_NetworkAdapterOfflineEvent 247
IBMPSG_NetworkAdapterOnlineEvent 247
IBMPSG_PFAEvent 248
IBMPSG_PowerSupplyEvent 248
IBMPSG_ProcessorPFEvent 249
IBMPSG_RedundantNetworkAdapterEvent 249
IBMPSG_RedundantNetworkAdapterSwitchback-
Event 250
IBMPSG_RedundantNetworkAdapterSwitchover-
Event 250
IBMPSG_RemoteLoginEvent 251
IBMPSG_SMARTEvent 251
IBMPSG_SPPowerSupplyEvent 252
IBMPSG_StorageEvent 252
IBMPSG_TemperatureEvent 254
IBMPSG_VoltageEvent 254
IBMPSG_WarrantyExpirationEvent 255
LSI_RAID_HS_Fail 284
LSI_RAID_LD_Degraded 284
LSI_RAID_LD_Offline 284
LSI_RAID_LD_Optimal 285
LSI_RAID_PD_Fail 285
LSI_RAID_PD_HS 285
LSI_RAID_PD_PartOf_LD_Add 286
LSI_RAID_PD_PartOf_LD_Fail 286
LSI_RAID_RbldComplete 286
LSI_RAID_RbldFail 287
LSI_RAID_RbldStart 287
LSI_RAID_SMART_Error 287
clear 46, 189, 190, 267, 268
Clock Module 83
Common Agent
events 209
compaction 35, 180, 258, 259
compression 36, 37, 181, 259, 260
Computer System events 128
controller
added 37, 182, 261
fail 40, 184, 262
failover 40, 184, 262
mismatched versions 40, 206, 263
none 60, 200, 280
polling 61, 201, 281
replaced 41, 185, 263
copyback 41, 42, 185, 186, 263, 264
Correlation events 232
Created event
virtual farm 231
virtual server 229
D
decompression 43, 187, 265, 266
Deleted event
virtual farm 231
virtual server 229
DIMM 25, 26, 88, 166, 246
Director events
Director Agent 237
Error 213, 214
Job 212
Process Alert 210
Process Failed to Start 210
Process Monitors 209
Process Started 210
Process Terminated 210
Resource Monitors 211
Scheduler 212
Success 213, 214
System 214
Director task events 209
Disk Drive events 151
disk space 253
E
enclosure
BladeCenter chassis 80
fail 48, 191, 270
OK 50, 192, 271
system 68, 163, 242
temperature 52, 205, 206, 273
enclosure fan
fail 49, 193, 270
installed 49, 194, 270
OK 49, 192, 271
removed 50, 194, 271
enclosure power supply
fail 50, 202, 272
OK 51, 202, 272
removed 52, 203, 273
environmental
events 69, 72, 118, 154, 165, 173, 175, 245, 254
error log 21, 24, 163, 166, 241, 243
Ethernet port 140
event
CIM 18
MPA 73
MPA source 235
PET 153, 236
SNMP 161
source 235
Windows Event Log 234
events
disk space 253
expansion 53, 192, 193, 274
expansion card 89
extended details
CIM 237
Director 237
MPA 238
overview 237
PET 238
SNMP 239
F
failover 40, 184, 262
fan 22, 90, 164, 244
Fan events 141
fan pack 91
Index 295
Fibre Channel Port events 142
files
ChassisID.properties 232
IBM-SYSTEM-RAID-MIB.mib 176
IBM-SYSTEM-TRAP-MIB.mib 162
FlashCopy 31, 32, 54, 55, 177, 194, 195, 255, 256, 275
front panel 92
FRU 44, 61, 188, 201, 266, 280
H
hard disk drive
added 45, 189, 267, 286
clear 46, 189, 190, 267, 268
defunct 44, 188, 266, 285, 286
defunct FRU 44, 188, 266
hot spare 45, 189, 267, 284, 285
nonwarranted 64, 206, 283
PFA 61, 201, 280, 287
removed 47, 190, 268
SMART 68, 171, 251
state change 19, 86, 163, 243
storage low 20, 172, 252
unsupported 64, 206, 283
verify 47, 48, 190, 191, 269
hardware
failure events 27, 101, 157, 168, 248
Hardware Console Point 23
hardware events 1
BladeCenter 18
Power 128
Storage 150
System x 18
Hardware Management Console 18, 23, 25, 28, 67, 237
Host Added event 231
Host Bus Adapter events 23
Host Removed event 231
I
I/O board 93
I/O Interposer 94
I/O module 95
IBM-SYSTEM-RAID-MIB.mib 176
IBM-SYSTEM-TRAP-MIB.mib 162
initialization 55, 56, 196, 275, 276
IPMI 24, 166, 241
J
job 209, 210, 211, 212, 213, 214
K
KVM 84
L
lease expiration 24, 165, 245
legal notices 289
Logical device events
processor 148
logical drive
added 56, 197, 276
blocked 57, 197, 276
logical drive (continued)
critical 57, 197, 198, 277
degraded 284
expansion 53, 192, 193, 274
FlashCopy 54, 55, 194, 195, 275
initialization 55, 56, 196, 275, 276
migration 59, 60, 199, 200, 279
offline 58, 198, 277, 284
OK 58, 198, 278, 285
rebuild 62, 203, 204, 281, 282
removed 59, 199, 278
unblocked 59, 199, 278
M
managed systems
state change 18, 31
management module events 74, 75, 76, 77, 79, 80, 83, 84, 86,
88, 89, 90, 91, 92, 93, 94, 95, 98, 99, 100, 101, 104, 106, 107,
109, 114, 115, 117, 118, 126
management module interposer 98
Media Access Device events
Physical Volume 147
media tray 99
memory 25, 26, 88, 166, 246
Memory events 143
MIB file 161, 162, 176
microprocessor 30, 84, 169, 249
migration 59, 60, 199, 200, 279
monitoring 209, 210, 211
MPA events
Alarm Panel 74
Battery 75
BIOS 76
Blade Expansion Unit 77
Blade Server 77
Bus 79
Chassis 80
Clock Module 83
Component 73
Concurrent KVM 84
Configuration 80
CPU 84
DASD 86
DIMM events 88
Environmental 118
Expansion Card 89
Failed 80
Fan 90
Fan Pack 91
Front Panel 92
I/O Board 93
I/O Interposer 94
I/O module 95
Management Module Interposer 98
Media Tray 99
Miscellaneous 125
Multiplexer Expansion Module 100
overview 73
PET events 153
PFA 101
Platform 126
Power Subsystem 101
Power Supply 104
Processor Board 106
MPA events (continued)
RAID 106
Server 107
Server WatchDog 126
Service Processor 109
SMP Expansion Module 113
source 235
Storage Module 114
Unknown 127
USB 115
VRM 117
multiplexer expansion module 100
N
network adapter 26, 65, 167, 169, 170, 246, 247, 249, 250
network device 95
NIC 26, 65, 167, 169, 170, 246, 247, 249, 250
nonwarranted hard disk drive 64, 206, 283
O
operating system
state change 160
operating system events 209
Operating System events 232
Optical Drive events 144
P
PCI Device events 146
PET events
BIOS 156
Boot 160
Cable/Interconnect 157
Case Intrusion 154
Current 154
Drive bay 157
Environmental 154
Fan 154
Firmware 156
Hardware 157
Heartbeat 160
Module/Board 157
Monitor ASIC/IC 157
Network 157
Operation 160
OS 160
overview 153
Power Supply 154
Progress 156
Sensor 154
System 160
Temperature 154
Voltage 154
Watchdog 157
PFA 26, 27, 30, 61, 101, 166, 168, 169, 201, 246, 248, 249, 280,
287
Physical Volume 147
Platform Event Trap 153, 236
polling 61, 201, 281
POST failed 126
power supply 29, 66, 104, 168, 171, 248, 252
Process Monitors events 209, 210
processor 30, 148
processor board 106
pSeries events
IP Change 23
Life Cycle 25
Power State 28
System Event 67, 69
Q
QLogic products 23
R
RAID 106
RAID Controller events 151
RAID events
array
FlashCopy 31, 32, 177, 255, 256
rebuild 32, 33, 178, 256, 257, 286, 287
synchronization 34, 179, 257, 258
battery 39, 42, 186, 261, 262, 264
battery-backup cache 42, 186, 265
compaction 35, 180, 258, 259
compression 36, 37, 181, 259, 260
configuration 37, 182, 260
controller
added 37, 182, 261
bad stripe 38, 182, 261
battery 39, 183, 184, 261, 262
fail 40, 184, 262
failover 40, 184, 262
none 60, 200, 280
polling 61, 201, 281
replaced 41, 185, 263
copyback 41, 42, 185, 186, 263, 264
decompression 43, 187, 265, 266
enclosure
fail 48, 191, 270
OK 50, 192, 271
temperature 52, 205, 206, 273
enclosure fan
fail 49, 193, 270
OK 49, 192, 271
removed 50, 194, 271
enclosure power supply
fail 50, 202, 272
OK 51, 202, 272
removed 52, 203, 273
expansion 53, 192, 193, 274
hard disk drive
added 45, 189, 267, 286
clear 46, 189, 190, 267, 268
defunct 44, 188, 266, 285, 286
defunct FRU 44, 188, 266
hot spare 45, 189, 267, 284, 285
PFA 61, 201, 280, 287
removed 47, 190, 268
unsupported 64, 206, 283
verify 47, 48, 190, 191, 269
initialization 55, 56, 196, 275, 276
logical drive 41, 42, 43, 53, 185, 186, 187, 192, 193, 263,
264, 265, 266, 274
added 56, 197, 276
Index 297
RAID events (continued)
logical drive (continued)
blocked 57, 197, 276
critical 57, 197, 198, 277
degraded 284
FlashCopy 54, 55, 194, 195, 275
initialization 55, 56, 196, 275, 276
migration 59, 60, 199, 200, 279
offline 58, 198, 277, 284
OK 58, 198, 278, 285
rebuild 62, 203, 204, 281, 282
removed 59, 199, 278
synchronization 63, 204, 205, 282, 283
unblocked 59, 199, 278
migration 59, 60, 199, 200, 279
overview 176
polling 61, 201, 281
rebuild 62, 203, 204, 281, 282
synchronization 63, 204, 205, 282, 283
temperature 52, 205, 206, 273
test event 64, 206, 283
rebuild 32, 33, 62, 178, 203, 204, 256, 257, 281, 282, 286, 287
redundant NIC 65, 169, 170, 249, 250
relocating virtual servers
events 229
remote login 66, 170, 251
Remote Supervisor Adapter
Renamed event
virtual farm 231
resource monitors 209
Resource Monitors events 211
S
scalable partition events 126
Scalable Systems Manager 126
scheduled job 209, 210, 211
Scheduler events 212, 213, 214
server
automatic restart 19, 176
service processors
events 74, 75, 76, 77, 79, 83, 84, 86, 88, 89, 90, 91, 92, 93,
94, 98, 99, 100, 101, 104, 106, 107, 109, 113, 114, 115, 117,
118, 125, 126, 127
MPA events 73, 235
SMART drive 68, 171, 251
SMP Expansion Module 113
SNMP events
ibmSystemMIB 162, 236
ibmSystemRaid 176
ibmSystemRaidArrayFlashCopyComplete 177
ibmSystemRaidArrayFlashCopyDetected 177
ibmSystemRaidArrayFlashCopyFail 177
ibmSystemRaidArrayRebuildComplete 178
ibmSystemRaidArrayRebuildDetected 178
ibmSystemRaidArrayRebuildFail 178
ibmSystemRaidArraySyncComplete 179
ibmSystemRaidArraySyncDetected 179
ibmSystemRaidArraySyncFail 179
ibmSystemRaidCompactionComplete 180
ibmSystemRaidCompactionDetected 180
ibmSystemRaidCompactionFail 180
ibmSystemRaidCompressionComplete 181
ibmSystemRaidCompressionDetected 181
ibmSystemRaidCompressionFail 181
SNMP events (continued)
ibmSystemRaidConfigFail 182
ibmSystemRaidControllerAdded 182
ibmSystemRaidControllerBadStripes 182
ibmSystemRaidControllerBatteryOvertemp 183
ibmSystemRaidControllerBatteryTempNormal 184
ibmSystemRaidControllerFail 184
ibmSystemRaidControllerFailover 184
ibmSystemRaidControllerReplaced 185
ibmSystemRaidCopyBackComplete 185
ibmSystemRaidCopyBackDetected 185
ibmSystemRaidCopyBackFail 186
ibmSystemRaidDeadBattery 186
ibmSystemRaidDeadBatteryCache 186
ibmSystemRaidDecompressionComplete 187
ibmSystemRaidDecompressionDetected 187
ibmSystemRaidDecompressionFail 187
ibmSystemRaidDefunctDrive 188
ibmSystemRaidDefunctDriveFRU 188
ibmSystemRaidDefunctReplaced 189
ibmSystemRaidDriveAdded 189
ibmSystemRaidDriveClearComplete 189
ibmSystemRaidDriveClearDetected 189
ibmSystemRaidDriveClearFail 190
ibmSystemRaidDriveRemoved 190
ibmSystemRaidDriveVerifyComplete 190
ibmSystemRaidDriveVerifyDetected 191
ibmSystemRaidDriveVerifyFail 191
ibmSystemRaidEnclosureFail 191
ibmSystemRaidEnclosureFanOK 192
ibmSystemRaidEnclosureOK 192
ibmSystemRaidExpansionComplete 192
ibmSystemRaidExpansionDetected 193
ibmSystemRaidExpansionFail 193
ibmSystemRaidFanFail 193
ibmSystemRaidFanInstalled 194
ibmSystemRaidFanRemoved 194
ibmSystemRaidFlashCopyComplete 194
ibmSystemRaidFlashCopyDetected 195
ibmSystemRaidFlashCopyFail 195
ibmSystemRaidInitComplete 196
ibmSystemRaidInitDetected 196
ibmSystemRaidInitFail 196
ibmSystemRaidLogicalDriveAdded 197
ibmSystemRaidLogicalDriveBlocked 197
ibmSystemRaidLogicalDriveCritical 197
ibmSystemRaidLogicalDriveCriticalPeriodic 198
ibmSystemRaidLogicalDriveOffLine 198
ibmSystemRaidLogicalDriveOK 198
ibmSystemRaidLogicalDriveRemoved 199
ibmSystemRaidLogicalDriveUnblocked 199
ibmSystemRaidMigrationComplete 199
ibmSystemRaidMigrationDetected 200
ibmSystemRaidMigrationFail 200
ibmSystemRaidNoControllers 200
ibmSystemRaidPFADrive 201
ibmSystemRaidPFADriveFRU 201
ibmSystemRaidPollingFail 201
ibmSystemRaidPowerSupplyFail 202
ibmSystemRaidPowerSupplyInstalled 202
ibmSystemRaidPowerSupplyOK 202
ibmSystemRaidPowerSupplyRemoved 203
ibmSystemRaidRebuildComplete 203
ibmSystemRaidRebuildDetected 203
ibmSystemRaidRebuildFail 204
ibmSystemRaidSyncComplete 204
ibmSystemRaidSyncDetected 204
SNMP events (continued)
ibmSystemRaidSyncFail 205
ibmSystemRaidTempFail 205
ibmSystemRaidTempOK 206
ibmSystemRaidTestEvent 206
ibmSystemRaidUnsupportedDrive 206
ibmSystemRaidVersionMismatch 206
ibmSystemTrapChassis 163
ibmSystemTrapDASDBackplane 163
ibmSystemTrapErrorLog 163
ibmSystemTrapFan 164
ibmSystemTrapGenericFan 164
ibmSystemTrapGenericVoltage 165
ibmSystemTrapLeaseExpiration 165
ibmSystemTrapMemoryPF 166
ibmSystemTrapMgmtHwLogStatus 166
ibmSystemTrapNetworkAdapterFailed 167
ibmSystemTrapNetworkAdapterOffline 167
ibmSystemTrapNetworkAdapterOnline 167
ibmSystemTrapPFA 168
ibmSystemTrapPowerSupply 168
ibmSystemTrapProcessorPF 169
ibmSystemTrapRedundantNIC 169
ibmSystemTrapRedundantNICSwitchback 169
ibmSystemTrapRedundantNICSwitchover 170
ibmSystemTrapRemoteLogin 170
ibmSystemTrapSMART 171
ibmSystemTrapSPPowerSupply 171
ibmSystemTrapStorage 172
ibmSystemTrapTemperature 173
ibmSystemTrapVoltage 175
ibmSystemTrapWarrantyExpiration 175
ibmSystemTrapxAutomaticServerRestart 176
overview 161
source 236
variable binding 239
software events 209
State events 230
storage events
battery 150
disk drive 151
RAID controller 151
storage pool 152
storage subsystem 152
storage volume 152
switch 153
Storage Module 114
Storage Pool events 152
Storage Subsystem events 152
Storage Volume events 152
switch 95
Switch events 153
synchronization 34, 63, 179, 204, 205, 257, 258, 282, 283
System p events
IP Change 23
IVM Unconfigured 23
Life Cycle 25
Power State 28
System Event 67, 69
T
Task Failed event 230
temperature 69, 173, 254
timeout settings 126
Topology events
See Operating System events
trademarks 291
U
Upward Integration Modules 162, 236
USB 115
USB Port events 149
V
variable binding 237, 238, 239
verify 47, 48, 190, 191, 269
voltage 72, 165, 175, 245, 254
W
warranty expiration 72, 175, 255
web resources ix
Windows
Event Log events 233, 234
events 233, 234
Index 299
Printed in USA
GC30-4172-03

Fqo0 BK Events Ref

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Fqo0 BK Events Ref

Diunggah oleh

Hak Cipta:

Format Tersedia

IBM Systems

IBM Systems Director

Systems Director. These commands fall into two broad categories:

and IBM Scalable Systems Manager

which provides links to

systems with IBM applications and

systems, see IBM Power

, see IBM System Storage

Managed Resource > Managed System Resource >

xSeries and BladeCenter Server Management

Upward Integration Modules (UIMs). When you configure your

Anda mungkin juga menyukai