...

• The node dashboard widgets and graph drill-ins now load substantially faster,
  and graph files are now cached for up to 60 seconds (configurable via graph_file_maxage config item).
• SNMP Uptime counter wrapping (at 497 days) is now handled more robustly.
• The logic for group display/exclusion in the GUI widgets was repaired,
  and now only nodes belonging to the configured groups (in group_list) are displayed.
  (Like before, all active nodes are handled by the polling and event engine, regardless of group membership.)
• The handling of node resets and long-term unpollable nodes is now more robust and reliable.
• The Polling Failover feature was extended to provide more fine-grained events and node states.
• NMIS now provides a configurable rule for acceptable node names (using the config item node_name_rule) which is consistely applied everywhere;
  the shipped default rule was also relaxed and now allows letters, numbers, space, underscore, hyphen and dot.
• NMIS now supports WMI polling in windows domains more robustly and username and domain can be provided in multiple formats.
• Various modelling improvements, e.g. the nocollect directive is now supported in systemHealth model sections.
• New and improved devices support for Nexus 7k, Adtran, Cisco, Arista, Mikrotik, Netvanta, PulseSecure, Juniper.
• admin/node_admin.pl now supports bulk export and import..
• Various robustness improvements, e.g. in fpingd.pl, more fine-grained logging, more flexible and precise polling candidate timing decisions.

NMIS 8.6.7G Erratta

If you are installing NMIS 8.6.7G and you have a busy server, then it is important that you modify the cron entry for NMIS and change it.

The setting is found in /etc/cron.d/nmis and the default is this:

* * * * * root /usr/local/nmis8/bin/nmis.pl type=collect mthread=true ; /usr/local/nmis8/bin/nmis.pl type=services mthread=true

This should be changed to:

*/1 * * * * root /usr/local/nmis8/bin/nmis.pl type=collect mthread=true
*/2 * * * * root /usr/local/nmis8/bin/nmis.pl type=services mthread=true

It is important to note that the NMIS polling engine had an overhaul in NMIS 8.6.6 and NMIS 8.6.7 to improve how parallel threads were handled and that polling was kept up to date.

So when NMIS starts a poll every 1 minute, not all nodes will be polled, it will poll as many as it can in that time and then leave the others for the next poll cycle, this has the result of spreading the polling (and load on the server) out over 5 minutes. If you are not getting all nodes polled in 5 minutes, you will need more threads (and enough memory).

If you are polling many nodes every 1 minute, then you will need to size the server accordingly.

NMIS 8.6.6G

This maintenance release of NMIS was published on 1 Jun 2018.

...

• The handling of nodes with large numbers of interfaces was substantially improved, and a number of optimisations to reduce the collect times for such devices were implemented.
• The event subsystem was reworked for improved performance, and a number of related bugs were identified and fixed.
• NMIS now uses locks for per-node operations to ensure correct sequencing even if an update or collect operation takes a very long time.
  Time-exceeded events now also include better diagnostic info, i.e. the node name in question.
• Improved Threshold Alerts for some measurements, e.g. CPU.
• New and improved models for Checkpoint, APC, ACME, Furukawa, Alcatel devices, Ubquiti, Microtek, Frogfoot, Cisco; better modelling of OSPF.
• A number of models have been reworked for greater modularity and ease of use. Many were adjusted to handle corner cases better.
• Updates of the Cisco product mibs.
• For newly added nodes a type=update operation is now run automatically if and when required.
• NMIS now detects problems with sending events via syslog better and logs them.
• Node Configuration overrides are now presented better in the GUI, and the nodeconf subsystem was reworked for better performance.

NMIS 8.5.8G

Friday 24 April 2015

...

'collect' => {
    'Description' => '(CNOC|Collection)',
},

# collect interval time in seconds
my $collect_time = $C->{ipsla_collect_time} ? $C->{ipsla_collect_time} : 60;
# collect interval of buckets in seconds
my $bucket_interval = $C->{ipsla_bucket_interval} ? $C->{ipsla_bucket_interval} : 180;
# extra collect buckets for polling cycle
my $extra_buckets = $C->{ipsla_extra_buckets} ? $C->{ipsla_extra_buckets} : 5; 

chown root /usr/sbin/mtr
chmod u+s /usr/sbin/mtr

NMIS 8.3.1G

Thursday 1 December 2011

...