Information Systems:Old Wireless (WiFi) Infrastructure (pre-2017) - Revision history

Norwinu at 22:38, 27 September 2018

2018-09-27T22:38:48Z

Norwinu at 16:50, 17 August 2017

2017-08-17T16:50:25Z

Norwinu at 23:26, 9 August 2017

2017-08-09T23:26:30Z

Norwinu: Norwinu moved page Information Systems:Wireless (WiFi) Infrastructure to Information Systems:Old Wireless (WiFi) Infrastructure (pre-2017)

2017-08-09T23:23:55Z

Norwinu moved page Information Systems:Wireless (WiFi) Infrastructure to Information Systems:Old Wireless (WiFi) Infrastructure (pre-2017)

Norwinu: /* Wireless networks */

2017-02-23T22:04:38Z

Wireless networks

Norwinu: /* 02/17 - Access point failure causing massive and random outages */

2017-02-23T22:03:50Z

02/17 - Access point failure causing massive and random outages

Norwinu: /* Access points */

2017-02-23T22:00:44Z

Access points

Norwinu: /* Configuration */

2017-02-23T00:23:21Z

Configuration

Norwinu at 00:23, 23 February 2017

2017-02-23T00:23:00Z

Norwinu: /* Configuration Notes and Changelog */

2017-02-23T00:17:42Z

Configuration Notes and Changelog

← Older revision		Revision as of 22:38, 27 September 2018
Line 77:		Line 77:

	[[Category: Archived Pages]]		[[Category: Archived Pages]]
−	[[Category: Networking]]

← Older revision		Revision as of 16:50, 17 August 2017
Line 1:		Line 1:
		+	Note: This page is old. [[Information_Systems:Wireless_Infrastructure_(WLAN)\|Refer to this article instead.]]
	=Overview=		=Overview=
	This page describes the current wireless (WLAN) infrastructure at uniPHARM. As of September 2016, there is a business case to redo the entire infrastructure, so the info on this page is slated to change drastically.		This page describes the current wireless (WLAN) infrastructure at uniPHARM. As of September 2016, there is a business case to redo the entire infrastructure, so the info on this page is slated to change drastically.

← Older revision		Revision as of 23:26, 9 August 2017
Line 75:		Line 75:
	* Presence of wireless b clients		* Presence of wireless b clients

−	[[Category:~~Networking~~]]	+	[[Category: Archived Pages]]
		+	[[Category: Networking]]

@@ Line 53: / Line 53: @@
 | uwddc1 || Mobile belt printers || Cisco AP541N-K9 || WEP || UWDVan20dyke52 || Implemented because mobile belt printers had trouble connecting to Psion access points. (I've validated this - the printers don't handle WPA-Enterprise well. -[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]]))
 |-
-| unioffice2 || Guest wireless (Walled garden) || Cisco WAP4410N || WPA2-Personal || Unipharm6y0d || '''Disabled due to interference'''
+| unioffice2 || Guest wireless (Walled garden) || Cisco WAP4410N || WPA2-Personal || Unipharm6y0d || '''Entire network disabled due to interference. Re-enabled upon visits from authorized guests.'''
 |}

@@ Line 62: / Line 62: @@
 It is theorized that a failure of even one AP in the cluster has major ramifications to the operation of the entire cluster. This could be because wireless clients unknowingly roam/reassociate to the failing AP, or because any one access point contributes some processing in the cluster mechanism.
-In an attempt to fix this, the AP8SHIP access point was replaced with AP13SHIP, a spare AP of the same model. During the replacement, the antenna connectors broke, such that the new AP did not seem to emit a strong enough signal for any of the guns to operate, despite being an active member (in other respects than wireless) of the cluster. Meanwhile, it was always a theory that the roaming between AP8SHIP and AP9CAGE to serve the main picking area (OTC,HTC,RX etc) was more detrimental than beneficial. This is due to the fact that the cluster is secured with WPA2-Enterprise - which requires slow, RADIUS authentication - coupled with the fact that no fast-roaming technologies are implemented (due to the client-side and AP-related barriers).
+In an attempt to fix this, the AP8SHIP access point was replaced with AP13SHIP, a spare AP of the same model. During the replacement, the antenna connectors broke, such that the new AP did not seem to emit a strong enough signal for any of the guns to operate, despite being an active member (in other respects than wireless) of the cluster. Meanwhile, it was always a theory that the roaming between AP8SHIP and AP9CAGE to serve the main picking area (OTC,HTC,RX etc) was more detrimental than beneficial. This is due to the fact that the cluster is secured with WPA2-Enterprise - which requires slow, RADIUS authentication - coupled with the fact that no fast-roaming technologies are implemented (due to the client-side and AP-related barriers). ''Therefore, AP13SHIP is in place and running but not serving wireless (no wireless clients can connect to it)''.
-'''Outcome''': The Psion cluster serving the RF network has been reduced to 3 APs (AP9cage,receiving, and narc). Feedback has been very positive thus far.
+'''Outcome''': The Psion cluster serving the RF network has been effectively reduced to 3 APs (AP9cage,receiving, and narc). Feedback has been very positive thus far.
 ==Misc. changes==

