Configuring an MPLS TE Tunnel Interface
Context
A tunnel interface must be created on the ingress so that a tunnel can be established and forward data packets.
- Establishes a tunnel. Tunnel constraints, bandwidth attributes, and advanced attributes such as TE FRR and tunnel re-optimization can be configured on the tunnel interface to establish the tunnel.
- Manages a tunnel. Tunnel attributes can be modified on the tunnel interface to manage the tunnel.
Because MPLS TE tunnels forward MPLS packets, not IP packets, IP forwarding-related commands run on the tunnel interface are invalid.
Perform the following configurations on the ingress node of an MPLS TE tunnel.
Procedure
- Run system-view
The system view is displayed.
- Run interface tunnel interface-number
A tunnel interface is created and the tunnel interface view is displayed.
If the shutdown command is run on the tunnel interface, all tunnels established on the tunnel interface will be deleted.
- Run either of the following commands to assign an IP address
to the tunnel interface:
To configure an IP address for the tunnel interface, run ip address ip-address { mask | mask-length } [ sub ]
The primary IP address must be configured before the secondary IP address is configured.
To configure the tunnel interface to borrow an IP address of another interface, run ip address unnumbered interface interface-type interface-number
An MPLS TE tunnel can be established even if the tunnel interface is assigned no IP address. The tunnel interface must obtain an IP address before forwarding traffic. An MPLS TE tunnel is unidirectional and does not need to configure a separate IP address for the tunnel interface. Generally, a loopback interface is created on the ingress node and a 32-bit address that is the same as the LSR ID is assigned to the loopback interface. Then the tunnel interface borrows the IP address of the loopback interface.
- Run tunnel-protocol mpls te
MPLS TE is configured as a tunnel protocol.
- Run destination dest-ip-address
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.
- Run mpls te tunnel-id tunnel-id
A tunnel ID is set.
- Run mpls te signal-protocol rsvp-te
RSVP-TE is configured as the signaling protocol.
- (Optional) Run mpls te signalled tunnel-name tunnel-name
The tunnel name is specified.
By default, the tunnel interface name such as Tunnel1 is used as the name of the TE tunnel.
Perform this step to fulfill the following purposes:- Facilitate TE tunnel management.
- Allow a Huawei device to be connected to a non-Huawei device that uses a tunnel name that differs from the tunnel interface name.
- (Optional) Run mpls te cspf disable
Do not perform the constraint shortest path first (CSPF) calculation when an MPLS TE tunnel is being set up.
- Run mpls te commit
The configuration is committed.
The mpls te commit command must be run to make configurations take effect each time MPLS TE parameters are changed on a tunnel interface.