wiki:NetworkCore

Version 36 (modified by eurumbae@indiana.edu, 7 years ago) (diff)

--

The initial Spiral 3 GENI network core is a set of OpenFlow-capable switches in NLR and Internet2.

There are currently two standing VLANs (3715 and 3716) carried on the ten switches in the core, which are located in the nine cities shown on the maps below. Each VLAN in each provider is topologically a broken ring (to help prevent accidental loops), with the two rings in each VLAN linked in Atlanta. The gap in each VLAN is between two different links, to provide either a longer or shorter path through the core between two switches. The two VLANs are not interconnected in the core, and should not be interconnected in regionals or at GENI sites either. Sites may connect to both VLANs as long as the site keeps them separated at layer 2.

VLAN 3715

VLAN 3716

VLAN 3717

Testing / monitoring

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:

VLAN OpenFlow Connector Participant Host IP
3715 WASH I2 Rutgers 10.37.15.145
3715 NEWY I2 BBN 10.37.15.102
3715 SEAT NLR Washington 10.37.15.90
3715 SUNN NLR Stanford 10.37.15.3
3716 HOUS I2 KSU 10.37.16.113
3716 CHIC NLR Indiana (Gigapop) 10.37.16.49

The core network status page at BBN shows whether test hosts at BBN and Stanford can ping the other test hosts right now.

For a complete list of known hosts in the connectivity subnets of these VLANs see:

Backbone Integration

Click the picture below for the full-sized image.

http://gmoc.grnoc.iu.edu/gmoc/file-bin/geni-network-diagram/of-int-bb-14-dec-2012.png

Note: Network Diagrams maintained by GMOC, historical revisions can be found here - http://gmoc.grnoc.iu.edu/gmoc/file-bin/geni-network-diagram.html

OpenFlow Core entry-points

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.

Site backbone "exit port" Openflow "entry port"
SiteWashington NLR seat.layer2[Te3/1] NLR seat.of[p25]
SiteStanford NLR sunn.layer2[Te3/4] NLR sunn.of[p25]
SiteGeorgiaTech NLR atla.layer2[Te3/2] NLR atla.of[p25]
SiteClemson NLR atla.layer2[Te3/2] NLR atla.of[p25]
SiteBbn NLR chic.layer2[Te3/4] NLR chic.of[p25]
SiteWisconsin NLR chic.layer2[TE3/4] NLR chic.of[p25]
SiteIndiana N/A NLR chic.of[p21]
SiteRutgers I2 rtr.wash[ge-7/0/3] I2 of.wash[gi0/1]
SiteBbn I2 rtr.newy[ge-7/0/4] I2 of.newy[gi0/1]

Core VLAN translation

Clemson

Clemson's VLANs are translated into the native OpenFlow Core VLANs using access ports on the Atlanta OpenFlow Switch. This is done to allow Georgia Tech to also reach the core using the shared Atlanta FrameNet switch. Georgia tech uses the native OpenFlow Core VLAN IDs.

Port Type Name
17    100/1000T Clemson 3798 -> OF 3715
18     100/1000T Clemson 3799 -> OF 3716
19    100/1000T OF 3715 -> Clemson 3798
20     100/1000T OF 3716 -> Clemson 3799

Cross Connect

The "cross-connect" between I2 and NLR in ATLA connects via I2 OF Atla, Te0/25 facing NLR OF Atla, port 28.

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.

Attachments (17)