Aruba Networks Version 3.3 manual Voice Deployment, Active Rfid Tag Deployment

Page 36

Be sure to remember that RF travels in three dimensions. In a multi-floor building, the strongest signal may be above or below rather than side-to-side. In all 802.11 networks the client, rather than the AP, makes the decision when to roam from one AP to another. The RF designer can use this to advantage by staggering APs from floor-to-floor. This will help ensure that client roaming behavior is predictable, and can improve how ARM makes decisions about channel selection and power settings.

Voice Deployment

When using Voice over WLAN take into consideration the type of handset that will be used. Many older voice handsets are only capable of operating in the 802.11b frequency range (2.4Ghz). To provide the highest quality of service, Aruba recommends moving clients into the 802.11a band due to the greater number of available channels, and using a higher AP density. This approach requires dual-radio APs to service both client types, and dual-radio AMs to lock the air in both bands.

The cell design and AP density is also affected by handset manufacturers. Generally speaking, a voice network should be RF planned to provide a minimum signal strength of -67dBm or better throughout the service area. In the Aruba RF Plan tool, use a 150% overlap setting with a 54 Mbps minimum data rate to provide this level of coverage. In most cases, this translates to an AP approximately every 60 feet.

Active RFID Tag Deployment

Placement Methodology and AP Density are both important when using active RFID tags. Because Aruba’s RF Locate feature uses triangulation of Received Signal Strength Indication (RSSI) to locate devices and active RFID tags, the tag or device must be heard by a minimum of three access points to obtain a reliable reading. APs should be deployed along the building perimeter so that there is always a defined edge the client or tag will be contained within. If necessary, external semi-directional antennas can be used on these perimeter APs to direct the maximum signal towards clients and to reduce susceptibility of the system to co-channel interference from outside the building.

36 Mobility Controller and Access Point Deployment

Campus Wireless Networks Validated Reference Design Version 3.3 Design Guide

Image 36

Contents Campus Wireless Networks Validated Reference Design Version Crossman Avenue Sunnyvale, California Phone Fax Contents Chapter RF Planning and Operation Aruba Reference Architectures Reference DocumentsContacting Aruba Networks IntroductionTelephone Support Understanding Centralized Wireless LAN Networks Aruba’s User-Centric Network ArchitectureIntroducing Aruba’s User-Centric Network Centralized Wlan ModelArubaOS and Mobility Controller ArubaOSMobility Controller Multi-function Thin Access Points Access PointAir Monitor Mesh Portal or Mesh Point Aruba’s Secure Enterprise Mesh NetworkMobility Management System Remote APMobility Management System PoC Network Physical Design Proof-of-Concept NetworkPoC Network Logical and RF Design VlanProof-of-Concept Network Proof-of-Concept Network Aruba Campus Wlan Physical Architecture Campus Wlan Validated Reference DesignAruba Campus Wlan Logical Architecture Data center ManagementMaster Campus Wlan Validated Reference Design Mobility Controller Access Point Deployment Understanding Master and Local OperationMobility Controller High Availability Master Controller Redundancy Local Controller Redundancy Second Local controller has an opposite configuration Vlan Design Do Not Make Aruba the Default Router Do Not Use Special VLANsVlan Pools VlanUser Mobility and Mobility Domains VLANs 10, 20, 30ArubaOS Mobility Domain MD1Mobility Controller Physical Placement and Connectivity Master Controller PlacementAP Placement, Power, and Connectivity Local Controller PlacementMobility Controller and Thin AP Communication AP Power and Connectivity AP Location and Density ConsiderationsOffice Deployment Voice Deployment Active Rfid Tag DeploymentConfiguration Profiles and AP Groups Mobility Controller ConfigurationConfiguration Profiles Required LicensesProfile Types AP groupSSIDs, VLANs and Role Derivation AP GroupsProfile Planning SSIDs VLANsSecure Authentication Methods Role DerivationAuthenticating with Corporate Authenticating with Captive Portal Authentication Methods for Legacy DevicesConfiguring Roles for Employee, Guest and Application Users Employee RoleGuest Role Create a bandwidth contract and apply it to an AP group Create the block-internal-access policy Modify the guest-logon role Device Role Wireless Intrusion Detection System Role Variation by Authentication MethodWireless Attacks Rogue APs Page Mobility Controller Configuration RF Plan Tool RF Planning and OperationAdaptive Radio Management Page Minimum Scan Time Sec Voice over Wi-Fi Quality of ServiceWMM and QoS Voice Functionality and Features Traffic PrioritizationNetwork Wide QoS Voice-Aware RF ManagementComprehensive Voice Management Voice over Wi-Fi Controller Clusters Mobility Management System LAN / WANMultiple Master/Local Clusters Page Multiple Master/Local Clusters Appendix a LicensesLicenses Appendix B Wlan Extension with Remote APWlan Extension with Remote AP Small Network Deployment Alternative Deployment ArchitecturesMedium Network Deployment Mobility Controller located in the network data centerBranch Office Deployment Corporate data center Pure Remote Access Deployment DMZ