squant wrote:
So the only way to do this is clone the LUN? The clone will have the LUN ID desired?
Just to get the lingo right. The VLUN (export of a VV with a LUN ID over one path to a host) can't be modified. You have one VLUN per path per volume per host. You do not have to clone the VV as the VV itself and the VLUN are only linked together and not dependent of eachother.
For a server to see a volume with another LUN ID than it does today, you will have to create new VLUNs(export the same VV to the same host) using another LUN ID. Once the new export is active and the host has detected and acknowgded the new paths to the same volume, you should be okay to deleted the old VLUNs using the old LUN IDs.
I say "should" because I know that Microsoft has had multiple MPIO hotfixes for stuff like this over the year and I don't know if every possible OS supports accessing the sam volume over multiple LUN IDs. I've sucessfully changed it online, but it might not work in your environment.