Forum Discussion
NimbostratusAdding VIP "networks" as connected routes
I recently came into an environment where they designed the load balancer so that the VIPs are on a separate subnet than the backend hosts. My concern with this design is not "routing" to the VIPs from a F5 perspective. Checking the route tables I do not see VIP network 1 (172.16.15.x). The only way to get this as part of the route table would be to create a self/float IP (HA). Is there logic within F5 that processes before hitting the route table to see that it owns that IP or IP space? I'd like to avoid wasting 3x IPs just to get connected routes in the route table.
Andy_McGrathCumulonimbus
Yes, all traffic goes via TMM so routing is just needs to be to a F5 self IP to get to a VS address on a different subnet.
- boneyard
MVP
i'm not sure if i totally understand your question.
you can use VIPs on any IP address, that IP address doesn't not have to match on an interface on the F5.
the F5 does of course need an IP to route traffic to from a router or such.
but you can you have VIPs in 10.10.10.0/24 and only have an interface on 10.20.20.1, those VIPs will work if you route traffic for it to it.
