3Com 4500 PWR 26-Port Configuration Manual page 303

Hide thumbs Also See for 4500 PWR 26-Port:
Table of Contents

Advertisement

To do...
Enter system view
Enter the route-policy
view
Define a rule to match the
IP address of routing
information
Define a rule to match the
cost of routes
Define a rule to match the
next-hop interface of
routing information
Define a rule to match the
next-hop address of
routing information
Define a rule to match the
tag field of routing
information
Apply a cost to routes
satisfying matching rules
Define an action to set the
tag field of routing
information
A route policy comprises multiple nodes. There is an OR relationship between the nodes in a route
policy. As a result, the system examines the nodes in sequence, and once the route matches a
node in the route policy, it will pass the matching test of the route policy without entering the test of
the next node.
During the matching, there is an AND relationship between the if-match clauses for a route policy
node. That is, a matching test against a node is successful only when all the matching conditions
specified by the if-match clauses in the node are satisfied.
If no if-match clauses are specified, all the routes will filter through the node.
A node can comprise no if-match clause or multiple if-match clauses.
Each node comprises a set of if-match and apply clauses. if-match clauses define matching rules.
apply clauses specify the actions performed after a matching test against the node is successful,
and the actions can be the attribute settings of routing information.
Use the command...
system-view
route-policy
route-policy-name { permit
| deny } node node-number
if-match { acl acl-number |
ip-prefix ip-prefix-name }
if-match cost value
if-match interface
interface-type
interface-number
if-match ip next-hop { acl
acl-number | ip-prefix
ip-prefix-name }
if-match tag value
apply cost value
apply tag value
24-4
Remarks
Required
Optional
By default, no matching is performed on
the address of routing information.
Optional
By default, no matching is performed
against the cost of routes.
Optional
By default, no matching is performed on
the next-hop interface of routing
information.
Optional
By default, no matching is performed on
the next-hop address of routing
information.
Optional
By default, no matching is performed on
the tag field of routing information.
Optional
By default, no cost is applied to routes
satisfying matching rules.
Optional
By default, no action is defined to set the
tag field of routing information.

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

4500 26-port4500 50-port

Table of Contents