Connectivity segment selection

• US 9,602,385 B2
• Filed: 12/18/2013
• Issued: 03/21/2017
• Est. Priority Date: 12/18/2013
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Tessmer, Alexander, Shen, Jianjun, Wang, Hua, Subramaniyam, Rahul Korivi
• Primary Examiner(s): Alia, Curtis A
• Application Number:
  US14/133,528
• Publication Number:
  US 20150172165A1
• Time in Patent Office: 1,189 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 12/1886 with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
• CPC Class Codes: H04L 12/462 LAN interconnection over a bridge based backbone
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 45/02 Topology update or discovery

Abstract

A novel method for fully utilizing the multicast or broadcast capability of a physical network is provided. The method identifies segments of the network within which broadcast traffic, multicast traffic, or traffic to unknown recipients (BUM traffic) is allowed or enabled. The identified segment encompasses parts of the network that the BUM traffic is able reach while excluding parts of the network nodes that the BUM traffic is unable to reach. Each identified segment includes network nodes that are interconnected by physical network hardware that supports BUM traffic. The method identifies multiple BUM traffic segments in a given network that each supports its own BUM traffic. The different BUM traffic segments are interconnected by physical network hardware that does not support BUM network traffic. Each identified segment is assigned an identifier that uniquely distinguishes the identified segment from other identified segments.

Claims

1. A system comprising:

a physical network having a plurality of connectivity segments, each connectivity segment supporting network traffic to unspecified recipients, wherein different connectivity segments are interconnected by network components that do not support network traffic to unspecified recipients; and

each connectivity segment comprising a plurality of host computers each executing a set of virtual machines, wherein each particular host computer of each particular connectivity segment is assigned a connectivity segment identifier that associates the particular host computer with the particular connectivity segment,

wherein to replicate, to a first connectivity segment, data messages that are distributed to unspecified recipients in a second connectivity segment, one host computer in the second connectivity segment sends a unicast message to one host computer in the first connectivity segment, which in response to the unicast message distributes data messages to unspecified recipients in the first connectivity segment.

2. The system of claim 1, wherein the network traffic to unspecified recipients is broadcast network traffic.

3. The system of claim 1, wherein the network traffic to unspecified recipients is multicast traffic to a group of virtual machines in the physical network.

4. The system of claim 1, wherein at least one connectivity segment comprises two or more different L3 subnets.

5. The system of claim 4, wherein at least one connectivity segment further comprises L3 routers that support network traffic to unspecified recipients between the different L3 subnets.

6. The system of claim 1, wherein the plurality of host computers execute network virtualization software.

7. The system of claim 1, wherein the network components that do not support traffic to unspecified recipients support unicast network traffic to specified recipients.

8. The system of claim 1, wherein connectivity segments are identified based on link layer connectivity.

9. The system of claim 1, wherein the connectivity segment identifier for a connectivity segment is based on a subnet IP address of a host computer in the connectivity segment.

10. A controller comprising:

a set of processing units; and

a non-transitory machine readable medium storing a program for execution by the set of processing units, the program comprising sets of instructions for;

defining a plurality of connectivity segments, each of which comprises a plurality of hosts, wherein each connectivity segment supports multicast traffic between said plurality of hosts; and

defining, for each particular connectivity segment, a particular host as a proxy for receiving, from a host of another connectivity segment, a request to generate multicast traffic to the plurality of hosts within the particular connectivity segment.

11. The controller of claim 10, wherein the plurality of connectivity segments are interconnected by network infrastructure that does not support multicast traffic.

12. The controller of claim 10, wherein the particular host for each connectivity segment is a tunnel endpoint for an overlay encapsulation network.

13. The controller of claim 10, wherein the particular host is a first host and the request is a first request for a first logical network, wherein a plurality of virtual machines that are in a plurality of different logical networks operate on the host of another connectivity segment, wherein the program further comprises a set of instructions for defining a second host of the particular connectivity segment as a proxy for receiving, from the host of another connectivity segment, a second request for a second logical network to generate multicast traffic to the plurality of hosts within the particular connectivity segment.

14. A method comprising:

at a first host machine that hosts a first set of virtual machines in a first network segment, storing segment identifier information for a plurality of host machines in a plurality of network segments, wherein the segment identifier information comprises a segment identifier that identifies a corresponding network segment for each host machine;

receiving a multicast message from a machine in the first network segment;

sending a multicast message to the first set of virtual machines and to a second host machine that hosts a second set of virtual machines in the first network segment; and

for the received multicast message, sending a unicast message to a proxy host machine for each of the other network segments of the plurality of network segments, each particular proxy host machine of each particular other segment for generating, based on the sent unicast message, a multicast message to other machines within the particular other segment.

15. The method of claim 14 wherein the second host machine has a same segment identifier as the first host machine.

16. The method of claim 14, wherein at least one network segment comprises host machines having different subnet addresses.

17. The method of claim 14, wherein each network segment is defined by broadcast, unknown unicast, or multicast (BUM) network traffic connectivity.

18. The method of claim 17, wherein the network does not support BUM traffic connectivity between the different network segments.

19. The method of claim 14, wherein the first set of virtual machines are in a plurality of different logical networks.

20. The method of claim 19, wherein the first host machine selects a different set of proxy host machines in the other network segments to act as proxies for the first host machine for different logical networks.

21. The method of claim 14, wherein the first host machine is a tunnel endpoint for an overlay encapsulation network.