Hi ! Thanks your quick replies to my question ! I'm stuck in a datacenter move, so I'll try this afterwards. But that's exactly the right idea for what I'm trying to achieve, so thank you very much in advance !   ... View more

I really cannot believe that such a simple feature as deleting an SSID isn't possible. ... View more

Any updates on this issue? I have been having this problem on my ms-220s and sure enough tried to update to 10.40 tonight and 1 of the 220s hung. It is not easy for me to get to this switch and rebooting the switch never seems to help.   this issue has been going for over a year and still happening? Has anyone found a way to fix this remotely? ... View more

sounds good... but then i need to have a mac for the profile manager to be installed, correct ? ... View more

Same thing here. i was told it is a GUI bug and support is on the run to fix all affected networks ... ... View more

Here's what I know   10.30 seems to work well with edge stacks - for example MS225   It has a lot of fixes   However, it has some serious issues when used iin an environment that has MS-425s as the  L-3 Stack and Dual LACP Links from MS-255 distributed edge sw to  a MS-425 L3 stack   From what I can determine after several sessions with TAC the last few days - Multicast was broke in this release and I would not recommend using it - especially if you have dual LACP Links   The 425 stack seems to have excessive CPU utilization and becomes very unstable (random reboots, etc.) - until I disabled Multicast and the 2nd Link of all LACP Uplinks   Has associated Spanning tree issues   If you are running LACP Links to edge stacks, connectivity is intermittent - for example, WAPs attached to Edge Stacks will randomly disconnect from Cloud - Overall network throughput will be  bad  - pinging the Net Management IP of the 425 Stack will result in dropped pings and high latency   It seems that Legacy Cisco switches running LACP Uplinks and connected to a MS425 Stack -  work well     I set up the LACP Links on the Legacy Cisco as follows:     interface GigabitEthernet0/51 description UPLINK-TO-MDF-425-16-CORE-STK switchport trunk encapsulation dot1q switchport mode trunk channel-group 1 mode active spanning-tree bpdufilter enable ! interface GigabitEthernet0/52 description UPLINK-TO-MDF-425-16-CORE-STK switchport trunk encapsulation dot1q switchport mode trunk channel-group 1 mode active spanning-tree bpdufilter enable   I used the bpdufilter enable because the 425 doesn't run legacy Cisco STP (pvst, etc.)   This seems to work well   I have been told that the developers are aware of these issues and are working on fixes   Having said that, I was able to make a couple of networks stable at 10.30 by only using a single uplink from the Edge stacks (NO LACP) and disabling Multicast Routing in the 425 Stack   If you need multicast - then I don't think 10.30 is for you   If you need Multicast and or LACP - look at 9.37   If you don't need these or you are not using a MS425 stack as the core then 10.30 seems to work pretty well   Lotsa fixes - but needs more   I have been told they are working on these issues   Good luck               ... View more

we had 14 units of MS350 that have this issue too. Luckily Meraki recall the units and we got it replaced 🙂 Not bad Meraki 🙂 ... View more

I’d also love to see a config export and import functionality. Of course the API can do this, but it would be great to have this as a HTTP up- / download feature in the dashboard. Ideally for each network and for the whole org. ... View more

Changed the core switches over to the MS250 Meraki Stack last night. Connected them to 8 HP Edge switches without problem. I dint realise the HP switches were such a mess with their trunks, native vlan mismatches unused vlans and some even in unused LACP groups, with all that mess the trunks still all worked. I had read that if your trunks were not configured identical each side you were in for trouble, but not this time. Cleaned up the trunks on the HP side anyway, next will be to implement LACP between Core and each HP Edge. Layer 3 setup is easy as pie, and yes yes yes I love the monitoring! ... View more

as long as the catalyst does not transport ALL VLans you should create one. But i'm not the catalyst expert... ... View more

I thought something like that would be the case. You‘re right with the IPs, two are left - sorry my fault, with these two free IPs the situation is not that odd.   I had another network-supplier in mind where this could be accomplished with the help of a loopback interface which is not supported until now on Meraki switches. ... View more

For syncing two NPS you can have a look here: https://deployhappiness.com/two-network-policy-server-tricks-subnets-and-syncing/ ... View more

Sounds good, will test in the 10.x branch, too. ... View more

Are these switches directly connected to a router or firewall or is there some kind of tunnel in between ? ... View more