Brocade Communications Systems ICX 7250 series, Руководство по настройке

Страница: 311 / 483

FIGURE 29 A route reflector configuration
Support for RFC 4456
Route reflection on Brocade devices is based on RFC 4456. This updated RFC helps eliminate routing loops that are possible in some
implementations of the older specification, RFC 1966. These instances include:
• The device adds the route reflection attributes only if it is a route reflector, and only when advertising IBGP route information to
other IBGP neighbors. The attributes are not used when communicating with EBGP neighbors.
• A device configured as a route reflector sets the ORIGINATOR_ID attribute to the device ID of the device that originated the
route. The route reflector sets this attribute only if this is the first time the route is being reflected (sent by a route reflector).
• 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 first time a route is reflected by a device configured as a route reflector, the route reflector adds the CLUSTER_LIST
attribute to the route. Other route reflectors that receive the route from an IBGP neighbor add their cluster IDs to the front of the
routes CLUSTER_LIST. If the route reflector does not have a cluster ID configured, the device adds its device ID to the front of
the CLUSTER_LIST.
• If a device configured as a route reflector receives a route with a CLUSTER_LIST that contains the cluster ID of the route
reflector, the route reflector discards the route.
Configuration procedures for BGP4 route reflector
To configure a Brocade device to be a BGP4 route reflector, use either of the following methods.
Optional BGP4 configuration tasks
Brocade FastIron Layer 3 Routing Configuration Guide
53-1003903-04 311