Virginia Tech 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 InstaGENI at Virginia Tech.
- Contact Name: Mark Gardner
- Contact Email: mkg at vt.edu
Eric Brown (brownej at vt.edu) is the network architect responsible for connections to the rack and the data center.
Mark is Network Research Manager in IT at Virginia Tech. He's also PI of the FitNet (FitGENI) project.
The rack is installaed in the VT datacenter in Blacksburg, VA.
Data Plane
This section captures Data plane information for Virginia Tech 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 should capture campus connections.
* NB. All switches not labelled with "OpenFlow" are non-OF.
Connections through Internet2 are made through an organization that serves several Virginia Universities. The organization is called Network Virginia (http://www.networkvirginia.net/), and the infrastructure group within it is MARIA (http://www.marialliance.net/). The regional is MREX (Mid Atlantic Research and Education Exchange). MREX was scheduled to have 100GE connectivity to Internet2 in 2015.
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 | Connects To | VLAN Config* |
B21 | AL2S ASHB at port et-3/0/0.0 | T 4001-4020 |
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 ID | OF Controlled? | Purpose |
4001-4015 | No | GENI Stitching in AL2S |
4016-4020 | Yes | OpenFlow experiments in AL2S |
VLAN Translation Table
If applicable, provide any VLAN translation details for site.
Non-VLAN Connections
NONE
Campus Connections
NONE
Public Internet
NOT APPLICABLE
Control Plane
This section captures Control plane information for University of Washington detailing topology and network address information. Additional site which is not specified, but deemed important, can also be captured here.
Details of control plane connectivity
- What is the upstream ISP?
- The rack is connected to the campus' Science DMZ which peers directly with I2 and PNWGP
- What is the identifier for the border router and port facing the ISP?
- uwrr-ads-1
- Ports:
ae0.627 - PNWGP Commodity ae0.628 PNWGP High Performance ae0.829 Inet2 peering ae0.2300 svlan carrying vlans 2301-2320 to the instageni rack xe-1/2/9 10G interface to instageni rack
- Is the rack directly connected to the border router?
- Yes
Resource control subnets
- IP: 198.82.156.0/26
- DOMAIN: instageni.arc.vt.edu
Firewall/IP tables
NONE
Experiment Resources
Links to resource and network aggregates available for experimenters for University of Washington:
Attachments (1)
- vtOperator.jpg (73.3 KB) - added by 9 years ago.
Download all attachments as: .zip