Version 4 (modified by 8 years ago) (diff) | ,
---|
A Tutorial on Systematic Experimental Design
3. End-to-End Validation
The RSpec file 4node-stitching.rspec
is modified from 4node-final.rspec
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
andserver
, respectively.
Run ping
and traceroute
from the client
to the server
pjayant@client:~$ ping 192.168.20.10 PING 192.168.20.10 (192.168.20.10) 56(84) bytes of data. 64 bytes from 192.168.20.10: icmp_seq=1 ttl=61 time=35.3 ms 64 bytes from 192.168.20.10: icmp_seq=2 ttl=61 time=35.1 ms 64 bytes from 192.168.20.10: icmp_seq=3 ttl=61 time=34.3 ms 64 bytes from 192.168.20.10: icmp_seq=4 ttl=61 time=34.6 ms ^C --- 192.168.20.10 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 192.168.20.10 traceroute to 192.168.20.10 (192.168.20.10), 30 hops max, 60 byte packets 1 router-1-link-5 (192.168.10.10) 1.153 ms 1.077 ms 1.013 ms 2 router-4-link-3 (192.168.4.1) 31.990 ms router-2-link-0 (192.168.1.2) 1.942 ms router-4-link-3 (192.168.4.1) 31.849 ms 3 192.168.3.1 (192.168.3.1) 33.083 ms 33.019 ms 32.934 ms 4 192.168.20.10 (192.168.20.10) 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-2
was about 38ms, and this reflected the delay between the aggregate located at Wisconsin and the aggregate located at New York City, and this shows the delay of the stitched link.