University of University of California Los Angeles Operational Data

This page captures information for InstaGENI sites that is intended for Operators. The goal is to capture site contacts, connectivity, and VLANs.

Contacts

Site contact information for InstaGENI UCLA.

Contact Name: insert_name_here Contact Email: insert_email_addr_here

---

Data Plane

This section captures Data plane information for University of University of California Los Angeles 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.

Data plane connectivity diagram

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 5406

Port	Connects To	VLAN Config*
A1	pc1[eth1]
A2	pc1[eth2]
A3	pc1[eth3]
A4	pc2[eth1]
A5	pc2[eth2]
A6	pc2[eth3]
A7	pc3[eth1]
A8	pc3[eth2]
A9	pc3[eth3]
A10	pc4[eth1]
A11	pc4[eth2]
A12	pc4[eth3]
A13	pc5[eth1]
A14	pc5[eth2]
A15	pc5[eth3]
A24	UCLA Brocade MLX	T 1855

Layer 3 information

NONE

Experimental VLANs

Provide a table of Experimental VLAN detailing VLAN numbers, the endpoints, its purposes and whether VLAN is OF or non-OF.

VLAN ID	OF Controlled?	Purpose
1855	Yes	Transport to COTN for shared mesoscale

VLAN Translation Table

The UCLA MLX does VLAN translation (of sorts) between the InstaGENI rack and the COTN switch:

InstaGENI-rack-facing VLAN	COTN-facing VLAN
1855	untagged

Non-VLAN Connections

NONE

Campus Connections

Document what network campus connection are in place for this rack.

Public Internet

NONE

---

Control Plane

This section captures Control plane information for University of University of California Los Angeles detailing topology and network address information. Additional site which is not specified, but deemed important, can also be captured here.

Control plane connectivity diagram

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.

Resource control subnets

Provide a list of subnets used in the rack and their intended use.

Firewall/IP tables

If firewall or IP tables are in use, insert who is responsible and any information deemed of importance about the setup.

---

Experiment Resources

Links to resource and network aggregates available for experimenters for University of University of California Los Angeles:

• ​http://groups.geni.net/geni/wiki/GeniAggregate/UCLAInstaGENI
• ​http://groups.geni.net/geni/wiki/GeniAggregate/UCLAInstaGENIOpenFlow