@@ Line 20: / Line 20: @@
 | ap7recv.unipharm.local || Receiving overhang || 172.30.18.117 || 11 || rowspan=4 | b/g, g-only || 00:08:A2:08:38:90 || admin/visionAP7
 |-
-| ap13ship.unipharm.local || Shipping overhang || 172.30.18.125 || - ||  00:08:A2:04:A7:94  || admin/visionAP13
+| ap13ship.unipharm.local || Shipping overhang || 172.30.18.125 || ''Disabled'' ||  00:08:A2:04:A7:94  || admin/visionAP13
 |-
 | ap9cage.unipharm.local || Forklift runway/Large Down || 172.30.18.119 || 6 || 00:08:A2:08:3C:E0 || admin/visionAP9
@@ Line 34: / Line 34: @@
 | rowspan=3 | Loomis Access Points - Cisco WAP4410N
 |-
-| ap1guest || Narc cage || 192.168.1.253 || Disabled || rowspan=2 | b/g/n, n-only || adminit/vision1t
+| ap1guest || Narc cage || 192.168.1.253 || ''Disabled'' || rowspan=2 | b/g/n, n-only || adminit/vision1t
 |-
-| ap2guest || Promo area (receiving) || 192.168.1.252 || Disabled || adminit/vision1t
+| ap2guest || Promo area (receiving) || 192.168.1.252 || ''Disabled'' || adminit/vision1t
 |-
 |}

@@ Line 5: / Line 5: @@
 =Configuration=
 ===Access points===
 {| border="1" class="wikitable" style="width: 90%"
@@ Line 56: / Line 55: @@
 | unioffice2 || Guest wireless (Walled garden) || Cisco WAP4410N || WPA2-Personal || Unipharm6y0d || '''Disabled due to interference'''
 |}
 =Notes=

@@ Line 57: / Line 57: @@
 |}
 =Notes=
-==To-do==
+=To-do=
 * Roaming and roaming authentication
 * Roaming stickiness

← Older revision		Revision as of 00:17, 23 February 2017
Line 58:		Line 58:

	==Configuration Notes and Changelog==		==Configuration Notes and Changelog==
−	===02/17 - Access point failure causing massive and random outages===
−	In Jan. to Feb. 2017, major issues were being experienced with the network serving the RF guns (Psion cluster). The guns would experience red locks (Lock-B) in TekTerm, which strongly indicates a loss of wireless connectivity (as opposed to the yellow Lock-H, which indicates being in host-wait i.e. attempting to resume communication with Bart). The most heavily affected area was OTC. After weeks of monitoring and investigation, it seems that one or more of the access points in the cluster are experiencing internal failure (likely the internal flash), due to age. Syslog indicated that some of the internal processes of the APs were restarting at random points in the day.

−	It is theorized that a failure of even one AP in the cluster has major ramifications to the operation of the entire cluster. This could be because wireless clients unknowingly roam/reassociate to the failing AP, or because any one access point contributes some processing in the cluster mechanism.
−
−	In an attempt to fix this, the AP8SHIP access point was replaced with AP13SHIP, a spare AP of the same model. During the replacement, the antenna connectors broke, such that the new AP did not seem to emit a strong enough signal for any of the guns to operate, despite being an active member (in other respects than wireless) of the cluster. Meanwhile, it was always a theory that the roaming between AP8SHIP and AP9CAGE to serve the main picking area (OTC,HTC,RX etc) was more detrimental than beneficial. This is due to the fact that the cluster is secured with WPA2-Enterprise - which requires slow, RADIUS authentication - coupled with the fact that no fast-roaming technologies are implemented (due to the client-side and AP-related barriers).
−
−	'''Outcome''': The Psion cluster serving the RF network has been reduced to 3 APs (AP9cage,receiving, and narc). Feedback has been very positive thus far.

	===Misc. changes===		===Misc. changes===