Changes between Version 4 and Version 5 of SiteInternet2

06/22/10 18:32:12 (12 years ago)



  • SiteInternet2

    v4 v5  
    77= ION =
     8From FIXMe_theattachment:[[BR]]
     9>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.
    811 webpages::
    912   *  -- ION homepage
    1417|| Circuit ID || Owner Site || Other Sites ||
    1621== Establishing an endpoint ==
    18 === establishing an ION account ===
     23=== Internet2 higher education members ====
     24(From FIXME_Attachhowto)
     25Researchers 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.
    20 == VLAN Provisioning ==
     27=== Initial connections ===
     28(From FIXME_theattachment)
     29The 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.
    22 See ConnectivityGuidelines for a complete listof steps necessary to provision an end to end connection over a backbone.
     31=== How can Internet2 members determine if they are ION-enabled? ===
     32)From FIXME_atachmewntFAQ )
     33Members should first verify whether their Connector has physically connected to the Ciena network that supports the ION service, either by asking their Connector or checking Internet2’s Connector status page at If the Connector is listed as “ION-enabled,” the member should speak with local network administrators and a Connector representative about how they may use the service.
    24 Once you have an ION account you will be able to provision VLANs between site's endpoints [ ION VLAN provisioning webpage].
    26 == required Topology Info ==
     36== Establishing an ION Web Service Account ==
     37The contact address for getting new ION accounts is:
     39== VLAN Provisioning within ION ==
     41This section outlines Provisioning within ION's web service, for the complete procedure of provisioning a VLAN between two sites see ConnectivityGuidelines.
     43Once you have an ION account you will be able to provision VLANs between site's endpoints using the [ ION VLAN provisioning webpage].
     45=== Required Topology Info ===
    2746  * Your endpoint's name
    2847  * Your VLAN to this endpoint to dedicate to connecting to the other site.
    3049  * The VLAN that your partner site is dedicating to connecting to your site.
     51=== Creating the Circuit ===
     52If 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:
     53 * "source" tab:
     54   * Description: put something meaningful and unique here, in case the first test fails, though the ION ID is also unique
     55   * Source: your campus's ION endpoint. It would be similar to
     56 * "destination" tab:
     57   * Destination: the other endpoint's ION name.  If you don't already know this you may be able to browse for a reasonable name
     58 * "time" tab: change these values to make the circuit good for the length of time you need; 1 hour isn't very useful
     59 * "bandwidth" tab: as appropriate though keep this as small as possible.
     60 * "vlan" tab:
     61   * Unclick "Same VLAN number on source and destination"
     62   * 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)
     63   * The destination VLAN should be whatever you agreed on with the remote site.  The tagging status is also whatever's appropriate for them (probably also tagged)
    3365== VLAN Translation ==
    35  You need to specify both your site's and your partner site's VLAN IDs, as outlined in [#VLANProvisioning VLAN Provisioning as ION will provide VLAN translation automatically. The two VLAN ID's do not need to be equal.
     67ION can do VLAN translation as mentioned in [#CreatingtheCircuit 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.