MustGather: AIX Install problems

The following procedures are for data collection, not for problem diagnosis. Gathering this information before calling IBM support can aid in problem determination and save time resolving Problem Management Records (PMRs).

The zsnap data collection tool is the recommended method for data collection; however, we realize many customers are unable to, or do not wish to, go through the installation process for that tool. For those instances, we have included alternative means of data collection.

Below you will find requirements for data collection for the following sub-components of install.

1. Explain the details of the failure - how it failed. Include the EXACT steps to recreate the problem and any error messages.
2. If the PMR is a Sev 1, confirm there is a production impact going on, (ie: Productions server is down, customer has a change window on the production server and needs to get issue fixed soon.)
3. zsnap --> primary snap tool used by WWINST.
   - If customer cannot install zsnap, snap is needed for escalation.
4. Make sure to run a snap -r to clean up any previous data that was collected and remove any *.pax files in /tmp/ibmsupt prior to running zsnap or snap.

Additional data needed for escalation:

# export INST_DEBUG=yes
# smitty -l /tmp/installp.out <update_all> (or substitute with whatever install command we ran)

OR

# script /tmp/installp.out
# export INST_DEBUG=yes
# Run your installp command here
# exit

Get Data:

# zsnap --INSTALL --addfile /tmp/installp.out,/<update_directory>/.toc (collect .toc file from the update directory)

OR

# snap -aZ
# script /tmp/lppchk.out
# lppchk -v
# lppchk -c
# exit
# cp /tmp/lppchk.out /tmp/ibmsupt/testcase
# cp /tmp/installp.out /tmp/ibmsupt/testcase
# cp /var/adm/ras/install_all_updates /tmp/ibmsupt/testcase/
# cp of the .toc file in /tmp/ibmsupt/testcase/
# snap -c

Additional data needed for escalation:

• Include copy of the smit.log if executed through smit. If we ran alt_disk_copy from command line, the /var/adm/ras/alt_disk_inst.log file is required.
• If an update also occurred, include the /var/adm/ras/install_all_updates file.
• If possible, run alt_disk* in debug mode.
  # smitty -l /tmp/alt_disk_copy.out alt_clone
• Follow the menus and include verbose and debug.

Get Data:

# zsnap --INSTALL --addfile </tmp/alt_disk_copy.out>

OR

# snap -aZ
# cp /var/adm/ras/alt_disk_inst.log /tmp/ibmsupt/testcase
# cp /var/adm/ras/install_all_updates.log /tmp/ibmsupt/testcase
# cp /tmp/alt_disk_copy.out /tmp/ibmsupt/testcase/
# snap -c

Note: DO NOT run rmfs or chlv commands against the multibos instance unless you consult with us.

If possible, run multibos in debug mode:
# script /tmp/multibos.out
# multibos <your params > -D
# exit

Get Data:

# zsnap --INSTALL --noprompt
# cp /tmp/multibos.out /tmp/ibmsupt/testcase
# cp /etc/filesystems /tmp/ibmsupt/testcase
# cp -r /etc/multibos /tmp/ibmsupt/testcase
# zsnap -c

OR

# snap -gL
# cp /tmp/multibos.out /tmp/ibmsupt/testcase
# cp /etc/filesystems /tmp/ibmsupt/testcase
# cp -r /etc/multibos /tmp/ibmsupt/testcase
# snap -c

If possible, run mksysb in debug mode:
# script /tmp/mksysb.out
# export MKSYSB_DEBUG=yes
# mksysb <your params >
# exit

Get Data:

# zsnap --INSTALL --addfile /tmp/mksysb.out
# zsnap -c

OR

# snap -aZ
# cp /tmp/mksysb.out /tmp/ibmsupt/testcase
# snap -c

If possible, run nimadm in debug mode
# smitty -l /tmp/nimadm.out nimadm
- Follow the menus and include verbose and debug.

OR

# script /tmp/nimadm.out
# nimadm -<whatever flags you are using > -DV
# exit

Get Data:

# zsnap --NIM --addfile /tmp/nimadm.out

OR

# snap -aZ
# cp /tmp/nimadm.out /tmp/ibmsupt/testcase/
# cp /etc/niminfo /tmp/ibmsupt/testcase
# cp /var/adm/ras/nimsh.log /tmp/ibmsupt/testcase
# lsnim -l > /tmp/ibmsupt/testcase/lsnim.l.out
# snap -c

# zsnap --NIM on both the Primary and Alternate Master.

OR

# snap -aZ
# cp /etc/niminfo /tmp/ibmsupt/testcase
# cp /var/adm/ras/nimsh.log /tmp/ibmsupt/testcase
# cp /etc/bootptab /tmp/ibmsupt/testcase
# lsnim -l > /tmp/ibmsupt/testcase/lsnim.l.out
# snap -c

Get mksysbs of Global and savewpars of the wpars in question.

OR

For syncwpar issues, get the ODM from the global and wpar in question.
From the Global:
# /usr/lib/instl/saveodms <hostname of Global Environment >
- This saves a directory in the u directory. Tar up the contents.
# cd /
# tar –cvf /tmp/PMR#.hostname.tar ./u/<hostname of Global Environment >

Log into the wpar and perform the same steps:
# /usr/lib/instl/saveodms <hostname of wpar >
# cd /
# tar –cvf /tmp/PMR#.hostname.tar ./u/<hostname of wpar >

Collect zsnaps –-INSTALL or snap -ac of the Global Environment and the wpars in question.

For mkwpar and savewpar issues, we need the debug output of those commands.
Example:
# export WPAR_SCREEN_LVL=D
# export WPAR_LOGFILE_LVL=D

Use the Technote below to gather all pertinent data needed for LKU issues.
Live Kernel Update Must Gather

Back to Collecting data