Configuring An As Path List - HP 7102dl - ProCurve Secure Router Configuration Manual

IP Routing—Configuring RIP, OSPF, BGP, and PBR
Configuring BGP
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.)
To deny a community from the list, enter this command from the community
list configuration mode context:
Syntax: deny [internet | local-as | no-advertise | no-export | <1-42949672957>]
Again, you can enter multiple keywords in the same command.

Configuring an AS Path List

You can use an AS path list to select routes for a policy according to values in
the routes' AS fields.
You create the AS path list from the global configuration mode context. Enter
this command:
Syntax: ip as-path-list <listname>
You then move to the AS path-list configuration mode context. For example:
ProCurve(config)# ip as-path-list CustomerA
ProCurve(config-as-path-list)#
You can then enter this command to select or deny a specific AS path:
Syntax: [permit | deny] <string of AS numbers>
For example:
ProCurve(config-as-path-list)# permit 1 2
If you want to filter traffic only according to AS path, and if you do not need
to apply attributes to filtered routes, then you can apply the AS path list
directly to a neighbor. Move to the BGP neighbor configuration mode context
and enter:
Syntax: as-path-list <listname> [in | out]
15-91