The common characteristic of a stack acting as a single switch is that there is a single IP address for remote administration of the stack as a whole, not an IP address for the administration of each unit in the stack. Features associated with stackable switches can include:
Single IP Address for multiple units. Multiple switches can share one IP Address for administrative purposes, thus conserving IP Addresses.
Single management view from multiple interfaces. Stack-level views and commands can be provided from a single Command Line Interface (CLI) and/or embedded Web interface. The SNMP view into the stack can be unified.
Stacking Resiliency. Multiple switches can have ways to bypass a “down” switch in a stack, thus allowing the remaining units to function as a stack even with a failed or removed unit.
Layer 3 redundancy. Some stackable architectures allow for continued Layer 3 routing if there is a “down” switch in a stack. If routing is centralized in one unit in the stack, and that unit fails, then there must be a recovery mechanism to move routing to a backup unit in the stack.
Mix and match of technology. Some stackable architectures allow for mixing switches of different technologies or from different product families, yet still achieve unified management. For example, some stacking allows for the mixing 10/100 and Gigabit switches in a stack.
Dedicated stacking bandwidth. Some switches come with built-in ports dedicated for stacking, which can preserve other ports for data network connections and can avoid the possible expense of an additional module to add stacking. Proprietary data handling or cables can be used to achieve higher bandwidths than standard Gigabit or 10-Gigabit connections.
There is not universal agreement as to the threshold for being a stackable versus being a standalone switch. Some companies call their switches stackable if they support a Single IP Address for multiple units even if they lack other features from this list. Some industry analysts have said a product is not a stackable if it lacks one of the above features (e.g., dedicated bandwidth).
Terminology
Here are other terms associated with stackable switches:
Stacking Backplane: Used to describe the connections between stacked units, and the bandwidth of that connection. Most typically, switches that have primarily Fast Ethernet ports would have at minimum Gigabit connections for its stacking backplane; likewise, switches that primarily have Gigabit Ethernet ports would have at minimum 10-Gigabit connections.
Clustering. The term sometimes used for a stacking approach that focuses on unified management with a single IP address for multiple stackable units. Units can be distributed and of multiple types.
Stack Master or Commander: In some stack architectures, one unit is designated the main unit of the stack. All management is routed through that single master unit. Some call this the master or commander unit. Other units in the stack are referred to as slave or member units.
Which switches:?
===========>
Cisco offers their StackWise feature on the Cisco Catalyst 3750 series switches, and StackWise Plus on Catalyst 3750-E series.
What StackWise basically does is build one big switch by intelligently joining several individual switches together (with a maximum of nice switches total). The switches are united into a single logical unit using special stack interconnect cables that create a bidirectional closed-loop path. The bidirectional path acts as a switch fabric for all the connected switches, where network topology and routing information is updated continuously through the stack. All stack members have full access to the stack interconnect bandwidth (32 Gb).
The stack is managed as a single unit by a master switch, which is elected from one of the stack member switches. Any stack member switch can become master, and election is done my one of these methods:
User priority-The network manager can select a switch to be master.
Hardware and software priority-This will default to the unit with the most extensive feature set.
Default configuration-If a switch has preexisting configuration information, it will take precedence over switches that have not been configured.
Uptime-The switch that has been running the longest is selected.
MAC address-Each switch reports its MAC address to all its neighbors for comparison. The switch with the lowest MAC address is selected.
When one master switch becomes inactive and while a new master is elected, the stack continues to function.
To build StackWise connections you need (at least two) of either of these cables:
CAB-STACK-50CM= (0.5-meter cable)
CAB-STACK-1M= (1-meter cable)
CAB-STACK-3M= (3-meter cable)
The reason you need at least two cables (or more precisely: X + 1, where X is the number of switches in the stack) is that the stacking cables must form a ring, as the connections are bidirectional, and without the ring a failure of one of the cables would break the stack with all manner of nasty things happening to your network. In a correct configuration a stack cable failure will halve the capacity but the stack continues functioning, while after the failed cable starts functioning again full capacity is automatically restored.
The main differences between StackWise (supported on 3750 and 3750-E series) and StackWise plus (only supported on 3750-E series) are:
StackWise plus performs destination stripping, where StackWise only supports source stripping. What this means is that with source stripping a unicast packet that is sent on the stack ring goes around the whole ring and is removed (i.e.: stripped) by the sender of the packet (i.e.: the source switch). With destination stripping the target switch of the packet removes it from the ring, freeing up bandwidth on the ring sooner.
StackWise Plus supports local switching, where StackWise doesn’t, forcing all packets on the stack ring. On a StackWise Plus stack any traffic destined for a node connected to the same member switch stays within that member switch, and doesn’t use the stack ring at all.
StackWise Plus will support up to 2 line rate 10 Gb Ethernet ports per switch.
You can build a stack consisting of a mix of 3750 and 3750-E switches, in that case only StackWise features are available with the exception of the local switching, the 3750-E’s will still do that.
All in all the StackWise feature is quite nice. Just as with RAID arrays you can build a resilient and easy to manage system by using relatively inexpensive devices. Management is almost as easy as managing a single switch, and most of the features that make StackWise worthwhile and in some respects even great are automatic and do their thing quietly and without fuss. Good stuff.
=======
To do this we require: GigaStack GBIC
Check out:
http://www.cisco.com/en/US/products/hw/switches/ps628/products_data_sheet09186a00800a1789.htmlhttp://linksys.custhelp.com/cgi-bin/linksys.cfg/php/enduser/std_adp.php?p_faqid=16639&p_created=1213295950Troubleshooting stackable switches:
http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/troubleshooting/switch_stacks.htmlhttp://www.cisco.com/en/US/products/hw/switches/ps5023/products_tech_note09186a00807ccc79.shtmlFinally some basics:
------------
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps5023/prod_white_paper09186a00801b096a.htmlhttp://newsroom.cisco.com/dlls/fspnisapi81e5.html
