MSA Storage
1753767 Members
5440 Online
108799 Solutions
New Discussion юеВ

Re: Setting Target ID for LUNs

 
Andrew Carson
New Member

Setting Target ID for LUNs

I've had a look through the forum but couldn't find anything along these lines, so forgive me if this is a previously asked & answered question. Have a blade center with FC2142 HBAs and ESX installed. Does anyone know how to set the TargetID for LUNs presented from a SAN?
TIA.
4 REPLIES 4
Uwe Zessin
Honored Contributor

Re: Setting Target ID for LUNs

You can't do that on a storage array. The target ID (if we are talking about the same thing: vmhbaA:T:L, where T is the target ID) is usually implicitly defined by the SAN topology.

For ESX V2.5 you can use "persistent target binding".

For ESX V3, you can't and don't need to, because it uses some form of "persistent LUN binding". I wrote 'some form', because you need to resignature the VMFS if you later re-map the storage space to a different LUN address.
.
Stephen Kebbell
Honored Contributor

Re: Setting Target ID for LUNs

Hi,

if you mean the Host LUN ID (the L that Uwe mentions from vmhbaA:T:L), you set that on the storage array. For an EVA LUN you can set it when you present the Virtual Disk. Why do you need to set a specifc LUN ID?

Regards,
Stephen
Uwe Zessin
Honored Contributor

Re: Setting Target ID for LUNs

> Why do you need to set a specifc LUN ID?

All VMware ESX V3 servers that access a single VMFS need to see it at the same LUN address.

If you add a server later to share this VMFS, you need to make sure it sees the virtual disk at the same LUN address.
.
Andrew Carson
New Member

Re: Setting Target ID for LUNs

Thanks for the replies, fellas. Yes - it was TargetID (TID) and not host LUn that I was after. I'm not sure if this helps yet - I'll have to pass the information on.