< Home

Configure Route Exchange Between an MCE Device and a PE Device

Context

Routing protocols that can be used between an MCE device and a PE device are IPv6 static routing, RIPng, OSPFv3, IS-IS IPv6, and BGP4+. Choose one of the following configurations as needed:

The following configurations are performed on the MCE device. The configurations on the PE device are similar. For details, see the user manual of the PE device.

Configure IPv6 Static Routes Between an MCE Device and a PE Device

Perform the following configurations on the MCE device.

Table 1 MCE configuration

Action

Command

Description

Enter the system view.

system-view

-

Configure a IPv6 static route to the PE device.

ipv6 route-static vpn-instance vpn-instance-name dest-ipv6-address prefix-length vpn-instance vpn-destination-name nexthop-ipv6-address [ preference preference | tag tag ] * [ description text ]

-

Configure RIPng Between an MCE Device and a PE Device

Perform the following configurations on the MCE device.
Table 2 MCE configuration

Action

Command

Description

Enter the system view.

system-view

-

Create a RIPng process running between the MCE and PE devices and enter the RIPng view.

ripng process-id vpn-instance vpn-instance-name

A RIPng process can be bound to only one VPN instance. If a RIPng process is not bound to any VPN instance before it is started, this process becomes a public network process and can no longer be bound to a VPN instance.

(Optional) Import VPN routes of the site into the RIPng routing table.

import-route { { ripng | isis | ospfv3 } [ process-id ] | bgp [ permit-ibgp ] | unr | direct | static } [ [ cost cost | inherit-cost ] | route-policy route-policy-name ] *

Perform this step if another routing protocol is running between the MCE device and VPN sites in the VPN instance.

Return to system view.

quit

-

Enter the view of the interface to which the VPN instance is bound.

interface interface-type interface-number

-

Enable RIPng on the interface.

ripng process-id enable

-

Configure OSPFv3 Between an MCE Device and a PE Device

Perform the following configurations on the MCE device.

Table 3 MCE configuration

Action

Command

Description

Enter the system view.

system-view

-

Create an OSPFv3 process running between the MCE and PE devices and enter the OSPFv3 view.

ospfv3 [ process-id ] [ vpn-instance vpn-instance-name ]

-

Configure the OSPFv3 router ID.

router-id router-id

-

(Optional) Import VPN routes of the site into the OSPF routing table.

import-route { bgp [ permit-ibgp ] | unr | direct | ripng help-process-id | static | isis help-process-id | ospfv3 help-process-id } [ { cost cost | inherit-cost } | type type | tag tag | route-policy route-policy-name ]*

Perform this step if another routing protocol is running between the MCE device and VPN sites in the VPN instance.

Return to system view.

quit

-

Enter the view of the interface to which the VPN instance is bound.

interface interface-type interface-number

-

Enable OSPFv3 on the interface which the VPN instance is bound.

ospfv3 process-id area area-id [ instance instance-id ]

-

Configure IS-IS IPv6 Between an MCE Device and a PE Device

Perform the following configurations on the MCE device.

Table 4 MCE configuration

Action

Command

Description

Enter the system view.

system-view

-

Create an IS-IS process running between the MCE and PE devices and enter the IS-IS view.

isis process-id vpn-instance vpn-instance-name

An IS-IS process can be bound to only one VPN instance. If an IS-IS process is not bound to any VPN instance before it is started, this process becomes a public network process and can no longer be bound to a VPN instance.

Set a network entity title (NET) for the IS-IS process.

network-entity net

A NET specifies the current IS-IS area address and the system ID of the switch. A maximum of three NETs can be configured for one process on each switch.

Enable IPv6 for the IS-IS process.

ipv6 enable [ topology { compatible [ enable-mt-spf ] | ipv6 | standard } ]

-

(Optional) Import VPN routes of the site into the IS-IS routing table.
Use either of the following commands:

  • ipv6 import-route { direct | unr | { ospfv3 | ripng | isis } [ process-id ] | bgp } inherit-cost [ tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] ] *

  • ipv6 import-route { static | direct | unr | { ospfv3 | ripng | isis } [ process-id ] | bgp } [ cost cost | tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] ] *

Perform this step if another routing protocol is running between the MCE device and VPN sites in the VPN instance.

Return to system view.

quit

-

Enter the view of the interface to which the VPN instance is bound.

interface interface-type interface-number

-

Enable IS-IS IPv6 on the interface.

isis ipv6 enable [ process-id ]

-

Configure BGP4+ Between an MCE Device and a PE Device

Perform the following configurations on the MCE device.
Table 5 MCE configuration

Action

Command

Description

Enter the system view.

system-view

-

Enter the BGP view.

bgp { as-number-plain | as-number-dot }

-

Enter the BGP-VPN instance IPv6 address family view.

ipv6-family vpn-instance vpn-instance-name

-

Configure the PE device as the EBGP peer of the MCE device.

peer ipv6-address as-number as-number

-

(Optional) Import VPN routes of the site into the BGP routing table.

import-route protocol [ process-id ] [ med med | route-policy route-policy-name ] *

Perform this step if another routing protocol is running between the MCE device and VPN sites in the VPN instance.
Parent Topic: Configuring IPv6 MCE
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >