I have been reading the Ace configuration manual and other resources but cannot find clear answers. I would like to clarify the Ace behaviour for the following please (or recommended reading):
Q. How does the Ace handle connection establishment to a server with the sticky setting and pattern matching.
We have a custom protocol, and clients cannot be uniquely identified by their source ip/port.
As a result, we will be matching the layer4-payload with a regular expression for a unique user id in our custom protocol, and making this assignment sticky. The client also needs to log on to our server.
At which point does the Ace setup a full tcp/ip connection?
- after the pattern match?
- after the user logon?
That is, are we forced to pattern match every single packet? If not, how does the Ace recognise the client without matching the payload?
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...