IBM Support

AIX migration failed due to duplicate PVIDs

Troubleshooting


Problem

If the rootvg exists on a SAN disk being served by a 3rd party, then migration from AIX 6.1 to 7.1, or 7.1 to 7.2 may fail due to duplicate PVIDs for the rootvg disk because the 3rd party multipath software is not available at migration time.

Symptom

The migration may fail with the following errors:
0516-1775 varyonvg: Physical volumes hdisk0 and hdisk1 have identical PVIDs (PVID). 
0516-780 importvg: Unable to import volume group from hdisk0.
Could not import the root volume group.
  ID#‌    OPTION
   1    Continue
   2    Perform System Maintenance and Then Continue
  Enter ID number: 

Cause

To use a 3rd party SAN disk on AIX, a specific 3rd party multipath software must be installed. This software is not included on the AIX installation media. Therefore, the rootvg disk is not managed by the multipath software or MPIO during the AIX migration. If there are multiple paths to the disk, each path will be recognized as a different disk, but will have identical PVIDs, causing the migration to fail.

Diagnosing The Problem

Select  option "2" ( Perform System Maintenance and Then Continue)
0516-1775 varyonvg: Physical volumes hdisk0 and hdisk1 have identical PVIDs (00f6xxxd4xxx28cf). 
0516-780 importvg: Unable to import volume group from hdisk0.
Could not import the root volume group.
  ID#‌    OPTION
   1    Continue
   2    Perform System Maintenance and Then Continue
  Enter ID number:  2
Check the rootvg disk
# lspv
hdisk0 00f6xxxd4xxx28cf None
hdisk1 00f6xxxd4xxx28cf None
hdisk2 00f6xxxd4xxx28cf None
hdisk3 00f6xxxd4xxx28cf None

# lsdev -Cc disk
hdisk0 Available 20-T1-01 Other FC SCSI Disk Drive
hdisk1 Available 20-T1-01 Other FC SCSI Disk Drive
hdisk2 Available 20-T1-01 Other FC SCSI Disk Drive
hdisk3 Available 20-T1-01 Other FC SCSI Disk Drive
**You will see several rootvg disks with identical PVIDs, and they are not managed by AIX MPIO.

Resolving The Problem

A)  Work with your SAN/Storage admin to reduce the path number of the rootvg disk to just one before the migration.

B)  If using NIM, add the the required multipath software to NIM spot prior to the migration.

Add the 3rd party multipath software to NIM spot:
Find the "lpp name":
# installp -qld [location of the 3rd party software].
Update the lpp_source:
# nim -o update -a source=[location of the 3rd party software] -a packages=[lpp name] [lpp_source name]
Add the lpp name to spot:
# nim -o cust -a filesets=<3rd party lpp name> -a lpp_source=[lpp_source name] [spot name]

For example:
# installp -qld /tmp/HDS
  Fileset Name                Level                     I/U Q Content
  ====================================================================
  devices.fcp.disk.Hitachi.array.mpio.rte 5.4.0.0                    I  b usr #   AIX MPIO Support for Hitachi Disk Arrays(New Install)
# nim -o update -a source=/tmp/HDS -a packages=devices.fcp.disk.Hitachi.array.mpio.rte AIX722lpp
# nim -o cust -a filesets=devices.fcp.disk.Hitachi.array.mpio.rte -a lpp_source=AIX722lpp AIX722spot
# nim -o lslpp AIX722spot |grep  devices.fcp.disk.Hitachi.array.mpio.rte
  devices.fcp.disk.Hitachi.array.mpio.rte 5.4.0.0  COMMITTED  AIX MPIO Support for Hitachi
The devices.fcp.disk.Hitachi.array.mpio.rte is the HDS storage's multipath software.
**Some 3rd party multipath software is unable to add to NIM spot, then please use option A).
SUPPORT

If additional assistance is required after completing all of the instructions provided in this document, please follow the step-by-step instructions below to contact IBM to open a case for software under warranty or with an active and valid support contract.  The technical support specialist assigned to your case will confirm that you have completed these steps.

1.  Document and/or take screen shots of all symptoms, errors, and/or messages that might have occurred. 

2.  Capture any logs or data relevant to the situation.

3.  Contact IBM to open a case:

   -For electronic support, please visit the IBM Support Community:
     https://www.ibm.com/mysupport
   -If you require telephone support, please visit the web page:
      https://www.ibm.com/planetwide/

4.  Provide a good description of your issue, and reference this Technote, and any issues you had with the instructions.

5.  Collect the system snap and upload all of the details and data for your case.

To collect a complete snap of your system information:

5.1) Remove previously gathered data

   # snap -r

5.2) Copy related files from #1 and #2 to the snap data directory

   # mkdir -p /tmp/ibmsupt/testcase
   # cp <logs, screenshots, etc> /tmp/ibmsupt/testcase

5.3) Run the snap command with one of the following options to collect all info.

     * If you have already engaged with a support engineer, use the flags specified by your support team.

   # snap -aZc (Omits system dump data)   
     OR 
   # snap -ac (Use if system dump data is needed)

5.4) Rename the testcase to include your case number to ensure it is properly attached to your case

  # mv /tmp/ibmsupt/snap.pax.Z  /tmp/ibmsupt/yourcase#[.optional_description].snap.pax.Z

5.5) Upload the file by one of the following options (a, b, or c)

     a) Attach to your case
     https://www.ibm.com/mysupport/s/my-cases

     b) Upload to the Enhanced Customer Data Repository(ECuRep) 
     https://www.secure.ecurep.ibm.com/app/upload_sf

     c) Upload to the Blue Diamond FTP server (Blue Diamond Customers Only)
     https://msciportal.im-ies.ibm.com

* Note: For information about blue diamond upload see:

     http://www.ibm.com/support/docview.wss?uid=nas8N1020947

Document Location

Worldwide

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG10","label":"AIX"},"Component":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"6.1;7.1","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Document Information

Modified date:
01 June 2019

UID

ibm10884684

Page Feedback