5 Posts
0
1902
Spanning Tree Issue - Maybe
Hi there,
Trying to figure out a really odd issue. This particular network has been running fine for ages with no issues at all. All the switches are N3024's either in single, double or triple stacks. I have one switch in the network that has suddenly starting dropping off the network.
There are three links into the switch, one fiber and two Microwave to ethernet and when the switch drops off I found that cycling the links at the other end would bring the switch back up. Further diagnostics show that if I leave one of the Microwave link ports disabled at the other end the switch stays perfectly stable. Enable that link and almost immediately the switch drops off the network.
Nothing has changed with regards firmware (although they do need updating) but I can't see why all of a sudden this one switch has started playing up. I also swapped the switch out for another one just in case it was a hardware fault but I'm seeing exactly the same behavior on the switch I've put in which makes me think it's some sort of config issue.
Any thoughts?
DELL-Josh Cr
Moderator
Moderator
•
8.4K Posts
0
July 25th, 2019 09:00
It does seem like it is something with port 22, what is it connecting to?
DELL-Josh Cr
Moderator
Moderator
•
8.4K Posts
0
July 24th, 2019 09:00
Hi,
Are there any other errors in the logs? It does sound like it could be spanning-tree and then shutting down ports. Is this one is a stack and is it the master? You may also want to check cabling.
JasonCoretek
5 Posts
0
July 25th, 2019 01:00
Single switch in this case and it's been swapped out for an identical switch but still exhibits the same problem. Anything specific I should be looking for in the logs that would help? I can easily clear the logs and then replicate the issue by turning the third link back on.
JasonCoretek
5 Posts
0
July 25th, 2019 01:00
So I've just re-enabled the link (with a ping running to the switch) and within seconds it dropped off. Left it like this for a couple of minutes then disabled the link and within about 45 seconds it started responding again (Log info below)
JasonCoretek
5 Posts
0
July 29th, 2019 01:00