1883
Comment:
|
← Revision 11 as of 2017-11-08 19:28:19 ⇥
1984
|
Deletions are marked like this. | Additions are marked like this. |
Line 7: | Line 7: |
* smokeping , !IpSla monitoring http://oss.oetiker.ch/smokeping/probe/CiscoRTTMonTcpConnect.en.html | |
Line 27: | Line 27: |
1. Setup IpSla on cisco router. | 1. Setup !IpSla on cisco router. |
Cisco IP SLA services
- Use the cisco router as a remote probe to do measurements.
smokeping , IpSla monitoring http://oss.oetiker.ch/smokeping/probe/CiscoRTTMonTcpConnect.en.html
Cacti Monitoring of Cisco IP SLA
http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hsthresh.html
At times of high network activity, an ICMP ping test often shows a long and inaccurate response time, while an Cisco IOS IP SLAs test shows an accurate response time due to the time stamping on the responder.
Setup from http://forums.cacti.net/about19542.html
- Files
cacti_data_query_cisco_ip_sla_statistics.xml
- File comment: Import using cacti import/export template interface
Unzip mibs, and $ sudo cp *.my /usr/share/snmp/mibs/
- File comment: Copy to {cacti_root}/resource/snmp_queries/
Unzip mibs, and $ sudo cp *.my /usr/share/snmp/mibs/
sudo cp cisco_saa.xml /usr/share/cacti/resource/snmp_queries/
- Import cacti_data_query_cisco_ip_sla_statistics.xml
Setup IpSla on cisco router.
- # ip sla monitor reaction-configuration 10 react mos threshold-type immediate threshold-value 490 250 action-type trapOnly
- ip sla monitor responder or ip sla responder
- ip sla 27
- (config-ip-sla)#path-echo 172.27.240.8 (config-ip-sla-pathEcho)# (config)#ip sla schedule 27 life forever start-time now
- ip sla 27002
- (config-ip-sla)#udp-jitter 172.27.240.8 16384 codec g729a source-ip 172.17.240.5
- tag Klerksdorp_7_Harties_Bank{udp-jitter}
- (config-ip-sla)#udp-jitter 172.27.240.8 16384 codec g729a source-ip 172.17.240.5
- Files
...