NMIS8 includes powerful capabilities for performance and operational thresholding, which greatly enhance network management capabilities.  These thresholds result in alerts/events/notifications which NMIS can send when it sees a threshold breached.  The thresholds have very granular controls which by default have been configured fairly broadly.

A list of standard thresholds NMIS includes is available in NMIS Threshold Configuration 

A  A simple example of this is that you will likely what need to be notified when the CPU is high on a Core device, vs an Access switch in Timbuktu.  This is part of the NMIS idea of relevance of information in general, not all devices are created equal, some devices deserve better alerting, people of course are created equal.

If you want to just modify and add new thresholds read the first section "Using the NMIS GUI to Configure Thresholds", the second section "About Threshold Controls" goes into more details about thresholds.

As always thanks to our commercial customers who support everyone who use NMIS8, including the creation of documentation and these great features, if you are interested in commercial support, please email contact@opmantek.com

Using the NMIS GUI to Configure Thresholds

NMIS 8.6 Example

Image Added

Select the Section to Modify

I have selected NMIS 8.6 Common-threshold.nmis to edit, we now just search for the "item" we want to change the threshold for.

Note: in older model formats e.g NMIS8.4 and before and in some older Modelling of devices you need to select the Nodes Model- file and the threshold section 

Image Added

Select the Threshold to Add a Controlled Select

In this example we will add a select section, which will be controlled to only work on a specific device named "meatball" and the interface is "Dialer1".  To do this we are going to hi-jack the threshold in the first position and edit the control.  This is because these selects are executed in order and we need ours to be first, this is like an access list on a router or firewall.  We will add another in position 10 when we are done.  I will also update the default models to have gaps in the orders.......

Image Added

Editing the Control

Now we just change the control to be the string "$node eq "meatball" and $ifDescr eq "Dialer1"" and click "Edit".

Image Added

A New Control is Available

Now we can tune the thresholds by clicking "edit" on the one we want to change,

Image Added

Changing a Threshold

Lets change the warning to be 65%, then click "Edit"

Image Added

Updated Threshold for Warning

Now the warning level is set to 65%

Image Added

Applying the Thresholds

The thresholds will be run on the next poll cycle or when they have been configured to run.  You can run them on demand from the command line, with the following command (meatball is my router here, so change for your device).

/usr/local/nmis8/bin/nmis.pl type=threshold debug=true node=meatball

Adding a New Select Block

Now we need to add back the one we hi-jacked.  So we add a new select block, click "add".

Image Added

Setting the Order and Thresholds

I am going to set this one as 10, it will happen after the others but before the default, complete all the details you require in the form and click "Edit"

Image Added

Adding a Control

We need to add a control field now, so on the new select section 10, click add

Image Added

Complete the details in the control "$ifSpeed <= 5000000 and $ifSpeed >= 1000000" and click add.

Image Added

New Threshold Select Added

Now we have the old hi-jacked threshold created anew ready for low speed thresholding.

Image Added

About Threshold Controls

Simple Thresholds

In NMIS a simple threshold is defined by the following:

• the name
• the event name (which must begin with the phrase "Proactive" for correct event handling)
• a select (with a default and optionally more)
• default threshold values

In the file /usr/local/nmis8/models/Common-thresholdsthreshold.nmis this looks like this:

'cpu' => {
  'item' => 'avgBusy5min',
  'event' => 'Proactive CPU',
  'select' => {
    'default' => {
      'value' => {
        'critical' => '70',
        'fatal' => '80',
        'minor' => '50',
        'warning' => '40',
        'major' => '60'
      }
    }
  }
},

Have a set of thresholds for Core CPU

...

Advanced Thresholds with Controls

...

These are executed in the select order, and if no control is matched, then the default set is used.

Advanced Control Options

The following are the available control options

...

• $name
• $node
• $host
• $group
• $roleType
• $nodeModel
• $nodeType
• $nodeVendor
• $sysDescr
• $sysObjectName

...

We have a feature in NMIS called threshold dampening, NMIS will only clear a threshold event when it passes the threshold + the dampening factor, this is configured with the configuration options threshold_rising_reset_dampening and threshold_falling_reset_dampening.

We added this feature because many times the threshold would drop a little, and clear the threshold, and then rise again, causing a new threshold event. So we provided an threshold clearing dampening factor to prevent the flaps.

There are two choices here, reduce the damping setting to a lower level, e.g. 1% which should be enough or disable the feature. You can edit this in the GUI it is in the section globals, or modify the Configuration directly nmis8/conf/Config.nmis

To reduce it to 1%, change the config values to be:

threshold_falling_reset_dampening = 1.01
threshold_rising_reset_dampening = 0.99

To disable it completely:

threshold_falling_reset_dampening = 1.0
threshold_rising_reset_dampening = 1.0