wiki:GENIRacksHome/InstageniRacks/Operators/Utah

Version 13 (modified by hdempsey@bbn.com, 5 years ago) (diff)

Add link to U of Utah campus drawing from Corbato's GEC18 presentation

University of Utah Operational Data

This page captures information for InstaGENI sites that is intended for Operators. The goal is to capture site contacts, connectivity, and VLANs.

Contacts

Site contact information for University of Utah InstaGENI.

Contact Name: Rob Ricci Contact Email: instageni-ops@flux.utah.edu


Data Plane

This section captures Data plane information for University of Utah detailing site topology, VLAN, Network Providers (I2/Regional) and network address information. Additional site which is not specified, but deemed important, can also be captured here.

Data plane connectivity diagram

Provide a diagram that captures device, ports and VLAN information at ingress and outgress for transport network. For non-OF connections provide device names and ports connected to transport network (I2/Regional) and VLAN used for those ports. Diagram below captures campus connections. All OpenFlow switches are HP ProCurve switches. Utah brought up a 100Gbps connection to Internet2 in December 2013 with the intention of switching all traffic to it eventually, but that has not happened yet.

UEN connection to Internet2 is currently 10Gbps at the UEN OpenFlow switch. The Utah Downtown Data Center InstaGENI rack also connects to this switch on a separate port to reach Internet2, as shown on the UtahDDC operator's page.

Layer 2 information

Provide layer 2 information for Circuits VLANs, plus network connection end-points, and purpose of VLAN.

*In the VLAN column, a single ID indicates that the port is an access port. A T followed by one or more IDs indicates that the port is a trunk (aka tagged) port with those VLAN IDs.

Rack Data Plane 5406

PortConnects ToVLAN Config*

Layer 3 information

If applicable, provide layer 3 information. If not applicable, replace with "none".

Experimental VLANs

Provide a table of Experimental VLAN detailing VLAN numbers, the endpoints, its purposes and whether VLAN is OF or non-OF.

VLAN IDOF Controlled?Purpose
256-1000 No Transport to utah-pg for stitching
1750 Yes Shared mesoscale transport
1755 Yes Exclusive mesoscale transport
1756 Yes Exclusive mesoscale transport
1757 Yes Exclusive mesoscale transport
1758 Yes Exclusive mesoscale transport
1759 Yes Exclusive mesoscale transport
1930 No fia-mobilityfirst transport
1931 No fia-ndn transport
1932 No fia-xia transport
1933 No reserved1 transport
1934 No wimax-multipoint transport

VLAN Translation Table

If applicable, provide any VLAN translation details for site.

Non-VLAN Connections

If applicable provide details for non VLAN connections. If not applicable, replace with "none".

Campus Connections

Document what network campus connection are in place for this rack.

This figure shows the campus network with several slices that are part of the UUtah CC-NIE project: GEC18 (10/2014) drawing of UUtah network slices in CC-NIE project

Public Internet

If applicable, provide details for public internet connectivity.


Control Plane

This section captures Control plane information for University of Utah detailing topology and network address information. Additional site which is not specified, but deemed important, can also be captured here.

Control plane connectivity diagram

Provide a diagram that captures device, port for the Control plane topology. Additional control network specific data which is not specified, but deemed important, can also be captured here.

Resource control subnets

Provide a list of subnets used in the rack and their intended use.

Firewall/IP tables

If firewall or IP tables are in use, insert who is responsible and any information deemed of importance about the setup.


Experiment Resources

Links to resource and network aggregates available for experimenters for University of Utah:

Attachments (2)

Download all attachments as: .zip