NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Stacked S3300 not communicating through regular port
Hello,
I have 2 stacked S3300 that have the default configuration except for the stack configuration, i'm using a 10G link port 49. Everything was working great.
I need to make some change and I tried to connect them on a regular port instead of the stack port with a single cable. (but leaving the stack configuration as is) Everything stopped working because the regular port got blocked by STP (Discarding status).
I have tried to connect 1 S3300 to another dummy switch, and it's working. I'd like to know if the fact that those switch have a stack configuration, it will trigger STP to block the link between them, even if there's not actual cable on the stack port.
Is that normal ?
2 Replies
Hi,
When the two switches are stacked and connected via the stacking link, then a loop will occur if you try to connect a second cable on the "normal" ports. It is like connecting two end of the same cable to the same switch. STP will shut that down.
However, if you break the stack apart (remove the stacking link) and then connect the switches via a normal Ethernet connection, well then STP should not shut that down. Question is whether you connected the Ethernet connection before you removed the stacking cable?
What sort of configuration caused you to want to break the stack? All configurations should normally be done on the running stack. Another thing you might not have taken into account is that when you break a stack, both units have the same IP. So, if you subsequently connect them via normal Ethernet, there will be IP conflicts, etc.
CheersI removed the stack cable prior to connect the ethernet cable.
I intend to use the stack again, but I've notice during the inital setup that when connecting switches stack cable, it will initiate the election but during a minute or two I'll lose the network. Since we have a high availability environment, I wanted to test the new link (which is a LANX) on regular ethernet before attempting a nightshift and re-stack.
You're right, I didn't thought about the same IP conflict, that would maybe explain why.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
