Stacking PowerConnect 8100 v1.1

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F
Rev. 1.1
Victor Teeter Network Solutions Engineer
This document is for informational purposes only and may contain typographical errors and technical inaccuracies. The content is provided as is, without express or implied warranties of any kind. 2013 Dell Inc. All rights reserved. Dell and its affiliates cannot be responsible for errors or omissions in typography or photography. Dell, the Dell logo, and PowerEdge are trademarks of Dell Inc. Intel and Xeon are registered trademarks of Intel Corporation in the U.S. and other countries. Microsoft, Windows, and Windows Server are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims proprietary interest in the marks and names of others. May 2013| Rev 1.1
ii
Contents
Important Firmware Update for PowerConnect 81xx Stacking .................................... 4 Introduction ............................................................................................... 6
Stacking and management ....................................................................................... 7 Simplified firmware updates for stack members ............................................................ 7 Stacking and redundancy......................................................................................... 7 Nonstop forwarding on the stack ............................................................................... 7 Hot add/delete and firmware synchronization .............................................................. 7 Meta-data considerations ........................................................................................ 7 How a Master is selected ......................................................................................... 8 How to select a Master during initial stack setup ......................................................... 10
Stacking scenarios ....................................................................................... 11

Creating a Stack ................................................................................................. 12 Command-line interface method ......................................................................... 23 Web interface method ..................................................................................... 27 Updating firmware on a stack ................................................................................. 30 Command-line interface method ......................................................................... 30 Web interface method ..................................................................................... 32 Removing member units ........................................................................................ 38 Command-line interface method ......................................................................... 39 Web interface method ..................................................................................... 44 Managing the standby unit ...................................................................................... 51 Command-line interface method ......................................................................... 51 Web interface method ..................................................................................... 52
Appendix A Commands used in this document .................................................... 55 Appendix B - Network switch versions ............................................................... 55 About Dell ................................................................................................ 55
iii
Important Firmware Update for PowerConnect 81xx Stacking

As of May 2013, PowerConnect 8100 switches ship with an improved B1 CPU. These new CPUs are fully compatible and virtually identical to the original A1 CPUs found in all prior PowerConnect 81xx switches. The only difference with the new B1 switch that will cause concern to those wanting to have both A1 and B1 switches in the same stack is the new B1 will not downgrade to the older 5.0.x.x firmware code. If attempting to add a B1 switch to a stack running 5.0.x.x firmware (or if trying to downgrade a standalone B1 to 5.0.x.x firmware), be aware that the device will not update to the older firmware and will fail to be added to the stack. Furthermore, if the boot auto-copy-sw feature is enabled on the stack master with the allow-downgrade option also enabled, the new B1 switch will continue to reboot until removed from the stack. The recommended solution to this issue is to update the switch stack to firmware version 5.1.x.x or later prior to adding any new switches to the stack. Find the latest firmware (5.1.x.x or later) at http://support.dell.com. Caution: Users can download the older 5.0.x.x firmware to the new B1 switch, but the firmware will not load and is not usable.
Firmware 5.0.x.x is no longer recommended

If after reading the above section, it is still desired to run 5.0.x.x on a stack (not recommended), there may be an option that will allow it depending on the CPU versions of each switch. Follow the instructions below to find the CPU versions for all 8100 switches involved and determine available options. 1. Run show version from the CLI prompt on either a stack or stand-alone switch. 2. If the stack or stand-alone is running 5.0.x.x firmware, then all switches in the stack (or standalone) contain A1 CPUs. This is because 5.0.x.x can only run on A1 CPU switches. 3. If the firmware version is 5.1.x.x, then a CPU version line is displayed CPU Version....................... XLP308H-A1 which shows the CPU version in the last two characters (either A1 or B1). 4. On a stack, run show version m where m is the unit number assigned to the stack member. This will display the CPU version for that stack member. Run this command for each member. If both A1 and B1 CPUs are among the switches you want to stack together, the only option is to upgrade to firmware 5.1.x.x or later on all switches before stacking them. If all switches are A1 CPUs, or if all switches are B1 CPUs, then they are ready to be stacked using any supported firmware. Just remember that the B1 CPUs are only compatible with firmware 5.1.x.x or later. A1 CPUs are compatible with all versions of PowerConnect 81xx firmware, including 5.0.x.x.
Note: Dell recommends that all PowerConnect switches are updated to the latest firmware.
Errors Downgrading Firmware

Before attempting to downgrade firmware on a stack to version 5.0.x.x, run the four steps above to determine each stack members CPU version. Know that all CPUs in the stack must be version A1 for the stack to successfully downgrade to 5.0.x.x. Attempting to downgrade to 5.0.x.x on a stack containing B1 CPUs will result in the following errors on the console: L7_LOGF(L7_LOG_SEVERITY_ERROR, L7_BSP_COMPONENT_ID, "Unit %d has a %s processor, which requires firmware revision 5.1 or later.", unitIndex, cpuString); When trying to downgrade a standalone B1 unit to firmware 5.0.x.x, the following error is displayed to the console: This unit or members of the stack require revision 5.1 or later firmware. This level of firmware is also required when attaching these units to a stack. To avoid errors, upgrade all PowerConnect 8100 stacks and stand-alone switches to 5.1.x.x or later. Dell recommends running the latest firmware available for the switch. Find the latest firmware at http://support.dell.com.
Note: Dell recommends that all PowerConnect switches are updated to the latest firmware.
Introduction
Most Dell PowerConnect switches today include a stacking feature that allows multiple switches to operate as a single unit. These stacks include up to six Dell PowerConnect 8132/8132F/8164/8164F switches in any combination, use up to four links between stack members, and use any port type on the front panel to create these links A single switch in the stack (known as the Master switch) manages all the units in the stack and uses a single IP address, which allows the user to manage every port in the stack from this one address. This IP address is copied from the Master to the Standby when the Standby is created. If for any reason the Master fails and the Standby takes over as Master, the IP address of the stack remains the same, allowing continuous management of the stack. The new Master unit also continues to use the original Master units MAC addresses, which helps to reduce disruptions to the network. When a failed Master re-joins the stack, it does so as a member (not a Master) unless a new Master has not had time to be elected. Note: Dell PowerConnect 8132, 8132F, 8164, and 8164F series switches can be mixed in any combination within a stack. This document provides an easy to use step-by-step guide on how to configure stacking for the Dell PowerConnect 8132 (Figure 1), PowerConnect 8132F (Figure 2), PowerConnect 8164 (Figure 3) and the PowerConnect 8164F (Figure 4).
Figure 1.
1
Dell PowerConnect 8132

3 5 7 9 11 13 15 17 19 21 LNK 23 ACT
10
12
14
16
18
20
22
24
Figure 2.
1
Dell PowerConnect 8132F

3 5 7 9 11 13 15 17 19 21 LNK 23 ACT
10
12
14
16
18
20
22
24
Figure 3.
1 3 5 7 9 11 13 15 17 19 21 23
Dell PowerConnect 8164

25 27 29 31 33 35 37 39 41 43 45
LN K A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
Figure 4.
1 3 5 7 9 11 13 15 17 19 21
Dell PowerConnect 8164F

23 25 27 29 31 33 35 37 39 41 43 45
LN K A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
Stacking and management

An important advantage of stacking is that it provides a consolidated interface for management of multiple switches that are linked together. One switch acts as the Master, and the entire stack is managed through the management interface (Web, CLI, or SNMP) of the stack Master. After a stack is deployed in the network, operators can easily add units to the stack as their port requirements increase, with minimal administrative overhead. Additional stack members can immediately use existing configuration information such as routing and switching configurations, VLANs, ACLs, port profiles, and security certificates.
Simplified firmware updates for stack members

