All these things are good also i suggest: measuring TX packets on one end and RX packets on the other end of a link is a good indication of the quality of the link. Using NTP + nanosleep to get hyperaccuate readings helps spot small problems quickly. Even using asyncronous readings will spot a sketchy link given enough time.
disparity of MTU/MRU is also a problem, but it normaly results in catastrophic failures that show up in other ways first. again all the usuall rants that hubs surpass unmanaged switches for most networks. On Mon, 26 Jun 2006, jeff vier wrote: > Date: Mon, 26 Jun 2006 13:10:04 -0500 > From: jeff vier <[EMAIL PROTECTED]> > To: "Pavleck, Jeremy D." <[EMAIL PROTECTED]> > Cc: [email protected] > Subject: Re: [Nagios-users] Network Monitoring? > > On Mon, 2006-06-26 at 13:00 -0500, Pavleck, Jeremy D. wrote: >> Greetings, >> This may be an odd question, considering my title is Network Engineer - >> but I'm the monitoring guy, and am going to setup a new instance of >> nagios dedicated to the network side of things - so simple question, >> what should I monitor as a general rule on each switch? Router? > > Here we monitor: > CPU Load > IOS Version > Input Errors > Ping > SNMP Traps > Uptime > Various interface statuses > All interfaces' bandwidth via MRTG > I have made this tar.bz2 longer (-6), because I lacked the cycles to make it shorter (-9). Robin-David Hammond KB3IEN www.aresnyc.org. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
