Vadym, etc.,
it is not is not just an issue on multicast setups - the same
thing happens if I set up an environment using unicasts ...
# cl_status hblinkstatus <nodename> eth<n>
returns "up" for every defined node and ethernet interface *except* on the
node you are running the command on, where it returns "dead" (for both eth0
and eth1).
/etc/ha.d/ha.cf looks something like this :-
udpport 694
ucast eth0 AAA.AAA.AAA.10
ucast eth0 AAA.AAA.AAA.11
ucast eth0 AAA.AAA.AAA.12
ucast eth0 AAA.AAA.AAA.13
ucast eth1 BBB.BBB.BBB.10
ucast eth1 BBB.BBB.BBB.11
ucast eth1 BBB.BBB.BBB.12
ucast eth1 BBB.BBB.BBB.13
auto_failback on
node <node-1> <node-2> <node-3> <node-4> <node-5>
ping AAA.AAA.AAA.1
respawn hacluster /usr/lib/heartbeat/ipfail
use_logd yes
crm yes
OS is CentOS 5.x, kernel 2.6.18-164.el5, crm_mon shows "Version: 1.0.9-89bd7..."
> On Nov 10, 2010, at 10:51 AM, Frank Lazzarini wrote:
>
> > > Correct me if I am wrong but you can't check the link of a node on that
> > > same
> > > node ?
> > >
>
> I sure hope not, why?
[ Well, if you are on a linux machine with a configured ethernet, remove the
ethernet cable and run a ping to the IP address assigned to that interface;
then the ping may well work even though the interface is not actually talking
to the outside world - so in that sense you "can't check the link of a node
on that same node", but I guess this is not what Frank meant :-) ]
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
