When enabling CIFS acceleration for the first time (TFO works fine), I created a connectivity directive between the edge and the WAE. I did not specifically define file servers for the core. Users at the edge site began having logon problems and either couldn't logon or got temporary profiles. I noticed that I did not have DNS settings configured on the edge WAE. Could this be the reason for the logon issues or is there something else I should look into?
I've seen issues where there is port speed/duplex issues. You can check those (it's always the last thing I check and often it's the issue).
Where is the AD server w/profiles, local, behind the core or at a third site? Do you see the CIFS connections in your "Sh tfo con summ" or are they inside the CIFS tunnel "sh cifs session list"? Usually login servers have SMB Signing enabled, so they should show up as optimized full in "sh tfo conn summ".
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...