Bridge ID/Priority not updating! 1.4.9

[troy]

Need to ensure that this switch is the root bridge, but doesn't look like it wants to accept the Priority settings.

WS-12-250-AC with 1.4.9.




Verified via CLI:

Code: Select all

"STP_Enable": true,
 "STP_Version": "RSTP",
 "STP_Max_Age": "20",
 "STP_Hello_Time": "2",
 "STP_Forward_Delay": "15",
 "STP_Priority": "24576",
 "STP_LAG_Enable": true,
 

Thanks!

[bravecurve]

Same issue here

[jpaine619]

I appear to be having the same issue.. I change the priority, but the bridge ID does not change to reflect it.

[jpaine619]

Update: A reboot of the "old" root switch cleared the problem.. All down the chain the Switches updated themselves to reflect the new root switch. It would be nice to not have to reboot though.. Although for me this probably will never again be an issue.

[mike99]

I'm pretty sure I already reported this bug but can't remember if it's cosmetic or a true bug. Have you try to check if you can set a netonix as root switch whitout rebooting ?

[jpaine619]

I'm pretty sure I already reported this bug but can't remember if it's cosmetic or a true bug. Have you try to check if you can set a netonix as root switch whitout rebooting ?

Yeah.. I changed the priority (lowered it) on the new switch, at the new fiber feed, to be the root.. Logged in to the old switch, at the coax feed, changed the priority back to the old higher default... and it refused to change the bridge ID.

When I rebooted it, and it came back online, only then did it reflect the bridge ID with the higher priority. Within a few seconds the rest of the switches on the network recognized the new switch as root.

It's definitely not cosmetic. All switches in between those two showed the path to the old switch as ROOT.

Upon reboot of the old switch, the switches in between then recognized the new switch as root.