I'm with you there.  We had a new location stand up with full Meraki.  (32 MS390 switches, an MS425 Agg switch, an MX250 soon to be 2, 33 MR56 APs).  It was kind of a test for us to see if we could replace most of our Cisco with Meraki.  We just worked through a QoS/SMB file transfer issue that would determine if we go full Meraki throughout.  That test was successful, only because the Meraki support keeps us up to date, and is more than willing to work with us at any point.  So even if the product isn't 100% ready for prime time (which I do believe we are currently in that situation), I can still justify moving forward with them due to the support that we have received, and continue to receive.   I'm fairly excited for what the future holds for Meraki, especially with the new addition of the sensors and cameras.  Just have faith, Meraki will take care of you. ... View more

@Iridium79 , all you have to do is ask...that's all I did so that I can update my management and show proof that they are still working on it.  In all honesty, Meraki support staff are some of the best people I've worked with.  If you want to go to Ubiquiti then do it.  If you don't like Meraki move on.  They work very well for us. ... View more

They keep updating me every two weeks.  They have replicated it in their lab environment and are working on a fix.  That's about all they can give me at the moment.  But frankly, in most firewalls you don't get LLDP info.  I think really our issue is that the topology displays completely wrong, and the clients may look like they are part of a switch that they aren't because of it.  So it's really the way they seem to be interacting with the dashboard.     We are also working on our own internal sort of dashboard via APIs, so we don't even have to login to the Meraki Dashboard most days. ... View more

I know this is a bit of an old post, but I'm hoping someone will be able to answer me.  This is going to become a problem for us, do you know if there is any movement on allowing the MX250/MX450 ports to be able to be aggregated? ... View more

Yes, they will send it, and the Meraki Dashboard seems to ignore the LLDP packets.  Not sure why. ... View more

The only way we were able to remedy this is to turn of CDP completely, and install an aggregations switch (we used an MS425) in between the MX and the rest of the switches.  The LLDP still does not show correctly between the MX250 and the MS425 unless you use an API to pull the correct data from the MX.  It's really a function of the Meraki Dashboard not pulling the correct information, or not pulling information in a timely manner.   We have started moving away from the Meraki Dashboard in favor of API calls because we get much more accurate information than the Meraki Dashboard will ever give us.   I recommend not using the Meraki Dashboard, and build your own dashboard via API calls.  It is a lot of initial setup, but you'll pull less hair out than looking at inaccurate information in the Meraki dashboard. ... View more

Yup, we have a case in as well.  We are also not getting LLDP information from our MS390s.  We are on the latest beta firmware for both our switches and our MX250, and we still have the LLDP issue.  I have it setup to get a check in on the progress every 2 weeks.  It's an active problem they are still working on. ... View more

For the MX84 and MX100, they are currently in development for replacements that will be FIPS 140-2 compliant that have similar price points and throughput, but the current MX84 and MX100 will not be unfortunately.  At least that is what my reps and Cisco/Meraki engineers are telling me. ... View more

From my Meraki rep,   Meraki MX450, MX250, and any MX6x will become FIPS compliant, but the rest of the MXs will not.  So for instance, the MX84 will never be FIPS compliant. ... View more

I'm really glad we held out for Meraki's FIPS compliancy.  This is going to just make everything much nicer in my realm. ... View more

That's your choice.  I'll just continue to buy the cheapest FP1010 for FIPS and run Meraki everywhere else until Meraki gets up to speed.  I love Meraki and their concepts.  Now with the muscle of Cisco, I can wait.  I'm patient.  ... View more

From my rep at Meraki...   Here’s the synopsis of what we heard from Product Management yesterday:   FIPS 140-2 validation for AutoVPN network traffic has been delayed due to a software architectural issue with incorporating the FIPS validated object module that they were looking to use. As a result, we are looking at a minimum of 18 months before AutoVPN traffic will support FIPS 140-2 validation as they will likely have to certify a brand new hardware-based object module and this process alone takes around 12 months. While FIPS for AutoVPN has been delayed, this software limitation will not delay the roadmap for FedRAMP certification. Development efforts are now being focused on achieving FedRAMP in progress (and certification) by using this object module for Meraki control traffic (mtunnel). ... View more

Since it is not May as you state, I have not heard anything more.  I'm going to at least wait until then to start asking more questions. ... View more

Due to confidentiality and non-disclosure agreements, I cannot share the content of the signed letter I received from an SVP in Meraki.  I can tell you that though the Meraki devices may not be on the FIPS compliancy list by May, the intent is to be by May. ... View more

I currently run this way.  I have a read only login to my main ISPs Meraki dashboard to gain some visibility, then I have my own Meraki dashboard to configure our own devices.  Works really well, and when you log into the Meraki website initially, it allows you to choose which dashboard you want to work with.  It's quite slick actually. ... View more

I have just heard a rumor...mind you it is just a rumor and is not substantiated at all, but I heard that Meraki devices will be on the FIPS 140-2 compliance list as soon as May of 2020. ... View more