|
|
You're in the
sql server clustering
group:3-Node Stretch SQL Cluster - Node 1 Ping/Name resolution failure - ANyone ever get this???
sql server clustering:
Cheers, Rod MVP - Windows Server - Clustering http://www.nw-america.com - Clustering [quoted text, click to view] "Barry Lynch" <allspammustdie@yahoo.com> wrote in message news:ce2r7102pv5@news1.newsguy.com... > OK - Hi all > I have an irritating problem with a cluster and perhaps some of you can > short circuit it for me... > > Environment > Windows Server 2003 > Sql Server 2000 EE - SPK 3 > 3 node stretch cluster - only 3rd node is stretched > > Problem Summary... > Node 1 (lets say 10.0.0.1) is ocassionally losing it ability to repond to > ping/name resolve. Trace route is failing one hop before reaching it. > However if we fail over to node 2 and back again all is ok for a random > period of time and then it fails to respond again > We are now leaving Node 2 as the Active node and witing to see if it happens > on node 2 also - if it does then I imagine the stakes will rise considerably > ;-( > > Things to Date... > All resources seem to be correctly configured and assigned to the correct > groups > The IP address is correct and unique for the SQL V Server resource > All n/w cards are functional > Nothing obvious in the event logs > The node responds to a ping locally (that is from Node1 over an RDP > session) without resorting to failover even though it is failing from an > external ping. > > Other... > Not sure if this is related but at installation time I could not build the 3 > nodes at once. I had to build Node 1 then add Node 2, then add Node 3. > Probably a red herring > > Anyone ever have this or shed any light. > Should I be talking to the networking geniuses? > > Thanks in advance > > Barry Lynch > > >
OK - Hi all
I have an irritating problem with a cluster and perhaps some of you can short circuit it for me... Environment Windows Server 2003 Sql Server 2000 EE - SPK 3 3 node stretch cluster - only 3rd node is stretched Problem Summary... Node 1 (lets say 10.0.0.1) is ocassionally losing it ability to repond to ping/name resolve. Trace route is failing one hop before reaching it. However if we fail over to node 2 and back again all is ok for a random period of time and then it fails to respond again We are now leaving Node 2 as the Active node and witing to see if it happens on node 2 also - if it does then I imagine the stakes will rise considerably ;-( Things to Date... All resources seem to be correctly configured and assigned to the correct groups The IP address is correct and unique for the SQL V Server resource All n/w cards are functional Nothing obvious in the event logs The node responds to a ping locally (that is from Node1 over an RDP session) without resorting to failover even though it is failing from an external ping. Other... Not sure if this is related but at installation time I could not build the 3 nodes at once. I had to build Node 1 then add Node 2, then add Node 3. Probably a red herring Anyone ever have this or shed any light. Should I be talking to the networking geniuses? Thanks in advance Barry Lynch
[quoted text, click to view] >-----Original Message----- >What are you using to stretch the cluster? > >Cheers, > >Rod > >MVP - Windows Server - Clustering >http://www.nw-america.com - Clustering > >"Barry Lynch" <allspammustdie@yahoo.com> wrote in message >news:ce2r7102pv5@news1.newsguy.com... >> OK - Hi all >> I have an irritating problem with a cluster and perhaps some of you can >> short circuit it for me... >> >> Environment >> Windows Server 2003 >> Sql Server 2000 EE - SPK 3 >> 3 node stretch cluster - only 3rd node is stretched >> >> Problem Summary... >> Node 1 (lets say 10.0.0.1) is ocassionally losing it ability to repond to >> ping/name resolve. Trace route is failing one hop before reaching it. >> However if we fail over to node 2 and back again all is ok for a random >> period of time and then it fails to respond again >> We are now leaving Node 2 as the Active node and witing to see if it >happens >> on node 2 also - if it does then I imagine the stakes will rise >considerably >> ;-( >> >> Things to Date... >> All resources seem to be correctly configured and assigned to the correct >> groups >> The IP address is correct and unique for the SQL V Server resource >> All n/w cards are functional >> Nothing obvious in the event logs >> The node responds to a ping locally (that is from Node1 over an RDP >> session) without resorting to failover even though it is failing from an >> external ping. >> >> Other... >> Not sure if this is related but at installation time I could not build the >3 >> nodes at once. I had to build Node 1 then add Node 2, then add Node 3. >> Probably a red herring >> >> Anyone ever have this or shed any light. >> Should I be talking to the networking geniuses? >> >> Thanks in advance >> >> Barry Lynch >> >> >> > > >. >Barry, I saw this problem before and it was because a client had the properties of the NIC set to update the DNS of the IP information & the servers were behind a BIgIP (NAT). This was hell on resolving and pings!
Hi Rodney et al
That's very interesting - I will check tomorrow and let you know how I get on Thanks Barry [quoted text, click to view] "Rodney" <anonymous@discussions.microsoft.com> wrote in message news:46e301c4734d$94d1f400$a401280a@phx.gbl... > > >-----Original Message----- > >What are you using to stretch the cluster? > > > >Cheers, > > > >Rod > > > >MVP - Windows Server - Clustering > >http://www.nw-america.com - Clustering > > > >"Barry Lynch" <allspammustdie@yahoo.com> wrote in message > >news:ce2r7102pv5@news1.newsguy.com... > >> OK - Hi all > >> I have an irritating problem with a cluster and perhaps > some of you can > >> short circuit it for me... > >> > >> Environment > >> Windows Server 2003 > >> Sql Server 2000 EE - SPK 3 > >> 3 node stretch cluster - only 3rd node is stretched > >> > >> Problem Summary... > >> Node 1 (lets say 10.0.0.1) is ocassionally losing it > ability to repond to > >> ping/name resolve. Trace route is failing one hop > before reaching it. > >> However if we fail over to node 2 and back again all is > ok for a random > >> period of time and then it fails to respond again > >> We are now leaving Node 2 as the Active node and witing > to see if it > >happens > >> on node 2 also - if it does then I imagine the stakes > will rise > >considerably > >> ;-( > >> > >> Things to Date... > >> All resources seem to be correctly configured and > assigned to the correct > >> groups > >> The IP address is correct and unique for the SQL V > Server resource > >> All n/w cards are functional > >> Nothing obvious in the event logs > >> The node responds to a ping locally (that is from Node1 > over an RDP > >> session) without resorting to failover even though it > is failing from an > >> external ping. > >> > >> Other... > >> Not sure if this is related but at installation time I > could not build the > >3 > >> nodes at once. I had to build Node 1 then add Node 2, > then add Node 3. > >> Probably a red herring > >> > >> Anyone ever have this or shed any light. > >> Should I be talking to the networking geniuses? > >> > >> Thanks in advance > >> > >> Barry Lynch > >> > >> > >> > > > > > >. > >Barry, > > I saw this problem before and it was because a client had > the properties of the NIC set to update the DNS of the IP > information & the servers were behind a BIgIP (NAT). This > was hell on resolving and pings! > > Good Luck, Rodney
To do a geographically dispersed cluster, you need to have
a solution that is in the Windows Catalog. How is the
[quoted text, click to view]
"Allan Hirt" <anonymous@discussions.microsoft.com> wrote in message news:<520d01c47405$998d2880$a301280a@phx.gbl>... > To do a geographically dispersed cluster, you need to have > a solution that is in the Windows Catalog. How is the > third connected to a SAN? I assume it is mirrored ... Hi there Allan The cluster is implemented as a VLAN over fibre so long as the ping time to the stretched node is under 1500 ms (If I remember correctly could be a differnt value - its 3am) then the cluster is viable - this part works perfectly With regard to this problem I'm beginning to work round to a mixture of DNS and AD upgrade issues Regards
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |