If "connection failure" is not a bug + Multi-Vlan SrvrFrm!
ACE-gurus & Gilles ,
First Query: We are facing "connection failure" counter increment, what all could be the reasons for this failures and what can be done to minimize it, if its not a bug, running 3.0 A2(1.0) ?
Second Query:I have a single farm with multiple vlans in it with URL hashing, we see that the load distribution on the caches in unequal, to say, 1 vlan with 1 server gets 500Meg of traffic and second vlan with 2 caches gets 400Meg of traffic which is almost equally divided between the 2 caches, its seems suspicious to the customer that the vlan is impacting load distribution, though we know its not possible to impact.
We do heavily suspect the kind of traffic entering the ACE like videos from various known sites goiing to 1 cache, on this with URl hash, does ace hash the whole URL, like www.abc.com/cat/video/ or just the domain, abc.com ??
IMHO its the whole URL, but need some confirmation on it, and to optimize somewhat equal distribution to the caches of traffic bytes ( as the no. of connections are almost equal.) what can be tweaked in the URl hash algorithm to make things work.
Have very little time to come up with a workable solution.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20080404 Firefox/220.127.116.11
here "/resources/abc.htm" will be the requested url and "www.reuters.com" will be the Host.
Url hash only takes url into consideration. If you want to use host to calulate hash then you will need
"predictor hash header Host" command.
Connection failure normally occurs due to backend server connections. There were few bugs open according to which this counter incremenents due to invalid client requests, when persistence rebalance is configured and no L7 matching occurs and in case of TCP resets. I am not sure if these are still open for A2(1).
You can play with "predictor hash url begin-pattern < > end-pattern < >" to improve the distribution.
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...