wiki:SiteNlr

Version 77 (modified by chsmall@grnoc.iu.edu, 9 years ago) (diff)

--

National LambdaRail

Contact

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. 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 current list FrameNet's active VLANs see http://atlas.grnoc.iu.edu/nlr-vlan/index.html. Note that this will not show reserved VLANs.

NLR VLAN DetailsStatus Participant Sites
NlrVlan:533 #VLAN533 UP SiteBbn, Umass Amherst (StarLite)
NlrVlan:546 #VLAN546 UP Umass Lowell
NlrVlan:3700 #VLAN3700 UP SiteStanford, SiteWisconsin
NlrVlan:3701 #VLAN3701 proposed SiteWashington, SiteStanford
NlrVlan:3702 #VLAN3702 UP SiteStanford, SiteIndiana
NlrVlan:3703 #VLAN3703 unavailable Other NLR subscriber
NlrVlan:3704 #VLAN3704 UP SiteBbn, SiteStanford
NlrVlan:3705 #VLAN3705 UP SiteNlr, SiteBbn, SiteStanford, SiteIndiana
NlrVlan:3706 #VLAN3706 unavailable Other NLR subscriber
NlrVlan:3707 #VLAN3707 UP SiteClemson, SiteStanford
NlrVlan:3708 #VLAN3708 unavailable Other NLR subscriber
NlrVlan:3709 #VLAN3709 UP SiteGeorgiaTech, SiteStanford
NlrVlan:3710 #VLAN3710 UP SiteBbn, SiteIndiana
NlrVlan:3711 #VLAN3711 UP SiteBbn, SiteClemson
NlrVlan:3712 #VLAN3712 UP SiteBbn, SiteGeorgiaTech
NlrVlan:3713 #VLAN3713 UP SiteBbn, SiteWisconsin
NlrVlan:3714 #VLAN3714 reserved SiteBbn, SiteWashington
NlrVlan:3715 #VLAN3715 reserved SiteNlr
NlrVlan:3716 #VLAN3716 reserved SiteNlr
-- -- -- --
NlrVlan:3722 #VLAN3722 reserved SiteBbn
NlrVlan:3723 #VLAN3723 unavailable Other NLR subscriber
NlrVlan:3724 #VLAN3724 reserved SiteBbn
NlrVlan:3725 #VLAN3725 reserved SiteBbn

FrameNet 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 chic.layer2.nlr.net[Gi9/1]
SiteWisconsin (TBD)

NLR's GENI VLANs

See SiteNlr/OpenFlowVlanNotes for information on these VLANs.

VLAN 546

Site IP MAC
(if known)
Purpose
Umass Lowell 10.5.46.99/24 00:0C:29:4A:B0:0F ping

VLAN 3700

Site IP MAC
(if known)
Purpose
SiteStanford 10.37.0.2/24 --- ping
SiteWisconsin 10.37.0.129/24 --- ping

VLAN 3702

Site IP MAC
(if known)
Purpose
SiteStanford 10.37.2.2/24 --- ping
SiteIndiana 10.37.2.101/24 --- ping

VLAN 3704

Site IP MAC
(if known)
Purpose
SiteBbn 10.37.4.100/24 0:0C:29:4A:B0:41 ping
SiteStanford 10.37.4.2/24 00:18:8B:F9:60:19 ping

VLAN 3705

This multi-point VLAN will interconnect all OpenFlow Campuses without using the OpenFlow Core Switches. See SiteNlr/OpenFlowVlanNotes#NLRmulti-pointVLAN for more info.

Site IP MAC
(if known)
Purpose
SiteBbn 10.37.5.100/24 00:0C:29:4A:B0:41 ping
SiteStanford 10.37.5.2/24 00:18:8B:F9:60:19 ping
SiteIndiana 10.37.5.49/24 00:16:B9:CF:FC:40 ping

VLAN 3707

Site IP MAC
(if known)
Purpose
SiteStanford 10.37.7.2/24 -- ping
SiteClemson 10.37.7.17/24 -- ping

VLAN 3709

Site IP MAC
(if known)
Purpose
SiteStanford 10.37.9.2/24 -- ping
SiteGeorgiaTech 10.37.9.3/24 -- ping

VLAN 3710

Site IP MAC
(if known)
Purpose
SiteBbn 10.37.10.100/24 00:0C:29:40:45:09 ping
SiteIndiana 10.37.10.101/24 00:16:B9:CF:FC:40 ping

VLAN 3711

Site IP MAC
(if known)
Purpose
SiteBbn 10.37.11.100/24 00:0C:29:4A:B0:05 ping
SiteClemson 10.37.11.101/24 00:22:64:CB:13:2D ping, iperf (TCP port 5001 (default), UDP port 5002), Ganglia

VLAN 3712

Site IP MAC
(if known)
Purpose
SiteBbn 10.37.12.100/24 00:0C:29:4A:B0:0F ping
SiteGeorgiaTech 10.37.12.101/24 00:E0:81:5E:E2:91 ping

VLAN 3713

Site IP MAC
(if known)
Purpose
SiteBbn 10.37.13.100/24 00:0C:29:4A:B0:4B ping
SiteWisconsin 10.37.13.129/24 00:26:b9:8b:c5:44 ping, Ganglia

VLAN 3715

NLR OpenFLow Core - North. This multi-point VLAN interconnects OpenFlow campuses. See SiteNlr/OpenFlowVlanNotes#NLROpenFlowCoreVLANs for more info.

Site IP MAC
(if known)
Purpose
SiteBbn 10.37.15.100/24 00:0C:29:40:45:13 ping
SiteStanford 10.37.15.2/24 -- ping
SiteWisconsin 10.37.15.129/24 -- ping
SiteIndiana 10.37.15.101/24 -- ping
SiteIndiana testpoint 10.37.15.102/24 -- ping
"SiteInternet2" ATLA 10.37.15.51/24 -- ping
SiteNLR ATLA 10.37.15.45/24 -- ping
SiteNLR CHIC 10.37.15.44/24 -- ping
SiteNLR DENV 10.37.15.42/24 -- ping
SiteNLR SEAT 10.37.15.41/24 -- ping
SiteNLR SUNN 10.37.15.41/24 -- ping

VLAN 3716

NLR OpenFLow Core - South. This multi-point VLAN interconnects OpenFlow campuses. See SiteNlr/OpenFlowVlanNotes#NLROpenFlowCoreVLANs for more info.

Site IP MAC
(if known)
Purpose
SiteBbn 10.37.16.100/24 00:0C:29:40:45:1D ping
SiteStanford 10.37.16.2/24 -- ping
SiteWisconsin 10.37.16.129/24 -- ping

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

FrameNet Traffic

From http://globalnoc.iu.edu/nlr/maps_documentation/nlr-framenet-documentation.html:

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

PacketNet

Experiments

OpenFlow

NLR's OpenFlow deployment GENI page: OFNLR


Email us with questions and feedback on this page!