I'm using 10m 10G Twinax (Cisco SFP-10G-AOC10M) between a MS350 Stack and a C9500 stack.   ... 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

Hey all,   We have done a number of improvements on quite some stuff in the latest release (including stacking and UDLD).    Can I recommend that you move up to 10.30 (you should be able to schedule your upgrades if they haven't been scheduled automatically already) and check if you are seeing the same behaviour?   Thanks!   Giacomo ... 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

Another concern, from my meraki switch going to firewall and router can we use lacp for redundancy as well. Coz currently I only have one line going thru firewall and another one going thru router. ... View more