Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Latency vs. Response Time

I am hoping you guys can help me out.

As I understand things, a Response Time graph will show how fast a device responds to a ping, and Latency would be how long a device takes to process a message/instruction/etc. When I am looking at response time graphs in Orion, these are just how long it took for the device to respond back to orion1 via a ping, right? Latency would be more of how long it took to process an SNMP query, or similar?

so, how would we measure true Latency on a router or switch interface? I dont see anything about latency in any of the canned charts for an interface, so if i am either confused about the definition, or just missed the option, please let me know.

If anyone knows of a custom poller/chart/graph that will measure latency, please point me in the right direction.

Tia!

Find more posts tagged with

Accepted answers

All comments

mcbridea

You could setup a TCP port IP SLA operation without a responder. This requires high level processing. This also will give you true latency from any place on the network you have a Cisco IP SLA capable device.

http://www.solarwinds.com/products/orion/ip_sla_monitoring/

dclick

That requires the IP SLA manager option, yes? I didnt purchase that module, so if there is a way with just Orion NPM and Netflow, great. If not, well.. thanks anyway.

mcbridea

You don't have to use the IP SLAM product. You can configure the operation from CLI and read the results from CLI. IPSLAM makes it easier to do so on a large scale and gives history, alerts reports etc.

byrona

dclick

We don't have the IPSLA module as it wasn't available at the time we started working with IPSLA. We monitor an extensive network with using the IPSLA protocol. I have written a bunch of UnDP's to collect the data and display it in graphs in Orion; some of these data-points include UDP Jitter, MOS, RTT, and Packet Loss. You will need Cisco devices that support the IPSLA protocol as it is Cisco proprietary.

Hope this helps!

fcaron

dclick, I'll contact you off line.