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 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - VPN
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 BGP VPWS Option C

Configuring Inter-AS BGP VPWS Option C

ASBRs do not need to maintain inter-AS L2VPN information or reserve interfaces for inter-AS L2VPN PWs. As L2VPN 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 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 that connects 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 quit

        Return to the system view.

      5. Run mpls

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

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

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

        The peer ASBR is configured as an EBGP peer.

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

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

        In inter-AS BGP VPWS 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 relevant standards, 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.

      11. Run commit

        The configuration is committed.

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

    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. Configure PEs to exchange VPWS information as BGP peers.
    1. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    2. Run peer ip-address as-number as-number

      A BGP peer and its AS number are specified.

    3. Run peer ip-address connect-interface interface-type interface-number

      The source interface for sending BGP packets is specified.

    4. Run l2vpn-ad-family

      The L2VPN-AD address family view is displayed.

    5. (Optional) Run vpn-orf enable

      The ORF is enabled.

    6. Run peer ipv4-address enable

      The route exchange capability is enabled.

    7. Run signaling vpws or peer ip-address signaling vpws

      BGP VPWS is enabled.

    8. Run quit

      Return to the BGP view.

    9. Run quit

      Return to the system view.

  4. Configure a remote BGP VPWS connection.
    1. Run mpls l2vpn l2vpn-name [ encapsulation encapsulation-type ] [ control-word | no-control-word ]

      A BGP VPWS instance is created, and the MPLS-L2VPN instance view is displayed.

      If heterogeneous interworking is required, specify encapsulation-type as ip-interworking for successful PW establishment.

    2. Run route-distinguisher route-distinguisher

      An RD is configured for the L2VPN instance.

    3. (Optional) Run mtu mtu-value

      An MTU is configured for the L2VPN instance.

      The MTU size determines the maximum packet size allowed by a VPWS network. If the MTU exceeds the maximum packet size allowed by a VPWS network or an intermediate node (P), packet fragmentation or even drop will occur, affecting network transmission. The MTU is one of the VPWS negotiation parameters. If the MTUs of the same L2VPN instance on the endpoint PEs are different, the two PEs cannot exchange reachability information or establish a PW. An appropriate MTU must be set for an L2VPN instance based on the MTU of the interface bound to the L2VPN instance. Specifically, the MTU of an L2VPN instance must be smaller than or equal to the MTU of the interface bound to the L2VPN instance.

    4. (Optional) Run ignore-mtu-match

      The current device is configured not to perform the MTU match check.

      By default, an MTU match check is performed on the endpoint PEs.

      If the MTUs of the same L2VPN instance on the two endpoint PEs do not match, the VC cannot go Up. If some devices do not support the MTU match check, run the ignore-mtu-match command to disable this check.

    5. Run vpn-target vpn-target & <1-16> [ both | export-extcommunity | import-extcommunity ]

      VPN targets are configured.

    6. Run ce ce-name [ id ce-id [ range ce-range ] [ default-offset ce-offset ] ]

      A CE is created in the L2VPN instance.

    7. Run connection [ ce-offset ce-offset-id ] interface interface-type interface-number [ tunnel-policy tunnel-policy-name ] [ raw | tagged ] [ secondary ]

      A remote BGP VPWS connection is configured.

  5. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27305

Downloads: 51

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