I have used the following config on legacy Cisco Switches connected to Meraki via LACP   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 to get around the pvst - rstp incompatibility     ... View more

I use Cisco DAC and SFPs with Meraki switches - to date - no issues   Most Cisco compatible 3rd party devices seem to work well  ... 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

Still trying to upgrade   Have a RMA unit - plan is to upgrade as a stand alone - then add to Network - and hopefully upgrade it's twin     ... View more

ex post ... ... View more

The first upgrade was a push from Meraki - with no sequencing   Since then - they added beta feature to do staged / sequenced upgrades to my dashboard   My issue is ax post facto - after the non sequenced push - the 425s get hung in an unrecoverable state - can't go forward to 10.26 - can't go backward to 9.37   Sometimes after several hardware defaults - I am able to get out of the loop and go back to 9.37 - sometimes the switch is bricked - and sometimes after leaving the switch connected for 4 hours it magically exits the loop and downgrades back to 9.37   In all cases, during this process, the MS-425 gets partially through the firmware load, re-boots, resets the static to DHCP and loses connectivity   We don't have DHCP on VLAN 1 - and our external address is not on vlan 1 - so maintaining the static is important for us   The magic switch above recovered after 4 hours of several re-boots - I think - because I had set up DHCP on VLAN 1   Other switches are not a magical and they turn into door stops after several days of the reboot of death loop   To be clear - I had no issues upgrading/downgrading the MS-225s   Want to trade MS-425s ? ...... LOL     ... View more

I have a few sites that are running 9.37   I have some issues that are supposed to be fixed in 10.26 - so I scheduled an upgrade to 10.26   The Network consists of MS-225 Stacks in IDFs connected back to a 2 x MS-425-16 Stack via LACP - with one link on MS-425-1 and the second Link from the IDF Stack on MS-425-2   All of my switches have a static IP on a VLAN - Class C Subnet that is the LAN input on my firewall   The upgrade took place and I lost my MS-425s - they were stuck in an upgrade loop of death   If you connect to the MS-425 via the Web interface you can see the following   After the upgrade had failed - the MS-425s were in DHCP Mode on VLAN 1 - they had lost their static IP   So I set the static and the device connected to the Meraki cloud - you can see the progress - 33%, 66 % and then a reboot by the switch - during which you lose web connectivity on the management port   Once you regain connectivity, the static is gone and the unit is back on DHCP, VLAN 1 - rinse, repeat....   You are stuck in this death loop   I was able to fix one switch by adding a temp DHCP server on VLAN 1 and connecting a port on the MS-425 to VLAN 1 with a DHCP Server   But the other switch became a brick and even after a hardware reset and multiple reboots - it would not complete a code upgrade   I RMA'd the switch and downgraded back to 9.37   I had a similar issue at another site - spent 12 hours on phone with TAC - I was able to get one of the MS-425s back to 9.37 but the other was in the boot loop of death and I could not go forward or backward with the firmware upgrade   I left the switch at midnight in a defaulted state and plugged into the internet with DHCP on VLAN 1   At about 4 am I received an email that the switch had joined the cloud - a miracle....   When I looked at the switch log - it had rebooted about 8 times since midnight (power supply inserted message...) and it indeed had broken free from the reboot of death loop   Here's what I know - after spending a total of about 30 hours on the phone with TAC - they don't have a clue what the issue is   During the initial deploy, I added a static IP to the MS-425s, the MS-425s were able to join the cloud and upgrade to 9.37 - then I created the stack and added Layer-3 Interfaces and configured the interfaces and added LACP   If you attempt to upgrade a stack of MS-425 from 9.37 to 10.26 - the upgrade fails on the 425 Stack and they get stuck in the reboot of death loop   If you attempt to downgrade them back to 9.37 - good luck - I found that I had to remove the stack cables, hw default one switch, set a static and connect it back to cloud - after several repeats of this process a 425 switch may rejoin the cloud - but after each failed attempt you have to re-add the static IP and set the WAN VLAN   Eventually I was able to get some of the switches to break out of the reboot of death loop and return back to 9.37   Some of the switches could not be revived and were RMA'd   I have an open case on this - but it does not look promising - "We have not been able to duplicate this in the lab...." - So resolution is not on the horizon   TAC has asked me to go on site again and try to do another upgrade - but these are production networks and who has another 12 hours to spend on a fools errand...   So at this time I have 2 networks that are running 9.37 - they have LACP and STP issues that supposedly fixed in 10.26 - but I seem to have no way of getting there   I have asked TAC to send me 2 - 425s that are already at 10.26 and I will attempt to insert them into the network   As of now - it looks like if you have 425s - you might want to try and upgrade them to 10.26 before deployment and then try and stack them - It appears that after they are stacked, they are doomed to the reboot of death loop         ... View more

LACP causes spanning tree issues with ver 10.26 ... View more

We tried to upgrade two sites from 9.37 to 10.26    LACP does not seem to work - creates spanning tree loops   Have not tried 10.29     ... View more