Configure RSVP-TE Routing

This chapter describes how Cisco Crosswork Planning simulates RSVP-TE routing. Unless otherwise noted, LSPs refer to RSVP-TE LSPs. Note that Cisco Crosswork Planning does not distinguish between LDP and RSVP-TE LSPs.

This section contains the following topics:

Dynamic LSP Routing and CSPF

If an RSVP LSP contains no LSP paths (also called MPLS TE tunnel paths), it is routed dynamically using Constrained Shortest Path First (CSPF). The weights used for the CSPF calculation are the TE metrics per interface. If the TE metric is not configured for an interface, then IGP metric is used.

If there are equal-cost routes, the following selection criteria apply in this order:

  • Bandwidth available—The route with the greatest reservable bandwidth is chosen.

  • Hop count—The route with the fewest hops is chosen.

  • Random—If neither of the above criteria can be used, the route is randomly chosen.

CSPF properties are set in the Edit LSP window and are viewable from the LSPs table. Note that these properties are available only for RSVP LSPs.

  • Setup bandwidth (Manual)—The amount of traffic the source node requests for this LSP in Mbps. The requested bandwidth is available from the reservable bandwidth of each interface in the path.

  • Setup bandwidth (Auto)—Dynamically update the Setup BW Sim value when using the Auto bandwidth convergence mode.

  • Setup priority—A priority for allocating reservable bandwidth. This is the order in which the LSPs are signaled. The lower the number, the higher the priority.

  • Hold priority—Priority that can preempt LSPs that are on the shortest path. This is typically set for a particular service or traffic type. The lower the number, the higher the priority.

  • Hop limit—The maximum number of hops permitted in the LSP route. If no path is available with this number of hops or fewer, the LSP is not routed.

  • TE metric disabled—If checked, the LSP is routed using IGP metrics. If unchecked (default), the LSP is routed using TE metrics.

Set Interface MPLS Properties

MPLS properties are set in the MPLS tab of the interface or circuit properties window and are viewable in the Interfaces or Circuits table.

  1. Open the plan file (see Open Plan Files). The plan file opens in the Network Design page.

  2. Select one or more interfaces or circuits from their respective tables.

  3. Click Edit icon.


    Note

    If you are editing a single interface or circuit, you can also use the > Edit option under the Actions column.

  4. Click the MPLS tab.

Figure 1. Interface MPLS Properties

Set the following properties, as required:

  • Reservable BW—Shows the amount of bandwidth that can be reserved by LSPs routed over the interface.

  • Reservable BW (%)—Shows the percentage of bandwidth that can be reserved by LSPs routed over the interface.

  • TE metric—Determines which path an LSP takes.

  • Affinities—Lists which affinities are set. For more information, see Configure Affinities.

  • Flex algo affinities—Lists the FlexAlgo affinities assigned to the interface (MPLS).

  • State:

    • TE enabled—Identifies whether an LSP can be routed over the interface. If checked, the value is set to True, and TE metrics are used in routing the LSP, provided the LSP’s TE metric disabled field is unchecked.

    • FRR enabled—Designated interface to be avoided by the FRR LSP. Only interfaces with this property set are used by the FRR LSPs initializer when creating FRR LSPs. This property does not affect FRR LSPs that are manually created. For more information, see Fast Reroute Simulations.

Following columns are updated in the Interfaces or Circuits tables:

  • TE metric sim—Derived column that shows the effective TE metric. If the TE Metric is empty, this is set to the IGP metric.

  • Resv BW sim—Derived column.

    • If a Reservable BW value is entered, this is copied to the Resv BW sim column.

    • If Reservable BW and Reservable BW (%) are “na”, the Resv BW sim is copied from the Capacity sim column.

    • If Reservable BW is “na”, but Reservable BW (%) has a value, the Resv BW sim value is derived by this formula:

      Capacity sim * (Reservable BW (%) / 100)

      If needed, you can change this behavior so that reserved bandwidth constraints are not used during simulations, which could be useful for planning purposes. For information, see Ignore Reservable Bandwidths for Capacity Planning.

  • To determine how much of the interface traffic is contained in LSPs, show these columns in the Interfaces table. The total of the two equals Traff sim.

    • Traff sim LSP—The total amount of LSP traffic on the interface.

    • Traff sim non LSP—The total amount of non-LSP traffic on the interface.

    To determine which interfaces carry LSP traffic, sort the columns. To determine the demands associated with one or more selected interfaces based on whether or not they have LSP traffic, select them and choose Cross Table Filter icon > Filter to demands > Through all interfaces. Then, choose Cross Table Filter icon > Filter to LSPs.

  • Loadshare—Show this column in the LSPs table. It indicates the value for redistributing either traffic across LSPs based on the ratio of this value with other LSPs that are parallel (have the same source and destination).

View LSP Reservations

To view the LSP reservations on the interfaces, choose LSP reservations from the Plot view drop-down list in the toolbar. The utilization colors are based on the LSP util column in the Interfaces table. The LSP util is the sum of all setup bandwidths for all LSPs through the interface, as a percentage of the Resv BW sim.

Simulated Traffic versus LSP Reservations shows how the network plot varies based on the Plot view option you choose, Simulated traffic or LSP reservations.

Figure 2. Simulated Traffic versus LSP Reservations

Calculate LSP Setup Bandwidth

The LSP setup bandwidth initializer calculates the setup bandwidth for existing RSVP-TE LSPs. The setup bandwidth is set to the maximum amount of demand traffic passing through the LSP for the traffic levels selected.

The best practice is to use the Autobandwidth convergence mode (Network options > Simulation > Simulation convergence mode). For more information, see Simulate Autobandwidth-Enabled LSPs

Procedure

Step 1

Open the plan file (see Open Plan Files). The plan file opens in the Network Design page.

Step 2

From the toolbar, choose Actions > Initializers > LSP setup bandwidth.

Step 3

Select the LSPs you want to optimize.

Step 4

Choose whether to set the setup bandwidth value to be equal to the maximum amount of traffic passing through each tunnel across selected traffic levels. Use the Initialize setup bandwidth from traffic levels check box for this purpose.

Step 5

Choose whether to set the load share values to be equal to the setup bandwidth. To set, check the Initialize loadshare from setup bandwidth check box.

Step 6

Click Submit.

RSVP LSP Paths

Like LSPs, LSP paths have CSPF properties, such as Setup priority and Hop limit. For a description of LSP properties, see Dynamic LSP Routing and CSPF.

If these properties are omitted, then they are inherited from the LSP. If these properties are set in the LSP path, they override the LSP settings.


