Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA 4.2.3 Administrator Guide > Get started with NTA > Reasons not to export both ingress and egress NetFlow traffic data

Reasons not to export both ingress and egress NetFlow traffic data

Table of contents
No headers

Flows carrying NetFlow traffic data enter a device through an ingress interface and leave the device through an egress interface. For more information, see Monitor traffic flow directions on page 1.

If you export both ingress and egress data for all interfaces, you will get the same data twice: once as ingress data entering the device, and once as egress data as the flow leaves the device.

If you configure exporting ingress data on some interfaces and exporting egress data on other interfaces, the data shown by SolarWinds NTA may be inconsistent.

We recommend that you configure exporting either ingress or egress data to prevent SolarWinds NTA from showing misleading traffic data.

 
Last modified
06:33, 13 Apr 2017

Tags

Classifications

Public