One type of network switch for routing communications over a network between devices, such as servers and clients, is a switch that can be stacked. A switch that can be stacked is fully functional operating standalone but may also be configured to operate in combination with one or more other switches that can be stacked. When configured to operate in combination with one or more other switches, the group of switches acts as a single switch with an increased port capacity.
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 with each other, unless specifically noted otherwise.
Stack 102 routes communications between first sever 106, second server 110, first client 114, and second client 118. Stack 102 includes a plurality of switches in either a dual ring topology or a mesh topology. In one example, for the mesh topology, stack 102 includes a dedicated stacking link between two of the switches for routing communications between the two switches. In another example, for the dual ring topology, stack 102 routes a first class of communications over one of the two rings and a second class of communications over the other one of the two rings.
As used herein, the term “stacking link” is defined as a link between two switches that is configured to pass traffic and control data between the two switches with the purpose of creating a stack that acts and is managed like a single switch.
Stack 102 includes common configuration data 104 that specifies the topology of the stack and whether specified stacking links are dedicated to particular classes of traffic between the switches of the stack. Common configuration data 104 is distributed to each switch within stack 102. The particular classes of traffic between the switches may be defined as all traffic directly between two of the switches, a particular Virtual Routing and Forwarding (VRF) instance, a particular set of ports, a particular Virtual Local Area Network (VLAN), a particular set of protocols, voice traffic, video traffic, or any other suitable type of traffic.
In one example, based on common configuration data 104, stack 102 routes traffic between first client 114 and second server 110 over a first set of stacking links within stack 102, and routes traffic between second client 118 and first server 106 over a second set of stacking links within stack 102 separate from the first set. In this way, if traffic over the first set of stacking links saturates the available bandwidth of the first set, the second set of stacking links is not adversely impacted. Thus, stack 102 enables a specific amount of inter-switch bandwidth to be dedicated to a particular use.
CPU 142 is communicatively coupled to memory 146 through communication link 144. CPU 142 is communicatively coupled to fabric chip 154 through communication link 152. Fabric chip 154 is communicatively coupled to node chip 160 through communication link 156 and to node chip 166 through communication link 158. Node chip 160 is communicatively coupled to a first portion of the plurality of ports 188 through communication link 162 and to a second portion of the plurality of ports 188 through communication link 164. Node chip 166 is communicatively coupled to a third portion of the plurality of ports 188 through communication link 168 and to a fourth portion of the plurality of ports 188 through communication link 170.
Fabric chip 154 is communicatively coupled to a first stacking port 181 through communication link 171. Fabric chip 154 is communicatively coupled to a second stacking port 182 through communication link 172. Fabric chip 154 is communicatively coupled to a third stacking port 183 through communication link 173. Fabric chip 154 is communicatively coupled to a fourth stacking port 184 through communication link 174.
In one example, first stacking port 181 is communicatively coupled to another switch (not shown) through stacking link 191. Second stacking port 182 is communicatively coupled to another switch (not shown) through stacking link 192. Third stacking port 183 is communicatively coupled to another switch (not shown) through stacking link 193. Fourth stacking port 184 is communicatively coupled to another switch (not shown) through stacking link 194. In one example, for a mesh topology, each stacking port 181-184 is communicatively coupled to a different switch. In another example, for a dual ring topology, two of the stacking ports 181-184 are communicatively coupled to a first switch, and the other two of the stacking ports 181-184 are communicatively coupled to a second switch.
In one example, memory 146 stores switch instructions 150 executed by CPU 142 for operating switch 140. Memory 146 includes any suitable combination of volatile and/or non-volatile memory, such as combinations of Random Access Memory (RAM), Read-Only Memory (ROM), flash memory, and/or other suitable memory. Memory 146 also stores local configuration data 148 for configuring switch 140. In one example, local configuration data 148 is a copy of common configuration data 104 previously described and illustrated with reference to
Fabric chip 154 routes communications (e.g. Ethernet packets) between stacking ports 181-184 and node chips 160 and 166 based on destination addresses of the communications. Node chips 160 and 166 route communications between fabric chip 154 and the plurality of ports 188. In one example, each of the plurality of ports 188 is an RJ 45 port. Each of the plurality of ports 188 may be communicatively coupled to a device that communicates over the network via switch 140, such as a server, a client, or another suitable device. In operation, switch 140 routes communications between the plurality of ports 188 and stacking ports 181-184 based on the destination addresses of the communications and local configuration data 148.
Each switch 201-205 includes four stacking ports (e.g., stacking ports 181-184 previously described and illustrated with reference to
A third stacking port and a fourth stacking port of third switch 203 is communicatively coupled to a first stacking port and a second stacking port of fourth switch 204 through a first stacking link 210(c) and a second stacking link 212(c), respectively. A third stacking port and a fourth stacking port of fourth switch 204 is communicatively coupled to a first stacking port and a second stacking port of fifth switch 205 through a first stacking link 210(d) and a second stacking link 212(d), respectively. A third stacking port and a fourth stacking port of fifth switch 205 is communicatively coupled to a third stacking port and a fourth stacking port of first switch 201 through a first stacking link 210(e) and a second stacking link 212(e), respectively.
Stacking links 210(a)-210(e), commonly referred to herein as stacking links 210, provide a first or outer ring of the dual ring topology. Stacking links 212(a)-212(e), commonly referred to herein as stacking links 212, provide a second or inner ring of the dual ring topology. In one example, a first class of communications are routed between switches 201-205 via the outer ring stacking links 210, and a second class of communications are routed between switches 201-205 via the inner ring stacking links 212. By specifying the class of communications to be routed through each ring, the available bandwidth of each ring can be efficiently managed.
In the dual ring topology, if one of the stacking links between the switches in either the outer ring or the inner ring is broken, communications can still reach each switch in both the outer ring and the inner ring. For example, if stacking link 210(a) is broken, communications can still be routed on the outer ring between first switch 201 and second switch 202 via stacking links 210(e), 210(d), 210(c), and 210(b).
If two of the stacking links between the switches in either the outer ring or the inner ring are broken, communications can still be routed on the other ring. For example, if stacking links 210(a) and 210(d) are broken, communications between second switch 202 and fifth switch 205 can still be routed via stacking links 212(b), 212(c), and 212(d) or via stacking links 212(a) and 212(e). Therefore, the dual ring topology of stack 200 not only allows specific traffic to be routed either through the outer ring or the inner ring, but also adds additional redundancy to stack 200 compared to a single ring topology. This capability of redundancy is configurable, such that a user may choose whether or not traffic from a failed ring is transferred to the other ring.
Each switch 201-205 includes four stacking ports (e.g., stacking ports 181-184 previously described and illustrated with reference to
A second stacking port of second switch 202 is communicatively coupled to a second stacking port of third switch 203 through a stacking link 234. A third stacking port of second switch 202 is communicatively coupled to a second stacking port of fourth switch 204 through a stacking link 232. A fourth stacking port of second switch 202 is communicatively coupled to a second stacking port of fifth switch 205 through a stacking link 230.
A third stacking port of third switch 203 is communicatively coupled to a third stacking port of fourth switch 204 through a stacking link 238. A fourth stacking port of third switch 203 is communicatively coupled to a third stacking port of fifth switch 205 through a stacking link 236. A fourth stacking port of fourth switch 204 is communicatively coupled to a fourth stacking port of fifth switch 205 through a stacking link 240.
In one example, one or more of the stacking links 222, 224, 226, 228, 230, 232, 234, 236, 238, and 240 may be dedicated to a particular class of traffic between two of the switches 201-205. By specifying the class of communications to be routed through a stacking link, the available bandwidth of each stacking link can be efficiently managed. For example, stacking link 228 may be dedicated to traffic between first switch 201 and fifth switch 205, and stacking link 230 may be dedicated to traffic between second switch 202 and fifth switch 205. Therefore, traffic between first switch 201 and fourth switch 204 is not routed over stacking link 228 or 230.
Video server 302 is communicatively coupled to a port (e.g., one of ports 188 previously described and illustrated with reference to
In this example, the inner ring (i.e., stacking links 212) of stack 200 is configured to carry traffic for a first VLAN, and the outer ring (i.e., stacking links 210) is configured to carry traffic for a second VLAN. In this example, laptop computer 310 and file server 306 belong to the second VLAN, and video camera 314 and video server 302 belong to the first VLAN. Third switch 203 is configured (e.g., via local configuration data 148 previously described and illustrated with reference to
By utilizing stack 200, traffic between laptop computer 312 and file server 306 will remain isolated from traffic between video camera 314 and video server 302. Therefore, even if video traffic saturates the available bandwidth on the inner ring, the ability of laptop computer 310 to access file server 306 will not be adversely impacted.
At 422, a third stacking link between a third stacking port of the first switch and a second stacking port of the second switch is established. At 424, a fourth stacking link between a fourth stacking port of the first switch and a second stacking port of the third switch is established. At 426, the first stacking link and the second stacking link are dedicated to a first class of traffic between the first switch, the second switch, and the third switch. At 428, the third stacking link and the fourth stacking link are dedicated to a second class of traffic between the first switch, the second switch, and the third switch.
At 442, a third stacking link between a third stacking port of the first switch and a first stacking port of a fourth switch is established. At 444, a fourth stacking link between a fourth stacking port of the first switch and a first stacking port of a fifth switch is established. At 446, the first stacking link is dedicated to a first class of traffic between the first switch and the second switch such that traffic between the first switch and the third switch, the fourth switch, and the fifth switch does not pass through the first stacking link.
Examples of the stack enable a specific amount of inter-switch bandwidth to be dedicated for a particular use. In either a mesh topology or a dual ring topology, examples of the stack enable a specific amount inter-switch bandwidth to remain dedicated for a particular use even if one of the stacking links between the switches of the stack is broken. In addition, high security traffic can be dedicated to particular switch interconnects, thereby reducing the number of physical connections for which a user has to maintain physical security.
Although specific examples have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that 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.
Number | Name | Date | Kind |
---|---|---|---|
6414958 | Specht | Jul 2002 | B1 |
6532088 | Dantu et al. | Mar 2003 | B1 |
6785272 | Sugihara | Aug 2004 | B1 |
6854015 | McCormack et al. | Feb 2005 | B2 |
6952396 | Cottreau et al. | Oct 2005 | B1 |
7295552 | Kadambi et al. | Nov 2007 | B1 |
7466653 | Cohen et al. | Dec 2008 | B1 |
7593320 | Cohen et al. | Sep 2009 | B1 |
7756015 | Bishara et al. | Jul 2010 | B1 |
7907518 | Kuhl et al. | Mar 2011 | B2 |
20060146697 | Magret et al. | Jul 2006 | A1 |
20070025362 | Jorgensen | Feb 2007 | A1 |
20070230368 | Shi et al. | Oct 2007 | A1 |
20080301319 | Dernosek et al. | Dec 2008 | A1 |
20090268748 | Ghaibeh et al. | Oct 2009 | A1 |
20090310610 | Sandstrom | Dec 2009 | A1 |
20110080829 | Breslin et al. | Apr 2011 | A1 |
20110110369 | Shiraki | May 2011 | A1 |
20110194404 | Kluger et al. | Aug 2011 | A1 |
20110305245 | Tanaka et al. | Dec 2011 | A1 |
Number | Date | Country | |
---|---|---|---|
20130279502 A1 | Oct 2013 | US |