NOTE
If you congure the Brocade device to use a loopback interface to communicate with a BGP4 neighbor, the peer IP address on
the remote device pointing to your loopback address must be congured.
To add a loopback interface, enter commands such as the following.
device(config-bgp)# exit
device(config)# int loopback 1
device(config-lbif-1)# ip address 10.0.0.1/24
Syntax: [no] interface loopback num
The num value can be from 1 through the maximum number of loopback interfaces supported on the device.
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
dierent 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 conguration by conguring a peer group, then
adding individual neighbors to it. The conguration steps are similar, except you specify a peer group name instead of a
neighbor IP address when conguring 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 congure 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 prexlist [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-rst-as] [lter-list access-list-name [in | out]] [local-
as as-num [no-prepend]] [maxas-limit in [num | disable] [maximum-prex num [threshold] [teardown] [next-hop-self] [password
string] [peer-group group-name] [prex-list string in | out] [remote-as as-number] [remove-private-as] [route-map in | out map-
name] [route-reector-client] [send-community] [shutdown [generate-rib-out]] [soft-reconguration 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 conguring an individual neighbor or a peer group. If you
specify a neighbor IP address, you are conguring that individual neighbor. If you specify a peer group name, you are conguring a peer
group.
activate allows exchange of routes in the current family mode.
advertisement-interval seconds congures an interval in seconds over which the specied 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.
Basic conguration tasks required for BGP4
FastIron Ethernet Switch Layer 3 Routing
53-1003627-04 367