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.
![]() |
Version Info:
|
---|
Figure - Circuit form for versions 7.0.2 and earlier
Figure - Circuit form for versions 7.0.2 Update 1 and later
Circuits are part of the policy tree. To learn how circuits, virtual circuits, and policies work together, see Policy Tree.
Go to Configuration > Traffic Policies > Optimizer > Optimizer, then click the Create New Circuit... link at the bottom of the page or edit an existing circuit.
A bridge can be assigned to more than one circuit. Once a type of traffic matches a virtual circuit and policy, it will not be processed by later circuits, virtual circuits, and policies. If the type of traffic does not match any policy in the first circuit, then it will attempt to match the policy in the second circuit.
For example, consider where circuits, virtual circuit, and policy are defined as:
In this case, br10 is assigned to both circuit A & B. However, br10 is bound to circuit A first.
Identify the available Inbound and Outbound bandwidth of the circuit.
Specify the bridge or out-of-path interface to bind the circuit to.
All bridges, individual bridge names, policy-based routing interfaces, and WCCP interfaces are available.
|
|