Wireless Mesh issues caused by spanning-tree loopguard
I have installed 3 APs in a wireless Mesh network (2 x Root APs and 1 x Mesh AP) at a client site. It seems that whenever my Mesh AP fails over to another parent Root AP, spanning-Tree's loopguard kicks in on the switches trunk connected to the Mesh AP for the native VLAN and CCTV VLAN (cameras are connected to the switch) . This causes a 3 minute network outage for the cameras connected every time.
Can loopgaurd even work on a Wireless Mesh setup? The Mesh Backhaul is essentially a bridge between the mesh connected switches, so I'm assuming when the switches receive BPDUs from different switches on the same trunk link, it will cause issues? I thought the Cisco Mesh had it's own inbuilt loop prevention mechanisms.
It turns out Loopguard should only be configured on Point-to-Point links. That is; when a single device is connected to the other end of a given port. Mesh being a shared medium should not have loopguard configured on any of its uplinks.
When a mesh connected switch stops receiving BPDUs (MAP fails over to another RAP for example) the switch-to-AP link is still 'UP' and thinks there is a unidirectional link failure.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...