3Com 4800G Series, Configuration Manual

Page: 493 / 1246

Configuring a Routing Policy 493
Creating a Routing
Policy
Follow these steps to create a routing policy:
n
■
If a node has the permit keyword specified, routing information meeting the
node’s conditions will be handled using the apply clauses of this node, without
needing to match against the next node. If routing information does not meet
the node’s conditions, it will go to the next node for a match.
■
If a node is specified as deny , the apply clauses of the node will not be
executed. When routing information matches all if-match clauses of the node,
it can neither pass the node, nor go to the next node. If route information
cannot match any
if-match clause of the node, it will go to the next node for a
match.
■
When a routing policy is defined with more than one node, at least one node
should be configured with the
permit keyword. If the routing policy is used to
filter routing information, routing information that does not meet any node’s
conditions cannot pass the routing policy. If all nodes of the routing policy are
set using the
deny keyword, no routing information can pass it.
Defining if-match
Clauses for the Routing
Policy
Follow these steps to define if-match clauses for a route-policy:
To do… Use the command… Remarks
Enter system view system-view -
Create a routing policy and
enter its view route-policy route-policy-name { permit |
deny } node node-number
Required
To do… Use the command… Remarks
Enter system view system-view -
Enter routing policy view route-policy route-policy-name
{ permit | deny } node
node-number
Required
Match IPv6 routes having
the next hop or source
specified in the ACL or IP
prefix list if-match ipv6 { address |
next-hop | route-source } { acl
acl-number | prefix-list
ipv6-prefix-name }
Optional
Not configured by default
Match IPv6 BGP routes
having AS path attributes
specified in the AS path list
(s) if-match as-path
as-path-number &<1-16>
Optional
Not configured by default
Match IPv6 BGP routes
having community attributes
in the specified community
list(s) if-match community
{ basic-community-list-number
[ whole-match ] |
adv-community-list-number }&<
1-16>
Optional
Not configured by default
Match routes having the
specified cost if-match cost value Optional
Not configured by default
Match BGP routes having
extended attributes
contained in the extended
community list(s) if-match extcommunity
ext-comm-list-number &<1-16>
Optional
Not configured by default
Match routes having
specified outbound
interface(s) if-match interface
{ interface-type
interface-number }&<1-16>
Optional
Not configured by default