OverviewCustomer notices traffic classified as ExindaCom, ExindaWM, ExindaAD and ExindaSSL in their reports.
Except for ExindaAD, these applications refer to traffic that is generated to/from Exindas while they are performing acceleration, these processes need to be in constant communication to achieve proper acceleration of packets:
ExindaCom means "Community" which is a way of all the exindas participating in the acceleration process to discover each other in order to further exchange important information. The exindas communicate on tcp port 8017, back in older firmware versions we used tcp port 8014 for a previous version of community, but this is just a legacy service in case there are exindas in the community running versions 6.1 or older. When it comes to classification, both ports are classified as ExindaCom
ExindaWM stands for "Wan Memory" which is the process in charge of reduction (Compression and Deduplication). The exindas communicate essential information with each other at the moment of accelerating packets. This service runs on port 8013.
ExindaSSL is for exchange of information that is necessary to perform acceleration on SSL traffic (Certificates, private keys, IPs of SSL servers). This process runs on tcp port 8018
ExindaAD stands for Active Directory, this process is in charge of receiving Users&Group information from the Active Directory server when users want to integrate the Exinda with the AD. It runs on tcp port 8015. NOTE: This is the only one of these applications that is not-acceleration related and could potentially occupy an important percentage of the link bandwidth. In order to avoid this, we recommend to carefully follow the hints of the AD Integration Guide available on our website.
These applications however, (Except for the ExindaAD one as per the note) should not occupy a high percentage of the entire pipe, so the chances of one of these applications to become part of the top 10 are very low. Nevertheless, if the user still notices either one of these application objects using too much bandwidth, there is a chance that there is a third party application running in the network using either one of the tcp ports mentioned above