# Patent

## Title
System and method for providing ethernet over network virtual hub scalability in a middleware machine environment

## Abstract

A system and method can support a middleware machine environment that include one or more gateway nodes. One or more gateways that resides on the one or more gateway nodes are provided in a subnet with a plurality of host servers, wherein each host server is associated with one or more virtual network interface cards (vNICs). The middleware machine environment also include a plurality of virtual hubs (vHUB) on the one or more gateways, with each vHUB associated with one or more said vNICs. The gateways are adapted to connect with an external network, and operate to forward a multicast packet to both the external network and the plurality of host servers via the plurality of vHUBs, and prevent multicast packet traffic loops between the subnet and the external network.

## Background
CLAIM OF PRIORITY
This application claims the benefit of priority on U.S. Provisional Patent Application No. 61/384,228, entitled “SYSTEM FOR USE WITH A MIDDLEWARE MACHINE PLATFORM” filed Sep. 17, 2010; U.S. Provisional Patent Application No. 61/484,390, entitled “SYSTEM FOR USE WITH A MIDDLEWARE MACHINE PLATFORM” filed May 10, 2011; U.S. Provisional Patent Application No. 61/493,330, entitled “STATEFUL SUBNET MANAGER FAILOVER IN A MIDDLEWARE MACHINE ENVIRONMENT” filed Jun. 3, 2011; U.S. Provisional Patent Application No. 61/493,347, entitled “PERFORMING PARTIAL SUBNET INITIALIZATION IN A MIDDLEWARE MACHINE ENVIRONMENT” filed Jun. 3, 2011; U.S. Provisional Patent Application No. 61/498,329, entitled “SYSTEM AND METHOD FOR SUPPORTING A MIDDLEWARE MACHINE ENVIRONMENT” filed Jun. 17, 2011, each of which applications are herein incorporated by reference.
COPYRIGHT NOTICE
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
FIELD OF INVENTION
The present invention is generally related to computer systems and software such as middleware, and is particularly related to supporting a middleware machine environment.
BACKGROUND
INFINIBAND® (IB) Architecture is a communications and management infrastructure that supports both I/O and interprocessor communications for one or more computer systems. An IB Architecture system can scale from a small server with a few processors and a few I/O devices to a massively parallel installation with hundreds of processors and thousands of I/O devices.
The IB Architecture defines a switched communications fabric allowing many devices to concurrently communicate with high bandwidth and low latency in a protected, remotely managed environment. An end node can communicate with over multiple IB Architecture ports and can utilize multiple paths through the IB Architecture fabric. A multiplicity of IB Architecture ports and paths through the network are provided for both fault tolerance and increased data transfer bandwidth.
These are the generally areas that embodiments of the invention are intended to address.
SUMMARY
Described herein is a system and method for supporting a middleware machine environment that include one or more gateway nodes. One or more gateways that resides on the one or more gateway nodes are provided in a subnet with a plurality of host servers, wherein each host server is associated with one or more virtual network interface cards (vNICs). The middleware machine environment also include a plurality of virtual hubs (vHUB) on the one or more gateways, with each vHUB associated with one or more said vNICs. The gateways are adapted to connect with an external network, and operate to forward a multicast packet to both the external network and the plurality of host servers via the plurality of vHUBs, and prevent multicast packet traffic loops between the subnet and the external network.



BRIEF DESCRIPTION OF THE FIGURES
FIG. 1 shows an illustration of an exemplary configuration for a middleware machine, in accordance with an embodiment of the invention.
FIG. 2 shows an illustration of a middleware machine environment, in accordance with an embodiment of the invention.
FIG. 3 shows an illustration of a middleware machine environment that provides Ethernet over IB (EOIB) vHUB scalability, in accordance with an embodiment of the invention.
FIG. 4 illustrates an exemplary flow chart for providing EOIB vHUB scalability in a middleware machine environment, in accordance with an embodiment of the invention.



