I did numerous searches so I apolozie in advance if this has already been addressed.
In the past few days, I observed that SMB connections between our sites have become increasingly slow and, at times, unresponsive. This seems to loosely correlate to a number of logs in the WAAS indicating that connections to the domain controllers will be handled by generic optimization only, since the domain controllers require digitial signing.
I apologize for the previous post, I did not intend to submit it yet.
As I was saying, I have seen a number of logs in the WAAS device indicating that connections to the domain controllers will be handled by generic optimization only, since the domain controllers require digital signing.
I was hoping to reach out to the community to see if anyone else has observed this particular symptom as a result of generic optimization or had any useful links or documentation regarding what happens when generic optimization is forced.
I apologize again for the duplicate messages and thanks in advance.
Thanks for the reply. If SMB is being pushed to generic optimization, then those packets wouldn't cross with any real optimization, is that correct? In other words, from a latency perspective, that data would appear to not be optimized at all since they are signed.
The issue I am seeing is also intermittent but during the certain time it seems that it takes users longer (we timed this) to list the contents of a share and download the files. After some time, it seems that when a lot of users are having this issue it compounds and slower and slower to the point where it takes almost 20 minutes to list the directory contents.
When a connection is handled with generic optimization, it means that we are only apply the TCP-level throughput and compression optimizations. So depending on the WAN characteristics, you may not see any improvement in end user response time. You should, however, still see some bandwidth reduction across the WAN for connections handled with generic optimization.
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...