This configuration would only work only if you're doing SSL offloading on the ACE, you don't need stickiness for the 80 connection because the redirect service is a fake rserver intended only to do HTTP redirection, once the connections goes over port 443 all the L5 data is hidden for the ACE so cookie inspection is not possible anymore.
If you're not doing SSL offloading on the ACE then you might want to configure sticky based on Sticky srcIP (not good if connections comes from a proxy) or also based on the SSL session ID.
If you need any examples of this two methods, ping back.
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...