Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA reporting shows incorrect ingress and egress data

NTA reporting shows incorrect ingress and egress data

Updated October 12, 2016

Overview

When creating a report that filters out one node using the Netflow Flow History the data shown is incorrect. The ingress and egress data display values that do not exist when looking at the charts for the specific interfaces.

Environment

All NTA versions

Cause 

This happens when using the egress or ingress ID as one of the queries. Some entities are blocked or filtered out when they are unrelated to the modifier selected, which in this case is Netflow Flows by history. This is by design and if you would like these entities filtered out so they are not available to display, a feature request can be submitted. 

Resolution

  1. Create a custom table.
  2. Select Netflow Flow By Interface History. You will only be able to use the columns for that Orion Object (Ingress Bytes, Egress Bytes, NodeID and InterfaceID).

 

 

 

 

Last modified

Tags

Classifications

Public