Operation Manual - Routing Protocol
Quidway S3500 Series Ethernet Switches Chapter 5 BGP Configuration
Huawei Technologies Proprietary
5-20
on route reflector, and all client peers and non-client peers are routine BGP peers. The
client peers are client peers just because the route reflector lists them as client peers.
I. Configure the route reflection between clients
Perform the following configurations in BGP view.
Table 5-33 Configuring the route reflection between clients
Operation Command
Enable route reflection between clients
reflect between-clients
Disable route reflection between clients
undo reflect between-clients
By default, the reflection between clients is enabled.
II. Configuring the cluster ID
Generally, there is only one route reflector in a cluster.
Perform the following configurations in BGP view.
Table 5-34 Configuring the Cluster_ID of the route reflector
Operation Command
Configure the Cluster_ID of the route reflector
reflector cluster-id { cluster-id
| address }
Canceling the Cluster_ID of the route reflector
undo reflector cluster-id
By default, the router ID of the route reflector is used as the cluster ID.
III. Two kinds of measures to avoid looping inside AS
As route reflector is imported, it is possible that path looping will be generated in AS.
Path update packets already left the cluster may attempt to return to the cluster. The
conventional AS path method can’t detect the internal AS looping, because the path
update packet hasn’t left AS. Upon configuring route reflector, BGP provides the
following measures to avoid internal AS looping:
1) Configure the Originator_ID of the route reflector
The Originator_ID is established by route reflector. The originator will drop the update
packet returning to the originator should it be improper configuration.
The parameter is not necessarily configured, and it will automatically function upon
enabling BGP.
2) Configure the Cluster_ID of the route reflector
To Next Page
Loading...
Need help?
General
