Forum Discussion

Brian_Saunders1's avatar
Brian_Saunders1
Icon for Altostratus rankAltostratus
Dec 05, 2013

Topology Records and WideIP vs. Pool Based Topology Decisions

Hello all,

 

I've never really been able to get a definitive answer on this. From the documentation about configuring topology based DNS on the GTM it shows examples of configuring topology at the wide IP level by creating topology records that reference the pool. And when configuring topology at the pool level the documentation shows examples of creating topology records that reference the data center.

 

In production we have topology DNS configured at the wide IP level (with two pools and one virtual server in each pool) and our topology records reference data centers. It'll work if at the pool level you have the topology set first and none as your second and third options. But if you were to change the second or third option to something else you will get mixed results and won't follow the toplogy records.

 

Can anyone explain this?

 

Thanks,

 

Brian

 

1 Reply

  • Hi Brian, When using topology based load balancing you have to specify the requesting source and the destination. As long as you only have topology based load balancing selected it works as per your expectations but when you select the second and third method of load balancing and the first option of Topology load balancing fails it moves down and try to get the reply via other two methods of load balancing so that is the reason why you get the different responses or unexpected responses. I hope this explains your question.

     

    Regards,