What would be the impact of running in this state? Is this just an issue for cluster takeovers/failover?
On Sat, Jan 31, 2009 at 11:18 PM, Webster, Stetson < Stetson.Webster@netapp.com> wrote:
I personally went through this problem about a year ago. At the time when I remedied it, I was not serving data. Luckily, it was in the beginning stages of my implementation. Though I don't remember if both controllers were brought down, my circumstances were such that it didn't matter.
*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/guarantee
[image: guarantee-email-sig2]http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.html?ref_source=eSig
*From:* Linux Admin [mailto:sysadmin.linux@gmail.com] *Sent:* Sunday, February 01, 2009 12:09 AM
*To:* Webster, Stetson *Cc:* NetApp Toasters List *Subject:* Re: Local FCP nodename does not match the cluster partner's FCP nodename.
Thanks again Stetson, great help!!!
Did anyone in the group ever remedy this bug manually: Do I need to run "fcp stop/start" on both nodes?
On Sat, Jan 31, 2009 at 10:58 PM, Webster, Stetson < Stetson.Webster@netapp.com> wrote:
You can change either to the other. The idea is to get them to match, so it doesn't matter which one. I believe there will be an outage. I would not recommend trying it while serving live data. I cannot comfortably tell you to do a failover to change it either.
*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/guarantee
[image: guarantee-email-sig2]http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.html?ref_source=eSig
*From:* Linux Admin [mailto:sysadmin.linux@gmail.com] *Sent:* Saturday, January 31, 2009 11:53 PM *To:* Webster, Stetson *Cc:* NetApp Toasters List *Subject:* Re: Local FCP nodename does not match the cluster partner's FCP nodename.
Stetson,
Thanks!!!!
Quick follow up to you and the group:
It says:
In such a case, the user must run an "fcp nodename" command on the partner and
obtain the partner's nodename. Update the local head's nodename (WWN) with the
partner's nodename using the "fcp set nodename WWN". Then, verify that it is
set with "fcp nodename" on the local head. Then run "fcp start" to start the fcp
service.
netapp01> fcp nodename
Fibre Channel nodename: 50:xx:xx:xx:xx:xx:xx:xx
netapp02> fcp nodename Fibre Channel nodename: 50:yy:yy:yy:yy:yy:yy:yy
Which one do I set with "fcp set" command: netapp1 and netapp2. Does it cause outage? (fcp start?)
On Sat, Jan 31, 2009 at 10:42 PM, Webster, Stetson < Stetson.Webster@netapp.com> wrote:
Try this:
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=202390
*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/guarantee
[image: guarantee-email-sig2]http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.html?ref_source=eSig
*From:* Linux Admin [mailto:sysadmin.linux@gmail.com] *Sent:* Saturday, January 31, 2009 11:23 PM *To:* NetApp Toasters List *Subject:* Local FCP nodename does not match the cluster partner's FCP nodename.
Ho folks
What does this error means and how do I remedy it?
