List of IMM events

40000001-00000000 : Management Controller [arg1] Network Initialization Complete.

This message is for the use case where a Management Controller network has completed initialization.

May also be shown as 4000000100000000 or 0x4000000100000000

40000002-00000000 : Certificate Authority [arg1] has detected a [arg2] Certificate Error.

This message is for the use case when there is an error with an SSL Server, SSL Client, or SSL Trusted CA Certificate.

May also be shown as 4000000200000000 or 0x4000000200000000

40000003-00000000 : Ethernet Data Rate modified from [arg1] to [arg2] by user [arg3].

This message is for the use case where a user modifies the Ethernet Port data rate.

May also be shown as 4000000300000000 or 0x4000000300000000

40000004-00000000 : Ethernet Duplex setting modified from [arg1] to [arg2] by user [arg3].

This message is for the use case where A user modifies the Ethernet Port duplex setting.

May also be shown as 4000000400000000 or 0x4000000400000000

40000005-00000000 : Ethernet MTU setting modified from [arg1] to [arg2] by user [arg3].

This message is for the use case where a user modifies the Ethernet Port MTU setting.

May also be shown as 4000000500000000 or 0x4000000500000000

40000006-00000000 : Ethernet locally administered MAC address modified from [arg1] to [arg2] by user [arg3].

This message is for the use case where a user modifies the Ethernet Port MAC address setting.

May also be shown as 4000000600000000 or 0x4000000600000000

40000007-00000000 : Ethernet interface [arg1] by user [arg2].

This message is for the use case where a user enables or disabled the ethernet interface.

May also be shown as 4000000700000000 or 0x4000000700000000

40000008-00000000 : Hostname set to [arg1] by user [arg2].

This message is for the use case where user modifies the Hostname of a Management Controller.

May also be shown as 4000000800000000 or 0x4000000800000000

40000009-00000000 : IP address of network interface modified from [arg1] to [arg2] by user [arg3].

This message is for the use case where user modifies the IP address of a Management Controller.

May also be shown as 4000000900000000 or 0x4000000900000000

4000000a-00000000 : IP subnet mask of network interface modified from [arg1] to [arg2] by user [arg3].

This message is for the use case where a user modifies the IP subnet mask of a Management Controller.

May also be shown as 4000000a00000000 or 0x4000000a00000000

4000000b-00000000 : IP address of default gateway modified from [arg1] to [arg2] by user [arg3].

This message is for the use case where a user modifies the default gateway IP address of a Management Controller.

May also be shown as 4000000b00000000 or 0x4000000b00000000

4000000c-00000000 : OS Watchdog response [arg1] by [arg2] .

This message is for the use case where an OS Watchdog has been enabled or disabled by a user.

May also be shown as 4000000c00000000 or 0x4000000c00000000

4000000d-00000000 : DHCP[[arg1]] failure, no IP address assigned.

This message is for the use case where a DHCP server fails to assign an IP address to a Management Controller.

May also be shown as 4000000d00000000 or 0x4000000d00000000

4000000e-00000000 : Remote Login Successful. Login ID: [arg1] from [arg2] at IP address [arg3].

This message is for the use case where a user successfully logs in to a Management Controller.

May also be shown as 4000000e00000000 or 0x4000000e00000000

4000000f-00000000 : Attempting to [arg1] server [arg2] by user [arg3].

This message is for the use case where a user is using the Management Controller to perform a power function on the system.

May also be shown as 4000000f00000000 or 0x4000000f00000000

40000010-00000000 : Security: Userid: [arg1] had [arg2] login failures from WEB client at IP address [arg3].

This message is for the use case where a user has failed to log in to a Management Controller from a web browser.

May also be shown as 4000001000000000 or 0x4000001000000000

40000011-00000000 : Security: Login ID: [arg1] had [arg2] login failures from CLI at [arg3].

This message is for the use case where a user has failed to log in to a Management Controller from the Legacy CLI.

May also be shown as 4000001100000000 or 0x4000001100000000

40000012-00000000 : Remote access attempt failed. Invalid userid or password received. Userid is [arg1] from WEB browser at IP address [arg2].

This message is for the use case where a remote user has failed to establish a remote control session from a Web browser session.

May also be shown as 4000001200000000 or 0x4000001200000000

40000013-00000000 : Remote access attempt failed. Invalid userid or password received. Userid is [arg1] from TELNET client at IP address [arg2].

This message is for the use case where a user has failed to log in to a Management Controller from a telnet session.

May also be shown as 4000001300000000 or 0x4000001300000000

40000014-00000000 : The [arg1] on system [arg2] cleared by user [arg3].

This message is for the use case where a Management Controller Event Log on a system is cleared by a user.

May also be shown as 4000001400000000 or 0x4000001400000000

40000015-00000000 : Management Controller [arg1] reset was initiated by user [arg2].

This message is for the use case where a Management Controller reset is initiated by a user.

May also be shown as 4000001500000000 or 0x4000001500000000

40000016-00000000 : ENET[[arg1]] DHCP-HSTN=[arg2], DN=[arg3], IP@=[arg4], SN=[arg5], GW@=[arg6], DNS1@=[arg7] .

This message is for the use case where a Management Controller IP address and configuration has been assigned by the DHCP server.

May also be shown as 4000001600000000 or 0x4000001600000000

40000017-00000000 : ENET[[arg1]] IP-Cfg:HstName=[arg2], IP@=[arg3] ,NetMsk=[arg4], GW@=[arg5] .

This message is for the use case where a Management Controller IP address and configuration has been assigned statically using user data.

May also be shown as 4000001700000000 or 0x4000001700000000

40000018-00000000 : LAN: Ethernet[[arg1]] interface is no longer active.

This message is for the use case where a Management Controller ethernet interface is no longer active.

May also be shown as 4000001800000000 or 0x4000001800000000

40000019-00000000 : LAN: Ethernet[[arg1]] interface is now active.

This message is for the use case where a Management Controller ethernet interface is now active.

May also be shown as 4000001900000000 or 0x4000001900000000

4000001a-00000000 : DHCP setting changed to [arg1] by user [arg2].

This message is for the use case where a user changes the DHCP setting.

May also be shown as 4000001a00000000 or 0x4000001a00000000

4000001b-00000000 : Management Controller [arg1]: Configuration restored from a file by user [arg2].

This message is for the use case where a user restores a Management Controller configuration from a file.

May also be shown as 4000001b00000000 or 0x4000001b00000000

4000001c-00000000 : Watchdog [arg1] Screen Capture Occurred .

This message is for the use case where an operating system error has occurred and the screen was captured.

May also be shown as 4000001c00000000 or 0x4000001c00000000

4000001d-00000000 : Watchdog [arg1] Failed to Capture Screen.

This message is for the use case where an operating system error has occurred and the screen capture failed.

May also be shown as 4000001d00000000 or 0x4000001d00000000

4000001e-00000000 : Running the backup Management Controller [arg1] main application.

This message is for the use case where a Management Controller has resorted to running the backup main application.

May also be shown as 4000001e00000000 or 0x4000001e00000000

4000001f-00000000 : Please ensure that the Management Controller [arg1] is flashed with the correct firmware. The Management Controller is unable to match its firmware to the server.

This message is for the use case where a Management Controller firmware version does not match the server.

May also be shown as 4000001f00000000 or 0x4000001f00000000

40000020-00000000 : Management Controller [arg1] Reset was caused by restoring default values.

This message is for the use case where a Management Controller has been reset due to a user restoring the configuration to default values.

May also be shown as 4000002000000000 or 0x4000002000000000

