Page 2 of 2

Re: Change LUN ID from CLI

Posted: Fri Mar 29, 2019 1:16 am
by apol
Hi,

could it be that you talk about the VV-WWN (SCSI-ID)?

Code: Select all

showvv -showcols Name,VV_WWN



It can be changed on 3PAR with

Code: Select all

setvv -wwn <newwwn>


but I don't know if this helps in your environment, no idea 'bout VMS.

Re: Change LUN ID from CLI

Posted: Fri Mar 29, 2019 4:59 am
by ailean
Ah VMS, I did spot a special option for that on the setvv command;

Code: Select all

-udid <Udid_Val>
Specifies the user defined identifier for VVs for OpenVMS hosts. Udid value should be between 0 to
65535 and can be identical for several VVs.


Maybe that's what you need?

Re: Change LUN ID from CLI

Posted: Fri Mar 29, 2019 5:44 am
by apol
I just checked it on our test array, Udid and VV-ID are the same if you don't mess with it. Maybe that's why it looks like one has to change VV-ID...

Re: Change LUN ID from CLI

Posted: Mon Apr 01, 2019 7:50 am
by squant
You are correct.

To migrate the VMS existing LUNS to new LUNS the UDID can not match. However once migrated we need to change the udid to match that of the migrated LUN.

When creating a VV from the CLI we can give the LUN a number that sets LUNID, BSID and UDID to be the same. However when we change the udid (setvv -udid "some number" "vv name") it doesn't change the LUNID or the BSID.

This method works for migrations but I was looking for a command to change all ID to match for consistancy.

I found the only way to achive this is by cloning the migrated LUN and giving the clone the ID needed. Mapping it to the host and the host removing the old lun.

Both methods work, cloning is a few extra steps but cleaner and consistant.

Thank you for your replys.