/opt/NetApp/santools/bin/ntap_config_paths ## the path on Solaris may be different
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@netapp.com> 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 District919.250.0052 Mobile
Stetson.Webster@netapp.comLearn how: netapp.com/guarantee
From: Romeo Theriault [mailto:romeotheriault@gmail.com]
Sent: Thursday, January 15, 2009 11:27 AM
To: Webster, Stetson; toasters@mathworks.com
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.
RomeoOn Thu, Jan 15, 2009 at 10:16 AM, Webster, Stetson <Stetson.Webster@netapp.com> 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@netapp.com
Learn how: netapp.com/guaranteeFrom: Romeo Theriault
To: toasters@mathworks.com
Sent: Thu Jan 15 09:49:19 2009
Subject: lun serial questionI 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-4611 jeff.cleverley@avagotech.com