Good Morning @GiacomoS. Thank you for the update and I appreciate that either you may not have all the information available to you currently or that you may not be allowed to release all the information. Hopefully further insights can be provided into why, what and when a change was made to 'restrict' the MX85 throughput from 750Mb down to 500Mb with all features turned on? I am curious though as to the testing feedback that @PhilipDAth stated, which seemed to indicate that if the resource being accessed is IPv6 then the MX85 will provide 750Mb but if it's an IPv4 it drops to 500Mb. It almost seems that there is a feature/function that restricts IPv4 which doesn't apply on IPv6? Are all features/functions supported on both IPv4 and IPv6. I'm thankfully not affected by this change, as I currently only have MX450s to support, but if there has been a change, of which there does see to have been, any restrictions/reductions in performance should be included in release notes or notifications in the dashboard (Sorry not meant to sound like a rant, just want to make sure this isn't another change similar to Apple battery/performance change in the background for the 'benefit' of the user). Please continue to look into this, as I'm sure all those who have taken part or read this thread are curious as to the cause. ... View more

I'm sure you have already checked this, but when your customers have complained that it has gone slower, was it close to a firmware update? Just wondering if there was a particular 'fix' included in a firmware which 'inadvertently' restricted throughput of devices.....If it was, could you try reverting to a previous firmware to prove it? Have you have tested it with the advanced security features off to see if you get the 1Gb throughput? ... View more

I have a similar issue, except it is between C9300 & MS390 stacks. The allowed trunk ports match but the one that doesn't is the native vlan, but I haven't changed the value yet as they are working as intended and they are a critical piece of our infrastructure and I've yet to pluck up the courage to make a change. If you view the ports in the meraki dahsboard, what does it show under the vlan mismatch info when you click on Warning: Vlan Mismatch under the CDP/LLDP value in the status section? Image is taken from my dashboard, but I can't show the info under the warning pop-up   ... View more

After receiving an update from Cisco (I am unable to share any information on this), I have re-on-boarded our Catalyst switches into the dashboard. I think there have been some updates to the on-boarding, as all of my stacks on-boarded first time with all members of the stacks. Previously on the odd occasion, some members wouldn't show in the dashboard. Also, clients connected on non-managed vlans and port-channel interfaces are also showing correctly, previously it seemed to only show clients on the switch on-boarded vlan interface. So Kudos to Meraki to continue to develop both on-boarding and monitoring of Catalyst switches. If Meraki are taking requests, could you please add a 'recommended IOS version' for each of the on-boarded switches to alert us of a suggested upgrade for them, and ideally add the functionality to perform the upgrade to the IOS similar to the current options for Meraki switches, i.e. Now or Schedule it. ... View more

Upgrading the IOS to a supported version for the catalyst on-boarding resolved the issue. ... View more

@jorisjean No update on this sorry. ... View more

@cmr No banner on the dashboard. No update on the support call I raised since the last one yesterday afternoon, however I have had emails from a few Cisco reps. I've been advised, that the change that took place on Thursday night has been rolled-back and Cisco have a detailed understanding of what happened and discussions are already under way to define what needs to be put in place to prevent this from happening again. Until then all our switches have been removed from the dashboard. With regards to changing the user privilege level, that would be a temporary fix, however I suppose you would need to make sure that the relevant commands are added to that privilege level for the dashboard to still have access to the information it gathers including 'show run'. Maybe someone from Meraki could advise which commands it needs to be able to run?? Please. ... View more

Thanks for the update. Hopefully this can get rectified quickly, and prevented from happening again, so I can on-board our switches again.  ... View more

I confirmed before posting this that no-one had logged onto the switches, or even had an open session and made any changes. But it's fair to ask the question. I've raised a support ticket with Meraki and thankfully I also have good relationship with the sales/technical reps at Cisco and Cisco Meraki..Can I just say Cisco and it covers both?? Anyway, it's looking likely that there was a change recently in relation to Catalyst monitoring in Meraki, but not had confirmation yet that it was absolutely the cause of the issue. I'll update once I have further details. ... View more

I've had that issue with a couple of stacked switches. I've re-ran the on-boarding process with one of the affected stacks and now both switches are showing in the dashboard. There is no need to remove the affected switch from the dashboard before re-running the on-boarding process. I couldn't find any reason why they didn't on-board the first time, versions and stack configurations are the same as other stacks that have successfully on-boarded without issues. ... View more

So unfortunately it is not fixed on this switch. Could it have anything to do with a character limit on the trunked vlans? ... View more

I had a couple of different switches reporting incorrect vlans being trunked. One of the switches was resolved, I'll double check if it was this one tomorrow and update you. ... View more

I haven't tested that, but I can try that out tomorrow on an unused port.  ... View more

The switches are Catalyst 9300s. ... View more

I've connected three switches, one individual and one stack of two. So far the individual switch is only displaying clients on the same vlan as the switch itself has an IP assigned to, and even then the actual amount of traffic linked to these clients is minimal Bytes rather than MB/GB. The stack is still currently only showing one switch and no clients. I have  only on-boarded these switches today. One other issue I've noticed is that it is highlighting vlan mis-match on some ports (these ports connect to MS390 switches), but the configuraiton is correctly applied to the switches, it seems the On-board switch which the Meraki dashboard isn't showing the correct trunked vlans, shows 1-1000 even though the vlans are named explictly. The switches are 9300 models and have advantage licenses. ... View more

So think I found the issue. The algorithms (mac and encrption) were restricted. I then realised that this switch is also running an old IOS, not supported by this tool....out of the 30 switches I choose to test it with, it's the one that hasn't been updated to 17.3.......I'll update the switch today and confirm that I can perform the pre-checks and on-board the device. ... View more

I can SSH directly to the switch itself from the endpoint that is running the onboarding app. I'm using putty to initiate the session to prove conenctivity. The switch is configured to only support v2, and the session from my endpoint is running v2. Is the on-boarding app itself only able to create a v1 session, I'd like to think not but just trying to understand why it's not working. ... View more