Managing a network by controlling edge and non-edge switching elements

• US 9,007,903 B2
• Filed: 08/26/2011
• Issued: 04/14/2015
• Est. Priority Date: 07/06/2010
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Koponen, Teemu, Casado, Martin
• Primary Examiner(s): HSU, ALPUS
• Application Number:
  US13/218,472
• Publication Number:
  US 20130058251A1
• Time in Patent Office: 1,327 Days
• Field of Search: 370/254, 370/396, 370/397, 370/400, 370/409, 370/428, 370/231, 370/235, 709/220, 709/223, 709/238, 709/201, 709/228
• US Class Current: 370/231
• CPC Class Codes: G06F 11/07 Responding to the occurrence of a fault, e.g. fault tolerance
• CPC Class Codes: G06F 15/17312 Routing techniques specific to parallel machines, e.g. wormhole, store and forward, shortest path problem congestion routing on a LAN H04L45/00
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 2101/622 Layer-2 addresses, e.g. medium access control [MAC] addresses
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/036 Updating the topology between route computation elements, e.g. between OpenFlow controllers
• CPC Class Codes: H04L 45/586 of virtual routers
• CPC Class Codes: H04L 45/76 Routing in software-defined topologies, e.g. routing between virtual machines
• CPC Class Codes: H04L 47/783 Distributed allocation of resources, e.g. bandwidth brokers
• CPC Class Codes: H04L 49/00 Packet switching elements
• CPC Class Codes: H04L 49/1546 using pipelined operation
• CPC Class Codes: H04L 49/3063 Pipelined operation
• CPC Class Codes: H04L 49/70 : Virtual switches
• CPC Class Codes: H04L 61/5007 : Internet protocol [IP] addresses

Abstract

Some embodiments provide a network system that includes several non-edge switching elements that are each for forwarding network data to other non-edge switching elements. The network system includes several edge switching elements that are each for (1) coupling to a set of network hosts and (2) forwarding network data to the non-edge switching elements and to the set of network hosts. Each of the non-edge switching elements of the several non-edge switching elements is further for forwarding network data to the several edge switching elements. The network system includes a set of network controllers for (1) receiving a definition of a logical switching element that couples to the sets of network hosts and (2) managing the several edge switching elements by configuring the several edge switching elements to forward network data between the sets of network hosts based on the definition of the logical switching element.

Claims

1. A network system comprising:

a plurality of software managed edge (ME) switching elements that are each for (1) coupling to a set of network hosts that operate in a same physical machine as the software ME switching element and (2) forwarding network data, according to a set of flow entries that specify operations for implementing a logical datapath set (LDPS) to which the network hosts couple, to other software ME switching elements in the plurality of software ME switching elements and to the set of network hosts that operate in the same physical machine as the software ME switching elements in order to implement the LDPS;

a plurality of managed non-edge (MNE) switching elements, each operating on a separate physical machine from the network hosts and the other managed switching elements, for facilitating communication between the software ME switching elements in order to implement the LDPS; and

a set of network controller instances for (1) identifying a definition of the LDPS and (2) managing the MNE and ME switching elements by providing the MNE and ME switching elements with data for specifying the flow entries for forwarding network data between the sets of network hosts based on the identified definition of the LDPS.

2. The network system of claim 1, wherein the definition of the LDPS is a first definition of a first LDPS, wherein the sets of network hosts coupled to the plurality of software ME switching elements are first sets of network hosts, wherein each software ME switching element in the plurality of software ME switching elements is further for coupling to a second set of network hosts that operate in the same physical machine as the software ME switching element, wherein the set of network controller instances is further for identifying a second definition of a second LDPS, and managing the ME and MNE switching elements by providing the ME and MNE switching elements with data for specifying flow entries for forwarding network data between the second sets of network hosts based on the identified second definition of the second LDPS.

3. The network system of claim 2, wherein the set of network controller instances configures the plurality of software ME switching elements such that network data forwarded between the first sets of network hosts based on the definition of the first LDPS is isolated from network data forwarded between the second sets of network hosts based on the second LDPS.

4. The network system of claim 1, wherein the set of network controller instances manages each software ME switching element in the plurality of software ME switching elements by providing the software ME switching element with data for specifying a particular set of flow entries for forwarding network data to a corresponding set of network hosts that are coupled to and operate in the same physical machine as the software ME switching element and to the plurality of MNE switching elements.

5. The network system of claim 4, wherein a particular network controller instance in the set of network controller instances manages the plurality of MNE switching elements by providing the MNE switching elements with data for specifying all of the particular sets of flow entries for forwarding network data among the plurality of software ME switching elements.

6. The network system of claim 1, wherein the plurality of MNE switching elements comprises a set of software switching elements.

7. The network system of claim 1, wherein at least one MNE switching element in the plurality of MNE switching elements is further for forwarding network data to at least one ME switching element in the plurality of software ME switching elements.

