I'm experiencing some strange behavior having configured cookie stickiness. In the request towards the CSS I see a cookie. The request is not forwarded to the correct server but to another server. Normaly this is working except if we are having some HTTP-Continuations. Is it possible, that the CSS is not listening correctly to this request or is missinterpreting something which leads to a rebalancing of the request instead of sticking to the correct server.
If I do layer3 stickiness and a layer 4 rule everything is working fine but I need to have cookie stickiness.
I fouind the reason. It's the spanning packets command I've to use as in default "only" 6 packets are checked for the sticky string. The problem was that the last part of the string was in packet 7 or 8 and therefor it was not parsable.
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
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...