The way we achieve this is for the network admins to put the connected host name into the port description on the switches. Then, cfgmaker pulls out the port description which is placed in the Target definition for the link names and titles and so on. It also allows our snazzy config tool to parse through the links and putt Routers2 crosslinks between the Targets to link the port graphs and the host graphs, but you'd have to take care of that yourself.
Steve ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lyle Giese Sent: Tuesday, 5 August 2008 08:58 To: [email protected] Subject: Re: [mrtg] (no subject) Rodge Stumbaugh wrote: I am new to mrtg. The previous network admin setup a network bandwidth monitoring application using mrtg and I noticed that most of the ,monitoring is through the switch port that the servers are connected to..is this the best practice? Also, if I want to make changes to correct where I see that several servers are no longer in service and some servers have been assigned to different ports than what is set up in mrtg, is it easier to change the inc files and the html for the monitoring site or is it better to accomplish this through the config maker? Thanks, Rodge ________________________________ _______________________________________________ mrtg mailing list [email protected]<mailto:[email protected]> https://lists.oetiker.ch/cgi-bin/listinfo/mrtg Config maker will setup monitoring for the ports on the switch, but it won't have a clue as to what is attached to which port on the switch. You need to hand edit the files made by config maker for that information. Includes are better than one big mrtg.cfg file, esp if you grow and decide to use routers2cgi and rrd later. Lyle Giese LCR Computer Services, Inc.
_______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
