We have been tasked with measuring and reporting the amount of time it takes remote workers, who access networks with a cisco VPN client, to open the client and then establish full access to their remote workspaces. Are there any logs on the client machine that this information can be derived from?
I am not clear whether your question is directed toward the traditional Cisco IPSec VPN client or toward the new Cisco AnyConnect VPN client. At a high level I believe that the answer for both clients is yes there are logs and you should be able to derive the information you need from them. The details of what each client logs and of how you access the logs is different.
There are a couple of ways to access the logs of the tradition Cisco IPSec VPN client. Probably the easiest is on the main page of the VPN client there is a tab identified as log, and if you click that tab it will display the contents of the logs. Or you can use ctrl + L to display the log entries. Or on the main page in the tool bar is an option for log. If you click that it will open a drop down menu with an option for log window, and this will display the log contents.
The logs display messages in 10 categories and each category has a severity level that can be selected, ranging from disabled to low to medium to high. You may need to do some adjusting to get log messages that will satisfy your requirements. I would assume that log messages from ISAKMP would be a good place to identify the beginning of the connection process. I am not sure whether messages from the Connection Manager or from PPP (or perhaps some other category) would be the best to indicate completion of the connection process.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...