[mrtg] cfgmaker support for Watchguard devices?
Edwin A. Epstein III
ed at rhinobee.com
Sat Jan 6 22:46:23 CET 2018
Hi Mr. Nilsen,
Unfortunately, you may need to have your own custom cfgmaker. We use a lot of custom gauges and only find cfgmaker useful for "advice" on bandwidth graphs. All of our MRTG target configurations are created by custom code that facilitates it. Cfgmaker gets it right most of the time for most devices. In other cases though, you need to know how to construct your own target definitions and options.
This sounds like a one-off situation that cfgmaker could handle, but I don't know whether or not you could get them to alter cfgmaker for you. It might be easier to construct your own target lines, and it sounds like you already know the OIDs you need to use. I highly recommend the MRTG book (got the hardcover), and all of it is available online.
Edwin A Epstein, III
Rhinobee Internet Services
707.237.7504 ext 209
----- Original Message -----
From: "mrtg-request" <mrtg-request at lists.oetiker.ch>
To: "mrtg" <mrtg at lists.oetiker.ch>
Sent: Saturday, January 6, 2018 3:00:03 AM
Subject: mrtg Digest, Vol 125, Issue 2
Send mrtg mailing list submissions to
mrtg at lists.oetiker.ch
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
mrtg-request at lists.oetiker.ch
You can reach the person managing the list at
mrtg-owner at lists.oetiker.ch
When replying, please edit your Subject line so it is more specific
than "Re: Contents of mrtg digest..."
1. cfgmaker support for Watchguard devices? (Morten Nilsen)
Date: Fri, 5 Jan 2018 15:46:18 +0100
From: Morten Nilsen <morten at runsafe.no>
To: mrtg at lists.oetiker.ch
Subject: [mrtg] cfgmaker support for Watchguard devices?
Message-ID: <232e433f-bd2a-785a-849a-a6470040aa81 at runsafe.no>
Content-Type: text/plain; charset=utf-8; format=flowed
I've been using MRTG for years, in combination with PHP Weathermap to
monitor our infrastructure, and it works great!
But I've recently run into a bit of a snag with our firewalls, as I was
looking into automating weathermap configuration.
When I run cfgmaker on a firewall, it fails to connect the IP
information to the proper interface, instead generating configuration
### Interface 16 >> Descr: 'No-Description' | Name: 'No Name' | Ip:
'10.61.1.1' | Eth: 'No Ethernet Id' ###
### The following interface is commented out because:
### * got 'No counter exists for 16' from interface when trying to query
### * --ifref=name is not unique for this interface
# Target[wg-jessheim_16]: 16:... at wg-jessheim::60:5::2
# SetEnv[wg-jessheim_16]: MRTG_INT_IP="10.61.1.1"
### Interface 131112 >> Descr: 'vlan40' | Name: 'vlan40' | Ip: 'No Ip' |
Eth: 'No Ethernet Id' ###
Target[wg-jessheim_vlan40]: #vlan40:... at wg-jessheim::60:5::2
SetEnv[wg-jessheim_vlan40]: MRTG_INT_IP="No Ip" MRTG_INT_DESCR="vlan40"
I reported this to watchguard, but got this response:
> In 12.0.1, changes were made to net-snmp to enable fixed OIDs for
> In previous versions, these values could change on reboot, which had
the potential to break SNMP polling of specific interfaces.
> After this change, the OIDs of specific interfaces start at 65536.
For example, getting link speed on eth0 would use OID
> The cfgmaker script appears to make some assumptions about how these
OID values are mapped
> and it seems to try using information returned by OID
22.214.171.124.126.96.36.199.1.1 (ifindex) to generate specific queries for each
> The problem with this is that these values do not map to the same
values used in the fixed OIDs,
> and causes cfgmaker to fail when retrieving some of the data for the
> The only real solutions here would be to either create a custom
script to properly parse data returned by snmpwalk
> when querying the Firebox and generate an MRTG configuration file
based on it or modify the cfgmaker script to do this.
I would prefer to not run my own custom version of cfgmaker, so was
wondering if this might get fixed upstream somehow?
Subject: Digest Footer
mrtg mailing list
mrtg at lists.oetiker.ch
End of mrtg Digest, Vol 125, Issue 2
More information about the mrtg