Information Systems:Wireless Infrastructure (WLAN)

From uniWIKI
Jump to navigation Jump to search

Overview

This article documents the current wireless infrastructure. A complete overhaul of the wireless was conducted in July 2017; the old article is now located here.

This article is broken down into 2 main sections, Configuration (background information) and Administration (troubleshooting).

I ramble a lot in my articles so I figure I should start splitting content so that there's at least an area that's straightforward for someone trying to get stuff done. You're welcome. -norwizzle (talk)

The WiNG platform by Extreme Networks is used for wireless at uniPHARM.

Configuration

Access Points

  • The model of AP is the Extreme Networks AP7532.
  • 6 units total - 4 of the external antenna variant, 2 with internal antennas
DNS Hostname Alias Network Hostname Location IP address Notes
apxoffice2floor office_2ndfloor ap_office_2f_controller Office, 2nd floor (I.S.) 172.30.18.80 Controller.
apxoffice1floor office_1stfloor ap_office_1f Office, 1st floor (Reception) 172.30.18.82
apxdchhc dc_hhc ap_dc_hhc Home Health Care 172.30.18.84 On picking station shelf.
apxdcrec dc_receiving ap_dc_receiving Unity Training Room 172.30.18.83 In the small office.
apxdclargedown dc_largedown ap_dc_largedown Pillar, large down/fridge area 172.30.18.85 Temporarily mounted to pillar.
apxdcalt dc_alt ap_dc_alt Spare 172.30.18.86 TBD

Channels and antenna power

Wireless channels and output power are locked-in per AP. No auto is used (that would be a severe indication of technical incompetence).

On the 2.4GHz band, only the non-overlapping channels 1, 6 and 11 are used. 4 access points (see table above) are enabled for 2.4GHz, with the farthest 2 sharing the same channel. There is also not that much noise from surrounding WiFi networks so there is little channel overlap. The intent is to keep wireless traffic on this spectrum to primarily serving RF gun usage to prevent interference. For devices able to use 5GHz, performance is drastically improved on that band anyway (802.11ac), so it is more desirable to steer clients to that radio.

On the 5GHz band, there are more non-overlapping channels than there are access points, so channels were selected randomly. It is worthy to note that all channels are available for selection, but some are supposed to be for DFS use (e.g. channel 165). These are expansion channels, so choosing one as the primary channel will cause most clients to not be able to connect to that radio.

Antenna output power was tuned using a semi-scientific process of detecting signal strength of the access points from different locations. If left at full power, 1 access point can blanket virtually 80% of the entire building with signal (leading to poor-quality signal at farther distances). Thus, it is ideal to restrict power to influence client-roaming to connect to the nearest AP for the best signal quality.

Controller

One of the APs (office_2ndflr_controller), is being used as a virtual controller - a WiNG feature that allows an AP to manage other APs. Due to the fairly beefy internal specs of a typical AP in the market today, this feature is being offered more and more by vendors, and is completely feasible for smaller deployments (e.g. the management of 5 other APs by this controller is actually well under the recommended maximum of 64 devices).

It is quite important to note that the term 'controller' in this scenario does not refer to a traditional wireless controller, where there is centralized traffic forwarding i.e. all wireless traffic passes through the controller, and the APs can't function without one. Rather, what we have is known as a distributed architecture, where the APs are independent and can function without a controller, yet their settings are configured and their stats are monitored by the adopting controller. This wireless architecture is highly efficient as it centralizes management but avoids a hardware appliance, which as a single point of failure would make for a less fault-tolerant setup.

Hardware mounting and PoE

Currently, none of the APs are permanently mounted. Ideal hardware mounting solutions for each AP is under exploration.

PoE adapters were purchased separately and currently power the APs. It is expected that PoE switches will be acquired in the future, perhaps as part of the VoIP upgrade project.

Network configuration

  • The APs have static IP addresses.
  • Most are configured to communicate on VLANs 1 and 2.
  • IP routing is turned off.
  • Much of the IPv6 functionality is turned off.
  • The domain controllers are used for DNS resolution.

System profile and device overrides

It is highly important to understand this following section if you are involved in the technical administration of the APs.

WiNG APs adopted by a controller are managed through a system profile. This profile is specific to a model of AP and is stored and managed by the controller. It contains base/default settings and applies them to adopted APs. Therefore, the method of configuring settings specific to a device (access point) is thus to configure device overrides that override the system profile. For example, the system profile sets the following:

  • Have the device acquire an IP address by DHCP.
  • Only VLAN 1 enabled by default, port type is Access.
  • Turn off the 2.4GHz radio, turn on the 5GHz radio with auto channel and auto power.
  • No SSIDs are mapped to either radio

Configuring the device overrides, the settings for a particular AP would then be as follows:

  • AP is set with a static IP.
  • Ge0 (ethernet port) of AP is set as a VLAN trunk, with VLAN 1 being native, and VLAN 2 being tagged on the port.
  • 2.4GHz radio is activated if necessary, 5GHz radio is set to a custom channel and power.
  • Select SSIDs are mapped accordingly, as BSSIDs on either or both radios.
  • Device name is configured.

