Method and mechanism for efficiently managing flows

Patent metadata

Field	Value
Publication number	US-10511487-B2
Application number	US-201916364158-A
Country	US
Kind code	B2
Filing date	Mar 25, 2019
Priority date	Mar 8, 2016
Publication date	Dec 17, 2019
Grant date	Dec 17, 2019

Abstract

Some embodiments provide a novel method for installing flows of a desired network state in an actualized network state of a managed forwarding element. In some embodiments, the method maintains a flow output table based on flow events received from a computation engine for computing desired state, and from a set of managed forwarding elements on which the computed desired state is installed. The method of some embodiments then installs flows on the set of managed forwarding elements based on the flow output table.

First claim

We claim:

1. For a network controller that manages a flow-based managed forwarding element (MFE), a method comprising:
maintaining a flow entry output table comprising:
a first set of records for flow entries generated by the network controller for the MFE and determined to have a matching flow entry installed on the MFE;
a second set of records for flow entries generated by the network controller for the MFE but without a matching flow entry yet installed on the MFE; and
a third set of records for flow entries generated by the network controller and determined to have (i) a same matching expression as another flow entry in one of the first and second sets of records and (ii) a different action than the flow entry with the same matching expression; and

when a record for a first flow entry with a particular match condition is removed from one of the first and second sets of records and a record for a second flow entry with the particular match condition is in the third set of records, moving the record for the second flow entry from the third set of records to the second set of records for the second flow entry to be installed on the MFE.

2. The method of claim 1 , wherein the record for the first flow entry with the particular match condition is removed from the first set of records by moving the first flow entry to a fourth set of records of the flow entry output table.

3. The method of claim 2 , wherein the fourth set of records is for flow entries installed on the MFE but which the network controller has either (i) not generated for the MFE or (ii) indicated as flow entries to be removed from the MFE.

4. The method of claim 3 further comprising using the flow entry output table to direct the MFE to install the second flow entry and remove the first flow entry.

5. The method of claim 1 , wherein the flow entries generated by the network controller describe a desired network state and the flow entries installed on the MFE describe an actualized network state, wherein the method further comprises using the flow entry output table to match the actualized network state to the desired network state.

6. The method of claim 1 , wherein each flow entry comprises (i) a matching expression for matching against packets to be handled by the flow entry and (ii) an action that describes an action for the MFE to perform on packets that match the matching expression of the flow entry.

7. The method of claim 1 further comprising, prior to moving the record for the second flow entry, receiving a flow event from a central network controller that specifies to remove the second flow entry from the MFE.

8. The method of claim 7 , wherein the flow event is a first flow event, the method further comprising, prior to receiving the first flow event, receiving a second flow event from the central network controller that specifies to add the first flow entry to the MFE.

9. The method of claim 1 , wherein the network controller is a local network controller that executes on a same host computer as the MFE.

10. The method of claim 9 , wherein the network controller provides data to a plurality of local network controllers, wherein each respective local network controller executes on a same respective host computer as a respective MFE that the respective local network controller manages.

11. A non-transitory machine readable medium storing a network controller program which when executed by at least one processing unit manages a flow-based managed forwarding element (MFE), the network controller program comprising sets of instructions for:
maintaining a flow entry output table comprising:
a first set of records for flow entries generated by the network controller for the MFE and determined to have a matching flow entry installed on the MFE;
a second set of records for flow entries generated by the network controller for the MFE but without a matching flow entry yet installed on the MFE; and
a third set of records for flow entries generated by the network controller and determined to have (i) a same matching expression as another flow entry in one of the first and second sets of records and (ii) a different action than the flow entry with the same matching expression; and

when a record for a first flow entry with a particular match condition is removed from one of the first and second sets of records and a record for a second flow entry with the particular match condition is in the third set of records, moving the record for the second flow entry from the third set of records to the second set of records for the second flow entry to be installed on the MFE.

12. The non-transitory machine readable medium of claim 11 , wherein the record for the first flow entry with the particular match condition is removed from the first set of records by moving the first flow entry to a fourth set of records of the flow entry output table.

13. The non-transitory machine readable medium of claim 12 , wherein the fourth set of records is for flow entries installed on the MFE but which the network controller has either (i) not generated for the MFE or (ii) indicated as flow entries to be removed from the MFE.

14. The non-transitory machine readable medium of claim 13 , wherein the network controller program further comprises a set of instructions for using the flow entry output table to direct the MFE to install the second flow entry and remove the first flow entry.

15. The non-transitory machine readable medium of claim 11 , wherein the flow entries generated by the network controller describe a desired network state and the flow entries installed on the MFE describe an actualized network state, wherein the network controller program further comprises a set of instructions for using the flow entry output table to match the actualized network state to the desired network state.

16. The non-transitory machine readable medium of claim 11 , wherein each flow entry comprises (i) a matching expression for matching against packets to be handled by the flow entry and (ii) an action that describes an action for the MFE to perform on packets that match the matching expression of the flow entry.

17. The non-transitory machine readable medium of claim 11 , wherein the network controller program further comprises a set of instructions for, prior to moving the record for the second flow entry, receiving a flow event from a central network controller that specifies to remove the second flow entry from the MFE.

18. The non-transitory machine readable medium of claim 17 , wherein the flow event is a first flow event, the network controller program further comprising a set of instructions for, prior to receiving the first flow event, receiving a second flow event from the central network controller that specifies to add the first flow entry to the MFE.

19. The non-transitory machine readable medium of claim 11 , wherein the network controller is a local network controller that executes on a same host computer as the MFE.

20. The non-transitory machine readable medium of claim 19 , wherein the network controller provides data to a plurality of local network controllers, wherein each respective local network controller executes on a same respective host computer as a respective MFE that the respective local network controller manages.

Assignees

• Nicira Inc

Inventors

• Lim Harold Vinson C
• Gude Natasha

Classifications

• H04L12/28

  characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks] (wireless communication networks H04W {; arrangements for dividing the transmission path H04W40/00}) · CPC title

• H04L41/0813

  characterised by the conditions triggering a change of settings · CPC title

• H04L45/54

  Organization of routing tables · CPC title

• H04L43/18

  Protocol analysers · CPC title

• H04L45/38

  Flow based routing · CPC title