Note

If operating in the Autobandwidth convergence simulation mode and if the LSP's Setup bandwidth is set to Auto, the LSP path Setup BW property (like the LSP Setup BW) is ignored, and the LSP’s Setup BW sim value is calculated and used.

If an LSP path does not have an associated named path, it is routed dynamically. However, you can use named paths to fully or partially describe a path from the LSP source to destination.


Note
This chapter refers to LSPs and LSP paths as dynamic, explicit, or loose explicit, depending on whether their associated named paths have no defined hops, all hops defined, or only some hops defined.

Define Hot Standby Paths

An LSP path can be defined as a “hot” standby path. Standby paths are always established even if the associated LSP is routed using a path with a different path option. For RSVP LSPs, setup bandwidth, if any, is reserved for them. These standby LSP paths are then immediately available should the currently routed path become unavailable.

Example Response to Failures

Example RSVP LSP and Associated LSP Paths shows an RSVP LSP (cr1.lon_cr2.fra) that uses four LSP paths. The cr1.lon_cr2.fra LSP has a primary and standby secondary path options (100 and 200), each with a setup bandwidth of 0. They are both established, using their defined named paths. Both primary and secondary LSP paths have associated named paths, which appear in the Path name column. The other two paths do not have associated named paths, and so are dynamically routed.

Figure 3. Example RSVP LSP and Associated LSP Paths

This example LSP responds to failures as follows:

  1. If the primary path (cr1.lon_cr2.fra_100) fails, the secondary path (cr1.lon_cr2.fra_200) is used.

  2. If both paths with associated name paths fail, a dynamic path is established with a reserved bandwidth of 125 Mbps, which it inherits from the LSP. This path is not set up initially because it is not a standby.

  3. If all paths fail, the path of last resort is a dynamic path with zero bandwidth. This ensures that there is always an LSP up so that services relying on the LSP are always available.

  4. The simulation changes if the LSP Active path has been set. For example, if cr1.lon_cr2.fra_200 is the active path (that is, 200 appears in the LSP’s Active path column), Cisco Crosswork Planning uses cr1.lon_cr2.fra_200 first, and then goes through the previous sequence.

Named Paths and Explicit LSP Routing

Named paths specify a route though the network using an ordered list of adjacencies. The route is defined by named path hops, which can be nodes or interfaces, and each hop type specifies whether the route should be strict, loose, or excluded. Named path hops can be nodes or interfaces. The hop type is identified visually on the plot, as well as listed in the Type column of the Named path hops table.

  • Strict—The LSP must reach the named path hop directly from the previous one, with no intermediate interfaces.

  • Loose—The LSP is routed to this hop from the previous hop using CSPF. Intermediate interfaces can be used.

  • Exclude—The node or interface is excluded from the LSP path. This hop type cannot be combined with strict or loose hops in the same named path.

The named paths and their hops are listed and selectable from the Named paths and Named path hops tables. The advantage of having separate tables is that you can have named paths that have missing or unresolved hops. Also, the path name can be reserved even if it is not part of the Cisco Crosswork Planning simulation.

Named Path Hops Example

Example Named Paths the cr1.lon_cr2.fra LSP extends the earlier example (Example RSVP LSP and Associated LSP Paths), showing two named paths for the cr1.lon_cr2.fra LSP. This shows that the first two LSP paths each have a named path. The naming convention is <LSP_Name>_<Path_Option>, which in this case is cr1.lon_cr2.fra_100 and cr1.lon_cr2.fra_200.

Figure 4. Example Named Paths the cr1.lon_cr2.fra LSP

The hops for each named path are defined in a separate table called Named Path Hops. Example Named Path Hops for cr1.lon_cr2.fra_100 shows the named path hops for the cr1.lon_cr2.fra_100 named path. The Step column shows the hop order.

  • The first hop is an interface hop: a strict hop on the interface from cr1.par to cr2.par.

  • The second is a node hop, also strict, to cr2.par.

  • The third hop is an interface hop: a strict hop on the interface from cr1.fra to cr2.fra.

Hops for cr1.lon_cr2.fra_200 are defined similarly.

Figure 5. Example Named Path Hops for cr1.lon_cr2.fra_100

Create Named Paths and Their Hops

To create Named paths and their hops, do the following:

Procedure

Step 1

Open the plan file (see Open Plan Files). The plan file opens in the Network Design page.

Step 2

Named paths can be created in the Cisco Crosswork Planning UI in using the following two methods:

  • When creating LSP paths, check the Create associated named paths check box. Using this option does not create hops.

  • From the toolbar, choose Actions > Insert > LSPs > Named path.

  • In the Network Summary panel on the right side, click Add icon in the Named paths tab.

    The Named paths tab is available under the More tab. If it is not visible, then click the Show/hide tables icon (Show/Hide Tables Icon) and check the Named paths check box.

Step 3

Named path options:

  • Enter the name in the Name field.

  • To change the source site or source nodes, choose them from the drop-down lists.

  • To activate or deactivate, check Active.

Step 4

Hop options:

  • To add a new hop, click Add icon. Go to Step 5.

  • To edit an existing hop, select it from the Hops list and then click Edit icon. The Edit window opens for named path hops. Go to Step 5.

  • To delete an existing hop, choose it from the Hops list, click Delete icon.

Step 5

To continue creating or editing the named path hop, use the following options.

  • As needed, choose the site, node, and interface. For node hops, do not choose an interface.

  • Choose the Type as Loose, Strict, or Exclude. See Named Paths and Explicit LSP Routing for a description of each.

Step 6

Click Add.

Edit Named Paths and Named Path Hops

Once the named paths are created, you can create, edit, or delete their named path hops. Note that discovered named paths can contain unresolved hops, which are nodes and interfaces that are not in the plan file. For information on resolving named paths, see Unresolved LSP Destinations and Hops.

The recommended method of editing the named path hop type is to access it directly from the Named paths table as described in the following steps. This is the most efficient way of viewing the entire path.

Procedure

Step 1

Select one or more named paths from the Named paths table.

Step 2

Click Edit icon.

Note

 

If you are editing a single named path, you can also use the > Edit option under the Actions column.

Step 3

In the Hop section, edit the Named path hop details, as required. For reference, see Create Named Paths and Their Hops.

Step 4

Click Save.

Actual Paths

In Cisco Crosswork Planning, actual paths are the actual route that routed LSP paths are taking. They are read from the live network, per LSP path. RSVP-TE routing is not always completely predictable because it depends on the order in which LSPs are established and reserve their bandwidth on the network. Cisco Crosswork Planning uses actual paths in LSP routing simulations to match the current LSP routing state of a network as accurately as possible.

