hello managers,
My original query was :
i have installed
Trucluster software ver 1.6 on a
Digital Alpha 4100 server with
Digital Unix 4.0f as the operating system.
Two 4100 servers participate on my Trucluster environment.
I have created three services favoured to first system and three
services favoured to second system.
The failover of services is WORKING FINE when one of the server is
shutdown.
but if any one of the system goes out of the network the failover DOES
NOT take place.
of cource i will not be able to access the service from any client where
the service(NFS) is locally mounted. it just keeps seeking.
Thanks to the following people who took time to reply to me,
Davis, Alan <Davis_at_Tessco.Com>
Wolf Dieter Brandt <wolf_at_chaos.gwdg.de>
Antonio Urbano <a.urbano_at_mailcity.com>
alan.garde_at_transport.uk.eds.com
I think Alan Garde got my problem, his reply was
###################
What network cards are you using? Are they DE500's and if so which
model?
If I remember them the right way round, the DE500-AA card's don't detect
the
network link dropping, so the server will sit there thinking everything
is
happy. DE500-BA's can detect network dropout between it and the hub,
and
these should failover.
The solution for a DE500-AA is have a script sitting there pinging
router's,
etc, and if the network disappears, reboot/failover.
Alan
##################
In fact it was the problem with the nic, particularly when it was
configured in 100mbps/fullduplex
for all other combination ie 10/half, 10/full & 100/half the cluster
started working as expected in
case of nic failure. But our requirement was 100/full, therefore i had
to write a script to check for the
nic status and do a manual relocation in case of nic failure.
cheers
umapathy
Received on Tue Sep 07 1999 - 04:54:52 NZST