WO2013081953A1 - Connecting on-premise networks with public clouds - Google Patents

Connecting on-premise networks with public clouds

Info

Publication number
WO2013081953A1
WO2013081953A1 PCT/US2012/066488 US2012066488W WO2013081953A1 WO 2013081953 A1 WO2013081953 A1 WO 2013081953A1 US 2012066488 W US2012066488 W US 2012066488W WO 2013081953 A1 WO2013081953 A1 WO 2013081953A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
tenant
packet
act
customer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2012/066488
Other languages
English (en)
French (fr)
Inventor
Changhoon Kim
Vijayan Ramakrishnan
Albert Greenberg
Monika MACHADO
Vijay P. SINGH GILL
Dharshan Rangegowda
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Corp
Original Assignee
Microsoft Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Corp filed Critical Microsoft Corp
Priority to JP2014544794A priority Critical patent/JP2015505431A/ja
Priority to KR1020147014706A priority patent/KR20140099464A/ko
Priority to EP12853513.5A priority patent/EP2786536A4/en
Publication of WO2013081953A1 publication Critical patent/WO2013081953A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L12/4645—Details on frame tagging
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Definitions

  • Computer systems and related technology affect many aspects of society. Indeed, the computer system's ability to process information has transformed the way we live and work. Computer systems now commonly perform a host of tasks (e.g., word processing, scheduling, accounting, etc.) that prior to the advent of the computer system were performed manually. More recently, computer systems have been coupled to one another and to other electronic devices to form both wired and wireless computer networks over which the computer systems and other electronic devices can transfer electronic data.
  • tasks e.g., word processing, scheduling, accounting, etc.
  • an entity e.g., a corporation
  • applications such as, for example, Web services, "on-premise" within the infrastructure.
  • computing tasks are performed on the on-premise (or private) computer network.
  • a corporation or other enterprise customer
  • the corporation or other enterprise customer
  • one entity uses another entity's infrastructure to run application on behalf of the entity.
  • one entity can run an application on machines in another entities data center.
  • Running an application in another entities data center can be referred to as running an application "in the cloud”.
  • computing resources and storage resources of the data center are allocated to a user.
  • Hybrid arrangements can exist on a temporary basis, such as, for example, when one entity supplements its own resources with resources from another entity.
  • Hybrid arrangements can exist on a temporary basis, such as, for example, when one entity supplements its own resources with resources from another entity.
  • on-premise resources are operating at or near capacity or in response to a surge in workload
  • a user of the on- premise resources can request allocation of cloud resources to perform additional work.
  • the cloud resources can be returned back to an available pool of resources for allocation to other users.
  • the user can be charged for use of any allocated resources.
  • the user of the on-premise resources essentially rents cloud- based resources.
  • Outsourcing computing workloads to a public cloud can require significant bandwidth between a user's on-premise network and the public cloud.
  • data from an on-premise network typically passes through a gateway between the on-premise network and the network of the cloud provider.
  • existing gateway solutions for realizing this cross-premise connectivity fail to meet various requirements, such as, for example, increased performance, multi-tenancy, security, predictability, compatibility with various modes of access, scalability, low cost, and simplicity.
  • One embodiment illustrated herein is directed to a method practiced at a computer system including one or more processors and system memory.
  • the computer system includes a shim gateway.
  • the method includes acts for encapsulating a packet between a customer premise for delivery to customer resources within a public cloud data center.
  • the method includes an act of receiving a packet from a customer premise.
  • the packet is received at a customer specific shim component in the shim gateway.
  • the packet has a VLAN tag.
  • the packet identifies a tenant within a designated virtual network for the customer.
  • the designated virtual network is within the public cloud data center.
  • the method further includes an act of encapsulating the packet into an encapsulated packet.
  • Encapsulation includes mapping the VLAN tag to a destination network address of a tenant gateway for the customer.
  • the tenant gateway is in the designated virtual network.
  • the method further includes an act of forwarding the encapsulated packet to the tenant gateway in the designated virtual network for delivery to the identified tenant.
  • FIG. 1 Another embodiment illustrated herein includes a method that may be practiced at a computer system including one or more processors and system memory.
  • the computer system includes a tenant gateway.
  • the method includes acts for delivery of an encapsulated packet between a customer premise for delivery to customer resources within a public cloud data center.
  • the method includes an act of the tenant gateway receiving an encapsulated packet for delivery to a tenant in a designated virtual network.
  • the encapsulated packet is sent to the tenant gateway from a shim gateway component for the customer using a destination network address for the tenant gateway that was mapped from a VLAN tag.
  • the method further includes an act of the tenant gateway using information in the encapsulated packet to send data from the encapsulated packet to the tenant in the designated virtual network.
  • Figure 1 illustrates generally a number of modalities for communicating packets from a customer premise to a data center
  • Figure 2 illustrates communication details of a tenant gateway
  • Figure 3 illustrates an indirect splicing example of communication between customer premises and a data center
  • Figure 4 illustrates a second example of indirect splicing for communication between customer premises and a data center
  • Figure 5 illustrates shim device operations for indirect splicing
  • Figure 6 illustrates a direct splicing example of communication between customer premises and a data center
  • Figure 7 illustrates shim device operations for direct splicing
  • Figure 8 illustrates a detailed example of direct splicing
  • FIG. 9 illustrates a detailed example of ISP/MPLS Attachment
  • Figure 10 illustrates packet flow from a customer premise to a data center for a direct connect example
  • Figure 1 1 illustrates packet flow from a data center to a customer premise for a direct connect example
  • Figure 12 illustrates a first redundancy model
  • Figure 13 illustrates a second redundancy model
  • Figure 14 illustrates a third redundancy model
  • Figure 15 illustrates a method of encapsulating a packet between a customer premise for delivery to customer resources within a public cloud data center
  • Figure 16 illustrates a method of encapsulating a packet between a customer premise for delivery to customer resources within a public cloud data center.
  • the present invention extends to methods, systems, and computer program products for connecting on-premise networks with public clouds.
  • Embodiments of the invention include a cross-premise gateway configured for a public cloud offering.
  • the gateway facilitates cross-premise connectivity between a customer's on-premise networks and a public cloud.
  • the gateway supports scalability, multiple modes of access, multi- tenancy, simplicity, and support for virtualization protocols, such as, for example, Network Virtualization using Generic Routing Encapsulation (“NVGRE"). Accordingly, customers are provided efficient and predictable (e.g., better Service Level Agreements ("SLAs”)) cross-premise connectivity to utilize a public cloud.
  • SLAs Service Level Agreement
  • Embodiments of the present invention may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below.
  • Embodiments within the scope of the present invention also include physical and other computer- readable media for carrying or storing computer-executable instructions and/or data structures.
  • Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system.
  • Computer-readable media that store computer-executable instructions are computer storage media (devices).
  • Computer- readable media that carry computer-executable instructions are transmission media.
  • embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: computer storage media (devices) and transmission media.
  • Computer storage media includes RAM, ROM, EEPROM, CD-ROM, solid state drives (“SSDs”) (e.g., based on RAM), Flash memory, phase-change memory (“PCM”), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
  • SSDs solid state drives
  • PCM phase-change memory
  • a "network” is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices.
  • a network or another communications connection either hardwired, wireless, or a combination of hardwired or wireless
  • the computer properly views the connection as a transmission medium.
  • Transmissions media can include a network and/or data links which can be used to carry or desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.
  • program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (devices) (or vice versa).
  • computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a "NIC"), and then eventually transferred to computer system RAM and/or to less volatile computer storage media (devices) at a computer system.
  • a network interface module e.g., a "NIC”
  • NIC network interface module
  • computer storage media (devices) can be included in computer system components that also (or even primarily) utilize transmission media.
  • Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
  • the computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code.
  • the invention may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, edge devices, gateways, routers, switches, and the like.
  • the invention may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks.
  • program modules may be located in both local and remote memory storage devices.
  • FIG. 1 illustrates direct peering where corporate networks 102-A and 102-B, through their enterprise gateways connect directly to a cloud provider backbone/Global Network Service (“GNS”) 104, using Global Network Service Peer points, to a cloud provider data center 106.
  • GRS cloud provider backbone/Global Network Service
  • embodiments of the invention can use dedicated access connectivity options including Internet Service Provider ("ISP") peering.
  • ISP Internet Service Provider
  • corporate networks 102-A and 102-B using their enterprise gateways can connect to an Internet Service Provider 108, to a cloud provider backbone/Global Network Service (“GNS”) 104, and to a cloud provider data center 106.
  • GNS cloud provider backbone/Global Network Service
  • a gateway can be physically located at an anchor site for an ISP or Dedicated Connection Provider. Logically, the gateway can provide multi-tenant and multi-mode access functionality.
  • Figure 2 depicts an example gateway 110 illustrating logical representation of gateway functionality. However, various different components of a gateway can be utilized to provide gateway functionality. For example, gateway functionality can be split between different components and/or locations.
  • a multi-tenant multi-mode gateway can provide high bandwidth (e.g., 200 GB/s+ per data center) at a reduced cost.
  • a gateway can provide multi-protocol cross premise connectivity (e.g., via dedicated access or ISPs) using Multiprotocol Label Switching ("MPLS") (e.g., L3vpn, 6PE, 6VPE, etc), Ethernet over MPLS (EoMPLS), Virtual Private LAN Services (“VPLS”), Locator/ID Separator Protocol (LISP), Generic Routing Encapsulation (GRE), Level 2 Tunneling Protocol version 3 (L2TPv3), Direct circuit handoff, etc.
  • MPLS Multiprotocol Label Switching
  • L3vpn L3vpn, 6PE, 6VPE, etc
  • Ethernet over MPLS EoMPLS
  • VPLS Virtual Private LAN Services
  • Locator/ID Separator Protocol LISP
  • GRE Generic Routing Encapsulation
  • L2TPv3 Level 2 Tunneling Protocol version 3
  • Direct circuit handoff etc.
  • a gateway can provide dynamic routing. For example this may be done with Border Gateway Protocol ("BGP”)/ Extensible Messaging and Presence Protocol
  • XMPP XMPP peering with tenant gateways.
  • Gateway redundancy can be provided. For example, in some embodiments this may be provided via BGP multi-path/Equal-cost multi-path routing ("ECMP").
  • ECMP BGP multi-path/Equal-cost multi-path routing
  • a gateway can be programmable to create/delete loopbacks, GRE/NVGRE tunnel end points, VPN, BGP peering on router, etc., from the gateway to tenants.
  • Standardized Interface/ APIs and control protocols can assist with demand/automated provisioning.
  • a gateway architecture can use a split model.
  • a gateway can be split into a front-end and a back-end.
  • the front-end can be a shim gateway located at a remote anchor or peering site, for example, located afar from cloud-computing data centers.
  • a shim gateway can be a commodity switch or appliance configured for tunnel encapsulation/ decapsulation.
  • the back-end can be tenant gateway virtual machine(s) (VMs) at a cloud computing data center.
  • Gateway tenant VMs can have different arrangements.
  • tenant gateway VMs serve a single Virtual Network ("VNet") (a non multi- tenant arrangement).
  • tenant gateway VMs serve multiple VNets (a multi-tenant arrangement).
  • a shim gateway and tenant gateway virtual machines are commonly owned.
  • a gateway can provide Virtual Routing and Forwarding (VRF), VLANs to VNet translation layer using different mechanisms.
  • VRF Virtual Routing and Forwarding
  • an indirect splicing mechanism uses Generic Routing Encapsulation ("GRE") tunnels to Virtual Machines ("VMs").
  • GRE Generic Routing Encapsulation
  • VMs Virtual Machines
  • a direct splicing mechanism uses directory service lookup and VNet-NVGRE encapsulation/decapsulation. The direct mechanism also maps Tenant IDs in NVGRE to VRF instance and vice versa.
  • Figure 3 depicts an example of indirect splicing.
  • communication from any of a variety of customer networks including customer networks 102-X , 102-Y and 102-Z is sent from customer premises via customer gateways 112-X, 112-Y, and 112-Z to a shim gateway 114 (i.e., front-end of a gateway 110).
  • Data from customers can be sent using any of a variety of different protocols such as MPLS and direct circuit.
  • the shim gateway 114 includes components 116-X, 116-Y, and 116-Z corresponding to each customer. For each customer, the corresponding component at the shim gateway 114 translates communication from the customer into GRE communication.
  • Shim components can be configured to send GRE communication to a specified VNet.
  • the shim component 116-X can be configured to forward communication from customer network 102-X to VNet 118-X. GRE communication is forwarded to the corresponding specified VNet (e.g., VNet 118-X, VNet 118-Y, VNet 118-Z, etc.).
  • tenant gateways 120-X, 120-Y and 120-Z receive GRE communication.
  • the tenant gateways (referred to generically at 120) are examples of back-ends of the gateway 110.
  • a tenant gateway 120 translates GRE communication into NVGRE communication.
  • the GRE communication and NVGRE communication are examples of a data plane.
  • the tenant gateway 120 can also use addressing information in the GRE communication to locate appropriate tenants (e.g., tenants 122-X, 122-Y, and 122-Z) in the VNet (referred to generically as 118) for receiving the customer data.
  • This is an example of a control plane.
  • An example of using addressing information includes a directory lookup based on IP addresses in the GRE communication.
  • the customer data is then sent to the appropriate tenants (referred to generically as 122) using NVGRE.
  • Figure 4 depicts a second example of indirect splicing. Similar to Figure 3, Figure 4 depicts that communication from any of a variety of customers including customers X, Y and Z is sent from on-premise customer network 102-X, 102-Y and 102-Z via customer gateways 112-X, 112-Y and 112-Z to a shim gateway 114, that functions as a front-end of the gateway 110 illustrated in Figure 2. Data from customers can be sent using any of a variety of different protocols such as MPLS and direct circuit.
  • the shim gateway 114 includes a component 116-X, 116-Y and 116-Z corresponding to each customer X, Y and Z respectively.
  • the corresponding component at the shim gateway translates communication from the customer into NVGRE or GRE communication.
  • GRE can be used between the shim gateway 114 and the multi-tenant gateway 124 (the multi-tenant gateway 124 is an example of a backend of the gateway 110 illustrated in Figure 2) if multiple virtual IP addresses (VIPs) can be assigned to the multi- tenant gateway 124, each of which is unique for a VNet (e.g., VNets 118-X, 118-Y and 118-Z). If multiple VIPs are not used (either because they cannot be assigned or a choice is made not to use them) NVGRE is used along with one common VIP.
  • VNet e.g., VNets 118-X, 118-Y and 118-Z
  • Shim components can be configured to send the NVGRE or GRE communication to the multi-tenant gateway 124, that in this example, is used as a back-end of the gateway 110. Accordingly, any of shim components 116-X, 116-
  • Y and 116-Z that have customer data can send the customer data to the multi-tenant gateway 124.
  • the multi-tenant gateway 124 can translate GRE
  • the multi-tenant gateway 124 can also use addressing information in the GRE or NVGRE communication to locate (e.g., a directory lookup based on IP addresses in the GRE or NVGRE communication) appropriate tenants within an appropriate VNet for receiving the customer data to implement a control plane. The customer data is then sent to the appropriate VNet and onto the appropriate tenants within the appropriate VNet using NVGRE.
  • addressing information in the GRE or NVGRE communication to locate (e.g., a directory lookup based on IP addresses in the GRE or NVGRE communication) appropriate tenants within an appropriate VNet for receiving the customer data to implement a control plane.
  • the customer data is then sent to the appropriate VNet and onto the appropriate tenants within the appropriate VNet using NVGRE.
  • Figure 5 depicts shim gateway 114 operation for indirect splicing.
  • Figure 5 depicts shim gateway 114 operation for GRE.
  • NVGRE can be used as well.
  • the multi-tenant gateway 124 uses a common public IP address to communicate with the shim gateway 114.
  • Figure 6 depicts an example of direct splicing. As depicted in Figure 6, communication from any of a variety of customers, including customers X, Y, and Z is sent from customer networks 102-X, 102-Y and 102-Z via customer gateways 112-X, 112-
  • shim gateway 114 which functions as a front-end of the gateway 110.
  • Data from customers can be sent using any of a variety of different protocols including
  • the shim gateway 114 includes a component 116-X, 116-Y and 116-Z corresponding to each customer. For each customer, the corresponding component at the shim gateway 114 translates communication from the customer into NVGRE communication.
  • each shim component 116-X, 116-Y and 116-Z is compatible with a VNet (referred to generically as 118).
  • VNet referred to generically as 118.
  • the shim components 116-X, 1 16-Y and 116- Z can use addressing information in the NVGRE communication to locate (e.g., a directory lookup based on IP addresses in the NVGRE communication) appropriate tenants 122 in the appropriate VNet 118 for receiving the customer data to implement a control plane.
  • the customer data is then sent to the appropriate VNet 118 and onto the appropriate tenants 122 within the appropriate VNet 118 using NVGRE.
  • Figure 8 depicts a more detailed layout for direction connection.
  • various abbreviations are shown. The following summarizes those abbreviations:
  • Figure 8 illustrates that enterprise customers 102-A and 102-B have direct-access dedicated links from a switch 126.
  • Corporation A gets a 10G dedicated link
  • Corporation B gets a 1G dedicated link to the switch 126.
  • the switch performs a customer-circuit to VLan handoff (including tagging of the customer) to the shim gateway 114 installed at a peering or anchor site 126.
  • the shim gateway 114 comprises a 10/40G switch.
  • the shim gateway 114 takes VLan frames and maps (or encapsulates) them into the VNet domain using GRE.
  • the shim gateway 114 could do direct NVGRE encapsulation if it can lookup Directory service for CA ⁇ > PA mapping (thereby bypassing the VNet-gateway in datapath).
  • the tenant gateways 120- A and 120- B on the data center 106 side can be made multi -tenant. Further, the route exchange between on-premises systems (e.g., systems on Corporation A or Corporation B's site network) and cloud (e.g., the data center 106) could be done statically or using a BGP.
  • Figure 8 further illustrates that a control channel 128 from the data center 106 fabric to the shim- 114 may be implemented to facilitate automated provisioning.
  • Figure 9 depicts a more detailed layout for ISP/MPLS attach. Figure 9 illustrates a number of abbreviations in addition to those shown in Figure 8. Those additional abbreviations are summarized below:
  • PE Provider Edge Router (e.g., ISP provider)
  • enterprise customers 102-A and 102-B peering with ISPs, can attach to the data center 106.
  • the ISP does VRF to VLan handoff (including tagging of customers) to the shim gateway 114 installed at the switch provider site 130.
  • the shim gateway 114 takes VLan frames and maps (or encapsulates) them into the VNet domain using GRE/NVGRE.
  • the shim gateway 114 could do direct NVGRE
  • Tenant gateways 102-A and 102-B on the data center 106 side can be made multi-tenant. Further, the route exchange between on-premises systems (e.g., systems on Corporation A or Corporation B's site network) and cloud (e.g., the data center 106) could be done statically or using a BGP.
  • Figure 9 further illustrates that a control channel 128 from the data center 106 fabric to the shim- 114 may be implemented to facilitate automated provisioning.
  • Figure 10 depicts inbound packet flow to the data center for direct connect examples.
  • Figure 10 illustrates flow of packets from a host 132 at a customer site 102-X to tenants 122 at a VNet 118-X at a data center 106. Packets flow from the host 132 to a customer gateway 134-X. Encapsulation is performed at the customer gateway 134-X Packets are then sent to the switch 126. At the switch 126 VLan encapsulation is performed by the switch 126. Packets are then forwarded to the shim gateway 114. At the shim gateway 114, VLan decapsulation and GRE encapsulation are performed.
  • Packets are then forwarded to a software load balancer (SLB) 136.
  • SLB software load balancer
  • an SLB 136 is used to balance loads between different virtual machines of a tenant gateway 120- X.
  • SLB encapsulation is performed.
  • Packets are then forwarded to a selected tenant gateway virtual machine.
  • packets are forwarded to tenant gateway virtual machine 1.
  • a software load balancer driver is used to perform software load balancer decapsulation and DNAT.
  • VNet decapsulation is performed at the tenant gateway virtual machine.
  • IP routing is performed to route the packets tenant virtual machine 1022.
  • a VNet driver is used to perform VNet encapsulation.
  • a VNet driver is used to perform VNet decapsulation.
  • Figure 11 depicts inbound packet flow for direct connect examples.
  • a packet originates at a source, which in this example is a tenant from a set of tenants 122 at the VNet 118-X of the data center 106.
  • GRE encapsulation is performed using a VNet driver.
  • the packet is sent to the shim gateway 114.
  • GRE decapsulation is performed and VLan encapsulation is performed.
  • the encapsulation is Ethernet with VLan encapsulation.
  • the packet is then sent to the switch 126.
  • VLan decapsulation is performed and mapping to a customer port is performed. This allows the packet to be delivered to the host 132.
  • outgoing communication bypasses the tenant gateway 120-X.
  • VLAN to GRE lookup mapping can be performed in a variety of ways. To do VLAN to GRE lookup mapping:
  • VRF lite L3 subinterface per VLAN and GRE tunnels in a VRF lite
  • Embodiments of the invention include providing redundancy for customer connections to a cloud computing data center.
  • Figure 12 depicts a first example
  • Figure 12 illustrates one dedicated connection from the customer site 102-C using an eBGP session.
  • Figure 12 illustrates a cloud-connector.
  • Figure 12 further illustrates a tenant gateway 120-C.
  • the load-balanced gateway 102-C is a multi-instance device including tenant gateway 120-Cl and tenant gateway 120-C2.
  • Figure 13 depicts a second example redundancy model.
  • Figure 13 illustrates two dedicated connections from a customer site 102-C. In the illustrated example, two eBGP sessions are illustrated.
  • FIG 13 illustrates two separate switches 126-1 and 126-2 and two separate shim gateways 114-1 and 1 14-2.
  • the load-balanced gateway 102-C is a multi-instance device including tenant gateway 120-Cl and tenant gateway 120-C2.
  • Figure 14 depicts a third example redundancy model.
  • Figure 14 illustrates two separate switches 126-1 and 126-2 and two devices, shim 114-1 and shim 114-2, which act as one logical vPC device.
  • Figure 14 further illustrates a tenant gateway 120-C.
  • the load-balanced gateway 102-C is a multi-instance device including tenant gateway 120-Cl and tenant gateway 120-C2.
  • embodiments of the invention provide increased scalability.
  • the capacity of a gateway can be increased by adding more virtual machines running the connectivity service.
  • Gateways can be integrated with an existing network load-balancer and hence inherits the corresponding benefits, such as resource pooling and high availability.
  • Cross premise connectivity is supported via various access modes customers choose, including MPLS and direct circuit.
  • Embodiments permit multiple customers/tenants to connect to a public cloud using scalable gateway front end and multi-tenant back-end infrastructure. Dynamic routing, failover and resiliency are provided by leveraging BGP. Embodiments of the invention work at layer-2 and hence do not depend on IP routing or VRF (Virtual Routing and Forwarding) technology, lowering complexity significantly.
  • VRF Virtual Routing and Forwarding
  • embodiments of the invention include using any of the described indirect and direct splicing mechanisms with (1) multiple access modes, (2) multi-tenancy using L2 to L3 interconnection (and independent of other mechanisms, such as, VRF), (3) scaling-out and high availability facilitated by load balancing technology, and (4) support for NVGRE.
  • Embodiments of the invention enable high-speed cross-premise (e.g., customer site to virtual network) interconnection scenarios.
  • the method includes an act of receiving a packet from a customer premise (act 1502).
  • the packet is received at a customer specific shim component in the shim gateway, such as for example, a shim component 116.
  • the packet having a VLAN tag, such as the VLAN tags illustrated in Figures 5 and 7.
  • the packet identifies a tenant (e.g., from among tenants 122) within a designated virtual network (e.g., virtual network 118) for the customer.
  • the designated virtual network is within the public cloud data center.
  • the method 1500 further includes an act of encapsulating the packet into an encapsulated packet (act 1502).
  • Encapsulation includes mapping the VLAN tag to a destination network address of a tenant gateway for the customer, where the tenant gateway is in the designated virtual network. Examples of tenant gateways are illustrated 120 for individual gateways where each gateway is particular to a particular VNet or at 124 where a multi-tenant gateway is used for a plurality of different VNets.
  • the method 1500 further includes an act of forwarding the encapsulated packet to the tenant gateway in the designated virtual network for delivery to the identified tenant.
  • the method 1500 may be practiced where the act of receiving a packet from a customer premise comprises an act of receiving a packet via one of a plurality of access modes supported by the shim gateway.
  • the method 1500 may be practiced where the act of encapsulating the packet into an encapsulated packet comprises an act of encapsulating the packet into an encapsulated packet.
  • act of encapsulating the packet into an encapsulated packet comprises an act of encapsulating the packet into an encapsulated packet.
  • encapsulation may be
  • the method 1500 may be practiced where the tenant gateway is a multi-tenant gateway (such as is illustrated at 124).
  • the act of encapsulating the packet into an encapsulated packet comprises an act of encapsulating the packet into an encapsulated packet where encapsulation includes mapping the VLAN tag to a destination network address of a multi-tenant gateway.
  • the multi-tenant gateway is in the public cloud data center.
  • the multi-tenant gateway is a gateway for a plurality of different virtual networks, including the designated virtual network.
  • the an act of forwarding the encapsulated packet to the tenant gateway in the designated virtual network for delivery to the identified tenant includes act of an act of forwarding the encapsulated packet to the multi-tenant gateway for delivery to the identified tenant.
  • the method 1500 may be practiced where communication is facilitated by a high-speed cross premise interconnection.
  • the method 1500 may be practiced where the act of forwarding the encapsulated packet to the tenant gateway in the designated virtual network for delivery to the identified tenant comprises forwarding the packet to a software load balancer to forward the encapsulated packet to a virtual machine selected from a plurality of virtual machines at the tenant gateway.
  • Figure 10 illustrates the use of a software load balancer 136.
  • the method 1500 may be practiced where the act of encapsulating the packet into an encapsulated packet includes mapping the VLAN tag and a destination address in the packet to a Tenant ID, an electronic address for the designated virtual network, and an electronic address for the tenant.
  • the method 1600 may be practiced in a computer system including one or more processors and system memory.
  • the computer system including a tenant gateway (such as tenant gateway 120 or multi- tenant gateway 124).
  • the method includes acts for delivery of an encapsulated packet between a customer premise for delivery to customer resources within a public cloud data center (for example, delivery of packets from a customer premise 102 to resources at tenants 122 in a data center 106).
  • the method 1600 includes an act of the tenant gateway receiving an encapsulated packet for delivery to a tenant in a designated virtual network (act 1602).
  • the encapsulated packet is sent to the tenant gateway from a shim gateway component for the customer using a destination network address for the tenant gateway that was mapped from a VLAN tag.
  • the method 1600 further includes an act of the tenant gateway using information in the encapsulated packet to send data from the encapsulated packet to the tenant in the designated virtual network (act 1604).
  • the method 1600 may further include a load balancer determining to send the encapsulated packet to an instance of a virtual machine to load balance packets coming into the designated virtual network.
  • the method 1600 may be practiced where the act of the tenant gateway receiving an encapsulated packet for delivery to a tenant comprises an act of the tenant gateway receiving a GRE packet or an NVGRE patent. [0083] The method 1600 may be practiced where the act of the tenant gateway using information in the encapsulated packet to send data from the encapsulated packet to the tenant in the designated virtual network comprises an act of converting a GRE packet to an NVGRE packet.
  • the method 1600 may be practiced where the tenant gateway is a multi-tenant gateway.
  • the multi-tenant gateway is a gateway for multiple virtual networks.
  • the act of the tenant gateway receiving an encapsulated packet for delivery to a tenant in a designated virtual network comprises an act of the multi-tenant gateway receiving an encapsulated packet for delivery to a tenant in a designated virtual network from among the multiple virtual networks.
  • the encapsulated packet is sent to the multi- tenant gateway using a destination network address for the multi-tenant gateway that was mapped from the VLAN tag.
  • Such embodiments may further comprise an act of the multi- tenant gateway using information in the encapsulated packet to identify the designated virtual network.
  • Such embodiments may further comprise an act of the multi-tenant gateway sending data from the encapsulated packet to the tenant in the designated virtual network.
  • the method 1600 may be practiced where the tenant gateway corresponds to a single designated virtual network.
  • the method 1600 may be practiced where communication is facilitated by a high-speed cross premise interconnection.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
PCT/US2012/066488 2011-12-02 2012-11-26 Connecting on-premise networks with public clouds Ceased WO2013081953A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2014544794A JP2015505431A (ja) 2011-12-02 2012-11-26 オンプレミスネットワークの公衆クラウドとの接続
KR1020147014706A KR20140099464A (ko) 2011-12-02 2012-11-26 공개 클라우드와 온-프레미스 네트워크 연결 기법
EP12853513.5A EP2786536A4 (en) 2011-12-02 2012-11-26 CONNECTING NETWORKS ON SITE TO PUBLIC CLOUDS

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201161566166P 2011-12-02 2011-12-02
US61/566,166 2011-12-02
US13/650,750 2012-10-12
US13/650,750 US20130142201A1 (en) 2011-12-02 2012-10-12 Connecting on-premise networks with public clouds

Publications (1)

Publication Number Publication Date
WO2013081953A1 true WO2013081953A1 (en) 2013-06-06

Family

ID=48523968

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2012/066488 Ceased WO2013081953A1 (en) 2011-12-02 2012-11-26 Connecting on-premise networks with public clouds

Country Status (6)

Country Link
US (1) US20130142201A1 (https=)
EP (1) EP2786536A4 (https=)
JP (1) JP2015505431A (https=)
KR (1) KR20140099464A (https=)
CN (1) CN103188339B (https=)
WO (1) WO2013081953A1 (https=)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10541863B2 (en) * 2015-04-24 2020-01-21 Mitel Networks, Inc. Provisioning hybrid services
US11258635B2 (en) 2018-12-28 2022-02-22 Alibaba Group Holding Limited Overlay network routing using a programmable switch

Families Citing this family (120)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009155574A1 (en) * 2008-06-19 2009-12-23 Servicemesh, Inc. Cloud computing gateway, cloud computing hypervisor, and methods for implementing same
US20140201017A1 (en) 2008-06-19 2014-07-17 Servicemesh, Inc. Systems and methods for providing repeated use of computing resources
US9137210B1 (en) * 2012-02-21 2015-09-15 Amazon Technologies, Inc. Remote browsing session management
US9419894B2 (en) * 2012-04-30 2016-08-16 Futurewei Technologies, Inc. NVGRE biomodal tunnel mesh
EP2891277B1 (en) * 2012-09-26 2017-08-09 Huawei Technologies Co., Ltd. Overlay virtual gateway for overlay networks
US8948180B2 (en) * 2012-10-18 2015-02-03 Hewlett-Packard Development Company, L.P. Routing encapsulated data packets onto selected VLANs
US9634886B2 (en) * 2013-03-14 2017-04-25 Alcatel Lucent Method and apparatus for providing tenant redundancy
CN105264834B (zh) 2013-06-28 2018-12-07 华为技术有限公司 一种在nvo3网络中处理组播报文的方法、装置和nvo3网络
US10454714B2 (en) 2013-07-10 2019-10-22 Nicira, Inc. Method and system of overlay flow control
US10749711B2 (en) 2013-07-10 2020-08-18 Nicira, Inc. Network-link method useful for a last-mile connectivity in an edge-gateway multipath system
US9130775B2 (en) 2013-07-10 2015-09-08 Cisco Technology, Inc. Support for virtual extensible local area network segments across multiple data center sites
US9405568B2 (en) * 2013-09-13 2016-08-02 Microsoft Technology Licensing, Llc Multi-tenant network stack
US9565034B2 (en) * 2013-12-11 2017-02-07 Cisco Technology, Inc. System and method for scalable inter-domain overlay networking
BR112016025138A2 (pt) 2014-05-12 2017-08-15 Microsoft Technology Licensing Llc conexão de nuvem pública com recursos de rede privada
EP2945333B1 (de) * 2014-05-13 2018-03-07 Secunet Security Networks Aktiengesellschaft Übermittlungsverfahren für IP-Netze mittels VLAN-Tag
FR3025387A1 (fr) * 2014-09-03 2016-03-04 Orange Dispositif et procede de controle d'un coeur de reseau ip
US9342357B2 (en) 2014-09-11 2016-05-17 International Business Machines Corporation Extending cloud computing to on-premises data
US9509662B2 (en) 2014-09-24 2016-11-29 Microsoft Technology Licensing, Llc Techniques for providing services to multiple tenants via a shared end-point
US11216300B2 (en) * 2015-03-04 2022-01-04 Nec Corporation Datacenter, communication apparatus, communication method, and communication control method in a communication system
WO2016139948A1 (ja) * 2015-03-04 2016-09-09 日本電気株式会社 通信システムにおけるデータセンタ、通信装置、通信方法および通信制御方法
JP2016162415A (ja) * 2015-03-05 2016-09-05 株式会社野村総合研究所 本番環境アクセスシステム
US10425382B2 (en) 2015-04-13 2019-09-24 Nicira, Inc. Method and system of a cloud-based multipath routing protocol
US10135789B2 (en) 2015-04-13 2018-11-20 Nicira, Inc. Method and system of establishing a virtual private network in a cloud service for branch networking
US10498652B2 (en) 2015-04-13 2019-12-03 Nicira, Inc. Method and system of application-aware routing with crowdsourcing
US9948552B2 (en) * 2015-04-17 2018-04-17 Equinix, Inc. Cloud-based services exchange
US10021197B2 (en) * 2015-05-12 2018-07-10 Equinix, Inc. Multiple cloud services delivery by a cloud exchange
CN104966025B (zh) * 2015-06-01 2017-10-03 明算科技（北京）股份有限公司 数据隔离存储方法和系统
CN114549264B (zh) 2015-06-10 2025-07-01 株式会社宙连 用于利用多张sim卡的管理方法及管理服务器
EP3310008B1 (en) 2015-06-10 2021-02-17 Soracom, Inc. Communication system and communication method for providing ip network access to wireless terminals
JP5938498B1 (ja) * 2015-06-25 2016-06-22 株式会社ソラコム 無線端末に外部ネットワークへのアクセスを提供するための通信システム及び通信方法
US10075304B2 (en) * 2015-10-30 2018-09-11 Microsoft Technology Licensing, Llc Multiple gateway operation on single operating system
US10469559B2 (en) * 2015-12-03 2019-11-05 Avaya Inc. Quality of service for web real-time communication networks
US10171322B2 (en) 2016-01-11 2019-01-01 International Business Machines Corporation Dynamic and secure cloud to on-premise interaction and connection management
CN108702323B (zh) 2016-03-02 2021-06-01 日本电气株式会社 网络系统、控制装置、虚拟网络的构建方法以及计算机可读存储介质
US10931575B2 (en) 2016-04-13 2021-02-23 Nokia Technologies Oy Multi-tenant virtual private network based on an overlay network
US10523631B1 (en) * 2016-04-14 2019-12-31 Equinix, Inc. Communities of interest in a cloud exchange
US10819630B1 (en) 2016-04-20 2020-10-27 Equinix, Inc. Layer three instances for a cloud-based services exchange
US10447591B2 (en) 2016-08-30 2019-10-15 Oracle International Corporation Executing multiple virtual private network (VPN) endpoints associated with an endpoint pool address
WO2018102692A1 (en) 2016-12-02 2018-06-07 Carrier Corporation Mixed-mode cloud on-premise secure communication
US11252079B2 (en) 2017-01-31 2022-02-15 Vmware, Inc. High performance software-defined core network
US11121962B2 (en) 2017-01-31 2021-09-14 Vmware, Inc. High performance software-defined core network
US10992568B2 (en) 2017-01-31 2021-04-27 Vmware, Inc. High performance software-defined core network
US11706127B2 (en) 2017-01-31 2023-07-18 Vmware, Inc. High performance software-defined core network
US20200036624A1 (en) 2017-01-31 2020-01-30 The Mode Group High performance software-defined core network
US20180219765A1 (en) 2017-01-31 2018-08-02 Waltz Networks Method and Apparatus for Network Traffic Control Optimization
US10992558B1 (en) 2017-11-06 2021-04-27 Vmware, Inc. Method and apparatus for distributed data network traffic optimization
US10778528B2 (en) 2017-02-11 2020-09-15 Nicira, Inc. Method and system of connecting to a multipath hub in a cluster
EP3637702A4 (en) * 2017-05-11 2020-04-29 Nec Corporation GATEWAY DEVICE, SENDING METHOD AND PROGRAM
US10523539B2 (en) 2017-06-22 2019-12-31 Nicira, Inc. Method and system of resiliency in cloud-delivered SD-WAN
US10608844B2 (en) 2017-10-02 2020-03-31 Vmware, Inc. Graph based routing through multiple public clouds
US10959098B2 (en) 2017-10-02 2021-03-23 Vmware, Inc. Dynamically specifying multiple public cloud edge nodes to connect to an external multi-computer node
US10999100B2 (en) 2017-10-02 2021-05-04 Vmware, Inc. Identifying multiple nodes in a virtual network defined over a set of public clouds to connect to an external SAAS provider
US11115480B2 (en) 2017-10-02 2021-09-07 Vmware, Inc. Layer four optimization for a virtual network defined over public cloud
US10999165B2 (en) 2017-10-02 2021-05-04 Vmware, Inc. Three tiers of SaaS providers for deploying compute and network infrastructure in the public cloud
US11089111B2 (en) 2017-10-02 2021-08-10 Vmware, Inc. Layer four optimization for a virtual network defined over public cloud
KR102008918B1 (ko) 2017-10-13 2019-08-08 엔에이치엔 주식회사 클라우드 네트워크 구성
US11223514B2 (en) 2017-11-09 2022-01-11 Nicira, Inc. Method and system of a dynamic high-availability mode based on current wide area network connectivity
CA2987603A1 (en) * 2017-12-04 2019-06-04 Jason Sieben A method of broadcasting a live performance
US11102079B2 (en) 2018-04-17 2021-08-24 Microsoft Technology Licensing, Llc Cross-regional virtual network peering
US10771283B2 (en) 2018-07-06 2020-09-08 Sap Se Virtual cloud node
US20200067829A1 (en) * 2018-08-27 2020-02-27 Ca, Inc. Methods and devices for intelligent selection of channel interfaces
US10999244B2 (en) 2018-09-21 2021-05-04 Microsoft Technology Licensing, Llc Mapping a service into a virtual network using source network address translation
US11140050B2 (en) 2018-09-26 2021-10-05 International Business Machines Corporation Localization of private service instances
US10826874B2 (en) * 2018-11-29 2020-11-03 Mastercard International Incorporated Direct production network access using private networks and encapsulation
US11095558B2 (en) * 2018-12-28 2021-08-17 Alibaba Group Holding Limited ASIC for routing a packet
CN109995782B (zh) * 2019-03-31 2020-06-12 深圳联想懂的通信有限公司 一种信息处理方法、设备、系统及计算机存储介质
US11201915B1 (en) * 2019-06-28 2021-12-14 Amazon Technologies, Inc. Providing virtual server identity to nodes in a multitenant serverless execution service
US11212238B2 (en) 2019-08-27 2021-12-28 Vmware, Inc. Providing recommendations for implementing virtual networks
US11611507B2 (en) 2019-10-28 2023-03-21 Vmware, Inc. Managing forwarding elements at edge nodes connected to a virtual network
US11489783B2 (en) 2019-12-12 2022-11-01 Vmware, Inc. Performing deep packet inspection in a software defined wide area network
US11394640B2 (en) 2019-12-12 2022-07-19 Vmware, Inc. Collecting and analyzing data regarding flows associated with DPI parameters
US11588731B1 (en) * 2020-01-17 2023-02-21 Equinix, Inc. Cloud-to-cloud interface
US11606712B2 (en) 2020-01-24 2023-03-14 Vmware, Inc. Dynamically assigning service classes for a QOS aware network link
US11477127B2 (en) 2020-07-02 2022-10-18 Vmware, Inc. Methods and apparatus for application aware hub clustering techniques for a hyper scale SD-WAN
US11588726B2 (en) * 2020-07-08 2023-02-21 OpenVPN, Inc Augmented routing of data
US11709710B2 (en) 2020-07-30 2023-07-25 Vmware, Inc. Memory allocator for I/O operations
US11575591B2 (en) 2020-11-17 2023-02-07 Vmware, Inc. Autonomous distributed forwarding plane traceability based anomaly detection in application traffic for hyper-scale SD-WAN
US11575600B2 (en) 2020-11-24 2023-02-07 Vmware, Inc. Tunnel-less SD-WAN
US11601356B2 (en) 2020-12-29 2023-03-07 Vmware, Inc. Emulating packet flows to assess network links for SD-WAN
US11792127B2 (en) 2021-01-18 2023-10-17 Vmware, Inc. Network-aware load balancing
US12218845B2 (en) 2021-01-18 2025-02-04 VMware LLC Network-aware load balancing
US11979325B2 (en) 2021-01-28 2024-05-07 VMware LLC Dynamic SD-WAN hub cluster scaling with machine learning
US11456894B1 (en) 2021-04-08 2022-09-27 Cisco Technology, Inc. Automated connectivity to cloud resources
AU2022254668B2 (en) 2021-04-08 2024-01-18 Vivek Agarwal Automated connectivity to cloud resources
US12368676B2 (en) 2021-04-29 2025-07-22 VMware LLC Methods for micro-segmentation in SD-WAN for virtual networks
US11388086B1 (en) 2021-05-03 2022-07-12 Vmware, Inc. On demand routing mesh for dynamically adjusting SD-WAN edge forwarding node roles to facilitate routing through an SD-WAN
US12009987B2 (en) 2021-05-03 2024-06-11 VMware LLC Methods to support dynamic transit paths through hub clustering across branches in SD-WAN
US11729065B2 (en) 2021-05-06 2023-08-15 Vmware, Inc. Methods for application defined virtual network service among multiple transport in SD-WAN
US12015536B2 (en) 2021-06-18 2024-06-18 VMware LLC Method and apparatus for deploying tenant deployable elements across public clouds based on harvested performance metrics of types of resource elements in the public clouds
US12250114B2 (en) 2021-06-18 2025-03-11 VMware LLC Method and apparatus for deploying tenant deployable elements across public clouds based on harvested performance metrics of sub-types of resource elements in the public clouds
US11489720B1 (en) 2021-06-18 2022-11-01 Vmware, Inc. Method and apparatus to evaluate resource elements and public clouds for deploying tenant deployable elements based on harvested performance metrics
US12047282B2 (en) 2021-07-22 2024-07-23 VMware LLC Methods for smart bandwidth aggregation based dynamic overlay selection among preferred exits in SD-WAN
US12267364B2 (en) 2021-07-24 2025-04-01 VMware LLC Network management services in a virtual network
US11375005B1 (en) 2021-07-24 2022-06-28 Vmware, Inc. High availability solutions for a secure access service edge application
US11943146B2 (en) 2021-10-01 2024-03-26 VMware LLC Traffic prioritization in SD-WAN
WO2023105582A1 (ja) * 2021-12-06 2023-06-15 日本電信電話株式会社 テナント冗長化システム、および、テナント冗長化方法
US12603848B2 (en) 2022-01-04 2026-04-14 VMware LLC Efficient mechanism for the transmission of multipath duplicate packets
US12184557B2 (en) 2022-01-04 2024-12-31 VMware LLC Explicit congestion notification in a virtual environment
US12507120B2 (en) 2022-01-12 2025-12-23 Velocloud Networks, Llc Heterogeneous hub clustering and application policy based automatic node selection for network of clouds
US12425395B2 (en) 2022-01-15 2025-09-23 VMware LLC Method and system of securely adding an edge device operating in a public network to an SD-WAN
US12506678B2 (en) 2022-01-25 2025-12-23 VMware LLC Providing DNS service in an SD-WAN
CN114640556A (zh) * 2022-03-02 2022-06-17 京东科技信息技术有限公司 一种跨集群的网络通信系统和方法
CN116980293A (zh) * 2022-04-22 2023-10-31 华为云计算技术有限公司 一种虚拟网络管理方法及相关装置
US11909815B2 (en) 2022-06-06 2024-02-20 VMware LLC Routing based on geolocation costs
US12166661B2 (en) 2022-07-18 2024-12-10 VMware LLC DNS-based GSLB-aware SD-WAN for low latency SaaS applications
US12237990B2 (en) 2022-07-20 2025-02-25 VMware LLC Method for modifying an SD-WAN using metric-based heat maps
US12526183B2 (en) 2022-08-28 2026-01-13 VMware LLC Dynamic use of multiple wireless network links to connect a vehicle to an SD-WAN
CN115473767A (zh) * 2022-09-06 2022-12-13 中电云数智科技有限公司 一种使用云专线访问ovn集群租户网的方法和系统
US20240323139A1 (en) * 2023-03-23 2024-09-26 Ipco 2012 Limited Systems and methods for use in balancing network resources
US12425332B2 (en) 2023-03-27 2025-09-23 VMware LLC Remediating anomalies in a self-healing network
US12034587B1 (en) 2023-03-27 2024-07-09 VMware LLC Identifying and remediating anomalies in a self-healing network
US12057993B1 (en) 2023-03-27 2024-08-06 VMware LLC Identifying and remediating anomalies in a self-healing network
US12483968B2 (en) 2023-08-16 2025-11-25 Velocloud Networks, Llc Distributed gateways for multi-regional large scale deployments
US12587468B2 (en) 2023-08-16 2026-03-24 Velocloud Networks, Llc Route filtering for clusters in multi-regional large scale deployments with distributed gateways
US12507148B2 (en) 2023-08-16 2025-12-23 Velocloud Networks, Llc Interconnecting clusters in multi-regional large scale deployments with distributed gateways
US12563438B2 (en) 2023-08-16 2026-02-24 Velocloud Networks, Llc Distributed gateways for multi-regional large scale deployments
US12507153B2 (en) 2023-08-16 2025-12-23 Velocloud Networks, Llc Dynamic edge-to-edge across multiple hops in multi-regional large scale deployments with distributed gateways
US12355655B2 (en) 2023-08-16 2025-07-08 VMware LLC Forwarding packets in multi-regional large scale deployments with distributed gateways
US12261777B2 (en) 2023-08-16 2025-03-25 VMware LLC Forwarding packets in multi-regional large scale deployments with distributed gateways
US12603827B2 (en) 2023-08-16 2026-04-14 Velocloud Networks, Llc Asymmetric routing resolutions in multi-regional large scale deployments with distributed gateways

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003107604A1 (en) * 2002-06-14 2003-12-24 Flash Networks Ltd. Method and system for connecting manipulation equipment between operator's premises and the internet
WO2004102890A1 (en) * 2003-05-13 2004-11-25 Telefonaktiebolaget Lm Ericsson (Publ) An arrangement and a method relating to ethernet access systems
US7668166B1 (en) * 1997-12-23 2010-02-23 Cisco Technology, Inc. Peer-model support for virtual private networks having potentially overlapping addresses
US20110075667A1 (en) 2009-09-30 2011-03-31 Alcatel-Lucent Usa Inc. Layer 2 seamless site extension of enterprises in cloud computing
US20110134932A1 (en) * 2007-04-19 2011-06-09 Mark Gooch Marked packet forwarding
US20110261828A1 (en) 2010-04-27 2011-10-27 Cisco Technology, Inc. Virtual switching overlay for cloud computing

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2001288399A1 (en) * 2000-08-24 2002-03-04 Tiara Networks, Inc. System and method for connecting geographically distributed virtual local area networks
US8776050B2 (en) * 2003-08-20 2014-07-08 Oracle International Corporation Distributed virtual machine monitor for managing multiple virtual resources across multiple physical nodes
US20050044301A1 (en) * 2003-08-20 2005-02-24 Vasilevsky Alexander David Method and apparatus for providing virtual computing services
WO2009155574A1 (en) * 2008-06-19 2009-12-23 Servicemesh, Inc. Cloud computing gateway, cloud computing hypervisor, and methods for implementing same
US8549281B2 (en) * 2008-10-21 2013-10-01 Cohesive Flexible Technologies Corporation System and methods for enabling customer network control in third-party computing environments
CA3204215A1 (en) * 2009-04-01 2010-10-07 Nicira, Inc. Method and apparatus for implementing and managing virtual switches
WO2010127365A1 (en) * 2009-05-01 2010-11-04 Citrix Systems, Inc. Systems and methods for establishing a cloud bridge between virtual storage resources
CN101587577A (zh) * 2009-05-12 2009-11-25 刘利华 社区出租屋信息管理系统
US20110016473A1 (en) * 2009-07-20 2011-01-20 Srinivasan Kattiganehalli Y Managing services for workloads in virtual computing environments
US8619779B2 (en) * 2009-09-30 2013-12-31 Alcatel Lucent Scalable architecture for enterprise extension in a cloud topology
US8369333B2 (en) * 2009-10-21 2013-02-05 Alcatel Lucent Method and apparatus for transparent cloud computing with a virtualized network infrastructure
US20110126197A1 (en) * 2009-11-25 2011-05-26 Novell, Inc. System and method for controlling cloud and virtualized data centers in an intelligent workload management system
US8259571B1 (en) * 2010-03-26 2012-09-04 Zscaler, Inc. Handling overlapping IP addresses in multi-tenant architecture
JP5190084B2 (ja) * 2010-03-30 2013-04-24 株式会社日立製作所 仮想マシンのマイグレーション方法およびシステム
US8612600B2 (en) * 2010-12-07 2013-12-17 Nec Laboratories America, Inc. Negotiation tool and method for cloud infrastructure data sharing
EP2659624B1 (en) * 2010-12-28 2017-04-12 Citrix Systems Inc. Systems and methods for vlan tagging via cloud bridge
EP2482502B1 (en) * 2011-05-24 2017-05-10 Huawei Technologies Co., Ltd. Message handling method and apparatus
WO2012170016A1 (en) * 2011-06-07 2012-12-13 Hewlett-Packard Development Company, L.P. A scalable multi-tenant network architecture for virtualized datacenters

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7668166B1 (en) * 1997-12-23 2010-02-23 Cisco Technology, Inc. Peer-model support for virtual private networks having potentially overlapping addresses
WO2003107604A1 (en) * 2002-06-14 2003-12-24 Flash Networks Ltd. Method and system for connecting manipulation equipment between operator's premises and the internet
WO2004102890A1 (en) * 2003-05-13 2004-11-25 Telefonaktiebolaget Lm Ericsson (Publ) An arrangement and a method relating to ethernet access systems
US20110134932A1 (en) * 2007-04-19 2011-06-09 Mark Gooch Marked packet forwarding
US20110075667A1 (en) 2009-09-30 2011-03-31 Alcatel-Lucent Usa Inc. Layer 2 seamless site extension of enterprises in cloud computing
US20110261828A1 (en) 2010-04-27 2011-10-27 Cisco Technology, Inc. Virtual switching overlay for cloud computing

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ANDERSSON T; MADSEN ACREO AB L, PROVIDER PROVISIONED VIRTUAL PRIVATE NETWORK (VPN) TERMINOLOGY, 1 March 2005 (2005-03-01)
See also references of EP2786536A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10541863B2 (en) * 2015-04-24 2020-01-21 Mitel Networks, Inc. Provisioning hybrid services
US11258635B2 (en) 2018-12-28 2022-02-22 Alibaba Group Holding Limited Overlay network routing using a programmable switch

Also Published As

Publication number Publication date
JP2015505431A (ja) 2015-02-19
CN103188339B (zh) 2016-08-31
CN103188339A (zh) 2013-07-03
EP2786536A4 (en) 2015-08-19
US20130142201A1 (en) 2013-06-06
KR20140099464A (ko) 2014-08-12
EP2786536A1 (en) 2014-10-08

Similar Documents

Publication Publication Date Title
US20130142201A1 (en) Connecting on-premise networks with public clouds
US11375005B1 (en) High availability solutions for a secure access service edge application
US11343183B2 (en) Traffic forwarding between geographically dispersed sites
US20230026330A1 (en) Network management services in a point-of-presence
CN116158063B (zh) 多边以太信道（meec）创建和管理
US9590902B2 (en) Signaling aliasing capability in data centers
US9100213B1 (en) Synchronizing VPLS gateway MAC addresses
EP2891282B1 (en) System and method providing distributed virtual routing and switching (dvrs)
US10142218B2 (en) Hypervisor routing between networks in a virtual networking environment
EP4161003B1 (en) Evpn host routed bridging (hrb) and evpn cloud native data center
US11671358B2 (en) Disambiguating traffic in networking environments with multiple virtual routing and forwarding (VRF) logical routers
CN104283755B (zh) 一种虚拟专用云接入方法及系统
US20120216194A1 (en) Hypervisor application of service tags in a virtual networking environment
CN104813288A (zh) 用于在启用openflow的云计算中使用mpls时分离租户特定数据的装置和方法
US20240179089A1 (en) Containerized router service chaining for containerized network functions
EP3018866A1 (en) Signaling aliasing capability in data centers
CN117255019A (zh) 用于虚拟化计算基础设施的系统、方法及存储介质
US12592881B2 (en) Scaling efficiency for internal transport services in distributed network elements

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12853513

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20147014706

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2014544794

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012853513

Country of ref document: EP