how do you unmap VCM device on DMX

You are more than likely going to need a bin file done by emc to make the VCM change. Symcli cannot remove the VCM and re-add it, I do not believe.

what is DRV device?

That is a temporary device used by Optimizer for moving logical volumes around.

Actually I unmapped a VCM yesterday using symcli.
I needed to change FA flags.

So the option to unmap a VCM depends on which microcode you're using...

what flag was modified

Hmmm... SPC-2 os2007 and VSA, I think.

i think soncao01 wants to remove VCM device not disable VCM_State flag on the FA. The only time i had to disable VCM_State was on a brand new FA that was going to be used for Celerra Gateway. I don't remember specifically cycling the FA. Not sure why you would want to disable VCM_State otherwise, when you do that all hosts on the FA will see every single device mapped to that FA.

yes, first one is true. cannot unmap device with out putting it in not ready state.

second thing up to my knowledge there is a no big relationship between I/O and VCM. if it is GK than different thing.

But when you edit some port flag you have to restart fa port. this is real burden.

hi, MaximUnited,

When you unmapped the VCM device, you must have had to put into not_ready first.  First, is this true?  Second, did it impact I/O on other FAs that use the VCM for masking?

Thanks,

Son

It's recommended to temporarily suspend IO to the port but not actually bounce the FA, I've had to set port flags on the fly without any issues.

This e-mail message (including any attachments) is for the sole use of

the intended recipient(s) and may contain confidential and privileged

information. If the reader of this message is not the intended

recipient, you are hereby notified that any dissemination, distribution

or copying of this message (including any attachments) is strictly

prohibited.

If you have received this message in error, please contact

the sender by reply e-mail message and destroy all copies of the

original message (including attachments).

just for my knowledge, is it true for VCM enable/ disable flag also?

You can make it write_disabled just on that specific FA and then unmap it.

Symdev -sid 123 write_disable 0BAD -SA 9A - p 0

This e-mail message (including any attachments) is for the sole use of

the intended recipient(s) and may contain confidential and privileged

information. If the reader of this message is not the intended

recipient, you are hereby notified that any dissemination, distribution

or copying of this message (including any attachments) is strictly

prohibited.

If you have received this message in error, please contact

the sender by reply e-mail message and destroy all copies of the

original message (including attachments).

That's correct, dynamox, I want to unmap the VCM device from the FA, which is unused, by the way.  Bottom line - I want to enable volume_set_addressing on the FA.  When I run symconfigure to do that, it fails, reporting that there are devices mapped to the FA.  Makes sense, so I unmap all devices and GK's from the FA.  Ran symconfigure again to enable volume_set_addressing.  Fails again with the same error.  Only device left on that FA now is the VCM device at address 00.  I'm sure I can unmap the VCM device from the FA but I would be forced to put it into not_ready first.

$64K question:  If I put VCM device in not_ready, will this affect I/O on other FAs where the VCM is mapped?  In other words, the hosts that are using other FAs are relying on VCM to keep lun access straight...will they be impacted when VCM device goes to not_ready?

U da man, dynamox!  The write_disable worked.

this is the magic behind dynamox point soncao01.

Dynamox is EMC guru.