When switches are stacked, only the Master needs to be updated with new firmware. All members of the stack receive the firmware from the Master at the same time it is being updated, minimizing the administrators time used for updating firmware. Also, when a switch is added to a stack, if it is running a different backup version of firmware than the active version on the stack Master, the backup firmware on the new member is automatically updated to match the Master, the backup version of firmware on the new member is activated, and the new member is rebooted.
Stacking and redundancy

By connecting a cable from the last switch in a stack back to the first switch, the operator makes sure that a stack has the protection of redundant paths for control and data traffic, including support for Link Aggregation Group (LAGs) configured across multiple switches. This means that any single point of failure (a switch or a stack cable failure) does not affect the overall operation of the remaining stack elements.
Nonstop forwarding on the stack

The Nonstop Forwarding (NSF) feature allows the forwarding plane of stack units to continue to forward packets while the control and management planes restart as a result of a power failure, hardware failure, or software fault on the stack Master and allows the standby switch to quickly takeover as the Master.
Hot add/delete and firmware synchronization

Units can be added and removed to and from the stack without cycling the power on the stack. When adding a unit, the Stack Firmware Synchronization feature automatically synchronizes the firmware version with the version running on the stack Master. The synchronization operation may result in either an upgrade or a downgrade of firmware on the mismatched stack member. In addition, the running-config on the member is updated to match the Master switch. The startup-config on the standby and member switches is not updated to match the Master switch. The hardware configuration of every switch is updated to match the Master switch (unit number, slot configuration, stack member number, and so on).
Meta-data considerations
When creating a stack, the configuration information is meta-data that is part of the hardware configuration applied at boot time before the switch firmware is started (and before the startup configuration is read). The stack information shown in the startup and running configurations is simply
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F copies of the stack configuration for the users knowledge. The actual stack information used by the switch is not that which is stored in the startup configuration. A stack member configuration is always present on stacking capable switches, so there always is a line in the configuration that says stack and a second line that says member even if there are no devices stacked. Since these are stack-capable devices, an un-stacked device is still considered a stack of one. Here is an example configuration of a device that is not stacked. console#show run !Current Configuration: !System Description "PowerConnect 8164F, 5.0.0.0, Linux 2.6.27.47 !System Software Version 5.0.0.0 !Cut-through mode is configured as disabled ! configure slot 1/0 5 ! PowerConnect 8164F slot 1/1 8 ! Dell 10GBase-T Card stack member 1 4 ! PCT8164F exit interface out-of-band ip address 172.25.194.24 255.255.0.0 172.25.194.254 exit interface vlan 1 exit username "admin" password dec68e453164a2 privilege 15 encrypted line telnet enable authentication enableList exit snmp-server engineid local 800002a203001ec9ddad5b exit Notice there is only one member line in the configuration. If there were multiple members in the stack then there would be multiple member lines in the configuration, such as: stack member 1 1 member 2 1 member 3 1 ! PCT8164F ! PCT8164F ! PCT8132F
Note: A single stack member configuration is always present on stack-capable switches even if they are not part of an actual stack. The single switch is considered a stack of one.
How a Master is selected

A Master is elected or re-elected based on the following considerations, in order: 1. 2. The switch is currently the Master. The switch has the higher MAC address.
3.
A unit is selected as standby by the administrator, and a fail over action is manually initiated or occurs due to a Master unit failure. Note: The terms Master and Manager/Management Unit are often used interchangeably in regards to stacking.
In most cases, a switch that is added to an existing stack becomes a stack member, and not the Management Unit. When a switch is added to the stack, one of the following scenarios takes place regarding the management status of the new switch:
If the switch has the Management Unit function enabled but another Master unit is already active, then the switch changes its configured Management Unit value to disabled. If the Management Unit function is unassigned and there is another Management Unit in the system, then the switch changes its configured Management Unit value to disabled. If the Management Unit function is enabled or unassigned and there is no other Management Unit in the system, then the switch becomes Management Unit. If the Management Unit function is disabled, the unit remains a non-Management Unit.
If the entire stack is powered OFF and ON again, the unit that was the Management Unit before the reboot remains the Management Unit after the stack resumes operation. A Unit number for the switch can be manually set. To avoid unit-number conflicts, one of the following scenarios takes place when adding a new member to the stack:
If the switch has a unit number that is already in use, then the unit added to the stack changes its configured unit number to the lowest unassigned unit number. If the switch added does not have an assigned unit number, then the switch sets its configured unit number to the lowest unassigned unit number. If the unit number is configured and there are no other devices using the unit number, then the switch starts using the configured unit number. If the switch detects that the maximum number of units already exist in the stack making it unable to assign a unit number, then the switch sets its unit number to unassigned and does not participate in the stack.
After the stack is created, the show switch command displays the roles of each switch. console#show switch SW --1 2 3 4 5 6 Management Status ---------Mgmt Sw Stack Mbr Stack Mbr Stack Mbr Stack Mbr Stack Mbr Standby Preconfig Status Model ID --------- ---------PCT8164F Oper Stby PCT8132F PCT8132F PCT8164F PCT8164 PCT8164F Plugged-in Model ID ------------PCT8164F PCT8132F PCT8132F PCT8164F PCT8164 PCT8164F Switch Status ---------OK OK OK OK OK OK Code Version --------5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F Note that in this example Switch 1 is the Master (Mgmt Sw) and Switch 2 is the Standby (Oper Stby) ready to take over as Master in the event the Master fails. To find the same information from the Web UI go to System > Stack Management > Stack Summary .
How to select a Master during initial stack setup

