Supported Platforms
Related Documentation
- ACX, M, MX, T Series
- Example: Configuring BGP Route Reflectors
- ACX, J, M, MX, SRX Series
- Understanding External BGP Peering Sessions
- ACX, EX, M, MX, PTX, QFX, SRX, T Series
- no-client-reflect
cluster
Syntax
Hierarchy Level
Release Information
Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Description
Specify the cluster identifier to be used by the route reflector cluster in an internal BGP group.
![]() | If you configure both route reflection and VPNs on the same routing device, the following modifications to the route reflection configuration cause current BGP sessions to be reset:
|
![]() | Note: If you change the address family specified in the [edit protocols bgp family] hierarchy level, all current BGP sessions on the routing device are dropped and then reestablished. |
Options
cluster-identifier—4-byte number (such as an IPv4 address).
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- ACX, M, MX, T Series
- Example: Configuring BGP Route Reflectors
- ACX, J, M, MX, SRX Series
- Understanding External BGP Peering Sessions
- ACX, EX, M, MX, PTX, QFX, SRX, T Series
- no-client-reflect
Published: 2013-04-18
Supported Platforms
Related Documentation
- ACX, M, MX, T Series
- Example: Configuring BGP Route Reflectors
- ACX, J, M, MX, SRX Series
- Understanding External BGP Peering Sessions
- ACX, EX, M, MX, PTX, QFX, SRX, T Series
- no-client-reflect