High-radix network switch modules may support a high number of connectors on their faceplates. Network port standards allow 1-lane and wider ports (e.g., 12-lane for CXP), and wider ports use larger connectors and thus fewer connectors on the faceplate. Different applications use different port bandwidth. Traditionally, either 1-lane (e.g., Small Form-Factor Pluggable (SFP)) or 4-lane (e.g., Quad Small Form-Factor Piuggable (QSFP)) ports predominate the Ethernet industry. As the bandwidth per lane has reached 10 Gbps, however, not every system can take advantage of QSFP 4-lane ports.
In the following detailed description, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific examples in which the disclosure may be practiced. It is to be understood that other examples may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims. It is to be understood that features of the various examples described herein may be combined, in part or whole, with each other, unless specifically noted otherwise.
Traditional network ports have a fixed number of lanes. A lane includes a pair of transmit differential signals and a pair of receive differential signals for network communications. For example, 1 GbE and 10 GbE can be 1-lane, 10 GbE, 40 GbE, and 100 GbE may be 4-lane, and 100 GbE may be 10-lane, Accordingly, network chips, connectors, and cables have been defined to provide a fixed number of lanes for a network port. Ethernet standards have been emerging where a port of a network chip may be configured to be a 4-lane port (e.g., 4×25 G for 100 GbE), a 2-lane port (e.g., 2×25 G for 50 GbE), or a 1-lane port (e.g., 1×25 G for 25 GbE). Existing connectors and cables for network ports are defined for a fixed number of lanes. This is not a problem for 1-lane ports or for multi-lane ports as long as the application calls for fixed lane-count ports (e.g., QSFP for a 4-lane port). When a multi-lane port of a chip in a network switch system, however, needs to be connected by network interface chips in computer systems having a varying number of lanes (e.g., 1-lane, 2-lane, 4-lane), the fixed lane-count connectors and cables will force certain lanes on a network chip port to be unusable, thus resulting in wasted or stranded lanes. A network chip may be a switch ASIC, a NIC (network interface controller) chip, an electrical transceiver chip (e.g., retimer, redriver), an optical transceiver chip, or a combination of these chips interconnected.
To minimize product models, many switches include QSFP ports. Using only one lane or two lanes out of the available four lanes, however, is wasteful. Therefore, users may buy switches with QSFP 4-lane ports for future proofing, and use break-out cables to fan-out four SFP 1-lane ports or two 2-lane ports for every QSFP port or for every two QSFP ports, respectively. This approach is expensive and can introduce signal integrity and connection reliability issues. Accordingly, this disclosure describes receptacles and cable connectors to allow receptacles on the system side to accept different lane-count cables so that switch manufacturers can design one system with one set of connectors on each faceplate that will allow varying lane-count cables. Switch port signals may be connected to specific receptacle connector bays in a way that all the lanes of the network chips can be used regardless of the cable type installed. Therefore, the disclosure provides for high connector density and lower solution costs by enabling simple and compact connector designs. In addition, management signals may be provided in the connectors for dynamic detection of the cable types so that system management logic can appropriately configure the network switch chips and/or transceiver chips to support the cables installed.
Each network port connection is provided on a switch in the form of a receptacle for an external cable to be connected. Although the receptacles may be implemented on the front or the rear side of a switch, this disclosure uses the term “faceplate” to generically describe where the receptacles are located for cables to be installed.
System-B2130b includes a network chip-B2132b communicatively coupled to a receptacle 136b via a 2-lane port 134b. A cable 142b having a first 2-lane cable connector 140b at one end of the cable and a second 2-lane cable connector 144b at the other end of the cable communicatively couples system-A 102b to system-B2130b. First 2-lane cable connector 140b is connected to receptacle 108, and second 2-lane cable connector 144b is connected to receptacle 136b. In this example, while system-A 102b uses a 4-lane receptacle, system-B1130a and system-B2130b use 2-lane receptacles. Network chip-A 104 is configured for a pair of 2-lanes L0, L1, and network chip-B1132a and network chip-B2132b are each configured for a corresponding 2-lanes L0, L1.
System-B2150b includes a network chip-B2152b communicatively coupled to a receptacle 156b via a 1-lane port 154b. A cable 162b having a first 1-lane cable connector 160b at one end of the cable and a second 1-lane cable connector 164b at the other end of the cable communicatively couples system-A 102c to system-B2 150b. First 1-lane cable connector 160b is connected to receptacle 108, and second 1-lane cable connector 164b is connected to receptacle 156b.
System-B3150c includes a network chip-B3152c communicatively coupled to a receptacle 156c via a 1-lane port 154c. A cable 162c having a first 1-lane cable connector 160c at one end of the cable and a second 1-lane cable connector 164c at the other end of the cable communicatively couples system-A 102c to system-B3150c. First 1-lane cable connector 160c is connected to receptacle 108, and second 1-lane cable connector 164c is connected to receptacle 156c.
System-B4150d includes a network chip-B4152d communicatively coupled to a receptacle 156d via a 1-lane port 154d. A cable 162d having a first 1-lane cable connector 160d at one end of the cable and a second 1-lane cable connector 164d at the other end of the cable communicatively couples system-A 102c to system-B4 150d. First 1-lane cable connector 160d is connected to receptacle 108, and second 1-lane cable connector 164d is connected to receptacle 156d. In this example, while system-A 102c uses a 4-lane receptacle, system-B1150a, system-B2150b, system-B3150c, and system-B4150d each use a 1-lane receptacle. Network chip-A 104 is configured for four 1-lanes L0 and network chip-1152a, network chip-B2152b, network chip-B3152c, and network chip-B4152d are each configured for a corresponding 1-lane L0.
In systems 100a-100c, the network chip-A ports and cable signal paths are fully utilized so there are no stranded lanes. Each cable is independently connecting the corresponding ports on system-A and system-B so there is no single point-of-failure. Each cable is directly coupled between a system-A port and a system-B port such that no additional connectors or cable stages are used, thereby improving signal integrity, improving connection reliability, and reducing cost. In addition, the 4-lane system receptacle may be more compact than four independent 1-lane receptacles. System-A, which is the same in systems 100a-100c, has receptacle 108 to enable coupling to system-B1, system-B2, system-B3, and system-B4, which have network chips having different lane-counts, by using appropriate lane-count cables, thereby reducing the system-A development cost. Without receptacle 108 and configurable network chip-A 104, different system-A designs would be needed to support varying number of lane count receptacles to avoid stranded ports.
A signal lane includes a “transmit” differential-pair of signal pins surrounded by a pair of ground pins, and a “receive” differential-pair of signal pins surrounded by another pair of ground pins. The transmit signal pins may be arranged on one side of connector finger 206, and the receive signal pins may be arranged on the opposite side of connector finger 206. One differential-pair of signal pins 210 surrounded by a pair of ground pins 208 are visible in
As illustrated in
A QX2 cable connector may have one “joint” finger, as illustrated in
Latch 262 is attached to cable connector 260 and includes two levers that are linked such that one motion will actuate both levers. In another example, a second latch may be arranged on the opposite side of housing 260 of cable connector 260. Latch 262 ensures positive retention of QX4 cable 192 in QX4 receptacle 190 when the cable is installed, and allows easy removal of the cable from QX4 receptacle 190. Cable connector fingers 266a and 266b are supported by cable connector 260 and include four signal lanes (i.e.,4-lane). Two differential-pairs of signal pins 210a and 210b surrounded by a pair of ground pins 208a and 208b, respectively, are visible in
Housing 270 includes keyed bay openings 274a and 278b separated by a divider 272. Housing 270 also includes latch areas 222 to ensure that a QX4 cable 192, QX2 cable 188, or a QX1 cable 184 is correctly oriented prior to installing into a QX4 receptacle as illustrated in
A QX2s receptacle as indicated at 402 has two split bays including bay-1 in the left and bay-2 in the right. When using QX1 cables with a QX2s receptacle as indicated at 408, each of the two bays are assigned lane-0 such that a network chip is configured for up to two 1-lane ports. When using QX2s cables with a QX2s receptacle as indicated at 414, bay-1 is assigned lane-0 and bay-2 is assigned lane-1 such that a network chip is configured for one 2-lane port. A QX1 receptacle as indicated at 404 has one bay (Le., bay-1), which is assigned lane-0 as indicated at 410 for use with a QX1 cable such that a network chip is configured for one 1-lane port.
A QX2j receptacle as indicated at 422 has one joint bay providing two total bays including bay-1 in the left and bay-2 in the right. When using QX1 cables with a QX2j receptacle as indicated at 428, each of the two bays are assigned lane-0 such that a network chip is configured for up to two 1-lane ports. When using QX2j or QX2s cables with a QX2j receptacle as indicated at 434 and 438, respectively, bay-1 is assigned lane-0 and bay-2 is assigned lane-1 such that a network chip is configured for one 2-lane port. A QX1 receptacle as indicated at 424 has one bay (i.e., bay-1), which is assigned lane-0 as indicated at 430 for use with a QX1 cable such that a network chip is configured for one 1-lane port.
Each connector finger (whether a split finger as indicated at 450 or part of a joint finger as indicated at 460) includes two pairs of differential signal lines, one pair for transmit signals and another pair for receive signals. For example, a first side of connector finger 451 of QX4s cable 450 includes first differential signal pins 452 surrounded by ground pins 454, and a second side of connector finger 451 opposite to the first side includes second differential signal pins 456 surrounded by ground pins 458.
The QX4j and QX2j cables indicated at 460 and 480, respectively, may include a Presence (P) signal pin to provide a P signal to signify that an adjacent lane is present, and a Low (L) signal pin to provide an L signal to signify that the row contains the lane-0. These P and L signals are detected by a system manager when a cable is installed in a receptacle. Based on these signals, the system manager configures the network chip to provide a 1-lane, 2-lane, or 4-lane port corresponding to the installed cable. In one example, the P and L signal pins interface with corresponding receptacle contacts such that no cable conductors are used to communicate these signals across a cable.
QX4j cable 460 includes a P signal pin and an L signal pin on each joint connector finger 461 and 463. The upper connector finger 461 includes a P signal pin 462 on one side of the connector finger in the joint region and an L signal pin 464 on the opposite side of the connector finger in the joint region. The lower connector finger 463 includes an L signal pin 466 on one side of the connector finger in the joint region and a P signal pin 468 on the opposite side of the connector finger in the joint region. QX2j cable 480 includes a P signal pin 482 on one side of connector finger 481 in the joint region and an L signal pin 484 on the opposite side of connector finger 481 in the joint region.
The split-type receptacles 400 and 402 and cables 450 and 470 do not have P and L signal contacts and corresponding P and L signal pins in this example, respectively. Therefore, to dynamically detect whether a wider than one lane port is supported by an installed cable, in one example the network chips go through an auto negotiation phase to determine the lane width of the installed cable.
For a QX2j receptacle, when two QX1 cables are installed, there are no P or L signal connections. In one example, when a QX2s cable is installed, there are also no P or L signal connections. Within a QX2j cable, however, both the P and the L signal pins are connected to ground (e.g., to a ground pin or a ground plane). When a QX2j cable is installed, the system manager can detect a2-lane cable and send appropriate messages to configure the network chip for lane-0 and lane-1, for the QX2j receptacle.
For a QX4j receptacle, when four QX1 cables are installed there are no P or L signal connections. In one example, when two QX2s or one QX4s cable is installed, there are also no P or L signal connections. When a QX2j cable is installed in the top or the bottom joint bay, the system manager can detect a2-lane cable and send appropriate messages to configure the network chip for lane-0 and lane-1, for the QX4j receptacle top or bottom joint bay, respectively. When two QX2j cables are installed in the QX4j receptacle, the system manager can detect two 2-lane cables are installed by sensing that both P and L signals for both joint bays are connected to ground. As previously described, there are ground pins on each cable connector finger surrounding the differential signal pins. The P and/or L pins may be coupled to these ground pins. Within a QX4j cable, both the P and the L signals in the top joint bay are connected to ground, but only the P signal in the bottom bay is connected to ground. When a QX4j cable is installed, the system manager can detect a 4-lane cable by sensing that both P signals and one L signal are connected to ground, and subsequently send appropriate messages to configure the network chip for lane-0, lane-1, lane-2, and lane-3 for the QX4j receptacle.
A QX4s cable 600 useable with QX4s receptacle 400, a QX2s cable 610 useable with a QX2s receptacle 401, and a QX1 cable usable with a QX1 receptacle 404 each include bays having management signal contacts. For example, connector finger 601 of QX4s cable 600 corresponding to bay-1 of QX4s receptacle 400 includes a management pin 602 on one side of the connector finger 601 and a management pin 603 on the opposite side of connector finger 601. Similarly, the contact assignment for the management pins is replicated in each bay of each QX4 receptacle 400, QX2 receptacle 402, and QX1 receptacle 404 and corresponding QX4 cable 600, QX2 cable 610, and QX1 cable 620. Since each bay has its own set of management signals, there is no joint area needed to provide the management signals. Although the connector width may be larger for this example, it might be acceptable for applications that desire QX1 to have management signals. Some of these management signals may be connected to cable conductors so that the system manager on one end of the cable can detect the presence of a system on the other end, or the two system managers across the cable can communicate with each other.
Although specific examples have been illustrated and described herein, a variety of alternate and/or equivalent implementations may be substituted for the specific examples shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the specific examples discussed herein. Therefore, it is intended that this disclosure be limited only by the claims and the equivalents thereof.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2014/057858 | 9/26/2014 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2016/048374 | 3/31/2016 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
3521332 | Kramer | Jul 1970 | A |
4386752 | Pavlak | Jun 1983 | A |
4767338 | Dennis | Aug 1988 | A |
5263671 | Baum | Nov 1993 | A |
5386487 | Briggs | Jan 1995 | A |
5559590 | Arai et al. | Sep 1996 | A |
5564939 | Maitani et al. | Oct 1996 | A |
5586906 | Staros et al. | Dec 1996 | A |
5669590 | Przewodek | Sep 1997 | A |
5993237 | Kern, Jr. et al. | Nov 1999 | A |
6062516 | Rizzo | May 2000 | A |
6175080 | Nightingale | Jan 2001 | B1 |
6216410 | Haberman | Apr 2001 | B1 |
6219479 | Madden | Apr 2001 | B1 |
6364721 | Stewart, III | Apr 2002 | B2 |
6378811 | Potter | Apr 2002 | B1 |
6669150 | Benoit | Dec 2003 | B2 |
6808116 | Eslambolchi | Oct 2004 | B1 |
6887091 | Wu | May 2005 | B1 |
6926237 | Shereyk | Aug 2005 | B2 |
7044802 | Chiou | May 2006 | B2 |
7055784 | Stigler | Jun 2006 | B2 |
7119280 | Ray | Oct 2006 | B1 |
7134908 | Wu | Nov 2006 | B2 |
7241163 | Ray et al. | Jul 2007 | B1 |
7294789 | Watthanasintham | Nov 2007 | B1 |
7318740 | Henry et al. | Jan 2008 | B1 |
7494353 | Choi | Feb 2009 | B2 |
7494363 | Wu | Feb 2009 | B1 |
7605707 | German | Oct 2009 | B2 |
7622682 | Malin | Nov 2009 | B2 |
7648392 | Chambers et al. | Jan 2010 | B2 |
7654831 | Wu | Feb 2010 | B1 |
7661979 | Hughes | Feb 2010 | B2 |
7789718 | Desard | Sep 2010 | B2 |
7841889 | Gerard et al. | Nov 2010 | B2 |
7845859 | Roth et al. | Dec 2010 | B2 |
8212145 | Nagai | Jul 2012 | B2 |
8340123 | Barbieri | Dec 2012 | B2 |
8370704 | Ganga et al. | Feb 2013 | B2 |
8475197 | Zerebilov et al. | Jul 2013 | B2 |
8506176 | Daikuhara et al. | Aug 2013 | B2 |
8585426 | Zerebilov | Nov 2013 | B2 |
8596882 | Smrha | Dec 2013 | B2 |
8636544 | Briant | Jan 2014 | B1 |
8639082 | Haley | Jan 2014 | B2 |
8645747 | Buckland et al. | Feb 2014 | B2 |
8668525 | Tu et al. | Mar 2014 | B1 |
8770990 | Sytsma et al. | Jul 2014 | B2 |
8867883 | Crain | Oct 2014 | B2 |
8882514 | Enge | Nov 2014 | B2 |
8910912 | Child | Dec 2014 | B2 |
8926339 | Houtz | Jan 2015 | B2 |
9088119 | Baker | Jul 2015 | B2 |
20040048506 | Chung et al. | Mar 2004 | A1 |
20040115997 | Scherer | Jun 2004 | A1 |
20050098688 | Miarka | May 2005 | A1 |
20050224585 | Durrant | Oct 2005 | A1 |
20050271328 | Ohtsu | Dec 2005 | A1 |
20060148279 | German | Jul 2006 | A1 |
20060189180 | Lang | Aug 2006 | A1 |
20070111598 | Quilici | May 2007 | A1 |
20070232132 | Ling | Oct 2007 | A1 |
20100062627 | Ambo | Mar 2010 | A1 |
20100065327 | Lin | Mar 2010 | A1 |
20100130063 | Lang et al. | May 2010 | A1 |
20110034082 | Zhu | Feb 2011 | A1 |
20110165785 | Lindner | Jul 2011 | A1 |
20110168423 | Hagi | Jul 2011 | A1 |
20110237112 | Wu | Sep 2011 | A1 |
20110300735 | Wu | Dec 2011 | A1 |
20120129382 | Regnier | May 2012 | A1 |
20120251064 | Crain | Oct 2012 | A1 |
20130005173 | Reed et al. | Jan 2013 | A1 |
20130183846 | Kappla et al. | Jul 2013 | A1 |
20130231011 | Sytsma | Sep 2013 | A1 |
20140038447 | Brown | Feb 2014 | A1 |
20140041937 | Lloyd et al. | Feb 2014 | A1 |
20140205243 | Baker | Jul 2014 | A1 |
20140363171 | Tang et al. | Dec 2014 | A1 |
20150244109 | Byczkiewicz et al. | Aug 2015 | A1 |
Number | Date | Country |
---|---|---|
101789575 | Jul 2010 | CN |
102210065 | Oct 2011 | CN |
2007317434 | Dec 2007 | JP |
2009076375 | Apr 2009 | JP |
1020100068002 | Jun 2010 | KR |
I267238 | Nov 2006 | TW |
M430018 | May 2012 | TW |
WO-2014043426 | Mar 2014 | WO |
Entry |
---|
“8 Channel Dula Multi-lane Sata2 Enclosure Device Bracket Scsi Opening,” Retrieved from Internet Sep. 15, 2014, http://www.satacable.com/8-channel-dula-multi-lane-sata2-enclosure-device-bracket-scsi-opening.html. |
Dennis Martin, “Demartek Storage Networking Interface Comparison,” May 9, 2014, http://www.demartek.com/Demartek_Interface_Comparison.html. |
Neer, et al.; “Advanced SAS Connections Converge at 3.0,” Retrieved form Internet Sep. 15, 2014; 5 pages; http://www.serialstoragewire.net/Articles/2009_12/molex.html. |
“LC Right Angle Clip” Feb. 22, 2013, <http://www.senko.com/fiber/pdf_brochure/FeaturesBrochure_2013-v5.pdf >. |
Accessories for Retaining Helawrap Open Cable Cover HWCLIP08, 3 pages; Retrieved from Internet Sep. 1, 2015, <http://www.hellermanntyton.co.uk/site/products/protective-tubing-and-spiral-binding/hwclip08/161-64002 >. |
PCT/ISA/KR, International Search Report and Written Opinion, dated Nov. 11, 2015, PCT/US2015/016283, 9 pps. |
PCT/ISA/KR, International Search Report and Written Opinion, dated Jun. 19, 2015, PCT/US2014/057858, 12 pps. |
PCT/ISA/KR, International Search Report and Written Opinion, dated Nov. 20, 2015, PCT/US2015/017964, 10 pps. |
PCT/ISA/KR, International Search Report and Written Opinion, dated Jan. 22, 2016, PCT/US2015/028277, 14 pages. |
“QSFP+ in the 40 Gigabit Ethernet Fiber Optic Media Systems” Retrieved from Internet Feb. 20, 2015, http://www.fiber-optic-equipment.com/tag/qsfp-cables >, 6 pps. |
Number | Date | Country | |
---|---|---|---|
20170222379 A1 | Aug 2017 | US |