Table of Contents |
---|
...
- Some node properties have been updated. This mean the event action rules should be updated regarding this document.
- Parser plugins also needs to be update.
...
Step 3. OMK Applications considerations
opCharts
opCharts uses the same database.
...
Status | ||||
---|---|---|---|---|
|
opEvents
Update database name in opCommon.json:
...
Code Block |
---|
/usr/local/omk/bin/opevents-cli.pl act=setup-db debug=1 |
opConfig
Update database name in opCommon.json:
...
Code Block |
---|
/usr/local/omk/bin/opconfig-cli.pl act=setup-db debug=1 |
opReports
NMIS8 opReports and NMIS9 opReports work the same way:
...
Code Block |
---|
rsync -r root@myserver.com:/usr/local/omk/var/reports var/ rsync -r root@myserver.com:/usr/local/omk/var/opreports var/ |
opHA
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.
...
We can move all the model customisations in the models-custom directory. We can use rsync for this again.
NOTE Some models may need to be adjusted. Specially if they are using nmis internal functions.
...
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)
...
Step 2. Customise configuration
Same steps as the other procedure.
Step 3. opConfig data
Run the migration script:
Code Block |
---|
/usr/local/omk/bin/opconfig-cli.pl act=migrate-nodes debug=9 |
Step 4. opReports data
Same steps as the other procedure.
Step 5. opCharts data
Run the migration script:
...