The default priority for all Meraki switches is 32768. It is recommended that you set the priority of your desired root bridge to 4096 to ensure its election. The root bridge should be a switch in the center of the network, near high traffic sources (such as servers), to optimize traffic flow across the network. Using priority 0 is also acceptable for the root, but leaves no room for modification when replacing a core switch in production or modifying behavior temporarily. It is best practices to set a layered approach to the STP priorities in a network. For instance, if there is a clear Core <> Distribution <> Access Layer, priorities should be Core (4096), Distribution (16384), and Access (61440). At no point in a production network should you leave the any switch at its default configurations.  Reference: https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Configuring_Spanning_Tree_on_Meraki_Switches_(MS)#Set_Bridge_Priority ... View more

 If you have "modified" the native VLAN as many do, be sure it's also set that change accordingly under Switching > Switch Settings as pictured above where is shows VLAN configuration (Management VLAN) at the top of the page. ... View more

You will need to define (create/add) VLAN1 within your network for the MS130 to use the non-existent NATIVE 1 VLAN as you've told the switch to use.  The 3850 fails as well because it remains undefined (non-existent).  VLAN1 doesn't seem to exist anywhere in the network. Or you could make VLAN10 the native VLAN (untagged) - could be the easier solution.  Both the 3850 and MS130 ports that connect to one another need to be identical.  VLAN 1 (non-existent) - ???.???.??.0/?? (it doesn't exist) VLAN 5 (Voice) - 192.168.20.0/24 (DHCP from a Cisco 3945 ISR) VLAN 10 (Data) - 172.16.0.0/23 (DHCP from Windows Server 2016) ... View more

What is the VLAN1 subnet?  Have you defined or added a VLAN1 subnet? The reason VLAN1 fails on the MS130 is likely because it's not defined just showing what the default is as native VLAN 1.  It needs to be listed for it to work and be used.  I don't see what IP/subnet range VLAN 1 is. ... View more

What subnets are you using? Example VLAN 1 is 10.10.10.0/24 VLAN 5 is 172.16.5.0/24 VLAN10 is 172.16.10.0/24 When you set the static IP address of the MS130 switch it should also fall within the VLAN1 subnet. The screenshot you have above shows DHCP using VLAN 1 however it looks like you are manually setting it to VLAN10 on the Data VLAN. Do you have two or three subnets?  Is your 3850 Catalyst using Native VLAN1 subnet for a static IP address as well or using VLAN10 data subnet?   ... View more

Does the static IP address you are attempting to assign to the MS130 switch fall into the VLAN1 subnet or VLAN10 data subnet? ... View more

Native VLAN for your switch is VLAN1 Data VLAN should be something other than VLAN1 Voice VLAN should be something other than VLAN1 and the Data VLAN. Setting your static IP VLAN field should be 1 (separate subnet). ... View more

The static VLAN should reflect the NATIVE VLAN (1) to talk to the cloud - not for your data/voice VLANs. ... View more

And I would turn OFF PoE on the UPLINK as well. ... View more

Does turning OFF trusted DAI fix the issue or have you tested that idea/suggestion? ... View more

Is your static IP setup have the VLAN field set or is it empty? ... View more

What is the switch connected to?  Can you show screenshots of your uplink settings that might help us see how it's configured.  Your initial post doesn't have a lot of info/details for us to go off of without seeing how it's configured. ... View more

        First thing I would check is the TRUNK uplink.  If you have "modified" the native VLAN as many do, be sure it's also set that change accordingly under Switching > Switch Settings as pictured above where is shows VLAN configuration (Management VLAN) at the top of the page. ... View more

What Meraki devices are you working with?  MX and MRs only?  MS in the equation? ... View more

Correct and for full implementation of Adaptive Policy is referenced in the link shared. Adaptive Policy with Security Group Tags simplifies network segmentation and boosts security without sacrificing agility or flexibility. Additional Adaptive Policy Resources  Adaptive Policy Overview Adaptive Policy Configuration Guide Adaptive Policy MS Configuration Guide Adaptive Policy MR Configuration Guide Adaptive Policy Telemetry ... View more

This might help answer your question: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Adaptive_Policy_for_MX%2F%2FZ_Platforms ... View more

Are you assigning one RF profile across the entire network or assigning a separate RF profile to each AP that is or would be different RF profile for each AP?  I tend to create a separate RF profile for each AP that I manage in order to reduce the channel overlap - it's kind of a cumbersome task up front but alleviates problems long term.  Just a thought or idea if you aren't doing so already. https://documentation.meraki.com/MR/Radio_Settings/RF_Profiles ... View more

Pressing the Update Auto Channels button on the radio settings page in the dashboard will force a one-time optimization of channels used by all APs within the dashboard network. This will usually result in a minute or two of downtime as the APs adjust their channel.  ... View more

Auto Channel dynamically adjusts the channels of the client-serving radios to avoid RF interference (both 802.11 and non-802.11) and develops a channel plan for the wireless network.  Auto Channel is a good fit for most wireless networks, providing a baseline channel configuration that can then be adjusted manually if needed.  https://documentation.meraki.com/MR/Monitoring_and_Reporting/Location_Analytics/Meraki_Auto_RF%3A__Wi-Fi_Channel_and_Power_Management ... View more

  You can go to Wireless > Configure > Radio Settings and select the RF profile (tab) and select UPDATE AUTO CHANNELS to refresh the channels.  In my experience that has fixed close proximity AP overlap issues.  ... View more

Depending on how your setup is configured as mentioned by @ww, the VPN Concentrator Deployment Guide might help you with your setup/configuration. https://documentation.meraki.com/MX/Deployment_Guides/VPN_Concentrator_Deployment_Guide#Deploying_a_one-armed_concentrator ... View more

I am not familiar with this NIC but it might be worth checking the MTU size? ... View more

Have you tried a different SFP+ module? ... View more

What firmware are the MS125s running? ... View more