Using transactions to compute and propagate network forwarding state

• US 9,306,843 B2
• Filed: 04/18/2013
• Issued: 04/05/2016
• Est. Priority Date: 04/18/2012
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Koponen, Teemu, Padmanabhan, Amar
• Primary Examiner(s): Phan, Tri H
• Application Number:
  US14/348,885
• Publication Number:
  US 20140247753A1
• Time in Patent Office: 1,083 Days
• Field of Search: 370229-240, 370254-258, 370351-356, 370389-401, 709/200, 709220-244, 709249-253
• US Class Current: 1/1
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/08 Configuration management of networks or network elements address allocation H04L61/50
• CPC Class Codes: H04L 41/0803 Configuration setting
• 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/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 43/0823 Errors, e.g. transmission errors
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/64 using an overlay routing layer
• CPC Class Codes: H04L 45/72 Routing based on the source address
• CPC Class Codes: H04L 49/70 Virtual switches

Abstract

For a controller for managing a network comprising several managed forwarding elements that forward data in the network, a method for configuring a managed forwarding element is described. The method generates a first set of flow entries for defining forwarding behaviors of the managed forwarding element based on a current network policy for a logical network implemented in the several managed forwarding elements. The method sends the first set of flow entries to the managed forwarding element in order for the managed forwarding element to forward data that the managed forwarding element directly receives from an end machine based on the current network policy. The method generates a second set of flow entries for modifying forwarding behaviors of the managed forwarding element based on a new network policy for the logical network. The method sends the second set of flow entries to the managed forwarding element in order for the managed forwarding element to forward the data based on the new network policy.

Claims

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

generating a first set of configuration data for configuring a managed forwarding element as a first-hop forwarding element for (i) receiving a packet directly from an end machine that is a source of the packet and (ii) forwarding the packet towards an end machine that is a destination of the packet;

generating a second set of configuration data for configuring a set of managed forwarding elements as non-first-hop forwarding elements for (i) receiving the packet not directly from the source end machine and (ii) forwarding the packet towards the destination end machine; and

sending the second set of configuration data to the set of managed forwarding elements prior to sending the first set of configuration data to the managed forwarding element.

2. The method of claim 1 further comprising:

before sending the second set of configuration data to the set of managed forwarding elements;

generating a third set of configuration data for (i) configuring the managed forwarding element as a first-hop forwarding element and (ii) configuring the managed forwarding element to attach version information to a particular packet that the managed forwarding element as a first-hop forwarding element receives and forwards;

generating a fourth set of configuration data for configuring the set of managed forwarding elements as non-first-hop forwarding elements;

sending the third set of configuration data to the managed forwarding element; and

sending the fourth set of configuration data to the set of managed forwarding elements,

wherein after receiving the second set of configuration data from the controller, the set of managed forwarding elements uses the version information to choose the fourth set of configuration data over the second set of configuration data to use to forward the particular packet that the set of managed switching elements as non-first-hop forwarding elements receive and forward.

3. The method of claim 2, wherein the version information has a size of a single binary bit.

4. The method of claim 2 further comprising:

sending the first set of configuration data to the managed forwarding element,

wherein the first set of configuration data is further for configuring the managed forwarding element to attach different version information to the packet that the set of managed forwarding elements as a first-hop forwarding element receives and forwards,

wherein after receiving the second set of configuration data, the set of managed forwarding elements uses the different version information to choose the second set of configuration data over the fourth set of configuration data to use to forward the packet that the set of managed switching elements receives as non-first-hop forwarding elements.

5. The method of claim 2 further comprising configuring the managed forwarding element to remove the third set of configuration data after a certain period of time elapses after receiving the first set of configuration data.

6. The method of claim 2 further comprising sending a command to the managed forwarding element to remove the third set of configuration data after receiving the first set of configuration data.

7. The method of claim 1, wherein the managed forwarding element operates in a host, wherein the source end machine operates within the same host.

8. The method of claim 1, wherein the second set of configuration data is further for configuring a particular managed forwarding element of the set of managed forwarding elements as a last-hop forwarding element for sending a packet, which the particular forwarding element receives as a non-first-hop forwarding element, to the destination end machine directly.

9. The method of claim 8, wherein the particular managed forwarding element operates in a host, wherein the destination end machine operates within the same host.

10. For a controller for managing a network comprising managed forwarding elements that forward data in the network, a method for configuring a set of managed forwarding elements, the method comprising:

generating (i) a first set of flow entries for configuring the set of managed forwarding elements as first-hop forwarding elements that forward data received directly from a set of end machines and (ii) a second set of flow entries for configuring the set of managed forwarding elements as non-first-hop forwarding elements that forward data not received from the set of end machines; and

sending the second set of flow entries to the set of managed forwarding elements prior to sending the first set of flow entries to the set of managed forwarding elements.

11. The method of claim 10 further comprising:

before sending the second set of flow entries;

generating a third set of flow entries for (i) configuring the set of managed forwarding elements as first-hop forwarding elements and (ii) configuring the set of managed forwarding elements to attach version information to data that the set of managed forwarding elements as first-hop forwarding elements receives and forwards;

generating a fourth set of flow entries for configuring the set of managed forwarding elements as non-first-hop forwarding elements; and

sending the third and fourth sets of flow entries to the set of managed forwarding elements,

wherein after receiving the second set of flow entries from the controller, the set of managed forwarding elements uses the version information to choose the fourth set of flow entries over the second set of flow entries to use to forward the data that the set of managed switching elements receives as non-first-hop forwarding elements.

12. The method of claim 11, wherein the version information has a size of a single binary bit.

13. The method of claim 11 further comprising:

sending the first set of flow entries to the set of managed forwarding elements,

