Xcat; Xcatdebug; Resolving Xcat Configuration Issues - IBM Power Systems 775 Manual

4.1 xCAT

This section provides examples of common problems that might be encountered in an
environment that uses xCAT. Information about how to resolve those issues on an IBM Power
System 775 High Performance Computing (HPC) cluster also is presented. References to
tools, websites, and documentation also are included.
For more information about general troubleshooting methods, see this website:
http://sourceforge.net/apps/mediawiki/xcat/index.php?title=Debugging_xCAT_Probl
ems

4.1.1 xcatdebug

The xcatdebug script is used to trace the xcatd daemon, as shown in Example 4-1. The script
runs xcatd with the Perl Debug-Trace and outputs the data from the parameters in the xcatd
daemon subroutines that are specified in the input files in the
/opt/xcat/share/xcat/tools/tracelevel* files. (For more information, see the xcatdebug
man pages.)
The Perl Debug-Trace rpm is available in the latest xcat packages. More trace levels are
created based on the nature of the problem that is being debugged.
Example 4-1 run xcatd that uses the /opt/xcat/share/xcat/tools/tracelevel0 file
stop xcatd
xcatdebug 0

4.1.2 Resolving xCAT configuration issues

xCAT commands do not run if xCAT or DB2 is down. Complete the following steps to resolve
problems that are found:
1. Verify that xcatd is running and that DB2 is accessible, as shown in Example 4-2.
Example 4-2 Verify xcatd and DB
# lssrc -s xcatd
Subsystem
xcatd
# lsxcatd -d
cfgloc=DB2:xcatdb|xcatdb
dbengine=DB2
dbinstance=xcatdb
dbname=xcatdb
dbloc=/db2database/db2
# tabdump site
#key,value,comments,disable
"blademaxp","64",,
"fsptimeout","0",,
"installdir","/install",,
"master","192.168.0.103",,
"nameservers","192.168.0.103",,
244
IBM Power Systems 775 for AIX and Linux HPC Solution
Group PID
18677838
Status
active