EventType.txt Driver File Contents (DOMSA01.exe)

EventCategoryName,EventTypeName,Description
"Storage","RAID:Configuration Updated","Adapter: A New Configuration has been written.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated."
"Storage","Logical Drive State Change","Logical Drive State Changed\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated.\n3: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n4: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","RAID:Initialize Started","Initialization Started.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated."
"Storage","RAID:Initialize Completed","Initialization Completed Successfully.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated."
"Storage","RAID:Initialize Aborted","Initialization Aborted by User.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated."
"Storage","RAID:Initialize Failed","Initialization Failed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated."
"Storage","RAID:Check Consistency Aborted","Check Consistency Aborted by User.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated."
"Storage","RAID:Predictive Failures Exceeded","Reported Predictive Failure.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtChannelNumber\n\tChannel Number on the Adapter for which Trap is Generated.\n3: rtTargetID\n\tDevice ID of the Physical Drive for which Trap is Generated.\n4: rtDriveVendor\n\tVendor Identification String from the SCSI Inquiry Data for the Drive.\n5: rtSenseKey\n\tCheck Condition Sense-Key reported by Physical Drive for which Trap is Generated.\n6: rtASC\n\tCheck Condition Additional Sense Code (ASC) reported by Physical Drive for which Trap is Generated.\n7: rt"
"Storage","RAID:Predictive Failures False","Reported Failure Prediction Threshold Exceeded [FALSE].\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtChannelNumber\n\tChannel Number on the Adapter for which Trap is Generated.\n3: rtTargetID\n\tDevice ID of the Physical Drive for which Trap is Generated.\n4: rtDriveVendor\n\tVendor Identification String from the SCSI Inquiry Data for the Drive.\n5: rtSenseKey\n\tCheck Condition Sense-Key reported by Physical Drive for which Trap is Generated.\n6: rtASC\n\tCheck Condition Additional Sense Code (ASC) reported by Physical Drive for which Trap is Genera"
"Storage","RAID:Consistency Corrected","Check Consistency Operation Completed. Inconsistencies have been Cured.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated."
"Storage","RAID:Reconstruction Started","Reconstruction Started.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated."
"Storage","RAID:Reconstruction Completed","Reconstruction Completed Successfully.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated."
"Storage","RAID:Reconstruction Failed","Reconstruction Failed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated."
"Storage","RAID:Check Condition Status","Command Completed with Sense_Key.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtChannelNumber\n\tChannel Number on the Adapter for which Trap is Generated.\n3: rtTargetID\n\tDevice ID of the Physical Drive for which Trap is Generated.\n4: rtSenseKey\n\tCheck Condition Sense-Key reported by Physical Drive for which Trap is Generated.\n5: rtASC\n\tCheck Condition Additional Sense Code (ASC) reported by Physical Drive for which Trap is Generated.\n6: rtASCQ\n\tCheck Condition Additional Sense Code Qualifier (ASCQ) reported by Physical Drive for which Trap is Generated."
"Storage","RAID:NewDrive Inserted","New Device Inserted.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtChannelNumber\n\tChannel Number on the Adapter for which Trap is Generated.\n3: rtTargetID\n\tDevice ID of the Physical Drive for which Trap is Generated."
"Storage","RAID:Physical Drive State Ready","Drive State Changed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtChannelNumber\n\tChannel Number on the Adapter for which Trap is Generated.\n3: rtTargetID\n\tDevice ID of the Physical Drive for which Trap is Generated.\n4: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n5: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","RAID:Physical Drive State Online","Drive State Changed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtChannelNumber\n\tChannel Number on the Adapter for which Trap is Generated.\n3: rtTargetID\n\tDevice ID of the Physical Drive for which Trap is Generated.\n4: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n5: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","RAID:Physical Drive State Failed","Drive State Changed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtChannelNumber\n\tChannel Number on the Adapter for which Trap is Generated.\n3: rtTargetID\n\tDevice ID of the Physical Drive for which Trap is Generated.\n4: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n5: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","RAID:Physical Drive State Rebuild","Drive State Changed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtChannelNumber\n\tChannel Number on the Adapter for which Trap is Generated.\n3: rtTargetID\n\tDevice ID of the Physical Drive for which Trap is Generated.\n4: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n5: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","RAID:Physical Drive State Hotspare","Drive State Changed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtChannelNumber\n\tChannel Number on the Adapter for which Trap is Generated.\n3: rtTargetID\n\tDevice ID of the Physical Drive for which Trap is Generated.\n4: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n5: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","RAID:Logical Drive State Offline","Drive State Changed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated.\n3: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n4: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","RAID:Logical Drive State Degraded","Drive State Changed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated.\n3: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n4: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","RAID:Logical Drive State Optimal","Drive State Changed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated.\n3: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n4: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","RAID:Logical Drive State Initialize","Drive State Changed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated.\n3: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n4: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","RAID:Logical Drive State Check Consistent","Drive State Changed.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated.\n2: rtLogicalDriveNumber\n\tLogical Drive Number for which Trap is generated.\n3: rtOldDriveState\n\tOld State of Logical/Physical Drive, when a State Change Trap is Generated.\n4: rtNewDriveState\n\tNew State of Logical/Physical Drive, when a State Change Trap is Generated."
"Storage","Disks Status Change","The operational status of a physical disk on the system has changed, as indicated by the event severity."
"Storage","DMTF:Disks Initialization Error","A physical disk drive on the system failed to initialize properly on startup.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfDisksEvSys\n\tThe major functional aspe"
"Storage","DMTF:Disks Configuration Error","A disk drive on the system is not properly configured\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfDisksEvSys\n\tThe major functional aspect of the product causing"
"Storage","DMTF:Disk Controller Initialization Failure","A disk controller on the system failed to initialize properly during system startup.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfDiskControllerEvSys\n\tThe major"
"Storage","DMTF:Disk Controller Configuration Error","A disk controller on the system is not properly configured\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfDiskControllerEvSys\n\tThe major functional aspect of the"
"Storage","DMTF:Mass Store Logical Drives Physical Device Status Change","The status of a Logical Disk Drive (e.g., file system volume) has changed.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfMassStoreLogicalDrivesEvSys\n\tThe major "
"Storage","DMTF:Mass Store Logical Drives HotSpare Activated","The 'hot-swap spare' for an inoperable logical disk drive has been activated.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfMassStoreLogicalDrivesEvSys\n\tThe major"
"Storage","DMTF:Mass Store Logical Drives Logical Device Status Change","logicalDeviceStatusChange\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfMassStoreLogicalDrivesEvSys\n\tThe major functional aspect of the product causing the fault."
"Storage","DMTF:Mass Store Logical Drives Initialization Failure","A logical disk drive on the system failed to initialize properly during system startup.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfMassStoreLogicalDrivesEvSys\n\t"
"Storage","DMTF:Mass Store Logical Drives Configuration Error","A logical disk drive on the system is not properly configured\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfMassStoreLogicalDrivesEvSys\n\tThe major functional aspec"
"Storage","Number Of Hard Drives Increased","The security settings for the system chassis or physical container in the system have been modified.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dellConfigurationEvSys\n\tThe major functional"
"Storage","Number Of Hard Drives Decreased","The security settings for the system chassis or physical container in the system have been modified.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dellConfigurationEvSys\n\tThe major functional"
"Storage","IDE SMART Pre-Failure","The security settings for the system chassis or physical container in the system have been modified.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dellIDESMARTDriveEvSys\n\tThe major functional"
"Storage","SCSI SMART Pre-Failure","The security settings for the system chassis or physical container in the system have been modified.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dellSCSISMARTDriveEvSys\n\tThe major functiona"
"Storage","Storage Controller State Change","CIO storage controller has changed state.\nVariables:\n1: cycSeverity\n\tSeverity level of the trap.\n\t cycObject\n\tThe object identifier of the object referred to by the trap.\n3: cycPhysicalObjectState\n\tNew state for the object referred to by the trap."
"Storage","Bus Port State Change","CIO bus port has changed state.\nVariables:\n1: cycSeverity\n\tSeverity level of the trap.\n\t cycObject\n\tThe object identifier of the object referred to by the trap.\n3: cycPhysicalObjectState\n\tNew state for the object referred to by the trap."
"Storage","Storage Device State Change","CIO storage device has changed state.\nVariables:\n1: cycSeverity\n\tSeverity level of the trap.\n\t cycObject\n\tThe object identifier of the object referred to by the trap.\n3: cycPhysicalObjectState\n\tNew state for the object referred to by the trap."
"Storage","Volume Set State Change","CIO volume set has changed state.\nVariables:\n1: cycSeverity\n\tSeverity level of the trap.\n\t cycObject\n\tThe object identifier of the object referred to by the trap.\n3: cycVolumeSetState\n\tNew state for the object referred to by the trap."
"Storage","Volume Set Activity Change","CIO volume set has changed activity.\nVariables:\n1: cycSeverity\n\tSeverity level of the trap.\n\t cycObject\n\tThe object identifier of the object referred to by the trap.\n3: cycVolumeSetActivity\n\tNew activity for the object referred to by the trap.\n4: cycVolumeSetActivityState\n\tStatus of a new activity for the object referred to by the trap."
"Storage","Spare State Change","CIO spare has changed state.\nVariables:\n1: cycSeverity\n\tSeverity level of the trap.\n\t cycObject\n\tThe object identifier of the object referred to by the trap.\n3: cycSpareState\n\tNew state for the object referred to by the trap."
"Storage","Enclosure State Change","A component in CIO enclosure has changed state.\nVariables:\n1: cycSeverity\n\tSeverity level of the trap.\n\t cycObject\n\tThe object identifier of the object referred to by the trap.\n3: cycEnclosureComponent\n\tThe part of the enclosure affected by this trap.\n4: cycEnclosureComponentNumber\n\tThe ordinal number of the part of the enclosure affected by this trap. Numbers ordinarily start at 1, such as Fan 1. A number of 0 refers to all such parts as a single piece. For example, Fan 0 refers to all fans.\n5: cycEnclosureComponentState\n\tDescription of the change in status in the affected enclosure part."
"Storage","Hard Disk Space Threshold Warning","Hard disk drive free space is below user-defined threshold."
"Storage","Lost Storage System","Lost Connection with Storage System.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Storage","Connected Storage System","Connected to Storage System.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n\t AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Storage","Reconnected Storage System","Reconnected to Storage System.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n\t AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Storage","Fibre Channel Switch Power-up diagnostic fault status changed","The Fibre Channel Switch Power-Up Diagnostic Fault Status (swFault)\nVariables:\n1: swDiagResult\n\tThe result from the last power-up diagnostic. 	 2		central-memory-fault 	 3		embedded-port-fault "
"Storage","Fibre Channel Switch environment sensor status changed","A Fibre Channel Switch environment sensor status has changed. A sensor might be a fan, temperature or power-supply sensor\nVariables:\n1: swSensorStatus\n\tThe current status of the sensor.\n\t swSensorIndex\n\tA unique index value assigned to each sensor.\n3: swSensorType\n\tSensor type value\n4: swSensorValue\n\tValue of the sensor\n5: swSensorInfo\n\tSensor Information"
"Storage","Fibre Channel port changed status","The Fibre Channel Port status has changed.\nVariables:\n1: swFCPortOpStatus\n\tAn operational status associated with this FC port.\n\t swFCPortIndex\n\tA unique index value assigned to each FC Port."
"Storage","Switch:Event Log message trap","Event Log message trap. This trap is generated when an event whose level at or below swEventTrapLevel occurs.\nVariables:\n1: swEventIndex\n\tEventlog message index\n\t swEventTimeInfo\n\ttimestamp of the message\n3: swEventLevel\n\tSeverity level of the message\n4: swEventRepeat\n\tmessage repeat count\n5: swEventDescr\n\tmessage description"
"Storage","Array Disk Failed","%s,  %s failed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Array Disk Removed","%s, %s removed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Array Disk Off line","%s, %s offline.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Array Disk Degraded","%s, %s degraded.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Array Disk Inserted","%s, %s inserted.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Virtual Disk Created","%s, virtual disk (%s) created.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Deleted","%s, virtual disk (%s) deleted.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Config Changed","%s, virtual disk (%s) configuration changed from %s to %s\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated.\n3: oldVDConfigEv\n\tCurrent Virtual Disk configuration for which trap is generated\n4: newVDConfigEv\n\tNew Virtual Disk configuration for which trap is generated."
"Storage","Virtual Disk Failed","%s, virtual disk (%s) failed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Degraded","%s, virtual disk (%s) degraded.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Failed Redundancy","%s, virtual disk (%s) is no longer redundant.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Check Consistency Started","%s, virtual disk (%s) check consistency started.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Format Started","%s, virtual disk (%s) format started.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Format Started","%s, %s format started.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Virtual Disk Initialize Started","%s, virtual disk (%s) initialization started.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Initialize Started","%s, %s initialize started.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Virtual Disk Reconfig Started","%s, virtual disk (%s) reconfiguration from %s stripe size to %s stripe size started.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated.\n3: oldVDConfigEv\n\tCurrent Virtual Disk configuration for which trap is generated\n4: newVDConfigEv\n\tNew Virtual Disk configuration for which trap is generated."
"Storage","Virtual Disk Rebuild Started","%s, virtual disk (%s) rebuild started.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Rebuild Started","%s, %s rebuild started.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Array Disk Diag Started","%s, %s diagnostics started.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Check Consistency Cancelled","%s, virtual disk (%s) consistency check cancelled.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Format Cancelled","%s, virtual disk (%s) format cancelled.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Format Cancelled","%s, %s format cancelled.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Virtual Disk Initialize Cancelled","%s, virtual disk (%s) initialization cancelled.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Initialize Cancelled","%s, %s initialize cancelled.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Virtual Disk Reconfig Cancelled","%s, virtual disk (%s) reconfiguration cancelled.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Rebuild Cancelled","%s, virtual disk (%s) rebuild cancelled.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Rebuild Cancelled","%s, %s rebuild cancelled.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Array Disk Diag Cancelled","%s, %s diagnostics cancelled.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Check Consistency Failed","%s, virtual disk (%s) consistency check failed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Format Failed","%s, virtual disk (%s) format failed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Format Failed","%s, %s format failed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Virtual Disk Initialize Failed","%s, virtual disk (%s) initialization Failed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Initialize Failed","%s, %s initialize failed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Virtual Disk Reconfig Failed","%s, virtual disk (%s) reconfiguration failed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Rebuild Failed","%s, virtual disk (%s) rebuild failed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Rebuild Failed","%s, %s rebuild failed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Array Disk Diag Failed","%s, %s diagnostics failed.\nVariablesz\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Check Consistency Completed","%s, virtual disk (%s) consistency check completed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Format Completed","%s, virtual disk (%s) format completed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Format Completed","%s, %s format completed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Virtual Disk Initialize Completed","%s, virtual disk (%s) initialization completed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Initialize Completed","%s, %s initialize completed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Virtual Disk Reconfig Completed","%s, virtual disk (%s) reconfiguration completed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Virtual Disk Rebuild Completed","%s, virtual disk (%s) rebuild completed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: virtualDiskNameEv\n\tVirtual Disk for which trap is generated."
"Storage","Array Disk Rebuild Completed","%s, %s rebuild completed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Array Disk Diag Completed","%s, %s diagnostics completed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Perc Predictive Failure","%s, %s reported predictive failure.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Perc SCSI Sense Data","%s, %s SCSI sense failure.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Controller Battery Needs Reconditioning","%s battery needs reconditioning.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated."
"Storage","Controller Battery Low","%s battery low\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated."
"Storage","Controller Battery Recondition","%s battery is reconditioning.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated."
"Storage","Controller Battery Recon Complete","%s battery reconditioning completed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated."
"Storage","Controller Pause IO","%s I/O paused, I/O will automatically resume after the allotted time.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated."
"Storage","Controller Resume IO","%s I/O resumed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated."
"Storage","Perc2 Smart FPT Exceeded","%s SMART:FPT_EXCEEDED on %s.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Perc2 Smart Config Change","%s SMART configuration change on %s.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Perc2 Smart Warning","%s SMART Warning on %s.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Perc2 Smart Warning Temp","%s SMART Warning temperature on %s.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Perc2 Smart Warning Degraded","%s SMART warning degraded on %s.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Storage","Perc2 Smart FPT Exceeded Test","%s, On %s the failure prediction threshold exceeded due to test-No action needed.\nVariables:\n1: controllerNameEv\n\tController Name for which trap is generated.\n2: arrayDiskNameEv\n\tArray Disk for which trap is generated."
"Processor","DMTF:Processor Failure","A processor in the system has failed\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfProcessorEvSys\n\tThe major functional aspect of the product causing the fault."
"Processor","DMTF:Processor System Up","A system processor is now up and running.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfProcessorEvSys\n\tThe major functional aspect of the product causing the faul"
"Processor","DMTF:Processor Initialization Failure","A system processor failed to initialize properly during system startup.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfProcessorEvSys\n\tThe major functional aspect"
"Processor","DMTF:Processor Configuration Error","A system processor is not properly configured\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfProcessorEvSys\n\tThe major functional aspect of the product causing the"
"Processor","Processor Type Changed","The security settings for the system chassis or physical container in the system have been modified.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dellConfigurationEvSys\n\tThe major"
"Processor","Number Of Processors Increased","The security settings for the system chassis or physical container in the system have been modified.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dellConfigurationEvSys\n\tThe major functional"
"Processor","Number Of Processors Decreased","The security settings for the system chassis or physical container in the system have been modified.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dellConfigurationEvSys\n\tThe major functional"
"Processor","Processor Serial Number Changed","Processor Serial number has changed."
"Processor","DMTF:Motherboard Processor Failure","A processor on the system motherboard has failed or been fixed according to the event severity indicated.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfMotherboardEvSys"
"Environmental","DMTF:Temperature Probe Cooling Device Status Change","A temperature probe on the system has detected an abnormal change in temperature of the system or a system component.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfTemperatureProbeEvSys "
"Environmental","Temperature Failure","Temperature sensor detected a failure.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Environmental","Temperature Failure returned to Normal","Temperature sensor reading of failure returned to normal\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Environmental","Temperature Warning returned to Normal","Temperature sensor warning returned to normal.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Environmental","Temperature High","Temperature high - warning status."
"Environmental","Temperature Low","Temperature low - warning status."
"Environmental","Temperature Too High","Temperature too high - critical status."
"Environmental","Temperature Too Low","Temperature too low - critical status."
"Environmental","Temperature Probe Malfunction","Temperature probe malfunctioning or missing."
"Environmental","Temperature Fault - Non Critical","Temperature Values in non critical status"
"Environmental","Temperature Fault - Critical","Temperature Values in critical"
"Environmental","Temperature Fault - Non Recoverable","Temperature Values in non recoverable status"
"Environmental","Drac2 Temperature Good","This trap is sent each time a temperature channel reading	comes back in normal range.\nVariables:\n1: tempModIndex\n\tA link into the module table (modTable). This identifies which environmental device this temperature is associated with.\n\t tempIndex\n\tThis column is used to identify a particular temperature measurement channel.\n3: tempReading\n\tThe measured temperature.Units=Degrees Celcius\n4: perc\n\tPartial Object Name"
"Environmental","Drac2 Temperature Warning","This trap is sent each time a temperature channel reading goes out of warning range.\nVariables:\n1: tempModIndex\n\tA link into the module table (modTable). This identifies which environmental device this temperature is associated with.\n\t tempIndex\n\tThis column is used to identify a particular temperature measurement channel.\n3: tempReading\n\tThe measured temperature.Units=Degrees Celcius\n4: perc\n\tPartial Object Name"
"Environmental","Drac2 Temperature Critical","This trap is sent each time a temperature channel reading goes out of warning range.\nVariables:\n1: tempModIndex\n\tA link into the module table (modTable). This identifies which environmental device this temperature is associated with.\n\t tempIndex\n\tThis column is used to identify a particular temperature measurement channel.\n3: tempReading\n\tThe measured temperature.Units=Degrees Celcius\n4: perc\n\tPartial Object Name"
"Power","Current Failure","Current sensor detected a failure.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Current Failure returned to Normal","Current sensor reading of failure returned to normal.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Current Warning","Current sensor warning detected.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Current Warning returned to Normal","Current sensor warning returned to normal.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Environmental","Fan Enclosure Insertion","Fan enclosure has been inserted into system.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","Fan Enclosure Removal","Fan enclosure has been removed from system.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","Fan Enclosure Extended Removal","Fan enclosure has been removed from system for an extended amount of time.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","Fan Failure returned to Normal","Fan sensor reading of failure returned to normal.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Environmental","Fan Warning returned to Normal","Fan sensor warning returned to normal.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Environmental","DMTF:Cooling Device Temperature Fault","A temperature fault has been detected by a cooling device (e.g., fan) on the system. The system or a system component is either over-heating or too cold. Probable causes include an inoperable or obstructed cooling device; or insufficient ventilation around the system. This condition can lead to eventual breakdown of the system if left unattended.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 in"
"Environmental","DMTF:Physical Container Cooling Device Status Change","The cooling device for an associated system chassis or physical container has changed status.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPhysicalContainerGlobalEvSys\n\tThe major "
"Environmental","Cooling Device Speed High","Fan speed high - warning status."
"Environmental","Cooling Device Speed Low","Fan speed low - warning status."
"Environmental","Cooling Device Speed Too High","Fan speed too high - critical status."
"Environmental","Cooling Device Speed Too Low","Fan speed too low - critical status."
"Environmental","Cooling Device Malfunction","Cooling Device malfunctioning or missing."
"Environmental","Cooling Device Normal","Cooling device sensor has returned to a normal value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","Cooling Device Warning","Cooling device sensor has detected a warning value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","Cooling Device Failure","Cooling device sensor has detected a failure value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","Cooling Device Status Change - OK (Fan)","Fan speed normal"
"Environmental","Cooling Device Status Change - Non Critical (Fan)","Cooling device in non critical status"
"Environmental","Cooling Device Status Change - Critical (Fan)","Cooling device in critical status"
"Environmental","Cooling Device Status Change - Non Recoverable (Fan)","Cooling device in non recoverable status"
"Environmental","Cooling Device Status Change - OK (Temperature Probe)","Fan speed normal"
"Environmental","Cooling Device Status Change - Non Critical (Temperature Probe)","Cooling device in non critical status"
"Environmental","Cooling Device Status Change - Critical (Temperature Probe)","Cooling device in critical status"
"Environmental","Cooling Device Status Change - Non Recoverable (Temperature Probe)","Cooling device in non recoverable status"
"Environmental","Cooling Device Status Change - OK (Electric Current)","Cooling Device Status Change - non critical status"
"Environmental","Cooling Device Status Change - Non Recoverable (Electric Current)","Cooling device in non recoverable status"
"Environmental","Cooling Device Status Change - Critical (Electric Current)","Cooling Device Status Change - critical status"
"Environmental","Cooling Device Status Change - Non Critical (Electric Current)","Cooling Device Status Change - non critical status"
"Environmental","Cooling Device Status Change - OK (Physical Container)","Fan speed Normal"
"Environmental","Cooling Device Status Change - Non Recoverable (Physical Container)","Cooling device in non recoverable status"
"Environmental","Cooling Device Status Change - Critical (Physical Container)","Cooling Device Status Change - critical status"
"Environmental","Cooling Device Status Change - Non Critical (Physical Container)","Cooling Device Status Change - non critical status"
"Network","CLAN:Internal Error","cLAN Software detected nonrecoverable internal error.\nVariables:\n1: cLANTrSequence\n\tA counter of the number of cLAN traps generated since the agent was last initialized.\n\t cLANTrText\n\tAn ASCII string describing the cLAN alarm cause.\n3: cLANTrType\n\tThe Type number of the described cLAN alarm. See TRAP-TYPE macro definitions later in this MIB or product operations manual for a list of alarm types currently generated.\n4: cLANTrTime\n\tThe time that the condition or event occurred which caused generation of this alarm. This value is given in seconds since 00:00:00 GMT January 1, 1970.\n5: cLANTrDiagId\n\tcLAN internal event ID.\n6: cLANTrNicNumber\n\tNumber of the NIC card which detected alarm condition."
"Network","CLAN:Remote Node Up","cLAN Software detected new Node in a cluster.\nVariables:\n1: cLANTrSequence\n\tA counter of the number of cLAN traps generated since the agent was last initialized.\n\t cLANTrText\n\tAn ASCII string describing the cLAN alarm cause.\n3: cLANTrType\n\tThe Type number of the described cLAN alarm. See TRAP-TYPE macro definitions later in this MIB or product operations manual for a list of alarm types currently generated.\n4: cLANTrTime\n\tThe time that the condition or event occurred which caused generation of this alarm. This value is given in seconds since 00:00:00 GMT January 1, 1970.\n5: cLANTrDiagId\n\tcLAN internal event ID.\n6: cLANTrNicNumber\n\tNumber of the NIC card which detected alarm condition."
"Network","CLAN:Remote Node Down","cLAN Software lost contact with remote Node in a cluster.\nVariables:\n1: cLANTrSequence\n\tA counter of the number of cLAN traps generated since the agent was last initialized.\n\t cLANTrText\n\tAn ASCII string describing the cLAN alarm cause.\n3: cLANTrType\n\tThe Type number of the described cLAN alarm. See TRAP-TYPE macro definitions later in this MIB or product operations manual for a list of alarm types currently generated.\n4: cLANTrTime\n\tThe time that the condition or event occurred which caused generation of this alarm. This value is given in seconds since 00:00:00 GMT January 1, 1970.\n5: cLANTrDiagId\n\tcLAN internal event ID.\n6: cLANTrNicNumber\n\tNumber of the NIC card which detected alarm condition."
"Network","CLAN:Data Corruption","cLAN Software detected data corruption in the cluster fabric.\nVariables:\n1: cLANTrSequence\n\tA counter of the number of cLAN traps generated since the agent was last initialized.\n\t cLANTrText\n\tAn ASCII string describing the cLAN alarm cause.\n3: cLANTrType\n\tThe Type number of the described cLAN alarm. See TRAP-TYPE macro definitions later in this MIB or product operations manual for a list of alarm types currently generated.\n4: cLANTrTime\n\tThe time that the condition or event occurred which caused generation of this alarm. This value is given in seconds since 00:00:00 GMT January 1, 1970.\n5: cLANTrDiagId\n\tcLAN internal event ID.\n6: cLANTrNicNumber\n\tNumber of the NIC card which detected alarm condition."
"Network","Link Down","A linkDown trap signifies that the sending protocol entity recognizes a failure in one of the communication links represented in the agent's configuration. The data passed with the event is 1) The name and value of the ifIndex instance for the affected interface. The name of the interface can be retrieved via an snmpget of .1.3.6.1.2.1.2.2.1.2.INST, where INST is the instance returned with the trap "
"Network","Link Up","A linkUp trap signifies that the sending protocol entity recognizes that one of the communication links represented in the agent's configuration has come up. The data passed with the event is 1) The name and value of the ifIndex instance for the affected interface. The name of the interface can be retrieved via an snmpget of .1.3.6.1.2.1.2.2.1.2.INST, where INST is the instance returned with the trap "
"Network","SNMP Authen Failure","An authentication failure trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated. While implementations of the SNMP must be capable of generating this trap, they must also be capable of suppressing the emission of such traps via an implementation- specific mechanism. HP-UX only: On HP-UX agents, the valid community names can be found in the /etc/snmpd.conf file. The IP address that caused the authentication failure can be determined by either looking in the log file (snmpd.log), or by doing an snmpwalk on the SNMP variable .iso.org.dod.internet.private.enterprises.hp.nm.snmp. authfail.authFailTable.authFailEntry This event is sent when an entity does an SNMPGET with a community name that does not match the get-community name in /etc/snmpd.conf. It also is sent when an entity does an SNMPSET with a community name that does not match the set-community name AND does not match the get-community name."
"Network","SNMP EGP Down","An egpNeighborLoss trap signifies that an EGP neighbor for whom the sending protocol entity was an EGP peer has been marked down and the peer relationship no longer obtains. The data passed with the event is 1) The name and value of the ifIndex egpNeighAddr for the affected neighbor "
"Security","DMTF:System Hardware Security Container Security Breach","A secruity breach of the system hardware has occured. A secured component of the physical system has been accessed without proper authorization.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event."
"Security","DMTF:Physical Container Configuration Error","A chassis or other physical container on the system is not properly configured.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPhysicalContainerGlobalEvSys\n\tThe major functional aspect of"
"Security","Security Settings Change - OK","Security Settings Change - OK status"
"Security","Security Settings Change - Non Critical","Security Settings Change - non critical status"
"Security","Security Settings Change - Critical","Security Settings Change - critical status"
"Power","RAID:Battery Temperature High","Battery Module Temperature Exceeded Danger Threshold.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated."
"Power","RAID:Battery Voltage Low","Battery Module Voltage is Low.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated."
"Power","RAID:Battery Missing","Battery Module is missing.\nVariables:\n1: rtAdapterNumber\n\tAdapter Number for which Trap is generated."
"Power","DMTF:Power Supply Status Change","The operational status of a power supply on the system has changed according to the event severity indicated.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPowerSupplyEvSys "
"Power","DMTF:Power Supply Redundancy Change","The Power Supply Redundancy status has changed.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPhysicalContainerGlobalEvSys\n\tThe major functional aspect of the product causing the fault."
"Power","DMTF:Structure Dependency Battery Status Change","A battery powering the system has changed status.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfStructureDependencyEvSys\n\tThe major functional aspect of the product causing the fault."
"Power","DMTF:Portable Battery Low Combined Batteries Charge","The combined charge of all batteries in the portable computer is running low.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPortableBatteryEvSys\n\tThe major functional aspect of the "
"Power","DMTF:Portable Battery Critical Combined Batteries Charge","The combined charge of all batteries in the portable computer is critcally low.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPortableBatteryEvSys\n\tThe major functional aspect of the "
"Power","DMTF:Portable Battery Maintenance Required","A battery in the portable computer is defective and requires maintenance.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPortableBatteryEvSys\n\tThe major functional aspect of the product"
"Power","Voltage Failure","Voltage sensor detected a failure.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Voltage Failure returned to Normal","Voltage sensor reading of failure returned to normal.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Voltage Warning","Voltage sensor warning detected.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Voltage Warning Normal","Voltage sensor warning returned to normal.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Voltage High","Voltage high - warning status."
"Power","Voltage Low","Voltage low - warning status."
"Power","Voltage Too High","Voltage too high - critical status."
"Power","Voltage Too Low","Voltage too low - critical status."
"Power","Voltage Probe Malfunction","Voltage probe malfunctioning or missing."
"Power","Voltage Probe Non Recoverable","Voltage probe has detected a non recoverable value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Power","Power Supply Lost Redundancy","Power supply lost redundancy detected.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Power Supply Redundancy Normal","Power supply regained redundancy.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Power Supply Degraded Redundancy","Power supply degraded redundancy detected.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Power Supply Degraded Redundancy Normal","Power supply degraded redundancy returned to normal.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Power Supply Failure","Power supply detected a failure.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Power Supply Failure returned to Normal","Power supply failure returned to normal.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Power","Electric Current High","Electrical Current high - warning status."
"Power","Electric Current Low","Electrical Current low - warning status."
"Power","Electric Current Too High","Electrical Current too high - critical status."
"Power","Electric Current Too Low","Electrical Current too low - critical status."
"Power","Electric Current Probe Malfunction","Electrical probe malfunctioning or missing."
"Power","Current Probe Non Recoverable","Amperage probe has detected a non recoverable value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."Power","Power Supply Status Change - OK (Electric Current)","Power Supply Status Change - OK status"
"Power","Power Supply Status Change - OK (Electric Current)","Power Supply Status Change - OK status"
"Power","Power Supply Status Change - Non Critical (Electric Current)","Power Supply Status Change - non critical status"
"Power","Power Supply Status Change - Critical (Electric Current)","Power Supply Status Change - critical status"
"Power","Power Supply Status Change - Non Recoverable (Electric Current)","Power Supply Status Change - non recoverable status"
"Power","Power Supply Status Change - OK (Power Supply)","Power Supply Status Change - OK status"
"Power","Power Supply Status Change - Non Critical (Power Supply)","Power Supply Status Change - non critical status"
"Power","Power Supply Status Change - Critical (Power Supply)","Power Supply Status Change - critical status"
"Power","Power Supply Status Change - Non Recoverable (Power Supply)","Power Supply Status Change - non recoverable status"
"Power","Power Supply Status Change - OK (Voltage Probe)","Power Supply Status Change - OK status"
"Power","Power Supply Status Change - Non Critical (Voltage Probe)","Power Supply Status Change - non critical status"
"Power","Power Supply Status Change - Critical (Voltage Probe)","Power Supply Status Change - critical status"
"Power","Power Supply Status Change - Non Recoverable (Voltage Probe)","Power Supply Status Change - non recoverable status"
"Power","Power Supply Status Change - OK (Physical Container)","Power Supply Status Change - OK status"
"Power","Power Supply Status Change - Non Critical (Physical Container)","Power Supply Status Change - non critical status"
"Power","Power Supply Status Change - Critical (Physical Container)","Power Supply Status Change - critical status"
"Power","Power Supply Status Change - Non Recoverable (Physical Container)","Power Supply Status Change - non recoverable status"
"Power","Power Control Request - OK","Power Control Request - OK status"
"Power","Power Control Request - Non Critical","Power Control Request - non critical status"
"Power","Power Control Request - Critical","Power Control Request - critical status"
"Power","DMTF:UPS Battery Status Change","The UPS Battery has changed status according to the event severity indicated.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfUPSBatteryEvSys\n\tThe major functional "
"Power","DMTF:UPS Battery Utility Power Lost System On Battery","The system has lost primary power and is now running on UPS Battery.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfUPSBatteryEvSys\n\tThe major functional aspect of"
"Power","DMTF:UPS Battery Utility Power Up System Off Battery","Primary power to the system has been restored. The UPS battery is no longer in use.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfUPSBatteryEvSys\n\tThe major "
"Power","Drac2 Voltage Good","This trap is sent each time a voltage channel reading comes back in normal range.\nVariables:\n1: voltModIndex\n\tA link into the module table (modTable). This identifies which environmental device is associated with this voltage.\n\t voltIndex\n\tThis column is used to identify a particular voltage	measurement channel.\n3: voltReading\n\tThe measured voltage.Units=Millivolts\n4: perc\n\tPartial Object Name\n5: perc\n\tPartial Object Name"
"Power","Drac2 Battery Good","This trap is sent each time a battery with low charge is re-charged above the specified low threshold.\nVariables:\n1: batteryModIndex\n\tA link into the module table (modTable). This identifies which device this battery is associated with.\n\t batteryIndex\n\tThis column is used to identify a particular battery.\n3: perc\n\tPartial Object Name"
"Memory","Single Bit ECC Error","Single bit memory ECC error."
"Memory","Multi Bit ECC Error","Multi bit memory ECC error."
"Memory","Memory Device Warning","Memory device pre-failure sensor has detected a warning value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Memory","Memory Device Failure","Memory device pre-failure sensor has detected a failure value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Memory","Memory Device Non Recoverable","Memory device pre-failure sensor has detected a non recoverable value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Memory","Memory ECC Error - OK","Memory ECC Error - OK status"
"Memory","Memory ECC Error - Non Critical","Memory ECC Error - non critical status"
"Memory","Memory ECC Error - Critical","Memory ECC Error - critical status"
"Memory","Memory ECC Error - Non Recoverable","Memory ECC Error - non recoverable status"
"Memory","Memory Error - OK","Memory Error - OK status"
"Memory","Memory Error - Non Critical","Memory Error - non critical status"
"Memory","Memory Error - Critical","Memory Error - critical status"
"Memory","Memory Error - Non Recoverable","Memory Error - non recoverable status"
"Memory","DMTF:Logical Memory Error","A an error has occured in the system's logical memory space.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfLogicalMemoryEvSys\n\tThe major functional aspect of the"
"Memory","DMTF:Logical Memory Initialization Failure","An error occured while initializing the system's memory.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfLogicalMemoryEvSys\n\tThe major functional aspect of the"
"Memory","DMTF:System Cache Memory Error","A memory module in the system cache failed.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfSystemCacheEvSys\n\tThe major functional aspect of the product causing the"
"Memory","DMTF:System Cache Initialization Failure","The System Cache failed to initialize properly during system startup.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfSystemCacheEvSys\n\tThe major functional aspect"
"Memory","DMTF:Physical Memory Array Error","A physical memory module in the system has failed.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPhysicalMemoryArrayEvSys\n\tThe major functional aspect of the prod"
"Memory","DMTF:Physical Memory Array Initialization Failure","A physical memory module in the system failed to initialize properly during system startup.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPhysicalMemoryArrayEvSys\n\t"
"Memory","Memory Size Increased","The security settings for the system chassis or physical container in the system have been modified.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dellConfigurationEvSys\n\tThe major functional"
"Memory","Memory Size Decreased","The security settings for the system chassis or physical container in the system have been modified.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dellConfigurationEvSys\n\tThe major functional"
"Software","System Up - OK","System Up.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n\t AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Software","System Up - Non Critical","System Up - non critical status"
"Software","System Up - Critical","System Up - critical status"
"Operating System","SNMP Cold Start","A coldStart trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered. "
"Operating System","SNMP Warm Start","A warmStart trap signifies that the sending protocol entity is reinitializing itself such that neither the agent configuration nor the protocol entity implementation is altered. "
"Other","DMTF:Event Indication","A DMI Event associated with a group within a DMI component has occurred. Normally, DMI Events are translated into event specific SNMP notifications instead of this generic notification. However, this generic notification is defined for cases when mapping the DMI event to a specific SNMP trap is not possible (e.g., the DMI Class to SNMP OID mapping is not defined).\nVariables:\n1: dmiEventClassString\n\tThe Event Group class string used, along with the event type, to uniquely identify the DMI Event when translated into the general dmiEventIndication trap format.\n2: dmiEventType\n\tEvent-specific information that identifies the type of event within the DMI Event Generation group. Normally, this information is conveyed in the resulting SNMP Notification OID derived from the DMI Event to SNMP Trap mapping procedure. "
"Other","DMTF:Component Added Indication","A new component has been installed into the DMI Service Layer.\nVariables:\n1: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n2: dmiCompName\n\tThe value of the 'name' statement from the component definition block."
"Other","DMTF:Component Deleted Indication","An installed component has been uninstalled from the DMI Service Layer.\nVariables:\n1: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one."
"Other","DMTF:Language Added Indication","A new language binding has been added to a component in the DMI Service Layer.\nVariables:\n1: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n2: dmiLanguage\n\tThe language string, defined by the DMI 2.0 Specification, that identifies a native language character set supported by the component. The format of the string is: 'language-code|territory-code|encoding' where language-code is one of the two-letter codes defined in ISO 639, territory-code is one of the two leteter codes defined in ISO 3166, and encoding is either 'iso8859-1' or 'unicode'."
"Other","DMTF:Language Deleted Indication","An existing language binding has been removed from a component in the DMI Service Layer.\nVariables:\n1: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n2: dmiLanguage\n\tThe language string, defined by the DMI 2.0 Specification, that identifies a native language character set supported by the component. The format of the string is: 'language-code|territory-code|encoding' where language-code is one of the two-letter codes defined in ISO 639, territory-code is one of the two leteter codes defined in ISO 3166, and encoding is either 'iso8859-1' or 'unicode'."
"Other","DMTF:Group Added Indication","A new group has been added to a component in the DMI Service Layer.\nVariables:\n1: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n2: dmiGroupId\n\tAn identifier assigned by the DMI Service Layer that uniquely identifies this group instance within a particular component.\n3: dmiGroupClassString\n\tThe class string of the group (or table) instance as registered with the DMI Service Layer for the given component."
"Other","DMTF:Group Deleted Indication","An existing group has been removed from a component in the DMI Service Layer.\nVariables:\n1: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n2: dmiGroupId\n\tAn identifier assigned by the DMI Service Layer that uniquely identifies this group instance within a particular component."
"Other","DMTF:Motherboard System Up","The system's motherboard reports it has started-up successfully.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfMotherboardEvSys\n\tThe major functional aspect of"
"Other","DMTF:Motherboard Initialization Failure","The system's motherboard has failed to initialize properly during system startup.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfMotherboardEvSys\n\tThe major functi"
"Other","DMTF:Motherboard Configuration Error","The system's motherboard is not properly configured\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfMotherboardEvSys\n\tThe major functional aspect of the product"
"Other","DMTF:System Reset System Up","The system is up and running after having automatically re-booted due to some (abnormal) reset condition.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfSystemResetEvSys"
"Other","DMTF:Physical Container Physical Device Status Change","physicalDeviceStatusChange\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPhysicalContainerGlobalEvSys\n\tThe major functional aspect of the product causing the fault."
"Other","DMTF:Physical Container Logical Device Status Change","logicalDeviceStatusChange\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfPhysicalContainerGlobalEvSys\n\tThe major functional aspect of the product causing the fault."
"Other","DMTF:Structure Dependency System Up","An element of the system is up and running\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfStructureDependencyEvSys\n\tThe major functional aspect of the product causing the fault."
"Other","DMTF:Structure Dependency Initialization Failure","An element of the system failed to initialize properly during system startup.\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfStructureDependencyEvSys\n\tThe major functional aspect of the "
"Other","DMTF:Structure Dependency Configuration Error","An element of the system is not properly configured\nVariables:\n1: dmiEventDateTime\n\tThe timestamp attached to an event indication by the DMI Service Layer.\n2: dmiCompId\n\tThe unique Id assigned to the component by the Service Layer at registration time. By convention, the Service Layer itself will have an Id of one.\n3: dmiEventSeverity\n\tThe severity of this event.\n4: dmiEventStateKey\n\tThe index into the Event State group for the component generating this event, provided the event is state-based. The value -1 indicates the event is not state-based.\n5: dmiEventAssociatedGroup\n\tThe class string of the DMI group associated with this event.\n6: dmtfStructureDependencyEvSys\n\tThe major functional aspect of the product causing the fault."
"Other","Hung Server Action","A Hung Server Action (Watch Dog Event) occurred.\nVariables:\n1: AlertSystem\n\tName of the system generating the alert\n2: AlertGroup\n\tDMI group generating the alert\n3: AlertMessage\n\tAlert message\n4: AlertSeverity\n\tDMI alert severity\n5: AlertData\n\tAlert data"
"Other","Thermal Shut down","Thermal shutdown protection has been initiated. \nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object.If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","Redundancy Normal","Redundancy has returned to normal.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","Redundancy Degraded","Redundancy has been degraded.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","Redundancy Lost","Redundancy has been lost.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","Physical Device Status Change - OK","Physical Device Status Change - OK status"
"Other","Physical Device Status Change - Non Critical","Physical Device Status Change - non critical status"
"Other","Physical Device Status Change - Critical","Physical Device Status Change - critical status"
"Other","Physical Device Status Change - Non Recoverable","Physical Device Status Change - non recoverable status"
"Other","Logical Device Status Change - OK","Logical Device Status Change - OK status"
"Other","Logical Device Status Change - Non Critical","Logical Device Status Change  - non critical status ","5","DMTF|Physical Container Global Table|","-1","-1","8"
"Other","Logical Device Status Change - Critical","Logical Device Status Change - critical status"
"Other","Logical Device Status Change - Non Recoverable","Logical Device Status Change - non recoverable status"
"Other","Container Security Breach - OK","Container Security Breach - OK status"
"Other","Container Security Breach - Non Critical","Container Security Breach - non critical status"
"Other","Container Security Breach - Critical","Container Security Breach - critical status"
"Other","Container Security Breach - Non Recoverable","Container Security Breach - non recoverable status"
"Other","Configuration Error - OK","Configuration Error - OK status"
"Other","Configuration Error - Non Critical","Configuration Error - non critical status"
"Other","Configuration Error - Critical","Configuration Error - critical status"
"Other","Configuration Error - Non Recoverable","Configuration Error - non recoverable status"
"Other","Initialization Failure - OK","Initialization Failure - OK status"
"Other","Initialization Failure - Non Critical","Initialization Failure - non critical status"
"Other","Initialization Failure - Critical","Initialization Failure - critical status"
"Other","Initialization Failure - Non Recoverable","Initialization Failure - non recoverable status"
"Other","Drac2 Esm Normal","This trap is sent each time a ESM reading comes back in normal range.\nVariables:\n1: esmTrapSystem\n\tName of the system generating the alert\n2: esmTrapGroup\n\tDMI group generating the alert\n3: esmTrapMessage\n\tAlert message\n4: perc\n\tPartial Object Name\n5: perc\n\tPartial Object Name"
"Other","Drac2 Esm Warning","This trap is sent each time a ESM reading goes out of warning range.\nVariables:\n1: esmTrapSystem\n\tName of the system generating the alert\n\t esmTrapGroup\n\tDMI group generating the alert\n3: esmTrapMessage\n\tAlert message\n4: perc\n\tPartial Object Name\n5: perc\n\tPartial Object Name"
"Other","Drac2 Esm Critical","This trap is sent each time a ESM reading goes out of warning range.\nVariables:\n1: esmTrapSystem\n\tName of the system generating the alert\n\t esmTrapGroup\n\tDMI group generating the alert\n3: esmTrapMessage\n\tAlert message\n4: perc\n\tPartial Object Name\n5: perc\n\tPartial Object Name"
"Environmental","Temperature warning","Server temperature has exceeded the warning temperature threshold."
"Storage","Drive Letter Changed","This event occurs when the AAC software detects a drive letter change on a container."
"Storage","Failover Change","This event occurs when the AAC software setects a change in failover assignments."
"Storage","Container Change","This event occurs when the AAC software detects a change in container state."
"Storage","AFA File System Change","This event occurs when a file system is created or removed from a container."
"Storage","Container Failure","This event occurs when the AAC controller detects an error condition on a container."
"Storage","Mirror Not Mirroring","This event occurs when the AAC controller detects a container error that causes the container to no longer mirror."
"Storage","Mirror Failure No Space","This event occurs when an AAC controller detects a container that has failed and attempts to start a failover operation. The failover operation failed because there was not enough space on any failover of the assigned failover devices."
"Storage","Mirror No Unmirror","This error occurs when an AAC controller can not unmirror a container."
"Storage","Mirror Failover Start","The warning is generated when a failover starts on an AAC controller."
"Storage","Mirror Failover Failure","This event is generated when a failover fails for a container."
"Storage","Mirror No Failover Assigned","This event occurs when a failover operation fails because no failover device is assigned to a container."
"Storage","Mirror Drive Failure","This event is generated when a drive fails for a container."
"Storage","Raid Rebuild Start","The event occurs when a container rebuild operation starts."
"Storage","Raid Rebuild Restart","This event is generated when a raid rebuild operation is restarted on a container."
"Storage","Raid Drive Failed","This event occurs when a drive that is part of a redundant container failes."
"Storage","No Failover Device For Failed Redundant Container","This event is generated when an AAC controller detects that a failed redundant container does not have a failover device assigned to it."
"Storage","Raid Failed On Lack Of Resource","This event occurs when a raid container fails because of the lack of some resource."
"Storage","Snapshot Container Almost Full","This event occurs when the backing container of a snapshot set is almost full."
"Storage","Snapshot Container Full","This event occurs when the backing container of a snapshot set is full."
"Storage","Raid Rebuild Done","The event occurs when a raid rebuild operation has completed."
"Storage","Device Failure","This event occurs when a disk fails."
"Storage","Interface Up","This event is generated when the AAC management interface is up."
"Storage","Enclosure General Error","The event is generated when an AAC controller reports that an enclosure has failed."
"Storage","Enclosure Fan Error","The event is generated when an AAC controller reports that an enclosure fan failure has occured."
"Storage","Enclosure Power Supply Error","The event is generated when an AAC controller reports that an enclosure power supply failure has occured."
"Storage","Enclosure Temperature Abnormal","The event is generated when an AAC controller reports that an enclosure has reported an abnormal temperature reading."
"Storage","Enclosure Temperature Over User Threshold","The event is generated when an AAC controller reports that an enclosure has reported a temperature reading above the user set threshold."
"Storage","Enclosure Battery Dead","This event is reported by an AAC controller when its battery has lost all charge,missing or broken."
"Storage","Enclosure Battery Improving","This event is reported when an AAC controller detects that its battery has charged but should still be monitored."
"Storage","Enclosure Battery Degraded","This event is reported by an AAC controller when its battery has lost sufficient charge that it should be monitored."
"Storage","Enclosure Battery Good","This event is reported by an AAC controller when its battery has charged enough for normal operations."
"Storage","Container Created","This event occurs when a container is created on an AAC controller."
"Storage","Container Destroyed","This event occurs when a container is destroyed on an AAC controller."
"Storage","Device Threshold Mechanism Tested","This event occurs when a device reports that its failure prediction threshold reporting mechinism has been tested. This event is usually operator initiated."
"Storage","Device Warning","This event occurs when a device reports a warning. This is an indication that the device may soon fail."
"Storage","Device Temperature Warning","This event occurs when a device reports that its temperature is abnormal. This is an indication that the device may soon fail or that it is too hot."
"Storage","Device Degraded Warning","This event occurs when a device reports that its status had degraded. This is an indication that the device may soon fail."
"Storage","Device Reconfigured","This event occurs when a device reports that its failure prediction method has been reconfigured. This event usually occurs at the users request."
"Network","NIC Health Event","This event is reported by an Intel NIC when an unknown health event occurs."
"Network","LAN Controller hardware Failure.","This event is reported by an Intel NIC when the LAN Control hardward fails."
"Network","Cable unplugged/No LAN activity","This event is reported by an Intel NIC when the cable is unplugged or there is not LAN activity."
"Network","Adapter initialization failure","This event is reported by an Intel NIC when the adapter initialization fails."
"Network","Line up","This event is reported by an Intel NIC when the line is up."
"Network","NIC Team Event","This event is reported by an Intel NIC when an unknown team event occurs."
"Network","The Primary Adapter is switching over and the Secondary Adapter took over","This event is reported by an Intel NIC when the Primary Switch is switching over and the Secondary Adapter took over."
"Network","The Primary adapter became active","This event is reported by an Intel NIC when the Primary Adapter became active."
"Network","Secondary Adapter is deactivated from the team","This event is reported by an Intel NIC when the Secondary Adapter is deactivated from the team."
"Network","The last Adapter has lost link. Network connection has been lost","This event is reported by an Intel NIC when the last Adapter lost link and therefore the network connection has been lost."
"Network","Preferred Primary Adapter has been detected","This event is reported by an Intel NIC when the preferred Primary Adapter has been detected."
"Network","The team only has one active adapter","This event is reported by an Intel NIC when the team only has one active adapter."
"Network","The Secondary adapter has re-joined the team","This event is reported by an Intel NIC when the Secondary Adapter has re-joined the team."
"Network","Preferred Primary Adapter has taken over","This event is reported by an Intel NIC when the preferred Primary Adapter has taken over."
"Network","Network Connection restored","This event is reported by an Intel NIC when the Network Connection is restored."
"Security","SNMP Community name incorrect","Windows NT authentication error: community name incorrect."
"Other","Netware Generic Trap","Generic trap received from Netware system."
"Storage","Storage Device Rebuild in Progress","Storage Device Rebuild in Progress"
"Storage","Storage Device Readying","Storage Device Readying"
"Storage","Storage Device Error","Storage Device Error"
"Storage","Storage Device Self-Monitoring Warning","Storage Device Self-Monitoring Warning"
"Storage","Storage Device CI/O Event","Storage Device CI/O Event"
"Storage","Storage Controller Error","Storage Controller Error"
"Storage","Storage Controller Self-monitoring Warning","Storage Controller Self-monitoring Warning"
"Storage","Storage Controller CI/O Event","Storage Controller CI/O Event"
"Other","Enslosure CI/O Event","Enslosure CI/O Event"
"Other","Bus Port Error","Bus Port Error"
"Other","Volume Set Exposed","Volume Set Exposed"
"Other","Volume Set Rebuild in Progress","Volume Set Rebuild in Progress"
"Other","Volume Set Protection Disabled","Volume Set Protection Disabled"
"Other","Volume Set Readying","Volume Set Readying"
"Other","Volume Set Recalculate Active","Volume Set Recalculate Active"
"Other","Volume Set Spare in Use","Volume Set Spare in Use"
"Other","Volume Set Verify in Progress","Volume Set Verify in Progress"
"Other","Volume Set Broken","Volume Set Broken"
"Other","Volumn Set CI/O Event","Volumn Set CI/O Event"
"Other","Volumn Set Activity CI/O Event","Volumn Set Activity CI/O Event"
"Other","Redundancy Group Exposed","Redundancy Group Exposed"
"Other","Redundancy Group Rebuild in Progress","Redundancy Group Rebuild in Progress"
"Other","Redundancy Group Protection Disabled","Redundancy Group Protection Disabled"
"Other","Redundancy Group Recalculation Active","Redundancy Group Recalculation Active"
"Other","Redundancy Group Verify in Progress","Redundancy Group Verify in Progress"
"Other","Component Spare Broken","Component Spare Broken"
"Other","Component Spare in Use","Component Spare in Use"
"Other","Component Spare Readying","Component Spare Readying"
"Other","Component Spare CI/O Event","Component Spare CI/O Event"
"Other","New Object Detected","New Object Detected"
"Other","Existing Object Replaced","Existing Object Replaced"
"Other","Existing Object is Gone","Existing Object is Gone"
"Other","Unknown Adapter Event","Unknown Adapter Event"
"Other","Adapter Information","Adapter Information"
"Other","Adapter Warning","Adapter Warning"
"Other","Adapter Error","Adapter Error"
"Storage","Hard Disk Placed Online","A hard disk has been placed online."
"Storage","Hard Disk Added As Hot Spare","A hard disk added as hot spare."
"Storage","Hard Disk Error Found","Hard disk error found."
"Storage","Hard Disk May Fail Soon","Hard disk PFA condition found, this disk may fail soon."
"Storage","Automatic Rebuild Started","An automatic rebuild has started."
"Storage","Rebuild Started","A rebuild has started."
"Storage","Rebuild Over","Rebuild is over."
"Storage","Rebuild Cancelled","Rebuild is cancelled."
"Storage","Error- Rebuild Stopped (1)","Rebuild stopped with error."
"Storage","Error- Rebuild Of New Device Failed (1)","Rebuild stopped with error. New device failed."
"Storage","Rebuild Of Logical Drive Failed","Rebuild stopped because logical drive failed."
"Storage","Hard Disk Failed","A hard disk has failed."
"Storage","New Hard Disk Found","A new hard disk has been found."
"Storage","Hard Disk Removed","A hard disk has been removed."
"Storage","Previously Configured Disk Available","A previously configured disk is now available."
"Storage","Expand Capacity Started (1)","Expand Capacity Started."
"Storage","Expand Capacity Completed (1)","Expand Capacity Completed."
"Storage","Error- Expand Capacity Stopped (1)","Expand Capacity Stopped with error."
"Storage","SCSI Command Timeout","SCSI command timeout on hard device."
"Storage","SCSI Command Abort","SCSI command abort on hard disk."
"Storage","SCSI Command Retried","SCSI command retried on hard disk."
"Storage","Parity Error Found","Parity error found."
"Storage","Soft Error Found","Soft error found."
"Storage","Misc Error Found","Misc error found."
"Storage","SCSI Device Reset","SCSI device reset."
"Storage","Active Spare Found","Active spare found.-"
"Storage","Warm Spare Found","Warm spare found.-"
"Storage","Sense Data Available","Request Sense Data available."
"Storage","Initialization Started","Initialization started."
"Storage","Initialization Completed","Initialization completed."
"Storage","Initialization Failed","Initialization failed."
"Storage","Initialization Canceled","Initialization canceled."
"Storage","Hard Disk Write Recovery Failed","A hard disk failed because write recovery failed."
"Storage","Hard Disk SCSI Bus Reset Failed","A hard disk failed because SCSI bus reset failed."
"Storage","Hard Disk Failure On Double Check Condition","A hard disk failed because double check condition occured."
"Storage","Hard Disk Fail- Device Missing","A hard disk failed because device is missing."
"Storage","Hard Disk Fail- SCSI Processor Gross Error","A hard disk failed because of gross error on SCSI processor."
"Storage","Hard Disk Fail- Bad Device Tag","A hard disk failed because of bad tag from the device."
"Storage","Hard Disk Fail- Command To Device Timed Out","A hard disk failed because command to the device timed out."
"Storage","Hard Disk Fail- System Reset","A hard disk failed because of the system reset."
"Storage","Hard Disk Fail- Busy Status Or Parity Error","A hard disk failed because of busy status or parity error."
"Storage","Hard Disk Failure Set By Host","A hard disk set to failed state by host."
"Storage","Hard Disk Fail- Selection Time Out On Device Access","A hard disk failed because access to the device met with a selection time out."
"Storage","Hard Disk Fail- SCSI Bus Phase Handling Sequence Error","A hard disk failed because of a sequence error in the SCSI bus phase handling."
"Storage","Hard Disk Fail- Unknown Status Returned","A hard disk failed because device returned an unknown status."
"Storage","Hard Disk Fail- Device Not Ready","A hard disk failed because device is not ready."
"Storage","Hard Disk Fail- Device Not Found","A hard disk failed because device was not found on start up."
"Storage","Hard Disk Fail- Write "Configuration On Disk" Failed","A hard disk failed because write operation of the "Configuration On Disk" failed."
"Storage","Hard Disk Fail- Write Of "Bad Data Table" Failed","A hard disk failed because write operation of "Bad Data Table" failed."
"Storage","Physical Device Changed To Offline","Physical device status changed to offline."
"Storage","Physical Device Changed To Hot Spare","Physical device status changed to Hot Spare."
"Storage","Physical Device Changed To Rebuild","Physical device status changed to rebuild."
"Storage","Physical device ID Not Matching","Physical device ID did not match."
"Storage","Starting Physical Device Failed","Physical device failed to start."
"Storage","Different Offset Negotiated By Physical Device","Physical device negotiated different offset than config."
"Storage","Different Bus Width Negotiated By Physical Device","Physical device negotiated different bus width than config."
"Storage","Physical Drive Missing On Startup","Physical drive missing on startup."
"Storage","Low Disk Capacity- Rebuild Startup Fail","Rebuild startup failed due to lower disk capacity."
"Storage","Physical Drive Switching Channels","Physical drive is switching from a channel to the other channel."
"Storage","Temporary-Dead Physical Drive Online","Temporary-Dead physical drive is automatically made online."
"Storage","Standby Rebuild Started","A standby rebuild has started."
"Storage","Device Id Conflict Detected","Device Loop Id Conflict (Soft Addressing) Detected."
"Storage","Consistency Check Started","Consistency check is started."
"Storage","Consistency Check Finished","Consistency check is finished."
"Storage","Consistency Check Cancelled","Consistency check is cancelled."
"Storage","Consistency Check Error On Logical Drive","Consistency check on logical drive error."
"Storage","Consistency Check Failed On Logical Drive","Consistency check on logical drive failed."
"Storage","Consistency Check Failed On Physical Device Failure","Consistency check failed due to physical device failure."
"Storage","Logical Drive Offline","Logical drive has been made offline."
"Storage","Logical Drive Critical","Logical drive is critical."
"Storage","Logical Drive Online","Logical drive has been placed online."
"Storage","Automatic Rebuild On Logical Drive","An automatic rebuild has started on logical drive."
"Storage","Manual Rebuild On Logical Drive","A manual rebuild has started on logical drive."
"Storage","Logical Drive Rebuild Over","Rebuild on logical drive is over."
"Storage","Logical Drive Rebuild Cancelled","Rebuild on logical drive is cancelled."
"Storage","Error- Rebuild Stopped (2)","Rebuild stopped with error."
"Storage","Error- Rebuild Of New Device Failed (2)","Rebuild stopped with error. New device failed."
"Storage","Error- Rebuild Of Logical Drive Failed","Rebuild stopped because logical drive failed."
"Storage","Logical Drive Initialization Started","Logical drive initialization started."
"Storage","Logical Drive Initialization Done","Logical drive initialization done."
"Storage","Logical Drive Initialization Cancelled","Logical drive initialization cancelled."
"Storage","Logical Drive Initialization Failed","Logical drive initialization failed."
"Storage","Logical Drive Found","A logical drive has been found."
"Storage","Logical Drive Deleted","A logical drive has been deleted."
"Storage","Expand Capacity Started (2)","Expand Capacity Started."
"Storage","Expand Capacity Completed (2)","Expand Capacity Completed."
"Storage","Error- Expand Capacity Stopped (2)","Expand Capacity stopped with error."
"Storage","Bad Blocks Found","Bad Blocks found."
"Storage","System Drive Size Changed","System drive size changed."
"Storage","System Drive Type Changed","System drive type changed."
"Storage","Possible Data Loss","Bad data blocks found. Possible data loss."
"Storage","System Drive LUN Mapping Written To Config","System drive LUN mapping has been written to config."
"Storage","Read Data From Block In Bad Data Table","Attempt to read data from block that is marked in Bad Data Table"
"Storage","Disk Block Data Loss Due To Logical Drive Problem","Data for Disk Block has been lost due to Logical Drive problem"
"Storage","Temporary-Offline Array Available To User With Possible Data Loss","Temporary-Offline RAID5/RAID3 array is available to the user again with the possibility of data loss in the array."
"Storage","Temporary-Offline Array Available To User","Temporary-Offline RAID0+1/RAID1/RAID0/JBOD array is available to the user again."
"Storage","Logical Drive Standby Rebuild Started","An standby rebuild has started on logical drive."
"Storage","Fan Failure (1)","Fan failure."
"Storage","Fan Restored (1)","Fan has been restored."
"Storage","Fan Failure (2)","Fan failure."
"Storage","Missing Storage Cabinet Fan","Storage cabinet fan is not present."
"Storage","Power Supply Failure (1)","Power supply failure."
"Storage","Power Supply Restored (1)","Power supply has been restored."
"Storage","Power Supply Failure (2)","Power supply failure."
"Storage","Missing Storage Cabinet Power Supply","Storage cabinet power supply is not present."
"Storage","Temperature Above 70 Celsius","Over temperature. Temperature is above 70 degrees Celsius."
"Storage","Temperature Above 50 Celsius","Temperature is above 50 degrees Celsius."
"Storage","Normal Temperature Restored (1) ","Normal temperature has been restored."
"Storage","Over Temperature","Over temperature."
"Storage","Storage Cabinet Temperature Sensor Absent","Storage cabinet temperature sensor is not present."
"Storage","Storage Works Enclosure Failed","Storage Works enclosure reported failure state."
"Storage","Storage Works Enclosure Critical","Storage Works enclosure reported critical state."
"Storage","Storage Works Enclosure Normal","Storage Works enclosure reported normal state."
"Storage","Uninterruptible Power Supply Disabled","Uninterruptible Power Supply Disabled."
"Storage","Uninterruptible Power Supply AC Failed","Uninterruptible Power Supply AC Failed."
"Storage","Uninterruptible Power Supply Battery Low","Uninterruptible Power Supply Battery Low."
"Storage","Uninterruptible Power Supply Failed","Uninterruptible Power Supply Failed."
"Storage","Uninterruptible Power Supply Normal","Uninterruptible Power Supply Normal."
"Storage","Fan Failure (3)","Fan failure."
"Storage","Fan Restored (2)","Fan has been restored."
"Storage","Fan Not Present","Fan is not present."
"Storage","Power Supply Failure (3)","Power supply failure."
"Storage","Power Supply Restored (2)","Power supply has been restored."
"Storage","Power Supply Not Present","Power supply is not present."
"Storage","Temperature Over Safe Limit","Temperature is over safe limit. Failure imminent."
"Storage","Temperature Above Working Limit","Temperature is above working limit."
"Storage","Normal Temperature Restored (2)","Normal temperature has been restored."
"Storage","Temperature Sensor Not Present","Temperature sensor is not present."
"Storage","Enclosure Access Critical","Enclosure access critical."
"Storage","Enclosure Access Restored","Enclosure access has been restored."
"Storage","Enclosure Access Offline","Enclosure access is offline."
"Storage","Enclosure Soft Addressing Detected","Enclosure Soft Addressing Detected."
"Storage","Enclosure Services Ready","Enclosure services ready"
"Storage","Temperature Sensor Access Lost","Access to temperature sensor has been lost."
"Storage","Power Supply Information Access Lost","Access to power supply status information has been lost."
"Storage","Fan Status Information Access Lost","Access to fan status information has been lost."
"Storage","Array Mgmt Server Software Started Successfully","Array management server software started successfully."
"Storage","Write Back Error","Write back error."
"Storage","Internal Log Getting Full","Internal log structures getting full,PLEASE SHUTDOWN AND RESET THE SYSTEM IN THE NEAR FUTURE."
"Storage","Controller Dead","Controller is dead. System is disconnecting from this controller."
"Storage","Controller Reset","Controller has been reset."
"Storage","Controller Found","Controller is found."
"Storage","System Disconnecting From Absent Controller (1)","Controller is gone. System is disconnecting from this controller."
"Storage","BBU Present","BBU Present."
"Storage","BBU Power Low","BBU Power Low."
"Storage","BBU Power OK","BBU Power OK."
"Storage","System Disconnecting From Absent Controller (2)","Controller is gone. System is disconnecting from this controller."
"Storage","Controller Powered On","Controller powered on"
"Storage","Controller Online","Controller is online."
"Storage","System Disconnecting From Absent Controller (3)","Controller is gone. System is disconnecting from this controller."
"Storage","Controller Partner Gone","Controller's partner is gone, controller is in failover mode now."
"Storage","BBU Recondition Started","BBU reconditioning is started."
"Storage","BBU Recondition Finished","BBU reconditioning is finished."
"Storage","BBU Recondition Canceled","BBU reconditioning is canceled."
"Storage","Installation Aborted","Installation aborted."
"Storage","Controller Firmware Mismatch","Controller firmware mismatch."
"Storage","BBU Removed","BBU removed."
"Storage","WARM BOOT Failed","WARM BOOT failed."
"Storage","Controller Entered Conservative Cache Mode","Controller entered Conservative Cache Mode."
"Storage","Controller Entered Normal Cache Mode","Controller entered Normal Cache Mode."
"Storage","Controller Device Start Complete","Controller Device Start Complete."
"Storage","Soft ECC error Corrected","Soft ECC error Corrected."
"Storage","Hard ECC error Corrected","Hard ECC error Corrected."
"Storage","BBU Recondition Needed","BBU Recondition Needed."
"Storage","Controller Partner Removed","Controller's Partner Has Been Removed."
"Storage","BBU Out Of Service","BBU out of service."
"Storage","Updated Partner Status","Updated partner's status."
"Storage","Relinquished Partner","Relinquished partner."
"Storage","Inserted Partner","Inserted Partner."
"Storage","Dual Controllers Enabled","Dual Controllers Enabled."
"Storage","Killed Partner","Killed Partner."
"Storage","Dual Controllers Entered Nexus","Dual Controllers entered Nexus."
"Storage","Controller Boot ROM Image Needs Reloading","Controller Boot ROM Image needs to be reloaded."
"Storage","Controller Using Default Name","Controller is using default non-unique world-wide name."
"Storage","Mirror Race Recovery Failed","Mirror Race recovery failed."
"Storage","Mirror Race On Critical Drive","Mirror Race on critical drive."
"Storage","System Started","System started."
"Storage","Size Table Full","Size table full."
"Storage","User Logged In","User logged in."
"Storage","User Logged Out","User logged out."
"Storage","Server Alive","Server alive."
"Storage","Server Lost Connection Or Down","Lost connection to server, or server is down."
"Storage","Automatic Reboot Count Changed","Automatic reboot count has changed."
"Storage","Channel Failed","Channel Failed."
"Storage","Channel Online","Channel Online."
"Storage","Back End SCSI Bus Dead","Back End SCSI Bus Dead."
"Storage","Back End SCSI Bus Alive","Back End SCSI Bus Alive."
"Storage","Back End Fibre Dead","Back End Fibre Dead."
"Storage","Back End Fibre Alive","Back End Fibre Alive."
"Storage","Event Log Empty","Event Log Empty."
"Storage","Event Log Entries Lost","Event Log Entries Lost."
"Storage","Request Sense","Request Sense"
"Storage","Set Real Time Clock","Set Real Time Clock."
"Storage","New Configuration Received","New Configuration Received."
"Storage","Configuration Cleared","Configuration Cleared."
"Storage","Configuration Invalid","Configuration Invalid."
"Storage","Configuration On Disk Access Error","Configuration On Disk Access Error."
"Storage","Configuration On Disk Converted","Configuration On Disk Converted."
"Storage","Configuration On Disk Import Failed","Configuration On Disk Import Failed."
"Storage","Debug Dump Exists On System (1)","A Debug Dump exists on this system."
"Storage","Debug Dump Exists On System (2)","A Debug Dump exists on this system."
"Storage","Internal Controller Hung","Internal Controller is in the hung state."
"Storage","Internal Controller Firmware Breakpoint","Internal Controller has encountered a Firmware breakpoint."
"Storage","Internal Controller I960 Processor Specific Error","Internal Controller has encountered i960 processor specific error."
"Storage","Internal Controller Strong-ARM Processor Specific Error","Internal Controller has encountered Strong-ARM processor specific error"
"Software","System Up Mssg from IT Assistant","When IT Assistant has detected a system as down, when the system comes back up, IT Assistant will emit this event upon a discovery or status round."
"Software","System Down Mssg from IT Assistant","When IT Assistant cannot communicate with a discovered system, it will emit this event upon a discovery or status round. This occurs only once."
"Network","NIC Failover Event","This trap is generated to indicate that adapter Fail-Over event has occured."
"Cluster","Generic SNMP Trap","Generic SNMP trap generated by NuView ClusterX applications and services.\nVarbind #1:  Custom string.\nVariables:\n  1: clxTrapDataString01\n     Syntax=Display String\n     Descr=Custom string 1 (Varbind #1) for NuView ClusterX trap."
"Cluster","Failure of a node in an MSCS cluster","This trap is sent when ClusterX detects the failure of a node in an MSCS cluster. The trap identifies the cluster,the name of the node that failed \nVariables:\n  1: clxTrapDataClusterName\n     Syntax=Display String\n     Descr=Name of the MSCS Cluster. \n  2: clxTrapDataNodeName\n     Syntax=Display String\n     Descr=Name of the MSCS Node. "
"Cluster","Failure of an MSCS cluster","This trap is sent when ClusterX detects the failure of an MSCS cluster. The trap identifies the name of the failed cluster \nVariables:\n  1: clxTrapDataClusterName\n     Syntax=Display String\n     Descr=Name of the MSCS Cluster. "
"Cluster","Failure of a resource detected","This trap is sent when ClusterX detects the failure of a resource on an MSCS cluster. The trap identifies the names of the cluster, node and resource \nVariables:\n  1: clxTrapDataClusterName\n     Syntax=Display String\n     Descr=Name of the MSCS Cluster. \n  2: clxTrapDataNodeName\n     Syntax=Display String\n     Descr=Name of the MSCS Node. \n  3: clxTrapDataResourceName\n     Syntax=Display String\n     Descr=Name of the MSCS Resource. "
"Cluster","Detection of node joining or rejoining cluster","This trap is sent when ClusterX detects that node has joined or rejoined an MSCS cluster. The trap identifes the name of the cluster and the name of the node that joined.\nVariables:\n  1: clxTrapDataClusterName\n     Syntax=Display String\n     Descr=Name of the MSCS Cluster. \n  2: clxTrapDataNodeName\n     Syntax=Display String\n     Descr=Name of the MSCS Node. "
"Cluster","Detection of a failure of the private or public cluster interconnects","This trap is sent when ClusterX detects the failure of the private or public cluster interconnects on an MSCS cluster.\nVariables:\n  1: clxTrapDataClusterName\n     Syntax=Display String\n     Descr=Name of the MSCS Cluster. \n  2: clxTrapDataNetworkName\n     Syntax=Display String\n     Descr=Network Name"
"Cluster","Detected the cluster service wrote a normal event to the NT event log","This trap is generated when ClusterX detects that the Cluster Service has written a new entry in the Windows NT Event Log on a managed cluster.It contains the information about cluster service log\nVariables:\n  1: clxTrapEventDate\n     Syntax=Display String\n     Descr=Date of the Event created in NT event log file \n  2: clxTrapEventTime\n     Syntax=Display String\n     Descr=Time of the Event created in NT event log file \n  3: clxTrapEventSource\n     Syntax=Display String\n     Descr=Source of the Event created in NT event log file \n  4: clxTrapEventCategory\n     Syntax=Display String\n     Descr=Category of the Event created in NT event log file \n  5: clxTrapEventID\n     Syntax=Display String\n     Descr=ID of the Event created in NT event log file\n  6: clxTrapEventUser\n     Syntax=Display String\n     Descr=User which created the event in NT event log file \n  7: clxTrapEventComputer\n     Syntax=Display String\n     Descr=Computer which created Event in NT event log file"
"Cluster","Detected the cluster service wrote a warning event to the NT event log","This trap is generated when ClusterX detects that the Cluster Service has written a new entry in the Windows NT Event Log on a managed cluster.It contains the information about cluster service log\nVariables:\n  1: clxTrapEventDate\n     Syntax=Display String\n     Descr=Date of the Event created in NT event log file \n  2: clxTrapEventTime\n     Syntax=Display String\n     Descr=Time of the Event created in NT event log file \n  3: clxTrapEventSource\n     Syntax=Display String\n     Descr=Source of the Event created in NT event log file \n  4: clxTrapEventCategory\n     Syntax=Display String\n     Descr=Category of the Event created in NT event log file \n  5: clxTrapEventID\n     Syntax=Display String\n     Descr=ID of the Event created in NT event log file\n  6: clxTrapEventUser\n     Syntax=Display String\n     Descr=User which created the event in NT event log file \n  7: clxTrapEventComputer\n     Syntax=Display String\n     Descr=Computer which created Event in NT event log file"
"Cluster","Detected the cluster service wrote a critical event to the NT event log","This trap is generated when ClusterX detects that the Cluster Service has written a new entry in the Windows NT Event Log on a managed cluster.It contains the information about cluster service log\nVariables:\n  1: clxTrapEventDate\n     Syntax=Display String\n     Descr=Date of the Event created in NT event log file \n  2: clxTrapEventTime\n     Syntax=Display String\n     Descr=Time of the Event created in NT event log file \n  3: clxTrapEventSource\n     Syntax=Display String\n     Descr=Source of the Event created in NT event log file \n  4: clxTrapEventCategory\n     Syntax=Display String\n     Descr=Category of the Event created in NT event log file \n  5: clxTrapEventID\n     Syntax=Display String\n     Descr=ID of the Event created in NT event log file\n  6: clxTrapEventUser\n     Syntax=Display String\n     Descr=User which created the event in NT event log file \n  7: clxTrapEventComputer\n     Syntax=Display String\n     Descr=Computer which created Event in NT event log file"
"Cluster","Application failure detected","This trap is sent when ClusterX detects the failure of an application on a monitored node.\nVarbind #1: Cluster Name\nVarbind #2: Node Name\nVarbind #3: Application Name\nVarbind #4: Application Failure Reason\nVarbind #5: Application Failure Action"
"Cluster","WLBS has written an informational entry in the Windows NT Event Log","This trap is generated when ClusterX detects that WLBS has written an informational entry in the Windows NT Event Log on a managed cluster.\nVarbind #1: Event Creation Date\nVarbind #2: Event Creation Time\nVarbind #3: Event Source\nVarbind #4: Event Category\nVarbind #5: Event ID\nVarbind #6: Event Creation User\nVarbind #7: Event Creation Computer"
"Cluster","WLBS has written a warning entry in the Windows NT Event Log","This trap is generated when ClusterX detects that WLBS has written a warning entry in the Windows NT Event Log on a managed cluster.\nVarbind #1: Event Creation Date\nVarbind #2: Event Creation Time\nVarbind #3: Event Source\nVarbind #4: Event Category\nVarbind #5: Event ID\nVarbind #6: Event Creation User\nVarbind #7: Event Creation Computer"
"Cluster","WLBS has written an error entry in the Windows NT Event Log","This trap is generated when ClusterX detects that WLBS has written an error entry in the Windows NT Event Log on a managed cluster.\nVarbind #1: Event Creation Date\nVarbind #2: Event Creation Time\nVarbind #3: Event Source\nVarbind #4: Event Category\nVarbind #5: Event ID\nVarbind #6: Event Creation User\nVarbind #7: Event Creation Computer"
"Cluster","WLBS cluster operation control has been suspended","This trap is sent when ClusterX detects that WLBS cluster operation control has been suspended.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","WLBS cluster operation control has been resumed","This trap is sent when ClusterX detects that WLBS cluster operation control has been resumed.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","WLBS cluster operations have started","This trap is sent when ClusterX detects that WLBS cluster operations have started.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","WLBS cluster operations have stopped","This trap is sent when ClusterX detects that WLBS cluster operations have stopped.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","WLBS cluster operations have started draining","This trap is sent when ClusterX detects that WLBS cluster operations have started draining; once drained, cluster operations will stop.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","Node in a WLBS cluster has converged","This trap is sent when ClusterX detects that a node in a WLBS cluster has converged.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","WLBS traffic handling for the rule containing the specified port number has been enabled","This trap is sent when ClusterX detects that WLBS traffic handling for the rule containing the specified port number has been enabled.\nVarbind #1: Cluster Name\nVarbind #2: Node Name\nVarbind #3: Port Number or 'ALL'"
"Cluster","WLBS traffic handling for the rule containing the specified port number has been disabled for ALL traffic","This trap is sent when ClusterX detects that WLBS traffic handling for the rule containing the specified port number has been disabled for ALL traffic.\nVarbind #1: Cluster Name\nVarbind #2: Node Name\nVarbind #3: Port Number or 'ALL'"
"Cluster","WLBS traffic handling for the rule containing the specified port number has been disabled for NEW traffic","This trap is sent when ClusterX detects that WLBS traffic handling for the rule containing the specified port number has been disabled for NEW traffic.\nVarbind #1: Cluster Name\nVarbind #2: Node Name\nVarbind #3: Port Number or 'ALL'"
"Cluster","Application has come on line on a monitored node","This trap is sent when ClusterX detects that an application has come on line on a monitored node.\nVarbind #1: Cluster Name\nVarbind #2: Node Name\nVarbind #3: Application Name\nVarbind #4: Action Taken"
"Cluster","WLBS cluster parameters have been reloaded from the registry","ClusterX detects that WLBS cluster parameters have been reloaded from the registry.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Power","Dell AC Cord No Power Non-redundant","Dell AC Cord No Power Non-redundant"
"Power","Dell AC Cord Normal","Dell AC Cord Normal"
"Power","Dell AC Cord Failure","Dell AC Cord Failure"
"Operating System","SNMP Shutdown","A shutdown trap signifies that the sending protocol entity is stopped."
"Other","DRSC Test TRAP Event","The DRSC generated a test trap event in response to a user request.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Authentication Error","DRSC Authentication Failures during a time period have Exceeded a Threshold.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Lost Communication with ESM","DRSC cannot communicate with the baseboard management controller (ESM).\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Communication with ESM is OK","DRSC is communicating normally with the baseboard management controller (ESM).\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Detected System Powered-Off","The DRSC has detected a System power state change to powered-off.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Detected System Powered-On","The DRSC has detected a system power state change to powered-on.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Detected Watchdog Expired","The DRSC has detected that the system watchdog has expired indicating a system hang.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data." 
"Power","DRSC Battery Charge Low","The DRSC Battery charge is below 25% indicating that the battery may only be able to power the DRSC for 8-10 minutes.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","DRSC Temperature Normal","The DRSC Temperature probe has retured to a normal value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","DRSC Temperature Warning","The DRSC Temperature probe has detected a Warning value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","DRSC Temperature Failure","The DRSC Temperature probe has detected a failure (or critical) value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Power","DRSC Voltage Normal","A DRSC voltage has returned to a normal value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Power","DRSC Battery Warning","A DRSC voltage probe has detected a warning value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Power","DRSC Voltage Failure","A DRSC voltage probe has detected a failure (or critical) value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC System Event Log Warning","The DRSC has detected a new event in the System Event Log with Severity.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC System Event Log Critical","The DRSC has detected a new event in the System Event Log with Severity.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","System Event Log 80% Full","System Event Log 80% Full.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","System Event Log 90% Full","System Event Log 90% Full.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","System Event Log 100% Full","System Event Log 100% Full.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Storage","Logical drive background initialization started","Logical drive background initialization started.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","Logical drive background initialization stopped","Logical drive background initialization stopped.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","Logical drive background initialization paused","Logical drive background initialization paused.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","Logical drive background initialization restarted","Logical drive background initialization restarted.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","Logical drive background initialization failed","Logical drive background initialization failed.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","Logical drive background initialization completed","Logical drive background initialization completed.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","BBU calibration cycle started","BBU calibration cycle started.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated."
"Storage","BBU calibration cycle finished","BBU calibration cycle finished.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated."
"Storage","BBU calibration cycle canceled","BBU calibration cycle canceled.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated."
"Storage","BBU battery not present","BBU battery not present.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated."
"Network","Event caused for Broadcom CryptoNET device","This trap is generated to indicate that adapter event has occured"
"Network","Intel NIC Link Up","This event is reported by an Intel NIC when the link is up."
"Network","Intel NIC Link Down","This event is reported by an Intel NIC when the link is down."
"Network","Physical Network Adapter Added","This event is reported by the appropriate agent when a physical NIC adapter is added."
"Network","Physical Network Adapter Removed","This event is reported by the appropriate agent when a physical NIC adapter is removed."
"Network","Virtual Network Adapter Added","This event is reported by the appropriate agent when a virtual NIC adapter has been added to a team."
"Network","Virtual Network Adapter Removed","This event is reported by the appropriate agent when a virtual NIC adapter has been removed from a team."
"Network","Primary Change In Team","This event is reported by the appropriate agent when a change in teaming occurs."
"Network","Team Added","This event is reported by the appropriate agent when a team has been added."
"Network","Team Removed","This event is reported by the appropriate agent when a team has been removed."
"Network","Team Member Added","This event is reported by the appropriate agent when a team has been added."
"Network","Team Member Removed","This event is reported by the appropriate agent when a team has been removed."
"Storage","Enclosure has exceeded the maximum warning threshold","%s, %s has exceded the maximum warning threshold.\nVariables:\n1: enclosureNameEv\nSyntax=Display String\nDescr=Enclosure Name for which trap is generated.\n2: unitNameEv\nSyntax=Display String\nDescr=Unit Number for which trap is generated. (Fan, Power Supply, Temperature Probe)"
"Storage","Enclosure has dropped below the minimum warning threshold","%s, %s has dropped below the minimum warning threshold.\nVariables:\n1: enclosureNameEv\nSyntax=Display String\nDescr=Enclosure Name for which trap is generated.\n2: unitNameEv\nSyntax=Display String\nDescr=Unit Number for which trap is generated. (Fan, Power Supply, Temperature Probe)"
"Storage","Enclosure has exceded the maximum error threshold","%s, %s has exceded the maximum error threshold.\nVariables:\n1: enclosureNameEv\nSyntax=Display String\nDescr=Enclosure Name for which trap is generated.\n2: unitNameEv\nSyntax=Display String\nDescr=Unit Number for which trap is generated. (Fan, Power Supply, Temperature Probe)"
"Storage","Enclosure has dropped below the minimum error threshold","%s, %s has dropped below the minimum error threshold.\nVariables:\n1: enclosureNameEv\nSyntax=Display String\nDescr=Enclosure Name for which trap is generated.\n2: unitNameEv\nSyntax=Display String\nDescr=Unit Number for which trap is generated. (Fan, Power Supply, Temperature Probe)"
"Storage","Enclosure has failed","%s, %s failed.\nVariables:\n1: enclosureNameEv\nSyntax=Display String\nDescr=Enclosure Name for which trap is generated.\n2: unitNameEv\nSyntax=Display String\nDescr=Unit Number for which trap is generated. (Fan, Power Supply, Temperature Probe)"
"Storage","Enclosure is offline","%s, %s is offline.\nVariables:\n1: enclosureNameEv\nSyntax=Display String\nDescr=Enclosure Name for which trap is generated.\n2: unitNameEv\nSyntax=Display String\nDescr=Unit Number for which trap is generated. (Fan, Power Supply, Temperature Probe)"
"Storage","Enclosure is in an unknown state","%s, %s is in an unknown state.\nVariables:\n1: enclosureNameEv\nSyntax=Display String\nDescr=Enclosure Name for which trap is generated.\n2: unitNameEv\nSyntax=Display String\nDescr=Unit Number for which trap is generated. (Fan, Power Supply, Temperature Probe)"
"Storage","Enclosure is in a warning state","%s, %s is in a warning state.\nVariables:\n1: enclosureNameEv\nSyntax=Display String\nDescr=Enclosure Name for which trap is generated.\n2: unitNameEv\nSyntax=Display String\nDescr=Unit Number for which trap is generated. (Fan, Power Supply, Temperature Probe)"
"Storage","Array Manager Database UP","Array Manager Database UP"
"Storage","Array Manager Database DOWN","Array Manager Database DOWN"
"Storage","Low battery charge level","Low battery charge level. Logical drive may have lost data."
"Storage","Controller improperly shutdown","Controller improperly shutdown! Data may have been lost."
"Storage","Dual Active Automatic Flash of Replacement Controller","Dual Active Automatic Flash of Replacement Controller."
"Storage","Dual Active Negotiation failed jumpers","Dual Active Negotiation failed jumpers."
"Storage","Dual Active Negotiation failed IDs","Dual Active Negotiation failed ID's."
"Storage","Dual Active Negotiation failed board types","Dual Active Negotiation failed board types."
"Storage","Dual Active Negotiation failed disk channels","Dual Active Negotiation failed disk channels."
"Storage","Dual Active Negotiation failed host ports","Dual Active Negotiation failed host ports."
"Storage","Dual Active Negotiation failed memory size","Dual Active Negotiation failed memory size."
"Storage","Dual Active Negotiation failed cache memory size","Dual Active Negotiation failed cache memory size."
"Storage","Hot spare replaced with a smaller capacity drive","Hot spare replaced with a smaller capacity drive."
"Storage","A failback event has occurred","A failback event has occurred."
"Storage","A failover event has occurred","A failover event has occurred."
"Storage","A logical disk has come online","A logical disk has come online."
"Storage","All paths to a logical disk have gone offline","All paths to a logical disk have gone offline."
"Storage","Free disk space has reached warning threshold","Free disk space has reached warning threshold on volume %s."
"Storage","Free disk space has reached error threshold","Free disk space has reached error threshold on volume %s."
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web1, load: 1.07