When an LSP path is routed, the actual route is attempted first. If this routing fails due to CSPF constraints, such as not enough reservable bandwidth or affinity restrictions, Cisco Crosswork Planning reverts to the standard CSPF routing algorithm.

Example: Cisco Crosswork Planning routes all LSPs in its simulation according to the actual paths read from the network, and the routings completely match the network. If a circuit fails, only the LSPs through this circuit are rerouted. Because they cannot be established along their actual paths, standard CSPF is used. The result is a prediction of incremental routing changes that would occur on the current network if such a failure were to occur.

An LSP or an LSP path might have a corresponding actual path. An LSP path with no actual path inherits its LSP actual path, if available.

Two columns in the LSPs and LSP Paths tables are useful to see the result of actual paths on LSP routing.

Column

Description

Actual column in the LSP Paths table

The simulation can only use actual paths if they are resolved. If the network discovery was incomplete, this might not be possible.

  • true = the simulation converted the actual path hops into a complete path from source to destination of the LSP

  • false = the simulation did not convert the actual path hops into a complete path

  • NA = not applicable; no actual path was available.

Routed column in the LSPs table

  • Actual = The LSP follows an actual path.

  • Simulated = The LSP does not follow an actual path.

  • Unrouted = Routing was not possible.

Deactivate Actual Paths for Simulations

Cisco Crosswork Planning uses network state in its MPLS simulation, routing LSPs on actual paths where possible and using LSP active path settings. For planning purposes, when state is not relevant, you can change this behavior to disregard actual paths.

To disregard actual paths for simulations, do the following:

Procedure

Step 1

Open the plan file (see Open Plan Files). The plan file opens in the Network Design page.

Step 2

In the toolbar, click Network options or choose Actions > Edit > Network options. The Network Model Settings page opens.

Step 3

Click the Simulation tab.

Step 4

To use or disregard actual paths and active paths in MPLS simulation, check or uncheck Use LSP actual paths, active paths check box.

Step 5

Click Save.

Configure Affinities

Affinities provide a mechanism for implementing LSP path diversity. By assigning affinities to physical circuits and associating LSPs with affinities, you can implement a variety of routing policies. For example, you can use affinities to restrict certain traffic to specific topological regions. Or you can force primary and backup LSP paths onto different routes so they do not simultaneously fail.

Cisco Crosswork Planning supports an unlimited number of 64-bit affinities, each of which is defined by a number and an optional name. Named affinities are sometimes called administrative groups or link coloring.

The default network models have 0-31 unnamed and unassigned affinities.

Workflow:

  1. Create and Edit Affinities.

  2. Assign Affinities to Interfaces.

  3. Associate LSPs with Affinities.

Create and Edit Affinities

To create or edit affinities, do the following:

Procedure

Step 1

Open the plan file (see Open Plan Files). The plan file opens in the Network Design page.

Step 2

In the toolbar, click Network options or choose Actions > Edit > Network options. The Network Model Settings page opens.

Step 3

Choose Admin groups from the left pane. The Admin Groups page opens.

Step 4

To create a new affinity:

  1. Click Add icon.

  2. In the Affinity and Name fields, enter the affinity number and affinity name.

    Affinity numbers must be unique. Affinity names are optional and must also be unique.

  3. Click Save.

Step 5

To modify an existing affinity:

  1. Select the affinity you want to edit.

  2. Click Edit icon.

  3. In the Affinity and Name fields, enter the affinity number and affinity name.

    Affinity numbers must be unique. Affinity names are optional and must also be unique.

  4. Click Save.

Assign Affinities to Interfaces

To use affinities, you must assign them to interfaces in a way that encourages favorable routes and discourages others. For example, continental paths might have one affinity and international paths have another.

To assign affinities to interfaces, do the following:

Procedure

Step 1

Open the plan file (see Open Plan Files). The plan file opens in the Network Design page.

Step 2

From the Interfaces table, select one or more interfaces to which you are assigning the affinities.

Step 3

Click Edit icon.

Note

 

If you are editing a single interface, you can also use the > Edit option under the Actions column.

Step 4

Click the MPLS tab.

  1. Click the Edit button next to the Affinities field.

  2. In the Include column, check the boxes for the affinities that you want to associate with the selected circuits.

  3. Click Save.

Step 5

Click Save.

You can also follow the above steps to assign affinities to interfaces through a Edit Circuit window. However, you must choose and assign the affinity twice: once to each interface.

Associate LSPs with Affinities

For affinities to influence LSP routing, you must associate LSPs with the affinities assigned to interfaces that you want to include or exclude in the routing process. If no affinity is specified, the LSP can be routed through any path. Explicit routes can also have affinities for hops with a Loose relationship (see Named Paths and Explicit LSP Routing).

Inclusion and Exclusion Rules

You can choose any of the following rules while associating LSPs with affinities:

  • Include—Only use interfaces that include all affinities.

  • Include any—Use interfaces that include at least one affinity.

  • Exclude—Do not use interfaces with this affinity.

LSP paths inherit the LSP affinities. However, you can edit LSP path affinities to have priority over the LSP affinities.

Example

This example (Example Affinities) demonstrates how affinities affect the routing of two LSPs with the same source and destination nodes.

  • The to_cr1.nyc interface between wdc and nyc is assigned to both affinities 1 (Silver) and 2 (Bronze). No other interfaces are assigned affinities.

  • LSP A is configured to exclude all interfaces assigned to affinity 2. While it cannot take the shortest path using the to_cr1.nyc interface, it can route around it.

  • LSP B is not associated with any affinities. Its LSP path is configured to include any interfaces assigned to affinity 1 (Silver) and to exclude interfaces assigned to affinity 2 (Bronze). Because the to_cr1.nyc interface is assigned to both of these affinities, LSP B cannot route.

Figure 6. Example Affinities

Assign LSPs to Affinities

To assign LSPs to affinities, do the following:
Procedure

Step 1

Open the plan file (see Open Plan Files). The plan file opens in the Network Design page.

Step 2

From the LSPs table, choose one or more LSPs to which you are associating the affinities.

Step 3

Click Edit icon.

Note

 

If you are editing a single LSP, you can also use the > Edit option under the Actions column.

Step 4

Click the Affinities tab.

Figure 7. LSP Affinities

Step 5

Choose the inclusion or exclusion rule (Include, Include any, or Exclude) for the affinity you are associating with the selected LSPs.

Step 6

Click Save.

