ITS > NLR Home > Network Admin. NLR FAQ
Network Administrator NLR FAQ
Technical instructions for University IT administrators on how to access and use NLR services.
1. Which of the NLR services are free for Penn State?
The initial provision of the "Routed IP" version of NLR's PacketNet (layer 3) service will be provided free for anyone within Penn State to use. In addition, the first two connections to Pittsburgh of the "National Exchange Fabric" version of NLR's "FrameNet" (layer 2) service are provided free for Penn State's use, as part of the initial NLR service activation. However, there will be fees associated with use of intermediate segments of the overall NLR national infrastructure and with far end connection points for this service, and for other forms of NLR services.
2. Do I have to do anything to use either of these free services?
Penn State is connecting to NLR in such a way that the layer 3 service will be useable in a manner similar to Internet2. It will be carried for the immediate future as part of the University's Integrated Backbone service, and available for use without you having to do anything to communicate with other institutions connected to NLR, which provide layer 3 NLR service within the institution.
3. What about layer 2 service?
Each layer 2 service is unique in its end-to-end construction. Because of that, many parties will be involved in a layer 2 service implementation. These will include NLR personnel (to endorse network use, and determine which network segments are involved) and staff at Penn State and distant institutions (to determine work necessary at a local level). The mechanism for requesting this form or service is still in its infancy. For more information on ordering layer 2 services send email to noc@nlr.net, with a copy to nlr@psu.edu.
4. Why would I want to use a FrameNet (layer 2) service instead of PacketNet (layer 3) service, and vice versa?
PacketNet service includes familiar functions (such as routing and management of Domain Name Service), as are normally associated with a national network. Packets are routed automatically and share available bandwidth with all other users on that network. FrameNet service includes none of those functions; it simply affords an Ethernet-based transport. In addition to the "National Exchange Fabric" version of NLR's FrameNet (layer 2) service, there are two other versions which are dedicated to purposes of those choosing to use them. The "Point-to-Point Ethernet" version simply extends a local connection to a distant location elsewhere, with the only application(s) being those used by those connected. It essentially mimics a device at Penn State connecting with another alongside of it, except that the latter is at another institution. No routing or functions such as DNS are involved with the FrameNet (layer 2) service. The "Multipoint Ethernet" version of NLR's FrameNet (layer 2) service differs from the "Point-to-Point" version by adding nodes of the type above, at other institutions, creating a multi-institutional "flat" network. Again, no routing or functions such as DNS are involved, but more than two nodes share the same virtual segment. All versions of NLR's FrameNet service employ dedicated single mode fiber at University Park, from the Telecommunications Building to the wall plate near the device to be connected. Cost of that fiber connection will be paid from central funds for initial connections to this service.
5. Is there anything I should know about changes that might be made to either of these layer 2 or layer 3 services in the future?
One area of uncertainty is what impact the additional load associated with NLR might have on both the local network connecting you to the Integrated Backbone, and upon the Integrated Backbone itself. As additional load is imposed upon the local network, upgrades to the local network electronics and/or the type of connection they have to the Integrated Backbone may be necessary to avoid deterioration of services. The Integrated Backbone itself may require architectural or equipment changes, dependent upon the degree of additional load resulting from NLR. Costs to address local networking needs would be borne by the individual department; those to address changes to the Integrated Backbone are funded centrally.
6. What if there is a disruption of service due to a problem with the fiber that NLR uses between State College and Pittsburgh?
Those from whom the fiber and associated physical facilities were obtained have been contracted to provide maintenance support and fiber repair on a multi-hour response basis, should that be required. The electronics used have a degree of redundancy built into them, and can be remotely managed and analyzed for certain problems. Since it is expected that those who use the initial NLR PacketNet (layer 3) service would also have connectivity via Internet2 and the commodity Internet, connections will automatically be routed to those networks at Penn State, should NLR connections fail. Note that, just because Penn State has set up internal routing this way doesn't mean it is done elsewhere.
7. Isn't extra fiber available?
A separate pair of fiber for each of the segments of the route between State College and Pittsburgh is available for Penn State's use, should that prove necessary. The cost to also replicate electronics and arrange backup such that automatic changeover could occur, however, was unaffordable, and deemed inconsistent with the objectives of NLR.
8. When can we expect further information on availability and cost of the other services described in the NLR literature?
Work continues by those overseeing NLR to define both. There is little more that we know, at this time; certain types of the other services presently defined, will have costs associated with them ...which reportedly will be based upon some criteria that includes the location and distance of the distant peer(s) a NLR user would work with, and the characteristics of the connection required, especially if the connection was not shared. As more information becomes available, it will be highlighted by ITS. That will include the process by which requests are to be made and approved by NLR for services.
9. What transmission speeds/bandwidths are used by NLR?
To explain this in useful terms requires some explanation of how the use of the fiber is "divided" among wavelengths. The electronics used will initially enable use of 4 "lambdas" (wavelengths) of light, and can later be expanded if necessary to handle 28 more. Each of the 4 lambdas initially used will provide 10 Gigabits of capacity.
The 10 Gigabits of capacity of one of the lambdas will be divided into a number of virtual local area networks (VLANs). The first VLAN will be used to carry Internet2 traffic being moved to it from another, separate circuit that presently carries both Internet2 and commodity Internet traffic between State College and Pittsburgh. While this traffic is unrelated to NLR per se, the use of a small portion of the fiber's capacity for Internet2, while we retain the circuit that will still support commodity Internet traffic, affords additional capacity for both of those types of network connections, and gains the advantage of each of them having an alternate path available to them, in case of a problem on either the fiber route, or the circuit route, between State College and Pittsburgh. This adds a degree of reliability to both of those services which we did not have before, without detracting from current service levels.
The second and third VLANs on the first lambda are expected to be used to support the initial FrameNet (layer 2) services, in the form of 1 Gigabit Ethernet connections.
To use these Ethernet connections, facilities separate from the current Integrated Backbone would have to be extended to the user's location at UP, and similar facilities made available at distant institutions where connections were desired to peers.
The remaining VLANs on the first lambda would be available for interconnection at Pittsburgh, although there would be a fee to be able to connect them to NLR.
The second 10G lambda will be used to support the initial PacketNet (layer 3) service. This 10G Ethernet will terminate on the Integrated Backbone's Border Router in the Telecommunications Building, where routing decisions for packets destined for NLR, Internet2 or the commodity Internet are made, based on destination address.
The remaining 2 lambdas initially available likewise remain available to accommodate those requiring other types of NLR services, with costs associated with their use remaining to be defined by NLR, but including those costs as well as costs for fiber or electronic installations needed to extend the connection from the Telecommunications Building, to the end user's location at University Park.
Note that, even though those at campuses other than UP will not have the same degree of performance available as those at UP, all who are connected to Penn State's Integrated Backbone will have access to NLR's "Routed IP" (layer 3) service. Although the other types of NLR connections can only be provided at UP, those at non-UP campuses having peer relationships with the "Routed IP" version of NLR's "PacketNet" (layer 3) service will have similar ability to use NLR, and will traverse the same NLR connection from State College to Pittsburgh that UP users of that version of that service use.