Create P2MP LSP Tunnels and Generate Corresponding LSP Configlets

Paragon Planner allows the user to create P2MP LSP tunnels. First, switch to Modify mode and then select Modify > Elements > Tunnels to bring up the Tunnels Window. Then click on the Add button, and select the P2MP Tunnels option to bring up the Add P2MP Tunnels window.

Figure 1: Selecting the P2MP Tunnels Option in the Tunnels Window Dropdown menu for adding tunnels, options: One Tunnel, Multiple Tunnels, P2MP Tunnels highlighted, One Hop Tunnels.

Dropdown menu for adding tunnels, options: One Tunnel, Multiple Tunnels, P2MP Tunnels highlighted, One Hop Tunnels.

Figure 2: Adding a P2MP LSP tunnel Software interface for configuring P2MP tunnels: Template Default, P2MP Name espntv, Bandwidth 300m, Source DENVER, Destinations BOSTON, MIAMI, PALOALTO, Add and Help buttons.

Software interface for configuring P2MP tunnels: Template Default, P2MP Name espntv, Bandwidth 300m, Source DENVER, Destinations BOSTON, MIAMI, PALOALTO, Add and Help buttons.

As shown in the above figure, first specify a name for the P2MP LSP instance and then choose the source node (ingress LSR) and the leaf nodes (egress LSRs for the sub-LSPs) for the P2MP tree. Then click on the Add button, and the tool will automatically perform the P2MP LSP path computations necessary to place the sub-LSPs associated with the P2MP LSP.

The user has the option to further specify traffic engineering constraints (such as bandwidth and explicit path) for each sub-LSP, as can be done with any point-to-point LSP. For further information on how to specify tunnel parameters. For more information, see Paragon Planner LSP Tunnels Overview.

To see the newly-created P2MP LSP, switch out of Modify mode, and bring up the NetInfo > Multicast > Multicast Trees window to see the P2MP LSP tunnels configured in the network.

Figure 3: Newly-Added P2MP LSP Called espntv Table of multicast trees detailing names, source nodes, bandwidth, destination count, routed count, average and maximum hops, crossovers, and lengths. Options: Highlight, P2MP Tunnels.

Table of multicast trees detailing names, source nodes, bandwidth, destination count, routed count, average and maximum hops, crossovers, and lengths. Options: Highlight, P2MP Tunnels.

Figure 4: The Sub-LSPs for the P2MP LSP espntv Table of multicast tunnels for espntv with columns ID, NodeA.ID, NodeZ.ID, Type, BW, HopCount, and Current_Route.

Table of multicast tunnels for espntv with columns ID, NodeA.ID, NodeZ.ID, Type, BW, HopCount, and Current_Route.

After using the Paragon Planner to model P2MP LSPs, the P2MP LSPs can be rolled out according to the tool’s P2MP LSP path computation calculations. This allows the P2MP LSPs created during network planning to be translated into a series of actions that can be easily implemented by network operations. Paragon Planner can be used to easily convert the outputs of the network modeling into LSP configlets.

A configlet is a small section of the router configuration file that describes all the LSP attributes: bandwidth, admin-group, primary path, etc. To generate the configlets, select Design > Confligets/Delta > LSP Configlet to bring up the LSP Configlet window. After the appropriate options have been specified, click on Submit button to generate the configlets for the selected nodes/tunnels.

Figure 5: LSP Configlet Generation Window Graphical user interface for LSP Configlet tool, used for configuring Label Switched Paths in a network environment related to MPLS.

Graphical user interface for LSP Configlet tool, used for configuring Label Switched Paths in a network environment related to MPLS.

The following figure shows the various statements listed in the configlet generated by Paragon Planner for the P2MP LSP (espntv) that was created above.

Figure 6: Configlet Generated for the P2MP LSP espntv. Text editor showing MPLS configuration file defining label-switched paths from Denver to Boston, Miami, Palo Alto with 300 Mbps bandwidth and priority 7 7.

Text editor showing MPLS configuration file defining label-switched paths from Denver to Boston, Miami, Palo Alto with 300 Mbps bandwidth and priority 7 7.