IBM Support

Basic Data Collection for Debugging VIOS SSP Cluster

Question & Answer


Question

Following is the basic testcase needed for initial investigation of VIOS SSP Cluster issues. It involves gathering a snap from the Primary Database Node (DBN) AND all other nodes that are failing in the cluster. Note: More data may be requested later on depending on the nature of the problem or the failing component. This applies to VIOS 2.2.x

Answer

1. Gather VIOS Snap

a. Determine which VIOS is the DBN node. This can be run from any node that is online in the cluster.
$ cluster -list (to list the cluster name)
$ cluster -status -clustername <clustername> -verbose | grep -p DBN

b. Gather VIOS snap from DBN node as padmin
$ snap
Upon completion, this will create /home/padmin/snap.pax.Z. If this file exists prior to running snap command, it will automatically be deleted and recreated.
(Repeat for any other failing VIOS node(s).

For VIOS snap issues, see Troubleshooting VIOS Snap Command Issues.

c. Rename the compressed file to reflect your Support Case ID and denote the DBN node using the following naming convention:
$ mv snap.pax.Z TS<xxxxxxxxx>.<VIOhostname>.DBNnode.snap.pax.Z
where TS<xxxxxxxxx> is your Support Case ID
If you are submitting snaps for more than one VIOS, rename the files using the following naming convention:
<VIOhostname>.DBNnode.snap.pax.Z for the DBN node
<VIOhostname>.snap.pax.Z for any other failing nodes


Problem Getting a Full Snap

If there is a problem capturing snap or using SSP script, as a very last resource, we may ask to manually attempt to gather svCollect, caa, poolfs, and ctsnap data on that VIOS. As padmin, run:

$ snap svCollect (creates /home/padmin/snap.pax.Z)
Rename to <VIOhostname>.svCollect.snap.pax.Z

$ snap caa (creates /home/padmin/snap.pax.Z)
Rename to <VIOhostname>.caa.snap.pax.Z

$ snap poolfs (creates /home/padmin/snap.pax.Z)
Rename to <VIOhostname>.poolfs.snap.pax.Z

To gather ctsnap
$ oem_setup_env
# ctsnap -x runrpttr (creates /tmp/ctsupt/ctsnap.<VIOhostname>.*.tar.gz)
Rename to <VIOhostname>.ctsnap.tar.gz

If unable to manually gather the above, gather output from the following commands from each VIOS node in the cluster, as padmin:

$ oem_setup_env
# script -a /tmp/<VIOS_hostname>.out
# uname -uML
# su - padmin
$ ioslevel
$ df -g
$ cluster -list
$ cluster -status -clustername <cluster name>
$ lscluster -m
$ lscluster -c
$ lscluster -i
$ lscluster -d
$ lscluster -s
$ lssrc -ls vio_daemon
$ exit (padmin)
$ exit (script)


2. Packaging Testcase When Submitting Multiple VIOS Snaps or Files

ftp all files to an AIX host to package them into a single pax file using your IBM Service Request as part of the file naming convention.  Example:
In AIX host, as root, run:
# mkdir /tmp/sspdata (ftp the files to this directory)
# cd /tmp/sspdata
# ls -la (ensure all expected files are listed)
# pax -wf TS<xxxxxxxxx>.pax ./*   (This packages all files into a single .pax file.  This is the file you want to submit.)

3. Where to Submit Testcase

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSMHJ","label":"PowerVM Virtual I\/O Server"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"}],"Version":"VIOS 2.2","Edition":"Enterprise;Express;Standard","Line of Business":{"code":"","label":""}}]

Document Information

More support for:
PowerVM Virtual I/O Server

Software version:
VIOS 2.2

Operating system(s):
AIX

Document number:
678757

Modified date:
19 February 2022

UID

isg3T1020698