Stacking in 3x50

Contents

Stacking Architecture Review

High Availability

Stack Modifications

Mismatch Cases
Stacking in 3x50
Stacking Architecture Review
Stacking in 3x50
High Availability
1. The switch that is currently the active
switch.
2. The switch with the highest stack member
priority value.
3. The switch with the shortest start-up time.
4. The switch that has the configuration file.
5. The switch with the lowest MAC address.
Stacking in 3x50
Stack Modifications
Provisioning Members

Provisioning a New Member for a Switch Stack

switch stack-member-number provision type
Example:
Device(config)# switch 3 provision WS-xxxx

Removing Provisioned Switch Information

Before you begin, you must remove the provisioned switch from the stack.

no switch stack-member-number provision

Example:
Device(config)# no switch 3 provision
Stacking in 3x50
Mismatch Cases
Scenario 1 - Version Mismatch

We had 4 switches in a stack running version 16.3.6 and the 4th member
failed and it was RMAd. We replaced and powered on the switch, but the RMAd
switch is running version 16.6.4.
Scenario 1 - Version Mismatch

show switch detail

Switch/Stack Mac Address : 00bf.77c2.df80 - Local Mac Address
Mac persistency wait time: Indefinite
H/W Current
Switch# Role Mac Address Priority Version State
------------------------------------------------------------
*1 Active 00bf.77c2.df80 1 V08 Ready
2 Standby 00bf.7750.dc80 1 V08 Ready
3 Member 00c1.b137.6b80 1 V08 Ready
4 Member 00bf.77c2.d200 1 V-Mismatch
Scenario 1 - Version Mismatch

Upgrading an Incompatible Switch in the Switch Stack

Before you begin
Ensure the switches are install booted.
Ensure that the stack is connected in full ring mode.

Step 1
# software auto-upgrade
Upgrades incompatible switches in the switch stack, or changes switches in bundle mode to installed
mode.

Step 2
# copy running-config startup-config
Scenario 2 - License Mismatch

We had 4 switches in a stack running version 16.3.6 and the 4th member
failed and it was RMAd. We replaced and powered on the switch, but the RMAd
switch is running a different license level.
Scenario 2 - License Mismatch

show switch detail

Switch/Stack Mac Address : 00bf.77c2.df80 - Local Mac Address
Mac persistency wait time: Indefinite
H/W Current
Switch# Role Mac Address Priority Version State
------------------------------------------------------------
*1 Active 00bf.77c2.df80 1 V08 Ready
2 Standby 00bf.7750.dc80 1 V08 Ready
3 Member 00c1.b137.6b80 1 V08 Ready
4 Member 00bf.77c2.d200 1 Lic-Mismatch
Scenario 2 - License Mismatch

How to Solve this:

license right-to-use activate {ipbase |ipservices | lanbase} {all | evaluation all } [slot slot-number] [
acceptEULA]

Example:
Switch# license right-to-use activate ipservices all acceptEULA
Switch# reload slot 4
Proceed with reload? [confirm] y

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/3se/system_
management/configuration_guide/b_sm_3se_3850_cg/b_sm_3se_3850_cg_chapter_0100.html
Scenario 3 - OS-Mismatch

We had 4 switches in a stack running version 16.3.6 and the 4th member
failed and it was RMAd. We replaced and powered on the switch, but the RMAd
switch is running version 15.2.2E8.
Scenario 3 - OS-Mismatch

As the 4th member is booting up we are seeing the following logs:

*Sep 16 20:26:40.866: %STACKMGR-1-STACK_LINK_CHANGE:Switch 1 R0/0: stack_mgr: Stack port 2 on switch 1
is up
*Sep 16 20:26:49.383: %STACKMGR-1-STACK_LINK_CHANGE:Switch 3 R0/0: stack_mgr: Stack port 1 on switch 3
is up
*Sep 16 20:26:59.128: %SIF_MGR-1-FAULTY_STACK_CABLE:Switch 1 R0/0: sif_mgr: High hardware interrupt seen
on switch 1 on stack port 1
*Sep 16 20:27:03.628: %AUTO_UPGRADE-5-AUTO_UPGRADE_START_CHECK:Switch 1 R0/0:
auto_upgrade_client.sh: Auto upgrade start checking for incompatible switches.
*Sep 16 20:29:11.829: %AUTO_UPGRADE-3-AUTO_ADVISE_SW_MODE_UNKNOWN:Switch 1 R0/0:
auto_upgrade_client.sh: Switch 4 has been added to the stack. Failed to initiate auto advise for switch 4 because
switch 4 is not running installed or bundled software
Scenario 3 - OS-Mismatch

show switch detail

Switch/Stack Mac Address : 00bf.77c2.df80 - Local Mac Address
Mac persistency wait time: Indefinite
H/W Current
Switch# Role Mac Address Priority Version State
------------------------------------------------------------
*1 Active 00bf.77c2.df80 1 V08 Ready
2 Standby 00bf.7750.dc80 1 V08 Ready
3 Member 00c1.b137.6b80 10 V08 Ready
4 Member 00bf.77c2.d200 0 OS-Mismatch
Scenario 3 - OS-Mismatch

After almost 3 minutes the new switch reloads.

*Sep 16 20:31:45.875: %STACKMGR-1-STACK_LINK_CHANGE:Switch 1 R0/0: stack_mgr: Stack port 2 on switch 1

is down
*Sep 16 20:31:50.950: %STACKMGR-1-STACK_LINK_CHANGE:Switch 3 R0/0: stack_mgr: Stack port 1 on switch 3
is down
*Sep 16 20:31:45.946: %HMANRP-5-CHASSIS_DOWN_EVENT: Chassis 4 gone DOWN!

<Sun Sep 16 20:31:50 2018> Message from sysmgr: Reason Code:[4] Reset Reason:Reset/Reload requested by
[stack-manager]. [SESA:no communication timeout]
Scenario 3 - OS-Mismatch

What happens if autoupgrade is enabled?

show run | include auto-upgrade
software auto-upgrade enable
*Sep 16 21:13:26.048: %HMANRP-5-CHASSIS_DOWN_EVENT: Chassis 4 gone DOWN!
Chassis 1 reloading, reason - SESA: master requested reboot
*Sep 16 21:13:31.686: %STACKMGR-1-RELOAD:Switch 1 R0/0: stack_mgr: Reloading due to reason SESA: master requested reboot
Sep 16 21:13:39.971 R0/0: %PMAN-5-EXITACTION: Process manager is exiting: reload fp action requested
Sep 16 21:13:49.041 R0/0: %PMAN-5-EXITACTION: Process manager is exiting: rp processes exit with reload switch code

The whole stack goes down.