NOTE: This information is subject to change, but is actively maintained. Please email us with updates and corrections.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.

Reference Material

How-tos, background, and recommendations to help you set up GENI connections and experiments.

ConnectivityOverview - Introduction. A high-level overview of what site connectivity looks like Start here if you are new to connectivity in GENI.

GENI Layer-2 Connectivity

The OpenFlow Core consists of interconnected OpenFlow-enabled switches on the Internet2 and National LambdaRail networks. To reach these VLANs, a campus typically uses VLANs through either the National LambdaRail or Internet2 layer-2 services. The OpenFlow Core deployment's topology and configuration is documented on the NetworkCore wikipage.

Internet2 Ingress point

VLAN ID table

Note: the "reservedvlan2" VLAN has had it's name changed to "wimax-multipoint"

fia-mobilityfirst

fia-ndn

fia-xia

reservedvlan1

wimax-multipoint

Utah/UEN

1930

1931

1932

1933

1934

Wisconsin/CIC

925

926

927

928

929

GPO/NoX

3701

3702

3703

3704

3705

NYU and NYSERNet

4083

4084

4085

4086

4087

Rutgers/MAGPI

3701

3702

3703

3704

3705

Illinois/ICCN

4083

4084

4085

4086

4087

AL2S

4083

4084

4085

4086

4087

Implementation notes - ION Glue circuit numbers

As of 10/16/2013:

These multipoint VLANs are implemented using multipoint features of AL2S. Non-AL2S endpoints (all but NYU above) use an ION VLAN (with translation to the AL2S VLAN number) to get between the endpoint to an ION-AL2S peering point. AL2S multipoint implementation is a broadcast -- a packet in on one port is broadcast to all others. For reference, the ION GRNs (essentially circuit IDs) and AL2S peering interfaces are in the table below. ION GRNs are abbreviated, 44331 is "ion.internet2.edu-44331".

NYU is connected via an NYU GENI rack to the New York GENI openflow switch; that switch is directly connected to AL2S (port 15/7).

As of 11/26/2013:
Added fia-ndn and fia-xia to fia-mobilityfirst. Last two are still unimplemented.

As of 04/11/2014:
Added wimax-multipoint to WiMAX sites.

All the glue ION circuits are set to expire 10/4/2015 23:59.

AL2S port

connected router port

fia-mobilityfirst

fia-ndn

fia-xia

reservedvlan1

wimax-multipoint

Utah/UEN

salt e15/1

xe-0/1/1

44341

51711

51721

n/a

Wisconsin/CIC

chic e3/1

et-10/0/0

51671

51691

51701

84401

GPO/NoX

newy e3/2

et-5/0/0

44331

51731

51741

84391

NYU and NYSERNet

newy e15/7

(is GENI OF 0/26)

n/a

n/a

n/a

n/a

n/a

Illinois/ICCN

star e7/2

n/a

n/a

n/a

n/a

n/a

n/a

Rutgers/MAGPI

wash e5/2

et-9/0/0

44351

51751

51761

84381

Regional VLANs

Regional VLAN Interconnections Table

Connectivity IP networks

Site's IP Ranges

For initial Connectivity testing, a typical nomenclature is to use a 10.X.X.0/24 net with a VLAN ID encoded into the IP address. To save time allocating IP addresses the following range-by-subnet scheme can be used for initial connectivity and "path-finding" experiments and configurations. This is particularly useful for multi-site connections, such as the OpenFlow Core VLANs.

Note that these IP addresses are allocated in blocks of /28 for consistency, this is not a subnet. All hosts in the /24 net should be able to ping one another by default. For example, a host at Clemson (10.37.5.17) should be able to ping a host at Washington (10.37.5.81).

This specific IP network (which corresponds to the VLAN) is meant for monitoring and testing of the connection, though host addresses within this IP network may be used in "small" experiments. Other IP networks following the same nomenclature maybe also be used on a given VLAN. Specific experiments may also designate other addition IP networks on the VLAN for specific use. This scheme lays the groundwork for initial connectivity only, it is expected other IP networks (as well as non-IP networks) will be devised in the future.

Campuses may assign other sites IPs from their range. This range-by-subnet scheme also allows for campuses to subnet the IP addresses not used for connectivity monitoring for additional traffic isolation.