...
Please feel free to submit your comment here or email us with your questions!
Upgrading NMIS 9 Compatible Opmantek Applications
We have made significant changes on our internal code for all our applications to work on Opmantek's latest and fastest platform, however, previously installed product are not compatible with these new changes.
| Compatibility Table | |
Application | Version |
|---|---|
| NMIS 9 | > 9.1.0G |
| opCharts 4 | >= 4.20 |
| opConfig 4 | >= 4.20 |
| opEvents 3 | >= 3.2.0 |
| opHA 3 | >= 3.20 |
| opReports 4 | >= 4.20 |
To find out more about this upgrade please read:
Uninstalling Opmantek Applications
...
- Removal of all Opmantek daemon init scripts from
/etc/init.d
This may include init scripts foromkd,nmisd,opeventsd,opconfigd,nfdump,opflowd.
You should stop the daemons before removing the init scripts. - Removal of
cronschedules for the Opmantek applications
This may include files in/etc/cron.dnamedoae,opaddress,opconfig,opevents,opflow,opreports,optrend. - Removal of all of
/usr/local/omk,/var/log/omk,/data/omk
The latter two may not be present (but will be if your system started as an Opmantek Virtual Appliance). - Cleanup or removal of the Opmantek applications' MongoDB databases
Unless you are actively using MongoDB you might simply stop themongoddaemon and remove the database files (typically under/var/lib/mongodbor/data/mongodbfor the Opmantek VM).