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

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

Adding BGP4 neighbors
Because BGP4 does not contain a peer discovery process, for each BGP4 neighbor (peer), you must indicate the IP address and the AS
number of each neighbor. Neighbors that are in different autonomous systems communicate using EBGP. Neighbors within the same
AS communicate using IBGP.
NOTE
If the device has multiple neighbors with similar attributes, you can simplify configuration by configuring a peer group, then
adding individual neighbors to it. The configuration steps are similar, except you specify a peer group name instead of a
neighbor IP address when configuring the neighbor parameters, then add individual neighbors to the peer group.
NOTE
The device attempts to establish a BGP4 session with a neighbor as soon as you enter a command specifying the IP address
of the neighbor. If you want to completely configure the neighbor parameters before the device establishes a session with the
neighbor, you can administratively shut down the neighbor.
To add a BGP4 neighbor with an IP address 10.157.22.26, enter the following command.
device(config-bgp-router)# neighbor 10.157.22.26 remote-as 100
The neighbor ip-addr must be a valid IP address.
The neighbor command has additional parameters, as shown in the following syntax:
Syntax: no neighbor { ip-addr | peer-group-name } {[ activate ] [ advertisement-interval seconds [ allowas-in num ] [ capability as4 [ enable |
disable ]] [ capability orf
prefixlist [ send | receive ]] [ default-originate [ route-map map-name ]] [ description string ] [ distribute-list in | out
num,num,... | ACL-num localin | out ] [ ebgp-btsh ] [ ebgp-multihop [ num ]] [ enforce-first-as ] [ filter-list access-list-name [ in | out ]] [ local-
as as-num [ no-prepend ]] [ maxas-limit in [ num | disable ] [ maximum-prefix num [ threshold ] [ teardown ] [ next-hop-self ] [ password
string ] [ peer-group group-name ] [ prefix-list string in | out ] [ remote-as as-number ] [ remove-private-as ] [ route-map in | out map-
name ] [ route-reflector-client ] [ send-community ] [ shutdown [ generate-rib-out ]] [ soft-reconfiguration inbound ] [ timers keep-alive
num hold-time num ] [ unsuppress-map map-name ] [ update-source ip-addr | ethernet unit / slot / portnum | loopback num | ve num ]
[ weight num ] [ send-label ]}
The ip-addr and peer-group-name parameters indicate whether you are configuring an individual neighbor or a peer group. If you
specify a neighbor IP address, you are configuring that individual neighbor. If you specify a peer group name, you are configuring a peer
group.
activate allows exchange of routes in the current family mode.
advertisement-interval seconds configures an interval in seconds over which the specified neighbor or peer group will hold all route
updates before sending them. At the expiration of the timer, the routes are sent as a batch. The default value for this parameter is zero.
Acceptable values are 0 to 3600 seconds.
NOTE
The device applies the advertisement interval only under certain conditions. The device does not apply the advertisement
interval when sending initial updates to a BGP4 neighbor. As a result, the device sends the updates one immediately after
another, without waiting for the advertisement interval.
allowas-in num disables the AS_PATH check function for routes learned from a specified location. BGP4 usually rejects routes that
contain an AS number within an AS_PATH attribute to prevent routing loops.
capability as4 [ enable | disable ] enables the capability of processing AS4s. The optional keywords enable and disable specify whether
the feature should be changed from its current state. For example, if this neighbor belongs to a peer group that is enabled for AS4s but
you want to disable it on the current interface, use the command and include the
disable keyword.
Basic configuration tasks required for BGP4
Brocade FastIron Layer 3 Routing Configuration Guide
53-1003903-04 289