DETAILED DESCRIPTION
Described herein is a system and method for providing a middleware machine or similar platform. In accordance with an embodiment of the invention, the system comprises a combination of high performance hardware (e.g. 64-bit processor technology, high performance large memory, and redundant INFINIBAND® and Ethernet networking) together with an application server or middleware environment, such as WebLogic Suite, to provide a complete Java EE application server complex which includes a massively parallel in-memory grid, that can be provisioned quickly, and that can scale on demand. In accordance with an embodiment of the invention, the system can be deployed as a full, half, or quarter rack, or other configuration, that provides an application server grid, storage area network, and INFINIBAND® (IB) network. The middleware machine software can provide application server, middleware and other functionality such as, for example, WebLogic Server, JRockit or Hotspot JVM, Oracle Linux or Solaris, and Oracle VM. In accordance with an embodiment of the invention, the system can include a plurality of compute nodes, one or more IB switch gateways, and storage nodes or units, communicating with one another via an IB network. When implemented as a rack configuration, unused portions of the rack can be left empty or occupied by fillers.
In accordance with an embodiment of the invention, referred to herein as “Sun Oracle Exalogic” or “Exalogic”, the system is an easy-to-deploy solution for hosting middleware or application server software, such as the Oracle Middleware SW suite, or Weblogic. As described herein, in accordance with an embodiment the system is a “grid in a box” that comprises one or more servers, storage units, an IB fabric for storage networking, and all the other components required to host a middleware application. Significant performance can be delivered for all types of middleware applications by leveraging a massively parallel grid architecture using, e.g. Real Application Clusters and Exalogic Open storage. The system delivers improved performance with linear I/O scalability, is simple to use and manage, and delivers mission-critical availability and reliability.
FIG. 1 shows an illustration of an exemplary configuration for a middleware machine, in accordance with an embodiment of the invention. As shown in FIG. 1, the middleware machine 100 uses a single rack configuration that includes two gateway network switches, or leaf network switches, 102 and 103 that connect to twenty-eight server nodes. Additionally, there can be different configurations for the middleware machine. For example, there can be a half rack configuration that contains a portion of the server nodes, and there can also be a multi-rack configuration that contains a large number of servers.
As shown in FIG. 1, the server nodes 106-109 can connect to the ports provided by the gateway network switches 102-103. Furthermore, each server machine can have connections to the two gateway network switches 102 and 103 separately. For example, the gateway network switch 102 connects to the port 1 of the servers 1-14 106 (14 connections) and the port 2 of the servers 15-28 107 (14 connections), and the gateway network switch 103 connects to the port 1 of the servers 15-28 108 (14 connections) and the port 2 of the servers 1-14 109 (14 connections).
In accordance with an embodiment of the invention, each gateway network switch can have multiple internal ports that are used to connect with different servers, and the gateway network switch can also have external ports that are used to connect with an external network, such as an existing data center service network 104-105 (12 10G connections).
In accordance with an embodiment of the invention, the middleware machine can include a separate storage system 110 that connects to the servers through the gateway network switches 102-103 using single (1) link. Additionally, the middleware machine can include a spine network switch 101 that connects to the two gateway network switches 102 and 103 using single (1) link. As shown in FIG. 1, there can be optionally two (2) links from the storage system to the spine network switch.
IB Fabric/Subnet
In accordance with an embodiment of the invention, an IB Fabric/Subnet in a middleware machine environment can contain a large number of physical hosts or servers, switch instances and gateway instances that are interconnected in a fat-tree topology.
FIG. 2 shows an illustration of a middleware machine environment, in accordance with an embodiment of the invention. As shown in FIG. 2, the middleware machine environment 200 includes an IB subnet or fabric 220 that connects with a plurality of end nodes. The IB subnet includes a plurality of subnet managers 211-214, each of which resides on one of a plurality of network switches 201-204. The subnet managers can communicate with each other using an in-band communication protocol 210, such as the Management Datagram (MAD)/Subnet Management Packet (SMP) based protocols or other protocol such as the Internet Protocol over IB (IPoIB).
In accordance with an embodiment of the invention, a single IP subnet can be constructed on the IB fabric allowing the switches to communicate securely among each other in the same IB fabric (i.e. full connectivity among all switches). The fabric based IP subnet can provide connectivity between any pair of switches when at least one route with operational links exists between the two switches. Recovery from link failures can be achieved if an alternative route exits by re-routing.
The management Ethernet interfaces of the switches can be connected to a single network providing IP level connectivity between all the switches. Each switch can be identified by two main IP addresses: one for the external management Ethernet and one for the fabric based IP subnet. Each switch can monitor connectivity to all other switches using both IP addresses, and can use either operational address for communication. Additionally, each switch can have a point-to-point IP link to each directly connected switch on the fabric. Hence, there can be at least one additional IP address.
IP routing setups allow a network switch to route traffic to another switch via an intermediate switch using a combination of the fabric IP subnet, the external management Ethernet network, and one or more fabric level point-to-point IP links between pairs of switches. IP routing allows external management access to a network switch to be routed via an external Ethernet port on the network switch, as well as through a dedicated routing service on the fabric.
The IB fabric includes multiple network switches with management Ethernet access to a management network. There is in-band physical connectivity between the switches in the fabric. In one example, there is at least one in-band route of one or more hops between each pair of switches, when the IB fabric is not degraded. Management nodes for the IB fabric include network switches and management hosts that are connected to the IB fabric.
A subnet manager can be accessed via any of its private IP addresses. The subnet manager can also be accessible via a floating IP address that is configured for the master subnet manager when the subnet manager takes on the role as a master subnet manager, and the subnet manager is un-configured when it is explicitly released from the role. A master IP address can be defined for both the external management network as well as for the fabric based management IP network. No special master IP address needs to be defined for point-to-point IP links.
In accordance with an embodiment of the invention, each physical host can be virtualized using virtual machine based guests. There can be multiple guests existing concurrently per physical host, for example one guest per CPU core. Additionally, each physical host can have at least one dual-ported Host Channel Adapter (HCA), which can be virtualized and shared among guests, so that the fabric view of a virtualized HCA is a single dual-ported HCA just like a non-virtualized/shared HCA.
The IB fabric can be divided into a dynamic set of resource domains implemented by IB partitions. Each physical host and each gateway instance in an IB fabric can be a member of multiple partitions. Also, multiple guests on the same or different physical hosts can be members of the same or different partitions. The number of the IB partitions for an IB fabric may be limited by the P_Key table size.
In accordance with an embodiment of the invention, a guest may open a set of virtual network interface cards (vNICs) on two or more gateway instances that are accessed directly from a vNIC driver in the guest. The guest can migrate between physical hosts while either retaining or having updated vNIC associates.
In accordance with an embodiment of the invention, switchs can start up in any order and can dynamically select a master subnet manager according to different negotiation protocols, for example an IB specified negotiation protocol. If no partitioning policy is specified, a default partitioning enabled policy can be used. Additionally, the management node partition and the fabric based management IP subnet can be established independently of any additional policy information and independently of whether the complete fabric policy is known by the master subnet manager. In order to allow fabric level configuration policy information to be synchronized using the fabric based IP subnet, the subnet manager can start up initially using the default partition policy. When fabric level synchronization has been achieved, the partition configuration that is current for the fabric can be installed by the master subnet manager.
Providing Ethernet Over IB (EOIB) vHUB Scalability
In accordance with an embodiment of the invention, the system can provide Ethernet over IB (EOIB) Level 2 (L2) subnet implementations that scales both in terms of the number of member host ports on the IB fabric, and in terms of the number of gateway ports connecting to the corresponding L2 subnet on the external Ethernet fabric.
FIG. 3 shows an illustration of a middleware machine environment that provides EOIB vHUB scalability, in accordance with an embodiment of the invention. As shown in FIG. 3, a middleware machine environment 300 includes an IB subnet/fabric 320, which can be connected with a plurality of host servers 304-307 and an external local area network (LAN) 301. The IB fabric includes several gateways 302-303, which are associated with different vNICs 321-328. Each gateway instance can reside on a gateway node 308-309 that contains one or more microprocessors, and the core gateway function in the gateway instance can be implemented in hardware using a “data path” operation.
In accordance with an embodiment of the invention, a gateway in the system can be associated with different vHUBs. Each vHUB defines a logical level 2 link on the IB fabric side that contains vNICs associated with the same gateway instance. The vNICs and the hosts that belong to the same vHUB can communicate with each other without involving the associated gateway instance.
In the example as shown in FIG. 3, vHUB I 311 on gateway A is associated with vNIC a 321 and vNIC c 323 on host server A, and vNIC e 325 on host server B. Hence, vNIC a, vNIC c, and vNIC e can communicate with each other without involving the associated gateway A. Also as shown in FIG. 3, vHUB II 312 on gateway A is associated with vNIC b 322 on host server A and vNIC f 326 on host server C; and vHUB III 313 on gateway B is associate with vNIC d 324 on host server B, and vNIC g 327 and vNIC h 328 on host server D.
In accordance with an embodiment of the invention, several vHUBs can represent the same logical Ethernet L2 link and/or the same level 3 (L3) IP subnet. In the example as shown in FIG. 3, gateway A 302 and gateway B 303 both connect to the same external LAN 301 via multiple gateway ports. Various vNICs 321-328 that belong to the different vHUBs 311-313 can be connected and can communicate with each other through the external LAN 301, or alternatively by routing logic implemented by hosts on the IB fabric.
In accordance with an embodiment of the invention, a separate IP subnet (IPoIB or EoIB) can be provided on the IB fabric side for handling high bandwidth IP traffic between the hosts on the IB fabric, and between the hosts and the external LAN. This separate IP subnet on the IB fabric side can avoid wasting gateway bandwidth for traffic among hosts on the IB fabric. Additionally, when multiple IP subnets are not desirable, it can be useful to allow communication between vNICs that belongs to different vHUBs on the internal IB fabric.
In the example as shown in FIG. 3, when multiple vHUBs 311-313 are connected together, a multicast packet can be forwarded to both the external LAN 301 through the gateway instances 302-303 and to the member host ports on the host servers 304-307 in the IB fabric. For example, a first gateway port in the IB fabric 302 can send a multicast packet to an external LAN 301, which may send the multicast packet back to a second gateway port in the IB fabric 320. The second gateway port can in turn forward the multicast packet again on the IB fabric. This can lead to traffic loops between the IB fabric 320 and the external network 301. Additionally, an internal vNIC 321-328 and a gateway port may receive multiple versions of the same logical packet.
In order to solve the inbound packet loop problem that concerns traffic from external network to the IB fabric, the gateway instances can forward incoming multicast packets to an IB multicast group that represents a private vHUB, which has a single gateway member and allows each vNIC to be a member of a single private vHUB.
In order to solve the outbound packet loop problem that concerns traffic from IB fabric to external network, each gateway instance can detect if a multicast packet that is received from the local IB fabric is originating from a vNIC in its private vHUB. The gateway instance can proceed to forward the multicast packet to the external network if the multicast packet is originating from a vNIC in its private vHUB. Dedicated hardware logic can be used to make such decisions. In one example, this dedicated hardware logic can use either information about the local vNICs, or one or more sets of range registers for source Media Access Control (MAC) addresses in the private vHUB.
In accordance with an embodiment of the invention, an alternative approach can require that multicast packets forwarded between different private vHUBs have to involve the external LAN, such that the underlying IB multicast groups are always limited to a single private vHUB. At the same time, unicast traffic can span multiple vHUBs. This alternative approach can solve the inbound loop problem and can also ensure that only a single version of a multicast packet is forwarded from the IB fabric to the external LAN.
In accordance with an embodiment of the invention, communication between vNICs belonging to different vHUBs can be implemented without depending on connectivity between the external gateway ports via the external Ethernet LAN. For unicast traffic, the host vNIC driver can explicitly send a single packet to a destination port on the IB fabric that the destination MAC/vNIC is associated with. Also, the host vNIC driver can send the single packet to a destination vNIC that belongs to a different vHUB. For multicast traffic, the system can ensure that only a single gateway instance forwards a specific multicast packet from a specific host or a vNIC to the external LAN. And, the multiple gateway instances, which receive a same logical multicast packet, may not forward the same logical multicast packet from external LAN to the same hosts or vNICs on the IB fabric.
In accordance with an embodiment of the invention, a special global vHUB multicast group can avoid dependency on the external LAN for multicast forwarding between private vHUBs, and also ensure that only a single version of a multicast packet is forwarded from the IB fabric to the external LAN. This special global vHUB multicast group can include only a single gateway instance and all relevant vNICs on the IB fabric. Using this approach, the system can avoid creating loops for traffic between the IB fabric and the external LAN. Furthermore, in order to avoid receiving multiple copies of multicast packets originating from a vNIC in another private vHUB, the EoIB driver can include logic to discard a multicast packet arriving from the gateway in its private vHUB, when the source MAC of the multicast packet is from a vNIC in the corresponding global vHUB.
A limitation of this approach is that more bandwidth may be consumed on the IB fabric because of packet forwarding in both the global vHUB as well as in the various private vHUBs that receive the packet from the external LAN. Also, the restriction of only a single egress gateway instance for sending multicast packets may require that bonding and other host based IP multi-pathing schemes depend on global-vHUB reconfiguration in order to restore external multicast sending capability after failure of the current egress gateway instance. Thus, the multicast bandwidth from the IB fabric to the external LAN may also be limited by the single egress gateway instance.
In accordance with an embodiment of the invention, the system can manage the communication between vNICs belonging to different vHUBs using a source MAC address filtering approach. In the example as shown in FIG. 3, each gateway instance 302-303 in the IB fabric 320 can detect whether a source MAC address of a multicast packet received from an external LAN 301 belongs to a relevant vNIC 321-328 on the local IB fabric 320.
In accordance with an embodiment of the invention, the system can use one or more sets of range registers that define source MAC addresses belonging to relevant vNICs on the local IB fabric, in order to prevent sending a multicast packet in loops between the IB fabric and the external LAN that wastes network bandwidth resources, and ensure that the internal vNIC or gateway ports will not receive duplicated versions of a same logic multicast packet.
In accordance with an embodiment of the invention, the system can use a dedicated multicast group to distribute multicast packets to vNICs on the IB fabric, but not to any gateway instances. In order to ensure that exactly one copy of a multicast packet is sent out to the external LAN via exactly one gateway external port, the vNIC driver can send the packet to a single gateway (e.g. the one associated with the vHUB that the local vNIC belongs to). This multicast packet can then be received by other gateway external ports via the external Ethernet LAN and be replicated to vNICs belonging to other vHUBs.
The receiving vNIC drivers can determine that the source MAC in the packet belongs to a vNIC on the IB fabric that is part of the same logical subnet. Then, the vNIC drivers can discard the packet since the packet have already been, or will be, received via the said dedicated multicast group on the IB fabric. On the other hand, if the received multicast packet source address is determined to belong to a station on the external Ethernet LAN (i.e. as opposed to a vNIC on the local IB fabric), the multicast packet can be processed accordingly.
In accordance with an embodiment of the invention, with a scheme for filtering out copies of multicast packets, it is possible to use one global multicast group to forward multicast packets within the global vHUB on the IB fabric, and it is also possible to allow the sending EoIB driver to explicitly send another packet copy to be forwarded by the gateway instance in its private vHUB, for example via unicast. This scheme allows any number of gateway instances to be used as egress ports for outbound MC traffic (i.e. one active egress gateway per private vHUB).
In accordance with an embodiment of the invention, a hybrid L2 link can be used in an IB fabric, in which case a single IB fabric internal EoIB vHUB, which is similar to an IPoIB link, can be combined with one or more vHUBs that are only used for external traffic. The gateway's ability to filter multicast packets from the external LAN based on source address can prevent wasting of IB fabric bandwidth on duplicate multicast packets.
In accordance with an embodiment of the invention, for the situations when the IPoIB Connected Mode (CM) provides better bandwidth than EoIB based IP traffic, the IPoIB CM can be merged with EoIB in order to allow a single IP subnet to span any number of nodes on the IB fabric as well as any number of gateway instances and nodes on the external LAN, while still providing the best possible bandwidth between any pair of endpoints.
FIG. 4 illustrates an exemplary flow chart for providing scalability in a middleware machine environment, in accordance with an embodiment. As shown in FIG. 4, at step 401, one or more gateways can be provided in a subnet with a plurality of host servers, wherein each host server is associated with one or more virtual network interface cards (vNICs). Then, at step 402, a plurality of virtual hubs (vHUBs) can be provided on the one or more gateways, wherein each vHUB is associated with one or more said VNICs. Additionally, the one or more gateways can be connected with an external network, at step 403. Also, the one or more gateways can forward a multicast packet to both the external network and the plurality of host servers via the plurality of vHUBs at step 404. Finally, at step 405, the one or more gateways can prevent multicast packet traffic loops between the subnet and the external network.
The present invention may be conveniently implemented using one or more conventional general purpose or specialized digital computer, computing device, machine, or microprocessor, including one or more processors, memory and/or computer readable storage media programmed according to the teachings of the present disclosure. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art.
In some embodiments, the present invention includes a computer program product which is a storage medium or computer readable medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the present invention. The storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
The foregoing description of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to the practitioner skilled in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalence.

