On 12/01/2010 03:52 PM, Raoul Bhatia [IPAX] wrote:
> hi,
> 
> i have a cluster with an internal ip address and several clustered
> public service ips.
> e.g.
> 
>> interface   ip address
>> eth0        192.168.1.100/24 = internal management/cluster ip
>> eth0.12     a.b.c.d/24       = service ip
> 
> to make the public ip reachable, i use:
> 
> 
>> /sbin/ip rule add from a.b.c.0/24 table 12
>> /sbin/ip route add default dev eth0 via a.b.c.1 table 12
> 
> if i issue this by hand, it works perfectly fine.
> 
> right now, i'm using something like this for the second part:
>> primitive dbiproute ocf:heartbeat:Route \
>>         params device="eth0.1112" gateway="93.189.24.193" table="12" 
>> destination="default" \
>>         op monitor interval="10"
> 
> 
> what i'm thinking about:
> 
> 1. issue "/sbin/ip rule add from a.b.c.0/24 table 12" upon
>    reboot/firewall setup (my current solution); or
> 2. create ocf:heartbeat:Iprule - similar to ocf:heartbeat:Route; or
> 3. adapt ocf:heartbeat:Route to handle the rule.
> 
> what would you guys do?

anyone?

thanks,
raoul
-- 
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc.          email.          [email protected]
Technischer Leiter

IPAX - Aloy Bhatia Hava OG          web.          http://www.ipax.at
Barawitzkagasse 10/2/2/11           email.            [email protected]
1190 Wien                           tel.               +43 1 3670030
FN 277995t HG Wien                  fax.            +43 1 3670030 15
____________________________________________________________________
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Reply via email to