11-09-2017 12:35 PM - edited 03-01-2019 06:14 PM
Hi there,
Thanks for reading.
I'm exceeding thresholds in my IP SLA udp-echo monitoring. I have reaction-alerts enabled and a logging host defined. Test messages (send log 5) are received by my SNMP server (logging host). The problem is I'm expecting the threshold traps to be forwarded to the server but they're not.
ID Type Destination Stats Return Last (ms) Code Run
-----------------------------------------------------------------------
*1 udp-echo 10.156.255.5 RTT=127 Over threshold 37 seconds ago
ip sla auto discovery
ip sla responder
ip sla 1
udp-echo 10.156.255.5 5000
owner US3_IM_SC
tag US3_MX3_RTT
threshold 50
ip sla schedule 1 life forever start-time now
ip sla logging traps
ip sla enable reaction-alerts
logging source-interface Loopback0
logging host 10.150.2.192
Thanks,
Bob
Solved! Go to Solution.
11-14-2017 02:53 PM
Problem solved: I had two conflicting thresholds configured. I removed the threshold limit under the ip sla command and relied only on the ip sla reaction-configure threshold setting. Now, i'm getting the logging & alerting I was expecting.
Br,
Bob
11-09-2017 01:54 PM
I added an ip sla reaction-configuration command against ip sla #1 with threshold values and threshold type configured. That generated a single forwarded alert on my snmp server but appears to have stopped (because the ip sla 1 threshold continues to be surpassed.
Any thoughts on that?
Thanks again!
Bob
11-14-2017 02:53 PM
Problem solved: I had two conflicting thresholds configured. I removed the threshold limit under the ip sla command and relied only on the ip sla reaction-configure threshold setting. Now, i'm getting the logging & alerting I was expecting.
Br,
Bob
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide