> Hey > I need to make a strange config: two ips, one side is standard - eth1 on > host A will get an alias ip, but the other one (B) is tricky. > B has eth1 which is not really on the right network, but I also have vlan > interface eth1.442 which is there. What I'd like to set up is ip resource > bringing eth1.442 up with it's ip when it's needed - not an alias. > What I currently do is: > - host A: eth1: ..0.10 + ip resources (..0.40 / ..0.41) > - host B: eth1.442: ..0.42 + ip resources (..0.40 / ..0.41) and eth1: > ..1.1 > > but the ..0.42 address on B is not used for anything there - I would like > to get rid of it. Problem is that, if there's no interface with ip in > ..0.0/24 subnet, heartbeat won't assign alias ip to the eth1.442 > interface. > > I've tried forcing "nic" attribute in resource as well as setting up > eth1.442 without ip at all, but none of that helped. Google doesn't help > here either. > Is there any good solution for that? Or should I just keep that useless ip > assigned?
Ive been using static /32 routes Keep an ip address on the interface you want the ip to end up on, any ip address. (linux seems to need any ip address up on the interface to route to it). Heartbeat will use the most direct route to the IP it is managing to determine which interface to use. So then ip route add x.x.x.x/32 dev eth1.442 where x.x.x.x is the ip your trying to get heartbeat to add on a different interface. Do so before starting heartbeat and it should follow that route to the device. Kevin Karsh _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
