Changes between Version 65 and Version 66 of clusterdvlan


Ignore:
Timestamp:
12/07/09 12:41:54 (12 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • clusterdvlan

    v65 v66  
    102102 NLR FrameNet  [[BR]]
    103103 Internet2 GENI WAVE  [[BR]]
    104  NLR C-Wave  (not sure)[[BR]]
    105  Internet2  ION (DCN)  (not recommended, and shown in Fugre 1)
     104 NLR C-Wave [[BR]]
     105 Internet2  ION (DCN)  (not recommended, and not shown in figure)
    106106 
    107107Figure 1,  Backbone Network Options
     
    262262
    263263a)  Contacts:
    264  Joe Mambretti
    265  Jim Chen
    266  Fei Yeh
     264 Joe Mambretti  j-mambretti@northwestern.edu  [[BR]]
     265 Jim Chen  [[BR]]
     266 Fei Yeh   [[BR]]
    267267
    268268b)  iGENI to Backbone Networks and to International Testbeds  (Fig 3)
    269269
    270  VLANs from Starlight L2 crossconnect service in Chicago, to multiple backbone networks, including NLR FramewNet and Internet2 GENI WAVE and NLR C-Wave.
    271  See [[http://www.startap.net/starlight/NETWORKS/   Starlight]]
    272  See [[http://www.startap.net/starlight/ENGINEERING/SL-TransLight_5.06.pdf  Starlight GLIF GOLE May, 2006]]
    273 
     270 VLANs from Starlight L2 crossconnect service in Chicago, to multiple backbone networks, including NLR FramewNet and Internet2 GENI WAVE and NLR C-Wave.[[BR]]
     271 VLANs from Starlight L2 crossconnect service in Chicago, to multiple international testbeds, including Japan, Korea, South America and Europe. [[BR]]
     272 See [[http://www.startap.net/starlight/NETWORKS/   for more detail on Starlight facility]] [[BR]]
     273 See [[http://www.startap.net/starlight/ENGINEERING/SL-TransLight_5.06.pdf  for more detail on Starlight GLIF GOLE May, 2006]][[BR]]
     274 
     275 Figure 3-1,  iGENI Connections to Backbone Networks and to International Testbeds
     276 
     277 
     278 
     279 Figure 3-2,  StarLight GLIF GOLE Configuration
     280 
    274281 [[Image(SL-TransLight_5.06.jpg, 80%)]]
    275282
     
    277284=== 5.3.3.9 Combined Configuration ===
    278285
    279 See Fig 4
     286 The combined configuration of currently planned connections between Cluster D aggregates, including the iGENI (Starlight) crossconnect, to the backbone networks and to international testbeds, is shown in Figure 4.  [[BR]]
     287 
     288 
     289 Figure 4,  Connections from all Cluster D Aggregates to Backbone Networks and International Testbeds.
    280290
    281291
    282292== 5.3.4  First Phase:  Connect Cluster D Aggregates via NLR FrameNet Service ==
    283293
    284  See Fig 5
    285 
    286  Use NLR Framenet, since a mojority of Cluster D aggregates can connect with it.
    287 
    288  Implement pre-configured (or dynamic) connectivity via NLR and regionals
    289 
    290  Implement dynamic connections at each aggregate.
    291 
    292  Ordering of VLAN connections is likely to proceed from the backbone out to the endpoints:
    293   In a demo on 7/7/09, the ORCA/BEN project:
    294   Used Sherpa to pre-configure VLANs through NLR
    295   And then mapped VLAN tags near the endpoint nodes.
    296   See [[http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf Figures 6-2, 6-3 and 6-4]].
    297 
    298   In a suggested approach to connectivity specification at [[http://groups.geni.net/syseng/wiki/RspecConnectivity RSpec Connectivity]], it is suggested that:  “we give the backbone priority in selecting a network's VLAN ID and aggregates must map the ID within their local network by whatever means is most convenient for them. This way, the experimenter need only know what backbone the aggregate is connected to, and can design the network from there.”
    299 
    300  Dynamic setup would allow additional flexibility, with some complications.
     294 The first phase will be to connect Cluster D aggregates via the NLR FrameNet service, as shown in Figure 5.  [[BR]]
     295 
     296 Figure 5,  Connections Between Cluster D Aggregates via NLR FrameNet Service
     297 
     298 
     299
     300 Use NLR Framenet, since a majority of Cluster D aggregates can connect with it.[[BR]]
     301 Pre-configured paths via NLR FrameNet, regionals and campus networks.[[BR]]
     302 A "Cluster D Backbone Aggregate" created to setup and assign these paths to experimenters.  [[BR]]
     303 "Cluster D Backbone Aggregate" would have one or more pre-configured point-to-point paths between all (or perhaps a subset) of the Cluster D endpoint aggregates.  These would be assigned to an experimenter upon request. Each path would have a spcific identifier (e.g., port/VLAN tag) a the interface to the endpoint aggregate.[[BR]]
     304 Possible extension:  Use SHERPA, and possibly tools for regional networks,  to dynamically add paths when more are required.[[BR]]
     305
     306 Make connections at each endpoint aggregate between ednpoint of the backbone path and designated endpoint aggregatte component.  Typically, this would be done by mapping combinations of VLAN ports/tags in an Ethernet switch dedicated to the endpoint aggegate.[[BR]]
     307
     308 Thus, ordering of VLAN connections is likely to proceed from the backbone out to the endpoints, as in the demo on 7/7/09, by the ORCA/BEN project.[[BR]]
     309  Used Sherpa to pre-configure VLANs through NLR[[BR]]
     310  And then mapped VLAN tags near the endpoint nodes.[[BR]]
     311  See [[http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf Figures 6-2, 6-3 and 6-4]].[[BR]]
     312
     313 Similarly, the suggested approach to connectivity specification at [[http://groups.geni.net/syseng/wiki/RspecConnectivity RSpec Connectivity]], was:  “we give the backbone priority in selecting a network's VLAN ID and aggregates must map the ID within their local network by whatever means is most convenient for them. This way, the experimenter need only know what backbone the aggregate is connected to, and can design the network from there.”
     314
    301315
    302316