network failover on cluster

  • Thread starter Thread starter kelvin
  • Start date Start date
K

kelvin

I installed a cluster on win2k with 2 nodes connected to
external storage. If you power off a server everything
fails over to the second server fine. But if you just
unplug the network cable from the first node all that
fails over to the 2nd server is the cluster group(cluster
name, ip address and quorum drive). The disk groups(4
disk groups) do not fail over. I've disable network
teaming thinking that could cause problems but no luck.
There is 2 nics on each server. One for the private
(heartbeat) and one for the public. The 2 servers are
configured exactly along with there nics. Nothing is auto-
negotiating.

Any help is greatly appreciated
 
kelvin said:
I installed a cluster on win2k with 2 nodes connected to
external storage. If you power off a server everything
fails over to the second server fine. But if you just
unplug the network cable from the first node all that
fails over to the 2nd server is the cluster group(cluster
name, ip address and quorum drive). The disk groups(4
disk groups) do not fail over. I've disable network
teaming thinking that could cause problems but no luck.
There is 2 nics on each server. One for the private
(heartbeat) and one for the public. The 2 servers are
configured exactly along with there nics. Nothing is auto-
negotiating.

Any help is greatly appreciated
Click to expand...

It's working fine. I'm assuming that all that exists in your disk groups
are the disks themselves. Since disks aren't dependant on a network to
function, a network failure will not cause the disks themselves to move.

Add an IP resource to a disk group and then unplugging the network cable
will cause the IP resource to fail and it will move the group to the other
node.
 
Hi Kelvin,
When you create a new group you are in essence beginning the creation of a
new virtual server. So you have to give it a new unique IP and a new unique
Network Name. Then users can access the virtual server. The Cluster group
(cluster IP, Network Name and Quorum dirve) should never be used for
anything other than managing the cluster and for the existance of the
cluster.

Cluster group should not be tied to any other group for the following
reasons-

According to: 168948 Information About the Cluster Group
http://support.microsoft.com/?id=168948

"The cluster group contains resources that are related to cluster
administration only and are considered core resources. If you add
additional resources to the group, you may not be able to administer the
cluster effectively. If resources in the cluster group fail, failover may
be triggered or you may not be able to administer the cluster effectively.
Therefore, Microsoft recommends that the quorum resource remain in a group
that has core resources only.

For best results and high availability of the cluster, do not add resources
to the cluster group. Instead, put additional resources in other groups as
appropriate."

280345 Quorum Drive Configuration Information
http://support.microsoft.com/?id=280345

"At a minimum, you must create at least one physical drive for the quorum
disk and a separate physical drive for data. Each drive must be formatted
as NTFS."

--
Curtis Koenig
Support Professional
Microsoft Clustering Technologies Support

Microsoft Certified Systems Engineer
Microsoft Certified Systems Engineer - Security

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!
--------------------
 
Back
Top