Browse Prior Art Database

USE OF LOCATOR IDENTIFICATION SEPARATION PROTOCOL CONTROL PLANE FOR TRAFFIC ENGINEERING OF VIRTUAL PRIVATE NETWORK PSEUDOWIRE HEADENDS

IP.com Disclosure Number: IPCOM000249474D
Publication Date: 2017-Feb-28
Document File: 4 page(s) / 184K

Publishing Venue

The IP.com Prior Art Database

Related People

Reshad Rahman: AUTHOR

Abstract

Mechanisms for a service provider-edge router (S-PE) to steer incoming traffic are provided herein. A Locator Identification Separation Protocol (LISP) control plane is used for traffic engineering of Layer 2 (L2) virtual private networks (VPNs) and Ethernet VPNs (EVPNs). A S-PE registers a mapping of its loopback address to the routing locator (RLOC) interface address. LISP encapsulation is not needed because the loopback and interface addresses belong to the S-PE. Thus, no configuration is required on the access provider edge router (A-PE) or the access network to steer traffic in certain links.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 41% of the total text.

Copyright 2017 Cisco Systems, Inc. 1

USE OF LOCATOR IDENTIFICATION SEPARATION PROTOCOL CONTROL PLANE FOR TRAFFIC ENGINEERING OF VIRTUAL PRIVATE NETWORK

PSEUDOWIRE HEADENDS

AUTHORS: Reshad Rahman

CISCO SYSTEMS, INC.

ABSTRACT

Mechanisms for a service provider-edge router (S-PE) to steer incoming traffic are

provided herein. A Locator Identification Separation Protocol (LISP) control plane is used

for traffic engineering of Layer 2 (L2) virtual private networks (VPNs) and Ethernet VPNs

(EVPNs). A S-PE registers a mapping of its loopback address to the routing locator (RLOC)

interface address. LISP encapsulation is not needed because the loopback and interface

addresses belong to the S-PE. Thus, no configuration is required on the access provider

edge router (A-PE) or the access network to steer traffic in certain links.

DETAILED DESCRIPTION

Pseudowire (PW) / Ethernet virtual private networks (EVPN) – virtual private wire

service (VPWS) services are terminated at a service provider-edge router (S-PE). The S-

PE steers incoming traffic to specific interfaces. The target application is a PW Headend

(PWHE), which is a virtual interface representing a PW/EVPN-VPWS. To increase the

system scale on the S-PE, the PWHE is replicated to only a subset of ports/LCs.

PWHE and EVPN-VPWS use a per-PW interface-list configuration for traffic

engineering for scaling purposes. The interface-list is used on the S-PE for outgoing traffic

(i.e., from the S-PE to the A-PE). For L2VPN incoming traffic (i.e., A-PE to S-PE), flexible

label distribution protocol (LDP) targets for PWs and static routes on penultimate hop (PH)

routers are used. These are redistributed in the interior gateway protocol (IGP). However,

the interface-list configuration is cumbersome and error-prone because it requires

configuration of the S-PE and penultimate hop (PH) routers. For EVPN, all interfaces are

configured in the interface-list.

Copyright 2017 Cisco Systems, Inc. 2

A mechanism is desired that steers incoming traffic onto the ports, with the

intelligence/decision-maker stored mainly on the S-PE nodes. Restricting traffic on a

subset of links reduces resource allocation per PWHE interface (e.g., PWHE queues are

allocated on fewer ports for quality of service purposes) and allows for a higher PWHE

scale per system. This applies to both “classic” PWHEs (i.e., LDP PWs) and EVPN-VPWS.

Figure 1 below illustrates a sample network.

Figure 1

Traffic on the PWs from the A-PEs may arrive on any of the four links on the S-PE

(i.e., L1, L2, L3, or L4). For each PW/EVPN-VPWS, the S-PE may restrict incoming

traffic to one or more links or LCs (i.e., LC1 or LC2).

The mechanisms presented herein may include the following features.

1) A Locator Identification Separation Protocol (LISP) control plane for

L2VPN/EVPN is used for traffic engineering. Traffic engineering may be needed to scale

the L2VPN/EVPN services on the S-PE. Otherwise the L2VPN/EVPN virtual interface

may be replicated on all LCs on the...