A tunnel interface must be configured on an ingress so that the interface is used to establish and manage an E2E SR-MPLS TE tunnel.
An SR-MPLS TE tunnel is unidirectional. To configure a reverse tunnel, perform the configuration on the ingress of the reverse tunnel.
The system view is displayed.
An inter-AS E2E tunnel interface is created, and the tunnel interface view is displayed.
To configure an IP address for the tunnel interface, run the ip address ip-address { mask | mask-length } [ sub ] command.
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 the ip address unnumbered interface interface-type interface-number command.
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. Use the LSR ID of the ingress as the tunnel interface's IP address.
MPLS TE is configured as a tunneling protocol.
A tunnel destination address, which is usually the LSR ID of the egress, is configured.
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.
An explicit path is configured for the tunnel.
The path-name value must be the same as that specified in the explicit-path path-name command.
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.