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

Zdenda's avatar
Zdenda
Icon for Cirrus rankCirrus
Feb 09, 2015

2 traffic-groups, routed VIP subnet and Best Practises with Active-Active mode

Hi, we want to use 2 or more traffic-groups and assign each VIP or server subnet to separated traffic-group. We now have all configuration in one traffic-group and I am not sure what objects to add t...
Zdenda's avatar
Zdenda
Icon for Cirrus rankCirrus
Feb 09, 2015

Yep, since we need to keep current "one traffic-group" design, we have to use routing domain separation and therefore also partitioning (we never have multiple routing domain in one partition).

 

I was thinking that we can have design using one routing domain with multiple traffic-groups, but looks like in this case our vlans connected to LB (interconnect, server vlan) should have more floating IPs - each dedicated for own traffic group.

 

For example I am not sure if LB supports scenario when standard VIP is active on A unit, but floating IP of server vlan is active on B unit (together with forwarding VIP for server vlan). Will A unit still be able to send and receive users traffic to/from server vlan? I would say yes, but have no experience in this yet

 

  • NikhilB's avatar
    NikhilB
    Icon for Employee rankEmployee
    Feb 09, 2015
    Why do you need separate partitions in this case? (why not work off the Common - root folder)
  • Zdenda's avatar
    Zdenda
    Icon for Cirrus rankCirrus
    Feb 09, 2015
    Mainly because traffic-group is not an option specified during creating new virtual server and I am pretty sure that this would be making mixed up config in future and therefore not all VIPs would be in proper traffic-group.