40
Step Command
Remarks
2.
Configure an IPv6 static route
for an IPv6 VPN instance.
•
ipv6 route-static
ipv6-address prefix-length
{
interface-type
interface-number
[
next-hop-address
] |
next-hop-address
|
vpn-instance
d-vpn-instance-name
nexthop-address
} [
preference
preference-value
]
•
ipv6 route-static
vpn-instance
s-vpn-instance-name
&<1-6>
ipv6-address
prefix-length
{
interface-type
interface-number
[
next-hop-address
] |
nexthop-address
[
public
] |
vpn-instance
d-vpn-instance-name nexthop-address
}
[
preference
preference-value
]
Use either command.
Perform this
configuration on the
IPv6 MCE. On a VPN
site, configure normal
IPv6 static routes.
Configuring RIPng between IPv6 MCE and VPN site
A RIPng process belongs to the public network or a single IPv6 VPN instance. If you create a RIPng
process without binding it to an IPv6 VPN instance, the process belongs to the public network. By
configuring RIPng process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of different
VPNs to be exchanged between the IPv6 MCE and the sites through different RIPng processes, ensuring
the separation and security of IPv6 VPN routes.
For more information about RIPng, see
Layer 3—IP Routing Configuration Guide
.
To configure RIPng between IPv6 MCE and VPN site:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a RIPng process for a
VPN instance and enter RIPng
view.
ripng
[
process-id
]
vpn-instance
vpn-instance-name
Perform this configuration on the
IPv6 MCE. On a VPN site,
configure normal RIPng.
3.
Redistribute remote site routes
advertised by the PE.
import-route
protocol
[
process-id
]
[
allow-ibgp
] [
cost
cost
|
route-policy
route-policy-name
] *
By default, no route of any other
routing protocol is redistributed
into RIPng.
4.
Configure the default cost
value for the redistributed
routes.
default cost
value
Optional.
0 by default.
5.
Return to system view.
quit
N/A
6.
Enter interface view.
interface
interface-type
interface-number
N/A
7.
Enable RIPng on the interface.
ripng
process-id
enable
Disabled by default.
Configuring OSPFv3 between IPv6 MCE and VPN site
An OSPFv3 process belongs to the public network or a single IPv6 VPN instance. If you create an
OSPFv3 process without binding it to an IPv6 VPN instance, the process belongs to the public network.
By configuring OSPFv3 process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of
different IPv6 VPNs to be exchanged between the IPv6 MCE and the sites through different OSPFv3
processes, ensuring the separation and security of IPv6 VPN routes.
