OARnet Network Performance Workshop: Requirements

Agenda -- Participants-- Prerequisites -- Logistical Information -- Presentations -- Workshop Locations

---

29-30 September 2005
The Ohio State University
Columbus, Ohio

To ensure the best possible use of time at the workshop, Internet2 recommends that the following technical capabilities be met by all participants. Participants are encouraged to meet all prerequisites so that they may fully participate in, and benefit from, all workshop activities.

Goal:
Participants will configure measurement hosts on their own network during the Workshop. These hosts will be configured to run the beacon tools (NDT, One-Way Ping, and Bandwidth Test Controller).

General Requirements:

• Participants should have their own laptop at the workshop with sufficient access to their home site to remotely install and configure measurement hosts on their own network.
  Participants should have identified at least one measurement point (preferably two) on their own network. Each measurement point may require multiple hosts to run the current measurement tools.
• Latency measurement can not co-exist with throughput measurements. And different throughput tools can interfere with each other on the same host. We intend to create a meta-scheduler for this purpose but until we do, the easiest solution is to run multiple hosts. This means each measurement point will ideally have 3 hosts currently to run each of the current tools.
• For each measurement point, participants should determine which tools they would like to install. We recommend installing all of the tools at every measurement point even if you need to install them on the same host and only make one of them active at a time for now.
• All of the tools are dependent upon the hosts having good time. Therefore, NTP is a requirement for all hosts. In particular this means:
• Each host should have full access to the internet for NTP (port UDP 123 must be open for sending and receiving). Information on how to configure NTP in a sufficient way for the measurement tools will be one of the topics of the workshop.
• It would be useful for each participant to find several (at least 4 or 5) stratum-1 NTP servers "close" to the measurement points. Ideally these servers will be reached by diverse network paths.

Server Requirements:

NDT requires a machine with a web100-enhanced Linux kernel. We prefer FreeBSD for the machine that runs One-Way Ping, and Linux for the machine that runs the Bandwidth Test Controller. A web100-enhanced kernel for the Bandwidth Test Controller machine can be useful, so we recommend that as well. We also recognize that installing and configuring multiple machines is time consuming; if you can only configure one machine before the workshop, make it a web100-enhanced Linux kernel machine.

The Bandwidth Test Controller has the most stringent hardware requirements, along with NDT. However, the requirements depend on the maximum bandwidth you wish to test. For example, if you have 100 Mbps FastEthernet at your edge, and that is what you want to test, then pretty much any modern PC with a FastEthernet interface will do. Below we will show minimum requirements for Gigabit Ethernet. Machines capable of 10 Gigabit Ethernet are just now becoming available, and will be the most expensive. To see what other sites have deployed, visit the Performance Measurement Point Directory page, and look at any of the "PMP Info" links.

        Hardware:

• CPU: 1+ GHz, 512 KB L2 cache, 133 MHz FSB
• Memory: 512MB minimum, with a motherboard and chipset that supports memory interleaving
• Disk: no stringent requirement, something comfortable. 18 GB is a good minimum value as of early 2005.
• NIC: One-Way Ping only requires FastEthernet. For Gigabit Ethernet, recent motherboard 1000bTX interfaces are sufficient (for example, on Dell rack-mounted servers [e.g. 2650, 1850]). We have used SysKonnect multi-mode fiber interfaces in Abilene; we are told the Intel multi-mode fiber interfaces work best in Dell 2650s.
• Bus: at least 64-bit 66MHz PCI for GigE. (Make sure your NIC and Bus are compatible.)

        OS:

• Linux: Latest kernel version that supports Web100, see the Web100 download page.
• FreeBSD: the current production release should be sufficient, see the FreeBSD site. Note that we haven't tested the latest one just yet; Abilene runs an older version (4.6) and we had some problems starting NTP automatically in release 5.1. That should be fixed in the current release (5.4 as of this writing), but if you have problems let us know (we want to ensure we can use the latest FreeBSD release). You can also try installing the legacy production release (4.11).

        Software:

• C development environment (compiler/libraries/make etc.)
• Web100 libraries/tools
• libpcap library
• we recommend ensuring you have a recent Perl release (5.8.0 or greater), but it is not required to run any of the tools individually.

Note: NDT web100srv process needs root access

One-Way Ping Requirements:
(These differences are only needed if an actual hardware clock will be connected to the host for better accuracy. This case will not be covered at the workshop unless there are specific requests for it, and extra time is alloted for it. This is a non-trivial exercise.)

        OS:

• FreeBSD 5.3 (NTP PPS kernel turned on in kernel config)        

        NTP:

• UDP 123

        One-Way Ping:

• UDP * (all ephemeral outgoing)
• UDP * (all ephemeral incoming - administrator selectable for upcoming version)
• TCP 4822 (4824 for the upcoming version)

        Bandwidth Test Controller :

• UDP 5001-5010 (iperf ports - admin configurable, but these are recommended for matching with other sites)
• TCP 5001-5010 (iperf ports - admin configurable, but these are recommended for matching with other sites)
• (The "receiver" gets to define the port number, so another reasonable solution is to allow anything outgoing and only a specific set incoming.)
• TCP 4823
• TCP (* outgoing for peer communication between bwctld's)
• TCP (XX incoming - admin configurable, incoming for peer communication between bwctld's. On Abilene we just use ephemeral, we could suggest something I suppose...)

        NDT:

• TCP 7123        (fakewww server default - or real web server)
• TCP 3001-3003 (web100srv ports - testing and analysis engine)