Version 12 (modified by 9 years ago) (diff) | ,
---|
Florida International University Operational Data
This page captures information that is intended for Operators. The goal is to capture site contacts, connectivity, and VLANs.
Contacts
Site contact information for ExoGENI FIU.
- Contact Name: Eric Johnson
- Contact Email: esj@cs.fiu.edu
Data Plane
This section captures Data plane information for FIU detailing site topology, VLAN, Network Providers (I2/NLR/Regional) and network address information.
Data plane connectivity diagram
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.
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 Switch
Port | Connects To | VLAN Config* |
64 | AL2S JACK | T 1752 1755 1756 1757 1758 1759 1760-1769 |
Layer 3 information
NONE
Experimental VLANs
VLAN ID | OF Controlled? | Purpose |
1752 | YES | Transport to I2 Atlanta via FLR and AL2S |
1755 | YES | Transport to I2 Atlanta via FLR and AL2S |
1756 | YES | Transport to I2 Atlanta via FLR and AL2S |
1757 | YES | Transport to I2 Atlanta via FLR and AL2S |
1758 | YES | Transport to I2 Atlanta via FLR and AL2S |
1759 | YES | Transport to I2 Atlanta via FLR and AL2S |
1760-1769 | NO | Orca-managed transport VLANs to AL2S JACK |
VLAN Translation Table
VLAN 1752 is translated in AL2S to VLAN 1749 before entering the mesoscale switch in Atlanta.
Non-VLAN Connections
NONE
Campus Connections
NONE
Public Internet
NOT APPLICABLE
Control Plane
This section captures Control plane information for University of Florida, detailing topology and network address information.
Details of control plane connectivity
- Path:: FIU SERVICE PROVIDERS <--> [FIU BORDER ROUTER] <--> [ SCIS BORDER ROUTER ] <--> [SCIS CORE ROUTER] <---> RACK
- Next-hop ISP: FIU peers with many commercial and R&E ISPs, and the GENI traffic could be routed over any of them. Commercial providers include Cogent, Lan Nautilis, and Terramark.
Resource control subnets
- IP: 131.94.124.0/25
Firewall/IP tables
There are ports blocked on routers in the control plane path of the rack. Please contact the aggregate's operational contact listed on this page to request changes.
Experiment Resources
Links to resource and network aggregates available for experimenters for <site>:
Attachments (2)
-
fiu_dataplane.png (114.7 KB) - added by 10 years ago.
FIU dataplane diagram
-
fiu_dataplane.vsd (155.0 KB) - added by 10 years ago.
FIU dataplane diagram source
Download all attachments as: .zip