3com S7906E Manuel De Montage

Page de 2621
 
1-40 
To do… 
Use the command… 
Remarks 
Advertise the 
community attribute to 
a peer/peer group 
peer { group-name | ip-address 
advertise-community 
Advertise the 
community 
attribute to a 
peer/peer group 
Advertise the 
extended community 
attribute to a peer/peer 
group 
peer { group-name | ip-address 
advertise-ext-community 
Required 
Not configured 
by default. 
Apply a routing policy to routes advertised 
to a peer/peer group 
peer { group-name | ip-address 
route-policy route-policy-name 
export 
Required 
Not configured 
by default. 
 
Configuring a BGP Route Reflector 
If an AS has many BGP routers, you can configure them as a cluster and configure one of them as a 
route reflector and others as clients to reduce iBGP connections. 
To enhance network reliability and prevent single point failures, you can specify multiple route reflectors 
for a cluster. The route reflectors in the cluster must have the same cluster ID specified to avoid routing 
loops. 
Follow these steps to configure a BGP route reflector: 
To do… 
Use the command… 
Remarks 
Enter system view 
system-view 
— 
Enter BGP view 
bgp as-number 
— 
Configure the router as a route 
reflector and specify a 
peer/peer group as its client 
peer { group-name | 
ip-address 
reflect-client 
Required 
Not configured by default. 
Enable route reflection 
between clients 
reflect between-clients 
Optional 
Enabled by default 
Configure the cluster ID of the 
route reflector 
reflector cluster-id cluster-id 
Optional 
By default, a route reflector 
uses its router ID as the cluster 
ID. 
 
 
In general, it is not required to make clients of a route reflector fully meshed. The route reflector 
forwards routing information between clients. If clients are fully meshed, you can disable route 
reflection between clients to reduce routing costs. 
In general, a cluster has only one route reflector, and the router ID is used to identify the cluster. 
You can configure multiple route reflectors to improve network stability. In this case, you need to 
specify the same cluster ID for these route reflectors using the reflector cluster-id command to 
avoid routing loops.