Browse Source

added ITL network map documentation

Jared Dunbar 1 year ago
parent
commit
c0b30fe42c
Signed by: Jared Dunbar <jrddunbr@gmail.com> GPG Key ID: CF202CC859BAC692
2 changed files with 190 additions and 0 deletions
  1. BIN
      img/itl-network-diagram.png
  2. 190
    0
      itl-patch.md

BIN
img/itl-network-diagram.png View File


+ 190
- 0
itl-patch.md View File

@@ -0,0 +1,190 @@
1
+# itl-patch.md
2
+
3
+This set of tables shows where the ITL patch panels are connected as of the new resructuring in Fall 2018.
4
+
5
+![ITL Network Diagram](img/itl-network-diagram.png "ITL Network Diagram")
6
+
7
+# Implementation Details
8
+
9
+This is the current patching diagram, showing the color of the cable, the group it travels with, and the switch it terminates at.
10
+
11
+There are 4 dead ports, and 4 unused ports (which are temp ports for courses, presentations, and projects that exist near the front of the ITL, `R3-R6`). There are also 2 special ports that are NOT TO BE TOUCHED - these are `R1` and `R2`.
12
+
13
+## Row 1: A1 - F4
14
+
15
+Port | Switch | Color | Grouping
16
+-- | -- | --
17
+A1 | ITL 1 | Green | A1 - B4
18
+A2 | ITL 1 | Green | A1 - B4
19
+A3 | ITL 1 | Green | A1 - B4
20
+A4 | ITL 1 | Green | A1 - B4
21
+B1 | ITL 1 | Green | A1 - B4
22
+B2 | ITL 1 | Green | A1 - B4
23
+GAP | -- | -- | --
24
+B3 | ITL 1 | Green | A1 - B4
25
+B4 | ITL 1 | Green | A1 - B4
26
+C1 | ITL 1 | Green | C1 - D2
27
+C2 | ITL 1 | Green | C1 - D2
28
+C3 | ITL 1 | Green | C1 - D2
29
+C4 | ITL 1 | Green | C1 - D2
30
+GAP | -- | -- | --
31
+D1 | ITL 1 | Green | C1 - D2
32
+D2 | ITL 1 | Green | C1 - D2
33
+D3 | ITL 1 | Green | D3 - E4
34
+D4 | ITL 1 | Green | D3 - E4
35
+E1 | ITL 1 | Green | D3 - E4
36
+E2 | ITL 1 | Green | D3 - E4
37
+GAP | -- | -- | --
38
+E3 | ITL 1 | Green | D3 - E4
39
+E4 | ITL 1 | Green | D3 - E4
40
+F1 | ITL 2 | Purple | F1 - F4
41
+F2 | ITL 2 | Purple | F1 - F4
42
+F3 | ITL 2 | Purple | F1 - F4
43
+F4 | ITL 2 | Purple | F1 - F4
44
+
45
+## Row 2: G1 - L4
46
+
47
+Port | Switch | Color | Grouping
48
+-- | -- | -- | --
49
+G1 | ITL 2 | Purple | G1 - G4
50
+G2 | ITL 2 | Purple | G1 - G4
51
+G3 | ITL 2 | Purple | G1 - G4
52
+G4 | ITL 2 | Purple | G1 - G4
53
+H1 | ITL 2 | Purple | H1 - I2
54
+H2 | ITL 2 | Purple | H1 - I2
55
+GAP | -- | -- | --
56
+H3 | ITL 2 | Purple | H1 - I2
57
+H4 | ITL 2 | Purple | H1 - I2
58
+I1 | ITL 2 | Purple | H1 - I2
59
+I2 | ITL 2 | Purple | H1 - I2
60
+I3 | ITL 2 | Purple | I3 - J4
61
+I4 | ITL 2 | Purple | I3 - J4
62
+GAP | -- | -- | --
63
+J1 | ITL 2 | Purple | I3 - J4
64
+J2 | ITL 2 | Purple | I3 - J4
65
+J3 | ITL 2 | Purple | I3 - J4
66
+J4 | ITL 2 | Purple | I3 - J4
67
+K1 | ITL 3 | Blue | K1 - L4
68
+K2  | ITL 3 | Blue | K1 - L4
69
+GAP | -- | -- | --
70
+K3 | ITL 3 | Blue | K1 - L4
71
+K4 | ITL 3 | Blue | K1 - L4
72
+L1 | ITL 3 | Blue | K1 - L4
73
+L2 | ITL 3 | Blue | K1 - L4
74
+L3 | ITL 3 | Blue | K1 - L4
75
+L4 | ITL 3 | Blue | K1 - L4
76
+
77
+## Row 3: M1 - Q4
78
+
79
+Port | Switch | Color | Grouping
80
+-- | -- | -- | --
81
+M1 | ITL 3 | Blue | M1 - N1
82
+M2 | ITL 3 | Blue | M1 - N1
83
+M3 | ITL 3 | Blue | M1 - N1
84
+M4 | ITL 3 | Blue | M1 - N1
85
+N1 | ITL 3 | Blue | M1 - N1
86
+**N2** | **N/A** | | **BAD PORT**
87
+GAP | -- | -- | --
88
+N3 | ITL 3 | Blue | N3 - O4
89
+N4 | ITL 3 | Blue | N3 - O4
90
+O1 | ITL 3 | Blue | N3 - O4
91
+O2 | ITL 3 | Blue | N3 - O4
92
+O3 | ITL 3 | Blue | N3 - O4
93
+O4 | ITL 3 | Blue | N3 - O4
94
+GAP | -- | -- | --
95
+**O5** | **N/A** | | **BAD PORT**
96
+**O6** | **N/A** | | **BAD PORT**
97
+P1 | ITL 4 | Green | P1 - P5
98
+P2 | ITL 4 | Green | P1 - P5
99
+P3 | ITL 4 | Green | P1 - P5
100
+P4 | ITL 4 | Green | P1 - P5
101
+GAP | -- | -- | --
102
+P5 | ITL 4 | Green | P1 - P5
103
+**P6** | ITL 1 | Green | **P6**
104
+**Q1** | **N/A** | | **BAD PORT**
105
+Q2 | ITL 2 | Purple | Q2 - Q4
106
+Q3 | ITL 2 | Purple | Q2 - Q4
107
+Q4 | ITL 2 | Purple | Q2 - Q4
108
+
109
+## Row 4: Q5 - U4
110
+
111
+Port | Switch | Color | Grouping
112
+-- | -- | -- | --
113
+Q5 | ITL 4 | Green | Q5 - Q6
114
+Q6 | ITL 4 | Green | Q5 - Q6
115
+R1 | Note 1 | White | R1
116
+R2 | Note 2 | Orange | R2
117
+R3 | **N/C** | | **N/C**
118
+R4 | **N/C** | | **N/C**
119
+GAP | -- | -- | --
120
+R5 | **N/C** | | **N/C**
121
+R6 | **N/C** | | **N/C**
122
+S1 | ITL 4 | Green | S1 - S4, Q5 - Q6
123
+S2 | ITL 4 | Green | S1 - S4, Q5 - Q6
124
+S3 | ITL 4 | Green | S1 - S4, Q5 - Q6
125
+S4 | ITL 4 | Green | S1 - S4, Q5 - Q6
126
+GAP | -- | -- | --
127
+S5 | ITL 4 | Green | S5 - T4
128
+S6 | ITL 4 | Green | S5 - T4
129
+T1 | ITL 4 | Green | S5 - T4
130
+T2 | ITL 4 | Green | S5 - T4
131
+T3 | ITL 4 | Green | S5 - T4
132
+T4 | ITL 4 | Green | S5 - T4
133
+GAP | -- | -- | --
134
+T5 | ITL 4 | Green | T5 - U4
135
+T6 | ITL 4 | Green | T5 - U4
136
+U1 | ITL 4 | Green | T5 - U4
137
+U2 | ITL 4 | Green | T5 - U4
138
+U3 | ITL 4 | Green | T5 - U4
139
+U4 | ITL 4 | Green | T5 - U4
140
+
141
+### Notes on Ports R1 and R2
142
+
143
+* R1: For Polycom. To VoIP box, and then to OIT sc-334-c2960, port 22
144
+* R2: For Echo360. To OIT sc-334-c2960, port 21
145
+
146
+## Row 5: U5 - U6
147
+
148
+Port | Switch | Color | Grouping
149
+-- | -- | -- | --
150
+Q5 | ITL 1 | Green | S1 - S4, Q5 - Q6
151
+Q6 | ITL 1 | Green | S1 - S4, Q5 - Q6
152
+
153
+# Inception and Planning
154
+
155
+In the Fall of 2018, it was suggested by Ryan S. (aka, Stew) that we re-wire the ITL. Jared D. had been itching to do this for over a year, and so, since freshman were handy, we began at around 6pm by removing the existing cabling, and that did not take very long. We spent at least an hour or two coming up with the way we wanted to set up the ITL, since we could do many different things with it.
156
+
157
+## Constraints
158
+
159
+The main constraints were as follows:
160
+
161
+* Rewire the ITL in such a way that there are at most 6-7 computers per switch
162
+* Be able to split the ITL into 2-4 parts during competitive hackathons
163
+* Be able to completely isolate the ITL from the rest of the COSI network with only 4 uplink cables
164
+* Restrict port utilization on the switches to allow all 24 port switches
165
+
166
+## Reasoning
167
+
168
+The reasoning for the constraints is as follows:
169
+
170
+### Only 6-7 Computers per Switch
171
+
172
+We wanted to have only 6-7 computers per switch for various reasons. Firstly, it allows the dumb 1Gb/s switches (which can only have one 1Gb/s uplink per switch). Since the uplinks from `ITL 1` through `ITL 4` are all connected directly to `swm1`, and that switch has a 4Gb/s LAG to `swf1` (the 10Gb/s fiber network), this affords each computer the fastest shared connection to the rest of the COSI and the campus network as possible. This is particularly useful for the ITL deployments - we reduced the time from ~8 hours down to ~1.5 hours of clone time by just re-balancing the cables, and by using NFS for the cloning process instead of SSHFS.
173
+
174
+### Split the ITL into 2-4 parts
175
+
176
+During hackathons, we would like to be able to split the room up. The idea is that we could split two (or more) parts of the ITL against one another on separate servers on separate subnets, or keep them from interacting entirely, using a NAT.
177
+
178
+### Be able to isolate the ITL from the COSI network using 4 uplink cables
179
+
180
+In 2017, Jared D. removed the old air-gapped ITL network. In 2015, it used to be that each computer had two network interfaces - one on the public internet, and one on the airgap network. The idea was that you would disconnect the ITL from the public internet, and just use the existing airgap network to spread viruses within the ITL. There was an incident with an IPv6 bug in Windows at the time, and a lab that was supposed to only affect the ITL, since it was supposed that the network was disconnected, but it was not disconnected correctly, and instead crashed the networking stack for every single Windows computer on the entire campus. The reason for this occurence is not known, but my guess is that a port died on the airgap network, or a computer got unplugged and replugged. Whatever the reason, a computer was still connected to the public internet.
181
+
182
+My resolution for this is threefold - make the ITL documentation as clear as possible, and stick with it, and also to make sure that there is no "airgap" network mistake to be made - if you need an airgap network, use the network you have, and disconnect it entirely from the internet. The other major problem we had is that since there were two network interfaces live, some PXE images failed because they would boot from one, and try to get the image from the other. This obviously would cause the boot to fail, so the airgap switch had to be kept off when this happened. Add to this that the airgap switch was an old 100Mb/s switch, and there were more than enoguh reasons for its deprecation entirely.
183
+
184
+### Restrict port utilization to 24 port switches
185
+
186
+Hardware in COSI tends to go bad over time. 48 port switches are hard to maintain, dumb switches have major problems with bandwidth, since they can only have one (non LAG'd) connection to the uplink, this creates many problems. 24 port switches are also more common and easier to find, and cheaper, than 48 port switches. Even though we have a 48 port switch, I would feel that should it ever die, it would be annoying to find a quick pair of 24 port replacements to fill it's place. This also means that in the future, if we decide to upgrade `swm1` through `swm4`, we can use managed switches on the ITL.
187
+
188
+## Other Planning
189
+
190
+We wanted to make sure that the ports near the computers were as similar to the computers near it as possible. This means that if a port dies in the wall, that the computer can be relocated to a physically nearby port, and be able to be used without ending up on a complete other network. This also means that duing competitive events, people can't just patch into another network without having to be physically in another part of the room. While not optimal, we have tried our best to fulfill this design.

Loading…
Cancel
Save