topic Re: LUN ID in VMware Solutions Discussions

LUN ID

saranraj456 — Thu, 05 Jun 2025 06:47:46 GMT

Hi All,

Does LUN id in netapp filer is used for any reference purpose ?.if so,how it would refer.

Is it been going to have any influence on host end?

Cheers,

Saran

LUN ID

jacint — Sun, 21 Aug 2011 08:32:09 GMT

Hi,

the host identifies the LUN by the LUN ID:

"A LUN must have a unique identification number (ID) so that the host can identify and access the

LUN."

cheers,

Jacint

LUN ID

arunchak — Sun, 21 Aug 2011 12:28:22 GMT

Yea, Lun id is always used to differentiate the LUNs uniquely.

Hey we can also use the info in this file "/proc/scsi/scsi" to find whether the LUN is from NetApp or whether it is from other vendors with their specific LUN id's (as we were discussing in the post http://communities.netapp.com/message/61532#61532):

[root@warspite ~]# cat /proc/scsi/scsi

Attached devices:

Host: scsi0 Channel: 00 Id: 00 Lun: 00

Vendor: IBM-ESXS Model: CBR036C31210ESFN Rev: DFQG

Type: Direct-Access ANSI SCSI revision: 04

Host: scsi0 Channel: 00 Id: 01 Lun: 00

Vendor: IBM-ESXS Model: ST336607LC FN Rev: B25H

Type: Direct-Access ANSI SCSI revision: 03

Host: scsi0 Channel: 00 Id: 08 Lun: 00

Vendor: IBM Model: 25P3495a S320 1 Rev: 1

Type: Processor ANSI SCSI revision: 02

Host: scsi3 Channel: 00 Id: 00 Lun: 00

Vendor: NETAPP Model: LUN Rev: 7330

Type: Direct-Access ANSI SCSI revision: 04

Host: scsi3 Channel: 00 Id: 00 Lun: 01

Vendor: NETAPP Model: LUN Rev: 7330

Type: Direct-Access ANSI SCSI revision: 04

Host: scsi3 Channel: 00 Id: 00 Lun: 03

Vendor: NETAPP Model: LUN Rev: 7330

Type: Direct-Access ANSI SCSI revision: 04

Thanks,

Arun

Re: LUN ID

saranraj456 — Wed, 27 Mar 2013 03:07:05 GMT

Do we need to have the same LUN ID across ,when we are using LUNs to cluster servers?

Re: LUN ID

jacint — Wed, 27 Mar 2013 12:46:51 GMT

hi,

when you provision a LUN for a Cluster, usually you create an igroup which contains the FC or iSCSI address of the HBAs from all the Cluster nodes. When you provision the LUN and select the appropriate igroup, you'll select the LUN ID, which will be the same for all cluster nodes in this way.

Re: LUN ID

saranraj456 — Wed, 27 Mar 2013 17:50:49 GMT

here i had a seperate igroup for each node in cluster

Re: LUN ID

jacint — Wed, 27 Mar 2013 21:40:09 GMT

I'd recommend to use a single igroup. Here's what SAN Administration Guide says:

"Typically, you want all of the host’s HBAs or software initiators to have access to a LUN. If you are using multipathing software or have clustered hosts,

each HBA or software initiator of each clustered host needs redundant paths to the same LUN. "

LUN ID

saranraj456 — Thu, 28 Mar 2013 14:42:16 GMT

the recommendations are, invidual igroup in my case to map a new LUN should i have to maintain same LUN ID ?

LUN ID

arunchak — Tue, 23 Apr 2013 05:17:25 GMT

Hi,

LUN id is used to identify the LUN uniquely in the mapped Host. What exactly are you trying to achieve here? If you are mapping two LUNs to the same host then do not have same LUN id.

Re: LUN ID

saranraj456 — Thu, 25 Apr 2013 16:45:47 GMT

Arun,

We have a 2 node cluster (active /passive) server with two igroups separately ,in regards to LUN id do we need to do have the same ID for both igroups.If it is not be the same what would be impact.

Saran

Re: LUN ID

arunchak — Mon, 29 Apr 2013 09:29:16 GMT

Hi,

Are you trying to map single LUN to 2 igroups. AFAIK you can have different LUN id there should not be any impact. LUN id is to identify the LUN from host side.

Thanks

Arun

Re: LUN ID

johannbell — Wed, 01 May 2013 02:54:07 GMT

saranraj456, I recommend using the same LUN ID for the same LUN to all hosts in the cluster.

This will prevent confusion and mistakes later. Use the LUN ID as a unique identifier for those hosts to that storage system.

If you end up with the same LUN having multiple IDs across different hosts in the same cluster, you could cause future administrators some major headaches, particularly during DR or failover situations.

Re: LUN ID

saranraj456 — Sun, 12 May 2013 18:20:00 GMT

other than administrative problem , does it have any other implications on the host end.

Saran