Viewing LSP Details of a CSD-Topology for Analyzing Network Changes
You can view the details of all the label-switched paths (LSPs) configured for devices in the Topology View that are managed by the CSD-Topology. For MPLS-enabled networks, after you configure an LSP, you should also configure a standby or secondary LSP to provide an alternate route in the event the primary route fails. The tunnel ID, from node, to node, and IP address of a secondary or standby tunnel must be identical to those of the primary tunnel.
When you expand a zone or a group in the Topology View, and select an LSP on the map, the LSP is highlighted. Different highlighting colors are used to distinguish the LSPs on the map.
To view details of LSPs in the Topology View:
- From the Junos Space user interface, click the Build icon on the Connectivity Services Director banner.
The workspaces that are applicable to Build mode are displayed on the Tasks pane.
- From the View selector, select Topology View.
The topology map of the sites or zones and the devices configured in each zone using the CSD-Topology is displayed.
- Select the LSPs tab on the lower portion of
LSP names that are not unique in the network are not displayed in the Topology View.
For columns in the table that contain an empty text field displayed at the top of the table on each tab, you can enter the search criterion that you want to use for that particular column or parameter to sort and classify the display of values in the table. For parameters that you can enable or disable, you can select or clear the check boxes respectively. The page is refreshed to display the devices that match the specified criterion. The search criteria that you have entered are displayed above the first row of the table. You can click Clear All displayed beside each of the search terms to remove the previously defined search terms.
Name—Name of the LSP. Click in the first cell in the Name column to enter the name of the LSP that you want to use as the filter for viewing the LSPs.
Start Node Router ID—Node ID of the LSP head end. A router ID is used to uniquely identify the router within a BGP autonomous system (AS). The router ID is the IP address of the loopback interface.
Start Node Hostname—Hostname of the router at the LSP head end
End Node Router ID—Node ID of the LSP tail end
End Node Hostname—Hostname of the router at the LSP tail end
End A IP—IP address of the LSP head end. Click in the first cell in the End A IP column to enter the IP address of the head end that you want to use as the filter for viewing the LSPs.
End B IP— IP address of the LSP tail end. Click in the first cell in the End B IP column to enter the IP address of the tail end that you want to use as the filter for viewing the LSPs.
Operational Status—Whether the LSP is active (up) or inactive (down). Click in the first cell in the Operational Status column to select the status from the drop-down menu that you want to use as the filter for viewing the LSPs.
Path Type—Whether the path is a primary path (explicit or dynamic) or a secondary path (explicit or dynamic)
Control Type—Whether the LSP is router controlled or PCC initiated, CSD-Topology initiated or PCEP initiated, or CSD-Topology managed or delegated LSP. Click in the first cell in the Control Type column to specify the type of LSP from the drop-down menu that you want to use as the filter for viewing the LSPs.
Metric—LSP tunnel metric
Setup Priority—Setup priority supported by RSVP for the tunnel traffic
You must assign priorities according to network policies to prevent resource poaching and LSP thrashing. The hold priority values should be lower than or equal to the setup priority value.
Holding Priority—Hold priority supported by RSVP for the tunnel traffic
The default is priority 07 and hold 07, which is the standard MPLS LSP definition in Junos OS. Setup priority determines whether a new LSP that preempts an existing LSP can be established. For preemption to occur, the setup priority of the new LSP must be higher than the setup priority of the existing LSP. In addition, the act of preempting the existing LSP must provide sufficient bandwidth to support the new LSP. Therefore, preemption occurs only if the new LSP can be set up successfully. You can configure each LSP with a setup priority and hold priority to provide a preemption strategy whereby a new LSP can claim resources from an existing LSP. Each LSP can claim resources from an existing LSP. Priority levels range from 0 (highest priority) through 7 (lowest priority). If traffic engineering admission control determines that there are insufficient resources available to accept a request to set up a new LSP, the setup priority is evaluated against the hold priority of the existing LSPs (per standard Junos OS behavior). An LSP with a hold priority lower than the setup priority of the new LSP can be preempted. The existing LSP is terminated to make resources available for the new LSP.
Current Bandwidth—Bandwidth that is specified for the tunnel traffic (bandwidth applies for each direction)
- Mouse over an LSP and click the LSP to display a menu.
When you mouse over an LSP, the name of the LSP is displayed on a pop-up menu. The following fields are displayed in the pop-up dialog box when you mouse over the LSP:
Name—Name of the LSP. The names of all the LSPs that are configured for the particular link are displayed.
View Details—Detailed information about the selected LSP.