You might be able to  use this method:https://documentation.meraki.com/MR/Encryption_and_Authentication/Meraki_Local_Authentication_-_MR_802.1X   Set something like this: I've never done it so can't speak to whether it would actually work, but as long as each client has a cert signed by the client certificate CA and that's what presented it seems like it should work. I'm not sure I'd recommend it unless you have no other options. A shared certificate on every device with no verification could leave room for a lot of shenanigans. This is another serverless method that could work that I'm aware of: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Certificate-based_Wi-Fi_authentication_with_Systems_Manager_and_Meraki_APs The new access manager may be able to help eventually if you have an Entra environment:https://documentation.meraki.com/Access_Manager   ... View more

Congrats!! ... View more

Per the documentation, the called station ID attribute contains the SSID so you should be able to filter on that basis within NPS. There is also the ability for support to enable the Filter-Id so that you can return a group policy value based on staff or student and consolidate SSIDs. ... View more

I just did a test on a couple of orgs. One on shard 874 worked fine, one on 97 got what you are seeing. I would open a support case. ... View more

You can do the capture on the Meraki side from the Meraki. On Windows all you  need to do is install wireshark.  https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Packet_Capture_Overview https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Getting_started_on_Packet_Captures_with_Wireshark That may help you, Meraki support may be able to help to some extent, but if the issue is on Windows it may be best effort.     ... View more

Can the MX ping the NPS server? Is any authentication working? If you do a packet capture on either end what do you see?  Is the right source IP configured in NPS? https://documentation.meraki.com/MX/Other_Topics/MX_and_Z-series_Source_IP_for_RADIUS_Authentication ... View more

The two things you are looking to resolve are not exactly the easiest to do in a Meraki environment. The level of routing you need to make this work automatically is not available in Meraki right now.  If your team has a desire to move to a fully Meraki setup, this is where I'd consider switching your MPLS circuits to DIA and putting in MXs at each site.   Regarding your comment about SFPs, there are generally not issues with Meraki SFPs interfacing with other vendors SFPs in their gear. I did notice you mentioned MS120 switch models. These are end of sale next month and end of support announced for 2030. I would be looking at MS130s or MS150s for your access layer and perhaps 9300s for your core. Overall, I strongly recommend working with your Cisco account rep and partner to get into detail with your requirements and make sure you can get the solution you need. ... View more

Meraki is working on rolling out RBAC to allow you do do just that. The first portion of that is in Early Access now: https://community.meraki.com/t5/Feature-Announcements/Introducing-RBAC-Role-Based-Access-Control-Foundations-for/ba-p/257642 If you need something more immediately or beyond the scope of the above a marketplace partner has a solution: https://www.boundlessdigital.com/network-management/meraki-automation/role-based-access-control/ I can't speak to its quality and am merely sharing to make you aware. Other options would be to develop your own tools based on the API. ... View more

Making the sites find each other is easy and at the simplest level you could just use static routes and perhaps mix in OSPF if there are capable switches at all 4 sites. However Meraki does not support backup routes on switches.  Not even on the 9300s where the base IOS could do them. A few possible solutions: 1) If you have 9300s at Sites 3 and 4 you could possible convert them to IOS mode and then you'd be able to use SLAs. I'd call this the cheapest scenario as you don't need other equipment. Learning curve could have some time cost. 2) You could put a router at sites 3 and 4 that can do SLAs between your switches and the circuit. 3) Get your ELAN provider to switch to DIA circuits and get MXs for Sites 3 and 4. I'd call this the ideal scenario if your goal is to have everything Meraki There are lots of smaller pieces to all of these scenarios which you may want to engage your partner on if they aren't just a reseller.   Hopefully this at least helps you get on the right direction.   ... View more

  You may want to look at this: https://documentation.meraki.com/MX/Access_Control_and_Splash_Page/MX_Access_Policies_(802.1X) If you have one of the smaller models you can do more normal access control. What you found is designed for splash page control  for whole VLANs and that may be the source of the limitation.   ... View more

Yes that would be the easiest solution. ... View more

Ok so this is my second comment. You need some sort of firewall to enable routing between these networks. You are not using the MG as its intended (solely to provide internet to a firewall device). You certainly can connect layer 2 wise, but you will not be able to enable layer 3 communication between the two networks as-is. ... View more

I'm not entirely sure what you are asking so going to attempt to provide two answers based on what I think you may be asking:    If about getting the MG online, The MG41 will connect to any standard lan via ethernet. The MG41 generally gets its internet from its cellular connection so it doesn't need DHCP. If you are having to setup/troubleshoot in safe mode it would need it temporarily If you have an MS130 and are using the MG41 to provide internet/dhcp to the devices on the MS130 and the MS130 yourself, you will be able to  make the physical connection but the MG doesn't support routing. You will need to change your configuration and put other items in place to have the networks talk. An MX would be the easiest thing, but it depends on your requirements. ... View more

MX100 and MS120 use regular C13. A C15 cable would also be compatible and allow reuse with higher voltage gear if necessary. ... View more

Nexus has not been actively discussed in any of the various conversations I've ever been part of. The goal is the entire Catalyst line and that timeline is still rather far out for completion. NX-OS would need completely new code to operate and require significant engineering effort. Anything is possible, but I would not hold my hopes up. Your account rep may be able to tell you something more under NDA. ... View more

These are basically (and perhaps completely) the same cord. One is just the regular Cisco SKU and one is the Meraki SKU. Because of the different fulfillment methods they have separate skus to keep things straight. ... View more

Well that seems new, we've had a few posts about these alerts since they added them and this hasn't come up! 👏 ... View more

I sympathize and would also love to be able to turn these off when it's known and not going to be changed. Recommend filling out a give your feedback: https://documentation.meraki.com/General_Administration/Other_Topics/Give_your_feedback_(previously_Make_a_Wish) ... View more

I just checked a random sampling of my clients/networks and don't have issues. Have you tried the normal different browser, clear cache, clear cookies stuff? If so I'd open a support case. I'm not aware of any plans to remove this. ... View more

I just checked a random sampling of orgs I have access to and don't see the issue but I don't have too many clients still on the firmware level you are on. ... View more

I was told free conversions ended 1/31 when I asked for one after that. I made a bunch of complaints about the lack of communication and kept asking to talk to a manager and got a one time exception approved. Luckily we caught everything else in our pipeline. ... View more

It's not listed on the 9176 or 9172 datasheets, but the 9178 does list the supported bands and those are not included: https://documentation.meraki.com/MR/MR_Overview_and_Specifications/CW9178I_Datasheet My assumption would be if the highest model doesn't have them, the lower levels won't either, but your account rep may be able to have an SE confirm. ... View more