Re: arptables on slave not get released, pls help!!! urgent!!!
Jiang <[email protected]>
| Newsgroups | gmane.linux.highavailability.ultramonkey |
|---|---|
| Message-ID | <[email protected]> |
sorry, configuration error... forgot to link giveip and takeip on this node. On 6/22/06, Jiang <[email protected]> wrote: > Hi, > > I just got a very weird problem, when stop heartbeat on master to > force failover to slave, slave is able to take up all my virtual IPs, > but I lost all the connections to the VIPs. I checked arptables -L -v > -n, it is still showing: > ******************************************************************** > Chain IN (policy ACCEPT 230 packets, 6440 bytes) > pkts bytes target in out source-ip > destination-ip source-hw destination-hw hlen op > hrd pro > 10 280 DROP * * 0.0.0.0/0 > 10.226.200.210 00/00 00/00 any > 0000/0000 0000/0000 0000/0000 > 10 280 DROP * * 0.0.0.0/0 > 10.226.200.220 00/00 00/00 any > 0000/0000 0000/0000 0000/0000 > > Chain OUT (policy ACCEPT 37 packets, 1036 bytes) > pkts bytes target in out source-ip > destination-ip source-hw destination-hw hlen op > hrd pro > 0 0 mangle * bond0 10.226.200.210 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 10.226.200.213 > 0 0 mangle * eth0 10.226.200.210 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 10.226.200.213 > 0 0 mangle * eth1 10.226.200.210 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 172.16.1.20 > 0 0 mangle * eth2 10.226.200.210 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 10.226.200.213 > 0 0 mangle * eth3 10.226.200.210 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 172.16.1.20 > 0 0 mangle * bond1 10.226.200.210 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 172.16.1.20 > 0 0 mangle * bond0 10.226.200.220 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 10.226.200.213 > 0 0 mangle * eth0 10.226.200.220 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 10.226.200.213 > 0 0 mangle * eth1 10.226.200.220 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 172.16.1.20 > 0 0 mangle * eth2 10.226.200.220 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 10.226.200.213 > 0 0 mangle * eth3 10.226.200.220 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 172.16.1.20 > 0 0 mangle * bond1 10.226.200.220 0.0.0.0/0 > 00/00 00/00 any 0000/0000 > 0000/0000 0000/0000 --mangle-ip-s 172.16.1.20 > ********************************************************************* > > By right it should release all these policies. > What could be wrong to have this kind of problem? > > Urgent!! Pls help!! Your help is highly appreciated! > > > -- > Regards, > Jiang > -- Regards, Jiang Lei -- Ultra Monkey - http://www.ultramonkey.org/ To UNSUBSCRIBE, email to [email protected], with a body: unsubscribe ultramonkey-users [email protected] where "[email protected]" is YOUR email address.