[mrtg] How to setup the mrtg for monitoring more things

Steve Shipway s.shipway at auckland.ac.nz
Mon Aug 18 07:23:49 CEST 2008

>After installed and setup the mrtg with the Windows Server machine :
>Running :  perl cfgmaker public at xxx.xxx.xxx.xxx --global "WorkDir: c:\inetpub\mrtg" --output >mrtg.cfg
>Then the mrtg may be know ( Auto detect ) the snmp port of the Network INT ( Surecom-EP320G-TX->Family-Gigabit-Ethernet-NIC ) is 16777219, but what is the SNMPOID ?

This is not the SNMP port, this is the SNMP interface number.  You do not need to know the OID when you are monitoring network interfaces, as MRTG takes care of this for you.

>So, if this is the network traffic usage ( B/s ), then how can I create the following hardware >usage config file also ?

For these, you need to know the OIDs and configure the MRTG target definitions appropriately.  This can be complex and not all are necessarily supported by your system, and also not necessarily in a consistent manner (eg storage can re-enumerate itself if you insert a USB key)

The cfgmaker script only generates configuration files for network interfaces (unless you use templates, but that's a bit advanced for you at the moment)

>"We use the nsclient agent under windows and the mrtg-pnsclient.pl script to query it instead of using SNMP" ???

This is a different way to obtain information, using a data collection plug-in rather than SNMP.  You can read about how to do this in the MRTG manual (you've looked at this, right?).  If you obtain the Routers2 frontend, in the extras directory are the query tools and some instructions on how to use them.

>Sorry, would you mind give me more help ?
>All of the OS is Windows 2000 Server...

The best thing for you to do is to initially try installing configuration just for network interfaces, and get this working correctly before trying to monitor something more complex like server statistics.  Once you have network stats working, and you have fully read the MRTG configuration manual plus all the help on the website, you should be ready to configure to monitor other things


More information about the mrtg mailing list