Cisco Cisco AnyConnect Secure Mobility Client v2.x Troubleshooting Guide
debug messages.
Configure NAM Packet Capture
When Extended Logging is enabled, NAM also keeps a packet capture buffer going. The buffer is
by default limited to about 1MB. If packet capture is needed, it may be beneficial to
increase buffer size so it captures more activities. To extend the buffer, a XML setting file must be
manually modified.
by default limited to about 1MB. If packet capture is needed, it may be beneficial to
increase buffer size so it captures more activities. To extend the buffer, a XML setting file must be
manually modified.
Step 1. On the Windows PC, browse to:
C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Network Access
Manager\system\
C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Network Access
Manager\system\
Step 2. Open file internalConfiguration.xml.
Step 3. Locate XML tag <packetCaptureFileSize>1</packetCaptureFileSize> and adjust the value
to 10 for a 10MB buffer size, and so on.
to 10 for a 10MB buffer size, and so on.
Step 4. Reboot the client PC for the change to take effect.
Log Collection
NAM log collection is done via Diagnostic And Reporting Tool (DART), which is a module of
AnyConnect suite. In the installer, select a module and use AnnyConnect full installation ISO to
install. The Cisco Media Services Interface (MSI) installer can also be found inside the ISO.
AnyConnect suite. In the installer, select a module and use AnnyConnect full installation ISO to
install. The Cisco Media Services Interface (MSI) installer can also be found inside the ISO.
After you enable Extended Logging and perform a test, simply run DART and go through the
dialogue, the log bundle is located by default on the Windows Desktop.
dialogue, the log bundle is located by default on the Windows Desktop.
In addition to DART bundle, the NAM message log is also helpful to locate the relevant data in the
NAM log. In order to find the NAM message log, navigate to AnyConnect settings window >
Network Access Manager > Message History. The message log contains timestamp of each
network connection event, which can be used to find the logs relevant to the event.
NAM log. In order to find the NAM message log, navigate to AnyConnect settings window >
Network Access Manager > Message History. The message log contains timestamp of each
network connection event, which can be used to find the logs relevant to the event.
Reading NAM Logs
NAM logs, especially after you enable Extended Logging, contains a large amount of data, most of
which are irrelevant and can be ignored. This section lists out the debug lines to demonstrate each
step NAM takes to establish a network connection. When you work through a log, these key
phrases may be helpful to locate part of the log relevant to the issue.
which are irrelevant and can be ignored. This section lists out the debug lines to demonstrate each
step NAM takes to establish a network connection. When you work through a log, these key
phrases may be helpful to locate part of the log relevant to the issue.
Log Summary of a Network Connection without 802.1x Enabled
Authentication
Authentication
Explanation: This indicates that the user has selected a network from NAM module, and NAM has
received a userEvent of START.
received a userEvent of START.