we want to see and log (best would be to syslog) why the CSS takes a loadbalancing decision on stickiness. Is this possible and how should this be configured?
Our current problem is the following. We got a CSS11503 pair in box redundancy. They are loadbalancing https traffic to two SUN iPlanet instances using SSLv3. The rule is the following:
add service service1_https
add service service2_https
vip address 10.1.1.1
what we see is that some client gets forwarded to the second server during a session although it was directed to the first one before. And this leads to an 'authorization required' error in the client application. We can trace this in the iPlanet logs.
When using src-sticky, everything works fine, so this leads to the conclusion that it has to do with SSL loadbalancing.
Of course the application guys now blame the CSS for not working correctly, but I think (as a CSS guy) that the application is doing something wrong. So, I need to trace the sticky decision on the CSS.
The sticky decision is based upon the SSL hash at the time of the SSL Session Setup. As long as your Sticky Table Timeout is not set extremely low (and your's isn't) there should be no reason for the sticky association to change servers, unless, the application is renegotiating the SSL Session frequently (an application issue). This would cause a new hash and therefore, a new sticky condition balanced according the the ACA alogorithm.
I do not know a way to monitor the decision process, however, maybe Gilles can show you a debug routine.
Have you investigated the actual SSL session ID's being used for that particular client when this error occurs?
We had a problem with very similar symptoms and had to use a Sniffer in order to find the root cause.
Our servers (I think they were IPlanet too, running on Linux) were not handling the SSL session-id "re-use" option properly. They were instead providing a bran new SSL session-id each time the client would send a SSL "re-negotiation handshake" (I'm not sure about terminology here!). In our case, we saw this happenning every 90 seconds, causing the clients to bounce from server to server because the CSS would not find a match in its SSL-sticky table and load-balancing would therefore take effect and cause the client to end up on a different server (similar to what you are reporting).
Unfortunately, in our case (also) we were unable to resolve this server issue and we resorted to src-sticky.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...