• 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.

Need some expert advice on Cisco IOS releases...

L

loosbrew

Golden Member
Hello all,
Recently, the co that I work for purchased quite a few Cisco 2950 switched. along with a 3508 and a few 2950-24t's. What i have been tryng to do is get them all in the same cluster and configure them from the GUI after the initial setup. everything goes fine except for one major switch. for some reason we cant disable STP, and we can't make it join the cluster. I did notice that the IOS of the stubborn switch is a newer version the the commander. does this matter? i can get more specific version numbers tomorrow, but what my question is for right now is, Will this problem be apparent when different IOS's are in play?

tia
loosbrew
 
Yes, different IOS versions are and can be very different. You should be able to read the release notes on both specific versions.

Please do NOT disable STP. it is there to help you and if you disable it and somehow get a loop in your network you'll be in a world of hurt trying to find it. STP will detect and block the loop.
 
Yes unless you intricatley understand how STP works you should not touch it. Besides STP really doesn't take much cpu or bandwidth...unless you are dealing with mission crititical real time something don't change STP. It is there for a reason
 
i know what stp does, but i was instructed by my superior to disable it. what if we enable it again, will i have more problems?
 
You'll likely have fewer problems, most definitely in the long run. STP really just guards against someone doing something stupid. In addition, it lets you build more redundant networks, to guard against a switch or a link failure. STP is, most definitely, your friend.

When you built your switches, are you sure you don't have any loops built in the topology? If that was the case, Cisco might be looking out for you and not letting you take down your own network by disabling STP. I don't remember the details, but there's a "show spantree" set of commands that you might want to check out.

- G
 
From what I hear.. doing what you are told is an utmost priority.. explain what it might cause and go on about it.. if later it becomes a problem fix it and explain STP solved the problem and become a hero.. (for the day of course). Obviously your problem lies in the new cluster feature of these switches and I too would be interested in how this dohicky works since it is new to me also.

I recently got in 3 2950T-24s im playing with to make work for a new office and saw the Clustering a facinating peice of technology.
 


<< From what I hear.. doing what you are told is an utmost priority.. explain what it might cause and go on about it.. >>



True. However, you should document that. Even if it's just a simple email. 🙂



<< I recently got in 3 2950T-24s im playing with to make work for a new office and saw the Clustering a facinating peice of technology. >>



Eh. I find trunking much more interesing. Just mho though.
 
I don't have the gear for ISL yet.. but oooo I can't wait for that either.. near future near future 🙂

I too agree with the documentation part.. welcome to CYA land 🙂
 


<< I too agree with the documentation part.. welcome to CYA land >>


Heh, 11 years in the US Army. I "get" it. Oh, trust me, I get it. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top