Changes between Version 63 and Version 64 of clusterdvlan


Ignore:
Timestamp:
12/07/09 11:49:59 (12 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • clusterdvlan

    v63 v64  
    66Cluster D System Engineer:  Harry Mussman  hmussman@bbn.com
    77
    8 Current version represents plan established at GEC-6 meeting on 11/17/09
     8Current version represents the plan established at the GEC-6 meeting on 11/17/09
    99
    1010
     
    4040== 5.3.2  Backbone Options ==
    4141
    42 The NLR and Internet2 backbone networks are options for carrying VLANs between GENI Cluster D aggregates.  See Figure 1.
    43 
    44 Figure 1.
     42The NLR and Internet2 backbone networks are the current options for carrying VLANs between GENI Cluster D aggregates. 
    4543
    4644=== 5.3.2.1 Internet2 ===
    4745
    48 a)  See [[http://www.internet2.edu/  Internet2]]
     46a)  See [[http://www.internet2.edu/  Internet2]]   
     47 Contact:  ?
    4948
    5049b)  L3 service
    51  Details?
    52  Reach?
    53 
    54 c)  Pre-configured VLANs on GENI “wave”, between certain Internet2 Wave System nodes.  See [[http://www.internet2.edu/waveco/  Internet2 WAVE]]
     50  Uses public IP addresses, but only connects to other endpoints who are connected to Internet2. 
     51  Details?
     52  Reach?
     53
     54c)  Pre-configured VLANs on GENI “wave”, between certain Internet2 Wave System nodes. See[[http://www.internet2.edu/waveco/  Internet2 WAVE]]
    5555 This is the approach being used by ProtoGENI backbone. 
    5656 See [[http://www.protogeni.net/trac/protogeni/wiki/Backbone  ProtoGENI Backbone]]
     
    6767 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.
    6868
    69 f)  Switched VLANs using Internet2 DCN service.
    70  The Internet2 DCN service provides switched VLANs, but there are two issues that suggest that it will not be utilized for GENI traffic.   
     69f)  Switched VLANs using Internet2 ION (DCN) service.
     70 The Internet2 (DCN) service provides switched VLANs, but there are two issues that suggest that it will not be utilized for GENI traffic.   
    7171 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.
    7272 Second, it is available in only a limited number of Internet2 PoPs, and these may be difficult to reach.
     
    7474
    7575
    76 === 5.3.3.2 NLR ===
     76=== 5.3.2.2 NLR ===
    7777
    7878a)  See [[http://www.nlr.net/   NLR]]
     
    8080
    8181b)  L3 service  See [[http://www.nlr.net/packetnet.php  PacketNet]]
    82  PacketNet is a barebones service providing high-speed access to other things which happen to be on PacketNet.
     82 PacketNet is a barebones service providing high-speed access to other endpoints which happen to be on PacketNet.
    8383 Details?
    8484 Reach?
    8585
    8686c)  Switched (or pre-configured) VLANs using FrameNet service.  See [[http://www.nlr.net/framenet.php  NLR FrameNet]]
    87  Pt-to-pt?   
    88  Multi-point?
    89  Setup using Sherpa service. 
    90  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]].
    91  ORCA plans to provide an interface into the Sherpa GCI by 2/1/10.
    92  FrameNet/SHERPA is used to create dedicated static VLANs between sites with NLR access.  NLR does *not* (afaik)
    93 provide any sort of VLAN translation or tunnelling support, so you are entirely responsible for arriving at your NLR endpoint
    94 with your VLANs intact, as it were.  This seems likely to cause problems for some sites, given NLR's relatively small number of
    95 endpoints.  It has certainly caused some problems for us. 
     87 Pt-to-pt.   Multi-point?  If not now, when?  [[BR]]
     88 Setup using Sherpa service.  FrameNet/SHERPA is used to create dedicated static VLANs between sites with NLR access.  Exactly what is interface to Sherpa? [[BR]]
     89 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]]  [[BR]]
     90 ORCA plans to provide an interface into the Sherpa GCI by 2/1/10 [[BR]]
     91 NLR does *not* provide any sort of VLAN translation or tunnelling support, so you are entirely responsible for arriving at your NLR endpoint with your VLANs intact, as it were.  This seems likely to cause problems for some sites, given NLR's relatively small number of endpoints.  It has certainly caused some problems for us.  [[BR]]
    9692 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.)
    9793
    98 d)  VLANs via C-Wave service?
     94d)  Switched (or pre-configured) VLANs via C-Wave service.
    9995 NLR press release includes this is offering to GENI
    10096 Details?
    10197 How?
    10298
    103 
     99=== 5.3.2.3 Combined Options ===
     100
     101The following bacbone network options are available for carrying VLANs between GENI endpoint aggregates:
     102 NLR FrameNet
     103 Internet2 GENI WAVE
     104 NLR C-Wave
     105 
     106Figure 1  Backbone Network Options
    104107
    105108