Modern Ethernet switches continue to increase in scale, such as with respect to a higher port count per switch chip or device and a greater bandwidth per port. Some server (blade) enclosures are typically designed to support a fixed, small number of servers per enclosure, such as to support enterprise data centers, small and medium businesses (SMB), and/or remote/branch offices. Typically, these server enclosures also have slots, or bays, where a number of network switch modules are installed to provide connectivity between the servers/blades themselves, and between the servers/blades and external networks. In a single server enclosure, network connectivity can be optimized to a small, fixed number of server network interface card (NIC) connections. To achieve an optimum balance in such connectivity, network switch devices or chips, such as implemented via an application specific integrated circuit (ASIC) with high radix, can be utilized to increase port count and port bandwidth and to provide connectivity to more than one enclosure.
In a network system architecture, a group of enclosures can be implemented to form an enclosure group to provide connectivity for one or more computer systems installed in the enclosures of the enclosure group to a network. An enclosure group can include a primary enclosure, which can be configured as a blade enclosure with at least one network switch system installed (e.g., a blade switch), or a top-of-rack (ToR) enclosure that does not house a computer system, but instead only includes one or more network switch systems (e.g., a ToR switch). The network switch system in the primary enclosure can include a plurality of ports, such that one or more of the ports can be communicatively coupled to one or more external networks, and one or more of the other ports being coupled to a respective one or more downlink extension modules (DEMs) that are each provided in one or more separate respective sub-enclosures. In the example of the network switch system being installed in a blade enclosure, some of the ports can be communicatively coupled to the bays or slots in which the computer systems are installed in the same enclosure. Each of the primary enclosure and the one or more sub-enclosures can include one or more computer systems (e.g., servers), or blades, each including a network interface card (NIC) that can provide network connectivity to the network.
The NIC on computer systems that are installed within each of the sub-enclosures can be coupled to a respective port of the network switch system in the primary enclosure, such that the computer system(s) associated with each of the sub-enclosures can be provided network connectivity via the network switch system in the primary enclosure. The connectivity can be provided via the DEM in the sub-enclosure and the network connection between the DEM and the network switch system in the primary enclosure. Additionally, the network system architecture can include a plurality of primary enclosures, each including a network switch system coupled to respective DEMs in respective sets of sub-enclosures to form a network logical domain. Each of the primary enclosures can be communicatively coupled via the respective network switch systems, such as in a loop configuration, such that each of the network switch system can be communicatively coupled to a pair of network switch systems of a respective pair of primary enclosures via a first physical interface port and a second physical interface port, respectively, of the plurality of primary enclosures.
In the example of
In addition, the network system 10 includes a plurality of sub-enclosures (demonstrated as “SUB-ENCL”) 18. In the example of
Each of the sub-enclosures 18 includes a downlink extension module (DEM) 20 that can provide connectivity of a respective computer system to the network(s) 12. The DEM 20 in each of the first set of sub-enclosures 18 can be communicatively coupled to a respective one of the physical interface ports of the network switch system 16 of the respective one of the primary enclosures 14 (e.g., PRIMARY ENCLOSURE 1). Similarly, the DEM 20 in each of the second set of sub-enclosures 18 can be communicatively coupled to a respective one of the physical interface ports of the network switch system 16 of the respective one of the primary enclosures 14 (e.g., PRIMARY ENCLOSURE N). Therefore, the computer system associated with each of the sub-enclosures 18 can be communicatively coupled to the network(s) 12 via the network switch system 16 in the respective primary enclosures 14. As an example, each of the sub-enclosures 18 in a given enclosure group can be coupled to a single one of the network(s) 12 via a single physical interface port of the respective network switch system 16, redundantly to a single one of the network(s) 12 via multiple physical interface ports of the network switch system 16, to multiple separate networks 12 via respective physical interface ports of the network switch system 16, or a combination thereof.
Therefore, the network system 10 provides a network topology in which the high radix of the network switch systems 16 is largely utilized while providing flat network connectivity among associated computer systems to substantially mitigate latency. Therefore, the network system 10 provides a more efficient utilization of the high radix of the network switch systems 16 than typical network topologies (e.g., blade switch topologies) in which multiple blade servers are provided in a given enclosure, each with a respective network switch system. Such typical network topologies can result in the physical interface ports of the switches being trapped and/or unused, which can lead to an increased cost per connected server or device on the associated network topology. Additionally, the network system 10 is highly scalable based on adding additional enclosure groups (e.g., hundreds) that include a primary enclosure 14 and one or more sub-enclosures 18 to the network logical domain coupled to the network(s) 12, and can scale up to support higher lane speeds. For example, the network system 10 can be limited only by a number of switch-hops that can be tolerated by the applications running on the associated computer systems.
The blade switch enclosure group 50 includes a blade enclosure 52 that includes a blade server 54 and a blade switch system 56. The blade enclosure 52 can correspond to a primary enclosure 14 in the example of
The blade server 54 includes a network interface card (NIC) 58 that is coupled to the blade server 54 and can provide network interface for the blade server 54. As an example, the blade server 54 can be communicatively coupled to the blade switch system 56 through a backplane, and can have network connectivity based on the NIC 58 via the blade switch system 56. Therefore, the blade enclosure 52 can provide connectivity of the blade server 54 to the network(s) 12 via the blade switch system 56. In the example of
The blade switch enclosure group 50 also includes a blade sub-enclosure 62. The blade sub-enclosure 62 includes a computer system 64, such as a blade server, and a DEM 66. The blade sub-enclosure 62 can correspond to a sub-enclosure 18 in the example of
In addition, the blade switch enclosure group 50 can include one or more additional sub-enclosures that can be configured substantially the same as the blade sub-enclosure 62. For example, the additional one or more sub-enclosures 62 can be communicatively coupled to separate respective physical interface ports 60 of the blade switch system 56 to provide network connectivity of computer systems associated with the one or more additional sub-enclosures 62 to the network(s) 12 via the blade switch system 56. Furthermore, the blade switch enclosure group 50 can be part of a network logical domain, such that the blade switch system 56 can be communicatively coupled via separate respective physical interface ports 60 to a blade switch system of one or more separate blade enclosure that can be configured substantially the same as the blade enclosure 52. As an example, the blade switch system 56 can be coupled to a blade switch system of a respective first separate blade enclosure via a first physical interface port 60 and to a blade switch system of a respective second separate blade enclosure via a second physical interface port 60. Thus, the blade enclosures 52 can be communicatively coupled in a loop arrangement.
It is to be understood that the blade switch enclosure group 50 is not limited to the example of
A given network enclosure group, as described herein, is not limited to being implemented as a blade switch system.
The ToR switch enclosure group 100 includes a ToR enclosure 102 that includes a ToR switch system 106. The ToR enclosure 102 can correspond to a primary enclosure 14 in the example of
Similar to as described in the example of
In addition, the ToR switch enclosure group 100 can include one or more additional sub-enclosures that can be configured substantially the same as the blade sub-enclosure 112. For example, the additional one or more sub-enclosures 112 can be communicatively coupled to separate respective physical interface ports 110 of the ToR switch system 106 to provide network connectivity of computer systems associated with the one or more additional sub-enclosures 112 to the network(s) 12 via the ToR switch system 106. Furthermore, the ToR switch enclosure group 100 can be part of a network logical domain, such that the ToR switch system 106 can be communicatively coupled via separate respective physical interface ports 110 to a ToR switch system of one or more separate ToR enclosure that can be configured substantially the same as the ToR enclosure 102. As an example, the ToR switch system 106 can be coupled to a ToR switch system of a respective first separate ToR enclosure via a first physical interface port 110 and to a ToR switch system of a respective second separate ToR enclosure via a second physical interface port 110. Thus, the ToR enclosures 102 can be communicatively coupled in a loop arrangement. Furthermore, the ToR switch enclosure group 100 can be implemented in a network logical domain with blade switch enclosure groups, such as similar to the blade switch enclosure group 50 in the example of
The enclosure groups 152 each include a primary enclosure 154 and one or more sub-enclosures 156. As an example, the primary enclosures 154 can include a blade server. In the example of
Each of the sub-enclosures 156 can be configured substantially similar to the blade sub-enclosure 62 in the example of
In addition, the network switch system 158 of each of the primary enclosures 154 is coupled to a network switch system 158 of two other primary enclosures 154. As an example, each of the network switch systems 158 can have a first physical interface port that is coupled to a physical interface port of a first additional network switch system 158 and a second physical interface port that is coupled to a physical interface port of a second additional network switch system 158. Therefore, the enclosure groups 152 are demonstrated as communicatively coupled via the respective network switch systems 158 in a loop arrangement. Specifically, the first primary enclosure 154 is communicatively coupled to the second and sixth primary enclosures 154, the second primary enclosure 154 is communicatively coupled to the first and third primary enclosures 154, and the third primary enclosure 154 is communicatively coupled to the second and fourth primary enclosures 154. Similarly, the fourth primary enclosure 154 is communicatively coupled to the third and fifth primary enclosures 154, the fifth primary enclosure 154 is communicatively coupled to the fourth and sixth primary enclosures 154, and the sixth primary enclosure 154 is communicatively coupled to the fifth and first primary enclosures 154.
Based on the loop arrangement of the enclosure groups 152, the computer systems in a given one of the enclosure groups can have wire speed connectivity to the network switch system 158. Additionally between separate respective enclosure groups 152, the bandwidth of the communicative connection can be chosen to accommodate the expected traffic between the separate respective enclosure groups 152. Thus, the network logical domain 150 can provide flat network access to all of the computer systems associated with the primary enclosures 154 and the sub-enclosures 156 within the network logical domain 150. Additionally, the network logical domain 150 can be implemented at a significant less cost and with less power consumption than typical network architecture topologies.
What have been described above are examples. It is, of course, not possible to describe every conceivable combination of components or methods, but one of ordinary skill in the art will recognize that many further combinations and permutations are possible. Accordingly, the invention is intended to embrace all such alterations, modifications, and variations that fall within the scope of this application, including the appended claims. Additionally, where the disclosure or claims recite “a,” “an,” “a first,” or “another” element, or the equivalent thereof, it should be interpreted to include one or more than one such element, neither requiring nor excluding two or more such elements. As used herein, the term “includes” means includes but not limited to, and the term “including” means including but not limited to. The term “based on” means based at least in part on.
Number | Name | Date | Kind |
---|---|---|---|
5627788 | Chang et al. | May 1997 | A |
6181619 | Bogin et al. | Jan 2001 | B1 |
6324652 | Henderson et al. | Nov 2001 | B1 |
6516352 | Booth et al. | Feb 2003 | B1 |
6618392 | Richard | Sep 2003 | B1 |
6785793 | Aboulenein et al. | Aug 2004 | B2 |
6799241 | Kahn et al. | Sep 2004 | B2 |
6976122 | Sander et al. | Dec 2005 | B1 |
7610418 | Holland et al. | Oct 2009 | B2 |
7761656 | Madrid et al. | Jul 2010 | B2 |
8284771 | Julien et al. | Oct 2012 | B1 |
8406128 | Brar et al. | Mar 2013 | B1 |
8495194 | Brar | Jul 2013 | B1 |
8607225 | Rudd | Dec 2013 | B2 |
8619483 | Katoch et al. | Dec 2013 | B2 |
8661309 | Bliss et al. | Feb 2014 | B2 |
8880739 | Brar et al. | Nov 2014 | B1 |
20030161348 | Mills et al. | Aug 2003 | A1 |
20040120210 | Dong-Yang | Jun 2004 | A1 |
20040196728 | Yasurou | Oct 2004 | A1 |
20040208180 | Light et al. | Oct 2004 | A1 |
20040257990 | Lingafelt et al. | Dec 2004 | A1 |
20050002253 | Shi et al. | Jan 2005 | A1 |
20050002390 | Kim et al. | Jan 2005 | A1 |
20050055456 | Chalupsky et al. | Mar 2005 | A1 |
20050138191 | Seto et al. | Jun 2005 | A1 |
20060212636 | Akihiro | Sep 2006 | A1 |
20070110088 | Kemp | May 2007 | A1 |
20070165663 | Aloni et al. | Jul 2007 | A1 |
20080140819 | Bailey et al. | Jun 2008 | A1 |
20080239858 | Rajan et al. | Oct 2008 | A1 |
20090074001 | Kalkunte et al. | Mar 2009 | A1 |
20090232151 | Furlong et al. | Sep 2009 | A1 |
20100095185 | Ganga et al. | Apr 2010 | A1 |
20110035498 | Shah et al. | Feb 2011 | A1 |
20120272083 | Minoru | Oct 2012 | A1 |
20130235762 | Anantharam et al. | Sep 2013 | A1 |
20140016637 | Masood et al. | Jan 2014 | A1 |
20140032066 | Shigeru | Jan 2014 | A1 |
20140115137 | Singh | Apr 2014 | A1 |
20150098473 | Ariel | Apr 2015 | A1 |
20150271244 | Bloch et al. | Sep 2015 | A1 |
20160335216 | Krishnan | Nov 2016 | A1 |
20160373292 | Benoit | Dec 2016 | A1 |
20170054603 | Kulkarni | Feb 2017 | A1 |
20170244817 | Zhang et al. | Aug 2017 | A1 |
Number | Date | Country |
---|---|---|
1574751 | Feb 2005 | CN |
102394782 | Mar 2012 | CN |
2557739 | Feb 2013 | EP |
2688243 | Jan 2014 | EP |
3284218 | Feb 2018 | EP |
2004021194 | Mar 2004 | WO |
WO-2015147840 | Oct 2015 | WO |
2017065732 | Apr 2017 | WO |
Entry |
---|
Dr. Franz-Joachim Kauffels, “40GBase-T,” (Research Paper), Apr. 23, 2009, 20 pages. |
Extended European Search Report received for EP Patent Application No. 15906343.7, dated Feb. 12, 2018, 9 pages. |
Freesacle Semiconductor Inc , “Initializing SDRAM Parameters for Motorola MPC106-based Systems,” Rev 0.1, Jun. 2003, 8 pages. |
International Search Report and Written Opinion received for PCT Application No. PCT/US2014/067935, dated Aug. 11, 2015, 11 pages. |
International Search Report and Written Opinion received for PCT Application No. PCT/US2015/055129, dated Jul. 12, 2016, 8 pages. |
International Search Report and Written Opinion received for PCT Application No. PCT/US2015/055320, dated Jul. 13, 2016, 13 pages. |
Mellanox Technologies Inc., “Realizing the Full Potential of Server, Switch & I/O Blades with Infiniband Architecture,” 2009, pp. 1-11 pages. |
Number | Date | Country | |
---|---|---|---|
20200220819 A1 | Jul 2020 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15766002 | US | |
Child | 16819421 | US |