Forum Discussion

Josh_41258's avatar
Josh_41258
Icon for Nimbostratus rankNimbostratus
Jul 10, 2013

GTM Topology

I use topology records to make the GTM decide if it needs to hand out internal IPs (to internal clients) or external IPs (to external clients) for one specific service. I do this by defining two topology records that verify if the source of the LDNS request is "172.16.0.0/12," make the destination "INTERNAL-POOL." If the LDNS source is anything else, make the destination "EXTERNAL-POOL"

 

This has worked well up until now. Now, we have other applications on the GTM that need to do the same type of thing. We also need topology rules for other services that send users to different datacenters based on their LDNS request source. Since my first two topology records referenced in the first paragraph are specific to one service/pool, I'm not sure how to proceed. I could use weights to make the INTERNAL/EXTERNAL rules a higher priority and then the new rules for Datacenter selection could go under them. But, what if I need to have the GTM decide rather to hand out internal/external IPs for a NEW service. This wouldn't be possible since the two toplogy records are specific to one pool/service.

 

Ideally, the toplogy rules would allow you to specify a LDNS Request Hostname and let you create rules based on that, but it does not.

 

Any ideas would be greatly appreciated. My apologies for a somewhat confusing explanation and question.

 

Thanks!

 

5 Replies

  • Do I maybe need to scrap the INTERNAL/EXTERNAL topology rules for the one specific service, and use an iRule bound to the WIP instead? This would allow me to have more generic topology rules.
  • We have hundreds of WideIPs that all use the Topology load balancing method. The Topology method only checks those pools that are defined in the WideIP. So, you can have many all in the same Topology file that don't interact with each other so long as they all use different pools.

     

  • Oh, I had no idea that Topology worked this way. So, if I have multiple topology rules:

     

     

    Source: internal-users

     

    Destination: internal-app1-pool

     

     

    Source: internal-users

     

    Destination: internal-app2-pool

     

     

    These two topology rules won't get in the way of each other since the app1/app2 pools are associated with different WideIP's?

     

     

    Thanks,

     

     

    Josh
  • Correct. We use the same topology regions ("Dublin", "Westerville", "Everywhere") for all our WideIPs. Since any given WideIP only as 3 pools assigned, only those 3 are considered in the topology mix for that WideIP.

     

  • Ok, I think this is the "Longest Match" (enabled by default) option that handles this type of thing. Thanks for the tip!