I think this can be best explained using an example.
3 hosts connect to your VIP address:
host1 - 192.168.0.5
host2 - 192.168.0.200
host3 - 172.16.0.20
imagine you use source sticky with a netmask of 255.255.255.0
host1 connects to the VIP and a check for is done if he already exists in the sticky table. this is not the case so the predictor is used to balance. he goes to server 1, and a sticky entry is added to the sticky database (I don't know the way this is done internally, but the result will be that any host with source address 192.168.0.0/24 (<-- netmask) is sticked to server1.
Host 2 arrives and the same process is done; a lookup in the sticky database results in a match, because host1 its source matches 192.168.0.0/24, and he is also send to server1.
Host3 does the same thing, again a lookup in the sticky database, no entry found, balance using predictor, send to server2 and added to sticky database.
Imagine if we used a netmask of 255.255.255.128, in this case host1 and host2 would not match each other and would be balanced individually.
Concerning the predictor, this is only used when no sticky entry exists for a certain connection. I think it is the same question you can pose yourself when you need to choose a predictor with or without stickyness.
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...