Brocade Communications Systems FastIron SX 800 Configuration Manual page 412

Filtering
Syntax: [no] match ip route-source ACL | prefix-list name
The acl and prefix-list name parameters specify the name or ID of an IP ACL, or an IP prefix list.
Matching on routes containing a specific set of communities
The device can match routes based on the presence of a community name or number in a route. To match based on a set of
communities, configure a community ACL that lists the communities, then compare routes against the ACL.
device(config)# ip community-list standard std_1 permit 12:34 no-export
device(config)# route-map bgp2 permit 1
device(config-routemap bgp2)# match community std_1 exact-match
The first command configures a community ACL that contains community number 12:34 and community name no-export. The
remaining commands configure a route map that matches the community attributes field in BGP4 routes against the set of communities
in the ACL. A route matches the route map only if the route contains all the communities in the ACL and no other communities.
Syntax: [no] match community ACL exact-match
The ACL parameter specifies the name of a community list ACL. You can specify up to five ACLs. Separate the ACL names or IDs with
spaces.
Here is another example.
device(config)# ip community-list standard std_2 permit 23:45 56:78
device(config)# route-map bgp3 permit 1
device(config-routemap bgp3)# match community std_1 std_2 exact-match
These commands configure an additional community ACL, std_2, that contains community numbers 23:45 and 57:68. Route map
bgp3 compares each BGP4 route against the sets of communities in ACLs std_1 and std_2. A BGP4 route that contains either but not
both sets of communities matches the route map. For example, a route containing communities 23:45 and 57:68 matches. However, a
route containing communities 23:45, 57:68 and 12:34, or communities 23:45, 57:68, 12:34, and no-export does not match. To
match, the route communities must be the same as those in exactly one of the community ACLs used by the match community
statement.
Matching based on BGP4 static network
Thematch option has been added to the route-map command that allows you to match on a BGP4 static network. In the following
example, the route-map is configured to match on the BGP4 static network. The device is then configured to advertise to the core BGP4
peer (IP address 192.168.6.0) only the BGP4 static routes and nothing else.
device(config)# route-map policygroup3 permit 10
device(config-routemap policygroup3)# match protocol bgp static-network
device(config-routemap policygroup3)# set local-preference 150
device(config-routemap policygroup3)# set community no-export
device(config-routemap policygroup3)# exit
device(config)# router bgp
device(config-bgp)# neighbor 192.168.6.0 route-map out policymap3
Syntax: [no] match protocol bgp [ external | internal | static-network ]
The match protocol bgp external option will match the eBGP routes.
The match protocol bgp internal option will match the iBGP routes.
The match protocol bgp static-network option will match the static-network BGP4 route, applicable at BGP4 outbound policy only.
412
FastIron Ethernet Switch Layer 3 Routing
53-1003627-04