< 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 static routing, RIP, OSPF, IS-IS, and BGP. 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 to those on a PE device in the BGP/MPLS IP VPN networking. For detailed configuration, see Configuring Route Exchange Between PE and CE Devices.

Configure 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 static route to the PE device.

ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } vpn-instance vpn-destination-name nexthop-address [ preference preference | tag tag ] *

You must specify the next hop address on the MCE device.

Configure RIP 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 RIP process running between the MCE and PE devices and enter the RIP view.

rip process-id vpn-instance vpn-instance-name

A RIP process can be bound to only one VPN instance. If a RIP 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.

Enable RIP on the network segment of the interface to which the VPN instance is bound.

network network-address

-

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

import-route bgp [ permit-ibgp ] [ cost { cost | transparent } | route-policy route-policy-name ] *

import-route { { static | direct | unr } | { { rip | ospf | isis } [ process-id ] } } [ cost 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.

Configure OSPF 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 OSPF process running between the MCE and PE devices and enter the OSPF view.

ospf [ process-id | router-id router-id ] * vpn-instance vpn-instance-name

-

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

import-route { limit limit-number | { bgp [ permit-ibgp ] | direct | unr | rip [ process-id-rip ] | static | isis [ process-id-isis ] | ospf [ process-id-ospf ] } [ cost 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.

Disable routing loop detection in the OSPF process.

vpn-instance-capability simple

By default, routing loop detection is disabled in an OSPF process. If routing loop detection is not disabled in the OSPF process on the MCE device, the MCE device rejects OSPF routes sent from the PE device.

Configure an OSPF area and enter the OSPF area view.

area { area-id | area-id-address }

-

Enable OSPF on the network segment of the interface to which the VPN instance is bound.

network ip-address wildcard-mask

-

Configure IS-IS 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.

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

  • import-route { direct | static | unr | { ospf | rip | isis } [ process-id ] | bgp } [ cost-type { external | internal } | cost cost | tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] ] *

  • import-route { { ospf | rip | isis } [ process-id ] | bgp | direct | unr }inherit-cost [ { level-1 | level-2 | level-1-2 } | 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 IS-IS on the interface.

isis enable [ process-id ]

-

Configure BGP 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 IPv4 address family view.

ipv4-family vpn-instance vpn-instance-name

-

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

peer ipv4-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 an MCE Device
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >