Cisco Catalyst 3560-CX User manual

Managing Switch Stacks
•Prerequisites for Switch Stacks, on page 1
•Restrictions for Switch Stacks, on page 1
•Information About Switch Stacks, on page 1
•How to Configure a Switch Stack, on page 11
•Troubleshooting the Switch Stack, on page 18
•Monitoring the Device Stack, on page 20
•Configuration Examples for Switch Stacks, on page 21
•Additional References for Switch Stacks, on page 24
Prerequisites for Switch Stacks
Restrictions for Switch Stacks
There are no restrictions with Horizontal Stacking on Catalyst 3560cx.
Information About Switch Stacks
Horizontal Stacking
The Catalyst 3560CX series switches supporting 10G SFP+ uplink ports and MGig ports can be part of
horizontal stacking. We can use SFP+ with the optical cables and copper cables on the MGig ports to connect
boxes placed at different location to form a stack, where the compact boxes are placed in different floors or
buildings. We can form half-ring or full-ring based on need, and remaining uplink ports will continue to work
as network ports.
When we convert a network port to stack port, it will continue to work as network port without any impact
to current running configuration until next reload of switch. All current configurations of that particular
network port will be lost after reload of switch once port comes up as Stack port.
When we convert a stack port back to network port it will continue to work as stack port until next reload of
switch. After reload port comes up as network port with default configuration.
Managing Switch Stacks
1

When uplink ports are working as stack ports, those particular uplink interfaces (ex: Te1/0/1) will not be listed
in any show command or will not be available under any config command, unlike any other network port.
They will be made available only after reload of the switch once ports are converted back to network.
Note
Table 1: C3560CX Switches Supporting Horizontal Stacking
Stackable PortsUplinksAccess PortsProduct ID
2 10G uplink2GE + 2SFP+12 GEWS-C3560CX-12PD-S
1 multigig and 1 10G
uplink, or 2 multigig, or 2
10G uplink
2multigig + 2SFP+6 GEWS-C3560CX-8XPD-S
Switch Stack Membership
A switch stack has up to eight stack members connected through their stack ports. A switch stack always has
one active switch.
A standalone device is a device stack with one stack member that also operates as the active switch. You can
connect one standalone device to another to create a stack containing two stack members, with one of them
as the active switch. You can connect standalone devices to an existing device stack to increase the stack
membership.
Figure 1: Creating a Switch Stack from Two Standalone Switches
Managing Switch Stacks
2
Managing Switch Stacks
Switch Stack Membership

Figure 2: Adding a Standalone Switch to a Switch Stack
Changes to Switch Stack Membership
If you replace a stack member with an identical model, the new switch functions with exactly the same
configuration as the replaced switch, assuming that the new switch (referred to as the provisioned switch) is
using the same member number as the replaced switch.
The operation of the switch stack continues uninterrupted during membership changes unless you remove the
active switch or you add powered-on standalone switches or switch stacks.
• Adding powered-on switches (merging) causes the active stack of the merging switch stacks to elect an
active stack from among themselves. The reelected active stack retains its role and configuration as do
its stack members. All remaining switches, including the former active stacks, reload and join the switch
stack as stack members. They change their stack member numbers to the lowest available numbers and
use the stack configuration of the reelected active stack.
• Removing powered-on stack members causes the switch stack to divide (partition) into two or more
switch stacks, each with the same configuration. This can cause:
• An IP address conflict in your network. If you want the switch stacks to remain separate, change
the IP address or addresses of the newly created switch stacks.
• A MAC address conflict between two members in the stack. You can use the stack-mac update
force command to resolve the conflict.
Managing Switch Stacks
3
Managing Switch Stacks
Changes to Switch Stack Membership

