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

NE40E V800R010C10SPC500 Configuration Guide - IP Routing 01

This is NE40E V800R010C10SPC500 Configuration Guide - IP Routing
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 Peer Group

Configuring a BGP Peer Group

Configuring BGP peer groups simplifies the BGP network configuration and improves the route advertisement efficiency.

Usage Scenario

A BGP peer group consists of BGP peers that have the same update policies and configurations.

A large-scale BGP network has a large number of peers. Configuring and maintaining these peers is difficult. To address this problem, configure a BGP peer group for BGP peers with the same configurations. Configuring BGP peer groups simplifies peer management and improves the route advertisement efficiency.

Based on the ASs where peers reside, peer groups are classified as follows:
  • IBGP peer group: The peers of an IBGP peer group are in the same AS.
  • Pure EBGP peer group: The peers of a pure EBGP peer group are in the same external AS.
  • Mixed EBGP peer group: The peers of a mixed EBGP peer group are in different external ASs.

If a function is configured on a peer and its peer group, the function configured on the peer takes effect. After a peer group is created, peers can be added to the peer group. If these peers are not configured separately, they will inherit the configurations of the peer group. If a peer in a peer group has a specific configuration requirement, the peer can be configured separately. The configuration of this peer will override the configuration that the peer has inherited from the peer group.

Pre-configuration Tasks

Before configuring BGP peer groups, configure basic BGP functions.

Configuration Procedures

Perform one or more of the following configurations as required.

Creating an IBGP Peer Group

If multiple IBGP peers exist, adding them to an IBGP peer group can simplify the BGP network configuration and management. When creating an IBGP peer group, you do not need to specify an AS number for the IBGP peer group.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run group group-name internal

    An IBGP peer group is created.

  4. Run peer ipv4-address group group-name

    A peer is added to the peer group.

    NOTE:

    You can repeat step 4 to add multiple peers to the peer group. If the local device has not established a peer relationship with this peer, the device will attempt to establish a peer relationship with this peer, and set the AS number of this peer to the AS number of the peer group.

    When creating an IBGP peer group, you do not need to specify the AS number.

    After configuring a peer group, you can configure BGP functions for the peer group. By default, all peers in a peer group inherit the entire configuration of the peer group. If you configure a peer in a peer group independently. The configuration of this peer will override the configuration that the peer has inherited from the peer group.

  5. (Optional) Run peer group-name description description-text

    The description of the peer group is configured.

    You can simplify network management by configuring the descriptions of peers.

  6. Run commit

    The configuration is committed.

Creating a Pure EBGP Peer Group

If multiple EBGP peers exist in an AS, adding them to an EBGP peer group can simplify the BGP network configuration and management. All the peers in a pure EBGP peer group must have the same AS number.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run group group-name external

    A pure EBGP peer group is created.

  4. Run peer group-name as-number as-number

    An AS number is set for the EBGP peer group. If peers already exist in a peer group, you can neither change the AS number of the peer group nor delete the AS number of the peer group using the undo peer as-number command.

  5. Run peer ipv4-address group group-name

    A peer is added to the peer group.

    NOTE:

    You can repeat step 5 to add multiple peers to the peer group. If the local device has not established a peer relationship with this peer, the device will attempt to establish a peer relationship with this peer, and set the AS number of this peer to the AS number of the peer group.

    After configuring a peer group, you can configure BGP functions for the peer group. By default, all peers in a peer group inherit the entire configuration of the peer group. If you configure a peer in a peer group independently. The configuration of this peer will override the configuration that the peer has inherited from the peer group.

  6. (Optional) Run peer group-name description description-text

    The description of the peer group is configured.

    You can simplify network management by configuring the descriptions of peers.

  7. Run commit

    The configuration is committed.

Creating a Mixed EBGP Peer Group

If multiple EBGP peers exist in different ASs, adding them to a mixed EBGP peer group can simplify the BGP network configuration and management. When creating a mixed EBGP peer group, you need to specify an AS number for each peer.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run group group-name external

    A mixed EBGP peer group is created.

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

    A peer is created and an AS number is set for this peer.

  5. Run peer ipv4-address group group-name

    The peer is added to the peer group.

    NOTE:

    You can repeat Steps 4 and 5 to add multiple peers to the peer group.

    You need to specify an AS number for each peer in a mixed EBGP peer group.

    After configuring a peer group, you can configure BGP functions for the peer group. By default, all peers in a peer group inherit the entire configuration of the peer group. If you configure a peer in a peer group independently. The configuration of this peer will override the configuration that the peer has inherited from the peer group.

  6. (Optional) Run peer group-name description description-text

    The description of the peer group is configured.

    You can simplify network management by configuring the descriptions of peers.

  7. Run commit

    The configuration is committed.

Verifying the BGP Peer Group Configuration

After configuring a BGP peer group, check information about BGP peers and BGP peer groups.

Prerequisites

A BGP peer group has been configured.

Procedure

  • Run the display bgp peer [ ipv4-address ] verbose command to check detailed information about BGP peers.
  • Run the display bgp group [ group-name ] command to check information about BGP peer groups.

    NOTE:

    This command is applied only to devices on which BGP peer groups are created.

    If a peer group is specified in this command, detailed information about this peer group will be displayed. If no peer group is specified in this command, information about all BGP peer groups is displayed.

Example

Run the display bgp group [ group-name ] command in the system view to view information about a specified peer group.

# View information about a peer group named my-peer.

<HUAWEI> display bgp group my-peer
 BGP peer-group: my-peer
 Remote AS 200
 Group's BFD has been enabled
 Type : internal
 Maximum allowed route limit: 150000
 Threshold: 75%
 Configured hold timer value: 180
 Keepalive timer value: 60
 Minimum route advertisement interval is 15 seconds
 listen-only has been configured
PeerSession Members:
   2.2.2.2
 Peer Preferred Value: 0
 No routing policy is configured
  Peer Members:
  Peer            V   AS   MsgRcvd  MsgSent  OutQ  Up/Down      State PrefRcv
  2.2.2.2         4   200        0        0     0 00:00:47     Active       0
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055018

Views: 48960

Downloads: 201

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