Connectivity problems after upgrading MX105 cluster

[rfranco]

Hello everybody,

Last year, we encountered an issue immediately after upgrading an MX105 cluster (warm spare) from version 18.107.2 to 18.208.
The connected switch ports on the Cisco ACI leaf changed to err-disable status after some flapping. It was necessary to shut/no shut the switch ports to restore connectivity. The issue occurred twice within the following 48 hours after the upgrade, and neither Cisco support nor Meraki support was able to provide a full diagnosis.

We are now facing a similar upgrade and are unsure whether we will experience the same behavior.

Has anyone experienced a similar issue?

Best regards,

[GreenMan]

Can you document how the MXs are interconnected with the switching (and each other, if applicable) on the LAN side?
This may or may not apply here, but I see lots of people trying to use their warm spare pair of MXs as a LAN core, when that's not best use of them.  Instead; aggregate LAN uplinks in the switching then use as simplified a set of trunk uplinks from switch aggregation layer into the MX pair as per the recommended topologies section here:   https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair#Recomme...

[rfranco]

Thanks for your post @GreenMan

Actually this is a VPN Hub and it only has (each MX) one SFP+ port connected the the Cisco ACI infraestructure

Regards

[PhilipDAth]

What was the err-disable error code given?

ps. Have you configured errdisable recovery?

[Inderdeep]

People shared issue related to this version , may be support call if something triggered

https://community.meraki.com/t5/Security-SD-WAN/MX-18-208-release-being-pushed-Performance-improveme...