445
as a client of the RR (the MCE).
8. Redistribute
routes advertised by the PE
into BGP.
import-route
protocol
[ process-id [
allow-direct
|
med
med-value
|
route-policy
route-policy-name ] * ]
By default, no routes are
redistributed into BGP.
9. (Optional.) Configure filtering
of advertised routes.
filter-policy
{ acl6-number |
prefix-list
ipv6-prefix-name }
export
[ protocol process-id ]
By default, BGP does not filter
advertised routes.
10. (Optional.) Configure filtering
of received routes.
filter-policy
{ acl6-number |
prefix-list
ipv6-prefix-name }
import
By
default, BGP does not filter
received routes.
2. Configure a VPN site:
1. Enter system view.
N/A
2. Enter BGP view.
bgp
as-number N/A
3. Configure the MCE as an
IBGP peer.
peer
{ group-name | ipv6-address
[ prefix-length ] }
as-number
as-number
N/A
4. Enter BGP-VPN IPv6 unicast
address family view.
address-family ipv6
[
unicast
]
N/A
5. E
IPv6 unicast routes with the
peer.
peer
{ group-name | ipv6-address
[ prefix-length ] }
enable
exchange IPv6 unicast routes with
any peer.
6.
Redistribute the IGP routes
of the VPN into BGP.
import-route
protocol
[ process-id [
allow-direct
|
med
med-value
|
route-policy
route-policy-name ] * ]
By
redistributed into BGP.
A VPN
site must advertise VPN
network addresses to the
connected MCE.
Configuring routing between an MCE and a PE
MCE-PE routing configuration includes these 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 configuration tasks on the MCE. Configure the PE in the same way that you
configure a PE in a basic MPLS L3VPN. For more information about configuring the PE, see
"Configuring MPLS L3VPN."
Configuring IPv6 static routing between an MCE and a PE
1. Enter system view.
N/A
To Next Page
Loading...
