wiki:SiteInternet2

Version 45 (modified by chsmall@grnoc.iu.edu, 14 years ago) (diff)

--

Internet 2

  1. Internet 2
      1. Contact
  2. ION
    1. Known Issues
    2. GENI ION VLANs
      1. ION VLAN 1
      2. ION VLAN 2
      3. ION VLAN 3
      4. ION VLAN 4
      5. ION VLAN 5
      6. ION VLAN 6
      7. ION VLAN 7
      8. ION VLAN 8
      9. ION VLAN 9
      10. ION VLAN 10
      11. ION VLAN 11
      12. ION VLAN 3734
      13. ION VLAN 3738
    3. Establishing an Endpoint
      1. Internet2 Higher-Education Members
      2. Initial Connections
      3. How Can Internet2 Members Determine if They Are ION-enabled?
    4. ION Web Service Account
    5. VLAN Provisioning within ION
      1. Required Topology Info
      2. Creating the Circuit
    6. VLAN Translation
  3. Experiments
    1. OpenFlow

Contact

Submit issues or VLAN provisioning/translation requests through:

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.

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.

GENI ION VLANs

The number assigned in this wiki is for linking purposes only and has no actual meaning.

Number Details StatusParticipant Sites
1 #IONVLAN1 down SiteBbn, Michigan
2 #IONVLAN2 down (deprecated) SiteBbn, SiteRutgers
3 #IONVLAN3 UP SiteBbn, ProtoGENI.salt (Salt Lake City, Utah)
4 #IONVLAN4 proposed SiteBbn, SiteWashington
5 #IONVLAN5 proposed SiteBbn, SiteWisconsin
6 #IONVLAN6 UP SiteBbn, SiteKansasState
7 #IONVLAN7 proposed SiteRutgers, SiteKansasState
8 #IONVLAN8 UP SiteBbn, SiteRutgers
9 #IONVLAN9 UP SiteBbn, ProtoGENI.kans(Kansas City, MO)
10 #IONVLAN10 UP SiteBbn, ProtoGENI.wash(Washington, D.C.)
11 #IONVLAN11 UP SiteBbn, ProtoGENI.salt(Washington, D.C.) for VIOLIN
3734 #IONVLAN3734 UP SiteRutgers, SiteInternet2
3738 #IONVLAN3738 proposed SiteRutgers, SiteIndiana

ION VLAN 1

ION VLAN 2

Site IP MAC
(if known) 		Purpose
SiteBbn 10.37.27.100/24 00:0C:29:4A:B0:23 ping
SiteRutgers 10.37.27.101/24 00:1b:21:32:b5:5c ping, iperf
MagPI (regional) 10.37.27.102/24 00:23:9c:19:0f:d8 ping

ION VLAN 3

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 4

ION VLAN 5

ION VLAN 6

Site IP MAC
(if known) 		Purpose
SiteBbn 10.37.32.100/24 00:0C:29:40:45:31 ping
SiteKansasState 10.37.32.101/24 00:11:85:de:68:35 ping, iperf

ION VLAN 7

ION VLAN 8

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 9

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 10

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 11

Site IP MAC
(if known) 		Purpose
SiteBbn 10.6.70.100/24 -- ping
ProtoGENI Washington, D.C. 10.6.70.101/24 -- ping
ProtoGENI Washington, D.C. 10.6.70.102/24 -- ping

ION VLAN 3734

Site IP MAC
(if known) 		Purpose
SiteInternet2 ATLA 10.37.34.60/24 -- ping
SiteNlr ATLA -- -- ping
SiteRutgers 10.37.34.144/24 -- ping

ION VLAN 3738

Site IP MAC
(if known) 		Purpose
SiteIndiana 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!