I don't recall having to use different UDP port numbers when exporting to Cisco Lancope Stealthwatch. It was able to differentiate traffic based on the source IP the traffic was coming from. I think the limitation may be due to PRTG. Unique port numbers for every device doesn't seem like it would scale.
Agreed, I find the same with solarwinds and liveaction. I think it's a limitation to what he has been using. It should be able to tell based on source IP like you're saying.
Great video idea. With everyone working from home, we have been setting up and monitoring Netflow much more in the last few weeks to watch traffic and warn high bandwidth users. Much easier to do on switches and routers than ASA’s I have found though.
hello Jeremy...first thanks for this wonderful video....but I have question which bother me currently regarding two features....NBAR2 vs Netflow...I can see they are very similar ....what is your suggestion on this one...
I found your guidance for using separate port numbers per device sending netflow interesting. Normally I will set a source ip / interface on the device sending netflow and have the monitoring software set to receive from that ip address. From a management perspective it is a much cleaner approach, we usually send from the management interface for the device, which is already documented as part of the overall monitoring solution. With using separate port numbers per device, I could see another excel spreadsheet getting messed up. Any benefits or downside besides these that you see between the two methods?
I am confused on the part about the port number. We setup netflow from TONS of our devices into PRTG. We have been using port 2055 for all of them. It appears to be working fine, but the video states each device should be using a different port? Can you clarify?
Interesting; that recommendation comes from seeing the data merge in a couple different scenarios - I'll dig a little and see if it's still an issue. Thanks for the heads up!
Just saw this on a quick google...but very old article; sounds like the issue no longer exists: kb.paessler.com/en/topic/5673-do-i-need-to-use-a-separate-port-for-each-netflow-sensor
Thanks for the video but are you sure about using different port number for each NF device!! at work I'm using the same port I think and my netflow server shows them in different graphs and correctly! I'm using another app and not PRTG
Interesting; that recommendation comes from seeing the data merge in a couple different scenarios - I'll dig a little and see if it's still an issue. Thanks for the heads up!
* Volume is a bit low * How about ENARSI? I suppose this will be heavy on labs/sims because on the blueprint is tons of "troubleshoot". This could be a reason why ENCOR is a question-only exam
Can you do a video on physical lab set up vs. Virtual Lab options like Virl or GNS3? Im starting my study for CCNP and finding resources lacking. Im having a hard time choosing between a physicall lab and virtual.
RedefinedOne both are good, however you are’s going to understand SFP’s and fiber types, etc from a virtual lab. You may not even know what a GBIC or SFP is until you have physical equipment and out in the field. Same goes with understanding port status and led indicators and watching ports for collisions etc. There deff is a value in physical equipment as you will understand more out in the field.
Jeremy is such a great teacher.... Kudos Jeremy!
Enjoy your teaching style. Can’t wait till your done with the Encor tutorial then will sign up with CBT nuggets
I don't recall having to use different UDP port numbers when exporting to Cisco Lancope Stealthwatch. It was able to differentiate traffic based on the source IP the traffic was coming from. I think the limitation may be due to PRTG. Unique port numbers for every device doesn't seem like it would scale.
Agreed, I find the same with solarwinds and liveaction. I think it's a limitation to what he has been using. It should be able to tell based on source IP like you're saying.
This dude is awesome.
damn, he is awesome. Going for my ccnp, thanks for so much!
Great video idea. With everyone working from home, we have been setting up and monitoring Netflow much more in the last few weeks to watch traffic and warn high bandwidth users.
Much easier to do on switches and routers than ASA’s I have found though.
Awesome, when can I expect this course to be released by CBT nuggets?
hello Jeremy...first thanks for this wonderful video....but I have question which bother me currently regarding two features....NBAR2 vs Netflow...I can see they are very similar ....what is your suggestion on this one...
I found your guidance for using separate port numbers per device sending netflow interesting. Normally I will set a source ip / interface on the device sending netflow and have the monitoring software set to receive from that ip address. From a management perspective it is a much cleaner approach, we usually send from the management interface for the device, which is already documented as part of the overall monitoring solution. With using separate port numbers per device, I could see another excel spreadsheet getting messed up. Any benefits or downside besides these that you see between the two methods?
Jeremy, if we have multiple vrf on one cisco router, do we need to assign different ports to each vrf or one udp port number will suffice ?
Thank you so much
First like,. Then watch,,, Thank You Sir,,, Fan Love😇
Any Idea when CBT nuggets ENCORE will be published?
I am confused on the part about the port number.
We setup netflow from TONS of our devices into PRTG. We have been using port 2055 for all of them. It appears to be working fine, but the video states each device should be using a different port?
Can you clarify?
Interesting; that recommendation comes from seeing the data merge in a couple different scenarios - I'll dig a little and see if it's still an issue. Thanks for the heads up!
Just saw this on a quick google...but very old article; sounds like the issue no longer exists: kb.paessler.com/en/topic/5673-do-i-need-to-use-a-separate-port-for-each-netflow-sensor
Thanks for the video but are you sure about using different port number for each NF device!! at work I'm using the same port I think and my netflow server shows them in different graphs and correctly! I'm using another app and not PRTG
Interesting; that recommendation comes from seeing the data merge in a couple different scenarios - I'll dig a little and see if it's still an issue. Thanks for the heads up!
* Volume is a bit low
* How about ENARSI? I suppose this will be heavy on labs/sims because on the blueprint is tons of "troubleshoot". This could be a reason why ENCOR is a question-only exam
have you any VXLAN video tutorials?
Can you do a video on physical lab set up vs. Virtual Lab options like Virl or GNS3? Im starting my study for CCNP and finding resources lacking. Im having a hard time choosing between a physicall lab and virtual.
RedefinedOne both are good, however you are’s going to understand SFP’s and fiber types, etc from a virtual lab. You may not even know what a GBIC or SFP is until you have physical equipment and out in the field.
Same goes with understanding port status and led indicators and watching ports for collisions etc.
There deff is a value in physical equipment as you will understand more out in the field.
Greetings from Kosovo
You meant kokomo by the beach boys lol
port numbers in hex 😰
4th of April 2020:
Currently there 6 Million unemployment in USA.