After adding a new LUN to LDOM system unable to view device in 'vxdisk list'

book

Article ID: 100020822

calendar_today

Updated On:

Resolution

Devices are identified through a different mechanism inside a Sun LDOM machine environment and as a result VxVM may attribute a new LUN as a secondary path to a previous removed device.

Examine the getsubpaths output for all LUNs to determine if multiple paths are being shown for any devices.
# vxdmpadm getsubpaths ctlr=c0 | grep

The first column of output is the path name, and the fourth column is the DMP node name.

c0d15s2 ENABLED PRIMARY c0d13s2 OTHER_DISKS Disks -

This output shows the c0d15 paths is being claimed by the c0d13 DMP node.

To resolve this issue perform the following procedure where is the name of the DMP node claiming the new LUN (in this case, c0d13):
# rm /dev/vx/*dmp/*
# vxdisk rm

For example:
# rm /dev/vx/*dmp/c0d13*
# vxdisk rm c0d13

Once this is complete, reinitiate devices canning:
# devfsadm -C
# vxdisk scandisks

Verify that issue is resolved (the new path should be displayed in vxdisk list):
# vxdisk list
 
 

 

Issue/Introduction

After adding a new LUN to LDOM system unable to view device in 'vxdisk list'