In debugging why random users get an Internet Explorer "page not found" error when connecting through our new content switch to our web servers, I have tracked down the problem from debug logging on the content switch.
The error that appears in the log of the CSS11503 when the user's IE is unable to find the page is:
This error is on the server side. The CSS is sending the spanned content request to the server and either did not get an acknowledgement or got an unexpected response or more likely in this case the client
side was torn down. In the example you gave the two log messages came together, So perhaps the client closed down in the middle.
I would suggest to capture a sniffer trace of the problem and see what is going on there.
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...