@Ryan_Miles Is there any documentation regarding Warm-Spare designs with using the MX85 WAN ports for PoE?  I have a single MG51 setup, both LAN ports on it are going to the WAN2 ports on the MX85 (primary and secondary). Only one port ever gets PoE, and so when that FW goes down, the MG51 goes down with it until the other connection from the other FW kicks in and starts to provide PoE. Not ideal, because it causes a 3-5 min outage while waiting for the MG51 to boot back up (or however long it takes). Opening a support case now to figure this out. Would be great if both WAN2 ports were able to provide PoE at the same time so there is no outage created. ... View more

Have you had any luck with these during fail-over @KarstenI ?   I have an MG51 plugged into WAN2 on FW1 and FW2 (warm-spare) and only one of the WAN2 ports ever provides PoE.  When the FW that is providing PoE goes down (reboot or whatever), the MG51 loses power, and then PoE on the other FW kicks in. So there is an outage that really should not exist given the physical redundancy, which is upsetting. ... View more

So I'm discovering now that the LAN ports on MG51, when connected to two MX85 WAN ports, only one port gets PoE. So if FW1 dies, and its the one providing PoE to the MG51, the second connection (which is up) to FW2 doesn't have PoE, so the MG51 goes down.  Any way to get dual-PoE from the WAN ports to both LAN ports on the MG51?  So there is no outage created. ... View more

I see it now via DHCP Servers & ARP settings, however I'm not sure its working. I have it set to block ALL IPV6 DHCP servers, but my switch is still getting an IPV6 via the ISP device. I have it routing through the switch first via transit VLAN so that I could split it off from there to go into WAN1 on both primary and spare MX units since I only have one physical hand-off from the ISP. ... View more

So I can't imagine there actually being any real 6GHz usage around you, so I would suspect cosmetic bug. The spectrum and channel utilization is nice but it has a history of being unreliable.   https://nolanwifi.com/2017/02/02/meraki-rf-falsehoods/   As for the MAC, I don't see 6GHz mentioned on this document, but I suspect its MESH https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Calculating_Cisco_Meraki_BSSID_MAC_Addresses ... View more

Thanks for bringing this issue to our attention. ... View more

Otherwise - not sure how I feel about this new layout. On both wireless and switch page, I now have a scroll bar at the bottom (left/right), whereas before I never had that and I could see everything. I have a 32" 4K screen and in order to remove the scroll bar I have to zoom out to like 75%.   See below, all I did was revert it back to the 'old version', which is just so much simplier.   ... View more

Meraki support got back to me with a fix:   We have investigated and the reason the issue is occurring, is because of the following Organization setting in the Meraki Dashboard: -If Organization > Early Access > 'Dashboard Design System' is NOT set to 'opt-in', then you experience the issue that you are. -If Organization > Early Access > 'Dashboard Design System' IS set to opt-in, then the issue no longer occurs. Can you please go to the specific section in Dashboard, toggle the setting to 'opt-in', refresh the page and confirm the issue no longer occurs? I will raise this issue with our Developers (after I check if it has not already been reported) and let you know what their feedback is. I believe they may fix something in our back-end systems relating to that specific setting which probably should not even make any difference and is essentially no longer required, as the new Dashboard look and has been rolled out to all customers and is the new look Dashboard, going forward. I performed this task and things appear to be acting normal now. One caveat that I re-raised in my case is that when I click the network drop down menu (I have lots of networks), I still get a scroll bar and the window for all the networks is larger than before I fixed this issue, but still seems small to me.   See image below: ... View more

Both my ORGs use SAML/OKTA SSO, and only one of them has this issue. ... View more

Haha, right?!   I just come here now to complain.  =( ... View more

I have another ORG that I just tested and it's working as expected, so I guess me and my lucky shard?   I'll open a case with support, thanks @Ryan_Miles  ... View more

Windows 11 Chrome and Edge, same issue. Scaling 100% Incognito mode makes no difference either. ... View more

Yup, it's a me issue. Thanks guys appreciate it! ... View more

Do you have a link you can share regarding that Microsoft issue? ... View more

Am I the only one still running 28.7 that isn't interested in going past that lol. It's stable, that's more important to me than any new features. ... View more

From what I hear, there is going to be an option to do this in the near future. ... View more

I just got confirmation from a Meraki TAC case that rebooting a switch in a switch stack will only reboot 'that' specific switch and not all of them in the stack.  If you want to reboot all the switches, we have to do them all individually. This lines up with my contact on the MS team feedback as well. This applies to all switches except the MS390. ... View more

So that document only specifies that the MS390 models will have the entire stack reboot if you click on one and reboot it. The non-MS390 models (say MS250 etc.), from what I have gathered, if you reboot a single switch in a stack, it will only reboot that single switch and not the entire stack. This is based on historical experience (it's just been forever so I can't remember well now) but also a contact who would know confirmed. I also opened a TAC case to have support confirm as well. So for now I believe you have to reboot each one manually in the stack, but I won't lie, that seems real lame. ... View more

So all my networks are on 14.33.1 and I was looking at upgrading to 15.21.1 and did some community searches and found several red flag discussions with people reverting back to 14.33.1. I'm not in any rush so I'll hold off, but it seems like 15.21.1 is causing issues for people. Thoughts? ... View more

The release notes from 29.5 and 29.5.1 are identical, like 100% the same. So what did this introduce/fix? ... View more

I can't speak for Meraki, but 6GHz (Wi-Fi 6E) requires WPA3 or better. Meraki's current implementation of iPSK does not support WPA3, so that is why you are running into that.  ... View more