Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Using the Auto-Upgrade feature on the cisco Catalyst 3850

Introduction

There are a number of scenarios when you would need to introduce a new switch into an existing stack of 3850 switches.  One particular example is when a new switch is purchased to expand the number of usable ports in the stack.  To successfully add a new switch to a stack, you will need to ensure that the same software version is running on the new switch.  Prior to IOS-XE release 3.3.1, the only way to ensure the versions matched was to stage the new switch prior to introducing it into the stack.

Prerequisites

The 3850, includes a feature called “Auto-Upgrade” which might be familiar if you are migrating from the 3750 series platform.  The goal of this feature is to ensure that any newly added switch will automatically be provisioned by the stack members with the running IOS-XE version.  One caveat to note however is that prior to 3.3.1, this feature did not work  (Tracked by defect CSCui69999 ), and so you must ensure that your existing stack is running at least 3.3.1 in INSTALL mode.

** Auto-upgrade is disabled by default.

** Auto-upgrade is not available in bundle mode.

To utilize the “Auto-Upgrade” feature, you simply need to add the command “software auto-upgrade enable” in the running configuration of the existing stack.  This will ensure that any newly added stack members will automatically be upgraded.

Configure

Once the switch is stacked and booted up, you will see a clear indication that there is a mismatch in versions and the new member will not fully join the stack.  If you watch the syslog as the switch is trying to join, you will notice the “auto advise” feature will alert you that the newly added switch is running a different software version and mode (INSTALL & BUNDLE explained here).  For this example, my new switch is running IOS-XE version 3.2.2 in BUNDLE mode.

%STACKMGR-1-STACK_LINK_CHANGE: STANDBY: 1 stack-mgr:  Stack port 2 on switch 1 is up  (3850-Stack-1)

%STACKMGR-1-STACK_LINK_CHANGE: 2 stack-mgr:  Stack port 1 on switch 2 is up

%STACKMGR-6-SWITCH_ADDED: 2 stack-mgr:  Switch 3 has been added to the stack.

%STACKMGR-6-SWITCH_ADDED: STANDBY:1 stack-mgr:  Switch 3 has been added to the stack.  (3850-Stack-1)

%INSTALLER-6-AUTO_ADVISE_SW_INITIATED: 2 installer:  Auto advise initiated for switch 3

%INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  Switch 3 running bundled software has been added

%INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  to the stack that is running installed software.

%INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  The 'software auto-upgrade' command can be used to

%INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  convert switch 3 to the installed running mode by

%INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  installing its running software.

Once the newly joined member is fully booted, you can see that a mismatch has been detected.

3850-Stack#show switch

Switch/Stack Mac Address : 0c27.24cf.ab80 - Local Mac Address

Mac persistency wait time: Indefinite

                                             H/W   Current

Switch#   Role    Mac Address     Priority Version  State

------------------------------------------------------------

*1       Active   0c27.24cf.ab80     14     B0      Ready             

2       Standby  f41f.c238.a800     13     B0      Ready             

3       Member   b4e9.b0d3.6600     12     0       V-Mismatch

Enable the auto-upgrade feature

In global configuration mode, type the command “software auto-upgrade enable.”  This will enable the feature for any new switches that join the stack.

3850-Stack(config)#software auto-upgrade enable

3850-Stack(config)#end

You will now have to reload the newly added switch only, a full stack reload is not necessary.  In my case, the newly added switch is “switch 3” so I simply type “reload slot 3.”  Remember that “slot” designates the switch in the stack (slot 1 = switch 1)

3850-Stack#reload slot 3

Proceed with reload? [confirm]

%STACKMGR-1-RELOAD_REQUEST: 1 stack-mgr:  Received reload request for switch 3, reason Reload Slot Command

%STACKMGR-1-STACK_LINK_CHANGE: 1 stack-mgr:  Stack port 2 on switch 1 is down

%STACKMGR-6-SWITCH_REMOVED: 1 stack-mgr:  Switch 3 has been removed from the stack.

%STACKMGR-1-STACK_LINK_CHANGE: STANDBY:2 stack-mgr:  Stack port 1 on switch 2 is down  (3850-Stack-2)

