New "root port" showing on logs after problems occur

User avatar
wispwest
Member
 
Posts: 33
Joined: Tue Sep 30, 2014 6:08 pm
Has thanked: 7 times
Been thanked: 10 times

New "root port" showing on logs after problems occur

Thu Aug 08, 2019 1:08 pm

I had sent this PM to Sirhc back in July and looks like was never even read (is there any support for Netonix anymore, no WISP shows, etc.?) No new products, no SFP+ ports, I hope Netonix isn't being neglected now that it got all the fortune and fame, the soul is gone!

I've been seeing some issues recently at a couple sites where the whole switch just becomes unreachable (though still linked ethernet). One today needed rebooted, is there a way to setup watchdog to simply reboot the SWITCH instead only options to power cycle ports?
Also at one site it would randomly drop connectivity and when it came back, I could see the log before rebooting it, and the only thing I could see that might be a problem is the "root bridge port changed", does the root bridge port need to be the uplink? Or could it be an AP?
STP: MSTI0: New root on port 12, root path cost is 20000
STP: MSTI0: New root on port 12, root path cost is 20010
STP: MSTI0: New root on port 11, root path cost is 20000
STP: MSTI0: New root on port 9, root path cost is 20010

Return to General Discussion

Who is online

Users browsing this forum: MSN [Bot] and 8 guests