After creating a stack it is easy to go into the settings on the Master and select any of the members to take its place as Master. The former Master becomes a regular stack member automatically. To select a particular physical unit to be Master during initial setup, simply boot it up completely before powering on any of the other switches. All subsequent members added to the stack will join as regular stack members. When using two or more switches to initially create a stack, the Master is chosen based on the highest MAC address. To find the MAC address of a switch, type show system from a CLI prompt: console#show system System Description: Dell Ethernet Switch System Up Time: 0 days, 00h:12m:53s Burned In MAC Address: A4BA.DB69.330B
Or from the Web UI, go to the System > General > System Information page:
10
Stacking scenarios
The following sections present examples in a variety of areas concerning stacking the Dell PowerConnect 8100 switches and provides step-by-step guidance using the CLI and Web UI, with screen shots as a visual guide. Consult the table of contents above for a list of examples covered in this document. Each scenario in this document assumes that all Dell PowerConnect devices are using the same firmware revision. It is also recommended that all devices are using the latest firmware version. Note: Upgrade the firmware to the latest revision on the units before stacking them. Unless mentioned otherwise, all scenarios below assume the switches are using the static ports that are hard-wired into the switches, and that no modules are installed providing additional ports. However, ports from an installed expansion module are supported and may be used for stacking. The following expansion modules are supported for stacking in the Dell PowerConnect series:
11
Figure 5.
10Gbase-T four-port expansion module for the Dell PowerConnect 81xx and 81xxF
LNK ACT
10GBASE-T MODULE
Figure 6.
40G QSFP+ two-port expansion module for the Dell PowerConnect 81xx and 81xxF
LNK LNK
ACT
QSFP+ MODULE
ACT
Figure 7.
10G SFP+ four-port expansion modules for the Dell PowerConnect 81xx and 81xxF
LNK ACT
10G SFP+ MODULE
With an expansion module installed, the command show switch stack-ports shows the link status, link speed, and stack mode for each port in the module.
Creating a Stack
Examples below provide steps on how to create a stack. Graphics shown in this section only depict some of the possibilities of how to cable together members of a stack. Note: While the cable pictures below come before the configuration steps, it is important not to cable the stack until instructed to do so. Cabling is one of the last steps and comes after configuring all switches used in the stack; however, it is necessary to know exactly each port that is going to be cabled to configure each switch correctly. The Dell PowerConnect 8100 series switches can be stacked up to six high, supporting up to 336x10G ports when two 40G ports on each unit are configured as stacking ports. The stack can contain any combination of Dell PowerConnect 8100 and Dell PowerConnect 8100F switches. The switches can be stacked using any Ethernet port on the front panel, which includes 40Gb QSFP+ ports, 10Gb SFP+ fiber ports, and 10Gb baseT copper ports. Each of these default to Ethernet mode and must be reconfigured as stacking ports in order to stack. This scenario shows steps to create a stack. Figure 8 shows one example of connectivity between stack members.
12
Figure 8.
Stacking Dell PowerConnect 8100 series switches using 40G and 10G stack links
1 3 5 7 9 11 13 15 17 19 21 LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
Notice the top two switches are stacked together using four cables plugged into 10G ports. For each remaining switch in the stack, one cable from a 40G stacking port on a switch is connected to a 40G stacking port on the next switch. This process is repeated until all of the devices are connected. To complete the ring topology for the stack, one stacking port on the last switch is connected to a stacking port on the first switch. Things to consider when cabling a stack together: Only use interfaces with the same bandwidth to stack between members. It is not supported to mix 40G QSFP+ ports with 10G SFP+ or 10Gbase-T ports on a switch when stacking. It is okay however to use one interface type between two stack members, then a different interface type between two other stacking members as shown in Figure 8. A QSFP+ port is counted as one port when stacking. Therefore if stacking only two switches together, all QSFP+ ports (including those on an expansion module) can be used to stack between them when in 40G port mode. Up to eight ports may be used on any switch for stacking purposes.
Connecting additional cables in parallel increases the stacking bandwidth. Up to eight ports can be connected in parallel when only stacking two switches. When stacking three or more switches, up to 4 cables can be connected in parallel between members. It is recommended to have the same bandwidth between the stack members. It is also recommended to connect the stack in a ring topology for resiliency. Figure 9 shows an example of connecting four stack ports between each stacking peer. Note: In a stack of three or more switches, Dell strongly recommends connecting the stack in a ring topology so that each switch is connected to two other switches.
13
Figure 9.
1 3
Stacking Dell PowerConnect 8100/8100F series switches using multiple stack links
5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45
LN K A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
LNK 23 ACT
10
12
14
16
18
20
22
24
QSFP+ quad-breakout cables

QSFP+ quad-breakout cables may also be used for stacking. This allows a 40G QSFP+ port to connect to four 10G SFP+ ports on the adjacent switch. When a breakout cable is used, the connections are considered to be four links taking up four ports.
Figure 10.
QSFP+ quad-breakout cable may be used for stacking

1 3 5 7 9 11 13 15 17 19 21 LNK 23 ACT
LNK LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
11
13
15
17
19
21
LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
To use a QSFP+ quad-breakout cable to stack two peers, the QSFP+ port must be set to port mode 4x10G and reloaded before setting it to stack mode (described in the next section). From the interface configuration CLI prompt, use the hardware profile command to set the port to this mode. The command is: console(config-if-Fo5/0/1)#hardware profile portmode 4x10g This command will not take effect until the switch is rebooted. When the portmode changes on a port, so do the interface names. For example, a QSFP+ port may be named Fo1/0/1 when in 40G mode but takes on a new identity as Te1/1/1 through Te1/0/4 when changed to 10G mode. Therefore, if it is desired to use the QSFP+ quad-breakout cable, be sure to set the port mode to 4x10G and reload the switch before setting the ports to stack mode since configuration settings on one port mode does not translate to the other portmode. Also, when in port mode 4x10G it is required that all four of the breakout ports be moved from Ethernet mode to Stack mode to use them for stacking.
14
Command-line interface method

Make sure all switches are at the same firmware version prior to configuring the stack, or use the Stack Firmware Synchronization (boot auto-copy-fw) feature to synchronize all firmware during the stack setup process to that of the Master. The boot auto-copy-fw command is explained below in this example. Connect power to all switches to be stacked. Performing the command show switch stack-ports will provide information on the unit number for the switch, which is used in the stacking commands. It also shows Interfaces of the switch that may be used for stacking and whether they are in Ethernet or Stacking mode. console#show switch stack-ports Configured Stack Interface Mode ---------- ---------Te1/0/1 Ethernet Te1/0/2 Ethernet Te1/0/3 Ethernet
. . .
Running Stack Mode ---------Ethernet Ethernet Ethernet
Link Status ---------Link Down Link Down Link Down
Link Speed (Gb/s) -----------Unknown Unknown Unknown
Te1/0/22 Te1/0/23 Te1/0/24 Fo1/1/1 Fo1/1/2 Te1/1/1 Te1/1/2 Te1/1/3 Te1/1/4 Te1/1/5 Te1/1/6 Te1/1/7 Te1/1/8
Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet
Link Down Link Down Link Down Link Down Link Down Detach Detach Detach Detach Detach Detach Detach Detach
Unknown Unknown Unknown 40 40 10 10 10 10 10 10 10 10
The example above shows a Dell PowerConnect 8132F with a QSFP+ two-port expansion module installed. The two 40G QSFP+ ports are represented by interfaces F01/1/1 and F01/1/2. We will use these two interfaces for stacking in the example below. Notice that Configured Stack Mode and the Running Stack Mode are currently both Ethernet. Perform the following commands to convert each desired port to Stack mode.
console#config console(config)#stack console(config-stack)#stack-port fortygigabitethernet 1/1/1 stack console(config-stack)#stack-port fortygigabitethernet 1/1/2 stack console(config-stack)#show switch stack-ports
15
Configured Stack Interface Mode ---------- ---------Te1/0/1 Ethernet Te1/0/2 Ethernet Te1/0/3 Ethernet
. . .
Te1/0/23 Te1/0/24 Fo1/1/1 Fo1/1/2
Ethernet Ethernet Stack Stack
Ethernet Ethernet Ethernet Ethernet
Link Link Link Link
Down Down Down Down
Unknown Unknown 40 40
The Configured Stack Mode is now Stack, but the Running Stack Mode is still Ethernet. The Running Mode changes to Stack upon reloading the switch, as instructed below. Save the configuration to the Startup-Configuration. console#copy running-config startup-config This operation may take a few minutes. Management interfaces will not be available during this time. Are you sure you want to save? (y/n) y Configuration Saved! Perform the same steps for the remaining switches. Do not forget to configure the stacking ports on the last and first switch to create a ring topology if desired. Once the switches have been configured, remove power from all switches. While powered off, cable all of the switches together using the stack ports that were configured. Select the switch to be the Master switch and power up that switch only allowing a few minutes to boot up completely. Verify the switch is up by logging into the CLI. Once the Master is up, power up the next switch in line. Allow the second switch 30 seconds to boot up, then power up the third switch. Continue to power up each switch allowing 30 seconds between powering switches. This allows each adjacent switch to be active before the next one. Failure to wait may result in another switch becoming the Master. All subsequent switches will enter the stack as Member Units. Stack Member units serial ports and management IP addresses are not accessible for managing those devices. Only the Masters management ports can be used to monitor and configure ports in the stack. Validation After the entire stack is created, it can be validated with the show switch command from the Master switch:
16
console#show switch SW --1 2 3 Management Status ---------Mgmt Sw Stack Mbr Stack Mbr Standby Preconfig Status Model ID --------- ----------PCT8164F Oper Stby PCT8164 PCT8132 Plugged-in Model ID ----------PCT8164F PCT8164 PCT8132 Switch Status -------OK OK OK Code Version ------5.0.0.3 5.0.0.3 5.0.0.3
The show switch stack-ports command can also be used to see all of the ports that have been added to the stack as well as which ones are being used for stacking. To view only ports that are configured for stacking, use the command show switch stack-ports | include Stack. Figure 11 shows the Stack LED that is located on the back panel of every Dell PowerConnect 8100 series switch.
Figure 11.
Stacking LED for the Dell PowerConnect 8100/8100F series switch
When the switch is the Master of a stack, the LED glows solid blue. If it is a stack member only, it glows a solid amber. When in stand-alone mode, the LED is off. Note: Each stack members role (including the Master and Standby) can be defined any time after the initial stack is created.
Web interface method