Starting SWITCH-DELETE sequence, switch 3

SWITCH-DELETE sequence complete, switch 3

%STACKMGR-6-SWITCH_REMOVED: STANDBY:2 stack-mgr:  Switch 3 has been removed from the stack.  (3850-Stack-2)

Starting SWITCH-DELETE sequence, switch 3 (3850-Stack-2)

SWITCH-DELETE sequence complete, switch 3 (3850-Stack-2)

Wait a few minutes while the switch reloads in the background

%STACKMGR-1-STACK_LINK_CHANGE: 1 stack-mgr:  Stack port 2 on switch 1 is up

3850-Stack#

%STACKMGR-1-STACK_LINK_CHANGE: STANDBY:2 stack-mgr:  Stack port 1 on switch 2 is up  (3850-Stack-2)

3850-Stack#

%STACKMGR-6-SWITCH_ADDED: 1 stack-mgr:  Switch 3 has been added to the stack.

%STACKMGR-6-SWITCH_ADDED: STANDBY:2 stack-mgr:  Switch 3 has been added to the stack.  (3850-Stack-2)

3850-Stack#

First we can see that it does the conversion from BUNDLE to INSTALL mode followed by a reload.

%INSTALLER-6-AUTO_UPGRADE_SW_INITIATED: 1 installer:  Auto upgrade initiated for switch 3

%INSTALLER-6-AUTO_UPGRADE_SW: 1 installer:  Converting switch 3 to installed mode by

%INSTALLER-6-AUTO_UPGRADE_SW: 1 installer:  installing its running software

%INSTALLER-6-AUTO_UPGRADE_SW: 1 installer:  Setting the boot var on switch 3

%INSTALLER-6-AUTO_UPGRADE_SW: 1 installer:  Finished installing the running software on switch 3

%INSTALLER-6-AUTO_UPGRADE_SW: 1 installer:  Reloading switch 3 to boot in installed mode

%STACKMGR-1-RELOAD_REQUEST: 1 stack-mgr:  Received reload request for switch 3, reason Auto upgrade

%STACKMGR-1-STACK_LINK_CHANGE: 1 stack-mgr:  Stack port 2 on switch 1 is down

%STACKMGR-6-SWITCH_REMOVED: 1 stack-mgr:  Switch 3 has been r

3850-Stack#emoved from the stack.

%STACKMGR-1-STACK_LINK_CHANGE: STANDBY:2 stack-mgr:  Stack port 1 on switch 2 is down  (3850-Stack-2)

Starting SWITCH-DELETE sequence, switch 3

SWITCH-DELETE sequence complete, switch 3

%STACKMGR-6-SWITCH_REMOVED: STANDBY:2 stack-mgr:  Switch 3 has been removed from the stack.  (3850-Stack-2)

3850-Stack#

Starting SWITCH-DELETE sequence, switch 3 (3850-Stack-2)

SWITCH-DELETE sequence complete, switch 3 (3850-Stack-2)

Once it reboots, the upgrade will then continue

3850-Stack#

%INSTALLER-6-AUTO_UPGRADE_SW_INITIATED: 1 installer:  Auto upgrade initiated for switch 3

%INSTALLER-6-AUTO_UPGRADE_SW: 1 installer:  Searching stack for software to upgrade switch 3

%INSTALLER-6-AUTO_UPGRADE_SW: 1 installer:  Found donor switch 1 to auto upgrade switch 3

%INSTALLER-6-AUTO_UPGRADE_SW: 1 installer:  Upgrading switch 3 with software from switch 1

%INSTALLER-6-AUTO_UPGRADE_SW: 1 installer:  Finished installing software on switch 3

%INSTALLER-6-AUTO_UPGRADE_SW: 1 installer:  Reloading switch 3 to complete the auto upgrade

%STACKMGR-1-RELOAD_REQUEST: 1 stack-mgr:  Received reload request for switch 3, reason Auto upgrade

%STACKMGR-1-STACK_LINK_CHANGE: 1 stack-mgr:  Stack port 2 on switch 1 is down

%STACKMGR-6-SWITCH_REMOVED: 1 stack-mgr:  Switch 3 has been removed from the stack.