The system profile in use - given we have only 1 type of access point - is called default-ap7532.

Of course, only a fraction of the settings need to be overridden, so the settings a device will consist of the those applied from the system profile, plus those configured as overrides.

Administration

Web GUI: https://172.30.18.80
Login: (username/password found here)

For the most part, there is little administration to be done, as wireless is a set-and-forget type of deal (especially when the platform and devices are very stable). To monitor WiFi health (but specifically, RF gun performance) check these two areas:

Wireless Networks

These settings are provided here for convenience but may change at any time in the future. Log in to the web GUI to verify actual settings.
SSID Purpose Authentication VLAN office_2ndflr 2.4GHz office_2ndflr 5GHz office_1stflr 2.4GHz office_1stflr 5GHz dc_hhc 2.4GHz dc_hhc 5GHz dc_largedown 2.4GHz dc_largedown 5GHz dc_receiving 2.4GHz dc_receiving 5GHz
uwd_dcrf Warehouse RF Guns, Mobile printers (Receiving) WPA2-PSK, shared key: uwdrf2051 1 on on on
uwd_guest Guest Access Captive Portal 2 on on on on on on
uwd Staff Access WPA2-PSK, shared key: unipharm 2 on on on on on on
uwd_z Privileged/Admin Access WPA2-PSK, shared key: visionit 1 on on on on on on

Wireless security

WPA2-PSK was deliberately chosen for all networks (except the guest WiFi, which has a captive portal) as it provides the best balance between convenience of administration, wireless performance, and security. Enterprise security (e.g. 802.1x) was deliberately avoided - the company is just too small to warrant going down this road.

Other/advanced features

  • BSSID mapping: Enterprise APs such as the WiNG AP 7532 will often allow multiple SSIDs mapped to a wireless radio as BSSIDs. This minimizes interference by allowing the same radio to broadcast several wireless networks serving different purposes.
  • Antenna diversity: Antenna diversity is enabled on the 2.4GHz of some access points as an experimental setting (it's disabled by default).


Web GUI layout

The reason for the seemingly complicated layout of the Web GUI can be better understood when considered that the WiNG platform is designed for large-scale deployments that involve multiple sites and hundreds to thousands of APs. There is a reason WiNG Express (a dumbed down version of the software) is installed by default. Taking the time to go through each tab and section of the Web GUI is the best way to learn it. If not doing administration, the Statistics panel is perhaps the most useful.

Hardware support

Extreme Networks Web Portal: https://extremeportal.force.com (username/password found here)

Tickets can be submitted via the web portal.

The 6 APs are covered under Limited Lifetime Warranty support under Extreme. There are maintenance contracts and software upgrade/support entitlements that can be purchased on a per-device, per-year basis - they are currently being explored. The fact is that these units are both fairly easy to acquire and expected to be quite stable, so common sense dictates that "Next Business Day" hardware replacement options would be excessive in this situation (not to mention that we currently have a spare unit). However, if the ability to upgrade the firmware requires a software entitlement, then it would be in our best interest to obtain entitlements for all devices.

Other Notes

Acquisition of Zebra

The WiNG platform was originally a product by Motorola (their mobile enterprise division), which was acquired by Zebra. Zebra evolved the platform for several years, then their WLAN portfolio was acquired by Extreme Networks. From discussions with Extreme Networks reps, it seems they plan to continue with the WiNG platform despite having their own wireless platform (ExtremeWireless). They did hint at integration of the two at some point, perhaps from a management standpoint (i.e. converging the software to be able to manage both types of APs).

WiNG vs WiNG Express

WiNG Express is a scaled down version of WiNG. The 7532 APs actually use WiNG Express as a default. Upon inspection, WiNG Express appeared too simplistic. A CLI command exists to switch to WiNG from the default WiNG Express.

Wireless performance and future optimization

Since the primary objective of the wireless infrastructure upgrade was to solve the connectivity issues with the RF guns, no analysis of throughput and latency has been conducted. In fact, wireless coverage (signal strength), was the only factor taken into consideration in the placement and settings configuration during initial implementation.

Wireless QoS and Fast Transition (802.11r) is something to be explored in the future if the plan to use VoIP cordless phones comes to being.

Wireless site survey

A site survey was strongly considered, but in the end was forgone. It was determined that it was just not necessary given the particularly low requirements of our current wireless needs. It may be considered in the future should the requirements change (e.g. a need to support VoIP).

Power outages

Power outages remove the AP names in the web interface. This is for sure a glitch.

On a brighter note, on October 2, 2017, a power outage was experienced, downing several APs, including the controller. However, there were no calls from the warehouse. One AP must be on the UPS and supported all users at that point. The system came up gracefully when power was restored. Therefore, the group of APs as a unit have proven to be quite resilient and each recovering its configuration elegantly when the controller comes back up.