Forum Discussion
AltostratusConnections appear not to use Persistence
I have created some new Pools, VIPS, WideIP List and published to the organization. It appears that when a user connects to the FQDN they land on NodeA, but when they log into the application they are switching to a different node in the Pool.
The reason I suspect an issue with persistence, is when I have a single active node in the pool, the users do not receive/experience any issues connecting and logging into their application.
I have tested with "Cookie" "Named Cookie" and "Source IP" with the same results.
Any suggestion would be greatly appreciated.
6 Replies
- Paulius
MVP
Are you able to provide the configuration for the WIP, VIPs, and pools? I assume that you have confirmed that when they login they are returning to the same VIP that was passed out previously from the GTM for the associated WIP?
- zamroni777
what is node A?
wideip/dns config selects vip of ltm vserver;
app request to ltm vserver's vip:port causes ltm vserver to select pool member
Larry_Wilkszamroni777
Node A is one of five servers in the LTM pool for LTM VIP.We are not doing full GSLB between datacenters for this implementation.
We have two load balancers in datacenter one in HA configuration on which the VIP, Pool, and nodes are configured.
VIP "myhttps_vs" uses Pool "myhttps_pool", which has five node members "myhttps1", "myhttps2", so on...
If all five nodes are active/enabled we experience issues logging into the https application. If we force four nodes out of service, then everything functions as expected.- Paulius
Can you provide your configuration of the VIP in question and it's associated configuration?
