Forum Discussion
AltostratusLTM/GTM 11.6.x and Route Domains
I am in the process of deploying LTM and GTM 11.6.x on the same box, and am looking for some clarification of language in the F5 manual. Specifically, the manual chapter on GTM with Route Domains shows this caution: "For BIG-IP systems that include both LTM and GTM modules, you can configure route domains on internal interfaces only." What determines an internal interface? The manual's example shows one VLAN is literally named "external", and one VLAN is literally named "internal", and both are added to a single route domain. Fine, but the example does not show what happens when you have more than one route domain on the same box. I can't re-use the VLAN names "external" and "internal", nor can I add them to another route domain. So if I add a second route domain on the the same box, what determines that it is internal?
TIA, Jason
3 Replies
dragonflymrCirrostratus
Good question, I was wondering about same thing when reading this doc. Sometimes it's hard to figure out what statements really mean :-( Piotr- boneyard
MVP
of course they exist as names but I read external vlans as ones on the client side and internal vlans on the server side.
I think that statement is old, and was never worded correctly. When it says "internal" I believe they are saying the LTM aka BIG-IP Server and the GTM needs to be on the same default route domain. Maybe they were thinking "internal" to each other? who knows..
From an old 10x manual - https://support.f5.com/kb/en-us/products/big-ip_gtm/manuals/product/gtm_config_10_2/gtm_setting_up_and_configuring.html
"When you configure a Global Traffic Manager to communicate with other BIG-IP systems, the IP addresses of the system servers must reside within the default route domain on the BIG-IP system. Otherwise, the Global Traffic Manager cannot communicate with those systems. For more information about configuring route domains, see the TMOS® Management Guide for BIG-IP® Systems"
I've set up BIG-IP servers in GTMs that reside on non default route domains, but it's not as straight forward as the doc would lead you to believe - try to avoid it if you can.
