Page History

...

• Model file caching was added for improved performance
  If you are making model changes you will have to run a type=update operation to refresh that cache.

• nmis type=update has new force=true option
  If set, all existing node information (except RRD databases) is ignored and the node status is reinitialized completely from scratch.

• The interface speed limit enforcement is now configurable
  NMIS has long supported to ignore invalid or nonsensical interface counters, but  in version 8.6.0 this is an automatic standard feature.
  Every nmis type=update operation now automatically enforces all (new or modified) interface limits, by updating the RRD file limits according to the selected enforcement policy.
  The Node Configuration GUI lets you set the desired enforcement limits: option off disables limits for the given interface, option normal (which is the default) sets the limit to 2 times  the configured interface speed, while option strict sets the limit to be precisely the configured interface speed.

• All Down events now include outage information for easier external consumption
  The event details will include text similar to this example: outage_current=true change='comment from the outage setup'

• SNMP Version 3 support was improved, and SNMP V3 Contexts are now supported.

• SNMP error handling was improved for greater ease of use
  In the past, errors related to SNMP data not fitting into a single packet ("message size exceeded") were terminal and required the user to adjust the node configuration, trading off robustness against speed.
  NMIS 8.6.0 handles this situation automatically and sensibly: if such an error is encountered, then the issue is logged, then NMIS automatically reduces the "maxrepetitions" parameter and retries the request. If the request with the reduced parameter works, NMIS caches that parameter setting for the remainder of the SNMP session lifetime. Up to four back-off and retry iterations are attempted before NMIS gives up.

• Role types, Node types and Network types are now fully customizable
  In the past there were two or three hardcoded choices for each of these, and NMIS' internal logic depended on particular values.
  This is no longer the case. You can use the Configuration GUI to edit, replace or add new values for each of these properties.
  There is one minor caveat: in earlier versions SNMP service checks were only performed for nodes with nodeType "server", but now they are attempted for any node that has such service checks configured. If your device does not support the Host-Resources MIB but is (mis-)configured for SNMP service checks, then you will receive nuisance SNMP Down events (distinguishable by the event detail info saying something like "get SNMP Service Data: The requested table is empty or does not exist"). The solution is to deconfigure SNMP service checks for this  node.

• Better integration of plugin code and main SNMP functions
  All plugins now  use the improved standard SNMP code, which makes extending plugins much simpler.

• Better control over retaining of historic,closed events
  If the new option keep_event_history is set to false then NMIS cleans up old closed events immediately. Default is true, i.e. old  events are kept for archival purposes until the purging policy causes their cleanup.

• Improved purging of old files
  The nmis file cleanup script was removed (as being too brittle and inflexible), and a new operation type=purge was added to nmis.pl. This operation is much more precise and reliable, and also supports the option simulate=true, where it only shows candidate files for purging without making any changes.

• The content of  test emails was improved.
• Improved webtest Service test program
  The webtest script now supports https better, also offers explicit proxy selection, and can optionally make its requests with caching off.  In addition to that, the size of the response data is now reported to (and stored by) NMIS.
• Some new Service test programs
  For example NMIS now ships with a test program for testing Citrix Netscaler logins.
• Service tests can now run at custom frequencies, independent of the collect cycle
  (This does not apply to SNMP-based services, which are always and exclusively tested during a collect operation.)
  NMIS now honors your choice of service Poll Interval configuration, and the service will be tested no more frequently than requested.
  Service tests are performed as part of the collect cycle, but you may enable a more frequent type=services operation in the standard NMIS cron snippet.
  RRD parameters are adjusted to suit the service frequency, but only on service creation.
• SNMP-based service tests now offer improved precision,  flexibility and robustness.
  It is now possible to check particular process instances, based on their command line arguments. Besides that, all instances of a given process are considered (instead  of just the last listed process as in the past). SNMP errors for a node no longer produce spurious service down events.

• reporting of the interface availability of  a down interface is now configurable
  The  new configuration option interface_availability_value_when_down can be used to store the value 0 instead of the default value "U(ndefined)". This applies to interfaces that are down, and affects RRD and the graphing: RRD ignores periods where the value was "U", doesn't draw anything for such periods and the overall figures (in the legend) are also automatically based on just the non-U(ndefined) periods. On an interface that is down for a long time this may lead to certain legends reading "N/A" or "NaN". If this is undesirable, the value 0 can be saved in such cases.

• NMIS now automatically ignores interfaces that have been down for N days or more
  The new config option global_nocollect_interface_down_days (default: 30) controls whether NMIS should stop attempting to collect interfaces that have been down for more than N days.

• Multiprocessing behaviour can now be controlled from the configuration file
  The mthread and maxthreads commandline arguments now have corresponding configuration items nmis_mthread (default: false) and nmis_maxthreads (default: 10), and the maxthreads arguments have been removed from the default Cron snippet. If your environment requires greater parallelization you can now simply update the nmis_maxthreads configuration option and all NMIS operations will honor that setting. (As always, options passed on the command line override the configuration options.)

...