IP SLA Error Latest operation return code: Socket bind error

Unanswered Question
Apr 2nd, 2012

1) I have defined the following ip sla test on a c2800. I want to mainly monitor  rrt and packet loss between c2800 and  a remote c2900.

     ip sla monitor 9002

      type jitter dest-ipaddr xxx.xxx.xxx.xxx dest-port 6666 source-ipaddr xxx.xxx.xxx.xxx source-port 6666 num-packets 50 interval 30

      verify-data

      owner foo

      tag rtr-1

      frequency 30

      hours-of-statistics-kept 1

     ip sla monitor reaction-configuration 9002 react rtt threshold-value 100 60 threshold-type consecutive 2 action-type trapOnly

     ip sla monitor reaction-configuration 9002 react packetLossSD threshold-value 2 1 threshold-type immediate action-type trapOnly

     ip sla monitor reaction-configuration 9002 react packetLossDS threshold-value 2 1 threshold-type immediate action-type trapOnly

     ip sla monitor reaction-configuration 9002 react connectionLoss threshold-type immediate action-type trapOnly

2) When I do  a "show ip sla monitor stat 9002" on my  IP SLA source router  I get back

     latest operation return code:  Socket bind error

I did enable rtr responder on my target rtr-1.  So why the error ? On the target router do I need to specify port 6666 when I enable the responder ?

Jerry

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
Joseph Clarke Mon, 04/02/2012 - 17:18

We typically see this when multiple collectors are configured to use the same source port.  Only one source port can be used per collector (if they all run simultaneously).  Can you pick another source port other than 6666?

GERARD PUOPLO Wed, 04/04/2012 - 11:06

I am using a dedicate router for several IP SLA test to client sites.  For security reasone I only had one port opened to me (say port xxxxx) and the security folks required me to use that same port for source port and dest port.   I see now what you mean.  I cannot keep using port xxxxx as source port on many IP SLA jitter entries.

Thanks

Jerry

Joseph Clarke Wed, 04/04/2012 - 11:16

Dest port is one thing.  That can be the same.  Would your security folks not allow a random choice of source port (or at least a preset range)?

borislavpopov Fri, 04/27/2012 - 09:27

Hi,

I have the following issue. I have few routers configured the same way with a SLA and tcp-connect. Each of the routers has successful probes for few hours (one of it even 3 days) and after unpredicted period the probes fail. The error returned is

'Latest operation return code: Socket connect error'. I have done some debug and I can see that the router initiates SYNs but no ACK are received. If I delete the SLA and reconfigure it with new source port it runs for few hours and again fails. The following is the configuration and the debug output (IPs are changed). I have even configured additional SLA which in the debug below you can see that it's working (first SLA 102 failed, second SLA 101 is working working)

Have you got any idea what should be the reason?

****************************************************************************************************

ip sla 101
tcp-connect 10.10.10.10 23456 source-ip 192.168.1.1 source-port 50000 control disable
ip sla schedule 101 life forever start-time now

ip sla 102
tcp-connect 10.10.10.10 23456 source-ip 192.168.1.1 source-port 60000 control disable
ip sla schedule 102 life forever start-time now


Round Trip Time (RTT) for       Index 101
        Latest RTT: 32 milliseconds
Latest operation start time: .11:55:53.540 BST Thu Apr 26 2012
Latest operation return code: OK
Number of successes: 14
Number of failures: 0
Operation time to live: Forever

Round Trip Time (RTT) for       Index 102
        Latest RTT: 0 milliseconds
Latest operation start time: .11:54:58.848 BST Thu Apr 26 2012
Latest operation return code: Socket connect error
Number of successes: 0
Number of failures: 12
Operation time to live: Forever

.Apr 26 11:01:12.818: IP: tableid=0, s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), routed via FIB
.Apr 26 11:01:12.818: IP: s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), len 44, sending
.Apr 26 11:01:12.818:     TCP src=60000, dst=23456, seq=3276669687, ack=0, win=4128 SYN

