I am investigating a load balancer issue and have been told some things about SSL stickiness on the 1100 catalyst that I would like to confirm.
Firstly, we have an environment where SSL stickiness has been turned on and based on IP address. We are not using SSL Session IDs and therefore are not using this to track the source.
I have found that even with this set, the requests still get sprayed to both backend servers. It doesn't maintain the stickiness to the same backend server. Does anyone know why this would be? Maybe the setup is wrong, I don't know.
The other thing is what I heard was that in order for the SSL stickiness to be maintained, you needed to use a cookie instead. If so, is this supported on an 1100 and where does it store the cookie - in each browser from the same IP or different cookie for each browser regardless of IP?
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...