Version 129 (modified by, 14 years ago) (diff)

Moved NLR FrameNet VLANs to ConnectivityHome

National LambdaRail

GENI connections using Internt2 can be found at: ConnectivityHome.


Submit issues or VLAN provisioning/translation requests through:

Known Issues

  • Sherpa currently cannot be used to provision a VLAN that uses a port-channel interface (e.g.[Po1]).

Report a Problem


From the NLR Interview 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.

Establishing an Endpoint

Membership Information

NLR does not require a site to be an NLR member to utilize a GENI VLAN; it is possible to share a member's endpoint (either a campus or a regional). If you need help identifying an NLR endpoint to support your GENI research effort please contact the GENI Project Office.

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

Sherpa Account

From the !FrameNet documentation:

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.

The process for requesting Sherpa access right now is fairly informal. Currently there are no rules/regulations/procedures outlined for requesting Sherpa access. For now, send a request to the globalnoc <>.

If your campus has their own dedicated NLR FrameNet port
You can directly ask NLR for Sherpa access to provision VLANs on that port.
If the campus connects through a regional and a shared FrameNet port
It would be up to the regional whether the regional chooses to grant access to the campus to do Sherpa provisioning on the FN port. You may need to request your Regional IT staff to provision FrameNet VLANs on your behalf.

VLAN Provisioning Within FrameNet using Sherpa

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

It is important to work with your Campus and Regional Network (as well as your partner Campus and regional network) to negotiate a common VLAN ID.

Once you (or your IT contact at your regional) have an Sherpa account you will be able to provision VLANs between site's endpoints using the !FrameNet VLAN provisioning webpage.

There only needs to be one organization with Sherpa access with permission to provision VLANs on both endpoints.

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

Multi-point VLANs

NLR currently supports creating multi-point VLANs through Sherpa.

FrameNet Traffic


Members should refrain from sending unnecessary broadcast packets to the NLR switch fabric. We ask that you make sure that your routing devices that are connected are configured to not forward broadcast packets. For example, on a Cisco, please insure "no ip directed broadcast" is configured on your interface that is connected to NLR. We will rate limit broadcast traffic to preserve the integrity of the network to a small percentage of the line rate of the interface.)




NLR's OpenFlow deployment GENI page: OFNLR

Email us with questions and feedback on this page!