Changes between Version 11 and Version 12 of GENIOESSTopologiesTestStatus/OESS-T2
- Timestamp:
- 10/22/13 12:09:39 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIOESSTopologiesTestStatus/OESS-T2
v11 v12 8 8 9 9 || '''Scenario''' || '''State''' || ''' Ticket ''' || '''Notes''' || 10 || 1. ION to AL2S experiment || 10 || 1. ION to AL2S experiment ||[[Color(#63B8FF,In Progress)]]|| || || 11 11 || 2. Meso-scale to AL2S experiment|| || || || 12 12 || 3. AL2S to AL2s experiment || || || || … … 22 22 [[BR]] 23 23 24 == Test Execution Details == 25 Two endpoints will be connected with the cross-connects defined in each section below. 24 == 1. ION to AL2S experiments == 26 25 27 === 1. ION to AL2S experiment === 26 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. 28 27 29 An ION to AL2S experiment will connect GPO IG ION to an AL2S Test endpoint.28 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. 30 29 31 In order for the above to work, some cross-connect configuration had to be defined to the GENI Stitching Computation Service(SCS) to define the ION side of the cross-point. 32 The ION part of this topology is set 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 by the user and reserved via the OESS Aggregate. 33 34 These are the cross-connects configured for SCS: 30 These are the cross-connects that are verified: 35 31 36 32 ||''' x-connect'''||''' AL2S Ports ''' || ''' ION Ports''' || … … 56 52 || urn="urn:publicid:IDN+oess:foam:nddi+sdn-sw.wash.net.internet2.edu+e15/2" || 57 53 58 VLAN ranges suggested by Luke for testing: '' 3950-4000'' 54 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. 59 55 60 '''Cross-connect 1 - sdn-sw.losa e1/1 <-> rtr.losa:port=et-10/0/0 ''' 56 The VLAN ranges used for testing: '' 3950-4000'' 57 58 === Cross-connect 1 - sdn-sw.losa e1/1 <-> rtr.losa:port=et-10/0/0 === 61 59 62 60 For the first topology attempted tried the following: … … 67 65 68 66 69 '''Cross-connect 2 - sdn-sw.atla e15/1 <-> rtr.atla:port=xe-0/3/0 ''' 67 === Cross-connect 2 - sdn-sw.atla e15/1 <-> rtr.atla:port=xe-0/3/0 === 70 68 71 '''Cross-connect 3 - sdn-sw.chic e3/1 <-> rtr.chic:port=et-10/0/0''' 69 === Cross-connect 3 - sdn-sw.chic e3/1 <-> rtr.chic:port=et-10/0/0 === 72 70 73 '''Cross-connect 4 - sdn-sw.clev e5/1 <-> rtr.clev:port=et-5/0/0''' 71 === Cross-connect 4 - sdn-sw.clev e5/1 <-> rtr.clev:port=et-5/0/0 === 74 72 75 '''Cross-connect 5 - sdn-sw.hous e15/3 <-> rtr.hous:port=xe-0/1/3''' 73 === Cross-connect 5 - sdn-sw.hous e15/3 <-> rtr.hous:port=xe-0/1/3 === 76 74 77 '''Cross-connect 6 - sdn-sw.kans e15/1 <-> rtr.kans:port=xe-0/0/3''' 75 === Cross-connect 6 - sdn-sw.kans e15/1 <-> rtr.kans:port=xe-0/0/3 === 78 76 79 '''Cross-connect 7 - sdn-sw.newy32aoa e3/2 <-> rtr.newy:port=et-5/0/0''' 77 === Cross-connect 7 - sdn-sw.newy32aoa e3/2 <-> rtr.newy:port=et-5/0/0 === 80 78 81 '''Cross-connect 8 - sdn-sw.salt e15/1 <-> rtr.salt:port=xe-0/1/1''' 79 === Cross-connect 8 - sdn-sw.salt e15/1 <-> rtr.salt:port=xe-0/1/1 === 82 80 83 '''Cross-connect 9 - sdn-sw.seat e-2/0/0.0 <-> rtr.seat:port=et-5/0/0''' 81 === Cross-connect 9 - sdn-sw.seat e-2/0/0.0 <-> rtr.seat:port=et-5/0/0 === 84 82 85 '''Cross-connect 10 - sdn-sw.wash e5/2 <-> rtr.wash:port=et-9/0/0 ''' 83 === Cross-connect 10 - sdn-sw.wash e5/2 <-> rtr.wash:port=et-9/0/0 === 86 84 87 85