WAE has most of the default traffic policies for msot of the well knowjn traffic. however, if you have any TCP / known traffic showing up under "Other" category, you can create a policy and classifier and try to optimize it. Please note that optimization may break traffic if it is not following standard tcp protocol.
Creatign a classifier is the only good way to analyze it unless you want to use netflow analyzers.
Hope this helps.
PS: If this answers your question, please mark this as Answered.
If you are referring to the "other traffic" that you see in the Central Manager GUI reports this actually encompasses all traffic not listed in the other 19 applications selected to display reports in the Central Manager. It does not necessarily mean that the traffic is not being optimized. The traffic that is not being optimized is classified as "Pass-through traffic" instead. You can change the applications you want to monitor but you will be limited to that and should expect to see the sum of the traffic from the remaining applications displaying in the "other traffic” category.
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...