SummaryWhen the optimizer is turned off on the Exinda appliance, it is still possible to see the recommendation engine on the dashboard inform the users that there is traffic falling into the auto catch all circuit.
OverviewThe recommendation engine is a feature of the Exinda that shows administrator suggestions based on what the engine finds in the system, such as high volume traffic which isn't being shaped, or traffic that has been missed to the point where it might be a good idea to look for it and see if it was forgotten about. The recommendation engine shows on the dashboard in a blue stripe near the top of the page, and has dates beside the recommendation to let users know when they were suggested.
When the optimizer is off on an Exinda (and thus not shaping any traffic), it is possible for the recommendation to say the following alert:
- The circuit - Auto Catch-all - has traffic that was not caught by a virtual circuit. Exinda recommends that you investigate by looking at the Virtual Circuits monitor or Real Time monitor, then redefine your virtual circuits to capture all of the circuit data.
CauseThis alert should theoretically only be shown when the optimizer is on, because it references a circuit, which is a part of the optimizer. The Auto Catch-all circuit is an invisible circuit which is implicitly at the bottom of any optimizer configuration to take in traffic that does not fit into any other circuit. This is to ensure that traffic is not dropped, but the admin is still at least alerted to its presence, which is done by the above recommendation alert. This traffic shows up in the real time monitor under the policy "Auto Catch-All: Auto Catch-All", if 'Show Policies' is turned on.
However, the alert can still be shown when the optimizer is off. This is due to the fact that the recommendation engine works in part with the collection and monitoring processes that are still working to catalog and categorize the traffic going through the Exinda, regardless if the traffic is being optimized. These collection stats are also compared against the policy tree in the configuration (though not actually applied against it). If there is traffic coming through the Exinda that would not have a home in the optimizer, it would notify the recommendation engine as such, and the alert would still come through to the dashboard.