| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | = University of North Florida Operational Data = |
| | 4 | |
| | 5 | This page captures information that is intended for Operators. The goal is to capture site contacts, connectivity, and VLANs. |
| | 6 | |
| | 7 | == Contacts == |
| | 8 | |
| | 9 | Site contact information for ExoGENI UNF. |
| | 10 | * Contact Name: Chris Griffin |
| | 11 | |
| | 12 | * Contact Email: cgriffin@ufl.edu |
| | 13 | |
| | 14 | ----- |
| | 15 | == Data Plane == |
| | 16 | |
| | 17 | This section captures Data plane information for UNF detailing site topology, VLAN, Network Providers (I2/Regional) and network address information. |
| | 18 | |
| | 19 | === Data plane connectivity diagram === |
| | 20 | |
| | 21 | The following diagram captures device, ports and VLAN information at ingress and egress for transport network. For non-OF connections, the diagram also provides device names and ports connected to transport network (I2/Regional) and VLANs used for those ports. |
| | 22 | |
| | 23 | [[Image(UNFOperator.jpg)]] |
| | 24 | |
| | 25 | === Layer 2 information === |
| | 26 | |
| | 27 | Provide layer 2 information for Circuits VLANs, plus network connection end-points, and purpose of VLAN. |
| | 28 | |
| | 29 | *''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.'' |
| | 30 | |
| | 31 | ==== Rack Data Plane Switch ==== |
| | 32 | ||'''Port'''||'''Connects To'''||'''VLAN Config*'''|| |
| | 33 | || 64/64 || AL2S JACK || 1470-1484 || |
| | 34 | |
| | 35 | === Layer 3 information === |
| | 36 | NONE |
| | 37 | |
| | 38 | === Experimental VLANs === |
| | 39 | |
| | 40 | ||'''VLAN ID'''||'''OF Controlled?'''||'''Purpose''' || |
| | 41 | || 1470-1484 || NO || Transport to I2 AL2S Atlanta via FLR || |
| | 42 | || 1485-1489 || YES || Transport to I2 AL2S Atlanta via FLR || |
| | 43 | |
| | 44 | === VLAN Translation Table === |
| | 45 | If applicable, provide any VLAN translation details for site. |
| | 46 | |
| | 47 | === Non-VLAN Connections === |
| | 48 | NONE |
| | 49 | |
| | 50 | === Campus Connections === |
| | 51 | NONE |
| | 52 | |
| | 53 | == Public Internet == |
| | 54 | NOT APPLICABLE |
| | 55 | |
| | 56 | ----- |
| | 57 | |
| | 58 | == Control Plane == |
| | 59 | This section captures Control plane information for University of Florida, detailing topology and network address information. |
| | 60 | |
| | 61 | === Details of control plane connectivity === |
| | 62 | 1. What is the upstream ISP? |
| | 63 | * Primarily FLR, but also Cox communications for Internet. |
| | 64 | 2. What is the identifier for the border router and port facing the ISP? |
| | 65 | * ssrb230a-ewan-msfc-1 (both R&E and ISP paths) |
| | 66 | * ctx36-ewan-msfc-1 (both R&E and ISP paths) |
| | 67 | * ssrb230a-crn-mlxe16-1 (R&E paths only) |
| | 68 | 3a. Is the rack directly connected to the border router? |
| | 69 | * NO |
| | 70 | |
| | 71 | 3b. Does the connection pass through a campus firewall? |
| | 72 | * NO |
| | 73 | |
| | 74 | |
| | 75 | |
| | 76 | === Resource control subnets === |
| | 77 | N/A |
| | 78 | |
| | 79 | === Firewall/IP tables === |
| | 80 | N/A |
| | 81 | |
| | 82 | ----- |
| | 83 | == Experiment Resources == |
| | 84 | Links to resource and network aggregates available for experimenters for <site>: |
| | 85 | - http://groups.geni.net/geni/wiki/GeniAggregate/SitenameExoGENI |
| | 86 | - http://groups.geni.net/geni/wiki/GeniAggregate/SitenameExoGENIOpenFlow |
