heartbeat network not sustaining cluster

Hi,

We have been seeing a problem where when the public network becomes
unavailable, the cluster IP and name resources go offline and the cluster
effectively stops. The heartbeat network remains available. The bindings etc
are set correctly.
Should this be the case and what else can I check?

Many thanks

G.

"gjb" <> wrote in message
news:%23MZAaut$...
> Hi,
>
> We have been seeing a problem where when the public network becomes
> unavailable, the cluster IP and name resources go offline and the cluster
> effectively stops. The heartbeat network remains available. The bindings
> etc are set correctly.
> Should this be the case and what else can I check?

If all nodes lose connectivity to the public network, than neither can run
the clustered application or service. The IP Address is a resource that is
required for other resources, such as the Network Name. If the IP Address
resource can't be run on either for lack of connectivity, then the entire
cluster will stop.

So, short answer: Yes, this is expected behaviour.

--
Russ Kaufmann,
MVP, MCSE: Messaging and Security, MCT, MCITP, MCTS and other stuff

ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp