Re: CSS11501 Simple SSL (HTTP to HTTPS) configuration
We have it working very well now, with one slight workaround:
The SSL-HTTP proxying worked fine. We have only one content rule for client facing, and for to where the ssl-proxy-list redirects. When we added another L4 rule to redirect port 80 requests to port 443, we ended up with a loop.
To resolve this issue we changed the HTTP port on the webservers to 81, and used this port in the ssl-proxy-list.
I assume if we had two separate content rules (one for client facing, and one for the ssl-proxy-list to forward to), we would not have had this issue?
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...