No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - VPN

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of VPN, including GRE, BGP/MPLS IP VPN, BGP/MPLS IPv6 VPN, VLL, PWE3, and VPLS.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Route Exchange Between an MCE Device and a PE Device

Configuring Route Exchange Between an MCE Device and a PE Device

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

Perform the following configurations on the MCE device.

Table 3-19 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 ]

-

Commit the configuration.

commit

-

Configuring RIPng Between an MCE Device and a PE Device

Perform the following configurations on the MCE device.
Table 3-20 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 | direct | static } [ 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.

Return to the system view.

quit

-

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

interface interface-type interface-number

-

(For an Ethernet interface) Switch the interface to Layer 3 mode.

undo portswitch

By default, an Ethernet interface works in Layer 2 mode.

If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.
NOTE:

If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

Enable RIPng on the interface.

ripng process-id enable

-

Commit the configuration.

commit

-

Configuring OSPFv3 Between an MCE Device and a PE Device

Perform the following configurations on the MCE device.

Table 3-21 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 ] | direct | ripng help-process-id | static | isis help-process-id | ospfv3 help-process-id } [ 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.

Return to the system view.

quit

-

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

interface interface-type interface-number

-

(For an Ethernet interface) Switch the interface to Layer 3 mode.

undo portswitch

By default, an Ethernet interface works in Layer 2 mode.

If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.
NOTE:

If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

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

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

-

Commit the configuration.

commit

-

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

Perform the following configurations on the MCE device.

Table 3-22 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 | { 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 | { 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 the system view.

quit

-

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

interface interface-type interface-number

-

(For an Ethernet interface) Switch the interface to Layer 3 mode.

undo portswitch

By default, an Ethernet interface works in Layer 2 mode.

If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.
NOTE:

If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

Enable IS-IS IPv6 on the interface.

isis ipv6 enable [ process-id ]

-

Commit the configuration.

commit

-

Configuring BGP4+ Between an MCE Device and a PE Device

Perform the following configurations on the MCE device.
Table 3-23 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

-

(Optional) Configure a unique AS number for the VPN instance IPv6 address family.

as-number as-number

A VPN instance uses the AS number of BGP by default.

To re-assign a device to another AS or transmit different services in different instances, run this command to configure a different AS number for each VPN instance IPv6 address family.
NOTE:

The AS number configured in the VPN instance IPv6 address family view must be different from the AS number configured in the BGP view.

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

peer ipv6-address as-number as-number

-

Import the routes to the remote sites advertised by the PE device into the BGP4+ 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.

Commit the configuration.

commit

-

Translation
Download
Updated: 2019-04-03

Document ID: EDOC1100075353

Views: 14104

Downloads: 25

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next