I wonder if anyone could shed some light on a developement here.
We have service that is currently being load balanced. Very basic -
2. port 9081
3. two servers
4. one serverfarm
5. stickines required (originally and currently on source IP)
Issue now is that the client connects via Data Power servers, which first of all proxies tha connections making source IP stickiness pointless (we are not getting any load balancing) and the client connection via HTTP gets modified by Data Power into SOAP/HTTP xmlns.
My question is could we use Layer 4 payload stickiness? I have attached the data portion of the first frame after the TCP setup (all traffic seem as TCP), have also added port 9081 to Wireshark and only see two HTTP frames once all data transaction has completed), no cookies.
What could we use from this, if anything, for the stickiness on layer 4 payload? I was thinking of theFE_GEN_USER_ID if it is unique for each user, so config something like:
sticky layer4-payload PAS-STICKY
policy-map type loadbalance generic first-match LB-POLICY
Am a bit stuck on this one. Many of the other existing servics that are currently being load balanced will eventually migrate to be front-ended by the Data Power devices, so I am sure we will run into this again.
Any assitance would be greatly appreciated as always.
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...