Vocera WLAN Requirements and Best Practices. B3000n Compatible

Transcription

1 Vocera WLAN Requirements and Best Practices B3000n Compatible

2 Notice Copyright Vocera Communications, Inc. All rights reserved. Vocera is a registered trademark of Vocera Communications, Inc. This software is licensed, not sold, by Vocera Communications, Inc. ( Vocera ). The reference text of the license governing this software can be found at The version legally binding on you (which includes limitations of warranty, limitations of remedy and liability, and other provisions) is as agreed between Vocera and the reseller from whom your system was acquired and is available from that reseller. Certain portions of Vocera s product are derived from software licensed by the third parties as described at Microsoft, Windows, Windows Server, Internet Explorer, Excel, and Active Directory are registered trademarks of Microsoft Corporation in the United States and other countries. Java is a registered trademark of Oracle Corporation and/or its affiliates. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owner/s. All other brands and/or product names are the trademarks (or registered trademarks) and property of their respective owner/s. Vocera Communications, Inc. tel :: fax :: :24 ii VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

3 Contents WLAN Requirements and Best Practices... 4 WLAN s...4 Vocera Recommendations for Cisco CAPWAP...5 Vocera Recommendations for Aruba Networks... 6 Vocera Recommendations for Ruckus Networks...7 Vocera Recommendations for Meru Networks...8 IP Port Usage...9 Opening Ports for Communication...12 iii VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

4 WLAN Requirements and Best Practices This document summarizes the required settings and best practices for Vocera system implementations. You can find more detailed information in the Vocera Infrastructure Planning Guide, available for download at: WLAN s Table 1: Required WLAN s Voice Grade Site Survey B3000 Transmit Power (2.4GHz) B3000n Transmit Power (2.4GHz) B3000n Transmit Power (5 GHz) Minimum Power Coverage Required Value Required Max 15dBm (30mW) - Min 11dBm (12.5mW) Max 17dBm (50mW) - Min 12dBm (16mW) Max 16dBm (40mW) - Min 13dBm (20mW) -65dBm Minimum SNR 25 Beacon Interval 100 DTIM 1 Peer to peer blocking Public Secure Packet Forwarding ARP Cache Priority Queue Encryption If N Rates Are Used except for Autonomous APs Highest - Voice AES Radio Channel Utilization Consistent less than 30% Channel Width Guard Interval 2.4 GHz: 20MHz 5 GHz: 20MHz or 40MHz 2.4 GHz: Long 5 GHz: Long Table 2: Recommended WLAN s Code Version Basic Data Rates Supported Data Rates Use most recent version of Controller and AP code Needs to be determined for each site All 4 VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

5 WLAN REQUIREMENTS AND BEST PRACTICES Channel Plan 2.4 GHz: 1, 6, 11 5 GHz: 36, 40, 44, 48, 149, 153, 157, 161 Avoid channel 165 if possible Avoid DFS channels near an airport If you are using DFS channels, broadcast the SSID in beacons for B3000n benefit Roam Threshold 2 - May adjust based on AP density or Meru Virtual Cell Max Number of SSIDs 5 Client Exclusions Authentication Timeouts EAP Retry Timeout Add session timeout of at least 1 full shift 200 milliseconds or lower Max Retries 4 5 Ghz Channels in badge.properties (B3N.ChannelsToScan5G) Must match 5Ghz channels enabled in the controller Table 3: Multicast Recommendations IGMP on Badge IGMP V2 on Network Multicast Configuration PIM (Sparse Mode or Sparse Dense Mode) must be applied to all Vocera VLANs and the WLC management VLAN Enable IGMP Snooping on APs and all L2 devices in the multicast audio path Block all unnecessary multicast traffic Use Band Steering for data SSIDs to steer them towards a to reduce airtime contention Reverse Path Forwarding Table 4: Association Delays Caused by Authentication Authentication Type Association Delay Comments PSK < 100 ms PSK often provides the optimal trade-off between security and performance. EAP-FAST LEAP 200 ms Frequent session timeouts can result in additional delays Note: For EAP-FAST, use CCKM and OKC to cache credentials and optimize roaming times PEAP EAP-TLS Varies The association delay caused by authentication varies based on the cipher strength (1024 bit or 2048 bit) and the depth of certificate chains Note: For EAP-TLS, use CCKM and OKC to cache credentials and optimize roaming times Vocera Recommendations for Cisco CAPWAP Table 5: Cisco s RRM Dynamic Channel Assignment OK - Interval should be more than 8 hours (typical duration of one nursing shift) 5 VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

