MX 105 to 18.211.2 to resolve 1 problem, now many more

mikecarter
Here to help

MX 105 to 18.211.2 to resolve 1 problem, now many more

Here is the situation, we upgraded our HA pair of MX105 to 18.211.2 to resolve the issue where the Non-Meraki VPN service to fail to properly establish IKEv2 tunnels when the MX appliance was acting as the IKEv2 responder. We performed this upgrade on July 12. Today, July 22, performance at that site was down to a crawl. The only way we could get usable performance back at the site was to disable one of our Non-Meraki tunnels and remove the secondary MX. Both of these had to be done in order to restore performance. I've been on the phone with Meraki support all day and no solution has been presented. Has anybody seen anything similar? I need to take some sort of action here.

0 Replies 0
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels