Unable to stack 3850, platform mismatch

[Vainius Dangovas]

Hi,

When a few switches are stacked, during the boot one of them states an error:
Switch X has a platform mismatch with the stack. Only on changing to a compatible bandwidth mode will the switch join

When booted, show switch command output in master switch states that switch X is in waiting mode, that means that it doesn't participate in stack master election.

The reason is that switches are in different booting mode, for example the first one is in bundle and another is in installed.

When boot mode is changed to the same on both switches, stacking is successful.

Anyone knows why?

Vainius

[Jose Solano]

Hi,

Take a look at this:

Auto-Advise

The auto-advise feature is triggered when:

• The auto-upgrade feature is disabled.
• The new switch is in bundle mode and the stack is in installed mode. Auto-advise displays syslog messages about using the software auto-upgrade privileged EXEC command to change the new switch to installed mode.
• The stack is in bundle mode. Auto-advise displays syslog messages about booting the new switch in bundle mode so that it can join the stack.
• An auto-upgrade attempt fails because the new switch is running incompatible software. After the switch stack performs compatibility checks with the new switch, auto-advise displays syslog messages about whether the new switch can be auto-upgraded.

Auto-advise cannot be disabled. It does not give suggestions when the switch stack software and the software of the switch in version-mismatch (VM) mode do not contain the same license level.

• Examples of Auto-Advise Messages

Examples of Auto-Advise Messages

Auto-Upgrade Is Disabled and Incompatible Switch Attempting to Join: Example

This sample auto-advise output shows the system messages displayed when the auto-upgrade feature is disabled and an incompatible switch 1 tries to join the switch stack:

*Oct 18 08:36:19.379: %INSTALLER-6-AUTO_ADVISE_SW_INITIATED: 2 installer:  Auto advise initiated for switch 1
*Oct 18 08:36:19.380: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  Searching stack for software to upgrade switch 1
*Oct 18 08:36:19.382: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  Switch 1 with incompatible software has been
*Oct 18 08:36:19.382: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  added to the stack. The software running on
*Oct 18 08:36:19.382: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  all stack members was scanned and it has been
*Oct 18 08:36:19.382: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  determined that the 'software auto-upgrade'
*Oct 18 08:36:19.382: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  command can be used to install compatible
*Oct 18 08:36:19.382: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  software on switch 1.

Auto-Upgrade is Disabled and New Switch is in Bundle Mode: Example

This sample auto-advise output shows the system messages displayed when auto-upgrade is disabled and a switch running in bundle mode tries to join the stack that is running in installed mode:

*Oct 18 11:09:47.005: %INSTALLER-6-AUTO_ADVISE_SW_INITIATED: 2 installer:  Auto advise initiated for switch 1
*Oct 18 11:09:47.005: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  Switch 1 running bundled software has been added
*Oct 18 11:09:47.005: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  to the stack that is running installed software.
*Oct 18 11:09:47.005: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  The 'software auto-upgrade' command can be used to
*Oct 18 11:09:47.005: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  convert switch 1 to the installed running mode by
*Oct 18 11:09:47.005: %INSTALLER-6-AUTO_ADVISE_SW: 2 installer:  installing its running software.

SDM Template Mismatch in Switch Stacks

All stack members use the Switch Database Management (SDM) template configured on the active switch. When a new switch is added to a stack, the SDM configuration that is stored on theactive switch overrides the template configured on an individual switch.

You can use the show switch privileged EXEC command to see if any stack members are in SDM-mismatch mode.

Version-mismatch (VM) mode has priority over SDM-mismatch mode. If a VM-mode condition and an SDM-mismatch mode exist, the switch stack first attempts to resolve the VM-mode condition.

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

Hope this helps..!

[rwhisby56]

Thanks...   It's a good start.

[mchapendama]

How do I solve platform mismatch between ws-c3850-48p-s and ws-c3850-12xs-s

[paul driver]

Hello

Make sure they have to same ios and feature set applied prior to stacking them.

res
Paul

[Julio E. Moisa]

Hi

You must verify they have the same IOS and license type. 

[mchapendama]

I have upgraded the IOS on 48 port switch and now there is a V-Mismatch

[Leo Laohoo]

Ok, now post the complete output to the command "sh version".

[Leo Laohoo]

---

@mchapendama wrote:

How do I solve platform mismatch between ws-c3850-48p-s and ws-c3850-12xs-s

---

Find an IOS version and read the Release Notes.  One of the items listed in the Release Notes is a list of models that is supported in that particular version.  If the specific model is not in the list, then the switch won't join the stack.  

[dkruger]

no boot system switch all flash:cat3k_caa-universalk9.16.03.07.SPA.bin ****YOUR .bin FILE *******
boot system switch all flash:packages.conf
Reload