Date: Thu, 28 Mar 2024 14:59:18 +0000 (UTC) Message-ID: <366646387.3892.1711637958779@skald.opmantek.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3891_1974153281.1711637958779" ------=_Part_3891_1974153281.1711637958779 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Upgrading NMIS to 8.5.12G is extremely simple: all you need to do is fol= low the guidance of the interactive installation script, which will perform= all the necessary steps that are safely automatable. Since version 8.5.6G = the installer also takes care of installing both operating system packages = and CPAN perl packages that NMIS depends on.
Please note that the installer script does not unconditionally o= verwrite your existing models or configuration items for safety re= asons. Instead it offers to run the Automatic Model Upgrade Tool for you; if the model upgrades cannot = be performed automatically (e.g. due to local customizations) you should fo= llow the (semi-manual) model upg= rade procedure to gain the benefits of the newest models.
For your convenience the installer offers to save a compressed backup sn=
apshot of your NMIS configuration in root
's home director=
y, and a log of the actions that were performed is saved in install.l=
og
in the NMIS directory.
Some of our customers are running Opmantek applications without direct a= ccess to the Internet, which can make installations and upgrades quite = ; tedious when new pre-requisites are introduced. We have therefore prepare= d a document that describes all the common options for working around t= his problem. The installer also mentions this page if it detects missin= g pre-requisites but no Internet access.
NMIS Versions 8.5.6G and newer recommend an updated and simplified direc=
tory structure for your RRD files, which is more robust and easier to deal =
with from an administrative perspective: all of a node's RRD database files=
are kept within the directory <nmisdir>/database/nodes/<nod=
ename>
. (In the past, a node's RRD files were spread across multi=
ple directories; furthermore the directory names did include the node type,=
which can change under certain circumstances and which can cause all kinds=
of subtle inconsistencies.)
This new recommended structure is controlled by the settings in mo=
dels/Common-database.nmis
, and great care has been taken to make the=
migration from old to new layout safe and unproblematic.
NMIS 8.5.8G ships with the tool admin/migrate_rrd_locations.pl and the installer will offer to run it for you automatically. This tool=
takes care of moving any existing RRD files from old to new location, and =
merges a new
Common-database.nmis
with the other settings in y=
our existing file (e.g. custom RRD period values). You can run the tool rep=
eatedly; if there is nothing to migrate, then it'll show that and simply ex=
it. There is a simulation mode for only seeing prospective changes without =
performing them, and the migration tool also creates a rollback script in /=
tmp which can be used to reverse a (partially or fully completed) RRD migra=
tion.
It is highly recommended that you let the installer per= form the RRD migration on your behalf.
Once you've unpacked the NMIS tarball you will see install.pl=
in the NMIS source directory. Running ./install.pl -h will show you what options it offers.
A simple invocation of ./install.pl
will prompt you for a f=
ew bits of necessary information and confirmations, after which the tool wi=
ll backup your current NMIS installation and then perform the upgrade or in=
stallation steps.
Once the installer has finished its work you will likely need to r=
eview your config and model files and determine whether there are any custo=
mizations that you need to merge with newer files from the NMIS tarball. NM=
IS live configuration files are in /usr/local/nmis8/conf
,=
the updated material from the release is in /usr/local/nmis8/in=
stall
; for models please see the page on Upgrading Models.
To simplify the comparison and merging process NMIS provides the helper =
program admin/diffconfigs.pl
. As an example, to check your Con=
fig.nmis against the one included with a new NMIS release you would use the=
tool like this:
cd /usr/local/nmi= s8 ./admin/diffconfigs.pl install/Config.nmis conf/Config.nmis Comparing install/Config.nmis to conf/Config.nmis Output format: "Config Key Path: - Status in install/Config.nmis + Status in conf/Config.nmis" /system/threshold_period-pkts_hc: - -15 minutes + -5 minutes ...possibly lots more changes... Difference Summary: /authentication/auth_user_name_regex /system/threshold_period-interface /system/threshold_period-pkts /system/threshold_period-pkts_hc