There is one thing that will not work: If you now have a LAG between the 3504 and the 2960, this must be removed and configured for individual interfaces as the LAG implementation on the WLC and the MS switches is not compatible.
... View more
The NICs don't report anything back and they don't participate in STP. The logs show a completely normal behaviour. When a port comes up it has to transition to designated to make sure the attached device will receive traffic.
... View more
Meraki really doesn't like to talk about roadmaps. Being able to use more than two WANs is quite often asked here in the community. But probably the core of the MX has to be changed significantly to make it work. Don't wait for it, likely it won't happen soon. But tell Meraki that you want to have this every time possible.
... View more
This is what I expected when I saw this new firmware. But the documentation is not yet updated. This would be great although IMO this feature is quite useless with only the MS390 supporting it on the switch side.
... View more
Yes, but the question is if the RADIUS server processed the last request and just the reply got lost somewhere of if the RADIUS server was not able to process the last request. Which RADIUS server is it?
... View more
If the serial number doesn't work, I would assume that you've already set a new password in the dashboard and now need to use admin and this password. Just because the MX is in a new location it doesn't mean that the recent config is not used any more.
... View more
@Gsintes I have to disappoint you, also this year the socks are mine ... (No, better luck this year, everyone running a Meraki network deserves Meraki Swag!)
... View more
I think the problem you are running into is based on that Meraki doesn't yet support transition mode with OWE. There you would see one SSID and the capable client would use OWE and the older client would use the standard open mode. Unless that is implemented by Meraki I would either not use OWE or use two SSIDs with different names like "Guest" and "Guest-Secure". But I am not sure what you mean with the EAP methods, This is typically related to an Enterprise WPA implementation and will always show up on the client devices.
... View more
My New Year resolution for this year is to catch up with the previous years resolutions ... 🙂 And with having the term "500-220" multiple times in this thread, I could think of a New Years resolution for @AmyReyes and the Community team: What about the CMSS-badges?
... View more
@RaphaelL Last year I missed you, but perhaps we meet this year. (I just declare that I identify as one of the nice people 😀) And good luck with the rest!
... View more
As already mentioned, no problem with this setup. If your MX is the only device to use this IP subnet, you can ask the ISP to route it to your MX IP. It's slightly more secure and you get one more usable IP.
... View more
The way the actual WPA3-SAE implementation is done, MPSK (or iPSK without RADIUS) can not work. The AP had to try multiple PSKs until the right one is matched. But this was prohibited by design in WPA3. On each connect, only one PSK can be checked. iPSK with RADIUS could work, but probably needs to be implemented.
... View more
I just got an answer from Support: RADIUS-Authorisation is not supported at all on the MX, only Authentication. Ignoring the VLAN-attribute that is sent by the RADIUS server is the expected behaviour. I just added feedback on this topic on the dashboard.
... View more
What are you referring to with "Study-Guide"? At least my experience was that many of the questions were only to answer after reading lots ans lots of the documentation and practicing the stuff. Good luck next time.
... View more
