Cheshire Cat Software

Frequently Asked Questions

General
What is cfgmaker?
cfgmaker is a utiltity, distributed with MRTG, which helps to generate configuration files by polling the device using SNMP and probing for network interface information.

What are templates?
Templates are snippets of Perl code, which allow you to modify the configuration output by cfgmaker to customise it in some way, such as to add the additional Routers2 directives. These are run for each network interface which is detected on the device.

What are host templates?
Host templates are snippets of Perl code, which specify additional configuration output to be added for the device. This can allow you to add CPU monitoring for a switch, for example. These are run once for each device.

What are filters?
Filters are Perl expressions which allow you to define new rules to decide if a given interface should be included in the configuration file or not. The default is to include all interfaces which are not loopback and have a valid speed defined, but you may also wish to exclude dialup interfaces, for example.

Filters
How do I use a filter?
Add the following option to the cfgmaker command line for some filter code 'xxx':

Why would I want to use filters?
You may wish to automatically exclude some interfaces from monitoring, or certain interface types, such as dial-up interfaces.

Templates
How do I use a template?
Add the following option to the cfgmaker command line for a template file xxxx:

Why would I use a template?
By using templates, you can redefine the way the configuration script is output. For example, to add extra Routers2-specific directives.

Host Templates
How do I use a host template?
Add the following option to the cfgmaker command line for a template file xxxx:

What is the difference between templates and host templates?
Templates are run for each interface on the device. Host templates are run once for the device itself and do not relate to any interface.

Why would I want to use a host template?
Thes can allow you to add additional non-interface items to the monitoring if they are available via SNMP, such as CPU monitoring.