#************************************************************************
# This evafilter.txt file CVS Revision is 1.22                          |
#									|
# The format of the EVA Event Code values used for WEBES EVA HSV	|
# filtering contained in this file is as follows:			|
#									|
# The filter number  "0xAABBCCDD" is the complete VCS Event Code.	|
# 									|
# Where:  AA = SCID							|
#	  BB = EIP_event_number						|
#	  CC = CAC							|
#	  DD = EIP_type_code						|
#									|
# They are located in, and extracted from the EIP_Common_Prefix frame 	|
# of the event log							|
#									|
# In the following list of EVA event codes, two comment characters      |
# are used to separate the event code from the corresponding text.      |
# When the pound sign (#) is used, this event will be processed by      |
# the analysis rules.  When the at sign (@) is used, the event will     |
# not be processed, but the text following the event code will be       |
# with the event in the event summary.                                  |
#                                                                       |
# An additional feature is that the <FONT COLOR=...></FONT> tags        |
# should be recognized by supported browers with the affect of          |
# displaying the event text in the specified color in the Summary       |
# section.                                                              |
#                                                                       |
# Color Legend:                                                         |
#                                                                       |
#    red         = Significant events                                   |
#    green       = Configuration events and return to normal status     |
#                  from a previous failure                              |
#    blue        = EVA Reboot/Resync/Restart, etc.                      |
#    darkorange  = Data Availability, CA, Customer attention needed     |
#    magenta     = Drive firmware update events                         |
#    purple      = Thresholded events                                   |
#                                                                       |
#************************************************************************
#Revision History
#
#	Randy Wolf 	Added DRM events 0x0c17630c/	V1.120	01-Sep-04
#			0x0c18640c/0x0c1b5f0c/0x0c1c610c/
#			and 0x0c1e5f0c.  All of which are set 
#			as "analyzable".
#
#	Randy Wolf 	Added events 0x0300200a 	V1.120	02-Sep-04
#			and 0x0b01b515.  Both of which 
#			are set as "analyzable".
#	Randy Wolf	Enabled event 0x09d50005 per
#			Roy Carlson's request
#	Randy Wolf	Enabled events 0x0c22000c/ 	V1.22	14-Dec-04
#			0x0c23670c/ and 0x4206001b
#			as required to support VCS V3025
#	Randy Wolf	Enabled event 0x0c1a000c	V1.23	15-Dec-04
#			as required to support VCS V3025
#	Randy Wolf	Disabled event 0x4206001b.	V1.24	15-Dec-04
#			Will not analyze event
#       Randy Wolf      Added SDC (EIP19) events	V1.25	16-Feb-05
#	Roy carlson	Turned on 06120008, 944a0003	V1.26	17-Feb-05
#			09d1b905, & 09cdc305
#			Turned off 06130013, 09144005,
#			0914bf05, & 092dbf05 
#	Roy Carlson	Turned on 030b4f0b		V1.27	26-Feb-05
#			Turned off 0300000a, 0300200a, 0303000a, 06080007, 
#			060a0013, 06390009, 09010005, 09030005, 09040005, 
#			09090005, 090a0005, 09110005, 09160005, 09180005, 
#			091e0005, 09200005, 09210005, 09240005, 09270005, 
#			& 09290005
#	Randy Wolf	Added additional SDC (EIP19) 	V1.28	28-Feb-05
#	Roy Carlson	Added 0x0c20650c		V1.29	05-MAR-05
#			0x0c24000c, 0x0c285f0c, & 0x0c2a000c
#	Randy Wolf	Added 0x09d8b605 to fix PTR 	V1.30	07-Mar-05
#	Roy Carlson	Turned on 0303000a		V1.31	14-Mar-05
#	Randy Wolf	Added 0x0400031c, 0x0400031d, 	V1.302	12-Apr-05
#			0x0401031c, 0x0401031d,
#                       0x040e031c, 0x040e031d,
#	Roy Carlson	Added 0x0c2b600c, 0x0c2c660c	V1.4	15-Apr-05
#			Turned on 6000009, 06090013, 061a0009
#			06460008, 06480008, & 06394008
#	Roy Carlson	Changed colors from John c	V1.5	16-Jun-05
#	Roy Carlson	Added 0x0c0f, 0x0c0d, 0x0c1f	v1.6	28-Jun-05
#			and 0x0c25 to support DTCS
#	Roy Carlson	Turned on 06410017		V1.7	06-Jul-05
#	Roy Carlson	Ignore 0930 & turn on 0414	V1.8	06-Aug-05
#			0415, 0416, 041a, & 041b
#	Roy Carlson	Turned on 0e15, 0e17, 0e1b, 0e1c V1.9	29-Sep-05
#	Roy Carlson	Turned on 0x09040005			14-Mar-06
#	Roy Carlson	Added 64d0008, 64e0009, 30f001e  V2.0	29-Mar-06
#			70c0115, 70d0015, 83073a14, 9dd0005, 
#			9df0005, 9e00005, 9e100005, & 9e20005
#	Roy Carlson	Turned on 944ba0e		V2.1	25-APR-06
#	Roy Carlson	Turned off 942500e		V2.2	17-May-06
#	Roy Carlson	Turned on 0x060d		V2.3	25-May-06
#	Roy Carlson	Turned off 0905, 0907, & 092c	V2.4	06-Jun-06
#	Roy Carlson	Turned on 8308, 8309, 0b08,	V2.5	29-Jul-06
#			0c2e, 0c2f,0df6, 0df8, 094c, 094d, 094e, 09de, 09e2, 0310
#	Roy Carlson	Turned on 0c30			V2.6	02-Aug-06
#	Roy Carlson	Ignore 6 35 & 6 37		V2.7	27-Nov-06
#	Roy Carlson	Added DRM events for v6.100	v2.8	05-Apr-07
#			oc: 31 thru 60, 830a, 0b09, 420a, 097e-0981, 0311-0317
#	Roy Carlson	Turned on 09 7b, 42 06, & 42 0a	v2.9	24-Apr-07
#	Roy Carlson	Turned on 06 03			v2.10	25-Apr-07
#
#
#------------------------------------------------------------------------
#  The Executive Services (EXEC) events are:
#
0x0100000d@-EXEC During Executive Services initialization the system time value was set.
0x0101000d@-EXEC The system time value was set by a call to the EXEC$SET_TIME service.
0x0102000d@-EXEC A time change occurred.
#
#-----------------------------------------------------------------------------------------------
#  The Storage System Services events are:
#
0x0301400b#-<FONT COLOR=red>SCS Disk rendered inoperable</FONT>
0x0302410a#-<FONT COLOR=red>SCS Disk won't be used because it represents "too many"</FONT>
0x0303000a#-<FONT COLOR=blue>SCS A controller has begun booting</FONT>
0x030b4f0b#-<FONT COLOR=red>SCS Disk drive has failed during Storage System realization</FONT>
0x030f001e#-<FONT COLOR=green>SCS RoHS Status of the HSV210 controller has been determined</FONT>
0x03114420#-<FONT COLOR=red>SCS A Fibre Channel Switch responded to a fabric port login</FONT>
#
0x0300000a@-SCS A controller can't communicate with the CBIC
0x0304000a@-SCS A controller has finished the process of bringing the Storage System online.
0x0305000a@-SCS A controller has been joined into the Storage System.
0x0306000a@-SCS A controller has been ousted from the Storage System.
0x0307000a@-SCS A controller is now the Storage System Master.
0x0308000a@-SCS A controller has been brought into the Storage System.
0x03090018@-SCS The Redundant Storage Set has started migrating members
0x030a0018@-SCS Redundant Storage Set has finished migrating members
0x030c001e@-SCS The DebugFlags and/or PrintFlags have changed
0x030d001e@-SCS Process with work during CSM reset
0x030e070b@-SCS About to write ID block to wrong physical disk drive
0x0310001f@-SCS A Storage System Virtual Disk has changed controller mastership
0x03120021@-SCS A Logical Disk attach operation has completed
0x03130021@-SCS A snapclone Logical Disk has completed the unsharing operation
0x03140021@-SCS A mirror clone Logical Disk has completed the detach operation
0x03150021@-SCS A mirror clone Logical Disk has completed the fracture operation
0x03160021@-SCS A mirror clone Logical Disk has completed the synchronization operation
0x03170021@-SCS A Logical Disk has completed the instant restore operation
#
#------------------------------------------------------------------------------------------------
#  The Fault Manager (FM) events are: (Note: this includes EIP1C and EIP1D Events)
#
0x04000300#-<FONT COLOR=blue>FM Termination Events (the controller reporting itself)</FONT>
0x0400031c#-<FONT COLOR=blue>FM Termination Events (the controller reporting itself)</FONT>
0x0400031d#-<FONT COLOR=blue>FM Termination Events (the controller reporting itself)</FONT>
0x04010300#-<FONT COLOR=blue>FM Last Gasp Termination Events (the other controller reporting)</FONT>
0x0401031c#-<FONT COLOR=blue>FM Last Gasp Termination Events (the other controller reporting)</FONT>
0x0401031d#-<FONT COLOR=blue>FM Last Gasp Termination Events (the other controller reporting)</FONT>
0x04020101#-<FONT COLOR=blue>FM Machine check while a Termination event was processed</FONT>
0x04030102#-<FONT COLOR=blue>FM Unexpected event while a Termination event was processed</FONT>
0x04060803#-<FONT COLOR=blue>FM Insufficient Event Log Packets on the Master</FONT>
0x04070803#-<FONT COLOR=blue>FM Insufficient Event Log Packets on the non-Master</FONT>
0x040c0803#-<FONT COLOR=blue>FM Invalid EIP from remote Fault Manager</FONT>
0x040e0300#-<FONT COLOR=blue>FM Last Gasp that indicates the other should terminate operation</FONT>
0x040e031c#-<FONT COLOR=blue>FM Last Gasp that indicates the other should terminate operation</FONT>
0x040e031d#-<FONT COLOR=blue>FM Last Gasp that indicates the other should terminate operation</FONT>
0x04100103#-<FONT COLOR=blue>FM Insufficient ISR Event Log Packets on the Master</FONT>
0x04100803#-<FONT COLOR=blue>FM Insufficient ISR Event Log Packets on the Master</FONT>
0x04110803#-<FONT COLOR=blue>FM Insufficient ISR Event Log Packets on the non-Master</FONT>
0x0414031d#-<FONT COLOR=blue>FM Controller operation terminated due to an unrecoverable event.</FONT>
0x0415031d#-<FONT COLOR=blue>FM Controller received a last gasp message from another controller.</FONT>
0x0416031d#-<FONT COLOR=blue>FM Controller sent last gasp message prior to terminating operation.</FONT>
0x041a031d#-<FONT COLOR=blue>FM An error while controller when Terminating this process.</FONT>
0x041b031d#-<FONT COLOR=blue>FM An error while controller on last Terminating process.</FONT>
#
0x04040003@-<FONT COLOR=green>FM The Storage System Event Log validation completed successfully.</FONT>
0x04050003@-FM The Storage System Event Log validation failed.
0x04080003@-FM The Storage System Termination Event Log has become inaccessible.
0x04090003@-<FONT COLOR=green>FM The Storage System Termination Event Log validation completed successfully.</FONT>
0x040a0003@-FM The Storage System Termination Event Log validation failed.
0x040b0003@-FM The Termination Event Log has been updated with info from the secondary controller.
0x040d0003@-FM The Fault Manager operation was made quiescent.
0x040f0003@-FM This controller sent its termination events to the Master controller.
0x04120003@-FM The last event reporting interval has changed.
0x04130003@-FM Storage System event reporting is still active.
0x04180003@-<FONT COLOR=green>FM Manufacturing Event Log validation completed successfully.</FONT>
0x04190003@-FM The Manufacturing Event Analysis Log validation failed.
#
#------------------------------------------------------------------------
#  The Fibre Channel Services (FCS) events are:
#
0x06004009#-<FONT COLOR=red>FCS Exceeded SMART threshold</FONT>
0x06014a08#-<FONT COLOR=red>FCS Fibre Channel port failed to respond</FONT>
0x06020009#-<FONT COLOR=purple>A drive has reported a check condition error</FONT>
0x06034713#-<FONT COLOR=purple> FC exchange sent to a physical disk drive has timed out</FONT>
0x06094013#-<FONT COLOR=red>FCS Numerous SMART errors</FONT>
0x060c0013#-<FONT COLOR=green>FCS Loop switch detected</FONT>
0x060d0013#-<FONT COLOR=green>FCS Location of a disk previously reported as unknown is now known.</FONT>
0x060e9613#-<FONT COLOR=red>FCS EMU Firmware update not found</FONT>
0x060f4013#-<FONT COLOR=red>FCS EMU can communicate to drive, but controller can't</FONT>
0x06108913#-<FONT COLOR=red>FCS Controller can't communicate with EMU</FONT>
0x06120008#-<FONT COLOR=red>FCS The retry count for a task assigned to a EMU has been exhausted.</FONT>
0x06149813#-<FONT COLOR=green>FCS Too many drive enclosures</FONT>
0x06159913#-<FONT COLOR=green>FCS FC Cable is connected to the wrong FC port</FONT>
0x06169713#-<FONT COLOR=green>FCS Controller doesn't have an address on the CAN bus</FONT>
0x06174013#-<FONT COLOR=red>FCS The EMU has bypassed a drive</FONT>
0x061a4009#-<FONT COLOR=red>FCS Disk exceeded soft error threshold</FONT>
0x061e4c13#-<FONT COLOR=red>FCS Controller has detected only one port on a device</FONT>
0x061c4709#-<FONT COLOR=purple>FCS Outbound frame timed out</FONT>
0x06204013#-<FONT COLOR=red>FCS Unsupported device found</FONT>
0x06224d04#-<FONT COLOR=magenta>FCS Unrecognized drive or firmware found by code load</FONT>
0x06254313#-<FONT COLOR=red>FCS EMU failed to assign a hard address to a drive</FONT>
0x06268913#-<FONT COLOR=red>FCS EMU failed to assign an address to a drive</FONT>
0x06270113#-<FONT COLOR=red>FCS EMU failed to assign address(s) to a drive</FONT>
0x062b4004#-<FONT COLOR=red>FCS Drive was bypassed</FONT>
0x06304e13#-<FONT COLOR=red>FCS All devices in an enclosure are Single Port on Fibre</FONT>
0x06324e13#-<FONT COLOR=red>FCS All devices on a loop are Single Port on Fibre</FONT>
0x06364d04#-<FONT COLOR=magenta>FCS Unsupported Fibre Channel drive firmware revision</FONT>
0x0638c404#-<FONT COLOR=magenta>FCS Down-rev Fibre Channel drive firmware revision</FONT>
0x06394009#-<FONT COLOR=red>FCS A drive bay was bypassed to restore operability</FONT>
0x06394008#-<FONT COLOR=red>FCS A drive bay was bypassed to restore operability</FONT>
0x063d9b09#-<FONT COLOR=red>FCS An enclosure on the cabinet address bus has no FC connection</FONT>
0x063ec513#-<FONT COLOR=red>FCS An enclosure was found on FC, but not on the cab addr bus</FONT>
0x063f9c13#-<FONT COLOR=red>FCS Disk is using improper protocol to attempt communication with EMU</FONT>
0x06404d04#-<FONT COLOR=magenta>FCS A disk that has new capabilities has been detected.</FONT>
0x06410017#-<FONT COLOR=magenta>FCS The loop config may have changed on a controller's FC port.</FONT>
0x06430008#-<FONT COLOR=green>FCS Loop switch detection on a controller's Fibre Channel port.</FONT>
#
0x06044812@-FCS Unexpected work
0x06054909@-FCS Disk or MP didn't respond
0x06074709@-FCS Target Discovery Service Descriptor timed out
0x06080007@-FCS Excessive link errors on a Fibre Channel port
0x060a0013@-FCS A drive has reported numerous check condition errors
0x060b4709@-FCS Non-data exchange has timed out
0x06130013@-FCS Controller to EMU communication restored
0x06180013@-FCS An EMU has begun updating its code.  Do not power down the enclosure.
0x06190013@-FCS An EMU has completed updating its code.  It is now safe to power down enclosure.
0x061b0013@-FCS A controller now has an address on the enclosure address bus.
0x061d4709@-FCS Exchange to a disk finished, but is missing data
0x061f0013@-FCS Drive Single Port on Fibre fixed
0x06210013@-FCS A Fibre Channel device with incorrect block size has been detected.
0x06230013@-FCS A controller is about to retry a failed port.
0x06240013@-FCS A controller has successfully retried a failed port.
0x06280008@-FCS The retry count for an OB task assigned to a EMU has been exhausted.
0x06290009@-FCS The controller has sent a Basic Link Service command Abort Sequence Frame.
0x062a0009@-FCS The controller has sent an Extended Link Service command Reinstate Recovery Qualifier.
0x062c0012@-FCS One or more media defects were detected on a physical disk drive.
0x062d0012@-FCS A controller issued a directed LIP to an arbitrated loop physical address.
0x062e0012@-FCS A controller has detected loop receiver failures.
0x06310013@-FCS Enclosure Single Port on Fibre fixed
0x06330013@-FCS Loop Single Port on Fibre fixed
0x06340013@-FCS A controller has been told to enable a device port.
0x06354d04@-FCS Unrecognized Fibre Channel drive firmware revision
0x0637c404@-FCS Newer than supported Fibre Channel drive firmware revision
0x063a0008@-FCS The controller is attempting to recover devices
0x063b0008@-FCS The controller has finished error recovery attempts
0x063c0008@-FCS The controller has been requested to unbypass bays on a port
0x06440008@-FCS Controller is evaluating the next drive enclosure in the Loop Recovery Process.
0x06450008@-FCS Controller has identified a starting point for the Loop Recovery Process.
0x06460008@-FCS Controller has determined the CAB bus is not usable at this time.
0x06480008@-FCS EMU unbypass operation failed.
0x06490008@-FCS Controller is attempting to recover devices in the indicated enclosure.
0x064a0008@-FCS Controller has finished error recovery attempts in the indicated enclosure.
0x064c0004@-FCS Device Fibre Channel physical disk drive was placed on the Drive Suspect List (DSL)
0x064b0008@-FCS Controller has been instructed to Enable or Disable Loop Recovery Operations
0x064d0008@-FCS Controller has completed codeload to all EMUs
0x064e0009@-FCS A physical disk drive has reported a non-zero RSP_CODE in response to an I/O
#
#--------------------------------------------------------------------------
#  The Container Services events are:
#
0x0700b515#-<FONT COLOR=darkorange>CS Allocation of a Virtual Disk stalled; out of space.</FONT>
0x0701b515#-<FONT COLOR=darkorange>CS Expansion of a Virtual Disk stalled; out of space.</FONT>
0x070c0115#-<FONT COLOR=red>CS Metadata inconsistency.</FONT>
#
0x07020015@-CS Leveling of capacity in a Disk Group has started.
0x07030015@-<FONT COLOR=green>CS Leveling of capacity in a Disk Group has finished.</FONT>
0x07040015@-CS A member management operation has started
0x07050015@-<FONT COLOR=green>CS A member management operation has finished</FONT>
0x07060015@-CS Data Migration has started on a Disk Group.
0x07070015@-<FONT COLOR=green>CS Data migration has finished on a Disk Group.</FONT>
0x07080015@-CS Deallocation of a Virtual Disk has failed.
0x0709b515@-CS A member management operation has stalled; out of space
0x070a0015@-CS A stalled member management operation is being restarted.
0x070b0015@-CS Unexpected metadata utility event.
0x070d0015@-CS A member management operation encounter an error while processing a Logical Disk.
#
#--------------------------------------------------------------------------
#  The Storage System Management Interface (SCMI) event are:
#
0x09020005#-<FONT COLOR=green>SCMI Volume condition changed; no action required</FONT>
0x09040005#-<FONT COLOR=green>SCMI Controller Normal</FONT>
0x09070005#-<FONT COLOR=green>SCMI Fibre Channel port NORMAL</FONT>
0x0908b405#-<FONT COLOR=darkorange>SCMI Occupancy Alarm Level threshold has been reached</FONT>
0x090e2e05#-<FONT COLOR=red>SCMI Temperature trip point has been reached</FONT>
0x090f2e05#-<FONT COLOR=darkorange>SCMI Temperature nearing trip point</FONT>
0x09122405#-<FONT COLOR=red>SCMI Blower #1 has failed</FONT>
0x09132005#-<FONT COLOR=red>SCMI Voltage sensor detected voltage out-of-range</FONT>
0x0915b905#-<FONT COLOR=red>SCMI Controller Failed</FONT>
0x09172805#-<FONT COLOR=red>SCMI Battery #1 has been removed</FONT>
0x091a2005#-<FONT COLOR=red>SCMI Battery voltage regulator is offline</FONT>
0x091d2205#-<FONT COLOR=red>SCMI Battery #1 has malfunctioned</FONT>
0x091f2905#-<FONT COLOR=red>SCMI Battery #2 has been removed</FONT>
0x09222305#-<FONT COLOR=red>SCMI Battery #2 has malfunctioned</FONT>
0x09232b05#-<FONT COLOR=red>SCMI Blower #2 has been removed</FONT>
0x09252505#-<FONT COLOR=red>SCMI Blower #2 has failed</FONT>
0x09262c05#-<FONT COLOR=red>SCMI Blower/Power Supply #1 has been removed or lost power</FONT>
0x09282d05#-<FONT COLOR=red>SCMI Blower/Power Supply #2 has been removed or lost power</FONT>
0x092a2605#-<FONT COLOR=red>SCMI Blower/Power Supply #1 has failed</FONT>
0x092b2705#-<FONT COLOR=red>SCMI Blower/Power Supply #2 has failed</FONT>
0x09314205#-<FONT COLOR=red>SCMI Physical Disk Drive state is Degraded</FONT>
0x09324005#-<FONT COLOR=red>SCMI Physical Disk Drive state is Failed</FONT>
0x0936000e#-<FONT COLOR=green>SCMI Physical Disk Drive has been Discovered</FONT>
0x093e420e#-<FONT COLOR=red>SCMI Physical Disk Drive state is Disappeared</FONT>
0x094a0003#-<FONT COLOR=darkorange> Destination DR Group not deleted </FONT>
0x097b000f#-<FONT COLOR=darkorange> Auto suspend attribute of a DR Group changed </FONT>
0x09c85105#-<FONT COLOR=darkorange>SCMI Logical Disk Data Availability state is Data Lost</FONT>
0x09c95105#-<FONT COLOR=red>SCMI Disk Group state is INOPERATIVE</FONT>
0x09ca5105#-<FONT COLOR=red>SCMI Logical Disk state is Failed</FONT>
0x09cb5005#-<FONT COLOR=red>SCMI Logical Disk state is Snapshot Overcommit</FONT>
0x09cc5105#-<FONT COLOR=red>SCMI Logical Disk state is Data Lost</FONT>
0x09cdc305#-<FONT COLOR=red>SCMI Fibre Channel port FAILED</FONT>
0x09ce0005#-<FONT COLOR=darkorange>SCMI Disk Group state is INOPERATIVE MARKED</FONT>
0x09cf4105#-<FONT COLOR=red>SCMI Physical Disk Drive state is Not Present</FONT>
0x09d1b905#-<FONT COLOR=red>SCMI The HSV controller needs attention</FONT>
0x09d22a05#-<FONT COLOR=red>SCMI Blower #1 has been removed</FONT>
0x0944ba0e#-<FONT COLOR=darkorange>SCMI An HSV controller has left the Storage System</FONT>
0x09d50005#-<FONT COLOR=red>SCMI Disk is "Single Port on Fibre"</FONT>
0x09d63705#-<FONT COLOR=red>SCMI Temperature sensors do not agree</FONT>
0x09d73705#-<FONT COLOR=red>SCMI Temperature sensors can not be accessed</FONT>
0x09df0005#-<FONT COLOR=green>SCMI A mirror clone Logical Disk completed detach operation.</FONT>
0x09e00005#-<FONT COLOR=green>SCMI A mirror clone Logical Disk completed fracture operation.</FONT>
0x09e10005#-<FONT COLOR=green>SCMI Mirror clone Logical Disk completed synchronization operation</FONT>
0x09e20005#-<FONT COLOR=green>SCMI Logical Disk has completed the instant restore operation</FONT>
#
0x09010005@-<FONT COLOR=green>SCMI Physical Disk Drive state is Normal.</FONT>
0x09030005@-SCMI Logical Disk state changed; no action required.
0x09050005@-<FONT COLOR=green>SCMI Battery hold-up time is > 0 hours</FONT>
0x0906bf05@ SCMI Volume Missing
0x09090005@-SCMI Volume Resource Availability Sufficient
0x090a0005@-<FONT COLOR=green>SCMI Logical Disk Data Availability state is Normal</FONT>
0x090c0005@-SCMI A snapclone Logical Disk has completed the unsharing operation.
0x090d0005@-SCMI The state of the quorum disk flag of a Volume has changed.
0x09110005@-<FONT COLOR=green>SCMI Blower #1 is present</FONT>
0x091bf005@-SCMI Volume Failed
0x09160005@-<FONT COLOR=green>SCMI Temperature returned to normal</FONT>
0x09180005@-<FONT COLOR=green>SCMI Battery #1 is normal</FONT>
0x09190005@-<FONT COLOR=green>SCMI A voltage sensor has returned to a normal range./FONT>
0x091b0005@-<FONT COLOR=green>SCMI Disk Group state is Normal</FONT>
0x091c0005@-<FONT COLOR=green>SCMI Occupancy Alarm Level Normal</FONT>
0x091e0005@-<FONT COLOR=green>SCMI Battery #1 is present</FONT>
0x09200005@-<FONT COLOR=green>SCMI Battery #2 is present</FONT>
0x09210005@-<FONT COLOR=green>SCMI Battery #2 is normal</FONT>
0x09240005@-<FONT COLOR=green>SCMI Blower #2 is present</FONT>
0x09270005@-<FONT COLOR=green>SCMI Blower/Power Supply #1 is present</FONT>
0x09290005@-<FONT COLOR=green>SCMI Blower/Power Supply #2 is present</FONT>
0x092c2f05@-<FONT COLOR=darkorange>SCMI Battery hold-up time is zero hours</FONT>
0x092dbf05@-SCMI Volume Resource Availability Insufficient
0x092e0005@-SCMI A controller has rejected a login attempt.
0x092f0005@-SCMI A controller has processed a SCMI command with the result of non-success return code.
0x09300005@-SCMI Physical drive map has been updated
0x0933000e@-SCMI A Derived Unit was created.
0x0934000e@-SCMI A Logical Disk was created.
0x0935000e@-SCMI A Disk Group was created.
0x0937000e@-SCMI A Presented Unit was created
0x0937000e@-SCMI A Presented Unit was created.
0x0938000e@-SCMI A Storage System Host Path was created.
0x0939000e@-SCMI A Storage System Virtual Disk was created.
0x093a000e@-SCMI A Volume was created.
0x093b000e@-SCMI A Derived Unit was deleted.
0x093c000e@-SCMI A Logical Disk was deleted.
0x093d000e@-SCMI A Disk Group was deleted.
0x093f000e@-SCMI A Presented Unit was deleted.
0x0940000e@-SCMI A Storage System Host Path was deleted.
0x0941000e@-SCMI A Storage System Virtual Disk was deleted.
0x0942500e@-<FONT COLOR=darkorange>SCMI Snapshot marked inoperative due to insufficient space</FONT>
0x0943000e@-SCMI A controller has joined the Storage System.
0x0945000e@-SCMI The Storage System has been deleted.
0x0946000e@-<FONT COLOR=green>SCMI A Data Replication Group has been created</FONT>
0x0947000e@-SCMI A Data Replication Group was deleted.
0x0948000e@-SCMI An internal Logical Disk associated with a snapshot Virtual Disk was created.
0x0949000e@-SCMI An internal Logical Disk associated with a copy of a Virtual Disk was created.
0x094b000e@-SCMI A Volume was removed from a LDAD.
0x094c000e@-SCMI A new Remote Node has been discovered
0x094d000e@-SCMI The Remote Node object has been discarded
0x094e000e@-SCMI The Remote Node Storage System UUID has changed
0x0965000f@-SCMI A host operating system mode has changed.
0x0966000f@-SCMI Time was set on a Storage System.
0x0967000f@-SCMI The LUN of a Presented Unit has changed.
0x0968000f@-SCMI The device addition policy of a Storage System has changed.
0x0969000f@-SCMI The quiescent state of a Storage System Virtual Disk has changed.
0x096a000f@-SCMI The enabled/disabled state of a Storage System Virtual Disk has changed.
0x096b000f@-SCMI The cache policy of a Storage System Virtual Disk has changed.
0x096c000f@-SCMI The usage state of a Volume changed.
0x096d000f@-SCMI The disk failure protection level of a Disk Group has changed.
0x096e000f@-SCMI The write protected state of a Derived Unit has changed.
0x0970460f@-SCMI Drive has numerous communication failures
0x0971000f@-SCMI A controller has received a request to shutdown.
0x0972000f@-SCMI A controller has completed its shutdown preparations.
0x0973000f@-SCMI The failsafe state of a Data Replication Group has changed.
0x0974000f@-SCMI The mode of a Data Replication Group has changed.
0x0975000f@-SCMI The synchronous/asynchronous operational state of a Data Replication Group has changed.
0x0976000f@-SCMI The read only attribute of a Data Replication Group has changed.
0x0977000f@-SCMI A Data Replication Group failover has occurred.
0x0978000f@-SCMI A Data Replication Group has been suspended or resumed.
0x0979000f@-SCMI A Storage System Virtual Disk was added to a Data Replication Group.
0x097a000f@-SCMI A Storage System Virtual Disk was removed from a Data Replication Group.
0x097c000f@-SCMI The destination presentation attribute of a Data Replication Group has changed
0x097d000f@-SCMI The flags of a physical disk drive have changed because of a maintenance mode change
0x09d00005@-<FONT COLOR=green>SCMI The HSV controller no longer needs attention</FONT>
0x09d35105@-SCMI A Virtual Disk in the DR Group is Inoperative
0x09d40005@-SCMI All the Vdisks associated with a DR Group have transitioned to the OPERATIVE state.
0x09d8b605@-SCMI Disk Group has lost Redundancy
0x09d90005@-SCMI A Disk Group has attained a Single Point of Failure Robust Configuration
0x09da0005@-<FONT COLOR=green>SCMI A controller's blower "1" is running at normal speed.</FONT>
0x09db0005@-<FONT COLOR=green>SCMI A controller's blower "2" is running at normal speed.</FONT>
0x09dc0b05@-SCMI Controller's glue eeprom has been programmed
0x09dd0005@-SCMI Controller receives a maintenance mode call from the user
0x09de5205@-SCMI Internal Logical Disk has transitioned to the INVALIDATED state
0x097e000f@-SCMI Data Replication Group has changed
0x097f000f@-SCMI Data Replication Group has changed
0x0980000f@-SCMI Data Replication Group has changed
0x0981000f@-SCMI Data Replication Group has changed
#
#---------------------------------------------------------------------------
#  The System Services (SYS) event is:
#
0x0b000010#-<FONT COLOR=red>EXECB The controller has begun a resynchronization operation</FONT>
0x0b01b515#-<FONT COLOR=darkorange>EXECB A migrate method drive codeload has stalled.</FONT>
0x0b080c1a#-<FONT COLOR=red>EXECB Controller failed a code load</FONT>
#
0x0b020004@-EXECB A FC disk drive firmware has been loaded into memory in preparation for codeload
0x0b040004@-EXECB A fibre channel physical disk drive firmware codeload begun
0x0b050004@-EXECB A fibre channel physical disk drive firmware has finished
0x0b060004@-EXECB Controller has begun/finished a code load
0x0b070b1a@-EXECB Controller has finished a code load to the GLUE eeprom
0x0b09001e@-EXECB Process with work, eg. During CSM Hang and Unit Stalled Too Long
#
#---------------------------------------------------------------------------
#  The Data Replication Manager (DRM) events are:
#
0x0c00000c#-<FONT COLOR=darkorange>DRM Destination Virtual Disk has completed a full copy</FONT>
0x0c015f0c#-<FONT COLOR=darkorange>DRM Source Virtual Disk transitioned to Logging</FONT>
0x0c02610c#-<FONT COLOR=darkorange>DRM Source Virtual Disk transitioned to Logging</FONT>
0x0c03000c#-<FONT COLOR=darkorange>DRM Destination Virtual Disk is Merging</FONT>
0x0c045f0c#-<FONT COLOR=darkorange>DRM The DR Group has entered Failsafe locked</FONT>
0x0c05600c#-<FONT COLOR=darkorange>DRM The DR Group has entered Failsafe locked</FONT>
0x0c06600c#-<FONT COLOR=darkorange>DRM An unrecoverable read error on the Source</FONT>
0x0c075f0c#-<FONT COLOR=green>DRM A Full Copy terminated prior to completion</FONT>
0x0c08610c#-<FONT COLOR=green>DRM A Full Copy terminated prior to completion</FONT>
0x0c09620c#-<FONT COLOR=darkorange>DRM A Data Replication Log has been reset due to space</FONT>
0x0c0a000c#-<FONT COLOR=darkorange>DRM A DR Log has been reset due to a DR Group failover.</FONT>
0x0c0c000c#-<FONT COLOR=green>DRM A Destination Data RG has successfully completed a Merge.</FONT>
0x0c0f000c#-<FONT COLOR=blue>DRM A DR Group is no longer in a Failsafe Locked state (DTCS only).</FONT>
0x0c10000c#-<FONT COLOR=darkorange>DRM A Destination DR Group has been marked for a full copy</FONT>
0x0c11000c#-<FONT COLOR=darkorange>DRM A Virtual Disk is transitioning from Source to Destination</FONT>
0x0c155f0c#-<FONT COLOR=darkorange>DRM Path between this Site and the Alternate Site has closed.</FONT>
0x0c17630c#-<FONT COLOR=darkorange>DRM DRM comm protocol is mismatched between dest and source.</FONT>
0x0c18640c#-<FONT COLOR=darkorange>DRM The DR Destination is limiting replication throughput.</FONT>
0x0c1a000c#-<FONT COLOR=darkorange>DRM Data Replication Manager State Change.</FONT>
0x0c1b5f0c#-<FONT COLOR=darkorange>DRM The DR Group has transitioned to the Logging state.</FONT>
0x0c1c610c#-<FONT COLOR=darkorange>DRM The DR Group has transitioned to the Logging state.</FONT>
0x0c1e5f0c#-<FONT COLOR=darkorange>DRM The Remote Storage System is not accessible.</FONT>
0x0c1d000c#-<FONT COLOR=blue>DRM Inconsistency was found in the group log (DTCS only).</FONT>
0x0c1f000c#-<FONT COLOR=blue>DRM Members of a Source DR Group are presented to host (DTCS only).</FONT>
0x0c20650c#-<FONT COLOR=darkorange>DRM DR Destination Site are preventing replication processing</FONT>
0x0c21660c#-<FONT COLOR=darkorange>DRM Data Replication Manager State Change.</FONT>
0x0c22000c#-<FONT COLOR=darkorange>DRM Data Replication Path has been opened.</FONT>
0x0c23670c#-<FONT COLOR=darkorange>DRM Unacceptable Data replication throughput.</FONT>
0x0c24000c#-<FONT COLOR=darkorange>DRM The Source DR Group has transitioned to the Logging state</FONT>
0x0c25000c#-<FONT COLOR=blue>DRM A Full Copy terminated prior to completion (DTCS only).</FONT>
0x0c285f0c#-<FONT COLOR=darkorange>DRM A DR Path Alternate Site is not currently accessible.</FONT>
0x0c2a000c#-<FONT COLOR=darkorange>DRM A DR Path Alternate Site is now accessible</FONT>
0x0c2b600c#-<FONT COLOR=darkorange>DRM A Merge was terminated prior to completion</FONT>
0x0c2c660c#-<FONT COLOR=darkorange>DRM A replication operation has stalled</FONT>
0x0c2e680c#-<FONT COLOR=darkorange>DRM Unable to discover additional remote nodes</FONT>
0x0c3f000c#-<FONT COLOR=darkorange>DRM Able to discovery of additional remote node</FONT>
0x0c30000c#-<FONT COLOR=darkorange>DRM Received command to dump log data and start a full copy</FONT>
0x0c325f0c#-<FONT COLOR=darkorange>DRM DR tunnel closed because host port failed</FONT>
0x0c335f0c#-<FONT COLOR=darkorange>DRM DR tunnel closed because link is unresponsive</FONT>
0x0c345f0c#-<FONT COLOR=darkorange>DRM DR tunnel closed because of slow response on connection</FONT>
0x0c35070c#-<FONT COLOR=darkorange>DRM DR tunnel closed because config change lock release slow</FONT>
0x0c365f0c#-<FONT COLOR=darkorange>DRM DR tunnel closed due to thrashing between 2 host ports</FONT>
0x0c375f0c#-<FONT COLOR=darkorange>DRM DR tunnel closed because max ping count exceeded</FONT>
0x0c38630c#-<FONT COLOR=darkorange>DRM DR tunnel closed because protocal version not supported</FONT>
0x0c3a5f0c#-<FONT COLOR=darkorange>DRM DR tunnel could not be created</FONT>
0x0c3d5f0c#-<FONT COLOR=darkorange>DRM DR tunnel closed because frame retransmit limit</FONT>
0x0c40690c#-<FONT COLOR=darkorange>DRM DR tunnel closed because of out of order frame sequence</FONT>
0x0c58690c#-<FONT COLOR=darkoragne>DRM Excessive data exchange retry rate on link</FONT>
0x0c59690c#-<FONT COLOR=darkoragne>DRM Excessive out of order message rate on link</FONT>
0x0c5a670c#-<FONT COLOR=darkoragne>DRM Excessive PING response time on link</FONT>
0x0c5b670c#-<FONT COLOR=darkoragne>DRM Write resources on link reduced to minimum levels</FONT>
0x0c5c670c#-<FONT COLOR=darkoragne>DRM Copy resources on link reduced to the minimum levels</FONT>
0x0c5d000c#-<FONT COLOR=green>DRM Quality of service on the inter site link has improved</FONT>
0x0c60000c#-<FONT COLOR=darkoragne>DRM Excessive Vdisk response time at Destination</FONT>
#
0x0c12000c@-DRM A DR Group is transitioning from Destination to Source.
0x0c160016@-DRM A controller has sent a time report message to this controller.
0x0c26000c@-<FONT COLOR=green>DRM DR Path between this Site & Alternate Site has been re-opened.</FONT>
0x0c27000c@-<FONT COLOR=green>DRM DR Path between this Site & Alternate Site has been opened.-<FONT>
0x0c29000c@-DRM The DR Path between this Site and the Alternate Site has closed.
0x0c2d000c@-DRM Alternate Site port name that was incorrectly associated with a host
0x0c31000c@-DRM A stalled Full Copy has been restarted
0x0c39000c@-DRM DR tunnel closed because path is not being used
0x0c3b000c@-DRM DR tunnel closed because peer requested new DR path
0x0c3c000c@-DRM DR tunnel closed because peer tried to open DR path to a different host port
0x0c3e000c@-DRM DR tunnel closed by peer
0x0c3f000c@-DRM DR tunnel closed because NPortID of the remote port changed
0x0c41000c@-DRM DR tunnel closed to allow lower protocal version create path
0x0c42000c@-DRM DR tunnel closed because peer no longer exists
0x0c43000c@-DRM DR tunnel closed by user
0x0c49000c@-DRM DR tunnel closed because corresponding connection data was deleted
0x0c4a000c@-DRM A request to create a tunnel was rejected because the Storage System is re-starting
0x0c4b000c@-DRM A request to create a tunnel was rejected because system is not active
0x0c4c000c@-DRM A request to create a tunnel was rejected because path discovery has not completed
0x0c4d000c@-DRM A request to create a tunnel was rejected because path discovery is in process
0x0c4e000c@-DRM A request to create a tunnel was rejected because remote port is not recognized
0x0c4f000c@-DRM A request to create a tunnel was rejected because remote port WWN not recognized
0x0c50000c@-DRM A request to create a tunnel was rejected because mismatch of UUID
0x0c51000c@-DRM A request to create a tunnel was rejected because protocal not compatible
0x0c52000c@-DRM A request to create a tunnel was rejected because remote port disabled by user
0x0c53000c@-DRM A request to create a tunnel was rejected due to insufficient resources
0x0c54000c@-DRM A request to create a tunnel was rejected to force lower protocal version
0x0c55000c@-DRM A time synchronization message has been sent to a Alternate Site
0x0c56000c@-DRM The DRM Forced Logging Timeout value has been changed
0x0c57000c@-DRM The DRM Forced Logging Timeout value has been reset to the default value
0x0c5e000c@-DRM Replication Write History Log Shrink is in progress
0x0c5f000c@-DRM Replication Write History Log Shrink has completed
#
#---------------------------------------------------------------------------
#  The Drive Enclosure Environmental Monitoring Unit (EMU) events are:
#
0x0d000111#-<FONT COLOR=red>EMU Unrecognized EMU Event</FONT>
0x0d014011#-<FONT COLOR=red>EMU Non-Fibre Channel drive or incompatible link rate</FONT>
0x0d024111#-<FONT COLOR=red>EMU Drive improperly installed or missing</FONT>
0x0d034111#-<FONT COLOR=red>EMU Drive removed; drive locking enabled on non-locking enclosure</FONT>
0x0d044211#-<FONT COLOR=red>EMU Drive operating at different loop link rate</FONT>
0x0d330911#-<FONT COLOR=red>EMU AC power has been lost</FONT>
0x0d348011#-<FONT COLOR=red>EMU Power Supply improperly installed or missing</FONT>
0x0d358111#-<FONT COLOR=red>EMU Power Supply has failed</FONT>
0x0d359a11#-<FONT COLOR=red>EMU Power Supply has failed</FONT>
0x0d478311#-<FONT COLOR=red>EMU Blower not operating properly</FONT>
0x0d4b8211#-<FONT COLOR=red>EMU Blower improperly installed or missing</FONT>
0x0d4c8411#-<FONT COLOR=red>EMU Both blowers missing</FONT>
0x0d5b8611#-<FONT COLOR=red>EMU Temperature out of range</FONT>
0x0d5f8711#-<FONT COLOR=red>EMU 2 of 3 temperature groups exceed critical</FONT>
0x0d6f8811#-<FONT COLOR=red>EMU Internal EMU Error</FONT>
0x0d728a11#-<FONT COLOR=red>EMU EMU can't collect data for the SES page</FONT>
0x0d7e8c11#-<FONT COLOR=red>EMU Invalid data read from EMU NVRAM</FONT>
0x0d7f8b11#-<FONT COLOR=red>EMU Internal EMU Error</FONT>
0x0d828e11#-<FONT COLOR=red>EMU Enclosure has no address or address is incorrect</FONT>
0x0d838911#-<FONT COLOR=red>EMU EMU hardware failure</FONT>
0x0d858f11#-<FONT COLOR=red>EMU Power Supply didn't shutdown</FONT>
0x0d8d9011#-<FONT COLOR=red>EMU Transceiver error</FONT>
0x0da18111#-<FONT COLOR=red>EMU Power Supply voltage out of range</FONT>
0x0db58111#-<FONT COLOR=red>EMU Power Supply current out of range</FONT>
0x0dd89211#-<FONT COLOR=red>EMU Enclosure invalid NVRAM read error</FONT>
0x0dd99111#-<FONT COLOR=red>EMU Enclosure backplane error</FONT>
0x0ddd9311#-<FONT COLOR=red>EMU I/O Module error</FONT>
0x0dde9511#-<FONT COLOR=red>EMU I/O Module can't communicate with EMU</FONT>
0x0dec9411#-<FONT COLOR=red>EMU I/O Module invalid NVRAM read error</FONT>
0x0df68811#-<FONT COLOR=red>EMU EMU has detected missing receive  interrupts on its Com Port</FONT>
#
0x0d710011@-EMU An internal EMU error has occurred.
0x0df00011@-EMU The status has changed on one or more of the drive enclosures.
0x0df70011@-EMU EMU has rebooted following the detection of missing receive interrupts
0x0df80011@-<FONT COLOR=green>EMU EMU has initialized its Com Port</FONT>
#
#---------------------------------------------------------------------------
#   The Host Port (HP) event is:
#
0x42000008#-<FONT COLOR=darkorange>Host Port Fibre Channel link is down</FONT>
0x42010008#-<FONT COLOR=darkorange>Host Port Fibre Channel link failed</FONT>
0x42030007#-<FONT COLOR=darkorange>Host Port Fibre Channel link has excessive errors</FONT>
0x42044a08#-<FONT COLOR=red>Host Port Fibre Channel port failed to respond</FONT>
0x4206001b#-<FONT COLOR=darkoragne> Indicated VDisk transitioned to Stalled Too Long</FONT>
0x420a001b@-<FONT COLOR=green> Virtual Disk has now been unstalled and resumed</FONT>
#
0x42000006@-Host Port Fibre Channel link is down
0x42010006@-Host Port Fibre Channel link failed
0x42050008@-Host Port Fibre Channel port has transitioned to the link wedged state.
0x4207001b@-Host Indicated Virtual Disk has transitioned to ownership by other ctlr.
0x42080008@-Host A host Fibre Channel port has been reissued a freeze command.
0x42090008@-Host A host Fibre Channel port has been issued a soft reset.
#
#---------------------------------------------------------------------------
#   The Diagnostic Operations Generator (DOG) event is:
#
0x83002014#-<FONT COLOR=red>Diag On-board diagnostic failed</FONT>
0x83013014#-<FONT COLOR=red>Diag GBIC SSF Serial ID Data check code failure</FONT>
0x83022214#-<FONT COLOR=red>Diag Battery assembly failure: Battery #1</FONT>
0x83032314#-<FONT COLOR=red>Diag Battery assembly failure: Battery #2</FONT>
0x83043114#-<FONT COLOR=red>Diag Battery assembly IIC operation failure: Battery #1</FONT>
0x83053214#-<FONT COLOR=red>Diag Battery assembly IIC operation failure: Battery #2</FONT>
0x83063314#-<FONT COLOR=red>Diag Soft cache memory ECC error or low battery voltage</FONT>
0x83073a14#-<FONT COLOR=darkorange>Diag GBIC SFF not present during on-board diagnostics</FONT>
0x83083b14#-<FONT COLOR=red>Diag Failure detected during testing of this controller's SRAM.</FONT>
0x83093b14#-<FONT COLOR=red>Diag Parity error detected during testing of this controller's SRAM</FONT>
0x830a3b14#-<FONT COLOR=darkoragne>Parity failure during test of controller's SRAM</FONT>
#
#---------------------------------------------------------------------------
#   The System Data Center (SDC) events:
#
0x0e02cc19#-<FONT COLOR=red>SDC battery assembly 0 been removed </FONT> 
0x0e04c819#-<FONT COLOR=red>SDC battery assembly 0 has malfunctioned </FONT> 
0x0e06cd19#-<FONT COLOR=red>SDC battery assembly 1 been removed </FONT>
0x0e08cd19#-<FONT COLOR=red>SDC battery assembly 1 has malfunctioned </FONT> 
0x0e0ace19#-<FONT COLOR=red>SDC battery assembly 2 has been removed </FONT>
0x0e0cca19#-<FONT COLOR=red>SDC battery assembly 2 has malfunctioned </FONT>
0x0e0ecf19#-<FONT COLOR=red>SDC battery assembly 3 has been removed </FONT>
0x0e10cb19#-<FONT COLOR=red>SDC battery assembly 3 has malfunctioned </FONT>
0x0e13d019#-<FONT COLOR=red>SDC The battery subsystem has transitioned to the bad state</FONT>
0x0e150019#-<FONT COLOR=green>SDC Blower assembly 0 is now present</FONT>
0x0e16d419#-<FONT COLOR=red>SDC blower assembly 0 has been removed </FONT> 
0x0e170019#-<FONT COLOR=green>SDC The status of blower assembly 0 has changed</FONT> 
0x0e18d219#-<FONT COLOR=red>SDC blower assembly 0 has malfunctioned </FONT>
0x0e190019#-<FONT COLOR=green>SDC Diag blower assembly 1 is now present</FONT>
0x0e1ad419#-<FONT COLOR=red>SDC blower assembly 1 has been removed </FONT> 
0x0e1b0019#-<FONT COLOR=green>SDC The status of blower assembly 1 has changed</FONT> 
0x0e1cd319#-<FONT COLOR=red>Diag blower assembly 1 has malfunctioned </FONT>
0x0e1d0019#-<FONT COLOR=red>SDC A battery read memory fauilure has occured </FONT>
0x0e1f0019#-<FONT COLOR=red>SDC The temperature within a controller has returned to normal </FONT>
0x0e202e19#-<FONT COLOR=red>SDC The temperature within a controller is approaching trip point </FONT>
0x0e213619#-<FONT COLOR=red>SDC The temperature within a controller has reached the trip point </FONT>
0x0e24d819#-<FONT COLOR=red>SDC Power supply assembly 0 has been removed </FONT>
0x0e26d619#-<FONT COLOR=red>SDC Power supply 0 has lost AC connection or has malfunctioned </FONT>
0x0e28d919#-<FONT COLOR=red>SDC Power supply 1 has been removed </FONT>
0x0e2ad719#-<FONT COLOR=red>SDC Power supply 1 has lost AC connection or has malfunctioned </FONT>
#
0x0e000019@-SDC Battery subsystem boot time status report
0x0e010019@-<FONT COLOR=green>SDC Diag battery assembly 0 is now present</FONT>
0x0e030019@-SDC The status of Battery assembly 0 has changed 
0x0e050019@-<FONT COLOR=green>SDC Diag battery assembly 1 is now present</FONT>
0x0e070019@-SDC The status of Battery assembly 1 has changed  
0x0e090019@-<FONT COLOR=green>SDC Diag battery assembly 2 is now present</FONT>
0x0e0b0019@-SDC The status of Battery assembly 2 has changed  
0x0e0d0019@-<FONT COLOR=green>SDC Diag battery assembly 3 is now present</FONT>
0x0e0f0019@-SDC The status of Battery assembly 3 has changed 
0x0e110019@-<FONT COLOR=green>SDC The battery subsystem has transitioned to the good state</FONT> 
0x0e120019@-SDC The battery subsystem has transitioned to the low state
0x0e140019@-SDC Blower subsystem boot time status report
0x0e1e0019@-SDC Temperature subsystem boot time status report
0x0e220019@-SDC Power supply subsystem boot time status report
0x0e230019@-<FONT COLOR=green>SDC Power supply assembly 0 is now present</FONT>
0x0e250019@-SDC The status of power supply 0 has changed 
0x0e270019@-<FONT COLOR=green>SDC Power supply assembly 0 is now present</FONT>
0x0e290019@-SDC The status of power supply 0 has changed
#
#---------------------------------------------------------------------------
#
#   Other 
#
#
#
#