vxdg list shows disks disabled

[Jamie A Dennis]

Hello,

Has anyone seen this problem?

I am seeing several disks showing as disabled in vxdg list on my disk groups.

Examples:
# vxdg list dg02
Group: dg02
dgid: 1236968235.311.xiachp003
import-id: 1024.93
flags: cds
version: 140
alignment: 8192 (bytes)
local-activation: read-write
ssb: on
detach-policy: global
dg-fail-policy: dgdisable
copies: nconfig=default nlog=default
config: seqno=0.1059 permlen=24072 free=24063 templen=4 loglen=3648
config disk c2t0d3 copy 1 len=24072 state=clean online
config disk c2t0d4 copy 1 len=24072 state=clean online
config disk c2t0d5 copy 1 len=24072 state=clean online
config disk c2t0d6 copy 1 len=24072 disabled
config disk c2t0d7 copy 1 len=24072 state=clean online
config disk c2t1d0 copy 1 len=24072 state=clean online
config disk c2t1d1 copy 1 len=24072 disabled
config disk c2t1d2 copy 1 len=24072 disabled
config disk c2t1d3 copy 1 len=24072 disabled
config disk c2t1d4 copy 1 len=24072 disabled
config disk c2t1d5 copy 1 len=24072 disabled
config disk c2t1d6 copy 1 len=24072 disabled
config disk c2t1d7 copy 1 len=24072 disabled
config disk c2t2d0 copy 1 len=24072 disabled
config disk c2t2d1 copy 1 len=24072 disabled
log disk c2t0d3 copy 1 len=3648
log disk c2t0d4 copy 1 len=3648
log disk c2t0d5 copy 1 len=3648
log disk c2t0d6 copy 1 len=3648
log disk c2t0d7 copy 1 len=3648
log disk c2t1d0 copy 1 len=3648 disabled
log disk c2t1d1 copy 1 len=3648 disabled
log disk c2t1d2 copy 1 len=3648 disabled
log disk c2t1d3 copy 1 len=3648 disabled
log disk c2t1d4 copy 1 len=3648 disabled
log disk c2t1d5 copy 1 len=3648 disabled
log disk c2t1d6 copy 1 len=3648 disabled
log disk c2t1d7 copy 1 len=3648 disabled
log disk c2t2d0 copy 1 len=3648 disabled
log disk c2t2d1 copy 1 len=3648 disabled
#

These are all disks that have just been added to this newly created disk group.

vxdisk list doesn't show any problems:
# vxdisk list | grep dg02
c2t0d3 auto:cdsdisk c2t0d3 dg02 online
c2t0d4 auto:cdsdisk c2t0d4 dg02 online
c2t0d5 auto:cdsdisk c2t0d5 dg02 online
c2t0d6 auto:cdsdisk c2t0d6 dg02 online
c2t0d7 auto:cdsdisk c2t0d7 dg02 online
c2t1d0 auto:cdsdisk c2t1d0 dg02 online
c2t1d1 auto:cdsdisk c2t1d1 dg02 online
c2t1d2 auto:cdsdisk c2t1d2 dg02 online
c2t1d3 auto:cdsdisk c2t1d3 dg02 online
c2t1d4 auto:cdsdisk c2t1d4 dg02 online
c2t1d5 auto:cdsdisk c2t1d5 dg02 online
c2t1d6 auto:cdsdisk c2t1d6 dg02 online
c2t1d7 auto:cdsdisk c2t1d7 dg02 online
c2t2d0 auto:cdsdisk c2t2d0 dg02 online
c2t2d1 auto:cdsdisk c2t2d1 dg02 online

The OS is
# uname -a
HP-UX xiachp003 B.11.23 U ia64 0742470887 unlimited-user license

OS has all required and recommended patches for Veritas products applied.

Veritas Foundation Suite 5.0 with MP1 and RP1 applied.

vxdg deport/vxdg import did not help, nor did vxdctl enable.

Not sure what I'm missing here...

Any help greatly appreciated.

[Johnson Punniyalingam]

Hi,

Can please try below command.

/usr/sbin/vxvol -fg dg02 startall


Thanks,
JOhnson

[Richard Hepworth · Accepted solution]

Hi,

The output shows that the configuration copies on certain disks are disabled which is normal. As long as you have at least one disk in the disk group that has a clean online configuration then you are ok.

Veritas decides which disks will hold active configuration copies, however, if you are not happy with the number you can always increase this via:

vxedit -g set nconfig=

[Jamie A Dennis]

Richard,

So it really has no bearing on the usability of the disk, it's just the copies of the log files and configuration database that are not online?

Thanks,

Jamie

[Richard Hepworth]

Hi Jamie,

That is correct, you normally don't need to concern yourself with the status of the config copies. As long as vxdisk list doesn't complain the disk should be usable.

regards,

Richard

[Jamie A Dennis]

Great, thanks. One more question, if you don't mind. Does one need to use Veritas Volume Manager disk groups in order to use Veritas Dynamic MultiPath? Or can one just use Veritas Filesystems with the HP-UX LVM and still use DMP?

My understanding was in order to use DMP you had to use Veritas Storage Foundation as if there were no built in Logical Volume Manager, i.e. initialize disks into VVM, create Disk groups, do the entire VVM procedures. Am I correct in that?

[Richard Hepworth]

Can't say I've ever tried to pvcreate a Veritas dmp device, not sure it would work and am even less sure it would be a supported configuration.

[Jamie A Dennis]

That was my thought as well.. just hadn't run across that question before.. I spend WAY more time in AIX than I do in HP-UX, although that is rapidly changing...

[Jamie A Dennis]

This was not really a problem, it was expected behavior as per Richards post. Thanks!

[Nilesh Patoliya]

vxdisk -g testdg set keepmeta=always

keepmeta={default|always}
If set to default, a configuration copy and a log
copy are written to the specified disk when it is
added to a disk group if this is accord with the
standard placement policy.
If set to always, a configuration copy and a log
copy are written to the specified disk when it is
added to a disk group irrespective of the standard
placement policy.

after apply above mention command status changed from disabled to clean online