31
peer
{
group-name
|
ipv6-address
[
prefix-length
]
}
as-number
as-number
4.
Enter BGP IPv6 unicast address family view.
address-family ipv6
[
unicast
]
5.
Enable BGP to exchange IPv6 unicast routes with the peer.
peer
{
group-name
|
ipv6-address
[
prefix-length
]
}
enable
By default, BGP does not exchange IPv6 unicast routes with any peer.
6.
Redistribute the IGP routes of the VPN into BGP.
import-route
protocol
[
{
process-id
|
all-processes
}
[
allow-direct
|
med med-value
|
route-policy route-policy-name
]
*
]
By default, no routes are redistributed into BGP.
Configuring routing between an MCE and a PE
About routing between an MCE and a PE
MCE-PE routing configuration includes the following tasks:
•
Binding the MCE-PE interfaces to IPv6 VPN instances.
•
Performing routing configurations.
•
Redistributing IPv6 VPN routes into the routing protocol running between the MCE and the PE.
Perform the following configurations on the MCE. For information about configuring the PE, see the
documentation for the PE.
Configuring IPv6 static routing between an MCE and a PE
1.
Enter system view.
system-view
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
}
3.
(Optional.) Set the default preference for IPv6 static routes.
ipv6 route-static default-preference
default-preference
The default value is 60.
Configuring RIPng between an MCE and a PE
1.
Enter system view.
system-view
2.
Create a RIPng process for an IPv6 VPN instance and enter RIPng view.
ripng
[
process-id
]
vpn-instance
vpn-instance-name
3.
Redistribute VPN routes.
import-route protocol
[
as-number
|
process-id
]
[
allow-ibgp
]
[
allow-direct
|
cost cost-value
|
route-policy route-policy-name
]
*
By default, no routes are redistributed into RIPng.
