cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1303
Views
5
Helpful
5
Replies

Active Endpoints showing as 0 in ISE

DigiDen
Level 1
Level 1

Good morning, I recently had the issue, where we couldn't profile or add endpoint devices into our ISE deployment. We were getting the error, "unable to create the endpoint/Endpoint already exists in the database.  As recommended, I ran the "Reset Identity Services Engine (ISE) Context Visibility" which did cure the issue (although we do see it still occasionally) but it then reset my active endpoints to 0.

DigiDen_0-1698916866917.png

 

ISE is running as expected, devices are profiling, and we can add endpoints to the database manually if required.

Is it worth running the Reset again?  Is it anything to worry about?

CISCO ISE
SNS-3655-K9
Version Identifier (VID)
ADE-OS Version
3.1.0.135

 

thanks,

Den

3 Accepted Solutions

Accepted Solutions

Hm I would say a TAC case is in order.  Also ensure you have RADIUS accounting properly configured on your NADs.

View solution in original post

Thank you, Will do, there were endpoints listed in the active endpoints container before the context visibility process was run. Will give TAC a shout.

View solution in original post

Just to update, as part of the internal certificate renewal update, both of the policy servers were restarted. This has resolved the issue. 

 

DigiDen_0-1700124895669.png

 

View solution in original post

5 Replies 5

Did you rebuild the CV after the reset?  Or just reset only?  Once you reset you have to run option 21 to rebuild the CV database.

Yes, 99% confident that I did, as it's listed on the Document to run option 21.

Hm I would say a TAC case is in order.  Also ensure you have RADIUS accounting properly configured on your NADs.

Thank you, Will do, there were endpoints listed in the active endpoints container before the context visibility process was run. Will give TAC a shout.

Just to update, as part of the internal certificate renewal update, both of the policy servers were restarted. This has resolved the issue. 

 

DigiDen_0-1700124895669.png