Forum Discussion
BIG-IP always injecting default-route and CGNAT block through BGP
Hello devs!
I read on the "routing administration guide" that when you have a cluster, RHI announces routes (when you're running BGP) with the next-hop as the float IP of the egress interface. Which makes sense.
I also read that when you do not have a float, RHI will only announce the route through the active box when you have a cluster. Which also makes sense.
But this behavior (announcing only through the active box) is only valid for virtual servers/address that have an IP.
I'm configuring an environment with the CGNAT module enabled in which I want to announce the LSN block configured inside the LSN pool only through the active box to the edge of the network (so traffic can come back) and also a default route (through a forward VS 0.0.0.0/0) to the inside of the network.
But to both these cases (CGNAT block and default route) the rule of only announcing through the active doesn't seem to apply.
I know I could fine tune the routes inside BGP but I wanted to make theses changes based on the active box and I don't think there is a way (at least to my knowledge) of doing this.
Any ideas?
Thanks! Rafael
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com