## Claims

1. A method for supporting a network having an InfiniBand architecture, the network including a subnet comprising a first gateway and a second gateway in communication with an external Ethernet network, a plurality of host servers and a plurality of virtual network interface cards (vNICs) wherein each host server is associated with one or more of said plurality of vNICs, said method comprising:
providing a first private virtual hub (vHUB) on said first gateway wherein a first subset of said plurality of vNICs is in communication with said first vHUB;
providing a second vHUB on said second gateway wherein a second subset of said plurality of vNICs is in communication with said second vHUB, and said first vHUB is in communication with said second vHUB;
receiving at said first vHUB a first multicast packet originating from a vNIC in said first subset of vNICs;
detecting with said first gateway that said first multicast packet originated from said first subset of vNICs, and forwarding said first multicast packet from said first gateway to said external Ethernet network, and to host servers associated with the first subset of vNICs; and
receiving at said first vHUB a second multicast packet originating from a vNIC in said second subset of vNICs;
detecting with said first gateway that said second multicast packet did not originate from said first subset of vNICs, and forwarding said second multicast packet from said first gateway to host servers associated with the first subset of vNICs without forwarding said second multicast packet to the external Ethernet network;
receiving at said second vHUB said first multicast packet originating from said vNIC in said first subset of vNICs;
detecting with said second gateway that said first multicast packet did not originate from said second subset of vNICs, and forwarding said first multicast packet from said second gateway to host servers associated with the second subset of vNICs without forwarding said first multicast packet to the external Ethernet network;
receiving at said second vHUB said second multicast packet originating from said vNIC in said second subset of vNICs; and
detecting with said second gateway that said second multicast packet originated from said second subset of vNICs, and forwarding said multicast packet from said second gateway to said external Ethernet network, and to host servers associated with the second subset of vNICs;
whereby only a single copy of said first multicast packet is transmitted from said network having the InfiniBand architecture to said external Ethernet network via said first gateway, and whereby only a single copy of said second multicast packet is transmitted from said network having the InfiniBand architecture to said external Ethernet network via said second gateway.