8. The network system of claim 1, wherein at least one MNE switching element in the plurality of MNE switching elements is further for forwarding network data from a software ME switching element to another different MNE switching element.

9. The network system of claim 1, wherein the plurality of MNE switching elements are located at an interior of the network system and the plurality of ME switching elements are located at a boundary of the network system.

10. The network system of claim 1, wherein each MNE switching element in the plurality of MNE switching elements is at least two hops away from a network host in the network system.

11. The network system of claim 1, wherein at least one software ME switching element of the plurality of software ME switching elements is coupled to at least one MNE switching element of the plurality of MNE switching elements using a tunnel provided by one of a set of tunneling protocols.

12. The network system of claim 1, wherein each software ME switching element of the plurality of software ME switching elements sends network data to at least one MNE switching element of the plurality of MNE switching elements through an uplink port of the software ME switching element that corresponds to a physical port of the physical machine on which the software ME switching element operates.

13. The network system of claim 1, wherein the set of network controller instances manages the ME and MNE switching elements by providing data through a set of communication protocols comprising an OpenFlow protocol for communicating flow entries to the ME and MNE switching elements.

14. The network system of claim 13, wherein the set of communication protocols further comprises a configuration protocol for communicating configuration data to the ME and MNE switching elements.

15. A network system comprising:

a first plurality of physical host machines, each physical host machine comprising;

a set of network hosts that couples to a logical datapath set (LDPS); and

a software managed edge (ME) switching element for (1) coupling to the network hosts that operate in the physical host machine and (2) forwarding network data, according to a set of flow entries that specify operations for implementing the LDPS, to other software ME switching elements of other physical host machines in the first plurality of physical host machines and to the set of network hosts in order to implement the LDPS;

a second plurality of physical machines without network hosts that operate as managed non-edge (MNE) switching elements, the plurality of MNE switching elements for facilitating communication between the software ME switching elements in order to implement the LDPS; and

a set of network controller instances for (1) identifying a definition of the LDPS and (2) managing the ME and MNE switching elements by providing the MNE and ME switching elements with data for specifying the flow entries for forwarding network data between the sets of network hosts based on the identified definition of the LDPS.

16. The network system of claim 15, wherein a particular network controller instance in the set of network controller instances manages at least one MNE switching element in the plurality of MNE switching elements by providing the MNE switching element with data for specifying the flow entries for forwarding network data from a first software ME switching element in the plurality of software ME switching elements to a second software ME switching element in the plurality of software ME switching elements, when the first software ME switching element cannot forward the network data to the second software ME switching element.

17. The network system of claim 16, wherein the particular network controller instance is a first network controller instance and the MNE switching element is a first MNE switching element, wherein a second network controller instance in the set of network controller instances manages a second MNE switching element in the plurality of MNE switching elements by providing the second MNE switching element with data for specifying flow entries for forwarding the network data for the first MNE switching element, when the first MNE switching element cannot forward the network data.

18. The network system of claim 17, wherein the first MNE switching element cannot forward the network data because the first MNE switching element does not have a flow entry that specifies that the network data should be forwarded to at least one ME switching element in the second plurality of ME switching elements.

19. The network system of claim 17, wherein the first network controller instance and the second network controller instance are the same.

20. The network system of claim 17, wherein the second network controller instance manages the second MNE switching element by providing the second MNE switching element with data for specifying flow entries for forwarding network data to and from a particular switching element that serves as a communication bridge to a particular network.

21. The network system of claim 20, wherein the particular network is an unmanaged network.

22. The network system of claim 20, wherein the set of network controller instances is a first set of network controller instances, wherein the particular network is a managed network managed by a second set of network controller instances.

23. The network system of claim 20, wherein the network system is located in a first datacenter and the particular network is located in a second datacenter.

24. The network system of claim 23, wherein the second MNE switching element is located in the second datacenter.

25. The network system of claim 20, wherein the second MNE switching element is a software switching element executing on a standalone computing device.

26. The network system of claim 15, wherein each MNE switching element in the plurality of MNE switching elements is at least two hops away from a network host in the network system.

27. The network system of claim 15, wherein at least one software ME switching element of the plurality of software ME switching elements is coupled to at least one MNE switching element of the plurality of MNE switching elements using a tunnel that is provided by a tunneling protocol.

28. The network system of claim 15, wherein each software ME switching element of the plurality of software ME switching elements sends network data to at least one MNE switching element of the plurality of MNE switching elements through an uplink port of the software ME switching element that corresponds to a physical port of the physical machine on which the software ME switching element operates.

29. The network system of claim 15, wherein the set of network controller instances configures the plurality of software ME switching elements and the plurality of MNE switching elements by providing data through a set of communication protocols comprising an OpenFlow protocol for communicating flow entries to the plurality of software ME switching elements and the plurality of MNE switching elements.

30. The network system of claim 29, wherein the set of communication protocols further comprises a configuration protocol for communicating configuration information to the plurality of software ME switching elements and the plurality of MNE switching elements.