[mrtg] Re: organizing *.cfg files

[Henry Steinhauer]

?  What are the implications of putting each interface configuration into a
separate *.cfg file, as opposed to having one *.cfg file with multiple
interfaces described therein?


Well - It depends. -   What are you trying to do with the process ?

The biggest reasons I found for splitting CFG files are:

1 - Time to do an update -  By splitting I can do them in parallel  (But I
want to avoid one cfg per interface - perhaps 20 in one but not 100)
2 - Management of the cfg files -  Frame relay in one and the non-frame
relay in another.  Frame Relay tend to change CIR and I need to touch them.
3 -  One per Router even if the routers are all in the same campus
location.  Keeps updating simpler.

Henry






From: "Scheidel, Greg" <Greg_Scheidel at ed.gov> on 12/28/99 08:54 AM

To:   mrtg at list.ee.ethz.ch
cc:
Client:
Subject:  [mrtg] organizing *.cfg files




Here's a vague question.
What are the implications of putting each interface configuration into a
separate *.cfg file, as opposed to having one *.cfg file with multiple
interfaces described therein?
Greg S.

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:mrtg-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/mrtg







--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:mrtg-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/mrtg