Solved: Cisco IP SLA Help

Carlton Patterson · ‎03-03-2014

Hello Community,

I've configured the following tcp-connect ip sla on my router. The server is an email server.

However, I can't achieve any successes. I'm sure its something very simple. ICMP-ECHO works fine.

Any help will be greatly appreciated.

ip sla monitor 209

type tcpConnect dest-ipaddr 150.50.5.2 dest-port 25 source-ipaddr 150.50.5.1 source-port 9995

ip sla monitor schedule 209 life forever start-time now

!

r3#show ip sla monitor statistics 209

Round trip time (RTT) Index 209

Latest RTT: NoConnection/Busy/Timeout

Latest operation start time: *00:13:17.291 UTC Fri Mar 1 2002

Latest operation return code: No connection

Number of successes: 0

Number of failures: 10

Operation time to live: Forever

Cheers

Carlton

cadet alain · ‎03-03-2014

Hi,

Can you try this one:

no ip sla monitor schedule 209 life forever start-time now

no ip sla monitor 209

ip sla monitor 209

type tcpConnect dest-ipaddr 150.50.5.2 dest-port 25 control disable source-ipaddr 150.50.5.1 source-port 9995

ip sla monitor schedule 209 life forever start-time now

Post the output from the debug and also enable this debug: debug ip sla monitor trace 209

Regards

Alain

Don't forget to rate helpful posts.

View solution in original post

cadet alain · ‎03-03-2014

Hi,

can you do debug ip tcp transactions and post output.

Regards

Alain

Don't forget to rate helpful posts.

Carlton Patterson · ‎03-03-2014

Hi Cadet,

Thanks for getting back to me.

I'm not getting any information from debug ip tcp transactions ...

Any other ideas?

Cheers

cadet alain · ‎03-03-2014

Hi,

Can you try this one:

no ip sla monitor schedule 209 life forever start-time now

no ip sla monitor 209

ip sla monitor 209

type tcpConnect dest-ipaddr 150.50.5.2 dest-port 25 control disable source-ipaddr 150.50.5.1 source-port 9995

ip sla monitor schedule 209 life forever start-time now

Post the output from the debug and also enable this debug: debug ip sla monitor trace 209

Regards

Alain

Don't forget to rate helpful posts.

Carlton Patterson · ‎03-03-2014

Hi Cadet,

Thanks again for responding .. going to apply your suggestion now..

Carlton Patterson · ‎03-03-2014

Cadet,

You're a star. I think it's working, but does the highlighted section suggest there is a problem

The following is the debug:

*Mar 1 03:03:53.931: TCB64DF173C created

*Mar 1 03:03:53.931: TCB64DF173C setting property TCP_PID (8) 6478562C

*Mar 1 03:03:53.935: TCB64DF173C setting property TCP_NO_DELAY (1) 64785630

*Mar 1 03:03:53.935: TCB64DF173C bound to 150.50.5.1.9995

*Mar 1 03:03:53.935: TCB64DF173C setting property TCP_TOS (11) 647856A8

*Mar 1 03:03:53.935: TCB64DF173C setting property TCP_NONBLOCKING_WRITE (10) 647856C4

*Mar 1 03:03:53.935: TCB64DF173C setting property TCP_NONBLOCKING_READ (14) 647856C4

*Mar 1 03:03:53.935: Reserved port 9995 in Transport Port Agent for TCP IP type 1

*Mar 1 03:03:53.939: TCP: sending SYN, seq 3069072801, ack 0

*Mar 1 03:03:53.943: TCP0: Connection to 150.50.5.2:25, advertising MSS 1460

*Mar 1 03:03:53.947: TCP0: state was CLOSED -> SYNSENT [9995 -> 150.50.5.2(25)]

*Mar 1 03:03:53.955: TCP0: state was SYNSENT -> ESTAB [9995 -> 150.50.5.2(25)]

*Mar 1 03:03:53.955: TCP: tcb 64DF173C connection to 150.50.5.2:25, peer MSS 1460, MSS is 1460

*Mar 1 03:03:53.955: TCP0: state was ESTAB -> FINWAIT1 [9995 -> 150.50.5.2(25)]

*Mar 1 03:03:53.955: TCP0: sending FIN

*Mar 1 03:03:53.971: TCP0: state was FINWAIT1 -> FINWAIT2 [9995 -> 150.50.5.2(25)]

*Mar 1 03:03:53.971: TCP0: bad seg from 150.50.5.2 -- Application closed: port 9995 seq 2089479353 ack 3069072803 rcvnxt 2089479353 rcvwnd 4128 len 95

*Mar 1 03:03:53.971: TCP: sending RST, seq 3069072803, ack 0

*Mar 1 03:03:53.971: TCP0: state was FINWAIT2 -> CLOSED [9995 -> 150.50.5.2(25)]

*Mar 1 03:03:53.971: Released port 9995 in Transport Port Agent for TCP IP type 1 delay 240000

*Mar 1 03:03:53.971: TCB 0x64DF173C destroyed

*Mar 1 03:03:53.971: TCP: sending RST, seq 3069072803, ack 0

*Mar 1 03:03:53.975: TCP: sent RST to 150.50.5.2:25 from 150.50.5.1:9995

The following is the statistics:

r3#show ip sla monitor statistics 209

Round trip time (RTT) Index 209

Latest RTT: 28 ms

Latest operation start time: *03:04:53.927 UTC Fri Mar 1 2002

Latest operation return code: OK

Number of successes: 3

Number of failures: 0

Operation time to live: Forever

cadet alain · ‎03-03-2014

Hi,

I have exactly the same output in my small lab I created to test this feature and apparently it doesn't seem to impact the success of the SLA instance as we don't see any failures so I would tend to reply that this shouldn't be a problem but I can't be 100% sure.

Regards

Alain

Don't forget to rate helpful posts.

Carlton Patterson · ‎03-03-2014

Hi Cadet,

I applied the following to our production router and now it won't work. The configuration is as follows:

ip sla 209

tcp-connect 10.50.83.11 25 source-ip 10.44.113.6 source-port 9995

ip sla schedule 209 life forever start-time now

You will notice it's slightly different than our lab router but it should still work.

Unfortunately, I'm not getting any output from the debug. The following is the stats:

UK00132-DM07-MapleCross#show ip sla statistics 209

IPSLAs Latest Operation Statistics

IPSLA operation id: 209

Latest RTT: NoConnection/Busy/Timeout

Latest operation start time: 15:54:26 GMT Mon Mar 3 2014

Latest operation return code: No connection

Number of successes: 0

Number of failures: 4

Operation time to live: Forever

Carlton Patterson · ‎03-03-2014

Hi Alain,

It worked - I forget to add control disable

Cheers mate.