...
| Status | ||||
|---|---|---|---|---|
|
opEvents
opConfig
...
Update database name in opCommon.json:
| Code Block |
|---|
"opevents_db_name": "nmis", |
Run migration scripts:
| Code Block |
|---|
/usr/local/omk/bin/opevents-cli.exe act=migrate-nodes debug=8
/usr/local/omk/bin/opevents-cli.exe act=migrate debug=8 |
opConfig
Update database name in opCommon.json:
| Code Block |
|---|
"opconfig_db_name": "nmis", |
opReports 
opReports
NMIS8 opReports and NMIS9 opReports work the same way:
...
If you followed the instructions above, your Report Schedules are back in place, as you've copied over the entire omk-old/conf directory in step five. The /data/omk/var reports directory should still be where it was at the beginning of the upgrade, as it was never changed.
We recommend coping can copy the ./ opreports /known_reports_cache directory and the ./opreports/selftest.json file and reports directories into the new application .to move all the reports:
| Code Block |
|---|
cprsync -rf r root@uburnto.opmantek.net:/usr/local/omk-old/var/opreports/known_reports_cache /usr/local/omk/var/opreports cp rsync -r root@uburnto.opmantek.net:/usr/local/omk-old/var/opreports/selftest.json /usr/local/omk/var/opreports |
opHAopHA
opHA 3 works different from opHA 2. The peers would need to be imported manually using the GUI or the cli, using nmis8/conf/Servers.nmis file.
Further information can be found here.
...