Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > How Netflow summaries of TCP RST packets are handled by NTA

How Netflow summaries of TCP RST packets are handled by NTA

Table of contents
Created by Daniel Polaske, last modified by Alexandra.Nerpasova on Oct 12, 2017

Views: 198 Votes: 0 Revisions: 8

Updated October 12, 2017


TCP RST is generated by the router firewall when the idle TCP session times out (1 hour by default) and thus are valid to have an ingress/source Interface index of '0', because they're locally self-generated packets originating in the Router's CPU, without a real 'interface'.  If it's a firewall RST injection packet, the source IP will be spoofed.



  • All Orion NTA environments


Please note, this behavior will cause NTA to drop the flows due to the SNMP interface index ID of 0, or due to a mismatching management IP address mapped between the node and source IP address (the spoofed address).


Suggested Tags:  TCP, TCP RST, RST, SNMP, interface, index, ID, 


Reason for Rework or Feedback from Technical Content Review:



Last modified