Pull-based state dissemination between managed forwarding elements

• US 9,246,833 B2
• Filed: 01/31/2013
• Issued: 01/26/2016
• Est. Priority Date: 10/25/2011
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Koponen, Teemu, Padmanabhan, Amar
• Primary Examiner(s): Avellino, Joseph E
• Assistant Examiner(s): MCLEOD, MARSHALL M
• Application Number:
  US13/756,501
• Publication Number:
  US 20130212246A1
• Time in Patent Office: 1,090 Days
• Field of Search: 709/204, 709/201, 709/208
• US Class Current: 1/1
• CPC Class Codes: G05B 11/01 electric
• CPC Class Codes: G06F 15/177 Initialisation or configuration control processor initialisation G06F9/4405
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 41/0226 Mapping or translating multiple network management protocols
• CPC Class Codes: H04L 41/042 comprising distributed management centres cooperatively managing the network
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/20 Network management software packages
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/42 Centralised routing
• CPC Class Codes: H04L 45/66 Layer 2 routing, e.g. in Ethernet based MAN's
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/50 Queue scheduling
• CPC Class Codes: H04L 47/825 Involving tunnels, e.g. MPLS
• CPC Class Codes: H04L 49/254 Centralised controller, i.e. arbitration or scheduling

Abstract

For a controller that manages managed forwarding elements that forward data in a network, a method for configuring the managed forwarding elements is described. The method computes forwarding state and pushes the computed forwarding state to the managed switching elements. The forwarding state defines forwarding behaviors of the managed switching elements. The method configures the managed switching elements to exchange forwarding state with each other. The method configures the managed switching elements by configuring a first managed forwarding element to send a forwarding state information request to a second managed forwarding element and by configuring the second managed forwarding element to (1) respond to the forwarding state information request by looking up a forwarding state information repository and (2) update the forwarding state information repository with forwarding states information received from a third managed forwarding element.

Claims

1. For a controller that manages managed forwarding elements that forward data in a network, a method for configuring the managed forwarding elements, the method comprising:

computing forwarding state and sending the computed forwarding state to the managed forwarding elements, the forwarding state defining forwarding behaviors of the managed forwarding elements; and

configuring the managed forwarding elements to exchange forwarding state with each other, the configuring comprising;

configuring a first managed forwarding element to send a forwarding state information request to a second managed forwarding element;

configuring the second managed forwarding element (i) to respond to the forwarding state information request by performing a lookup in a forwarding state information repository and (ii) to update the forwarding state information repository with forwarding state information received from a third managed forwarding element; and

configuring the third managed forwarding element to send a removal request to the second managed forwarding element to remove certain forwarding state information from the forwarding state information repository when the third managed forwarding element determines that the certain forwarding state information is no longer valid.

2. The method of claim 1, wherein said configuring the managed forwarding elements further comprises configuring the third managed forwarding element to send forwarding state information regarding the third managed forwarding element to the second managed forwarding element.

3. The method of claim 1, wherein the third managed forwarding element determines that the certain forwarding state information is no longer valid by comparing information of a packet received from the first managed forwarding element or the second managed forwarding element with a local information repository of the third managed forwarding element.

4. The method of claim 1, wherein the forwarding state information request is a first forwarding state information request, wherein said configuring the managed forwarding elements further comprises configuring the second managed forwarding element to send a second forwarding state information request to a fourth managed forwarding element when the forwarding state information repository does not have the requested forwarding state information.

5. The method of claim 4, wherein the second managed forwarding element belongs to a first group of managed forwarding elements and the fourth managed forwarding element belongs to a second group of managed forwarding elements, wherein the second managed forwarding element is coupled to the fourth managed forwarding element and no other managed forwarding element of the first group of managed forwarding elements is coupled to any other managed forwarding element of the second group of managed forwarding elements, wherein managed forwarding elements in each group are coupled to each other in a full tunnel mesh configuration.

6. The method of claim 1, wherein the forwarding state information repository includes a plurality of key and value pairs, wherein the forwarding state information request includes a key.

