We do monitor node&alias table via SNMP on all enterasys devices with netdisco (postgre db). Netflow is more for Traffic analysis and reports about top talkers. If you need long term trend analysis i recommend using RRD-based tools like Cacti. This will let you graph any value you can get via SNMP or scriptable input.
Mit freundlichen Grüßen i.A. André Keller Informationssysteme Lokaler Betrieb und Support Volkswagen Original Teile Logistik GmbH und Co. KG Vertriebszentrum Nord Am Stammgleis 6 22844 Norderstedt Tel.: +49 (40) 52200-3211 Fax: +49 40 52200-3209 <http://www.volkswagen-otlg.de <blocked::http://www.volkswagen-otlg.de/> > ________________________________ Von: Pala, Zdenek [mailto:[email protected]] Gesendet: Montag, 19. Januar 2009 22:09 An: Enterasys Customer Mailing List Betreff: RE: RE: [enterasys] Best practice: Network information management Sorry for this flame & back to the original request. Netflow is not supported on C2 - device which was in original request. (unfortunately no cflow, qflow, sflow either). The request was (if I understand it well) just to know the mapping between port - mac - ip - vlan => node&alias table is exactly the right answer (unfortunately enterasys proprietary) Netflow can deliver much more, but just to know the mapping I do not have to use Netflow with SQL database... Zdenek P.S. Last comment from my side to this topic. ________________________________ From: Volker Kull [mailto: ] Sent: Monday, January 19, 2009 8:45 PM To: Enterasys Customer Mailing List Subject: AW: RE: [enterasys] Best practice: Network information management If you are using a switch or router with netflow, qflow, sflow capabilities you are able to see ALL traffic passing this device. For having a overview on the network the flow-data looking up to layer 4+ is enough. You can save this data on a database an you can analyse this data later on in reports or detailed searches of specific traffic. The key point is, that you have data of traffic on ALL interfaces at the same time. With snmp you can have a view only to one or few interfaces at the same time and there is no way to save data for a long period (weeks/months/years) and compare the different interfaces when ever you want and from what sight to the information you need ! Try it and see the advantages ! Ask me if you need help. Volker Volker Kull BELL Computer-Netzwerke GmbH Ohmstr. 6 - 76229 Karlsruhe (Germany) Tel: +49 721/6624993-0 Fax: +49 721/6624993-30 Email: [email protected] ________________________________ Von: Pala, Zdenek An: Enterasys Customer Mailing List Gesendet: Mon Jan 19 20:06:36 2009 Betreff: RE: [enterasys] Best practice: Network information management I just wanted to point that using Netflow does not have to be the best way as simply stated by Volker. I have not seen any CPU issue on Enterasys switches either, but on Cisco I have seen many. And with the sampling issue you will not see all traffic. That is my experience... The Netsitght compas tool is excelent if you search something. I agree with Nees that snmp graphs tell nothing, but Netsight can export the source address table and other sources like Node&Alias tables, where you see the records and history. You can use also DSCC with the feature of asset profiles, but use DSCC just for the this is wasting of money I believe. Regards Zdenek ________________________________ From: Matthias Nees [mailto:[email protected]] Sent: Monday, January 19, 2009 7:04 PM To: Enterasys Customer Mailing List Subject: AW: [enterasys] Best practice: Network information management Running Netflow on several HP / Cisco and Enterasys Switches did not tells us the fears of Pala. Netflow on Enterasys DFE Board is excellent - without any negative effects. Is is right that not all Switch does have netflow / c-flow / ... capabilities. And of course the Switch is consuming CPU power for building netflow packets. But the other side is that it is an excellent possibility to see whats going on on your network - without reading millions of wireshark lines (from your analyzer) or SNMP graphs that does not really tell anything. With kind regards, Matthias Nees ________________________________ Von: Pala, Zdenek [mailto:[email protected]] Gesendet: Montag, 19. Januar 2009 18:50 An: Enterasys Customer Mailing List Betreff: RE: [enterasys] Best practice: Network information management Netflow is CPU hungry, not supported on all products and sometimes it requires license. Based on my experience networking people do not want to run netflow because it will kill the CPU of their catalysts... Netflow on some Cisco devices is ususaly only sampling = you will not see all the traffic Regards Zdenek ________________________________ From: Volker Kull [mailto:[email protected]] Sent: Monday, January 19, 2009 1:33 PM To: Enterasys Customer Mailing List Subject: AW: [enterasys] Best practice: Network information management Using netflow ist the best way !! Volker Kull BELL Computer-Netzwerke GmbH Ohmstr. 6 - 76229 Karlsruhe (Germany) Tel: +49 721/6624993-0 Fax: +49 721/6624993-30 Email: [email protected] ________________________________ Von: [email protected] An: Enterasys Customer Mailing List Gesendet: Mon Jan 19 13:20:07 2009 Betreff: [enterasys] Best practice: Network information management Hi folks This question is not really Enterasys related but I hope I can get some feedback anyway. What is your approach to collect and maintain network information?! I actually think about how to get all the data from Layer 1 (i.e. C2 Switch, Cisco Firewall, WAN Accelerator etc) to Layer 2 VLANs to IP Subnets... Putting it in Word or Excel doesn't seems to be very helpful... buying an expensive IPAM software is also not an option... I gladly appreciate any input ;) Bye Tom -- Thomas Hofmann, System-/Networkadministrator, IT EB - Discover the Experience Visitors: Am Wolfsmantel 46, 91058 Erlangen, Germany Phone: +49 (9131) 7701 6969, mailto:[email protected] <mailto:[email protected]> Fax: +49 (9131) 7701 6333, http://www.elektrobit.com <http://www.elektrobit.com/> PGP-Key: http://keyserver.elektrobit.com <http://keyserver.elektrobit.com/> Elektrobit Automotive GmbH, Am Wolfsmantel 46, 91058 Erlangen, Germany Managing Director Otto Fößel Register Court Fürth HRB 4886 ---------------------------------------------------------------- Please note: This e-mail may contain confidential information intended solely for the addressee. If you have received this e-mail in error, please do not disclose it to anyone, notify the sender promptly, and delete the message from your system. Thank you. * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
