- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2025 07:07 AM
Hello guys,
the operation team noticed me that there is a discrepancy between the endpoint status in the endpoint context visibility and the live logs.
The endpoint in the context visibility is marked as "rejected" while in the live logs is correctly authenticated, even from the switch authentication session on cli i can see it correctly authenticated as MAB and working.
Did you ever face this issue?
What could cause this discrepancy?
Ise is 3.3 patch 4.
Following all the screenshots of context visibility, live logs and the switch.
Thanks
Bye
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2025 01:27 AM
I reached out TAC and told me this is a bug fixed in 3.4 p1, not scheduling for other version...
this is the bug:

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2025 01:48 PM
Not seen this before.
The Live Logs show a failure and then success - is this from the same endpoint? Then perhaps the Context Visibility didn't get updated. I assume you took the screenshot of the Context Visibility after the endpoint was successfully authenticated?
I have seen cases where the endpoint had to be deleted from Context Visibility to allow the correct status to be displayed. I decided to perform the Option 20/21 in the "application configure ise") to Reser and resync the Context Visibility. That was done, but then I had to wait quite some time for the status of al the endpoints to be reflected again in Context Visibility, since I don't re-auth the endpoints - I had to wait for the Accounting interim updates to come in (up to 48 hours later).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2025 01:27 AM
I reached out TAC and told me this is a bug fixed in 3.4 p1, not scheduling for other version...
this is the bug:
