How to Change LUN ID

Storage Pools and Storage Groups, I didn't catch the difference but I see it now.  Okay, I figured out how to set 1 of the boot LUNs to LUN ID 0, but I can not get all of them configured to ID 0 in the same Storage Group, is this normal??  THe better question might be what is the best pratice for setting up ESXi to boot from SAN on this VNX system.  Also, how do I add the Hosts without having valid IPs for them yet??  Thank you.

To see what the Host LUN ID is compared to the CLARiiON LUN ID, you must bring up Navisphere/Unisphere Manager and go into the Host properties. The Storage tab displays the CLARiiON LUN ID and the Host LUN ID.  

To change the Host LUN ID you must remove the LUN from the Storage Group and re-add it back into the Storage Group. Before applying it, you must slide over to the last column to the right and click in the field. You will then get a drop-down menu to set the Host LUN ID to what you want it to be. 

Note: This is a disruptive operation. The host will not have access to the LUN while it is removed from the Storage Group.

Please, refer KB Article: 116197.

In addition to what dynamox said, please, refer to Host Connectivity Guide for VMWare ESX Server Page 239.

only one LUN in storage group can be LUN id 0. Since you are using UCS, you could create two vHBAs and use that for boot from SAN, that would go into dedicated storage group for that host (with just one LUN), the other set of vHBAs could be connected to your "shared" storage group where you have LUNs that you use for VMFS datastores.

We will  also soon  implement "boot form SAN" on a UCS and I'd like to better understand the idea of using additional vHBAs when you can just creat a storage group for each host in the cluster and have LUN 0 as a stand alone device for each host.The shared luns can then be added to each storage group.

Also another question that comes up is what are the safeguards agaainst a corrupted boot device? Would it amke since to image the boot device, save this image elsewhere disk, tape, and then restore if in the event there is corruption?

Thanks,

Dali

you have to manage adding "shared" luns to each individual storage groups, sure ..it's doable. With UCS you can have your vHBAs dedicated for shared storage to be in the same "shared storage" storage group.

Also another question that comes up is what are the safeguards agaainst a corrupted boot device? Would it amke since to image the boot device, save this image elsewhere disk, tape, and then restore if in the event there is corruption?

you can with local and remote replication technologies ...does it make sense for your shop, i don't know. I know some shops where everything is booted from SAN and everything is SRDF'ed to remote site where they have standby servers. Great for BC but comes with a $ tag.

Interesting we did think about doing this for quick recovery if need be. We are looking at 5 GB devices, not sure if compressing will buy us anything. Will compressing shrink the device size or just the content?

Dali

Seems like the easiest way would be to just clone the LUN on the VNX

You could also compress your ”archived” LUN tehn and save some space there

John;

Did you check this article I posted?  It shows how to set a specific LUN host ID.

How to create a LUN with a matching or specific HOST LUN ID

@jonathanlackman