wiki:GeniNetworkStitchingConfirmationTestStatus/Kansas

Version 2 (modified by lnevers@bbn.com, 4 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:

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
stitcher.py createsliver IG-ST-1 IG-ST-1-ion.rspec -o

Determined login information at each KANSAS and GPO aggregate:

$ readyToLogin.py IG-ST-1 -a kansas-ig
  ....

$ readyToLogin.py IG-ST-1 -a gpo-ig
  ....

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 [http://groups.geni.net/geni/browser/trunk/stitch-examples/KANSAS/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.

{{{
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:
 
 1. Verified that stitching VLANs and Device URN information exists in the [http://groups.geni.net/geni/wiki/GeniAggregate/KANSASInstaGENI#GENINetworkStitching KANSAS 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/KANSAS/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 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 '''
{{{

}}}
---
{{{
#!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!
}}}