Make sure that you power off the switches that you add to or remove from the switch stack.
After adding or removing stack members, make sure that the switch stack is operating at full bandwidth .
Press the Mode button on a stack member until the Stack mode LED is on. The last two right port LEDs on
all switches in the stack should be green. Depending on the switch model, the last two right ports are 10-Gigabit
Ethernet ports or small form-factor pluggable (SFP) module ports (10/100/1000 ports). If one or both of these
LEDs are not green on any of the switches, the stack is not operating at full bandwidth.
It may take upto 4 seconds for stack convergence when a new stack member is added to the existing switch
stack.
Note
If you remove powered-on members but do not want to partition the stack:
• Power off the switches in the newly created switch stacks.
• Reconnect them to the original switch stack through their stack ports.
• Power on the switches.
Stack Member Numbers
The stack member number (1 to 8) identifies each member in the switch stack. The member number also
determines the interface-level configuration that a stack member uses. You can display the stack member
number by using the show switch EXEC command.
A new, out-of-the-box device (one that has not joined a device stack or has not been manually assigned a
stack member number) ships with a default stack member number of 1. When it joins a device stack, its default
stack member number changes to the lowest available member number in the stack.
Stack members in the same stack cannot have the same stack member number. Every stack member, including
a standalone device, retains its member number until you manually change the number or unless the number
is already being used by another member in the stack.
• If you manually change the stack member number by using the switch current-stack-member-number
renumbernew-stack-member-number command, the new number goes into effect after that stack member
resets (or after you use the reload slot stack-member-number privileged EXEC command) and only if
that number is not already assigned to any other members in the stack. Another way to change the stack
member number is by changing the device_NUMBER environment variable.
If the number is being used by another member in the stack, the device selects the lowest available number
in the stack.
If you manually change the number of a stack member and no interface-level configuration is associated
with that new member number, that stack member resets to its default configuration.
You cannot use the switchcurrent-stack-member-numberrenumbernew-stack-member-numbercommand
on a provisioned device. If you do, the command is rejected.
• If you move a stack member to a different device stack, the stack member retains its number only if the
number is not being used by another member in the stack. If it is being used, the device selects the lowest
available number in the stack.
• If you merge device stacks, the device that join the device stack of a new active device select the lowest
available numbers in the stack.
Managing Switch Stacks
4
Managing Switch Stacks
Stack Member Numbers

As described in the hardware installation guide, you can use the device port LEDs in Stack mode to visually
determine the stack member number of each stack member.
In the default mode Stack LED will blink in green color only on the active switch. However, when we scroll
the Mode button to Stack option - Stack LED will glow green on all the stack members.
When mode button is scrolled to Stack option, the switch number of each stack member will be displayed as
LEDs on the first five ports of that switch. The switch number is displayed in binary format for all stack
members. On the switch, the amber LED indicates value 0 and green LED indicates value 1.
Example for switch number 5 (Binary - 00101):
First five LEDs glow as follows on stack member with switch number 5.
• Port-1 : Amber
• Port-2 : Amber
• Port-3 : Green
• Port-4 : Amber
• Port-5 : Green
Similarly, the first five LEDs glow amber or green, depending on the switch number on all stack members.
• If you connect a Horizontal stack port to a normal network port on other end, stack port
transmission/reception will be disabled within 30 seconds if no SDP packets are received from the other
end.
• Stack port will not go down but only transmission/reception will be disabled. The log message shown
below will be displayed on the console. Once the peer end network port is converted to stack port,
transmission/reception on this stack port will be enabled.
%STACKMGR-4-HSTACK_LINK_CONFIG: Verify peer stack port setting for hstack
StackPort-1 switch 5 (hostname-switchnumber)
Note
Stack Member Priority Values
A higher priority value for a stack member increases the probability of it being elected active switch and
retaining its stack member number. The priority value can be 1 to 15. The default priority value is 1. You can
display the stack member priority value by using the show switch EXEC command.
We recommend assigning the highest priority value to the device that you prefer to be the active device. This
ensures that the device is reelected as the active device if a reelection occurs.
Note
To change the priority value for a stack member, use the switch stack-member-number priority new
priority-value command. For more information, see the “Setting the Stack Member Priority Value” section.
Managing Switch Stacks
5
Managing Switch Stacks
Stack Member Priority Values

