• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Adding a 3750X to an existing 3750E stack?

RadiclDreamer

RadiclDreamer

Diamond Member
I have an existing stack of 3750E/G switches. The current setup is as follows

1- 3750E
2 -3750E
3 -3750G
4-3750X

They are stacked together in a cascading fashion where switch 1 goes to 2 and 2 to 3 etc.

I am running 12.2(53)SE2 Code on the existing stack while the newly added is running 12.2(55)SE3

The issue I am having is the new 3750X never joins the stack, I see in the boot sequence it says it is doing the stack master election but then it always ends up being a standalone switch and then it will get fully booted and say "Reloading because of stack merge or communication failure"

Does this mean there is a cabling issue or am i mising something here? I thought the switch stack would auto downgrade the 3750X and join it like a 3750E would.
 
Last edited:
There is more to it, Stackwise (Plus) is the exact same on the 3750E and 3750X switches. Stackwise (non-Plus) is the original stack protocol available on 3750 and 3750G switches. If Stackwise Plus and Stackwise members are joined together in one stack, the ring looses some of the Plus functionality. However, you may or may not need thos Plus features. See here for the product sheet:

http://www.cisco.com/en/US/prod/col.../ps5023/prod_white_paper09186a00801b096a.html
 
Looks like I had to manually downgrade the code on the X series in order for it to work properly. Any idea why it wouldnt auto load the correct code?
 
Probably because of the slight hardware difference and no other reference 3750X in the stack.
 
RadiclDreamer said:
Looks like I had to manually downgrade the code on the X series in order for it to work properly. Any idea why it wouldnt auto load the correct code?
Click to expand...

I've seen that happen on different code trains where it won't downgrade code and you have to manually do it. Upgrading normally works just fine, but putting a switch in the stack with newer can be iffy depending on version.
 
spidey07 said:
I've seen that happen on different code trains where it won't downgrade code and you have to manually do it. Upgrading normally works just fine, but putting a switch in the stack with newer can be iffy depending on version.
Click to expand...

same here. Downgrades sometimes have to be manual in a stack.
 
AFAIK the reason the old code can't downgrade newer code is because the older code simply can't talk to it to know it should be downgraded. Along the same code train, they know what to build in...when it's a different pathway, all bets are off.
 
According to Cisco TAC they both are capable of running the same image, they are the same train. He wasn't sure why it didnt downgrade and I didnt want to waste my time trying to escalate. I'll read into it and see if i can find out why later when i have some time to spare
 
12.2(53)SE2 should work just fine. I've just recently install a bunch of 3750X's to an existing stack of the old school 3750 🙂. The main thing to pay attn to is making sure the software revision are the same and license.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top