Mailing List Archive: Netapp: toasters

lun serial question

Index | Next | Previous | View Threaded

romeotheriault at gmail

Jan 15, 2009, 6:49 AM

Post #1 of 10 (2827 views)
Permalink

lun serial question

I recently became aware of the lun serial command and am wondering if there
is anyway for a client that has said lun or luns presented to them to "see"
this lun serial string. I'm thinking this would be an ideal way (i.e.
script) to find out which lun corresponds to which filesystem/mountpoint on
servers with lots of luns.

Thanks,
--
Romeo Theriault
System Administrator
Information Technology Services

Stetson.Webster at netapp

Jan 15, 2009, 7:16 AM

Post #2 of 10 (2751 views)
Permalink

Re: lun serial question [In reply to]

There are tools in the NetApp Host Utilities that already do this very thing. It is recommended (and on some platforms it's mandatory) that you use this method to connect your systems to the NetApp SAN.

On unix systems, a popular command that I use is:

sanlun lun show -p

Unfortunately, I am not as verse on Windows systems, but I expect something similar (if not the same). Good luck.

Cheers,

Stetson M. Webster
Professional Services Engineer
NCIE-SAN, NCIE-B&R, SNIA-SCSE
NetApp Global Services - Southeast District

919.250.0052 Mobile
Stetson.Webster [at] netapp

Learn how: netapp.com/guarantee

________________________________

From: Romeo Theriault
To: toasters [at] mathworks
Sent: Thu Jan 15 09:49:19 2009
Subject: lun serial question

I recently became aware of the lun serial command and am wondering if there is anyway for a client that has said lun or luns presented to them to "see" this lun serial string. I'm thinking this would be an ideal way (i.e. script) to find out which lun corresponds to which filesystem/mountpoint on servers with lots of luns.

Thanks,
--
Romeo Theriault
System Administrator
Information Technology Services

Justin.Parisi at netapp

Jan 15, 2009, 7:47 AM

Post #3 of 10 (2735 views)
Permalink

RE: lun serial question [In reply to]

I don't see any Windows equivalent commands in the Host Utilities.
Knowing the LUN serial numbers usually isn't as crucial in a Windows
environment.

However, Microsoft has some ways to do this. One thing I found:

http://blogs.msdn.com/adioltean/pages/344588.aspx

Additionally:
http://msdn.microsoft.com/en-us/library/aa383387(VS.85).aspx

But overall, I'd do some searches and maybe engage Microsoft for their
recommendation.

________________________________

From: Webster, Stetson
Sent: Thursday, January 15, 2009 10:17 AM
To: romeotheriault [at] gmail; toasters [at] mathworks
Subject: Re: lun serial question

There are tools in the NetApp Host Utilities that already do this very
thing. It is recommended (and on some platforms it's mandatory) that you
use this method to connect your systems to the NetApp SAN.

On unix systems, a popular command that I use is:

sanlun lun show -p

Unfortunately, I am not as verse on Windows systems, but I expect
something similar (if not the same). Good luck.

Cheers,

Stetson M. Webster
Professional Services Engineer
NCIE-SAN, NCIE-B&R, SNIA-SCSE
NetApp Global Services - Southeast District

919.250.0052 Mobile
Stetson.Webster [at] netapp

Learn how: netapp.com/guarantee

________________________________

From: Romeo Theriault
To: toasters [at] mathworks
Sent: Thu Jan 15 09:49:19 2009
Subject: lun serial question

I recently became aware of the lun serial command and am wondering if
there is anyway for a client that has said lun or luns presented to them
to "see" this lun serial string. I'm thinking this would be an ideal way
(i.e. script) to find out which lun corresponds to which
filesystem/mountpoint on servers with lots of luns.

Thanks,
--
Romeo Theriault
System Administrator
Information Technology Services

Peter.Learmonth at netapp

Jan 15, 2009, 7:49 AM

Post #4 of 10 (2746 views)
Permalink

RE: lun serial question [In reply to]

Hi
Like Stetson said LUN S/N is exposed by the Host Utilities. It's also
available to the operating system and is commonly used for multipathing.
Whether it's available to user or admin commands depends on the OS
and/or MPIO software.

Also, the LUN S/N as reported by the lun serial command is in a kinda
base64 (uses A-Z, a-z,0-9, /, and - to represent 64 possible values for
each digit), and the command in your OS may report in decimal or hex.

For implications of LUN /SN with ESX, see NOW kb33990
(https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb33990)

Share and enjoy!

Peter

________________________________

From: Romeo Theriault [mailto:romeotheriault [at] gmail]
Sent: Thursday, January 15, 2009 6:49 AM
To: toasters [at] mathworks
Subject: lun serial question

I recently became aware of the lun serial command and am wondering if
there is anyway for a client that has said lun or luns presented to them
to "see" this lun serial string. I'm thinking this would be an ideal way
(i.e. script) to find out which lun corresponds to which
filesystem/mountpoint on servers with lots of luns.

Thanks,
--
Romeo Theriault
System Administrator
Information Technology Services

romeotheriault at gmail

Jan 15, 2009, 8:27 AM

Post #5 of 10 (2733 views)
Permalink

Re: lun serial question [In reply to]

Thanks for the reply. We're a unix shop so I don't have to worry about
windows. I was aware that I can get this kind of information from the Host
Utilities but was wondering if there was a way to get the info without
installing Host Utilities. I'd be mainly interested in Linux.

Thanks for the help.

Romeo

On Thu, Jan 15, 2009 at 10:16 AM, Webster, Stetson <
Stetson.Webster [at] netapp> wrote:

> There are tools in the NetApp Host Utilities that already do this very
> thing. It is recommended (and on some platforms it's mandatory) that you use
> this method to connect your systems to the NetApp SAN.
>
> On unix systems, a popular command that I use is:
>
> sanlun lun show -p
>
> Unfortunately, I am not as verse on Windows systems, but I expect something
> similar (if not the same). Good luck.
>
> Cheers,
>
>
>
> Stetson M. Webster
> Professional Services Engineer
> NCIE-SAN, NCIE-B&R, SNIA-SCSE
> NetApp Global Services - Southeast District
>
> 919.250.0052 Mobile
> Stetson.Webster [at] netapp
>
> Learn how: netapp.com/guarantee
>
> ------------------------------
> *From*: Romeo Theriault
> *To*: toasters [at] mathworks
> *Sent*: Thu Jan 15 09:49:19 2009
> *Subject*: lun serial question
> I recently became aware of the lun serial command and am wondering if there
> is anyway for a client that has said lun or luns presented to them to "see"
> this lun serial string. I'm thinking this would be an ideal way (i.e.
> script) to find out which lun corresponds to which filesystem/mountpoint on
> servers with lots of luns.
>
> Thanks,
> --
> Romeo Theriault
> System Administrator
> Information Technology Services
>

--
Romeo Theriault
System Administrator
Information Technology Services

romeotheriault at gmail

Jan 15, 2009, 8:53 AM

Post #6 of 10 (2747 views)
Permalink

Re: lun serial question [In reply to]

>
> Are you getting "FC Partner Path Misconfigured" errors from any of your
> NetApp SAN systems?
>

Yes, actually! But this is another ball of wax. The machines that are
getting these errors have the Host Utilities installed. (Solaris 9). I've
been working with Netapp Support on this and what it comes down to is that
we are in an unsupported configuration. (Veritas VXVM, Veritas VXFS, but
using the Sun HBA drivers, which we have to due to the cards being Sun
branded cards.) To get to a supported configuration (and hopefully get rid
of these errors) I need to upgrade our VXVM to 5.0 and then upgrade the
Host Utilities to a version that supports our config. Oh, what fun.

But..... The linux boxes I'd be interested in using such a script that I
initially asked about are using single pathed iscsi and are not causing any
errors. I'd just like a way to map this info without having to install Host
Utilities.

Romeo

On Thu, Jan 15, 2009 at 11:31 AM, Webster, Stetson <
Stetson.Webster [at] netapp> wrote:

> Are you getting "FC Partner Path Misconfigured" errors from any of your
> NetApp SAN systems? If so, you may want to reconsider your decision. The
> documentation and tools in the Host Utilities will resolve this.
>
>
>
> *Stetson M. Webster**
> *Professional Services Engineer
> NCIE-SAN, NCIE-B&R, SNIA-SCSE
> NetApp Global Services - Southeast District
>
> 919.250.0052 Mobile
> Stetson.Webster [at] netapp
>
> Learn how: netapp.com/guarantee
>
>
>
> [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.html?ref_source=eSig>
>
>
>
>
> *From:* Romeo Theriault [mailto:romeotheriault [at] gmail]
> *Sent:* Thursday, January 15, 2009 11:27 AM
> *To:* Webster, Stetson; toasters [at] mathworks
> *Subject:* Re: lun serial question
>
>
>
> Thanks for the reply. We're a unix shop so I don't have to worry about
> windows. I was aware that I can get this kind of information from the Host
> Utilities but was wondering if there was a way to get the info without
> installing Host Utilities. I'd be mainly interested in Linux.
>
>
> Thanks for the help.
>
> Romeo
>
> On Thu, Jan 15, 2009 at 10:16 AM, Webster, Stetson <
> Stetson.Webster [at] netapp> wrote:
>
> There are tools in the NetApp Host Utilities that already do this very
> thing. It is recommended (and on some platforms it's mandatory) that you use
> this method to connect your systems to the NetApp SAN.
>
> On unix systems, a popular command that I use is:
>
> sanlun lun show -p
>
> Unfortunately, I am not as verse on Windows systems, but I expect something
> similar (if not the same). Good luck.
>
> Cheers,
>
>
>
> Stetson M. Webster
> Professional Services Engineer
> NCIE-SAN, NCIE-B&R, SNIA-SCSE
> NetApp Global Services - Southeast District
>
> 919.250.0052 Mobile
> Stetson.Webster [at] netapp
>
> Learn how: netapp.com/guarantee
> ------------------------------
>
> *From*: Romeo Theriault
> *To*: toasters [at] mathworks
> *Sent*: Thu Jan 15 09:49:19 2009
> *Subject*: lun serial question
>
> I recently became aware of the lun serial command and am wondering if there
> is anyway for a client that has said lun or luns presented to them to "see"
> this lun serial string. I'm thinking this would be an ideal way (i.e.
> script) to find out which lun corresponds to which filesystem/mountpoint on
> servers with lots of luns.
>
> Thanks,
> --
> Romeo Theriault
> System Administrator
> Information Technology Services
>
>
>
>
> --
> Romeo Theriault
> System Administrator
> Information Technology Services
>

--
Romeo Theriault
System Administrator
Information Technology Services

Attachments:

image003.jpg (7.36 KB)

romeotheriault at gmail

Jan 15, 2009, 11:59 AM

Post #7 of 10 (2764 views)
Permalink

Re: lun serial question [In reply to]

>
> /opt/NetApp/santools/bin/ntap_config_paths ## the path on Solaris may be
> different

This file didn't seem to come with my Solaris Host Utilities. Poking around
on netapp site I can only seem to find reference to it in regards to HP-UX.
But I'll poke around a bit more.

Thanks,
Romeo

On Thu, Jan 15, 2009 at 12:21 PM, Jeff Cleverley <
jeff.cleverley [at] avagotech> wrote:

> Romeo,
>
> The partner mismatch doesn't deal with the serial numbers as you mention.
> It is telling you that the file systems are accessing the luns through the
> incorrect path. I get this a lot on my hpux system which use pvlinks for
> failover. All I have to do is run:
>
> /opt/NetApp/santools/bin/ntap_config_paths ## the path on Solaris may be
> different
>
> and it re-orders the disks in the volume group using vgreduce/vgextend
> commands. I wouldn't think this would require a VX* upgrade on anything.
>
> Jeff
>
>
> Romeo Theriault wrote:
>
> Are you getting "FC Partner Path Misconfigured" errors from any of your
>> NetApp SAN systems?
>>
>
> Yes, actually! But this is another ball of wax. The machines that are
> getting these errors have the Host Utilities installed. (Solaris 9). I've
> been working with Netapp Support on this and what it comes down to is that
> we are in an unsupported configuration. (Veritas VXVM, Veritas VXFS, but
> using the Sun HBA drivers, which we have to due to the cards being Sun
> branded cards.) To get to a supported configuration (and hopefully get rid
> of these errors) I need to upgrade our VXVM to 5.0 and then upgrade the
> Host Utilities to a version that supports our config. Oh, what fun.
>
> But..... The linux boxes I'd be interested in using such a script that I
> initially asked about are using single pathed iscsi and are not causing any
> errors. I'd just like a way to map this info without having to install Host
> Utilities.
>
> Romeo
>
>
>
> On Thu, Jan 15, 2009 at 11:31 AM, Webster, Stetson <
> Stetson.Webster [at] netapp> wrote:
>
>> Are you getting "FC Partner Path Misconfigured" errors from any of your
>> NetApp SAN systems? If so, you may want to reconsider your decision. The
>> documentation and tools in the Host Utilities will resolve this.
>>
>>
>>
>> *Stetson M. Webster**
>> *Professional Services Engineer
>> NCIE-SAN, NCIE-B&R, SNIA-SCSE
>> NetApp Global Services - Southeast District
>>
>> 919.250.0052 Mobile
>> Stetson.Webster [at] netapp
>>
>> Learn how: netapp.com/guarantee
>>
>>
>>
>> [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.html?ref_source=eSig>
>>
>>
>>
>>
>> *From:* Romeo Theriault [mailto:romeotheriault [at] gmail]
>> *Sent:* Thursday, January 15, 2009 11:27 AM
>> *To:* Webster, Stetson; toasters [at] mathworks
>> *Subject:* Re: lun serial question
>>
>>
>>
>> Thanks for the reply. We're a unix shop so I don't have to worry about
>> windows. I was aware that I can get this kind of information from the Host
>> Utilities but was wondering if there was a way to get the info without
>> installing Host Utilities. I'd be mainly interested in Linux.
>>
>>
>> Thanks for the help.
>>
>> Romeo
>>
>> On Thu, Jan 15, 2009 at 10:16 AM, Webster, Stetson <
>> Stetson.Webster [at] netapp> wrote:
>>
>> There are tools in the NetApp Host Utilities that already do this very
>> thing. It is recommended (and on some platforms it's mandatory) that you use
>> this method to connect your systems to the NetApp SAN.
>>
>> On unix systems, a popular command that I use is:
>>
>> sanlun lun show -p
>>
>> Unfortunately, I am not as verse on Windows systems, but I expect
>> something similar (if not the same). Good luck.
>>
>> Cheers,
>>
>>
>>
>> Stetson M. Webster
>> Professional Services Engineer
>> NCIE-SAN, NCIE-B&R, SNIA-SCSE
>> NetApp Global Services - Southeast District
>>
>> 919.250.0052 Mobile
>> Stetson.Webster [at] netapp
>>
>> Learn how: netapp.com/guarantee
>> ------------------------------
>>
>> *From*: Romeo Theriault
>> *To*: toasters [at] mathworks
>> *Sent*: Thu Jan 15 09:49:19 2009
>> *Subject*: lun serial question
>>
>> I recently became aware of the lun serial command and am wondering if
>> there is anyway for a client that has said lun or luns presented to them to
>> "see" this lun serial string. I'm thinking this would be an ideal way (i.e.
>> script) to find out which lun corresponds to which filesystem/mountpoint on
>> servers with lots of luns.
>>
>> Thanks,
>> --
>> Romeo Theriault
>> System Administrator
>> Information Technology Services
>>
>>
>>
>>
>> --
>> Romeo Theriault
>> System Administrator
>> Information Technology Services
>>
>
>
>
> --
> Romeo Theriault
> System Administrator
> Information Technology Services
>
>
> --
>
> Jeff Cleverley
> Unix Systems Administrator
> 4380 Ziegler Road
> Fort Collins, Colorado 80525
> 970-288-4611jeff.cleverley [at] avagotech
>
>

--
Romeo Theriault
System Administrator
Information Technology Services

romeotheriault at gmail

Jan 15, 2009, 12:01 PM

Post #8 of 10 (2731 views)
Permalink

Re: lun serial question [In reply to]

Great! This is exactly what I was looking for. Thanks, should be fairly easy
to script too.

On Thu, Jan 15, 2009 at 1:02 PM, Dalvenjah FoxFire <dalvenjah [at] dal>wrote:

> Yup, you can -- the command is scsi_id from the udev packages. Note that
> you have to have sysfs (/sys) mounted and active for this to work.
> Determine the Linux block device name (e.g. /dev/sdc), then replace /dev/
> with /block/ and pass it to scsi_id:
> /sbin/scsi_id -g -u -s /block/sdc360a....
> It's what the dm-multipath software uses to determine which devices are the
> same LUN.
> -dalvenjah
>
> On Jan 15, 2009, at 8:27 AM, Romeo Theriault wrote:
>
> Thanks for the reply. We're a unix shop so I don't have to worry about
> windows. I was aware that I can get this kind of information from the Host
> Utilities but was wondering if there was a way to get the info without
> installing Host Utilities. I'd be mainly interested in Linux.
>
> Thanks for the help.
>
> Romeo
>
> On Thu, Jan 15, 2009 at 10:16 AM, Webster, Stetson <
> Stetson.Webster [at] netapp> wrote:
>
>> There are tools in the NetApp Host Utilities that already do this very
>> thing. It is recommended (and on some platforms it's mandatory) that you use
>> this method to connect your systems to the NetApp SAN.
>>
>> On unix systems, a popular command that I use is:
>>
>> sanlun lun show -p
>>
>> Unfortunately, I am not as verse on Windows systems, but I expect
>> something similar (if not the same). Good luck.
>>
>> Cheers,
>>
>>
>>
>> Stetson M. Webster
>> Professional Services Engineer
>> NCIE-SAN, NCIE-B&R, SNIA-SCSE
>> NetApp Global Services - Southeast District
>>
>> 919.250.0052 Mobile
>> Stetson.Webster [at] netapp
>>
>> Learn how: netapp.com/guarantee
>>
>> ------------------------------
>> *From*: Romeo Theriault
>> *To*: toasters [at] mathworks
>> *Sent*: Thu Jan 15 09:49:19 2009
>> *Subject*: lun serial question
>> I recently became aware of the lun serial command and am wondering if
>> there is anyway for a client that has said lun or luns presented to them to
>> "see" this lun serial string. I'm thinking this would be an ideal way (i.e.
>> script) to find out which lun corresponds to which filesystem/mountpoint on
>> servers with lots of luns.
>>
>> Thanks,
>> --
>> Romeo Theriault
>> System Administrator
>> Information Technology Services
>>
>
>
>
> --
> Romeo Theriault
> System Administrator
> Information Technology Services
>
>
>

--
Romeo Theriault
System Administrator
Information Technology Services

romeotheriault at gmail

Jan 15, 2009, 12:13 PM

Post #9 of 10 (2733 views)
Permalink

Re: lun serial question [In reply to]

Thanks for the reply and clarification on the FC path misconfiguration
errors". I understand that the error is caused by the client using the
secondary path that goes through the cluster partners head, but I just can't
figure out why and how to stop it. Here is why:

The DMP (veritas vxdmp) is setup with two paths, one primary and another
secondary and is vxdmp policy set to to use round-robin, so you would think
that the partner path issue would be happening all the time on all luns, but
it's not. It is only happening on a handful of them and only on some of the
servers and all the Solaris servers have the same vxdmp configs.

The other really bizarre thing is that I tried changing the DMP to use
single-active during a maintenance window and about half of the luns would
not even mount. (diskgroups went offline and disabled). So I had to set the
dmp policy back to round-robin to even get them to mount again.

So at this point I'm kinda thinking that the version of VXVM I'm running has
some bugs in it that would hopefully be fixed by a newer version. I'm just
running out of ideas and Netapp support has been of very little help at all.

Thanks for the link and tips on udev, lun serials too.

Romeo

On Thu, Jan 15, 2009 at 1:59 PM, <jemans [at] xs4all> wrote:

>
> Hi,
>
> Regarding "FC path misconfigured errors":
>
> Both your cluster filers present their own luns but also their partner
> luns on each FC port, this means your clients will see double the amount
> of paths for each LUN. To prevent the error from occurring you should make
> sure all clients *ONLY* go through paths that are local to a filer.
>
> Example:
> filer1
> LunA
> LunB
>
> filer2
> LunC
> LunD
>
> Client X sees LunA and LunC through both filers. LunA should *ONLY* be
> accessed through filer1 although it is also available through filer1. The
> reverse is true for LunC. You should configure this on the client not on
> the filer.
>
> Changing your config to a supported one will not by itself do anything,
> except that maybe NetApp will then help you fix it.
>
> As to the other issue on linux and seeing serial numbers, investigate
> "udev" and "udevinfo":
> http://www.reactivated.net/writing_udev_rules.html
>
> Also checkout the sysfs file system you can use this to figure out which
> device has which serial.
>
> You can write rules to create file devices like:
> /dev/scsi/lun-serialX
>
> That way the path is always unique for that LUN. You can then fdisk
> /dev/scsi/lun-serialX or whatever.
>
> Regards,
>
> Johan
>

--
Romeo Theriault
System Administrator

Christopher.Naddeo at netapp

Jan 16, 2009, 8:16 AM

Post #10 of 10 (2688 views)
Permalink

RE: lun serial question [In reply to]

Make sure you have the right DMP Array Support Library/Array Policy
Modules (ASL/APM) libraries installed on your host. Else DMP and the
device discovery engine will not properly claim and manage the array.

You can get these from the Symantec.com support website.

--Chris

Chris Naddeo
Consulting Systems Engineer
U.S. Eastern Area - Northeast Region

NetApp
Moblie: 610-724-6244
cnaddeo [at] netapp
<mailto:Christopher.Naddeo [at] netapp> www.netapp.com
<http://www.netapp.com/>

________________________________

From: Romeo Theriault [mailto:romeotheriault [at] gmail]
Sent: Thursday, January 15, 2009 3:14 PM
To: jemans [at] xs4all; toasters [at] mathworks
Subject: Re: lun serial question

Thanks for the reply and clarification on the FC path misconfiguration
errors". I understand that the error is caused by the client using the
secondary path that goes through the cluster partners head, but I just
can't figure out why and how to stop it. Here is why:

The DMP (veritas vxdmp) is setup with two paths, one primary and another
secondary and is vxdmp policy set to to use round-robin, so you would
think that the partner path issue would be happening all the time on all
luns, but it's not. It is only happening on a handful of them and only
on some of the servers and all the Solaris servers have the same vxdmp
configs.

The other really bizarre thing is that I tried changing the DMP to use
single-active during a maintenance window and about half of the luns
would not even mount. (diskgroups went offline and disabled). So I had
to set the dmp policy back to round-robin to even get them to mount
again.

So at this point I'm kinda thinking that the version of VXVM I'm running
has some bugs in it that would hopefully be fixed by a newer version.
I'm just running out of ideas and Netapp support has been of very little
help at all.

Thanks for the link and tips on udev, lun serials too.

Romeo

On Thu, Jan 15, 2009 at 1:59 PM, <jemans [at] xs4all> wrote:

Hi,

Regarding "FC path misconfigured errors":

Both your cluster filers present their own luns but also their partner
luns on each FC port, this means your clients will see double the amount
of paths for each LUN. To prevent the error from occurring you should
make
sure all clients *ONLY* go through paths that are local to a filer.

Example:
filer1
LunA
LunB

filer2
LunC
LunD

Client X sees LunA and LunC through both filers. LunA should *ONLY* be
accessed through filer1 although it is also available through filer1.
The
reverse is true for LunC. You should configure this on the client not on
the filer.

Changing your config to a supported one will not by itself do anything,
except that maybe NetApp will then help you fix it.

As to the other issue on linux and seeing serial numbers, investigate
"udev" and "udevinfo":
http://www.reactivated.net/writing_udev_rules.html

Also checkout the sysfs file system you can use this to figure out which
device has which serial.

You can write rules to create file devices like:
/dev/scsi/lun-serialX

That way the path is always unique for that LUN. You can then fdisk
/dev/scsi/lun-serialX or whatever.

Regards,

Johan

--
Romeo Theriault
System Administrator

Attachments:

image001.jpg (1.55 KB)

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads