Route Domain

Hi,

Instead of asking if

the route domains in LTM is equivalent to contexts in ACE

, can you describe what a context in ACE?

We then will be able if route domain do what you expect!

it is part of it, combined with a configuration partition you are closer. then you isolate your config and routing. although you can still borrow from the main configuration partition and if you want to from main routing domain.

 

if you want more isolation from each other you can look at vCMP, then you have virtual instances of BIG-IP on one box. but that goes beyond ACE contexts.

 

in general it might be wise to contact your local F5 partner, they might have done some more ACE to F5 migrations and can possibly help.

 

If the end goal is to segregate IP traffic and routing between different environments within the same device, you can do it using a combination of partitions an route domains. That would allow you to segregate traffic within the same LTM instance. You can do this by: Create a new partition Moving to the partition you just created Create the vlans within the new partition Create a new route domain (selecting strict isolation, the vlans you just created for the partition, and making it the default route domain for the partition) Create the self IPs for the vlans

 

You repeat the process for each partition you want to create. Make sure you assign a different route domain ID for each partition you create. If you're doing an HA pair you need to do this on each box. Make sure you use the same names for the vlans, route domains and partitions on each box.

 

Once both boxes have the same partitions, vlans, route domains and self IPs, you can create the object that get synchronized with the device group on the Active box. Ex. Floating IPs, default routes, pools, profiles, iRules, virtual servers, etc.

 

This setup allows you to keep traffic from one partition isolated from the rest. Thus you can have a different default route for each partition, which is a great convenience.

 

Hope this helps!