Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > NetPath last hop shows high latency

NetPath last hop shows high latency

Updated November 15, 2016

Overview

The NetPath last hop shows high latency when dealing with ASA.

Environment

NPM version 12.0

Cause 

NetPath standard probing sends multiple rounds of SYN packets to the endpoint. The endpoint responds to each SYN with SYN-ACK. Typically, OS on NetPath probe catches SYN-ACK and responds with RESET packet which clears the half-open connection in ASA. So the ASA treats the next SYN for a new half-open connection. 

 

In some rare cases, OS doesn't send RESET. ASA would catch an extra SYN for the existing half-open connection and may consider an anomaly. The SendResetPerRoundStandard flag basically forces NetPath probe to send the RESET packet by itself so it clears out the half-open connection in ASA.

Resolution

  1. Go to C:\ProgramData\Solarwinds\Orion\NetPath\NetPathAgent.cfg on the SolarWinds server.
  2. Set the SendResetPerRoundStandard value to True.
  3. Restart all services.

 

 

 

Last modified

Tags

Classifications

Public