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

Brad_146558's avatar
Brad_146558
Icon for Nimbostratus rankNimbostratus
Jun 08, 2016

Implementing Route Domains on an existing Production F5

Hi everyone,   Our security team is wanting us to keep the data flowing through the F5 separated. Basically in short they have some complicated routing they want me to do in the F5. Route domains ...
application delivery
LTM
security
jgranieri's avatar
jgranieri
Icon for Nimbostratus rankNimbostratus
Jun 08, 2016

I have implemented route domains to address two issues:

 

1 - Allow a separate "vrf" or route domain to function across a specific set of physical interfaces and self contained routing domain separate from other different trust zones through the F5.

 

  1. Route domain allows us to have use an 11.5 feature called HA active-active traffic groups... what this does is allows a traffic-group fail over to the secondary F5 and not impact another traffic-group. Using route domains we can keep one set of vs/self-ips contained and isolated so that any link failure in one route domain does not cause all other route-domain/traffic groups to experience a failure as well.