Auto-Last-Hop vs Routing

[NetCohort]

Hey guys,

cause of an active-active DSC setup I don't want to work with routes. (Two gateways for the same subnet) 

I thought I could manage it with the "Auto Last Hop" feature which is enabled. Unfortunately the health check traffic is passing the management interface at the moment. If I use more specific route on the mgmt Interface should the Auto Last Hop idea working for the active-active DSC setup?

Kind regards

[JoshBecigneul]

Hi @NetCohort 

Are your pool members in a subnet directly connected to the BIG-IPs?

[NetCohort]

Hi,

unfortunately not. That would work, but the real servers are behind my next hop. 

Because I have to route same subnets (because real server may running on the same site) to different gateways to connect my real servers, it looks like that I have configure route domains per site.

Any other idea?

route hop (firewall) <-> active-active DSC <-> route hop (firewall) <-> real server

[JoshBecigneul]

This article seems like it might fit what you're looking for: K15582: Configuring multiple default routes on the BIG-IP system (11.x - 15.x) 

The BIG-IP has the ability to specify an LTM pool as the "hop" for a default route, where you might be able to have both of your gateways in the pool.

Another option could be to look into dynamic routing protocols.

[NetCohort · Accepted solution]

However I solved it with route domains. I thing it is the smartest solution for this deployment.