Assign LSP Paths to Affinities

To assign LSP paths to affinities, do the following:
Procedure

Step 1

Open the plan file (see Open Plan Files). The plan file opens in the Network Design page.

Step 2

From the LSP paths table, choose one or more LSP paths to which you are associating the affinities.

Step 3

Click Edit icon.

Note

 

If you are editing a single LSP path, you can also use the > Edit option under the Actions column.

Step 4

Click the Edit button in the Affinities section.

Step 5

Choose the inclusion or exclusion rule (Include, Include any, or Exclude) for the affinity you are associating with the selected LSP paths. You can choose the LSP paths to inherit the LSP affinities or choose the values from the table. After making the selections, click Save.

Figure 8. LSP Path Affinities

Step 6

Click Save in the Edit window to save and exit.

Assign Affinities When Creating LSP Meshes

You can associate affinities with LSPs when creating a new LSP mesh.

Procedure

Step 1

Open the plan file (see Open Plan Files). The plan file opens in the Network Design page.

Step 2

From the toolbar, choose Actions > Insert > LSPs > LSP mesh.

OR

In the Network Summary panel on the right side, click Add icon > LSP mesh in the LSPs tab.

Step 3

After selecting the required nodes and options, go to the Affinities page.

Figure 9. Insert LSP Mesh Window

Step 4

Click Choose affinities under the Affinities section.

Step 5

Choose the inclusion or exclusion rule for each affinity you are associating with all LSPs in the mesh, and click Add.

Step 6

Click Submit to save and exit.

Set Global Simulation Parameters

Cisco Crosswork Planning lets you set global parameters that affect how LSPs are routed or rerouted. To access these options, in the toolbar, click Network options or choose Actions > Edit > Network options. Then, click the Simulation tab.

Cisco Crosswork Planning supports four simulation modes for RSVP-TE LSPs. These are listed as options in the Layer 3 drop-down list in the Simulation convergence mode section.

  • Autobandwidth convergence—In this mode, the network is simulated after the traffic (Traff sim) has been rerouted to other LSPs, but before the Setup BW sim values have been reset. See Simulate Autobandwidth-Enabled LSPs.

  • Fast reroute—This mode uses FRR LSPs, which is a common failure restoration mechanism used by RSVP-TE LSPs. In a live network, FRR restoration typically occurs within milliseconds. See Fast Reroute Simulations.

  • IGP and LSP reconvergence—By default, Cisco Crosswork Planning simulates the state of the network once it has fully responded to a failure. Specifically, this is the network state after LSPs have re-established new routes around the failure, and the IGP has fully reconverged. The optimization tools only work in IGP and LSP reconvergence mode.

  • Autobandwidth convergence (including failures)—In this mode, the network is simulated after the Setup BW sim values have been reset. See Simulate Autobandwidth-Enabled LSPs.

Fast Reroute Simulations

Cisco Crosswork Planning simulates a Fast Reroute convergence mode using FRR LSPs. If a failure occurs in the route of a protected RSVP-TE LSP, a presignaled FRR LSP (or bypass tunnel) forwards traffic locally around the point of failure, typically from the node just before the failure to a node downstream. This restoration mechanism gives the source node (head-end) of the FRR LSP time to re-establish an alternate route around the failure. This period is sometimes described as the 50 millisecond behavior of the network because FRR restoration ideally becomes effective within approximately 50 milliseconds of a failure.

Routing of LSPs and demands differ in FRR simulations compared to full convergence simulations, as follows:

  • The source node of the protected LSP does not reroute the traffic. If a failure occurs on a node or circuit (link) within the LSP path, the following routing occurs:

    • If an FRR LSP exists to protect a failed node or circuit, the protected LSP continues to be routed, but its new path includes the FRR LSP route that redirects the traffic around the failure. This traffic enters the FRR LSP’s source node just prior to the failure and rejoins the protected LSP path after the failure at the FRR LSP’s destination node.

    • If the LSP is not protected by an FRR LSP, then the LSP traffic is not routed.

  • Since there is no IGP reconvergence, demands through unrouted LSPs are unrouted. Additionally, demands through failures outside of these LSPs are not routed.

FRR Fundamentals

This section summarizes key properties and terms, and how FRR LSPs are visualized in the network plot. More details about these are further explained throughout the following sections. Note that FRR LSPs appear in the same table as the regular LSPs and are identified in the Metric type column as FRR.

Objects and Properties

Object

Type

Column

Description

LSP

FRR LSP

FRR interface

Designated interface to be avoided by the FRR LSP.

FRR type

Type of FRR protection: Link or Node.

Autoroute

Forwarding Adjacency

FRR enabled

Marks an LSP to be protected by FRR LSPs.

Interface

na

FRR enabled

Marks an interface to be protected by FRR LSPs. This property is required if an interface is to be used when running the FRR LSPs initializer.

Terms

  • Protected interface—An interface that is avoided when using FRR LSPs.

  • Protected LSP—An LSP that would be rerouted through FRR LSPs in the event of failures. In Cisco Crosswork Planning, this requires the Fast Reroute simulation mode. To turn this mode on, see Run Fast Reroute Simulation.

  • Protected SRLG—An SRLG that contains a protected interface.

Visualization

An unused FRR LSP path highlights in violet when it is selected from the LSPs table. When routed under failure, FRR LSPs appear as a dashed black line.

FRR LSP Routing

The source and destination of an FRR LSP can be any pair of nodes, although in practice the source and destination nodes are usually one hop (link protection) or two hops (node protection) apart. The source node for the FRR LSP has a designated interface that is configured so that it is avoided during Fast Reroute simulations. This is the protected interface.

This is configured using the FRR interface property, which is set in the Edit LSP window when manually creating the FRR LSP, or it is automatically created when running the FRR LSPs initializer. The initializer derives it from interface's FRR enabled property.

Example

This figure shows an FRR LSP sourced at sjc, destined for mia, and whose protected interface (FRR interface) is to_cr1.hst. Therefore, the FRR LSP path routes towards okc and away from hst. If this FRR interface property were to_cr1.okc instead, the FRR LSP path would route sjc-hst-mia, away from okc.

Like other LSPs, FRR LSPs can use actual and named paths. Unlike other LSPs, they do not use setup bandwidth when routing and they only use one LSP path.

Link and Node Protection

