Normal (Non-Resilient) Options
|
Minimize maximum interface utilization
|
This default is usually the primary objective, and concentrates on reducing the utilization of the interface with the highest
utilization.
|
Minimize # of interfaces with utilization > x
%
|
Often a small number of interfaces are bottlenecks in the network, and their utilizations cannot be reduced through rerouting.
However, it is still desirable to reduce the utilization of other, under-utilized interfaces. This option tries to reduce
all interface utilizations to below a specified utilization level, or, if this is not possible, to minimize the number of
interfaces over this level.
|
Minimize average latency
|
If after the optimizations flexibility is available in the choice of metrics, WAE Design uses this flexibility to minimize
the average latency of the routes across the network. This is not user-configurable and is always on.
|
Enforce latency bounds
|
If checked, the choice of paths for each demand is restricted, if possible, to those demands with latency below the latency
bound.
|
Failure (Resilient) Options
|
Minimize maximum interface utilization
|
If checked, WAE Design selects metrics to minimize the maximum interface utilization over all interfaces and all failure scenarios.
If unchecked, only normal operation is optimized, and the remainder of the failure section is ignored.
|
Minimize # of interfaces with utilization > x
%
|
The number of interfaces with utilization (under any failure scenario) above a specified percentage is minimized.
|
Enforce no-failure utilization bound
|
If unchecked, maximum failure utilization is minimized with no consideration for utilization under normal operation. It is
often convenient to check this option and place a bound on the utilization under normal operation, which Metric Optimization
then satisfies, if possible.
|
Failures to consider
|
This option determines the failure scenarios over which optimization is performed. You can select any combination of failures.
This option does not consider port or port circuit failures. For information on protecting objects from being included in
this analysis, see Simulation Analysis
.
To control the number of threads that WAE Design processes in parallel when examining failure scenarios, set the Maximum number of threads field.
|
Other Options
|
Optimization Type
|
WAE Design can perform global or incremental metric optimizations.
-
Incremental—Uses the current routes as a basis from which improvements can be made. The target routes are not changed as
radically as when using global optimizations, and therefore the number of metric changes from the metric targets is typically
much smaller using the incremental option.
-
Global—Creates optimal routes from scratch, and targets the old metrics afterward. Because WAE Design can choose routes globally,
this option tends to perform better under some circumstances, particularly when the target routes are poorly chosen. However,
global optimization typically takes longer than incremental optimization.
|
Set Metrics on Interfaces
|
By default, WAE Design sets or changes metrics on any of the core interfaces in the network to achieve its optimization goals.
Alternatively, as provided by this option, Metric Optimization restricts metric changes to the following interfaces: all,
core, selected in table, or tag name.
|
Traffic Level
|
The traffic level over which the optimization is performed.
|
Interfaces to Optimize
|
By default, WAE Design optimizes all interfaces. You can restrict the optimized interfaces using this option and choosing
the Optimize utilization on interfaces value: all, core, selected in table, or tag name.
For those interfaces that are not optimized, you can set the following:
|
Target to Current Metrics
|
There are many sets of metrics that will result in equivalent sets of routes. (Doubling all metrics, for example, does not
change routes.) WAE Design selects between these sets of metrics by metric targeting. Metrics can be selected to match as
closely as possible the current metrics in the network. This simplifies the changeover from one set of metrics to the next.
Targeting optimized metrics to the current metrics in the plan is performed by default. Various targeting refinements are
available as CLI options to specify upper and lower bounds on metric selections.
|
Enforce Symmetric Metrics
|
This option sets the two metrics on each interface of each circuit equal to one another. This constraint can reduce optimization
performance. However, it ensures that demands from A (source) to Z (destination) and from Z to A (in the core) take the same
path, and so the chances of a session between A and Z being interrupted by a failure is minimized.
|
Prevent Edge Leakage
|
This default option restricts how WAE Design can change demand routes. If a demand starts by routing only through the core,
or from the edge through the core to the edge, this option prevents the routing from being changed so that it routes through
the edge in the middle of its path. This is usually a desired routing policy restriction.
|
Simulate after optimization
|
This default option performs a simulation analysis after optimizing metrics. The simulation analysis allows a detailed view,
for example, of the utilizations under failure resulting from the new metric settings.
|
New Plan for Result
|
This default option creates a new plan as a result of running Metric Optimization. Unless a name is specified, WAE Design
attaches the suffix -mopt
to the plan filename. If not selected, WAE Design changes the current plan file with the updated information.
|