FIGURE 31 A route reector conguration
Support for RFC 4456
Route reection on Brocade devices is based on RFC 4456. This updated RFC helps eliminate routing loops that are possible in some
implementations of the older specication, RFC 1966. These instances include:
• The device adds the route reection attributes only if it is a route reector, and only when advertising IBGP route information to
other IBGP neighbors. The attributes are not used when communicating with EBGP neighbors.
• A device congured as a route reector sets the ORIGINATOR_ID attribute to the device ID of the device that originated the
route. The route reector sets this attribute only if this is the rst time the route is being reected (sent by a route reector).
• If a device receives a route with an ORIGINATOR_ID attribute value that is the same as the ID of the device, the device discards
the route and does not advertise it. By discarding the route, the device prevents a routing loop.
• The rst time a route is reected by a device congured as a route reector, the route reector adds the CLUSTER_LIST
attribute to the route. Other route reectors that receive the route from an IBGP neighbor add their cluster IDs to the front of the
routes CLUSTER_LIST. If the route reector does not have a cluster ID congured, the device adds its device ID to the front of
the CLUSTER_LIST.
• If a device congured as a route reector receives a route with a CLUSTER_LIST that contains the cluster ID of the route
reector, the route reector discards the route.
Conguration procedures for BGP4 route reector
To congure a Brocade device to be a BGP4 route reector, use either of the following methods.
Optional BGP4 conguration tasks
FastIron Ethernet Switch Layer 3 Routing
390 53-1003627-04
To Next Page
Loading...
Need help?
General
