Bandwidth to the World - host requirements

Les Cottrell, last update Jan 24, '05
Bulk Throughput Measurements | Bulk Throughput Simulation | Windows vs. streams | Effect of load on RTT and loss | Bulk file transfer measurements

Also see Installation and Program Logic Manual of the SLAC WAN Bandwidth Tests (IEPM-BW) hardware & software requirements.

Remote/Monitored host

There are two possibilities. One requires the administrator of the remote host to install required servers, the other requires the administrator to set up an account (iepm) and password for us so we can install the remote host toolkit.

Admin at Remote site installs servers

The host requirements are roughly: CPU: >= 1000MHz, NIC card >= 100Mbits/s full duplex (GE preferred), 64 bit 66MHz PCI bus. If site has good connectivity to the Internet (e.g. >= OC3), then a GE interface is necessary. The host SHOULD be registered with DNS.

SLAC installs remote host toolkit

We need an account ideally with the with the name of iepm, running under the tc shell (tcsh), on a suitable Linux or Solaris host at your site. The host must also support ssh. The $HOME directory must not be in AFS space, NFS or local space is fine.

CPU: >= 1000MHz, NIC card >= 100Mbits/s full duplex (GE preferred), 64 bit 66MHz PCI bus. If site has good connectivity to the Internet (e.g. >= OC3), then a GE interface is necessary. Disk space to save a file copy of up to 2GBytes. Ideally this disk space should be mounted so the file cannot be cached and it must not be /tmp space mapped to swap/memory space.

Operating system: Linux 2.4 or later

Iperf processes appear to take (according to top) about 5MB, there should only be one iperf process running at a time on the remote host for IEPM. In addition they need roughly 2*streams +1 window buffers. Typical window buffers * streams are about 4MBytes for each process.

System tools: ssh protocol version 1 or 2, gunzip, tar, make

Tools: pico, C++ (c++ or g++), C (gcc or cc), Perl 5, Pthreads library, 64 bit libc support, libz

Need an account with userid cottrell with ssh access & RSAAuthentication yes in /etc/ssh/ssh_config, does not need root.

TCP ports 22 (for ssh), 5000-5011 (for iperf, 5000 is used most frequently, 5001-5011 are used for occasional measurenents with varying window sizes, each port in the range 5001-5011 uses a different maximum receive window size), 5003 for thrulay, 5020-5022 (for bbftp, most of the traffic will be seen on 5020, 5021 is the client's default control port and 5022 is the server control port), 5031-5039 (for bbcp, it tries 5031 first and only if it is already in use will it try a different port in the specified range), and 2811 (for GridFTP) must be open (inbound to the site) from the outside world. Also UDP port 8365 for pathchirp, UDP 55001 and TCP 55002 for pathload and port 8176 must be opened for ABwE/abing.

We also need to know the speed of the NIC, and the speed of the site's connection to the Internet. If there are any unusual features such as the host is multihomed (in which case we need to know the IP address of the interface to use), it may be important to let us know.

We will create the following directories: $HOME/bin, $HOME/package, $HOME/pinger/load. We will also set up a .forward file to forward email to the account. Click here to find instructions for conducting a localmake on remote hosts.

Network Impact

A set of measurements are made to each remote host about every 90 minutes. Each set typically consists of a set of 10 pings, a traceroute, an ssh (port 22) to start the iperf client, a 10 second iperf TCP client (usually port 5000) run to measure throughput, a 10 second bbcp memory-to-memory run, a 10 second bbcp disk-to-disk run, and a 10 second bbftp run. The traffic generated by the iperf client, bbcp and bbftp runs depends on the bottleneck achievable throughput of the link. See SLAC WAN bandwidth Measurement Tests for some examples.

Monitoring Host

The monitoring host has the same requirements as the remote host, plus:

Demo Host

The demo host for iGrid2002 and SC2002 needs all the above plus:
Created November 2, 2001, last update July 11, 2002.
Comments to