![H3C S5500-EI series Скачать руководство пользователя страница 442](http://html2.mh-extra.com/html/h3c/s5500-ei-series/s5500-ei-series_configuration-manual_3726960442.webp)
425
To do…
Use the command…
Remarks
Configure the default precedence
for IPv6 static routes
ipv6 route-static default-preference
default-preference-value
Optional
60 by default
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.
Follow these steps to configure RIPng between IPv6 MCE and VPN site:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a RIPng process for a VPN
instance and enter RIPng view
ripng
[
process-id
]
vpn-instance
vpn-instance-name
Required
Perform this configuration on the
IPv6 MCE. On a VPN site,
configure normal RIPng.
Redistribute remote site routes
advertised by the PE
import-route
protocol
[
process-id
]
[
allow-ibgp
] [
cost
cost
|
route-policy
route-policy-name
] *
Required
By default, no route of any other
routing protocol is redistributed
into RIPng.
Configure the default cost value for
the redistributed routes
default cost
value
Optional
0 by default
Return to system view
quit
—
Enter interface view
interface
interface-type
interface-number
—
Enable RIPng on the interface
ripng
process-id
enable
Required
Disabled by default
NOTE:
For more information about RIPng, see
Layer 3—IP Routing Configuration Guide.
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.
Follow these steps to configure OSPFv3 between IPv6 MCE and VPN site:
To do…
Use the command…
Remarks
Enter system view
system-view
—