Hi Tim, What I did was to split the switch configs up and then arrange by floor of the building they're on, with a separate one for the backbone in the server room.
Set up a generic header with the stuff that's common to all switches (location of log files, images, etc), then use the INCLUDE directive to include the switch specific stuff. E.g. Akl_backbone_switches.cfg # Created by Craig HtmlDir: /var/www/mrtg ImageDir: /var/www/mrtg/images LogDir: /var/mrtg/work RunAsDaemon: no ### Global Defaults # to get bits instead of bytes and graphs growing to the right Options[_]: growright, bits, nobanner WithPeak[_]: wmy # Backbone only Include: /var/mrtg/configs/AKLSW368.inc Include: /var/mrtg/configs/AKLSW369.inc --------------------------------------------------------- AKLSW368.inc ###################################################################### # System: AKLSW368 # Description: Cisco Internetwork Operating System Software # IOS (tm) C2950 Software (C2950-C3H2S-M), Version 12.0(5.3)WC(1), MAIN TENANCE INTERIM SOFTWARE # Copyright (c) 1986-2001 by cisco Systems, Inc. # Compiled Mon 30-Apr-01 07:56 by devgoyal # Contact: # Location: ###################################################################### ### Interface 2 >> Descr: 'FastEthernet0/1' | Name: 'Fa0/1' | Ip: '' | Eth: '00- 08-e3-25-2a-41' ### Target[10.9.50.68_2]: 2:[EMAIL PROTECTED]: SetEnv[10.9.50.68_2]: MRTG_INT_IP="" MRTG_INT_DESCR="FastEthernet0/1" MaxBytes[10.9.50.68_2]: 12500000 Title[10.9.50.68_2]: Traffic Analysis for Uplink to Aklsw360 -- AKLSW368 PageTop[10.9.50.68_2]: <H1>Traffic Analysis for Uplink to Aklsw360 -- AKLSW368<H1> <TABLE> etc Hope that helps. Whether you use these "master" cfg files to run MRTG, or set up separate groupings, is up to you. You have to be a bit careful if you starting using routers.cgi or 14all.cgi, as I don't think they handle multple levels of INCLUDEs or something (I tried it a long time ago and ran into trouble, but I must revisit again at somepoint) Later'ish Craig > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Tim Holmes > Sent: Wednesday, October 20, 2004 9:55 AM > To: [EMAIL PROTECTED] > Subject: [mrtg] Monitoring Multiple Switches > > Hello All, > > Once again thanks to all who helped me get MRTG up and running, it is > totally great!!! > > As I am continuing to implement MRTG, I am facing somewhat of a > congestion problem on the index page. By the time that I have MRTG > fully implemented, I will be monitoring almost 300 ports of on 8 > switches around the building. Obviously that is quite a few to handle > on one screen. What I would love to do is to break it up > with a central > page listing each switch, that is a link to be clicked to access the > typical MRTG page for that switch. > > To do this, I don't think poses a huge problem, what I > anticipate doing > is creating a separate folder for each switch, and routing the > indexmaker command output to that folder. > > The problem that I am not sure of is the only way that I have seen the > indexmaker command implemented is to have multiple configuration files > in the command line for it, which presents a problem unless it is > possible to call more than one instance of Indexmaker. Or some such > thing. Once I get the pages being generated within the > proper folders, > I am planning to construct a cool looking front page for the > whole thing > (no problem, I do web stuff all the time). > > If someone could please enlighten me on how to get it > creating different > output in different folders at the same time, I would be most > appreciatative. > > TIM > > > Tim Holmes -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
