Hi folks,
I have set up a cluster on CentOS 5.2 using /etc/cluster/cluster.conf - and it works fine. It's only purpose is to switch a virtual IP between two routers.
Now the service is running, I can ping the virtual IP from outside - but this virtual IP is not bound to any interface. How does this work? Can I force the cluster to bind it to a certain interface?
I need this because the routing daemon (xorp) does not make use of an ip address that is not bound to an interface.
Any hint or help is appreciated.
Dirk
Okay, I found that ifconfig does not show the virtual IP address, but "ip addr show" shows it bound to an interface. Seems that ifconfig can only handle old style aliases.
dirk
--On 13. Juli 2008 14:28:29 +0200 "Dirk H. Schulz" dirk.schulz@kinzesberg.de wrote:
Hi folks,
I have set up a cluster on CentOS 5.2 using /etc/cluster/cluster.conf - and it works fine. It's only purpose is to switch a virtual IP between two routers.
Now the service is running, I can ping the virtual IP from outside - but this virtual IP is not bound to any interface. How does this work? Can I force the cluster to bind it to a certain interface?
I need this because the routing daemon (xorp) does not make use of an ip address that is not bound to an interface.
Any hint or help is appreciated.
Dirk _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-------------------------------------------------------------- Dirk H. Schulz IT Systems Service Wiesenweg 12, 85567 Grafing Tel. 0 80 92/86 25 68 Fax. 0 80 92/86 25 72 -------------------------------------------------------------- Technik vom Feinsten - und das nötige Tuning
On Sun, Jul 13, 2008 at 10:56 AM, Dirk H. Schulz dirk.schulz@kinzesberg.de wrote:
Okay, I found that ifconfig does not show the virtual IP address
Are you sure?
These are interface aliases, they should show up as a "different" interface such as eth0:0 or eth0:1. If you run "ifconfig" without any parameters, doesn't it show up?
Filipe
Filipe Brandenburger wrote:
On Sun, Jul 13, 2008 at 10:56 AM, Dirk H. Schulz dirk.schulz@kinzesberg.de wrote:
Okay, I found that ifconfig does not show the virtual IP address
Are you sure?
These are interface aliases, they should show up as a "different" interface such as eth0:0 or eth0:1. If you run "ifconfig" without any parameters, doesn't it show up?
with the IP stack in Linux as of kernel 2.4.something, and the 'ip' command, virtual addresses no longer need be associated with virtual interfaces like eth0:1, instead you can `ip addr add eth0 a.b.c.d`
the ifconfig command, written back in the stone ages, is blissfully unaware of this. it really should be deprecated in favor of `ip addr`
John R Pierce wrote:
Okay, I found that ifconfig does not show the virtual IP address
Are you sure?
These are interface aliases, they should show up as a "different" interface such as eth0:0 or eth0:1. If you run "ifconfig" without any parameters, doesn't it show up?
with the IP stack in Linux as of kernel 2.4.something, and the 'ip' command, virtual addresses no longer need be associated with virtual interfaces like eth0:1, instead you can `ip addr add eth0 a.b.c.d`
the ifconfig command, written back in the stone ages, is blissfully unaware of this. it really should be deprecated in favor of `ip addr`
Where is the best documentation on how the ip capabilities map to the files in /etc/sysconfig/network-scripts? Do you have to use the eth0:n syntax there? Also, isn't there some way to describe up vlan trunks and subinterfaces there?
Dirk H. Schulz wrote:
I have set up a cluster on CentOS 5.2 using /etc/cluster/cluster.conf - and it works fine. It's only purpose is to switch a virtual IP between two routers.
Where did you find docs on how to do this? I have set up LVS with piranha but couldn't find anything decent or a tool to set up high availability failover like I did with LVS. All of the cluster suite stuff I read about involves quorums and shared storage etc which is not what I need here. I just need a firewall that will bring up the network gateway address in the event the primary fails.
Thanks!
-
Dirk H. Schulz -
Filipe Brandenburger -
John R Pierce -
Les Mikesell -
Tracy R Reed