04-02-2018 09:22 PM - edited 03-01-2019 06:29 PM
my config look like this..
ip sla 1
icmp-echo 210.1x.x.x source-ip 172.30.0.11
tag pingToCErtr
threshold 1000
timeout 1500
frequency 5
history hours-of-statistics-kept 25
history distributions-of-statistics-kept 5
history statistics-distribution-interval 10
history lives-kept 2
history buckets-kept 60
history filter all
history enhanced interval 900 buckets 100
ip sla schedule 1 life forever start-time now
1.how can monitor this IP SLA using my NMS.. is it some thing missing at the config?
2. how can i save the raw data from the IP SLA i'hve config?
04-05-2018 11:59 AM
Hi,
This might not be a whole lot of help, but maybe a little. To monitor the SLA drops in the device's logs, you would configure (on Cisco router) "track 1 ip sla 1 reachability".
As far as NMS monitoring SLA, you would need an SLA specific MIB in your NMS. Do a search on it. I don't want to give you false info on that specific MIB. You will then obviously have to configure your NMS to poll the device for user defined parameters based on that MIB.
04-05-2018 07:07 PM
how do i get raw data for the ipsla echo?
04-06-2018 01:16 AM - edited 04-06-2018 01:18 AM
What do you mean "raw data"? Do you mean failure dates/times? "show logs". Do mean export to a different data system? Send to Syslog.
04-08-2018 06:29 PM
04-11-2018 04:18 PM
Sorry, been busy at work. Are you talking about getting data on the RTT/Response time? No way that I'm aware of. You can check statistics on failures. You can have failures logged with time stamps. But SLAs aren't really for documenting response time. Once again, you can dive into the SLA MIB and see what options it has for your NMS.
04-17-2018 06:25 PM
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