Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

IPSLA Responder Not Working IPSLA Contantly Timing Out (Can Anyone Save Me)

Hi All

I'm doing a university project and need urgent help. My Topology is below.

PC1 ---------------------- R1 --------------------------SWITCH 2 ---------------R2 -------------------- PC 2

192.168.1.1        1.2                                                                                    2.1                    192.168.2.7

IPSLA UDP jitter operation works not a problem, but any other operation dows not. I don't have any access-lists configured or anything.

Please see the below. debugs. I just want a simple operation to work. My ipsla does'nt work i've got a feeling that theres a problem at the responder end. My responder does'nt respond to probes are pick up any statistics. This should be simple but i don't understand.

Config on source.....

ip sla monitor 1
type jitter dest-ipaddr 192.168.2.7 dest-port 16384 source-ipaddr 192.168.1.2 source-port 16384 num-packets 100 interval 1
ip sla monitor schedule 1 life forever start-time now

ip sla monitor 6
type udpEcho dest-ipaddr 192.168.2.7 dest-port 16384
frequency 30
ip sla monitor schedule 6 life forever start-time now

ip sla monitor 123
type pathJitter dest-ipaddr 192.168.2.7 num-packets 100 interval 2
ip sla monitor schedule 123 life forever start-time now

Only the path jitter works and resturns results for me.

config on r2

###########

ip sla monitor responder
ip sla monitor responder type udpEcho ipaddress 192.168.1.2 port 16384

Mar  1 05:51:54.118: IP SLA Monitor(2) Scheduler: Starting an operation
Mar  1 05:51:54.118: IP SLA Monitor hash insert : 192.168.1.2 50123
Mar  1 05:51:54.118: IP SLA Monitor(2) jitter operation: Starting jitter operati
on
Mar  1 05:51:54.118: IP SLA Monitor(2) CtrlMsg: Sending msg, ver=1, id=114, len=
52, cmd=4, ip=192.168.2.7, port=50122, duration=45000ms
Mar  1 05:51:56.850: IP SLA Monitor(6) CtrlMsg: Timeout
Mar  1 05:51:56.850: IP SLA Monitor(6) CtrlMsg: No connection
Mar  1 05:51:56.850: IP SLA Monitor(6) Scheduler: Updating result
Mar  1 05:51:57.150: IP SLA Monitor(1) CtrlMsg: Timeout
Mar  1 05:51:57.150: IP SLA Monitor(1) CtrlMsg: No connection
Mar  1 05:51:57.150: IP SLA Monitor hash remove: 192.168.1.2 16384
Mar  1 05:51:57.150: IP SLA Monitor(1) Scheduler: Updating result
Mar  1 05:51:59.118: IP SLA Monitor(2) CtrlMsg: Timeout
Mar  1 05:51:59.118: IP SLA Monitor(2) CtrlMsg: Sending msg, ver=1, id=115, len=
52, cmd=4, ip=192.168.2.7, port=50122, duration=45000ms
Mar  1 05:52:04.122: IP SLA Monitor(2) CtrlMsg: Timeout
Mar  1 05:52:04.122: IP SLA Monitor(2) CtrlMsg: Sending msg, ver=1, id=116, len=
52, cmd=4, ip=192.168.2.7, port=50122, duration=45000ms

I need help big time!!!! project needs to be handed in on Wednesday

6 REPLIES
Cisco Employee

Re: IPSLA Responder Not Working IPSLA Contantly Timing Out (Can

First, you state two contradictory things.  You say first that UDP jitter works, then you say that path jitter works.  Which collectors (collector numbers) fail, and which succeed?  We typically recommend you don't specify any port number of the responder device.  Just configure:

ip sla monitor responder

Nothing else.  The other thing that looks weird is that it appears you're sending probes to your PCs (which, of course, wouldn't work).  The topology diagram is a bit shifted, so I can't see if this is really the case.  It would help to see complete running configurations from both routers.

--

Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com

Community Member

Re: IPSLA Responder Not Working IPSLA Contantly Timing Out (Can

Hi Joe

Brilliant stuff i thought i was wrong, what i meant to say was that the UDP path Jitter probe works well, but not the other. The reason why this is is because the UDP path Jitter probes can only send packets to a cisco device as in only a cisco device will respond.

Will try changing this in a short while.

Also I'm going to need to know which is the best tool to use to pull of the IPSLA UDP jitter statistics. I want the easiest one to use.

regards

Carl

Cisco Employee

Re: IPSLA Responder Not Working IPSLA Contantly Timing Out (Can

CiscoWorks Internetwork Performance Monitor can process IP SLA data.  If you use it to configure the collectors, then it is very easy to display graphs associated with the collectors.  If you configure the collectors manually, then you need to use a command line tool to import them.  However, I'm guessing that for a class project, you're not looking to spend any money.  While you can download an evaluation copy of CiscoWorks LMS from http://www.cisco.com/go/lms , you might also want to look into Solarwinds free IP SLA monitoring tool at http://www.solarwinds.com/products/freetools/ip_sla_monitor/ .

--

Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com

Community Member

Re: IPSLA Responder Not Working IPSLA Contantly Timing Out (Can

Will the LMS give me stats UDP jitter , packet loss graphs and so on.

Cisco Employee

Re: IPSLA Responder Not Working IPSLA Contantly Timing Out (Can

Community Member

Re: Need help setting up cisco works LMS urgently.....

Hi Joe

Can you help me in setting up this software step by step.....

regards

Carl Williams

559
Views
0
Helpful
6
Replies
CreatePlease to create content