Version 10 (modified by, 5 years ago) (diff)


A Tutorial on Systematic Experimental Design

Step I: Single Node

Step II: Small Topology

Step III: Scaling Up

Image Map

3. End-to-End Validation

The RSpec file Stitcher_rspec.xml is modified from Quagga_4node_final_rspec.xml created in Step II, so all software has been installed to the slivers already.

Follow the steps in Manually Configure OSPF section and configure OSPF on all the nodes in your topology.

Open two terminals, and login to the client and server, respectively.

Run ping and traceroute from the client to the server

pjayant@client:~$ ping
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=61 time=35.3 ms
64 bytes from icmp_seq=2 ttl=61 time=35.1 ms
64 bytes from icmp_seq=3 ttl=61 time=34.3 ms
64 bytes from icmp_seq=4 ttl=61 time=34.6 ms
--- ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 34.388/34.893/35.399/0.408 ms
pjayant@client:~$ traceroute
traceroute to (, 30 hops max, 60 byte packets
 1  router-1-link-5 (  1.153 ms  1.077 ms  1.013 ms
 2  router-4-link-3 (  31.990 ms router-2-link-0 (  1.942 ms router-4-link-3 (  31.849 ms
 3 (  33.083 ms  33.019 ms  32.934 ms
 4 (  33.681 ms  33.560 ms  33.521 ms

From the traceroute result, we found that the delay between the client and router-1, the delay between router-3( and the server( were very small (about 0.5ms), this is because the end host and the associated router are from the same aggregate. However, the delay between router-1( and router-4( was about 30ms, and this reflected the delay between the aggregate located at Kentucky and the aggregate located at New Jersey, and this shows the delay of the stitched link.

Previous: Scaling Up: Design/Setup

Next: Scaling Up: Finish