7. The method of claim 6, wherein each key and value pair is associated with a time indicator that indicates an amount of time during which the key and value pair is valid.

8. The method of claim 1, wherein the first and third managed forwarding elements are managed edge forwarding elements that directly interface with sources or destinations of packets.

9. The method of claim 8, wherein the second managed forwarding element is a second-level managed forwarding element, wherein the second-level managed forwarding element facilitates communications between two managed edge forwarding elements, wherein the second-level managed forwarding element does not directly interface with the sources and destinations of packets.

10. A computer configured as a host for managing network traffic to forward, the computer comprising:

a set of processing units;

a software forwarding element that operates on at least one processing unit in the set of processing units, the software forwarding element for processing a packet to forward the packet;

an information repository comprising forwarding state information stored as a plurality of key and value pairs, wherein each key and value pair is associated with a time indicator that indicates an amount of time during which the key and value pair is valid; and

a lookup module that operates on at least one processing unit in the set of processing units, said lookup module for (i) providing information from the information repository to the software forwarding element that the software forwarding element needs in order to process the packet and (ii) sending an information request to another software forwarding element running in another host to obtain the information from the other software forwarding element when the information repository does not have the information.

11. The computer of claim 10 further comprising a registering module that operates on at least one processing unit in the set of processing units, said registering module for sending information regarding the software forwarding element to the other software forwarding element so that the other software forwarding element updates another information repository in the other host with said information regarding the software forwarding element.

12. The computer of claim 11, wherein the registering module is further for sending a request to the other software forwarding element to remove certain information from the other information repository in the other host.

13. The computer of claim 10, wherein the software forwarding element is an edge forwarding element that directly interfaces with sources and destinations of packets.

14. The computer of claim 13, wherein the other software forwarding element is a second-level managed forwarding element, wherein the second-level managed forwarding element facilitates communications between two managed edge forwarding elements, wherein the second-level managed switching element does not directly interface with the sources and destinations of packets.

15. A non-transitory machine readable medium storing a program which when executed by at least one processing unit manages a set of managed forwarding elements that forward data in a network, the set of managed forwarding elements comprising edge managed forwarding elements that directly interface with sources and destinations of packets and second-level managed forwarding elements that facilitate communications between sets of edge managed forwarding elements and do not directly interface with the sources and destinations of packets, the program comprising sets of instructions for:

computing forwarding state and sending the computed forwarding state to the managed forwarding elements, the forwarding state defining forwarding behaviors of the managed forwarding elements; and

configuring the managed forwarding elements to exchange forwarding state with each other, the set of instructions for configuring comprising sets of instructions for;

configuring a first edge managed forwarding element to send a forwarding state information request to a second-level managed forwarding element; and

configuring the second-level managed forwarding element (i) to respond to the forwarding state information request by looking up a forwarding state information repository and (ii) to update the forwarding state information repository with forwarding state information received from a second edge managed forwarding element.

16. The machine readable medium of claim 15, wherein the set of instructions for configuring the managed forwarding elements further comprises a set of instructions for configuring the third managed forwarding element to send forwarding state information regarding the third managed forwarding element to the second managed forwarding element.

17. The machine readable medium of claim 15, wherein the set of instructions for configuring the managed forwarding elements further comprises a set of instructions for configuring the third managed forwarding element to send a removal request to the second managed forwarding element to remove certain forwarding state information from the information repository.

18. The machine readable medium of claim 15, wherein the forwarding state information request is a first forwarding state information request, wherein the set of instructions for configuring the managed forwarding elements further comprises a set of instructions for configuring the second managed forwarding element to send a second forwarding state information request to a fourth managed forwarding element when the information repository does not have the requested forwarding state information.

19. The machine readable medium of claim 18, wherein the second managed forwarding element belongs to a first group of managed forwarding elements and the fourth managed forwarding element belongs to a second group of managed forwarding elements, wherein managed forwarding elements in each group are coupled to each other in a full tunnel mesh configuration.

20. The machine readable medium of claim 15, wherein the forwarding state information repository includes a plurality of key and value pairs, wherein the forwarding state information request includes a key.