"We are relying on the Cisco CSS load balancer to provide our application with failover capability.
We're currently using the CSS KeepAlive mechanism to detect a failure of a service.
Our problem relates to those requests that reach CSS from the time a service has failed until its failure is detected by the load balancer's KeepAlive: These requests expose the failure to the clients.
Our application is a standard web application and is using HTTPS protocol. We are looking for a way to configure the load balancer to detect HTTP requests that failed (due to "connection failed" sockets exception) and to retry these requests on another service which hasn't failed.
We have been able to configure the BigIP load balancer to retry failed HTTP requests, and thus provide seamless failover capability to the end users.
In our BigIp implementation, we catch the load balancer event indicating that the connection to the server\service failed (for BigIp it is LB_FAILED).
In BigIp script code, we try connecting to current server 10 times, and if we fail we change the relevant server\service status to bad (not available).
Then we call the load balancer's reselecting function (which selects other server from the cluster).
We had to use some proprietary BigIp scripting in order to implement this.
Our question is how can we achieve the same functionality with the Cisco load balancer ?"
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...