347
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure an IPv6
static route for an IPv6
VPN instance.
ipv6 route-static
vpn-instance
s-vpn-instance-name
ipv6-address prefix-length
{
interface-type interface-number
[
next-hop-address
] |
nexthop-address
[
public
] |
vpn-instance
d-vpn-instance-name
nexthop-address
} [
permanent
] [
preference
preference-value
] [
tag
tag-value
] [
description
description-text
]
By default, no IPv6
static route is
configured.
Perform this
configuration on the
MCE. On a VPN site,
configure normal IPv6
static routes.
3.
(Optional.) Configure
the default preference
for IPv6 static routes.
ipv6 route-static default-preference
default-preference-value
The default
preference for IPv6
static routes is 60.
Configuring RIPng between an MCE and a 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 a MCE, you allow routes of different
VPNs to be exchanged between the 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 an MCE and a 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
MCE. On a VPN site, configure
normal RIPng.
3.
Redistribute remote site
routes advertised by the PE.
import-route
protocol
[
process-id
] [
allow-ibgp
]
[
allow-direct
|
cost
cost
|
route-policy
route-policy-name
]
*
By default, no routes are
redistributed into RIPng.
4.
(Optional.) Configure the
default cost value for the
redistributed routes.
default cost
value
The default value is 0.
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
RIPng is disabled by default.
Configuring OSPFv3 between an MCE and a 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 a MCE, you allow routes of
different IPv6 VPNs to be exchanged between the MCE and the sites through different OSPFv3
processes, ensuring the separation and security of IPv6 VPN routes.
For more information about OSPFv3, see
Layer 3—IP Routing Configuration Guide
.
Содержание HPE FlexNetwork MSR Router Series
Страница 10: ...viii Index 540 ...
