Forum Discussion

Jason_40733's avatar
Jason_40733
Icon for Cirrocumulus rankCirrocumulus
Apr 06, 2012

Advanced Routing Module & Route Domains Question

We're working in a multi-tenant environment. My research has left a few questions about ARM and route domains. Specifically, using the ARM module, can we route traffic to specific subnets within differing route domains and partitions?

 

 

Our scenario is as follows.

 

 

 

Separate customers in partitions with route domains for each customer so they can re-use RFC1918 space.

 

 

 

Empty Route domain 0 ( since everyone has access to it and we can not currently change that from being the default route domain for every partition. )

 

 

 

Create Route domain 1 which would ideally have an IP as a routing point for our different subnets. This would keep our switch to Bigip client side trunk to only a single Vlan.

 

 

 

Have ARM handle routing from our client trunk side into the multiple route domains as needed ( granted that there will not be duplicate routable IPs between any customers )

 

 

 

 

 

Our goal: Not require trunking multiple VLANs from the client side switches to the Bigip. Instead have 1 Vlan connected on the client side with the other hundreds to thousands of vlans being used only on server side. This will push the routing to IPs down to the Bigip and keep it in the load balancing provisioning side instead of having to involve multiple groups for operational deployments.

 

 

 

Yes, I understand that we could just route each individual IP to specific VLANs from the client side switch and not lose/gain any VLAN capacity. But our goal is to minimize the of groups or touch points when provisioning new customers with public and private IP needs.

 

 

 

 

 

Thanks in advance for any assistance.

 

 

 

Hex

 

 

 

 

 

 

 

config
design

22 Replies

Sort By
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Apr 07, 2012
    just in case you have not yet seen this.

     

     

    If you are using the route domains feature, you can implement dynamic routing, but only for route domain 0. Route domain 0 is the default route domain on the BIG-IP system and the only route domain of which the advanced routing modules have knowledge. For this reason, you should consider the following:

     

    All dynamic routing peers must be connected to networks in the default route domain (route domain 0).

     

     

    You can implement non-default route domains and simultaneously use dynamic routing in the default route domain. However, the advanced routing modules can use and advertise only those objects (routes, self IP addresses, and virtual addresses) that pertain to the default route domain.

     

     

    Considerations for route domains, route propagation, and route precedence

     

    http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos_management_guide_10_1/tmos_routes_dynamic.html
  • Jason_40733's avatar
    Jason_40733
    Icon for Cirrocumulus rankCirrocumulus
    Apr 09, 2012
    Thank you. That answers my question. And docks me a few points on reading comprehension since I've specifically read through that document and managed to miss the big bold faced type pointing that out. LoL.

     

     

     

     

    Much appreciated.

     

     

     

    J