Issue creating static route in Route Domain
I have 3 route domains configured on the F5 other than the default route domain 0. Now I am trying to configure default routes in each route domain. While default route creation for RD:2 was successful, when I try creating the default route for RD:3 it give the following error: "01070712:3: Cannot create static route: 0.0.0.0%3/0 gw 10.0.21.1%3 on interface in rd3 - netlink error:3 (No such process)" We are running BIG-IP v11.6.0.4.0.420. I remember configuring multiple route domain, multiple static routes and default routes in each route domain on another box which was running version 12. Appreciate if anyone can help with this. Am I missing something or is this a BIG-IP Version limitation?Solved1.5KViews0likes13CommentsActive/active with BGP. Do I need floating IPs?
Hi We're in the process of enabling bgp routing to our bigips. Each ltm is primary for a traffic group and will advertise routes when the VIPs are up ( https://support.f5.com/csp/article/K14267 ). Our isp wants a separate link net between our two ltm<->router pairs. And so far in our lab setup we don't have any floating self ips on the external vlan/link net. Everything seems to work. Is it necessary to have the floating self ips? BGP advertises the local self ip as next-hop for the active vips in each traffic group, and when it fails over it advertises the local self ip on the other ltm as next-hop. Will this cause me problems down the road?323Views0likes0CommentsOSPF - F5 Equivalent to Non Stop Routing
I'm running OSPF between a Juniper and a PAN. When I reboot a box, either the PAN or the F5, the routes immediately timeout however the peer relationship stays. As a result if the box is the DR the routes do not reappear until the peer relationship drops off. How can I avoid this? On the SRX this is non stop routing, is there an equivalent on the F5? OSPF configuration is straight forward with basic network statements and area 0.0.0.0. I have considered BFD however that is a bigger architectural change throughout the network. Thank you.189Views0likes0CommentsEnabling ARM on Viprion C2400 with VCMP guests
Use case: We're in the middle of an effort to enable the Advanced Routing Module (ARM) with OSPFv2 so that we can essentially employ route advertisement on virtual addresses, and be able to remove them via dynamic routing when any of the services become unavailable. We appear to be having issues properly enabling them on specific LTM guests that reside on VCMP-enabled Viprion hosts. While I do have a support case open, I thought I would try devcentral. So, enabling OSPFv2 is done at the route domain level, and I have tried two ways - 1)enable ospfv2 on route domain 0 at the vcmp guest level -- OR -- 2)enable ospfv2 on route domain 0 at the host level -- OR -- 3) BOTH None of these options appear to work. taking traces, I do see the OSPFv2 Hello packets from the adjacent routers (which are also the default gateways being sent via multicast, but I don't see the F5s send their OSPFv2 Hello packets. So, no ospf neighbor info is getting across between Cisco routers and F5 BIGIPs. Am I missing something on the OSPF configuration side? I did follow instructions given in this article: https://support.f5.com/kb/en-us/solutions/public/14000/400/sol14490.html Looking for anyone else out there who may have done this successfully before. Thanks!271Views0likes2Comments