rboyd (AT) onlinemicrosoft (DOT) com (Rand Boyd [MSFT]) wrote in message news:<#of5eELTEHA.496 (AT) cpmsftngxa10 (DOT) phx.gbl>...
Quote:
I would assume that the cluster service is connecting over the private
network. The major thing that will cause a failover to initiate is the
cluster service cannot connect to SQL Server. When say it cannot failover
does it try. In other words, does SQL Server shut down and not failover or
does SQL Server stay on line.
Rand
This posting is provided "as is" with no warranties and confers no rights. |
I found the problem. None of the nodes can send ICMP messages to the
default gateway (disabled by the network admin.). When a network cable
is disabled on the active node, the following happens:
-both cluster nodes then test network connectivity by using Internet
Control Message Protocol (ICMP) echo requests to determine whether
they can connect to at least one external host. An external host is
represented by an IP address that has the following characteristics:
--It is not local to either cluster node. For example, it is not a
cluster virtual IP address.
--It is on the same client-access network subnet as both cluster
nodes.
--It currently exists as a destination address in the routing table of
either cluster node, and the routing interface is the corresponding
local client-access cluster network interface. Or it is currently
present as an active TCP connection for either cluster node.
-The default gateway is typically used as an external host because it
meets all three of these characteristics. Since no other computers are
on the DMZ and the only computer that the cluster nodes can send ICMP
messages was the default gateway, both public network connections had
the disconnected status.
Thank you all for trying.
Sas