wiki:GeniNetworkStitchingConfirmationTestStatus/UWashington

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

--

University of Washington 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 Washington site advertises the following stitching details:

<stitching xmlns="http://hpn.east.isi.edu/rspec/ext/stitch/0.1/" lastUpdateTime="2015-02-12T15:36:03Z" >
<aggregate id="urn:publicid:IDN+instageni.washington.edu+authority+cm" url="https://www.instageni.washington.edu:12369/protogeni/xmlrpc/am">
<aggregatetype>protogeni</aggregatetype>
<stitchingmode>chainANDTree</stitchingmode>
<scheduledservices>false</scheduledservices>
<negotiatedservices>false</negotiatedservices>
<lifetime id="life">
    <start type="time">2015-02-12T15:36:03Z</start>
    <end type="time">2015-02-12T15:36:03Z</end>
</lifetime>
<node id="urn:publicid:IDN+instageni.washington.edu+node+procurve2">
  <port id="urn:publicid:IDN+instageni.washington.edu+stitchport+procurve2:2.1.al2s">
    <capacity>1000000</capacity>
    <maximumReservableCapacity>1000000</maximumReservableCapacity>
    <minimumReservableCapacity>1000</minimumReservableCapacity>
    <granularity>1</granularity>
    <link id="urn:publicid:IDN+instageni.washington.edu+interface+procurve2:2.1.al2s">
      <remoteLinkId>urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.seat.net.internet2.edu:et-3/0/0.0:uwashington-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>2301-2315</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
14:38:05 INFO    : Configured logging from file /home/lnevers/gcf-2.8/src/gcf/stitcher_logging.conf
14:38:06 INFO    : Reading slice IG-ST-1 credential...
14:38:06 INFO    : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-1 expires on 2015-02-18 16:48:13 UTC
14:38:06 INFO    : Using SCS at https://nutshell.maxgigapop.net:8443/geni/xmlrpc
14:38:06 INFO    : Calling SCS...
14:38:07 INFO    : Multi-AM reservation will include resources from these aggregates:
14:38:07 INFO    : 	<Aggregate uwash-ig>
14:38:07 INFO    : 	<Aggregate gpo-ig>
14:38:07 INFO    : 	<Aggregate al2s>
14:38:07 INFO    : 	<Aggregate ion>
14:38:08 INFO    : Stitcher doing createsliver at <Aggregate uwash-ig>...
14:38:24 INFO    : ... Allocation at <Aggregate uwash-ig> complete.
14:38:24 INFO    : Stitcher doing createsliver at <Aggregate gpo-ig>...
14:38:38 INFO    : ... Allocation at <Aggregate gpo-ig> complete.
14:38:38 INFO    : Stitcher doing createsliver at <Aggregate al2s>...
14:38:43 INFO    : ... Allocation at <Aggregate al2s> complete.
14:38:43 INFO    : Stitcher doing createsliver at <Aggregate ion>...
14:39:28 INFO    : DCN AM <Aggregate ion>: must wait for status ready....
14:39:28 INFO    : Pausing 30 seconds to let circuit become ready...
14:40:05 INFO    : Pausing 30 seconds to let circuit become ready...
14:40:43 INFO    : DCN circuit 153651 is ready at <Aggregate ion>
14:40:50 INFO    : ... Allocation at <Aggregate ion> complete.
14:40:50 INFO    : All aggregates are complete.
14:40:50 INFO    : Your resources expire at 2015-02-17T19:28:07 (UTC). 
14:40:50 INFO    : Saved combined reservation RSpec at 4 AMs to file '/home/lnevers/gcf-test/stitch-test/Washington/IG-ST-1-manifest-rspec-multia
Success: Reserved resources in slice IG-ST-1 at 4 Aggregates (including 2 intermediate aggregate(s) not in the original request)

Determined login information at each Washington and GPO aggregate:

$ readyToLogin.py IG-ST-1 --useSliceAggregates
  ....
ig-wash's geni_status is: ready 
User lnevers logs in to ig-wash using:
	ssh -p 30266  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.washington.edu
 ....
ig-gpo's geni_status is: changing 
User lnevers logs in to ig-gpo using:
	ssh -p 32570  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc4.instageni.gpolab.bbn.com

Measurements

Iperf InstaGENI GPO VM to InstaGENI Washington 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 Washington VM (UDP) - UDP buffer size: 224 KByte (default)

Ping from InstaGENI GPO VM to the InstaGENI Washington VM

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

Collected: 2015-02-XX

One Client_

Five Clients

Ten Clients

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

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

$ stitcher.py createsliver IG-ST-2 IG-ST-2.rspec -o
14:06:53 INFO    : Configured logging from file /home/lnevers/gcf-2.8/src/gcf/stitcher_logging.conf
14:06:53 INFO    : Reading slice IG-ST-2 credential...
14:06:54 INFO    : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-2 expires on 2015-02-18 16:50:26 UTC
14:06:54 INFO    : Using SCS at https://nutshell.maxgigapop.net:8443/geni/xmlrpc
14:06:54 INFO    : Calling SCS...
14:06:57 INFO    : Multi-AM reservation will include resources from these aggregates:
14:06:57 INFO    : 	<Aggregate uwash-ig>
14:06:57 INFO    : 	<Aggregate gpo-ig>
14:06:57 INFO    : 	<Aggregate al2s>
14:06:57 INFO    : 	<Aggregate ion>
14:06:57 INFO    : Stitcher doing createsliver at <Aggregate uwash-ig>...
14:07:14 INFO    : ... Allocation at <Aggregate uwash-ig> complete.
14:07:15 INFO    : Stitcher doing createsliver at <Aggregate gpo-ig>...
14:07:31 INFO    : ... Allocation at <Aggregate gpo-ig> complete.
14:07:31 INFO    : Stitcher doing createsliver at <Aggregate al2s>...
14:07:38 INFO    : ... Allocation at <Aggregate al2s> complete.
14:07:38 INFO    : Stitcher doing createsliver at <Aggregate ion>...
14:08:26 INFO    : DCN AM <Aggregate ion>: must wait for status ready....
14:08:26 INFO    : Pausing 30 seconds to let circuit become ready...
14:09:03 INFO    : Pausing 30 seconds to let circuit become ready...
14:09:41 INFO    : DCN circuit 153581 is ready at <Aggregate ion>
14:09:41 INFO    : DCN circuit 153591 is ready at <Aggregate ion>
14:09:48 INFO    : ... Allocation at <Aggregate ion> complete.
14:09:48 INFO    : All aggregates are complete.
14:09:48 INFO    : Your resources expire at 2015-02-17T18:56:57 (UTC). 
14:09:48 INFO    : Saved combined reservation RSpec at 4 AMs to file '/home/lnevers/gcf-test/stitch-test/Washington/IG-ST-2-manifest-rspec-multiam-combined.xml'
Success: Reserved resources in slice IG-ST-2 at 4 Aggregates (including 2 intermediate aggregate(s) not in the original request), creating 2 stitched link(s).

Determined login information at each Washington and GPO aggregate:

$ readyToLogin.py IG-ST-2 --useSliceAggregates
  ....
ig-wash's geni_status is: ready 
User lnevers logs in to ig-wash using:
	ssh -p 30522  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc3.instageni.washington.edu
 ....
ig-gpo's geni_status is: ready 
User lnevers logs in to ig-gpo using:
	ssh -p 34874  -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:

remote-execute.py IG-ST-2 -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

IG-ST-4 New Site to GPO EG interoperability

IG-ST-5 Site Information

IG-ST-6 New Site OpenFlow topology