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

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	BBN (later: KSU)	10.37.16.102
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:

• ConnectivityHome#net10.37.15.0
• ConnectivityHome#net10.37.16.0

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

KSU can't easily reach the I2 endpoint in Houston yet, so we're planning to use VLAN translation to link a host in the GPO lab at BBN to that endpoint, for now.