Hi gang,
I'm calling for some help from all you SAN admins... Since we have another group here that provisions storage, we're having issues speaking the same language. Does anyone know how to present a new LUN with a specific LUN ID (say 20) to an ESX cluster? Where is this setting made?
I guess I'd better share that we're using an EMC Symmetrix DMX3 array.
Thanks for the suggestions!
Theo Merian
Carving out LUNs is almost the same procedure across all SAN systems. You pick the storage array and create a RAID group and than create LUNs under your RAID group. Usually you create 400-600GB LUN size standard. You have two choices to present with RDM or VMFS LUN to ESX host. Make sure you present with the correct LUN ID and also your WWN matches otherwise it will not be visible. Once you presented on the Navisphere console, you can rescan the storage and add LUNs using VI Client ->Configuration->Storage Adapters and also click on "Storage" as well and if presented correctly you will see those LUNs listed and add them. I would prefer to specific DMX & Symmetrix model how to present LUNs in ESX. Your storage admin should know this on the fly.
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Regards,
Stefan Nguyen
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant
Here's a step by step guides how to present it on Clarrion but should be similiar.
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Regards,
Stefan Nguyen
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant
Thanks for the info Stefan.
We can provision the storage without porblems - the issue is with setting the LUN ID that is shown in the VIC for the storage. And I'm told that Clariion and Symmetrix was fairly different in setup/config.
Theo
I got this from another site, but hopefully it's what you need:
The Host ID (or HLU) is assigned when a LUN is assigned to a storage group. If you do not specify a host ID when you assign the LUN to the storage group, it will be assigned automatically starting with zero. If you want to change it once the LUN assignment has been applied, you will need to remove the LUN from the storage group and apply changes and then re-add it, adjust the host id and apply change.
-KjB
Hi,
a DMX provides multiple ways to fulfill your request.
First of all, your storage admins could add your LUN with the ID 20 to the FA ports your ESX Host is connected to.
Of course this does only work if that LUN ID isn't used on these FA's.
The other way to fulfill your request is that your storage admins use available masking options.
A DMX could present a LUN ID a multiple time on the same FA port, based on the HBA WWN.
They need to perform the following commands.
symmask -sid SymmetrixID[/i] -wwn WWN of your HBA[/i] -dir used FA[/i] -p FA port[/i] add devs SymDev1,SymDev2,....[/i] -lun ID1,ID2,.....[/i][/b]
symmask -sid SymmetrixID[/i] refresh[/b]
Replace the [i]italic[/b][/i] parts of the command with valid informations.
Ghost,
That command may prove to be useful. However, won't it become a mile long when your cluster grows to 100 LUNs or more? Or am I interpreting the command wrong? It looks to me that is needs to include every LUN (not just new ones) when executed... Maybe it's just me...
Theo
Theo,
as usually, it depends on your request.
The posted command grant your HBA access to a symmetrix device and define a LUN ID.
It's only needed for new devices, you don't need to add already granted devices to your list.
If your talking about the initial device masking operation for an ESX Hosts with 100+ LUN's, each of them with a user defined LUN ID, you're right.
But nobody would do so, because you can't really organize a SAN using LUN ID's.
Hope this helps a bit.