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 - MPLS

S7700 and S9700 V200R010C00

This document describes MPLS configurations supported by the switch, including the principle and configuration procedures of static LSPs, MPLS LDP, MPLS TE, MPLS QoS, MPLS OAM, Seamless MPLS, and MPLS common features, and provides 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 AGG and Core ABR as RRs

Configuring AGG and Core ABR as RRs

Context

To enable the CSG and MASG to learn loopback routes to each other on an intra-AS seamless MPLS network, configure an AGG and a core ABR as reflectors, specify a CSG and the core ABR as the AGG's clients, and specify the AGG and an MASG as the core ABR's clients. The loopback routes can be used to set up an MP-IBGP peer relationship between the CSG and MASG.

Procedure

  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:

    ipv4-family unicast

    The IPv4 unicast address family view is displayed.

  4. Run:

    peer { ipv4-address | group-name } reflect-client

    An RR is configured, and the peer is specified as a client.

    By default, no RR or specified client is configured for BGP.

  5. Run:

    peer { ipv4-address | group-name } next-hop-local

    BGP is configured to use its own IP address as the next hops of routes when advertising these routes to its clients.

    By default, when BGP advertises routes to an EBGP peer, it uses its own IP address as the next hops. When BGP advertises routes to an IBGP peer, it does not change the next hop attribute.

    To enable the AGG or core ABR to advertise routes with the next hop address set to a local address, run the peer next-hop-local command on the AGG or core ABR.

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000141902

Views: 73366

Downloads: 189

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