After thinking about it, all the EOL information should be available via the API, with the results being clean JSON objects. ... View more

So much makes this a terrible idea as a permanent solution, but it could be acceptable as a temporary solution while the migration is ongoing. Clients will be able to roam. But roaming is always affected. For .1X, there will always be a slow roam between the two worlds, and the clients must go through the entire EAP exchange with the radius server. This is fine for PSK, as the handoff from one AP to the other is always relatively fast. Regardless of .1X or PSK, the client has less power to choose the next roam candidate as the neighbor reports will not include the APs of the other technology. And you need to ensure that the other world is not classified as rogue APs. ... View more

There is an important implication is Purroy’s answer: The Wi-Fi 6 APs (non 916x) don’t support the Meraki Persona. But if you have a 9800-L/40/80 with these APs, this can be added into the dashboard for monitoring. ... View more

I would open a support case for that as there should not be DFS events. Of course, there could happen events based on other interferences. ... View more

Luckily, the client base seems to use the RNR quite efficiently. With that, even 40 MHz without PSC is possible: https://www.youtube.com/watch?v=lAG5jXZCd_8   ... View more

You can go to your preferred Cisco Learning partner to attend this training: https://learninglocator.cloudapps.cisco.com ... View more

Another better solution is to give them internet access on a dedicated SSID (for example, the Guest SSID) for their personal devices. ... View more

This is a perfect use case for the new Auto RF functionality with AI. At least when you have repeated events on multiple APs. It will take care of the channels and ensure that only the relevant APs are excluded from those impacted. For the client impact at a DFS event, the AP will send a Channel Switch Announcement before moving to the new channel, giving the client an experience comparable to a roam. But as usual, it doesn't always work that smoothly with all clients. ... View more

This is nothing more than an additional condition in the corresponding rule in the authorization policy. But it is also an administrative nightmare. The better solution would be to use TEAP with EAP-Chaining. ... View more

Not anymore. SDW+ can now be bought per network, even in Co-Term. ... View more

Oh, I also missed that. Very good and important question ... ... View more

  @PhilipDAth wrote:   When you lick on it and device in - what device(s) does it say is generating the traffic? Licking your AP could get you a free AP:     ... View more

Yes, it is also possible with the MX. Your mentioned benefits are real, but the drawbacks of the MX for extranet VPN are also often relevant. You won't have a single license renewal if you place the MX in a different dashboard org. But the rest should be fine.  ... View more

If it is an Intel wireless card, the first step in troubleshooting is to update the drivers to the actual version from the Intel download site. And for the invalid authentication, the RADIUS log could give you some more information. ... View more

How you missed this update? I have no idea how this could happen ...! 😉 ... View more

Whoever told you to look at the maximum frame rates, don't listen to him, as these numbers are pure marketing beeeeep (censored) and have no relevance at all in the real world. ... View more

It all depends. With redundant MXes, there is no IPv6, and I don't use PPPoE to have both ISPs on both MXes. On other devices, I use PPPoE on the MX, but not with FB. At home, I have two FBs, only one MX, and an IPv6 /56 prefix only from Telekom. This is delegated to the internal network. ... View more

And for "modem" mode, I have a better experience with Draytek Vigor than with FB. ... View more

This is what I do: FB runs in routed mode; I have a dedicated transfer network between FB and MX. typically 192.168.177.0/24 for the first FB (Telekom at my home) and 192.168.178.0/24 for the second FB with the connection Vodafone to MX The FB has static routes to the MX IP The MX is configured for NAT-Exemption to avoid double NAT. This works fine but the NAT-Exceptions have some restrictions: https://documentation.meraki.com/MX/Networks_and_Routing/NAT_Exceptions-No_NAT_on_MX_Security_Appliances ... View more

This is an important point I didn't think about before. In my setup, only Switch 2 should provide power to the MG, and PoE needs to be disabled on Switch 1. If Switch 1 goes down, ISP1 is lost, and the MG as ISP2 needs to stay up. ... View more

Not a single point of failure, as these switches are also redundant. One for ISP1 and one for ISP2. I use either the CBS350-8 or Catalyst 1000-8 for this. ... View more