Changes between Version 64 and Version 65 of clusterdvlan


Ignore:
Timestamp:
12/07/09 12:03:08 (9 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • clusterdvlan

    v64 v65  
    100100
    101101The 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  
    106 Figure 1  Backbone Network Options
     102 NLR FrameNet  [[BR]]
     103 Internet2 GENI WAVE  [[BR]]
     104 NLR C-Wave  (not sure)[[BR]]
     105 Internet2  ION (DCN)  (not recommended, and shown in Fugre 1)
     106 
     107Figure 1,  Backbone Network Options
    107108
    108109
     
    138139
    139140f)  Backbone network
    140  Network: (I2 GENI wave, I2 DCN, NLR Framenet) [[BR]]
     141 Network: (I2 GENI wave, I2 DCN, NLR Framenet, NLR C-Wave) [[BR]]
    141142 Staff contact:[[BR]]
    142143 How are VLANs accepted?  (direct, tunnel)[[BR]]
     
    152153a)  Contact: Chris Heermann ckh@renci.org (RENCI) [[BR]]
    153154
    154 b)  RENCI, UNC-CH and Duke to NLR Configuration (Fig 2-1) 
     155b)  RENCI, UNC-CH and Duke to NLR Connections 
    155156
    156157 VLANs from RENCI BEN PoP, via fiber, to NLR FrameNet  [[BR]]
     
    158159 VLANs from Duke BEN MPoP, via Duke Campus OIT, to NLR FrameNet [[BR]]
    159160
    160 
     161 Figure 2-1,  RENCI, UNC-CH and Duke Connections to NLR FrameNet
    161162
    162163g)  References [[BR]]
     
    172173=== 5.3.3.3 BBN Aggregate ===
    173174
    174 a)  Contact: Josh Karlin  jkarlin@bbn.com
    175 
    176 b)  BBN to NLR Configuration (Fig 2-2)
     175a)  Contacts: Josh Karlin  jkarlin@bbn.com  and Chaos Golubitsky
     176
     177b)  BBN to NLR Connection
    177178
    178179 VLANs from BBN, via NOX, to NLR FrameNet [[BR]]
    179  Note:  An aggregate with a cluster of VMs is included at this site.[[BR]]
    180 
    181 
    182 
    183 d)
    184 Current  [[BR]]
    185  L3 service from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to NLR.[[BR]]
    186  VLANs from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to NLR.[[BR]]
    187  See http://groups.geni.net/syseng/wiki/OpsLabConnectivity [[BR]]
    188 Pending:  [[BR]]
    189  L3 service from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to Internet2[[BR]]
    190  VLANs from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to Internet2.[[BR]]
     180 An aggregate with a cluster of VMs is included at this site.[[BR]]
     181
     182 Figure 2-2,  BBN to NLR Connection
     183
     184d) Campus
     185 Current  [[BR]]
     186  L3 service from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to NLR.[[BR]]
     187  VLANs from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to NLR.[[BR]]
     188  See http://groups.geni.net/syseng/wiki/OpsLabConnectivity [[BR]]
     189 Pending:  [[BR]]
     190  L3 service from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to Internet2  When?  [[BR]]
     191  VLANs from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to Internet2.  When?  [[BR]]
    191192
    192193g)  References [[BR]]
     
    199200  Rich Tuthill  tuthill@oit.umass.edu
    200201
    201 b)  UMass to NLR Configuration (Fig 2-3)
    202 
    203  
     202b)  UMass Amherst to NLR Connection (Fig 2-3)
    204203 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]]
    205  Note:  Current connection runs from UMass to BBN, temporarily.
    206  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]]
     204 Current connection runs from UMass to BBN, temporarily.
     205 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]]
    207206 Note:  Cloud Control aggregate will require special connectivity arrangements to cloud resources.
    208207
     208 Figure 2-3,  UMass Amherst to NLR Connection
    209209
    210210c)  Campus network:
     
    225225 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]]
    226226
    227 g)  References:
    228  See [http://groups.geni.net/geni/wiki/DOME#Spiral1Connectivity DOME Spiral 1 Connectivity]
    229 
    230227
    231228=== 5.3.3.5 Kansei Aggregates ===
     
    235232 Hongwei Zhang, Wayne State University, hzhang@cs.wayne.edu, http://www.cs.wayne.edu/~hzhang/
    236233
    237 b)  Ohio State to NLR Configuration  (Fig 2-4)
     234b)  Ohio State to NLR Connection
    238235
    239236 VLANs from Ohio State, via ?, to NLR  [[BR]]
    240237 Note:  VLANs from Wayne State, via ?, to NLR not yet defined
    241238
     239 Figure 2-4,  Ohio State to NLR Connection
     240 
    242241=== 5.3.3.6 OKGems Aggregate ===
    243242
    244243a)  Contact:  Xiaolin (Andy) Li, Computer Science Department, Oklahoma State University (OSU) xiaolin@cs.okstate.edu
    245 
    246  Note:  VLANs from Oklahoma State, via ?, to NLR not yet defined
     244 VLANs from Oklahoma State, via ?, to NLR not yet defined
    247245
    248246=== 5.3.3.7 LEARN Regional Network and Connected Aggregates ===
     
    250248a)  Contact:  Deniz Gurkan University of Houston College of Technology dgurkan@uh.edu
    251249
    252 b)  LEARN to NLR configuration drawing  (Fig 2-5)
    253 
     250b)  LEARN to NLR Connection  (Fig 2-5)
    254251 VLANs from UH, Rice, TAMU and UT-Austin, via LEARN network, to NLR PoP in Houston
    255252 See [http://groups.geni.net/geni/attachment/ticket/267/GENI_MS2ab_LEARN_Nov16.pdf  ] for details
    256253
     254 Figure 2-5,  LEARN to NLR Connection
     255 
     256 
    257257f)  Note:  Other backbone network options are pending
    258258  Internet2 ION - IDC installation is in progress at UH, Rice, TAMU and UT-Austin