Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) - Manual (Page 73)

Multi-Service IronWare Routing Configuration Guide 45
53-1003033-02
Configuring a static BGP4 network
The number variable specifies the number of equal-cost multipath IBGP routes that will be
selected. The range is 2 to 32. If the value is set to 1, BGP4 level equal-cost multipath is disabled
for IBGP routes.
To set the number of equal-cost multipath EBGP routes or paths that will be selected, enter
commands such as the following.
Brocade(config)# router bgp
Brocade(config-bgp)# maximum-paths ebgp
Syntax: [no] maximum-paths ebgp num
The number variable specifies the number of equal-cost multipath EBGP routes that will be
selected. The range is 2 to 32. If the value is set to 1, BGP4 level equal-cost multipath is disabled
for EBGP routes.
Configuring a static BGP4 network
This feature allows you to configure a static network in BGP4, creating a stable BGP4 network in
the core. While a route configured with this feature will never flap unless it is manually deleted, a
“static” BGP4 network will not interrupt the normal BGP4 decision process on other learned routes
being installed into the RTM (Routing Table Manager). Consequently, when there is a route that can
be resolved, it will be installed into the RTM.
To configure a static BGP4 network, enter commands such as the following.
Brocade(config)# router bgp
Brocade(config-bgp)# static-network 10.157.22.26/16
Syntax: [no] static-network ipAddressPrefix/mask
The ipAddress/mask variable is the IPv4 address prefix and mask of the static BGP4 network you
are creating.
Using the no option uninstalls a route (that was previously installed) from BGP4 RIB-IN and
removes the corresponding drop route from the RTM. If there is a new best route, it is advertised to
peers if necessary. Otherwise, a withdraw message is sent.
NOTE
The BGP4 network route and the BGP4 static network route are mutually exclusive. They cannot be
configured with the same prefix and mask.
When you configure a route using the static-network command, BGP4 automatically generates a
local route in BGP4 RIB-IN, and installs a NULL0 route in the RTM if there is no other valid route
with the same prefix/mask learned from any peer. Otherwise, the learned BGP4 route will be
installed in the RTM. In either situation, the new locally generated route will be the best route in
RIB-IN and will be advertised to peers if it passes the per-peer outbound policies.
Setting an administrative distance for a static BGP4 network
When a static BGP4 network route is configured, its type is local BGP4 route and has a default
administrative distance value of 200. To change the administrative distance value, change the
value of all local BGP4 routes using the distance command at the router bgp level of the CLI, and
set a new value for local routes as described in
“Changing administrative distances” on page 39.
You can also assign a specific administrative distance value for each static network using the
distance option as shown.