Owner's Manual

704 | Chapter 26. BGP
NETGEAR 8800 User Manual
• Inactive Route Advertisement on page 710
• Default Route Origination and Advertisement on page 711
• Using the Loopback Interface on page 712
• Looped AS_Path Attribute on page 713
• BGP Peer Groups on page 713
• BGP Route Flap Dampening on page 714
• BGP Route Selection on page 716
• Stripping Out Private AS Numbers from Route Updates on page 716
• Route Redistribution on page 717
• BGP Static Network on page 718
• Graceful BGP Restart on page 719
• Cease Subcodes on page 721
• Fast External Fallover on page 722
• Capability Negotiation on page 722
• Route Refresh on page 723
Route Reflectors
Another way to overcome the difficulties of creating a fully meshed AS is to use route
reflectors. Route reflectors allow a single router to serve as a central routing point for the AS.
A cluster is formed by the route reflector and its client routers. Peer routers that are not part of
the cluster must be fully meshed according to the rules of BGP.
A BGP cluster, including the route reflector and its clients, is shown in Figure 80.
Figure 80. Route Reflectors
EX_042
Client
Route Reflector
Non-client
10.0.0.1
10.0.0.2
30.0.0.1
30.0.0.2
20.0.0.2
20.0.0.1
1.1.1.1
2.2.2.2
3.3.3.3
Cluster
AS 100
Client
4.4.4.4