Interoperability report Ascom Ruckus SCG i62 3.5 R1 · 2017-06-21 · Interoperability Report -...

Interoperability Report - Ascom i62 – Ruckus SmartZone Platform 1 2017-06-15

INTEROPERABILITY REPORT Ascom i62 Ruckus Wireless SmartZone, R300, R310, R500, R510, R600, R610, R710, T300, 7372, 7982 access points i62 and OEM derivatives version 5.5.0

Ruckus SmartZone Plattform version 3.5.0.0.808

Ascom, Gothenburg

June 2017

[ ]


TABLE OF CONTENT: INTRODUCTION ........................................................................................................................... 3

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

SUMMARY .................................................................................................................................... 5 Known issues and limitations .................................................................................................... 6 Compatibility information .......................................................................................................... 6

APPENDIX A: TEST CONFIGURATIONS .................................................................................... 7 Ruckus Wireless SmartZone version 3.5.0.0.808 ..................................................................... 7

Security settings (PSK) ......................................................................................................... 8 Security settings (802.1X / PEAP-MSCHAPv2) .................................................................. 11 General settings (QoS, Radio) ............................................................................................ 14 CLI commands .................................................................................................................... 16

APPENDIX B: DETAILED TEST RECORDS .............................................................................. 19


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 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,200 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 Test Site: Ascom US 300 Perimeter park drive Morrisville, NC, US-27560 USA Participants: Karl-Magnus Olsson, Ascom HQ, Gothenburg Sweden TEST TOPOLOGY


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 87ms)* Roaming, PEAP-MSCHAPv2 Auth, AES Encryption OK (Typical roaming time 86ms)* /** *) 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)


Known issues and limitations

- 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. Problem is currently being investigated further by Ascom and Ruckus. Refer to Ascom ticket INTOP-60

- Observe 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 R510 and R610 while a less extensive test was performed on the already known access points 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 access ports with Ruckus Wireless version SmartZone 3.5.0.0.808: ZoneFlex R300, R310, R500, R510, R600, R610, R710, T310 ZoneFlex 7372 / 7982 Supported controller platforms with Ruckus Wireless version SmartZone 3.5.0.0.808: Virtual SmartZone H (vSZ-H) Virtual SmartZone E (vSZ-E) Virtual SmartZone D (vSZ-D) SmartCell Gateway SmartZone 100


APPENDIX A: TEST CONFIGURATIONS

Ruckus Wireless SmartZone version 3.5.0.0.808 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


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


Recommended i62 setting.

Network settings for WPA2-PSK


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.


APPENDIX B: DETAILED TEST RECORDS VoWIFI Pass 15 Fail 0 Comments 1 Untested 5 Total 21 Above results are valid for R510 and R610. 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


Document History Rev Date Author DescriptionPA 2017-06-01 SEKMO Draft 1 R1 2017-06-14 SEKMO Corrections after review. Revision R1

WLAN TR

WLAN Interoperability Test ReportWLAN configuration:

Beacon Interval: 100ms

Test object - Handset:DTIM Interval: 5

Ascom i62 5.5.0802.11d Regulatory Domain: World

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

Ruckus Smartzone 3.5.0.0.808No Auto-tune

AP 710, 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 encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASS

#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 TESTEDPASSPASSNOT TESTEDNOT TESTEDPASSPASSNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDFAIL

#151Beacon period and DTIM intervalSee CommentSee CommentSee CommentSee CommentSee CommentSee CommentSee CommentSee CommentSee CommentSee CommentSee CommentSee CommentSee CommentSee CommentOny DTIM 1, 5 tested due to configuration via CLI. Beacon Period 100tuNOT TESTED

#152802.11e U-APSDPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSSee Comment

#202WMM prioritizationNOT TESTEDNOT TESTEDPASSPASSNOT TESTEDNOT TESTEDPASSPASSNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDiperf used to generate backgound load.

TEST AREA "PERFORMANCE"

#308Power-save mode U-APSD – WPA2-PSKPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASS12hs ok on one single radio. Note that 12 was not the limit.

#310CAC - TSPECNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNot supported by SmartZone

TEST AREA ROAMING AND HANDOVER TIMES

#401Handover with open authentication and no encryptionNOT TESTEDNOT TESTEDPASSPASSNOT TESTEDNOT TESTEDPASSPASSNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDAVG 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 encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSAVG roaming time 11an:87ms, bgn: 83ms (No significant difference seen in roaming times between different AP models)

#408Handover with PEAP-MSCHAPv2 authentication and AES-CCMP encryptionPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSAVG roaming time 11an: 86ms, bgn: 88ms (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 TESTEDPASSPASSNOT TESTEDNOT TESTEDPASSPASSNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED80-95hours. DTIM 5. Non-DFS channels only. QTIME had to be changed for optimal battery life

#504Battery lifetime in call with power save mode U-APSDNOT TESTEDNOT TESTEDPASSPASSNOT TESTEDNOT TESTEDPASSPASSNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTEDNOT TESTED12-14h

TEST AREA STABILITY

#602Duration of call – U-APSD modePASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASS24h call maintained 510 and R610 (New HW). Already tested Aps 1h+

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 TESTEDUplink and downlink.

#80440Mhz channelsNOT TESTEDPASSNOT TESTEDPASSNOT TESTEDPASSNOT TESTEDPASSNOT TESTEDPASSNOT TESTEDPASSNOT TESTEDPASSonly 20MHz channel width tested on 2.4GHz band

#805802.11n ratesPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSPASSUplink and downlink.

look at uapsd deliver AP710

Interoperability report Ascom Ruckus SCG i62 3.5 R1 · 2017-06-21 · Interoperability Report -...

Documents

Transcript of Interoperability report Ascom Ruckus SCG i62 3.5 R1 · 2017-06-21 · Interoperability Report -...