Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Add a Tunnel

Paragon Automation allows you to add label-switched paths (LSPs) by using Path Computation Element Protocol (PCEP). You can create RSVP and segment-routed (SR) LSPs, and view the LSPs on the topology map.

LSPs are referred to as tunnels in the Paragon Automation GUI.

To provision a tunnel:

  1. Navigate to Observability > Topology.
    The Topology page is displayed with the topology map at the center and the network information table at the bottom of the page.
  2. Navigate to the Tunnels tab.
  3. Click the Provisioning drop down and select Tunnel.
    The Add Tunnel Page appears.
  4. Complete the configuration on each tab according to the guidelines in Table 1.
    Note:

    Fields marked with an asterisk (*) are mandatory.
  5. (Optional) From any tab, click Preview Path at the bottom of the page to view the path on the topology map.
  6. Click Add to add the tunnel.

    A confirmation message appears on the top of the page, indicating that a provision tunnel request was successfully created.

  7. Verify that the LSPs are configured correctly. In the Tunnels tab of the Network Information table:
    1. Verify that the Operation Status field displays Active.
    2. Select the LSP and check the path of the LSP on the topology map.
    3. Check the tunnel traffic and tunnel delay by selecting the LSP and clicking View > Tunnel Traffic and View > Delay respectively.
    Table 1: Fields on the Add Tunnel Page

    Field

    Description

    PROPERTIES

    Provisioning Method

    From the list, select PCEP.

    When you select PCEP (Path Computation Element Protocol), the path computation element (PCE) initiates the tunnel and the associated configuration statements do not appear in the router configuration file. Upon provisioning, this tunnel is added as a PCE-initiated tunnel.

    Note:

    We do not support NETCONF in Release 2.3.0.

    Provision Type

    From the list, select the type of tunnel that you want to provision:

    • RSVP
    • SR (segment routing)
    • SRv6
      Note:

      You can provision SRV6 only through CLI.

    Name

    Specify a unique name for the tunnel.

    You can use any number of alphanumeric characters, period, hyphens, colons, and underscores.

    Note:

    If you are adding multiple parallel tunnels that will share the same design parameters, the name you specify here is used as the base for automatically naming those tunnels. See the Count and Delimiter fields in the Advanced tab for more information.

    Device A

    From the list, select the device that you want to use as the ingress node.

    Device Z

    From the list, select the device that you want to use as the egress node.

    Admin Status

    The Path Computation Server uses the administration status of the tunnel to decide whether to route, provision, or both route and provision the tunnel.

    By default, the status is Up, which indicates that the Path Computation Server routes and provisions the tunnel, and no traffic flows through the tunnel.

    Path Type

    From the list, select primary, secondary, or standby as the path type.

    Path Name

    Specify the name for the path.

    This field is available only for primary tunnels with RSVP provisioning type, and for all secondary and standby tunnels.

    Planned Bandwidth

    Specify the planned bandwidth (along with valid units, with no space between the bandwidth and units) for the tunnel.

    If you specify a value without units, bps is automatically applied.

    Valid units are:

    • B or b

    • M or m

    • K or k

    • G or g

    Examples: 50M, 1000b, 25g.

    Planned Metric

    Specify the static tunnel metric.

    The PCE uses this metric to route the tunnel instead of allowing the router to choose a path.

    Setup

    Specify the setup priority for the tunnel traffic.

    Priority levels range from 0 (highest priority) through 7 (lowest priority). The default is 7, which is the standard MPLS tunnel definition in Junos OS.

    Based on the setup priority, the PCE determines whether a new tunnel can be established, by preempting an existing tunnel. The existing tunnel can be preempted if the setup priority of the new tunnel is higher than that of the existing tunnel and the preemption releases enough bandwidth for the new tunnel.

    Routing Method

    From the list, select a routing method to specify whether the PCE should compute and provision the path for the tunnel:

    The available options are:

    • routeByDevice—This is the default routing method when the PCE learns or creates a PCC-controlled tunnel. For this method, The PCE does not compute and provision a path.

      This method is appropriate for three types of tunnels: RSVP TE PCC-controlled tunnels, segment routing PCEP-based tunnels, and segment routing NETCONF-based tunnels.

      Note:

      If you select this routing method, your router must run Junos OS Release 19.1 or later. This is to ensure that the router can abide by the hop requirements that you specify in the Path tab in this configuration.

    • Other routing methods (default, delay, IS-IS, OSPF)—When a PCC-controlled tunnel uses a routing method other than RouteByDevice, the PCE computes and provisions the path as a strict explicit route. The tunnel’s existing explicit route might be modified to a PCE-computed strict explicit route.

      For example, a loose explicit route specified by you or learned from the router might be modified to a strict explicit route.

    Hold

    Specify the hold priority for the tunnel traffic.

    Priority levels range from 0 (highest priority) through 7 (lowest priority). The default is 7, which is the standard MPLS tunnel definition in Junos OS.

    Based on the hold priority, the PCE determines whether the tunnel can be preempted or not. If the hold priority for a tunnel is higher, it is unlikely for the tunnel to be preempted.

    Color Community
    Note:

    This field is available only for the SR provision type. This field is not available for the RSVP provision type.

    Assign a color for the segment routing tunnel that can be used to map traffic on the tunnel.

    CONSTRAINTS

    Admin Group Include All

    From the list, select one or more admin group bits for the tunnel to traverse links that include all of the admin groups specified in this field. The maximum selections allowed is 32.

    Admin Group Include Any

    From the list, select one or more admin group bits. The tunnel traverses links that include at least one of the admin groups specified in this field. The maximum selections allowed is 32.

    Admin Group Exclude

    From the list, select one or more admin group bits. The tunnel traverses links that do not include any of the admin groups specified in this field. The maximum selections allowed is 32.

    Maximum Delay

    Specify the maximum delay (in milliseconds) for the tunnel, which is used as a constraint for tunnel rerouting.

    Maximum Hop

    Specify an integer value for the maximum number of hops that the tunnel can traverse.

    Maximum Cost

    Specify an integer value for the maximum cost to be associated with the tunnel.

    ADVANCED

    Count

    Specify the number of parallel tunnels to be created between two endpoints.

    These tunnels share the same design parameters as specified in the Constraints tab.

    Delimiter
    Note:

    This field is available only when the count value is greater than 1.

    Specify a delimiter value, which can consist of alphanumeric characters and special characters except space, comma (,), and semicolon (;).

    This value is used in the automatic naming of parallel tunnels that share the same design parameters. The PCE names the tunnels using the name you enter in the Properties tab and appends the delimiter value plus a unique numerical value beginning with 1.

    Example: myTunnel_1, myTunnel_2, and so on.

    Description

    Specify a comment or description for the tunnel for your reference.

    PATH

    Routing Path Type

    From the list, select the type of routing path for the tunnel:

    • Dynamic—Allows the PCE to compute a path without imposing any path restrictions.

    • Required—Prevents the PCE from using any other path for this tunnel. If the required path is not viable and available, the tunnel is down and the PCE does not perform computation to look for an alternate path.

    • Preferred—Instructs the PCE to use this path over any other, as long as it is viable and available. If it is not viable and available, the PCE computes an alternate path.

    Add Hop

    This option available only if the routing path type is Preferred or Required.

    Click the Add (+) icon or click Add Hop. From the list, select an option as the first hop between node A and node Z.

    In addition, click the toggle button next to this field to specify whether the hop is strict or loose:

    • If you specify the hop as strict, the tunnel must take a direct path from the previous router to this router.

    • If you specify the hop as loose, the tunnel can take any path to reach this router; the PCE chooses the best path.

    To add more hops, click the + icon again. You can add a maximum of 37 hops.

    Note:

    When specifying a loose hop, you can choose from all links in the network. When specifying a loose hop for a Required path, anycast group SIDs are also available for selection.