Just follow what's in the slides you received and everything will be fine.   I think there's nothing better than a practical test for you to validate the difficulties yourself. You have a plan, now you just need to execute it. ... View more

What firmware version are you runnig?   As mentioned it's now under smartports.         ... View more

Pay attention to the firmware requirements.   For MS switches and Catalyst switches (cloud management with IOS XE 17.18.2+)   HW and SW Requirements Platform Software Requirement MS Switches MS120, MS125, MS130, MS130R, MS150, MS210, MS225, MS250, MS350, MS355, MS410, MS425 and MS450 series switches While there are no minimum firmware requirements for Profiles, MS 15.21.1 or later is recommended. Firmware MS 17 introduces support for Automations.   And check if you enabled it in Early Access. ... View more

The MS doesn't have a WAN port, but rather a management VLAN. You can use a DHCP or static IP address; it doesn't make a difference as long as it can communicate with the Meraki Cloud. ... View more

Please check the documentation.   https://documentation.meraki.com/SASE_and_SD-WAN/MX/Design_and_Configure/Configuration_Guides/Networks_and_Routing/MX_Layer_2_Functionality#LACP_and_Link_Aggregation ... View more

You need to configure a transit VLAN and use VIP co figure on the Warm Spare.   https://documentation.meraki.com/SASE_and_SD-WAN/MX/Design_and_Configure/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair#WAN_Virtual_IPs ... View more

It's now under smart ports.   https://documentation.meraki.com/Switching/MS_-_Switches/Design_and_Configure/Configuration_Guides/Port_and_VLAN_Configuration/SmartPorts#Applying_the_Profile_to_Switch_Ports ... View more

This is the expected behavior. ... View more

Just to clarify, the method you're suggesting doesn't prevent the client from associating with the SSID, it only blocks browsing.   This still presents a security risk because the client will still be receiving an IP address, allowing it to scan the network.   I don't know if you've done this before, but what he actually wants is to implement MAC address filtering, so only clients on the list will be allowed to associate with the SSID. ... View more

It's not the same thing. This way is a possibility, but I think that it's more painful. ... View more

Could you please share the solution so that future readers can use it as a basis? ... View more

You can find more information at the link below.   https://meraki.cisco.com/trust/#data-centers ... View more

While the term “shard” itself isn’t explicitly used in the current Meraki Cloud Architecture document, the architecture does describe how customer management data and dashboard services are hosted and replicated. Those functions map directly to what Meraki engineers commonly call shards.   According to the documentation, if a data center fails completely, the backup center can be activated within minutes using real-time data replication. ... View more

I just checked here and the parameter is enabled by default; you probably disabled it at some point. ... View more

Here you can find all the information that you need.   https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Troubleshooting_and_Support/Troubleshooting/Getting_started_on_Packet_Captures_with_Wireshark ... View more

  The block and allow list is for a different purpose and I believe it won't meet your needs.   https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Operate_and_Maintain/How-Tos/Blocking_and_Allowing_Clients ... View more

Meraki doesn't have that level of granularity. ... View more

Meraki does have that limitation. Unfortunately, to restrict access via MAC address, you need a Radiu server.   https://documentation.meraki.com/Wireless/Design_and_Configure/Deployment_Guides/MAC-Based_Access_Control_Using_Microsoft_NPS_-_MR_Access_Points/Enabling_MAC-based_access_control_on_an_SSID ... View more

Yo can call them.   https://meraki.cisco.com/meraki-support/overview/ ... View more

In short, what you want to do will not work.   Because when RADSec is enabled for any server on an SSID, the Meraki access point changes the transport mode for all RADIUS authentication to TCP instead of UDP. ... View more

Another important detail: RadSec is TCP and regular Radius (port 1812) is UDP. So, although you can configure both on the same SSID, it's recommended that you use one or the other, not both. ... View more

Strict Priority Order The servers will always be contacted in the order listed in Dashboard. In the example given, that ordering is 1,2,3. That means that server 1 is always contacted first and server 2 will only be contacted if server 1 cannot be reached. Similarly, server 3 will only be contacted if neither server 1 nor server 2 can be reached.   https://documentation.meraki.com/Wireless/Design_and_Configure/Configuration_Guides/Encryption_and_Authentication/RADIUS_Failover_and_Retry_Details#:~:text=(see%20below).-,Retry%20Timing,An%20error%20packet%20is%20received. ... View more

You asked if it was possible to configure it, and in fact it is, but whether it will actually work is another question. 😉 ... View more

Remember, the SSID will respect the server list from top to bottom, so while the server above is responding, nothing will be forwarded to the server below. This explains the behavior. Keep them on separate SSIDs and everything will be fine, or move everything to RadSec. ... View more