This is not going to be possible if you are not terminating SSL traffic on the balancer. The layer 5 information is encrypted so the balancer is not going to be able to look at the cookies or urls in order to do balancing or stickiness.
One important thing to mention is that the SSL ID in SSL v3.0 is not encrypted, so the stickiness based on SSL ID will work fine, but then again not based on cookies or URL.
The servers are single sign on servers. And the clients are going to be a mix of everything. People will logged on to the same server for hours at a time. A disconnection because of CSS will not be acceptable.
Do you think I can rely on SSLID or shall I push for terminating the SSL on the CSS.
i'm at the beginning of the project so if I have to change something I must do it now.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...