A tunnel interface must be configured on an ingress so that the interface is used to establish and manage an SR-MPLS TE tunnel.
The system view is displayed.
A tunnel interface is created, and the tunnel interface view is displayed.
To configure the IP address of the tunnel interface, run ip address ip-address { mask | mask-length } [ sub ]
The secondary IP address of the tunnel interface can be configured only after the primary IP address is configured.
To configure the tunnel interface to borrow the IP address of another interface, run ip address unnumbered interface interface-type interface-number
The SR-MPLS TE tunnel is unidirectional and does not need a peer IP address. A separate IP address for the tunnel interface is not recommended. The LSR ID of the ingress is generally used as the tunnel interface's IP address.
MPLS TE is configured as a tunneling protocol.
A tunnel destination address is configured, which is usually the LSR ID of the egress.
Various types of tunnels require specific destination addresses. If a tunnel protocol is changed from another protocol to MPLS TE, a configured destination address is deleted automatically and a new destination address needs to be configured.
A tunnel ID is set.
Segment Routing is configured as the signaling protocol of the TE tunnel.
PCE server delegation is enabled so that the controller can calculate paths.
Path verification for SR-MPLS TE tunnels is enabled. If a label fails, an LSP using this label is automatically set to Down.
This function does not need to be configured if the controller or BFD is used.
To enable this function globally, run the mpls te path verification enable command in the MPLS view.
DSCP values are configured for IPv4/IPv6 packets to enter the SR-MPLS TE tunnel.
The DSCP configuration and mpls te service-class command configuration of an SR-MPLS TE tunnel are mutually exclusive.
The configuration is committed.