Configuring Track-Policy Routing Collaboration - 3Com MSR 50 Series Configuration Manual

3com msr 30-16: software guide
Hide thumbs Also See for MSR 50 Series:
Table of Contents

Advertisement

2210
C
127: T
HAPTER
RACK
Configuring Track-Policy
Routing Collaboration
C
ONFIGURATION
If a static route needs route recursion, the associated Track object must monitor
the next hop of the recursive route instead of that of the static route;
otherwise, a valid route may be considered invalid.
For details of static route configuration, refer to
Routing" on page
Associated with a Track object, IP unicast policy routing can be used more flexibly,
and its dynamic awareness of the networking environment is enhanced.
You can associate the policy routing with a Track object when configuring the
output interface, the default output interface, the next hop, and the default next
hop, so as to determine the availability of the policy dynamically. After you
configure a Track object association in an apply clause, when an event occurs:
If the status of the Track object is positive, the configuration is valid and can
be used to instruct forwarding.
If the status of the Track object is negative or invalid, the configuration is
invalid and is ignored during forwarding.
Configuration prerequisites
Before configuring Track-Policy Routing, you need to create a policy or a policy
node and configure the match rules as well.
Configuration procedure
Follow these steps to configure the Track-Policy Routing collaboration:
To do...
Enter system view
Create a policy or policy node
and enter the policy view
Set the packet length match
rule
Match an ACL
Specify the packet output
interface and associate it with
a Track object
Specify the next hop of
packets and associate it with
a Track object
Specify the default output
interface of packets and
associate it with a Track
object
Specify the default next hop
of packets and associate it
with a Track object
817.
Use the command...
system-view
policy-based-route policy-name { deny |
permit } node node-number
if-match packet-length min-len max-len Use either
if-match acl acl-number
apply output-interface interface-type
interface-number [ track
track-entry-number ] [ interface-type
interface-number [ track
track-entry-number ] ]
apply ip-address next-hop ip-address
[ track track-entry-number ] [ ip-address
[ track track-entry-number ] ]
apply default output-interface
interface-type interface-number [ track
track-entry-number ] [ interface-type
interface-number [ track
track-entry-number ] ]
apply ip-address default next-hop
ip-address [ track track-entry-number]
[ ip-address [ track track-entry-number] ]
"Static Routing and Dynamic
Remarks
-
Required
command.
Use at least one of
the four
commands.

Hide quick links:

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents