Browse Prior Art Database

BGP-EVPN REMOTE BORDER LEAF BEHIND NETWORK ADDRESS TRANSLATION

IP.com Disclosure Number: IPCOM000243191D
Publication Date: 2015-Sep-17
Document File: 6 page(s) / 749K

Publishing Venue

The IP.com Prior Art Database

Related People

Kevin Fang: AUTHOR [+4]

Abstract

A new optional attribute in the Border Gateway Protocol (BGP) is added to allow BGP to deploy when support for multiple-data center inter-connections is needed with Network Address Translation (NAT) traversal mode.

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

Page 01 of 6

BGP-EVPN REMOTE BORDER LEAF BEHIND NETWORK ADDRESS TRANSLATION

AUTHORS:

Kevin Fang

 Linyu Lu
Feng Cai
Yuxiang Chen

CISCO SYSTEMS, INC.

ABSTRACT

    A new optional attribute in the Border Gateway Protocol (BGP) is added to allow BGP to deploy when support for multiple-data center inter-connections is needed with Network Address Translation (NAT) traversal mode.

DETAILED DESCRIPTION

    Currently, in an Ethernet Virtual Private Network (EVPN) (Border Gateway Protocol/Virtual Extensible Local Area Network (VxLAN) deployment, the BGP control plane does not support Network Address Translation (NAT)-traversal. Such a situation is shown in FIG. 1 below.

FIG. 1

    This is a typical hybrid cloud deployment scenario. In a public cloud border, if the public cloud operator use OpenStack, NAT is configured. When the public cloud wants to connect back to a private cloud, a BGP-EVPN NAT traversal scenario could arise.

    Some users deploy an Application Centric Infrastructure (ACI) in their data center for a private cloud. However, they still deploy a branch to the public cloud, and enable

Copyright 2015 Cisco Systems, Inc.

1


Page 02 of 6

Network Function Virtualization (NFV) for the connection of ACI remote leaf. NAT is available at the public cloud.

    Other users deploy Overlay Transport Virtualization (OTV), and are faced with an issue when traversal over NAT. OTV has a scaling issue, and users often plan to migrate to BGP-EVPN eventually.

    Techniques are presented in which a new attribute for BGP is added for the NAT traversal situation, as depicted in FIG. 2 below. Note that the yellow block could be a private service provider-wide area network (SP-WAN) link or the Internet, as in a multiple data center hybrid cloud situation.

FIG. 2

The operational flow is now described with reference to FIGs. 3- 6 below.

    1. DC Border Leaf (DCBL) as a Route Reflector (RR) or External BGP (EBGP). RBL(Remote Border Leaf) initial BGP session to DCBL.

    2. DCBL marks RBL's Public IP/port as neighbor information (like RBL-1 will have 2.2.2.2:port-1). This is why public/ip/port is needed as neighbor information.

Copyright 2015 Cisco Systems, Inc.

2


Page 03 of 6

Consider RBL-2/3 case, in which they behind a same NAT device, so it will have
3.3.3.3:port2/port3, and only public IP is not enough.

This field will also be an Extended Router-ID.

    Another case is that RBL-1 may have dual/mult...