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 22, 2014

You're welcome.

 

  1. Sounds good

     

  2. Correct - just make sure you route those subnets to the F5 on the firewall, over the small routed subnet

     

  3. You'll need to specify SNAT Automap in the configuration for each Virtual Server but yes, the SNAT will use the self IP of the relevant VLAN

     

  4. OK, shouldn't be an issue as long as you apply the SNAT

     

  5. OK

     

  6. Sure, in F5 terminology the Trunk is the bundle, VLAN tagging is called, err VLAN tagging (rather than trunking as in the Cisco world)

     

7. If you are going to do that, there's no point in the small routed segment we've discussed in 1) is there?

 

  1. Sure, as per 6)