wiki:GENIRacksHome/Operators/iMindsSCS

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

--

  1. iMinds SCS
      1. Contact
  2. Stitching Service Details
    1. Establishing Connections to Endpoint iMinds End-points
    2. Stitching Path details
      1. Required Topology Info
      2. Creating the Circuit
    3. extending an ION circuit
    4. VLAN Translation
  3. Experiments
    1. OpenFlow
      1. Shared Mesoscale VLANs
      2. Exclusive Mesoscale VLANs
  4. Connection Inventory
    1. ATLA
      1. VLANs
      2. Ports
    2. HOUS
      1. VLANs
      2. Ports
    3. LOSA
      1. VLANs
      2. Ports
    4. NEWY
      1. VLANs
      2. Ports
    5. WASH
      1. VLANs
      2. Ports

iMinds SCS

​iMinds is Flanders' digital research center and business incubator established in 2004. The iMinds team runs a Stitching Computation Service (SCS) that supports both GENI and iMinds stitching computation.

Contact

Submit issues or question about the iMinds SCS to <insert email here for SCS issues contact>

<question> Should GMOC be involved in problem reporting? <if yes, insert http://globalnoc.iu.edu/i2network/support/report-a-problem.html>

Stitching Service Details

The iMinds SCS service is based on the MAX SCS service. This service includes known GENI stitching paths in addition to iMinds stitching paths.

Establishing Connections to Endpoint iMinds End-points

Using GENI credentials and the jFed toolkit embedded in the ​GENI portal any GENI user can request resources in both GENI and iMinds environments. The jFed toolkit can also be accessed outside of GENI environment at this ​location.

Stitching Path details

iMinds has ​3 resource aggregates, but only two aggregates support stitching:

Aggregate name AM API V3 URL AM API V2
Virtual Wall 1 https://www.wall1.ilabt.iminds.be:12369/protogeni/xmlrpc/am/3.0 https://www.wall1.ilabt.iminds.be:12369/protogeni/xmlrpc/am/2.0
Virtual Wall 2 https://www.wall2.ilabt.iminds.be:12369/protogeni/xmlrpc/am/3.0 https://www.wall2.ilabt.iminds.be:12369/protogeni/xmlrpc/am/2.0

Stitching Information for Virtual Walls:

Link id remoteLinkId Stitching VLAN range
urn:publicid:IDN+wall1.ilabt.iminds.be+interface+c300a:7.44 urn:publicid:IDN+wall2.ilabt.iminds.be+interface+c300b:0.16 197,300-349,750-1000
urn:publicid:IDN+wall2.ilabt.iminds.be+interface+c300b:0.12 urn:publicid:IDN+ion.internet2.edu+interface+rtr.newy:xe-0/2/2:* 300-349

Required Topology Info

  • Your endpoint's name
  • Your VLAN to this endpoint to dedicate to connecting to the other site.
  • Your partner site's endpoint's name
  • The VLAN that your partner site is dedicating to connecting to your site.

Creating the Circuit

If you know the other endpoint's ION name, creating a circuit is straightforward. Click the 'Reserve Circuits' tab, and fill out appropriate values. Things to know:

  • "source" tab:
    • Description: put something meaningful and unique here, in case the first test fails, though the ION ID is also unique
    • Source: your campus's ION endpoint. It would be similar to bbn.bost.dcn.internet2.edu
  • "destination" tab:
    • Destination: the other endpoint's ION name. If you don't already know this you may be able to browse for a reasonable name
  • "time" tab: change these values to make the circuit good for the length of time you need; 1 hour isn't very useful
  • "bandwidth" tab: as appropriate though keep this as small as possible.
  • "vlan" tab:
    • Unclick "Same VLAN number on source and destination"
    • The source VLAN will be the VLAN you've provisioned to your endpoint for this connection. Usually this will be a "Tagged" VLAN. (i.e. dot1q)
    • The destination VLAN should be whatever you agreed on with the remote site. The tagging status is also whatever is appropriate for them (probably also tagged)

extending an ION circuit

It's possible to "extend" the reservation of existing ION circuits. Do this by clicking on "View/Edit" for the circuit in question and then enter the circuit's new expiration date and time.

Note the "cancel" button in the "view circuits" screen means canceling, i.e. de-provision, the circuit. this does not cancel the edit request and take you back to the screen listing the ION circuits.

VLAN Translation

