Operation Manual – Routing ProtocolH3C S9500 Series Routing Switches Chapter 6 BGP Configuration6-23This command works on IBGP peer groups only.By default, all IBGP routes in an AS must be full-connected, and neighbors do notadvertise learned IBGP routes to one another.II. Configuring the route reflection between clientsPerform the following configuration in BGP view.Table 6-38 Configure the route reflection between clientsOperation CommandEnable route reflection between clients reflect between-clientsDisable route reflection between clients undo reflect between-clientsBy default, the route reflection between clients is allowed. If the clients are fullyconnected, for the purpose of overhead reduction, it is recommended to use the undoreflect between-clients command to disable the route reflection between clients.III. Configuring the cluster IDGenerally, there is only one route reflector in a cluster which is identified by the routerID of the route reflector.Perform the following configuration in BGP view.Table 6-39 Configure the Cluster_ID of the route reflectorOperation CommandConfigure the Cluster_ID of the route reflector reflector cluster-id { cluster-id |address }Cancel the Cluster_ID of the route reflector undo reflector cluster-idThe autonomous system possibly generates routing loop due to the route reflector in acluster. After leaving a cluster, a routing update packet possibly tries to go back to thecluster. Because the routing update packet has not left an AS, the traditional AS pathmethod cannot detect the loop inside the AS. When configuring route reflectors, youcan use the following two methods to avoid loop inside the AS. One is to use the clusterID; the other is to use Originator_ID of a route reflector.If you configure Originator_ID improperly, the originator will discard the update packetwhen the update packet goes back to the originator. You do not need to configureOriginator_ID. Originator_ID automatically takes effect when BGP is enabled.
