Folks I am new to this forum, have a question on the http header we see ACE-LB is setting set-cookie value being set on every http get response though http get request comes with a valid cookie and valid rserver same cookie has been set on get response is that normal or any impact on this?
Any idea what is causing this behaviour? Is that something to do with Persistant Rebalance Param Map, what exactly this will do?
Is there any impact if the same cookie is being sent as "set-cookie" header tag again and again for all response to same client?
Gilles is absolutely correct in his reply, but in addition, you may want to read the section in our documentation on header modify per-request, for more information on persistence-rebalance and how it differs from header modify per-request.
While it is harmless to your connections add the cookie to every response, if it is not needed, I would recommend turning it off.
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...