Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > NetFlow data collection device no longer updating in sources or charts

NetFlow data collection device no longer updating in sources or charts

Created by Michael Almadova, last modified by Alexander Aguilar on Mar 14, 2018

Views: 1,790 Votes: 0 Revisions: 4

Overview

This article addresses the issue where a Cisco device that used to collect NetFlow data is no longer updating in NetFlow sources or charts when NetFlow data appears in Wireshark with proper template schema fields that are required for NTA to display the data.

Environment

  • NTA 4.1.1
  • Cisco devices

Cause 

This can occur when changes made on the device are not in sync with what is being polled in NPM.

Resolution

  1. Run List Resources on the device.
  2. Remove any unknown interfaces. 
  3. Change the device polling IP in NPM to the device export source that is being used to send the NetFlow to the collector. 
  4. Restart NetFlow services on the remote server and primary server. If it is all installed on one server, restart the NetFlow service in Orion Service Manager. 

 

 

Last modified

Tags

Classifications

Public