Under CentOS 5.9 (PAE kernel), I'm used to seeing an IP alias managed
by heartbeat 2.1.3, as seen from heartbeat's logs, here 'bond0:0':
2014/01/03_17:20:00 INFO: eval ifconfig bond0:0 172.20.242.52
netmask 255.255.0.0 broadcast 172.20.255.255
And as seen by 'ifconfig':
# ifconfig bond0:0
bond0:0 Link encap:Ethernet HWaddr 00:15:5D:0A:3E:D7
inet addr:172.20.242.52 Bcast:172.20.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500
Metric:1
But, on a CentOS 6.5 64-bit box, I'm provisioning, when I configure
heartbeat to manage an IP address as a resource, the IP is bound
to my interface (in this example, 172.20.217.250 is the managed resource.)
# /sbin/ip -o -f inet addr show
1: lo inet 127.0.0.1/8 scope host lo
6: bond0 inet 172.20.240.98/16 brd 172.20.255.255 scope global bond0
6: bond0 inet 172.20.217.250/16 brd 172.20.255.255 scope global secondary
bond0
There is no ip alias on 'bond0:0', and this managed IP is not seen
at all with 'ifconfig'. (It does seem to be receiving traffic.)
I've heard scuttle that Fedora Core is pushing the use of 'ip' over
'ipconfig', but I'm surprised to see ifconfig not reveal this
information at all.
Anyway, my question is: is this behavior (not using IP aliases) a
feature of heartbeat 3.0.x, or is this an artifact of the CentOS
plumbing the heartbeat invokes? I didn't see anything in the
changelog in a quick perusal.
My environment:
# cat /etc/redhat-release
CentOS release 6.5 (Final)
# rpm -q heartbeat
heartbeat-3.0.4-2.el6.x86_64
As per https://bugzilla.redhat.com/show_bug.cgi?id=1028127 I've
installed heartbeat-3.0.4-2 from EPEL. (Wonder why 3.0.5 isn't
available yet?)
Thanks for any feedback you may have...
--
Brian Reichert <[email protected]>
BSD admin/developer at large
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
