<HTML dir=ltr><HEAD><TITLE>[mrtg] Strategery for cfg file</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16525" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText77877 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>We do this with routers2 as the MRTG frontend (OK so Im biased).</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>With routers2, you get all the interfaces in the side menu, which helps, paritcularly if your default is the summary or info page. Have one cfg file per devices, and optionally use a master.cfg to include them all for MRTG's benefit only.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>You can enable the 'active' option on the summary pages, to suppress graphs for any interfaces with completely zero traffic, and simplify the summary.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>We also define userdefined summary graphs, stacked with total lines in groups of 8 ports, and then place these summary graphs into separate summary pages grouped by slot number.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>This minimises the links in the menu and makes it easier to follow.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>For multiple devices (we have several hundred) we use the grouping and subgroups in the Devices menu.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>See <A href="http://www.steveshipway.org/software">http://www.steveshipway.org/software</A> for routers2 and the demo system if you're interested.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Steve</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mrtg-bounces@lists.oetiker.ch on behalf of Peter Laws<BR><B>Sent:</B> Tue 28-Aug-07 6:05 AM<BR><B>To:</B> mrtg@lists.oetiker.ch<BR><B>Subject:</B> [mrtg] Strategery for cfg file<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Just last week, I started playing with MRTG (v2.14.5 on RHEL 5) for the<BR>first time in many years.<BR><BR>I've got a couple core routers, a dozen or so main floor switches, then<BR>bunches more odds'n'ends around the shop.<BR><BR>MRTG is working fine, but I need advice on how to manage configs. I dumped<BR>all the devices into one cfg file, ran indexmaker and voila .... a huge<BR>ugly page with hundreds and hundreds of ports! Not what I wanted but<BR>exactly what I specified. :-) Shouldn't it do what I mean and not what I<BR>said?<BR><BR>What I want is a page that has one link for each device showing its<BR>aggregate traffic. Click on the link, and I see the breakdown of each<BR>port. What is the best way to do that? Separate cfgs? A different set of<BR>options on indexmaker?<BR><BR>If this is a FAQ, please point me in the direction of answers ...<BR><BR>Thanks.<BR><BR><BR>--<BR>Peter Laws / N5UWY<BR>National Weather Center / Network Operations Center<BR>University of Oklahoma Information Technology<BR>plaws@ou.edu<BR><BR>-----------------------------------------------------------------------------<BR>+ Ranked 10th in PC Magazine's 2007 Top 20 Wired Campuses<BR>+ Computerworld 2006 100 Best Places to Work in IT<BR>-----------------------------------------------------------------------------<BR></FONT></P></DIV></BODY></HTML>