No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE40E V800R010C00 Configuration Guide - MPLS 01

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring a Reverse GMPLS UNI Tunnel

Configuring a Reverse GMPLS UNI Tunnel

A GMPLS UNI tunnel is unidirectional. After a forward GMPLS UNI tunnel is configured, a reverse GMPLS UNI tunnel must be configured on the egress EN.

Context

A GMPLS UNI tunnel is bound to the physical interface of the data channel or VLAN sub-interface of the physical interface to carry data services on the ingress EN and egress EN. A GMPLS UNI tunnel is established using extended RSVP-TE. The ingress EN initiates tunnel establishment requests containing tunnel attributes by sending Path messages. Therefore, tunnel attributes and functions need to be configured on the ingress EN and do not need to be configured on the egress EN for a reverse GMPLS UNI tunnel. A reverse GMPLS UNI tunnel only needs to be matched with its corresponding forward GMPLS UNI tunnel and bound to the service bearer interface.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    gmpls-tunnel gmpls-tunnel-name

    A GMPLS UNI tunnel is established, and the tunnel view is displayed.

  3. Run:

    passive

    The established tunnel is configured as a reverse GMPLS UNI tunnel.

  4. Run:

    bind interface interface-type interface-number

    A GMPLS UNI tunnel interface is bound to a service interface.

    Only a local GMPLS UNI can function as a service interface.

  5. Run:

    match-tunnel ingress-lsr-id ingress-lsr-id tunnel-id tunnel-id

    The name and node ID of the ingress are configured for the forward GMPLS UNI tunnel.

    The ingress-lsr-id parameter is set to the LSR ID of the ingress EN. The tunnel-id parameter is set to the forward tunnel ID.

  6. Run:

    commit

    The configuration is committed.

Follow-up Procedure

After the preceding configurations are complete, a GMPLS UNI tunnel is established, and the service bearer interface bound to the tunnel goes Up. IP and MPLS services can be configured on the interface. Configurations are the same as those of other interfaces that are not bound to the GMPLS UNI tunnel. Detailed configuration procedures are not mentioned here.

Download
Updated: 2018-07-12

Document ID: EDOC1100028530

Views: 101840

Downloads: 336

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next