For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Arunprabhu_1147's avatar
Arunprabhu_1147
Icon for Nimbostratus rankNimbostratus
Apr 21, 2014

Multi tenancy design, Route domain

Dear Techies,   For Cloud design The following are the design options considered for the Implementation of F5. we have F5 1600 having Four Gigabit Copper Interfaces.   Creation of three Admi...
cloud
design
virtualization
What_Lies_Bene1's avatar
What_Lies_Bene1
Icon for Cirrostratus rankCirrostratus
Apr 21, 2014

  1. You don't need to have a VLAN specifically for VIPs. Just route the IP subnet you want to use for VIPs to a self IP on any appropriate VLAN. So, for instance, create the external VLAN using a /29 or /30 IP subnet as appropriate. Then route say, 10.10.10.0/24 (your VIP range) from the core switch or firewall (or whatever) over that external VLAN, to the relevant self IP on the F5. If you did create 5 VLANs, yes, each one will need a self IP.

     

  2. In the F5 world, a trunk is a logical bundling of multiple physical interfaces, independent of L2 VLANs. Whatever you can do with an interface, you can do with a trunk. You can tag multiple VLANs over any kind of interface.

     

  3. APs have no direct relation to physical interfaces, but Route Domains do relate to VLANs and they exist within APs. A VLAN (rather than physical interface) can only be present in one RD. Multiple RDs can exist in a single AP. A trunk can carry tagged VLAN traffic for multiple RDs even if they are in different APs.

     

  4. See here: https://devcentral.f5.com/articles/v10-a-look-at-route-domains