Match Metric - Enterasys X-Pedition XSR CLI Cli Reference Manual

Route Map Commands
Mode
Route‐map configuration:
Default
No match based on community list
Example
The following example configures the match community value in the context of configuring a
route map named 1 and community list 77 on XSRA and XSRB:
Router A configuration:
XSRA(config)#route-map 1 permit 1
XSRA(config-route-map)#match community 77
XSRA(config-route-map)#set local-preference 500
XSRA(config-route-map)#exit
XSRA(config)#ip community-list 77 permit 300:22
Router B configuration:
XSRB(config)#route-map 1 permit 1
XSRB(config-route-map)#match community 77
XSRB(config-route-map)#set local-preference 200
XSRB(config-route-map)#exit
XSRB(config)#ip community-list 77 permit 300:22
XSRA and XSRB are border routers within the same AS. The community is identified by name
300:22. The numeric format aa:nn, where aa and nn represent two‐byte numbers, is one of the
allowable formats for community names. BGP updates matching community name 300:22 are
assigned a higher local preference on XSRA (500) than on XSRB (200). This makes XSRA the
preferable exit point from this AS for the networks that have been grouped under the community
name 300:22. Use the

match metric

This command matches the MED attribute in a BGP routing update message. A route must match
at least one match statement of a
statements, the route is not advertised on outbound route maps and is not accepted on inbound
route maps.
Syntax
match metric metric-value
metric-value
Syntax of the "no" Form
The no form of this command removes the match metric value:
no match metric metric-value
6-112 Configuring the Border Gateway Protocol
XSRA(config-route-map)#
set community
command to assign community names.
route-map
MED value to match, ranging from 0 to 2147483647.
command. If a route does not match any match