Changes between Initial Version and Version 1 of SiteNlr

06/22/10 22:49:55 (11 years ago)



  • SiteNlr

    v1 v1  
     1= National Lambda Rail =
     4 *  -- homepage
     5 * -- NLR NOC
     7= !FrameNet =
     8From the [attachment:NationalLambdaRail_OverviewBrochure.pdf NLR Iverview Brochure]:
     9>ational LambdaRail (NLR) is a high-speed, fiber-optic network infrastructure covering 12,000 miles and 21 states across the U.S. Owned by the U.S. research and education community, NLR does not impose any restrictions on usage, as do commercial carriers, offering users total flexibility and control. With a total capacity of 1600 Gbps, production 40G implemented and planning underway for 100G, NLR is the cutting-edge network platform for a wide range of advanced research projects and public-private partnerships.
     10 * -- FrameNet overview
     11 *
     12 * -- NLR VLAN provisioning
     13 *  -- demo (username: `sherpademo`, password: `nationwide`)
     17== GENI FrameNet VLANs ==
     19|| Circuit ID || Owner Site || Other Sites ||
     23== Establishing an endpoint ==
     25=== membership information ===
     28Once this is complete, the NLR NOC ( will work with you to setup the appropriate accounts and access needed for your project.
     30=== Initial connections ===
     31From the [attachment:200909-IS-ION-HowTo.pdf ION HowTo]:
     32>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.
     35== Establishing an !FrameNet Sherpa Web Service Account ==
     36From the [ FrameNet documentation]:
     37>Those interested in using the Dynamic VLAN Service can contact NLR Experiments Support Services (ESS) at  The ESS will work with you to make sure DVS fits your needs, and shepherd the administrative and financial process.
     40== VLAN Provisioning within !FrameNet ==
     42This section outlines Provisioning within Sherpa. For the complete procedure of provisioning a VLAN between two sites see ConnectivityGuidelines.
     44Once you have an ION account you will be able to provision VLANs between site's endpoints using the [ ION VLAN provisioning webpage].
     46You cannot create VLANs to arbitrary endpoints locations, but only to those endpoints which you have permission to access. This is a manual process in which someone contacts the SHERPA account holders at both endpoints and gets permission. Once that permission step has been accomplished, the other endpoint will show up as a valid choice in the SHERPA "Z End" dialogue.
     48=== Required Topology Info ===
     49  * Your endpoint's name
     50  * Your partner site's endpoint's name
     51  * The VLAN ID that you and your partner site dedicated for this connection.
     53=== Creating the Circuit ===
     54  * Step 1 (Edit Vlan): it is fine to request a particular VLAN tag; the system will report quickly whether it is available.
     55  * Step 2 (A End): specify your campus's endpoint
     56  * Step 3 (Z End): specify your partner campus's endpoint.
     57  * Step 4 (Vlan Path): Unless you and your partner site have specific path requirements you can use the `Recommend Path` button.
     58  * Step 5 (Root Bridge): Choose the root bridge for the VLAN.
     61== VLAN Translation ==
     63If VLAN Translation is required NLR may be able to accomidate on acase by case basis.