RSTP in SLM2008 has a serious bug - wrong source bridge ID in root port BPDUs
after having examined all the BPDUs transferred between the various switches by means of tcpdump and wireshark, I think I found the bug here which is really serious: a non-root SLM2008 sends BPDU frames where it steals the root's bridge ID and claims it as its own! This means the SLM2008 sends the root's bridge ID in both the source and root ID fields which is not allowed.
Either it should not send back BPDUs to the root at all, or it must use its own ID in the source field and mention the root ID only in the root's ID field.
If someone from Cisco reads this here: this bug should be fixed by the next firmware release as it can render a whole network unusable if STP is activated on the SLM2008 and it is used together with other switches.
Thanks and best regards,
PS: The examination also answered one of my questions - the protocol used is RSTP, at least by type and BPDU length.
--- old message follows ---
Now I own three of the little SLM2008 which seem to be designed quite well and mostly behave as expected, but one annoying problem bites me: the spanning tree protocol behaves strange as soon as I connect switches from other manufacturers to it.
A larger D-Link switch with RSTP and fallback STP enabled causes all connected and STP-enabled (without portfast) SLM2008s to go into blocking mode at the HOST (!) ports, the D-Link in turn blocks all ports where an SLM2008 is attached.
As the SLM2008 has almost no options except for portfast and enabling/disabling STP, I tried to fiddle around with the D-Link, logically as well as by random trial-error attempts, but there is no chance at the moment. It is always the same and very unsatisfying.
Using a cheaper Netgear (in the range of the SLM2008) instead of the D-Link works fine, but also the D-Link works perfectly with the Netgear. Why does the SLM2008 not fit in here?
To me it's also quite confusing that the manual states "STP" as the feature's name, but the open source note talks about RSTP... which variant is really implemented in the SLM2008?
Hi. We have been looking at using either the RV260P or RV345P as basically a "network in a box" type of solution for some of our small customers. The hope is we can use these devices when the customer has 8 or fewer VoIP phones rather than deploying a sma...
At Cisco, we’re helping small businesses implement technology innovations so they can find success while navigating a complex and hard-to-predict business landscape. Through our Small Business Recovery Kit contest, we’re also giving entrepreneurs the...
How do I configure a Windows VPN to a Cisco RV260W? Firmware 1.0.00.17 purchased June 2020 Tried PPTP many different ways and all I can ever receive is:"The remote connection was denied because the user name and password combination you provide...
Small businesses are facing the realities of the new normal and wondering how to best monitor, protect, manage and grow. Cisco understands the unique needs of small businesses and is committed to help overcome their top IT challenges.