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


To have a better experience, please upgrade your IE browser.


Configuration Guide - IP Unicast Routing

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.
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 a BGP Confederation

Configuring a BGP Confederation


A confederation divides an AS into sub-ASs. Within each sub-AS, IBGP peers establish full-mesh connections or have an RR configured. Sub-ASs establish EBGP connections. On a large BGP network, configuring a confederation can reduce the number of IBGP connections, simplify routing policy management, and improve route advertisement efficiency.

Other devices may implement the confederation not in accordance with RFC 3065. You can configure confederation compatibility to make standard devices compatible with nonstandard devices.


BGP peers within a BGP confederation do not change the next hop of BGP routes to their local IP addresses before advertising the routes to each other, unless the peer next-hop-local command is run.


  1. Run system-view

    The system view is displayed.

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

    BGP is enabled and the BGP view is displayed.

  3. Run confederation id { as-number-plain | as-number-dot }

    A confederation ID is configured.

    By default, no BGP confederation is configured.

    An old speaker that has a 2-byte AS number cannot be in the same confederation with a new speaker that has a 4-byte AS number. Otherwise, a routing loop may occur. This is because the AS4_Path attribute does not support confederations.

  4. Run confederation peer-as { as-number-plain | as-number-dot } &<1-32>

    A sub-AS number is configured for a confederation.

    By default, no sub-AS number of the confederation is configured.

  5. (Optional) Run confederation nonstandard

    Confederation compatibility is configured.

    By default, confederations comply with RFC 3065.

  6. Run commit

    The configuration is committed.

Verifying the Configuration

  • Run the display bgp peer [ ipv4-address ] verbose command to check detailed information about BGP peers.
  • Run the display bgp routing-table [ ipv4-address [ { mask | mask-length } [ longer-prefixes ] ] ] command to check routing information in a BGP routing table.
Updated: 2019-04-20

Document ID: EDOC1100074760

Views: 45413

Downloads: 58

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