cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
880
Views
2
Helpful
7
Replies

ASA Remote Access VPN, management tunnel not working

FredrikW73
Level 1
Level 1

We upgraded our VPN ASA (FPR-2130) to 9.16(4)19 software recently. 

After this remote access VPN units (Windows10 PCs with AnyConnect 4.10.05085) fail to establish management tunnel. 

Management tunnel setup worked on ASA 9.14(4)17. 

Anyone else with this experience? Is this a known bug?

1 Accepted Solution

Accepted Solutions

FredrikW73
Level 1
Level 1

It turns out that the ASA software has changed the requirements for the algorithms used by certificates. 

Since the algorithms used by our machine certificates do not fullfill these new requiremets, setup of management tunnels fail. 

There is a command to bypass the requirements and we have used that command as a workaround successfully.

View solution in original post

7 Replies 7

FredrikW73
Level 1
Level 1

Why is this post not showing when I browse through in the Cisco Community/Technology and Support/Security/VPN section???

EDIT, now it finally shows...

you connect anyconnect to outside of asa, outside is VPN in routing table not in management-only routing table, 
cisco recommend make the direct and vpn in same routing table 
so here what you need is 
telnet 0.0.0.0 0.0.0.0 inside <- then try telnet to asa via anyconnect 

The problem is not related to management access. We have OOB management access.

The problem is the following:
Normally, since we have "Always On" set, the PCs of Remote Access VPN users will connect by setting up a management tunnel already before the user logs in to the PC. This enable us to connect to the PCs and manage them even when the users are logged out. When the user logs in a user tunnel is established and the management tunnel is released.

This have stopped working after update to 9.16(4)19 software.

Management tunnels fail to establish.

Background (From the ASA Admin Guide):

"A management VPN tunnel ensures connectivity to the corporate network whenever the client system is powered up, not just when a VPN connection is established by the end user. You can perform patch management on out-of-the-office endpoints, especially devices that are infrequently connected by the user, via VPN, to the office network. Endpoint OS login scripts that require corporate network connectivity also benefit from this feature.

AnyConnect Management Tunnel allows administrators to have AnyConnect connected without user intervention prior to when the user logs in. AnyConnect Management tunnel can work in conjunction with Trusted Network Detection and therefore is triggered only when the endpoint is off-premise and disconnected from a User-initiated VPN. AnyConnect Management tunnel is transparent to the end user and disconnects automatically when the user initiates VPN."

FredrikW73
Level 1
Level 1

It turns out that the ASA software has changed the requirements for the algorithms used by certificates. 

Since the algorithms used by our machine certificates do not fullfill these new requiremets, setup of management tunnels fail. 

There is a command to bypass the requirements and we have used that command as a workaround successfully.

what is the command to bypass?

crypto ca permit-weak-crypto

yes we applied and fixed the issue .