F5 LTM creating VLANs etc

***** Update ******* I got this resolved by manually adding the route to the RADIUS server through the management interface and removing the default one that was in there. I am assuming that is ok to do?yes i believe so.

 

 

would it be a best practice to create a default route via VLAN250 (Internal VLAN)? normally, route on bigip (e.g. static route) is intended for bigip to be able to reach pool member/node. return traffic to client does not need the route because bigip is using auto last hop feature which is turned on by default.

 

 

sol13876: Overview of the Auto Last Hop setting (11.x)

 

http://support.f5.com/kb/en-us/solutions/public/13000/800/sol13876.html

 

 

What I want to do is use the 10.1.250.x internal VLAN for the clients inside and 10.1.25.x external VLAN for when the clients are coming in from the Internet. Should have I used the Virtual Server IP's from the Internal VLAN network instead of 10.1.6.x?as you see, virtual server ip does not need to be in the same subnet as selfip (but we have to setup routing properly). so, i think either same or different subnet is okay.

 

 

Also correct me if I am wrong but the servers that are in VLAN5 (10.1.5.0/24) nework I need to change the gateway on them to F5 as well? Which means do I need to create a VLAN5 and Self IP's from that VLAN etc on F5?bigip has to see return traffic from server. we use snat automap to ensure the return traffic is coming back to bigip. anyway, if you have selfip on vlan5 and server default gateway is bigip, i believe you do not need to use snat automap (because the return traffic will be sent to default gateway which is bigip anyway).