Question & Answer
Question
What data is needed to diagnose problem on redundant PowerVM Virtual I/O Servers (VIOS) environment?
Note: Per government and privacy regulations, IBM is not authorized to move client data. For IBM to review your data, you must upload the data to an IBM official testcase server. For details, see Where to Submit Testcase.
Cause
- Virtual SCSI adapter or AIX VSCSI MPIO disk
- Shared Ethernet Adapter
- Virtual Fibre Channel adapter
- Active Memory Sharing partition
Answer
Testcase collection involves
1. How to gather snap from VIO servers
2. Client data
3. How to gather virtual mapping (lshwres) data from HMC
4. How to package and where to submit the testcase
1. How to gather snap from the VIO Servers
Note: If the testcase is needed to diagnose a virtual SCSI problem, it is important that you first collect the snap from the VIO servers, and then the AIX client in question. For VIOS snap collection details, click here.
2. Client Data
a. For Linux or IBM i
Provide OS type, version, partition name, and partition ID in order to determine the associated virtual adapters on the VIOS.
If the problem is specific to some virtual adapters, list the client adapter IDs in question.
# 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 by using a naming convention similar to the VIO server snap. Example: client_hostname.snap.pax.Z
3. How to Collect Virtual Mapping (lshwres) Data for HMC-Managed System
The following procedure requires access to an AIX host with ssh configured to access the HMC in order to capture data to a file. Note: The HMC must be configured to accept ssh connections.
Log in to AIX server, as root, and issue
# script -a /tmp/lshwres.out
# ssh -l hscroot <HMC hostname>
Once logged in to the HMC, run
# lshmc -V
# lssyscfg -r sys -F name (to list all managed system names)
Next, run the appropriate lshwres command that relates to your problem.
To gather virtual SCSI mapping
# lshwres -r virtualio -m <managed_system_name> --rsubtype scsi --level lpar
To gather virtual Fibre Channel mapping
# lshwres -r virtualio -m <managed_system_name> --rsubtype fc --level lpar
To gather virtual memory sharing (AMS) mapping
# lshwres -r mempool -m <managed_system_name>
# lshwres -r mempool -m <managed_system_name> --rsubtype pgdev
To gather virtual ethernet mapping
# lshwres -r virtualio -m <managed_system_name> --rsubtype eth --level lpar
# exit (from the HMC)
# exit (to end the script)
4. How to Package and Where to Submit the Testcase
# mkdir /tmp/viotc transfer 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.
# 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 client_hostname.snap.pax.Z
-rw------- 1 root system 7648755 Sep 04 08:09 vios1_hostname.snap.pax.Z
-rw------- 1 root system 7648755 Sep 04 08:09 vios2_hostname.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 file is the one you need to send.
Related Information
Was this topic helpful?
Document Information
Modified date:
08 September 2022
UID
isg3T1010950