Changes between Version 48 and Version 49 of NetworkCore


Ignore:
Timestamp:
02/24/14 17:05:10 (6 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NetworkCore

    v48 v49  
    33'''NOTE:  NLR is in the process of being shut down.  GENI has moved connections off of NLR, but we are in the process of updating documentation.'''
    44
    5 The initial Spiral 3 GENI network core is a set of OpenFlow-capable switches in NLR and Internet2.
     5The current GENI network core is a set of OpenFlow-capable switches in Internet2.
    66
    7 There are currently three standing backbone interconnect VLANs (3715, 3716, and 3717) carried on the ten switches in the core, which are located in the nine cities shown on the maps below. Two of the VLANs in each provider are topologically a broken ring (to help prevent accidental loops), with the two rings in each VLAN linked in Atlanta.  The third VLAN (3717) is a ring within each provider. The gap in each of the broken-ring VLANs is between two different links, to provide either a longer or shorter path through the core between two switches. The three VLANs are not interconnected in the core, and should not extend beyond the backbone providers into regionals or campuses.
     7There are currently three standing backbone interconnect VLANs (3715, 3716, and 3717) carried on the five switches in the core, which are located in the five cities shown on the maps below. Two of the VLANs are topologically a broken ring (to help prevent accidental loops).  The third VLAN (3717) is a ring. The gap in each of the broken-ring VLANs is between two different links, to provide either a longer or shorter path through the core between two switches. The three VLANs are not interconnected in the core, and should not extend beyond the backbone providers into regionals or campuses.
    88
    99= VLAN 3715 =
     
    2121
    2222= Testing / monitoring =
    23 
    24 We're in the process of setting up a process for testing the OpenFlow core from end to end, including out to campuses. VLAN 3715 has four endpoints, and VLAN 3716 has two, which we intend to connect to these campuses:
    25 || '''VLAN''' || '''OpenFlow Connector''' || '''Participant''' || '''Host IP''' ||
    26 || 3715       || WASH I2                  || Rutgers           || 10.37.15.145  ||
    27 || 3715       || NEWY I2                  || BBN               || 10.37.15.102  ||
    28 || 3715       || SEAT NLR                 || Washington        || 10.37.15.90   ||
    29 || 3715       || SUNN NLR                 || Stanford          || 10.37.15.3    ||
    30 || 3716       || HOUS I2                  || KSU               || 10.37.16.113  ||
    31 || 3716       || CHIC NLR                 || Indiana (Gigapop) || 10.37.16.49   ||
    32 
    33 [http://monitor.gpolab.bbn.com/connectivity/core.html The core network status page at BBN] shows whether test hosts at BBN and Stanford can ping the other test hosts right now.
    34 
    35 For a complete list of known hosts in the connectivity subnets of these VLANs see:
    36  * ConnectivityHome#net10.37.15.0
    37  * ConnectivityHome#net10.37.16.0
     23[http://monitor.gpolab.bbn.com/connectivity/core.html The core network status page at BBN] shows whether a test host at BBN can ping the other test hosts right now.
    3824
    3925= Backbone Integration =
     
    4430Note: Network Diagrams maintained by GMOC, historical revisions can be found here - http://gmoc.grnoc.iu.edu/gmoc/file-bin/geni-network-diagram.html
    4531
     32== VLAN Translation ==
     33The shared mesoscale VLAN in the core uses loopback cables for VLAN translation where needed.  Some of those VLANs are not experimenter controlled, but rather are used for isolated transport to a specific site.  On the Internet2 core switches, the [http://groups.geni.net/geni/wiki/Layer1Transport Layer1Transport] software is used to pass that traffic along at layer 1, similar to how a psuedowire would work.
    4634
    47 == OpenFlow Core entry-points ==
    48 Note, the OpenFlow Core Entry-points are available from the diagram above. The diagram is the authoritative source of information but is listed below for easier review.
    49 
    50 || '''Site'''      || '''backbone "exit port"''' || '''Openflow "entry port"''' ||
    51 || GeniSite/Washington  || NLR seat.layer2[Te3/1]     || NLR seat.of[p25]            ||
    52 || GeniSite/Stanford    || NLR sunn.layer2[Te3/4]     || NLR sunn.of[p25]            ||
    53 || GeniSite/GeorgiaTech || NLR atla.layer2[Te3/2]     || NLR atla.of[p25]            ||
    54 || GeniSite/Clemson     || NLR atla.layer2[Te3/2]     || NLR atla.of[p25]            ||
    55 || [wiki:GeniSite/BBN]         || NLR chic.layer2[Te3/4]     || NLR chic.of[p25]            ||
    56 || GeniSite/Wisconsin   || NLR chic.layer2[TE3/4]     || NLR chic.of[p25]            ||
    57 || GeniSite/Indiana     || N/A                        || NLR chic.of[p21]            ||
    58 ||                 ||                            ||                             ||
    59 || GeniSite/Rutgers     || I2 rtr.wash[ge-7/0/3]      || I2 of.wash[gi0/1]           ||
    60 || [wiki:GeniSite/BBN]         || I2 rtr.newy[ge-7/0/4]      || I2 of.newy[gi0/1]           ||
    61 
    62 == Cross Connect ==
    63 The "cross-connect" between I2 and NLR in ATLA connects via I2 OF Atla, Te0/25 facing NLR OF Atla, port 28.
    64 
    65 '''Note:''' atla.layer2.nlr.net[Te3/2] Is the port facing the NLR ATLA OpenFlow switch, in this sense, this port is the FrameNet endpoint.
    66 
    67 == VLAN Translation ==
    68 The shared mesoscale VLAN in the core uses loopback cables for VLAN translation where needed.  Some of those VLANs are not experimenter controlled, but rather are used for isolated transport to a specific site.  On the NLR and Internet2 core switch, the [http://groups.geni.net/geni/wiki/Layer1Transport Layer1Transport] software is used to pass that traffic along at layer 1, similar to how a psuedowire would work.
    69