You can use the SR-TE Optimization tool to design, capacity plan, and manually configure networks to meet the following objectives:
TE Metric or Delay Minimization—Minimize distance between hops with respect to metrics other than IGP metrics. These can be either TE metrics configured on interfaces (which can be set proportional to circuit latency) or latencies (delays) for each circuit. An example application is a differentiated service in which latency-sensitive network traffic is routed on shortest latency paths, while the bulk of the traffic routes over cost-optimized paths.
Avoidance—Create or optimize segment lists so they avoid routing through specified objects (nodes, interfaces, L1 links, L1 nodes, or SRLGs). An example application is routing pairs of LSPs, each over a different plane in a dual-plane network. The same traffic is routed over both LSPs simultaneously, thus improving availability.
While there is an option to specify a maximum number of hops, doing so might not achieve the lowest possible latency. In this case, the best achievable solution is provided.
You can additionally avoid unnecessary LSP churn by specifying boundaries (bounds) on the path length and margins within which the shortest path must be optimized.
Note Unless qualified with “TE” or “IGP,” the term metric in this chapter applies to IGP metric, TE metric, or delay.
Optimizing SR-TE LSPs
Tools > SR LSP Optimization > SR-TE Opt
. Then identify which SR LSPs to optimize: all SR LSPs, those selected before opening the dialog box, or those with specific tags. The default is to optimize all selected SR LSPs, and by default, all SR LSPs are considered selected.
Parameters for optimizing explicit LSP paths are specified in the Bound, Margin, and Constraints areas of the dialog box. If you do not specify a bound, margin, or constraint, WAE Design generates the best possible SR LSP routes for the given path metric.
A segment list is created or updated for all SR LSP paths that can be optimized using the minimum number of segment list hops possible.
– If an LSP has a directly associated segment list, the segment list is deleted.
– If an LSP has no LSP paths, an LSP path with a path option of 1 is created.
– If an LSP has no segment list, but it has LSP paths, a segment list is created for the active path if it exists and if not, for the lowest path option (where lowest means the smallest value).
– If an LSP has associated LSP paths and a segment list associated with either the active path or lowest path option, the segment list hops in the segment list are updated.
Example: Figure 22-1 shows an SR LSP that normally routes from AMS-FRA-PAR based on IGP metrics. It has no LSP paths. All circuits have a Delay Sim value of 50 except for the AMS-FRA circuit, which has a Delay Sim value of 60. Optimizing this SR LSP based on delay results in rerouting the SR LSP over the shortest achievable delay path, creating an LSP path with a path option of 1, and creating a segment list node hop on the cr.lon node.
– The final hop is either a node hop or interface whose remote node is the destination of the LSP.
If it is not possible to achieve the lowest possible path without exceeding the specified maximum number of segment list hops, WAE Design provides the best achievable solution within this restriction of maximum permissible hops.
If it is not possible to avoid all specified nodes for an SR LSP, that SR LSP is not updated.
If an existing segment list would be better optimized by removing all segment list hops, those hops are removed, though the segment list remains.
If a previously optimized SR LSP does not need further optimization, it is not changed and its previously set SROpt tag is removed.
If the source and destination nodes are in different IGP areas, WAE Design creates an explicit hop on the most optimal ABR for each IGP area that the SR LSP traverses.
Figure 22-1 Example SR LSP Optimization
Optimizing the Path Metric
The Minimize Path Metric selection defines whether to optimize SR LSPs based on interface IGP metrics, interface TE metrics, or circuit delays. This minimization is for the sum of the metrics along the path. Note that for inter-AS SR LSPs, these metrics are calculated end-to-end for the LSP, not per AS. These properties are configurable from an interface Properties dialog box, and delays can also be set in a circuit Properties dialog box.
Bound and Margin
Bounds and margins identify which paths to optimize, as well as when to stop optimizing a given path. If you enter a value for more than one restriction, WAE Design uses the strictest limitation as the optimization target. If there is no bound or margin specified, WAE Design optimizes LSP paths to the best possible solution (lowest total metrics for the LSP path).
Bound: Maximum Acceptable Path Length
The Fixed Bound entry lets you set the maximum path metric that is acceptable. WAE Design tries to optimize LSP paths with metrics that exceed this bound. If a solution adhering to this bound cannot be found, the best possible solution is provided and bound violations are listed in the report. LSP paths that are less than or equal to this bound are not optimized.
Example: If you select to optimize LSP paths based on TE metrics, the value entered is 50, and the sum of TE metrics on the LSP path is 51, that LSP path is optimized.
Enter a number based on the selected path metric. A TE metric is a property values whose total sum for the LSP path cannot be exceeded. The delay is also a property value, but it is in milliseconds (ms). If you enter “50” and you have selected delay as the metric to optimize, this represents 50 ms as the maximum acceptable delay for the LSP path.
Margin: Maximum Acceptable Metric Above Shortest Path
The Margin entries let you identify the acceptable deviation above the shortest achievable path metric. Any existing LSP path with a metric that is less than or equal to the shortest path metric plus the margin is not optimized.
Fixed—The amount by which a metric must be surpassed before it is optimized.
Example: If an SR LSP route has a delay of 110 (as in Figure 22-1), a fixed margin set to 10, and the shortest achievable delay path is 100, the current SR LSP is within the margin and will not be updated (Figure 22-2). If the fixed margin is set to 9, the SR LSP would be optimized.
100 (shortest path) + 10 (fixed margin) = 110, so all paths greater than 110 are optimized
Percentage—The amount by which a metric must be surpassed, expressed as a percentage of the shortest path, before it is optimized.
Example: If an existing SR LSP route has a TE metric of 210, a percentage margin set to 10%, and the shortest achievable TE metric path is 200, the current SR LSP is within the margin and will not be updated. If the current SR LSP had a metric of 225, it would be optimized.
200 (shortest path) x .10 (percentage margin) = 20, so all paths greater than 220 must be optimized
Example: If an SR LSP route has a delay of 110 (as in Figure 22-1), a fixed bound is set to 120, a fixed margin is set to 15, a percentage margin is set to 5%, and the shortest achievable delay path is 100, the strictest of these restrictions takes precedence, and the SR LSP is optimized (Figure 22-2).
Fixed Bound = 120
100 (shortest path) + 15 (fixed margin) = 115
100 (shortest path) x .05 (percentage margin) = 5, so all paths greater than 105 are optimized because it is the strictest margin
Figure 22-2 Example SR LSPs Optimized with Margins
The constraints let you specify restrictions for the optimizations.
Maximum Segment List Hops—The maximum number of segment list hops that any given segment list can contain after optimization. If no value is specified, WAE Design creates as many hops as needed to optimize the SR LSP.
Avoid—Do not permit optimized segment lists to route through the selected or tagged objects (nodes, interfaces, L1 links, L1 nodes, or SRLGs). This constraint is useful when modeling dual-plane topologies that route disjoint LSPs.
Figure 22-3 shows an SR LSP from cr1.chi to cr1.mia that is routed based on its shortest IGP route. It also shows the optimized SR LSP path if it were to avoid cr1.okc based on its tag.
Restrict segment nodes to core nodes—Segment list node hops must be core nodes (nodes that have their Function property set to “core”), and the local node of segment list interface hops must be a core node. An SR LSP could still route using edge nodes if they are not used as hops.
Figure 22-3 Example of Avoiding Tagged Nodes During SR-TE Optimization
Using SR Tags and Creating New Plan Files
These options identify how optimized SR LSPs are tagged, and whether to create new plan files with the results:
Tag updated LSPs with—Create and add tags to all SR LSPs rerouted during optimization. Using tags makes it easier to find the changed SR LSPs that are deployed to the network or to find those SR LSPs that need to be reconfigured in the actual network according to the optimization results. By default, newly optimized LSPs are tagged as
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
suffix to the current plan filename. If not selected, WAE Design changes the current plan file with the updated information. Saving this plan file then simplifies the process of identifying which LSPs to reconfigure in the network.
Upon completion, WAE Design writes a report containing the results of the optimization, as well as verifications that the results met the criteria for avoiding nodes and meeting the specified bounds. To access this information later, choose
Window > Reports
SR-TE Bandwidth Optimization
The goal when reducing traffic is to reroute as few demands as possible. This is achieved by creating private SR LSPs for demands. The SR-TE BW Optimization tool also creates LSP paths and segment lists for these LSP paths with the fewest node or interface segment list hops possible, with a maximum of three hops. The final hop is either a node hop or interface whose remote node is the destination of the LSP.
The tool operates on a set of constraints that determine which paths are selected, whether demands and LSPs can be rerouted, and whether demand latency bounds can be surpassed. If the traffic cannot be reduced to below the threshold given these constraints, private SR LSPs are still created to route demands to reduce congestion as much as possible. If interface utilization surpasses the threshold prior to the optimization, it does not go higher. Utilization of non-congested interfaces might increase, though these will not surpass the threshold.
The tool reroutes existing SR LSPs only if they are private to a demand.
You can run the SR-TE BW Optimization tool in two modes:
Analysis—Performs multiple optimizations, one for each failure scenario within the specified failure set. The results of these optimizations are aggregated in a report.
Operation—Performs an optimization using a specified set of constraints.
An output plan file is produced with the optimization results. Only a single state of the network is considered. For example, if no objects are failed in the input plan file, the optimization is performed for normal operation. If a circuit is failed in the input plan file, the optimization is performed considering this particular failure scenario.
Both the analysis and operation modes use the same dialog box for specifying bandwidth constraints:
Path Selection—When choosing demand routes, the SR-TE BW Optimization tool uses one of two criteria:
– Maximize Available BW—Paths are optimized to achieve the highest available bandwidth on interfaces (Capacity Sim - Traff Sim).
– Minimize Metric—Paths are optimized to minimize the sum of the metrics along the path with respect to delay, TE, or IGP metrics. All of these properties are configurable from an interface Properties dialog box, and delays can also be set in a circuit Properties dialog box.
– Create Interface Segment Hops—If checked, the tool considers interface hops when trying to drive down utilization.
– Create new LSPs—If checked, new private SR LSPs with optimized routing can be created. If unchecked, new LSPs are not created.
– Fix LSPs—Controls whether or not LSP routes can be modified. This constraint is useful if you want to reroute existing LSPs to mitigate congestion.
– Fix Demands—Selected or tagged demands are not rerouted. This constraint is useful, for example, when you have previously optimized specific LSPs within the network and want to maintain the route of one or more existing demands.
– Enforce latency bounds—If checked, demands cannot surpass their configured latency bound. (This property is set in a demand’s Properties dialog box.) If the latency of rerouted demands exceeds the configured bound, the tool does not reroute demands on congested interfaces.
Bandwidth Optimization Report
Upon completion of a basic optimization, the SR-TE BW Optimization tool generates a summary report to identify key changes due to the optimization. The tool tags the LSPs with
and generates a new plan file with an
suffix. This plan file opens, showing the LSPs table that is filtered to these rerouted (and newly tagged) LSPs. Saving this plan file then simplifies the process of identifying which LSPs to reconfigure in the network. Both the tags and the new plan filenames are editable.
After running the bandwidth optimization, the optimizer creates a summary report of the:
Number of interfaces that exceeded the utilization both before and after the optimization.
Maximum utilization both before and after the optimization.
Number of demands that were rerouted.
Number of LSPs that were created and rerouted.
Average segment list length.
Number of latency bound violations both before and after the optimization.
Figure 22-4 shows a network before bandwidth optimization. It has no LSPs, and there is congestion between San Jose (sjc) and Los Angeles (lax), as well as between Los Angeles (lax) and Houston (hst). Sorting the Util Sim column shows the top five highest utilizations with two of them higher than 90%. Notice that the demand from sjc to hst routes directly over these highly used interfaces.
Figure 22-4 Network Before Optimization
To optimize the maximum available bandwidth to be below 90% and to enforce latency bounds, the following parameters are set:
Congestion threshold = 90%.
Base the rerouted paths on maximizing available bandwidth.
Enforce latency bounds.
The result of this optimization is that no interfaces have utilization over 90%, and the interfaces with the highest utilization are different interfaces than prior to the optimization. Figure 22-5 shows this redistribution of traffic across the network. The only demand rerouted was the one between sjc and hst, which you can compare to Figure 22-4.
Figure 22-5 Network After Reducing Utilization to Below 90%
Figure 22-6 shows this same network, but with a failed circuit between Seattle (sea) and Chicago (chi). There are three interfaces with over 100% utilization. Here, the SR-TE BW Optimization tool was rerun using the same parameters as above except the congestion threshold was set to 100. Although congestion cannot be completely mitigated, the tool minimizes congestion as much as it can, leaving only one interface congested (over 100% utilized).
Figure 22-6 Optimized Network Under Failure
Step 1 Skip this step if you are using tags. You can also skip this step if you want to run the tool on all interfaces, and if you are not selecting demands to fix.
If you are fixing selected demands or running the optimization on selected interfaces, select them before opening the dialog box.
If you are selecting one or the other, do so from their respective Demands or Interfaces tables.
If you are selecting both, make your selection in one table, and then press and hold the Alt key (Option key on a Mac) while making selections in another table.
Step 2 Choose
Tools > SR LSP Optimization > SR-TE BW Opt > Operation
Step 3 Select whether to optimize bandwidth for all interfaces, selected interfaces, or tagged interfaces.
Step 4 Specify constraints. See Constraints.
Step 5 Specify whether to create and add tags to all SR LSPs rerouted during optimization. You can edit the
Step 6 Specify whether to create a new plan with the results of the optimization. Unless a name is specified, WAE Design attaches an
suffix to the current plan filename. If unchecked, WAE Design changes the current plan file with the updated information.
Step 7 Click
Analyzing Congestion Under Different Failure Sets
You can perform multiple optimizations, one for each failure scenario within a specified failure set. The results of these optimizations are aggregated in a report. This way, you can evaluate the ability of the optimizer to mitigate congestion under different failure scenarios.
Step 1 Choose
Tools > SR LSP Optimization > SR-TE BW Opt > Analysis
. By default, the analysis tool presents you with the Basic bandwidth optimization options.
Step 2 Click the
Step 3 Select failure sets that you want the optimizer to consider (circuits, nodes, sites, and so on).
Entries appear dimmed if they are not available in your design plan.
Step 4 (Optional) Specify the maximum number of threads.
By default, the optimizer tries to set this value to the optimal number of threads based on the available cores.
Step 5 Click
This runs a simulation analysis and creates the optimization report.
Compressing Segment Lists
Some routers might not support long segment lists; however, long segment lists might be required to achieve the desired route.
The Compress Segment Lists tool takes LSPs as input and creates new segment lists that adhere to a maximum length. Any segment lists that exceed the maximum length are replaced by new LSPs, LSP paths, and segment lists. A newly created LSP is set as the final segment list hop of the previous LSP; this process repeats until the initial LSP reaches its destination. The tool also creates new LSPs when the route crosses an AS boundary.
Step 1 Choose
Tools > SR LSP Optimization > Compress Segment Lists
Step 2 Choose which segment lists to compress: all (the default), those selected before opening the dialog box, or those with specific tags.
Step 3 In the Maximum Segment List Length field, enter a value of at least 3 hops. The default limit is 9 hops.
Step 4 Check the
Remove Orphaned Segment Lists
check box if you want to remove segment lists that are not used by other LSP paths or SR FRRs as a result of the optimization.
Step 5 In the
Tag updated LSPs with
field, enter a tag to add to all segment lists that are compressed during optimization. Using tags makes it easier to find the segment lists that need to be compressed in the actual network according to the optimization results. By default, newly compressed segment lists are tagged as
Step 6 Check or uncheck the
New plan for result
check box. If checked, WAE Design generates a new plan file with the results of the optimization and appends the suffix
to the new plan filename. (You can change the filename.) If unchecked, WAE Design changes the current plan file with the updated information.
Step 7 Click