Make sure all switches are at the same firmware version prior to configuring the stack, or use the Stack Firmware Synchronization (boot auto-copy-fw) feature to synchronize all firmware during the stack setup process to that of the Master. The boot auto-copy-fw command is explained below in this example. Select a switch to be Master of the stack and for managing all ports and member units with the stack. Login to the Web UI for this switch by entering the IP address of the switch into a supported Web browser. A username and password is required and should be setup beforehand on each switch. See the switch User Guide for more information regarding username, password, and Web access.
17
After login, the first screen to appear is the Home screen, which shows the current stacking member number. Before stacking, the single member has the Stack number of 1 (one).
The example above shows a Dell PowerConnect 8132F with a QSFP+ two-port expansion module installed in Slot 1. The two 40G QSFP+ ports are interfaces F01/1/1 and F01/1/2. We will use these two interfaces for stacking in the example below. Click System > Stack Management > Stack Port Summary to bring up the next page used to select the ports for stacking. For this example ports F01/1/1 and F01/1/2 are used.
18
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F Selecting the Edit check box activates the drop-down menu in the Configured Stack-mode column. Use this menu to change port modes from Ethernet to Stack.
Clicking Apply at the bottom of the screen with set the Configured Stack Mode to Stack, but the Running Stack Mode remains Ethernet until the switch is reloaded as instructed below. Save the configuration to the Startup-Configuration on the System > File Management > Copy Files page.
19
Perform the same steps for the remaining switches. Dont forget to configure stacking ports on the last and first switch to create a ring topology if desired. Once every switch has been configured, remove power from all switches. While powered off, cable all of the switches together using the stack ports that were configured. Select the switch that is desired to be the Master switch and power up that switch only, allowing a few minutes to boot up completely. Verify the switch is up by logging into the CLI. Once the Master is up, power up the next switch in line. Allow the second switch 30 seconds to boot up, then power up the third switch. Continue to power up each switch allowing 30 seconds between powering switches. This allows each adjacent switch to be active before the next one. Failure to wait may result in another switch becoming the Master. All subsequent switches enter the stack as Member Units. Stack Member units serial ports and management IP addresses are not accessible for managing those devices. Only the Masters management ports can be used to monitor and configure ports in the stack. Validation After the entire stack is created, it can be validated from the Master switch Web UI by going to System > Stack Management > Stack Summary.
20
The following figure shows shows the Stack LED that is located on the back panel of every Dell PowerConnect 8100 series switch.
Figure 12.
Stacking LED for the Dell PowerConnect 8100/8100F series switch
When the switch is the Master of a stack, the LED glows solid blue. If it is a stack member only, it glows solid amber. When in stand-alone mode, the LED is off. Note: Each stack members role (including the Master and Standby) can be defined at any time after the initial stack is created.
Automatic firmware updates for new members joining the stack

For member units to work properly within a stack, they need to have the same firmware as the Master. Perform a manual update of the firmware on a new member to synchronize the firmware prior to cabling it into the stack. Or, another way to accomplish this is to configure the Master switch to use Stack Firmware Synchronization, which automatically upgrades firmware on new members as they join the stack. In the event the new stack member unit being added has a newer firmware version, a downgrade is also allowed. To prevent the downgrade of the new stack member units firmware, the Master needs to be configured with the Allow-Downgrade option. This allows all new member units to synchronize with the Master only if the firmware revision of the new members is older than that of the Master. Use the System > Stack Management > Stack Firmware Synchronization page to view and set these features.
21
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F Caution: 5.0.x.x firmware will not load on a switch with the newer B1 CPU. It is therefore recommended to upgrade all PowerConnect 8100 switches to the latest firmware. See Important Firmware Update for PowerConnect 81xx Stacking at the beginning of this document for more information.
Save the configuration to the Startup-Configuration on the System > File Management > Copy Files page.
22
Adding new member units to a stack

It is important that all stack member units run the same version of firmware. Make sure to either upgrade firmware on the new units to be added to match the firmware on the Master, or use the automatic firmware update method found in section Automatic firmware updates for new members joining the stack. Caution: 5.0.x.x firmware will not load on a switch with the newer B1 CPU. It is therefore recommended to upgrade all PowerConnect 8100 switches to the latest firmware. See Important Firmware Update for PowerConnect 81xx Stacking at the beginning of this document for more information. The example below shows how to add a stack member to an existing stack. Before cabling a new switch into the stack, perform the commands below to setup the switch ports to be stacked. Once configured, continue to follow the instructions for cabling to complete the task. If multiple new members are to be added, complete the installation of one switch before going to the next. Complete these steps again for each switch to be added. This example allows adding new members without preconfiguring the existing stack, though the new members themselves will need to be configured. To preconfigure a stack before connecting the new stack member, consult the User Guide under Preconfiguring a Stack Member.

Run the commands below on the switch to be added using either the console port or a telnet session. console#show switch stack-ports Configured Stack Interface Mode ---------- ---------Te1/0/1 Ethernet Te1/0/2 Ethernet Te1/0/3 Ethernet
. . .
Te1/0/22 Te1/0/23 Te1/0/24 Fo1/1/1 Fo1/1/2 Te1/1/1 Te1/1/2 Te1/1/3 Te1/1/4 Te1/1/5 Te1/1/6 Te1/1/7 Te1/1/8
Link Down Link Down Link Down Link Down Link Down Detach Detach Detach Detach Detach Detach Detach Detach
Unknown Unknown Unknown 40 40 10 10 10 10 10 10 10 10
23
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F Notice the two 40G QSFP+ ports represented by interfaces F01/1/1 and F01/1/2. These two interfaces will be used for stacking in the example below, though any of the interfaces listed may be used. Perform the following commands to convert each desired port to Stack mode. console#config console(config)#stack console(config-stack)#stack-port fortygigabitethernet 1/1/1 stack console(config-stack)#stack-port fortygigabitethernet 1/1/2 stack
console(config-stack)#show switch stack-ports | include Stack Fo1/1/1 Fo1/1/2 Stack Stack Stack Stack Ethernet Ethernet Link Link Down Link Down Link 40 40
The Configured Stack Mode is now Stack, but the Running Stack Mode is still Ethernet. The Running Mode changes to Stack upon reloading the switch, as instructed below. Save the configuration to the Startup-Configuration. console#copy running-config startup-config This operation may take a few minutes. Management interfaces will not be available during this time. Are you sure you want to save? (y/n) y Configuration Saved! Remove power from the switch. Note: Hot insertion of units into the stack is not supported. Do not connect a new member to the stack while the new unit is powered up. Follow the steps in the following section to properly add the stacking cables and complete the process. Ring vs. daisy-chain topology If the original stack is cabled in a ring topology where a stacking port on the last switch is connected to a stacking port on the first switch, the entire stack continues to work correctly through the process of adding a new switch regardless of where the new switch is cabled within the stack. This is due to the built-in resiliency of the ring topology that allows all switches to remain in communication with each other in the event a single link or switch is lost or removed. When adding a switch to a daisy-chain topology stack, add it to one end of the stack and not in the middle. Adding to the middle requires breaking the daisy-chained stack which will cause the stack to split, creating a new Master on the group of switches that lost contact with the original Master. This 24
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F would result in two stacks. Adding a new switch to the either end of the daisy-chain allows all other members to stay in constant communication and in turn allow the stack to stay intact during the process. On a daisy-chain stack: 1. Configure the existing stack with new stack ports to be used to connect to the new switch. 2. Cable the new switch into the existing stack. 3. Power up the new switch. The switch will be added to the stack.
On a ring topology stack: 1. Plug new cables into half of the stack ports configured on the new switch to be added. 2. Unplug the stacking cables from any existing member going to another existing member in the stack. Only unplug the cables from one end, leaving them plugged into the other member. Note: Only half of the stack cables in this member will be unplugged. The cables going in the other direction to a third existing member will not be removed. 3. Plug the other end of the new cables of the switch being added into the stack ports that were unplugged in step 2. 4. Plug the remaining cable ends (removed in step 2) into the remaining stack ports configured on the new switch unit. 5. Power up the new switch. The switch will be added to the stack. Allow a few minutes for the new switch to boot up completely. Validation After the entire stack is created, it can be validated with the show switch command from the Master switch: console#show switch SW --1 2 3 4 Management Status ---------Mgmt Sw Stack Mbr Stack Mbr Stack Mbr Standby Preconfig Status Model ID --------- ----------PCT8164F Oper Stby PCT8164 PCT8132 PCT8132F Plugged-in Model ID ----------PCT8164F PCT8164 PCT8132 PCT8132F Switch Status -------OK OK OK OK Code Version ------5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3
The example above shows a new stack member (PCT8132F) was added. The show switch stackports command can also be used to see all of the ports that have been added to the stack as well as which ones are being used for stacking. If a switch (SW) number is configured prior to adding it to the stack and there are no other devices using that number, then the switch continues to use the same number. Otherwise, the switch sets its number to the lowest unassigned number upon joining the stack. 25
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F Note: Once added to a stack, a switchs out -of-band IP address and console port are no longer accessible. Use the IP address and console port of the Master unit for management access, since the stack now acts as a single large switch. Repeat the above steps to add more new members to the stack.
26

