Configuring 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 configuration tasks on the MCE. Configure the PE in the same way that you configure a PE in a basic IPv6 MPLS L3VPN. For more information about configuring the PE, see "Configuring IPv6 MPLS L3VPN."
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 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 ] [ tag tag-value ] [ description text ] | By default, no IPv6 static routes are configured. |
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
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a RIPng process for an IPv6 VPN instance and enter RIPng view. | ripng [ process-id ] vpn-instance vpn-instance-name | N/A |
3. Redistribute VPN routes. | import-route protocol [ process-id ] [ allow-ibgp ] [ allow-direct | cost cost-value | route-policy route-policy-name ] * | By default, no routes are redistributed into RIPng. |
4. Return to system view. | quit | N/A |
5. Enter interface view. | interface interface-type interface-number | N/A |
6. Enable the RIPng process on the interface. | ripng process-id enable | By default, RIPng is disabled on an interface. |
Configuring OSPFv3 between an MCE and a PE
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create an OSPFv3 process for an IPv6 VPN instance and enter OSPFv3 view. | ospfv3 [ process-id | vpn-instance vpn-instance-name ] * | N/A |
3. Set the router ID. | router-id router-id | N/A |
4. Disable routing loop detection. | vpn-instance-capability simple | By default, routing loop detection is enabled. On an MCE network, you must disable routing loop detection for a VPN OSPFv3 process. Otherwise, the MCE does not receive OSPFv3 routes from the PE. |
5. Redistribute VPN routes. | import-route protocol [ process-id | all-processes | allow-ibgp ] [ allow-direct | cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ] * | By default, no routes are redistributed into OSPFv3. |
6. Return to system view. | quit | N/A |
7. Enter interface view. | interface interface-type interface-number | N/A |
8. Enable the OSPFv3 process on the interface. | ospfv3 process-id area area-id [ instance instance-id ] | By default, OSPFv3 is disabled on an interface. |
Configuring IPv6 IS-IS between an MCE and a PE
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create an IS-IS process for an IPv6 VPN instance and enter IS-IS view. | isis [ process-id ] vpn-instance vpn-instance-name | N/A |
3. Configure a network entity title. | network-entity net | By default, no NET is configured. |
4. Create the IS-IS IPv6 unicast address family and enter its view. | address-family ipv6 [ unicast ] | By default, the IS-IS IPv6 unicast address family is not created. |
5. Redistribute VPN routes. | import-route protocol [ process-id ] [ allow-ibgp ] [ allow-direct | cost cost-value | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] * | By default, IPv6 IS-IS does not redistribute routes from any other routing protocol. If you do not specify the route level in the command, the command redistributes routes to the level-2 routing table. |
6. Return to system view. | quit | N/A |
7. Enter interface view. | interface interface-type interface-number | N/A |
8. Enable the IPv6 IS-IS process on the interface. | isis ipv6 enable [ process-id ] | By default, no IPv6 IS-IS process is enabled on the interface. |
Configuring EBGP between an MCE and a PE
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter BGP instance view. | bgp as-number [ instance instance-name ] [ multi-session-thread ] | N/A |
3. Enter BGP-VPN instance view. | ip vpn-instance vpn-instance-name | N/A |
4. Configure the PE as an EBGP peer. | peer { group-name | ipv6-address [ prefix-length ] } as-number as-number | By default, no BGP peers exist. |
5. Enter BGP-VPN IPv6 unicast address family view. | address-family ipv6 [ unicast ] | N/A |
6. Enable BGP to exchange IPv6 unicast routes with the specified peer. | peer { group-name | ipv6-address [ prefix-length ] } enable | By default, BGP does not exchange IPv6 unicast routes with any peer. |
7. Redistribute VPN routes. | 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 IBGP between an MCE and a PE
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter BGP instance view. | bgp as-number [ instance instance-name ] [ multi-session-thread ] | By default, BGP is not enabled. |
3. Enter BGP-VPN instance view. | ip vpn-instance vpn-instance-name | N/A |
4. Configure the PE as an IBGP peer. | peer { group-name | ipv6-address [ prefix-length ] } as-number as-number | By default, no BGP peers or peer groups exist. |
5. Enter BGP-VPN IPv6 unicast address family view. | address-family ipv6 [ unicast ] | N/A |
6. 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. |
7. Redistribute the VPN routes of the VPN site. | 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. |