H3C Technologies H3C SecPath F1000-E - Manual (Page 944)

919
Routing policy configuration task list
Task
Defining filters
Defining an IP-prefix list
Defining an AS path list
Defining a community list
Configuring a routing policy
Creating a routing policy
Defining if-match clauses
Defining apply clauses
Defining a continue clause
Defining filters
Configuration prerequisites
Before configuring this task, you must determine IP-prefix list name, matching address range, and
extcommunity list sequence number.
Defining an IP-prefix list
Defining an IPv4 prefix list
Identified by name, an IPv4 prefix list can comprise multiple items. Each item specifies a prefix range to
match and is identified by an index number.
An item with a smaller index number is matched first. If one item is matched, the IP prefix list is passed,
and the routing information will not go to the next item.
To define an IPv4 prefix list:
Step Command Remarks
1. Enter system view. system-view N/A
2. Define an IPv4
prefix list.
ip ip-prefix ip-prefix-name [ index index-number ]
{ deny | permit } ip-address mask-length
[ greater-equal min-mask-length ] [ less-equal
max-mask-length ]
Not defined by default.
NOTE:
If all the items are set to the deny mode, no routes can pass the IPv4 prefix list. You need to define the
permit 0.0.0.0 0 less-equal 32 item following multiple deny items to allow other IPv4 routing information
to pass.
For example, the following configuration filters routes 10.1.0.0/16, 10.2.0.0/16 and 10.3.0.0/16, but
allows other routes to pass.