| Version 4 (modified by , 10 years ago) (diff) |
|---|
Rutgers University Stitching Confirmation Tests
This pages capture the detailed test logs for each test defined in the New Site Stitching Confirmation Tests page. For the sites status see the New Site Stitching Confirmation Tests Status page.
IG-ST-1 New Site to GPO IG topology
The Rutgers site advertises the following stitching details:
<stitching xmlns="http://hpn.east.isi.edu/rspec/ext/stitch/0.1/" lastUpdateTime="2014-08-01T18:20:36Z" >
<aggregate id="urn:publicid:IDN+instageni.rutgers.edu+authority+cm" url="https://www.instageni.rutgers.edu:12369/protogeni/xmlrpc/am">
<aggregatetype>protogeni</aggregatetype>
<stitchingmode>chainANDTree</stitchingmode>
<scheduledservices>false</scheduledservices>
<negotiatedservices>false</negotiatedservices>
<lifetime id="life">
<start type="time">2014-08-01T18:20:36Z</start>
<end type="time">2014-08-01T18:20:36Z</end>
</lifetime>
<node id="urn:publicid:IDN+instageni.rutgers.edu+node+procurve2">
<port id="urn:publicid:IDN+instageni.rutgers.edu+stitchport+procurve2:1.19.ion">
<capacity>1000000</capacity>
<maximumReservableCapacity>1000000</maximumReservableCapacity>
<minimumReservableCapacity>1000</minimumReservableCapacity>
<granularity>1</granularity>
<link id="urn:publicid:IDN+instageni.rutgers.edu+interface+procurve2:1.19.ion">
<remoteLinkId>urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:xe-0/2/2:rutgers-ig</remoteLinkId>
<trafficEngineeringMetric>10</trafficEngineeringMetric>
<capacity>1000000</capacity>
<maximumReservableCapacity>1000000</maximumReservableCapacity>
<minimumReservableCapacity>1000</minimumReservableCapacity>
<granularity>1</granularity>
<switchingCapabilityDescriptor>
<switchingcapType>l2sc</switchingcapType>
<encodingType>ethernet</encodingType>
<switchingCapabilitySpecificInfo>
<switchingCapabilitySpecificInfo_L2sc>
<interfaceMTU>1500</interfaceMTU>
<vlanRangeAvailability>3730-3739</vlanRangeAvailability>
<vlanTranslation>false</vlanTranslation>
</switchingCapabilitySpecificInfo_L2sc>
</switchingCapabilitySpecificInfo>
</switchingCapabilityDescriptor>
</link>
</port>
</node>
</aggregate>
</stitching>
Experimenter may not need any of this data, but it is helpful to reference when trying to determine how many VLANs are delegated for stitching at the site or how much bandwidth can be requested.
Create a slice and then create the stitched slivers with the RSpec IG-ST-1-ion.rspec:
$ stitcher createsliver IG-ST-1 IG-ST-1-ion.rspec 14:25:09 INFO : Configured logging from file /home/lnevers/gcf-2.6-oess/src/gcf/stitcher_logging.conf 14:25:09 INFO : Reading slice IG-ST-1 credential... 14:25:09 INFO : Slice urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Proj_01+slice+IG-ST-1 expires on 2014-08-08 18:23:48 UTC 14:25:09 INFO : Calling SCS... 14:25:10 INFO : Multi-AM reservation will include resources from these aggregates: 14:25:10 INFO : <Aggregate rutgers-ig> 14:25:10 INFO : <Aggregate gpo-ig> 14:25:10 INFO : <Aggregate ion> 14:25:10 INFO : Stitcher doing createsliver at <Aggregate rutgers-ig>... 14:25:26 INFO : ... Allocation at <Aggregate rutgers-ig> complete. 14:25:26 INFO : Stitcher doing createsliver at <Aggregate gpo-ig>... 14:25:41 INFO : ... Allocation at <Aggregate gpo-ig> complete. 14:25:41 INFO : Stitcher doing createsliver at <Aggregate ion>... 14:26:26 INFO : DCN AM <Aggregate ion>: must wait for status ready.... 14:26:26 INFO : Pausing 30 seconds to let circuit become ready... 14:27:03 INFO : DCN circuit 111291 is ready at <Aggregate ion> 14:27:10 INFO : Getting credential from file /tmp/slice-ch-geni-net-Luisa_Nevers-Test-Proj_01-IG-ST-1-for-lnevers-cred.xml 14:27:10 INFO : ... Allocation at <Aggregate ion> complete. 14:27:10 INFO : All aggregates are complete. 14:27:10 INFO : Your resources expire at 2 different times at different AMs. The first expiration is 2014-08-02 18:25:45 UTC at <Aggregate ion>. Second expiration is 2014-08-08T18:23:48 UTC. 14:27:10 INFO : Saved combined reservation RSpec at 3 AMs to file '/home/lnevers/gcf-test/stitch-test/Rutgers/IG-ST-1-manifest-rspec-stitching-combined.xml' Success: Reserved resources in slice IG-ST-1 at 3 Aggregates (including 1 intermediate aggregate(s) not in the original request), creating 1 stitched link(s).
Determined login information at each Rutgers and GPO aggregate:
$ readyToLogin.py IG-ST-1 -a rutgers-ig .... ig-rut's geni_status is: ready User lnevers logs in to ig-rut using: ssh -p 31802 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc3.instageni.rutgers.edu $ readyToLogin.py IG-ST-1 -a gpo-ig .... ig-gpo's geni_status is: changing User lnevers logs in to ig-gpo using: ssh -p 37946 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc4.instageni.gpolab.bbn.com
Measurements
Iperf InstaGENI GPO VM to InstaGENI Rutgers VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2014-08-XX
One Client_
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.0 sec 143 MBytes 19.9 Mbits/sec
Five Clients
[ ID] Interval Transfer Bandwidth [ 6] 0.0-60.2 sec 30.2 MBytes 4.21 Mbits/sec [ 5] 0.0-60.5 sec 24.8 MBytes 3.43 Mbits/sec [ 4] 0.0-60.6 sec 34.2 MBytes 4.74 Mbits/sec [ 3] 0.0-61.2 sec 27.2 MBytes 3.73 Mbits/sec [ 7] 0.0-61.3 sec 28.4 MBytes 3.88 Mbits/sec [SUM] 0.0-61.3 sec 145 MBytes 19.8 Mbits/sec
Ten Clients
[ ID] Interval Transfer Bandwidth [ 8] 0.0-60.2 sec 18.4 MBytes 2.56 Mbits/sec [ 3] 0.0-60.4 sec 12.0 MBytes 1.67 Mbits/sec [ 5] 0.0-60.5 sec 9.62 MBytes 1.34 Mbits/sec [ 12] 0.0-60.6 sec 9.50 MBytes 1.32 Mbits/sec [ 6] 0.0-60.7 sec 17.9 MBytes 2.47 Mbits/sec [ 4] 0.0-60.9 sec 22.9 MBytes 3.15 Mbits/sec [ 10] 0.0-61.0 sec 15.9 MBytes 2.18 Mbits/sec [ 11] 0.0-61.4 sec 16.5 MBytes 2.26 Mbits/sec [ 7] 0.0-62.1 sec 15.9 MBytes 2.14 Mbits/sec [ 9] 0.0-62.2 sec 8.62 MBytes 1.16 Mbits/sec [SUM] 0.0-62.2 sec 147 MBytes 19.8 Mbits/sec
Iperf InstaGENI GPO VM to InstaGENI Rutgers VM (UDP) - UDP buffer size: 224 KByte (default)
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.0 sec 719 MBytes 101 Mbits/sec [ 3] Sent 512813 datagrams [ 3] Server Report: [ 3] 0.0-60.2 sec 139 MBytes 19.4 Mbits/sec 12.952 ms 413453/512811 (81%) [ 3] 0.0-60.2 sec 1 datagrams received out-of-order
Ping from InstaGENI GPO VM to the InstaGENI Rutgers VM
60 packets transmitted, 60 received, 0% packet loss, time 59108ms rtt min/avg/max/mdev = 15.522/15.701/15.953/0.116 ms
Iperf InstaGENI Rutgers VM to GPO InstaGENI VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2014-08-01
One Client_
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.1 sec 143 MBytes 19.9 Mbits/sec
Five Clients
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.0 sec 27.9 MBytes 3.89 Mbits/sec [ 7] 0.0-60.3 sec 36.6 MBytes 5.10 Mbits/sec [ 6] 0.0-60.4 sec 21.6 MBytes 3.01 Mbits/sec [ 4] 0.0-60.5 sec 30.4 MBytes 4.21 Mbits/sec [ 5] 0.0-60.7 sec 28.4 MBytes 3.92 Mbits/sec [SUM] 0.0-60.7 sec 145 MBytes 20.0 Mbits/sec
Ten Clients
[ ID] Interval Transfer Bandwidth [ 6] 0.0-60.4 sec 19.2 MBytes 2.68 Mbits/sec [ 10] 0.0-60.5 sec 15.4 MBytes 2.13 Mbits/sec [ 9] 0.0-60.5 sec 18.1 MBytes 2.51 Mbits/sec [ 11] 0.0-60.7 sec 13.5 MBytes 1.87 Mbits/sec [ 8] 0.0-60.8 sec 8.00 MBytes 1.10 Mbits/sec [ 12] 0.0-60.8 sec 11.0 MBytes 1.52 Mbits/sec [ 7] 0.0-60.9 sec 12.2 MBytes 1.69 Mbits/sec [ 3] 0.0-61.0 sec 20.4 MBytes 2.80 Mbits/sec [ 5] 0.0-61.1 sec 11.8 MBytes 1.61 Mbits/sec [ 4] 0.0-62.1 sec 16.9 MBytes 2.28 Mbits/sec [SUM] 0.0-62.1 sec 146 MBytes 19.8 Mbits/sec
Iperf InstaGENI Rutgers VM to GPO InstaGENI VM (UDP) - UDP buffer size: 224 KByte (default)
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.0 sec 719 MBytes 101 Mbits/sec [ 3] Sent 512757 datagrams [ 3] Server Report: [ 3] 0.0-60.0 sec 139 MBytes 19.5 Mbits/sec 0.109 ms 413391/512752 (81%) [ 3] 0.0-60.0 sec 1 datagrams received out-of-order
Ping from InstaGENI Rutgers VM to GPO InstaGENI VM
60 packets transmitted, 60 received, 0% packet loss, time 59110ms rtt min/avg/max/mdev = 15.399/15.701/15.905/0.121 ms
IG-ST-2 New Site to GPO IG Loop topology
Create a slice and then create the stitched slivers with the RSpec IG-ST-2.rspec:
$ stitcher.py createsliver IG-ST-2 IG-ST-2.rspec -o 15:42:04 INFO : Configured logging from file /home/lnevers/gcf-2.6-oess/src/gcf/stitcher_logging.conf 15:42:04 INFO : Reading slice IG-ST-2 credential... 15:42:04 INFO : Slice urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Proj_01+slice+IG-ST-2 expires on 2014-08-08 19:10:48 UTC 15:42:04 INFO : Calling SCS... 15:42:06 INFO : Multi-AM reservation will include resources from these aggregates: 15:42:06 INFO : <Aggregate rutgers-ig> 15:42:06 INFO : <Aggregate gpo-ig> 15:42:06 INFO : <Aggregate ion> 15:42:06 INFO : Stitcher doing createsliver at <Aggregate rutgers-ig>... 15:42:22 INFO : ... Allocation at <Aggregate rutgers-ig> complete. 15:42:22 INFO : Stitcher doing createsliver at <Aggregate gpo-ig>... 15:42:40 INFO : ... Allocation at <Aggregate gpo-ig> complete. 15:42:40 INFO : Stitcher doing createsliver at <Aggregate ion>... 15:43:25 INFO : DCN AM <Aggregate ion>: must wait for status ready.... 15:43:25 INFO : Pausing 30 seconds to let circuit become ready... 15:44:02 INFO : Pausing 30 seconds to let circuit become ready... 15:44:39 INFO : DCN circuit 111341 is ready at <Aggregate ion> 15:44:39 INFO : DCN circuit 111331 is ready at <Aggregate ion> 15:44:46 INFO : Getting credential from file /tmp/slice-ch-geni-net-Luisa_Nevers-Test-Proj_01-IG-ST-2-for-lnevers-cred.xml 15:44:46 INFO : ... Allocation at <Aggregate ion> complete. 15:44:46 INFO : All aggregates are complete. 15:44:46 INFO : Your resources expire at 2 different times at different AMs. The first expiration is 2014-08-02 19:42:44 UTC at <Aggregate ion>. Second expiration is 2014-08-08T19:10:48 UTC. 15:44:46 INFO : Saved combined reservation RSpec at 3 AMs to file '/home/lnevers/gcf-test/stitch-test/Rutgers/IG-ST-2-manifest-rspec-stitching-combined.xml' Success: Reserved resources in slice IG-ST-2 at 3 Aggregates (including 1 intermediate aggregate(s) not in the original request), creating 2 stitched link(s).
Determined login information at each Rutgers and GPO aggregate:
$ readyToLogin.py IG-ST-2 -a rutgers-ig .... ig-rut's geni_status is: ready User lnevers logs in to ig-rut using: ssh -p 32058 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.rutgers.edu $ readyToLogin.py IG-ST-2 -a gpo-ig .... ig-gpo's geni_status is: ready User lnevers logs in to ig-gpo using: ssh -p 38458 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.gpolab.bbn.com
Login to GPO host and ping the remote on each of the two interfaces. Below is the ping output for the GPO site:
$ ping 10.10.4.2 -c 60 -q PING 10.10.4.2 (10.10.4.2) 56(84) bytes of data. --- 10.10.4.2 ping statistics --- 60 packets transmitted, 60 received, 0% packet loss, time 59062ms rtt min/avg/max/mdev = 15.059/15.379/31.411/2.090 ms $ ping 192.168.4.2 -c 60 -q PING 192.168.4.2 (192.168.4.2) 56(84) bytes of data. --- 192.168.4.2 ping statistics --- 60 packets transmitted, 60 received, 0% packet loss, time 59044ms rtt min/avg/max/mdev = 15.050/15.373/31.460/2.095 ms
IG-ST-3 IG-ST-3 New Site 3 node linear topology
Create a slice and then create the stitched slivers with the RSpec IG-ST-3.rspec:
$ stitcher.py createsliver IG-ST-3 IG-ST-3.rspec -o 08:15:01 INFO : Configured logging from file /home/lnevers/gcf-2.6-oess/src/gcf/stitcher_logging.conf 08:15:02 INFO : Reading slice IG-ST-3 credential... 08:15:02 INFO : Slice urn:publicid:IDN+ch.geni.net:Luisa_Nevers-Test-Proj_01+slice+IG-ST-3 expires on 2014-08-11 11:58:32 UTC 08:15:02 INFO : Calling SCS... 08:15:04 INFO : Multi-AM reservation will include resources from these aggregates: 08:15:04 INFO : <Aggregate rutgers-ig> 08:15:04 INFO : <Aggregate ion> 08:15:04 INFO : <Aggregate gpo-ig> 08:15:04 INFO : <Aggregate utah-pg> 08:15:04 INFO : <Aggregate utah-ig> 08:15:04 INFO : Stitcher doing createsliver at <Aggregate rutgers-ig>... 08:15:20 INFO : ... Allocation at <Aggregate rutgers-ig> complete. 08:15:20 INFO : Stitcher doing createsliver at <Aggregate gpo-ig>... 08:15:34 INFO : ... Allocation at <Aggregate gpo-ig> complete. 08:15:34 INFO : Stitcher doing createsliver at <Aggregate utah-pg>... 08:16:10 INFO : ... Allocation at <Aggregate utah-pg> complete. 08:16:10 INFO : Stitcher doing createsliver at <Aggregate ion>... 08:16:55 INFO : DCN AM <Aggregate ion>: must wait for status ready.... 08:16:55 INFO : Pausing 30 seconds to let circuit become ready... 08:17:32 INFO : Pausing 30 seconds to let circuit become ready... 08:18:09 INFO : DCN circuit 111581 is ready at <Aggregate ion> 08:18:09 INFO : DCN circuit 111591 is ready at <Aggregate ion> 08:18:17 INFO : Getting credential from file /tmp/slice-ch-geni-net-Luisa_Nevers-Test-Proj_01-IG-ST-3-for-lnevers-cred.xml 08:18:17 INFO : ... Allocation at <Aggregate ion> complete. 08:18:17 INFO : Stitcher doing createsliver at <Aggregate utah-ig>... 08:18:31 INFO : ... Allocation at <Aggregate utah-ig> complete. 08:18:31 INFO : All aggregates are complete. 08:18:31 INFO : Your resources expire at 4 different times at different AMs. The first expiration is 2014-08-04 17:15:38 UTC at <Aggregate utah-pg> and <Aggregate utah-ig>. Second expiration is 2014-08-05T12:16:14 UTC. 08:18:31 INFO : Saved combined reservation RSpec at 5 AMs to file '/home/lnevers/gcf-test/stitch-test/Rutgers/IG-ST-3-manifest-rspec-stitching-combined.xml' Success: Reserved resources in slice IG-ST-3 at 5 Aggregates (including 2 intermediate aggregate(s) not in the original request), creating 2 stitched link(s).
Determined login information the Rutgers host:
$ readyToLogin.py IG-ST-3 -a rutgers-ig .... ig-rut's geni_status is: ready User lnevers logs in to ig-rut using: ssh -p 32314 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.rutgers.edu
Login to the Rutgers host and ping each remote:
#ping GPO IG [lnevers@ig-rut ~]$ ping 192.168.2.1 -c 60 -q PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. --- 192.168.2.1 ping statistics --- 60 packets transmitted, 60 received, 0% packet loss, time 59070ms rtt min/avg/max/mdev = 15.046/15.372/30.623/1.989 ms # Utah IG [lnevers@ig-rut ~]$ ping 192.168.4.1 -c 60 -q PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data. --- 192.168.4.1 ping statistics --- 60 packets transmitted, 0 received, +45 errors, 100% packet loss, time 59013ms pipe 3
