I am with a doubt about the traffic mapi intercepted by waas. I have a topology inline in both side Data Center and Branch office , but I see HTTPS, HTTPS works fine but MAPI I do not understand if a have a gain in acceleration, optimization or compression.
I only see this in reports.
MAPI: Acceleration Bypass Reasons
I understand that I am with a problem. My customer did a change in the exchange server that he disable cryptography connection, but I think its not solve.
We had significant issues with eMAPI, due to our domain structure (one domain, but "sub" UPN names)
Our users are "@country.domain.com" in "domain.com" and in previous WAAS versions, this did not work well (blacklisted identities, claiming domain identity was not present, whilst that was not true, as all users are member of one single domain)
WAAS 5.4.1 solved that for us, and we now have a +50% reduction on all mail traffic.
In your experience. You solve your issue about domain creating a user to WAAS in each sub-domain or you create only one user in a parent domain?
I would like to know because in my case the mail server is in the parent domain and users are configured to another domain. And my customer do not want permit create a WAAS user in the parent domain with all privillege because the security.
Today I have version 5.3.1 installed and the sub-domain appears in the black list with the follow status.
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...