Interoperability Report - Ascom Myco / Aerohive Networks 1 2016-08-24 INTEROPERABILITY REPORT Ascom Myco Aerohive Networks, AP130, 230, 250, 330, 350, HiveOS version 6.8r3 (Ap 130/230 – 6.8.r1, AP330/350 - 6.541, AP 250 – 7.0r1) Ascom Myco version 5.5.0 Ascom, Gothenburg August 2016 [ ]
25
Embed
INTEROPERABILITY REPORT Ascom Myco Aerohive …media.boundless.aerohive.com/documents/Interoperability+Report... · relevant here since testing homes in on interoperability in relation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
TABLE OF CONTENT: INTRODUCTION ........................................................................................................................... 3
About Ascom ............................................................................................................................ 3 About Aerohive Networks ......................................................................................................... 3
SITE INFORMATION .................................................................................................................... 4 SUMMARY .................................................................................................................................... 5
General conclusion ................................................................................................................... 6 Known issues ............................................................................................................................ 6
APPENDIX A: TEST CONFIGURATIONS .................................................................................... 7 Aerohive HiveManager and Access Points configurations. ...................................................... 7
ESS, Security settings. .......................................................................................................... 7 Quality of Service (QoS) ..................................................................................................... 13 Radio Configuration ............................................................................................................ 15
INTRODUCTION This document describes necessary steps and guidelines to optimally configure the Aerohive Networks solutions WLAN platform with Ascom Myco handsets.
The guide should be used in conjunction with both Aerohives and Ascoms configuration guide(s).
About Ascom
Ascom Wireless Solutions (www.ascom.com/ws) is a leading provider of innovative communication solutions providing integrated workflow intelligence for hospitals, senior care, and independent living, and other business areas where mission-critical communication is essential. Approximately 100 000 systems are installed globally. The company offers a broad range of voice and professional messaging solutions, creating value for customers by supporting and optimizing their mission-critical communication processes. The solutions are based on Cellular, VoWiFi, IP-DECT, Nurse call and Paging technologies, smartly integrated via Ascom Unite into existing enterprise systems. The company has subsidiaries in 13 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 (ASCN:SIX).
About Aerohive Networks Aerohive (NYSE: HIVE) enables our customers to simply and confidently connect to the information, applications, and insights they need to thrive. Our simple, scalable, and secure platform delivers mobility without limitations. For our customers worldwide, every access point is a starting point. Aerohive was founded in 2006 and is headquartered in Milpitas, CA. For more information, please visit www.aerohive.com, call us at 408-510-6100, follow us on Twitter @Aerohive, join our LinkedIn group, subscribe to our blog http://boundless.aerohive.com/, or become a fan on our Facebook page.
Please refer to Appendix B for detailed results for respective access point. WLAN 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
*) Enabled by default Roaming
High Level Functionality Result
Roaming, Open with No Encryption OK (typical roaming time 12ms) *
Roaming, WPA2-PSK, AES Encryption OK (Typical roaming time 29ms)*
Roaming, PEAP-MSCHAPv2 Auth, AES Encryption OK (Typical roaming time 26ms)* /**
*) Average roaming times are based on results from 802.11a/n. Refer to Appendix B for detailed test results * *) Measured times is with opportunistic/proactive Key Caching enabled (default enabled)
General conclusion The result of the verified test areas, such as authentication, association, handover and call stability test, produced very good results. The roaming times, both PSK and 802.1x were excellent by ranging in the interval 20 to 30ms. Performance has also been proven to be very good. In both active and U-APSD mode it was possible to keep 12 simultaneously calls per AP radio. Keep in mind that the limitation was available handsets and not system capacity.
Known issues
Stability issues with Aerohive AP 370/390 (6.5r4). AP 370/390 (6.5r4) is not supported by
Ascom. Refer to previous certifications for stable firmware. For additional information regarding the known issues please contact [email protected] or [email protected]
Aerohive HiveManager and Access Points configurations.
In the following chapter you will find screenshots and explanations of basic settings in order to get the Aerohive Networks solution operational with Ascom Myco. Please note that security settings were modified according to requirements in individual test cases. The configuration file is found at the bottom of this chapter. ESS, Security settings.
- Select WPA/WPA2 PSK (Personal) - Select WPA2-PSK and CCMP (AES) as Key Management and Encryption Method - Key can be entered in HEX or in ASCII format. Example shows a key entered in ASCII format.
- Select WPA/WPA2 802.1X (Enterprise) - Select WPA2-802.1X and CCMP and Key Management and Encryption Method - Make sure Enable Proactive PMK ID response is checked.
Advanced SSID settings (Same for all encryption methods)
- Set the DTIM settings to 5. DTIM value 5 is recommended in order to allow maximum battery conservation without impacting the quality. A lower value is possible but will negatively impact the standby time.
- Make sure that “Enable WMM” is checked. - Make sure that “Enable Unscheduled Automatic Power Save Delivery” is checked.
WMM and U-APSD is required for Ascom Myco to function properly.
Note. Ascom Myco do not support 802.11k,v,r. Do not enable the Voice Enterprise parameters.
- Example shows the default profile radio_ng0 - Channel width is set to 20MHz. 40MHz channel width is not recommended on the 2.4GHz band. - Make sure the beacon period is set to 100TU
- Radio profiles used is the default (radio_na0 or radio_na0 for 11ac access point and radio_ng0). See earlier steps for configuration of the radio profiles.
- In the example channel and power level has been set manually for each access point (for testing).
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.
Innovaphone IP6000 (IP PBX) The Innovaphone IP6000 was configured with a static IP address of 172.20.106.113. Signaling is less relevant here since testing homes in on interoperability in relation to the WLAN infrastructure and not features of the IP PBX. IP6000 configuration: See attached file (complete-IP6000-08-03-a6.txt) for configuration.
APPENDIX B: DETAILED TEST RECORDS VoWIFI Pass 17 Fail 0 Comments 0 Untested 3 Total 20 See attached file (WLANinteroperabilityTestReport_Aerohive.xls) for detailed test results. MISCELLANEOUS 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