I was wondering if anyone knows if it is possible to implement stickyness across multiple VIPs. In other words, if a client hits a specific VIP on a specific TCP port, then hits a different VIP on a different tcp port, can stickyness be configured to stick that client to the same server?
u talk about stickineess on the CSM? it's possible :), but be careful...
and one sticky group for both server farms (one for rserver1, second for rserver2).
first session is established to vserver1:
- sticky is recorded to rserver1 (rserver_ip1:portX)
second session is established to vserver2:
- sticky exists (client matched the sticky rule)
- session is not load-balanced, but connected to rserver by sticky record (!), in other words, session is directed to rserver_ip1:portX and no to :portY
^^^ answer to your question: it's possible :), but be careful... in other words, it's possible if the service on the server side is running on the same real server and port (portX=portY). other, use different sticky group for second server farm.
I think, it's not possible, because CSS use sticky definition for each content rule (unlike CSM, where you define sticky group and you can associate one group with some server farm. the similar situation is for ACE.).
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
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...