IP SLA
Used to be (RTA - Real Time Responder), then it was called the (SAA - Service Assurance Agent) and now its called IP SLA.
Last updated
Used to be (RTA - Real Time Responder), then it was called the (SAA - Service Assurance Agent) and now its called IP SLA.
Last updated
We can set up synthetic traffic to be generated from an IP SLA source device on one router to another IP SLA Responder on another router.
R2(config)# ip sla responder
R2# show ip sla responder
R1(config)# ip sla 1 -------------- to create a particu;ar test
R1(config-ip-sla)# udp-jitter 10.1.1.2 49152 codec g711ulaw
How often is this test going to run for? Set a frequency for the generation of this traffic R1(config-ip-sla)# frequency 75
R1(config-ip-sla)# owner Wallis (owner of this particular test)
R1(config-ip-sla)#tag TEST (so we can pull this info easily into SNMP)
R1(config-ip-sla)#tos 184 (type of service for these synthetic, say packets-expedited forwarding traffic = 184 in decimal that differentiated services value)
Test is set up with the parameters we are interested in, we set up a schedule R1(config)# ip sla schedule 1 start-time now life forever (specify our particular IP SLA number that we set up of one. and then are we going to start it - right now- and what should be the life of this particular test - forever
R1#sho ip sla statistics 1 ---this 1 is from above "ip sla 1"
We can pull this information into SNMP and be proactive for example checking statistics on links etc.
