...
| Code Block |
|---|
# best way to configure these is via /etc/default/nfdump or /etc/sysconfig/nfdump, # DATA_BASE_DIR needs to be the same as "<opflow_dir>" in opCommon.json DATA_BASE_DIR="/var/libcach/nfdump" DATA_ROTATE_INTERVAL=300 NETFLOW_PORT=99952055 PIDFILE=/var/run/$NAME.pid |
...
The following changes can be made in the opCommon configuration file file /usr/local/omk/conf/opCommon.nmisjson
opflowd/ndfump
It is important that that the <opflow_dir> in opCommon.nmis json matches the DATAthe DATA_BASE_DIR in the nfdump configuration
| Code Block |
|---|
'<opflow_dir>' => '/data/opflow', # or '/var/libcache/nfdump' to match the default shipping config |
...
Linking with opCharts/NMIS can be done to an NMIS instance on the same server (Local) or can integrate to a remote instance of opCharts. If you are running opCharts3 as the remote it must not be a Primary instance it must be a normal poller instance. If you are running opCharts4 the remote server can be a poller or a Primary.
...
If the config setting 'opflow_opcharts_url_base' is left blank, opFlow will attempt to load node information from a local NMIS server found at at 'nmis_dir' => '/usr/local/nmis8nmis9'
Remote NMIS/opCharts integration
...