Exinda Network Orchestrator
3 Using
|
274
Catch-all. Any traffic that falls into a virtual circuit, but not into any of policies, will fall into the Auto Catch-all policy and
will not have any of your policies applied to it.
Consider the opposite scenario where you have more than one circuit that could capture the same traffic. For example,
you have two circuits that could both capture br10 traffic. The traffic will be evaluated against the virtual circuits and
policies within the first circuit. If the traffic does not match any virtual circuits and policies in the first circuit, then it will
attempt to match the traffic to the virtual circuits and policies in the second circuit. If the traffic does not match any of the
virtual circuits and policies in any of the matching circuits, then the traffic will fall into the Auto Catch-All virtual circuit
and Auto Catch-All policy in the last matching circuit and will not have any of your policies applied to it.
BEST PRACTICE
It is a best practice to explicitly create your own "catch-all" policy so that you can apply the appropriate control and
prioritization.
If traffic is not caught by a circuit or by a virtual circuit or by a policy, it will show up in the real-time monitor as an
Auto
Catch-all
circuit and an
Auto Catch-all
virtual circuit and an
Auto Catch-all
policy. The Auto Catch-all circuits and virtual
circuits will also be shown on the Virtual Circuit monitor report.
Enabling policies
Policies that are enabled are shown with a green checkmark in the policy tree. Policies that are disabled are shown with
a red x. You can toggle the enable state by clicking the checkmark or x.
NOTE
Whenever the Optimizer is modified, it must be restarted before the changes will take effect on your traffic. Restart
the Optimizer, by selecting the Optimizer menu in the status bar at the top of the screen.
Screenshot 125: Web interface menu
Related Topics
Adding a Policy to the Policy Tree
Re-using Policies from the Library
3.4.2 Circuits
Circuits define physical connections to the WAN/Internet. For appliances with more than one bridge configured, you
can bind each bridge to a separate circuit or you can treat all bridges as one combined circuit. Typically, when the
appliance is placed in line, one circuit would be created for each physical link.
When defining circuits, ensure each bridge is bound to a circuit; otherwise network traffic on any bridge that is not
bound to a circuit, will not be affected by policy and will be monitored in a catch-all circuit.
Summary of Contents for EXNV-10063
Page 369: ...Exinda Network Orchestrator 4 Settings 369 ...
Page 411: ...Exinda Network Orchestrator 4 Settings 411 Screenshot 168 P2P OverflowVirtualCircuit ...
Page 420: ...Exinda Network Orchestrator 4 Settings 420 Screenshot 175 Students OverflowVirtualCircuit ...