2. The method of claim 1, wherein each of said first gateway and second gateway includes a dedicated detecting hardware logic, and wherein:
detecting with said first gateway that said first multicast packet originated from said first subset of vNICs comprises detecting with said dedicated hardware logic of said first gateway using information about the first subset of vNICs that said first multicast packet originated from said first subset of vNICs;
detecting with said first gateway that said second multicast packet did not originate from said first subset of vNICs comprises detecting with said dedicated hardware logic of said first gateway using information about the first subset of vNICs that said second multicast packet did not originate from said first subset of vNICs;
detecting with said second gateway that said first multicast packet did not originate from said second subset of vNICs comprises detecting with said dedicated hardware logic of said second gateway using information about the first subset of vNICs that said first multicast packet did not originate from said first subset of vNICs; and
detecting with said second gateway that said second multicast packet originated from said second subset of vNICs comprises detecting with said dedicated hardware logic of said second gateway using information about the first subset of vNICs that said second multicast packet originated from said first subset of vNICs.

3. The method of claim 1, wherein each of said first gateway and second gateway includes a dedicated detecting hardware logic, and wherein:
detecting with said first gateway that said first multicast packet originated from said first subset of vNICs comprises detecting with said dedicated hardware logic of said first gateway using range registers for Media Access Control (MAC) addresses in the first vHUB that said first multicast packet originated from said first subset of vNICs;
detecting with said first gateway that said second multicast packet did not originate from said first subset of vNICs comprises detecting with said dedicated hardware logic of said first gateway using range registers for Media Access Control (MAC) addresses in the first vHUB that said second multicast packet did not originate from said first subset of vNICs;
detecting with said second gateway that said first multicast packet did not originate from said second subset of vNICs comprises detecting with said dedicated hardware logic of said second gateway using range registers for Media Access Control (MAC) addresses in the second vHUB that said first multicast packet did not originate from said first subset of vNICs; and
detecting with said second gateway that said second multicast packet originated from said second subset of vNICs comprises detecting with said dedicated hardware logic of said second gateway using range registers for Media Access Control (MAC) addresses in the second vHUB that said second multicast packet originated from said first subset of vNICs.