6 WLAN REQUIREMENTS AND BEST PRACTICES RRM Dynamic Transmit Power Control Transmit Power Threshold Coverage Hole Aggressive Load Balancing Multicast Mode Multicast Tx Data Rate Unicast-ARP WMM U-APSD DHCP Address Assignment Symmetric Mobility Tunneling Priority Queue Client Load Balancing Band Select CCKM Frame Aggregation Encryption if honoring the maximum and minimum transmit power levels Adjust to fit site - If Coverage Hole Detection is necessary, enable it with the following settings: Set Voice RSSI (-60 to -90 dbm) to -70 Set Min Failed Client Count per AP to 12 Multicast, Direct Disable Mobility Multicast Messaging if multicast is not properly enabled in network (causes one-way audio or no audio) Highest data rate Only have one Mandatory rate, fit to site. B3000n: B3000: Smartphone clients: B3000n: B3000: Smartphone clients: Platinum on transmit or receive for Traffic ID 6 (voice) and 7 (network control) Avoid WEP and TKIP Vocera Recommendations for Aruba Networks Table 6: Aruba s Minimum Controller Code Role ARM Voice Aware Scanning Voice if honoring the maximum and minimum transmit power levels Tx Data Rates 2.4 GHz: 6, 9, 11, 12, 18, 24 5 GHz: Enable 9Mbps and above; disable all lower rates Probe Retry Max Tx Failure 25 Session ACL vocera-acl 6 VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

7 WLAN REQUIREMENTS AND BEST PRACTICES Mcast-rate-opt (needed for multicast to go at highest rate) Multicast Filters - Use the Aruba Policy Enforcement Firewall (PEF) to configure these multicast filters to block traffic. netdestination HSRP Host netdestination VRRP host netdestination RIP host netdestination OSPF host host netdestination PIM host netdestination EIGRP host OKC Vocera Recommendations for Ruckus Networks Table 7: Ruckus s Tunnel traffic Channel fly (Self-Healing) QOS Smart-Roam VLAN Authentication/Encryption Wireless Client Isolation WLAN Background Scanning Power Level Directed-Multicast Band steering, load balancing Mesh Proxy ARP EAP Retry Timeout ARP Broadcast Filter DHCP Relay Agent Inactivity Timeout Minimum BSS Rate Hiding SSID in Beacons Controller Code High, Smartcast enabled on WLAN Dedicated non-native VLAN WPA2/AES (802.11i) 1/8 (25mW) using SSH / console CLI 200 milliseconds or lower 480 (8 hrs) Depends on AP density Not recommended Latest from Ruckus 7 VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

8 Vocera Recommendations for Meru Networks Table 8: Meru s WLAN REQUIREMENTS AND BEST PRACTICES SSID IGMP Snooping QoS Rules Virtual Port Virtual Cell 1 Separate for Vocera Enable QoS Rules 7 & 8 ( by Default) Badge Roaming Policy 1 Silent Client Polling Vocera Location Feature Multicast setting Disable Virtual Cell or divide APs into zones Configure UDP Broadcast Port 5555 for Badge Discovery for Meru 1 A Transmit Power Asymmetry problem may arise at the edges of Virtual Cell coverage if an AP s transmit power is higher than the Vocera device (~30mW). To avoid poor audio at the edges of the Virtual Cell, the RSSI of the Vocera device on the AP must be verified. The Vocera device should never drop below an RSSI of -75dBm on the AP. 8 VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

9 IP Port Usage The following tables indicates the ports used by Vocera system components for IP communication: Table 9: Vocera Server IP port usage Badge Server Signaling UDP 5002 Vocera SIP Telephony Gateway -> Vocera Server Signaling TCP 5001 Vocera Client Gateway -> Vocera Server Signaling TCP 5006 Badge Updater Signaling UDP 5400 Badge -> Vocera Server Audio UDP Max 2 Badge -> Vocera Server Audio Recording UDP Vocera SIP Telephony Gateway -> Vocera Server Audio UDP Vocera Client Gateway -> Vocera Server Audio UDP Browser Apache Signaling TCP 80 and 443 (for SSL) Apache Tomcat Connector TCP 8009 Tomcat HTTP Connector TCP 8080 MySQL Signaling TCP 3306 Vocera Server VMI Clients TCP 5005 Vocera Server VMI Clients (TLS) TCP 5007 Vocera Server VAI Clients TCP 5251 Vocera Server Vocera Report Server Signaling TCP 5251 Vocera Server Cluster Signaling TCP 5251 Badge Vconfig (Vch) Signaling during Discovery UDP 5555 and 5556 Badge Vconfig (Vch) Signaling during Connection TCP 5555 and 5556 Nuance Watcher Telnet Client TCP 7023 Nuance Watcher HTTP Client TCP 7080 Nuance Watcher UDP 7890 Nuance License Manager TCP Nuance Speech Server (listens) TCP 5060, 5062 Nuance Speech Server (allows UDP connections) TCP 5060, 5062 Nuance Recognition Server (nuance-server.exe) TCP The port range used is based on the number of licensed speech ports. 9 VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

