Skip to end of metadata
Go to start of metadata

We recommend that you use the automated installer script for all upgrades.

Automated Patching using the installer script

One of the new features available since 8.4.8G is an automated installation and upgrade script which can perform all of the automatable steps listed below on your behalf.

Once you've unpacked the NMIS tarball you will see in the NMIS source directory. Running ./ -h will show you what options it offers.

A simple invocation of ./ will prompt you for a few bits of necessary information and confirmations, after which the tool will backup your current NMIS installation and then perform the upgrade or installation steps. Please note that the installer script does not overwrite your existing models or configuration items, so a (semi-)manual comparison of your local changes (if any) will still be required.

To help with this procedure NMIS provides the helper program admin/ As an example, to check your Config.nmis against the one included with a new NMIS release you would use the tool like this:

The diffconfigs tool also works for model files.

At the end of the installation or upgrade run the installer script will save a log of the actions performed in install.log in the NMIS source directory.

If you don't want to use the installer script please follow the procedure listed below.

Upgrading NMIS8 code with an NMIS patch release

If you are patching from a version earlier than 8.4.6G, there are a few extra steps, none of them are distruptive, so we have left them all together.

The new script, install/ needs to be run at the end of the configuration upgrade to ensure required changes to Config.nmis are made (specifically for this release a newer version of jQuery is being used); if you use the automated installer script this will be taken care of for you.

We have made some improvements to the NMIS dash performance by improving the volume of data loaded, for people with over 500 nodes this will help, if you have over 1500 nodes it is a MUST have feature.

Checking Model Changes

Recent releases have included many device modelling enhancements, improved graphs and more, if you have made no changes to your models you can overwrite your existing models, otherwise you will need to merge the new models with the existing models, that requires consideration outside this document (git could be your friend here).  To overwrite your existing models:

Patch NMIS8 Config

Your NMIS installation may have settings that you have changed from the default installation.  If you would like to keep these changes you will need to merge the additional fields that have been added into the stock configuration into your custom configuration.  NMIS provides a tool called to help you do this:

Most of the config files will likely be the same as the install version, for these you can just copy the new versions

If you haven't changed your users you can update these:

Update Server Configuration


The new crontab which you generate by running this command /usr/local/nmis8/bin/ type=crontab

NMIS Configuration

You will need to verify the following configuration options have been set correctly or removed.  You can edit the configuration through the NMIS UI or with your favorite editor "vi /usr/local/nmis8/conf/Config.nmis"


There are some updates to improve UI and polling synchronisation.  Check the following configuration option for nmis_summary_poll_cycle, it should be set to false and the summary update added to the crontab.


This needs to be set to blank unless you intentionally want it to be "true"


We have found this is better set to a lower number, but if your experience has been otherwise, you do not need to change it.


This config setting "tables_case_sensitive_keys" is redundant, it is being done in the Tables.nmis file now.

File Permissions

Change Config.nmis to tell NMIS to use the new file permission scheme


We recommend updating the authentication system from apache to htpasswd (so NMIS does authentication instead of Apache). 3 steps need to be taken to change this.

  1. Change Config.nmis to tell NMIS to use htpasswd 

  2. Backup old apache configGenerate new apache configuration (if you have customised yours edit it and remove the auth portions instead of generating a new one) 

  3. Create new config to replace old config and restart apache 

Setup SNMP Trap Daemon

NMIS 8.4.6 includes some Cisco and Generic MIBS and has the ability to view the SNMP traps in the NMIS logging tool.

You will need to copy the options file to the right location and restart the daemon.

You can test the MIB resolution with this command

Which should result in:

Fix Data Type for Some Counters

Fix Data Type on mib2ip Counters

Run this command to make all the DS's COUNTER instead of GAUGE

 Fix Data Type on TopChanges Counters

 Run this command to make TopChanges the DS's COUNTER instead of GAUGE

Restart Daemons

Remove Old PID files

Update the Font Cache

In order to make RRD run faster it really helps to update the font cache 

Clean up and Test

  • No labels