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 is a vector path comprised of a series of nodes that are arranged in the configuration sequence. The path through which an SR-MPLS TE LSP passes can be planned by specifying next-hop labels or next-hop IP addresses on an explicit path. The IP addresses involved in an explicit path are set to interfaces' IP addresses. 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.
Perform either of the following operations:
- To specify a next-hop label for the explicit path, run the next sid label label-value type { adjacency | prefix | binding-sid } command.
- Specify a next-hop address for the explicit path:
  
  In this scenario, the mpls te cspf command must be run on the ingress to enable CSPF.
  1. Run the next hop ipv4 [ include [ [ strict | loose ] | [ incoming | outgoing ] ] ^* | exclude ] command to specify a next-hop node for the explicit path.
    
    The include parameter indicates that an LSP must pass through a specified node. The exclude parameter indicates that an LSP cannot pass through a specified node.
  2. (Optional) Run the add hop ipv4 [ include [ [ strict | loose ] | [ incoming | outgoing ] ] ^* | exclude ] { after | before } contrastIpv4 command to add a node to the explicit path.
  3. (Optional) Run the modify hop contrastIpv4 ipv4 [ include [ [ strict | loose ] | [ incoming | outgoing ] ] ^* | exclude ] command to change the address of a node to allow another specified node to be used by the explicit path.
  4. (Optional) Run the delete hop ipv4 command to remove a node from the explicit path.
- To configure an explicit path where the next hop label and IP address are mixed, perform the following operations:
  
  In this scenario, the mpls te cspf command must be run on the ingress to enable CSPF.
  1. Run the next sid label label-value type { adjacency | prefix | binding-sid } or next hop ip-address [ include [ [ strict | loose ] | [ incoming | outgoing ] ] ^* | exclude ] command to specify the next label or node for an explicit path.
  2. (Optional) Run the add sid label label-value type { adjacency | prefix | binding-sid } { after | before } { hop contrastIpv4 | index indexValue | sid label contrastLabel index indexValue } or add hop ipv4 [ include [ [ strict | loose ] | [ incoming | outgoing ] ] ^* | exclude ] { after | before } { hop contrastIpv4 | index indexValue | sid label contrastLabel index indexValue } command to add a label or node to the specified explicit path.
  3. (Optional) Run the modify hop contrastIpv4 to { hop ipv4 [ exclude | include [ [ strict | loose ] | [ incoming | outgoing ] ] * ] | sid label label-value type { adjacency | prefix } } or modify index indexValue to { hop ipv4 [ exclude | include [ [ strict | loose ] | [ incoming | outgoing ] ] * ] | sid label label-value type { adjacency | prefix | binding-sid } } or modify sid label contrastLabel index indexValue to { hop ipv4 [ exclude | include [ [ strict | loose ] | [ incoming | outgoing ] ] * ] | sid label label-value type { adjacency | prefix | binding-sid } } command to modify the label or node of the specified explicit path.
  4. (Optional) Run the delete { sid label labelValue index indexValue | index indexValue } or delete hop ip-address command to delete a label or node from the specified explicit path.
Run commit
The configuration is committed.