The example below shows how to add a stack member to an existing stack using the Web user interface. Before cabling an additional member to a stack, perform the steps below to setup the switch to join the stack. Once configured, continue to follow the instructions for cabling to complete the task. This works best when adding one stack member at a time. If multiple new members are to be added, follow these directions and complete the install of one before going to the next. Complete these steps again for each remaining switch to be added. Caution: 5.0.x.x firmware will not load on a switch with the newer B1 CPU. It is therefore recommended to upgrade all PowerConnect 8100 switches to the latest firmware. See Important Firmware Update for PowerConnect 81xx Stacking at the beginning of this document for more information. Note: The example given below allows the new member to be added without preconfiguring the existing stack, though the new member itself needs to be configured. To preconfigure a stack before connecting the new stack member, consult the User Guide under Preconfiguring a Stack Member. On the new member switch to be added to the stack, select System > Stack Management > Stack Port Summary from the main navigation menu. In this example, two 40G QSFP+ interfaces F01/0/1 and F01/0/2 will be used for stacking, though any of the interfaces shown may be used.
In the Edit column, select the check box to allow editing on the ports to be used for stacking. Then use the drop-down menu in the Configured Stack-mode column to put each port in stack mode. The Configured Stack Mode is now Stack, but the Running Stack-mode does not show Stack until the switch is reloaded, as instructed below. Save the configuration to the Startup-Configuration using the System > File Management > Copy Files page.
27
After saving the configuration, remove power from the switch. Note: Hot insertion of units into the stack is not supported. Do not connect a new member to the stack while the new unit is powered up. Follow the steps in the following section to properly add the stacking cables and complete the process. Ring vs. daisy-chain topology If the original stack is cabled in a ring topology, where a stacking port on the last switch is connected to a stacking port on the first switch, the entire stack continues to work correctly through the process of adding a new switch regardless of where the new switch is cabled within the stack. This is due to the built-in resiliency of the ring topology that allows all switches to remain in communication with each other in the event a single link or switch is lost or removed. When adding a switch to a daisy-chain topology stack, add it to one end of the stack and not in the middle. Adding to the middle requires breaking the daisy-chained stack, which causes the stack to split, creating a new Master on the group of switches that lost contact with the original Master. This would result in two stacks. Adding a new switch to the either end of the daisy-chain allows all other members to stay in constant communication and in turn allow the stack to stay intact during the process. On a daisy-chain stack: 1. Configure the existing stack with new stack ports to be used to connect to the new switch. 2. Cable the new switch into the existing stack. 3. Power up the new switch. The switch will be added to the stack. On a ring topology stack: 1. Plug new cables into half of the stack ports configured on the new switch to be added. 28
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F 2. Unplug the stacking cables from any existing member going to another existing member in the stack. Only unplug the cables from one end, leaving them plugged into the other member. Note: Only half of the stack cables in this member will be unplugged. The cables going in the other direction to a third existing member will not be removed. 3. Plug the other end of the new cables of the switch being added into the stack ports that were unplugged in step 2. 4. Plug the remaining cable ends (removed in step 2) into the remaining stack ports configured on the new switch unit. 5. Power up the new switch. The switch will be added to the stack. Allow a few minutes for the new switch to boot up completely. Validation After the entire stack is created, validate it with the show switch command from the Master switch:
The example above shows a new stack member (Unit 4) was added. If a switch (SW) number is configured prior to adding it to the stack and there are no other devices using that number, then the switch continues to use the same number. Otherwise, the switch sets its number to the lowest unassigned number upon joining the stack. Note: Once added to a stack, a switchs out -of-band IP address and console port are no longer accessible to the user. Use the IP address and console port of the Master unit for management access, since the stack now acts as a single large switch. Repeat the above steps to add more new members to the stack.
29
Updating firmware on a stack

Note: Make sure to check the Release Notes and any special instructions that may have come with new firmware updates. It is important to follow instructions found in those documents if they deviate from this white paper. Steps for upgrading the firmware on a stack of switches are similar to upgrading the firmware on a single switch. Whether downloading a new image to the Master by using the System > File Management > File Download page in the Web UI or the copy command in the CLI, the downloaded image is distributed to all member units of the stack. The instructions below guide the user through these steps.

