| Version 75 (modified by , 13 years ago) (diff) |
|---|
Internet 2
- http://www.internet2.edu -- homepage
- http://www.internet2.edu/maps/network -- network map
- http://routerproxy.grnoc.iu.edu/internet2/ -- tool for debugging connectivity issues.
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.
- http://www.internet2.edu/ion/ -- ION homepage
- https://ion.net.internet2.edu:8443/ion/# -- ION VLAN provisioning
- http://iondemo.net.internet2.edu/ -- demo (use
guestfor username and password)
Known Issues
- A person with an ION account currently cannot see circuits provisioned by other members of the same organization.
- The history view always returns an error.
ION Endpoints
| Organization | ION endpoint name |
| SiteBbn | NOX.newy.ion.internet2.edu (old) |
| SiteBbn | bbn.newy.ion.internet2.edu (new) |
| SiteRutgers | MAGPI.wash.ion.internet2.edu |
| SiteKansasState | GPN.kans.ion.internet2.edu |
| ProtoGENI - Salt Lake City POP | ProtoGENI.salt.ion.internet2.edu |
| ProtoGENI - Washington, D.C. POP | ProtoGENI.wash.ion.internet2.edu |
| ProtoGENI - Kansas City, MO POP | ProtoGENI.kans.ion.internet2.edu |
| OpenFlow ATLA cross-connect | openflow.atla.ion.internet2.edu |
GENI ION VLANs
| circuit # | ION VLAN | Status | Expires | endpoint | endpoint | I2 ION testpoint | Bandwidth | Details |
| 1137 | 670 | UP | 11/30/2010 | NOX.newy.ion.internet2.edu (SiteBbn) | ProtoGENI.salt.ion.internet2.edu | -- | 100 Mbps | GENI-Violin demo #IONVLAN670 |
| 979 | 3728 | expired | 11/05/2010 | SiteBbn | ProtoGENI.salt | -- | 100 Mbps | |
| 1149 | 3729 | UP | 11/30/2010 | bbn.newy.ion.internet2.edu (SiteBbn) | ProtoGENI.kans | -- | 100 Mbps | NetServ #IONVLAN3729 |
| 978 | 3733 | expired | 11/05/2010 | SiteBbn | SiteRutgers | -- | 100 Mbps | |
| 1049 | 3740 | expired | 11/05/2010 | SiteBbn | cron.loni.org | -- | 100 Mbps | |
| -- | #IONVLAN3730 | expired | -- | SiteBbn | ProtoGENI.wash | -- | 50 Mbps | |
| ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- |
| 1138 | 917 | UP | 11/30/2010 | ProtoGENI.kans.ion.internet2.edu | openflow.atla.ion.internet2.edu | 10.9.17.222/24 | 100 Mbps | NetServ, To SiteClemson via NLR VLAN 917 #IONVLAN917 |
| 953 | 3738 | expired | 11/05/2010 | SiteKansasState | openflow.atla.ion.internet2.edu | 10.37.38.222/24 | 100 Mbps | SmartRE, To SiteStanford (VLAN 3738) via NLR |
| 900 | 3734 | expired | 11/05/2010 | SiteRutgers | openflow.atla.ion.internet2.edu | 10.37.34.222/24 | 100 Mbps | To SiteStanford ia NLR (VLAN 3722) (not up end to end) |
| -- | #IONVLAN3735 | expired | -- | SiteRutgers | openflow.atla.ion.internet2.edu | 10.37.35.222/24 | 100 Mbps | To NLR OpenFlow Core North (NLR VLAN 3715) |
| -- | #IONVLAN3736 | expired | -- | SiteRutgers | openflow.atla.ion.internet2.edu | 10.37.36.222/24 | 100 Mbps | To NLR OpenFlow Core South (NLR VLAN 3716) |
| -- | #IONVLAN3737 | expired | -- | SiteRutgers | openflow.atla.ion.internet2.edu | 10.37.37.222/24 | 100 Mbps | To NLR Multipoint (NLR VLAN 3705) |
| ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- |
| -- | #IONVLAN3727 | deprecated | -- | SiteBbn | SiteRutgers | -- | -- | Required VLAN translation, not supported |
| -- | -- | future | -- | SiteBbn | SiteWashington | -- | -- | Currently connected via SiteNlr |
| -- | -- | future | -- | SiteBbn | SiteWisconsin | -- | -- | Currently connected via SiteNlr |
| -- | -- | future | -- | SiteRutgers | SiteIndiana | -- | -- |
ION VLAN 3727
Depricated
| Site | VLAN | IP | MAC (if known) | Purpose |
| SiteBbn | 3727 | 10.37.27.100/24 | 00:0C:29:4A:B0:23 | ping |
| SiteRutgers | 190 | 10.37.27.101/24 | 00:1b:21:32:b5:5c | ping, iperf |
| MagPI (regional) | 190 | 10.37.27.102/24 | 00:23:9c:19:0f:d8 | ping |
ION VLAN 3728
| Site | IP | MAC (if known) | Purpose |
| SiteBbn | 10.37.28.100/24 | 00:0C:29:4A:B0:19 | ping |
| ProtoGENI Salt Lake City | 10.37.28.101/24 | 00:1B:21:3A:0E:89 | ping |
ION VLAN 3733
| Site | IP | MAC (if known) | Purpose |
| SiteBbn | 10.37.33.100/24 | 00:0C:29:40:45:27 | ping |
| SiteRutgers | 10.37.33.101/24 | -- | ping, iperf |
ION VLAN 3729
| Site | IP | MAC (if known) | Purpose |
| SiteBbn | 10.37.29.100/24 | 00:0C:29:4A:B0:37 | ping |
| ProtoGENI Kansas City, MO | 10.37.29.101/24 | -- | ping |
ION VLAN 3730
| Site | IP | MAC (if known) | Purpose |
| SiteBbn | 10.37.30.100/24 | 00:0C:29:40:45:59 | ping |
| ProtoGENI Washington, D.C. | 10.37.30.101/24 | 00:1B:21:3A:D9:C9 | ping |
ION VLAN 670
| Site | IP | MAC (if known) | Purpose |
| SiteBbn | 10.6.70.100/24 | -- | ping |
| ProtoGENI.salt | 10.6.70.101/24 | -- | ping |
| ProtoGENI.salt | 10.6.70.102/24 | -- | ping |
ION VLAN 3734
| Site | IP | MAC (if known) | Purpose |
| SiteInternet2 ATLA | 10.37.34.222/24 | -- | ping |
| SiteNlr ATLA | -- | -- | ping |
| SiteRutgers | 10.37.34.144/24 | -- | ping |
ION VLAN 3738
| Site | IP | MAC (if known) | Purpose |
| SiteIndiana via Indiana Gigapop ATLA | 10.37.38.200/24 | -- | ping |
| SiteRutgers | -- | -- | ping |
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)
VLAN Translation
Note: ION translation is currently unavailable due to a hardware migration. It should be supported again in the near future. 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
Email us with questions and feedback on this page!
