Changes between Version 57 and Version 58 of clusterdvlan

12/04/09 16:36:23 (12 years ago)



  • clusterdvlan

    v57 v58  
    3737 k)  The resulting  connectivity plan should support this roadmap for Cluster D VLAN capabilities:  [[  roadmap]]  [[BR]]
     40== 5.3.2  Backbone Connectivity Options ==
     43=== Internet2 ===
     45a)  See [[  Internet2]]
     47b)  L3 service
     48 Details?
     49 Reach?
     51c)  Pre-configured VLANs on GENI “wave”, between certain Internet2 Wave System nodes.  See [[  Internet2 WAVE]]
     52 This is the approach being used by ProtoGENI backbone. 
     53 See [[  ProtoGENI Backbone]]
     54 See [[   ProtoGENI Backbone Node]]
     55 Multi-point
     57d)  Direct connections to the Internet2 Wave System nodes. 
     58 This is the approach being used by ProtoGENI backbone nodes.
     59 See [[  ProtoGENI Backbone]]
     60 See [[   ProtoGENI Backbone Node]]
     61 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.
     63e)  Tunnel to Internet2 Wave System nodes. 
     64 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.
     66f)  Switched VLANs using Internet2 DCN service.
     67 The Internet2 DCN service provides switched VLANs, but there are two issues that suggest that it will not be utilized for GENI traffic.   
     68 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.
     69 Second, it is available in only a limited number of Internet2 PoPs, and these may be difficult to reach.
     70 Currently, ORCA plans to provide an interface into the Internet2 IDC by 2/1/10.
     73=== NLR ===
     75a)  See [[   NLR]]
     77b)  L3 service  See [[  PacketNet]]
     78 PacketNet is a barebones service providing high-speed access to other things which happen to be on PacketNet.
     79 Details?
     80 Reach?
     82c)  Switched (or pre-configured) VLANs using FrameNet service.  See [[  NLR FrameNet]]
     83 Pt-to-pt?   
     84 Multi-point?
     85 Setup using Sherpa service. 
     86 BEN has used Sherpa to pre-configure VLANs.  See [[  Figure 6-4]].
     87 ORCA plans to provide an interface into the Sherpa GCI by 2/1/10.
     88 FrameNet/SHERPA is used to create dedicated static VLANs between sites with NLR access.  NLR does *not* (afaik)
     89provide any sort of VLAN translation or tunnelling support, so you are entirely responsible for arriving at your NLR endpoint
     90with your VLANs intact, as it were.  This seems likely to cause problems for some sites, given NLR's relatively small number of
     91endpoints.  It has certainly caused some problems for us. 
     92 RENCI controls their access all the way to their NLR switch port, which gives them a lot more flexibility.  (And note that, since they can be flexible and do arbitrary VLAN translation on their own equipment, people who want to talk to them (like us), don't have to be as flexible.)
     94d)  VLANs via C-Wave service?
     95 NLR press release includes this is offering to GENI
     96 Details?
     97 How?