Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

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

Tags

Classifications

Public