opConfig can be upgraded to Version 2.x with very little effort, and this document describes the process and caveats:
/usr/local/omk
, and the binaries are named differently from Version 1.x:
Old Name | New Name |
---|---|
/usr/local/opmantek/ | /usr/local/omk |
/usr/local/opmantek/bin/opConfig-cli.pl | /usr/local/omk/bin/opconfig-cli.pl |
/usr/local/opmantek/bin/opConfigd.pl | /usr/local/omk/bin/opconfigd.pl |
http://<machine>/cgi-omk/opConfig.pl |
|
connections.nmis
and credential_sets.nmis
files to the database on first startup, then renames the files with the suffix .disabled
. In version 2.x all credential set and node configurations are performed in the GUI.If you have a license for Version 1.4 of Open-AudIT Enterprise or newer, then opConfig can import audit data from Open-AudIT. This audit information will show up in opConfig as command "audit", and the command output will be the full audit data set in JSON format.
To enable this, set the necessary options in conf/opCommon.nmis
and run opconfig-cli.pl act=import_audit
periodically or as a one-off. The related config settings are as follows:
'opconfig_audit_import' => 1, # to enable this altogether 'opconfig_audit_import_url_base' => "http://my.oae.system.com/omk/oae/", 'opconfig_audit_import_user' => "nmis", # needs ro-access 'opconfig_audit_import_password' => "somepassword", |
/usr/local/omk/logs
: opConfig.log
is for any opConfig-specific GUI logs, opConfig-cli.log
is for opconfig-cli.pl
. opconfigd logs to common.log
, and opDaemon.log
is for the Opmantek Web Infrastructure."tags=tagA,tagB"
to the opconfig-cli.pl invocation for act=run_command_sets.