Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Agent response time is different than expected using ICMP

Agent response time is different than expected using ICMP

Table of contents

Overview

The Agent response time is different than expected using ICMP. When using Agent initiated Response time. 

Environment

All SAM versions

Detail

ICMP is a low level messaging protocol. Because of its simplicity, it is not possible to accurately record the same response time values using a different protocol. For example: An agent node reports a response time in the range 490-850 ms, but typical ICMP response time is about 150 ms.

 

Agent Initiated Response and Status Enabled in List resources triggers the Agent to use the TCP port 17778 to do a 'pseudo-ping' -or- TCP Ping instead of a 'datagram' ping, used by ICMP. 

 

ICMP pings are much faster as they use an IP DATAGRAM packet.

TCPIP pings are slower to process due to the extra load to proces get verification in the network.

 

Diagram: 

sw agent initiated response time.png

 

 

 

 

Last modified

Tags

Classifications

Public