I’ve got a question regarding stickiness in relation to Microsoft ISA servers.I have configured stickiness based on source ip address, but I understand that ISA servers reverse-proxy their client requests, hence making the requests look like they’re coming from only the ISA source ip addresses.I am worried this will make even load-balancing difficult.
In the same environment we have 1000’s of other clients who will also be hitting the ACE looking for content.My question is how do I differentiate requests coming from the ISA servers to those coming from the “normal” clients, so I can treat them differently (to try and balance them across all real servers)?
Normal clients I believe should be load-balanced, with stickiness based on source ip. However to distribute the ISA servers requests, perhaps I should base stickiness on something other than source ip, maybe cookie – or turn off stickiness and load-balancing for the requests?
Either way I presume I need to differentiate the traffic using class-maps, then use policy-maps to specify the action to take.I would be grateful if someone could provide a sample config of how to do this.
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...