Changes between Version 2 and Version 3 of GENIRacksHome/InstageniRacks/Operators/Wisconsin
- Timestamp:
- 10/23/13 11:53:31 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/InstageniRacks/Operators/Wisconsin
v2 v3 1 1 [[PageOutline]] 2 2 3 = University of Wisconsin Operational Data =3 = University of Wisconsin-Madison Operational Data = 4 4 5 5 This page captures information for InstaGENI sites that is intended for Operators. The goal is to capture site contacts, connectivity, and VLANs. … … 7 7 == Contacts == 8 8 9 Site contact information for InstaGENI Northwestern.10 Contact Name: insert_name_here11 Contact Email: insert_email_addr_here9 Site contact information for InstaGENI UMC. 10 * Contact Name: Dale W. Carder 11 * Contact Email: dwcarder@wisc.edu 12 12 13 13 ----- 14 14 == Data Plane == 15 15 16 This section captures Data plane information for University of Wisconsin detailing site topology, VLAN, Network Providers (I2/NLR/Regional) and network address information. Additional site which is not specified, but deemed important, can also be captured here.16 This section captures Data plane information for University of Wisconsin-Madison detailing site topology, VLAN, Network Providers (I2/NLR/Regional) and network address information. Additional site which is not specified, but deemed important, can also be captured here. 17 17 18 18 === Data plane connectivity diagram === 19 19 20 Provide a diagram that captures device, ports and VLAN information at ingress and outgress for transport network. For non-OF connections provide device names and ports connected to transport network (NRL/I2/Regional) and VLAN used for those ports. Diagram should capture campus connections. 20 The following diagram captures device, ports and VLAN information at ingress and outgress for transport network. For non-OF connections, the diagram also provides device names and ports connected to transport network (NRL/I2/Regional) and VLAN used for those ports. 21 22 [[Image(UWOperator.jpg)]] 21 23 22 24 === Layer 2 information === … … 26 28 *''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.'' 27 29 28 ==== Rack Data Plane 5406 ==== 29 ||'''Port'''||'''Connects To'''||'''VLAN Config*'''|| 30 || || || || 30 ==== Rack Data Plane OpenFlow Switch (HP 5406) ==== 31 ||'''Port'''||'''Connects To''' ||'''VLAN Config*'''|| 32 || A19/19 || ION WASH at port gi0/20 || T 2497 || 33 || A19/19 || ION CHIC || T 925-929 || 34 || A19/19 || UW WiMAX Lab || T 912 || 35 31 36 32 37 === Layer 3 information === 33 If applicable, provide layer 3 information. If not applicable, replace with "none".38 NONE 34 39 35 40 === Experimental VLANs === 36 41 Provide a table of Experimental VLAN detailing VLAN numbers, the endpoints, its purposes and whether VLAN is OF or non-OF. 37 42 38 ||'''VLAN ID'''||'''OF Controlled?'''||'''Purpose''' || 39 || || || || 43 ||'''VLAN ID'''||'''OF Controlled?'''||'''Purpose''' || 44 || 2497 || YES || Transport to I2 ION WASH (Shared Mesoscale) via CIC OmniPoP || 45 || 912 || NO || Transport to WiMAX Lab for Mobility First Project || 46 || 925 || NO || Transport to I2 ION CHIC Lab for Mobility First Project || 47 || 926-929 || NO || Transport to I2 ION CHIC Lab for FIA Projects || 40 48 41 49 === VLAN Translation Table === … … 43 51 44 52 === Non-VLAN Connections === 45 If applicable provide details for non VLAN connections. If not applicable, replace with "none".53 NONE 46 54 47 55 === Campus Connections === 48 Document what network campus connection are in place for this rack. 56 NONE 49 57 50 58 == Public Internet == 51 If applicable, provide details for public internet connectivity. 59 NOT APPLICABLE 52 60 53 61 ----- 54 62 55 63 == Control Plane == 56 This section captures Control plane information for University of Wisconsindetailing topology and network address information. Additional site which is not specified, but deemed important, can also be captured here.64 This section captures Control plane information for University of Missouri-Columbia detailing topology and network address information. Additional site which is not specified, but deemed important, can also be captured here. 57 65 58 === Control plane connectivity diagram === 66 === Details of control plane connectivity === 67 1. What is the upstream ISP? 68 * !WiscNet (AS 2381) 69 2. What is the identifier for the border router and port facing the ISP? 70 * ID: rx-cssc-b380-1-core (ASR9922) 71 * Port (Research): Hu0/0/0/1, Te0/9/0/31, Te0/9/0/32 72 * Port (Commodity): Te0/9/0/33 73 3a. Is the rack directly connected to the border router? 74 * NO 59 75 60 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. 76 3b. Does the connection pass through a campus firewall? 77 * NO 61 78 62 79 === Resource control subnets === 63 Provide a list of subnets used in the rack and their intended use. 80 * IP: 128.204.159.0/26 81 * DOMAIN: instageni.wisc.edu 64 82 65 83 === Firewall/IP tables === 66 If firewall or IP tables are in use, insert who is responsible and any information deemed of importance about the setup.84 NONE. 67 85 68 86 ----- 69 87 == Experiment Resources == 70 Links to resource and network aggregates available for experimenters for University of Wisconsin:71 - http://groups.geni.net/geni/wiki/GeniAggregate/ WisconsinInstaGENI72 - http://groups.geni.net/geni/wiki/GeniAggregate/ WisconsinInstaGENIOpenFlow88 Links to resource and network aggregates available for experimenters for University of Missouri-Columbia: 89 - http://groups.geni.net/geni/wiki/GeniAggregate/MissouriColumbiaInstaGENI 90 - http://groups.geni.net/geni/wiki/GeniAggregate/MissouriColumbiaInstaGENIOpenFlow