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

S1720, S2700, S5700, and S6720 V200R010C00

This document describes the VPN configuration procedures and provides configuration examples.
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).
Configure Route Exchange Between an MCE Device and VPN Sites

Configure Route Exchange Between an MCE Device and VPN Sites

Context

The following configurations are performed on the MCE device. On the devices in the site, you only need to configure the corresponding routing protocol.

Configure Static Routes Between an MCE Device and a Site

Perform the following configurations on the MCE device. You only need to configure a static route to the MCE device in the site. The site configuration is not provided here. For detailed configuration of static routes, see Static Route Configuration in the S1720, S2700, S5700, and S6720 V200R010C00 Configuration Guide - IP Unicast Routing.

Table 3-23  MCE configuration

Action

Command

Description

Enter the system view.

system-view

-

Configure a static route to the site.

ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } interface-type interface-number [ 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 Site

Perform the following configurations on the MCE device. Configure RIPv1 or RIPv2 in the site. The site configuration is not provided here. For detailed RIP configuration, see RIP Configuration in the S1720, S2700, S5700, and S6720 V200R010C00 Configuration Guide - IP Unicast Routing.
Table 3-24  MCE configuration

Action

Command

Description

Enter the system view.

system-view

-

Create a RIP process running between the MCE device and the site 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 the routes to the remote sites advertised by the PE device in to the RIP routing table.

import-route { { static | direct | unr } | { rip | ospf | isis } [ process-id ] } [ cost cost | route-policy route-policy-name ] *

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

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

Configure OSPF Between an MCE Device and a Site

Perform the following configurations on the MCE device. Configure OSPF in the site. The site configuration is not provided here. For detailed OSPF configuration, see OSPF Configuration in the S1720, S2700, S5700, and S6720 V200R010C00 Configuration Guide - IP Unicast Routing.

Table 3-25  MCE configuration

Action

Command

Description

Enter the system view.

system-view

-

Create an OSPF process running between the MCE device and the site and enter the OSPF view.

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

-

(Optional) Import the routes to the remote sites advertised by the PE device into the OSPF routing table.

import-route { 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 and PE devices in the VPN instance.

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 Site

Perform the following configurations on the MCE device. You only need to configure IS-IS in the site. The site configuration is not provided here. For detailed IS-IS configuration, see IPv4 IS-IS Configuration in the S1720, S2700, S5700, and S6720 V200R010C00 Configuration Guide - IP Unicast Routing.

Table 3-26  MCE configuration

Action

Command

Description

Enter the system view.

system-view

-

Create an IS-IS process running between the MCE device and the site 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.

Import the routes to the remote sites advertised by the PE device 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 and PE devices 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 Site

Perform the following configurations on the MCE device.
Table 3-27  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 device connected to the MCE device in the site as a VPN peer.

peer ipv4-address as-number as-number

-

Import the routes to the remote sites advertised by the PE device 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 and PE devices in the VPN instance.

Perform the following configurations on the device connected to the MCE device in the site.
Table 3-28  Site configuration

Action

Command

Description

Enter the system view.

system-view

-

Enter the BGP view.

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

-

Configure the MCE device as a VPN peer.

peer ipv4-address as-number as-number

-

Import IGP routes of the VPN into the BGP routing table.

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

The site must advertise routes to its attached VPN network segments to the MCE device.

Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141944

Views: 72389

Downloads: 507

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