| | 1 | |
| | 2 | [[PageOutline]] |
| | 3 | |
| | 4 | <<University of Utah Utah-Stitch>> Operational Data |
| | 5 | |
| | 6 | |
| | 7 | This page captures GENI rack information that is intended for Operators. The goal is to capture site contacts, connectivity, and VLANs. |
| | 8 | |
| | 9 | Note anything unusual about this rack in this section. For example, this is a 12-node rack instead of a standard 5-node rack. |
| | 10 | Contacts |
| | 11 | |
| | 12 | Site contact information: |
| | 13 | |
| | 14 | Contact Name: Robert Ricci |
| | 15 | |
| | 16 | Contact Email: instageni-ops@flux.utah.edu, ricci@cs.utah.edu |
| | 17 | |
| | 18 | Data Plane |
| | 19 | |
| | 20 | This section captures data plane information for utah-stitch 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. |
| | 21 | |
| | 22 | Additional sites that are important to operations for this one (e.g. VLANs through a non-GENI regional) should also be captured here. |
| | 23 | Data plane connectivity |
| | 24 | |
| | 25 | <<Insert relevant L2 dataplane diagram here>>> |
| | 26 | Layer 2 information |
| | 27 | |
| | 28 | Provide layer 2 information for Circuits VLANs, plus network connection end-points, and purpose of VLAN. |
| | 29 | |
| | 30 | *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. |
| | 31 | Rack Data Plane Switch |
| | 32 | Port Connects To VLAN Config* |
| | 33 | |
| | 34 | <<Insert port to VLAN mappings here>>> |
| | 35 | Layer 3 information |
| | 36 | |
| | 37 | <<Insert available layer 3 information here. If not applicable, replace with "none".>> |
| | 38 | Experimental VLANs |
| | 39 | |
| | 40 | Provide a table of Experimental VLAN detailing VLAN numbers, the endpoints, its purposes and whether VLAN is OF or non-OF. |
| | 41 | VLAN ID OF Controlled? Purpose |
| | 42 | |
| | 43 | <<Insert OF and non-OF experimenter VLANs and expected use>> |
| | 44 | VLAN Translation Table |
| | 45 | |
| | 46 | << If applicable provide details for VLAN translation. If not applicable, replace with "none".>> |
| | 47 | Non-VLAN Connections |
| | 48 | |
| | 49 | << If applicable provide details for non VLAN connections. If not applicable, replace with "none".>> |
| | 50 | Campus Connections |
| | 51 | |
| | 52 | << Provide details for campus connection. If none are available, replace with "none".>> |
| | 53 | Public Internet |
| | 54 | Control Plane |
| | 55 | |
| | 56 | 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. |
| | 57 | Control Plane Connectivity |
| | 58 | |
| | 59 | <<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. >> |
| | 60 | Resource control subnets |
| | 61 | |
| | 62 | <<Enter Control network subnet>> |
| | 63 | Firewall/IP tables |
| | 64 | |
| | 65 | << If firewall or IP tables are in use, insert who is responsible and any information deemed of importance about the setup. >> |
| | 66 | Experiment Resources |
| | 67 | |
| | 68 | Links to resource and network aggregates available for experimenters for <<SitenameX>>: |
| | 69 | |
| | 70 | GeniAggregate/SitenameX? |
| | 71 | GeniAggregate/SitenameXOpenflow? |
| | 72 | |
