peer update-group-independent (BGP multi-instance VPNv4 address family view) (group)

Usage Scenario

To improve the efficiency of route advertisement, BGP uses the dynamic update peer-group mechanism. The BGP peers with the same configurations are placed in an update peer-group. These routes are grouped once and then sent to all peers in the update peer-group. However, the routes learned from a peer may be sent back to the peer, for example, the preferred route learned from an EBGP peer is sent back to the EBGP peer, or the preferred route that an RR learns from a client is reflected back to the client. In this case, messages are discarded, wasting network resources.

To address this problem, you can run the peer update-group-independent command to set a specified peer or each peer in a peer group as an independent update peer-group so that the routes learned from the peer are not sent back to the peer. However, if a specified peer or each peer in a peer group is set as an independent update peer-group, the advantages of the dynamic update peer-group mechanism cannot be brought into full play. Therefore, this command is used only when users have such a requirement.

Prerequisites

A peer group has been added to an update peer-group using the peer group command.

Precautions

The configuration of a peer takes precedence over that of the peer group to which the peer belongs. For example, if the peer update-group-independent disable command is run for a peer and the peer update-group-independent command is run for the peer group to which the peer belongs, the configuration of the peer prevails. That is, the peer is not set as an independent update peer-group.

On a device with a large memory, you are advised to run the peer update-group-independent command to prevent network resource waste by route sending back.