Changes between Version 64 and Version 65 of clusterdvlan

Timestamp:

12/07/09 12:03:08 (15 years ago)

Author:

hmussman@bbn.com

Comment:

--

clusterdvlan

@@ -100 +100 @@
 
 The following bacbone network options are available for carrying VLANs between GENI endpoint aggregates:
- NLR FrameNet
- Internet2 GENI WAVE
- NLR C-Wave
- 
-Figure 1  Backbone Network Options
+ NLR FrameNet  [[BR]]
+ Internet2 GENI WAVE  [[BR]]
+ NLR C-Wave  (not sure)[[BR]]
+ Internet2  ION (DCN)  (not recommended, and shown in Fugre 1)
+ 
+Figure 1,  Backbone Network Options
 
 
@@ -138 +139 @@
 
 f)  Backbone network
- Network: (I2 GENI wave, I2 DCN, NLR Framenet) [[BR]]
+ Network: (I2 GENI wave, I2 DCN, NLR Framenet, NLR C-Wave) [[BR]]
  Staff contact:[[BR]]
  How are VLANs accepted?  (direct, tunnel)[[BR]]
@@ -152 +153 @@
 a)  Contact: Chris Heermann ckh@renci.org (RENCI) [[BR]]
 
-b)  RENCI, UNC-CH and Duke to NLR Configuration (Fig 2-1)  
+b)  RENCI, UNC-CH and Duke to NLR Connections  
 
  VLANs from RENCI BEN PoP, via fiber, to NLR FrameNet  [[BR]]
@@ -158 +159 @@
  VLANs from Duke BEN MPoP, via Duke Campus OIT, to NLR FrameNet [[BR]]
 
-
+ Figure 2-1,  RENCI, UNC-CH and Duke Connections to NLR FrameNet
 
 g)  References [[BR]]
@@ -172 +173 @@
 === 5.3.3.3 BBN Aggregate ===
 
-a)  Contact: Josh Karlin  jkarlin@bbn.com
-
-b)  BBN to NLR Configuration (Fig 2-2)
+a)  Contacts: Josh Karlin  jkarlin@bbn.com  and Chaos Golubitsky
+
+b)  BBN to NLR Connection
 
  VLANs from BBN, via NOX, to NLR FrameNet [[BR]]
- Note:  An aggregate with a cluster of VMs is included at this site.[[BR]]
-
-
-
-d)  
-Current  [[BR]]
- L3 service from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to NLR.[[BR]]
- VLANs from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to NLR.[[BR]]
- See http://groups.geni.net/syseng/wiki/OpsLabConnectivity [[BR]]
-Pending:  [[BR]]
- L3 service from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to Internet2[[BR]]
- VLANs from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to Internet2.[[BR]]
+ An aggregate with a cluster of VMs is included at this site.[[BR]]
+
+ Figure 2-2,  BBN to NLR Connection
+
+d) Campus 
+ Current  [[BR]]
+  L3 service from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to NLR.[[BR]]
+  VLANs from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to NLR.[[BR]]
+  See http://groups.geni.net/syseng/wiki/OpsLabConnectivity [[BR]]
+ Pending:  [[BR]]
+  L3 service from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to Internet2  When?  [[BR]]
+  VLANs from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to Internet2.  When?  [[BR]]
 
 g)  References [[BR]]
@@ -199 +200 @@
   Rich Tuthill  tuthill@oit.umass.edu
 
-b)  UMass to NLR Configuration (Fig 2-3)
-
-  
+b)  UMass Amherst to NLR Connection (Fig 2-3)
  VLANs from control plane server geni.cs.umass.edu  in UMass Amherst CS building, via UMass Amherst campus OIT, via Northern Crossroads (NoX), via handoff located at 300 Bent St in Cambridge, MA, to NLR.  [[BR]]
- Note:  Current connection runs from UMass to BBN, temporarily.
- Note:  Per Kathy Benninger, staff engineer for NLR, benninger@psc.edu, on 11/17/09:  UMass should be able to connect to NLR for GENI per GENI agreement, even though htey are not members of NLR.[[BR]]
+ Current connection runs from UMass to BBN, temporarily.
+ Per Kathy Benninger, staff engineer for NLR, benninger@psc.edu, on 11/17/09:  UMass should be able to connect to NLR for GENI per GENI agreement, even though they are not members of NLR.[[BR]]
  Note:  Cloud Control aggregate will require special connectivity arrangements to cloud resources.
 
+ Figure 2-3,  UMass Amherst to NLR Connection
 
 c)  Campus network:
@@ -225 +225 @@
  3) Also, once IP addressing is clarified for this VLAN, we’ll need to configure some OIT network equipment to allow the selected address range(s) to pass through.  [[BR]]
 
-g)  References:
- See [http://groups.geni.net/geni/wiki/DOME#Spiral1Connectivity DOME Spiral 1 Connectivity]
-
 
 === 5.3.3.5 Kansei Aggregates ===
@@ -235 +232 @@
  Hongwei Zhang, Wayne State University, hzhang@cs.wayne.edu, http://www.cs.wayne.edu/~hzhang/ 
 
-b)  Ohio State to NLR Configuration  (Fig 2-4)
+b)  Ohio State to NLR Connection 
 
  VLANs from Ohio State, via ?, to NLR  [[BR]]
  Note:  VLANs from Wayne State, via ?, to NLR not yet defined
 
+ Figure 2-4,  Ohio State to NLR Connection
+ 
 === 5.3.3.6 OKGems Aggregate ===
 
 a)  Contact:  Xiaolin (Andy) Li, Computer Science Department, Oklahoma State University (OSU) xiaolin@cs.okstate.edu
-
- Note:  VLANs from Oklahoma State, via ?, to NLR not yet defined
+ VLANs from Oklahoma State, via ?, to NLR not yet defined
 
 === 5.3.3.7 LEARN Regional Network and Connected Aggregates ===
@@ -250 +248 @@
 a)  Contact:  Deniz Gurkan University of Houston College of Technology dgurkan@uh.edu
 
-b)  LEARN to NLR configuration drawing  (Fig 2-5)
-
+b)  LEARN to NLR Connection  (Fig 2-5)
  VLANs from UH, Rice, TAMU and UT-Austin, via LEARN network, to NLR PoP in Houston
  See [http://groups.geni.net/geni/attachment/ticket/267/GENI_MS2ab_LEARN_Nov16.pdf  ] for details
 
+ Figure 2-5,  LEARN to NLR Connection
+ 
+ 
 f)  Note:  Other backbone network options are pending
   Internet2 ION - IDC installation is in progress at UH, Rice, TAMU and UT-Austin