Chapter 4. Continuous availability and manageability 115
Figure 4-3 IVM Manage Serviceable Events window
The first occurrence of each failure type is recorded in Manage Serviceable Events. This task
filters and maintains a history of duplicate reports from other logical partitions or the service
processor. It looks at all active service event requests, analyzes the failure to ascertain the
root cause and, if enabled, initiates a call for service. This methodology ensures that all
platform errors are reported through at least one functional path, resulting in a single
notification for a single problem.
Extended error data (EED)
EED is additional data that is collected either automatically at the time of a failure or manually
at a later time. The data collected is dependent on the invocation method but includes
information such as firmware levels, operating system levels, additional fault isolation register
values, recoverable error threshold register values, system status, and any other pertinent
data. The data is formatted and prepared for transmission back to IBM to assist with
preparing a service action plan for the service representative or for additional analysis.
System dump handling
In certain circumstances, an error might require a dump to be automatically or manually
created. A manual dump creation can be done through the AMM Blade Service Data window.
A service processor, platform, or partition dump can be initiated for a blade from the AMM.
Service processor and platform dumps can be managed and downloaded to a workstation
from the IVM Mange Dumps window, under the Service Focal Point.
Note: Because errors are sent to both the Service Focal Point on the blade and to the
BladeCenter AMM, duplicate call home requests can be generated.
To Next Page
Loading...
Need help?
General