ION can do VLAN translation as mentioned in above. ION will provide VLAN translation automatically if the "Same VLAN number on source and destination" is unchecked; the two VLAN ID's do not need to be equal.

Experiments

OpenFlow

Internet2's OpenFlow deployment GENI page: OFI2

The Internet2 OpenFlow Aggregate (i2-of) FlowVisor is running a newer FV version than most sites: 1.0.8. There are issues with collecting flowstats for this version of FV.

DPIDs in the I2 OF core (sorted by DPID):

Shared Mesoscale VLANs

switch VLAN 3715 VLAN 3716 VLAN 3717
of.newy.net.internet2.edu 0e:83:00:12:e2:22:63:1d 0e:84:00:12:e2:22:63:1d 0e:85:00:12:e2:22:63:1d
of.wash.net.internet2.edu 0e:83:00:12:e2:22:6f:e5 0e:84:00:12:e2:22:6f:e5 0e:85:00:12:e2:22:6f:e5
of.atla.net.internet2.edu 0e:83:00:12:e2:22:63:6e 0e:84:00:12:e2:22:63:6e 0e:85:00:12:e2:22:63:6e
of.hous.net.internet2.edu 0e:83:00:12:e2:22:81:42 0e:84:00:12:e2:22:81:42 0e:85:00:12:e2:22:81:42
of.losa.net.internet2.edu 0e:83:00:12:e2:22:63:38 0e:84:00:12:e2:22:63:38 0e:85:00:12:e2:22:63:38

Exclusive Mesoscale VLANs

switch VLAN 1755 VLAN 1756 VLAN 1757 VLAN 1758 VLAN 1759
of.newy.net.internet2.edu 06:db:00:12:e2:22:63:1d 06:dc:00:12:e2:22:63:1d 06:dd:00:12:e2:22:63:1d 06:de:00:12:e2:22:63:1d 06:df:00:12:e2:22:63:1d
of.wash.net.internet2.edu 06:db:00:12:e2:22:6f:e5 06:dc:00:12:e2:22:6f:e5 06:dd:00:12:e2:22:6f:e5 06:de:00:12:e2:22:6f:e5 06:df:00:12:e2:22:6f:e5
of.atla.net.internet2.edu 06:db:00:12:e2:22:63:6e 06:dc:00:12:e2:22:63:6e 06:dd:00:12:e2:22:63:6e 06:de:00:12:e2:22:63:6e 06:df:00:12:e2:22:63:6e
of.hous.net.internet2.edu 06:db:00:12:e2:22:81:42 06:dc:00:12:e2:22:81:42 06:dd:00:12:e2:22:81:42 06:de:00:12:e2:22:81:42 06:df:00:12:e2:22:81:42
of.losa.net.internet2.edu 06:db:00:12:e2:22:63:38 06:dc:00:12:e2:22:63:38 06:dd:00:12:e2:22:63:38 06:de:00:12:e2:22:63:38 06:df:00:12:e2:22:63:38

Connection Inventory

ATLA

VLANs

VLANOF Enabled?Purpose
1748 Yes RENCI transport (OF enabled for layer1transport)
1749 Yes FIU transport (OF enabled for layer1transport)
1750 Yes Translation; SoX transport; UKY transport; UMC transport
1751 Yes UFL transport
1752 Yes Kansas transport (OF enabled for layer1transport)
1753 Yes StarLight transport (OF enabled for layer1transport)
1754 Yes K-State transport (OF enabled for layer1transport)
1755 Yes Exclusive OpenFlow VLAN
1756 Yes Exclusive OpenFlow VLAN
1757 Yes Exclusive OpenFlow VLAN
1758 Yes Exclusive OpenFlow VLAN
1759 Yes Exclusive OpenFlow VLAN
3715 Yes Backbone (star topology)
3716 Yes Backbone (bus topology)
3717 Yes Backbone (loop topology)

Ports

In the VLAN Config column, a single ID indicates that the port is an access port on that VLAN. A T followed by one or more IDs indicates that the port is a trunk (aka tagged) port with those VLAN IDs.

