...
A key concept with these features is to avoid running an update cycle for interfaces when changes are detected and to minimise the number of bulk walks NMIS does, most devices handle this no problem, but when there are slow SNMP engines or VERY high interface counts, optimisation is needed.
Below is the sample model which To configure these options, a 'custom' model section can be added to an NMIS model to use these feature, this section will describe each of the features in more detail the settings below are considered the defaults, as if the features were not presenta model. The 'custom' model section needs to be a top-level section, ie. on the same nesting level as '-common-' for example:
| Code Block |
|---|
%hash = (
'-common-' => {
# lots of lines skipped
},
'custom' => {
# the custom model options go here
},
# and the rest of the model follows here
'interface' => {
... |
An example custom section is shown below, which contains default settings, ie. as if the custom section was not present at all. You'll find a description of each of the features in more detail in the next sections.
Default Interface Handling Options
...
When enabled, the IP address table will not be updated when a single interface is being updated.
Model custom - interface - skipIfType skipIfDescr
Skip Interfaces is used for mega devices to get rid of unwanted interfaces. Big SP switches for example. If skipIfType or skipIfDescr regex is matched, then just skip this interface all together. Must be used with ifNumber = false, ifAdminStatus = false, ifLastChange = false, ifTableLastChange = false
For example, skip all the PPP interfaces on a DSLAM so you can monitor the Ethernet uplinks.
| Code Block |
|---|
'skipIfType' => 'ppp', 'skipIfDescr' => 'Virtual-Access|noSuchInstance' |