wherein the first set of flow entries is further for configuring the set of managed forwarding elements to attach different version information to the data that the set of managed forwarding elements as first-hop forwarding elements receives and forwards,

wherein after receiving the second set of flow entries, the set of managed forwarding elements uses the different version information to choose the second set of flow entries over the fourth set of flow entries to use to forward the data that the set of managed switching elements receives as non-first-hop forwarding elements.

14. The method of claim 11 further comprising configuring the set of managed forwarding elements to remove the third and fourth sets of flow entries after a certain period of time elapses after receiving the first set of flow entries.

15. The method of claim 11 further comprising sending a command to the set of managed forwarding elements to remove the third and fourth sets of flow entries after receiving the first set of flow entries.

16. A non-transitory machine readable medium storing a program for configuring managed forwarding elements that forward data in a network, the program comprising sets of instructions for:

generating a first set of configuration data for configuring a managed forwarding element as a first-hop forwarding element for (i) receiving a packet directly from an end machine that is a source of the packet and (ii) forwarding the packet towards an end machine that is a destination of the packet;

generating a second set of configuration data for configuring a set of managed forwarding elements as non-first-hop forwarding elements for (i) receiving the packet not directly from the source end machine and (ii) forwarding the packet towards the destination end machine; and

sending the second set of configuration data to the set of managed forwarding elements prior to sending the first set of configuration data to the managed forwarding element.

17. The non-transitory machine readable medium of claim 16, wherein the program further comprises sets of instructions for:

before sending the second set of configuration data to the set of managed forwarding elements;

generating a third set of configuration data for (i) configuring the managed forwarding element as a first-hop forwarding element and (ii) configuring the managed forwarding element to attach version information to a particular packet that the managed forwarding element as a first-hop forwarding element receives and forwards;

generating a fourth set of configuration data for configuring the set of managed forwarding elements as non-first-hop forwarding elements;

sending the third set of configuration data to the managed forwarding element; and

sending the fourth set of configuration data to the set of managed forwarding elements,

wherein after receiving the second set of configuration data, the set of managed forwarding elements uses the version information to choose the fourth set of configuration data over the second set of configuration data to use to forward the particular packet that the set of managed switching elements as non-first-hop forwarding elements receive and forward.

18. The non-transitory machine readable medium of claim 17, wherein the program further comprises sets of instructions for:

sending the first set of configuration data to the managed forwarding element,

wherein the first set of configuration data is further for configuring the managed forwarding element to attach different version information to the packet that the set of managed forwarding elements as a first-hop forwarding element receives and forwards,

wherein after receiving the second set of configuration data, the set of managed forwarding elements uses the different version information to choose the second set of configuration data over the fourth set of configuration data to use to forward the packet that the set of managed switching elements receives as non-first-hop forwarding elements.

19. The non-transitory machine readable medium of claim 17, wherein the program further comprises a set of instructions for configuring the managed forwarding element to remove the third set of configuration data after a certain period of time elapses after receiving the first set of configuration data.

20. The non-transitory machine readable medium of claim 17, wherein the program further comprises a set of instructions for sending a command to the managed forwarding element to remove the third set of configuration data after receiving the first set of configuration data.

21. The non-transitory machine readable medium of claim 16, wherein the managed forwarding element operates in a host, wherein the source end machine operates within the same host.

22. A non-transitory machine readable medium storing a program for configuring a set of managed forwarding elements that forward data in a network, the program comprising sets of instructions for:

generating (i) a first set of flow entries for configuring the set of managed forwarding elements as first-hop forwarding elements that forward data received directly from a set of end machines and (ii) a second set of flow entries for configuring the set of managed forwarding elements as non-first-hop forwarding elements that forward data not received from the set of end machines; and

sending the second set of flow entries to the set of managed forwarding elements prior to sending the first set of flow entries to the set of managed forwarding elements.

23. The non-transitory machine readable medium of claim 22, wherein the program further comprises sets of instructions for:

before sending the second set of flow entries;

generating a third set of flow entries for (i) configuring the set of managed forwarding elements as first-hop forwarding elements and (ii) configuring the set of managed forwarding elements to attach version information to data that the set of managed forwarding elements as first-hop forwarding elements receives and forwards;

generating a fourth set of flow entries for configuring the set of managed forwarding elements as non-first-hop forwarding elements; and

sending the third and fourth sets of flow entries to the set of managed forwarding elements,

wherein after receiving the second set of flow entries, the set of managed forwarding elements uses the version information to choose the fourth set of flow entries over the second set of flow entries to use to forward the data that the set of managed switching elements receives as non-first-hop forwarding elements.

24. The non-transitory machine readable medium of claim 23, wherein the version information has a size of a single binary bit.

25. The non-transitory machine readable medium of claim 23, wherein the program further comprises sets of instructions for:

sending the first set of flow entries to the set of managed forwarding elements,

wherein the first set of flow entries is further for configuring the set of managed forwarding elements to attach different version information to the data that the set of managed forwarding elements as first-hop forwarding elements receives and forwards,

wherein after receiving the second set of flow entries, the set of managed forwarding elements uses the different version information to choose the second set of flow entries over the fourth set of flow entries to use to forward the data that the set of managed switching elements receives as non-first-hop forwarding elements.

26. The non-transitory machine readable medium of claim 23, wherein the program further comprises a set of instructions for configuring the set of managed forwarding elements to remove the third and fourth sets of flow entries after a certain period of time elapses after receiving the first set of flow entries.

27. The non-transitory machine readable medium of claim 23, wherein the program further comprises a set of instructions for sending a command to the set of managed forwarding elements to remove the third and fourth sets of flow entries after receiving the first set of flow entries.