This happens when vxencap detects that namingscheme is not set with "persistence" option.

To set it use following command:

# vxddladm set namingscheme=osn persistence=yes

Please note, namingscheme above could be osn (Operating System Naming - like cxtxdx format) or ebn which is enclosure based naming like Disk_0 or EMC_0 format). If the persistence option is not set, disk names might get changed which might result in confusion of disknames being encapsulated hence it is recommended to enable persistence.

Alternatively if above doesn't help, following steps can be tried:

a) Move the disk.info file

# mv /etc/vx/disk.info /etc/vx/disk.info.old

b) set the namingscheme with above command

# vxddladm set namingscheme=osn persistence=yes

c) Restart the vxconfigd daemon (Please take precautions in this step if you have A/A clustered setup & using CVM/CFS, freezing all service groups would be recommended before running this step)

# vxconfigd -k

This step should regenerate the disk.info file & encapsuation should progress fine now.