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

CLI-based Configuration Guide - VPN

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document describes VPN features on the device and provides configuration procedures and configuration examples.
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 Inter-AS Martini VPLS in OptionC Mode

Configuring Inter-AS Martini VPLS in OptionC Mode

In inter-AS LDP VPLS Option C, ASBRs do not need to maintain inter-AS LDP VPLS information or reserve interfaces for inter-AS LDP VPLS PWs. As LDP VPLS information is exchanged only between PEs, this solution requires few resources and is easy to deploy.

Pre-configuration Task

Before configuring inter-AS Martini VPLS in OptionC mode, complete the following tasks:
  • Configure IGP for the MPLS backbone network of each AS to ensure IP connectivity of the backbone network within an AS.
  • Configure basic MPLS functions on the MPLS backbone network of each AS.
  • Configure MPLS LDP and establish the LDP LSP for the MPLS backbone network of each AS.
  • Set up the IBGP peer relationship between the PE and the ASBR of the same AS and set up the EBGP peer relationship between two inter-AS ASBRs.

Procedure

  1. Configure the capability to exchange labeled IPv4 routes.

    • Perform the following steps on each PE:
      1. Run system-view

        The system view is displayed.

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

        The Border Gateway Protocol (BGP) view is displayed.

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

        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

        Exchange of the labeled IPv4 routes with the ASBR in the same AS is enabled.

    • Perform the following steps on each ASBR:
      1. Run system-view

        The system view is displayed.

      2. Run interface interface-type interface-number

        The view of the interface connecting to the peer ASBR is displayed.

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

        An IP address is configured for the interface.

      4. Run mpls

        MPLS is enabled on the interface.

      5. Run mpls ldp

        MPLS LDP is enabled on the interface.

      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

        An IBGP peer relationship is established between the local PE and the remote 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

        Exchange of the labeled IPv4 routes with the remote PE in the same AS is enabled.

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

        The peer ASBR is specified as the EBGP peer.

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

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

        In inter-AS LDP VPLS Option C, an inter-AS LSP must be established and the public network routes advertised between PEs and ASBRs carry MPLS labels.

        An EBGP peer relationship must be established between ASBRs in different ASs for them to exchange labeled IPv4 routes.

        The public network routes carrying MPLS labels are advertised through MP-BGP. Label mappings about routes can be piggybacked inside the BGP Update messages that are used to advertise these routes. This feature is implemented through an extended BGP attribute, which enables BGP peers to process labeled IPv4 routes.

        By default, BGP peers cannot process labeled IPv4 routes.

  2. Configure a routing policy on the ASBR to control label distribution.

    After the routing policy is applied to an ASBR, the ASBR allocates MPLS labels to routes received from a PE in the local AS before advertising the routes to the remote ASBR, and reallocates MPLS labels to labeled IPv4 routes advertised to a PE in the local AS.

    By default, an IPv4 route does not carry any MPLS label.

    Perform the following steps on each ASBR:

    1. Run system-view

      The system view is displayed.

    2. Run route-policy policy-name1 permit node seq-number

      A routing policy applicable to the local PE is created.

      The device reallocates MPLS labels to labeled IPv4 routes advertised to a PE in the local AS.

    3. Run if-match mpls-label

      Filtering out labeled IPv4 routes is configured as a matching rule for the routing policy.

    4. Run apply mpls-label

      Allocating MPLS labels to IPv4 routes is configured as an action for the routing policy.

    5. Run quit

      Return to the system view.

    6. Run route-policy policy-name2 permit node seq-number

      A routing policy applicable to the peer ASBR is created.

      When an ASBR advertises the routes received from a PE in the same AS to the peer ASBR, the ASBR allocates MPLS labels to the routes.

    7. Run apply mpls-label

      Allocating MPLS labels to IPv4 routes is configured as an action for the routing policy.

    8. Run quit

      Return to the system view.

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

      The BGP view is displayed.

    10. Run peer ipv4-address route-policy policy-name1 export

      The routing policy applicable to the local PE is applied.

    11. Run peer ipv4-address route-policy policy-name2 export

      The routing policy applicable to the peer ASBR is applied.

  3. Establish remote MPLS LDP sessions between PEs.

    Configure an ASBR to send the loopback interface IP addresses of a PE device used for peer relationship establishment to the ASBRs of other ASs and the PEs in different ASs.

    • Perform the following steps on each ASBR:
      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 network ip-address [ mask | mask-length ] [ route-policy route-policy-name ]

        The capability to advertise the local PE's loopback interface address used for BGP sessions to the peer ASBR is configured.

      4. Run quit

        Return to the system view.

    • Perform the following steps on each PE:
      1. Run system-view

        The system view is displayed.

      2. Run mpls ldp remote-peer peer-name

        The name of the remote MPLS LDP session is specified.

        Remote MPLS LDP sessions need to be established between PEs, so that they can directly exchange PW information.

      3. Run remote-ip ip-address

        The peer IP address of the remote MPLS LDP session is specified.

  4. Configure Martini VPLS on each PE. For configuration details, see Configuring Martini VPLS.
Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100033725

Views: 143189

Downloads: 361

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