How You Can Run The Demos
Contents
Getting Started
- Contact
If you have problems with the instructions on this page,
send email to Charlie (sigcomm AT onl.wustl.edu).
- Get an ONL account
- Preliminaries
- After account setup
Do the following only
after you get your ONL account confirmation email.
Some of the examples assume that you can run ssh
from the command-line.
If you don't, then run your ssh client tool.
Replace USERNAME below with your ONL username.
client> ssh USERNAME@onl.wustl.edu # NOT NOT NOT onlusr.wustl.edu
# The host name onl.arl.wustl.edu also works
onlusr> # you should get this prompt
This verifies that your password works and that you can
ssh to the ONL user node.
ONL "Getting Started" Web Page
- In your browser, open the ONL web page
(
http://www.onl.wustl.edu ).
- Log into the ONL website using the same password
that you used to ssh to onlusr.
The sidebar bar should show additional menu items.
- Select the Getting Started link in the
sidebar and follow the instructions skipping
any parts that you have already done.
Note:
It is important that you can build the ssh
tunnel AND that you follow the instructions for
verifying that it works.
At this point:
- You should have JRE 1.6, ssh and the
RLI.jar file on your machine.
- You have verified that you can ssh to the
onlusr host.
- You have verified that you can run the RLI GUI on
your machine and that it can communicate with
the ONL testbed.
Back to Table of Contents
The TCP Demo
- The .onldir directory
- Get the configuration file
- Download the file demo1.exp (see below) and copy
it to the .onldir directory on your machine.
This may involve saving it (using your browser's
Save As ... menu item) into a download directory
and then copying it to the .onldir directory.
- Click this link for the
demo1.exp file.
This file will be used for both the TCP and the
Multicast demos.
- Open the configuration file
- Start the RLI either through the command line
(java -jar RLI.jar) or by selecting the RLI icon
on your Desktop.
- In the RLI menu, select File => Open.
- Then, select demo1.exp and then select the
Open button to open the configuration.
- Build the ssh tunnel
- Open an ssh tunnel to ONL.
The easiest way to do this is through a Linux or Cygwin
command-line:
ssh -L 7070:onlsrv:7070 Username@onl.wustl.edu)
See the ONL web page for other ways to build the tunnel.
The prompt [Username@onlusr ~]$ should appear.
- We will refer to this window as the onlusr window below.
- Reserve ONL resources for your experiment
- In the RLI menu, select File => Make Reservation.
- Enter 1 in the hours box then click Enter.
- Enter your user name and password when prompted.
If there are enough resources available, you will get
a message that contains your reservation start time.
If that time is in the future, you will have to wait
until then to continue
You can also verify that you have a reservation by selecting
the My Reservations link in the sidebar of the
ONL web site.
- Get ONL resources for your experiment
- Once your reservation start time has come,
select File => Commit in the RLI menu
(after re-opening the demo1.exp file
if you have closed the RLI since making your reservation).
- It will take up to a few minutes to set up all of the
resources in your configuration, and the message at the
bottom of the RLI will change from Committing to
Commit Completed when everything is ready.
You should also see that the links are now solid black
and the RLI icons are dark colors.
- Get demo shell scripts
- Copy the demo scripts to the ./sigcomm_demo1
directory in your ONL home directory by
running this command in your onlusr window:
onlusr> cp -r ~onl/demos/sigcomm_demo1 ~
- Change to the demo directory (onlusr window):
onlusr> cd sigcomm_demo1
onlusr> ls -l
You should see five scripts in this directory:
mcSndrs, sack-off-forall,
sack-on-forall, tcp, tcpRcvrs.
- Send TCP traffic (onlusr window)
- To configure TCP on the end hosts, start the TCP senders,
and start the TCP receivers, enter this command:
onlusr> ./sack-on-forall; ./tcpRcvrs; ./tcp
Three iperf senders (clients) and
three receivers (servers) are now running and will continue
to run until you terminate them or terminate the RLI.
- Change the Y-axis label on the TCP chart labeled
TCP Bandwidth to Mb/s by doing the following
in the chart window:
- Select View => Change Y-Axis Label
- Select Mb/s in the pop-up window.
- Change the Y-axis label on the TCP chart labeled
TCP Queues to KB (KiloBytes) by doing the following
in the chart window:
- Select View => Change Y-Axis Label
- Select KB in the pop-up window.
- Things you can try
Note:
Remember that
whenever you make a configuration change in the RLI, they
will not take effect until you have committed the changes
by selecting File => Commit in the RLI menu.
- Look at the names, properties, and menus of the NPRs
by clicking on the center of the NPR icons.
- Look at the names, properties, and menus of the ports
on some of the two NPRs in the dumbbell configuration
by clicking on the port of the NPR icons and selecting
configuration menus.
- Change the bottleneck output port capacity
- Select port 0 on NPR 5 (left router in the
dumbell topology or the router in the southwest
corner) to get the port menu.
- Select Configuration => Queue Table.
- Select File => Commit in the main RLI
window.
- What is the effect of this change?
- Reset the port capacity to 300 Mb/s.
- Change the size of one of the queues at the bottleneck
port
- Select port 0 on NPR 5 (left router in the
dumbell topology or the router in the southwest
corner) to get the port menu
- Select Configuration => Queue Table
- Change the threshold parameter value for
one or more of the three queues (64, 65, 66).
- Select File => Commit in the main RLI
window.
- What is the effect of this change?
- Reset the size of the queue to 600000 bytes.
- Change the route that packets from host n5p1 take by
making the prirority of the route table at
port 1, NPR 5 (southwest corner) be higher than the
filter entry (Note: the filters have been configured
to have a priority of 50; so a priority of 40 for the
route table will make the route table entries higher priority
than the filter).
- Select port 1 on NPR 5 (southwest corner).
- Select Configuration => Route Table.
- Change the priority to 40.
- Change the sixth route table entry
(192.168.6.0/24, 0, 16) to
(192.168.6.0/24, 4, 16).
- Remember to select File => Commit.
- What is the effect of this change?
Back to Table of Contents
The Multicast Demo
- The TCP demo
- You can leave the TCP Demo running or you can stop the
TCP senders before starting the Multicast Demo.
If you want to reuse the command-line window that you
used in the TCP Demo, you wil need to stop the TCP senders.
Here is one way to stop them (onlusr window):
- Enter ctrl-c.
This will kill the tcp script that is used
to repeatedly launch the three iperf TCP
senders.
Each sender may continue to send traffic but will
terminate when they have finished sending their
30-seconds of traffic.
The three iperf receivers are still running,
but that is OK.
- If you want to leave the TCP Demo running then you probably
want to open up another command-line window; ssh
to onl.wustl.edu; and go to the
sigcomm_demo1 directory.
- Configuration file
- This demo is run with the same configuration file that
you used in the TCP Demo.
If you just finished the TCP Demo, then go to the next
step.
- If you are starting this demo from scratch, you will need
to follow the instructions for the TCP Demo to commit
resources for the demo.
In the command-line window, go to your sigcomm_demo1
directory where the scripts are.
- Run the Multicast Demo (onlusr window).
- To start the multicast senders, enter this command:
Back to Table of Contents
Revised: Aug 13, 2009