- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Switchport STP state changes continuously, what it means?
Hi,
Uplink switchport in our MS120-48LP (SW2) change continuously status from designated→root and root→designated.
we lost connectivity with SW2 for almost one day and suddenly it came up during last night and after two hours it stopped with the STP status changing.
.
This switch (SW2) is connected with fiber to SW1 and SW1 is the RSTP root. When we had lost connectivity with the switch we got high CRC error on the uplink port in SW2. SW3 is connected at the same way to SW1 and it works perfectly.
What cause the continuously STP status changing in uplink switchport? Is it related to Fiber & SFP or there could be another reasons?
Thank you advance.
Here is the topology:
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey @Herixon. I would guess that it is related to that link. What I would think is happening is that the STP BPDU's are getting lost in transit on that link, so SW2 is actually transitioning to root because it stops hearing BPDU's from SW1.
When SW2's port is designated it thinks it is the root. When its port is root then it agrees that SW1 is the root.
If there's no other devices between those two switches then I would certainly look at the components of that link. SFP's, patch cables, the fibre run itself... If you have a tester that's a good place to start, Swapping the modules (one at a time to isolate one as the problem if it is) is another good option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey @Herixon. I would guess that it is related to that link. What I would think is happening is that the STP BPDU's are getting lost in transit on that link, so SW2 is actually transitioning to root because it stops hearing BPDU's from SW1.
When SW2's port is designated it thinks it is the root. When its port is root then it agrees that SW1 is the root.
If there's no other devices between those two switches then I would certainly look at the components of that link. SFP's, patch cables, the fibre run itself... If you have a tester that's a good place to start, Swapping the modules (one at a time to isolate one as the problem if it is) is another good option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This was exactly our problem. We changed the SFP and problem solved.
Thank you 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have this same issue. It started yesterday evening. No one is on site and there has been no connection changes made to the trunk port. Here's the messages I received from the log:
Client Event type Details
Aug 3 07:25:40 | Port STP change | Port 1 disabled→designated | |
Aug 3 07:25:40 | Port status change | port: 1, old: down, new: 1Gfdx | |
Aug 3 07:22:46 | Port STP change | Port 1 designated→disabled | |
Aug 3 07:22:46 | Port status change | port: 1, old: 1Gfdx, new: down | |
Aug 3 07:22:16 | Port STP change | Port 1 disabled→designated | |
Aug 3 07:22:16 | Port status change | port: 1, old: down, new: 1Gfdx | |
Aug 3 07:21:12 | Port STP change | Port 1 designated→disabled | |
Aug 3 07:21:12 | Port status change | port: 1, old: 1Gfdx, new: down | |
Aug 3 07:20:45 | Port STP change | Port 1 disabled→designated | |
Aug 3 07:20:45 | Port status change | port: 1, old: down, new: 1Gfdx | |
Aug 3 07:20:40 | Port STP change | Port 1 designated→disabled | |
Aug 3 07:20:40 | Port status change | port: 1, old: 1Gfdx, new: down | |
Aug 3 07:20:39 | Port STP change | Port 1 disabled→designated | |
Aug 3 07:20:39 | Port status change | port: 1, old: down, new: 1Gfdx | |
Aug 3 07:20:34 | Port STP change | Port 1 designated→disabled | |
Aug 3 07:20:34 | Port status change | port: 1, old: 1Gfdx, new: down | |
Aug 3 07:20:33 | Port STP change | Port 1 disabled→designated | |
Aug 3 07:20:33 | Port status change | port: 1, old: down, new: 1Gfdx | |
Aug 3 07:19:50 | Port STP change | Port 1 designated→disabled | |
Aug 3 07:19:50 | Port status change | port: 1, old: 1Gfdx, new: down | |
Aug 3 07:19:47 | Port STP change | Port 1 disabled→designated | |
Aug 3 07:19:47 | Port status change | port: 1, old: down, new: 1Gfdx | |
Aug 3 07:19:04 | Port STP change | Port 1 designated→disabled | |
Aug 3 07:19:04 | Port status change | port: 1, old: 1Gfdx, new: down | |
Aug 3 07:18:58 | Port STP change | Port 1 disabled→designated | |
Aug 3 07:18:58 | Port status change | port: 1, old: down, new: 1Gfdx | |
Aug 3 07:18:53 | Port STP change | Port 1 designated→disabled | |
Aug 3 07:18:53 | Port status change | port: 1, old: 1Gfdx, new: down | |
Aug 3 07:18:42 | Port STP change | Port 1 disabled→designated | |
Aug 3 07:18:42 | Port status change | port: 1, old: down, new: 1Gfdx |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You may have some kind of funny loop as well. Have you made SW1 the root of the spanning tree network? If not - do that before trying anything else.
EDIT: Oops just spotted that you said it is already the root.
