Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Got a problem with integration between Ruckus and Cisco 9300 but after investigating the problem seems general and more related with the basic of STP behavior that I can't understand.First here the schematic of the simplified network in cause:Everyth...
Hi Paul, You're right there is no BPDU frame received on the root bridge coming from the blocked port on the Ruckus side. BPDU frames are going downward and the Ruckus receives BPDU frames on both ports (blocked and forwarding state). BUT the root br...
Hi Georg,Yes that is the way STP works. The root bridge gets all ports in forwarding state. This is the switch below the root bridge that is blocking one port to prevent loop. https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-pro...
I had drill down the problem and I confirm that the problem comes from the mac address table (CAM) on the root bridge that gets updated by two control data protocol: LLDP and FDP. FDP is an equivalent of CDP for discovering neighbors devices in a Ruc...
When we clear the mac address-table on the root bridge the problem is fix for few seconds.It's why I'm thinking the root bridge uses her mac address table to know wich forwarding port to use.
Hi Georg, Thanks for helping but maybe I don't explain correctly (sorry for my english!).Spanning-tree works as it should for 99,9% of the traffic. The problem concerns ONLY the management IP address of the Ruckus device and I need basic explanation ...
