I have configured the CSS in our test lab. I have done a basic configuration. When I go into the Web browser and put in the VIP address, I get nothing displayed. I currently have a CDM pushing data to my CE device. I have my services configured and they are active.
Have you looked at your return path, i.e. the path the traffic will take from the server back to the client?
For the CSS to work properly, it needs to see the traffic in both directions. If the path through the CSS is not the optimal path for return traffic (or you are in a "one-armed" configuration) you will need to setup a source group with a VIP address that makes sense for your scenario and add your service as destination services in the group.
This will result in the CSS NAT'ing the source address of clients before the sessions are forwarded to the backend server, thereby forcing the return traffic through the CSS. Hopefully, your server app doesn't need to see the true client IP addresses, (most don't). If it does, you'll need to place the CSS in-line between the client(s) and server(s) from either a L2 or L3 perspective.
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...