The new priority value takes effect immediately but does not affect the current active device. The new priority
value helps determine which stack member is elected as the new active device when the current active device
or the device stack resets.
Switch Stack Bridge ID and MAC Address
The MAC address of the active switch determines the stack MAC address.
When the stack initializes, the MAC address of the active switch determines the bridge ID that identifies the
stack in the network.
If the active switch changes, the MAC address of the new active switch determines the new bridge ID and
stack MAC address.
If the entire switch stack reloads, the switch stack uses the MAC address of the active switch.
Persistent MAC Address on the Switch Stack
You can also configure stack MAC persistency so that the stack MAC address never changes to the new active
switch MAC address.
Active and Standby Switch Election and Reelection
The active switch is elected or reelected based on one of these factors and in the order listed:
1. The switch that is currently the active switch.
2. The switch with the highest stack member priority value.
We recommend assigning the highest priority value to the switch that you prefer to be the active switch. This
ensures that the switch is reelected as active switch if a reelection occurs.
Note
3. The switch with the lowest MAC address.
Switch Stack Configuration Files
The configuration files record these settings:
• System-level (global) configuration settings such as IP, STP, VLAN, and SNMP settings that apply to
all stack members
• Stack member interface-specific configuration settings that are specific for each stack member
The interface-specific settings of the active switch are saved if the active switch is replaced without saving
the running configuration to the startup configuration.
Note
A new, out-of-box device joining a switch stack uses the system-level settings of that switch stack. If a device
is moved to a different switch stack before it is powered on, that device loses its saved configuration file and
Managing Switch Stacks
6
Managing Switch Stacks
Switch Stack Bridge ID and MAC Address

uses the system-level configuration of the new switch stack. If the device is powered on as a standalone device
before it joins the new switch stack, the stack will reload. When the stack reloads, the new device may become
the device, retain its configuration and overwrite the configuration files of the other stack members.
The interface-specific configuration of each stack member is associated with the stack member number. Stack
members retain their numbers unless they are manually changed or they are already used by another member
in the same switch stack. If the stack member number changes, the new number goes into effect after that
stack member resets.
• If an interface-specific configuration does not exist for that member number, the stack member uses its
default interface-specific configuration.
• If an interface-specific configuration exists for that member number, the stack member uses the
interface-specific configuration associated with that member number.
If you replace a failed member with an identical model, the replacement member automatically uses the same
interface-specific configuration as the failed device. You do not need to reconfigure the interface settings.
The replacement device (referred to as the provisioned device) must have the same stack member number as
the failed device.
You back up and restore the stack configuration in the same way as you would for a standalone device
configuration.
Offline Configuration to Provision a Stack Member
You can use the offline configuration feature to provision (to supply a configuration to) a new switch before
it joins the switch stack. You can configure the stack member number, the switch type, and the interfaces
associated with a switch that is not currently part of the stack. The configuration that you create on the switch
stack is called the provisioned configuration. The switch that is added to the switch stack and that receives
this configuration is called the provisioned switch.
You manually create the provisioned configuration through the switch stack-member-number provision type
global configuration command. You must change the stack-member-number on the provisioned switch before
you add it to the stack, and it must match the stack member number that you created for the new switch on
the switch stack. The switch type in the provisioned configuration must match the switch type of the newly
added switch. The provisioned configuration is automatically created when a switch is added to a switch stack
and when no provisioned configuration exists.
When you configure the interfaces associated with a provisioned switch, the switch stack accepts the
configuration, and the information appears in the running configuration. However, as the switch is not active,
any configuration on the interface is not operational and the interface associated with the provisioned switch
does not appear in the display of the specific feature. For example, VLAN configuration information associated
with a provisioned switch does not appear in the show vlan user EXEC command output on the switch stack.
The switch stack retains the provisioned configuration in the running configuration whether or not the
provisioned switch is part of the stack. You can save the provisioned configuration to the startup configuration
file by entering the copy running-configstartup-configprivileged EXEC command. The startup configuration
file ensures that the switch stack can reload and can use the saved information whether or not the provisioned
switch is part of the switch stack.
Managing Switch Stacks
7
Managing Switch Stacks
Offline Configuration to Provision a Stack Member

