275 | | |
276 | | |
277 | | == 5.3.3 Backbone Connectivity Options == |
278 | | |
279 | | |
280 | | === 5.3.3.1 Internet2 === |
281 | | |
282 | | a) See [[http://www.internet2.edu/ Internet2]] |
283 | | |
284 | | b) L3 service |
285 | | |
286 | | Details? |
287 | | Reach? |
288 | | |
289 | | c) Pre-configured VLANs on GENI “wave”, between certain Internet2 Wave System nodes. See [[http://www.internet2.edu/waveco/ Internet2 WAVE]] |
290 | | |
291 | | This is the approach being used by ProtoGENI backbone. |
292 | | |
293 | | See [[http://www.protogeni.net/trac/protogeni/wiki/Backbone ProtoGENI Backbone]] |
294 | | |
295 | | See [[http://www.protogeni.net/trac/protogeni/wiki/BackboneNode ProtoGENI Backbone Node]] |
296 | | |
297 | | Pt-to-pt? Multi-point? |
298 | | |
299 | | |
300 | | d) Direct connections to the Internet2 Wave System nodes. |
301 | | |
302 | | This is the approach being used by ProtoGENI backbone nodes. |
303 | | |
304 | | See [[http://www.protogeni.net/trac/protogeni/wiki/Backbone ProtoGENI Backbone]] |
305 | | |
306 | | See [[http://www.protogeni.net/trac/protogeni/wiki/BackboneNode ProtoGENI Backbone Node]] |
307 | | |
308 | | More details on this can be found at ? It states that the ProtoGENI switches (shown below in the IP table) are each attached to the GENI L2 wave but also to I2's Layer 3 network at 1Gb/s. |
309 | | |
310 | | e) Tunnel to Internet2 Wave System nodes. |
311 | | |
312 | | From ?: Those aggregates that cannot get on the wave but are attached to I2 might be able to configure static IP tunnels (such as Ethernet over GRE) to one of the ProtoGENI switches attached to I2's Layer 3 services. |
313 | | |
314 | | f) Switched VLANs using Internet2 DCN service. |
315 | | |
316 | | The Internet2 DCN service provides switched VLANs, but there are two issues that suggest that it will not be utilized for GENI traffic. |
317 | | |
318 | | First, its use has not been included in the package of services donated to GENI, and thus there may be a cost to the GENI aggregate now, or in the future. |
319 | | |
320 | | Second, it is available in only a limited number of Internet2 PoPs, and these may be difficult to reach. |
321 | | |
322 | | Currently, ORCA plans to provide an interface into the Internet2 IDC by 2/1/10. |
323 | | |
324 | | |
325 | | === 5.3.3.2 NLR === |
326 | | |
327 | | a) See [[http://www.nlr.net/ NLR]] |
328 | | |
329 | | b) L3 service See [[http://www.nlr.net/packetnet.php PacketNet]] |
330 | | |
331 | | PacketNet is a barebones service providing high-speed access to other things which happen to be on PacketNet. |
332 | | Details? |
333 | | Reach? |
334 | | |
335 | | c) Switched (or pre-configured) VLANs using FrameNet service. See [[http://www.nlr.net/framenet.php NLR FrameNet]] |
336 | | |
337 | | Pt-to-pt? |
338 | | Multi-point? |
339 | | |
340 | | Setup using Sherpa service. |
341 | | |
342 | | BEN has used Sherpa to pre-configure VLANs. See [[http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf Figure 6-4]]. |
343 | | |
344 | | ORCA plans to provide an interface into the Sherpa GCI by 2/1/10. |
345 | | |
346 | | FrameNet/SHERPA is used to create dedicated static |
347 | | VLANs between sites with NLR access. NLR does *not* (afaik) |
348 | | provide any sort of VLAN translation or tunnelling support, so |
349 | | you are entirely responsible for arriving at your NLR endpoint |
350 | | with your VLANs intact, as it were. This seems likely to cause |
351 | | problems for some sites, given NLR's relatively small number of |
352 | | endpoints. It has certainly caused some problems for us. RENCI |
353 | | controls their access all the way to their NLR switch port, which |
354 | | gives them a lot more flexibility. (And note that, since they |
355 | | can be flexible and do arbitrary VLAN translation on their own |
356 | | equipment, people who want to talk to them (like us), don't have |
357 | | to be as flexible.) |
358 | | |
359 | | d) VLANs via C-Wave service? |
360 | | |
361 | | Details? |
362 | | How? |
363 | | |
364 | | |
365 | | |
366 | | == 4. Configuration of VLAN Connections == |
| 275 | == 5.3.4 Configuration of VLAN Connections == |