After a search in the docs I couldn´t find what is this status "Pending Deletion" in the "Blocked on" line.
sw#sh authentication sessions int gi 1/0/12 det
MAC Address: [omitted]
IPv6 Address: Unknown
IPv4 Address: 10.7.0.76
Oper host mode: single-host
Oper control dir: both
Session timeout: N/A
Common Session ID: 0AFE0AF00022940F55761E56
Acct Session ID: 0x002443D3
Current Policy: (Unnamed Policy)
Blocked On: Pending Deletion
Method status list:
dot1x Authc Success
can someone explain me what is this?
What i´ve found so far:
so in this case,
D - Awaiting Deletion—Session deletion has
begun. One or more asynchronous actions are
currently in progress (either retrieving
accounting data from the platform or deleting
the IIF ID).
what does this mean? What is the IIF ID?
I havent found any information on this myself and have not worked with a 3850 for any radius authentication. This will take some time on my end to get an answer for you. In the meantime and if this is an issue you may want to open a TAC case to see if an engineer can shed some light on this.
*Please rate helpful posts*
I am experiencing exactly same problem with 3850 and ISE 1.2 - everything works correctly with other switch types.
It worked some time but last few days this problem appeared.
Have you found the solution? My IOS version is 03.02.02.SE. I will try to upgrade tonight and hope it will work - otherwise I am going to open TAC case.
so far the client haven´t told me anything new concerning this subject. I think that the upgrade to 03.03.01SE resolved the problem.
Upgrade your Sw first and then tell me if it solved this problem.
Upgrade to version 03.03.02SE seems to solve this issue. It works now, but it worked before and than stopped, so I will confirm later.
Do you still have this problem? Today i got an email from a customer which has this problem too... he has Cisco 3650 with IOS XE 03.03.02SE.
I know this is an old thread, but I thought I'd mention that I've got a stack on 3.3.3SE with the same "stuck in deletion" problem for only one MAC address. We've had a wide range of dot1x/mab issues with these 3850's, so it's not too surprising that we're adding another one to the pile. I'm wondering if it wasn't your upgrade that fixed it, but rather the reboot required for the upgrade that did. We're getting ready to upgrade to 3.6.1 this weekend to resolve another dot1x issue we've been working on with Cisco TAC and developers. Did either of you ever see this issue come back?