The hash function is a mechanism that takes the source ip address, and the number of servers and gives an index which represent the
server to use.
The same ip, will always result in the same index.
Therefore it is considered some kind of stickyness mechanism.
However, if you change the number of the servers or if you re-order the servers, the resulting hash will be different and your client will then be send to a different server.
On the other hand, stickyness works in combination with a predictor algorithm.
The predictor determines the server to use for the first time the user is detected.
Once the predictor has selected the server (roundrobin, or leastconn, or ....), the sticky functions saves the result in a sticky table and each time the use comes back, we use the cached information instead of calling the predictor again.
If you change the predictor, add or remove servers, or reorganise servers, that does not affect the cached entry.
So your user will continue to hit the same server.
Before using sitckyness, you should verify you have allocated enough sticky resource.
Don't forget sticky resource are not like the others.
The value you allocated (even if called minimum) is the maximum the device will use.
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...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...