# US 10,374,827 B2 · Identifier that maps to different networks at different datacenters > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,374,827 B2 - Document ID: US10374827B2 - Status: Granted - Kind: B2 - Application number: 15/813,120 - Filed: 2017-11-14 - Published: 2019-05-16 - Granted: 2019-08-06 - Earliest claimed: 2017-11-14 - Assignees: Nicira, Inc. - Applicants: Nicira, Inc. - Inventors: Xiaohu Wang; Ankur Kumar Sharma; Hongwei Zhu - Web page: https://patentgrep.com/patent/US10374827B2 ## CPC - H04L 12/4625: {Single bridge functionality, e.g. connection of two networks over a single bridge} - H04L 12/4645: {Details on frame tagging (routing of packets H04L45/00; support for virtual LAN H04L49/354)} - H04L 12/4675: {Dynamic sharing of VLAN information amongst network nodes (configuration of the network or of network elements H04L41/08)} - H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play - H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Some embodiments provide a method for a network manager that manages multiple managed forwarding elements at a particular datacenter. The method receives a configuration for a bridge between a logical L2 network that spans at least two datacenters and physical L2 networks at one or more of the spanned datacenters. The configuration includes a generic physical network identifier. The method maps the generic physical network identifier to a particular physical L2 network at the particular datacenter. The generic physical network identifier maps to other physical networks at other spanned datacenters. The method provides the configuration to a set of central controllers using an identifier for the particular physical L2 network. The set of central controllers configures a managed forwarding element operating at the particular datacenter to implement the bridge to bridge packets between the logical L2 network and the particular physical L2 network. ## Claims ### Claim 1 For a network manager that manages a plurality of managed forwarding elements at a particular datacenter, a method comprising: receiving a configuration for a bridge between a logical L2 network that spans at least two datacenters and physical L2 networks at one or more of the spanned datacenters, wherein the configuration includes a generic physical network identifier; mapping the generic physical network identifier to a particular physical L2 network at the particular datacenter, wherein the generic physical network identifier maps to other physical networks at other spanned datacenters; and providing the configuration to a set of central controllers using an identifier for the particular physical L2 network, wherein the set of central controllers configures a managed forwarding element operating at the particular datacenter to implement the bridge to bridge packets between the logical L2 network and the particular physical L2 network. ### Claim 2 (depends on 1) The method of claim 1, wherein the configuration is received from an administrator setting up the bridge. ### Claim 3 (depends on 1) The method of claim 1, wherein the configuration is received from a network manager at a different one of the at least two datacenters. ### Claim 4 (depends on 1) The method of claim 1, wherein: the particular datacenter is a first datacenter, the physical network is a first physical network, the managed forwarding element is a first managed forwarding element, and the network manager is a first network manager; the bridge is initially implemented by a second managed forwarding element at a second datacenter; the first network manager provides the configuration to the set of central controllers after a second network manager at the second datacenter fails. ### Claim 5 (depends on 4) The method of claim 4, wherein the initial implementation of the bridge bridges packets between the logical L2 network and a second physical network at the second datacenter. ### Claim 6 (depends on 1) The method of claim 1, wherein: the particular datacenter is a first datacenter and the managed forwarding element is a first managed forwarding element; the bridge is also implemented by a second managed forwarding element operating at the second datacenter. ### Claim 7 (depends on 6) The method of claim 6, wherein the physical network is a first physical network, wherein the bridge as implemented by the second managed forwarding element bridges packets between the logical L2 network and a second physical network at the second datacenter. ### Claim 8 (depends on 7) The method of claim 7, wherein packets bridged by the first managed forwarding element are marked with a bridge flag to prevent the second managed forwarding element from also bridging the packets. ### Claim 9 (depends on 8) The method of claim 8, wherein the bridge flag is a bit in a tunnel header for the packets. ### Claim 10 (depends on 6) The method of claim 6, wherein: the physical network is a first physical network and the network manager is a first network manager; and a second network manager at the second datacenter (i) receives the configuration for the bridge that includes the generic physical network identifier, (ii) maps the generic physical network identifier to a second physical L2 network at the second datacenter, and (iii) provides the configuration to the set of central controllers using an identifier for the second physical L2 network, wherein the set of central controllers configures the second managed forwarding element to implement the bridge to bridge packets between the logical L2 network and the second physical L2 network. ### Claim 11 A non-transitory machine readable medium storing a program for a network manager which when executed by at least one processing unit manages a plurality of managed forwarding elements at a particular datacenter, the program comprising: receiving a configuration for a bridge between a logical L2 network that spans at least two datacenters and physical L2 networks at one or more of the spanned datacenters, wherein the configuration includes a generic physical network identifier; mapping the generic physical network identifier to a particular physical L2 network at the particular datacenter, wherein the generic physical network identifier maps to other physical networks at other spanned datacenters; and providing the configuration to a set of central controllers using an identifier for the particular physical L2 network, wherein the set of central controllers configures a managed forwarding element operating at the particular datacenter to implement the bridge to bridge packets between the logical L2 network and the particular physical L2 network. ### Claim 12 (depends on 11) The non-transitory machine readable medium of claim 11, wherein the configuration is received from an administrator setting up the bridge. ### Claim 13 (depends on 11) The non-transitory machine readable medium of claim 11, wherein the configuration is received from a network manager at a different one of the at least two datacenters. ### Claim 14 (depends on 11) The non-transitory machine readable medium of claim 11, wherein: the particular datacenter is a first datacenter, the physical network is a first physical network, the managed forwarding element is a first managed forwarding element, and the network manager is a first network manager; the bridge is initially implemented by a second managed forwarding element at a second datacenter; the first network manager provides the configuration to the set of central controllers after a second network manager at the second datacenter fails. ### Claim 15 (depends on 14) The non-transitory machine readable medium of claim 14, wherein the initial implementation of the bridge bridges packets between the logical L2 network and a second physical network at the second datacenter. ### Claim 16 (depends on 11) The non-transitory machine readable medium of claim 11, wherein: the particular datacenter is a first datacenter and the managed forwarding element is a first managed forwarding element; the bridge is also implemented by a second managed forwarding element operating at the second datacenter. ### Claim 17 (depends on 16) The non-transitory machine readable medium of claim 16, wherein the physical network is a first physical network, wherein the bridge as implemented by the second managed forwarding element bridges packets between the logical L2 network and a second physical network at the second datacenter. ### Claim 18 (depends on 17) The non-transitory machine readable medium of claim 17, wherein packets bridged by the first managed forwarding element are marked with a bridge flag to prevent the second managed forwarding element from also bridging the packets. ### Claim 19 (depends on 18) The non-transitory machine readable medium of claim 18, wherein the bridge flag is a bit in a tunnel header for the packets. ### Claim 20 (depends on 16) The non-transitory machine readable medium of claim 16, wherein: the physical network is a first physical network and the network manager is a first network manager; and a second network manager at the second datacenter (i) receives the configuration for the bridge that includes the generic physical network identifier, (ii) maps the generic physical network identifier to a second physical L2 network at the second datacenter, and (iii) provides the configuration to the set of central controllers using an identifier for the second physical L2 network, wherein the set of central controllers configures the second managed forwarding element to implement the bridge to bridge packets between the logical L2 network and the second physical L2 network.