About the Tunnels Tab
On the Tunnels tab of the network table (Observability > Network > Topology > Tunnels), you can view the information about label-switched paths (LSPs) in your network.
Routing Director uses Path Computation Element Protocol (PCEP) sessions to discover the tunnels that run in your network.
A PCEP session must be established between Routing Director and the devices.
To establish a PCEP session, you must specify a VIP address either at the time of installing Routing Director or post-installation of the cluster. For more information, see Configure a PCE Server.
To establish PCEP on a PE router, see Configuring PCEP on a PE Router.
To configure BGP-LS topology acquisition on Routing Director, see Configuring Topology Acquisition Using BGP-LS.
You must have adopted or onboarded the device to Routing Director; otherwise, the tunnel-related information is not displayed on the Tunnels tab.
Tasks You Can Perform
-
Hide unrelated nodes of a tunnel—To hide unrelated nodes of a tunnel, select one or more tunnels and enable the Hide unrelated toggle button. The topology map limits the display to only the nodes that are related to the selected tunnel.
-
Provision tunnels—You can provision the following:
-
Provision a tunnel—Click Provisioning and select Tunnel to provision a tunnel. For more information, see Add a Tunnel.
-
Provision secondary or standby tunnels—If you want to provide an alternate route in case the primary route fails, you can add additional secondary or standby tunnels for a tunnel. Select the tunnel and click Provision Secondary/Standby.
The Add Tunnel page appears, where you can select a secondary or standby tunnel for the existing tunnel. After the secondary or standby tunnel that you created is provisioned, you can see it in the network information table and in the topology map.
Note: You can provision a secondary or standby tunnel only for RSVP tunnels. The Provision Secondary/Standby option is available only for PCC-initiated and PCC-controlled tunnels.Routing Director supports the discovery, control, and creation of primary and protection LSPs. Primary LSPs provide the primary (preferred) route for traffic flows, while protection LSPs provide an alternate route if the primary route fails.
Protection LSPs are of two types: standby LSPs and secondary LSPs. The tunnel ID, source node, destination node, and IP address of a secondary or standby LSP are identical to that of the primary LSP. However, secondary and standby LSPs have the following differences:
-
A secondary LSP is not signaled until the primary LSP fails.
-
A standby LSP is signaled regardless of the status of the primary LSP.
When you configure a protection LSP from the GUI, you must have a primary LSP of the same control type (PCC-controlled, PCC-delegated, or PCE-initiated) available before you configure a protection LSP.
Note: By default, a protection LSP uses the bandwidth, setup priority, and hold priority values of the primary LSP. However, each protection LSP can be configured to use values different from the primary LSP. -
-
Provision Diverse Tunnels—Click Provisioning and select Diverse Tunnels to implement tunnel diversity in your network. For more information, see Add Diverse Tunnels.
-
Trigger tunnel optimization—Routing Director ensures that LSPs are automatically routed through the most optimal paths. However, if you want Routing Director to recalculate an optimal path, click Provisioning and select Trigger Tunnel Optimization. For information on how Routing Director automatically reroutes LSPs see Reroute LSPs.
-
- Add or Remove delegation—To delegate one or more PCC-controlled LSPs to the PCE or
return control of delegated LSPs to the PCC, select Configure Delegation.
For more information, see Add and Remove LSP Delegation.
-
View historical data—Routing Director enables you to view historical data. Historical data provides you valuable insights to past trends and patterns.
For Routing Director to collect historical data, you need to do the following:
Enable the collection of statistics.
To collect historical data for tunnel traffic, you must enable traffic engineering while creating a device profile. For more information, see Add a Device Profile.
To collect historical data for tunnel delay, you must enable link delay measurements. For more information, see How to Enable Link Delay Measurement and Advertising in IS-IS.
Enable dynamic topology so that you can view real-time changes in your network. For more information, see Dynamic Topology Workflow.
You can view the historical data for the following:
-
Tunnel traffic—To view traffic and bandwidth for a tunnel in graphical form, select the tunnel and click Tunnel Traffic. In the Tunnel Traffic page that appears, select the period for which you want to view the data. You can view data for the previous 3 hours, the previous day, the previous week, or choose from a custom time range by specifying the start and end dates and the time.
Note:You can view the tunnel traffic if the device has Junos OS Release 22.X or later releases.
If you are using ACX Series device, then you can view tunnel traffic only if you have installed Junos OS Evolved Release 23.4R2-S2.1.
-
Tunnel delay—Tunnel delay is the sum of all link delays in the tunnel path. At any given time, the Path Computation Element (PCE) is aware of the paths of all tunnels in the network. Periodically, the PCE uses the reported link delays to compute the end-to-end tunnel delay.
To view tunnel delay in graphical form, select the tunnel and click Delay. In the Tunnel Delay page that appears, select the period for which you want to view the data. You can view data for the previous 3 hours, the previous day, the previous week, or choose from a custom time range by specifying the start and end dates and the time.
You can choose to refresh the data automatically or manually.
Note: We do not support traffic statistics collection for Segment Routing (SR) LSPs. -
View events for tunnels—To view historical events (such as actions performed on the tunnel and bandwidth changes) for a tunnel for a specific time range, select the tunnel and click View > Event History.
On the Events page, you can:
-
View a graphical representation of bandwidth changes for an LSP to analyze trends over time. Select the period for which you want to view the bandwidth-related data. You can view data for the previous 2 hours, 4 hours, 8 hours, 16 hours, 24 hours, 1 week, or choose from a custom time range by specifying the start and end dates and the time.
-
View changes to label-switched path (LSP) attributes and events in the table. The Timestamp column helps you to identify the time at which a change has been made to a tunnel.
-
View changes to an LSP on the Topology map. You can use the More > Show Path Changes option to view highlights on the Topology map for any changes to the LSP path, making it easier to track and analyze routing changes.
-
Download comma-separated values (CSV) file that includes information on LSP event history to your local system by clicking the More > Download option.
Note: You can track event history for all types of LSPs only if the router reports the LSP to Router Director using PCEP protocol. If PCEP is not enabled on the router, then the LSPs are not reported and the LSP event history is not displayed. The default retention policy for LSP event history data is three days. -
-
Download—To download tunnels-related data to your local system, click Download. The data is downloaded to your local system as a comma-separated values (CSV) file.
-
From the More list, you can perform the following tasks:
-
View details of a tunnel—To view the details of a tunnel, you can do one of the following:
-
Select a tunnel on the table and click More > Show Details. The Tunnel - Tunnel-Name page appears. You can view the To and From traffic-related information.
-
Hover over a tunnel row in the table and click the Details icon. The Tunnel - Tunnel-Name page appears. You can view the To and From traffic-related information.
-
-
Reload—To view the latest changes in the network map, click Reload.
-
-
To perform common actions such as filtering using advanced filter criteria and resetting preferences, see Network Table Overview.
| Fields | Description |
|---|---|
|
Name |
Displays the name of the tunnel. |
|
Device A |
Displays the device at which traffic enters. |
|
Device Z |
Displays the device at which traffic exits. |
|
IP A |
Displays the IPv4 address of the interface from which device A sends traffic.
Routing Director displays the IPv4 address of IP A based on device A's active configuration. If the IPv4 addresses of IP A and IP Z are in the same subnet, Routing Director forms an interface between devices A and Z. |
|
IP Z |
Displays the IPv4 address of device Z interface that receives
traffic. Routing Director displays the IPv4 address of IP Z based on device Z's active configuration. If the IPv4 addresses of IP A and IP Z are in the same subnet, Routing Director forms an interface between devices A and Z. |
|
Vendor |
Displays the vendor name of the device. |
|
Bandwidth |
Displays the traffic rate (bps) associated with the LSPs, fast reroutes, or multiclass LSPs. |
|
Color |
Displays the color associated with the segment routing (SR) policy. A segment routing (SR) policy uses the color community value to steer traffic flows on to a tunnel. |
|
Admin Group Include All |
Displays a list of all admin groups that are created for LSPs. Admin groups are created to implement a variety of policy-based LSP setups. |
|
Admin Group Include Any |
Displays a list of the admin groups that are created for LSPs. Admin groups are created to implement a variety of policy-based LSP setups. |
|
Metric |
Displays the metric value of an LSP. The LSP metric is used to indicate the ease or difficulty of sending traffic over a particular LSP. Lower LSP metric values (lower cost) increase the likelihood of an LSP being used. Conversely, high LSP metric values (higher cost) decrease the likelihood of an LSP being used. |
|
Path Type |
Displays the type of LSP path—primary, secondary, or standby. |
|
Path Name |
Displays the user-defined name of the LSP path. |
|
Type |
Displays the type of the LSP—RSVP or SR. |
|
Op Status |
Displays the operational status of the LSP—Failed, pending, unknown, live. |
|
Signaling address |
Displays the signaling address Egress Peer Engineering (EPE). |
|
Path Intent |
Displays the name of the path intent, if any. |
|
Control Type |
Displays the control type. |
|
Setup |
Displays the setup priority of the LSP. The setup priority ranges from 0 (highest) through 7 (lowest). |
|
Hold |
Displays the RSVP hold priority for the tunnel traffic. The hold priority ranges from 0 (highest) through 7 (lowest). |
|
Record Route |
Displays whether Routing Director should actively record the path by sending the record route object (RRO). The RRO is used to record the path that the LSP traverses. It includes the IP address and router/node ID of each RSVP node in the path. |
|
Last Update |
Displays the last updated time of the LSP. |
|
Controller Status |
Displays the controller status—No path found, Reschedule in X minutes. |
|
RRO Hop Count |
Displays the hop count of the record route object (RRO). The RRO keeps track of the actual path the LSP is traversing. |
|
Comment |
Displays the comment that the user has added at the time of tunnel creation. |
|
Admin Group Exclude |
Displays the admin group that is excluded. The tunnel traverses links that do not include any of the admin groups listed here. |
|
Planned Metrics |
Displays the static tunnel metric. The PCE uses this metric to route the tunnel instead of allowing the router to choose a path |
|
FlexAlgo ID |
Displays the flex algo ID that is associated with the LSP. |
| Diversity Group | Displays the name of the diversity group to which this tunnel belongs |
| Diversity Level | Displays the diversity level (Link, SRLG, or site) of the tunnel. |