Hello everyone. I had a interesting event while managing a client's network yesterday. And by "interesting" I mean unexpected and very frustrating. I can't find any reference to it through googling and I'm wondering if this is isolated or a known/expected behavior. I have a client that has two locations, each running with a single MX84 with redundant WAN connections. They recently ordered two new MX84s to act as warm spares. So while these devices were still in their box I added these devices to their inventory, then to their respective networks as a warm spare, and that's where the fun began. The moment I added this (still boxed) device all network traffic reset. Logs showed DHCP leases dropped, VPN tunnels reset, WAN connections reset, the whole package. It only lasted for 20-30 seconds, but it took place at both locations separately, at separate times, the moment it was added. Then the client said they wanted to use two different serial numbers instead, and the same thing happened when I removed the devices. Maybe I missed it, but I didn't see anything about this in the HA Pair guide MX Warm Spare - High Availability Pair - Cisco Meraki Also, it just doesn't make sense to me that the device would behave in this way when presented with a spare configuration of a device that isn't even connected. No warnings, nothing. Has anyone else experienced this?
... View more
