The part I want to use for stickiness is the "sessionid=" section in the beginning of the URL.
I have configured my content rules as follows:
add service testweb01
add service testweb02
add service testweb03
add service testweb04
vip address 192.168.1.1
string prefix "sessionid="
string eos-char "&"
Unfortunately this doesn't see to assign any stickiness (I still get all four servers in subsequent requests); I have tried using the "string process-length" command in place of the "string eos-char" command but the results are the same. Issuing a "show rule" command displays exactly what I would expect.
Can anybody give me any ideas on what I am doing wrong, or how I might troubleshoot this? Thanx.
Often times complex troubleshooting issues are best addressed in an interactive trouble-shooting session with one of our trained technical assistance engineers. While other forum users may be able to help, its often difficult to do so for this type of issue.
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...