wiki:GENIRacksHome/InstageniRacks/Operators/UtahDDC

Version 7 (modified by asydney@bbn.com, 11 years ago) (diff)

--

Utah Downtown Data Center 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 Utah DDC.


Data Plane

This section captures Data plane information for Utah Downtown Data Center 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 (NRL/I2/Regional) and VLAN used for those ports. Diagram should capture campus connections.

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

Port Name/NumberConnects To VLAN Config*
B22/46 UEN at port B22/46 T 1750, 1755-1759

Layer 3 information

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

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.

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 (1)

Download all attachments as: .zip