F5 Cisco ACI
1 TopicF5 BGP Peering in Active /Standby Cluster
Hi team , I am trying to achieve Dynamic Routing over F5 BIGIP Devices with Cisco ACI in front which has the following design requirements. F5 is configured to be as default gateway for pool of webservers with a Virtual IP Subnet hosted for VIP on the F5 itself. The BGP is established by using a separate vlan to peer with CISCO ACI BGP Peering running an EBGP. The BGP peering is established by declaring selfip on the BGP Vlan and the route is advertised through the peering. I can see the Virtual Subnet a.a.a.a and Pool Member Subnet b.b.b.b as directly connected routes in the sh ip route on Imish console. Moreover a.a.a.a and b.b.b.b are consistently being advertised from Active and Standby F5 devices to Cisco ACI peers from their specific BGP peers hosted locally in F5. I tried to inject a Route for VIP subnet a.a.a.a with /32 by advertising route on BGP which is advertised as Kernel route and works well in Clustering scenario by being advertised from Active Boxes. The problem comes for Pool Member subnet b.b.b.b which is being advertised as connected route from both active and standby devices to Cisco ACI Peers and traffic ends up taking both the paths simultaneously. I have few questions in this design : Is there a way we can supress routes from Standby device being advertised to the upstream routers? Is there a way we can adjust the metrics for directly connected routes to be advertised with low metrics from Standby device. I have tried to configure the Pool Member as Wild Card Forwarding IP and to inject the RHI for b.b.b.b subnet as TMM route but the same was not honoured as TMM route because of its nature of directly connected routes. Any way to feasibly stop route advertisement from Standby would be greatly appreciated.89Views0likes7Comments