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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

3750--Mixing EMI and SMI in the Stack

Does anyone know if Cisco will support mixing EMI and SMI in a 3750 stack? I keep hearing mixed things--some say yes and some say no. Any help would be greatly appreciated. I don't really want to pay for EMI on switches that don't uplink to the cores.


Re: 3750--Mixing EMI and SMI in the Stack

If you have an emi as the stackmaster the other switches should upgrade themselves to that version .

Cisco Employee

Re: 3750--Mixing EMI and SMI in the Stack


This configuration is not recommended by Cisco, to run a mix stack of EMI and SMI switches. This configuration will work with SMI switches only running with limited featureset that they support.Advanced EMI features will not be supported by the SMI switches.

Glen: The stack master will not update the other stack memeber with the EMI software.

I think TAC will not support this.

-amit singh

Cisco Employee

Re: 3750--Mixing EMI and SMI in the Stack

Hi Friend,

Mixed stack with IP Base (formerly SMI) and IP Services (formerly EMI) or Advanced IP Services is supported.

Here is what we recommend:

* The IOS software version on all stack members, including the stack master, should be the same. This helps ensure full compatibility in the stack protocol version among the stack members. For example, all stack members should have either the EMI or SMI

* If your switch stack must have switches running SMI and EMI software,the switch running the EMI software should be the stack master. EMI features become unavailable to all stack members if the stack master is running the SMI software.

* At least two stack members should have the EMI software installed to ensure redundant support of the EMI features. The EMI has precedence over the SMI during stack master election, assuming that the priority value of the stack members are the same. If the EMI stack master fails,the other stack member running the EMI software becomes the stack master.

* When a switch running the EMI joins a switch stack running the SMI of the same version, the EMI switch does not automatically become the stack master. If you want the EMI switch to become the stack master, reset the current SMI stack master by using the reload slot stack-member-number privileged EXEC command. The EMI switch is elected the stack master, assuming its priority value is higher or the same as the other stack members.

However, there are some issues to consider when deploying such mixed stacks.

* If you have a stack of SMI switches, with a single EMI unit, the EMI unit will, by default, become the master switch. It will give EMI functionality to the entire stack. This is because Layer-3 functionality is centralized in nature, on the 3750. However, if the master switch were to fail, the entire stack would revert to the feature-set of the new master, who happens to be SMI. The user would lose all EMI-only functionality such as advanced IP routing protocols. This is the reason we include a recommendation that if users deploy a mixed stack, they should have at least two EMI units to provide protection against such failures.

* If the user does decide to use the unified upgrade feature to upgrade the stack, it will be a single upgrade. This means that the entire stack will get upgraded to the same image. The upgrade process will involve copying the same new image file to the flash of every switch in the stack. So, if the new image is an EMI image, all the EMI switches will get upgraded. The originally SMI switches will not get upgraded to EMI, in this scenario! They will give a "Version Mismatch" error and you will need to upgrade them separately, to an SMI image (or purchase an SMI-to-EMI upgrade license for those switches).



*Pls rate all helpfull post