-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
1 2016-06-14
INTEROPERABILITY REPORT Ascom i62 Ruckus Wireless SmartZone,
R300, R310, R500, R600, R710, T300, 7372, 7982 access points i62
and OEM derivatives version 5.4.2
Ruckus SmartZone Plattform version 3.2.1.0.139
Ascom, Gothenburg
March 2016
[ ]
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
2 2016-06-14
TABLE OF CONTENT: INTRODUCTION
...........................................................................................................................
3
About Ascom
............................................................................................................................
3 About Ruckus Wireless
.............................................................................................................
3
SUMMARY
....................................................................................................................................
5 Known issues
............................................................................................................................
6 Compatibility information
..........................................................................................................
6 General conclusion
...................................................................................................................
6
APPENDIX A: TEST CONFIGURATIONS
....................................................................................
7 Ruckus Wireless SmartZone version 3.2.1.0.139
.....................................................................
7
Security settings (PSK)
.........................................................................................................
8 Security settings (802.1X / PEAP-MSCHAPv2)
..................................................................
10 General settings (QoS, Radio)
............................................................................................
12 CLI commands
....................................................................................................................
14
APPENDIX B: DETAILED TEST RECORDS
..............................................................................
17
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
3 2016-06-14
INTRODUCTION This document describes necessary steps and
guidelines to optimally configure Ruckus Wireless platform with
Ascom i62 VoWiFi handsets.
The guide should be used in conjunction with both Ruckus and
Ascoms configuration guide(s).
About Ascom Ascom Wireless Solutions (www.ascom.com/ws) is a
leading provider of on-site wireless communications for key
segments such as hospitals, elderly care, independent living,
manufacturing industries, secure establishments, retail and hotels.
More than 75,000 systems are installed at major companies all over
the world. The company offers a broad range of voice and
professional messaging solutions, creating value for customers by
supporting and optimizing their Mission-Critical processes. The
solutions are based on VoWiFi, IP-DECT, nurse call and paging
technologies, smartly integrated into existing enterprise systems.
The company has subsidiaries in 11 countries and 1,200 employees
worldwide. Founded in 1955 and based in Göteborg, Sweden, Ascom
Wireless Solutions is part of the Ascom Group, listed on the Swiss
Stock Exchange.
About Ruckus Wireless Ruckus Wireless delivers simply better
wireless for more than 65,300 enterprise, service provider,
government and small business customers worldwide. The company is
focused on technology innovation, partner ecosystems and customer
service - yielding the best possible wireless experience for the
most challenging indoor and outdoor environments. Its Smart Wi-Fi
platform delivers scalable, high-performance Wi-Fi with simplified
control and management for on-premise and cloud-based Wi-Fi
deployments, along with new services for secure on-boarding, policy
management, location services and analytics that enable new
business opportunities. Ruckus and Ruckus Wireless are trademarks
of Ruckus Wireless, Inc. in the United States and other countries.
All other product or company names may be trademarks of their
respective owners.
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
4 2016-06-14
SITE INFORMATION Test Site: Ascom US 300 Perimeter park drive
Morrisville, NC, US-27560 USA Participants: Karl-Magnus Olsson,
Ascom HQ, Gothenburg Sweden TEST TOPOLOGY
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
5 2016-06-14
SUMMARY Please refer to Appendix B for detailed results. WLAN
Controller Features
High Level Functionality Result Association, Open with No
Encryption OK Association, WPA2-PSK, AES Encryption OK Association,
PEAP-MSCHAPv2 Auth., AES Encryption OK Association, EAP-TLS Auth.,
AES Encryption OK Association, Multiple ESSIDs OK Beacon Interval
and DTIM Period OK PMKSA Caching OK WPA2-opportunistic/proactive
Key Caching OK WMM Prioritization OK Active Mode (load test) OK
802.11 Power-save mode OK 802.11e U-APSD OK 802.11e U-APSD (load
test) OK Roaming
High Level Functionality Result Roaming, Open with No Encryption
OK (Typical roaming time 24ms) Roaming, WPA2-PSK, AES Encryption OK
(Typical roaming time 48ms)* Roaming, PEAP-MSCHAPv2 Auth, AES
Encryption OK (Typical roaming time 58ms)* /** *) Average roaming
times are measured using 802.11an. Refer to Appendix B for detailed
test results * *) Measured times is with opportunistic/proactive
Key Caching enabled (default enabled)
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
6 2016-06-14
Known issues
- Note that the Qtime and DTIM settings described in the “CLI
commands” chapter is necessary for optimal battery life.
For additional information regarding the known issues please
contact [email protected] or [email protected]
Compatibility information A full test round was performed on
ZoneFlex R310, R500 and R710 while a less extensive test was
performed on the already known access points 7982 and 7363. All
test were done with a Virtual SmartZone E. We ensure
compatibility/interoperability with all the access points and
controllers listed below given that they run the software tested.
i62 version 5.4.2 is using WLAN driver version 3.6.h. Supported
access ports with Ruckus Wireless version SmartZone 3.2.1.0.139:
ZoneFlex R300, R310, R500, R600, R710, T310 ZoneFlex 7372 / 7982
Supported controller platforms with Ruckus Wireless version
SmartZone 3.2.1.0.139: Virtual SmartZone H (vSZ-H) Virtual
SmartZone E (vSZ-E) Virtual SmartZone D (vSZ-D) SmartCell Gateway
SmartZone 100
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 30-60ms for both
WPA2-PSK AES and .1X authentication. The outcome of the load test
was in general acceptable. In both active and U-APSD mode it was
possible to keep up 12 simultaneously calls per AP one single
access point. Note that 12 was not the limit.
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
7 2016-06-14
APPENDIX A: TEST CONFIGURATIONS
Ruckus Wireless SmartZone version 3.2.1.0.139 In the following
chapter you will find screenshots and explanations of basic
settings in order to get a Ruckus WLAN system to operate with an
Ascom i62. Please note that security settings were modified
according to requirements in individual test cases.
Virtual SmartZone Dashboard
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
8 2016-06-14
Security settings (PSK)
Example of how to configure the system for PSK security
(WPA2-AES)
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
9 2016-06-14
The Advanced Options are left as default
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
10 2016-06-14
Security settings (802.1X / PEAP-MSCHAPv2)
Example of how to configure the system for .1X authentication.
AAA server dashboard (Proxy AAA). In the example one Radius servers
configured (InteropFreeRADIUS). See next screen shot for
configuration of the profile “InteropFreeRADIUS”.
The IP address and the secret must correspond to the IP and the
credential used by the Radius server.
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
11 2016-06-14
Configuration of ESS profile for utilization of 802.1X
authentication. Authentication server “InteropFreeRADIUS”
corresponds to the server configured in previous step. Note.
Depending on which Authentication method used it might be necessary
to add a certificate into the i62. PEAP-MSCHAPv2 requires a CA
certificate and EAP-TLS requires both a CA 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
i62 section in Appendix A for matching handset configurations.
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
12 2016-06-14
General settings (QoS, Radio)
Access Points Common Settings. Ascom recommended settings for
802.11b/g/n are to only use channel 1, 6 and 11. For 802.11a/n/ac
use channels according to the infrastructure manufacturer and
country regulations. General guidelines when deploying Ascom Myco
handsets in 802.11a/n/ac environments:
1. Enabling more than 8 channels will degrade roaming
performance. Ascom 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. Ascom do support and can coexist in 80MHz channel bonding
environments. The recommendations is however to avoid 80Mhz channel
bonding as it severely reduces the number of available non
overlapping channels.
4. 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. Hence Ascom recommends if possible avoiding the
use of DFS channels in VoWIFI deployments.
*) Dynamic Frequency Selection (radar detection)
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
13 2016-06-14
Individual AP configuration
- Channel and Tx power override was used to create suitable cell
overlap for test purposes.
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
14 2016-06-14
CLI commands 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.
- First find the WLAN number in your system:
get wlanlist rkscli: get wlanlist name status type wlanID
radioID bssid
----------------------------------------------------------- wlan0
up AP wlan0 0 00:1d:2e:02:79:09 wlan1 up AP wlan1 0
00:1d:2e:42:79:09 Then apply the setting to all voice WLANs.
set dtim-period wlan0 5 set dtim-period wlan1 5 For
configuration of multiple access points please refer to Ruckus
TAC.
Qtime To increase the battery standby time Ascom and Ruckus
recommends that the qtime parameter is adjusted. This will increase
the standby time from ~40hours to ~100hours.
- Apply setting to the desired radio (2.4/5GHz) or both: set mq
wifi0 qtime 2000 2000 4000 4000 set mq wifi1 qtime 2000 2000 4000
4000 For configuration of multiple access points please refer to
Ruckus TAC.
Ascom i62
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
15 2016-06-14
Recommended i62 setting.
Network settings for WPA2-PSK
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
16 2016-06-14
Network settings for .1X authentication (PEAP-MSCHAPv2)
If 802.1X Authentication is used a root certificate has to be
uploaded to the phone by “right clicking” - > Manage
Certificates. EAP-TLS will require both a CA certificate and a
client certificate. Note that both a root and a client certificate
are needed for TLS. Otherwise only a CA certificate is needed.
Server certificate validation can be overridden in version 4.1.12
and above per handset setting.
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
17 2016-06-14
APPENDIX B: DETAILED TEST RECORDS VoWIFI Pass 19 Fail 0 Comments
1 Untested 1 Total 21 See attached file
(WLANinteroperabilityTestReport_Ruckus SZ.xls) for detailed test
results. Please refer to the test specification for WLAN systems on
Ascom’s interoperability web page for explicit information
regarding each test case. See URL (requires login):
https://www.ascom-ws.com/AscomPartnerWeb/en/startpage/Sales-tools/Interoperability
-
Interoperability Report - Ascom i62 – Ruckus SmartZone Plattform
18 2016-06-14
Document History Rev Date Author DescriptionPA 2016-03-08 SEKMO
Draft 1 PB 2016-03-14 SEKMO Corrections after Ruckus review. R1
2016-03-22 SEKMO Corrections after Ascom internal review. Revision
R1 R1a 2016-06-14 SEKMO Corrected typo T310 now T300.
WLAN TR
WLAN Interoperability Test ReportWLAN configuration:
Beacon Interval: 100ms
Test object - Handset:DTIM Interval: 5
Ascom i62 5.4.2802.11d Regulatory Domain: World
Test object - WLAN system:WMM Enabled (Auto/WMM)
Ruckus Smartzone 3.2.1.0.139No Auto-tune
AP 710, 500, 310, 7982, 7372R710R500R31079827372Single Voice
VLAN
2.4Ghz5.0Ghz2.4Ghz5.0Ghz2.4Ghz5.0Ghz2.4Ghz5.0Ghz2.4Ghz5.0Ghz
Test
CaseDescriptionVerdictVerdictVerdictVerdictVerdictVerdictVerdictVerdictVerdictVerdictComment
TEST AREA ASSOCIATION / AUTHENTICATION
#101Association with open authentication, no
encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASS
#107Association with WPA2-PSK authentication, AES-CCMP
encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASS
#110Association with PEAP-MSCHAPv2 auth, AES-CCMP
encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSFreeRADIUS
server; RootCA loaded to device; Handset autheticates twiceFAIL
#116Association with EAP-TLS
authenticationPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSFreeRADIUS
server; RootCA and clients certificate loaded to device
TEST AREA POWER-SAVE AND QOSPASS
#150802.11 Power-save
modePASSPASSPASSPASSPASSPASSPASSPASSPASSPASSFAIL
#151Beacon period and DTIM intervalPASSPASSPASSPASSPASSPASSNOT
TESTEDNOT TESTEDNOT TESTEDNOT TESTEDOny DTIM 1, 5 tested due to
configuration via CLI. Beacon Period 100tuNOT TESTED
#152802.11e U-APSDPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSSee
Comment
#202WMM prioritizationPASSPASSPASSPASSPASSPASSNOT TESTEDNOT
TESTEDNOT TESTEDNOT TESTEDiperf used to generate backgound
load.
TEST AREA "PERFORMANCE"
#308Power-save mode U-APSD – WPA2-PSKPASSPASSPASSPASSPASSPASSNOT
TESTEDNOT TESTEDNOT TESTEDNOT TESTED14hs ok on one single radio.
Note that 14 was not the limit.
#310CAC - TSPECSee CommentSee CommentSee CommentSee CommentSee
CommentSee CommentSee CommentSee CommentSee CommentSee CommentNot
supported by SmartZone
TEST AREA ROAMING AND HANDOVER TIMES
#401Handover with open authentication and no
encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSAVG roaming time
11an: 24ms, bgn: 29ms (No significant difference seen in roaming
times between different AP models)
#404Handover with WPA2-PSK auth and AES-CCMP
encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSAVG roaming time
11an:48ms, bgn: 50ms (No significant difference seen in roaming
times between different AP models)
#408Handover with PEAP-MSCHAPv2 authentication and AES-CCMP
encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSAVG roaming time
11an: 58ms, bgn: 55ms (No significant difference seen in roaming
times between different AP models)
#411Handover using PMKSA and opportunistic/proactive key
cachingPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSOKC always on. Same
test as #408
TEST AREA BATTERY LIFETIME
#501Battery lifetime in idlePASSPASSPASSPASSNOT TESTEDNOT
TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED80-95hours. DTM 5.
Non-DFS channels only. QTIME had to be changed for optimal battery
life
#504Battery lifetime in call with power save mode
U-APSDPASSPASSPASSPASSPASSPASSNOT TESTEDNOT TESTEDNOT TESTEDNOT
TESTED12-14h
TEST AREA STABILITY
#602Duration of call – U-APSD
modePASSPASSPASSPASSPASSPASSPASSPASSPASSPASS24h call maintained
TEST AREA 802.11n
#801Frame aggregation A-MSDUNOT TESTEDNOT TESTEDNOT TESTEDNOT
TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT
TESTED
#802Frame aggregation
A-MPDUPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSUplink and
downlink.
#80440Mhz channelsNOT TESTEDPASSNOT TESTEDPASSNOT TESTEDPASSNOT
TESTEDPASSNOT TESTEDPASSonly 20MHz channel width tested on 2.4GHz
band
#805802.11n ratesPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSUplink
and downlink.