40000021-00000000 : Management Controller [arg1] clock has been set from NTP server [arg2].

This message is for the use case where a Management Controller clock has been set from the Network Time Protocol server.

May also be shown as 4000002100000000 or 0x4000002100000000

40000022-00000000 : SSL data in the Management Controller [arg1] configuruation data is invalid. Clearing configuration data region and disabling SSL.

This message is for the use case where a Management Controller has detected invalid SSL data in the configuration data and is clearing the configuration data region and disabling the SSL.

May also be shown as 4000002200000000 or 0x4000002200000000

40000023-00000000 : Flash of [arg1] from [arg2] succeeded for user [arg3] .

This message is for the use case where a user has successfully flashed the firmware component (MC Main Application, MC Boot ROM, BIOS, Diagnostics, System Power Backplane, Remote Expansion Enclosure Power Backplane, Integrated System Management Processor, or Remote Expansion Enclosure Processor) from the interface and IP address ( %d.

May also be shown as 4000002300000000 or 0x4000002300000000

40000024-00000000 : Flash of [arg1] from [arg2] failed for user [arg3].

This message is for the use case where a user has not flashed the firmware component from the interface and IP address due to a failure.

May also be shown as 4000002400000000 or 0x4000002400000000

40000025-00000000 : The [arg1] on system [arg2] is 75% full.

This message is for the use case where a Management Controller Event Log on a system is 75% full.

May also be shown as 4000002500000000 or 0x4000002500000000

40000026-00000000 : The [arg1] on system [arg2] is 100% full.

This message is for the use case where a Management Controller Event Log on a system is 100% full.

May also be shown as 4000002600000000 or 0x4000002600000000

40000027-00000000 : Platform Watchdog Timer expired for [arg1].

This message is for the use case when an implementation has detected a Platform Watchdog Timer Expired

May also be shown as 4000002700000000 or 0x4000002700000000

40000028-00000000 : Management Controller Test Alert Generated by [arg1].

This message is for the use case where a user has generated a Test Alert.

May also be shown as 4000002800000000 or 0x4000002800000000

40000029-00000000 : Security: Userid: [arg1] had [arg2] login failures from an SSH client at IP address [arg3].

This message is for the use case where a user has failed to log in to a Management Controller from SSH.

May also be shown as 4000002900000000 or 0x4000002900000000

4000002a-00000000 : [arg1] firmware mismatch internal to system [arg2]. Please attempt to flash the [arg3] firmware.

This message is for the use case where a specific type of firmware mismatch has been detected.

May also be shown as 4000002a00000000 or 0x4000002a00000000

4000002b-00000000 : Domain name set to [arg1].

Domain name set by user

May also be shown as 4000002b00000000 or 0x4000002b00000000

4000002c-00000000 : Domain Source changed to [arg1] by user [arg2].

Domain source changed by user

May also be shown as 4000002c00000000 or 0x4000002c00000000

4000002d-00000000 : DDNS setting changed to [arg1] by user [arg2].

DDNS setting changed by user

May also be shown as 4000002d00000000 or 0x4000002d00000000

4000002e-00000000 : DDNS registration successful. The domain name is [arg1].

DDNS registation and values

May also be shown as 4000002e00000000 or 0x4000002e00000000

4000002f-00000000 : IPv6 enabled by user [arg1] .

IPv6 protocol is enabled by user

May also be shown as 4000002f00000000 or 0x4000002f00000000

40000030-00000000 : IPv6 disabled by user [arg1] .

IPv6 protocol is disabled by user

May also be shown as 4000003000000000 or 0x4000003000000000

40000031-00000000 : IPv6 static IP configuration enabled by user [arg1].

IPv6 static address assignment method is enabled by user

May also be shown as 4000003100000000 or 0x4000003100000000

40000032-00000000 : IPv6 DHCP enabled by user [arg1].

IPv6 DHCP assignment method is enabled by user

May also be shown as 4000003200000000 or 0x4000003200000000

40000033-00000000 : IPv6 stateless auto-configuration enabled by user [arg1].

IPv6 statless auto-assignment method is enabled by user

May also be shown as 4000003300000000 or 0x4000003300000000

40000034-00000000 : IPv6 static IP configuration disabled by user [arg1].

IPv6 static assignment method is disabled by user

May also be shown as 4000003400000000 or 0x4000003400000000

40000035-00000000 : IPv6 DHCP disabled by user [arg1].

IPv6 DHCP assignment method is disabled by user

May also be shown as 4000003500000000 or 0x4000003500000000

40000036-00000000 : IPv6 stateless auto-configuration disabled by user [arg1].

IPv6 statless auto-assignment method is disabled by user

May also be shown as 4000003600000000 or 0x4000003600000000

40000037-00000000 : ENET[[arg1]] IPv6-LinkLocal:HstName=[arg2], IP@=[arg3] ,Pref=[arg4] .

IPv6 Link Local address is active

May also be shown as 4000003700000000 or 0x4000003700000000

40000038-00000000 : ENET[[arg1]] IPv6-Static:HstName=[arg2], IP@=[arg3] ,Pref=[arg4], GW@=[arg5] .

IPv6 Static address is active

May also be shown as 4000003800000000 or 0x4000003800000000

40000039-00000000 : ENET[[arg1]] DHCPv6-HSTN=[arg2], DN=[arg3], IP@=[arg4], Pref=[arg5].

IPv6 DHCP-assigned address is active

May also be shown as 4000003900000000 or 0x4000003900000000

4000003a-00000000 : IPv6 static address of network interface modified from [arg1] to [arg2] by user [arg3].

A user modifies the IPv6 static address of a Management Controller

May also be shown as 4000003a00000000 or 0x4000003a00000000

4000003b-00000000 : DHCPv6 failure, no IP address assigned.

S DHCP6 server fails to assign an IP address to a Management Controller.

May also be shown as 4000003b00000000 or 0x4000003b00000000

4000003c-00000000 : Platform Watchdog Timer expired for [arg1].

An implementation has detected an OS Loader Watchdog Timer Expired

May also be shown as 4000003c00000000 or 0x4000003c00000000

4000003d-00000000 : Telnet port number changed from [arg1] to [arg2] by user [arg3].

A user has modified the telnet port number

May also be shown as 4000003d00000000 or 0x4000003d00000000

4000003e-00000000 : SSH port number changed from [arg1] to [arg2] by user [arg3].

A user has modified the SSH port number

May also be shown as 4000003e00000000 or 0x4000003e00000000

4000003f-00000000 : Web-HTTP port number changed from [arg1] to [arg2] by user [arg3].

A user has modified the Web HTTP port number

May also be shown as 4000003f00000000 or 0x4000003f00000000

40000040-00000000 : Web-HTTPS port number changed from [arg1] to [arg2] by user [arg3].

A user has modified the Web HTTPS port number

May also be shown as 4000004000000000 or 0x4000004000000000

40000041-00000000 : CIM/XML HTTP port number changed from [arg1] to [arg2] by user [arg3].

A user has modified the CIM HTTP port number

May also be shown as 4000004100000000 or 0x4000004100000000

40000042-00000000 : CIM/XML HTTPS port number changed from [arg1] to [arg2] by user [arg3].

A user has modified the CIM HTTPS port number

May also be shown as 4000004200000000 or 0x4000004200000000

40000043-00000000 : SNMP Agent port number changed from [arg1] to [arg2] by user [arg3].

A user has modified the SNMP Agent port number

May also be shown as 4000004300000000 or 0x4000004300000000

40000044-00000000 : SNMP Traps port number changed from [arg1] to [arg2] by user [arg3].

A user has modified the SNMP Traps port number

May also be shown as 4000004400000000 or 0x4000004400000000

40000045-00000000 : Syslog port number changed from [arg1] to [arg2] by user [arg3].

A user has modified the Syslog receiver port number

May also be shown as 4000004500000000 or 0x4000004500000000

40000046-00000000 : Remote Presence port number changed from [arg1] to [arg2] by user [arg3].

A user has modified the Remote Presence port number

May also be shown as 4000004600000000 or 0x4000004600000000

40000047-00000000 : LED [arg1] state changed to [arg2] by [arg3].

A user has modified the state of an LED

May also be shown as 4000004700000000 or 0x4000004700000000

40000048-00000000 : Inventory data changed for device [arg1], new device data hash=[arg2], new master data hash=[arg3] .

Something has caused the physical inventory to change

May also be shown as 4000004800000000 or 0x4000004800000000

40000049-00000000 : SNMP [arg1] enabled by user [arg2] .

A user enabled SNMPv1 or SNMPv3 or Traps

May also be shown as 4000004900000000 or 0x4000004900000000

4000004a-00000000 : SNMP [arg1] disabled by user [arg2] .

A user disabled SNMPv1 or SNMPv3 or Traps

May also be shown as 4000004a00000000 or 0x4000004a00000000

4000004b-00000000 : SNMPv1 [arg1] set by user [arg2]: Name=[arg3], AccessType=[arg4], Address=[arg5], .

A user changed the SNMP community string

May also be shown as 4000004b00000000 or 0x4000004b00000000

4000004c-00000000 : LDAP Server configuration set by user [arg1]: SelectionMethod=[arg2], DomainName=[arg3], Server1=[arg4], Server2=[arg5], Server3=[arg6], Server4=[arg7].

A user changed the LDAP server configuration

May also be shown as 4000004c00000000 or 0x4000004c00000000

4000004d-00000000 : LDAP set by user [arg1]: RootDN=[arg2], UIDSearchAttribute=[arg3], BindingMethod=[arg4], EnhancedRBS=[arg5], TargetName=[arg6], GroupFilter=[arg7], GroupAttribute=[arg8], LoginAttribute=[arg9].

A user configured an LDAP Miscellaneous setting

May also be shown as 4000004d00000000 or 0x4000004d00000000

4000004e-00000000 : Serial Redirection set by user [arg1]: Mode=[arg2], BaudRate=[arg3], StopBits=[arg4], Parity=[arg5], SessionTerminateSequence=[arg6].

A user configured the Serial Port mode

May also be shown as 4000004e00000000 or 0x4000004e00000000

4000004f-00000000 : Date and Time set by user [arg1]: Date=[arg2], Time-[arg3], DST Auto-adjust=[arg4], Timezone=[arg5].

A user configured the Date and Time settings

May also be shown as 4000004f00000000 or 0x4000004f00000000

40000050-00000000 : Server General Settings set by user [arg1]: Name=[arg2], Contact=[arg3], Location=[arg4], Room=[arg5], RackID=[arg6], Rack U-position=[arg7].

A user configured the Location setting

May also be shown as 4000005000000000 or 0x4000005000000000

40000051-00000000 : Server Power Off Delay set to [arg1] by user [arg2].

A user configured the Server Power Off Delay

May also be shown as 4000005100000000 or 0x4000005100000000

40000052-00000000 : Server [arg1] scheduled for [arg2] at [arg3] by user [arg4].

A user configured a Server Power action at a specific time

May also be shown as 4000005200000000 or 0x4000005200000000

40000053-00000000 : Server [arg1] scheduled for every [arg2] at [arg3] by user [arg4].

A user configured a recurring Server Power Action

May also be shown as 4000005300000000 or 0x4000005300000000

40000054-00000000 : Server [arg1] [arg2] cleared by user [arg3].

A user cleared a Server Power Action.

May also be shown as 4000005400000000 or 0x4000005400000000

40000055-00000000 : Synchronize time setting by user [arg1]: Mode=[arg2], NTPServerHost=[arg3]:[arg4],NTPUpdateFrequency=[arg5].

A user configured the Date and Time synchronize settings

May also be shown as 4000005500000000 or 0x4000005500000000

40000056-00000000 : SMTP Server set by user [arg1] to [arg2]:[arg3].

A user configured the SMTP server

May also be shown as 4000005600000000 or 0x4000005600000000

40000057-00000000 : Telnet [arg1] by user [arg2].

A user enables or disables Telnet services

May also be shown as 4000005700000000 or 0x4000005700000000

40000058-00000000 : DNS servers set by user [arg1]: UseAdditionalServers=[arg2], PreferredDNStype=[arg3], IPv4Server1=[arg4], IPv4Server2=[arg5], IPv4Server3=[arg6], IPv6Server1=[arg7], IPv6Server2=[arg8], IPv6Server3=[arg9].

A user configures the DNS servers

May also be shown as 4000005800000000 or 0x4000005800000000

40000059-00000000 : LAN over USB [arg1] by user [arg2].

A user configured USB-LAN

May also be shown as 4000005900000000 or 0x4000005900000000

4000005a-00000000 : LAN over USB Port Forwarding set by user [arg1]: ExternalPort=[arg2], USB-LAN port=[arg3].

A user configured USB-LAN port forwarding

May also be shown as 4000005a00000000 or 0x4000005a00000000

4000005b-00000000 : Secure Web services (HTTPS) [arg1] by user [arg2].

A user enables or disables Secure web services

May also be shown as 4000005b00000000 or 0x4000005b00000000

4000005c-00000000 : Secure CIM/XML(HTTPS) [arg1] by user [arg2].

A user enables or disables Secure CIM/XML services

May also be shown as 4000005c00000000 or 0x4000005c00000000

4000005d-00000000 : Secure LDAP [arg1] by user [arg2].

A user enables or disables Secure LDAP services

May also be shown as 4000005d00000000 or 0x4000005d00000000

4000005e-00000000 : SSH [arg1] by user [arg2].

A user enables or disables SSH services

May also be shown as 4000005e00000000 or 0x4000005e00000000

4000005f-00000000 : Server timeouts set by user [arg1]: EnableOSWatchdog=[arg2], OSWatchdogTimout=[arg3], EnableLoaderWatchdog=[arg4], LoaderTimeout=[arg5].

A user configures Server Timeouts

May also be shown as 4000005f00000000 or 0x4000005f00000000

40000060-00000000 : License key for [arg1] added by user [arg2].

A user installs License Key

May also be shown as 4000006000000000 or 0x4000006000000000

40000061-00000000 : License key for [arg1] removed by user [arg2].

A user removes a License Key

May also be shown as 4000006100000000 or 0x4000006100000000

40000062-00000000 : Global Login General Settings set by user [arg1]: AuthenticationMethod=[arg2], LockoutPeriod=[arg3], SessionTimeout=[arg4].

A user changes the Global Login General Settings

May also be shown as 4000006200000000 or 0x4000006200000000

40000063-00000000 : Global Login Account Security set by user [arg1]: PasswordRequired=[arg2], PasswordExpirationPeriod=[arg3], MinimumPasswordReuseCycle=[arg4], MinimumPasswordLength=[arg5], MinimumPasswordChangeInterval=[arg6], MaxmumLoginFailures=[arg7], LockoutAfterMaxFailures=[arg8], MinimumDifferentCharacters=[arg9], DefaultIDExpired=[arg10], ChangePasswordFirstAccess=[arg11].

A user changes the Global Login Account Security Settings to Legacy

May also be shown as 4000006300000000 or 0x4000006300000000

40000064-00000000 : User [arg1] created.

A user account was created

May also be shown as 4000006400000000 or 0x4000006400000000

40000065-00000000 : User [arg1] removed..

A user account was deleted

May also be shown as 4000006500000000 or 0x4000006500000000

40000066-00000000 : User [arg1] password modified.

A user account was changed

May also be shown as 4000006600000000 or 0x4000006600000000

40000067-00000000 : User [arg1] role set to [arg2].

A user account role assigned

May also be shown as 4000006700000000 or 0x4000006700000000

40000068-00000000 : User [arg1] custom privileges set: [arg2].

User account priveleges assigned

May also be shown as 4000006800000000 or 0x4000006800000000

40000069-00000000 : User [arg1] for SNMPv3 set: AuthenticationProtocol=[arg2], PrivacyProtocol=[arg3], AccessType=[arg4], HostforTraps=[arg5].

User account SNMPv3 settings changed

May also be shown as 4000006900000000 or 0x4000006900000000

4000006a-00000000 : SSH Client key added for user [arg1].

User locally defined an SSH Client key

May also be shown as 4000006a00000000 or 0x4000006a00000000

4000006b-00000000 : SSH Client key imported for user [arg1] from [arg2].

User imported an SSH Client key

May also be shown as 4000006b00000000 or 0x4000006b00000000

4000006c-00000000 : SSH Client key removed from user [arg1].

User removed an SSH Client key

May also be shown as 4000006c00000000 or 0x4000006c00000000

4000006d-00000000 : Management Controller [arg1]: Configuration saved to a file by user [arg2].

A user saves a Management Controller configuration to a file.

May also be shown as 4000006d00000000 or 0x4000006d00000000

4000006e-00000000 : Alert Configuration Global Event Notification set by user [arg1]: RetryLimit=[arg2], RetryInterval=[arg3], EntryInterval=[arg4].

A user changes the Global Event Notification settings.

May also be shown as 4000006e00000000 or 0x4000006e00000000

4000006f-00000000 : Alert Recipient Number [arg1] updated: Name=[arg2], DeliveryMethod=[arg3], Address=[arg4], IncludeLog=[arg5], Enabled=[arg6], EnabledAlerts=[arg7], AllowedFilters=[arg8].

A user adds or updates an Alert Recipient

May also be shown as 4000006f00000000 or 0x4000006f00000000

40000070-00000000 : SNMP Traps enabled by user [arg1]: EnabledAlerts=[arg2], AllowedFilters=[arg3] .

A user enabled the SNMP Traps configuration

May also be shown as 4000007000000000 or 0x4000007000000000

40000071-00000000 : The power cap value changed from [arg1] watts to [arg2] watts by user [arg3].

Power Cap values changed by user

May also be shown as 4000007100000000 or 0x4000007100000000

40000072-00000000 : The minimum power cap value changed from [arg1] watts to [arg2] watts.

Minimum Power Cap value changed

May also be shown as 4000007200000000 or 0x4000007200000000

40000073-00000000 : The maximum power cap value changed from [arg1] watts to [arg2] watts.

Maximum Power Cap value changed

May also be shown as 4000007300000000 or 0x4000007300000000

40000074-00000000 : The soft minimum power cap value changed from [arg1] watts to [arg2] watts.

Soft Minimum Power Cap value changed

May also be shown as 4000007400000000 or 0x4000007400000000

40000075-00000000 : The measured power value exceeded the power cap value.

Power exceeded cap

May also be shown as 4000007500000000 or 0x4000007500000000

40000076-00000000 : The new minimum power cap value exceeded the power cap value.

Minimum Power Cap exceeds Power Cap

May also be shown as 4000007600000000 or 0x4000007600000000

40000077-00000000 : Power capping was activated by user [arg1].

Power capping activated by user

May also be shown as 4000007700000000 or 0x4000007700000000

40000078-00000000 : Power capping was deactivated by user [arg1].

Power capping deactivated by user

May also be shown as 4000007800000000 or 0x4000007800000000

40000079-00000000 : Static Power Savings mode has been turned on by user [arg1].

Static Power Savings mode turned on by user

May also be shown as 4000007900000000 or 0x4000007900000000

4000007a-00000000 : Static Power Savings mode has been turned off by user [arg1].

Static Power Savings mode turned off by user

May also be shown as 4000007a00000000 or 0x4000007a00000000

4000007b-00000000 : Dynamic Power Savings mode has been turned on by user [arg1].

Dynamic Power Savings mode turned on by user

May also be shown as 4000007b00000000 or 0x4000007b00000000

4000007c-00000000 : Dynamic Power Savings mode has been turned off by user [arg1].

Dynamic Power Savings mode turned off by user

May also be shown as 4000007c00000000 or 0x4000007c00000000

4000007d-00000000 : Power cap and external throttling occurred.

Power cap and external throttling occurred

May also be shown as 4000007d00000000 or 0x4000007d00000000

4000007e-00000000 : External throttling occurred .

External throttling occurred

May also be shown as 4000007e00000000 or 0x4000007e00000000

4000007f-00000000 : Power cap throttling occurred.

Power cap throttling occurrred

May also be shown as 4000007f00000000 or 0x4000007f00000000

40000080-00000000 : Remote Control session started by user [arg1] in [arg2] mode.

Remote Control session started

May also be shown as 4000008000000000 or 0x4000008000000000

40000081-00000000 : PXE boot requested by user [arg1].

PXE boot requested

May also be shown as 4000008100000000 or 0x4000008100000000

40000082-00000000 : The measured power value has returned below the power cap value.

Power exceeded cap recovered

May also be shown as 4000008200000000 or 0x4000008200000000

40000083-00000000 : The new minimum power cap value has returned below the power cap value.

Minimum Power Cap exceeds Power Cap recovered

May also be shown as 4000008300000000 or 0x4000008300000000

40000084-00000000 : IMM firmware mismatch between nodes [arg1] and [arg2]. Please attempt to flash the IMM firmware to the same level on all nodes.

A mismatch of IMM firmware has been detected between nodes

May also be shown as 4000008400000000 or 0x4000008400000000

40000085-00000000 : FPGA firmware mismatch between nodes [arg1] and [arg2]. Please attempt to flash the FPGA firmware to the same level on all nodes.

A mismatch of FPGA firmware has been detected between nodes

May also be shown as 4000008500000000 or 0x4000008500000000

40000086-00000000 : Test Call Home Generated by user [arg1].

Test Call Home generated by user.

May also be shown as 4000008600000000 or 0x4000008600000000

40000087-00000000 : Manual Call Home by user [arg1]: [arg2].

Manual Call Home by user.

May also be shown as 4000008700000000 or 0x4000008700000000

40000088-00000000 : Management Controller [arg1]: Configuration restoration from a file by user [arg2] completed.

This message is for the use case where a user restores a Management Controller configuration from a file and it completes.

May also be shown as 4000008800000000 or 0x4000008800000000

40000089-00000000 : Management Controller [arg1]: Configuration restoration from a file by user [arg2] failed to complete.

This message is for the use case where a user restores a Management Controller configuration from a file and the restoration fails to complete.

May also be shown as 4000008900000000 or 0x4000008900000000

4000008a-00000000 : Management Controller [arg1]: Configuration restoration from a file by user [arg2] failed to start.

This message is for the use case where a user restores a Management Controller configuration from a file and the restoration fails to start.

May also be shown as 4000008a00000000 or 0x4000008a00000000

4000008b-00000000 : One or more of the Storage Management IP addresses has changed.

This message is for the use case where an IP address for the Storage Management has changed

May also be shown as 4000008b00000000 or 0x4000008b00000000

80010002-0701ffff : Numeric sensor [NumericSensorElementName] going low (lower non-critical) has asserted. (CMOS Battery)

This message is for the use case when an implementation has detected a Lower Non-critical sensor going low has asserted.

May also be shown as 800100020701ffff or 0x800100020701ffff

80010202-0701ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (CMOS Battery)

This message is for the use case when an implementation has detected a Lower Critical sensor going low has asserted.

May also be shown as 800102020701ffff or 0x800102020701ffff

80010204-1d01ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 1Aa Tach)

