This is from Citrix "Spare connections available: To save time and resources in establishing another connection for a new client, the connection on the server is not closed after completing the request from the first client and is available for serving future requests.". Basically connection pooling. What I've seen is when the NetScalers get pounded by a lot of new connection requests, then the sessions close, the spare count gets high. I would expect this to be lower than 700. Check your "TCP Current Conn Established" counter. If you see a very short spike in that counter at the same time the spare connection goes up, that's a problem. See the graphic below. The time around 1am was a surge in connections the netscaler had a problem handling. The top graph shows the normal ramp-up of connections.
Dumb question here. I found that our Spare TCP connections value is over 700. The template has 50 as warn and 100 as alarm. I want to assume this is based on a vendor recommendation but am not sure. Is this a good value to monitor? Suggested out network team consider a ticket with the vendor but figured I would ask here at the same time.
Thanks for the template, I am taking the values and setting up pollers to save on SAM licenses myself but you gave me a perfect roadmap of what to look for.
Top Comments