A P P E N D I X B

System Events

Event Details

This appendix contains tables of details and troubleshooting suggestions for system events. The tables are organized in alphabetical order, by component and sub-type.

Note - You can view system events if you use the sp get events command, or if you open the System Events table in the SM Console. IPMI events usually provide information about sensors in the system. See the Systems Management Commands document for more information.

TABLE B-1 <comp id>, Voltage, Temp, or Fan:Sensor
In Field	Description
Component	<comp id>, Voltage, Temp, or Fan
Sub-type	Sensor:Voltage, Temp, or Fan
Severity	Critical, Warning, or Informational
Brief Description	Sensor threshold has been crossed.
Message	Sensor <sensor> reports <value> <type> [ [but should be [between A and B] \| [greater than B] \| [less than A] ] \| [and has returned to normal]
Detailed Description	The systems management software monitors a variety of sensors including voltage, temperature, fan speed, and so on. Sensors have thresholds that define normal, warning, and critical ranges. When a sensor reading moves among these ranges, a system event is generated and persisted.
Steps	Sensor thresholds should not be modified. If they have been modified, reset them to their default settings. For a temperature sensor, verify that the site air conditioning is working properly and that there is proper airflow into the system. Ensure that there is no buildup of dust on any of the system components (especially fans, heat sinks and vent holes). Ensure that the CPU heat sinks are properly attached (screws tightened to specification, levers locked in position). Ensure that there is sufficient thermal grease between the CPU and the heat sink. For a fan sensor, ensure that there is no dust buildup on the fan. Ensure that no foreign matter is blocking the fan blades. Ensure that the fan is operating; if it is not, replace the fan. Exchange the fan with a known good fan to determine if the problem persists. For a voltage problem, ensure that the A/C voltage is correct. Determine if there have been any recent A/C fluctuations (sags, surges, brownouts). Ensure that the VRM modules are seated properly. If the voltage is derived from a pluggable VRM module, exchange the module with a known good module to determine if the problem persists. A return to normal is possible if the problem corrects itself or if you hotswap a hotpluggable component (fan or power supply). If you reboot the SP, the error state is reset to informational, unless the problem recurs.

TABLE B-2 CPU Planar, Configuration
In Field	Description
Component	CPU planar
Sub-type	Configuration
Severity	Warning
Brief Description	Incompatible planar and cpuplanar have been detected.
Message	CPU Planar card is a different revision from main Planar card. This configuration may not operate properly and is unsupported.
Detailed Description	There are two revisions of the CPU card which are both physically and electrically compatible with each other. The system only supports connecting version 1 of the card to a version 1 planar and version 2 of the card to a version 2 planar. This warning indicates that you have mixed the versions. The system will operate, but certain features might not work properly (revision E cpus, DDR 400 memory).
Steps	Replace the CPU card with one of the proper version.

TABLE B-3 CPU <X>, Configuration
In Field	Description
Component	CPU <X>
Sub-type	Configuration
Severity	Warning
Brief Description	Unknown SPU model has been installed in system.
Message	CPU Family <x>, Model <y>, Stepping <z> is unknown, Thermal offset may lead to erroneous shutdowns.
Detailed Description	The SP does not support the specific revision of CPU you have installed in the system.
Steps	Verify that the CPU you have installed is of the correct type for this system and is not an engineering sample. Update the SP software (and BIOS software, if necessary) to the latest revision, and retry. If the problem persists, contact your sales representative for further assistance.

TABLE B-4 CPU <X>, Heartbeat
In Field	Description
Component	CPU<X>
Sub-type	Heartbeat
Severity	Critical, Information
Brief Description	Heartbeat stopped or resumed: platform OS has stopped running or platform POCI driver has stopped.
Message	CPU<x> [has not sent a heartbeat in the last minute] \| [has resumed sending heartbeats] \| [Platform no longer running OS]
Detailed Description	The platform side drivers have stopped or resumed sending heartbeat signals to the SP, or the platform OS has been shut down while heartbeats were lost. During normal operation, with the appropriate platform drivers installed, the platform sends a periodic heartbeat signal to the SP to indicate it is alive. If the heartbeat signal is lost for more than a minute, the SP will issue the warning message. When it resumes, or when the system reboots, the corresponding message is sent.
Steps	This is usually caused by platform OS shutdown that is initiated from the platform side, since the SP cannot detect this event. (The shutdown might stop the platform drivers before the SP is notified of this event.) It also can be caused by reinstalling or upgrading the platform drivers. Finally, it can be caused by the platform OS crashing or hanging. In this last case, the remedy is to reboot the system.

TABLE B-5 CPU <X>, MachineCheck
In Field	Description
Component	CPU<X>
Sub-type	MachineCheck
Severity	Critical, Warning, Information
Brief Description	Incompatible planar and cpuplanar have been detected.
Message	A platform CPU has issued a machine check.
Detailed Description	Machine Check error detected on cpu <CPU>. [Machine Check in Progress.] [Error IP Valid.] [Restart IP Valid.] Error detected in [Data Cache] \| [InstructionCache] \| [Bus Unit] \| [Load/Store unit] \| [North Bridge] \| [Invalid bank reached]. [Second error detected.] [Error not corrected] [Error reporting disabled.] [Misc. register contains more info.] [Error occurred at address <address>.] [Processor state may have been corrupted] [Correctable ECC error.] [Un-correctable ECC error.] [Detected on a scrub.] Raw data: <data>
Steps	See Machine Check Error.

TABLE B-6 CPU <X>, TempSensor
In Field	Description
Component	CPU<X>
Sub-type	TempSensor
Severity	Critical
Brief Description	CPU thermal trip has occurred.
Message	CPU thermal trip has occurred.
Detailed Description	A CPU has indicated a thermal trip event and the system has been shut down as a result.
Steps	This occurs when the temperature of a CPU reaches approximately 120C and is a fail-safe operation to help prevent damage to the processor. If this occurs, the only recourse is to A/C cycle the power to the system. See "Thermal Trip Events" on page 87.

TABLE B-7 CPU <X>DIMM<X>, MachineCheck
In Field	Description
Component	CPU<X>DIMM<X>
Sub-type	MachineCheck
Severity	Critical, Warning, Information
Brief Description	DIMM error has occurred.
Message	[A [fatal \| recoverable] machine check error occurred on cpu <cpu>: dimm <dimm>] \| [Correctable error rate exceeded, consider replacing the dimm.]
Detailed Description	For the recoverable error case, a DIMM module is experiencing a high rate of correctable errors. This is affecting system performance and reliability. For the fatal case, a DIMM module has experienced an uncorrectable error. Data has been lost.
Steps	In both cases, replace the DIMM with a known good DIMM and see if the problem persists. If it does, inspect the DIMM connector area for debris (dust, metal shavings, and so on) and clean the connector area with compressed air to remove all foreign matter. Remove and inspect other DIMMs that are connected to the same memory controller and their connector areas. Ensure that the DIMM edge connector is clean and free from corrosion. Use only qualified memory in the system. After cleaning the connector area, replace the DIMM.

TABLE B-8 Planar, Crowbar
In Field	Description
Component	Planar
Sub-type	Crowbar
Severity	Critical, Information
Brief Description	Crowbar; fatal error in the power supply or the VRM modules has occurred.
Message	Sensor <sensor> reports that [crowbar failure has been detected - attempting to power system off] \| [crowbar failure has been cleared].
Detailed Description	One of the VRM modules has indicated either an over-temperature condition, an over-current condition, or an inability to regulate voltage properly, or the condition has been cleared. This usually is an over-temperature error when the failure is detected.
Steps	See Thermal Trip Events.

TABLE B-9 Planar, Power
In Field	Description
Component	Planar
Sub-type	Power
Severity	Critical
Brief Description	Power supply fans have failed.
Message	Sensor <sensor> reports that the [fans have failed].
Detailed Description	The internal fans within a power supply have failed.
Steps	Replace the power supply.

TABLE B-10 Planar, Power
In Field	Description
Component	Planar
Sub-type	Power
Severity	Warning
Brief Description	Power supply AC has been unplugged.
Message	<power supply> does not appear to be connected to AC power
Detailed Description	The power supply is plugged into the system but is not providing power.
Steps	Ensure that the AC line cord is plugged in. Ensure that there is AC power to the outlet to which it is not connected. Exchange it with a known good power supply.

TABLE B-11 Planar, Power
In Field	Description
Component	Planar
Sub-type	Power
Severity	Information
Brief Description	Power supply has been restored.
Message	<power supply> has resumed normal operation
Detailed Description	A power supply which had previously failed or been unplugged is now available and working normally.
Steps	N/A

TABLE B-12 Planar, Power
In Field	Description
Component	Planar
Sub-type	Power
Severity	Information
Brief Description	Power supply has been installed.
Message	<power supply> installed
Detailed Description	A new power supply has been plugged into the system and identified.
Steps	N/A

TABLE B-13 Planar, Power
In Field	Description
Component	Planar
Sub-type	Power
Severity	Information
Brief Description	Power supply has been removed.
Message	<power supply> removed
Detailed Description	One of the power supplies no longer can be accessed. It is assumed that it has been removed.
Steps	N/A

TABLE B-14 Planar, Power
In Field	Description
Component	Planar
Sub-type	Power
Severity	Information
Brief Description	Power supply fans have recovered from a failure.
Message	Sensor <sensor> reports that the fans have resumed normal operation.
Detailed Description	The internal fans within a power supply have recovered from a failure and now are working normally.
Steps	N/A

TABLE B-15 Planar, Power
In Field	Description
Component	Planar
Sub-type	Power
Severity	Critical
Brief Description	Power supply failure has occurred.
Message	<power supply> has failed (or is not plugged in), now running in degraded condition
Detailed Description	A power supply has failed or has become unplugged.
Steps	Ensure that the AC line cord is plugged in. Ensure that there is AC power to the outlet to which it is not connected. Exchange it with a known good power supply.

TABLE B-16 Planar, PowerGood
In Field	Description
Component	Planar
Sub-type	PowerGood
Severity	Warning
Brief Description	Power-good failure has occurred.
Message	Power good failure detected - latched values are DDR: <x>, CPU, <X>, LTD: <x>, S0: <x>.
Detailed Description	The PRS chip has detected a failure in one of the power good signals and has shut down the system as a result. This usually occurs due to a bad voltage regulation module, due to a bad power supply, or due to an A/C sag or surge of sufficient duration. The DDR values indicate which DDR VRM caused the problem (numbered 3210 high bit to low in each nybble, both are associated with each VRM). CPU values indicate which CPU VRM caused the problem (high nybble indicates vrm module). The LDT values indicate which LDT regulator caused the problem. The S0 values indicate which of the miscellaneous regulators caused the problem (0x40 = A/C, 0x20 = Power Supply). Any failure indicated in the low nybble of the CPU value, any part of the LDT value, or bits 2-4 of the S0 value represents on-board regulators and are not replaceable.
Steps	If the failure indicates a pluggable module and is consistent, replace the module with a spare, if one is available. If the failure indicates a regulator on the planar and is consistent, the planar might require service. If the failure indicates a power supply or is inconsistent (moves from regulator to regulator), verify that the A/C power to the system is clean and of the proper voltage. If it is, ensure that both power supplies are installed, properly seated, plugged in, and functional (green LED is illuminated when platform power is on). If the problem persists, exchange the power supplies with spares, if they are available, one at a time.

TABLE B-17 Planar, TempSensor
In Field	Description
Component	Planar
Sub-type	TempSensor
Severity	Critical, Information
Brief Description	Power supply temperature is too high or has returned to normal.
Message	Sensor <sensor> reports that the [temperature has exceeded specification] \| [temperature has returned to normal].
Detailed Description	The power supply temperature is too high or has returned to normal.
Steps	See Thermal Trip Events.

TABLE B-18 Platform BIOS, BIOS
In Field	Description
Component	Platform BIOS
Sub-type	BIOS
Severity	Critical
Brief Description	BIOS error has occurred.
Message	Received [early] fatal error from BIOS: [Unable to do anything] \| [Fixed Disk Failure] \| [Shadow RAM Failed] \| [System RAM Failed] \| [Extended RAM Failed] \| [System Timer Error] \| [Real-Time Clock Error] \| [Date and Time Setting Error] \| [CPU ID Error] \| [DMA Test Failed] \| [Software NMI Failed] \| [Fail-Safe Timer NMI Failed] \| [Operating System not found] \| [Parity Error (Memory)] \| [Extended Memory Truncation] \| [Memory Mismatched] \| [Flash Image Validation Error] \| [Flash Process Failure] \| [Diagnostic Load Failure] \| [IP Failure] \| [Diag Failed Memtest] \| [Incorrect BIOS image file (wrong platform type?)], Post Code: <code>
Detailed Description
Steps	See BIOS Error or Warning Events.

TABLE B-19 Platform BIOS, BIOS
In Field	Description
Component	Platform BIOS
Sub-type	BIOS`
Severity	Warning
Brief Description	BIOS reported a DIMM fault.
Message	Dimm Fault: CPU <cpu>, Dimm <dimm>, [Fault Detected] \| [Paired with faulty Dimm] \| [Unknown]
Detailed Description	The platform bios has detected an error in the DIMMs during memory configuration and initialization. It might or might not be possible to isolate the fault to a specific DIMM. (Certain configurations of memory do not allow for fault isolation across the paired DIMMs of a single memory channel.)
Steps	Run the memory diagnostics tests and seeDIMM Faults.

TABLE B-20 Platform BIOS, BIOS
In Field	Description
Component	Platform BIOS
Sub-type	BIOS`
Severity	Warning
Brief Description	BIOS warning has occurred.
Message	Received warning from BIOS: [CMOS Battery Failure] \| [CMOS Invalid] \| [I20 Block Storage Device excluded from Boot Menu] \| [CMOS Checksum Failure] \| [CMOS Settings do not match hardware configuration] \| [Memory truncated to valid functional memory] \| [PCI-X Slot disabled for Golem Errata 56] \| [Last Good Config Checksum Invalid] \| [Last Good Config Invalid], Post Code: <code>
Detailed Description
Steps	See BIOS Error or Warning Events.

TABLE B-21 Service Processor, Configuration
In Field	Description
Component	Service Processor
Sub-type	Configuration
Severity	Warning
Brief Description	User keys directory creation error has occurred.
Message	Error creating users' authorized_keys directories. It is likely that the persistent filesystem is full.
Detailed Description	An error occurred while saving the user key directories to the persistent storage on the SP.
Steps	See Persistent Storage Issues.

TABLE B-22 Service Processor, Configuration
In Field	Description
Component	Service Processor
Sub-type	Configuration
Severity	Warning
Brief Description	Add Trusted Host error has occurred.
Message	Error persisting user configuration. It is likely that the persistent filesystem is full.
Detailed Description	An error occurred while saving the trusted host configuration to the persistent storage on the SP.
Steps	Persistent Storage Issues.

TABLE B-23 Service Processor, Configuration
In Field	Description
Component	Service Processor
Sub-type	Configuration
Severity	Warning
Brief Description	ADS keytab error has occurred.
Message	Error persisting user configuration. It is likely that the persistent filesystem is full.
Detailed Description	An error occurred while saving the NIS configuration to the persistent storage on the SP.
Steps	Persistent Storage Issues.

TABLE B-24 Service Processor, Configuration
In Field	Description
Component	Service Processor
Sub-type	Configuration
Severity	Warning
Brief Description	Delete Trusted Host error has occurred.
Message	Error persisting user configuration. It is likely that the persistent filesystem is full.
Detailed Description	An error occurred while saving the trusted host configuration to the persistent storage on the Service Processor.
Steps	See Persistent Storage Issues.

TABLE B-25 Service Processor, Configuration
In Field	Description
Component	Service Processor
Sub-type	Configuration
Severity	Warning
Brief Description	NIS config error has occurred.
Message	Error persisting user configuration. It is likely that the persistent filesystem is full.
Detailed Description	An error occurred while saving the NIS configuration to the persistent storage on the Service Processor.
Steps	See Persistent Storage Issues.

TABLE B-26 Service Processor, Configuration
In Field	Description
Component	Service Processor
Sub-type	Configuration
Severity	Warning
Brief Description	NIS Domain bind error has occurred.
Message	Unable to bind to NIS Domain <domain>, Server(s):<server(s)>
Detailed Description	The NIS configuration request could not be completed because of an error. Either the server list is invalid, the NIS server is non-responsive, or the domain is invalid.
Steps	Check all configuration parameters to ensure that they are correct and ensure that the NIS servers are functioning properly.

TABLE B-27 Service Processor, Configuration
In Field	Description
Component	Service Processor
Sub-type	Configuration
Severity	Warning
Brief Description	ADS Kerberos ticket cache generation error has occurred.
Message	Unable to generate Kerberos ticket cache with Active Directory Account:<account>, Domain:<domain>, Server(s):<server(s)>
Detailed Description	The ticket cache for the specified user, domain, and server(s) was not generated due to an error. Either the user account, domain, or server list is incorrect, or the servers are non-responsive.
Steps	Check that all configuration parameters are correct and that the Active Directory server(s) are functioning properly.

TABLE B-28 Service Processor, Configuration
In Field	Description
Component	Service Processor
Sub-type	Configuration
Severity	Warning
Brief Description	Invalid SSL certificate exists.
Message	User supplied SSL certificate appears invalid. Reverting to factory default SSL certificate.
Detailed Description	The user-supplied SSL certificate appears to be invalid. The Service Processor will use the factory default SSL certificate.
Steps	Double-check the validity of the user-supplied certificate and try to reinstall to the Service Processor.

TABLE B-29 Service Processor, Configuration
In Field	Description
Component	Service Processor
Sub-type	Configuration
Severity	Information
Brief Description	Service Processor IP reconfigure has occurred.
Message	SP <hostname> IP [is now set to <ip_addr>] \| [deconfigured].
Detailed Description	The IP address on the SP has been changed.
Steps	Verify that the new value is correct.

TABLE B-30 Service Processor, Configuration
In Field	Description
Component	Service Processor
Sub-type	Configuration
Severity	Information
Brief Description	Service Processor hostname has changed.
Message	SP hostname set to <hostname>, IP is [<ip_addr>] \| [not configured.]
Detailed Description	The hostname on the SP has been changed.
Steps	Verify that the new value is correct.

TABLE B-31 Service Processor, Initialization
In Field	Description
Component	Service Processor
Sub-type	Initialization
Severity	Warning
Brief Description	Event deserialization error has occurred.
Message	Error deserializing events.
Detailed Description	The Event Manager Event Data storage has been corrupted and some event data has been lost. This usually occurs if the event manager shuts down improperly (application failure) or if the service processor is rebooted at an unexpected time (PRS or user reset).
Steps	System was shut down improperly. Lost data cannot be recovered. To prevent this problem, ensure that the system is shut down properly.

TABLE B-32 Service Processor, PlatformStateChange
In Field	Description
Component	Service Processor
Sub-type	PlatformStateChange
Severity	Information
Brief Description	Platform state change has occurred.
Message	[The platform has been powered off] \| [The platform has been rebooted] \| [The platform BIOS update has completed successfully]
Detailed Description	This message indicates that one of the various platform state changes has occurred.
Steps	N/A

TABLE B-33 Service Processor, Reboot
In Field	Description
Component	Service Processor
Sub-type	Reboot
Severity	Critical
Brief Description	SP has been rebooted by PRS due to lost heartbeat or failure of SP to initialize.
Message	SP Rebooted by PRS - reason is [SP Failed to Initialize] \| [SP Heartbeat was lost] \| [SP Failed Init and HB].
Detailed Description	The SP failed to boot properly and was reset by the platform power sequencing chip. A failure to initialize indicates that the SP failed to boot far enough, fast enough to indicate to PRS that it had completed initialzation. A loss of heartbeat indicates that either the SP failed to complete the boot process, or hung during normal operation.
Steps	See DIMM Faults.

TABLE B-34 Service Processor, Reboot
In Field	Description
Component	Service Processor
Sub-type	Reboot
Severity	Critical
Brief Description	SP has been rebooted by PRS due to lost heartbeat or failure of SP to initialize.
Message	SP Rebooted by PRS - reason is [SP Failed to Initialize] \| [SP Heartbeat was lost] \| [SP Failed Init and HB].
Detailed Description	The SP failed to boot properly and was reset by the platform power sequencing chip. A failure to initialize indicates that the SP failed to boot far enough, fast enough to indicate to PRS that it had completed initialzation. A loss of heartbeat indicates that either the SP failed to complete the boot process, or hung during normal operation.
Steps	See DIMM Faults.

TABLE B-35 Service Processor, ResourceAllocation
In Field	Description
Component	Service Processor
Sub-type	ResourceAllocation
Severity	Warning
Brief Description	Event log has been purged to low threshold.
Message	System event capacity exceeded. <num> events purged [<num> critical, <num> warning, <num> informational], <num> historical records purged The maximum number of active events was reached and old events were dropped.
Detailed Description	The system purges itself of the history for an event and then any clearable events before it removes any non-clearable events. Either the system has been running for a long time and has accumulated a large number of events (reboot or power off notifications, and so on) or there is a problem with the system that is causing a number of events to occur over time.
Steps	If the system has accumulated only informational messages (that the platform state has changed, and so on), consider using an automatic script to periodically clear the logs, in order to avoid this message. If the system has accumulated other types of warning or critical messages, follow the troubleshooting steps for those messages, to clear the problems.

TABLE B-36 Service Processor, ResourceAllocation
In Field	Description
Component	Service Processor
Sub-type	ResourceAllocation
Severity	Critical
Brief Description	Portmap Daemon died; SP was rebooted by spasm.
Message	Rebooted SP because of failed application: portmap
Detailed Description	Portmap is a critical application on the SP. If it fails, the SP must shut down and restart. Portmap must be started before all other SP applications are started.
Steps	N/A

TABLE B-37 Service Processor, ResourceAllocation
In Field	Description
Component	Service Processor
Sub-type	ResourceAllocation
Severity	Warning
Brief Description	(IPMI) SDRR write error has occurred.
Message	Error writing to SDRR.
Detailed Description	An error occurred while writing the content of the SDRR to persistent storage. This usually results when persistent storage is full.
Steps	See Persistent Storage Issues.

TABLE B-38 Service Processor, ResourceError
In Field	Description
Component	Service Processor
Sub-type	ResourceError
Severity	Critical
Brief Description	Application failure after 3 or more restarts within 90 seconds.
Message	Application respawning too rapidly, aborted: <app>
Detailed Description	An application is not operating properly and is exiting shortly after being started. This is probably caused by an intermittent hardware problem on the Service Processor (for example, one of the sensor devices has gone into an incorrect state and is causing problems). This also can be caused by a bad SP software load or by misconfigured network or file system settings.
Steps	See DIMM Faults.

TABLE B-39 Service Processor, SoftwareUpdate
In Field	Description
Component	Service Processor
Sub-type	SoftwareUpdate
Severity	Information
Brief Description	BIOS update was successful.
Message	BIOS Flash update completed successfully.
Detailed Description	The BIOS flash image has been updated successfully.
Steps	To verify the update, reboot the system and check the version on the boot screen. Alternatively, run the inventory get software command on the Service Processor, after the reboot.

TABLE B-40 Service Processor, SoftwareUpdate
In Field	Description
Component	Service Processor
Sub-type	SoftwareUpdate
Severity	Information
Brief Description	Diagnostics software has been updated successfully.
Message	Diagnostics software has been updated.
Detailed Description	The SP-Based diagnostics tests are installed on a separate NSV server and accessed via each SP using a mount. This message indicates that the /diags symbolic link on the SP has been changed to point to a different location within the NSV, on the external mount.
Steps	If the "diags start" command will not execute, verify that the /diags symbolic link is pointing to the desired diagnostics folder on the external mount. See the Systems Management Guide for details about how to install and use the NSV.

TABLE B-41 Service Processor, SoftwareUpdate
In Field	Description
Component	Service Processor
Sub-type	SoftwareUpdate
Severity	Information
Brief Description	The Operator Panel PIC firmware has been updated.
Message	PIC firmware has been updated.
Detailed Description	Operator Panel PIC firmware update is done via a service-level utility. End users should not see this message.
Steps	Use inventory get software command to verify that the correct firmware version is now installed.

TABLE B-42 Service Processor, SoftwareUpdate
In Field	Description
Component	Service Processor
Sub-type	SoftwareUpdate
Severity	Information
Brief Description	Value-Add software has been updated successfully.
Message	SP Applications/Value-Add software has been updated.
Detailed Description	The SP firmware is flashed as two components, the Base (kernel and other software that rarely changes) and Value-Add (system management software that changes from release to release). This message indicates that both components have been updated (probably via the sp update flash applications command, the Operator Panel, or a platform-side application).
Steps	Use the inventory get software command to verify that the correct firmware version is now installed.

TABLE B-43 Service Processor, SoftwareUpdate
In Field	Description
Component	Service Processor
Sub-type	SoftwareUpdate
Severity	Information
Brief Description	Service Processor Base software has been updated successfully.
Message	SP Base and Value-Add software has been updated.
Detailed Description	The SP firmware is flashed as two components, the Base (kernel and other software that rarely changes) and Value-Add (system management software that changes from release to release). This message indicates that both components have been updated (probably via the 'sp update flash applications' command, the Operator Panel, or a platform-side application).
Steps	Use the inventory get software command to verify that the correct firmware version is now installed.

TABLE B-44 Service Processor, SoftwareUpdate
In Field	Description
Component	Service Processor
Sub-type	SoftwareUpdate
Severity	Information
Brief Description	Event log has been purged; first boot of SP firmware since update.
Message	SP firmware updated and event cache cleared
Detailed Description	Previous Event Log was purged when the first boot of the updated SP version 2.2 occurred. This is because the event format changed in version 2.2. Records with the previous format, even outstanding events known to the SP, are not migrated to the new event log, but are purged.
Steps	To avoid loss of outstanding event records when you update to SP 2.2, simply delay the reboot (when the update actually takes place) until you address the outstanding events.

TABLE B-45 TEST, TestEvent
In Field	Description
Component	TEST
Sub-type	TestEvent
Severity	Critical, Warning, Information
Brief Description	Testing configuration of <severity> event.
Message	Test events have been created.
Detailed Description	The three test events (critical, warning, informational) have been created. Use these to verify that system management clients (SNMP, IPMI, SMTP, custom) have been configured correctly and can receive events. If your management clients do not receive these events, verify their respective configurations.
Steps	See the Sun Fire V20z and Sun Fire V40z Servers--Server Management Guide for information about SNMP, IPMI, SMTP and scripting configuration.