Take server out-of-service and route new HTTP requests to one of the other servers
We have several server farms configured on our ACE. We have sticky sessions configured based on either Hash Address or Least Connections. We also have TCP reuse enabled. When we take one server out of service, we can still see new HTTP requests going to the out-of-service server. We can explain this by the persistent HTTP connections (HTTP Keep-Alive).
What we want is that the currently executing requests can finish on the out-of-service server, but new requests should be handled by one of the other servers. The other servers may not drop their existing connections/sessions.
How can we force that new HTTP requests will no longer be deliverd to the out-of-service server? Will clearing the sticky table solve our problem? Or are there any other ways of accomplishing this?
Take server out-of-service and route new HTTP requests to one of
The default behavior of ACE is to take the rserver out of loadbalancing if it fails or is taken "out of service". Only existing connections are allowed to complete or connections matching the sticky entry. All new connections are loadbalanced.
You can tell the ACE to either remove the connections or reassign it to another server if you configure a backup server in serverfarm.You can find details here:
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...