Effects of Adding a Provisioned Switch to a Switch Stack
When you add a provisioned Device to the switch stack, the stack applies either the provisioned configuration
or the default configuration. This table lists the events that occur when the switch stack compares the provisioned
configuration with the provisioned switch.
Table 2: Results of Comparing the Provisioned Configuration with the Provisioned Switch
ResultScenario
The switch stack applies the
provisioned configuration to the
provisioned switch and adds it to the
stack.
1. If the stack member number of the
provisioned switch matches the
stack member number in the
provisioned configuration on the
stack, and
2. If the Device type of the
provisioned switch matches the
Device type in the provisioned
configuration on the stack.
The stack member numbers
and the Device types match.
The switch stack applies the default
configuration to the provisioned switch
and adds it to the stack.
The provisioned configuration is
changed to reflect the new information.
1. If the stack member number of the
provisioned switch matches the
stack member number in the
provisioned configuration on the
stack, but
2. The Device type of the
provisioned switch does not match
the Device type in the provisioned
configuration on the stack.
The stack member numbers
match but the Device types
do not match.
The switch stack applies the default
configuration to the provisioned switch
and adds it to the stack.
The provisioned configuration is
changed to reflect the new information.
The stack member number
is not found in the
provisioned configuration.
The switch stack applies the default
configuration to the provisioned switch
and adds it to the stack.
The stack member number
of the provisioned switch is
not found in the provisioned
configuration.
If you add a provisioned switch that is a different type than specified in the provisioned configuration to a
powered-down switch stack and then apply power, the switch stack rejects the (now incorrect) switch
stack-member-number provision type global configuration command in the startup configuration file. However,
during stack initialization, the nondefault interface configuration information in the startup configuration file
for the provisioned interfaces (potentially of the wrong type) is executed. Depending on the differences between
the actual Device type and the previously provisioned switch type, some commands are rejected, and some
commands are accepted.
Managing Switch Stacks
8
Managing Switch Stacks
Effects of Adding a Provisioned Switch to a Switch Stack

If the switch stack does not contain a provisioned configuration for a new Device, the Device joins the stack
with the default interface configuration. The switch stack then adds to its running configuration with a switch
stack-member-number provision type global configuration command that matches the new Device. For
configuration information, see the Provisioning a New Member for a Switch Stack section.
Note
Effects of Replacing a Provisioned Switch in a Switch Stack
When a provisioned switch in a switch stack fails, it is removed from the stack, and is replaced with another
Device, the stack applies either the provisioned configuration or the default configuration to it. The events
that occur when the switch stack compares the provisioned configuration with the provisioned switch are the
same as those when you add a provisioned switch to a stack.
Effects of Removing a Provisioned Switch from a Switch Stack
If you remove a provisioned switch from the switch stack, the configuration associated with the removed
stack member remains in the running configuration as provisioned information. To completely remove the
configuration, use the no switch stack-member-number provision global configuration command.
Stack Protocol Version
Each software image includes a stack protocol version. The stack protocol version has a major version number
and a minor version number (for example 1.4, where 1 is the major version number and 4 is the minor version
number). Both version numbers determine the level of compatibility among the stack members.
The switches with the same Cisco IOS software version have the same stack protocol version. Such switches
are fully compatible, and all features function properly across the switch stack. A device with the same Cisco
IOS software version as the active switch can immediately join the switch stack.
If an incompatibility exists, the fully functional stack members generate a system message that describes the
cause of the incompatibility on the specific stack members. The active switch sends the message to all stack
members.
For more information, see the Major Version Number Incompatibility Among Switches procedure and the
Minor Version Number Incompatibility Among Switches procedure.
Major Stack Protocol Version Number Incompatibility Among Stack-Capable Switches
Device with different major Cisco IOS software versions usually have different stack protocol versions. Device
with different major version numbers are incompatible and cannot exist in the same switch stack.
Minor Stack Protocol Version Number Incompatibility Among Stack-Capable Switches
Auto-Upgrade
The purpose of the auto-upgrade feature is to allow a switch to be upgraded to a compatible software image,
so that the switch can join the switch stack.
When a new switch attempts to join a switch stack, each stack member performs compatibility checks with
itself and the new switch. Each stack member sends the results of the compatibility checks to the active stack,
Managing Switch Stacks
9
Managing Switch Stacks
Effects of Replacing a Provisioned Switch in a Switch Stack