%STACKMGR-1-STACK_LINK_CHANGE: STANDBY:2 stack-mgr:  Stack por

3850-Stack#t 1 on switch 2 is down  (3850-Stack-2)

Starting SWITCH-DELETE sequence, switch 3

SWITCH-DELETE sequence complete, switch 3

%STACKMGR-6-SWITCH_REMOVED: STANDBY:2 stack-mgr:  Switch 3 has been removed from the stack.  (3850-Stack-2)

Another reload is automatically performed.  Once the switch is booted back up, it will successfully join the stack with the correct IOS-XE version and software mode.

%STACKMGR-6-SWITCH_ADDED: 1 stack-mgr:  Switch 3 has been added to the stack.

%STACKMGR-6-SWITCH_ADDED: STANDBY:2 stack-mgr:  Switch 3 has been added to the stack.  (3850-Stack-2)

%STACKMGR-6-SWITCH_READY: STANDBY:2 stack-mgr:  Switch 3 is ready.  (3850-Stack-2)

%STACKMGR-6-SWITCH_READY: 1 stack-mgr:  Switch 3 is ready.

Starting SWITCH-ADD sequence, switch 3

%NGWC_USB_CONSOLE-6-CONFIG_ENABLE: Switch 3: Console media-type changed to default

Starting SWITCH-ADD sequence, switch 3 (3850-Stack-2)

SWITCH-ADD sequence complete, switch 3 (3850-Stack-2)

SWITCH-ADD sequence complete, switch 3

Verify

3850-Stack#show switch

Switch/Stack Mac Address : 0c27.24cf.ab80 - Local Mac Address

Mac persistency wait time: Indefinite

                                             H/W   Current

Switch#   Role    Mac Address     Priority Version  State

------------------------------------------------------------

*1       Active   0c27.24cf.ab80     14     B0      Ready             

2       Standby  f41f.c238.a800     13     B0      Ready             

3       Member   b4e9.b0d3.6600     12     B0      Ready

3850-Stack#show version

Switch Ports Model              SW Version        SW Image              Mode 

------ ----- -----              ----------        ----------            ---- 

*    1 56    WS-C3850-48P       03.03.01SE        cat3k_caa-universalk9 INSTALL

     2 56    WS-C3850-48P       03.03.01SE        cat3k_caa-universalk9 INSTALL

     3 56    WS-C3850-48P       03.03.01SE        cat3k_caa-universalk9 INSTALL

Reference:

http://www.cisco.com/en/US/docs/switches/lan/catalyst3850/software/release/3se/consolidated_guide/configuration_guide/b_consolidated_3850_3se_cg_chapter_01101101.html#con_1189959

Version history
Revision #:
1 of 1
Last update:
‎01-26-2014 04:26 PM
Updated by:
 
Labels (1)
Comments
New Member

What happens if the newly added switch has a newer version? will it then downgrade the new switch?

New Member

does it work with 3750

or 3750x?

New Member

I have the same question.  I use 3850's in a 911 Communications Center environment and I really need a solid answer to this from Cisco.  From the documentation, it looks as though any switch with whatever code that's incompatible with the stack gets upgraded or downgraded to what's on the stack and only the new switch will be rebooted....Is that true?  Can I see documentation?  I don't want to see random answers telling not to use auto-anything...that's not helpful.

It's a little disconcerting that there aren't any answers to the above question as it was posted 3 years ago.

-anne

New Member

Looks like it will do either.

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750/software/troubleshooting/switch_stacks.html

"If the stack master detects that the software on a new switch does not match, it upgrades (or downgrades) the new switch with the active image that is running on the switch stack by using the automatic upgrade (auto-upgrade) and the automatic advise (auto-advise) features."

New Member

Ok so why in the hell does Cisco not include the 3.3.0 issue on any of the 3650 documentation? I researched the auto upgrade feature before working in a customer switch into a new 3650 stack and it crashed the entire damn stack. It'd be nice if the documentation I rely on for uptime and seamless implementation actually included this incredibly important detail.  

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/software/release/3se/system_management/configuration_guide/b_sm_3se_3650_cg/b_sm_3se_3650_cg_chapter_010101.html