I want to use IP SLA to perform simple up/down monitoring of an IP host and to generate a syslog alert if the host goes down.
I have a 2650XM router running 12.4(23) IP Voice IOS.
My basic IP SLA config is hown below:
ip sla monitor 10
type echo protocol ipIcmpEcho 10.55.1.1
ip sla monitor schedule 10 life forever start-time now
Based upon the output of the show ip sla monitor statistics command the up/down status of the host is being tracked ok.
GWYDAT01#sho ip sla monitor statistics
Round trip time (RTT) Index 10
Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: 09:23:19.426 BST Thu May 20 2010
Latest operation return code: Timeout
Number of successes: 24!
logging buffered 4096 debugging
logging console informational
Operation time to live: Forever
Solved! Go to Solution.
The command ip sla monitor logging traps generates a syslog trap not a syslog message.
You may send this traps to NMS stations listening to traps. Use following commands with the above one to do so,
snmp-server community TEST RW
snmp-server enable traps syslog
snmp-server host 22.214.171.124 TEST
snmp-server host 126.96.36.199 TEST syslog
This will sent the IP sla logging to NMS station listening on port 162.
Please rate useful posts.
Thank you for the reply. I have added the SNMP commands from your post but it still does not seem to be working.
When I replicate the monitored condition no SNMP trap is generated.
SNMP logging: enabled
Logging to 10.1.1.225.162, 0/10, 0 sent, 0 dropped.
Just to let you know that I have managed to get an alert shown on the console by adding the command listed below:
track 1 rtr 10
delay down 10 up 20
I know that this was not what initially asked for but it does show in the log when the monitored condition changes.
Thanks to everyone who read the post.
My name is Rogelio; I am a technician located in Argentina. I am experiencing quite the same problem mentioned in this thread.
Actually, I just see the trap sent ONCE (more preciselly, when the IP SLA object starts and times out in reaching the objective). ¿Is this the expected behavior?
I want the trap be sent (either SNMP or SYSLOG style) EVERY TIME the IP SLA object times out with the target. ¿ is it possible? The following is my basic configuration:
ip sla 2
ip sla schedule 2 life forever start-time now
ip sla reaction-configuration 2 react timeout threshold-type immediate action-type trapOnly
logging trap debugging
logging source-interface Loopback0
snmp-server enable traps syslog
snmp-server enable traps ipsla
snmp-server host 188.8.131.52 mycommunity syslog ipsla
Your help will be greatly appreciated
You can also configure an EEM script to monitor the IP SLA and of then have the EEM script generate a message. I'll posy the script when I get a computer. But with that you can your NMS alert when it sees this particular message. That's what I have done in the past.
Sent from Cisco Technical Support Android App
Thank you very much for answer, and I apologize for my late answer. I have been 5 days without broadband access...
I managed to build an EEM script, but the problem is that I can only generate an event "once". I need the router to generate a notification (trap, syslog, or both) EVERY time the condition is met (ie, as long as the IP SLA object times out, i want the router to generate an event.
As far as I saw, there is no simple way to generate a continuous stream of events (once each time the IP SLA times out).
Any hints will be appreciated!