Ip sla
Hello,
what is the purpose of ip sla responder command?
I can configure simple icmp echo probes with
ip sla 1
icmp-echo 10.0.0.2 source-ip 10.0.0.1
ip sla schedule 1 start now life forever
And ping will work;
I imagine udp-echo has the same logic only works with udp packets to specific port;
So i configure something like:
ip sla 2
udp-echo 10.0.0.2 67 source-ip 10.0.0.1
ip sla 2 schedule 2 start now life forever
And on other host i configure ip sla responder (don't know why should I, i just know if its tcp/udp probe i should include that) - but all probes return as failures.
So with that ip sla 2 I am trying to probe port 67 (DHCP/BOOTS).
Why is it not working? And why do i need ip sla responder (or rtr responder on my switches)?
Thank you
what is the purpose of ip sla responder command?
I can configure simple icmp echo probes with
ip sla 1
icmp-echo 10.0.0.2 source-ip 10.0.0.1
ip sla schedule 1 start now life forever
And ping will work;
I imagine udp-echo has the same logic only works with udp packets to specific port;
So i configure something like:
ip sla 2
udp-echo 10.0.0.2 67 source-ip 10.0.0.1
ip sla 2 schedule 2 start now life forever
And on other host i configure ip sla responder (don't know why should I, i just know if its tcp/udp probe i should include that) - but all probes return as failures.
So with that ip sla 2 I am trying to probe port 67 (DHCP/BOOTS).
Why is it not working? And why do i need ip sla responder (or rtr responder on my switches)?
Thank you
Comments
-
glorfindal2000
Member Posts: 2 ■□□□□□□□□□
By using an IP SLA responder you will gain much more accurate information, as it is able to send back processing delay information.
In answer to the issue you have with just recieving failures, perhaps the responder is unable to bind to that port. Are you running DHCP already on the destination router?
You'll find a wealth of information here: Cisco IOS IP Service Level Agreements User Guide [IP Application Services] - Cisco Systems