- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Radius Testing - Cisco ISE - not all passing
Hello
Firmware: 25.13
Cisco ISE: 2.3.0.298
just testing the radius authentication from the dashboard to our Cisco ISE radius
Total APs: | 9 |
APs passed: | 4 |
APs failed: | 5 |
APs unreachable: | 0 |
these are same subnet, same site, same everything
each time I test I receive different results and sometime I receive an error
Airespace-ACL-Name:HS-Laptop
RADIUS attributes unused:
User-Name: *domain\user*
State:ReauthSession:0a2d000fKS4uutHjQp5FArmB2ZstcLZ63zRmIXdtubIA7tDgTB4
Authentication Details
Source Timestamp | 2019-09-05 09:42:20.332 |
Received Timestamp | 2019-09-05 09:42:20.333 |
Policy Server | servername |
Event | 5200 Authentication succeeded |
Username | domain\user |
Endpoint Id | 00:00:00:00:00:02 |
Calling Station Id | 00-00-00-00-00-02 |
Authentication Identity Store | HS_AD |
Authentication Method | MSCHAPV2 |
Authentication Protocol | PEAP (EAP-MSCHAPv2) |
Network Device | Meraki_AP |
Device Type | All Device Types#Meraki_AP |
Location | All Locations |
NAS IPv4 Address | 10.45.99.12 |
NAS Port Type | Wireless - IEEE 802.11 |
Authorization Profile | HS_Laptop_Permit_All |
Response Time | 19 milliseconds |
failing AP ISE output
Authentication Details
Source Timestamp | 2019-09-05 09:42:21.899 |
Received Timestamp | 2019-09-05 09:42:21.9 |
Policy Server | servername |
Event | 5400 Authentication failed |
Failure Reason | 12953 Received EAP packet from the middle of conversation that contains a session on this PSN that does not exist |
Resolution | Verify known NAD issues and published bugs. Verify NAD configuration. Turn debug log on DEBUG level to troubleshoot the problem. |
Root cause | Session was not found on this PSN. Possible unexpected NAD behavior. Session belongs to this PSN according to hostname but may has already been reaped by timeout. This packet arrived too late. |
Username | domain\user |
Endpoint Id | 00:00:00:00:00:02 |
Calling Station Id | 00-00-00-00-00-02 |
Network Device | Meraki_AP |
Device Type | All Device Types#Meraki_AP |
Location | All Locations |
NAS IPv4 Address | 10.45.99.13 |
NAS Port Type | Wireless - IEEE 802.11 |
Response Time | 4 milliseconds |
any help on this is greatly appreciated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can't help here as I don't mess with ISE, but found the following links that might be of assistance (unless you've already read them then never mind lol).
You'll want to make sure your ISE is updated/patched etc.
Are you able to open up a TAC case for your issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Lagcat
Do you have radius accounting enabled? If so you might be running into an ISE bug.
Can you try disabling accounting and see if you still see the same issue?
P.S: For security reasons, it will be a good idea to mask out sensitive information like Re-auth session IDs and all 🙂
Cheers!
Raj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are all the APs listed as clients in ISE?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Philip
i am covering our entire network subbnet with meraki so authentication is covered at this point as you can see the Same subnet is taking authentication the same as the AP which is not
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Raj
sorry I was not sure what is passed in all these things
do you have any description of what the ISE bug could be as I am sure we are running accounting
cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Lagcat I was looking into the Auth error details and found this article in Cisco forums which is related to the auth error you are seeing. You can see the bug id in there.
Cheers!
Raj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