4. The method of claim 1, further comprising:
providing a global vHUB multicast group in communication with all of said plurality of vNICs in the subnet and only said first gateway;
receiving an inbound multicast packet from said external Ethernet network at said first gateway, and transmitting said inbound multicast packet to each of said plurality of vNICs in the subnet via said global vHUB multicast group.

5. The method of claim 1, wherein the first gateway and second gateway reside on a first network switch and a second network switch respectively.

6. The method of claim 1, wherein the first gateway and second gateway reside on a first network switch and a second network switch respectively, and wherein each of said first network switch and second network switch has an external port connected to said external Ethernet network and a plurality of internal ports connected to host servers of said plurality of hosts servers.

7. The method of claim 1, further comprising:
managing communications between vNICs is said first subset of vNICs and vNICs in said second subset of vNICs using source media access control (MAC) address filtering.

8. A system for supporting a middleware machine environment connected to an external Ethernet network, the system comprising:
a network having an InfiniBand architecture, the network comprising a subnet, said subnet comprising
a first gateway in communication with said external Ethernet network, said first gateway comprising a first private virtual hub (vHUB), and one or more microprocessors,
a second gateway in communication with said external Ethernet network, said second gateway comprising a second private virtual hub (vHUB), and one or more microprocessors,
a plurality of host servers and a plurality of virtual network interface cards (vNICs), wherein each host server is associated with one or more of said plurality of vNICs,
wherein a first subset of said plurality of vNICs is in communication with said first vHUB, a second subset of said plurality of vNICs is in communication with said second vHUB, and said first vHUB is in communication with said second vHUB;

