| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | = Texas A&M University Operational Data = |
| | 4 | |
| | 5 | This page captures GENI rack information that is intended for Operators. The goal is to capture site contacts, connectivity, and VLANs. |
| | 6 | |
| | 7 | Note anything unusual about this rack in this section. For example, this is a 12-node rack instead of a standard 5-node rack. |
| | 8 | |
| | 9 | == Contacts == |
| | 10 | |
| | 11 | Site contact information: |
| | 12 | * Contact Name: Joe Lewis |
| | 13 | * Contact Email: jdlewis [at] tamu [dot] edu |
| | 14 | |
| | 15 | ----- |
| | 16 | == Data Plane == |
| | 17 | |
| | 18 | This section captures data plane information for Texas A&M University detailing site topology, VLAN, Network Providers (I2/Regional) and network address information. Be sure to note the total link bandwidth of data plane connections. Note the vendor and model for any OpenFlow switches that are not part of a GENI rack. |
| | 19 | |
| | 20 | Additional sites that are important to operations for this one (e.g. VLANs through a non-GENI regional) should also be captured here. |
| | 21 | |
| | 22 | === Data plane connectivity === |
| | 23 | |
| | 24 | <<Insert meso-scale or other relevant L2 dataplane diagram here>>> |
| | 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 Switch ==== |
| | 34 | ||'''Port'''||'''Connects To'''||'''VLAN Config*'''|| |
| | 35 | || 64 || ??? || T 940-949 || |
| | 36 | <<Insert port to VLAN mappings here>>> |
| | 37 | |
| | 38 | === Layer 3 information === |
| | 39 | NONE |
| | 40 | |
| | 41 | === Experimental VLANs === |
| | 42 | |
| | 43 | Provide a table of Experimental VLAN detailing VLAN numbers, the endpoints, its purposes and whether VLAN is OF or non-OF. |
| | 44 | |
| | 45 | ||'''VLAN ID'''||'''OF Controlled?'''||'''Purpose''' || |
| | 46 | || 880-889 || No || Orca-controlled ExoGENI stitching || |
| | 47 | || 940-949 || No || GENI Stitching || |
| | 48 | |
| | 49 | |
| | 50 | === VLAN Translation Table === |
| | 51 | NONE |
| | 52 | |
| | 53 | === Non-VLAN Connections === |
| | 54 | NONE |
| | 55 | |
| | 56 | === Campus Connections === |
| | 57 | NONE |
| | 58 | |
| | 59 | == Public Internet == |
| | 60 | |
| | 61 | |
| | 62 | ----- |
| | 63 | |
| | 64 | == Control Plane == |
| | 65 | |
| | 66 | This section captures Control plane information for OSF detailing topology and network address information. Additional site which is not specified, but deemed important, can also be captured here. |
| | 67 | |
| | 68 | === Control Plane Information === |
| | 69 | |
| | 70 | <<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. >> |
| | 71 | |
| | 72 | === Resource control subnets === |
| | 73 | |
| | 74 | <<Enter Control network subnet>> |
| | 75 | |
| | 76 | === Firewall/IP tables === |
| | 77 | |
| | 78 | << If firewall or IP tables are in use, insert who is responsible and any information deemed of importance about the setup. >> |
| | 79 | |
| | 80 | ----- |
| | 81 | |
| | 82 | == Experiment Resources == |
| | 83 | |
| | 84 | Links to resource and network aggregates available for experimenters for Texas A&M University: |
| | 85 | - [wiki:GeniAggregate/TexasAMUniversityExoGENI] |
| | 86 | - [wiki:GeniAggregate/TexasAMUniversityExoGENIOpenflow] |
