VCMDb device in Windows Disk Management

it should be write disabled, can you run symdev show on the VCM device and look for "Device Status" line.

The VCMDB will be write disabled from the array.You would not be able to access it.But Disk management will find it as a Disk.

Since the VCM is simply a gatekeeper, since DMX3 you MAY find VCM devices being rw enabled. While it's still true that the VCM SHOULD be write disabled, don't be scared if you find a RW enabled VCM

I would say allocate dedicated GK make VCM device WD

ok...
So since the server sees it as a mounted disk drive, not initialized or formated. how do i ensure that after each reboot the message indicating that volume is new hardware found?
We are afraid someone is going to see it as a usable device and try to initialize.
Should we set the device to write disabled? i believe it is RW at this time

Since code 5771 (DMX3 and later) the VCM is simply a GK. I'd unmap the VCM from affected ports and leave it only on management FA ports. My 2 euro-cents

One workaround for this would be to disable the device on the host so that it basically no longer sees the VCM device.

The easiest way to do this would be through Disk Management, right-click on the disk and choose Properties. On the properties screen, at the bottom of the General tab is a "Device usage" value. You can use the pull down to change the device usage value to "Do not use this device (disable)". This will cause the device to immediately disappear from Disk Management. You'll want to repeat this for all other instances of the VCM on the host. You'll need to reboot in order to get the Disk numbers back in order without the gaps from these disabled devices.

If you ever need to bring these back, it can be done through Device Manager > Disk Drives. Just find the device with the red X thru it and choose to enable the disk...if you just disabled the disk, you would need to reboot the host in order to see the red X through the device.

Hope this helps.

You can use the symmask command to set the disk offset so the VCMDB device shows becomes a "negative address" and doesn't display on the host.

symmask -sid 0394 -wwn set lunoffset on 10 0 -dir -p

This command will have the SYM present the LUN at address 10 on the director:port to be presented to the system as LUN 0. In our environement this has the effect of "hiding" the VCMDB device as it is mapped to the FA at an address lower than 10.

This will really only help if your VCMDB device is mapped to the FA at a lower LUN address then the actual disk you wish to present to the server. Note that this offset acts on the WWN/Director/Port combo and affects every LUN assigned to that combo.

Tim, the offset feature is superceded by DLA. I strongly suggest NOT using lun offset anymore.

Indeed it works.

IMHO it's just like using an hammer to turn a screw. It works, but maybe there are better tools