This message was deleted.
# citrix-netscaler
s
This message was deleted.
d
Since it just a DNS name, I use GSLB, so if the primary goes down, it fails the name over to another ADC.
There are other options for HA DNS of course. I am just using GSLB as it is part of the ADC. Looking at this: https://www.jgspiers.com/storefront-high-availability-optimal-routing/ I can see how using GSLB can route to the gateway closest to the user. Not really needed in my environment, but I can see how that could be useful too.
f
I'm already using GSLB but the location accuracy is poor and users end up at the wrong gateway via the browser or workspace app all the time. So what I'd like is for Optimal HDX routing to steer the users session to the best gateway regardless of where they authenticated from, but best doesn't seem to take into account actual availability at least from the way I see it on paper.
It looks like from the comments on that article that this is only doable with manual intervention. Wish that were not the case and that they'd integrate SF better with an ADC GSLB config.
d
Yeah, I don't use GSLB for location accuracy for the HDX routing. The Gateway addresses are Active-Passive. So, say I have dc1.domain.com and dc2.domain.com as my ADCs. I have two Citrix farms, but can be done with Zones too. Farm 1 is in the same Data Center as dc1.domain.com and Farm 2 in dc2.domain.com. If ADC that is primary for dc2.domain.com goes down, GSLB sends the IP address over to the same address as dc1.domain.com and can backhaul via VPN connection to Data Center 2.
f
I've found an old blog post that talks about a GSLB extension to StoreFront to solve my use case... https://www.citrix.com/blogs/2014/11/10/accurately-direct-xenappxendesktop-users-to-a-correct-location-based-datacenter/. I have to do some more digging to see if it is still available and what cons if any exist.