.Apr 26 11:01:58.814: IP: tableid=0, s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), routed via FIB
.Apr 26 11:01:58.814: IP: s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), len 44, sending
.Apr 26 11:01:58.814:     TCP src=60000, dst=23456, seq=1140928655, ack=0, win=4128 SYN

.Apr 26 11:02:00.813: IP: tableid=0, s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), routed via FIB
.Apr 26 11:02:00.813: IP: s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), len 44, sending
.Apr 26 11:02:00.813:     TCP src=60000, dst=23456, seq=1140928655, ack=0, win=4128 SYN


.Apr 26 11:02:04.813: IP: tableid=0, s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), routed via FIB
.Apr 26 11:02:04.813: IP: s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), len 44, sending
.Apr 26 11:02:04.813:     TCP src=60000, dst=23456, seq=1140928655, ack=0, win=4128 SYN


.Apr 26 11:04:53.489: IP: tableid=0, s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), routed via FIB
.Apr 26 11:04:53.489: IP: s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), len 44, sending
.Apr 26 11:04:53.489:     TCP src=50000, dst=23456, seq=1531259741, ack=0, win=4128 SYN
.Apr 26 11:04:53.521: IP: tableid=0, s=10.10.10.10 (FastEthernet0/1), d=192.168.1.1 (FastEthernet0/0.1), routed via RIB
.Apr 26 11:04:53.521: IP: s=10.10.10.10 (FastEthernet0/1), d=192.168.1.1, len 44, rcvd 4
.Apr 26 11:04:53.521:     TCP src=23456, dst=50000, seq=3016350808, ack=1531259742, win=16384 ACK SYN
.Apr 26 11:04:53.521: IP: tableid=0, s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), routed via FIB
.Apr 26 11:04:53.521: IP: s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), len 40, sending
.Apr 26 11:04:53.521:     TCP src=50000, dst=23456, seq=1531259742, ack=3016350809, win=4128 ACK
.Apr 26 11:04:53.521: IP: tableid=0, s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), routed via FIB
.Apr 26 11:04:53.521: IP: s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), len 40, sending
.Apr 26 11:04:53.521:     TCP src=50000, dst=23456, seq=1531259742, ack=3016350809, win=4128 ACK PSH FIN
.Apr 26 11:04:53.549: IP: tableid=0, s=10.10.10.10 (FastEthernet0/1), d=192.168.1.1 (FastEthernet0/0.1), routed via RIB
.Apr 26 11:04:53.549: IP: s=10.10.10.10 (FastEthernet0/1), d=192.168.1.1, len 40, rcvd 4
.Apr 26 11:04:53.549:     TCP src=23456, dst=50000, seq=3016350809, ack=1531259743, win=65535 ACK
.Apr 26 11:04:53.549: IP: tableid=0, s=10.10.10.10 (FastEthernet0/1), d=192.168.1.1 (FastEthernet0/0.1), routed via RIB
.Apr 26 11:04:53.549: IP: s=10.10.10.10 (FastEthernet0/1), d=192.168.1.1, len 40, rcvd 4
.Apr 26 11:04:53.549:     TCP src=23456, dst=50000, seq=3016350809, ack=1531259743, win=65535 ACK FIN
.Apr 26 11:04:53.549: IP: tableid=0, s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), routed via FIB
.Apr 26 11:04:53.553: IP: s=192.168.1.1 (local), d=10.10.10.10 (FastEthernet0/1), len 40, sending
.Apr 26 11:04:53.553:     TCP src=50000, dst=23456, seq=1531259743, ack=3016350810, win=4128 ACK

Actions

Login or Register to take actions

This Discussion

Posted April 2, 2012 at 10:14 AM
Stats:
Replies:6 Avg. Rating:
Views:1867 Votes:0
Shares:0
Tags: No tags.
Categories: IP SLA
+

Discussions Leaderboard

Rank Username Points
1 2,478
2 1,624
3 1,445
4 861
5 578