I test piranha in a private network 192.168.1.0 following the
piranha howto step by step.
Everything goes very well until it comes to taking up!
primary node eth0 192.168.1.231 eth1 192.168.2.1 default gw 192.168.1.1
backup node eth0 192.168.1.230 eth1 192.168.2.2 default gw 192.168.1.1
when I use piranha to stop lvs on primary node,
the result of "ifconfig" on primary node is only "lo 127.0.0.1" left,
that 's not a problem.
The backup node takes up the configurations,
so it's ip address of eth0 changes from 192.168.1.230 to 192.168.1.231
it comes to the important part :
there is no default gateway in routing table!
I must rerun "route add default gw 192.168.1.1" to make it
able to get outward .(I just don't have so much valid ip address,
so I test it in my private network . If the two nodes have valid ip
addresses, still the default gateway must be reconfigured, else it
could only be seen in the local network.)
And the reconfiguration of default gw is not done by pulse automaticly,
so the taking up of the backup node doesn't solve all the problems.
Thank you for your patience.
Maybe it's my problem.
If so , sorry for bothering you !
Tao Hua <email@example.com>
> The state changes to:
> primary node
> only "lo 127.0.0.1" left when "ifconfig" run.
> (but it doesn't matter, I guess that's the way it goes.)
The real IP address of the node should have been kept intact. Piranha
does not touch it. Perhaps you are mapping things to eth0 instead
It is also possible you are getting hit with a know bug in the kernel,
where removing a VIP from an ethernet device causes all IP
addresses for that device to vanish. This only happens with
odd subnet masks.
> backup node
> eth0 18.104.22.168 ,eth1 192.168.1.1
> (that's the same as former primary node.)
> no default gateway configured
> (it matters a lot, I can olny visit LVS from inside of
> my local network(22.214.171.124).
> I can't visit LVS from outside of my local network.)
Piranha does not configure a default gateway, you should
already have had that defined. The only addresses piranha
"plays" with are those defined in the virtual server or
failover service sections of the config file. Again, if you did have
it defined and it vanished, it is possible you are encountering
a known kernel bug. If so, try using a different subnet mask and
see if you get different behavior.
We would need to see a copy of your lvs config file,
and a "ifconfig" output of both systems before and
after failover to understand what you are seeing.
[Posted from customer's email to me]
Thank you very much.
I've solved the problem!
Mapping the Virtual Server to eth0:1 and the NAT Router to eth1:1
is really really very important,that leaves the real IP address of
the node intact, so the taking up won't change the default gateway.
I didn't think that is important, I thought I've mastered it, so I
didn't do as HOWTO tells me step by step.
Sorry for bothering you with MY mistakes.
[BTW -- it was no bother]