| 1 | [[PageOutline]] |
| 2 | |
| 3 | = Virginia Tech Operational Data = |
| 4 | |
| 5 | This page captures information for InstaGENI sites that is intended for Operators. The goal is to capture site contacts, connectivity, and VLANs. |
| 6 | |
| 7 | == Contacts == |
| 8 | |
| 9 | Site contact information for InstaGENI uwashington. |
| 10 | * Contact Name: Mark Gardner |
| 11 | * Contact Email: mkg@vt.edu |
| 12 | |
| 13 | ----- |
| 14 | == Data Plane == |
| 15 | |
| 16 | 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. |
| 17 | |
| 18 | === Data plane connectivity diagram === |
| 19 | |
| 20 | 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. |
| 21 | |
| 22 | [[Image(vtOperator.jpg)]] |
| 23 | |
| 24 | ''' * NB. All switches not labelled with "OpenFlow" are non-OF.''' |
| 25 | |
| 26 | |
| 27 | === Layer 2 information === |
| 28 | |
| 29 | Provide layer 2 information for Circuits VLANs, plus network connection end-points, and purpose of VLAN. |
| 30 | |
| 31 | *''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.'' |
| 32 | |
| 33 | ==== Rack Data Plane 5406 ==== |
| 34 | ||'''Port''' ||'''Connects To''' ||'''VLAN Config*'''|| |
| 35 | || B21 || AL2S ASHB at port et-3/0/0.0 || T 4001-4020 || |
| 36 | |
| 37 | === Layer 3 information === |
| 38 | NONE |
| 39 | |
| 40 | === Experimental VLANs === |
| 41 | Provide a table of Experimental VLAN detailing VLAN numbers, the endpoints, its purposes and whether VLAN is OF or non-OF. |
| 42 | |
| 43 | ||'''VLAN ID''' ||'''OF Controlled?'''||'''Purpose''' || |
| 44 | || 4001-4015 || No || GENI Stitching in AL2S || |
| 45 | || 4016-4020 || Yes || OpenFlow experiments in AL2S || |
| 46 | |
| 47 | === VLAN Translation Table === |
| 48 | If applicable, provide any VLAN translation details for site. |
| 49 | |
| 50 | === Non-VLAN Connections === |
| 51 | NONE |
| 52 | |
| 53 | === Campus Connections === |
| 54 | NONE |
| 55 | |
| 56 | == Public Internet == |
| 57 | NOT APPLICABLE |
| 58 | |
| 59 | ----- |
| 60 | |
| 61 | == Control Plane == |
| 62 | 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. |
| 63 | |
| 64 | === Details of control plane connectivity === |
| 65 | 1. What is the upstream ISP? |
| 66 | * The rack is connected to the campus' Science DMZ which peers directly with I2 and PNWGP |
| 67 | 2. What is the identifier for the border router and port facing the ISP? |
| 68 | * uwrr-ads-1 |
| 69 | * Ports: |
| 70 | {{{ |
| 71 | ae0.627 - PNWGP Commodity |
| 72 | ae0.628 PNWGP High Performance |
| 73 | ae0.829 Inet2 peering |
| 74 | ae0.2300 svlan carrying vlans 2301-2320 to the instageni rack |
| 75 | xe-1/2/9 10G interface to instageni rack |
| 76 | }}} |
| 77 | 3. Is the rack directly connected to the border router? |
| 78 | * Yes |
| 79 | |
| 80 | === Resource control subnets === |
| 81 | * IP: 198.82.156.0/26 |
| 82 | * DOMAIN: instageni.arc.vt.edu |
| 83 | |
| 84 | === Firewall/IP tables === |
| 85 | NONE |
| 86 | |
| 87 | ----- |
| 88 | == Experiment Resources == |
| 89 | Links to resource and network aggregates available for experimenters for University of Washington: |
| 90 | - http://groups.geni.net/geni/wiki/GeniAggregate/VirginiaTechInstaGENI |
| 91 | - http://groups.geni.net/geni/wiki/GeniAggregate/VirginiaTechInstaGENIOpenFlow |