GSLB Persistence table not synchronizing across sites
Article ID: CTX230249
Updated On:
Description
In this Scenario the users are unable to launch applications Randomly. The environment consist of 2 NetScaler Gateways in 2 different locations, Dallas and Chicago.
Resolution
Configure the same persistenceID value for the GSLB Vservers with the same name in all sites:
GSLB autosync is recommended to avoid this issue.
- Output from Dallas site :
add gslb vserver GSLB-Vserver-LLCITRIX-External SSL -lbMethod STATICPROXIMITY -backupLBMethod RTT -tolerance 100 -persistenceType SOURCEIP -persistenceId 2 -persistMask 255.255.0.0 -v6persistmasklen 64 -timeout 60 -appflowLog DISABLED
- Output from Chicago site :
add gslb vserver GSLB-Vserver-LLCITRIX-External SSL -lbMethod STATICPROXIMITY -backupLBMethod RTT -tolerance 100 -persistenceType SOURCEIP -persistenceId 1 -persistMask 255.255.0.0 -v6persistmasklen 64 -timeout 60 -appflowLog DISABLED
GSLB autosync is recommended to avoid this issue.
Problem Cause
The persistenceid is different for the GSLB virtual server same across all the GSLB sites.
Issue/Introduction
In this Scenario the users are unable to launch applications Randomly. The environment consist of 2 NetScaler Gateways in 2 different locations, Dallas and Chicago under a GSLB environment.
Persistency is critical in this case as the client needs to stay connected to the same NetScaler Gateway once the initial logon is initiated since AAA sessions are not synchronized across GSLB sites.
Was this article helpful?
Yes
No
Powered by
