Forum Discussion

killcity_177823's avatar
killcity_177823
Icon for Nimbostratus rankNimbostratus
Nov 19, 2014

Routing through cores

Has anyone setup their LTMS on a transit VLAN for the inside interface and then routed via a core layer (using OSPF in between the core and ltms) to the backend servers? The default route on each backend server would be the core layer and in turn, the core would have it's default route set to the load balancer. Is this not recommended or even possible due to the stripping of source and destination fields in the IP header by the core? I'm always seeing LTMs used with directly connected vlan interfaces and IPs on each backend subnet.

 

We've got other internal destination networks defined on the core that backend servers need to communicate with. Im not sure how else to allow them to route via the core to these destination nets without defining static routes to them, via the core on each server OR adding the routes to the ltms, which I would think would not be best practice (adds lots of extra net IO and cpu weight to the them).

 

Thanks! BJ

 

1 Reply

  • I have routed to back-end servers, but have always used a SNAT when doing it. I've also used static routes, but I don't how the route gets in the routing table really matters in this case. If you are not using SNAT, I would think as long as the traffic is properly routed back through the LTM it should be OK, but I have never done this.