Matching based on as-path acl, Matching based on community acl – Brocade BigIron RX Series Configuration Guide User Manual

Page 957

Advertising
background image

BigIron RX Series Configuration Guide

879

53-1002484-04

Filtering

27

NOTE

The filters must already be configured.

The community <num> parameter specifies a community ACL.

NOTE

The ACL must already be configured.

The community <acl> exact-match parameter matches a route if (and only if) the route's
community attributes field contains the same community numbers specified in the match
statement.

The ip address | next-hop <acl-num> | prefix-list <string> parameter specifies an ACL or IP prefix
list. Use this parameter to match based on the destination network or next-hop gateway. To
configure an IP ACL for use with this command, use the ip access-list command. Refer to

Chapter

22, “Access Control List”

. To configure an IP prefix list, use the ip prefix-list command. Refer to

“Defining and applying IP prefix lists”

on page 875.

The ip route-source <acl> | prefix <name> parameter matches based on the source of a route (the
IP address of the neighbor from which the device learned the route).

The metric <num> parameter compares the route’s MED (metric) to the specified value.

The next-hop <address-filter-list> parameter compares the IP address of the route’s next hop to the
specified IP address filters. The filters must already be configured.

The route-type internal | external-type1 | external-type2 parameter applies only to OSPF routes.
This parameter compares the route’s type to the specified value. The level-1 parameter compares
ISIS routes only with routes within the same area. The level-2 parameter compares ISIS routes only
with routes in different areas, but within a domain. The level-1-2 parameter compares ISIS routes
with routes the same area and in different areas, but within a domain.

The tag <tag-value> parameter compares the route’s tag to the specified tag value.

The following sections are some examples of how to configure route maps that include match
statements that match on ACLs.

Matching based on AS-path ACL

To construct a route map that matches based on AS-path ACL 1, enter the following commands.

BigIron RX(config)# route-map PathMap permit 1

BigIron RX(config-routemap PathMap)# match as-path 1

Syntax: match as-path <num>

The <num> parameter specifies an AS-path ACL and can be a number from 1 – 199. You can
specify up to five AS-path ACLs. To configure an AS-path ACL, use the ip as-path access-list
command. Refer to

“Defining an AS-path ACL”

on page 870.

Matching based on community ACL

To construct a route map that matches based on community ACL 1, enter the following commands.

BigIron RX(config)# ip community-list 1 permit 123:2

BigIron RX(config)# route-map CommMap permit 1

BigIron RX(config-routemap CommMap)# match community 1

Advertising