There they are... some of the usual suspects!  🙂  Congrats to the members of the month @Uberseehandel @Adam @PhilipDAth and thank you for your continued dedication and valuable contributions to the Meraki Community!  Congrats @MRCUR for your special recognition this month!     @CarolineS I'd like to add that while @MRCUR is CMNO # 12, not only is he an early adopter, but he actually provided valuable input and feedback during the development of CMNO itself!  Sometimes I joke with him that's the only reason he passed it.  (Joking of course! ...he rocked it.)  The initial batch of CMNO graduates just happened to be about 15 or so people (don't recall the exact numbers) and he was in that first round of official CMNO graduates.  So I often say that he's actually CMNO #1, in my book, anyway!  The #12 may just reflect the fact that he tested in the 2nd group or on the 2nd day that first week.     Quick funny story.  Only because the eagle-eyed among you will notice another vendor's switch in that image.  Which is ok, no environment is perfect (joke) and we all make mistakes sometimes (another joke).  @MRCUR asked once about using another vendor's optics, if only temporarily.  I explained that while Meraki does recognize (does not lock out) 3rd party optics, Meraki devices have an electromechanical plunger deep in the SFP cage that, upon detection of another vendor's optics, will immediately and forcefully eject the SFP onto the floor, and Dashboard will generate a scolding email alert, and shorten your license by a month on subsequent attempts.  His response was classic, something like, "I think I'll go make a wish, can you put in the FR, I've gotta see that!" 🙂    ... View more

Yes, this is being looked at, stand by... ... View more

Interesting, I tried it, and as soon as I type a password into the box (or click the generate button) a checkbox then appears.  Sure enough, when I un-check the box, I still get an email, but the username and password are suppressed.  Same for you?   ... View more

Negative.  If you are using the user creation under Network Wide > Configure > Users, you can create new user accounts like normal, and there should be a pre-checked checkbox that you can turn off so the user will not get an email with their password, however it must be a valid email address, and that user will have to get an email advising them they have been authorized to use a particular SSID.  I believe un-checking the box only suppresses the username & password in the email.    Since they must get an email to a valid inbox as part of the process, perhaps the best option might be to prime the user(s) with an email of your own in advance?  That "priming" email could explain what to do, which might involve them being taken to the account info update page where they can update their email or password or view balance, etc.  Hope that might help.  More info here: https://documentation.meraki.com/MR/Splash_Page/Managing_User_Accounts_using_Meraki_Authentication     ... View more

Yes, it is being looked at and your wish is not the first for exporting >60 minutes.  Best to speak directly with your Meraki SE to discuss your options. ... View more

Hey folks, sorry late to the thread, @MRCUR is correct, that setting is really for when you have L2 versus L3 connectivity downstream.  That said I don't have an answer at the moment, have you bounced it off Support yet to take a look? ... View more

Thanks @MRCUR for the shout-out, the Community has become so well received, successful and (most importantly) helpful for so many, it's hard to NOT check on it every day!  Spare moments?  If you find any please send me some.  haha ... View more

Great to see!  Thank you Caroline for all your dedication and hard work to make Meraki Community such a big success!  I'm excited to be a part of it, and thank you to all of our super-dedicated members who help out tremendously and on a volunteer basis... YOU are also the reason Meraki Community now has 5,000 members and is growing every day.    In no particular order  @Adam @PhilipDAth @BlakeRichardson @Uberseehandel  @MRCUR @MilesMeraki @geoffbernard @Mr_IT_Guy @jared_f @WadeAlsup  just to name a handful of top contributors I've gotten to know over the past 6 months, thank you for bringing and sharing your Meraki expertise, positive energy, and IT passion.  Here's to the next 5,000 members!   ... View more

At your own risk I'll add.  Meraki does not lock out 3rd party optics, and I've seen multiple 3rd party optics work in Meraki switches, and if these work for you I won't tell you not to use them (since there's no other choice yet apparently) but it is officially not certified and not supported.  Definitely don't buy these in bulk until you've conducted your own tests on a trial basis. ... View more

