Running the RSVP-TE LSP Optimization Tool
Procedure
Step 1 |
Choose Tools > RSVP LSP Optimization > Explicit Opt. (See Table 1 for field descriptions.) |
Step 2 |
Specify objectives for primary, secondary, and tertiary paths. |
Step 3 |
Identify which interfaces to optimize. The default is to optimize RSVP LSP paths on all selected interfaces, and by default, all interfaces are considered selected. You can, however, optimize a limited number of interfaces or specify a set of RSVP LSPs by preselecting them or by using tags. |
Step 4 |
Click OK. |
What to do next
Field |
Description |
---|---|
Primary Path Options |
|
Primary paths |
Define whether to reroute primary RSVP LSP paths:
|
1. Minimize # of interfaces with utilization > x % |
Specify a percentage and minimize the number of selected interfaces with utilizations over that percentage under normal operation (default). |
2. Minimize maximum interface utilization |
Route primary paths so that the maximum interface utilization over all selected interfaces is minimized under normal operation. |
3. Balance across equal latency paths |
Balance utilizations over lower utilized interfaces. For example, use this option to balance utilizations on parallel interfaces between two nodes if the two interfaces have the same latency.
|
Enforce latency bounds |
Enforce latency bounds that can be specified for some or all demands in the plan file. If checked, this option takes precedence over all of the preceding objectives. |
Secondary Path Options |
|
Secondary paths |
Define whether and how to route secondary paths.
|
Hot Standby |
Set the secondary path to be a hot standby, which means it is established at the same time as the primary path, rather than after the primary path fails. |
1. Maximize primary/secondary path disjointness with respect to |
Define primary and secondary paths for each RSVP LSP that are disjoint with respect to circuit, SRLG, node, and Layer 1 (L1) link failures, depending on what is selected.
|
2. Minimize # of interfaces with utilization > ___ %— |
Options 2 and 3 both operate on the selected failure scenarios (circuits, SRLGs, nodes, L1 nodes, and L1 links) listed in the “Failures to consider” options listed under 3. These choices are the failure scenarios over which the simulation is performed at the end of the optimization. Note that this selection of failure scenarios is distinct from the failure scenarios selected for the disjointness objective 1. Use option 2 to minimize the number of interfaces with utilizations over the specified percentage across all selected failure scenarios. |
3. Minimize maximum interface utilization |
Use option 3 to minimize the maximum interface utilization over all interfaces and over all selected failure scenarios. |
Tertiary Path Options |
|
Tertiary paths |
Define whether to create tertiary paths:
|
Hot Standby |
Set the tertiary path to be a hot standby path, which means it is brought up with the primary path, rather than after the primary path fails. |
Other Options |
|
Optimized Interfaces |
Identify which interfaces to optimize: all interfaces, those selected prior to opening the dialog box, or those with specific tags. |
Using RSVP LSPs |
Specify which LSPs are candidates for rerouting. The default is all the LSPs currently routed on the selected interfaces. |
Tag changed LSPs |
Create and add tags to all LSPs rerouted during optimization. Using tags makes it easier to find the LSPs that need to be reconfigured in the actual network according to the optimization results. By default, newly optimized RSVP LSPs are tagged as expopt . |
New plan for result |
This default option creates a new plan with the results of the optimization. Unless a name is specified, WAE Design attaches an -eopt suffix to the current plan filename. If unchecked, WAE Design changes the current plan file with the updated information. |
Details button |
Setting Optimization Details
Procedure
Step 1 |
Choose Tools > RSVP LSP Optimization > Explicit Opt. (See Table 1 for field descriptions.) |
Step 2 |
Click the Details button to identify less frequently used parameters, such as traffic levels and how to treat non-optimized interfaces.
Example: There are two non-optimized interfaces: cr1.chi_cr1.mia has a utilization of 60% and cr2.sjc_cr2.okc has a utilization of 78%. The acceptable utilization settings for non-optimized interfaces are:
Result: The maximum utilization for each interface is individually calculated. The acceptable level of utilization for cr1.chi_cr1.mia is 80%, and the acceptable level of utilization for cr2.sjc_cr2.okc is 83% (78 + 5).
|
Step 3 |
Click OK to close the Details dialog box. |
Step 4 |
Click OK. |