Cisco Crosswork Planning supports both link (circuit) and node protection FRR LSPs. The type of protection shows in the FRR type column of the LSPs table.

  • Link-protection LSPs—Protect an LSP from a circuit failure by routing an FRR LSP around the failed circuit. The source node of the FRR LSP is the local node of the failed circuit, and if configured correctly, the destination of the FRR LSP is the remote node of the failed circuit.

  • Node-protection LSPs—Protect an LSP from a node failure by routing an FRR LSP from the node one hop prior to the failed node in the protected LSP path to the node one hop after the failed node.

SRLG Protection

In a network, if interfaces are sourced from the same node (router) and are configured as an SRLG, an FRR LSP protecting one of these interfaces can be configured to reroute around that interface. If possible, the FRR LSP avoids all other interfaces in the SRLG. In Cisco Crosswork Planning, FRR LSPs can be configured to avoid all objects defined in the SRLG, not just interfaces on the source node of the FRR LSP.

Routing around Failures

Before you begin

Assuming one or more failures occurred, the following decisions determine which FRR LSP to take:

Procedure

Step 1

For each such interface on the LSP path, Cisco Crosswork Planning checks for an FRR LSP protecting that interface whose destination is a node further down the path of the LSP.

Step 2

If more than one of these FRR LSPs exist, Cisco Crosswork Planning chooses the one that is farthest down that path of the protected LSP, thus simulating standard FRR behavior that prefers node protection over link protection.

If more than one eligible FRR LSP has the same destination farthest down the protected LSP path, the FRR LSP is chosen arbitrarily among them.

Step 3

If more failed circuits or nodes occur after this destination, further FRR LSPs are chosen in the same manner.

Set Up Fast Reroute Simulations

To set up FRR simulations, do the following:
Procedure

Step 1

Set appropriate properties on LSPs to mark them for protection. See Identify LSPs for Protection.

Step 2

If protecting SRLGs, associate a node with the SRLG in order to establish the protected interface within it. See Identify SRLGs for Protection.

Step 3

If you are using the initializer to create FRR LSPs, identify which interfaces to protect. See FRR LSPs Initializer.

Step 4

Create the FRR LSPs using the FRR LSPs initializer or manually. See FRR LSPs Initializer or Create FRR LSPs Manually.

Identify LSPs for Protection

To mark the LSPs for Fast Reroute protection, you must set the following properties in the Edit LSP window.

  • In the LSPs details section, check the FRR enabled check box. This appears as "true" in the FRR enabled column of the LSPs table. If this is "false", the LSP is not protected.

  • In the Routing section, set the Routing type as Autoroute or FA (Forwarding Adjacency). The type appears as "autoroute” or “FA” in the Metric type column of the LSPs table.

Identify SRLGs for Protection

To simulate a router’s “exclude protect” configuration, associate the source node of the protected circuit with the SRLG. If that circuit fails, the FRR LSP reroutes around all circuits within that SRLG.

Procedure

Step 1

Select the source node of a circuit within an SRLG that you want to protect. Click Edit icon or choose > Edit.

Step 2

Click the SRLGs tab.

Step 3

Choose one or more SRLGs with which you want to associate this node, and click Save.

FRR LSPs Initializer

The FRR LSPs initializer automatically creates link-protection or node-protection FRR LSPs provided two conditions are met:

  • One or more LSPs have their FRR enabled property set (see Identify LSPs for Protection).

  • One or more interfaces on the path of these LSPs have their FRR enabled property set. This tells the FRR LSPs initializer how to create the FRR LSPs so that in the event of a failure, the interface would be avoided when the LSP is being rerouted.

    • This property is set in the MPLS tab of the interface Properties window. The FRR enabled column in the Interfaces table shows "true" if the interface is included or "false" if it is not.

    • After FRR LSPs are created, the interface is listed in the FRR interface column in the LSPs table.

The initializer creates the FRR LSPs based on these FRR enabled properties and based on whether you choose to create link or node protection.

  • Link protection—Cisco Crosswork Planning creates FRR LSPs for each pair of next-hop nodes (two connected nodes) in the protected LSP path where the egress interface of the first hop has its FRR enabled property set.

  • Node protection—Cisco Crosswork Planning creates FRR LSPs between each set of next next-hop nodes (three connected nodes) in the protected LSP path where the egress interface of the first hop has its FRR enabled property set.

These new FRR LSPs are named FRR_<source> _<destination> _<postfix> , where postfix is optional and set in the initializer’s window.

Run the FRR LSPs Initializer
To run the FRR LSPs initializer, do the following:
Procedure

Step 1

Open the plan file (see Open Plan Files). It opens in the Network Design page.

Step 2

From the toolbar, choose Actions > Initializers > FRR LSPs.

Step 3

Select the nodes that you want to optimize. If you do not choose any nodes, the initializer uses all nodes in the plan file.

Step 4

Click Next.

Step 5

Choose whether to create FRR LSPs that protect links (circuits), nodes, or both.

Step 6

(Optional) Enter a postfix to add to the end of the names of the newly created FRR LSPs.

Step 7

(Optional) Uncheck the Delete current FRR LSPs check box if you want to retain the existing FRR LSPs.

Step 8

Click Submit.

Create FRR LSPs Manually

This section describes the required properties for an FRR LSP. It does not describe all the options available when creating an LSP.

Procedure

Step 1

Choose Actions > Insert > LSPs > LSP, or click Add icon > LSPs in the LSPs page. Alternatively, you can choose an existing LSP to modify to be an FRR LSP. If doing so, click Edit icon or choose > Edit.

Step 2

Choose the source site and node of the FRR LSP.

Step 3

Choose the destination site and node, or enter a NetInt destination IP address. For information on NetInt destination IP addresses, see Unresolved LSP Destinations and Hops.

Step 4

In the Routing area, choose FRR as the Routing type.

Step 5

Specify the interface that is to be avoided during routing by choosing it from the FRR interface drop-down list or by entering its IP address in the NetInt FRRInterface field.

Step 6

Click Save.

Run Fast Reroute Simulation

FRR LSPs are routed only when simulating failures in the Fast Reroute simulation mode. To enable the Fast Reroute simulation mode, follow these steps.

Procedure

Step 1

In the toolbar, click Network options or choose Actions > Edit > Network options. The Network Model Settings page opens.

Step 2

Click the Simulation tab.

Step 3

In the Simulation convergence mode section, choose Fast reroute from the Layer 3 drop-down list.

Step 4

Click Save.

Simulate Autobandwidth-Enabled LSPs

In a network, autobandwidth-enabled LSPs reset their setup bandwidth periodically based on the configured autobandwidth timers, and establish new routes if necessary. In networks with constrained bandwidth, changes in LSP routes can make other LSPs unroutable, which can then affect the amount of traffic in each LSP, the setup bandwidth settings, and the routes taken, without ever converging.