PortConnects ToVLAN Config
gi0/1 ION ATLA T 1750 1755 1756 1757 1758 1759 3715 3716
gi0/2 of.wash.net.internet2.edu T 1755 1756 1757 1758 1759 3715 3716 3717
gi0/3 of.hous.net.internet2.edu T 1755 1756 1757 1758 1759 3715 3717
gi0/4 SoX T 1750 1755 1756 1757 1758 1759
gi0/5
gi0/6
gi0/7 gi0/8 1750
gi0/8 gi0/7 3715
gi0/9 gi0/10 1750
gi0/10 gi0/9 3716
gi0/11 gi0/12 1750
gi0/12 gi0/11 3717
gi0/13 gi0/14 1750
gi0/14 gi0/13 1752
gi0/15 gi0/16 1750
gi0/16 gi0/15 1751
gi0/17 gi0/18 1750
gi0/18 gi0/17 1748
gi0/19 gi0/20 1750
gi0/20 gi0/19 1754
gi0/21 gi0/22 1750
gi0/22 gi0/21 1749
gi0/23 gi0/24 1750
gi0/24 gi0/23 1753
Te0/25 atla.of.nlr.net
Te0/26 AL2S ATLA T 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759

HOUS

VLANs

VLANOF Enabled?Purpose
1750 Yes Translation
1751 Yes UH transport (OF enabled for layer1transport)
1755 Yes Exclusive OpenFlow VLAN
1756 Yes Exclusive OpenFlow VLAN
1757 Yes Exclusive OpenFlow VLAN
1758 Yes Exclusive OpenFlow VLAN
1759 Yes Exclusive OpenFlow VLAN
1760 Yes UMKC transport (OF enabled for layer1transport)
2497 Yes ohmetrodc-ig transport (OF enabled for layer1transport)
3715 Yes Backbone (star topology)
3716 Yes Backbone (bus topology)
3717 Yes Backbone (loop topology)

Ports

In the VLAN Config column, a single ID indicates that the port is an access port on that VLAN. A T followed by one or more IDs indicates that the port is a trunk (aka tagged) port with those VLAN IDs.

PortConnects ToVLAN Config
gi0/1 ION HOUS T 1751 1755 1756 1757 1758 1759 1760 2497
gi0/2 of.atla.net.internet2.edu T 1755 1756 1757 1758 1759 3715 3717
gi0/3 of.losa.net.internet2.edu T 1755 1756 1757 1758 1759 3715 3716 3717
gi0/4
gi0/5
gi0/6
gi0/7
gi0/8
gi0/9
gi0/10
gi0/11
gi0/12
gi0/13 gi0/14 1750
gi0/14 gi0/13 3715
gi0/15 gi0/16 1750
gi0/16 gi0/15 3716
gi0/17 gi0/18 1750
gi0/18 gi0/17 3717
gi0/19 gi0/20 1750
gi0/20 gi0/19 1751
gi0/21 gi0/22 1750
gi0/22 gi0/21 2497
gi0/23 gi0/24 1750
gi0/24 gi0/23 1760
Te0/25
Te0/26

LOSA

VLANs

VLANOF Enabled?Purpose
1750 Yes Translation; UEN transport; CENIC transport
1751 Yes OSF transport (OF enabled for layer1transport)
1755 Yes Exclusive OpenFlow VLAN
1756 Yes Exclusive OpenFlow VLAN
1757 Yes Exclusive OpenFlow VLAN
1758 Yes Exclusive OpenFlow VLAN
1759 Yes Exclusive OpenFlow VLAN
1805 Yes UH transport (OF enabled for layer1transport)
1853 Yes UCDavis transport
3715 Yes Backbone (star topology)
3716 Yes Backbone (bus topology)
3717 Yes Backbone (loop topology)

Ports

In the VLAN Config column, a single ID indicates that the port is an access port on that VLAN. A T followed by one or more IDs indicates that the port is a trunk (aka tagged) port with those VLAN IDs.

PortConnects ToVLAN Config
gi0/1 ION LOSA T 1750 3715 3716
gi0/2 of.hous.net.internet2.edu T 1755 1756 1757 1758 1759 3715 3716 3717
gi0/3 of.newy.net.internet2.edu T 1755 1756 1757 1758 1759 3715 3716 3717
gi0/4
gi0/5
gi0/6
gi0/7
gi0/8
gi0/9
gi0/10
gi0/11
gi0/12 UEN T 1750 1755 1756 1757 1758 1759
gi0/13 gi0/14 1750
gi0/14 gi0/13 3715
gi0/15 gi0/16 1750
gi0/16 gi0/15 3716
gi0/17 gi0/18 1750
gi0/18 gi0/17 3717
gi0/19 gi0/20 1750
gi0/20 gi0/19 1853
gi0/21 gi0/22 1750
gi0/22 gi0/21 1751
gi0/23 gi0/24 1750
gi0/24 gi0/23 (reserved 1805)
Te0/25
Te0/26 AL2S LOSA T 1751 (reserved 1805) 1853

