Forum Discussion
NimbostratusPriority group activation with multiple gateway pool members
Hi Team,
My requirement is to create secondary gateway(ISP) if primary goes down. Secondary should not be used as long as primary is up. I think with the help of priority group activation i can accomplish it. Created a gateway pool and assign transparent monitor for pool. So below is summary :
- added in the gateway_pool with 2 members + priority group (gateway A has higher priority)
- added default route to use gateway_pool
So how does my route table entry loo like ? Will it show both Gateway A and B or only Gateway A ?
I wanted to make sure there is only 1 GW as the default even though there are 2 pool members/Gws. I do not want traffic to be send out of both GWs ( thus setting up priority activation in the pool).
Is it possible ?
Leonardo_SouzaCirrocumulus
"So how does my route table entry loo like ? Will it show both Gateway A and B or only Gateway A?"
[root@LABBIGIP1:Active:Disconnected] config netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.0.0.254 0.0.0.0 UG 0 0 0 external 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 external 127.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 tmm 127.7.0.0 127.1.1.253 255.255.0.0 UG 0 0 0 tmm 127.20.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tmm_bp 172.16.0.0 0.0.0.0 255.255.255.0 U 0 0 0 internal 192.168.255.0 0.0.0.0 255.255.255.0 U 0 0 0 mgmt [root@LABBIGIP1:Active:Disconnected] config tmsh show net route ---------------------------------------------------------------------------------------- Net::Routes Name Destination Type NextHop Origin ---------------------------------------------------------------------------------------- route_default default gw 10.0.0.254 static 1500 127.20.0.0/16 127.20.0.0/16 interface tmm_bp connected 172.16.0.0/24 172.16.0.0/24 interface /Common/internal connected 10.0.0.0/24 10.0.0.0/24 interface /Common/external connected 127.1.1.0/24 127.1.1.0/24 interface tmm connected ff02:ffc::/64 ff02:ffc::/64 interface /Common/vlan1 connected fe80::%vlan4092/64 fe80::%vlan4092/64 interface /Common/vlan1 connected fe80::%vlan4094/64 fe80::%vlan4094/64 interface /Common/external connected fe80::%vlan4093/64 fe80::%vlan4093/64 interface /Common/internal connected ff02:fff::/64 ff02:fff::/64 interface tmm_bp connected fe80::%vlan4095/64 fe80::%vlan4095/64 interface tmm_bp connected fe80::/64 fe80::/64 interface /Common/cp_portal connected fe80::/64 fe80::/64 interface /Common/cp_network connected fe80::/64 fe80::/64 interface /Common/cp_full connected fe80::/64 fe80::/64 interface /Common/socks-tunnel connected fe80::/64 fe80::/64 interface /Common/http-tunnel connected ff02:fff::/64 ff02:fff::/64 interface /Common/tmm_bp connected fe80::%vlan4095/64 fe80::%vlan4095/64 interface /Common/tmm_bp connected ff02:ffd::/64 ff02:ffd::/64 interface /Common/internal connected ff02:ffe::/64 ff02:ffe::/64 interface /Common/external connected ff02::/64 ff02::/64 interface tmm connected fe80::/64 fe80::/64 interface tmm connected [root@LABBIGIP1:Active:Disconnected] config netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 127.1.1.253 0.0.0.0 UG 0 0 0 tmm 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 external 127.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 tmm 127.7.0.0 127.1.1.253 255.255.0.0 UG 0 0 0 tmm 127.20.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tmm_bp 172.16.0.0 0.0.0.0 255.255.255.0 U 0 0 0 internal 192.168.255.0 0.0.0.0 255.255.255.0 U 0 0 0 mgmt [root@LABBIGIP1:Active:Disconnected] config tmsh show net route ---------------------------------------------------------------------------------------- Net::Routes Name Destination Type NextHop Origin ---------------------------------------------------------------------------------------- route_default default pool /Common/gateway_pool static 1500 127.20.0.0/16 127.20.0.0/16 interface tmm_bp connected 172.16.0.0/24 172.16.0.0/24 interface /Common/internal connected 10.0.0.0/24 10.0.0.0/24 interface /Common/external connected 127.1.1.0/24 127.1.1.0/24 interface tmm connected ff02:ffc::/64 ff02:ffc::/64 interface /Common/vlan1 connected fe80::%vlan4092/64 fe80::%vlan4092/64 interface /Common/vlan1 connected fe80::%vlan4094/64 fe80::%vlan4094/64 interface /Common/external connected fe80::%vlan4093/64 fe80::%vlan4093/64 interface /Common/internal connected ff02:fff::/64 ff02:fff::/64 interface tmm_bp connected fe80::%vlan4095/64 fe80::%vlan4095/64 interface tmm_bp connected fe80::/64 fe80::/64 interface /Common/cp_portal connected fe80::/64 fe80::/64 interface /Common/cp_network connected fe80::/64 fe80::/64 interface /Common/cp_full connected fe80::/64 fe80::/64 interface /Common/socks-tunnel connected fe80::/64 fe80::/64 interface /Common/http-tunnel connected ff02:fff::/64 ff02:fff::/64 interface /Common/tmm_bp connected fe80::%vlan4095/64 fe80::%vlan4095/64 interface /Common/tmm_bp connected ff02:ffd::/64 ff02:ffd::/64 interface /Common/internal connected ff02:ffe::/64 ff02:ffe::/64 interface /Common/external connected ff02::/64 ff02::/64 interface tmm connected fe80::/64 fe80::/64 interface tmm connected [root@LABBIGIP1:Active:Disconnected] confignetstat is from Linux point of view, tmsh is from TMM point of view. First 2 commands when using gateway (single IP), and last 2 when using pool.
"Is it possible ?"
Yes, should work.
youssef1Cumulonimbus
Hi Anoop,
this is the kind of deployment that we implement for LC. For outboung traffic with 2 or 3 ISP (according to your convenience).
Yes it's possible
Here is a F5 documentation that show this kind of deployment (the version is old but it's the same principle):
For information I alredy implement It several times...
Regards