While Cisco Crosswork Planning does not simulate this instability, it does simulate autobandwidth-enabled LSPs. In this simulation mode, internally Cisco Crosswork Planning first routes the autobandwidth-enabled LSPs with a setup bandwidth of zero. Then, demands are routed to determine the simulated traffic (Traff Sim) through each LSP. The result in the plan file and GUI is that the Traff Sim value is copied to the Setup BW Sim for each autobandwidth-enabled LSP, and these LSPs are then routed using their new Setup BW Sim value. Note that if some LSPs cannot be routed, the Traff Sim and Setup BW Sim values resulting from this process might not match one another for all autobandwidth-enabled LSPs.

There are two autobandwidth simulation modes available. Before simulating failures or running Simulation Analysis on autobandwidth-enabled LSPs, choose the appropriate mode depending on which state you need to simulate.

  • In the Autobandwidth convergence mode, the network is simulated after the traffic (Traff Sim) has been rerouted to other LSPs, but before the Setup BW Sim values have been reset. This simulates the immediate, less optimal response to failures.

  • In the Autobandwidth convergence (including failures) mode, the network is simulated after the Setup BW Sim values have been reset. This simulates the longer, more optimal response to failures.


Note
The Autobandwidth convergence and Autobandwidth convergence (including failures) simulation modes are only available in plan files with a single traffic level.

These autobandwidth simulations require that the LSPs have their Autobandwidth property set to true, and that one of the two autobandwidth modes be selected from the Network Model Settings page (in the toolbar, click Network options or choose Actions > Edit > Network options).

Example Autobandwidth Convergence Without and with Failures

The network in this example has the following parameters:

  • One demand from er1.chi to cr1.wdc.

  • Two LSPs: LSP-A from cr1.chi to cr1.wdc and LSP-B from cr2.chi to cr1.wdc.

  • Neither of these LSPs has a Setup BW.

  • All circuits have a 10,000 Mbps capacity except for one (between cr2.chi and cr1.wdc), which is only 1000 Mbps.

  • Example LSP Routing Using IGP and LSP Reconvergence and Using Autobandwidth Convergence shows that in the IGP and LSP Reconvergence mode, the Setup BW sim value for both LSPs is 0.

    • In the Autobandwidth convergence mode, the Setup BW sim value for LSP-A is copied from its Traff sim value, which is 5000.

    • There are no failures, and each LSP follows the same route in both convergence modes.

  • Example Autobandwidth Convergence with Failures shows the Autobandwidth convergence mode when there is a failure.

    • Failing the circuit between cr1.chi and cr1.wdc causes LSP-A to reroute through cr2.chi.

    • The shortest path from er1.chi through cr1.chi is now longer than the shortest path from er1.chi through cr2.chi, and so the demand moves over to LSP-B. This is shown in the LSPs table where the traffic (Traff Sim) of LSP-A is moved to LSP-B.

    • Because the smaller of the two circuits is congested, LSP-A uses the larger circuit, which has enough capacity to carry the traffic.

    • LSP-B continues to route on the lower capacity circuit, thus causing congestion.

    • The Setup BW sim value is not updated for either LSP because the Autobandwidth convergence mode does not update setup bandwidth as a result of traffic shifts due to failure.

  • Example Autobandwidth Convergence Including Failures shows the same failure in Autobandwidth convergence (including failures) mode.

    • The LSP-B Setup BW sim is updated to the Traff sim value, forcing it to take the larger circuit to reach its destination. Note that the plot shows both the normal (solid) and failure (dashed) route for LSP-B, indicating that it has rerouted under the failure, even though the failure did not interrupt its path.

    • The demand continues to route on LSP-B, but because the LSP has found a path with sufficient capacity, there is no more congestion.

Figure 10. Example LSP Routing Using IGP and LSP Reconvergence and Using Autobandwidth Convergence
Figure 11. Example Autobandwidth Convergence with Failures
Figure 12. Example Autobandwidth Convergence Including Failures

Advanced RSVP-TE LSP Simulations

Ignore Reservable Bandwidths for Capacity Planning

When using Cisco Crosswork Planning for capacity planning, it is common to increase the demand traffic to a level expected at a future date. Various simulations are then performed, such as failures and worst-case analysis, to determine which circuits will likely experience over-utilization.

In MPLS networks using RSVP-TE LSPs, a setup bandwidth is configured for each LSP. If the demand traffic is increased, LSP setup bandwidths are usually increased correspondingly (for example, by using the LSP Setup Bandwidth initializer). When these LSP setup bandwidths become too large, some LSPs might not be routable, thus rendering an improbable view of the future network. When this occurs, you have the option to temporarily remove the reservable bandwidth constraints for a more realistic view into future capacity requirements. While this is not a routing method that actually exists on routers, it is a convenient Cisco Crosswork Planning simulation that can assist you when planning networks.

When you enable this routing mode, Cisco Crosswork Planning routes LSPs in the order they appear in the plan file LSPs table, as described in the following steps. Note that static order of the LSPs table in the plan file likely differs from the order of LSPs in the GUI, which changes frequently due to user interaction.

This operates only on LSPs that do not have autobandwidth enabled.

Procedure

Step 1

Route LSPs as usual. (For information, see Dynamic LSP Routing and CSPF.)

Step 2

If an LSP is not routable (call it “LSP-A”), try to route it with zero setup bandwidth.

  • If LSP-A cannot be routed, leave it unrouted and try to route the next LSP in the LSPs table. If this LSP cannot be routed, try to route the next LSP listed in the LSPs table in the plan file.

  • If LSP-A can be routed, then there will be one or more interfaces on its route whose reservable bandwidth is exceeded. These interfaces are marked as having unlimited reservable bandwidth during the simulation of all subsequent LSPs, thus allowing for the routing of LSP-A and other LSPs that would otherwise exceed the reservable bandwidth on these interfaces. Note that actual Resv BW and Resv BW Sim values in the Interfaces table do not change.

On completion of the simulation, a number of interfaces will have their reserved bandwidth greater than their configured reservable bandwidth. The circuits containing these interfaces are candidates for capacity expansion.

Enable Capacity Planning Mode for LSPs

To ignore reservable bandwidth constraints in routing simulations, do the following:

Procedure

Step 1

From the toolbar, click Network options or choose Actions > Edit > Network options. The Network Model Settings page opens.

Step 2

Click the Simulation tab.

Step 3

In the Label switched paths section, check the LSP capacity planning mode check box. This ignores the reservable bandwidth constraints.

