H3C Technologies H3C SecPath F1000-E - Manual (Page 575)

550
Configuring PBR at the CLI
Defining a policy
Step Command Remarks
1. Enter system view. system-view N/A
2. Create a policy or
policy node and enter
PBR policy node view.
policy-based-route policy-name
[ deny | permit ] node node-number
N/A
3. Define a packet length
match criterion.
if-match packet-length min-len
max-len
Optional.
4. Define an ACL match
criterion.
if-match acl acl-number Optional.
5. Set VPN instances.
apply access-vpn vpn-instance
vpn-instance-name&<1-6>
Optional.
6. Set an IP precedence. apply ip-precedence value Optional.
7. Set outgoing
interfaces.
apply output-interface interface-type
interface-number [ track
track-entry-number ] [ interface-type
interface-number [ track
track-entry-number ] ]
Optional.
Two interfaces at most can be specified
to send matching IP packets. These two
interfaces are simultaneously active to
achieve load sharing.
For a non-P2P outgoing interface
(broadcast and NBMA interfaces) such
as Ethernet interface, multiple next
hops are possible, and thus packets
may not be forwarded successfully.
8. Set next hops.
apply ip-address next-hop ip-address
[ direct ] [ track track-entry-number ]
[ ip-address [ direct ] [ track
track-entry-number ] ]
Optional.
Two next hops at most can be
specified. These two next hops are
simultaneously active to achieve load
sharing.
9. Set default outgoing
interfaces.
apply default output-interface
interface-type interface-number [ track
track-entry-number ] [ interface-type
interface-number [ track
track-entry-number ] ]
Optional.
Two default outgoing interfaces at most
can be specified. These two interfaces
are simultaneously active to achieve
load sharing.
10. Set default next hops.
apply ip-address default next-hop
ip-address [ track track-entry-number ]
[ ip-address [ track
track-entry-number ] ]
Optional.
Two default next hops at most can be
specified. These two next hops are
simultaneously active to achieve load
sharing.