Reference Guide

match as-path
This route map match term matches BGP (Border Gateway Protocol) autonomous system paths against
an AS path access list. If you enter a new match as-path term in a route map statement that already has
a match as-path term, the AS path list numbers in the new term are added to the existing match term,
up to the maximum number of lists in a term. A route is considered a match if it matches any one or
more of the AS path access lists the match term refers to.
Format match as-path as-path-list-number
Mode Route Map Configuration
Parameter Description
as-path-list-
number
An integer from 1 to 500 identifying the AS path access list to use as match criteria.
no match as-path
This command deletes the match as-path term that matches BGP autonomous system paths against an
AS path access list.
Format no match as-path as-path-list-number
Mode Route Map Configuration
match community
To configure a route map to match based on a BGP community list, use the match community
command in Route Map Configuration mode. If the community list returns a permit action, the route is
considered a match. If the match statement refers to a community list that is not configured, no routes
are considered to match the statement.
Format
match community community-list [community-list...] [exact-
match]
Mode Route Map Configuration
Parameter Description
community-list
The name of a standard community list. Up to eight names may be included in a single
match term.
exact-match (Optional) When this option is given, a route is only considered a match if the set of
communities on the route is an exact match for the set of communities in one of the
statements in the community list.
no match community
To delete a match term from a route map, use the no form of this command. The command no match
community list exact-match removes the match statement from the route map. (It does not simply
Routing Commands
ExtremeSwitching 200 Series: Command Reference Guide for version 01 .02.04.0007 536