Configuring a Tunnel Interfaces

Procedure

1. Run system-view

   The system view is displayed.

2. Run interface tunnel interface-number

   A tunnel interface is created, and the tunnel interface view is displayed.

3. (Optional) Run description text

   The tunnel description is configured.

4. (Optional) Run either of the following commands to assign an IP address to the tunnel interface:

   • To configure an IP address, 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

   To forward traffic, the tunnel interface must have an IP address. An MPLS TE tunnel, however, is unidirectional, and o peer address exists. Therefore, it is unnecessary to assign an IP address to a tunnel interface. A tunnel interface usually borrows the loopback address, which functions as the LSR ID of the local node.

5. Run tunnel-protocol mpls te

   MPLS TE is configured as a tunneling protocol.

6. Run destination ip-address
7. Run mpls te tunnel-id tunnel-id

   A tunnel ID is set.

8. Run mpls te signal-protocol { cr-static | rsvp-te }

   A signaling protocol is configured for a tunnel.

9. (Optional) Run mpls te priority setup-priority [ hold-priority ]

   The tunnel priorities are set.

   A smaller value indicates a higher priority.

   

   The holding priority must be higher than or equal to the setup priority. If no holding priority is set, its value is the same as that setup priority. If the combination of the bandwidth and priorities is not listed in the TE class mapping table, LSPs cannot be established.

10. Run commit

    The configuration is committed.

    Each time you change an MPLS TE parameter, run the commit command to commit the configuration.