160
IBM
Eserver
p5 590 and 595 System Handbook
Errors that are recoverable but should be recorded for threshold monitoring.
These events do not require immediate service but should be logged and
tracked to look for, and effectively respond to, future problems.
Fatal system errors (initiate server reboot and IPL, error analysis, and call
home if enabled).
Recoverable errors that require service either because an error threshold has
been reached or a component has been taken off-line (even if a redundant
component has been used for sparing).
When a recoverable and serviceable error (the third type above) is encountered,
the service processor notifies the POWER Hypervisor which places an entry into
the operating system error log. The operating system log contains all recoverable
error logs. These logs represent either recoverable platform errors or errors
detected and logged by I/O device drivers. Operating System Error Log Analysis
(ELA) routines monitor this log, identify serviceable events (ignoring
information-only log entries), and copy them to a diagnostic event log. At this
point the operating system will send an error notification to a client designated
user (by default, the root user). This action also invokes the Service Agent
application which initiates appropriate system serviceability actions.
On servers that do not include an HMC, the Service Agent notifies the system
operator of the error condition and, if enabled, also initiates a call for service.
The Service call can be directed to the IBM support organization, or to a client
identified pager or server identified and set-up to receive service information.
Note that an HMC is required on a p5-590 and p5-595 server.
On servers equipped with an HMC (including the p5-595 and p5-590 servers),
Service Agent forwards the results of the diagnostic error log analysis to the
Service Focal Point application running on the HMC. The Service Focal Point
consolidates and reports errors to IBM or a user designated system or pager.
In either case, failure information including:
The source of error
The part numbers of the components needing repair
The location of those components
Any available extended error data
The failure information is sent back to IBM service for parts ordering and
additional diagnosis if required. This detailed error information enables IBM
service representatives to bring along probable replacement hardware
components when a service call is placed, minimizing system repair time.
In a multi-system configuration, any HMC-attached IBM
Sserver
p5 server can
be configured to forward call home requests to a central Service Agent Gateway
Содержание p5 590
Страница 2: ......
Страница 16: ...xiv IBM Eserver p5 590 and 595 System Handbook...
Страница 38: ...16 IBM Eserver p5 590 and 595 System Handbook...
Страница 106: ...84 IBM Eserver p5 590 and 595 System Handbook...
Страница 132: ...110 IBM Eserver p5 590 and 595 System Handbook...
Страница 160: ...138 IBM Eserver p5 590 and 595 System Handbook...
Страница 215: ...Chapter 7 Service processor 193 Figure 7 21 Current boot sequence menu default boot list...
Страница 216: ...194 IBM Eserver p5 590 and 595 System Handbook...
Страница 258: ...236 IBM Eserver p5 590 and 595 System Handbook Figure 8 34 Inventory Scout Figure 8 35 Select server to get VPD data...
Страница 264: ...242 IBM Eserver p5 590 and 595 System Handbook Figure 8 40 Detail view of a service event...
Страница 280: ...258 IBM Eserver p5 590 and 595 System Handbook...
Страница 285: ...Appendix C Installation planning 263 Figure C 1 Search for planning Figure C 2 Select 9119 590 and 9119 595...
Страница 286: ...264 IBM Eserver p5 590 and 595 System Handbook Figure C 3 Planning information...
Страница 298: ...276 IBM Eserver p5 590 and 595 System Handbook...
Страница 302: ...280 IBM Eserver p5 590 and 595 System Handbook...
Страница 312: ...290 IBM Eserver p5 590 and 595 System Handbook...
Страница 313: ...0 5 spine 0 475 0 875 250 459 pages IBM Eserver p5 590 and 595 System Handbook...
Страница 314: ......
Страница 315: ......