Defining neighbor distribute lists, Defining route maps – Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) User Manual
Page 109
Multi-Service IronWare Routing Configuration Guide
81
53-1003033-02
Filtering
The network-addr/mask-bits parameters specify the network number and the number of bits in the
network mask.
You can specify a range of prefix length for prefixes that are more specific than
network-addr/mask-bits.
The prefix-list matches only on this network unless you use the ge ge-value or le le-value
parameters.
•
If you specify only ge ge-value, the mask-length range is from ge-value to 32.
•
If you specify only le le-value, the mask-length range is from length to le-value.
The ge-value or le-value you specify must meet the following condition:
length < ge-value <= le-value <= 32
If you do not specify ge ge-value or le le-value, the prefix list matches only on the exact network
prefix you specified with the network-addr/mask-bits parameter.
For the syntax of the neighbor command shown in this example, refer to
“Configuring a BGP4 peer group”
Defining neighbor distribute lists
A neighbor distribute list is a list of BGP4 address filters or ACLs that filter the traffic to or from a
neighbor.
To configure a distribute list that uses ACL 1, enter a command such as the following.
Brocade(config-bgp)# neighbor 10.10.10.1 distribute-list 1 in
This command configures the device to use ACL 1 to select the routes that the device will accept
from neighbor 10.10.10.1.
Syntax: [no] neighbor ip-addr distribute-list name-or-num in | out
The ip-addr parameter specifies the neighbor.
The name-or-num parameter specifies the name or number of a standard, extended, or named
ACL.
The in | out parameters specify whether the distribute list applies to inbound or outbound routes:
•
in – controls the routes the device will accept from the neighbor.
•
out – controls the routes sent to the neighbor.
Defining route maps
A route map is a named set of match conditions and parameter settings that the device can use to
modify route attributes and to control redistribution of the routes into other protocols. A route map
consists of a sequence of instances. If you think of a route map as a table, an instance is a row in
that table. The device evaluates a route according to route map instances in ascending numerical
order. The route is first compared against instance 1, then against instance 2, and so on. When a
match is found, the device stops evaluating the route.
Route maps can contain match clauses and set statements. Each route map contains a permit or
deny action for routes that match the match clauses:
•
If the route map contains a permit action, a route that matches a match statement is
permitted; otherwise, the route is denied.