H3C Technologies H3C S12500 Series Switches - Manual (Page 423)

407
Step Command Remarks
2. Define a community list.
• Define a basic community list:
ip community-list { basic-comm-list-num |
basic comm-list-name } { deny | permit }
[ community-number-list ] [ internet |
no-advertise | no-export |
no-export-subconfed ] *
• Define an advanced community list:
ip community-list { adv-comm-list-num |
advanced comm-list-name } { deny |
permit } regular-expression
Use either method.
Not defined by
default.
Defining an extended community list
You can define multiple items for an extended community list that is identified by number. During
matching, the relationship between items is logic OR. If routing information matches one of these items,
it passes the extended community list.
To define an extended community list:
Step Command Remarks
1. Enter system view. system-view N/A
2. Define an extended
community list.
ip extcommunity-list ext-comm-list-number { deny |
permit } { rt route-target | soo
site-of-origin }&<1-16>
Not defined by default.
Configuring a routing policy
A routing policy is used to filter routing information and modify attributes of matching routing information.
The match criteria of a routing policy can be configured by referencing filters mentioned in the previous
sections.
A routing policy can comprise multiple nodes, and each routing policy node can contain the following
clauses:
• if-match clauses—Define the criteria that routing information must match. The matching objects are
some attributes of routing information.
• apply clauses—Specify the actions to be taken on routing information that has matched the criteria,
such as route attribute modification.
• continue clauses—Specify the next routing policy node to be matched. With this clause configured,
when a route matches the current routing policy node, it continues to match against the specified
next node in the same routing policy.
Configuration prerequisites
Before you configure this task, you must configure the following:
• Filters