wherein, in response to receiving at said first vHUB a first multicast packet originating from a vNIC in said first subset of vNICs, said first gateway selectively forwards, responsive to detecting that said first multicast packet originated from said first subset of vNICs, said first multicast packet to said external Ethernet network, and to host servers associated with the first subset of vNICs; and
wherein, in response to receiving at said first vHUB a second multicast packet originating from a vNIC in said second subset of vNICs, said first gateway selectively forwards, responsive to detecting that said second multicast packet did not originate from said first subset of vNICs, said second multicast packet to host servers associated with the first subset of vNICs without forwarding said second multicast packet to the external Ethernet network;
wherein, in response to receiving at said second vHUB said first multicast packet originating from said vNIC in said first subset of vNICs, said second gateway selectively forwards, responsive to detecting that said first multicast packet did not originate from said second subset of vNICs, said first multicast packet to host servers associated with the second subset of vNICs without forwarding said first multicast packet to the external Ethernet network; and
wherein, in response to receiving at said second vHUB said second multicast packet originating from said vNIC in said second subset of vNICs, said second gateway selectively forwards, responsive to detecting that said second multicast packet originated from said second subset of vNICs, said multicast packet to said external Ethernet network, and to host servers associated with the second subset of vNICs;
whereby only a single copy of said first multicast packet is transmitted from said network having the InfiniBand architecture to said external Ethernet network via said first gateway, and whereby only a single copy of said second multicast packet is transmitted from said network having the InfiniBand architecture to said external Ethernet network via said second gateway.