10 IP PORT USAGE Nuance RTP signaling UDP Administration Console Vocera Server TCP 9091 Vocera Server CUCM JTAPI Signaling TCP 2748 Table 10: Vocera SIP Telephony Gateway IP port usage IP PBX Vocera SIP Telephony Gateway Signaling Vocera Server -> Vocera SIP Telephony Gateway Audio IP PBX -> Vocera SIP Telephony Gateway Audio (RTP/RTCP) UDP 5060 UDP UDP Vocera Server -> Vocera SIP Telephony Gateway Signaling TCP any free port Table 11: Vocera Client Gateway IP port usage Smartphone Vocera Client Gateway Signaling UDP 5060, Badge -> Vocera Client Gateway Audio Vocera Server -> Vocera Client Gateway Audio Vocera SIP Telephony Gateway -> Vocera Client Gateway Audio UDP Smartphone -> Vocera Client Gateway Audio (RTP/RTCP) UDP Vocera Server -> Vocera Client Gateway Signaling TCP any free port Table 12: MSP Server IP port usage MSP Console (Browser) IIS Web Server TCP 80 and 443 (for SSL) FTP Server Smartphone Note: Different ports are required based on the FTP mode used (Active vs. Passive). See below. TCP UDP 20 and 21 > 1023 Ports used when the FTP Server is in Passive Mode: FTP Server's port 21 from anywhere (Client initiates connection) FTP Server's port 21 to ports > The number of ports used is based on the number of lines configured. The maximum number of lines is 256 with one Vocera RTP port for each. The base port for this range is configurable. 4 The number of ports used is based on the number of lines configured. The maximum number of lines is 256 with 2 ports (RTP and RTCP) for each, or 512 total. The server multiplies 512 by 1.5 to reserve additional ports in case some ports are already in use, resulting in 768 ports. The base port for this range is configurable. 5 The number of ports used is based on the number of lines configured. 6 The number of ports used is based on the number of lines configured. 10 VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

11 IP PORT USAGE (Server responds to client's control port) FTP Server's ports > 1023 from anywhere (Client initiates data connection to random port specified by server) FTP Server's ports > 1023 to remote ports > 1023 (Server sends acknowledgments and data to client's data port) Ports used when the FTP Server is in Active Mode: FTP Server's port 21 from anywhere (Client initiates connection) FTP Server's port 21 to ports > 1023 (Server responds to client's control port) FTP Server's port 20 to ports > 1023 (Server initiates data connection to client's data port) FTP Server's port 20 from ports > 1023 (Client sends acknowledgements to server's data port) Table 13: Vocera Report Server IP port usage Vocera Server Vocera Report Server Signaling TCP 5251 Report Console (Browser) Apache Tomcat TCP 8080 Report Console Report server TCP 9090 Report results TCP 80 MySQL port TCP 3306 Table 14: Badge IP port usage Badge Server Signaling UDP 5002 Badge -> Vocera Server Audio Recording UDP Vocera Server -> Badge Audio Vocera SIP Telephony Gateway -> Badge Audio Badge -> Badge Audio UDP 5200 Badge Updater Signaling UDP 5400 Badge Vconfig (Vch) Signaling during Discovery UDP 5555 and 5556 Badge Vconfig (Vch) Signaling during Connection TCP 5555 and 5556 Table 15: Smartphone IP port usage Smartphone Vocera Client Gateway Signaling UDP 5060, Vocera Client Gateway -> Smartphone Audio (RTP) UDP FTP Server Smartphone UDP > VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

12 IP PORT USAGE Table 16: Vocera Collaboration Suite IP port usage Vocera Collaboration Suite Contacts TCP 80 or 443 (for SSL) iphone and Android Smartphone Vocera Client Gateway Signaling UDP 5060, iphone Audio UDP Android Audio UDP Opening Ports for Communication If a firewall separates Vocera servers from the wireless network, make sure the following ports are open for communication: Table 17: WLAN Ports Used by Vocera Clients Client Direction Server / Client Type Protocol Ports Badge VS Signaling UDP 5002 Badge Inbound VS Audio UDP / TCP Badge Badge/VS/VSTG Audio UDP 5200 Badge Inbound VSTG Audio UDP Badge Updater Signaling UDP 5400 Badge Badge VS Discovery UDP 5555 & 5556 VS Connection TCP 5555 & Badge Inbound VCG Audio UDP Badge Inbound VS Audio UDP Smartphone VCG Signaling UDP 5060 Smartphone VCG Audio UDP Smartphone Smartphone FTP Server MSP / FTP TCP 20 & 21 FTP Server MSP / FTP UDP > 1023 Smartphone, Vocera Collaboration Suite for Android and iphone Inbound VCG Audio UDP Smartphone, Vocera Collaboration Suite for Android and iphone Inbound VS Signaling (Comet push) TCP 80 or 443 (for SSL) 7 Make sure you allow packets from TCP port 5556 to be received on any available port on the Vocera Voice Server. 8 The base port for this range is configurable. 12 VOCERA WLAN REQUIREMENTS AND BEST PRACTICES

13 Client Direction Server / Client Type Protocol Ports IP PORT USAGE Vocera Collaboration Suite for Android and iphone Inbound VMP Signaling (Data) TCP 80 or 443 (for SSL) Vocera Collaboration Suite for Android and iphone Vocera Collaboration Suite for Android VMIClients VAI Clients (includes Staff Assignment) VCG Signaling UDP 5060, Vocera Devices Audio UDP VS Connection TCP 5005 VS Connection TCP 5251 VS (Vocera Connect for Cisco) Cisco UCM Signaling TCP VOCERA WLAN REQUIREMENTS AND BEST PRACTICES