ascom i62 ruckus wireless€¦ · indoor and outdoor environments. its smart wi-fi platform...

Interoperability Report

Ascom i62 Ruckus Wireless

SmartZone platform

Ruckus SZ v. 3.5.1.0

Ascom i62 v. 6.0.1

Morrisville, NC, USA

November 2017

Interoperability Report Date Page Ascom i62 – Ruckus Wireless SmartZone 2017-10-03 2 / 21

Contents

Introduction ......................................................................................................................................... 3

About Ascom ..................................................................................................................................... 3

About the Ruckus Wireless Business Unit ........................................................................................ 3

Site Information ................................................................................................................................... 4

Verification site .................................................................................................................................. 4

Participants ........................................................................................................................................ 4

Verification topology .......................................................................................................................... 4

Summary .............................................................................................................................................. 5

General conclusions .......................................................................................................................... 5

Compatibility information ................................................................................................................... 5

Verification overview .......................................................................................................................... 6

Known limitations ............................................................................................................................... 7

Appendix A: Verification Configurations ......................................................................................... 8

Ruckus Wireless SmartZone version 3.5.1.0.862 ............................................................................. 8

Ascom i62 ........................................................................................................................................ 18

Appendix B: Detailed Verification Records ................................................................................... 21

Document History ............................................................................................................................. 21


Introduction This document describes a summary of the interoperability verification results of the Ascom’s and Ruckus Wireless platform, necessary steps and guidelines to optimally configure the platforms and support contact details. The report should be used in conjunction with both Ruckus Wireless and Ascom’s platform configuration guides.

About Ascom Ascom is a global solutions provider focused on healthcare ICT and mobile workflow solutions. The vision of Ascom is to close digital information gaps allowing for the best possible decisions – anytime and anywhere. Ascom’s mission is to provide mission-critical, real-time solutions for highly mobile, ad hoc, and time-sensitive environments. Ascom uses its unique product and solutions portfolio and software architecture capabilities to devise integration and mobilization solutions that provide truly smooth, complete and efficient workflows for healthcare as well as for industry, security and retail sectors.

Ascom is headquartered in Baar (Switzerland), has subsidiaries in 15 countries and employs around 1,300 people worldwide. Ascom registered shares (ASCN) are listed on the SIX Swiss Exchange in Zurich.

About the Ruckus Wireless Business Unit Ruckus Wireless delivers simply better wireless networking—and now wired switching as well—for enterprise, service provider, government and small business customers worldwide. The Ruckus Wireless Business Unit of Brocade is focused on technology innovation, partner ecosystems and customer service—yielding the best possible wireless or wired 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. The Ruckus ICX 7000 Family Switches provide flexible scalability and simplified management, meeting the needs of businesses and organizations of all types and sizes.

About Brocade Brocade® (NASDAQ: BRCD) networking solutions help the world’s leading organizations turn their networks into platforms for business innovation. With solutions spanning public and private data centers to the network edge, Brocade is leading the industry in its transition to the New IP network infrastructures required for today's era of digital business. (www.brocade.com)


Site Information

Verification site Ascom US 300 Perimeter park drive Morrisville, NC, US-27560 USA

Participants Karl-Magnus Olsson, Ascom, Morrisville

Verification topology


Summary

General conclusions With no new hardware the performed test has been following the less extensive regression test suite. For example, capacity test and battery measurements have been left out. For test cases left out we consider the test results from previous full test valid.

Test cases, such as authentication and roaming and power save have howerver all been succesful. Observe that the Qtime and DTIM settings described in the “CLI commands” chapter is still necessary for optimal battery life.

Compatibility information Based on the R510, R610, R310, R500, R710, 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.

Supported Partner Access Points with Ruckus Wireless version SmartZone 3.5.1.0.862:

ZoneFlex R300, R310, R500, R510, R600, R610, R710, T310

ZoneFlex 7372 / 7982

Supported controller platforms with Ruckus Wireless version SmartZone 3.5.1.0.862: Virtual SmartZone H (vSZ-H)

Virtual SmartZone E (vSZ-E)

Virtual SmartZone D (vSZ-D)

SmartCell Gateway

SmartZone 100


Verification overview

WLAN Compatibility and Performance

High Level Functionality Result Comments

Association, Open with No Encryption OK

Association, WPA2-PSK / AES Encryption OK

Association, PEAP-MSCHAPv2 Auth, AES Encryption OK

Association with EAP-TLS authentication OK

Association, Multiple ESSIDs OK

Beacon Interval and DTIM Period OK

PMKSA Caching OK

WPA2-opportunistic/proactive Key Caching OK

WMM Prioritization OK

802.11 Power-save mode OK

802.11e U-APSD OK

802.11e U-APSD (load test) OK

Roaming, WPA2-PSK, AES Encryption OK * Typical roaming time 82 ms

Roaming, PEAP-MSCHAPv2 Auth, AES Encryption OK ** Typical roaming time 93 ms

*) Average roaming times are measured using 802.11a/n. Refer to Appendix B for detailed test results

* *) Measured times is with opportunistic/proactive Key Caching enabled (default enabled)


Known limitations Description and Consequence Workaround Ticket(s)

raised It has been noticed that the delta time between the re-association response and the M1 EAPOL key from the AP is sometimes higher than expected (up to 30-40ms). However, even with this delay the roaming time is within the upper bound of 150ms for VoWiFi and will typically not be noticed in a normal user scenario. Refer to the appendix B for detailed roaming times.

