Version 5 (modified by 10 years ago) (diff) | ,
---|
University of Kentucky PKS2 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 UKYPKS2 site advertises the following stitching details:
<stitching xmlns="http://hpn.east.isi.edu/rspec/ext/stitch/0.1/" lastUpdateTime="2014-09-08T18:15:11Z" > <aggregate id="urn:publicid:IDN+pks2.sdn.uky.edu+authority+cm" url="https://www.pks2.sdn.uky.edu:12369/protogeni/xmlrpc/am"> <aggregatetype>protogeni</aggregatetype> <stitchingmode>chainANDTree</stitchingmode> <scheduledservices>false</scheduledservices> <negotiatedservices>false</negotiatedservices> <lifetime id="life"> <start type="time">2014-09-08T18:15:11Z</start> <end type="time">2014-09-08T18:15:11Z</end> </lifetime> <node id="urn:publicid:IDN+pks2.sdn.uky.edu+node+procurve2"> <port id="urn:publicid:IDN+pks2.sdn.uky.edu+stitchport+procurve2:1.18.ion"> <capacity>1000000</capacity> <maximumReservableCapacity>1000000</maximumReservableCapacity> <minimumReservableCapacity>1000</minimumReservableCapacity> <granularity>1</granularity> <link id="urn:publicid:IDN+pks2.sdn.uky.edu+interface+procurve2:1.18.ion"> <remoteLinkId>urn:publicid:IDN+ion.internet2.edu+interface+rtr.atla:xe-0/1/3:ukypks2-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>1830-1849</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:
$ omni.py createslice IG-ST-1 14:16:05 INFO : Loading agg_nick_cache file '/home/lnevers/.gcf/agg_nick_cache' 14:16:05 INFO : Loading config file /home/lnevers/.gcf/omni_config 14:16:05 INFO : Setting option useSliceMembers based on omni_config setting 14:16:05 INFO : Using control framework portal 14:16:05 INFO : Member Authority is https://ch.geni.net/MA (from config) 14:16:05 INFO : Slice Authority is https://ch.geni.net/SA (from config) 14:16:06 INFO : Created slice with Name IG-ST-1, URN urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-1, Expiration 2014-09-15 18:16:05+00:00 14:16:06 INFO : ------------------------------------------------------ 14:16:06 INFO : Completed createslice: Options as run: framework: portal project: ln-test useSliceMembers: True Args: createslice IG-ST-1 Result Summary: Created slice with Name IG-ST-1, URN urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-1, Expiration 2014-09-15 18:16:05+00:00 14:16:06 INFO : ====================================================== $ stitcher createsliver IG-ST-1 IG-ST-1-ion.rspec 10:11:28 INFO : Configured logging from file /home/lnevers/gcf-2.7-0908/src/gcf/stitcher_logging.conf 10:11:28 INFO : Reading slice IG-ST-1 credential... 10:11:28 INFO : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-1 expires on 2014-09-15 18:16:05 UTC 10:11:28 INFO : Using SCS at http://nutshell.maxgigapop.net:8081/geni/xmlrpc 10:11:28 INFO : Calling SCS... 10:11:30 INFO : Multi-AM reservation will include resources from these aggregates: 10:11:30 INFO : <Aggregate ukypks2-ig> 10:11:30 INFO : <Aggregate gpo-ig> 10:11:30 INFO : <Aggregate ion> 10:11:30 INFO : Stitcher doing createsliver at <Aggregate ukypks2-ig>... 10:11:47 INFO : ... Allocation at <Aggregate ukypks2-ig> complete. 10:11:47 INFO : Stitcher doing createsliver at <Aggregate gpo-ig>... 10:12:02 INFO : ... Allocation at <Aggregate gpo-ig> complete. 10:12:02 INFO : Stitcher doing createsliver at <Aggregate ion>... 10:12:47 INFO : DCN AM <Aggregate ion>: must wait for status ready.... 10:12:47 INFO : Pausing 30 seconds to let circuit become ready... 10:13:25 INFO : Pausing 30 seconds to let circuit become ready... 10:14:02 INFO : Pausing 30 seconds to let circuit become ready... 10:14:40 INFO : Pausing 30 seconds to let circuit become ready... 10:15:17 INFO : Pausing 30 seconds to let circuit become ready... 10:15:54 INFO : DCN circuit 116731 is ready at <Aggregate ion> 10:16:02 INFO : Getting credential from file /tmp/slice-ch-geni-net-ln-test-IG-ST-1-for-lnevers-cred.xml 10:16:02 INFO : ... Allocation at <Aggregate ion> complete. 10:16:02 INFO : All aggregates are complete. 10:16:02 INFO : Your resources expire at 2 different times at different AMs. The first expiration is 2014-09-10 14:12:07 UTC at <Aggregate ion>. Second expiration is 2014-09-15T18:16:05 UTC. 10:16:02 INFO : Saved combined reservation RSpec at 3 AMs to file '/home/lnevers/gcf-test/stitch-test/UKYPKS2/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 UKYPKS2 and GPO aggregate:
$ readyToLogin.py IG-ST-1 -a ukypks2-ig .... ig-pks2's geni_status is: ready User lnevers logs in to ig-pks2 using: ssh -p 30266 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc3.pks2.sdn.uky.edu $ readyToLogin.py IG-ST-1 -a gpo-ig .... ig-gpo's geni_status is: ready User lnevers logs in to ig-gpo using: ssh -p 34106 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc4.instageni.gpolab.bbn.com
Measurements
Iperf InstaGENI GPO VM to InstaGENI UKYPKS2 VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2014-09-09
One Client_
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.1 sec 142 MBytes 19.8 Mbits/sec
Five Clients
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.1 sec 27.9 MBytes 3.89 Mbits/sec [ 4] 0.0-60.5 sec 34.4 MBytes 4.77 Mbits/sec [ 6] 0.0-60.5 sec 32.1 MBytes 4.45 Mbits/sec [ 5] 0.0-60.9 sec 24.9 MBytes 3.43 Mbits/sec [ 7] 0.0-61.0 sec 25.4 MBytes 3.49 Mbits/sec [SUM] 0.0-61.0 sec 145 MBytes 19.9 Mbits/sec
Ten Clients
[ ID] Interval Transfer Bandwidth [ 7] 0.0-60.0 sec 12.0 MBytes 1.68 Mbits/sec [ 11] 0.0-60.1 sec 10.4 MBytes 1.45 Mbits/sec [ 12] 0.0-60.4 sec 12.8 MBytes 1.77 Mbits/sec [ 3] 0.0-60.7 sec 18.8 MBytes 2.59 Mbits/sec [ 6] 0.0-60.8 sec 17.8 MBytes 2.45 Mbits/sec [ 8] 0.0-61.0 sec 12.8 MBytes 1.75 Mbits/sec [ 5] 0.0-61.0 sec 22.2 MBytes 3.06 Mbits/sec [ 9] 0.0-61.2 sec 8.75 MBytes 1.20 Mbits/sec [ 10] 0.0-62.2 sec 16.6 MBytes 2.24 Mbits/sec [ 4] 0.0-62.2 sec 15.4 MBytes 2.07 Mbits/sec [SUM] 0.0-62.2 sec 147 MBytes 19.9 Mbits/sec
Iperf InstaGENI GPO VM to InstaGENI UKYPKS2 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 512810 datagrams [ 3] Server Report: [ 3] 0.0-60.2 sec 139 MBytes 19.4 Mbits/sec 8.980 ms 413507/512808 (81%) [ 3] 0.0-60.2 sec 1 datagrams received out-of-order
Ping from InstaGENI GPO VM to the InstaGENI UKYPKS2 VM
60 packets transmitted, 60 received, 0% packet loss, time 59100ms rtt min/avg/max/mdev = 36.426/36.607/39.727/0.448 ms
Iperf InstaGENI UKYPKS2 VM to GPO InstaGENI VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2014-09-09
One Client_
[ ID] Interval Transfer Bandwidth [ 3] 0.0-60.1 sec 142 MBytes 19.8 Mbits/sec
Five Clients
[ ID] Interval Transfer Bandwidth [ 6] 0.0-60.0 sec 26.6 MBytes 3.72 Mbits/sec [ 5] 0.0-60.1 sec 25.5 MBytes 3.56 Mbits/sec [ 4] 0.0-60.2 sec 36.1 MBytes 5.04 Mbits/sec [ 3] 0.0-60.4 sec 26.5 MBytes 3.68 Mbits/sec [ 7] 0.0-61.1 sec 29.6 MBytes 4.07 Mbits/sec [SUM] 0.0-61.1 sec 144 MBytes 19.8 Mbits/sec
Ten Clients
[ ID] Interval Transfer Bandwidth [ 12] 0.0-60.0 sec 11.1 MBytes 1.55 Mbits/sec [ 10] 0.0-60.1 sec 21.4 MBytes 2.98 Mbits/sec [ 9] 0.0-60.2 sec 12.8 MBytes 1.78 Mbits/sec [ 5] 0.0-60.4 sec 15.5 MBytes 2.15 Mbits/sec [ 6] 0.0-60.6 sec 20.1 MBytes 2.79 Mbits/sec [ 8] 0.0-60.7 sec 12.4 MBytes 1.71 Mbits/sec [ 7] 0.0-60.8 sec 10.0 MBytes 1.38 Mbits/sec [ 11] 0.0-61.3 sec 14.1 MBytes 1.93 Mbits/sec [ 4] 0.0-61.3 sec 13.4 MBytes 1.83 Mbits/sec [ 3] 0.0-62.1 sec 16.2 MBytes 2.19 Mbits/sec [SUM] 0.0-62.1 sec 147 MBytes 19.8 Mbits/sec
Iperf InstaGENI UKYPKS2 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 512790 datagrams [ 3] Server Report: [ 3] 0.0-60.3 sec 139 MBytes 19.4 Mbits/sec 14.567 ms 413570/512787 (81%) [ 3] 0.0-60.3 sec 1 datagrams received out-of-order
Ping from InstaGENI UKYPKS2 VM to GPO InstaGENI VM
60 packets transmitted, 60 received, 0% packet loss, time 59099ms rtt min/avg/max/mdev = 36.286/36.534/36.879/0.118 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:
$ omni.py createslice IG-ST-2 11:20:03 INFO : Loading agg_nick_cache file '/home/lnevers/.gcf/agg_nick_cache' 11:20:03 INFO : Loading config file /home/lnevers/.gcf/omni_config 11:20:03 INFO : Setting option useSliceMembers based on omni_config setting 11:20:03 INFO : Using control framework portal 11:20:03 INFO : Member Authority is https://ch.geni.net/MA (from config) 11:20:03 INFO : Slice Authority is https://ch.geni.net/SA (from config) 11:20:04 INFO : Created slice with Name IG-ST-2, URN urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-2, Expiration 2014-09-16 15:20:04+00:00 11:20:04 INFO : ------------------------------------------------------ 11:20:04 INFO : Completed createslice: Options as run: framework: portal project: ln-test useSliceMembers: True Args: createslice IG-ST-2 Result Summary: Created slice with Name IG-ST-2, URN urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-2, Expiration 2014-09-16 15:20:04+00:00 11:20:04 INFO : ====================================================== $ stitcher.py createsliver IG-ST-2 IG-ST-2.rspec -o 11:20:30 INFO : Configured logging from file /home/lnevers/gcf-2.7-0908/src/gcf/stitcher_logging.conf 11:20:31 INFO : Reading slice IG-ST-2 credential... 11:20:31 INFO : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-2 expires on 2014-09-16 15:20:04 UTC 11:20:31 INFO : Using SCS at http://nutshell.maxgigapop.net:8081/geni/xmlrpc 11:20:31 INFO : Calling SCS... 11:20:34 INFO : Multi-AM reservation will include resources from these aggregates: 11:20:34 INFO : <Aggregate ukypks2-ig> 11:20:34 INFO : <Aggregate gpo-ig> 11:20:34 INFO : <Aggregate ion> 11:20:34 INFO : Stitcher doing createsliver at <Aggregate ukypks2-ig>... 11:20:53 INFO : ... Allocation at <Aggregate ukypks2-ig> complete. 11:20:53 INFO : Stitcher doing createsliver at <Aggregate gpo-ig>... 11:21:11 INFO : ... Allocation at <Aggregate gpo-ig> complete. 11:21:11 INFO : Stitcher doing createsliver at <Aggregate ion>... 11:21:56 INFO : DCN AM <Aggregate ion>: must wait for status ready.... 11:21:56 INFO : Pausing 30 seconds to let circuit become ready... 11:22:34 INFO : Pausing 30 seconds to let circuit become ready... 11:23:12 INFO : DCN circuit 116751 is ready at <Aggregate ion> 11:23:12 INFO : DCN circuit 116761 is ready at <Aggregate ion> 11:23:19 INFO : Getting credential from file /tmp/slice-ch-geni-net-ln-test-IG-ST-2-for-lnevers-cred.xml 11:23:19 INFO : ... Allocation at <Aggregate ion> complete. 11:23:19 INFO : All aggregates are complete. 11:23:19 INFO : Your resources expire at 2 different times at different AMs. The first expiration is 2014-09-10 15:21:16 UTC at <Aggregate ion>. Se 11:23:19 INFO : Saved combined reservation RSpec at 3 AMs to file '/home/lnevers/gcf-test/stitch-test/UKYPKS2/IG-ST-2-manifest-rspec-multiam-combin Success: Reserved resources in slice IG-ST-2 at 3 Aggregates (including 1 intermediate aggregate(s) not in the original request), creating 2 stitched links
Determined login information at each UKYPKS2 and GPO aggregate:
$ readyToLogin.py IG-ST-2 -a ukypks2-ig .... ig-pks2's geni_status is: ready User lnevers logs in to ig-pks2 using: ssh -p 30266 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.pks2.sdn.uky.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 34106 -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:
[lnevers@ig-gpo ~]$ 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 59063ms rtt min/avg/max/mdev = 35.927/36.651/74.379/4.913 ms [lnevers@ig-gpo ~]$ 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 59068ms rtt min/avg/max/mdev = 35.876/36.638/74.746/4.963 ms