Interoperability Report: Alcatel-Lucent OT8118/8128 Ruckus Wireless ZF7962, 7363, 7341, 7343, 7372, 7982 and R300 AP's
Interoperability Report: Alcatel-Lucent OT8118/8128 Ruckus Wireless ZF7962, 7363, 7341, 7343, 7372, 7982 and R300 AP's
Alcatel-Lucent OT8118/8128
Ruckus wireless ZF7962, 7363, 7341, 7343, 7372, 7982 and R300
AP’s
Alcatel-Lucent OT81x8 version 5.1.30
Ruckus wireless version 9.7.1.0.17
8AL90483USAB Ed.01
July 2014
INTRODUCTION ........................................................................................................................... 3
About Alcatel-Lucent................................................................................................................. 3
About Ruckus Wireless ............................................................................................................. 3
SITE INFORMATION .................................................................................................................... 4
SUMMARY .................................................................................................................................... 5
Known issues............................................................................................................................ 6
Compatibility information .......................................................................................................... 6
General conclusion ................................................................................................................... 6
TEST RESULTS............................................................................................................................ 7
APPENDIX A: TEST CONFIGURATIONS .................................................................................... 8
Ruckus Wireless ZD 3000 version 9.7.0.220............................................................................ 8
Security settings (PSK) ......................................................................................................... 8
Security settings (802.1X / PEAP-MSCHAPv2) .................................................................. 10
General settings (QoS, Radio) ............................................................................................ 14
CLI commands .................................................................................................................... 16
Alcatel-Lucent OT81x8........................................................................................................ 17
APPENDIX B: DETAILED TEST RECORDS .............................................................................. 19
This document describes necessary steps and guidelines to optimally configure Ruckus wireless platform
with Alcatel-Lucent OT81x8 WLAN handsets.
The guide should be used in conjunction with both Ruckus and Alcatel-Lucent’s configuration guide(s).
About Alcatel-Lucent
The Alcatel-Lucent OmniTouch 8118/8128 WLAN handsets offer a sleeker design, high-resolution color
TFT display (OT8128), IP44 compliant construction, and longer battery time. OT 8118/8128 handsets
can be managed over-the-air (OTA) and are designed to interoperate within a Wi-Fi network. With the
OT 8118/8128 WLAN handsets, users get a mobile device for voice conversations, text messaging and
alarms from Alcatel-Lucent Call Servers and third party Alarm servers.
The Ruckus ZoneFlex system is a centrally managed WLAN system comprising of controllers and a
variety of 802.11 a/b/g/n APs. There are two unique features in the ZoneFlex product that enhance voice
communications. One is BeamFlex, our smart beamforming antennas, and the second is SmartCast, our
traffic management engine. Combining a compact internal antenna array with expert control software,
BeamFlex continuously ranks the antenna configurations for each receiving device and reconfigures itself
in real-time to bypass interference and physical barriers. SmartCast provides automatic flow
classification, software pre-queuing per station and per packet scheduling of traffic over the smart
antenna array. It applies heuristics to automatically classify voice packets and place them in the right
queue.
Test Site:
Ascom US
598 Airport Blvd, Suite 300
Morrisville, NC, US-27560
USA
Participants:
Karl-Magnus Olsson, Ascom HQ, Gothenburg Sweden
TEST TOPOLOGY
Roaming
High Level Functionality Result
Roaming, Open with No Encryption OK
Roaming, WPA-PSK, TKIP Encryption OK (Typical roaming time 218ms)*
Roaming, WPA2-PSK, AES Encryption OK (Typical roaming time 245ms)*
Roaming, PEAP-MSCHAPv2 Auth, AES Encryption OK (Typical roaming time 34ms)* /**
*) Average roaming times are measured using 802.11bgn on ZF7982. Refer to Appendix B for detailed test results
- Note that the “qtime” settings described in the “CLI settings” section is necessary for optimal
battery life.
For additional information regarding the known issues please contact Alcatel-Lucent technical
support.
Compatibility information
A full test round was performed on ZF7982 and ZF7372 while a less extensive test was performed on the
already known access points ZF 7962 and ZF 7363. All test were done with a ZD3000 controller. We
ensure compatibility/interoperability with all the access points and controllers listed below given that they
run the software tested.
ZoneFlex 7962
ZoneFlex 7363
ZoneFlex 7341/7343 (Single radio versions of 7363)
ZoneFlex 7372
ZoneFlex 7982
ZoneFlex R300
ZoneDirector 1100
ZoneDirector 3000
ZoneDirector 5000
General conclusion
With the exception of roaming time (WPA1/2-PSK), verified test areas, such as authentication,
association, handover and call stability tests, all produced good results. Roaming times with were in the
range of 200-250ms for both WPA2-PSK AES and WPA-PSK TKIP. However, when using .1X
authentication roaming times were a good 34ms in average.
The outcome of the load test was in general acceptable. In both active and U-APSD mode it was possible
to keep up 14 simultaneously calls per AP one single access point.
Software Versions:
Ruckus Wireless ZD 3000 version 9.7.1.0.17
ZF 7962 / 7363 / 7341 / 7343 / 7372 / 7983 / R300 access points
Alcatel-Lucent OT81x8, v5.1.30 (WLAN driver 3.5.f)
Keep in mind that security options and power save modes were adjusted according to requirements in
individual test cases. Please refer to appendix A for information regarding device configuration.
In the following chapter you will find screenshots and explanations of basic settings in order to get a
Ruckus WLAN system to operate with Alcatel-Lucent OT81x8. Please note that security settings were
modified according to requirements in individual test cases.
AAA server dashboard. In the example one Radius servers configured (Interop). See next picture for
configuration of the profile “Interop”.
Note. Depending on which Authentication method used it might be necessary to add a certificate
into the OT81x8. PEAP-MSCHAPv2 requires a Root certificate and EAP-TLS requires both a Root
certificate and a client certificate. Server certificate validation can be overridden in version 4.1.12
and above per handset setting.
Note. Refer to the OT81x8 section in Appendix A for matching handset configurations.
Note that in this example the TX power have been modified in order to facilitate roaming in a small area.
General guidelines when deploying Alcatel-Lucents OT81x8 handsets (SW version 2.5.7 or later)
in 802.11a/n/ac environments:
1. Enabling more than 8 channels will degrade roaming performance. Alcatel-Lucent strongly
recommends against going above this limit.
2. Using 40 MHz channels (or “channel-bonding”) will reduce the number of non-DFS*
channels to two in ETSI regions (Europe). In FCC regions (North America), 40MHz is a
more viable option because of the availability of additional non-DFS channels. The
handset can co-exist with 40MHz stations in the same ESS.
3. Make sure that all non-DFS channel are taken before resorting to DFS channels. The
handset can cope in mixed non-DFS and DFS environments; however, due to
“unpredictability” introduced by radar detection protocols, voice quality may become
distorted and roaming delayed.
DTIM
DTIM 5 value is recommended in order to allow maximum battery conservation without impacting the
quality. Using a lower DTIM value is possible but will reduce the standby time slightly.
get wlanlist
The dtim-period setting can be done either by SSH to each access point or via the controller to all
access points with the command below.
Qtime
To increase the battery standby time Alcatel-Lucent and Ruckus recommends that the qtime parameter is
adjusted. This will increase the standby time from ~40hours to ~100hours.
The qtime setting can be done either by SSH to each access point or via the controller to all
access points with the command below.
If 802.1X Authentication is used a root certificate has to be uploaded to the phone by “right clicking” - >
Edit certificates.
Note that both a root and a client certificate are needed for TLS. Otherwise only a root certificate
is needed. Server certificate validation can be overridden in version 4.1.12 and above per handset
setting (Validate server certificate).
VoWIFI
Pass 25
Fail 0
Comments 2
Untested 5
Total 33