Meraki

Adam_F · ‎Jun 19 2025

Sorry I should have clarified, this is in regards, specifically to the "Radius Monitoring" feature. While you're not wrong, it misses the point of what the feature can do when it works: it can cycle switch ports automatically, to recover devices that get placed in the critical auth/guest vlan. Without it, that is a manual process where you must bounce every port yourself. https://documentation.meraki.com/MS/Access_Control/MS_Switch_Access_Policies_(802.1X)#Other_RADIUS_Features

Adam_F · ‎Jun 10 2025

I just found out Portnox developers are testing a fix for this! 🎉 🎉🎉 Told them I would be happy to help test it. No idea when or if it will make it to release/production.

Adam_F · ‎May 5 2025

I tried for a solid month, opening cases with both Meraki and Portnox. I didn't get any upcoming fix, seemed they wanted to blame their azure hosting as blocking it, but clearly that isn't the case because of the "invalid shared secret" attempts being logged. Their workaround was to use portnox local radius as the primary radius (which yes that works, but does not fix the cloud radius). On Meraki's side, while helpful, no workaround or upcoming fix.

Adam_F · ‎May 2 2025

Just a heads up to all my fellow folks. I ran into a compatibility issue with Portnox cloud radius and Meraki radius implementation. The problem: Meraki likes to send Meraki_8021x_test radius requests to test if the server is alive/up. (Identity is Meraki_8021x_test and no password) Portnox likes to take those requests and throw them in the trash and not provide any response so Meraki thinks the server is dead and will continue to hammer Portnox with more of them. Portnox will fill its alert system with access attempts (invalid shared secret). This is one of those issues where the two companies' engineers would need to collaborate in order to play nice with each other but getting both sides to do so is impossible. The issue affects Portnox Cloud radius only. Portnox local radius is working properly and sending rejection/response. What Meraki can do to fix: Give me the ability to configure a password for Meraki_8021x_test identity. (unlikely to happen). What Portnox can do to fix: respond with a rejection, don't just discard.

Adam_F · ‎Apr 1 2025

Facing this exact issue as well. I love meraki don't get me wrong, but if I may just vent a little about this... Who's brilliant idea was it to make stack switches reboot at the same time and why is it so difficult to make them do a staggered reboot?! At least give us the option. Because, they market these things as "For the data center" but then you run into something like this.. (smh). Our solution is going to be to move away from external storage and switch to a virtualization platform with integrated storage instead. It's a real shame that we can't have staggered reboots for switch stacks. It would also be nice if we can disable auto-firmware-updates on critical infrastructure.

Adam_F · ‎Jan 22 2025

Happy new year 2025! 🎉 I desperately need dark mode. 😎 Every time I manage my company's networks, I go temporarily blind. 😭 I hope beyond hope the rumors that dark mode is coming are true. Wen?! Wen 🤔 wen 🤔 wen 🤔 wen??? I need dark mode Meraki dashboard in my life. 😎 🙏🙏🙏🙏 Sincerely, Every network administrator

Adam_F · ‎Mar 18 2024

Bummer, came searching to see if this was possible. +1 please add this.

Meraki

Community

About Adam_F

Adam_F

Community Record

Badges

Re: Portnox NAC incompatiblilty issue

Re: Portnox NAC incompatiblilty issue

Re: Portnox NAC incompatiblilty issue

Portnox NAC incompatiblilty issue

Re: Best practices on switch stacks?

Re: dark mode for dashboard?

Re: Schedule a reboot of a Meraki Device?

Re: Portnox NAC incompatiblilty issue

Re: Best practices on switch stacks?