which uses the results to determine whether the switch can join the switch stack. If the software on the new
switch is incompatible with the switch stack, the new switch enters version-mismatch (VM) mode.
If the auto-upgrade feature is enabled on the existing switch stack, the active stack automatically upgrades
the new switch with the same software image running on a compatible stack member. Auto-upgrade starts a
few minutes after the mismatched software is detected before starting.
Auto-upgrade includes an auto-copy process and an auto-extract process.
• Auto-copy automatically copies the software image running on any stack member to the new switch to
automatically upgrade it. Auto-copy occurs if auto-upgrade is enabled, if there is enough flash memory
in the new switch, and if the software image running on the switch stack is suitable for the new switch.
A switch in VM mode might not run all released software. For example, new
switch hardware is not recognized in earlier versions of software.
Note
When the auto-upgrade process is complete, the new switch reloads and joins the stack as a fully functioning
member. If you have both stack cables connected during the reload, network downtime does not occur because
the switch stack operates on two rings.
Switch Stack Management Connectivity
You manage the switch stack and the stack member interfaces through the active switch. You can use the
CLI, SNMP, and supported network management applications such as CiscoWorks. You cannot manage stack
members on an individual device basis.
Connectivity to Specific Stack Members
If you want to configure a specific stack member port, you must include the stack member number in the CLI
command interface notation.
Connectivity to the Switch Stack Through an IP Address
The switch stack is managed through a single IP address. The IP address is a system-level setting and is not
specific to the active stack or to any other stack member. You can still manage the stack through the same IP
address even if you remove the active stack or any other stack member from the stack, provided there is IP
connectivity.
Stack members retain their IP addresses when you remove them from a switch stack. To avoid a conflict by
having two devices with the same IP address in your network, change the IP addresses of any active stack
that you remove from the switch stack.
Note
For related information about switch stack configurations, see the Switch Stack Configuration Files section.
Connectivity to the Switch Stack Through Console Ports
You can connect to the active switch by connecting a terminal or a PC to the active switch through the console
port of one or more stack members.
Managing Switch Stacks
10
Managing Switch Stacks
Switch Stack Management Connectivity

Be careful when using multiple CLI sessions to the active switch. Commands that you enter in one session
are not displayed in the other sessions. Therefore, it is possible that you might not be able to identify the
session from which you entered a command.
We recommend using only one CLI session when managing the switch stack.
How to Configure a Switch Stack
Configuring a Network Port as Stack Port
You can configure both 10G network ports and multigig ports as stack ports or configure one port as stack
port and retain another port as network port.
SUMMARY STEPS
1. enable
2. configure terminal
3. switch switch-number hstack-port stack-port
4. end
5. show switch horizontal-stack-ports
6. copy running-config startup-config
7. reload
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode.enable
Step 1
Example: • Enter your password if prompted.
Device> enable
Enters global configuration mode.configure terminal
Example:
Step 2
Device# configure terminal
Configures the network port into a stack port .switch switch-number hstack-port stack-port
Example:
Step 3
After configuration, restart the switch for
network port to become a stack port.
Note
Device(config)# switch 1 hstack-port 1
TenGigabitEthernet 1/0/1
Returns to privileged EXEC mode.end
Example:
Step 4
Managing Switch Stacks
11
Managing Switch Stacks
How to Configure a Switch Stack

