212
command configures itself as the route reflector, while specific peer group is as its client. Note:
this configuration is only available inside AS
Example:
Switch(config)#router bgp 100
Switch(config-router)#neighbor 10.1.1.66 remote 100
Switch(config-router)#neighbor 10.1.1.66 route-reflector-client
Switch(config-router)#neighbor 10.1.1.68 remote 100
Switch(config-router)#neighbor 10.1.1.68 route-reflector-client
Switch(config-router)#
1.8.3.64 neighbor route-server-client
Command: neighbor {<ip-address>|<TAG>} route-server-client
no neighbor {<ip-address>|<TAG>} route-server-client
Function:
Configure the route server client. The “
no neighbor {<ip-address>|<TAG>}
route-server-client
” command cancels this configuration
Parameter: <ip-address>
: Neighbor IP address
<TAG>
: Name of peer group
Default:
Not configured
Command Mode:
BGP route mode and address-family mode.
Usage Guide:
The route service is for reducing the peers when the router between AS is too
much under EBGP environment. The server transparently transforms the routing messages to
other clients with its client exchanges messages through route server
Example:
Three routers : 10.1.1.64
（
AS100
）
and 10.1.1.68
（
AS300
）
respectively creates neighbor
relationship with the connected 10.1.1.66
（
AS200
）
, the configuration is as follows
Switch(config)#router bgp 200
Switch(config-router)#neighbor 10.1.1.64 remote-as 100
Switch(config-router)#neighbor 10.1.1.64 route-server-client
Switch(config-router)# neighbor 10.1.1.68 remote-as 300
Switch(config-router)# neighbor 10.1.1.68 route-server-client
1.8.3.65 neighbor send-community
Command: neighbor {<ip-address>|<TAG>} send-community [both|extended|standard]
no neighbor {<ip-address>|<TAG>} send-community
[both|extended|standard]
Function:
Configures whether sending the community attribute to the neighbors. The “
no
neighbor {<ip-address>|<TAG>} send-community [both|extended|standard]
” command set
to not sending.