This message is for the use case when an implementation has detected a Lower Critical sensor going low has asserted.

May also be shown as 800102041d01ffff or 0x800102041d01ffff

80010204-1d02ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 1Ab Tach)

This message is for the use case when an implementation has detected a Lower Critical sensor going low has asserted.

May also be shown as 800102041d02ffff or 0x800102041d02ffff

80010204-1d03ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 2Aa Tach)

This message is for the use case when an implementation has detected a Lower Critical sensor going low has asserted.

May also be shown as 800102041d03ffff or 0x800102041d03ffff

80010204-1d04ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 2Ab Tach)

This message is for the use case when an implementation has detected a Lower Critical sensor going low has asserted.

May also be shown as 800102041d04ffff or 0x800102041d04ffff

80010204-1d05ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 3Aa Tach)

This message is for the use case when an implementation has detected a Lower Critical sensor going low has asserted.

May also be shown as 800102041d05ffff or 0x800102041d05ffff

80010204-1d06ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 3Ab Tach)

This message is for the use case when an implementation has detected a Lower Critical sensor going low has asserted.

May also be shown as 800102041d06ffff or 0x800102041d06ffff

80010204-1d07ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 4 Tach)

This message is for the use case when an implementation has detected a Lower Critical sensor going low has asserted.

May also be shown as 800102041d07ffff or 0x800102041d07ffff

