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

CLI-based Configuration Guide - VPN

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document describes VPN features on the device and provides configuration procedures and 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 a PE Device

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 IPv6198742hw. Choose one of the following configurations as needed:

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

Perform the following configurations on the MCE device.

Table 8-7  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 { [ interface-type interface-number ] nexthop-ipv6-address | nexthop-ipv6-address [ public ] | vpn-instance vpn-destination-name nexthop-ipv6-address } [ preference preference | tag tag ] * [ description text ]

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

Configure RIPng Between an MCE Device and a PE Device

Perform the following configurations on the MCE device.
Table 8-8  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 RIP routing table.

import-route { { ripng | isis | ospfv3 } [ process-id ] | bgp | unr | 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 system view.

quit

-

Enter an interface view.

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 8-9  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

-

(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 | 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 an interface view.

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 8-10  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 router. A maximum of three NETs can be configured for one process on each router.

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 8-11  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 VPN 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.

Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100033725

Views: 145365

Downloads: 361

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