Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: MongoDB 6.0 release for all products

Product Compatibility

Refer to product compatibility to determine supported Operating Systems and Database Versions.

...

Table of Contents
maxLevel1

NMIS 9.5.0

Status
colourGreen
titleRELEASED
9 July 2024

NMIS 9.4.8

Status
colourGreen
titleRELEASED
20th May 2024

...

  • Updated services check for web availability in the installer
  • Improve installer with timestamps, indented urls, don't install unneeded packages
  • Ensure traceroute and mtr are installed by NMIS installer
  • Remove end-of-life Debian 8 (Jessie) code
  • Keep Inventory configuration/group in sync on update
  • Add new action nmis-cli act=inventoryrefresh to refresh inventory

NMIS 9.4.5

...

  • Admin tools:
    • New admin tool to test email, admin/testemail.pl
    • Improved polling summary output
    • New nmis-cli option to collect performance data. Used by a cron job. 
    • Improved support tool
    • Fixed import bulk for node_admin tool 
  • Collect engine: 
    • Check if collect is false before collect interface data
    • Support for variables names in rrd names
    • Update storage when changed the rrd names
    • Fixed manual model selection when collect is false
  • Improvements:
    • Improved the default SNMPTrapd options
    • Now it is possible to install nmis in an alternative path
    • Support for different size ICMP packets with FastPing
  • Other fixes: 
    • Fixed default table escalations
    • Fix omkd Opmantek.pl service monitor 
    • Fix error in saving windows positions
    • Fix permissions in node dump
    • Fixed issue with ifSpeed in parseString
    • Fixed connection leaks due to the use of ensure_index
    • Fixed GUI Node admin summary
    • Fix in update polling policy from GUI
    • IPv6 fixes
  • Model changes: 
    • Added Siklu models 
    • New model for Mikrotik TopN
    • Ported Fortinet models from nmis8
    • Added empty Common-heading for back compat NMIS8 models, removed using this from several ported models
    • Default no collect for veth interfaces in model net snmp

...

  • Be able to read other configuration files from the Primary server. Requires opHA 3.0.7
  • NMIS GUI configuration tables are not editable if other configuration files from the poller are sent.
  • Added conf.d configuration files to support zip.
  • The minimum length of time that a graph can show has been reduced from 30 min to 10 min, this allows to see shorter periods with better details, meaningful when used with 1min polls. 
  • Prevent the queue jobs from getting too big when unnecessary:
    • Add default configuration parameter 'abort_plugins_after' => 7200, # seconds
    • Updated nmis9 scheduler to not add a plugin job if already exist another for the same nodes. 
    • Updated the queue information message when truncate output to be more clear. 
  • Prevent tests collection events being contaminated by real NMIS9 processes. 
  • Added function 'retrieve_section' to lib/NMISNG/Node.pm to retrieve systemHealth sections for QoS for non-Cisco devices.

  • Added submodule SQoS (Standardised Quality of Service) to NMISNG as lib/NMISNG/SQoS.pm

  • Fix create Outages function used by opCharts (4.0.12) when programming an Outage. 
  • Added node group to Events to make the query faster for RBAC queries in opCharts (4.0.12). 

...

  • NMIS 9 configuration can be now set up using the Primary node
  • Fixed bug when renaming a node on a specific situation, when the node had track of files that doesn't exist anymore. The message was "Failed to relocate inventory storage XXX: file "/nodes/namenode/interface/inloopback0.rrd" does not exist, cannot relocate!".
  • Fixed bug in the NMIS interface that, in some situations, shows the wrong color (green) for unreachable nodes. It happened when the node was unreachable but a node down event does not exist. 
  • Fixed cgi-bin/models to handle distinction between config nmis_default_models and nmis_models directories for listing, and to use nmisng::util::getmodelfile to read the appropriate model file (custom or default); any written out data already went to the custom model directory.

  • Replace legacy logging code.
  • Fixed "Network Tools >> SNMP Tool" that was opening when the node was not active. 

NMIS 9.0.5

Status
colourGreen
titleReleased
 The beta release was published on 24 July 2019, and fixes  one scheduling bug in NMIS 9.0.4.

...

  • Smarter non-interactive installation with Preseeding
  • Support to See poller nodes from the primary server.
  • Fixed visualisation problem with numeric node nodes. Nodes with only numbers on the name, like "12345" were causing problems on the system.
  • Show poller_event_log by default if the NMIS9 is a Primary, in case syslog is configured to get network events on Primary.
  • mojolicious 8.x is a new dependency that has a totally rotten default format for mojo::log. Fixed log format and set log_level to info which is no longer the default.
  • Fixed race condition in the poll process causing the catchall inventory data not being updating properly when the ping operation runs at the same time. 
  • Fixed fpingd process on debian 10 was causing heaps of space padding to be added if $0 is changed.
  • Fixed NMIS9 runtime graph was not working. 
  • Change sysLocation field title to 'SNMP Location' to declash with manually configured location field, which is titled 'Location'.
  • Added hr* sections to net-snmp model so opCharts can know what charts to make. 
  • Fixed network_summary_group view had empty columns.
  • Fixed node response time graphs for nodes (shown NaN on previous):

