I have the following setup for load-balancing between two different web servers. I'm trying to apply stickiness by using cookies, and it appears to be working because all users have stuck to the server they originally connected to, but when I look in their cookie cache, I don't see one from the CSS. To be sure, I deleted all cookies and then went back to the site; still no cookies. Any idea where they went?
Sticky cookies are not maintained in the sticky table on the CSS. After the cookie is assigned to a client the client will store the cookie locally and provide it to the CSS when in session, therefore the CSS doesn't need to store it because the client is always providing it.
That's the reason why the cookies were not present in the cookie cache.
We have noticed the same thing. We are unable to locate the cookie (.txt file) on the client's workstation. I believe this could be due to the default arrowpoint-cookie expiration setting (expires when the client exits the browser), but it could also be due to the version of the browser the client is using (i.e.: Maybe IE6 keeps those type cookies on RAM and not on disk?). We instead setup the client's browser options (IE6) to always prompt when a site requests a cookie. When the prompt appears, you can click on "more details" to view the content of the cookie (where you should be able to see the string configured for the chosen service).
The cookies are stored on a DAT file on the client's PC. To view a cookie (with IE..):
Select Tools from the title bar
At the General tab click settings.
Then view files.
All Temporary internet cache is stored here, including cookies.
The ARPT cookie is stored in a text format and would probably be easier to find if you sort by type.
It should be there.
BUT, WHY are you using IP addresses in the string comand? I don't need an answer if you are using it as a potential 'honey pot.' But i would have thought something a little more cryptic could be interted in to the cookie!
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...