I didn't physically pull the cable out. What I did was shut down both ports, removed one port from the port-channel via "No channel-group" and then no shut that interface. The port then came up and I did learn some mac addresses from the other side, but Mgmt to the Meraki switch never restored.  The core logs clearly indicated they were not receiving LACP. *Aug 27 19:32:19.093: %ETC-5-L3DONTBNDL2: Twe2/0/34 suspended: LACP currently not enabled on the remote port. *Aug 27 19:32:19.974: %ETC-5-L3DONTBNDL2: Twe1/0/34 suspended: LACP currently not enabled on the remote port. Meraki support has come back with there is a bug in version 16.7+ with meraki switches having issues sending LACP when a port comes back up. They recommended we upgrade to 17.1.1.  --Fixed an issue that caused unexpected LACP discarding states after aggregate links were restarted or reconnected   ... View more

During the last event I pulled one of the interfaces out of the port-channel and it stayed up, however it did not restore connectivity.  ... View more

We have had this issues across multiple code versions. We are on 16.8 today. Yes, down/up the ports, but the cisco core says the meraki switch isn't sending LACP and suspends them again. Once the meraki switch is rebooted it comes right up. ... View more