PurposeCommand or Action
Device(config)# end
Verifies the operation status of network ports and stack
ports.
show switch horizontal-stack-ports
Example:
Step 5
Device# show switch hstack-ports
(Optional) Saves your entries in the configuration file.copy running-config startup-config
Example:
Step 6
Device# copy running-config startup-config
Reloads the configuration.reload
Example:
Step 7
Device# reload
What to do next
To convert a stack port into a network port, run the noswitch switch-number hstack-port stack-port command:
Device(config)# no switch 1 hstack-port 1 TenGigabitEthernet 1/0/1
Device# copy running-config startup-config
Device# reload
After configuration, restart the switch to convert the stack port into a network port.
Note
Stack port to network port conversion and vice versa cli is not nvgened. On write erase reload, the switch in
stack mode will not be converted to standalone, and manual conversion of stack port to network port is required.
Note
Enabling the Persistent MAC Address Feature
When you enter the command to configure this feature, a warning message appears with the consequences of
your configuration. You should use this feature cautiously. Using the old active switch MAC address elsewhere
in the same domain could result in lost traffic.
Note
Follow these steps to enable persistent MAC address:
Managing Switch Stacks
12
Managing Switch Stacks
Enabling the Persistent MAC Address Feature

SUMMARY STEPS
1. enable
2. configure terminal
3. stack-mac persistent timer [0|time-value]
4. end
5. copy running-config startup-config
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode.enable
Step 1
Example: • Enter your password if prompted.
Device> enable
Enters global configuration mode.configure terminal
Example:
Step 2
Device# configure terminal
Enables a time delay after a stack-active switch change
before the stack MAC address changes to that of the new
stack-mac persistent timer [0|time-value]
Example:
Step 3
ac. If the previous active switch rejoins the stack during
Device(config)# stack-mac persistent timer 7 this period, the stack uses that MAC address as the stack
MAC address.
You can configure the time period as 0 to 60 minutes.
• Enter the command with no value to set the default
delay of approximately 4 minutes. We recommend
that you always enter a value.
If the command is entered without a value, the time
delay appears in the running-config file with an explicit
timer value of 4 minutes.
• Enter 0to continue using the MAC address of the
current active switch indefinitely.
The stack MAC address of the previous active switch
is used until you enter the no stack-mac persistent
timercommand, which immediately changes the stack
MAC address to that of the current active switch.
• Enter a time-value from 1 to 60 minutes to configure
the time period before the stack MAC address changes
to the new active switch.
The stack MAC address of the previous active switch
is used until the configured time period expires or until
Managing Switch Stacks
13
Managing Switch Stacks
Enabling the Persistent MAC Address Feature

PurposeCommand or Action
you enter the no stack-mac persistent timer
command.
If you enter the no stack-mac persistent timer
command after a new active switch takes over,
before the time expires, the switch stack moves
to the current active switch MAC address.
Note
Returns to privileged EXEC mode.end
Example:
Step 4
Device(config)# end
(Optional) Saves your entries in the configuration file.copy running-config startup-config
Example:
Step 5
Device# copy running-config startup-config
What to do next
Use the no stack-mac persistent timer global configuration command to disable the persistent MAC address
feature.
Assigning a Stack Member Number
This optional task is available only from the active stack.
Follow these steps to assign a member number to a stack member:
SUMMARY STEPS
1. enable
2. configure terminal
3. switch current-stack-member-number renumber new-stack-member-number
4. end
5. reload slot stack-member-number
6. show switch
7. copy running-config startup-config
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode.enable
Step 1
Example: • Enter your password if prompted.
Managing Switch Stacks
14
Managing Switch Stacks
Assigning a Stack Member Number

