Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Netflow Traffic Analyzer (NTA) > 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: 127 Votes: 0 Revisions: 8

Updated October 12, 2017

Overview

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.

 

Environment

  • All Orion NTA environments

Detail

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

Tags

Classifications

Public