CSM : Slow Start not working with leastconns predictor
In my configuration, I have 2 real servers. The serverfarm is configured with "predictor leastconns slowstart 60". The current REAL_SLOW_START_ENABLE variable is set to its default value of 3. To test the slow start feature, I suspended on server and established 50 sessions on the working server. Then, I reactivated the first server and sent 50 new sessions. I observe that all new sessions are established on the "new" server ! the second server has still 50 sessions. The slow start seams not to be working...
What is the exact algorithm of the CSM with this setup (variable = 3 slowstart = 60) ?
Re: CSM : Slow Start not working with leastconns predictor
It seems that your CSM is more cooperative as mine ;-).
So to be sure that the CSM itself is not in question, I did the test on another CSM with only two servers in the serverfarm (instead of 8 as in the original case). Yes, the version of the CSM-S is still 2.1(2a). Yes the new sessions have been sent within the slowstart window. The same is observed when the slowstart timer is set to 600 actually. No connections were established on the first server at the time of its reactivation.
To document this problem , I attached a file showing all relevant configuration elements and a sequence of show commands demonstating the sessions ramp-up when the 50 new sessions are sent. In addition, I give you at the end of the attached file, the TCP script I use to generate session from my PC. I don't think that it is the problem however.
Thanks again Gilles for your support, it great. We are in trouble with this issue, which prevent us to put our Global portal in production...
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...