Cisco Cisco AnyConnect Secure Mobility Client v2.x Troubleshooting Guide
Explanation: Both Access State Machine and Network State Machine have been started.
Explanation: The IPv4 instance got cancelled in order to reset the states.
Explanation: The adapter with ID 484E4FEF-392C-436F-97F0-CD7206CD7D48 was selected to
connect to network test123, which is the name of the network connection configured in NAM.
connect to network test123, which is the name of the network connection configured in NAM.
Explanation: NAM has successfully engaged the adapter for this network. Now NAM tries to
associate (connect) to this network (which happens to be wireless):
associate (connect) to this network (which happens to be wireless):
Explanation: openNoEncryption indicates that the network is configured as open. On the
Wireless Lan Controller it uses MAC Authentication Bypass (MAB) to authenticate.
Wireless Lan Controller it uses MAC Authentication Bypass (MAB) to authenticate.
Explanation: cs can be seen a lot in NAM logs. These are irrelevant logs and should be ignored.
Explanation: These are Simple Object Access Protocol (SOAP) messages used to tell
AnyConnect GUI to display the connection status message such as Associating in this case.
Any error messages displayed on NAM window can be found in one of the SOAP messages in the
log which can be used to locate the issue easily.
AnyConnect GUI to display the connection status message such as Associating in this case.
Any error messages displayed on NAM window can be found in one of the SOAP messages in the
log which can be used to locate the issue easily.
Explanation: NAM receives an AUTH_SUCCESS event, which misleads because there is no
authentication which currently happened. You are get this event simply because you connect to an
open network, so by default authentication is successful.
authentication which currently happened. You are get this event simply because you connect to an
open network, so by default authentication is successful.
Explanation: Association to Service Set Identifier (SSID) is successful, time to handle
authentication.
authentication.
Explanation: Since this is an open network, it is by default authenticated. At this point, NAM is
connected to the network and now starts DHCP process:
connected to the network and now starts DHCP process:
Explanation: NAM successfully acquires an IP address.
Explanation: Once an IP address is received NAM will send ARP (AGet-Connectivity). Once the
ARP response is received the client is connected.
ARP response is received the client is connected.
Log Summary of a Network Connection using 802.1x and PEAP over Wired
Network
Network
Explanation: NAM started to connect to network WiredPEAP.
Explanation: NAM matched an adapter to this network.
Explanation: NAM started connecting to this wired network.
Explanation: Client sends EAPOL_START.
Explanation: Client receives Identity Request from the switch, it now looks for a credential to send
back.
back.
Explanation: By default, Anyconnect sends anonymous as unprotected identity (outter identity),
so here it tries anonymous and see if the server is OK with it. The fact that the identity is
anonymous as opposed to host/anonymous indicates that it's a user authentication, rather than
so here it tries anonymous and see if the server is OK with it. The fact that the identity is
anonymous as opposed to host/anonymous indicates that it's a user authentication, rather than