To find the firmware versions the stack members are using, enter the following. console#show version Image Descriptions active : backup : Images currently available on Flash unit ----1 2 3 4 active -----------5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 backup -----------4.2.0.0 4.2.0.0 4.2.0.0 4.2.0.0 current-active next-active ----------------- ----------------5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1
Each member of the stack is updated with the latest firmware simply by updating the Master switch. The commands below demonstrate how to copy the firmware file down to the Master using a TFTP server. The stack needs access to the TFTP server on the network and the firmware file needs to be present in the download folder of the TFTP server. Perform the following command from the CLI interface. Press y when prompted. console#copy tftp://10.10.1.10/PC8100v5.0.0.3.stk backup Transfer Mode.................................. Server IP Address.............................. Source File Path............................... Source Filename................................ Data Type...................................... Destination Filename........................... TFTP 10.10.1.10 ./ PC8100v5.0.0.3.stk Code backup
Management access will be blocked for the duration of the transfer Are you sure you want to start? (y/n) y TFTP code transfer starting 12487236 bytes transferred... File contents are valid. Copying file to flash... 30
Attempting to send the STK file to other units in the stack File transfer operation completed successfully.
Note: This procedure may take a few minutes longer than updating a single, non-stacked switch. Perform another show version command to see the new firmware has been downloaded to all members of the stack. Notice the firmware was only copied into the backup image for each member. console#show version Image Descriptions active : backup : Images currently available on Flash unit ----1 2 3 4 active -----------5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 backup -----------5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3 current-active next-active ----------------- ----------------5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1
The backup column now shows the same values as the active column. The next step is to activate the image that contains the new firmware by using the boot system backup command. console#boot system backup Activating image backup .. console#show version Image Descriptions active : backup : Images currently available on Flash unit ----1 2 3 4 active -----------5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 backup -----------5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3 current-active next-active ----------------- ----------------5.0.0.1 5.0.0.3 5.0.0.1 5.0.0.3 5.0.0.1 5.0.0.3 5.0.0.1 5.0.0.3
31
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F Notice the next-active column now shows the same version as the backup column. Next, type the reload command to complete the update. All switches in the stack reloads. console#reload Are you sure you want to reload the stack? (y/n) y Connection to host lost. The Connection to host lost message appears only if performing the reload from a telnet session. It will not appear if performing the command from a console session. Updating and rebooting the stack takes a few minutes longer than a single switch. After reload, the firmware upgrade is complete. To validate, login to the stack Master and perform a show version command. For the example given the following is displayed. console#show version Image Descriptions active : backup : Images currently available on Flash unit ----1 2 3 4 active -----------5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3 backup -----------5.0.0.1 5.0.0.1 5.0.0.1 5.0.0.1 current-active next-active ----------------- ----------------5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3
Notice as the backup becomes active, the active becomes the backup.

Find the firmware versions the stack members are using. Select System > File Management > Active Images. Look in the Current-Active column to find which images are enabled. In this example all three switches are currently using image2. Note: It is acceptable if some units are using image1 and others are using image2. Since image2 is active, look in the Image 2 Version column to see what version each stack member is at. These firmware versions being used should be the same across all stack member units.
32
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F To find the firmware versions the stack members are using, go to System > File Management > Active Images.
Each member of the stack will be updated with the latest firmware simply by updating the Master switch. The screenshot below demonstrate how to copy the firmware to the Master using a TFTP server. The stack needs access to a TFTP server on the network and the firmware file needs to be present in the download folder of the TFTP server. From the System > File Management > File Download page, select the appropriate settings. The most common settings are shown here.
33
Click Apply. A warning will appear.
Click OK. Note: Be patient as this procedure may take several minutes longer than updating a single, non-stacked switch. The following screen appears for several minutes while the firmware is being downloaded to the Master and distributed to all members of the stack.
34
Once the file has been distributed to the entire stack, the following dialog box appears.
Click Close. Go back to the Active Images screen to confirm that the new firmware was downloaded to all members of the stack. Notice the firmware was only copied into the backup image for each member.
35
The next step is to activate the image that contains the new firmware using the drop-down menus in the Next Active Image column. In this example the backup image is selected for each unit.
After selecting backup for each unit, click Apply. Go to the System > General > Reset page to reload the switch.
36
Click Apply to reload all switches in the stack. If the following screen appears, click OK.
Click OK again if this screen appears.
If either of the following screens appear, they are simply notifying the user that the network has been lost. This is only temporarily while the stack reloads.
37
Click OK if prompted with the above screen. Rebooting the stack may take a few minutes longer than a single switch. After reload, the firmware upgrade is complete. To validate each switch, login again to the Web UI of the stack Master, and then go to System > File Management > Active Images.
Notice that as the backup versions become active, the previous active versions now become the backup. This allows the administrator to toggle back to the previous image if needed for troubleshooting. Going back to the previous version is rarely ever used and must be done with extreme caution if the newer firmware has been running a long time with several configuration changes since the initial upgrade. Newer firmware can have dozens of valuable bug fixes that will not be there on the older firmware.
Removing member units

This section provides guidance on how to remove member units from a stack while minimizing traffic flow interruptions within the stack. Removing any member of a ring topology stack does not require a reload of any member unit in the stack. If a unit in the stack fails, the Master unit removes the failed unit from the stack and no changes or configuration are applied to the other stack members; however, the dynamic protocols will try to reconverge as the topology could change because of the failed unit. When there are no connected ports on the failed unit, the stack will be intact without changes. The example below demonstrates how to manually remove a single member while keeping the stack intact.
38

Since any interface on these switches can be used for stacking, make sure to verify exactly which ports are being used for stacking so they are un-cabled and re-routed last. This information is found with the following command. console#show switch stack-ports Configured Running Stack Stack Link Link Interface Mode Mode Status Speed (Gb/s) -------------- ---------- ---------- ------------ -----------Te1/0/45 Stack Stack Link Up 10 Te1/0/46 Stack Stack Link Up 10 Te1/0/47 Stack Stack Link Up 10 Te1/0/48 Stack Stack Link Up 10
:
Te2/0/21 Te2/0/22 Te2/0/23 Te2/0/24 Stack Stack Stack Stack Stack Stack Stack Stack Stack Stack Stack Stack Stack Stack Stack Stack Link Link Link Link Link Link Link Link Up Up Up Up Up Up Up Up 10 10 10 10 10 10 10 10
:
Te3/0/45 Te3/0/46 Te3/0/47 Te3/0/48
:
Note: To narrow the list to only view ports configured for stacking, use the command show switch stack-ports | include Stack. Make sure to capitalize Stack since the command is case sensitive. Look for interfaces shown to be in Stack mode. The logical stack unit number is represented in each interface name. The first number in the interface name is the logical stack unit. For example, interface Te2/0/21 is in logical unit number 2. A blinking LED light can be generated on the back of each PowerConnect 81xx to locate each physical unit. This blinking LED is useful when identifying physical units and ports for running diags, sniffing, mirroring ports, and other basic troubleshooting. It is also helpful when adding, removing, replacing or tracing cables associated with these interfaces. Use the locate switch command to blink the blue Locator LED on the switch unit you are trying to locate. console#locate switch 2 The LED locator light on switch 2 blinks for 20 seconds. The length of time the LED continues to blink can be changed using the locate time <ssss> command, where ssss is the time in seconds for the LED to blink. Removing the physical switch unit from the stack Before removing a physical unit from a stack, prepare ports on the other stack member units to receive the cables and traffic that is redirected to them from the member unit being removed. Consider all
39
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F LAGs, VLANs, STP, ACLs, security, and so on, that needs to be configured on the new ports to accept cables, establish links, and begin to forward traffic. Note: It is highly recommended not to continue until these things have been considered and proper preparations are made. Note: Do not remove or re-route stacking cables until prompted in the last step below. Do not remove or re-route stacking cables until prompted. Disconnect all other links on the member to be removed and re-route the traffic that was going through this unit so it now goes through the ports that were prepared on the remaining stack unit members. Caution: In the next step, make sure to keep track of all ports being used for stacking that will be temporarily unplugged. They need to be re-cabled in the following step. Only after re-routing the traffic through the remaining stack units, remove the stacking cables from the switch to be removed. The switch being removed does not need to be powered off. Keeping the switches power on automatically brings it to a stand-along state as the stack cables are removed. In the example below (Figure 13), the red quad-breakout cable is removed along with the switch.
Figure 13.
Cabling of five stacked units

1 3 5 7 9 11 13 15 17 19 21 LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
11
13
15
17
19
21
LNK 23 ACT
SWITCH TO BE REMOVED FROM STACK

2 4 6 8 10 12 14 16 18 20 22 24
Use the freed cables or new cables to connect the two switches together that were previously adjacent to the switch being removed. Since there are multiple interface and cable types supported for stacking, a different set of cables may be required to make this connection.
40
Figure 14.
1
Removal of a stack unit

