Version 5 (modified by 9 years ago) (diff) | ,
---|
University of Kansas 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 KANSAS site advertises the following stitching details:
<stitching xmlns="http://hpn.east.isi.edu/rspec/ext/stitch/0.1/" lastUpdateTime="2014-11-18T18:30:48Z" > <aggregate id="urn:publicid:IDN+instageni.ku.gpeni.net+authority+cm" url="https://www.instageni.ku.gpeni.net:12369/protoge ni/xmlrpc/am"> <aggregatetype>protogeni</aggregatetype> <stitchingmode>chainANDTree</stitchingmode> <scheduledservices>false</scheduledservices> <negotiatedservices>false</negotiatedservices> <lifetime id="life"> <start type="time">2014-11-18T18:30:48Z</start> <end type="time">2014-11-18T18:30:48Z</end> </lifetime> <node id="urn:publicid:IDN+instageni.ku.gpeni.net+node+procurve2"> <port id="urn:publicid:IDN+instageni.ku.gpeni.net+stitchport+procurve2:1.24.al2s"> <capacity>1000000</capacity> <maximumReservableCapacity>1000000</maximumReservableCapacity> <minimumReservableCapacity>1000</minimumReservableCapacity> <granularity>1</granularity> <link id="urn:publicid:IDN+instageni.ku.gpeni.net+interface+procurve2:1.24.al2s"> <remoteLinkId>urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:kansas-ig</remoteLi nkId> <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>1170-1189</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-1a IG-ST-1-al2s.rspec -o 14:15:31 INFO : Configured logging from file /home/lnevers/gcf-2.7/src/gcf/stitcher_logging.conf 14:15:32 INFO : Reading slice IG-ST-1a credential... 14:15:32 INFO : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-1a expires on 2014-11-25 19:13:52 UTC 14:15:32 INFO : Using SCS at http://nutshell.maxgigapop.net:8081/geni/xmlrpc 14:15:32 INFO : Calling SCS... 14:15:33 INFO : Multi-AM reservation will include resources from these aggregates: 14:15:33 INFO : <Aggregate gpo-ig> 14:15:33 INFO : <Aggregate kansas-ig> 14:15:33 INFO : <Aggregate oess> 14:15:33 INFO : <Aggregate ion> 14:15:33 INFO : Stitcher doing createsliver at <Aggregate gpo-ig>... 14:15:55 INFO : ... Allocation at <Aggregate gpo-ig> complete. 14:15:55 INFO : Stitcher doing createsliver at <Aggregate kansas-ig>... 14:16:11 INFO : ... Allocation at <Aggregate kansas-ig> complete. 14:16:11 INFO : Stitcher doing createsliver at <Aggregate oess>... 14:16:15 INFO : ... Allocation at <Aggregate oess> complete. 14:16:15 INFO : Stitcher doing createsliver at <Aggregate ion>... 14:17:02 INFO : DCN AM <Aggregate ion>: must wait for status ready.... 14:17:02 INFO : Pausing 30 seconds to let circuit become ready... 14:17:40 INFO : DCN circuit 139211 is ready at <Aggregate ion> 14:17:47 INFO : ... Allocation at <Aggregate ion> complete. 14:17:47 INFO : All aggregates are complete. 14:17:47 INFO : Your resources expire at 2014-11-24T19:05:33 (UTC). 14:17:47 INFO : Saved combined reservation RSpec at 4 AMs to file '/home/lnevers/gcf-test/stitch-test/Kansas/IG-ST-1a-manifest-rspec-multiam-combined.xml' Success: Reserved resources in slice IG-ST-1a at 4 Aggregates (including 2 intermediate aggregate(s) not in the original request), creating 1 stitched link(s).
Determined login information at each KANSAS and GPO aggregate:
$ readyToLogin.py IG-ST-1a -a kansas-ig .... ig-chic's geni_status is: ready User lnevers logs in to ig-chic using: ssh -p 30010 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.ku.gpeni.net $ readyToLogin.py IG-ST-1a -a gpo-ig .... ig-gpo's geni_status is: changing User lnevers logs in to ig-gpo using: ssh -p 34362 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc5.instageni.gpolab.bbn.com
Measurements
Iperf InstaGENI GPO VM to InstaGENI KANSAS VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2014-08-XX
One Client_
Five Clients
Ten Clients
Iperf InstaGENI GPO VM to InstaGENI KANSAS VM (UDP) - UDP buffer size: 224 KByte (default)
Ping from InstaGENI GPO VM to the InstaGENI KANSAS VM
Iperf InstaGENI KANSAS VM to GPO InstaGENI VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2014-08-XX
One Client_
Five Clients
Ten Clients
Iperf InstaGENI KANSAS VM to GPO InstaGENI VM (UDP) - UDP buffer size: 224 KByte (default)
Ping from InstaGENI KANSAS VM to GPO InstaGENI VM
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 stitcher.py createsliver IG-ST-2 IG-ST-2.rspec -o
Determined login information at each KANSAS and GPO aggregate:
$ readyToLogin.py IG-ST-2 -a kansas-ig .... $ readyToLogin.py IG-ST-2 -a gpo-ig ....
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 192.168.4.2 -c 60 -q
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:
omni.py createslice IG-ST-3 stitcher.py createsliver IG-ST-3 IG-ST-3.rspec -o
Determined login information the KANSAS host:
$ readyToLogin.py IG-ST-3 -a kansas-ig ....
Login to the KANSAS host and ping each remote:
#ping GPO IG ping 192.168.2.1 -c 60 -q # Utah IG ping 192.168.4.1 -c 60 -q
IG-ST-4 New Site to GPO EG interoperability
Create a slice and then create the stitched slivers with the 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.
omni.py createslice IG-ST-4 stitcher.py createsliver IG-ST-4 IG-ST-4.rspec -o
Determined login information at each KANSAS and GPO aggregate:
$ readyToLogin.py IG-ST-4 -a kansas-ig .... $ readyToLogin.py IG-ST-4 -a eg-sm ....
Measurements
Iperf ExoGENI GPO VM to InstaGENI KANSAS VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2014-08-XX
One Client_
Five Clients
Ten Clients
Iperf ExoGENI GPO VM to InstaGENI KANSAS VM (UDP) - UDP buffer size: 224 KByte (default)
Ping from ExoGENI GPO VM to the InstaGENI KANSAS VM
Iperf InstaGENI KANSAS VM to ExoGENI GPO VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2014-08-XX
One Client_
Five Clients
Ten Clients
Iperf InstaGENI KANSAS VM to ExoGENI GPO VM (UDP) - UDP buffer size: 224 KByte (default)
Ping from InstaGENI KANSAS 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:
- Verified that stitching VLANs and Device URN information exists in the KANSAS Aggregate page.
- Verified that Delegated GENI Stitching VLANs for site are documented at the Delegated GENI Stitching VLANs.
- Stitching Computation Service logs were reviewed while testing stitching to this site, no issues found.
- Added site to the list of 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 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 KANSAS and GPO aggregate:
$ readyToLogin.py IG-ST-6 -a kansas-ig .... $ readyToLogin.py IG-ST-6 -a gpo-ig ....
Measurements
Iperf InstaGENI GPO VM to InstaGENI KANSAS VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2014-xx-xx
One Client_
Five Clients
Ten Clients
Iperf InstaGENI GPO VM to InstaGENI KANSAS VM (UDP) - UDP buffer size: 224 KByte (default)
Ping from InstaGENI GPO VM to InstaGENI KANSAS VM
Iperf InstaGENI KANSAS VM to InstaGENI GPO VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2014-xx-xx
One Client_
Five Clients
Ten Clients
Iperf InstaGENI KANSAS VM to InstaGENI GPO VM (UDP) - UDP buffer size: 224 KByte (default)
Ping from InstaGENI KANSAS VM to InstaGENI GPO VM
Email help@geni.net for GENI support or email me with feedback on this page!