05-12-2010 10:25 AM - edited 02-21-2020 04:38 PM
I've put the Anyconnect VPN client in place at my organization and for the most part, it's working well. However, our mainframe terminal application (Attachmate's Extra) will time out after 60 minutes of inactivity. This is without any idle timers set in the ASA interface. I thought it might be the TCP CONN value, but upping it to 2 hours instead of 60 minutes had no effect. Any ideas where I can start troubleshooting this?
Thanks,
Greg
11-28-2012 11:26 AM
Hello. I am experiencing the same issue. Did you ever figure how to fix the problem?
Thanks
11-28-2012 11:34 AM
Hi Greg,
Please do the following:
logging buffer-size 1048576
logging buffered debugging
logging enable
Then connect the client, test the application behavior and once it fails do "show log | inc AnyConnect_IP" and "show log | inc server_IP".
HTH.
Portu.
Please rate any helpful posts
11-28-2012 01:05 PM
Greg,
Does it timeout if the application is in use ? Or is it only when it's idle ? Is it anyconnnect that's disconnecting or just the application ?
Capturing the log or a wire trace via a packet capture may show where or who is terminating the session but not why. Having an understanding of your mainframe and the application requirements will help understand the interaction and the environment.
What further details around the application and the client can you provide ?
Best Regards
Julian
Sent from Cisco Technical Support iPad App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide