Commit c3035d8d authored by 's avatar

Cleaned abw.conf including comments


git-svn-id: file:///home/svn/mapi/trunk@1549 8d5bb341-7cf1-0310-8cf6-ba355fef3186
parent f236e158
# This configuration file should be stored on each host that runs abw
# executable and is contacted by the web server. It can be a monitoring
# station (in which case we describe network cards on that particular
# monitoring station) or it can be a central station (in which case
# we describe network cards on all remote monitoring stations contacted
# by the central station through DiMAPI).
# Optional [global] section includes information common to all monitored links.
# [global]
# You must specify one [subject] section for each port on each network card
# used for monitoring. Each [subject] section MUST include id, hostname,
# interface and label. It CAN optionally include port, direction and
# description.
# Hostname says where the network card is located. Use fully-qualified domain
# name even if the card is on the local host. Interface is the device name.
# Specify one [subject] section for each port on each monitoring card.
# Use fully-qualified domain name even if the card is on the local host.
# Port should be specified only if you use a multi-port monitoring card
# (e.g., DAG) and starts from 0. Direction should be specified only if you are
# monitoring each direction (in or out) of a monitored link separately by two
# ports or two cards. [subject] sections for the same monitored link, but the
# oposite directions MUST have the same label.
# (e.g., DAG, Napatech) and starts from 0.
[subject]
id=1
hostname=perfmon1.cesnet.cz
interface=eth1
label=abw_test
description=ABW Test
# port=0
# [subject]
# id=2
# hostname=jra1-2.cesnet.cz
# interface=/dev/dag0
# label=GN2
# description=CESNET GN2
# port=1
# direction=out
# [subject] sections needs to be grouped together in [scope] sections. If you
# are unsure, specify one [scope] section for one [subject] section. Each
# [scope] section MUST include id and subject_ids (separated by commas)
# If you run abw executable on the central station, you can include more
# [subject] sections in one [scope]. This will result in one distributed
# flow (called scope) to be created by DiMAPI for all included [subjects]
# sections. All [subject] sections included in a [scope] section must have
# the same port and the same "mpls" field in the MAPI configuration file
# (mapi.conf).
# [subject] sections that refer to the same monitored link in the same
# direction need to be grouped together in one [scope] sections. This
# is usually the case when traffic is split into multiple virtual devices
# for multi-core processing. If you are unsure, specify one [scope] section
# for one [subject] section. Direction should be specified only if you are
# monitoring each direction (in or out) of a monitored link separately by two
# ports or two cards. [scope] sections for the same monitored link, but the
# oposite directions must have the same label.
[scope]
id=1
subject_ids=1
label=abw_test_scope
# [scope]
# id=2
# subject_ids=2
# You must specify one [parameters] section for each [scope] section.
# Each [paramaters] section MUST include id. It CAN optionally include
# header_filter, sau_mode, sau_threshold, payload_string, interval_sec and
# interval_usec.
# subject_ids=1,2,3
label=abw_test
description=ABW Test
# direction=in
# sau_mode can be d for deterministic, b for byte-deterministic or
# p for probabilistic, default is d
#
# sau_threshold is the number of packets for d (default is 1), number of
# bytes for b (default is 3000) or pass probability for p (default is 0.5)
#
# payload_string can be specified multiple times
#
# default interval_sec is 1 and default interval_usec is 0
# Specify one [parameters] section for each [scope] section.
# These parameters are discouraged. Just use empty [parameters] section
# with some id.
[parameters]
id=1
......@@ -82,10 +39,9 @@ id=1
# sau_threshold=10
# payload_search=virus
# You must specify one [measurement] section for each measurement using some
# [scope] with some [parameters]. Each [measurement] section MUST include
# id, scope_id and parameters_id. It CAN optionally include protocols.
# Default protocols is "all" (all traffic without classifying into protocols).
# Specify one [measurement] section for each measurement using some
# [scope] with some [parameters]. Default protocols is "all" (all traffic
# without classifying into protocols).
[measurement]
id=1
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment