This message was deleted.
# citrix-netscaler
s
This message was deleted.
👀 1
j
My understanding is that they survive a reboot in HA scenarios when SR is enabled (as session is passed to HA partner vs going the way of the dodo).
f
Hello, here is my feedback: We decided with my customer to rebuild a new VPX and to migrate from the old one to the new one : new NSIP, andSNIP but same VIP (disabled from the old and activated on the new one at network level) and configurations. Here is the result: All Citrix active sessions came back automatically and there is no HA context but completely different VPX... So we used the command to clear everythinhgas recommended by Citrix.
👀 1
m
That sounds like ICA sessions rather than SAML tokens or authentication sessions
those will be kept open at the citrix farm level
j
oh yeah, sessions themselves for sure, just not the unintentionally(?) persisted auth at the gw
m
I guess it depends on how/where you are doing the auth and where the clients are. I could see clients reconnecting if they are internal and able to see storefront directly as then beacons would kick in and try to connect through storefront rather than the gateway, and they would just get back in to the existing session.
if it’s all external and you hit a brand new gateway and it just lets you in, that’s concerning
I don’t understand how running the commands would even work on a bran new netscaler because there are no persistent sessions to clear
they are stored in RAM
f
Hi Mike i don't know the reason but it looks like the way it works when you separate authentication and HDX routing, you don't need to reauthenticate on the HDX routing NetScaler which can be completely different (GLSB deployment for example). I confirm that it's only the ICA session which came back not the AAA.
m
I wonder if auto client reconnect is doing it with saved credentials