Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > Collect NetFlow data from a non-NetFlow compatible device

Collect NetFlow data from a non-NetFlow compatible device

Table of contents
Created by Niall Fitzgerald, last modified by MindTouch on Jun 23, 2016

Views: 1,010 Votes: 0 Revisions: 3

Overview

Some CISCO devices do not support the collection of Netflow Data due to limitations of the hardware. It may however still be integrated these devices into Netflow Traffic Analyzer, providing the device supports the use of SPAN sessions and the deployment of a 3rd-party Netflow-compatible probe. 

Environment

  • All versions of NTA
  • CISCO: Non-Netflow Compatible device

Steps

  1. Configure a SPAN session on the Non-Netflow compatible device to mirror critical interface traffic to the SPAN port.
  2. Deploy a 3rd-Party Netflow-compatible probe on the SPAN port to perform the Netflow analysis of the traffic received (nProbe, Flowmon, etc.)
  3. Forward the analyzed data to the Netflow Traffic Analyser for inclusion in reporting along with the remainder of the Netflow compatible estate. 

 

Last modified

Tags

Classifications

Public