Difference between IPSLA TCP connect and Netpath.

Hi Guys,

Can someone let me know if configuring IPSLA TCP Connect on a Switch and Configuring Netpath does the same job?

I know Netpath can be installed on Server and get End user based data. However if we want to test from Switch is IPSLA TCP Connect the best option?

Please do let me know.

Thanks,

Reuben

Find more posts tagged with

connectivity

tcp

solarwinds

ipsla

NetPath

npm

Accepted answers

All comments

sgtp

TCP Connect SLA operation "measures the response time taken to perform a TCP Connect operation between a Cisco device and devices using IP." (IP SLAs Configuration Guide, Cisco IOS Release 15M&T - Configuring IP SLAs TCP Connect Operations [Cisco IOS 15.4M&T] - … ). It isn't going to tell you "where" the latency comes from, it will only tell you the amount of time it took the SYN SYN/ACK ACK process to complete.

NetPath provides hop by hop latency, displays multi-path information, and performs a connection to the destination from the perspective of a server or workstation device.

I guess I'm don't understand the use case. If I suspected there was an issue in my layer 2 infrastructure, I wouldn't use a TCP-connect SLA. I would look at the Devil, aka STP or layer 1.

can you provide some more details on what you are trying to accomplish?

Tony P

foonly

IP SLA has an operation called ICMP Path Echo that would do some of this, but I haven't gotten it to work reliably. Plus it certainly doesn't display as nicely in VNQM.

The nice thing about IP SLA, though, is that it's relatively impervious to performance spikes on the Orion server. I haven't had the time to play with an additional probe on an idle system. But usually, the problems I see via NetPath are well outside of Orion itself.

=Foon=