9. The system according to claim 8, further comprising:
a plurality of network switches, wherein the first gateway and second gateway reside on the plurality of network switches.

10. The system according to claim 9, wherein:
each said network switch provides one or more external ports that are used to connect with the external Ethernet network, and one or more internal ports that are used to connect with the plurality of host servers.

11. The system according to claim 8, wherein:
said first gateway includes multiple vHUBs.

12. The system according to claim 8, wherein:
the vNICs and host servers that belong to a same vHUB can communicate with each other without involving an associated gateway instance.

13. The system according to claim 8, wherein:
the vNICs and host servers that belong to different vHUBs can communicate with each other through corresponding gateway external ports and the external Ethernet network.

14. The system according to claim 8, wherein:
the first and second gateways operate to prevent an internal vNIC or a gateway port from receiving multiple versions of a same logical packet.

15. The system according to claim 8, wherein:
the first and second gateways operate to forward one or more incoming multicast packets received from the external Ethernet network to a multicast group.

16. The system according to claim 8, wherein:
the first and second gateways operate to use one or more sets of range registers to define different source MAC addresses associated with said plurality of vNICs.

17. The system according to claim 8, wherein:
the first and second gateways operate to manage communication between vNICs belonging to different vHUBs using a source media access control (MAC) address filtering approach.

