MRTG cfgmaker filter

[Tyler]

Hello all,

I'm wondering if there is a way to keep cfgmaker from scanning certain
interfaces. I have applied an if-filter within the cfgmaker command line,
but all that seems to do is filter the interfaces from being written to the
config file.

The example I'm speaking of is that I'm polling a large number of switches
that have alot of interfaces and even more vlans. I don't want to graph
VLAN traffic, I just want the interfaces. So I've filtered out
propVirtual(53) from being written to the config file, but it still scans
them. A typical switch takes about 10 minutes to poll. Times that by 3-400
and that's along time.

Any suggestions?
Tyler

[Hans Jørgen Jakobsen]

a) Convince your switch vendor to make an easy way of taking some interface types
out of a (snmp) view.
(HPOV takes long time demandpolling switches with many VLANs and creates a
lot of interface icons)
b) More efficient scanning/collection. (ie separate discovering the device and
collection)
/hjj

[Holger Petersen]

"Tyler" <tyler....@sjrb.ca> writes:

>Hello all,

>I'm wondering if there is a way to keep cfgmaker from scanning certain
>interfaces.

How often do you start 'cfgmaker'? I do it after a reboot of a router
or some config-change. For a switch, it's done only once here...

> A typical switch takes about 10 minutes to poll. Times that by 3-400
>and that's along time.

But only once a month, or?

AND if it really must be 'once a day', what about looking into the
source of cfgmaker? That's one of the benefits of *open* source!

just asking, Holger