IBM Support

VMRM Debug Data Collection including GUI Data Collection ; can be used for GDR

How To


Summary

Instructions for VMRM debug data gather.

Objective

Environment

This method is appropriate for:
IBM VM Recovery Manager DR for Power Systems (1.3, 1.4 - EOS), 1.5, 1.6, 1.7
IBM VM Recovery Manager HA for Power Systems (1.3, 1.4 - EOS), 1.5, 1.6, 1.7
IBM Geographically Dispersed Resiliency for Power Systems 1.1, 1.2 (Both are EOS)

Steps

Collect the following data needed to investigate the VMRM issue (by order of importance; steps 3 and 4 might not be needed):

1) On the KSYS LPAR:

Remove old data (old VMRM data is not completely cleaned up by "snap -r"). 

# snap -r

# rm -fr /tmp/ctsupt /tmp/ibmsupt

Ensure there is sufficient free space in the tmp filesystem (~300MB).

 snap vmsnap

The snap command stores the data at the following location: /tmp/ibmsupt/*.pax.Z.

Submit all snap files from:

/tmp/ibmsupt
/tmp/ibmsupt/snap.pax.Z
/tmp/ibmsupt/ksys.pax.Z

Rename any file before it is submitted.  If it is a snap.pax.Z file add KSYS --  

 mv snap.pax.Z TSxxxxxxxxx.KSYS.snap.pax.Z

---

2) On each VIOS do:

Log in to the VIO server as "padmin" and collect a snap.

$ snap

The snap output is copied to:

/home/padmin/snap.pax.Z

See: https://www.ibm.com/support/pages/node/671013 for more details.

Rename the file and submit it.

# mv snap.pax.Z TSxxxxxxxxx.<VIOS_hostname>.snap.pax.Z

---

3) If any managed Virtual Machine is an AIX LPAR, collect this data from such LPARs:

Gather a snap -ac

# snap -r

# snap -ac

The output goes to:

/tmp/ibmsupt

Rename the file and submit it.

# mv snap.pax.Z TSxxxxxxxxx.<VM_hostname>.snap.pax.Z

If you are using VMRM HA, gather this data:

# ksysvmmgr snap

If the ksysvmmgr command is not on your VM, install the ksys.vmmon.rte fileset.

This command creates a *.pax.gz file in:

/var/ksys/log/snap/*.pax.gz

The "*" part of the file name is the date and time.

Rename the file and submit it.

# mv *.pax.gz TSxxxxxxxxx.*.pax.gz

---

4) On the HMCs as user hscpe, do:

 pedbg -c -q 4

Look for a file like this --

 /dump/HMClogs*zip

Change the filename to be unique if necessary and submit it.

---

(GUI debug data gathering instructions follow.  Get at least the KSYS vmsnap from previous steps.  The KSYS vmsnap includes the ui logs in later versions.)

Collect the following data needed to investigate VMRM GUI issues:

1) Send screen captures showing evidence of the error if available.

2) On the GUI Server, do:

# cd /

# tar -cvf /tmp/TSxxxxxxxxx.server.tar ./opt/IBM/ksys/ui/*

3) If the GUI Server is not deployed on the GUI Agent KSYS, on the GUI Agent KSYS do:

# cd /

# tar -cvf /tmp/TSxxxxxxxxx.agent.tar ./opt/IBM/ksys/ui/*

4) If multiple VMRM KSYS clusters are part of the issue, do step 3 on all GUI Agent KSYS.

Add a KSYS name to the tar files --

# tar -cvf /tmp/TSxxxxxxxxx.agent.KSYSname.tar ./opt/IBM/ksys/ui/*

5) Submit the tar files.  The tar files can be compressed to reduce size.

Document Location

Worldwide

[{"Type":"SW","Line of Business":{"code":"","label":""},"Business Unit":{"code":"BU008","label":"Security"},"Product":{"code":"SGL4G4","label":"PowerHA"},"ARM Category":[{"code":"a8m3p0000006x4ZAAQ","label":"VMRM - Virtual Machine Recovery Manager-\u003EData Collection"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"All Version(s)"}]

Document Information

Modified date:
19 December 2022

UID

ibm16454141