[mrtg] Strategery for cfg file
m_cadek at fraen.com
Mon Aug 27 21:43:05 CEST 2007
I have to agree, write your own HTML pages with links.
My main page shows my router graphs for all my locations as well as
every switch within each physical location, you can click on router
graph to go to mrtg page for that router, or click on each switch which
sends you to a page with 24/48/etc... Ports and each one can be clicked
on as well for more details.
- The switch page is simply a collection of 24 or 48 images with
descriptions (very simple HTML table).
- The actual port pages are of course generated by MRTG
This way you can easily drill down from higher interfaces down to every
From: mrtg-bounces at lists.oetiker.ch
[mailto:mrtg-bounces at lists.oetiker.ch] On Behalf Of david brett
Sent: Monday, August 27, 2007 3:19 PM
To: Peter Laws
Cc: mrtg at lists.oetiker.ch
Subject: Re: [mrtg] Strategery for cfg file
I did this by creating my own webpages with links to the mrtg pages.
Peter Laws wrote:
> Just last week, I started playing with MRTG (v2.14.5 on RHEL 5) for
> the first time in many years.
> I've got a couple core routers, a dozen or so main floor switches,
> then bunches more odds'n'ends around the shop.
> MRTG is working fine, but I need advice on how to manage configs. I
> dumped all the devices into one cfg file, ran indexmaker and voila
> a huge ugly page with hundreds and hundreds of ports! Not what I
> wanted but exactly what I specified. :-) Shouldn't it do what I mean
> and not what I said?
> What I want is a page that has one link for each device showing its
> aggregate traffic. Click on the link, and I see the breakdown of each
> port. What is the best way to do that? Separate cfgs? A different
> set of options on indexmaker?
> If this is a FAQ, please point me in the direction of answers ...
> mrtg mailing list
> mrtg at lists.oetiker.ch
mrtg mailing list
mrtg at lists.oetiker.ch
More information about the mrtg