How to resolve service down event together with informing client this has happened possibly with TCP reset sending from CSS to client?
We have ordinary configuration with two real servers and two content rules for http (L5) and https (L4). When service is dying and is already down, CSS still have flow information in its table. Client who is connected to this service is hanging up waiting for application to time out. New connections are sent to the other live service as expected. Is there a way for CSS to notify client that this has happened, let say via TCP reset packet?
This could be done with "flow-reset-reject" command on content rule, but it is not functioning like expected.
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...