This message was deleted.
# citrix-netscalers
Slackbot
03/16/2021, 4:26 PMThis message was deleted.
e
Eddy
03/17/2021, 8:51 PMWe balance LDAP successfully with lb vs. leastconnection. No persistence. All parameters default except ciphers for 636.
636 is running on ssl_tcp. That’s it.
j
jvitech
03/18/2021, 11:19 AMVery good, thanks a mill!
jvitech
03/19/2021, 3:26 PMI have reports of timeout and slowness but using the LDAP VIP. I suspect surge queue, SP is disabled, it is strange. I can see the surge queue in NS graph spiking a bit and then going down. The load is not that heavy but I think NS is probably reaching some limits but I can't really see something proving this.
e
Eddy
03/19/2021, 3:31 PMDifficult to tell you what’s the problem without deep analysis.
Could be that you get some requests queueing up anyhow.
I have also heard for example of strange behavior of ADC when running on Hyper-V without min 4GB Memory per Core.
Would suggest to run min 2 cores with 8GB Memory at least for VPX.
j
jvitech
03/19/2021, 3:36 PMIndeed thanks, I was looking for some hints on what I could check to see if I don't hit the max nb established clients / servers connections. That's the only thing higher. It's a MPX 7500, CPU/Memory it's all good.
e
Eddy
03/19/2021, 3:43 PMVery old box. I would check what this box can handle in SSL TPS when you run LDAPS as SSL or SSL_TCP vServer. could reach out some limitation if you have high number of handshakes and using strong ciphers.
Eddy
03/19/2021, 3:43 PMI will check if I find the nsconmsg command I used in the past to check for queuing
Eddy
03/19/2021, 3:47 PMnsconmsg -K /var/nslog/newnslog -g ssl_cur_sslInfo_nsCardInQCount -d current
Was using this to identify ssl queueing
j
jvitech
03/19/2021, 3:51 PMThanks yes I was using it, I can't see anything wrong and the issue (time out, very slow requests initialization(prob in the queue)) now for 2 different apps started when using this VIP. It is LDAP 389, not SSL. I'll keep digging.