IBM Power Systems 775, Manual

Page: 315 / 358

Chapter 5. Maintenance and serviceability
301
The following tasks must be performed to recover from a problem:
򐂰 Determine the resource that failed.
򐂰
Determine whether the resource failed before.
򐂰 Determine the effect of the failure on which type of node (if any).
򐂰 Perform the appropriate recovery action according to the findings and the spare policy.
򐂰 Report the problem to IBM (serviceable events from the HMC must report automatically
via the electronic Service Agent).
򐂰 Gather data.
On the EMS Server, it is necessary to gather some data to check or analyze possible FIP
events. The xCAT script that is called
gatherfip is in /opt/xcat/sbin that collects
information about ISNM, SFP, and deconfigured resources. The generated .gz file is sent
to the IBM service team.
The console output is shown in Example 5-51.
Example 5-51 gatherfip command
# /opt/xcat/sbin/gatherfip
-----------------------------------------------------------------------------
10/07/2011 10:39 - Start gatherfip
10/07/2011 10:39 - gatherfip Version 1.0
10/07/2011 10:39 - xCAT Executive Management Server hostname is c250mgrs40-itso
10/07/2011 10:39 - Writing hardware service alerts in TEAL to
gatherfip.hardware.service.events
10/07/2011 10:39 - Writing ISNM Alerts in TEAL to gatherfip.ISNM.events
10/07/2011 10:39 - Writing deconfigred resource information to
gatherfip.guarded.resources
10/07/2011 10:39 - Writing ISNM Link Down information to
gatherfip.ISNM.links.down
10/07/2011 10:39 - Created tar file containing these /var/log files:
gatherfip.log gatherfip.hardware.service.events gatherfip.ISNM.events
gatherfip.guarded.resources gatherfip.ISNM.links.down
10/07/2011 10:39 - Created compressed tar file
/var/log/c250mgrs40-itso.gatherfip.20111007_1039.tar.gz
10/07/2011 10:39 - End gatherfip#
# (10:39:24) c250mgrs40-itso [AIX 7.1.0.0 powerpc] /opt/teal/bin
This data is used by IBM support to determine whether a hardware repair is necessary.
More data is gathered by the xCAT Administrator includes the output of the commands, as
shown in Table 5-2 on page 302.