Changes between Version 65 and Version 66 of clusterdvlan

Timestamp:

12/07/09 12:41:54 (14 years ago)

Author:

hmussman@bbn.com

Comment:

--

clusterdvlan

@@ -102 +102 @@
  NLR FrameNet  [[BR]]
  Internet2 GENI WAVE  [[BR]]
- NLR C-Wave  (not sure)[[BR]]
- Internet2  ION (DCN)  (not recommended, and shown in Fugre 1)
+ NLR C-Wave [[BR]]
+ Internet2  ION (DCN)  (not recommended, and not shown in figure)
  
 Figure 1,  Backbone Network Options
@@ -262 +262 @@
 
 a)  Contacts:
- Joe Mambretti
- Jim Chen
- Fei Yeh
+ Joe Mambretti  j-mambretti@northwestern.edu  [[BR]]
+ Jim Chen  [[BR]]
+ Fei Yeh   [[BR]]
 
 b)  iGENI to Backbone Networks and to International Testbeds  (Fig 3)
 
- VLANs from Starlight L2 crossconnect service in Chicago, to multiple backbone networks, including NLR FramewNet and Internet2 GENI WAVE and NLR C-Wave.
- See [[http://www.startap.net/starlight/NETWORKS/   Starlight]]
- See [[http://www.startap.net/starlight/ENGINEERING/SL-TransLight_5.06.pdf  Starlight GLIF GOLE May, 2006]]
-
+ VLANs from Starlight L2 crossconnect service in Chicago, to multiple backbone networks, including NLR FramewNet and Internet2 GENI WAVE and NLR C-Wave.[[BR]]
+ VLANs from Starlight L2 crossconnect service in Chicago, to multiple international testbeds, including Japan, Korea, South America and Europe. [[BR]]
+ See [[http://www.startap.net/starlight/NETWORKS/   for more detail on Starlight facility]] [[BR]]
+ See [[http://www.startap.net/starlight/ENGINEERING/SL-TransLight_5.06.pdf  for more detail on Starlight GLIF GOLE May, 2006]][[BR]]
+ 
+ Figure 3-1,  iGENI Connections to Backbone Networks and to International Testbeds
+ 
+ 
+ 
+ Figure 3-2,  StarLight GLIF GOLE Configuration
+ 
  [[Image(SL-TransLight_5.06.jpg, 80%)]] 
 
@@ -277 +284 @@
 === 5.3.3.9 Combined Configuration ===
 
-See Fig 4
+ 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]]
+ 
+ 
+ Figure 4,  Connections from all Cluster D Aggregates to Backbone Networks and International Testbeds. 
 
 
 == 5.3.4  First Phase:  Connect Cluster D Aggregates via NLR FrameNet Service ==
 
- See Fig 5
-
- Use NLR Framenet, since a mojority of Cluster D aggregates can connect with it.
-
- Implement pre-configured (or dynamic) connectivity via NLR and regionals
-
- Implement dynamic connections at each aggregate.
-
- Ordering of VLAN connections is likely to proceed from the backbone out to the endpoints:
-  In a demo on 7/7/09, the ORCA/BEN project:
-  Used Sherpa to pre-configure VLANs through NLR
-  And then mapped VLAN tags near the endpoint nodes.
-  See [[http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf Figures 6-2, 6-3 and 6-4]].
-
-  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.”
-
- Dynamic setup would allow additional flexibility, with some complications.
+ The first phase will be to connect Cluster D aggregates via the NLR FrameNet service, as shown in Figure 5.  [[BR]]
+ 
+ Figure 5,  Connections Between Cluster D Aggregates via NLR FrameNet Service
+ 
+ 
+
+ Use NLR Framenet, since a majority of Cluster D aggregates can connect with it.[[BR]]
+ Pre-configured paths via NLR FrameNet, regionals and campus networks.[[BR]]
+ A "Cluster D Backbone Aggregate" created to setup and assign these paths to experimenters.  [[BR]]
+ "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]]
+ Possible extension:  Use SHERPA, and possibly tools for regional networks,  to dynamically add paths when more are required.[[BR]]
+
+ 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]]
+
+ 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]]
+  Used Sherpa to pre-configure VLANs through NLR[[BR]]
+  And then mapped VLAN tags near the endpoint nodes.[[BR]]
+  See [[http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf Figures 6-2, 6-3 and 6-4]].[[BR]]
+
+ 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.”
+