What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Ingress and Egress NetFlow from same interface?

Votes:

0

I'm running NetFlow v9 on a Cisco router. The router supports adding multiple flow statements to the same interface. So I have 4 statements, 2 for IPv4 ingress/egress and 2 for IPv6 ingress/egress. Checking to see what is exported I can see that ingress/egress for both protocols are being exported. PRTG doesn't seem to pick this up though. For one it only shows IPv4 Egress when I have all four commands on the interface. I can't seem to find any documentation stating if PRTG is directionally aware or not.

cisco netflow prtg

Created on Mar 28, 2014 8:12:34 PM



9 Replies

Votes:

0

Hello,

thank you very much for your KB-Post. PRTG does not differ between in- and outbound traffic on Flow and/or Sniffer-Sensors. It will show the traffic type, as in protocols used. And then in the Toplists the sources and destination of the streams. You could check the Toplists for the directions of specific streams, if they are inbound or outbound. But it's not shown on the sensor result as on a SNMP Traffic Sensor for example.

best regards.

Created on Apr 1, 2014 10:27:47 AM by  Torsten Lindner [Paessler Support]

Last change on Dec 2, 2021 10:19:43 AM by  Maike Guba [Paessler Support] (2,404) 2 1



Votes:

0

Ok that helps. After looking a previous post I found that IPv6 isn't supported for NetFlow, that was awhile ago. Any ideas if that has changed? I also noticed that a custom top list for AS Destinations that I made doesn't populate. It just says 100% Other. Does that mean they vary so much that it can't determine a top 100 or do I need to setup something differently?

Created on Apr 1, 2014 1:14:05 PM



Votes:

0

IPv6 for Netflow is still only on the wishlist I'm afraid. I will count your vote for it!
Custom Toplists with the AS-Fields are a bit tricky, can you please try including maybe source & destination - IP -fields? Does it then show the AS column in the Toplist?

Created on Apr 1, 2014 2:58:00 PM by  Torsten Lindner [Paessler Support]



Votes:

0

So I added Source/Destination IP to my list which already had Source/Destination ASI. The list now shows several entries with Source/Destination IP but the AS fields show a "0" in both Source/Destination ASI columns.

Created on Apr 1, 2014 3:11:53 PM



Votes:

0

Just to check, did you create this Toplist anew? It might be, that the sending device doe snot send AS information. Can you please enable the sensors function to write a "Log Stream Data to Disk" for all data. Please then check the according CSV, if AS-information is included.

Created on Apr 1, 2014 4:25:25 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Yes this is a new Toplist. The sending device should be sending, it is a Cisco router and I setup what was suggested in the guides. One thing to note is that with the logging on for the sensor I can't see that the file gets created anywhere. I used the two below links for reference. My understanding is that it should be under C:\Program Files(X86)\PRTG Network Monitor\, however I don't have a Stream Log folder. Did this move and I'm reading something out of date?

https://www.paessler.com/knowledgebase/en/topic/463-how-and-where-does-prtg-store-its-data https://www.paessler.com/knowledgebase/en/topic/3223-where-is-the-log-stream-data-to-disk-for-debugging

Created on Apr 1, 2014 7:05:07 PM



Votes:

0

The files will be with the Program Data not with the Program Files. i.e. "%programdata%\Paessler\PRTG Network Monitor"

Under that folder you should see a folder called StreamLog and the files should be there.

Created on Apr 3, 2014 12:21:06 PM by  Greg Campion [Paessler Support]



Votes:

0

I appear to have gotten the AS information to work. The issue appears to be router related. My 7606S's seem to work fine with an AS Toplist. My ASR9K's don't seem to want to work. I'm going to open a TAC case and see what they have to say about it. It's got all the configs needs according to the setup guide.

Created on Apr 3, 2014 1:44:33 PM



Votes:

0

Thanks for letting us know and if you find a solution, please post it here!

Created on Apr 4, 2014 10:49:42 AM by  Greg Campion [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.