Does adding additional L5 rules increase processing time? I recall back in the day of the CSS 11000, it was claimed the box was not impacted by additional rules and processed at near line rate. Obviously, adding your first L5 rule for a given VIP will increase processing by the delayed binding, but is this increased when adding additional L5 rules for the same VIP? Or does the rule matching algorithim use a hash function that doesn't cost extra to find additional matches, much like the Catalysts' TCAM processing?
If there's a CCO doc detailing this -- couldn't find one -- that would be even better.
it will require more processing time but not much. The box has a rule order. So it does check the rule was the most requirements, does all the checking and then fallbacks to rules with less requirements.
So, if you have currently a rule with just a url matching and add anoter rule with url + header-map it will require more processing as before the box did not have to look at the header-map.
If you do the reverse and already have url + header-map and add a rule with just a url, the box will continue to check header + url and if the header does not match but the url does, it requires a small extra step to fallback from rule 1 to rule 2.
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...