MX Failover event detected

[This2shallpass]

Hi Community ,

I have been experiencing VRRP failover events between our Primary and Spare MXs since upgrading to Firmware MX 19.1.7.2. The failover and failback occur within a few seconds. Prior to this upgrade, when we were operating on MX 18.211.2 everything was functioning without any issues. 

It seems that the latest firmware upgrade may have introduced a problem. TAC is currently investigating this matter, but I wanted to reach out to see if anyone else has encountered similar issues with this firmware code. 

Any insights or experiences shared would be greatly appreciated.

Thanks!

[Mloraditch]

I have not seen this, but the issues with 19.1.7 seem to have been getting heavily documented on here as of late.

The more data support gets the better chance of finding and fixing the bugs so I do appreciate you working with them rather than just rolling back.

[alemabrahao]

I'm not surprised.

[PhilipDAth]

I had a customer's MX95s badly affected (had to roll back).  The failover were being caused by reboots.  I have a suspicion MX85s might be affected as well.

I have not seen issues on the other platforms.

[IvanJukic]

Hi @This2shallpass,

I have seen these similar types of situations before. Where the upgrade is the catalyst but not necessary the root cause. In these scenarios; which I've worked on. I've found that Spanning-Tree is shutting links. So the Primary MX reboots, this causes a TCN message sent and Spanning-Tree recalculates the Root Path. In those situations, it is usually the downlink switch ports or MX Lan ports missing a VLAN. I'd suggest double checking in case it may not been a firmware issue. Refer to the section "Requirements and Best Practices" for details.

https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair#Require...

[AndyHaines]

a pair of MX450 that i manage have the same issue.  i have a ticket in.