Table of Contents |
---|
...
Requirements
Warning Exercise caution while editing /path/to/omk/conf/opCommon.json, /path/to/omk/conf/opCommon.nmis or /path/to/nmis/conf/Config.nmis; if a syntax error is induced all OMK applications will cease to function
Check out How to make configuration changes to opCommon.nmis and other files for some more details on best practices for modifying the configuration file.
opReports 4 requires that configuration item nmis → nmis_host_base in/path/to/omk/conf/opCommon.json be set to the IP address or FQDN of the server for Snapshot ,
and be prepended by the HyperText Transfer Protocol ( http:// or https:// ),
for the Node Report to function correctly.opReports 3 requires that configuration item nmis → nmis_host_base in/path/to/omk/conf/opCommon.nmis be set to the IP address or FQDN of the server for Snapshot ,
and be prepended by the HyperText Transfer Protocol ( http:// or https:// ),
for the Node Report to function correctly.opReports 3 and 4 require that configuration item files → rrddraw in/path/to/nmis/conf/Config.nmis be set. The default setting is is 'rrddraw' => '<cgi_url_base>/rrddraw.pl'
Exercise caution while editing /path/to/omk/conf/opCommon.json, /path/to/omk/conf/opCommon.nmis or /path/to/nmis/conf/Config.nmis; if a syntax error is induced all OMK applications will cease to functionWarning ,
- opReports 3 and 4 require one to login to NMIS to view the graphs in the Node Report.
Introduction
The Node Report provides a detailed summary of one node. Node details such as status, sysName, IP address, type, model, uptime, interfaces, location, contact, description, last update, vendor, object name, group role and net and the interface table are presented. This report is useful in particular for incident and problem management reporting.
...