wiki:GeniNetworkStitchingConfirmationTestStatus/GATech

Version 6 (modified by lnevers@bbn.com, 5 years ago) (diff)

--

Georgia Tech 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 GATech site advertises the following stitching details:

<stitching xmlns="http://hpn.east.isi.edu/rspec/ext/stitch/0.1/" lastUpdateTime="2015-03-11T15:24:55Z" >
<aggregate id="urn:publicid:IDN+instageni.rnoc.gatech.edu+authority+cm" url="https://www.instageni.rnoc.gatech.edu:12369/protogeni/xmlrpc/am">
<aggregatetype>protogeni</aggregatetype>
<stitchingmode>chainANDTree</stitchingmode>
<scheduledservices>false</scheduledservices>
<negotiatedservices>false</negotiatedservices>
<lifetime id="life">
    <start type="time">2015-03-11T15:24:55Z</start>
    <end type="time">2015-03-11T15:24:55Z</end>
</lifetime>
<node id="urn:publicid:IDN+instageni.rnoc.gatech.edu+node+procurve2">
  <port id="urn:publicid:IDN+instageni.rnoc.gatech.edu+stitchport+procurve2:1.24.al2s">
    <capacity>1000000</capacity>
    <maximumReservableCapacity>1000000</maximumReservableCapacity>
    <minimumReservableCapacity>1000</minimumReservableCapacity>
    <granularity>1</granularity>
    <link id="urn:publicid:IDN+instageni.rnoc.gatech.edu+interface+procurve2:1.24.al2s">
      <remoteLinkId>urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.atla.net.internet2.edu:eth5/2:gatech-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>3520-3534</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-al2s.rspec -o
15:23:51 INFO    : Configured logging from file /home/lnevers/gcf-2.9-pre1/src/gcf/stitcher_logging.conf
15:23:52 INFO    : Reading slice IG-ST-1 credential...
15:23:52 INFO    : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-1 expires on 2015-03-18 15:16:57 UTC
15:23:52 INFO    : Calling SCS...
15:23:55 INFO    : Multi-AM reservation will include resources from these aggregates:
15:23:55 INFO    : 	<Aggregate gpo-ig>
15:23:55 INFO    : 	<Aggregate al2s>
15:23:55 INFO    : 	<Aggregate gatech-ig>
15:23:55 INFO    : 	<Aggregate ion>
15:23:55 INFO    : Stitcher doing createsliver at <Aggregate gpo-ig>...
15:24:10 INFO    : ... Allocation at <Aggregate gpo-ig> complete.
15:24:10 INFO    : Stitcher doing createsliver at <Aggregate gatech-ig>...
15:24:26 INFO    : ... Allocation at <Aggregate gatech-ig> complete.
15:24:26 INFO    : Stitcher doing createsliver at <Aggregate al2s>...
15:24:34 INFO    : ... Allocation at <Aggregate al2s> complete.
15:24:34 INFO    : Stitcher doing createsliver at <Aggregate ion>...
15:25:19 INFO    : DCN AM <Aggregate ion>: must wait for status ready....
15:25:19 INFO    : Pausing 30 seconds to let circuit become ready...
15:25:58 INFO    : DCN circuit 156481 is ready at <Aggregate ion>
15:26:07 INFO    : ... Allocation at <Aggregate ion> complete.
15:26:07 INFO    : All aggregates are complete.
15:26:07 INFO    : Your resources expire at 2015-03-17T19:13:55 (UTC). 
15:26:07 INFO    : Saved combined reservation RSpec at 4 AMs to file '/home/lnevers/gcf-test/stitch-test/GATech/IG-ST-1-manifest-rspec-multiam-combined.xml'
Success: Reserved resources in slice IG-ST-1 at 4 Aggregates (including 2 intermediate aggregate(s) not in the original request), creating 1 stitched link(s).

Determined login information at each GATech 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 38202  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc4.instageni.gpolab.bbn.com
....
ig-ga's geni_status is: ready 
User lnevers logs in to ig-ga using:
	ssh -p 33082  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.rnoc.gatech.edu

Measurements

Iperf InstaGENI GPO VM to InstaGENI GATech VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2015-03-13

One Client_

Five Clients

Ten Clients

Iperf InstaGENI GPO VM to InstaGENI GATech VM (UDP) - UDP buffer size: 224 KByte (default)

Ping from InstaGENI GPO VM to the InstaGENI GATech VM

Iperf InstaGENI GATech VM to GPO InstaGENI VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2015-03-13

One Client_

Five Clients

Ten Clients

Iperf InstaGENI GATech VM to GPO InstaGENI VM (UDP) - UDP buffer size: 224 KByte (default)

Ping from InstaGENI GATech 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 GATech 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 GATech host:

$ readyToLogin.py IG-ST-3 -a gatech-ig
  ....

Login to the GATech host and ping each remote:

#ping GPO IG 
ping 192.168.2.1 -c 60 -q
# UKYPKS2 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 GATech and GPO aggregate:

$ readyToLogin.py IG-ST-4 --useSliceAggregates
  ....

Measurements

Iperf ExoGENI GPO VM to InstaGENI GATech VM (TCP) - TCP window size: 85.0 KByte (default)

Collected: 2015-02-XX

One Client_

Five Clients

Ten Clients

Iperf ExoGENI GPO VM to InstaGENI GATech VM (UDP) - UDP buffer size: 208 KByte (default)

Ping from ExoGENI GPO VM to the InstaGENI GATech VM

Iperf InstaGENI GATech VM to ExoGENI GPO VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2015-02-XX

One Client_

Five Clients

Ten Clients

Iperf InstaGENI GATech VM to ExoGENI GPO VM (UDP) - UDP buffer size: 224 KByte (default)

Ping from InstaGENI GATech 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 GATech Aggregate page.

  1. Verified that Delegated GENI Stitching VLANs for site are documented at the Delegated GENI Stitching VLANs.
  1. Stitching Computation Service logs were reviewed while testing stitching to this site, no issues found.
  1. 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 GATech and GPO aggregate:

$ readyToLogin.py IG-ST-6 --useSliceAggregates
  ....

Measurements

Iperf InstaGENI GPO VM to InstaGENI GATech VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2015-02-xx

One Client_

Five Clients

Ten Clients

Iperf InstaGENI GPO VM to InstaGENI GATech VM (UDP) - UDP buffer size: 224 KByte (default)

Ping from InstaGENI GPO VM to InstaGENI GATech VM

Iperf InstaGENI GATech VM to InstaGENI GPO VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2015-02-xx

One Client_

Five Clients

Ten Clients

Iperf InstaGENI GATech VM to InstaGENI GPO VM (UDP) - UDP buffer size: 224 KByte (default)

Ping from InstaGENI GATech VM to InstaGENI GPO VM


Email help@geni.net for GENI support or email me with feedback on this page!