| Table of Contents |
|---|
| Status | ||||
|---|---|---|---|---|
|
Summary
In this guide we will migrate the data from NMIS8 and OMK Applications to nmis9 and OMK Applications.
- Server: uburnto (ubuntu 18) → deb-n-burn (debian 10)
- nmis 8.7.2 → nmis 9.2.2
- opCharts 2.5.1 → opCharts 3
- opConfig 3.5.2 → opConfig 4
- opEvents 2.6.3 → opEvents 3
- opHA 2.2.2 → opHA 3
- opReports 3.4.2 → opReports 4
| Status | ||||
|---|---|---|---|---|
|
...
We can move all the files except the Table-tablename.nmis.
- Import the old nmis8 configuration and review important configuration options
Configure
We need to make some adjustments to the Config file.
...
| Code Block |
|---|
/usr/local/nmis9/bin/nmis-cli act=fixperms |
Import NMIS 8 configuration Items
More information here
Review important configuration Items
More information here
Configuration Files: Option 2
...
Step 3. OMK Applications considerations
opCharts 
opCharts uses the same database.
...
| Code Block |
|---|
/usr/local/omk/bin/opevents-cli.pl act=setup-db debug=1 |
opConfig
Update database name in opCommon.json:
...
Here you can find further information.
Step 6. Copy RRDs
Link to Step 3 Copy RRDs above
Step 7: Verify
Upgrade process (II): Installing apps (OMK)
...
- It is important to update nmis 9 first and leave running for a couple of poll cycles so inventory is created. nmis9 will create its own inventory, as this is now saved in the db and has a specific format. These data will be used for other scripts from the apps to migrate some data.
- opconfig and opevents share the same database in the old version. This is because the products database name should be changed to "nmis", the old database name.
- nmis8 didn't use mongo. This is because opConfig has its own nodes database. We don't want to replicate information, so now opConfig will use nmisng database to get the nodes information. We would need to use the opConfig migration script to porte port some specific configurations from the internal database to nmis.