...

  • nmisng nodes now handle cluster_id on get_events_node: This is going to allow opHA to remove events from the poller on a peer deletion, so no data from the poller should remain. Also fix node_admin when dumping a node from the poller (Now will be able to get also event_data). 
  • Show message on delete node errors. 
  • Minor fixes ported from NMIS8:
    • Added support for fping inter packet gap for some firewalls. New configuration options added: fastping_interval and fastping_target_interval. 
    • IPrevent NMIS from failing when an escalation event element is c:\\
    • Adding the new opConfig "Node Configuration Change Detected event"
    • Fixed newlines being included in WMI error messages
    • Calling /proc/cpuinfo in the Support ZIP
    • run-reports.pl makes sure the reports directory exists
    • Optimisation to stop running services if no service polling required on a node
    • work around net-snmp snmpd which reports almost anything as hrfixeddisk
    • fixes for the Cisco Temperature model
  • loadServiceStatus: A new parameter is added that allows filter by all clusters. This will allow opCharts to show Monitored Services from the poller. 
  • services.nmis: Added Opmantek.pl
  • nmis-cli: On job type collect wasn't filter by local nodes.
  • purge_op_status: Changed to 7 days by default.
  • Display node name in opstatus.pl

NMIS 9.0.2

Status
colourGreen
titleReleased
 This beta release was published on 7 June 2019.

...

  • Feature Parity with NMIS 8.6.6G
    NMIS 9.0.0c supports the new  Polling Failover mechanism, and all  recent improvements made in NMIS 8 are present in NMIS 9.0.0c (where applicable).
    This also includes the recent improvements for Single-Sign-On.
  • Can run in parallel with NMIS 8
    If your server specs are suitable (min. 4GB of RAM, 6-8GB recommended), then NMIS 8 and NMIS 9 can be installed on the same server without interference.
    NMIS 9 normally installs itself into /usr/local/nmis9, and its web entry point (http://localhost/nmis9/) doesn't interfere with NMIS 8.
    If the installer detects an NMIS 8 instance on your server, then it offers to import the NMIS 8 nodes' configuration: all nodes would then be polled in parallel by both NMIS 8 and NMIS 9.
  • Full installer support for platforms Debian 9, Ubuntu 16.04, CentOS 7 and 6.
  • Improved installer behaviour for both installations from scratch and upgrades from 9.0.0b.
    Upgrading from earlier releases of NMIS 9 (nightly or 9.0.0b) should now be supported seamlessly, ie. all required structural changes should be taken care of by the installer.
  • Automatic priming for monitoring of localhost, ie. the NMIS server itself
  • Node administration suite is now feature-complete
    admin/node_admin.pl can now perform all typical node operations, as well as export and import of a node's complete database information for diagnostic purposes.
  • Improved and more consistent logging
  • Fine-grained Operational Status information
    NMIS 9 now creates operational status overview records for every operation that is performed in the background.
    This operational status is accessible from the GUI (in the menu under System -> Host Diagnostics -> Ops Status).
  • Improved robustness and flexibility of the job scheduling logic
    Long-dead nodes are now demoted to fewer connection attempts after 14 days of inaccessibility.
    Job priorities can now be freely configured (see priority_schedule in conf-default/Config.nmis).
    The intial update operation for newly added nodes is now automatically prioritised above all other operations.
  • Improved self-test capability and support tool.
  • More flexibility for manually scheduled jobs
    bin/nmis-cli can now schedule any job with a specific (higher or lower than default) verbosity, which will affect just that one job.
    See the help text from bin/nmis-cli act=schedule for details.
    Furthermore, all log output for a particular job can be redirected to a separate file as well (using job.output=/some/path/nameprefix).
  • NMIS 9 CLI Improvements
    bin/nmis-cli can now show the live NMIS daemon and worker process status (with act=status).
    It is now possible to delete or abort scheduled jobs in bulk, using bin/nmis-cli act=delete-schedule id=ALL job.type=<something> job.uuid=<somenodeuuid>; note that "id=ALL" is required to indicate that all matching jobs are to be removed.
  • Various Minor GUI Improvements
    The Node dashboard widget now displays the last time  for ping, collect and update separately, and if there is a job in progress or pending for this node, then that is shown as well.

...