SummaryWhen looking at the Exinda Optimizer, the Circuit level is the highest possible level in the heirarchy, meant to represent your physical pipe.
OverviewThe Circuit in the Optimizer of the Exinda represents a physical connection. While it can be further subdivided into Virtual Circuits and Policies, the Circuit level itself is the highest possible level. Any connection coming into the Exinda (whether it spans one bridge, or multiple bridges) should be considered a circuit. For example, if a topology has multiple physical connections coming in, such as a standard internet link and an MPLS link, each one should be its own Circuit in the Exinda.
The bandwidth assigned to a circuit should be reflective of the bandwidth of the physical connection going into the device. The Exinda will use the circuit size as a determination as a maximum speed to shape traffic to at a basic level. From there, it will subdivide into the effective bandwidths for Virtual Circuits and the policies.
For example, if a circuit bandwidth is set to 10Mbps, all traffic going through the Exinda - whether it is shaped by a virtual circuit or policy or neither - will only get a maximum of 10Mbps, regardless of how big the physical connection is. If an ISP is providing a bandwidth of 200Mbps, the Circuit size for that link should be 200Mbps, otherwise bandwidth will be missing and performance will not be as expected for the device.
Also if main network link is upgraded for e.g from 20M to 40M then along with increasing the circuit size, make sure that Exinda license is also upgraded from 20M to 40M else it will show optimizer error.
One can upgrade or downgrade the main circuit size of Exinda only after verifying if its license can supports that amount of traffic, Once verified upgrade or downgrade navigating via
Optimizer > Edit Main Circuit > Change the value of Inbound Bandwidth and Outbound Bandwidth according to the need > Apply Changes > Restart the optimizer