3 5 7 9 11 13 15 17 19 21 LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
SWITCH REMOVED FROM STACK
11
13
15
17
19
21
LNK 23 ACT
10
12
14
16
18
20
22
24
Removal of a stack unit results in one or more freed cables. In this example, there is a freed quadbreakout cable (red) that was used to link the bottom unit to the one directly above it. The second quad-breakout cable is then used to connect the top and bottom units to again complete the ring topology. Note: A QSFP+ quad-breakout cable connects one QSFP+ 40GE port to four SFP+ 10GE ports. Alternatively, once the unit is removed, the remaining quad-breakout cable could be replaced with a QSFP+ cable to connect the top and bottom stack members. This would free up four SFP+ interfaces, but would require the use of another QSFP+ interface. The interfaces used for stacking is based on the administrators preference. Validation To validate the stack unit has been removed and that the remaining stack members are still intact, type the show switch command. console#show switch SW --1 2 3 4 5 Management Status ---------Mgmt Sw Stack Mbr Stack Mbr Stack Mbr Unassigned Standby Preconfig Status Model ID --------- ----------PCT8132 Oper Stby PCT8164 PCT8164 PCT8132F PCT8132F Plugged-in Model ID -----------PCT8132 PCT8164 PCT8164 PCT8132F Switch Status ----------OK OK OK OK Not Present Code Version --------5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3
41
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F Removing units from the stack configuration Once a unit has been physically removed, it may be desired to remove it from the configuration as well, if there are no plans on restoring it later. For the above example Unit 5 wasremoved; however, the show switch command continues to show the removed switch in the configuration. Issuing a no member command in Stack Configuration mode deletes the removed switch from the configured stack information. console(config)#stack console(config-stack)#no member 5 console(config-stack)#show switch Management Status ---------Mgmt Sw Stack Mbr Stack Mbr Stack Mbr Standby Preconfig Status Model ID --------- ----------PCT8132 Oper Stby PCT8164 PCT8164 PCT8132F Plugged-in Model ID -----------PCT8132 PCT8164 PCT8164 PCT8132F Switch Status ----------OK OK OK OK Code Version --------5.0.0.3 5.0.0.3 5.0.0.3 5.0.0.3
SW --1 2 3 4
Notice that Unit 5 is no longer present in the configuration. A backup of the configuration (copy running-config startup-config) is required to make the change persist after a reload. Renumbering stack units It may be desired to renumber switches in the stack. While this feature may be used at any time, it is most commonly used after a switch has been removed and the remaining unit numbers are no longer consecutive. While inconsecutive numbers or numbers out of order do not impact traffic in any way, keeping an order can help quickly identify individual units and ports. A switch may be any number between 1 and 6 as long as it is not already taken by another switch. If it is desired to renumber the switch units to show units 1-2-3, instead of 1-2-4, it will require a brief reset of the stack and clear the configuration of the interfaces on the switch receiving the new number. Type the command show switch to see the current order of the units before renumbering. console#show switch Management Standby SW Status Status --- ---------- --------1 Stack Mbr Oper Stby 2 Mgmt Sw 4 Stack Mbr Preconfig Model ID ---------PCT8164F PCT8132F PCT8164F Plugged-in Model ID ----------PCT8164F PCT8132F PCT8164F Switch Status ---------OK OK OK Code Version ---------5.0.0.3 5.0.0.3 5.0.0.3
Caution: Renumbering stack units may hinder management scripts and monitoring software that collects data based on particular port traffic. Use renumbering with caution when monitoring ports and be aware that scripts and monitoring parameters may need to be modified.
42
Type the switch renumber command to change the number of the switch. console(config)#switch 4 The switch will be reset and the configuration of Are you sure you want to renumber 3 to perform unit renumbering switch interfaces will be cleared. renumber? (y/n)y
Allow a few minutes for the switch to renumber, then enter the following. console#show switch Management Standby SW Status Status --- ---------- --------1 Stack Mbr Oper Stby 2 Mgmt Sw 3 Stack Mbr 4 Unassigned
Preconfig Model ID ---------PCT8164F PCT8132F PCT8164F PCT8164F
Plugged-in Model ID ----------PCT8164F PCT8132F PCT8164F
Switch Status ---------OK OK OK Not Present
Code Version ---------5.0.0.3 5.0.0.3 5.0.0.3 0.0.0.0
The switch that was Unit #4 is now Unit #3. Unit #4 is no longer present. To remove it from the list, perform the no member command in Stack Configuration Mode. console(config)#stack console(config-stack)#no member 4 console(config-stack)#show switch Management Standby Preconfig SW Status Status Model ID --- ---------- --------- ---------1 Stack Mbr Oper Stby PCT8164F 2 Mgmt Sw PCT8132F 3 Stack Mbr PCT8164F
Plugged-in Model ID ----------PCT8164F PCT8132F PCT8164F
Switch Status ---------OK OK OK
Code Version ---------5.0.0.3 5.0.0.3 5.0.0.3
Configuring a removed unit to be stand-alone After removing a unit from a stack, the unit converts back to its original configuration that it had prior to adding it to the stack, retaining the IP address, VLAN, LAG, and other settings. This allows immediate access to the stand-alone through the out-of-band port if previously configured. Note: A duplicate address could occur on the network if another device was assigned the IP address of the device while it was a stack member. If this occurs simply detach the device from the network and change the IP address through the console port. Meta-data will remains on the switch until cleared or changes are made to the stack settings, but will not affect functions of the switch. For example, a stand-alone switch is assigned to be unit #1. Upon joining the stack it was assigned to be unit #3. When it is removed from the stack it will retain the assignment of unit #3 until changed by the administrator. For instructions on how to make this change, see Renumbering stack on page 42.
43

Since any interface on the 8100 series switches can be used for stacking, make sure to verify exactly which ports are being used for stacking so they are un-cabled and re-routed last, after the normal traffic-passing cables have been re-routed. This information is found at System > Stack Management > Stack Port Summary.
Note: Clicking the Configured Stack-mode column header brings all Stack ports to the top of the list. Look for interfaces shown to be in Stack mode. The logical stack unit number is represented in each interface name. The first number in the interface name is the logical stack unit. For example, interface Te2/0/21 is in logical unit number 2. A blinking LED light is generated on the back of each Dell PowerConnect 81xx to locate each physical unit. This blinking LED is useful when identifying physical units and ports for running diags, sniffing, mirroring ports, and other basic troubleshooting. It is also helpful when needing to add, remove, replace or trace cables associated with these interfaces. Use the locate switch CLI command to blink the blue Locator LED on the switch unit you are trying to locate. console#locate switch 2 The LED locator light on switch 2 blinks for 20 seconds. The length of time the LED continues to blink can be changed using the locate time <ssss> command, where ssss is the time in seconds for the LED to blink. Removing the physical switch unit from the stack Before removing a physical unit from a stack, prepare the ports on the other stack member units to receive the cables and traffic that will be redirected to them from the member unit being removed. 44
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F Consider all LAGs, VLANs, STP, ACLs, security, and so on, that needs to be configured on the new ports in order to accept cables, establish links, and begin to forward traffic. Note: It is highly recommended not to continue until these things have been considered and proper preparations are made. Note: Do not remove or re-route stacking cables until prompted in the last step below. Do not remove or re-route stacking cables until prompted. Disconnect all other links on the member to be removed and re-route the traffic that was going through this unit so it now goes through the ports that were prepared on the remaining stack unit members. Caution: In the next step, be sure to keep track of all ports being used for stacking that will be temporarily unplugged. They need to be re-cabled in the following step. Only after re-routing the traffic through the remaining stack units, remove the stacking cables from the switch to be removed. The switch being removed does not need to be powered off. Keeping the switches powered on automatically brings it to a stand-along state as the stack cables are removed. In the example below, the red quad-breakout cable will be removed along with the switch.
Figure 15.
Cabling of five stacked units.

