Packet processing for logical datapath sets

• US 10,021,019 B2
• Filed: 07/06/2012
• Issued: 07/10/2018
• Est. Priority Date: 07/06/2010
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Koponen, Teemu, Amidon, Keith E., Ingram, Paul S., Casado, Martin
• Primary Examiner(s): Strange, Aaron
• Application Number:
  US13/543,784
• Publication Number:
  US 20130058335A1
• Time in Patent Office: 2,195 Days
• Field of Search: 709225
• 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/0897 by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
• 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/22 Alternate routing
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 47/00 Traffic control in data switching networks arrangements for detecting or preventing errors in the information received H04L1/00
• CPC Class Codes: H04L 49/25 Routing or path finding in a switch fabric
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Some embodiments provide a method that processes network data through a network. The method receives a packet destined for a network host associated with a logical datapath set implemented by a set of managed edge switching elements and a set of managed non-edge switching elements in the network. The method determines whether the packet is a known packet. When the packet is a known packet, the method forwards the packet to a managed switching element in the set of managed edge switching elements for forwarding to the network host. When the packet is not a known packet, the method forwards the packet to a managed switching element in the set of managed non-edge switching elements for further processing.

Claims

1. For a first managed edge switching element (MESE), a method for processing packets for a logical datapath set (LDPS) implemented by the first MESE and a plurality of other MESEs, the method comprising:

at the first MESE, receiving a packet having a destination address associated with the LDPS from a source machine that couples directly to the first MESE, wherein each particular MESE that implements the LDPS has at least one machine associated with the LDPS coupled directly to the particular MESE;

determining whether the destination address is known to the first MESE;

when the destination address of the packet is known to the first MESE, transmitting the packet via a first tunnel to a second MESE, in the plurality of other MESEs to which the destination address corresponds; and

when the destination address is unknown to the first MESE, transmitting the packet via a second tunnel to a managed non-edge switching element (MNESE) of a plurality of MNESEs and not to any other MESE in the plurality of other MESEs, wherein the MNESE receives the packet and forwards the packet to the destination address through a third MESE of the plurality of other MESEs, wherein each MNESE of the plurality of MNESEs stores data for forwarding packets to a plurality of destination addresses and does not receive packets directly from the machines associated with the LDPS.

2. The method of claim 1, wherein the determining comprises performing a lookup operation on a forwarding table to determine whether the destination address is known.

3. The method of claim 2, wherein the destination address is determined to be known when the forwarding table includes an entry that matches a media access control (MAC) address that is specified in a header of the packet.

4. The method of claim 3, wherein the MAC address is a destination MAC address.

5. The method of claim 2, wherein the destination address is determined to be unknown when the forwarding table does not include an entry that matches a MAC address that is specified in a header of the packet.

6. The method of claim 1, wherein the MESEs comprise a set of managed software switching elements.

7. The method of claim 1, wherein the MESEs comprise a set of managed virtual switching elements.

8. The method of claim 1, wherein the MESEs comprise a set of managed hardware switching elements.

9. The method of claim 1, wherein the MNESE floods a network with a set of packets when the MNESE does not know the destination address, each particular packet in the set of packets including a destination MAC address specified in the header of the packet as the particular packet'"'"'s destination MAC address.

10. The method of claim 1, wherein the MNESE identifies the destination address of the packet before transmitting the packet to the third MESE.

11. The method of claim 1, wherein the second and third MESEs are the same MESE.

12. The method of claim 1, wherein the MNESE uses a third tunnel to forward the packet through the third MESE.

13. The method of claim 1, wherein the LDPS is a first LDPS that defines a first logical switching element to forward packets between a first plurality of machines that are associated with one another, wherein the first MESE and at least one other MESE in the plurality of other MESEs implements a second LDPS that defines a second logical switching element to forward packets between a second plurality of machines that are associated with one another.

14. A non-transitory machine readable medium storing a program which when executed by at least one processing unit processes packets for a logical datapath set (LDPS) implemented by a set of managed edge switching elements (MESEs), the program comprising sets of instructions for:

receiving, at a first MESE, a packet addressed to a destination machine associated with the LDPS from a source machine that couples directly to the first MESE, wherein each particular MESE that implements the LDPS has at least one machine associated with the LDPS coupled directly to the particular MESE;

determining whether the destination machine is known to the first MESE;

when the destination machine is known to the first MESE, transmitting the packet via a first tunnel to a second MESE in the set of MESEs to which the destination machine corresponds; and

when the destination machine is unknown to the first MESE, transmitting the packet via a second tunnel to a managed non-edge switching element (MNESE) of a plurality of MNESEs and not to any other MESE in the set of MESEs, wherein the MNESE receives the packet and forwards the packet to the identified destination machine through a third MESE in the set of MESEs, wherein each MNESE of the plurality of MNESEs stores data for forwarding packets to a plurality of destination machines and does not receive packets directly from the machines associated with the LDPS.

15. The non-transitory machine readable medium of claim 14, wherein the LDPS is a first LDPS, wherein the set of MESEs is further for implementing a second LDPS, wherein the set of MESEs isolates data for the first LDPS from data for the second LDPS.

16. The non-transitory machine readable medium of claim 14, wherein the set of instructions for determining comprises a set of instructions for performing a lookup operation on a forwarding table to determine whether the forwarding table includes an entry that matches a destination address that is specified in a header of the packet.

17. The non-transitory machine readable medium of claim 16, wherein the destination address is a destination media access control (MAC) address.

18. The non-transitory machine readable medium of claim 14, wherein the MNESE floods the network with a set of packets when the MNESE does not know of the destination machine, each particular packet in the set of packets including a destination MAC address specified in the header of the packet as the particular packet'"'"'s destination MAC address.

19. The non-transitory machine readable medium of claim 14, wherein the second and third MESEs are the same MESE.

20. The non-transitory machine readable medium of claim 14, wherein the source machine is one of a virtual machine and a physical machine.