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).
Configuring Inter-AS LDP VPLS Option C

Configuring Inter-AS LDP VPLS Option C

Context

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.

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 label-route-capability

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

      4. Run commit

        The configuration is committed.

    • 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. 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.

        If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

        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 quit

        Return to the system view.

      6. Run mpls

        MPLS is enabled.

      7. Run quit

        Return to the system view.

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

        The BGP view is displayed.

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

        The capability to exchange labeled IPv4 routes with the local PE is configured.

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

        The peer ASBR is configured as an External Border Gateway Protocol (EBGP) peer.

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

        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. According to RFC 3107, 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.

      12. Run commit

        The configuration is committed.

  2. Configure routing policies on each ASBR, so that an ASBR reallocates MPLS labels to the labeled IPv4 routes to be advertised to the local PE and allocates MPLS labels to the routes to be advertised to the peer ASBR.

    ASBRs allocate MPLS labels to IPv4 routes based on the configured routing policies. 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.

    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.

    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.

    12. Run commit

      The configuration is committed.

  3. Establish a remote MPLS LDP session between the PEs in different ASs, so that the PEs can exchange PW information.

    • 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.

      5. Run commit

        The configuration is committed.

    • 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.

      3. Run remote-ip ip-address

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

      4. Run commit

        The configuration is committed.

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

Document ID: EDOC1100075353

Views: 14219

Downloads: 25

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