Version 3 (modified by 9 years ago) (diff) | ,
---|
University of Missouri Kansas City InstaGENI 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 UMKC site advertises the following stitching details:
<stitching xmlns="http://hpn.east.isi.edu/rspec/ext/stitch/0.1/" lastUpdateTime="2015-04-09T13:59:55Z" > <aggregate id="urn:publicid:IDN+instageni.umkc.edu+authority+cm" url="https://www.instageni.umkc.edu:12369/protogeni/xmlrpc/am"> <aggregatetype>protogeni</aggregatetype> <stitchingmode>chainANDTree</stitchingmode> <scheduledservices>false</scheduledservices> <negotiatedservices>false</negotiatedservices> <lifetime id="life"> <start type="time">2015-04-09T13:59:55Z</start> <end type="time">2015-04-09T13:59:55Z</end> </lifetime> <node id="urn:publicid:IDN+instageni.umkc.edu+node+procurve2"> <port id="urn:publicid:IDN+instageni.umkc.edu+stitchport+procurve2:1.19.al2s"> <capacity>1000000</capacity> <maximumReservableCapacity>1000000</maximumReservableCapacity> <minimumReservableCapacity>1000</minimumReservableCapacity> <granularity>1</granularity> <link id="urn:publicid:IDN+instageni.umkc.edu+interface+procurve2:1.19.al2s"> <remoteLinkId>urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:umkc-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>1730-1744</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-al2s.rspec:
$ stitcher.py createsliver IG-ST-1 IG-ST-1-al 2s.rspec -o 12:13:01 INFO : Configured logging from file /home/lnevers/gcf-2.9-pre1/src/gcf/stitcher_logging.conf 12:13:01 INFO : Reading slice IG-ST-1 credential... 12:13:01 INFO : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-1 expires on 2015-05-30 00:00:00 UTC 12:13:01 INFO : Calling SCS... 12:13:03 INFO : Multi-AM reservation will include resources from these aggregates: 12:13:03 INFO : <Aggregate umkc-ig> 12:13:03 INFO : <Aggregate gpo-ig> 12:13:03 INFO : <Aggregate al2s> 12:13:03 INFO : Stitcher doing createsliver at <Aggregate umkc-ig>... 12:13:20 INFO : ... Allocation at <Aggregate umkc-ig> complete. 12:13:20 INFO : Stitcher doing createsliver at <Aggregate gpo-ig>... 12:13:38 INFO : ... Allocation at <Aggregate gpo-ig> complete. 12:13:38 INFO : Stitcher doing createsliver at <Aggregate al2s>... 12:13:44 INFO : ... Allocation at <Aggregate al2s> complete. 12:13:44 INFO : All aggregates are complete. 12:13:44 INFO : Your resources expire at 2015-05-29T16:03:03 (UTC). 12:13:44 INFO : Saved combined reservation RSpec at 3 AMs to file '/home/lnevers/gcf-test/stitch-test/UMKC/IG-ST-1-manifest-rspec-multiam-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 UMKC and GPO aggregate:
$ readyToLogin.py IG-ST-1 --useSliceAggregates .... ig-gpo's geni_status is: ready User lnevers logs in to ig-gpo using: ssh -p 38714 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc4.instageni.gpolab.bbn.com .... ig-umkc's geni_status is: ready User lnevers logs in to ig-umkc using: ssh -p 31802 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc3.instageni.umkc.edu
Measurements
Iperf InstaGENI GPO VM to InstaGENI UMKC VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2015-04-09
One Client_
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.1 sec 142 MBytes 19.9 Mbits/sec
Five Clients
[ ID] Interval Transfer Bandwidth [ 5] 0.0-60.2 sec 38.8 MBytes 5.40 Mbits/sec [ 7] 0.0-60.4 sec 23.1 MBytes 3.21 Mbits/sec [ 6] 0.0-60.7 sec 37.4 MBytes 5.17 Mbits/sec [ 4] 0.0-61.0 sec 27.1 MBytes 3.73 Mbits/sec [ 3] 0.0-61.0 sec 20.0 MBytes 2.75 Mbits/sec [SUM] 0.0-61.0 sec 146 MBytes 20.1 Mbits/sec
Ten Clients
[ ID] Interval Transfer Bandwidth [ 12] 0.0-60.0 sec 22.4 MBytes 3.13 Mbits/sec [ 8] 0.0-60.1 sec 13.8 MBytes 1.92 Mbits/sec [ 11] 0.0-60.5 sec 11.5 MBytes 1.60 Mbits/sec [ 5] 0.0-60.6 sec 19.4 MBytes 2.68 Mbits/sec [ 4] 0.0-60.7 sec 8.38 MBytes 1.16 Mbits/sec [ 10] 0.0-61.0 sec 9.38 MBytes 1.29 Mbits/sec [ 9] 0.0-61.2 sec 18.6 MBytes 2.55 Mbits/sec [ 7] 0.0-61.2 sec 18.9 MBytes 2.59 Mbits/sec [ 3] 0.0-61.3 sec 13.4 MBytes 1.83 Mbits/sec [ 6] 0.0-61.3 sec 10.8 MBytes 1.47 Mbits/sec [SUM] 0.0-61.3 sec 146 MBytes 20.0 Mbits/sec
Iperf InstaGENI GPO VM to InstaGENI UMKC VM (UDP) - UDP buffer size: 224 KByte (default)
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.0 sec 719 MBytes 100 Mbits/sec [ 3] Sent 512808 datagrams read failed: Connection refused [ 3] WARNING: did not receive ack of last datagram after 3 tries.
Ping from InstaGENI GPO VM to the InstaGENI UMKC VM
60 packets transmitted, 60 received, 0% packet loss, time 59092ms rtt min/avg/max/mdev = 39.836/40.508/43.271/0.560 ms
Iperf InstaGENI UMKC VM to GPO InstaGENI VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2015-04-09
One Client_
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.1 sec 141 MBytes 19.7 Mbits/sec
Five Clients
[ ID] Interval Transfer Bandwidth [ 7] 0.0-60.0 sec 39.8 MBytes 5.55 Mbits/sec [ 5] 0.0-60.2 sec 32.0 MBytes 4.46 Mbits/sec [ 3] 0.0-60.3 sec 29.8 MBytes 4.14 Mbits/sec [ 6] 0.0-60.3 sec 21.9 MBytes 3.04 Mbits/sec [ 4] 0.0-60.4 sec 21.8 MBytes 3.02 Mbits/sec [SUM] 0.0-60.4 sec 145 MBytes 20.2 Mbits/sec
Ten Clients
[ ID] Interval Transfer Bandwidth [ 5] 0.0-59.3 sec 8.62 MBytes 1.22 Mbits/sec [ 6] 0.0-59.8 sec 26.8 MBytes 3.76 Mbits/sec [ 11] 0.0-59.8 sec 15.8 MBytes 2.21 Mbits/sec [ 9] 0.0-59.9 sec 8.50 MBytes 1.19 Mbits/sec [ 7] 0.0-60.2 sec 12.4 MBytes 1.72 Mbits/sec [ 4] 0.0-60.3 sec 18.1 MBytes 2.52 Mbits/sec [ 3] 0.0-60.5 sec 14.8 MBytes 2.04 Mbits/sec [ 8] 0.0-60.7 sec 11.8 MBytes 1.62 Mbits/sec [ 10] 0.0-61.0 sec 14.9 MBytes 2.05 Mbits/sec [ 12] 0.0-61.3 sec 15.4 MBytes 2.10 Mbits/sec [SUM] 0.0-61.3 sec 147 MBytes 20.1 Mbits/sec
Iperf InstaGENI UMKC 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 512771 datagrams [ 3] Server Report: [ 3] 0.0-60.1 sec 139 MBytes 19.4 Mbits/sec 7.206 ms 413529/512766 (81%) [ 3] 0.0-60.1 sec 1 datagrams received out-of-order
Ping from InstaGENI UMKC VM to GPO InstaGENI VM
60 packets transmitted, 60 received, 0% packet loss, time 59086ms rtt min/avg/max/mdev = 39.911/40.353/43.151/0.507 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 12:14:55 INFO : Configured logging from file /home/lnevers/gcf-2.9-pre1/src/gcf/stitcher_logging.conf 12:14:56 INFO : Reading slice IG-ST-2 credential... 12:14:56 INFO : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-2 expires on 2015-05-30 00:00:00 UTC 12:14:56 INFO : Calling SCS... 12:14:58 INFO : Multi-AM reservation will include resources from these aggregates: 12:14:58 INFO : <Aggregate umkc-ig> 12:14:58 INFO : <Aggregate gpo-ig> 12:14:58 INFO : <Aggregate al2s> 12:14:58 INFO : Stitcher doing createsliver at <Aggregate umkc-ig>... 12:15:18 INFO : ... Allocation at <Aggregate umkc-ig> complete. 12:15:18 INFO : Stitcher doing createsliver at <Aggregate gpo-ig>... 12:15:39 INFO : ... Allocation at <Aggregate gpo-ig> complete. 12:15:39 INFO : Stitcher doing createsliver at <Aggregate al2s>... 12:15:48 INFO : ... Allocation at <Aggregate al2s> complete. 12:15:48 INFO : All aggregates are complete. 12:15:48 INFO : Your resources expire at 2015-05-29T16:04:58 (UTC). 12:15:48 INFO : Saved combined reservation RSpec at 3 AMs to file '/home/lnevers/gcf-test/stitch-test/UMKC/IG-ST-2-manifest-rspec-multiam-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 UMKC and GPO aggregate:
$ readyToLogin.py IG-ST-2 --useSliceAggregates .... ig-gpo's geni_status is: ready User lnevers logs in to ig-gpo using: ssh -p 39482 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc5.instageni.gpolab.bbn.com .... ig-umkc's geni_status is: ready User lnevers logs in to ig-umkc using: ssh -p 32314 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc3.instageni.umkc.edu
Login to GPO host and ping the remote on each of the two interfaces. Below is the ping output for the GPO site:
$ remote-execute.py IG-ST-2 -a gpo-ig -m "ping 10.10.4.2 -c 60 -q ;ping 192.168.4.2 -c 60 -q" 1. Find login Info for hosts in slice IG-ST-2 2. Send command 'ping 10.10.4.2 -c 60 -q ;ping 192.168.4.2 -c 60 -q' to ig-gpo 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 59083ms rtt min/avg/max/mdev = 39.947/40.376/45.658/0.760 ms 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 59083ms rtt min/avg/max/mdev = 40.003/40.384/41.473/0.452 ms ... Done with command 'ping 10.10.4.2 -c 60 -q ;ping 192.168.4.2 -c 60 -q' at ig-gpo
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 12:15:04 INFO : Configured logging from file /home/lnevers/gcf-2.9-pre1/src/gcf/stitcher_logging.conf 12:15:04 INFO : Reading slice IG-ST-3 credential... 12:15:04 INFO : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-3 expires on 2015-05-30 00:00:00 UTC 12:15:04 INFO : Calling SCS... 12:15:06 INFO : Multi-AM reservation will include resources from these aggregates: 12:15:06 INFO : <Aggregate cwru-ig> 12:15:06 INFO : <Aggregate umkc-ig> 12:15:06 INFO : <Aggregate al2s> 12:15:06 INFO : <Aggregate gpo-ig> 12:15:06 INFO : Stitcher doing createsliver at <Aggregate cwru-ig>... 12:15:24 INFO : ... Allocation at <Aggregate cwru-ig> complete. 12:15:24 INFO : Stitcher doing createsliver at <Aggregate umkc-ig>... 12:15:44 INFO : ... Allocation at <Aggregate umkc-ig> complete. 12:15:44 INFO : Stitcher doing createsliver at <Aggregate gpo-ig>... 12:16:03 INFO : ... Allocation at <Aggregate gpo-ig> complete. 12:16:03 INFO : Stitcher doing createsliver at <Aggregate al2s>... 12:16:11 INFO : ... Allocation at <Aggregate al2s> complete. 12:16:11 INFO : All aggregates are complete. 12:16:11 INFO : Your resources expire at 2015-05-29T16:05:06 (UTC). 12:16:11 INFO : Saved combined reservation RSpec at 4 AMs to file '/home/lnevers/gcf-test/stitch-test/UMKC/IG-ST-3-manifest-rspec-multiam-combined.xml' Success: Reserved resources in slice IG-ST-3 at 4 Aggregates (including 1 intermediate aggregate(s) not in the original request), creating 2 stitched link(s).}}} Determined login information the UMKC host: {{{ $ readyToLogin.py IG-ST-3 -a umkc-ig .... ig-umkc's geni_status is: ready User lnevers logs in to ig-umkc using: ssh -p 32570 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc3.instageni.umkc.edu }}} Login to the UMKC host and ping each remote: {{{ #ping GPO IG lnevers@ig-umkc:~$ 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 59082ms rtt min/avg/max/mdev = 39.943/40.307/42.830/0.422 ms # UMKCPKS2 IG lnevers@ig-umkc:~$ 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, 60 received, 0% packet loss, time 59100ms rtt min/avg/max/mdev = 22.600/22.893/23.181/0.241 ms }}} == IG-ST-4 New Site to GPO EG interoperability == Create a slice and then create the stitched slivers with the RSpec [http://groups.geni.net/geni/browser/trunk/stitch-examples/UMKC/IG-ST-4.rspec IG-ST-4.rspec], which specifies a 100 Mbps link capacity. This was done to get around the mismatch in link capacity units that exists between IG and EG. {{{ $ stitcher.py createsliver IG-ST-4 IG-ST-4.rspec -o 12:32:19 INFO : Configured logging from file /home/lnevers/gcf-2.9-pre1/src/gcf/stitcher_logging.conf 12:32:20 INFO : Reading slice IG-ST-4 credential... 12:32:20 INFO : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-4 expires on 2015-05-30 00:00:00 UTC 12:32:20 INFO : Calling SCS... 12:32:22 INFO : Multi-AM reservation will include resources from these aggregates: 12:32:22 INFO : <Aggregate umkc-ig> 12:32:22 INFO : <Aggregate al2s> 12:32:22 INFO : <Aggregate gpo-eg> 12:32:22 INFO : Stitcher doing createsliver at <Aggregate umkc-ig>... 12:32:39 INFO : ... Allocation at <Aggregate umkc-ig> complete. 12:32:39 INFO : Stitcher doing createsliver at <Aggregate gpo-eg>... 12:32:50 INFO : ... Allocation at <Aggregate gpo-eg> complete. 12:32:50 INFO : Stitcher doing createsliver at <Aggregate al2s>... 12:32:57 INFO : ... Allocation at <Aggregate al2s> complete. 12:32:57 INFO : All aggregates are complete. 12:32:57 INFO : Your resources expire at 2015-04-23T16:22:22 (UTC). 12:32:57 INFO : Saved combined reservation RSpec at 3 AMs to file '/home/lnevers/gcf-test/stitch-test/UMKC/IG-ST-4-manifest-rspec-multiam-combined.xml' Success: Reserved resources in slice IG-ST-4 at 3 Aggregates (including 1 intermediate aggregate(s) not in the original request), creating 1 stitched link(s). }}} Determined login information at each UMKC and GPO aggregate: {{{ $ readyToLogin.py IG-ST-4 --useSliceAggregates .... }}} === Measurements === '''Iperf ExoGENI GPO VM to InstaGENI UMKC VM (TCP) - TCP window size: 85.0 KByte (default)''' ''Collected: 2015-04-XX'' __One Client_ {{{ }}} __Five Clients__ {{{ }}} __Ten Clients__ {{{ }}} '''Iperf ExoGENI GPO VM to InstaGENI UMKC VM (UDP) - UDP buffer size: 208 KByte (default) ''' {{{ }}} '''Ping from ExoGENI GPO VM to the InstaGENI UMKC VM ''' {{{ }}} '''Iperf InstaGENI UMKC VM to ExoGENI GPO VM (TCP) - TCP window size: 23.5 KByte (default)''' ''Collected: 2015-04-XX'' __One Client_ {{{ }}} __Five Clients__ {{{ }}} __Ten Clients__ {{{ }}} '''Iperf InstaGENI UMKC VM to ExoGENI GPO VM (UDP) - UDP buffer size: 224 KByte (default) ''' {{{ }}} '''Ping from InstaGENI UMKC VM to ExoGENI GPO VM ''' {{{ }}} == IG-ST-5 Site Information == Various pages include stitching information for a site. Each of the following were verified for this site: 1. Verified that stitching VLANs and Device URN information exists in the [http://groups.geni.net/geni/wiki/GeniAggregate/UMKCInstaGENI#GENINetworkStitching UMKC Aggregate] page. 2. Verified that Delegated GENI Stitching VLANs for site are documented at the [https://wiki.maxgigapop.net/twiki/bin/view/GENI/StaticNetworksView Delegated GENI Stitching VLANs]. 3. Stitching Computation Service logs were reviewed while testing stitching to this site, no issues found. 4. Added site to the list of [wiki:GeniNetworkStitchingSites GENI Network Stitching Sites]. == IG-ST-6 New Site !OpenFlow topology == Create a slice and then create the stitched slivers using !OpenFlow with the RSPec [http://groups.geni.net/geni/browser/trunk/stitch-examples/UMKC/IG-ST-6.rspec IG-ST-6.rspec]: {{{ omni.py createslice IG-ST-6 stitcher.py createsliver IG-ST-6 IG-ST-6.rspec -o }}} Determined login information at each UMKC and GPO aggregate: {{{ $ readyToLogin.py IG-ST-6 --useSliceAggregates .... }}} === Measurements === '''Iperf InstaGENI GPO VM to InstaGENI UMKC VM (TCP) - TCP window size: 23.5 KByte (default)''' ''Collected: 2015-04-xx'' __One Client_ {{{ }}} __Five Clients__ {{{ }}} __Ten Clients__ {{{ }}} '''Iperf InstaGENI GPO VM to InstaGENI UMKC VM (UDP) - UDP buffer size: 224 KByte (default) ''' {{{ }}} '''Ping from InstaGENI GPO VM to InstaGENI UMKC VM ''' {{{ }}} '''Iperf InstaGENI UMKC VM to InstaGENI GPO VM (TCP) - TCP window size: 23.5 KByte (default)''' ''Collected: 2015-04-xx'' __One Client_ {{{ }}} __Five Clients__ {{{ }}} __Ten Clients__ {{{ }}} '''Iperf InstaGENI UMKC VM to InstaGENI GPO VM (UDP) - UDP buffer size: 224 KByte (default) ''' {{{ }}} '''Ping from InstaGENI UMKC VM to InstaGENI GPO VM ''' {{{ }}} ------ {{{ #!html Email <a href="mailto:help@geni.net"> help@geni.net </a> for GENI support or email <a href="mailto:luisa.nevers@bbn.com">me</a> with feedback on this page! }}}