Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > How status and response time agent messaging is different than ICMP in the Orion Platform

How status and response time agent messaging is different than ICMP in the Orion Platform

Table of contents

Updated October 24, 2018

Overview

The Orion platform offers two kinds of polling for node status and response time on an agent node, Agent messaging and ICMP(Ping). Depending on your environment, one may have an advantage over the other. This article details how status and response time polling works for each one.

00197570_1.PNG

Environment

Orion Platform

Detail

ICMP is a low-level messaging protocol. Because of its simplicity, it is impossible to accurately record the same response time values using a different protocol. For example, Agent messaging will report a response time in the range 490-850 ms, but typical ICMP response time will do it in 150 ms.

 

Status & Response Time Agent messaging enabled in the List Resources page triggers the Agent to use the TCP port 17778 and do a 'pseudo-ping' -or- TCP ping instead of a basic 'Datagram' ping used by ICMP. 

 

  • ICMP pings are much faster as they use an IP Datagram packet.
  • TCP pings are slower due to the extra processing load to get verification in the network.

 

Diagram: 

sw agent initiated response time.png

Last modified

Tags

Classifications

Public