[mrtg] Monitor 2 Interfaces on a router
pavouk at pavouk.org
Fri Aug 31 10:09:12 CEST 2018
much more simple variant is to use "cfgmaker" which is part of MRTG package.
You can call cfgmaker to your router and it generates MRTG configuration for
you. I am running them from a cron on all routers every night and it
regenerate configurations for them.
Advantage is that when you change configuration of routers that it is not
needed to do anything and every night is everything updated.
> The target "ID" if you will, is in the brackets . This has to be unique
> for the whole config file, and determines the file names of the output.
> In my experience, you can make it what you want. I'm experimenting with
> custom IDs out of a database.
> I bring this up because if the 172.31.254.254 graph works, then use that IP
> address instead.
> Try changing "Target[10.0.0.1]: 45:public at 10.0.0.1" to
> "Target[172.31.254.254_45]: 45:public at 172.31.254.254".
> You can also take the working graph and add _95 to the target ID. So
> "Target[172.31.254.254_95]: 95:public at 172.31.254.254"
> Edwin A Epstein, III
> Rhinobee Internet Services
> 707.237.7504 ext 209
> 707.737.0288 Mobile
> ----- Original Message -----
> From: "mrtg-request" <mrtg-request at lists.oetiker.ch>
> To: "mrtg" <mrtg at lists.oetiker.ch>
> Sent: Thursday, August 30, 2018 5:41:13 AM
> Subject: mrtg Digest, Vol 131, Issue 2
> The last two entries are the same devices. I am using different vlan
> gateways currently, but there are errors with the log pull for the vlan
> interface that I do not get with the mgmt vlan ip.
More information about the mrtg