Configuring A Community List - HP ProCurve Secure Router 7203 dl Advanced Management And Configuration Manual

IP Routing—Configuring RIP, OSPF, BGP, and PBR
Configuring BGP
13-88
For example, you can create an outbound route map that sets one route's
multi-exit discriminator metric and places another route in a community. You
simply create two route map entries with the same name:
ProCurve(config)# route-map ISP1out 10
ProCurve(config-route-map)# exit
ProCurve(config)# route-map ISP1out 20
You will learn how to define policies in route map entries in following sections.

Configuring a Community List

You can use a community list to:
select the communities to which the router will apply a specific policy—
See "Filtering Advertised Routes According to Community" on page 13-91
and "Applying Policies to Inbound Routes" on page 13-102.
define the communities that the BGP interface will delete from routes—
"Deleting Communities from a Route" on page 13-103.
To create a community list, move to the global configuration mode context
and enter:
Syntax: ip community-list <listname>
You will then move to the community list configuration mode context. For
example:
ProCurve(config)# ip community-list customers
ProCurve(config-comm-list)#
From this mode context, you can select one or more well-defined communi-
ties. You can also enter a value for a privately defined community. To add a
community to the list, enter this command:
Syntax: permit [internet | local-as | no-advertise | no-export | <1-42949672957>]
You can permit multiple communities by stringing several keywords in the
same command. For example:
ProCurve(config-comm-list)# permit local-as no-export
You can also specifically deny a community from a list. For example, in order
to prohibit the BGP interface from advertising routes belonging to a certain
community, you should configure a community list that denies that commu-
nity. (You would then match a route-map entry to the community list and apply
the map to a BGP neighbor.)