close

Вход

Забыли?

вход по аккаунту

?

Cisco TrustSec How-To Guide: Failed Authentications and

код для вставки
Cisco TrustSec How-To Guide:
Failed Authentications and Authorizations
For Comments, please email: howtoguides@external.cisco.com
Current Document Version: 3.0
August 27, 2012
Table of Contents
Table of Contents ............................................................................................................................ 1
Introduction .................................................................................................................................... 3
What Is the Cisco TrustSec System? ......................................................................................................................................................................... 3
About the TrustSec How-To Guides .......................................................................................................................................................................... 3
What does it mean to be �TrustSec Certified’? ................................................................................................................................................... 4
Troubleshooting Failed Authentications and Authorizations ......................................................... 5
Overview ............................................................................................................................................................................................................................... 5
TrustSec Components .................................................................................................................................................................................................. 10
5411 No response received during 120 seconds on last EAP message sent to the client ................................................................ 22
12520 EAP-TLS failed SSL/TLS handshake because the client rejected the ISE local-certificate .............................................. 22
22044 Identity policy result is configured for certificate based authentication methods but received password based .22
22045 Identity policy result is configured for password based authentication methods but received certificate based
authentication request ............................................................................................................................................................................................. 22
22056 Subject not found in the applicable identity store(s) ..................................................................................................................... 22
24408 User authentication against Active Directory failed since user has entered the wrong password .............................. 23
15039 Rejected per authorization profile ......................................................................................................................................................... 23
22040 Wrong password or invalid shared secret ..........................................................................................................................................23
11036 The Message-Authenticator RADIUS attribute is invalid .............................................................................................................. 23
11007 Could not locate Network Device or AAA Client ............................................................................................................................... 23
5417 Dynamic Authorization failed ....................................................................................................................................................................23
Appendix A: References ............................................................................................................... 24
Cisco TrustSec System: ................................................................................................................................................................................................ 24
Device Configuration Guides: ................................................................................................................................................................................... 24
HowTo-81-Troubleshooting_Failed_AuthC
2
Introduction
What Is the Cisco TrustSec System?
Cisco TrustSecВ®, a core component of the Cisco SecureX Architectureв„ў, is an intelligent access control solution. TrustSec
mitigates security risks by providing comprehensive visibility into who and what is connecting across the entire network
infrastructure, and exceptional control over what and where they can go.
TrustSec builds on your existing identity-aware access layer infrastructure (switches, wireless controllers, and so on). The
solution and all the components within the solution are thoroughly vetted and rigorously tested as an integrated system.
In addition to combining standards-based identity and enforcement models, such as IEEE 802.1X and VLAN control, the
TrustSec system it also includes advanced identity and enforcement capabilities such as flexible authentication,
Downloadable Access Control Lists (dACLs), Security Group Tagging (SGT), device profiling, posture assessments, and
more.
Figure 1: TrustSec Architecture Overview
RADIUS
Guest Services
Posture
Profiler
Ingress Enforcement
Wireless
user
SXP
Wired
user
y
rit ag
cu T
Se oup
Gr
Campus
Network
MACsec
Ingress Enforcement
S
Gr ec
ou uri
p ty
Ta
g
Data Center
Egress Enforcement
About the TrustSec How-To Guides
The TrustSec team is producing this series of How-To documents to describe best practices for TrustSec deployments. The
documents in the series build on one another and guide the reader through a successful implementation of the TrustSec
system. You can use these documents to follow the prescribed path to deploy the entire system, or simply pick the single
use-case that meets your specific need.
Each guide is this series comes with a subway-style “You Are Here” map to help you identify the stage the document
addresses and pinpoint where you are in the TrustSec deployment process (Figure 2).
Figure 2: How-To Guide Navigation Map
HowTo-81-Troubleshooting_Failed_AuthC
3
What does it mean to be �TrustSec Certified’?
Each TrustSec version number (for example, TrustSec Version 2.0, Version 2.1, and so on) is a certified design or
architecture. All the technology making up the architecture has undergone thorough architectural design development and
lab testing. For a How-To Guide to be marked “TrustSec certified,” all the elements discussed in the document must meet
the following criteria:
п‚·
п‚·
п‚·
Products incorporated in the design must be generally available.
Deployment, operation, and management of components within the system must exhibit repeatable processes.
All configurations and products used in the design must have been fully tested as an integrated solution.
Many features may exist that could benefit your deployment, but if they were not part of the tested solution, they will not be
marked as “TrustSec certified”. The TrustSec team strives to provide regular updates to these documents that will include
new features as they become available, and are integrated into the TrustSec test plans, pilot deployments, and system
revisions. (i.e., TrustSec 2.2 certification).
Additionally, many features and scenarios have been tested, but are not considered a best practice, and therefore are not
included in these documents. As an example, certain IEEE 802.1X timers and local web authentication features are not
included.
Note: Within this document, we describe the recommended method of deployment, and a few different options depending on the level of
security needed in your environment. These methods are examples and step-by-step instructions for TrustSec deployment as prescribed
by Cisco best practices to help ensure a successful project deployment.
HowTo-81-Troubleshooting_Failed_AuthC
4
Troubleshooting Failed Authentications and
Authorizations
Overview
Cisco TrustSec relies on multiple components. When authentication fails in the TrustSec environment, it may be challenging
to find out root cause of the issue because you may need to look at different components. TrustSec 2.1 components include:
п‚·
Cisco ISE nodes
п‚·
Network access devices (NADs): Cisco CatalystВ® Switches, Cisco Wireless LAN Controllers (WLC), Cisco ASA
Adaptive Security Appliances
п‚·
Supplicants
п‚·
External identity stores
With recent enhancements, Cisco has put effort into providing a single point of view for troubleshooting by correlating
switch syslog events to internal ISE events, as well as by providing interfaces on the ISE to poll for different authenticationrelated information on demand. Other enhancements on the ISE include a configuration validator, a TCP dump utility, and
the ability to provide details about supplicant issues when the client is running Cisco AnyConnectВ® Network Access
Manager with a certificate-based EAP type.
High-level Troubleshooting Steps
Figure 3 shows a high-level view of the troubleshooting flow.
Figure 3 High-level Troubleshooting Steps
HowTo-81-Troubleshooting_Failed_AuthC
5
Procedure 1
Check ISE Authentication Log
Log in to the primary ISE Policy Administration Node (PAN).
Go to Operations пѓ Authentications.
(Optional) If the event is not present in the Live Authentications log, go to Operations пѓ Reports пѓ Catalog пѓ AAA
Protocol пѓ RADIUS Authentication.
Procedure 2
Check for Any Failed Authentication Attempts in the Log
If the MAC address or username is known, use filters to view the events only from the specific endpoint.
Note: Even for 802.1X authentications, it is helpful to filter with MAC address instead because: depending on where in the process the failure
occurred, the endpoint user or computer name may not be known to ISE.
The Live Authentications log (Figure 4) shows events up to past 24 hours, so make sure to look at the latest events.
Successful events have status of
clearly identify the status.
with green background. A failed event will have
with red background to
Note the network device and device port before proceeding. Figure 4 Live Authentications Log: Failed
Authentication Events
Figure 4 Live Authentications
Procedure 3
Check the Log for More Information
In the Live Authentications log, check Failure Reason column.
Click the
button (Details button) for more information.
Click the Authentication failed message for additional detail (Figure 5).
HowTo-81-Troubleshooting_Failed_AuthC
6
Figure 5 Failed Authentication Detail
Perform the remediation action per the Resolution Steps (Figure 6).
Remediation is described in more detail later in this document.
Figure 6 Authentication Failure Code Lookup
Procedure 4
Check for Passed Authentication Entry or the MAC Address in the Log
Check to see if latest event for that endpoint was a passed authentication.
Since even after the passed authentication, the endpoint is still having issues, there may be configuration mismatch
between the ISE and the network access device (NAD).
If there are no events for that endpoint, follow the flow chart shown in Figure 3 for further troubleshooting on the
NAD and the endpoint.
Procedure 5
Check the NAD Interface Status or the ISE Detailed Reports
If this is a Cisco Catalyst switch, log in using Telnet or Secure Shell (SSH) and run following command in enabled
mode:
show authentication sessions interface Gig x/y/z
(Optional) If the switch is configured for ISE to poll information via SNMP, open detailed reports by selecting
Operations пѓ Authentications. Then click on the
HowTo-81-Troubleshooting_Failed_AuthC
button. Figure 7 shows the results:
7
Figure 7 Authentication Detail: Interface Status
(Optional) In Detailed Reports, click the interface name (for example, Gigabit Ethernet x/y/z).
This will do a SNMP poll that is the equivalent of the show authentication command in step 1 without your
having to log in to the individual switch.
Procedure 6
Validate the WLC or Switch Configuration
Check that the Cisco Wireless LAN Controller (WLC) configuration or the switch OS platform and/or version is
supported by the TrustSec version you are implementing.
For the NAD to be able to authorize, it needs to have following entry in the configuration:
aaa authorization network radius
For the dynamic VLAN (dVLAN), run the following from exec mode to check that the WLC or the switch VLAN
database includes the VLAN that the ISE is trying to assign:
show vlan
For dACL, validate that the ISE ACL syntax is correct by going to Policy пѓ Policy Elements пѓ Results пѓ Authorization пѓ Downloadable ACLs.
For Catalyst switches, you can verify the configuration using the ISE Evaluate Configuration Validator tool. Go to
Operations пѓ Troubleshooting пѓ Diagnostic Tools пѓ General Tools (Figure 8).
HowTo-81-Troubleshooting_Failed_AuthC
8
Figure 8 Evaluate Configuration Validator
Procedure 7
Validate Endpoint-to-NAD Communication
For Catalyst switches, enable 802.1X debugging by running the following in exec mode:
debug dot1x
Validate that client is sending EAP over LAN (EAPoL) Start message by checking the debug log.
For devices using MAC Authentication Bypass (MAB), validate that the device is sending traffic.
If the interface is configured with the settings for order and timers that are recommended for Cisco TrustSec 2.1, it will take
30 seconds before the switch will accept and use the traffic from the endpoint to send a MAB request. This is typically not an
issue for chatty devices, such as Windows PC devices; however, some printers may take a while to go through the MAB. If
you are experiencing long delays to successfully MAB a device, like a printer, consider running the interface-specific
command authentication control-direction in to allow traffic from the network to the endpoint prior to
authentication, which could accelerate the MAB process.
Procedure 8
Check the ACL Applied to the VLAN and to the Session
For the dVLAN, validate that the ACL applied to the VLAN is not too restrictive. You can do this by looking at the
VLAN interface ACL or manually assigning an interface to a non-802.1X-enabled interface and validating the endpoint
experience.
For the dACL, validate that the ACL applied to the session is not too restrictive. A few useful commands include the
following:
show
show
show
show
authentication sessions interface <int_name>
ip access-list interface <int_name>
running-config interface <int_name>
access-list <int_name>
Procedure 9
Validate the RADIUS Configuration on the NAD
For Catalyst switches, run the Evaluate Configuration Validator (as described in Procedure 6) to validate the
RADIUS configuration.
From the NAD, try to ping the ISE Policy Services Nodes (PSN).
If there are any filtering devices between the NAD and the ISE PSN, verify that the device is allowing RADIUS
authentication, authorization, and accounting (UDP 1645/1656 or 1812/1813).
HowTo-81-Troubleshooting_Failed_AuthC
9
You can use the Cisco IOSВ® Software test feature to run a test authentication. Enter the following command from
exec mode:
test aaa group radius {test_user} {test_password} new-code
Procedure 10
Validate That the Endpoint Has Correct IP Address
Next, we need to verify that the supplicant is configured properly and running. First we’ll validate that the endpoint
has the correct IP address.
For Windows devices, run the following from the command prompt:
ipconfig /all
For Mac OS X and Linux devices, run following from the command prompt:
ifconfig
For clientless devices, please refer to the device user guide to find out the IP address.
Procedure 11
Validate ISE Endpoint Group and AuthZ Policy
If troubleshooting a MAB authentication, validate that the endpoint MAC address is in correct endpoint group by
going to Administration пѓ Identity Management пѓ Endpoints.
The detailed endpoint screen will show the current endpoint group in the Identity Group assignment. If the
assignment is incorrect, update the group with correct one.
Validate the authorization rule by going to Policy пѓ Authorization.
TrustSec Components
Supplicant
As discussed earlier, the ISE Policy Administration Node (PAN) should be the first stop when troubleshooting
authentication failures. Some failures will require additional diagnostic work at the NAD level. In most cases, the logs and
debugs from the ISE and the NAD should be enough to determine the root cause of the problem.
The diagnostic work that can be performed on a supplicant is largely dependent on the troubleshooting tools that a
particular supplicant provides. The native Windows supplicant has almost no debugging tools. Cisco AnyConnect Network
Access Manager has a diagnostic and reporting tool (DART) that can be deployed to clients and used to generate a detailed
report file. However, the report file is primarily for use by Cisco support staff and not generally recommended for the end
user.
Sniffer traces provide vital troubleshooting information, but they are also of limited use on the end client. In general, using
the Cisco Switched Port Analyzer (SPAN) to sniff the traffic at the switch is a more reliable and effective way to gather
EAP packet traces.
Some of the common supplicant failures arise in situations where the client sends an EAPoL Start request, but fails to
respond to an Identity Request message from the switch. Usually this happens because the supplicant is unable to find valid
credentials. When the client “goes silent,” there is no way for the switch or Cisco ISE to understand the failure.
Unlike Windows native supplicants or other supplicants available on other operating systems, Cisco AnyConnect Network
Access Manager includes an enhanced feature for notifying the ISE of the failure reason. As an example, take the situation
in which the client is misconfigured and does not trust the ISE certificate in an EAP Transport Layer Security (EAP-TLS)
or Protected EAP (PEAP) authentication (Figure 9).
HowTo-81-Troubleshooting_Failed_AuthC
10
Figure 9 Failed Authentication Report: Native Supplicants
In Figure 9, the Windows native supplicant was used on the PC. There are no details on the event other than Failure
Reason: 5411 No response received during 120 seconds on last EAP message sent to the
client. At this point, the administrator will have to log in to the affected endpoint to troubleshoot the issue.
Figure 10 shows an example in which the PC is running Cisco AnyConnect Network Access Manager. The Failure Reason
clearly indicates what the issue is on the supplicant settings.
Figure 10 Failed Authentication Report: Cisco AnyConnect NAM
HowTo-81-Troubleshooting_Failed_AuthC
11
Network Access Devices (NADs)
Most of the information needed to troubleshoot Cisco TrustSec authentication issues can be gathered from the ISE itself. In
some situations, however, the ISE cannot provide sufficient information to troubleshoot a failed authentication. It is
therefore necessary to examine the troubleshooting capabilities of the NAD.
Useful Cisco IOS show Commands
One of the most useful show commands on the Cisco Catalyst switch is show authentication sessions
interface. The command output shows the current authentication status of the specified port. Other useful commands
include show dot1x interface and show running-config interface.
Switch#show authentication sessions interface fastEthernet 0/1
Interface: FastEthernet0/1
MAC Address: 0016.d42e.e8ba
IP Address: 192.168.1.78
User-Name: winxp.example.com
Status: Authz Success
Domain: DATA
Security Policy: Should Secure
Security Status: Unsecure
Oper host mode: multi-domain
Oper control dir: both
Authorized By: Authentication Server
Vlan Policy: 100
Session timeout: N/A
Idle timeout: N/A
Common Session ID: C0A8013C000006679C3F253D
Acct Session ID: 0x00000C51
Handle: 0x68000667
Runnable methods list:
Method
State
dot1x
Authc Success
mab
Not run
Switch#
Switch#
Switch#show dot1x interface fastEthernet 0/1
Dot1x Info for FastEthernet0/1
----------------------------------PAE
= AUTHENTICATOR
PortControl
= AUTO
ControlDirection
= Both
HostMode
= MULTI_DOMAIN
QuietPeriod
= 60
ServerTimeout
= 0
SuppTimeout
= 30
ReAuthMax
= 2
MaxReq
= 2
TxPeriod
= 10
Switch#
Switch#
Switch#show running-config interface fastEthernet 0/1
Building configuration...
HowTo-81-Troubleshooting_Failed_AuthC
12
Current configuration : 599 bytes
!
interface FastEthernet0/1
description 802.1x Enabled
switchport access vlan 2
switchport mode access
switchport voice vlan 110
authentication event fail action next-method
authentication event no-response action authorize vlan 100
authentication event server alive action reinitialize
authentication host-mode multi-domain
authentication port-control auto
authentication periodic
authentication timer reauthenticate server
authentication timer inactivity server
authentication violation restrict
mab
dot1x pae authenticator
dot1x timeout tx-period 10
spanning-tree portfast
end
Switch#
Switch#
SPAN
One of the most useful tools for debugging 802.1X failures on the authenticator is the Switched Port Analyzer (SPAN).
SPAN allows you to mirror all the EAP traffic sent and received on one port to a different port where it can be analyzed by
a sniffer. By sniffing the actual EAP packets that are exchanged between the authenticator and the client, you can diagnose
some failures that are not visible from the Cisco ISE.
To configure a Cisco Catalyst 3000 Series Switch to mirror all the traffic from one port (the source port) to another (the
destination port), use the following Cisco IOS commands in configuration mode:
(config)# monitor session 1 source interface Gigabit 0/1
(config)# monitor session 1 destination interface Gigabit 0/2 encapsulation replicate
To configure a Cisco Catalyst 4500 Series Switch to mirror all the traffic from one port (the source port) to another (the
destination port), use the following Cisco IOS commands in configuration mode:
(config)# monitor session 1 source interface Gigabit 1/1
(config)# monitor session 1 destination interface Gigabit 1/2
No special configuration options are required to use SPAN on Layer 2 frames on the Cisco Catalyst 4500 Series switch,
since the Cisco Catalyst 4500 monitors all Layer 2 frames with the default SPAN configuration shown above.
HowTo-81-Troubleshooting_Failed_AuthC
13
Communication with ISE PSN
There are three common reasons why the switch does not or cannot send RADIUS messages to the AAA server when a
client attempts to authenticate:
п‚·
Lack of proper network connectivity
п‚·
RADIUS configuration on the switch
п‚·
Lack of response from the client
To verify network connectivity, ping the AAA server from the switch. Here is an example ping command:
Switch#
Switch#ping 192.168.1.60
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.60, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Switch#
If the ping is not successful, or some packets are dropped, use standard routing and switching debugging techniques to
establish reliable connectivity between the switch and the AAA server.
If the ISE PSN is pingable, it can useful to use the test aaa diagnostic command in this situation. The following
example illustrates this command:
Switch#test aaa group radius testuser cisco123 new-code
User successfully authenticated
Switch#
The test aaa command causes the switch to send an Access Request to the AAA server for a PAP (clear-text)
authentication for (in this example) the user testuser with password cisco123. The switch will attempt to
authenticate to the server configured in the radius-server host command. Optionally, if you are using AAA groups instead
of the default RADIUS group, you can specify a specific RADIUS group to test a specific server configured as part of the
group.
If the result of the test aaa command is User successfully authenticated, as shown in the preceding code
snippet, it means that three things are true: the switch is properly configured to communicate with the AAA server (correct
shared key); the switch has network connectivity to the AAA server; and the username and password specified in the test
command are valid. The ISE Live Authentication event will show this authentication:
Switch#test aaa group radius testuser cisco123 new-code
User rejected
Switch#
If the result of the test aaa command is User authentication request was rejected by server, you
know that the switch configuration is working and network connectivity is validated, but the username and/or password
provided in the test command are not valid. This failed authentication will show up in the ISE Live Authentication event.
Another possibility is that the switch is not able to authenticate to the AAA server. Either the shared key does not match or
there is no network connectivity to the AAA server. This could be the reason that no RADIUS messages are received by the
AAA server. Revalidating the configuration and/or verifying network connectivity will allow the switch to communicate
with the AAA server during 802.1X authentications.
HowTo-81-Troubleshooting_Failed_AuthC
14
Policy Mismatch
If the ISE Live Authentications shows successful authentication for the endpoint, but the result of show
authentication sessions interface Gigabit x/y/z indicates that the port unauthorized, there may be
policy mismatch between the ISE policy and the switch. This means although the ISE was able to authenticate and
authorize the session, the attribute value pair (AVP) sent from the ISE to the NAD was invalid. Common reasons for this
are:
п‚·
The VLAN does not exist.
п‚·
There was an ACL syntax error.
п‚·
There was an AVP syntax error.
If the AAA server has attempted to assign a VLAN that is not defined on the switch, the switch will not be able to authorize
the port. In the following example, the AAA server tries to assign the VLAN named EMPLOYEE. The switch returns the
follow syslog message:
Switch#
Switch#
May 28 07:06:11.156 UTC: %AUTHMGR-5-START: Starting 'dot1x' for client (0016.d42e.e8ba)
on Interface Fa0/1 AuditSessionID C0A8013C0000066D9D16ABF7
May 28 07:06:11.592 UTC: %DOT1X-5-SUCCESS: Authentication successful for client
(0016.d42e.e8ba) on Interface Fa0/1 AuditSessionID
May 28 07:06:11.592 UTC: %AUTHMGR-7-RESULT: Authentication result 'success' from 'dot1x'
for client (0016.d42e.e8ba) on Interface Fa0/1 AuditSessionID C0A8013C0000066D9D16ABF7
May 28 07:06:11.592 UTC: %DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign nonexistent or shutdown VLAN EMPLOYEE to 802.1x port FastEthernet0/1 AuditSessionID
C0A8013C0000066D9D16ABF7
May 28 07:06:11.592 UTC: %AUTHMGR-5-FAIL: Authorization failed for client
(0016.d42e.e8ba) on Interface Fa0/1 AuditSessionID C0A8013C0000066D9D16ABF7
May 28 07:06:11.592 UTC: %EPM-6-POLICY_REQ: IP 0.0.0.0| MAC 0016.d42e.e8ba|
AuditSessionID C0A8013C0000066D9D16ABF7| AUTHTYPE DOT1X| EVENT APPLY
May 28 07:06:11.592 UTC: %EPM-6-IPEVENT: IP 0.0.0.0| MAC 0016.d42e.e8ba| AuditSessionID
C0A8013C0000066D9D16ABF7| AUTHTYPE DOT1X| EVENT IP-WAIT
May 28 07:06:11.592 UTC: %EPM-6-POLICY_REQ: IP 0.0.0.0| MAC 0016.d42e.e8ba|
AuditSessionID C0A8013C0000066D9D16ABF7| AUTHTYPE DOT1X| EVENT REMOVE
May 28 07:06:11.592 UTC: %DOT1X-5-RESULT_OVERRIDE: Authentication result overridden for
client (0016.d42e.e8ba) on Interface Fa0/1 AuditSessionID C0A8013C0000066D9D16ABF7
Switch#
Switch#
As you can see from the following output, the switch’s employee VLAN is named EMP, not EMPLOYEE:
Switch#sh vlan | i EMP
100 EMP
active
Fa0/15, Fa0/16, Fa0/17, Fa0/18, Fa0/19, Fa0/20, Fa0/21, Fa0/22,
Because the switch does not have an exact match for the VLAN name EMPLOYEE, it sends an EAP-Failure message to
the endpoint. To remedy this problem, either rename the VLAN on the switch or define the correct name in the ISE
authorization profile.
In the following example, the dACL uses a wrong syntax. ISE sent allow ip any any instead of permit ip any
any.
Switch#
May 28 07:11:59.395 UTC: %AUTHMGR-5-START: Starting 'dot1x' for client (0016.d42e.e8ba)
on Interface Fa0/1 AuditSessionID C0A8013C000006719D1BFAB1
May 28 07:11:59.815 UTC: %DOT1X-5-SUCCESS: Authentication successful for client
(0016.d42e.e8ba) on Interface Fa0/1 AuditSessionID
May 28 07:11:59.815 UTC: %AUTHMGR-7-RESULT: Authentication result 'success' from 'dot1x'
for client (0016.d42e.e8ba) on Interface Fa0/1 AuditSessionID C0A8013C000006719D1BFAB1
HowTo-81-Troubleshooting_Failed_AuthC
15
May 28 07:11:59.823 UTC: %EPM-6-POLICY_REQ: IP 0.0.0.0| MAC 0016.d42e.e8ba|
AuditSessionID C0A8013C000006719D1BFAB1| AUTHTYPE DOT1X| EVENT APPLY
May 28 07:11:59.823 UTC: %EPM-6-AUTH_ACL: POLICY Auth-Default-ACL| EVENT Auth-Default-ACL
Attached Successfully
May 28 07:11:59.823 UTC: %EPM-6-AAA: POLICY xACSACLx-IP-PERMIT_ALL_TRAFFIC-4fc368f7|
EVENT DOWNLOAD-REQUEST
May 28 07:11:59.840 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2, changed
state to up
May 28 07:11:59.890 UTC: %EPM-6-AAA: POLICY xACSACLx-IP-PERMIT_ALL_TRAFFIC-4fc368f7|
EVENT DOWNLOAD-FAIL
May 28 07:11:59.890 UTC: %EPM-4-POLICY_APP_FAILURE: IP 0.0.0.0| MAC 0016.d42e.e8ba|
AuditSessionID C0A8013C000006719D1BFAB1| AUTHTYPE DOT1X| POLICY_TYPE dACL| POLICY_NAME
xACSACLx-IP-PERMIT_ALL_TRAFFIC-4fc368f7| RESULT FAILURE| REASON AAA download failure
May 28 07:11:59.890 UTC: %EPM-6-IPEVENT: IP 0.0.0.0| MAC 0016.d42e.e8ba| AuditSessionID
C0A8013C000006719D1BFAB1| AUTHTYPE DOT1X| EVENT IP-WAIT
May 28 07:11:59.890 UTC: %AUTHMGR-5-FAIL: Authorization failed for client
(0016.d42e.e8ba) on Interface Fa0/1 AuditSessionID C0A8013C000006719D1BFAB1
May 28 07:11:59.890 UTC: %DOT1X-5-RESULT_OVERRIDE: Authentication result overridden for
client (0016.d42e.e8ba) on Interface Fa0/1 AuditSessionID C0A8013C000006719D1BFAB1
May 28 07:11:59.890 UTC: %EPM-6-POLICY_REQ: IP 0.0.0.0| MAC 0016.d42e.e8ba|
AuditSessionID C0A8013C000006719D1BFAB1| AUTHTYPE DOT1X| EVENT REMOVE
May 28 07:11:59.899 UTC: %EPM-6-AUTH_ACL: POLICY Auth-Default-ACL| EVENT DETACH-SUCCESS
May 28 07:11:59.899 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2, changed
state to down
May 28 07:12:00.846 UTC: %AUTHMGR-5-SUCCESS: Authorization succeeded for client
(0016.d42e.e8ba) on Interface Fa0/1 AuditSessionID C0A8013C000006719D1BFAB1
Switch#
Switch#
Because the switch was not able to process the dACL, it sends an EAP-Failure response to the endpoint. To remedy this
problem, correct the syntax error on the dACL on ISE, as follows:
Switch#show authentication sessions interface FastEthernet 0/1
Interface: FastEthernet0/1
MAC Address: 0016.d42e.e8ba
IP Address: 192.168.2.100
User-Name: winxp.example.com
Status: Authz Failed
Domain: DATA
Security Policy: Should Secure
Security Status: Unsecure
Oper host mode: multi-domain
Oper control dir: both
Authorized By: Authentication Server
Vlan Group: N/A
Session timeout: N/A
Idle timeout: N/A
Common Session ID: C0A8013C000006719D1BFAB1
Acct Session ID: 0x00000C5D
Handle: 0xB2000671
Runnable methods list:
Method
State
dot1x
Authc Success
mab
Not run
Switch#
HowTo-81-Troubleshooting_Failed_AuthC
16
Identity Services Engine (ISE)
Before looking at the symptoms and causes of specific failures, it is instructive to review what a successful authentication
looks like from the ISE perspective. This section will also serve to review the tools that can be used to troubleshoot
authentication failures.
Procedure 1
Live Authentications Log
The Live Authentications log in ISE lists all the authentications that have reached ISE. If there is no entry for the user in this
screen, the authentication request has not been received by ISE.
You can look at the Live Authentications log by logging in to ISE primary PAN and going to Operations пѓ Authentications. Doing so will bring up a screen similar to the one shown in Figure 11.
Note: The Live Authentications log screen is provided by Primary MnT node. The same information is also available on backup MnT node.
Access to the Live Authentications log is also available by logging in to the secondary PAN and also logging in directly to either MnT
node.
Figure 11 Live Authentications Log
The Live Authentications log has several important pieces of information that are critical to determining who is on the
network, when and where they connected, and how they were authenticated.
Note: Some of the columns listed described here are visible only by using the Add/Remove Columns feature. To make these columns visible,
right-click on the header row.
Time—Shows the time that the log was received by the collection agent. This column is required and cannot be deselected.
Status—Shows if the authentication was successful or failed. This column is required and cannot be deselected.
Details—Brings up a report when you click the magnifying glass icon, allowing you to drill down to view more detailed
information on the selected authentication scenario. This column is required and cannot be deselected.
Username—Shows the username that is associated with the authentication.
Endpoint ID—Shows the unique identifier for an endpoint, usually a MAC or IP address.
IP Address—Shows the IP address of the endpoint device.
Network Device—Shows the IP address of the network access device.
Device Port—Shows the port number at which the endpoint is connected.
Authorization Profiles—Shows an authorization profile that was used for authentication.
Identity Group—Shows the identity group that is assigned to the user or endpoint, for which the log was generated.
Posture Status—Shows the status of the posture validation and details on the authentication.
Event—Shows the event status.
Failure Reason—Shows a detailed reason for failure, if the authentication failed.
Optionally, you can choose to show the following categories:
HowTo-81-Troubleshooting_Failed_AuthC
17
Auth Method—Shows the authentication method that is used by the RADIUS protocol, such as Microsoft Challenge
Handshake Authentication Protocol version 2 (MSCHAPv2), IEE 802.1x, or dot1x, and so on.
Authentication Protocol—Shows the authentication protocol used, such as Protected Extensible Authentication Protocol
(PEAP), Extensible Authentication Protocol (EAP), and the like.
Security Group—Shows the group that is identified by the authentication log.
Server—Indicates the policy service from which the log was generated.
Session ID—Shows the session ID.
Procedure 2
Detailed Report
Figures 12 and 13 present a detailed authentication report showing a successful authentication of a machine using EAPTLS. In Figure 12, the Authentication Summary shows the information that was available when viewed in the Live
Authentications logs page. In Figure 13, the Related Events come from the syslog for the NAD that is relevant to this
session. This is automatically correlated and included in the detailed report when the NAD sends the event to ISE MnT
node.
Figure 12 RADIUS Authentication Detail 1
Figure 13 RADIUS Authentication Detail 2
To configure the switch to send the syslog to ISE, enter the following:
(config)# logging host {Primary_MnT} transport udp port 20514
(config)# logging host {Backup_MnT} transport udp port 20514
HowTo-81-Troubleshooting_Failed_AuthC
18
In Figure 14, the Authentication Details section shows other information produced during authentication. In Figure 15, the
Steps section shows the detailed process that the session went through within ISE.
Figure 14 RADIUS Authentication Detail 3
Figure 15 RADIUS Authentication Detail 4
Reports
If the event happened more than 24 hours ago, it’s a historical event can be viewed by going to Operations пѓ Reports пѓ Catalog пѓ AAA Protocol пѓ RADIUS Authentication.
Procedure 3
Configuration Validator
You can use the diagnostic tool to evaluate the configuration of a network device and identify any configuration problems.
The Expert Troubleshooter compares the configuration of the device with the standard configuration. Figure 16 shows the
Evaluate Configuration Validator options.
HowTo-81-Troubleshooting_Failed_AuthC
19
Figure 16 Evaluate Configuration Validator Options
Go to Operations пѓ Troubleshoot пѓ Diagnostic Tools пѓ Evaluate Configuration Validator.
Enter the Network Device IP address of the device whose configuration you want to evaluate, and specify other
options as necessary.
Select configuration options to compare against the recommended template. A green check mark means the option is
selected. Click the option again to deselect. Choose from the following:
Web Authentication—Select this check box to compare the Web Authentication configuration for the device with the
standard configuration.
Profiler Configuration—Select this check box to compare the Profiler configuration for the device with the standard
configuration.
CTS—Select this check box if you want to compare Security Group Access configuration for the device with the
standard configuration.
802.1X—Select this check box if you want to compare the 802.1X configuration for the device with the standard
configuration. Then choose one of the following options:
Open Authentication Mode
Low-Impact Mode (Open Mode + ACL)
High Security Mode (Closed Mode)
Click Run. The Progress Details page appears, prompting you for additional input.
Click User Input Required, and modify the fields as necessary. A new window appears, prompting you to select the
interfaces for the configuration analysis.
Check the check boxes next to the interfaces that you want to analyze, and click Submit. The Progress Details page
is displayed again.
Click Show Results Summary.
HowTo-81-Troubleshooting_Failed_AuthC
20
Procedure 4
TCP Dump
The TCP Dump utility monitors the contents of packets on a network interface that match a given Boolean expression. You
can use this utility to troubleshoot problems on your network. Cisco ISE troubleshooting diagnostic tools provide an
intuitive user interface (Figure 17).
Figure 17 TCP Dump Options
Go to Operations в†’ Troubleshoot в†’ Diagnostic Tools в†’ TCP Dump.
Select a Network Interface to monitor from the drop-down menu. This is the interface upon which the network traffic
is monitored, or sniffed.
Set Promiscuous Mode to On or Off by clicking the radio button. The default is On.
Promiscuous Mode is the default packet sniffing mode. It is recommended that you leave it set to On. In this mode,
the network interface is passing all traffic to the system's CPU.
In the Filter field, enter a Boolean expression on which to filter. Standard TCP Dump filter expressions are supported,
such as the following: host 10.0.2.1 and port 1812
Click Start to begin monitoring the network.
Click Stop when you have collected a sufficient amount of data, or wait for the process to conclude automatically
after accumulating the maximum number of packets (500,000).
HowTo-81-Troubleshooting_Failed_AuthC
21
Procedure 5
Failed Authentication Events
TrustSec authentications can fail for many reasons. These include an unknown user, bad credentials, expired credentials,
missing certificates, misconfiguration, and so on. Many of these failures can be diagnosed using careful examination of the
ISE logs. Common failures and their symptoms are explained below.
5411 No response received during 120 seconds on last EAP message sent to the client
Applies to
Possible
Causes
Resolution
All EAP types
NAD or supplicant: Timeout for EAP may be too aggressive.
Supplicant: Configured with certificate base authentication and the supplicant either does
not have valid credentials or does not trust ISE certificate.
Supplicant and user: Configured with password-based authentication and the user did not
provide valid credentials.
Verify that supplicant is configured properly to conduct a full EAP conversation with ISE.
Verify that NAS is configured properly to transfer EAP messages to or from supplicant.
Verify that supplicant or network access server (NAS) does not have a short timeout for EAP
conversations. Check the network that connects the NAS to ISE. If the external ID store is
used for the authentication, it may be not responding fast enough for current timeouts.
12520 EAP-TLS failed SSL/TLS handshake because the client rejected the ISE local-certificate
Applies to
Possible
Causes
Resolution
EAP-TLS (AnyConnect Network Access Manager)
The supplicant does not trust the ISE PSN certificate.
Check whether the proper server certificate is installed and configured for EAP by going to
the Local Certificates page
(Administration > System > Certificates > Local Certificates ). Also ensure that the certificate
authority that signed this server certificate is correctly installed in client's supplicant. Check
the previous steps in the log for this EAP-TLS conversation for a message indicating why the
handshake failed. Check OpenSSLErrorMessage and OpenSSLErrorStack for more
information.
22044 Identity policy result is configured for certificate based authentication methods but received password based
Applies to
Possible
Causes
Resolution
EAP-TLS, PEAP-TLS
ISE authentication policy is configured for password-based authentication, but the
supplicant is sending certificate credentials.
Check the appropriate configuration in Policy > Authentication. This error happens when
the identity source is configured for certificate-based authentication and received a
password based authentication request.
22045 Identity policy result is configured for password based authentication methods but received certificate based
authentication request
Applies to
Possible
Causes
Resolution
EAP-FAST, PEAP-MSCHAPv2
ISE authentication policy is configured for certificate-based authentication, but the
supplicant is sending password-based credentials.
Check the appropriate configuration in Policy > Authentication. This error happens when
the identity source is configured for password-based authentication and received a
certificate-based authentication request.
22056 Subject not found in the applicable identity store(s)
Applies to
Possible
Causes
Resolution
EAP-FAST, PEAP-MSCHAPv2, MAB
User or device was not found in the configured identity store
Check whether the subject is present in any one of the chosen identity stores. Note that
some identity stores may have been skipped if they do not support the current
authentication protocol.
Make sure the authentication policy points to correct identity store.
HowTo-81-Troubleshooting_Failed_AuthC
22
For authentication in a Microsoft Windows network with multiple domains, make sure that
the supplicant is appending the domain suffix (For users: administrator@example.com, for
machines: winxp.example.com).
24408 User authentication against Active Directory failed since user has entered the wrong password
Applies to
Possible
Causes
Resolution
EAP-FAST, PEAP-MSCHAPv2
User entered wrong password.
Check the user password credentials. If the RADIUS request is using PAP for authentication,
also check the shared secret configured for the network device.
15039 Rejected per authorization profile
Applies to
Possible
Causes
Resolution
All EAP types
The default AuthZ rule is to deny access, and there are no specific AuthZ rules for this
session.
The authorization profile with the ACCESS_REJECT attribute was selected as a result of the
matching authorization rule. Check the appropriate authorization policy rule-results.
22040 Wrong password or invalid shared secret
Applies to
Possible
Causes
Resolution
Password-based EAP types
Check the password of the user in internal identity store.
The shared RADIUS key does not match between ISE and NAD.
Check the user credentials and device shared secret in Administration > Network Resources
> Network Devices.
11036 The Message-Authenticator RADIUS attribute is invalid
Applies to
Possible
Causes
Resolution
All EAP types and MAB
The shared RADIUS key does not match between ISE and NAD
Check whether the shared secrets on the AAA client and ISE server match. Ensure that the
AAA client and the network device have no hardware problems or problems with RADIUS
compatibility. Also ensure that the network that connects the device to the ISE has no
hardware problems.
11007 Could not locate Network Device or AAA Client
Applies to
Possible
Causes
Resolution
All EAP types and MAB
NAD may not be in the network device list on ISE
Verify whether the network device or AAA client is configured in Administration > Network
Resources > Network Devices.
5417 Dynamic Authorization failed
Applies to
Possible
Causes
Resolution
All EAP types and MAB
NAD is not configured with change of authorization (CoA) from ISE PSN.
Check the connectivity between ISE and the NAD. Ensure that ISE is defined as the dynamic
authorization client on NAD and that CoA is supported on device.
HowTo-81-Troubleshooting_Failed_AuthC
23
Appendix A: References
Cisco TrustSec System:
п‚·
http://www.cisco.com/go/trustsec
п‚·
http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns744/landing_DesignZone_TrustSec.html
Device Configuration Guides:
Cisco Identity Services Engine User Guides:
http://www.cisco.com/en/US/products/ps11640/products_user_guide_list.html
For more information about Cisco IOS Software, Cisco IOS XE Software, and Cisco NX-OS Software releases, please refer
to following URLs:
п‚·
For Cisco Catalyst 2900 series switches:
http://www.cisco.com/en/US/products/ps6406/products_installation_and_configuration_guides_list.html
п‚·
For Cisco Catalyst 3000 series switches:
http://www.cisco.com/en/US/products/ps7077/products_installation_and_configuration_guides_list.html
п‚·
For Cisco Catalyst 3000-X series switches:
http://www.cisco.com/en/US/products/ps10745/products_installation_and_configuration_guides_list.html
п‚·
For Cisco Catalyst 4500 series switches:
http://www.cisco.com/en/US/products/hw/switches/ps4324/products_installation_and_configuration_guides_list.ht
ml
п‚·
For Cisco Catalyst 6500 series switches:
http://www.cisco.com/en/US/products/hw/switches/ps708/products_installation_and_configuration_guides_list.html
п‚·
For Cisco ASR 1000 series routers:
http://www.cisco.com/en/US/products/ps9343/products_installation_and_configuration_guides_list.html
For Cisco Wireless LAN Controllers: http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg.html
HowTo-81-Troubleshooting_Failed_AuthC
24
Документ
Категория
Без категории
Просмотров
470
Размер файла
1 929 Кб
Теги
1/--страниц
Пожаловаться на содержимое документа