| Version 2 (modified by , 10 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:
omni.py createslice IG-ST-1 stitcher.py createsliver IG-ST-1 IG-ST-1-al2s.rspec -o
Determined login information at each UMKC and GPO aggregate:
$ readyToLogin.py IG-ST-1 --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 the InstaGENI UMKC VM
Iperf InstaGENI UMKC VM to GPO InstaGENI VM (TCP) - TCP window size: 23.5 KByte (default)
Collected: 2015-04-XX
One Client_
Five Clients
Ten Clients
Iperf InstaGENI UMKC VM to GPO InstaGENI VM (UDP) - UDP buffer size: 224 KByte (default)
Ping from InstaGENI UMKC 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 UMKC and GPO aggregate:
$ readyToLogin.py IG-ST-2 --useSliceAggregates ....
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-2a -a gpo-ig -m "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 UMKC host:
$ readyToLogin.py IG-ST-3 -a umkc-ig ....
Login to the UMKC host and ping each remote:
#ping GPO IG ping 192.168.2.1 -c 60 -q # UMKCPKS2 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 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:
- Verified that stitching VLANs and Device URN information exists in the UMKC 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 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
Email help@geni.net for GENI support or email me with feedback on this page!
