Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Don't see router on Netflow Source page

I see that NTA is receiving flows from one of our routers based on the events list. However, I cannot add the router under Netflow Sources, even when I change the "Showing" feild to All or Cisco. It appears NTA tries to only display routers, but it is showing several switches and our VPN concentrator, but not our 3825 I am trying to monitor. I have another 3825 that I am monitoring fine, but this one will not show up as an option in the sources list.

Any ideas on how to ad the router as a source?

Find more posts tagged with

Accepted answers

All comments

mcbridea

What is the message in the events resource saying?

willettea

"NetFlow Receiver Service [GPNETMON] is receiving a NetFlow data stream from an unmanaged interface on HostnameOfOurRouter. The NetFlow data stream will be discarded. Please follow the link HostnameOfOurRouter or use the Orion System Manager to add Interface '#23' in order to process this NetFlow data stream."

chris.lapoint

Have you added that router's interface to Orion NPM? If it's not managed by Orion NPM, you're not going to be able to monitor it as a NetFlow source.

JesperVestergaard

I have the opposite problem - Having a few routers i can´t get rid of...

These are provider managed, and i need to submit a cr to enable flow export - so i leave the flow enabled, and (would like to) diable the flow collection for theese devices.

However - regardless what i try, i can´t get rid of the devices in my flow collection.....

Go figure...

willettea

It finally showed up in as a Netflow source after about 24 hours and is working well now.