...
Code Block |
---|
/usr/local/omk# /usr/local/omk/bin/opcommon-cli.exe act=convert_json_dir dir=conf |
Configure
Status | ||||
---|---|---|---|---|
|
Update opCommon.json:
Code Block |
---|
"database": { "db_name": "omk_shared", ... "nmis": { "<nmis9_dir>": "/usr/local/nmis9", "<nmis9_logs>": "/usr/local/nmis9/logs", "nmis9_cgi_url_base": "/cgi-nmis9", "nmis9_dir": "/usr/local/nmis9", |
...
Step 3. OMK Applications considerations
...
opCharts
...
opCharts uses the same database.
Status | ||||
---|---|---|---|---|
|
opEvents
opConfig
...
opReports
NMIS8 opReports and NMIS9 opReports work the same way:
...
Code Block |
---|
cp -rf /usr/local/omk-old/var/opreports/known_reports_cache /usr/local/omk/var/opreports cp /usr/local/omk-old/var/opreports/selftest.json /usr/local/omk/var/opreports |
opHA
opHA 3 works different from opHA 2. The peers would need to be imported manually using the GUI or the cli.
Further information can be found here.
Step 8. Start daemons
Code Block |
---|
sudo service nmis9d start sudo service omkd start sudo service opeventsd start sudo service opchartsd start sudo service opconfigd start |
...