cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1641
Views
11
Helpful
2
Replies

ISE Node Latency Alarms

jofische
Cisco Employee
Cisco Employee

Hello,

The guidance for ISE 2.1+ is to keep latency between nodes lower than 300ms for optimal performance.  Is it true that the following ISE alarms pertain to that threshold?  If so, what are their trigger points exactly and what is the difference between these 3 messages?

Thank you!

Capture.PNG

1 Accepted Solution

Accepted Solutions

hslai
Cisco Employee
Cisco Employee

Not directly. There could be other causes for slow replication.

They are triggered based on for how long an ISE node not consuming replicated messages.

60150 -- INFO: > 60 minutes but <= 180 minutes

60151 -- WARN: > 180 minutes but <= 300 minutes 

60152 -- ERROR: > 300 minutes

View solution in original post

2 Replies 2

hslai
Cisco Employee
Cisco Employee

Not directly. There could be other causes for slow replication.

They are triggered based on for how long an ISE node not consuming replicated messages.

60150 -- INFO: > 60 minutes but <= 180 minutes

60151 -- WARN: > 180 minutes but <= 300 minutes 

60152 -- ERROR: > 300 minutes

Thank you!

Does a more suitable alarm message exist to monitor for latency between the nodes themselves?

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: