SummaryIf a physical link has a guarnateed bandwidth, but for some reason can either fluctuate to a lower or higher bandwidth, it is not possible to set the Exinda to dhynamically adapt on the fly to this changein available bandwidth
OverviewThe Exinda 'Circuits' are equivalent to physical links - that is, they are the top level heirarchy before any subdivisions based on application or IPs are done. This means that they should be analogous to the bandwidth of the physical links going into the bridges of the Exinda appliance. There might be cases where a physical link from an ISP will give a guaranteed bandwidth but the ISP can send more if it is available on their side. That means that a link is guaranteed X Mbps, but can potentially get as high as Y Mbps.
While the Exinda can monitor and record information such as the throughput at the interface level, it does not have mechanisms involved to interpret this data at an optimizer level. The optimizer typically has a circuit bandwidth that is set, and all optimizer virtual circuits will adhere to that value. That circuit value cannot dynamically fluctuate if the throughput received at the interface is more than what it is set for.
What can be done in this situation, if it is known when the ISP will be delivering more bandwidth, and exactly how much bandwidth, two separate configurations can be made, where the circuit sizes differ. These configurations would have to be changed manually by an administrator. As a result, the change of bandwidth would have to be on a regular schedule or be known ahead of time, making it difficult if it's a 'random burst' link provided.
Configuration 1, for normal use - Circuit is 1M. All the virtual circuits and policies are set for percentages
Configuration 2, for burst use - Circuit is 2M. All the virtual circuits and policies and set for percentages
In order to create a new configuration, it can be done on the web UI on the Configuration > System > Maintenance page. There is an option to 'save as' your configuration as a new file. From here, switching to the new configuration made will allow for it to be changed without modifying the original.
Alternatively, this can be done through the CLI through the commands:
configuration copy [original file] [new file]
configuration switch-to [new file]
That will copy a configuration to a new one and will switch the configuration over to the new file so modifications can be made.