PurposeCommand or Action
Device> enable
Enters global configuration mode.configure terminal
Example:
Step 2
Device# configure terminal
Specifies the current stack member number and the new
stack member number for the stack member. The range is
1 to 8.
switch current-stack-member-number renumber
new-stack-member-number
Example:
Step 3
You can display the current stack member number by using
the show switch user EXEC command.
Device(config)# switch 3 renumber 4
Returns to privileged EXEC mode.end
Example:
Step 4
Device(config)# end
Resets the stack member.reload slot stack-member-number
Example:
Step 5
Device# reload slot 4
Verify the stack member number.show switch
Example:
Step 6
showDevice
(Optional) Saves your entries in the configuration file.copy running-config startup-config
Example:
Step 7
Device# copy running-config startup-config
Setting the Stack Member Priority Value
This optional task is available only from the active stack.
Follow these steps to assign a priority value to a stack member:
SUMMARY STEPS
1. enable
2. switch stack-member-number priority new-priority-number
3. show switch stack-member-number
Managing Switch Stacks
15
Managing Switch Stacks
Setting the Stack Member Priority Value

4. copy running-config startup-config
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode. Enter your password if
prompted.
enable
Example:
Step 1
Device enable
Specifies the stack member number and the new priority
for the stack member. The stack member number range is
1 to 8. The priority value range is 1 to 15.
switchstack-member-number priority new-priority-number
Example:
Device# switch 3 priority 2
Step 2
You can display the current priority value by using the show
switch user EXEC command.
The new priority value takes effect immediately but does
not affect the current active stack. The new priority value
helps determine which stack member is elected as the new
active stack when the current active stack or switch stack
resets.
Verify the stack member priority value.show switch stack-member-number
Example:
Step 3
Device# show switch
(Optional) Saves your entries in the configuration file.copy running-config startup-config
Example:
Step 4
Device# copy running-config startup-config
Provisioning a New Member for a Switch Stack
This optional task is available only from the active switch.
SUMMARY STEPS
1. show switch
2. configure terminal
3. switch stack-member-number provision type
4. end
5. copy running-config startup-config
Managing Switch Stacks
16
Managing Switch Stacks
Provisioning a New Member for a Switch Stack

DETAILED STEPS
PurposeCommand or Action
Displays summary information about the switch stack.show switch
Example:
Step 1
Device# show switch
Enters global configuration mode.configure terminal
Example:
Step 2
Device# configure terminal
Specifies the stack member number for the preconfigured
switch. By default, no switches are provisioned.
switch stack-member-number provision type
Example:
Step 3
For stack-member-number, the range is 1 to 8. Specify a
stack member number that is not already used in the switch
stack. See Step 1.
Device(config)# switch 3 provision WS-xxxx
For type, enter the model number of a supported switch that
is listed in the command-line help strings.
Returns to privileged EXEC mode.end
Example:
Step 4
Device(config)# end
(Optional) Saves your entries in the configuration file.copy running-config startup-config
Example:
Step 5
Device# copy running-config startup-config
Removing Provisioned Switch Information
Before you begin, you must remove the provisioned switch from the stack. This optional task is available
only from the active stack.
SUMMARY STEPS
1. configure terminal
2. no switch stack-member-number provision
3. end
4. copy running-config startup-config
Managing Switch Stacks
17
Managing Switch Stacks
Removing Provisioned Switch Information

DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure terminal
Example:
Step 1
Device# configure terminal
Removes the provisioning information for the specified
member.
no switch stack-member-number provision
Example:
Step 2
Device(config)# no switch 3 provision
Returns to privileged EXEC mode.end
Example:
Step 3
Device(config)# end
(Optional) Saves your entries in the configuration file.copy running-config startup-config
Example:
Step 4
Device# copy running-config startup-config
Example
If you are removing a provisioned switch in a stack with this configuration:
• The stack has four members
• Stack member 1 is the active stack
• Stack member 3 is a provisioned switch
and want to remove the provisioned information and to avoid receiving an error message, you can
remove power from stack member 3, disconnect the cables between the stack member 3 and switches
to which it is connected, reconnect the cables between the remaining stack members, and enter the
no switch stack-member-number provision global configuration command.
Troubleshooting the Switch Stack
Temporarily Disabling a Stack Port
If a stack port is flapping and causing instability in the stack ring, to disable the port, enter the switch
stack-member-number stack port port-number disable privileged EXEC command. To reenable the port,
enter the switch stack-member-number stack port port-number enable command.
Managing Switch Stacks
18
Managing Switch Stacks
Troubleshooting the Switch Stack

Be careful when using the switch stack-member-number stack port port-number disable command. When
you disable the stack port, the stack operates at half bandwidth.
Note
A stack is in the full-ring state when all members are connected through the stack ports and are in the ready
state.
The stack is in the partial-ring state when the following occurs:
• All members are connected through their stack ports but some are not in the ready state.
• Some members are not connected through the stack ports.
SUMMARY STEPS
1. switch stack-member-number stack port port-number disable
2. switch stack-member-number stack port port-number enable
DETAILED STEPS
PurposeCommand or Action
Disables the specified stack port.switch stack-member-number stack port port-number
disable
Step 1
Example:
Device# switch 2 stack port 1 disable
Reenables the stack port.switch stack-member-number stack port port-number
enable
Step 2
Example:
Device# switch 2 stack port 1 enable
When you disable a stack port and the stack is in the full-ring state, you can disable only one stack port. This
message appears:
Enabling/disabling a stack port may cause undesired stack changes. Continue?[confirm]
When you disable a stack port and the stack is in the partial-ring state, you cannot disable the port. This
message appears:
Disabling stack port not allowed with current stack configuration.
Reenabling a Stack Port While Another Member Starts
Stack Port 1 on Switch 1 is connected to Port 2 on Switch 4. If Port 1 is flapping, you can disable Port 1 with
the switch 1 stack port 1 disable privileged EXEC command. While Port 1 on Switch 1 is disabled and
Switch 1 is still powered on, follow these steps to reenable a stack port:
Managing Switch Stacks
19
Managing Switch Stacks
Reenabling a Stack Port While Another Member Starts

Step 1 Disconnect the stack cable between Port 1 on Switch 1 and Port 2 on Switch 4.
Step 2 Remove Switch 4 from the stack.
Step 3 Add a switch to replace Switch 4 and assign it switch-number 4.
Step 4 Reconnect the cable between Port 1 on Switch 1 and Port 2 on Switch 4 (the replacement switch).
Step 5 Reenable the link between the switches. Enter the switch 1 stack port 1 enable privileged EXEC command to enable
Port 1 on Switch 1.
Step 6 Power on Switch 4.
Powering on Switch 4 before enabling the Port 1 on Switch 1 might cause one of the switches to reload.
If Switch 4 is powered on first, you might need to enter the switch 1 stack port 1 enable and the switch 4
stack port 2 enable privileged EXEC commands to bring up the link.
Caution
Monitoring the Device Stack
Table 3: Commands for Displaying Stack Information
DescriptionCommand
Displays summary information about the stack, including the status of
provisioned switches and switches in version-mismatch mode.
show switch
Displays information about a specific member.show switch stack-member-number
Displays detailed information about the stack.show switch detail
Displays the stack neighbors.show switch neighbors
Displays port information for the stack.show switch stack-ports
Managing Switch Stacks
20
Managing Switch Stacks
Monitoring the Device Stack