Page History

...

    '<opflow_dir>' => '/var/cache/nfdump' to match the default shipping config

opCharts/NMIS integration

NMIS integration enables the resolution of Interface indexes to Interface Names.  The association to an NMIS node enables opFlow to look up the interface indexes which the traffic is flowing to and from.  Note the agents are a list of the IP addresses from which flows are received.  opFlow will automatically update Agent->Node links once an hour, at this time interface information will also be updated, the update can also be triggered from the GUI using System->Sync Agent/Node Data.  Associating to an NMIS node enables opFlow to look up the interface indexes which the traffic is flowing to and from.

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 opCharts4 the remote server can be a poller or a Primary.

If you are linking to a local omkd do not use a remote connection.

Local NMIS integration

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 'nmis_dir' => '/usr/local/nmis9'

Remote NMIS/opCharts integration

Remote integration requires setting 3 config items, these are used so the opFlow server can access an opCharts server.  When this is working the GUI will show ifDescr and Descriptions in the agent selector, and when filtering on an agent/interface will display the interface info panel.  

The two servers must have the same value for <omk_url_base> (which is not often changed)

# NOTE: no trailing slash
'opflow_opcharts_url_base' => "http://someserver.tld", # base for omk, do not connect to localhost this way, use local nmis integration
'opflow_opcharts_user' => "nmis",      # needs ro-access
'opflow_opcharts_password' => "nm1888",

High volume settings

There are two high volume controls for opFlow, one for the backend and one for the frontend.  

'opflow_high_volume' => 1,
'opflow_gui_high_flow_volume' => 1,
'opflow_gui_no_flows_over_time_graph' => 1,
'opflow_gui_display_other' => 0,

opflow_high_volume will cause opflowd to insert pre-aggregated flows if set, raw flows if not.  Currently the GUI has no way of displaying raw flows so this is enabled by default.

opflow_gui_high_flow_volume will force the GUI to show a simplified/optimized index page, it can also be viewed by setting ?simple=1 on the index page, it is enabled by default.

opflow_gui_no_flows_over_time_graph will remove the flows over time graph from the index page, this is off by default.

opflow_gui_display_other tells opFlow if all flows outside of the TopN should be summarised into an "other" entry, this is off by default

Graph display settings

The graph that show flows over time can display 2 modes: the default shows the number of octets/packets in the current time slice, the second mode makes the graph display the data in octets/second or packets/second.  To enable the second mode change the following config variable to 1:

	'opflow_gui_graph_over_time_per_sec' => 1

opFlowSP 1.0.9 introduced 3 new configuration items:

     'opflow_gui_hide_interface_performance_graphs' => 0,
     # Custom agent button
     #'opflow_gui_agent_custom_button_text' => 'Button Text',
     #'opflow_gui_agent_custom_button_url' =>'https://example.com/omk/opCharts/inventory/interfaces',

opflow_gui_hide_interface_performance_graphs is used to hide or show the button "Interface Performance Graphs". Default is 0 to show the button. Set to 1 to hide the button.

Image Removed

opflow_gui_agent_custom_button_text and opflow_gui_agent_custom_button_url are set together to add a button with a custom link to be visible to the right of "Interface Performance Graphs".

Possibility to set the octet format to MegaBytes (MB) or Megabits (Mbits) using the configuration item opflow_gui_octet_display_multiplier.

    'opflow_gui_octet_display_multiplier' => 0.000000953674316,
    'opflow_gui_octet_display_multiplier' => 0.000008,

Restart the daemons

After making changes to the config make sure to restart all opFlow daemons.

...