Over the years we've built a couple of Meraki sites but seem to have ended up with slightly different configs & conflicting advice re root & loop guard usage.
Previously had months of site stability until recent core switch MLAG additions appears to have kicked off a bunch of weirdness like 'Port running LACP and LACP has disabled this port' madness knocking out a bunch of links unexpecting. Firmware updating seems to have helped a lot, but I'm in need of a sanity check to clarify what Meraki's best practices for spanning tree.
Is this the recommended STP & UDLD config for a LACP trunk between a stacked MS425 core & MS225 access switches?
Inter-Meraki Switch trunk - AGGR/x (Core-side)
- Type = Trunk Native = 1
- Allowed = all (or as required)
- RSTP = Enabled
- STP Guard = Root Guard
- UDLD = Alert
Inter-Meraki Switch trunk - AGGR/x (Access-Stack-side)
- Type = Trunk Native = 1
- Allowed = all (or as required)
- RSTP = Enabled
- STP Guard = Loop Guard
- UDLD = Enforce
And whilst we're on the topic....
All end devices, computers, servers, users, etc
- Type = Access
- RSTP = Enabled
- STP Guard = BPDU Guard
- UDLD = Alert Only
Non-Meraki Wi-Fi Access Point with VLANs
- Type = Trunk
- STP Guard = Root Guard
- UDLD = Alert Only
Non-Meraki Switch with VLANs & any inbound STP not to be trusted
- Type = Trunk
- STP Guard = Root Guard
- UDLD = Alert Only
Unmanaged Switch
- Type = Access
- STP Guard = BPDU Guard
Non-Meraki Firewall cluster, LACP Trunk to each HA Node - no STP support since failing over results in MAC address jumping between ports
- Type = trunk
- RSTP = Disabled
- Native VLAN = 1
- Allowed VLAN = (selected ID's as required)
- UDLD = Alert Only
Trusted DAI not enabled globally, so that's not a factor.
Thanks in advance!