One other comment, note that you can export (download button) the topology to an SVG file and import into Visio.   ... View more

Unfortunate situation and sorry to hear this.  To comment on some other points: No, this is not an attempt by Meraki to simply sell more equipment, and yes, this is legal under the California laws where Cisco/Meraki are headquartered.  And there are no 3rd party beneficiaries to the original agreement.  Agreements are honored in the case of company mergers, as there's a clear legal transfer of assets and ownership.   What it really comes down to is that when the equipment was originally purchased, the legally binding agreement is between Cisco/Meraki and the original owner.  That's the part that cannot be transferred, because an eBay seller is not an authorized seller/reseller.  There's a definite risk (regardless of vendor) when buying used equipment on the grey market, because it's completely outside the terms of the original agreement.    That said, my suggestion would be to do it again!  That is, since you probably spent a couple hundred dollars on the license which is now doing nothing, and the 30-day RMA window has passed, just purchase another MS220-48P on eBay (perhaps for under $100) and apply the license you already have, and hopefully the hardware doesn't fail in the next couple years.  Might be the best way to recover some of what you already spent. ... View more

Understood.  I'd follow up with your Meraki sales SE, let them know the case number from when you called in, if there was one, and get them the laundry list of missing features, they will be able to check which ones might already have a back-end feature that could be enabled for you, which ones might already have a feature request or possibly in development, and which ones are just not there yet and could create an appropriate FR.   ... View more

Understood, thanks @kevinfor for the details and yes, I'd agree that posting to the community could prompt additional customers to try some quick tests, reproduce the issue, and log a case with Meraki Support.  Good thought.  That can only be a good thing as it gives Support and Engineering additional data points to compare with their own reproduction.  I know that frustration when Support escalates something to Engineering and the only status is "no ETA" but you can certainly ping Support for weekly updates perhaps, chances are they might be able to see some internal notes/progress they can report on. ... View more

