abw.conf 3.27 KB
Newer Older
's avatar
committed
1 2 3 4 5 6 7
# 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).

's avatar
 
committed
8 9 10 11
# Optional [global] section includes information common to all monitored links.

# [global]

's avatar
committed
12 13 14 15 16 17 18 19 20 21 22
# 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.
# 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 
's avatar
 
committed
23 24 25 26
# oposite directions MUST have the same label.

[subject]
id=1
's avatar
committed
27 28
hostname=perfmon1.cesnet.cz
interface=eth1
's avatar
 
committed
29 30 31 32 33
label=abw_test
description=ABW Test

# [subject]
# id=2
's avatar
committed
34
# hostname=jra1-2.cesnet.cz
's avatar
 
committed
35 36 37 38 39 40
# interface=/dev/dag0
# label=GN2
# description=CESNET GN2
# port=1
# direction=out

's avatar
committed
41 42 43 44 45 46 47 48 49 50
# [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).
's avatar
 
committed
51 52 53 54

[scope]
id=1
subject_ids=1
's avatar
committed
55
label=abw_test_scope
's avatar
 
committed
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93

# [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.

# 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

[parameters]
id=1
# interval_sec=1
# interval_usec=0
# header_filter=udp and port 2000
# sau_mode=d
# 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).

[measurement]
id=1
scope_id=1
parameters_id=1
's avatar
committed
94
protocols=all,tcp,udp,icmp,ip6,multicast,http,https,ssh,ftp,gnutella,dc,edonkey,torrent,skype