Multiple inbound gateways connecting to all vlans.

Big vlans...

 

 

Anyway. You can actually do this without a default route... Or with one. Depending on how you configure the VS's used to pass traffic through. Remember that the LTM is a proxy. Not a router. So where traffic flows depends entirely on the VS's that match the traffic.

 

 

Assuming that we don't have a firewall or anything that needs to pass inter-vlan traffic (Keeps it a bit more simple than otherwise), we have 5 vlans and 5 routes to directly attached networks.

 

 

Therefore we have 3 network VS's that are used to pass traffic to the server vlans. One each for 10.48.0.0/16, 10.9.0.0/16 and 10.14.0.0/16. Each is of type forwarding and available (By default) on all vlans. As traffic coming into the LTM matches the VS's the traffic is then 'forwarded' to the target vlan. Because we have auto last-hop enabled by default, it doesn't matter whether traffic came in via vlan a or vlan b. It'll pass BACK through the same MAC address that forwarded it TO the LTM.

 

 

Now for traffic OUTBOUND from the server VLANs to anywhere else. You have the choice of

 

 

A. Using a default route via one of the VLANs

 

B. Using one or more pools consisting of the router addresses off vlanA or vlanB to your destinations.

 

 

If using A then we can actually shortcut the 3 VLANs setup above. And have a SINGLE default (0.0.0.0/0) network VS of type forwarding. It'll just follow the routing table.

 

 

If using B. then we can take the original 3 VS's and add a new one (Or ones) of type standard. Disable IP and port translation. Destination IP and mask whet eve the destination is, and add the pool as the default. Traffic will be 'forwarded' to the pool members just like a router would. That leads you decide with an address/mask to route via either vlanA or vlanB.

 

 

 

You can make this as simple (One VS and routing table entries) or complex (Multiple network VS's with iRules and pools) as you like.

 

 

H