Upgrading opReports from version 2.x to 2.5.1 is almost effortless, but to gain access to the new features of version 2.5.1 a few changes have to be made.
First, of course, comes unpacking the new software (just like for the initial installation). For this first step it is assumed that you downloaded the opReports archive to root's home directory; if that is not the case you'll need to adjust the tar invocation below to indicate the appropriate path:
cd /usr/local tar xzvf ~/opReports-Linux-x86_64-<version>.tar.gz
This step does not overwrite any of your current configuration, because that resides in the conf directory (which is shipped as an empty directory with the software). However, there are some new configuration directives which need to be added -
To add the newly added configuration options to the active conf/opReports.nmis you should now run opupdateconfig.pl. You can also first try opdiffconfigs.pl to find out which config entries are different.
cd opmantek ./bin/opdiffconfigs.pl conf/opReports.nmis install/opReports.nmis ...shows list of differences... ./bin/opupdateconfig.pl install/opReports.nmis conf/opReports.nmis
Version 2.5.1 introduced the Response Time report type, which works best if you set the variable response_exception_threshold in opReports.nmis; otherwise the report will not count and report reponse time exceptions.
In version 2.4.1 we added customisable WAN report detail levels, if you are upgrading from a version older than that please see opReports detail levels for WAN reports.
That's it; on the opReports page you should now see the new version number, and all the new features should be ready.