F3215-HP Load Balancing Module Network Management Configuration Guide-6PW101
443
For more information about community list, see "Configuring BGP."
Extended community list
An extended community list matches the extended community attribute (Route-Target for VPN and Source
of Origin) of BGP routing information.
Routing policy
A routing policy can comprise multiple nodes, which are in a logical OR relationship. A node with a
smaller number is matched first. A route that matches one node matches the routing policy.
A node can comprise a set of if-match, apply, and continue clauses.
• The if-match clauses configure the match criteria that match the attributes of routing information. The
if-match clauses are in a logical AND relationship. A route must match all the if-match clauses to
match the node.
• The apply clauses specify the actions to be taken on permitted routes, such as modifying a route
attribute.
• The continue clause specifies the next node. A route that matches the current node must match the
specified next node in the same routing policy. The continue clause combines the if-match and
apply clauses of the two nodes to improve flexibility of the routing policy.
Follow these guidelines to configure if-match, apply, and continue clauses:
• If you only want to filter routes, do not configure apply clauses.
• If you do not configure any if-match clauses for a permit-mode node, the node will permit all routes.
• Configure a permit-mode node containing no if-match or apply clauses behind multiple deny-mode
nodes to allow unmatched routes to pass.
Configuring filters
Configuration prerequisites
Determine the IP-prefix list name, matching address range, and community list number.
Configuring an IP prefix list
Configuring an IPv4 prefix list
Ste
p
Command
Remarks
1. Enter system view.
system-view N/A
2. Configure 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 configured by
default.
If all the items are set to deny mode, no routes can pass the IPv4 prefix list. Configure 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.