wiki:GeniSite/Internet2

Version 20 (modified by tupty@bbn.com, 6 years ago) (diff)

--

Internet 2

GENI connections using Internt2 can be found at: ConnectivityHome.

Contact

Submit issues or VLAN provisioning/translation requests through:

Report a Problem

ION

From the ION HowTo:

Internet2 ION (Interoperable On-demand Network) is a revolutionary network service that allows researchers and engineers alike to create dedicated, point-to-point optical circuits—for immediate or future use—through a simple, secure web interface.

ION connectors

For a complete list of Organizations that can connect to ION see, http://www.internet2.edu/ion/connector-status.html

Known Issues

  • A person with an ION account currently cannot see circuits provisioned by other members of the same organization.
    • There are potential work arounds for seeing all circuits provisioned to a given endpoint name. Talk to I2 staff if you require this ability.
  • The history view returns an error.

Establishing an Endpoint

Internet2 Higher-Education Members

From the ION HowTo:

Researchers at Internet2 higher education member institutions who wish to collaborate using ION should first contact their campus network organization for support. The campus network team can then determine if their institution has an “enabled” link to an Internet2 Connector or other regional network. If their Internet2 Connector does not yet have a physical connection to ION, the Connector can submit a request using the process outlined above.

Initial Connections

From the ION HowTo:

The first step to take advantage of ION service is to interconnect with the Internet2 ION infrastructure via a 1GigE or 10GigE Ethernet connection. The logistics of that connection will be handled as part of the turnup process.

How Can Internet2 Members Determine if They Are ION-enabled?

The current ION service uses the Internet2 Juniper infrastructure and any can create a Layer 2 MPLS LSP to any site physically connected to the Internet2 IP backbone.

ION Web Service Account

The contact address for getting new ION accounts is: systems-support@tick.globalnoc.iu.edu.

VLAN Provisioning within ION

This section outlines Provisioning within ION's web service, for the complete procedure of provisioning a VLAN between two sites see ConnectivityGuidelines.

Once you have an ION account you will be able to provision VLANs between site's endpoints using the ION VLAN provisioning webpage.

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

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
1750 Yes Translation; SoX transport; UKY transport
1754 No K-State transport
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

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
gi0/15 gi0/16 1750
gi0/16 gi0/15
gi0/17 gi0/18 1750
gi0/18 gi0/17
gi0/19 gi0/20 1750
gi0/20 gi0/19 1754
gi0/21 gi0/22 1750
gi0/22 gi0/21
gi0/23 gi0/24 1750
gi0/24 gi0/23
Te0/25 atla.of.nlr.net T 3715 3716
Te0/26 AL2S ATLA T 1754

HOUS

VLANs

VLANOF Enabled?Purpose
1750 Yes Translation; KANREN transport
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); KSU transport
3716 Yes Backbone (bus topology); KSU transport
3717 Yes Backbone (loop topology)

Ports

PortConnects ToVLAN Config
gi0/1 ION HOUS T 3715 3716
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
gi0/21 gi0/22 1750
gi0/22 gi0/21
gi0/23 gi0/24 1750
gi0/24 gi0/23
Te0/25
Te0/26

LOSA

VLANs

VLANOF Enabled?Purpose
1750 Yes Translation; UEN transport; CENIC transport
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

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
gi0/21 gi0/22 1750
gi0/22 gi0/21
gi0/23 gi0/24 1750
gi0/24 gi0/23
Te0/25
Te0/26 AL2S LOSA

NEWY

VLANs

VLANOF Enabled?Purpose
1750 Yes Translation; GPO transport; WVNET transport; NYU transport; NYSERNet transport
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

PortConnects ToVLAN Config
gi0/1 ION NEWY T 1750
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
gi0/5
gi0/6
gi0/7
gi0/8
gi0/9
gi0/10
gi0/11
gi0/12 NYSERNet T 1750
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
gi0/21 gi0/22 1750
gi0/22 gi0/21
gi0/23 gi0/24 1750
gi0/24 gi0/23
Te0/25
Te0/26 AL2S NEWY T 1750

WASH

VLANs

VLANOF Enabled?Purpose
1750 Yes Translation; OSU transport
1751 No MOXI transport
1752 No Princeton transport
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); Rutgers transport
3716 Yes Backbone (bus topology); Rutgers transport
3717 Yes Backbone (loop topology)

Ports

PortConnects ToVLAN Config
gi0/1 ION WASH T 1750 1751 1752 3715 3716
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

Email us with questions and feedback on this page!

Attachments (2)