Defining An Extended Community List; Configuring A Route Policy; Prerequisites - HP 4800G Series Configuration Manual

Follow these steps to define a community list:
To do...
Enter system view
Define a
community
list

Defining an Extended Community List

You can define multiple items for an extended community list that is identified by number. During
matching, the relation between items is logic OR, that is, if routing information matches one of these
items, it passes the extended community list.
Follow these steps to define an extended community list:
To do...
Enter system view
Define an extended
community list

Configuring a Route Policy

A route policy is used to filter routing information, and modify attributes of matching routing information.
The match criteria of a route policy can be configured by referencing filters above mentioned.
A route policy can comprise multiple nodes, and each route policy node contains:
if-match clauses: Define the match criteria that routing information must satisfy. The matching
objects are some attributes of routing information.
apply clauses: Specify the actions to be taken on routing information that has satisfied the match
criteria, such as route attribute modification.

Prerequisites

Before configuring this task, you need to configure:
Filters
Routing protocols
You also need to decide on:
Name of the route policy, and node numbers
Match criteria
Attributes to be modified
system-view
ip community-list basic-comm-list-num
Define a basic { deny | permit } [ community-number-list ]
community list [ internet | no-advertise | no-export |
no-export-subconfed ] *
Define an
ip community-list adv-comm-list-num { deny
advanced
| permit } regular-expression
community list
system-view
ip extcommunity-list ext-comm-list-number
{ deny | permit } { rt route-target }&<1-16>
Use the command...
Use the command...
1-5
Remarks
—
Required to
define either;
Not defined by
default.
Remarks
—
Required
Not defined by default