# At the top level are elements specific to the overall Mesh. This includes a
# description of the 'mesh', the admins for the mesh, the organizations
# involved in the mesh, and the tests that the meshes perform.
# A human-readable description of the overall mesh
description DICE Mesh
# The overall mesh administrators (i.e. who one should contact if problems are
# seen with the mesh, etc).
name Roderick Mooi
email rmooi@csir.co.za
# Each mesh has one or more "organization" blocks. This allows encapsulating
# the administrators, sites, MAs, etc that are specific to the organization. In
# this example organization, all the data is stored on the hosts on which it is
# collected which is the norm for Toolkit instances.
# A human-readable description of the organization
description SANReN
# The administrators for the organization (i.e. who one should contact if
# problems are seen with individual sites/hosts in the mesh.
name Roderick Mooi
email rmooi@csir.co.za
# There can be one or more 'site' blocks. Each 'site' block corresponds to a
# logical site in the organization which may contain one or more hosts.
# Elements in the 'site' block apply to all the 'host' blocks contained
# within them, and inherit the properties from the 'organization'.
## A human-readable description of where the site is located (e.g. a city or state)
city New York
state NY
# The latitude and longitude where the site is located
latitude 40.720
longitude -74.005
# Individual sites can have specific administrators associated with them.
name Roderick Mooi
email rmooi@csir.co.za
# There can be one or more 'host' blocks. Each 'host' block corresponds to
# a single host at a site.
# An optional human-readable description of the host
description perfSONAR 6
address 155.232.40.42
# There can be one or more 'measurement_archive' blocks. These have a 'read'
# URL which corresponds to the perfSONAR-speaking MA where test results can
# be obtained from. The blocks also have a 'write' URL which tells tests
# where the results can be written to. For hosts running the Performance
# Toolkit, the following URLs will all match the measurement archives
# running on the host, just replace the perfsonar.newy.net.internet2.edu
# with the hosts address.
type traceroute
read_url http://155.232.40.42:8086/perfSONAR_PS/services/traceroute_ma
write_url http://155.232.40.42::8086/perfSONAR_PS/services/tracerouteCollector
type perfsonarbuoy/owamp
read_url http://155.232.40.42::8085/perfSONAR_PS/services/pSB
write_url 155.232.40.42::8570
type perfsonarbuoy/bwctl
read_url http://155.232.40.42::8085/perfSONAR_PS/services/pSB
write_url 155.232.40.42::8569
type pinger
read_url http://155.232.40.42::8075/perfSONAR_PS/services/pinger/ma
# No 'write_url' for PingER measurement archives
city Salt Lake City
state UT
latitude 40.757
longitude -111.953
description perfSONAR 7
address 155.232.40.50
type traceroute
read_url http://155.232.40.50:8086/perfSONAR_PS/services/traceroute_ma
write_url http://155.232.40.50:8086/perfSONAR_PS/services/tracerouteCollector
type perfsonarbuoy/owamp
read_url http://155.232.40.50:8085/perfSONAR_PS/services/pSB
write_url 155.232.40.50:8570
type perfsonarbuoy/bwctl
read_url http://155.232.40.50:8085/perfSONAR_PS/services/pSB
write_url 155.232.40.50:8569
type pinger
read_url http://155.232.40.50:8075/perfSONAR_PS/services/pinger/ma
# No 'write_url' for PingER measurement archives
# There can be one or more test_spec blocks. Each test_spec block represents a
# test specification, i.e. a test type, along with the parameters for the test.
# The test_spec's *must* have an 'id' field which gets used later to identify
# them.
# Define a test spec for testing achievable bandwidth once every 4 hours
type perfsonarbuoy/bwctl # Perform a bwctl test (i.e. achievable bandwidth)
tool bwctl/iperf # Use 'iperf' to do the bandwidh test
protocol tcp # Run a TCP bandwidth test
interval 14400 # Run the test every 4 hours
duration 20 # Perform a 20 second test
# Define a test spec for testing UDP bandwidth once every 24 hours
type perfsonarbuoy/bwctl
tool bwctl/iperf
protocol udp # Run a UDP bandwidth test
interval 86400 # Run the test every 24 hours
duration 10 # Perform a 10 second test
udp_bandwidth 50000000 # Perform a 50Mbps test
# Define a test spec for doing jitter, loss and latency testing
type perfsonarbuoy/owamp # Perform a constant low-bandwidth OWAMP test
packet_interval 0.01 # Send 10 packets every second (i.e. pause 0.1 seconds between each packet)
loss_threshold 10 # Wait no more than 10 seconds for a response
session_count 18000 # Refresh the test every half hour (once every 18000 packets)
sample_count 300 # Send results back every 30 seconds (once every 300 packets)
packet_padding 0 # The size of the packets (not including the IP/UDP headers)
bucket_width 0.001 # The granularity of the measurements
# Define a test spec for doing ICMP jitter, loss and latency testing every 5 minutes
type pinger # Perform PingER tests
test_interval 300 # Perform a test every 5 minutes
packet_count 10 # Send 10 packets for each test
packet_interval 1 # Pause 1 second between each packet sent
packet_size 1000 # The size of the packets (not include the IP headers)
# Define a test spec for running traceroute tests every 10 minutes
type traceroute # Perform a traceroute test
test_interval 600 # Run the test every 5 minutes
protocol udp # Run a UDP traceroute (could also be 'icmp')
timeout 30 # Wait 30 seconds
pause 0 # Number of seconds to pause between each traceroute probe
waittime 5 # Number of seconds to wait for a response before assuming its lost
first_ttl 0 # The initial value for the TTL
max_ttl 64 # The maximum value for the TTL
packet_size 40 # The size of the packets (not include IP/UDP headers)
# There can be one or more 'group' blocks. These contain a list of hosts that
# will be used in a test.
# A group type 'mesh' means that all hosts in the list will test to all other
# hosts in the list. The other available options is 'star' configuration
# detailed below.
type mesh
# The members contain a list of addresses that will be used in the tests.
# These *must* correspond to addresses in host blocks above.
member 155.232.40.42
member 155.232.40.50
type mesh
member 155.232.40.42
member 155.232.40.50
# There can be one or more 'test' blocks that represent tests that the mesh
# should be performing. These combine the group elements defined above with
# test parameters defined above.
description Traceroute Test Between DICE Latency Hosts
group dice_latency_hosts
test_spec traceroute_test
# For members who are not running the required mesh configuration agent, a
# list of 'no_agent' elements can be specified.
# no_agent chic-owamp.es.net
# no_agent newy-owamp.es.net
description TCP BWCTL Test Between DICE Bandwidth Hosts
group dice_bandwidth_hosts
test_spec bwctl_4h_tcp_test
description UDP BWCTL Test Between DICE Bandwidth Hosts
group dice_bandwidth_hosts
test_spec bwctl_24h_udp_test
description OWAMP Test Between DICE Latency Hosts
group dice_latency_hosts
test_spec owamp_test
description Ping Test Between DICE Latency Hosts
group dice_latency_hosts
test_spec ping_test
description Traceroute Test Between DICE Bandwidth Hosts
group dice_bandwidth_hosts
test_spec traceroute_test