Owners Manual

Best Practices: Performance Tuning Traffic Flow Analysis | Traffic Flow Analyzer
OMNM 6.5.2 User Guide 551
Best Practices: Performance Tuning Traffic Flow Analysis
Most OpenManage Network Manager packages limit Traffic Flow exporters through licensing,
however be aware that even small numbers of traffic flow exporters may overwhelm hardware
resources. For example even if you monitor as few as one to five nodes export data with a very high
sampling rate and have high traffic volumes, the amount of data that needs to be inserted into the
database may quickly exceed the insertion rate capacity of a single 7200 RPM disc. The
performance limitation imposed by the demands of Traffic Flow Analysis is one motivation to tailor
monitored flows to fit within the limits of your hardware.
You may also need to edit or fine-tune several default configurations to accommodate the volume
of traffic flow data exported from the managed devices and to manage the resources (processing
power, total memory) available to OpenManage Network Manager.
XML and properties files in
/owareapps/trafficanalyzer/server/conf/ contain these
configuration settings. The
ta-service.xml configures standalone environments, ta-med-
service.xml
configures distributed environments, and for additional configuration, edit
ta.properties . Any edits requires an application server and/or mediation server restart to take
effect.
NOTE:
Best practice: Contact Dell EMC support for assistance before editing these files.
In ta-service.xml and ta-med-service.xml , you can edit the entry for the
NetFlowListenerMBean, like the following:
<mbean code="com.dorado.netflow.NetFlowListenerMBean"
name="oware:service=NetFlowListenerMBean">
<attribute name="ReceiverUDPPort">9996</attribute> <!-- # NetFlow UDP
port -->
<attribute name="ReceiverTopNToKeep">0</attribute> <!-- Number of rows
per time bucket to keep -->
<attribute name="RecvQueueMaxSize">10000</attribute> <!-- # unparsed
packets -->
<attribute name="RecvQueueLowThreshold">80</attribute> <!-- Low
threshold for packet queue as pct -->
<attribute name="UnparsedMaxSize">10000</attribute> <!-- # unparsed v9
flows entries waiting on template -->
<attribute name="TransportBatchSize">1000</attribute> <!-- # NetFlow
values (inserts) and session summaries (updates) -->
<attribute name="TransportBatchTimeout">10000</attribute> <!--
milliseconds -->
<attribute name="SpoolQueueMaxSize">10000</attribute> <!-- # NetFlow
session results -->
<attribute name="SpoolBatchSize">50</attribute> <!-- # NetFlow session
results flushed at a time to disk during overflow -->
<attribute name="SpoolFileBufferSize">131072</attribute> <!-- # bytes
for I/O buffer -->
<attribute name="SpoolFileName">@OWARE_USER_ROOT@/owareapps/
trafficanalyzer/temp/tadata_spool.dat</attribute>
<attribute name="SpoolMaxFileSize">41943040</attribute> <!-- # bytes
for disk allocation -->