on server site, there is warning messages same as below:
Warning: The session id: sessionID has been accessed from currentServer, a server that is neither the primary (primaryServer) nor the secondary (secondaryServer). The request URL was: requestUrl
The session id: sessionID has been accessed from currentServer, a server that is neither the primary (primaryServer) nor the secondary (secondaryServer). Repeated occurrences of this can cause memory problems and performance degredation, as sessions are loaded into memory on more than two servers at a time.
The most likely cause is a configuration error on a front end hardware loadbalancer or webserver plugin. They should be configured to respect the values of primary/secondary in the cookie (i.e., stickyness), when possible.
Please ensure that the front end webserver or load-balancer has been properly configured.
I have been adviced that I need increase idle timeout.
but, I still do not understand this problem should increase idle timeout or stickness timeout?
if it is idle timeout, the server is 3 min, but, I looked CSS default, it only 8 second, so, do I cause any problem if I increase to 3 min?
If it is stickness inact timeout, server site has not document about it, how many I should set?
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
With Vignesh R. P.Welcome to the Cisco Support Community Ask the Expert
conversation.This is an opportunity to learn and ask questions of Cisco
expert Vignesh R. P. about the Cisco® Nexus 7000 Series Switches and
support for the Cisco NX-OS Software platf...