[mrtg] cfgmaker with template using SNMPv3 problems

[Dunc]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi folks,

I've been succesfully using cfgmaker to create me a config using
SNMPv3 for a while now, just for the standard interface graphs.

I'm now trying to create a host template to graph memory usage.

I've shamelessly ripped off the CPU template example from the cfgmaker
guide webpage and added the correct OID, I'm almost there apart from
the fact that it doesn't create the SnmpOptions line in the resultant
config file, and $router_connect doesn't contain my SNMP options string.

Even if I hack $router_connect in my template like this....

my $router_connect_with_SNMP_Options = $router_connect . "::2:1::3";

and then use as my target...

Target[$target_name]:
1.3.6.1.4.1.1991.1.1.2.1.53.0&1.3.6.1.4.1.1991.1.1.2.1.53.0:$router_connect_with_SNMP_Options


...when I run mrtg against the resultant .cfg file, it doesn't know to
use v3 and send a password etc. So it's got to be something to do with
cfgmaker as a whole not knowing to use v3 for this target, and thus
not creating the SnmpOptions line.

Also on the cfgmaker page is an example script that claims....

"This template file generates exactly the same configuration code per
interface as cfgmaker does by default, with the exception that it
eliminates all lines (comments as well as config code) for an
interface if the interface happens to be rejected."

But, seeing as how that template doesn't mention
SnmpOptions[$target_name] anywhere, I'm guessing that's not strictly
true.

Any help greatly appreciated.

Regards,

Dunc

- --
Duncan Lockwood
Network Team Leader

The Bunker Secure Hosting Limited       
Ash Radar Station
Marshborough Road
Sandwich
Kent CT13 0PL
UNITED KINGDOM

t: 01304 814 800
f: 01304 814 899
e: dunc at thebunker.net
w: www.thebunker.net
PGP on Key Servers
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkTPsQACgkQOZKi9YO9TB5DAgCeIdeVWe/qVDC1/gAtZIfK9oFp
rmMAnj5XcerZOkA/KV2y6NaQbKuSTxHf
=Mu3o
-----END PGP SIGNATURE-----