Something strange would happen when I connected to a Firepower 2130 running Firepower Threat Defense with Cisco AnyConnect.
Basically, the AnyConnect client would contact the VPN gateway just fine, prompt for user credentials, authenticate and connect but then literally after about 3 seconds of being connected it would immediately drop and attempt to reconnect again. This would typically happen about two or three times before the VPN client would make the connection and stay connected and stable. I actually never had to re-enter my user credentials during this connect / reconnect process.
While there are some topics discussed that I found by doing a couple of searches, none of them explicitly talked about Firepower 2100 series appliances, Firepower Threat Defense, or Firepower Management Center (FMC) in particular. Most articles or forum discussions were centered around ASA Firewall topics, but I think the concept behind the fix is the same.
A little bit of background regarding what device(s) are at play here:
- Cisco Firepower Management Center 184.108.40.206-51 running on VMware
- Cisco Firepower 2130 Next Generation Firewall on Firepower Threat Defense 220.127.116.11-51
- Cisco AnyConnect Secure Mobility Client 4.5.05030 on Windows 10 64-bit
Let’s take a look at some logs to see the problem in action.
Some information seemed to point to DTLS as being the problem and while the link here suggests this on ASA releases 9.0 and 9.1, the topic of MTU size caught my eye. Some other posts I read mentioned MTU as well, so I figured I would change the default MTU size from 1406 to something different and see if this helped, and it did.
Let’s see the problem first hand. Here are the message history logs from within Cisco AnyConnect:
What is the workaround to solve this “reconnecting” behavior?
Let’s go into FMC and change the MTU settings for the Group Policy associated with your Remote Access VPN setup.
Navigate to Objects tab > VPN > Group Policy > NAME OF YOUR RA VPN GROUP POLICY > Click on the pencil “Edit” icon.
Once you are on the Edit Group Policy screen, go to the “AnyConnect” Tab > SSL Settings > Change MTU Size to 1300 Bytes.
Don’t forget to click on Save at the bottom and then deploy the changes to the firewall that AnyConnect clients are connecting to. Grab some coffee, and check the latest weather update (since FMC takes a while to push policy… ugh). Once it is done, let’s connect through VPN and take a look at those AnyConnect message history entries again.
The logs show that the VPN connection was made, and then no reconnects were tried after the successful connection. I let the client stay connected for a few minutes just to make sure everything was OK, then manually disconnected at 11:27:06.
While leaving the MTU setting at 1300 bytes may not be possible for whatever environment you are working in, for now this seems to be working just fine. At any given time we have only about 50 concurrent AnyConnect sessions, so it’s a fairly low volume of remote workers that are being supported. If any long-term issues arise from this setup, i’ll be sure to update this post.
Thanks for reading, good luck!