Configuring Actions For A Node - HP MSR Series Configuration Manual

NOTE:
An ACL match criterion uses the specified ACL to match packets if the match mode is configured as permit. If the
specified ACL does not exist or the match mode is configured as deny, no packet can match the criterion.

Configuring actions for a node

Step
1. Enter system view.
2. Enter policy node view.
3. Set the DF bit in the IP header
to 0, which means the packet
can be fragmented.
4. Set VPN instances.
5. Set an IP precedence.
6. Set output interfaces.
7. Set the output interface and
next hop (the next hop
address is the gateway
address learned through
DHCP).
8. Set next hops.
9. Set default output interfaces.
10. Set default next hops.
Command
system-view
policy-based-route policy-name
[ deny | permit ] node
node-number
apply ip-df zero
apply access-vpn vpn-instance
vpn-instance-name&<1-6>
apply ip-precedence value
apply output-interface
interface-type interface-number
[ track track-entry-number ]
[ interface-type interface-number
[ track track-entry-number ] ]
apply output-interface
interface-type interface-number
ip-address next-hop dhcpc
apply ip-address next-hop
[ vpn-instance vpn-instance-name ]
ip-address [ direct ] [ track
track-entry-number ] [ ip-address
[ direct ] [ 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
[ vpn-instance vpn-instance-name ]
ip-address [ track
track-entry-number ] [ ip-address
[ track track-entry-number ] ]
263
Remarks
N/A
N/A
Optional.
Optional.
Optional.
Optional.
You can specify up to two output
interfaces to achieve load sharing.
Optional.
Optional.
You can specify up to two next
hops to achieve load sharing.
Optional.
You can specify up to two default
output interfaces to achieve load
sharing.
Optional.
You can specify up to two default
next hops to achieve load sharing.