NEWY

VLANs

VLANOF Enabled?Purpose
1750 Yes Translation; GPO transport; WVNET transport; NYU transport; NYSERNet transport
1751 Yes Illinois transport (OF enabled for layer1transport)
1755 Yes Exclusive OpenFlow VLAN
1756 Yes Exclusive OpenFlow VLAN
1757 Yes Exclusive OpenFlow VLAN
1758 Yes Exclusive OpenFlow VLAN
1759 Yes Exclusive OpenFlow VLAN
3715 Yes Backbone (star topology)
3716 Yes Backbone (bus topology)
3717 Yes Backbone (loop topology)
4083 No fia-mobilityfirst from NYU
4084 No fia-ndn from NYU
4085 No fia-xia from NYU
4086 No reservedvlan1 from NYU
4087 No reservedvlan2 from NYU

Ports

In the VLAN Config column, a single ID indicates that the port is an access port on that VLAN. A T followed by one or more IDs indicates that the port is a trunk (aka tagged) port with those VLAN IDs.

PortConnects ToVLAN Config
gi0/1 ION NEWY T 1750 1755 1756 1757 1758 1759 4085 4086 4087
gi0/2 of.losa.net.internet2.edu T 1755 1756 1757 1758 1759 3715 3716 3717
gi0/3 of.wash.net.internet2.edu T 1755 1756 1757 1758 1759 3716 3717
gi0/4 NYU GENI rack T 1750 1755 1756 1757 1758 1759 4083 4084 4085 4086 4087
gi0/5
gi0/6
gi0/7
gi0/8
gi0/9
gi0/10
gi0/11
gi0/12 NYSERNet T 1750 1755 1756 1757 1758 1759
gi0/13 gi0/14 1750
gi0/14 gi0/13 3715
gi0/15 gi0/16 1750
gi0/16 gi0/15 3716
gi0/17 gi0/18 1750
gi0/18 gi0/17 3717
gi0/19 gi0/20 1750
gi0/20 gi0/19 (reserved for NCSU)
gi0/21 gi0/22 1750
gi0/22 gi0/21 1751
gi0/23 gi0/24 1750
gi0/24 gi0/23 (reserved for VT)
Te0/25
Te0/26 AL2S NEWY T 1750 1751 1755 1756 1757 1758 1759 4083 4084 4085 4086 4087

WASH

VLANs

VLANOF Enabled?Purpose
1750 Yes Translation; OSU transport; MAX transport
1751 No MOXI transport (OF enabled for layer1transport)
1752 No Princeton transport (OF enabled for layer1transport)
1755 Yes Exclusive OpenFlow VLAN
1756 Yes Exclusive OpenFlow VLAN
1757 Yes Exclusive OpenFlow VLAN
1758 Yes Exclusive OpenFlow VLAN
1759 Yes Exclusive OpenFlow VLAN
3715 Yes Backbone (star topology)
3716 Yes Backbone (bus topology)
3717 Yes Backbone (loop topology)

Ports

In the VLAN Config column, a single ID indicates that the port is an access port on that VLAN. A T followed by one or more IDs indicates that the port is a trunk (aka tagged) port with those VLAN IDs.

PortConnects ToVLAN Config
gi0/1 ION WASH T 1750 1751 1752
gi0/2 of.newy.net.internet2.edu T 1755 1756 1757 1758 1759 3716 3717
gi0/3 of.atla.net.internet2.edu T 1755 1756 1757 1758 1759 3715 3716 3717
gi0/4
gi0/5
gi0/6
gi0/7
gi0/8
gi0/9
gi0/10
gi0/11
gi0/12
gi0/13 gi0/14 1750
gi0/14 gi0/13 3715
gi0/15 gi0/16 1750
gi0/16 gi0/15 3716
gi0/17 gi0/18 1750
gi0/18 gi0/17 3717
gi0/19 gi0/20 1750
gi0/20 gi0/19 1751
gi0/21 gi0/22 1750
gi0/22 gi0/21 1752
gi0/23
gi0/24
Te0/25
Te0/26 AL2S WASH T 1750 1755 1756 1757 1758 1759

Email us with questions and feedback on this page!