Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

group (Protocols BGP)

Syntax

Hierarchy Level

Description

Define a BGP peer group. BGP peer groups share a common type, peer autonomous system (AS) number, and cluster ID, if present. To configure multiple BGP groups, include multiple group statements.

By default, the group’s options are identical to the global BGP options. To override the global options, include group-specific options within the group statement.

The group statement is one of the statements you must include in the configuration to run BGP on the routing device.

Each group must contain at least one peer and can establish up to 2048 peers. Before establishing a BGP session, RPD checks for established peer count for the group. If the peer count is more than 2048 then the BGP session fails.

Options

group-name

Name of the BGP group

link-bandwith auto-sense

Enable this option to automatically detect the bandwidth towards the peer and attach the link-bandwith value to the interface speed over which the BGP route was received. This prevents a policy churn when there is a change in the link-bandwidth of an interface. Make sure that you also include the auto-sense statement in the import policy to enable this feature.

send-non-transitive-link-bandwidth

Enable this option to send non-transitive-link-bandwidth-extended-community towards EBGP neighbors only for link-bandwidth communities. All non-transitive link bandwith community values are advertised including originated or received and readvertised link-bw community.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced before Junos OS Release 7.4.

link-bandwith auto-sense, and send-non-transitive-link-bandwidth options introduced in Junos OS Release 24.2R1.