Version 7 (modified by, 7 years ago) (diff)


I2 ION Aggregate


This aggregate supports the GENI Aggregate Provider Agreement (mm/dd/yyyy).

Aggregate Overview

Aggregate Manager URL
Aggregate Manager URN
Aggregate Manager Common Name i2ion
Aggregate Resources Internet2 ION Layer-2 network aggregate. It is the backbone network providing VLAN circuits to connect GENI aggregates across the nation.
Typical Experiments It is the transit network that allows edge aggregates to reach each other through stitching.
Sample RSpecs No sample RSpecs are available for this aggregate, experimenters do not specify RSpecs for this aggregate.
Aggregate Status Operational monitoring not widely available, restricted access to monitoring at GMOC
Slice Authorities Recognized GENI Portal (
Usage Policies A GENI Recommended Use Policy is available.
Layer 2 Connectivity Layer-2 VLAN connectivity for connectors at ATLA (Atlanta, GA), CHIC (Chicago, IL), CLEV (Cleveland, OH), HOUS (Houston, TX), KANS (Kansas City, MO), LOSA (Los Angeles, CA), NEWY32AOA (New York, NY), SALT (Salt Lake City, UT), SEAT (Seattle, WA), and WASH (McLean, VA)

<<Insert Site Diagram Here>> Make sure to note firewalls, if any, on both control (layer 3) and data paths.

Aggregate Management

Aggregate Operator Enter Site POC information, enter URL of organization. This can be a person or (preferably) a mailing list that reaches all operators at a site.
Resource Owner Enter person that is responsible for site rack overall. This entry may also be same as POC. This is typically the person who would took responsibility for operating and maintaining the rack on behalf of their site, and who would make the final decision on policy that affects the rack such as usage policies.
Technical POC Enter email for technical point of content
Developer Links Enter Links to any aggregate documentation pages