Enabling System Policy Routing - 3Com MSR 50 Series Configuration Manual

n
Enabling System Policy
Routing
To do... Use the command...
Enter system view system-view
Create a policy or policy-based-route policy-name
policy node and enter [ deny | permit ] node node-number
policy view
Define a packet if-match packet-length min-len
length match rule max-len
Define an ACL match if-match acl acl-number
rule
Set the packet apply ip-precedence { type | value}
precedence
Set outgoing apply output-interface
interfaces interface-type interface-number
[ track track-entry-number ]
[ interface-type interface-number
[ track track-entry-number ] ]
Set next hops apply ip-address next-hop
ip-address [ track track-entry-number ]
[ ip-address [ track
track-entry-number ] ]
Set default outgoing apply default output-interface
interfaces interface-type interface-number
[ track track-entry-number ]
[ interface-type interface-number
[ track track-entry-number ] ]
Set default next hops apply ip-address default next-hop
ip-address [ track track-entry-number ]
[ ip-address [ track
track-entry-number ] ]
You can use the apply output-interface command to configure two outgoing
interfaces or the apply ip-address next-hop command two next hops. If you
want to modify either of the two outgoing interfaces or next hops, you can
execute the apply output-interface interface-type interface-number command
or apply ip-address next-hop ip-address command to overwrite the earlier one.
If you want to modify the two outgoing interfaces or next hops, you can directly
specify two interfaces or next hops before executing the apply output-interface
or apply ip-address next-hop command.
Policy routing includes system policy routing and interface policy routing. In most
cases, the interface policy routing is used for the consideration of ordinary
forwarding and security.
Configuring IP Unicast Policy Routing
Remarks
--
Required
Optional
Optional
Optional
Optional
Two interfaces at most can be
specified to send matched IP
packets. These two interfaces
are simultaneously active to
achieve load sharing.
For non-P2P interfaces
(broadcast and NBMA
interfaces) such as Ethernet
interface, multiple next hops
are possible, and thus packets
may not be forwarded
successfully.
Optional
Two next hops at most can be
specified. These two next
hops are simultaneously active
to achieve load sharing.
Optional
Two default outgoing
interfaces at most can be
specified. These two
interfaces are simultaneously
active to achieve load sharing.
Optional
Two default next hops at
most can be specified. These
two next hops are
simultaneously active to
achieve load sharing.
641