= OESS-T2: Two Site Cross-connect tests =

This test case verifies Two Site Cross-connect scenarios. For overall status see the [wiki:GENIOESSTopologiesTestStatus GENI OESS Topologies Test Status] page. 


= Test Status =
This section captures the status for each function verified by this test plan.

|| '''Scenario'''                  || '''State'''  || ''' Ticket '''  || '''Notes'''   ||
|| 1. ION to AL2S experiment       ||[[Color(#63B8FF,In Progress)]]||                 ||               ||
|| 2. Meso-scale to AL2S experiment||              ||                 ||               ||
|| 3. AL2S to AL2s experiment      ||              ||                 ||               ||

[[BR]]
|| '''State Legend'''                     || '''Description'''                                                    ||
|| [[Color(green,Pass)]]                  || Test completed and met all criteria                                  ||
|| [[Color(#98FB98,Pass: most criteria)]] || Test completed and met most criteria. Exceptions documented          ||
|| [[Color(red,Fail)]]                    || Test completed and failed to meet criteria.                          ||
|| [[Color(yellow,Complete)]]             || Test completed but will require re-execution due to expected changes ||
|| [[Color(orange,Blocked)]]              || Blocked by ticketed issue(s).                                        ||
|| [[Color(#63B8FF,In Progress)]]         || Currently under test.                                                ||
[[BR]]

== 1. ION to AL2S experiments ==

The two endpoints GPO IG host and AL2S test endpoints will be connected using each of the 10 cross-connects defined between Internet ION aggregate and AL2S OESS aggregate. 

The ten cross-connect were configured in the GENI Stitching Computation Service(SCS) to define the ION side of the network path. The ION part of this topology is set up with the dynamic GENI Network Stitching which uses SCS to determine paths.  The AL2S side of the topology is set up with AM API interface using OMNI, but the path is defined manually defined by the user and reserved via the OESS Aggregate.

These are the cross-connects that are verified:

||''' x-connect'''||''' AL2S Ports '''       || ''' ION Ports'''   ||
|| ||
|| 1 || sdn-sw.losa  e1/1 || urn:ogf:network:domain=ion.internet2.edu:node=rtr.losa:port=et-10/0/0:link=al2s||
|| 2 || sdn-sw.atla  e15/1 ||  urn:ogf:network:domain=ion.internet2.edu:node=rtr.atla:port=xe-0/3/0:link=al2s||
|| 3 || sdn-sw.chic  e3/1 || urn:ogf:network:domain=ion.internet2.edu:node=rtr.chic:port=et-10/0/0:link=al2s||
|| 4 || sdn-sw.clev  e5/1 || urn:ogf:network:domain=ion.internet2.edu:node=rtr.clev:port=et-5/0/0:link=al2s||
|| 5 ||sdn-sw.hous  e15/3 ||  urn:ogf:network:domain=ion.internet2.edu:node=rtr.hous:port=xe-0/1/3:link=al2s||
|| 6 ||sdn-sw.kans  e15/1 || urn:ogf:network:domain=ion.internet2.edu:node=rtr.kans:port=xe-0/0/3:link=al2s||
|| 7 ||sdn-sw.newy32aoa     e3/2 ||  urn:ogf:network:domain=ion.internet2.edu:node=rtr.newy:port=et-5/0/0:link=al2s||
|| 8 ||sdn-sw.salt  e15/1 ||  urn:ogf:network:domain=ion.internet2.edu:node=rtr.salt:port=xe-0/1/1:link=al2s||
|| 9 ||sdn-sw.seat  e-2/0/0.0 ||  urn:ogf:network:domain=ion.internet2.edu:node=rtr.seat:port=et-5/0/0:link=al2s||
|| 10 || sdn-sw.wash  e5/2 || urn:ogf:network:domain=ion.internet2.edu:node=rtr.wash:port=et-9/0/0:link=al2s||

These are the test endpoint that are available for testing and 

|| AL2S Test Endpoints ||
|| ||
|| urn="urn:publicid:IDN+oess:foam:nddi+sdn-sw.atla.net.internet2.edu+e15/3" ||
|| urn="urn:publicid:IDN+oess:foam:nddi+sdn-sw.losa.net.internet2.edu+e15/3" ||
|| urn="urn:publicid:IDN+oess:foam:nddi+sdn-sw.newy32aoa.net.internet2.edu+e15/5" ||
|| urn="urn:publicid:IDN+oess:foam:nddi+sdn-sw.wash.net.internet2.edu+e15/2" ||

The Atlanta test end-poing is used for all 10 scenarios covered.  The GPO endpoint is a node in the InstaGENI rack, which changes with every set up.

The VLAN ranges used for testing: '' 3950-4000''

=== Cross-connect 1 - sdn-sw.losa e1/1 <-> rtr.losa:port=et-10/0/0 ===

For the first topology attempted tried the following:

GPO IG <->(ION)->[(rtr.losa:port=et-10/0/0:link=al2s)cross-connect(sdn-sw.losa e1/1)]<->(AL2S)<->Atlanta Test Endpoint (sdn-sw.atla  e15/3)

<<<Attach log and rspecs>>>


=== Cross-connect 2 - sdn-sw.atla e15/1  <-> rtr.atla:port=xe-0/3/0 ===
 
=== Cross-connect 3 - sdn-sw.chic e3/1  <->  rtr.chic:port=et-10/0/0 ===

=== Cross-connect 4 - sdn-sw.clev e5/1  <->  rtr.clev:port=et-5/0/0 ===

=== Cross-connect 5 - sdn-sw.hous e15/3 <->  rtr.hous:port=xe-0/1/3 ===

=== Cross-connect 6 - sdn-sw.kans e15/1 <->  rtr.kans:port=xe-0/0/3 ===
 
=== Cross-connect 7 - sdn-sw.newy32aoa e3/2 <-> rtr.newy:port=et-5/0/0 ===

=== Cross-connect 8 -  sdn-sw.salt e15/1  <->  rtr.salt:port=xe-0/1/1 ===

=== Cross-connect 9 - sdn-sw.seat e-2/0/0.0  <-> rtr.seat:port=et-5/0/0 ===

=== Cross-connect 10 - sdn-sw.wash e5/2 <-> rtr.wash:port=et-9/0/0 ===


== 2. Meso-scale to AL2S experiment ==

A Meso-scale to AL2S experiment will connect GPO IG ION to Meso-scale VLAN to MAX AL2S.  Or if available, experiment may use NYU IG Meso-scale to MAX IG AL2S.

== 3. AL2S to AL2s experiment ==

An AL2S to AL2s experiment will connect MAX IG AL2S to an AL2S Test Point. Note, AL2S test-points are available and will be used throughout testing to help establish network connections defined in this plan.