1 3 5 7 9 11 13 15 17 19 21 LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
11
13
15
17
19
21
LNK 23 ACT
SWITCH TO BE REMOVED FROM STACK

2 4 6 8 10 12 14 16 18 20 22 24
Use the freed cables or new cables to connect the two switches together that were previously adjacent to the switch being removed. Since there are multiple interface and cable types supported for stacking, a different set of cables may be required to make this connection.
45
Figure 16.
1
Removal of a stack unit

3 5 7 9 11 13 15 17 19 21 LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
41
43
45
LN K
A 47 CT
LNK
LNK
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
ACT
ACT
11
13
15
17
19
21
LNK 23 ACT
LNK
LNK
10
12
14
16
18
20
22
24
ACT
QSFP+ MODULE
ACT
SWITCH REMOVED FROM STACK
11
13
15
17
19
21
LNK 23 ACT
10
12
14
16
18
20
22
24
Removal of a stack unit results in one or more freed cables. In this example, there is a freed quadbreakout cable (red) that was used to link the bottom unit to the one directly above it. The second quad-breakout cable is then used to connect the top and bottom units to again complete the ring topology. Note: A QSFP+ quad-breakout cable is one that allows the user to connect one QSFP+ 40GE port to four SFP+ 10GE ports. Alternatively, once the unit is removed, the remaining quad-breakout cable could be replaced with a QSFP+ cable to connect the top and bottom stack members. This would free up four SFP+ interfaces, but requires the use of another QSFP+ interface. The interfaces used for stacking is based on the users preference. Validation To validate the stack unit was removed and that the remaining stack members are still intact, go to System > Stack Management > Stack Summary.
46
Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F Removing units from the stack configuration Once a unit has been physically removed, it may be desired to remove it from the configuration as well, if there are no plans on restoring it later. For the above example Unit 5 was removed; however, the Stack Summary screen continues to show the removed switch in the configuration. To remove the switch from the configuration, go to the System > Stack Management > Unit Configuration screen. Select the Switch ID of the switch to be removed, and then check the Remove Switch check box at the bottom of the bottom of the screen.
Clicking Apply deletes the removed switch from the stack configuration on the running-configuration. Go back to the Stack Summary screen to verify the switch was removed. A backup of the configuration (copying the running-configuration to the startup-configuration) in System > File Management > Copy Files is required to make the change persist after a reload. Renumbering stack units It may be desired to renumber switches in the stack. While this feature may be used at any time, it is most commonly preferred after a switch has been removed and the remaining unit numbers are no longer consecutive. While inconsecutive numbers or numbers out of order do not impact traffic in any way, keeping an order can help quickly identify individual units and ports. A switch may be any number between 1 and 6 as long as it is not already taken by another switch. If it is desired to renumber the switch units to show units 1-2-3, instead of 1-2-4, it requires a brief reset of the stack and clear the configuration of the interfaces on the switch receiving the new number. View the System > Stack Management > Stack Summary to see the current numbering of each unit. 47
Select the Switch ID to be assigned as the Standby. Use the Unit Type drop-down menu and select Configured Standby. Note: Assigning the current Stack Master to the Standby role is not allowed using this method and results in an error. Instead, use the initiate failover method described below. Click Apply. Copying the running-configuration to the startup-configuration is not required. This setting will be persistent after a reload. Verify the new Standby switch from the Stack Summary screen.
53
If there is a need to change the role of the Master or make the Standby the Master, use the initiate failover command from the Command Line Interface. This command results in a warm restart of the stack Master, triggering the Standby unit to take over as a new Master switch. console(config)#stack console(config-stack)#initiate failover The system has unsaved changes. Would you like to save them now? (y/n) y Configuration Saved! Management unit will be reloaded. Are you sure you want to failover to the backup unit? (y/n) y Connection to host lost. This message is seen in telnet sessions.
If using the CLI through the console port, the session will no longer be valid. The console port on the new Master switch will now be activated for management. The IP and MAC addresses of the stack remains the same with the new Master. If using a telnet session, log in using the same IP address as before.
54
Appendix A Commands used in this document

All CLI commands used in this document, along with a brief description, are listed below in order of appearance. Some commands are used multiple times in the document. Command show run show switch show system hardware profile portmode 4x10g (from config-if) boot auto-copy-sw (from config#) show switch stack-ports show switch stack-ports | include Stack stack (from config#) stack-port fortygigabitether 1/1/1 stack (from configstack#) copy running-config startup-config show version m copy tftp://10.10.1.10/PC8100v5.0.0.3.stk backup boot system backup reload locate switch 2 no member 5 (from config-stack#) switch 4 renumber 3 (from config#) standby 3 (from config-stack#) initiate failover (from config-stack#) Definition Shows running configuration Shows all stack members and roles Shows MAC address Changes a QSFP+ port to 4x10G Allows for automatic firmware updates Shows available ports for stacking Shows only ports in stack mode Stack configuration mode Turns on stacking on a port Backs up the running configuration Shows firmware and CPU versions on units Example of firmware download using tftp Activates the backup image to be active Reloads the stack Blinks the locate LED on rear of switch Removes a unit from the stack config Renumbers a unit in the stack Changes the standby to another unit Causes Master to failover to the standby
Appendix B - Network switch versions

Version information for the network switches used in creating this document are as follows: Network switch Software version Dell PowerConnect 8100 5.0.0.3, 5.0.0.4, 5.1.0.0
About Dell
Dell is a leading technology provider to commercial and public enterprises around the world.
55

Stacking PowerConnect 8100 v1.1

Uploaded by

Copyright:

Available Formats

Stacking PowerConnect 8100 v1.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Stacking PowerConnect 8100 v1.1

Uploaded by

Copyright:

Available Formats

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Victor Teeter Network Solutions Engineer

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Stacking scenarios ....................................................................................... 11

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Important Firmware Update for PowerConnect 81xx Stacking

Firmware 5.0.x.x is no longer recommended

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Errors Downgrading Firmware

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Dell PowerConnect 8132

Dell PowerConnect 8132F

Dell PowerConnect 8164

Dell PowerConnect 8164F

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Stacking and management

Simplified firmware updates for stack members

Stacking and redundancy

Nonstop forwarding on the stack

Hot add/delete and firmware synchronization

How a Master is selected

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

How to select a Master during initial stack setup

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

10G SFP+ MODULE

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

QSFP+ quad-breakout cables

QSFP+ quad-breakout cable may be used for stacking

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Command-line interface method

Running Stack Mode ---------Ethernet Ethernet Ethernet

Link Status ---------Link Down Link Down Link Down

Link Speed (Gb/s) -----------Unknown Unknown Unknown

Unknown Unknown Unknown 40 40 10 10 10 10 10 10 10 10

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Running Stack Mode ---------Ethernet Ethernet Ethernet

Link Status ---------Link Down Link Down Link Down

Link Speed (Gb/s) -----------Unknown Unknown Unknown

Te1/0/23 Te1/0/24 Fo1/1/1 Fo1/1/2

Ethernet Ethernet Stack Stack

Ethernet Ethernet Ethernet Ethernet

Link Link Link Link

Down Down Down Down

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Stacking LED for the Dell PowerConnect 8100/8100F series switch

Web interface method

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Stacking LED for the Dell PowerConnect 8100/8100F series switch

Automatic firmware updates for new members joining the stack

Stacking Dell PowerConnect Switches: 8132, 8132F, 8164, 8164F

Adding new member units to a stack

Command-line interface method

Running Stack Mode ---------Ethernet Ethernet Ethernet

Link Status ---------Link Down Link Down Link Down