wiki:SiteNlr

Version 36 (modified by jwilliams@bbn.com, 9 years ago) (diff)

ndded wisconsin's (TBD) endpoint, removed Regionals from the Endpoint's table,

National LambdaRail

Known Issues

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

FrameNet

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.

GENI FrameNet VLANs

For a list of all active NLR VLANs (does not include reserved) see http://atlas.grnoc.iu.edu/nlr-vlan/index.html

VLAN ID Provisioning Site Other Sites Status
533 SiteBbn#VLAN533 Umass Amherst to StarLite NlrVlan:533 - Active
3701 SiteBbn#VLAN3701 RENCI NlrVlan:3701 - Inactive
3702 SiteBbn#VLAN3702 RENCI NlrVlan:3702 - Inactive
3703 Other NLR subscriber -- As of 6/3
3704 SiteBbn#VLAN3704 SiteStanford#VLAN3704 NlrVlan:3704 - Active
3705 SiteBbn#VLAN3705 SiteStanford, SiteIndiana, SiteNlr NlrVlan:3705 - Reserved, PROPOSED(6/30) waiting on Stanford's confirmation
3706 Other NLR subscriber -- As of 6/3
3707 SiteBbn#VLAN3707 SiteClemson, SiteStanford NlrVlan:3707 - Reserved, PROPOSED(6/30)
3708 Other NLR subscriber -- As of 6/3
3709 SiteBbn#VLAN3709 SiteGeorgiaTech, SiteStanford NlrVlan:3709 - Reserved, PROPOSED(6/30)
3710 SiteBbn#VLAN3710 SiteIndiana (tentative) NlrVlan:3710 - Reserved, PROPOSED (7/1)
3711 SiteBbn#VLAN3711 SiteClemson NlrVlan:3711 - Reserved, PROPOSED(6/30)
3712 SiteBbn#VLAN3712 SiteGeorgiaTech#VLAN3712 NlrVlan:3712 - Provisioning (07/07)

Endpoints

Site Endpoint
SiteBbn bost.layer2.nlr.net[Gi9/2]
SiteClemson atla.layer2.nlr.net[Po1]
SiteGeorgiaTech atla.layer2.nlr.net[Po1]
SiteStanford sunn.layer2.nlr.net[Gi9/1]
SiteIndiana N/A (direct provision)
SiteWisconsin cic.chic.ion.internet2.edu??? (TBD)

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.

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

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

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 Netowrk (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 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.

Multi-point VLANs

NLR currently supports creating multi-point VLANs through Sherpa.

PacketNet

Experiments

OpenFlow

NLR's OpenFlow deployment GENI page: OFNLR


Email us with questions and feedback on this page!