IBM Support

How to Collect Testcase for P/D on PowerVM Dual VIOS Environment

Technote (FAQ)


This document applies only to the following language version(s):

US English

Question

This document describes how to gather a testcase on a PowerVM Virtual I/O Server (VIOS) environment to diagnose issues on dual VIOS environment related to
- Virtual SCSI
- Virtual Ethernet
- Virtual Fibre Channel (NPIV) and/or
- Active Memory Sharing (AMS) also known as virtual memory

This applies to VIOS level 2.2 and above.

Known Issues with VIOS snap command.

Answer

Testcase collection involves

1. How to gather snap from VIO server(s)
2. How to gather snap from AIX client(s)
3. How to gather virtual mapping (lshwres) data from 1. HMC or 2. IVM
4. How to package and where to submit the testcase


1. How to gather snap from VIO Server

NOTE: If the testcase being collected is to diagnose issues specific to virtual SCSI, it is very important that you FIRST collect the snap from the VIO server(s), and then the AIX client(s) in question.

Login to VIO server, as padmin, and collect snap by running

$ snap (Repeat this for any additional VIO server.)

Upon completion, this will create /home/padmin/snap.pax.Z. If this file exists prior to running snap command, it will be deleted and recreated.

Next, rename the compressed file using the VIOS hostname as part of the naming convention if you are submitting snaps for more than one VIOS:

$ mv snap.pax.Z <VIO_hostname>.snap.pax.Z


2. How to gather snap from AIX client

Login to AIX server, as root and run
# snap -r (this will remove any previous snap)
# snap vfc_client_collect (for virtual fiber channel adapter mapping)
# snap -ac (this will create /tmp/ibmsupt/snap.pax.Z)

Rename the compressed file using a naming convention similar to the VIO sever snap (i.e <client_hostname>.snap.pax.Z).

Repeat this for any additional AIX client.


How to Collect Virtual Mapping (lshwres) Data

3.1 Collecting Virtual Mapping Data from an HMC Managed System

The following procedure requires access to an AIX host with secure shell (ssh) configuration to access the HMC. Note: the HMC must be configured to accept ssh connections.

Login to AIX server, as root, and issue

# script -a /tmp/lshwres.out
# ssh -l hscroot <HMC hostname>

Once logged in to the HMC issue
# lshmc -V
# lssyscfg -r sys -F name (to list all managed system names)

Run the appropriate lshwres command that relates to your problem


    To gather virtual SCSI mapping, run
    # lshwres -r virtualio -m <managed_system_name> --rsubtype scsi --level lpar

    To gather virtual fiber channel (NPIV) mapping, run
    # lshwres -r virtualio -m <managed_system_name> --rsubtype fc --level lpar

    To gather virtual memory sharing (AMS) mapping, run
    # lshwres -r mempool -m <managed_system_name>
    # lshwres -r mempool -m <managed_system_name> --rsubtype pgdev

    To gather virtual ethernet mapping, run
    # lshwres -r virtualio -m <managed_system_name> --rsubtype eth --level lpar

# exit (from the HMC)
# exit (to end the script)

3.2. Collecting Virtual Mapping Data from an IVM Managed Systems

Login to IVM (VIOS) server, as padmin, and run

$ oem_setup_env
# script -a /tmp/lshwres.out
# su - padmin

Run the appropriate lshwres command that relates to your problem


    To gather virtual SCSI mapping, run
    $ lshwres -r virtualio --rsubtype scsi --level lpar

    To gather virtual fiber channel (NPIV) mapping, run
    $ lshwres -r virtualio --rsubtype fc --level lpar

    To gather virtual memory sharing (AMS) mapping, run
    # lshwres -r mempool
    # lshwres -r mempool --rsubtype pgdev

    To gather virtual ethernet mapping, run
    $ lshwres -r virtualio --rsubtype eth --level lpar


$ exit (from padmin shell)
# exit (to end the script)

4. How to Package and Where to Submit the Testcase

Once the files on section 1-3 have been created, ftp them to a host (i.e. AIX server) to package them into a single file using pax command and your Support Case ID as part of the file name, i.e.

In AIX host, as root, run:

# mkdir /tmp/viotc (ftp the files to this directory)
# cd /tmp/viotc
# ls -la (ensure all files are listed: vio server snap(s), client snap, and lshwres.out)
# pax -wf TS<xxxxxxxxx>.pax ./* (this will create single pax file)

For example, if your Support Case ID is TS0123456789, you would do something similar to the following:

    # pwd
    /tmp/viotc

    # ls -la
    total 44848
    drwxr-xr-x   2 root  system          256 Sep 04 08:27 .
    drwxrwxrwt  12 bin   bin            4096 Sep 04 08:27 ..
    -r--r--r--   1 root  system          880 Sep 04 08:07 lshwres.out
    -rw-------   1 root  system      7648755 Sep 04 08:10 vioc1.snap.pax.Z
    -rw-------   1 root  system      7648755 Sep 04 08:09 vios1.snap.pax.Z
    -rw-------   1 root  system      7648755 Sep 04 08:09 vios2.snap.pax.Z

    # pax -wf TS0123456789 .pax -x pax ./*
    # ls -la
    ...
    -rw-r--r--   1 root  system     22958080 Jun 12 08:36 TS0123456789.pax  
    ...
    This is the file you need to send in.

Where to Submit the Testcase



Known Issues with VIOS snap command


1. IZ90550 ERRDEMON NOT RESTARTED AFTER SNAP EXECUTED
at VIOS 2.2.0.10-FP24 and 2.2.0.11-FP24 SP-01.
Recommendation: This issue is fixed in 2.2.0.12-FP24 SP-02 and 2.2.0.13-FP24 SP-03 with IZ89453 and in 2.2.1.1 (FP25) and 2.2.1.3 (FP25 SP01) with IZ90315. Please, update VIOS to any of these or higher levels.

2. IZ90486 SNAP SVCOLLECT HANGS GATHERING VASI DATA
at VIOS 2.2.0.10-FP24 and 2.2.0.11-FP24 SP-01.
Recommendation: This issue is fixed in VIOS 2.2.0.12-FP24 SP-02 2.2.0.13-FP24 SP-03 with IZ90645 and in 2.2.1.1 (FP25) and 2.2.1.3 (FP25 SP01) with IZ91752. Please, update VIOS to any of these or higher levels.

3. IV53574 SNAP -AC HANGS ON GATHERING SVCOLLECT DATA in VIOS 2.2.3.1.
This only applies to VIOS 2.2.3.1 if the VIOS has a virtual optical device and "snap -ac" is invoked.
To check if the VIOS has an optical device (cd#) virtualized, login to the VIOS as padmin and run
$ lsmap -all |grep cd
Recommendation: Contact your VIOS Support Representative and request ifix prior to running "snap -ac" (no reboot required after ifix is installed) or update the VIOS to 2.2.3.2
.

Related information

padmin snap command

Document information

More support for: Virtual I/O Server

Software version: 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5

Operating system(s): Other

Software edition: Enterprise, Express, Standard

Reference #: T1010950

Modified date: 28 June 2011


Translate this page: