Yeap! Thank you Adrian! It is really my fault do not look at the man pages! :(
2012/3/7 Adrian Popa <[email protected]>: > Sure it is. > > man nfdump: > > Router IP > router ip <ipaddr> > Filter the flows according the IP address of the exporting > router. > > Also, you can export to different ports and have multiple entries in nfsen > (each router exports to a different UDP port) and you won't need filtering > by router ip. > > On Wed, Mar 7, 2012 at 1:20 PM, Tiago Flôres <[email protected]> > wrote: >> >> I am not aware of this "router ip" syntax. This is very useful expr >> but it doesn't exist in the manuals?!?! >> >> Thanks all of you for the answers! >> >> Cheers >> >> Tiago >> >> >> 2012/3/7 Adrian Popa <[email protected]>: >> > Also, you can edit your filters to take into account the exporter router >> > ip >> > and input/output interface indexes when you count traffic for a prefix. >> > Something like >> > >> > router ip ip_of_router1 and in if snmp_index_of_input_interface and src >> > ip >> > 1.2.3.4 and dst net 5.6.7.0/24 >> > >> > >> > >> > On Tue, Mar 6, 2012 at 7:23 PM, Tiago Flôres <[email protected]> >> > wrote: >> >> >> >> Dear colleagues >> >> >> >> I have eight routers exporting flow to one source (I am not sure if it >> >> is the best scenario) or should I have each router exporting flow to >> >> own source (router1 -> source1, router2 -> source2, ...). One of these >> >> routers is a mpls concentrator and the others seven are peers, like >> >> clients. The concentrator is where the servers are installed. The >> >> network traffic are mostly destinated to the main site (router1) which >> >> has 34Mbps mpls bandwidth. >> >> >> >> I am using DST NET and SRC NET to classify the traffic for down and >> >> upload directions. The thing is I've been getting discrepancies in >> >> traffic graphs. The main site where I've 34Mbps 'physically limited' >> >> is showing me up to 90 Mbps in nfsen graphs. >> >> >> >> Remembering that I have eight routers exporting to one source. In this >> >> among of flows I am trying to analyze and identify the traffic which >> >> goes to router1, but the traffic graphed is much more than the >> >> interface is able to support. >> >> >> >> The flows are from all interfaces of all routers? LAN and WAN? >> >> >> >> By default nfsen aggregates identical network traffic? Or could the >> >> flows are not been aggregated? >> >> >> >> I am guessing around .... the same traffic which ingress in router1 >> >> WAN is arriving in router1 LAN interface, what about it? >> >> >> >> Thanks in advance for any explanations >> >> >> >> >> >> Hugs >> >> >> >> Tiago >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Keep Your Developer Skills Current with LearnDevNow! >> >> The most comprehensive online learning library for Microsoft developers >> >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, >> >> MVC3, >> >> Metro Style Apps, more. Free future releases when you subscribe now! >> >> http://p.sf.net/sfu/learndevnow-d2d >> >> _______________________________________________ >> >> Nfsen-discuss mailing list >> >> [email protected] >> >> https://lists.sourceforge.net/lists/listinfo/nfsen-discuss >> > >> > >> >> >> ------------------------------------------------------------------------------ >> Virtualization & Cloud Management Using Capacity Planning >> Cloud computing makes use of virtualization - but cloud computing >> also focuses on allowing computing to be delivered as a service. >> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> >> _______________________________________________ >> Nfsen-discuss mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/nfsen-discuss > > ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Nfsen-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
