Hi there,
I am having a problem with my cluster in which one the IP addresses assigned to
the members is not reachable from different networks.
My virtual IP address as you can see below is 192.168.33.183
192.168.33.210 and 192.168.33.209 belong to my hosts.
pintraweb02:~ #
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 1000
link/ether 00:50:56:91:01:7c brd ff:ff:ff:ff:ff:ff
inet 192.168.33.210/24 brd 192.168.33.255 scope global eth0
inet 192.168.33.183/24 brd 192.168.33.255 scope global secondary eth0
pintraweb01:~ #
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 1000
link/ether 00:50:56:91:01:7b brd ff:ff:ff:ff:ff:ff
inet 192.168.33.209/24 brd 192.168.33.255 scope global eth0
Other hosts within the 192.168.33.0/24 network can ping all three IP addresses.
However, if I grab a host from a different network (i.e. 10.0.0.1) I can ping
only two of the IP addresses listed above.
Interesting enough, after a failover, if I clear the physical address table of
my switch pintraweb02 and pintraweb01 are connected to, I can effectively ping
all three IP addresses again.
Have anyone come across with this problem?
Is there any special configuration that I need to apply in order to avoid this?
I am currently using Corosync Cluster Engine, version '1.4.5' Copyright (c)
2006-2009 Red Hat, Inc.
Thank you very much in advance.
Miguel.-
________________________________
CONFIDENTIALITY - The information contained in this email is confidential. If
you are not an authorised recipient of this message please contact the sender
immediately by reply email and destroy/delete the email from your computer. Any
unauthorised use or reproduction of this email is strictly prohibited.
DISCLAIMER - Unless specifically indicated otherwise, the views and opinions
expressed in this email are those of the sender and not of UXC. Whilst UXC
endeavours to protect its computers and network from computer viruses, UXC does
not warrant that this email or any attachments are free of viruses or errors.
You should virus scan and otherwise verify any information contained in this
email.
_______________________________________________
discuss mailing list
[email protected]
http://lists.corosync.org/mailman/listinfo/discuss
