Configuring an SR-MPLS TE Explicit Path

An explicit path over which an SR-MPLS TE tunnel is to be established is configured on the ingress. You can specify node or link labels for the explicit path.

Context

An explicit path refers to a vector path on which a series of nodes are arranged in a configuration sequence. To plan a path over which an SR-MPLS TE LSP is established, you can specify either next-hop labels or next-hop IP addresses for an explicit path. An IP address specified on an explicit path is the IP address of an interface. An explicit path in use can be dynamically updated.

Procedure

Run system-view
The system view is displayed.
Run explicit-path path-name
An explicit path is created and the explicit path view is displayed.
Configure an explicit path.
In the following example, two AS domains are connected. If there are multiple AS domains, add configurations based on the network topology.
1. Run next sid label label-value type binding-sid
  
  A binding SID is specified for the first AS domain on an explicit path.
  
  When the first hop of an explicit path is assigned a binding SID, the explicit path supports a maximum of three hops.
2. Run next sid label label-value type adjacency
  
  An inter-AS adjacency label is specified.
3. Run next sid label label-value type binding-sid
  
  A binding SID is specified for the second AS domain on an explicit path.
  
  In the case of multiple AS domains, this binding SID can be the binding SID of a new E2E SR-MPLS TE tunnel.
Run commit
The configuration is committed.