N/A Ascom ticket MRS-103

For additional information regarding the known limitations please contact [email protected] or [email protected]. For detailed verification results, refer to Appendix B: Detailed Verification Records.


Appendix A: Verification Configurations

Ruckus Wireless SmartZone version 3.5.1.0.862 In the following chapter you will find screenshots and explanations of basic settings in order to get a Ruckus Smartzone 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


Security settings (PSK)

Wireless LAN overview.


Example of how to configure the system for PSK security (WPA2-AES)

Continued. Example of how to configure the system for PSK security (WPA2-AES)


The Advanced Options are left as default

- Enable Proxy ARP - Make sure 802.11k Neighbor report is disabled


Security settings (802.1X / PEAP-MSCHAPv2)

Example of how to configure the system for .1X authentication.

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.


Configuration of ESS profile for utilization of 802.1X authentication.

Continued. 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.


General settings (QoS, Radio)

Access Points Common Settings per AP group.

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 i62 handsets in 802.11a/n/ac environments:

1. Enabling more than 8 channels will degrade roaming performance. In situations where UNII1 and UNII3 are used, a maximum of 9 enabled channels can be allowed. Ascom does not recommend exceeding 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)


Individual AP configuration

Channel and Tx power override was used to create suitable cell overlap for test purposes.


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

Network settings for WPA2-PSK

Note. Make sure that the enabled channels in the i62 handset match the channel plan used in the system.

Note. FCC is no longer allowing 802.11d to determine regulatory domain. Devices deployed in USA must set Regulatory domain to “USA”.


Network settings for .1X authentication (PEAP-MSCHAPv2)


802.1X Authentication requires a CA certificate to be uploaded to the phone by “right clicking” - > Edit certificates. EAP-TLS will require both a CA and a client certificate.

Note that both a CA 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.


Appendix B: Detailed Verification Records Pass Fail Comments Not verified

10 0 0 11

Total 21

Refer to the attached file for detailed verification results.

Refer to the verification specification for explicit information regarding each verification case. The specification can be found here (requires login): https://www.ascom-ws.com/AscomPartnerWeb/en/startpage/Sales-tools/Interoperability/Templates/

Document History

Rev Date Author Description P1 16-Nov-17 SEKMO Draft R1 8-Dec-17 SEKMO Correction after review. Revision R1.

WLAN TR

WLAN Interoperability Test ReportWLAN configuration:

Beacon Interval: 100ms

Test object - Handset:DTIM Interval: 5

Ascom i62 6.0.1802.11d Regulatory Domain: World

Test object - WLAN system:WMM Enabled (Auto/WMM)

Ruckus Smartzone 3.5.1.0.862No Auto-tune

AP 710, 610, 510, 500, 310, 7982, 7372R710R610R500R510R31079827372Single Voice VLAN

2.4Ghz5.0Ghz2.4Ghz5.0Ghz2.4Ghz5.0Ghz2.4Ghz5.0Ghz2.4Ghz5.0Ghz2.4Ghz5.0Ghz2.4Ghz5.0Ghz

Test CaseDescriptionVerdictVerdictVerdictVerdictVerdictVerdictVerdictVerdictVerdictVerdictVerdictVerdictVerdictVerdictComment

TEST AREA ASSOCIATION / AUTHENTICATION

#101Association with open authentication, no encryptionNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED

#107Association with WPA2-PSK authentication, AES-CCMP encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASS

#110Association with PEAP-MSCHAPv2 auth, AES-CCMP encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSFreeRADIUS server; RootCA loaded to device; Handset autheticates twiceFAIL

#116Association with EAP-TLS authenticationPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSFreeRADIUS server; RootCA and clients certificate loaded to device

TEST AREA POWER-SAVE AND QOSPASS

#150802.11 Power-save modeNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDFAIL

#151Beacon period and DTIM intervalNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED

#152802.11e U-APSDPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSSee Comment

#202WMM prioritizationPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSiperf used to generate backgound load.

TEST AREA "PERFORMANCE"

#308Power-save mode U-APSD – WPA2-PSKNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED

#310CAC - TSPECNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED

TEST AREA ROAMING AND HANDOVER TIMES

#401Handover with open authentication and no encryptionNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED

#404Handover with WPA2-PSK auth and AES-CCMP encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSAVG roaming time 11an:82ms, bgn: 87ms (No significant difference seen in roaming times between different AP models)

#408Handover with PEAP-MSCHAPv2 authentication and AES-CCMP encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSAVG roaming time 11an: 93ms, bgn: 98ms (No significant difference seen in roaming times between different AP models)

#411Handover using PMKSA and opportunistic/proactive key cachingPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSOKC always on. Same test as #408

TEST AREA BATTERY LIFETIME

#501Battery lifetime in idleNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED

#504Battery lifetime in call with power save mode U-APSDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED

TEST AREA STABILITY

#602Duration of call – U-APSD modePASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASS1h call maintained

TEST AREA 802.11n

#801Frame aggregation A-MSDUNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED

#802Frame aggregation A-MPDUNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED

#80440Mhz channelsNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED

#805802.11n ratesPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSUplink and downlink.

look at uapsd deliver AP710

ascom i62 ruckus wireless€¦ · indoor and outdoor environments. its smart wi-fi platform...

Documents