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

Configuration Guide - VPN

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of VPN, including GRE, BGP/MPLS IP VPN, BGP/MPLS IPv6 VPN, VLL, PWE3, and VPLS.
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).
Enabling the Labeled IPv4 Route Exchange

Enabling the Labeled IPv4 Route Exchange

Context

In inter-AS VPN Option C, you must establish an inter-AS VPN LSP. The related PEs and ASBRs exchange public network routes with the MPLS labels.

The public network routes with the MPLS labels are advertised using MP-BGP. Based on RFC 3107 (Carrying Label Information in BGP-4), the label mapping information of a route is carried in BGP Update messages. This feature is implemented through BGP extension attributes, which requires BGP peers to process the labeled IPv4 routes.

By default, BGP peers cannot process labeled IPv4 routes.

Procedure

  • Configuring the PE device
    1. Run system-view

      The system view is displayed.

    2. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    3. Run peer ipv4-address as-number as-number-plain

      An IBGP peer relationship is established between the local PE and ASBR in the same AS.

    4. Run peer ipv4-address connect-interface loopback interface-number

      A loopback interface is specified as the outbound interface of the BGP session.

    5. Run peer ipv4-address label-route-capability

      The PE device is enabled to exchange labeled IPv4 routes with the ASBR in the same AS.

    6. Run commit

      The configuration is committed.

  • Configuring the ASBR
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The view of the interface connected with the peer ASBR is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. Run ip address ip-address { mask | mask-length }

      An IP address is configured for the interface.

    5. Run mpls

      The MPLS capability is enabled.

    6. Run quit

      Return to the system view.

    7. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    8. Run peer ipv4-address as-number as-number-plain

      An IBGP peer relationship is established between the ASBR and the local PE in the same AS.

    9. Run peer ipv4-address connect-interface loopback interface-number

      A loopback interface is specified as the outbound interface of the BGP session.

    10. Run peer ipv4-address label-route-capability

      The ASBR is enabled to exchange labeled IPv4 routes with the local PE device in the same AS.

    11. Run peer ipv4-address as-number as-number

      The peer ASBR is specified as the EBGP peer.

    12. (Optional) Run peer { ipv4-address | group-name } ebgp-max-hop [ hop-count ]

      The maximum number of hops is configured for the EBGP connection.

      Generally, EBGP peers are connected directly using a physical link. If no direct physical link is available, run the peer ebgp-max-hop command to set the maximum number of hops in the EBGP connection.

      If BGP uses a loopback interface to establish an EBGP peer relationship, you must run the peer ebgp-max-hop command and set to the hop count to a value greater than or equal to 2. Otherwise, the peer relationship cannot be established. If hop-count is not specified, the default value 255 is used.

    13. Run peer ipv4-address label-route-capability [ check-tunnel-reachable ]

      The ASBR is enabled to exchange labeled IPv4 routes with the peer ASBR.

      • If you do not specify check-tunnel-reachable so that the system checks the reachability of tunnels, BGP advertises IPv4 unicast routes to peers when routed tunnels are unreachable or advertises labeled routes to peers when routed tunnels are reachable. This ensures that MP-EBGP peer relationships between PEs are not established over a faulty LSP, eliminating the associated risk of data forwarding failures.
      • If you specify check-tunnel-reachable, BGP advertises labeled routes to peers regardless of whether the tunnels for imported routes are reachable.

    14. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-04-03

Document ID: EDOC1100075353

Views: 16324

Downloads: 26

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