425
Configuring actions for an IPv6 node
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter IPv6 policy
node view.
ipv6 policy-based-route
policy-name
[
deny
|
permit
]
node
node-number
N/A
3.
Set an IP
precedence.
apply precedence
{
type
|
value
}
By default, no IP precedence is
specified.
4.
Set VPN
instances.
apply access-vpn vpn-instance
vpn-instance-name
&<1-
n
>
By default, no VPN instance is
specified.
You can specify up to six VPN
instances for a node. The matching
packets are forwarded according to
the forwarding table of the first
available VPN instance.
5.
Set next hops for
permitted IPv6
packets.
apply next-hop
[
vpn-instance
vpn-instance-name
|
inbound-vpn
]
{
ipv6-address
[
direct
] [
track
track-entry-number
] }&<1-
n
>
By default, no next hop is specified.
You can specify multiple next hops for
backup or load sharing by executing
this command once or multiple times.
You can specify up to 16 next hops
for a node.
6.
Enable load
sharing among
multiple next
hops.
apply loadshare next-hop
By default, the next hops operate in
primary/backup mode.
7.
Set output
interfaces.
apply output-interface
{
interface-type
interface-number
[
track
track-entry-number
] }&<1-
n
>
By default, no output interface is
specified.
You can specify multiple output
interfaces for backup or load sharing
by executing this command once or
multiple times.
You can specify up to 16 output
interfaces for a node.
8.
Enable load
sharing among
multiple output
interfaces.
apply loadshare output-interface
By default, the output interfaces
operate in primary/backup mode.
9.
Set default next
hops.
apply default-next-hop
[
vpn-instance
vpn-instance-name
|
inbound-vpn
]
{
ipv6-address
[
direct
] [
track
track-entry-number
] }&<1-
n
>
By default, no default next hop is
specified.
You can specify multiple default next
hops for backup or load sharing by
executing this command once or
multiple times.
You can specify up to 16 default next
hops for a node.
