398
NOTE:
After you configure an IPv6 BGP VPN instance, the IPv6 BGP route exchange for the IPv6 VPN
instance is the same with the normal IPv6 BGP VPN route exchange. For more information about
IPv6 BGP, see
Layer 3—IP Routing Configuration Guide
.
2.
Configure the VPN site:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter IPv6 address family
view.
ipv6-family
N/A
4.
Configure the MCE as the
EBGP peer.
peer
ipv6-address
as-number
as-number
N/A
5.
Redistribute the IGP routes
of the VPN.
import-route
protocol
[
process-id
[
med
med-value
|
route-policy
route-policy-name
]
* ]
Optional.
By default, no route redistribution
is configured.
A VPN site must advertise the
IPv6 VPN network addresses it
can reach to the connected MCE.
Configuring routing between an MCE and a PE
MCE-PE routing configuration includes these tasks:
•
Bind the MCE-PE interfaces to IPv6 VPN instances
•
Perform routing configurations
•
Redistribute IPv6 VPN routes into the routing protocol running between the MCE and the PE.
Perform the following configuration tasks on the MCE. Configurations on the PE are similar to those
on the PE in common IPv6 MPLS L3VPN network solutions. For more information, see "
"
Configuring IPv6 static routing between an MCE and a PE
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
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
]
User either
command as
needed.
Configuring RIPng between an MCE and a PE