Sorry to hear there might be a known issue with multigigabit negotiation on certain switches, I'll check if I can find a status on it, but I'm sure it's being worked on.  It's not "if Meraki decides to fix it" but what is the reasonable time to do an Engineering reproduction, root cause analysis, and write and deploy a firmware fix.  Meraki has a good history of fixing similar bugs in record time compared to other vendors because of the power of cloud management... being able to see (on the back-end and on a world-wide scale) exactly how many products/customers are impacted, generate appropriate bug reports, pop Dashboard banners if applicable, and roll out firmware fixes in a methodical & controlled fashion.   To the 2.5Gbps point on the MR53, @PhilipDAth is correct and I'll add that Meraki did not arbitrarily choose the lower of two data rates and select 2.5Gbps versus 5Gbps. It's physics. The 3800 has a software-defined XOR radio and can do dual 5GHz, and a 5Gbps mGig rate is warranted/required.  The MR53/53E/84 have one fixed 2.4GHz and one fixed 5GHz radio.  So roughly speaking, running all 4 spatial streams (clients can't do this yet) at 80MHz channels with MCS9 (256QAM, 5/6 coding) and short 400ns guard interval, the theoretical max is 433.3 Mbps per SS, so roughly 1.7Gbps on the 5G radio.  Add another theoretical max of 800Mbps on the 2.4GHz radio and there you've got a rather convenient AP max data rate of 2.5Gbps.      Even if we had 4x4 clients in the mainstream, the only way you'd really stress the AP to that level (today) is probably in a lab environment, and only with the most pristine RF conditions.  Very unlikely in any typical deployment.  Now you might be thinking what about 160MHz channels, fair point, as that takes us closer to 3.5Gbps theoretical for the 5GHz radio alone, and perhaps more of an argument for 5Gbps mGig on MR53/84.  I'd argue that's also a rather large unknown.  It will certainly be some time before enough spectrum is allocated to have a reasonable channel plan for the enterprise with 160MHz channels.  And even longer before client devices with 4x4 and 160MHz channels go mainstream.  By that time, we likely won't be designing with MR53/84 anymore and will be into next-gen 11ax APs. ... View more

@ZDonaldson Yes @MRCUR is correct, make a wish is not for feature requests, although it's fine to strike up conversation regarding wishes in the Community, the best way is to always discuss feature requests with your Cisco Meraki SE.  We can access our internal systems to see if an FR might already exist, and tag your account or opportunity to specific feature requests, and we can also create net-new feature requests, but will typically ask for the specific need, shortcoming, and/or use case.    That process also provides us the info we need to research back-end features/options that might already exist, but are much less common and might not appear in Dashboard by default, in order to keep Dashboard less cluttered and intuitive for the masses.  So it's also worth checking with Meraki Support to discuss a specific feature, which might be exactly what you need, but could be more of a niche feature that isn't available by default, and can simply be turned on for you.    I know what you might be thinking, why not show every option along with information bubbles and documentation, and I get that, but there's an also effort to keep Dashboard uncluttered, especially if only a small percentage of worldwide users need a niche feature.  Bottom line is always discuss with your Cisco Meraki team and/or Meraki Support. ... View more

@ZDonaldson that's a solid wish, but I think that could be a huge lift, I like your thinking but not sure if that would happen anytime soon.  Although the process of making a wish and clicking the submit button might give the impression it's sending your wish packets with DSCP 46 straight to the bit bucket, I assure you that wishes do matter. 🙂  Here's some info from a post I made a while back...   First, every wish is recorded in the system and has a unique wish ID, and like you might expect from any flex table in Dashboard, the Meraki product teams can see the entire wish list, search and sort for any wish right down to who made the wish, date/time, and what page in Dashboard you made the wish from.     Since Meraki has grown tremendously the last couple years (now a $2B business unit in Cisco, over 1.4 million active Meraki networks and counting) there are now dozens to hundreds of wishes every week.  While there actually is a monitor in the product team area with Dashboard wishes popping up in real time, that's more for show.  There is not (at least not anymore) some poor soul who has the job of reading, categorizing and prioritizing every wish.     The make-a-wish system has been improved to examine the metadata of all wishes and intelligently look at wish data in aggregate to help automate the process.  This way specific product teams can get more meaningful wish lists that are already properly categorized by product and feature and keywords and how frequently the same thing is being wished for.   Wishes do matter and are sometimes granted!  Examples: 1. MS: When looking at an individual switch port's Dashboard page, at the bottom where you can see bcast, mcast, CRCs, fragment counters over the last 5/15/60 minutes or full day... You now have the ability to zero the counters and start from that instant by selecting "with live data" which is a feature that was born out of customer wishes.  2. MR: On the RF tab, instead of just having "with live data" which was always there, you can now select hour/day/week/month and do retrospective wireless troubleshooting to see how many clients were associated, radio utilizations, and interference levels.  3. MV: Camera admins can now select a maximum retention period, per camera, so you can force any camera to discard footage after X number of days.  4. MX: Load monitoring, as described here https://documentation.meraki.com/MX-Z/Monitoring_and_Reporting/Load_Monitoring was prioritized by customer wishes.   As a reminder for others who stumble across this post, it's important to make your wishes from the Dashboard page where it is relevant, because that is part of the wish data, and helps categorize wishes properly.  This is also why wishes (and this Meraki community) are not for formal feature requests or new product requests.  Direct those (and their use cases) through your Meraki sales teams.    ... View more

If it's a newer quad-radio AP with 3x3:3 or 4x4:4 like MR42/52/53/84 etc then they can draw a maximum power greater than traditional 802.3af 15 watts, so even though they tend to draw less than that on average, if they do not see PoE+ 802.3at negotiation upon bootup during LLDP negotiation, then they are forced to run in low power mode.  If you've done the basic L1 troubleshooting, and confirmed via packet capture for example that the proper LLDP negotiations are taking place and the AP is still ending up in low power mode, open a support ticket. ... View more