80010204-1d08ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 5 Tach)

This message is for the use case when an implementation has detected a Lower Critical sensor going low has asserted.

May also be shown as 800102041d08ffff or 0x800102041d08ffff

80010701-0702ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (FHHL Amb Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107010702ffff or 0x800107010702ffff

80010701-0703ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (LowProfile Amb)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107010703ffff or 0x800107010703ffff

80010701-0704ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (RAID Amb Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107010704ffff or 0x800107010704ffff

80010701-0c01ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (Ambient Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107010c01ffff or 0x800107010c01ffff

80010701-1401ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (CPU1 VR Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107011401ffff or 0x800107011401ffff

80010701-1402ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (CPU2 VR Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107011402ffff or 0x800107011402ffff

80010701-1403ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (DIMM AB VR Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107011403ffff or 0x800107011403ffff

80010701-1404ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (DIMM CD VR Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107011404ffff or 0x800107011404ffff

80010701-1405ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (DIMM EF VR Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107011405ffff or 0x800107011405ffff

80010701-1406ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (DIMM GH VR Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107011406ffff or 0x800107011406ffff

80010701-2c01ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (Mezz Card Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107012c01ffff or 0x800107012c01ffff

80010701-2d01ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted. (PCH Temp)

This message is for the use case when an implementation has detected an Upper Non-critical sensor going high has asserted.

May also be shown as 800107012d01ffff or 0x800107012d01ffff

80010901-0702ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (FHHL Amb Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109010702ffff or 0x800109010702ffff

80010901-0703ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (LowProfile Amb)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109010703ffff or 0x800109010703ffff

80010901-0704ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (RAID Amb Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109010704ffff or 0x800109010704ffff

80010901-0c01ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (Ambient Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109010c01ffff or 0x800109010c01ffff

80010901-1401ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (CPU1 VR Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109011401ffff or 0x800109011401ffff

80010901-1402ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (CPU2 VR Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109011402ffff or 0x800109011402ffff

80010901-1403ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (DIMM AB VR Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109011403ffff or 0x800109011403ffff

80010901-1404ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (DIMM CD VR Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109011404ffff or 0x800109011404ffff

80010901-1405ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (DIMM EF VR Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109011405ffff or 0x800109011405ffff

80010901-1406ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (DIMM GH VR Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109011406ffff or 0x800109011406ffff

80010901-2c01ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (Mezz Card Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109012c01ffff or 0x800109012c01ffff

80010901-2d01ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (PCH Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109012d01ffff or 0x800109012d01ffff

80010902-0701ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted.

This message is for the use case when an implementation has detected an Upper Critical sensor going high has asserted.

May also be shown as 800109020701ffff or 0x800109020701ffff

80010b01-0702ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (FHHL Amb Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b010702ffff or 0x80010b010702ffff

80010b01-0703ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (LowProfile Amb)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b010703ffff or 0x80010b010703ffff

80010b01-0704ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (RAID Amb Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b010704ffff or 0x80010b010704ffff

80010b01-0c01ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (Ambient Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b010c01ffff or 0x80010b010c01ffff

80010b01-1401ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (CPU1 VR Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b011401ffff or 0x80010b011401ffff

80010b01-1402ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (CPU2 VR Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b011402ffff or 0x80010b011402ffff

80010b01-1403ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (DIMM AB VR Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b011403ffff or 0x80010b011403ffff

80010b01-1404ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (DIMM CD VR Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b011404ffff or 0x80010b011404ffff

80010b01-1405ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (DIMM EF VR Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b011405ffff or 0x80010b011405ffff

80010b01-1406ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (DIMM GH VR Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b011406ffff or 0x80010b011406ffff

80010b01-2c01ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (Mezz Card Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b012c01ffff or 0x80010b012c01ffff

80010b01-2d01ffff : Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has asserted. (PCH Temp)

This message is for the use case when an implementation has detected an Upper Non-recoverable sensor going high has asserted.

May also be shown as 80010b012d01ffff or 0x80010b012d01ffff

80030006-2101ffff : Sensor [SensorElementName] has deasserted. (Sig Verify Fail)

This message is for the use case when an implementation has detected a Sensor has deasserted.

May also be shown as 800300062101ffff or 0x800300062101ffff

80030012-2301ffff : Sensor [SensorElementName] has deasserted. (OS RealTime Mod)

This message is for the use case when an implementation has detected a Sensor has deasserted.

May also be shown as 800300122301ffff or 0x800300122301ffff

80030108-0a01ffff : Sensor [SensorElementName] has asserted. (PS Heavy Load)

This message is for the use case when an implementation has detected a Sensor has asserted.

May also be shown as 800301080a01ffff or 0x800301080a01ffff

8007010f-2201ffff : Sensor [SensorElementName] has transitioned from normal to non-critical state. (GPT Status)

This message is for the use case when an implementation has detected a Sensor transitioned to non-critical from normal.

May also be shown as 8007010f2201ffff or 0x8007010f2201ffff

8007010f-2582ffff : Sensor [SensorElementName] has transitioned from normal to non-critical state. (No PCI I/O Space)

This message is for the use case when an implementation has detected a Sensor transitioned to non-critical from normal.

May also be shown as 8007010f2582ffff or 0x8007010f2582ffff

80070114-2201ffff : Sensor [SensorElementName] has transitioned from normal to non-critical state. (TPM Phy Pres Set)

This message is for the use case when an implementation has detected a Sensor transitioned to non-critical from normal.

May also be shown as 800701142201ffff or 0x800701142201ffff

80070201-0301ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (CPU 1 OverTemp)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 800702010301ffff or 0x800702010301ffff

80070201-0302ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (CPU 2 OverTemp)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 800702010302ffff or 0x800702010302ffff

80070202-0701ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (SysBrd Vol Fault)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 800702020701ffff or 0x800702020701ffff

80070208-0a01ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (PS 1 Fan Fault)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 800702080a01ffff or 0x800702080a01ffff

80070208-0a02ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (PS 2 Fan Fault)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 800702080a02ffff or 0x800702080a02ffff

8007020f-2201ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (TXT ACM Module)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 8007020f2201ffff or 0x8007020f2201ffff

8007020f-2582ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (No PCI I/O Space)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 8007020f2582ffff or 0x8007020f2582ffff

80070214-2201ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (TPM Lock)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 800702142201ffff or 0x800702142201ffff

80070219-0701ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (SysBrd Fault)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 800702190701ffff or 0x800702190701ffff

8007021b-0301ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (CPU 1 QPILinkErr)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 8007021b0301ffff or 0x8007021b0301ffff

8007021b-0302ffff : Sensor [SensorElementName] has transitioned to critical from a less severe state. (CPU 2 QPILinkErr)

This message is for the use case when an implementation has detected a Sensor transitioned to critical from less severe.

May also be shown as 8007021b0302ffff or 0x8007021b0302ffff

80070301-0301ffff : Sensor [SensorElementName] has transitioned to non-recoverable from a less severe state. (CPU 1 OverTemp)

This message is for the use case when an implementation has detected a Sensor transitioned to non-recoverable from less severe.

May also be shown as 800703010301ffff or 0x800703010301ffff

80070301-0302ffff : Sensor [SensorElementName] has transitioned to non-recoverable from a less severe state. (CPU 2 OverTemp)

This message is for the use case when an implementation has detected a Sensor transitioned to non-recoverable from less severe.

May also be shown as 800703010302ffff or 0x800703010302ffff

80070608-0a01ffff : Sensor [SensorElementName] has transitioned to non-recoverable.

This message is for the use case when an implementation has detected a Sensor transitioned to non-recoverable.

May also be shown as 800706080a01ffff or 0x800706080a01ffff

80070608-0a02ffff : Sensor [SensorElementName] has transitioned to non-recoverable.

This message is for the use case when an implementation has detected a Sensor transitioned to non-recoverable.

May also be shown as 800706080a02ffff or 0x800706080a02ffff

80070614-2201ffff : Sensor [SensorElementName] has transitioned to non-recoverable. (TPM Phy Pres Set)

This message is for the use case when an implementation has detected a Sensor transitioned to non-recoverable.

May also be shown as 800706142201ffff or 0x800706142201ffff

8008010f-2101ffff : Device [LogicalDeviceElementName] has been added. (Phy Presence Jmp)

This message is for the use case when an implementation has detected a Device was inserted.

May also be shown as 8008010f2101ffff or 0x8008010f2101ffff

80080128-2101ffff : Device [LogicalDeviceElementName] has been added. (Low Security Jmp)

This message is for the use case when an implementation has detected a Device was inserted.

May also be shown as 800801282101ffff or 0x800801282101ffff

800b0008-1301ffff : Redundancy [RedundancySetElementName] has been restored. (Power Unit)

This message is for the use case when an implementation has detected Redundancy was Restored.

May also be shown as 800b00081301ffff or 0x800b00081301ffff

800b0108-1301ffff : Redundancy Lost for [RedundancySetElementName] has asserted. (Power Unit)

This message is for the use case when Redundancy Lost has asserted.

May also be shown as 800b01081301ffff or 0x800b01081301ffff

800b010a-1e81ffff : Redundancy Lost for [RedundancySetElementName] has asserted. (Cooling Zone 1)

This message is for the use case when Redundancy Lost has asserted.

May also be shown as 800b010a1e81ffff or 0x800b010a1e81ffff

800b010a-1e82ffff : Redundancy Lost for [RedundancySetElementName] has asserted. (Cooling Zone 2)

This message is for the use case when Redundancy Lost has asserted.

May also be shown as 800b010a1e82ffff or 0x800b010a1e82ffff

800b010a-1e83ffff : Redundancy Lost for [RedundancySetElementName] has asserted. (Cooling Zone 3)

This message is for the use case when Redundancy Lost has asserted.

May also be shown as 800b010a1e83ffff or 0x800b010a1e83ffff

800b010a-1e84ffff : Redundancy Lost for [RedundancySetElementName] has asserted. (Cooling Zone 4)

This message is for the use case when Redundancy Lost has asserted.

May also be shown as 800b010a1e84ffff or 0x800b010a1e84ffff

800b010a-1e85ffff : Redundancy Lost for [RedundancySetElementName] has asserted. (Cooling Zone 5)

This message is for the use case when Redundancy Lost has asserted.

May also be shown as 800b010a1e85ffff or 0x800b010a1e85ffff

800b010c-2581ffff : Redundancy Lost for [RedundancySetElementName] has asserted. (Backup Memory)

This message is for the use case when Redundancy Lost has asserted.

May also be shown as 800b010c2581ffff or 0x800b010c2581ffff

800b0309-1301ffff : Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for [RedundancySetElementName] has asserted. (Power Resource)

This message is for the use case when a Redundancy Set has transitioned from Redundancy Degraded or Fully Redundant to Non-redundant:Sufficient.

May also be shown as 800b03091301ffff or 0x800b03091301ffff

800b030c-2581ffff : Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for [RedundancySetElementName] has asserted. (Backup Memory)

This message is for the use case when a Redundancy Set has transitioned from Redundancy Degraded or Fully Redundant to Non-redundant:Sufficient.

May also be shown as 800b030c2581ffff or 0x800b030c2581ffff

800b0509-1301ffff : Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted. (Power Resource)

This message is for the use case when a Redundancy Set has transitioned to Non-redundant:Insufficient Resources.

May also be shown as 800b05091301ffff or 0x800b05091301ffff

800b050a-1e81ffff : Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted. (Cooling Zone 1)

This message is for the use case when a Redundancy Set has transitioned to Non-redundant:Insufficient Resources.

May also be shown as 800b050a1e81ffff or 0x800b050a1e81ffff

800b050a-1e82ffff : Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted. (Cooling Zone 2)

This message is for the use case when a Redundancy Set has transitioned to Non-redundant:Insufficient Resources.

May also be shown as 800b050a1e82ffff or 0x800b050a1e82ffff

800b050a-1e83ffff : Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted. (Cooling Zone 3)

This message is for the use case when a Redundancy Set has transitioned to Non-redundant:Insufficient Resources.

May also be shown as 800b050a1e83ffff or 0x800b050a1e83ffff

800b050a-1e84ffff : Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted. (Cooling Zone 4)

This message is for the use case when a Redundancy Set has transitioned to Non-redundant:Insufficient Resources.

May also be shown as 800b050a1e84ffff or 0x800b050a1e84ffff

800b050a-1e85ffff : Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted. (Cooling Zone 5)

This message is for the use case when a Redundancy Set has transitioned to Non-redundant:Insufficient Resources.

May also be shown as 800b050a1e85ffff or 0x800b050a1e85ffff

800b050c-2581ffff : Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted. (Backup Memory)

This message is for the use case when a Redundancy Set has transitioned to Non-redundant:Insufficient Resources.

May also be shown as 800b050c2581ffff or 0x800b050c2581ffff

806f0007-0301ffff : [ProcessorElementName] has Failed with IERR. (CPU 1)

This message is for the use case when an implementation has detected a Processor Failed - IERR Condition.

May also be shown as 806f00070301ffff or 0x806f00070301ffff

806f0007-0302ffff : [ProcessorElementName] has Failed with IERR. (CPU 2)

This message is for the use case when an implementation has detected a Processor Failed - IERR Condition.

May also be shown as 806f00070302ffff or 0x806f00070302ffff

806f0008-0a01ffff : [PowerSupplyElementName] has been added to container [PhysicalPackageElementName]. (Power Supply 1)

This message is for the use case when an implementation has detected a Power Supply has been added.

May also be shown as 806f00080a01ffff or 0x806f00080a01ffff

806f0008-0a02ffff : [PowerSupplyElementName] has been added to container [PhysicalPackageElementName]. (Power Supply 2)

This message is for the use case when an implementation has detected a Power Supply has been added.

May also be shown as 806f00080a02ffff or 0x806f00080a02ffff

806f0009-1301ffff : [PowerSupplyElementName] has been turned off. (Host Power)

This message is for the use case when an implementation has detected a Power Unit that has been Disabled.

May also be shown as 806f00091301ffff or 0x806f00091301ffff

806f000d-0400ffff : The Drive [StorageVolumeElementName] has been added. (Drive 0)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d0400ffff or 0x806f000d0400ffff

806f000d-0401ffff : The Drive [StorageVolumeElementName] has been added. (Drive 1)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d0401ffff or 0x806f000d0401ffff

806f000d-0402ffff : The Drive [StorageVolumeElementName] has been added. (Drive 2)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d0402ffff or 0x806f000d0402ffff

806f000d-0403ffff : The Drive [StorageVolumeElementName] has been added. (Drive 3)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d0403ffff or 0x806f000d0403ffff

806f000d-0404ffff : The Drive [StorageVolumeElementName] has been added. (Drive 4)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d0404ffff or 0x806f000d0404ffff

806f000d-0405ffff : The Drive [StorageVolumeElementName] has been added. (Drive 5)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d0405ffff or 0x806f000d0405ffff

806f000d-0406ffff : The Drive [StorageVolumeElementName] has been added. (Drive 6)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d0406ffff or 0x806f000d0406ffff

806f000d-0407ffff : The Drive [StorageVolumeElementName] has been added. (Drive 7)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d0407ffff or 0x806f000d0407ffff

806f000d-0408ffff : The Drive [StorageVolumeElementName] has been added. (Drive 8)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d0408ffff or 0x806f000d0408ffff

806f000d-0409ffff : The Drive [StorageVolumeElementName] has been added. (Drive 9)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d0409ffff or 0x806f000d0409ffff

806f000d-040affff : The Drive [StorageVolumeElementName] has been added. (Drive 10)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d040affff or 0x806f000d040affff

806f000d-040bffff : The Drive [StorageVolumeElementName] has been added. (Drive 11)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d040bffff or 0x806f000d040bffff

806f000d-040cffff : The Drive [StorageVolumeElementName] has been added. (Drive 12)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d040cffff or 0x806f000d040cffff

806f000d-040dffff : The Drive [StorageVolumeElementName] has been added. (Drive 13)

This message is for the use case when an implementation has detected a Drive has been Added.

May also be shown as 806f000d040dffff or 0x806f000d040dffff

806f000f-220101ff : The System [ComputerSystemElementName] has detected no memory in the system. (ABR Status)

This message is for the use case when an implementation has detected that memory was detected in the system.

May also be shown as 806f000f220101ff or 0x806f000f220101ff

806f000f-220102ff : Subsystem [MemoryElementName] has insufficient memory for operation. (ABR Status)

This message is for the use case when an implementation has detected that the usable Memory is insufficient for operation.

May also be shown as 806f000f220102ff or 0x806f000f220102ff

806f000f-220103ff : The System [ComputerSystemElementName] encountered firmware error - unrecoverable boot device failure. (ABR Status)

This message is for the use case when an implementation has detected that System Firmware Error Unrecoverable boot device failure has occurred.

May also be shown as 806f000f220103ff or 0x806f000f220103ff

806f000f-220104ff : The System [ComputerSystemElementName]has encountered a motherboard failure. (ABR Status)

This message is for the use case when an implementation has detected that a fatal motherboard failure in the system.

May also be shown as 806f000f220104ff or 0x806f000f220104ff

806f000f-220107ff : The System [ComputerSystemElementName] encountered firmware error - unrecoverable keyboard failure. (ABR Status)

This message is for the use case when an implementation has detected that System Firmware Error Unrecoverable Keyboard failure has occurred.

May also be shown as 806f000f220107ff or 0x806f000f220107ff

806f000f-22010aff : The System [ComputerSystemElementName] encountered firmware error - no video device detected. (ABR Status)

This message is for the use case when an implementation has detected that System Firmware Error No video device detected has occurred.

May also be shown as 806f000f22010aff or 0x806f000f22010aff

806f000f-22010bff : Firmware BIOS (ROM) corruption was detected on system [ComputerSystemElementName] during POST. (ABR Status)

Firmware BIOS (ROM) corruption was detected on the system during POST.

May also be shown as 806f000f22010bff or 0x806f000f22010bff

806f000f-22010cff : CPU voltage mismatch detected on [ProcessorElementName]. (ABR Status)

This message is for the use case when an implementation has detected a CPU voltage mismatch with the socket voltage.

May also be shown as 806f000f22010cff or 0x806f000f22010cff

806f000f-2201ffff : The System [ComputerSystemElementName] encountered a POST Error. (ABR Status)

This message is for the use case when an implementation has detected a Post Error.

May also be shown as 806f000f2201ffff or 0x806f000f2201ffff

806f0013-1701ffff : A diagnostic interrupt has occurred on system [ComputerSystemElementName]. (NMI State)

This message is for the use case when an implementation has detected a Front Panel NMI / Diagnostic Interrupt.

May also be shown as 806f00131701ffff or 0x806f00131701ffff

806f001e-2201ffff : No bootable media available for system [ComputerSystemElementName]. (No Boot Device)

This message is for the use case when an implementation has detected a System with No Bootable Media.

May also be shown as 806f001e2201ffff or 0x806f001e2201ffff

806f0021-2201ffff : Fault in slot [PhysicalConnectorSystemElementName] on system [ComputerSystemElementName]. (No Op ROM Space)

This message is for the use case when an implementation has detected a Fault in a slot.

May also be shown as 806f00212201ffff or 0x806f00212201ffff

806f0021-2582ffff : Fault in slot [PhysicalConnectorSystemElementName] on system [ComputerSystemElementName]. (All PCI Error)

This message is for the use case when an implementation has detected a Fault in a slot.

May also be shown as 806f00212582ffff or 0x806f00212582ffff

806f0021-3001ffff : Fault in slot [PhysicalConnectorSystemElementName] on system [ComputerSystemElementName]. (PCI 1)

This message is for the use case when an implementation has detected a Fault in a slot.

May also be shown as 806f00213001ffff or 0x806f00213001ffff

806f0023-2101ffff : Watchdog Timer expired for [WatchdogElementName]. (IPMI Watchdog)

This message is for the use case when an implementation has detected a Watchdog Timer Expired.

May also be shown as 806f00232101ffff or 0x806f00232101ffff

806f0028-2101ffff : Sensor [SensorElementName] is unavailable or degraded on management system [ComputerSystemElementName]. (TPM Cmd Failures)

This message is for the use case when an implementation has detected a Sensor is Unavailable or degraded.

May also be shown as 806f00282101ffff or 0x806f00282101ffff

806f0107-0301ffff : An Over-Temperature Condition has been detected on [ProcessorElementName]. (CPU 1)

This message is for the use case when an implementation has detected an Over-Temperature Condition Detected for Processor.

May also be shown as 806f01070301ffff or 0x806f01070301ffff

806f0107-0302ffff : An Over-Temperature Condition has been detected on [ProcessorElementName]. (CPU 2)

This message is for the use case when an implementation has detected an Over-Temperature Condition Detected for Processor.

May also be shown as 806f01070302ffff or 0x806f01070302ffff

806f0108-0a01ffff : [PowerSupplyElementName] has Failed. (Power Supply 1)

This message is for the use case when an implementation has detected a Power Supply has failed.

May also be shown as 806f01080a01ffff or 0x806f01080a01ffff

806f0108-0a02ffff : [PowerSupplyElementName] has Failed. (Power Supply 2)

This message is for the use case when an implementation has detected a Power Supply has failed.

May also be shown as 806f01080a02ffff or 0x806f01080a02ffff

806f0109-1301ffff : [PowerSupplyElementName] has been Power Cycled. (Host Power)

This message is for the use case when an implementation has detected a Power Unit that has been power cycled.

May also be shown as 806f01091301ffff or 0x806f01091301ffff

806f010c-2001ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 1)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2001ffff or 0x806f010c2001ffff

806f010c-2002ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 2)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2002ffff or 0x806f010c2002ffff

806f010c-2003ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 3)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2003ffff or 0x806f010c2003ffff

806f010c-2004ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 4)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2004ffff or 0x806f010c2004ffff

806f010c-2005ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 5)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2005ffff or 0x806f010c2005ffff

806f010c-2006ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 6)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2006ffff or 0x806f010c2006ffff

806f010c-2007ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 7)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2007ffff or 0x806f010c2007ffff

806f010c-2008ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 8)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2008ffff or 0x806f010c2008ffff

806f010c-2009ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 9)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2009ffff or 0x806f010c2009ffff

806f010c-200affff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 10)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c200affff or 0x806f010c200affff

806f010c-200bffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 11)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c200bffff or 0x806f010c200bffff

806f010c-200cffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 12)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c200cffff or 0x806f010c200cffff

806f010c-200dffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 13)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c200dffff or 0x806f010c200dffff

806f010c-200effff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 14)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c200effff or 0x806f010c200effff

806f010c-200fffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 15)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c200fffff or 0x806f010c200fffff

806f010c-2010ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 16)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2010ffff or 0x806f010c2010ffff

806f010c-2581ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (All DIMMS)

This message is for the use case when an implementation has detected a Memory uncorrectable error.

May also be shown as 806f010c2581ffff or 0x806f010c2581ffff

806f010d-0400ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 0)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d0400ffff or 0x806f010d0400ffff

806f010d-0401ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 1)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d0401ffff or 0x806f010d0401ffff

806f010d-0402ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 2)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d0402ffff or 0x806f010d0402ffff

806f010d-0403ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 3)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d0403ffff or 0x806f010d0403ffff

806f010d-0404ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 4)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d0404ffff or 0x806f010d0404ffff

806f010d-0405ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 5)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d0405ffff or 0x806f010d0405ffff

806f010d-0406ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 6)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d0406ffff or 0x806f010d0406ffff

806f010d-0407ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 7)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d0407ffff or 0x806f010d0407ffff

806f010d-0408ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 8)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d0408ffff or 0x806f010d0408ffff

806f010d-0409ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 9)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d0409ffff or 0x806f010d0409ffff

806f010d-040affff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 10)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d040affff or 0x806f010d040affff

806f010d-040bffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 11)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d040bffff or 0x806f010d040bffff

806f010d-040cffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 12)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d040cffff or 0x806f010d040cffff

806f010d-040dffff : The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 13)

This message is for the use case when an implementation has detected a Drive was Disabled due to fault.

May also be shown as 806f010d040dffff or 0x806f010d040dffff

806f010f-2201ffff : The System [ComputerSystemElementName] encountered a firmware hang. (Firmware Error)

This message is for the use case when an implementation has detected a System Firmware Hang.

May also be shown as 806f010f2201ffff or 0x806f010f2201ffff

806f0113-0301ffff : A bus timeout has occurred on system [ComputerSystemElementName]. (CPU 1 PECI)

This message is for the use case when an implementation has detected a Bus Timeout.

May also be shown as 806f01130301ffff or 0x806f01130301ffff

806f0113-0302ffff : A bus timeout has occurred on system [ComputerSystemElementName]. (CPU 2 PECI)

This message is for the use case when an implementation has detected a Bus Timeout.

May also be shown as 806f01130302ffff or 0x806f01130302ffff

806f011b-0701ffff : The connector [PhysicalConnectorElementName] has encountered a configuration error. (Front USB)

This message is for the use case when an implementation has detected an Interconnect Configuration Error.

May also be shown as 806f011b0701ffff or 0x806f011b0701ffff

806f0123-2101ffff : Reboot of system [ComputerSystemElementName] initiated by [WatchdogElementName]. (IPMI Watchdog)

This message is for the use case when an implementation has detected a Reboot by a Watchdog occurred.

May also be shown as 806f01232101ffff or 0x806f01232101ffff

806f0125-0b01ffff : [ManagedElementName] detected as absent. (PCI Riser 1)

This message is for the use case when an implementation has detected a Managed Element is Absent.

May also be shown as 806f01250b01ffff or 0x806f01250b01ffff

806f0125-0b02ffff : [ManagedElementName] detected as absent. (PCI Riser 2)

This message is for the use case when an implementation has detected a Managed Element is Absent.

May also be shown as 806f01250b02ffff or 0x806f01250b02ffff

806f0125-0c01ffff : [ManagedElementName] detected as absent. (Front Panel)

This message is for the use case when an implementation has detected a Managed Element is Absent.

May also be shown as 806f01250c01ffff or 0x806f01250c01ffff

806f0125-2c01ffff : [ManagedElementName] detected as absent. (Mezz Card)

This message is for the use case when an implementation has detected a Managed Element is Absent.

May also be shown as 806f01252c01ffff or 0x806f01252c01ffff

806f0207-0301ffff : [ProcessorElementName] has Failed with FRB1/BIST condition. (CPU 1)

This message is for the use case when an implementation has detected a Processor Failed - FRB1/BIST condition.

May also be shown as 806f02070301ffff or 0x806f02070301ffff

806f0207-0302ffff : [ProcessorElementName] has Failed with FRB1/BIST condition. (CPU 2)

This message is for the use case when an implementation has detected a Processor Failed - FRB1/BIST condition.

May also be shown as 806f02070302ffff or 0x806f02070302ffff

806f0207-2584ffff : [ProcessorElementName] has Failed with FRB1/BIST condition. (All CPUs)

This message is for the use case when an implementation has detected a Processor Failed - FRB1/BIST condition.

May also be shown as 806f02072584ffff or 0x806f02072584ffff

806f020d-0400ffff : Failure Predicted on drive [StorageVolumeElementName] for array [ComputerSystemElementName]. (Drive 0)

This message is for the use case when an implementation has detected an Array Failure is Predicted.

May also be shown as 806f020d0400ffff or 0x806f020d0400ffff

806f020d-0401ffff : Failure Predicted on drive [StorageVolumeElementName] for array [ComputerSystemElementName]. (Drive 1)

This message is for the use case when an implementation has detected an Array Failure is Predicted.

May also be shown as 806f020d0401ffff or 0x806f020d0401ffff

806f020d-0402ffff : Failure Predicted on drive [StorageVolumeElementName] for array [ComputerSystemElementName]. (Drive 2)

This message is for the use case when an implementation has detected an Array Failure is Predicted.

May also be shown as 806f020d0402ffff or 0x806f020d0402ffff

806f020d-0403ffff : Failure Predicted on drive [StorageVolumeElementName] for array [ComputerSystemElementName]. (Drive 3)

This message is for the use case when an implementation has detected an Array Failure is Predicted.

May also be shown as 806f020d0403ffff or 0x806f020d0403ffff