Version 2 (modified by, 14 years ago) (diff)


Page Outline?

GENI Cluster D Spiral 2 Connectivity Plan


The following goals have been identified for the GNEI Cluster D Spiral 2 connectivity plan:

a) Cluster D entities (aggregates and the clearinghouse) need reliable, high-bandwidth L3 (IP) and L2 (VLAN) connectivity between each other to meet their experimentation goals for Spiral 2.

b) L3 will be used to reach publically-available services via public IP addresses and /or DNS names.

c) L2 (VLAN) connectivity will be used to join aggregate (and possibly other) resources via pt-to-pt or multi-point VLANs.

d) Pt-to-pt or multi-point VLANs will be used between entities involved in an experiment, where each entity is assigned a unique private IP addresses for the duration of the experiment. This has proven to be a very useful and convenient way to group entities for an experiment, e.g., the OMF network arrangement.

e) Pt-to-pt or multi-point VLANs may be used between entities involved in an experiment, where each entity utilizes a L3 protocol that is not IP.

f) Two backbone network have donated resources to GENI for Spiral 2, and these will be utilized to provide reliable, high-bandwidth L3 and L2 connectivity: Internet2 and NLR. See and

g) Each Cluster D entity (aggregate or clearinghouse) must reach Internet2 and/or NLR to get L3 and L2 connectivity. It is expected that this will include connections through a campus network and a regional network to Internet2 or NLR (but not typically both).

h) It is important that all Cluster D entities have L3 and L2 connectivity with each other in Spiral 2; if not, then the combinations of joint experiment would be limited. This implies connectivity is needed between Internet2 and NLR, which is not currently supported.

i) It is important that the complexities of providing the connectivity be hidden from the experimenter, who should be able to request a L3 (IP) or L2 (VLAN) connection by dealing with primarily their own entity.

j) It should be possible to extend the Cluster D connectivity plan to include resources in the other GENI clusters, with the eventual goal of reliable, high-bandwidth L3 (IP) and L2 (VLAN) connectivity between all GENI entities.

k) The resulting connectivity plan should support this roadmap for Cluster D VLAN capabilities:

Connecting Cluster D Entities to Backbone 3.1 ORCA/BEN and IMF Aggregates

See , Fig 6-1 and 6-4.

VLANs from RENCI BEN PoP, via fiber, to NLR FrameNet

VLANs from UNC-CH BEN PoP, via BEN, via RENCI BEN PoP, to NLR FrameNet

VLANs from Duke BEN MPoP, via Duke Campus OIT, to NLR FrameNet

3.2 DOME , ViSE and Cloud-Control Aggregates Note: Cloud Control aggregate may require special connectivity arrangements to cloud resources. See Layer 3 Connectivity: IP access will be through UMass Amherst's campus network, using their public IP addresses. VLANs from 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? to Internet2? Or to both? Layer 2 Connectivity: In cooperation with OIT at UMass-Amherst we have provided a VLAN connection from our control plane server to an Internet2 point-of-presence in Boston. An MOU was agreed upon with the UMass Office of Information Technology (OIT) regarding connecting Internet2 to the DOME and ViSE servers, along with VLAN access. The OIT contact is Rick Tuthill, tuthill email at The agreements include: 1) CS shall order OIT-provisioned network jacks in appropriate locations in the Computer Science building using normal OIT processes. (completed) 2) OIT shall configure these jacks into a single VLAN that shall be extended over existing OIT-managed network infrastructure between the Computer Science building and the Northern Crossroads (NoX) Internet2 Gigapop located at 300 Bent St in Cambridge, MA. 3) OIT agrees to provide a single VLAN for “proof-of-concept” testing and initial GENI research activities. 4) The interconnection of the provided VLAN between the NoX termination point and other Internet2 locations remains strictly the province of the CS researchers and the GENI organization. 5) This service shall be provided by OIT at no charge to CS for the term of one year in the interest of OIT learning more about effectively supporting network-related research efforts on campus. In an email dated September 28th, 2009 Rick Tuthill of UMass-Amherst OIT updated us on the status of this connection, as follows: 6) The two existing ports at the CS building in room 218A and room 226 and all intermediary equipment are now configured to provide layer-2 VLAN transport from these networks jacks to the UMass/Northern Crossroads(NoX) handoff at 300 Bent St in Cambridge, MA. 7) The NoX folks are not doing anything with this research VLAN at this time. They need further guidance from GENI on exactly what they’re supposed to do with the VLAN. 8) 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. 3.3 Kansei Aggregate VLANs from Ohio State, via ?, to ? VLANs from Wayne State, via ?, to ?

3.4 OKGems Aggregate VLANs from Oklahoma State, via ?, to ?

3.5 iGENI (Starlight) Crossconnect

VLANs from Starlight L2 crossconnect service in Chicago, to multiple backbone networks, including NLR and Internet2. See and

3.6 LEARN Regional Network

VLANs from Univ of Houston and Rice University, via LEARN network, to ?

3.7 GENI Operations at BBN Technologies

Note: An aggregate with a cluster of VMs is included at this site. L3 service from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to NLR. VLANs from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to NLR. See

L3 service from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to Internet2 VLANs from BBN GENI ops lab in Cambridge (CamGENI), via Northern Crossroads (NoX), to Internet2.

Attachments (25)