Defining an extended community list, Configuring a route policy, Prerequisites – H3C Technologies H3C S7500E Series Switches User Manual
Page 363: Creating a route policy
12-6
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…
Use the command…
Remarks
Enter system view
system-view
—
Define an extended
community list
ip extcommunity-list ext-comm-list-number { deny
| permit } { rt route-target }&<1-16>
Required
Not defined by default
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:
z
if-match clauses: Define the match criteria that routing information must satisfy. The matching
objects are some attributes of routing information.
z
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:
z
Filters
z
Routing protocols
You also need to decide on:
z
Name of the route policy, and node numbers
z
Match criteria
z
Attributes to be modified
Creating a Route Policy
Follow these steps to create a route policy:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a route policy, specify a
node for it and enter route policy
node view
route-policy route-policy-name { deny | permit }
node node-number
Required