Changes between Version 1 and Version 2 of GENIExperimenter/Tutorials/SystematicExprCaseStudy/ScalingUp/Execute
- Timestamp:
- 08/13/14 11:56:17 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/SystematicExprCaseStudy/ScalingUp/Execute
v1 v2 30 30 = 3. End-to-End Validation = 31 31 32 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. Open two terminals, and login to the client and server, respectively.32 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. Open two terminals, and login to the `client` and `server`, respectively. 33 33 34 Run ping and traceroute from the client to the server34 Run `ping` and `traceroute` from the `client` to the `server` 35 35 36 36 {{{ … … 54 54 }}} 55 55 56 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 forthe stitched link.56 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. 57 57 58 58