GTM Pool Persistence with timer

There should be a 'Pools' tab for each wide IP. On the pools tab, you can configure persistence. Just enable it and set your TTL to however long you want to persist the connection (in seconds).

Be aware though that if clients are using multiple local DNS servers, the client may get different results as the persistence is set by default to a 32 bit mask (host address).

Hi cory, if the application is accessed by internet users loadbalancing and persistence will work well, since clients are spread over geographically different DNS providers and ISPs.

If the end users are from two or three private LANs with maximum of 2 or 3 DNS servers, will the GTM able to loadbalance between sites.

I am facing such an issue, since my end users are querying the domain via a single DNS server and hence all the users connections are persisted and resolved to a single site or pool member based on the GTM persistence table.

I need both loadbalancing and persistence for my private lan users. Can you guide me?

Unfortunately, you are much more limited as far as type of load balancing and overall options you have available when you are doing it at the DNS level (GTM) versus at the connection level (LTM).

You don't have any LTM appliances or other local load balancing available by chance do you?

Hi cory, thanks for the response.

We do have LTMs.

We have two sites DC and DR both are configured as Active - Active.

Network Setup

DC

• External users --> Internet --> Firewall --> GTM --> LTM --> App Servers

   

• Internal users --> MPLS --> Firewall --> GTM --> LTM --> App Servers

   

DR

• External users --> Internet --> Firewall --> GTM --> LTM --> App Servers

   

• Internal users --> MPLS --> Firewall --> GTM --> LTM --> App Servers

   

GTM loadbalancing method: Topology with persistence enabled

Topology:

• MPLS IP segments are grouped as PVT_LAN

   

• IPs not part of PVT_LAN grouped as PUBLIC

   

PVT_LAN users requests will hit GTM pool-1 PUBLIC users requests will hit GTM pool-2

Both the pool 1 and 2 have pool members from both sites (DC and DR).

Expected functionality is, GTM loadbalancing and site level persistence and LTM loadbalancing and session persistence should work for both PVT_LAN and PUBLIC.

As i already said, for internet users GTM loadbalancing and persistence, LTM loadbalancing and session persistence working fine. Loadbalancing is happening fine in terms of GTM as well as LTM.

Unfortunately we have 80% users are from PVT_LAN (MPLS) and their DNS server is very few.

So, DNS queries from these PVT_LAN are persisted to single site and load is hitting only one site till GTM DNS persistence timeout.

Is there any better way to rule out this loadbalancing issue, without compromising persistence.

Guys, is there a way to create an irule that will periodically change between pools so all traffic gets sent to the same place. I understand Cory's solution of enabling persistence+TTL at the WideIP level but my limitation is the possibility of clients using multiple LDNS. How do big e-comerce companies do it any ideas?