Storage disks/luns are not visible and the error "pp_claim_device: Could not get metanode from ODM database" is encountered.

book

Article ID: 100021568

calendar_today

Updated On:

Resolution

After presenting new storage disks/luns to a system, VxVM (Veritas Volume Manager) can encounter problems recognising the newly presented devices, however they are visible at the OS level.
 
The following device reconfiguration steps are performed to try and allow VxVM to recognise the newly presented devices:
 
#mv /etc/vx/array.info /etc/vx/array.info.old
#mv /etc/vx/disk.info /etc/vx/disk.info.old
#mv /etc/vx/jbod.info /etc/vx/jbod.info.old
#rm /dev/vx/dmp/*  
#rm /dev/vx/rdmp/*  
#vxconfigd -k -m enable -x syslog
 
The vxconfigd command above encountered the following errors:
 
pp_claim_device:Could not get metanode from ODM database
VxVMvxconfigd ERROR V-5-1-12223 Error in claiming /dev/rhdisk6: Error0
 
"pp_claim_device"is a routine that VxVM uses to probe devices which it believes are under third party (PowerPath) multipathing control. However, there was no third party multipathing software installed on the node, therefore VxVM was expecting DMP(VxVM's Dynamic Multi Pathing) to claim these devices. This problem can occur when the remnants of the PowerPath software is still configured in AIX's ODM(Object Data Manager) database.
 
To verify that ODM still has PowerPath configured, the following command can be used:
 
#odmget-q "value1 like powerdiskdd" CuDvDr
CuDvDr:
     resource= "ddins"
     value1= "powerdiskdd"              <<<<<<<<<<<<<
     value2= "49"
     value3= ""
 
The above output shows that the ODM database still has PowerPath entries.
 
Solution:
 
The above ODM definitions can be cleared as follows:
 
#odmdelete -o CuDvDr -q "resource = ddins AND value1 =powerdiskdd"
 
To allow VxVM to recognise the devices, the VxVM configuration daemon, vxconfigd, will require restarting as follows:
 
#vxconfigd -k -m enable -x syslog
 

 

Issue/Introduction

Storage disks/luns are not visible and the error "pp_claim_device: Could not get metanode from ODM database" is encountered.