National LambdaRail

• ​http://www.nlr.net/ -- homepage
• ​http://globalnoc.iu.edu/nlr/index.html -- NLR NOC

FrameNet

From the NLR Iverview Brochure:

National 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.

• ​http://www.nlr.net/framenet.php -- FrameNet overview
• ​http://globalnoc.iu.edu/nlr/maps_documentation/nlr-framenet-documentation.html
• ​https://sherpa.nlr.net/add/a_end.html -- NLR VLAN provisioning
• ​https://sherpademo.grnoc.iu.edu/index.html -- demo (username: sherpademo, password: nationwide)

GENI FrameNet VLANs

VLAN ID	Owner Site	Other Sites	Status
533	SiteBbn#VLAN533	Star Lite	​NlrVlan:533 - Active
3701	SiteBbn#VLAN3701	RENCI	​NlrVlan:3701 - Inactive
3702	SiteBbn#VLAN3702	RENCI	​NlrVlan:3702 - Inactive
3704	SiteBbn#VLAN3704	SiteStanford#VLAN3704	​NlrVlan:3704 - Proposed

Establishing an Endpoint

Membership Information

​http://www.nlr.net/members.php

Once this is complete, the NLR NOC ​<noc@nlr.net> will work with you to setup the appropriate accounts and access needed for your project.

Establishing an FrameNet Sherpa Web Service Account

From the ​!FrameNet documentation:

Those interested in using the Dynamic VLAN Service can contact NLR Experiments Support Services (ESS) at ​ess@nlr.net. The ESS will work with you to make sure DVS fits your needs, and shepherd the administrative and financial process.

VLAN Provisioning Within FrameNet

This section outlines Provisioning within Sherpa. For the complete procedure of provisioning a VLAN between two sites see ConnectivityGuidelines.

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

You 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.

Required Topology Info

• Your endpoint's name - will look like bost.layer2.nlr.net[Gi9/2]
• Your partner site's endpoint's name
• The VLAN ID that you and your partner site dedicated for this connection.

Creating the Circuit

• Step 1 (Edit Vlan): it is fine to request a particular VLAN tag; the system will report quickly whether it is available.
• Step 2 (A End): specify your campus's endpoint
• Step 3 (Z End): specify your partner campus's endpoint.
• Step 4 (Vlan Path): Unless you and your partner site have specific path requirements you can use the Recommend Path button.
• Step 5 (Root Bridge): Choose the root bridge for the VLAN.

VLAN Translation

If VLAN Translation is required NLR may be able to accommodate on a case by case basis.

---

Back to SiteIndex?

Email us with questions and feedback on this page!