Step 4

Click Save.

Example

In this example, there are four LSPs, each with a setup bandwidth (Setup BW) of 600 Mbps. All interfaces have a reservable bandwidth (Resv BW) of 1000 Mbps.

  • LSPs

    • LSP-1, LSP-2, and LSP-3 go from LON to FRA.

    • LSP-4 goes from LON to ROM.

  • IGP metrics

    • Interfaces between PAR and FRA, and interfaces between FRA and ROM have an IGP metric of 2.

    • All other interfaces have an IGP metric of 1.

Comparison of Reservable Bandwidth Being Used vs Not Being Used shows the LSP reservations view of this simple network in both simulations modes: the usual where reservable bandwidths are observed and the capacity planning version wherein they are ignored. In this latter mode, the two red circuits indicate they are being over utilized and likely need their capacity increased. (For information on the LSP Reservations view, see View LSP Reservations.)

Figure 13. Comparison of Reservable Bandwidth Being Used vs Not Being Used

Simulated Routing Using Reservable Bandwidth Constraints demonstrates routing simulations where reservable bandwidth constraints are applied (LSP capacity planning mode unchecked), which is the default behavior.

  • LSP-1 routes across LON-AMS-FRA, leaving circuits LON-AMS and AMS-FRA each with only 400 Mbps of available bandwidth.

  • LSP-2 routes across LON-PAR-FRA, leaving circuits LON-PAR and PAR-FRA each with only 400 Mbps of available bandwidth.

  • LSP-3 cannot be routed because there is not enough available bandwidth on LON-AMS or LON-PAR. Its Setup BW sim value in the LSPs table is set to “NA” and the Routed column is set to “Unrouted.”

  • LSP-4 cannot be routed, again because there is not enough available bandwidth. Its Setup BW Sim value in the LSPs table is set to “na” and the Routed column is set to “Unrouted.”

Figure 14. Simulated Routing Using Reservable Bandwidth Constraints

In Simulated Routing Without Using Reservable Bandwidth Constraints, the use of reservable bandwidth constraints has been disabled (LSP capacity planning mode checked). The LSP routes are now as follows.

  • As with the default behavior, LSP-1 routes across LON-AMS-FRA and LSP-2 routes across LON-PAR-FRA.

  • Once it is determined that there is not enough reservable bandwidth for LSP-3 to route, it takes the shortest path, LON-AMS-FRA. The reservable bandwidth on interfaces LON-to-AMS and AMS-to-FRA is ignored for the remainder of this simulation. LSP-3’s Setup BW sim value in the LSPs table is set to 600.

  • LSP-4 routes across LON-AMS-FRA-ROM because these reservable bandwidth constraints have been removed and because it is the only route available. Even though LON-PAR-MAD-ROM is the shortest path, there is not enough reservable bandwidth on LON-to-PAR or PAR-to-FRA. LSP-4’s Setup BW sim value in the LSPs table is set to 600.

Figure 15. Simulated Routing Without Using Reservable Bandwidth Constraints

If, however, LSP-4 were routed before LSP-3, then LSP-4 would route across its shortest path of LON-PAR-MAD-ROM, and the LON-to-PAR interface would have its reservable bandwidth constraint ignored. With this routing, LSP-3 would still route LON-AMS-FRA, and the interfaces LON-to-AMS and AMS-to-FRA would still be set to remove their reservable bandwidth constraint.

P2MP LSPs

Point-to-multipoint (P2MP) LSPs offer an MPLS alternative to IP multicast for setting up multiple paths to multiple locations from a single source. In live networks, the signal is sent once across the network and packets are replicated only at the relevant or designated branching MPLS nodes.

A P2MP LSP consists of two or more sub-LSPs that have the same source node. Most of Cisco Crosswork Planning refers to sub-LSPs as LSPs, and there is no distinction between the two.

To view the P2MP LSPs or their associated sub-LSPs, choose them from the P2MP LSPs and LSPs tables. To determine if an LSP belongs to a P2MP LSP, you can show the P2MP LSP column in the LSPs table.

Example: In P2MP LSPs and Associated Sub-LSPs, there are two P2MP LSPs, LSP_er12 and LSP_er13. LSP_er12 and LSP_er13 have "er12" and "er13" as their source nodes, respectively. In the LSPs table, the first three LSPs have er12 as the source node and are sub-LSPs of LSP_er12 P2MP LSP (as indicated by the P2MP LSP column). Similarly, the LSPs with er13 as the source node are the sub-LSPs of LSP_er13 P2MP LSP. The Sub LSP count in the P2MP LSPs table indicates the number of sub-LSPs of each P2MP LSP.

Figure 16. P2MP LSPs and Associated Sub-LSPs

P2MP LSP Bandwidth

All sub-LSPs within a given P2MP LSP share bandwidth and therefore, common circuits between these sub-LSPs have the same bandwidth, rather than an aggregate. Common practice is to set all sub-LSPs within a P2MP LSP to the same bandwidth. Otherwise, the bandwidth for the shared circuit is the highest bandwidth set.

To see the reserved LSP bandwidth, show the LSP Resv column in the Interfaces table. You can also view the associated traffic by choosing LSP Reservations in the Network Plot menu in the Visualization toolbar. For more information, see View LSP Reservations.

Example: If A-C LSP and A-D LSP each have a bandwidth 400 Mbps, the A-B circuit has an aggregate bandwidth of 800 Mbps (Bandwidth Behavior Without a P2MP LSP). However, if A-C and A-D are sub-LSPs within a P2MP LSP, the A-B circuit has a bandwidth of 400 Mbps (Bandwidth Behavior with a P2MP LSP).

Figure 17. Bandwidth Behavior Without a P2MP LSP
Figure 18. Bandwidth Behavior with a P2MP LSP

P2MP LSP Demands

Demands routed through P2MP LSPs must have the same source as the P2MP LSP; the demand then terminates at each of the P2MP LSP destinations. No other demands can go through the P2MP LSP except for the one created for it. If the P2MP LSP fails, its demand cannot be routed. (See Create Demands for P2MP LSPs for information on creating these demands.)

Demands must be private to the P2MP LSP. This privacy is automatically created when you insert a demand for a P2MP LSP.

Create P2MP LSPs and Sub-LSPs

Rules and guidelines:

  • All sub-LSPs within a given P2MP LSP must have the same source site and source node.

  • Because sub-LSPs within a P2MP LSP share setup bandwidth, typically bandwidth is set to the same value for each sub-LSP.

Create P2MP LSPs
Follow these steps to create P2MP LSPs.
Procedure