18. The system according to claim 8, wherein:
the first and second gateways each include dedicated hardware logic that uses either information about the vNICs, or one or more sets of range registers for source Media Access Control (MAC) addresses in the private vHUB, to detect whether the first and second multicast packet originated from the first subset of vNICs in communication with said first vHUB or the second subset of vNICs in communication with said second vHUB.

19. The system according to claim 8, further comprising:
a global vHUB multicast group that include only a single gateway instance and all of said plurality of vNICs in the subnet.

20. A non-transitory computer readable medium having instructions stored thereon for supporting a network having an InfiniBand architecture, the network including a subnet comprising a first gateway and a second gateway in communication with an external Ethernet network and a plurality of host servers and a plurality of virtual network interface cards (vNICs) wherein each host server is associated with one or more of said plurality of vNICs, which instructions, when executed, cause a system to perform steps comprising:
providing a first private virtual hub (vHUB) on said first gateway wherein a first subset of said plurality of vNICs is in communication with said first vHUB;
providing a second vHUB on said second gateway wherein a second subset of said plurality of vNICs is in communication with said second vHUB, and said first vHUB is in communication with said second vHUB;
receiving at said first vHUB a first multicast packet originating from a vNIC in said first subset of vNICs;
detecting with said first gateway that said first multicast packet originated from said first subset of vNICs, and forwarding said first multicast packet from said first gateway to said external Ethernet network, and host servers associated with the first subset of vNICs; and
receiving at said first vHUB a second multicast packet originating from a vNIC in said second subset of vNICs;
detecting with said first gateway that said second multicast packet did not originate from said first subset of vNICs, and forwarding said second multicast packet from said first gateway to host servers associated with the first subset of vNICs without forwarding said second multicast packet to the external Ethernet network;
receiving at said second vHUB said first multicast packet originating from said vNIC in said first subset of vNICs;
detecting with said second gateway that said first multicast packet did not originate from said second subset of vNICs, and forwarding said first multicast packet from said second gateway to host servers associated with the second subset of vNICs without forwarding said first multicast packet to the external Ethernet network;
receiving at said second vHUB said second multicast packet originating from said vNIC in said second subset of vNICs;
detecting with said second gateway that said second multicast packet originated from said second subset of vNICs, and forwarding said multicast packet from said second gateway to said external Ethernet network, and host servers associated with the second subset of vNICs; and
whereby only a single copy of said first multicast packet is transmitted from said network having the InfiniBand architecture to said external Ethernet network via said first gateway, and whereby only a single copy of said second multicast packet is transmitted from said network having the InfiniBand architecture to said external Ethernet network via said second gateway.