Step 1

Create an empty P2MP LSP.

  1. From the toolbar, choose Actions > Insert > LSPs > P2MP LSP, or click Add icon in the P2MP LSPs table.

  2. Enter a unique P2MP LSP name.

  3. Choose the source site and node. This selection is the root for all sub-LSPs contained in this P2MP LSP.

  4. (Optional) Enter or choose a disjoint group and disjoint priority.

Step 2

If you have not done so, create sub-LSPs for the P2MP LSP. For details, see Create Sub-LSPs.

Step 3

Associate the sub-LSPs to the P2MP LSP. You can follow these steps individually, or you can choose up to three LSPs and edit them collectively. If you are editing multiple sub-LSPs, verify that all of them have the same source site and node as the P2MP LSP.

  1. Select the sub-LSPs from the LSPs table and click Edit icon.

  2. In the Sub-LSP of P2MP LSP list under the Other section at the bottom, choose the P2MP LSP to which you want these LSPs to belong.

  3. Click Save.

Create Sub-LSPs
Follow these steps to create sub-LSPs.
Procedure

Step 1

From the toolbar, choose Actions > Insert > LSPs > LSP, or click Add icon > LSPs in the LSPs table.

Step 2

Choose the site and node that will be the source of the P2MP LSP. All sub-LSPs in a P2MP LSP must have the same source site and source node.

Step 3

Choose the site and node that are the final destination for the sub-LSP.

Step 4

Complete the remaining optional fields and tabs, as needed. Because sub-LSPs share bandwidth, typically the CSPF Setup bandwidth field is set to the same value for each sub-LSP in the P2MP LSP.

Step 5

If you have already created the P2MP LSP to which this sub-LSP will belong, choose that P2MP LSP from the Sub-LSP of P2MP LSP list (at the bottom). For creating P2MP LSPs, see Create P2MP LSPs.

Step 6

Click Save.

Create a Mesh of Sub-LSPs
Procedure

Step 1

In the Nodes table, choose the node you will be designating as the source for the P2MP LSP. All sub-LSPs in a P2MP LSP must have the same source node. A P2MP LSP cannot have multiple source nodes.

Step 2

From the toolbar, choose Actions > Insert > LSPs > LSP mesh, or click Add icon > LSP mesh in the LSPs table.

Step 3

In the Destination nodes section, uncheck these check boxes and click Next.

  • Same destinations as sources

  • Create LSPs from destination to source

Step 4

Complete the remaining optional fields as needed and click Next.

Step 5

To set the bandwidth to be the same for all sub-LSPs in this mesh, choose Fixed Value in the Bandwidth drop-down list. Enter that value in the Fixed value field (in Mbps).

To use the auto bandwidth feature so that these LSPs have their Setup BW sim value automatically calculated and used in auto bandwidth simulations, choose Auto Bandwidth in the Bandwidth drop-down list.

Step 6

Complete the remaining optional fields as needed and click Submit.

Create Demands for P2MP LSPs

To simulate traffic routing through a P2MP LSP, create a demand for it.

Procedure

Step 1

If you want to create demands for P2MP LSPs, choose one or more P2MP LSPs from the P2MP LSP table.

Step 2

From the toolbar, choose Actions > Insert > LSPs > Demands for P2MP LSPs, or click Add icon > Demands for P2MP LSPs in the LSPs table.

Step 3

Choose the P2MP LSPs through which you are routing traffic.

Step 4

(Optional) Choose a service class for the newly created demand.

Step 5

Choose the desired bandwidth: Minimum sub-LSP Setup BW or Zero.

Step 6

Click Submit.

Delete P2MP LSPs and Sub-LSPs

Deleting a P2MP LSP will invalidate the simulation and remove all demands that use the P2MP LSP as a private LSP. If you do not want all the sub-LSPs deleted, disassociate them first.

Disassociate Sub-LSPs from Their P2MP LSPs
Procedure

Step 1

In the LSPs table, choose one or more sub-LSPs.

Step 2

Click Edit icon.

Note

 

If you are editing a single sub-LSP, you can also use the > Edit option under the Actions column.

Step 3

In the Sub-LSP of P2MP LSP list, do one of the following:

  • Choose the empty row to disassociate the sub-LSP and change it to an LSP.

  • Choose a different P2MP LSP to associate the sub-LSP with a different P2MP LSP.

Step 4

Click OK.

Delete Sub-LSPs or P2MPs

Delete Sub-LSPs but Keep P2MP LSP

Delete P2MP LSP

  1. Select one or more sub-LSPs in the LSPs table.

  2. Click Delete icon. If you are deleting a single sub-LSP, you can also use the > Delete option under the Actions column.

  3. Click Delete in the confirmation dialog box to continue.

  1. Select one or more P2MP LSPs in the P2MP LSPs table.

  2. Click Delete icon. If you are deleting a single P2MP LSP, you can also use the > Delete option under the Actions column.

  3. Click Delete in the confirmation dialog box to continue.

Unresolved LSP Destinations and Hops

RSVP-TE LSP configurations and state are read using network discovery from the source node of the LSP, through SNMP, the Parse Configs tool, or other methods. These configurations might reference nodes or interfaces that do not exist in the plan file, so they are referred to as being unresolved. For example, the LSP destination node, read from the configuration on the source, might not be in the plan file. There are several reasons for these differences:

  • The plan file was modified to contain fewer nodes than are in the IGP.

  • Cisco Crosswork Planning cannot read all the nodes, or cannot obtain the IP addresses of all the nodes.

  • The LSPs themselves are not configured correctly.

References that might not be resolved are as follows:

  • Destination nodes of the LSPs.

  • Hops in named paths configured on the source node.

  • Hops in the actual paths read from the source node.

Cisco Crosswork Planning tries to resolve as many of these references as possible. Tables and columns are updated as follows:

  • If the LSP destinations are resolved, they are updated in the Destination column of the LSPs table. If they are not resolved, the column remains empty. The original IP address remains in the NetInt Destination column regardless of whether the destination is resolved or not.

  • If the hops are resolved, they are updated in the Node and Interface columns in the Named Path Hops and Actual Path Hops tables. If they are not resolved, the columns remain empty. The original IP address remains in the NetIntHop column regardless of whether the destination is resolved.

Cisco Crosswork Planning does not make further attempts to resolve these references unless you explicitly make the request. There are special cases in which this might be useful. For example, if additional nodes are added to a network from a second network discovery procedure and if LSPs in the original network have unresolved references to these nodes, it is useful to resolve the LSPs again.