Spectralink VIEW Certified Configuration Guidesupport.spectralink.com › sites › default › files › resource...721-1005-000 Rev: E December 2016 Spectralink VIEW Certified Configuration

721-1005-000 Rev: E December 2016

Spectralink VIEW Certified Configuration Guide

Zebra Technologies Corporation Access Points AP 621, 650, 6521, 6532, 7131, 7522, 7532, 7562, 8132

with WLAN controllers RFS40X0, RFS60X0, RFS70X0, and NX9XX0

Spectralink VIEW Certified Configuration Guide: Zebra Technologies Corporation

721-1005-000-E.docx December 2016 2

Copyright Notice

© 2015-2016 Spectralink Corporation All rights reserved. SpectralinkTM, the Spectralink logo and the

names and marks associated with Spectralink’s products are trademarks and/or service marks of

Spectralink Corporation and are common law marks in the United States and various other countries. All

other trademarks are property of their respective owners. No portion hereof may be reproduced or

transmitted in any form or by any means, for any purpose other than the recipient’s personal use, without

the express written permission of Spectralink.

All rights reserved under the International and pan-American Copyright Conventions. No part of this

manual, or the software described herein, may be reproduced or transmitted in any form or by any

means, or translated into another language or format, in whole or in part, without the express written

permission of Spectralink Corporation.

Do not remove (or allow any third party to remove) any product identification, copyright or other notices.

Notice

Spectralink Corporation has prepared this document for use by Spectralink personnel and customers.

The drawings and specifications contained herein are the property of Spectralink and shall be neither

reproduced in whole or in part without the prior written approval of Spectralink, nor be implied to grant any

license to make, use, or sell equipment manufactured in accordance herewith.

Spectralink reserves the right to make changes in specifications and other information contained in this

document without prior notice, and the reader should in all cases consult Spectralink to determine

whether any such changes have been made.

NO REPRESENTATION OR OTHER AFFIRMATION OF FACT CONTAINED IN THIS DOCUMENT

INCLUDING BUT NOT LIMITED TO STATEMENTS REGARDING CAPACITY, RESPONSE-TIME

PERFORMANCE, SUITABILITY FOR USE, OR PERFORMANCE OF PRODUCTS DESCRIBED

HEREIN SHALL BE DEEMED TO BE A WARRANTY BY SPECTRALINK FOR ANY PURPOSE, OR

GIVE RISE TO ANY LIABILITY OF SPECTRALINK WHATSOEVER.

Contact Information

US Location Denmark Location UK Location

+1 800-775-5330 +45 7560 2850 +44 (0) 20 3284 1536

Spectralink Corporation Spectralink Europe ApS Spectralink Europe UK

2560 55th Street Bygholm Soepark 21 E Stuen 329 Bracknell, Doncastle Road

Boulder, CO 80301 8700 Horsens Bracknell, Berkshire, RG12 8PE

USA Denmark United Kingdom

[email protected] [email protected] [email protected]

mailto:[email protected]

721-1005-000-E.docx December 2016 3

Contents

Introduction ...................................................................... 4

Certified Product Summary .............................................................................................. 4

Known Limitations ............................................................................................................ 5

Spectralink References .................................................................................................... 6

Support Documents ..................................................................................................... 6

White Papers ............................................................................................................... 7

Product Support ............................................................................................................... 7

Zebra Technologies Enterprise Support Center............................................................ 7

Customer Support Web Site ......................................................................................... 8

Chapter 1: Overview ........................................................... 9

Chapter 2: Connecting to a Controller for the First Time ............. 10

Connecting to the Controller via CLI for the First Time ................................................10

Configuring Controller IP address through CLI .............................................................10

Connecting to the Controller via the Web UI for the First Time ....................................11

Using the Initial Setup Wizard .........................................................................................11

Using a DHCP Server .......................................................................................................11

Logging in from GUI for the First Time: .........................................................................12

Configuring Controller IP address through the GUI ......................................................13

Adopting APs ...................................................................................................................17

Adopting APs through the CLI for a controller .............................................................17

Adopting APs through the Web interface .....................................................................18

Installing a New Image ....................................................................................................20

Installing controller firmware through the controller CLI ...............................................20

Installing firmware through the Web interface ..............................................................21

Upgrading controller-managed AP firmware through the Controller CLI ......................22

Upgrading controller-managed AP firmware through the Web interface ......................23

Chapter 3: Configuring the Controller and Access Point from Default

Configuration ................................................................... 25

SSID, QoS and Security Settings ....................................................................................25

Configuring SSID, QoS and security settings through the CLI .....................................25

Configuring SSID, QoS, and security settings through the Web interface ....................29

AP and Radio Settings ....................................................................................................48

Configuring radio and AP settings through the CLI ......................................................48

Configuring radio and AP settings through the Web interface......................................49

721-1005-000-E.docx December 2016 4

Introduction

Spectralink’s Voice Interoperability for Enterprise Wireless (VIEW) Certification Program is

designed to ensure interoperability and high performance between PIVOT™ by Spectralink®

(87-Series), 84-Series, and 8020/8030 Wireless Telephones and wireless LAN (WLAN)

infrastructure products.

The products listed below have been tested in Spectralink’s lab using the VIEW Certification

Test Plan. This document details how to configure the Zebra controllers RFS40X0, RFS60X0,

RFS70X0, and NX9XX0 to work with the AP8132. The configurations are chosen to best

support Spectralink wireless telephones.

Certified Product Summary

Manufacturer: Zebra Technologies Corporation

Approved products: AP650, AP6521, AP6532, AP7562, AP7532, AP7522, AP7131,

AP8132 with: RFS40X0, RFS60X0, RFS70X0, and NX9XX0

RF technology 802.11abgn

Radio: 2.4 GHz (802.11bgn), 5 GHz (802.11an)

Security : None, WPA-PSK, WPA2-PSK, WPA2-Enterprise (EAP-FAST

and PEAPv0/MSCHAPv2 and EAP-TLS)

QoS: Wi-Fi Standard

AP/controller software version tested: 5.5.6.x with AP 8132, 7131, 6532, 650

5.7.2.0-008R with AP7562, 7532, 7522, 6521, 621

Network topology Tunneled

Handset* models tested: PIVOT models

Handset radio mode: 802.11b/g/n 802.11a/n/c

Meets VIEW minimum call capacity per AP:** 8 10

Handset* models tested: Spectralink 84-Series Wireless Telephone

Handset radio mode: 802.11b/g/n 802.11a/n

Meets VIEW minimum call capacity per AP:** 8 10


721-1005-000-E.docx December 2016 5

Handset models tested: Spectralink 8020/8030 Wireless Telephone*

Handset radio mode: 802.11b/g/n 802.11a/n

Meets VIEW minimum call capacity per AP:** 6 (Wi-Fi Standard QoS)*** 8 (Wi-Fi Standard QoS)***

* Spectralink handset models and their OEM derivates are verified compatible with the WLAN hardware

and software identified in the table. Throughout the remainder of this document they will be referred to

collectively as “Spectralink wireless telephones”, “phones” or “handsets”. When necessary to differentiate,

the 8440, 8441 (8440 with personal alarm hardware), 8450 (with 1D bar code reader), 8452 (with 1D and

2D bar code reader), and 8453 (8452 with personal alarm hardware) handsets will be referred to

collectively as the 84-Series handsets. All PIVOT models will be referred to collectively as PIVOT

handsets.

** Maximum calls tested per the VIEW Certification Test Plan. The certified product may actually support

a higher number of maximum calls.

*** WPA2-Enterprise and Wi-Fi Standard QoS are not available for Spectralink 8020/8030 handsets

connecting to traditional PBXs.

Known Limitations

The following limitations were discovered during VIEW testing of this product:

Fast BSS Transition (802.11r) is not supported by the handsets but they will operate in a

network where the feature is advertised.

1Mb/s and 2Mb/s data rates must be disabled to meet maximum call capacity.

The SIP server/PBX must send a control class message to the phone within every

minute to keep the TSPEC bandwidth from thinking that it is idle and forcing the phone

to disassociate. In a SIP server based on an Asterisk model, this involves setting

qualify=yes and qualifyfreq=30. Similar settings exists on other SIP server models.

If an SSID with open security is used, there must be an unused SSID following it in the

list before an Enterprise SSID is advertised. Otherwise, poor multicast/broadcast

behavior may exist on the Enterprise SSID. This is a workaround: the issue is scheduled

to be fixed in the next releases of all active software chains.

The 650 and 6521 APs may have degraded call quality with heavy ftp background traffic.

This document does not cover the steps involved to configure a RADIUS server

required for using WPA2-Enterprise.


721-1005-000-E.docx December 2016 6

Spectralink References

All Spectralink documents are available at http://support.spectralink.com.

To go to a specific product page:

Select the Product Category and Product Type from the dropdown lists and then select the

product from the next page. All resources for that particular product are displayed by default

under the All tab. Documents, downloads and other resources are sorted by the date they were

created so the most recently created resource is at the top of the list. You can further sort the

list by the tabs across the top of the list to find exactly what you are looking for. Click the title to

open the link.

Support Documents

PIVOT by Spectralink Configuration Guide The PIVOT Configuration Guide provides detailed

information about PIVOT menu items that have been developed specifically for the PIVOT

handset.

Spectralink 87-Series Wireless Telephone Deployment Guide The Deployment Guide provides

sequential information for provisioning and deploying the handsets. It covers deployment using

the SLIC tool and CMS as well as manual deployment.

The Spectralink 84-Series Wireless Telephone Administration Guide provides a comprehensive

list of every parameter available on Spectralink 84-Series Wireless Telephones.

The Spectralink 84-Series Deployment Guide is your essential reference for provisioning and

deploying Spectralink 84-Series handsets in any environment.

http://support.spectralink.com/


721-1005-000-E.docx December 2016 7

The Web Configuration Utility User Guide explains how to use a web browser to configure the

Spectralink 84-Series handsets on a per handset basis.

The Spectralink 8020/8030 Wireless Telephone Handset Administration Tool document explains

how to use a software interface to configure the handsets.

Best Practices for Deploying Spectralink 87-Series PIVOT Handsets provides detailed

information on wireless LAN layout, network infrastructure, QoS, security and subnets.

White Papers

Spectralink White Papers are available at http://www.spectralink.com/resources/white-papers.

For the Spectralink 84-Series Wireless Telephones, please refer to Best Practices Guide for

Deploying Spectralink 84-Series Handsets for detailed information on wireless LAN layout,

network infrastructure, QoS, security and subnets.

For additional details on RF deployment please see The challenges of ensuring excellent voice

quality in a Wi-Fi workplace and Deploying Enterprise-Grade Wi-Fi Telephony.

These White Papers identify issues and solutions based on Spectralink’s extensive experience

in enterprise-class Wi-Fi telephony. It provides recommendations for ensuring that a network

environment is adequately optimized for use with Spectralink Wireless Telephones.

Product Support

Zebra Technologies Enterprise Support Center

If you have a problem with your equipment, contact Zebra Technologies Support for your region.

Support and issue resolution is provided for products under warranty or that are covered by an

Enterprise Services agreement.

Contact information and web self-Service is available by visiting

https://portal.zebra.com/Support/US-EN

When contacting Zebra Technologies Support, please provide the following information:

Serial number of the unit

Model number or product name

Software type and version number

Zebra Technologies responds to calls by email or telephone within the time limits set forth in

support agreements. If you purchased your product from a Zebra business partner, contact that

business partner for support.

http://www.spectralink.com/resources/white-papers



721-1005-000-E.docx December 2016 8

Customer Support Web Site

Zebra Technologies Support site, located at https://portal.zebra.com/Support/US-EN, provides

information and online assistance including developer tools, software downloads, product

manuals, support contact information and online repair requests.


721-1005-000-E.docx December 2016 9

Chapter 1: Overview

The following topology was used during VIEW Certification testing.

Note: Example configuration shown

It is important to note that this configuration is not necessarily applicable to all

customer environments.

721-1005-000-E.docx December 2016 10

Chapter 2: Connecting to a Controller for

the First Time

The controller can be accessed via SSH for CLI access, or via HTTPS for GUI

access. Configurations can be performed by either CLI or GUI, both of which will be

explained in this document. In CLI, use the command ‘commit write memory’ after

changes are made to save the entry. In GUI, click the ‘commit and save’ button

located on the upper-right side of the screen to save changes.

Connecting to the Controller via CLI for the First Time

Connect to the console port on the front of the controller using 19200 bits per second, 8 data

bits, no parity, no stop bit, and no flow control. The default login credentials are admin and

admin123 on the 5.7.2.0 version and admin and motorola on the 5.5.5.0 version. The user will

be prompted to change the password when logging in for the first time. Enter the new password

twice for verification purposes.

The AP’s IP address can be displayed using the following commands.

rfs6000-17EC66>enable

rfs6000-17EC66#config terminal

rfs6000-17EC66(config)# show ip interface brief

-------------------------------------------------------------

INTERFACE IP-ADDRESS/MASK TYPE STATUS PROTOCOL

-------------------------------------------------------------

vlan1 20.1.1.35/24(DCHP) primary UP up

-------------------------------------------------------------

Configuring Controller IP address through CLI

To use a static IP for the device, follow these steps:

rfs6000-17EC66#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

rfs6000-17EC66(config)#self

rfs6000-17EC66(config-device-00-23-68-86-47-DC)#interface vlan 1

rfs6000-17EC66(config-device-00-23-68-86-47-DC-if-vlan1)#ip address

<desired IP address>/24

rfs6000-17EC66(config-device-00-23-68-86-47-DC-if-vlan1)#exit


721-1005-000-E.docx December 2016 11

rfs6000-17EC66(config-device-00-23-68-86-47-DC)#ip default-gateway

<gateway IP address>

rfs6000-17EC66(config-device-00-23-68-86-47-DC-if-vlan1)#commit

write memory

Connecting to the Controller via the Web UI for the

First Time

The controllers utilize an initial setup wizard to streamline getting on the network for the first

time. This wizard configures location, network and WLAN settings and assists in the discovery

of Access Points and their connected clients. See the System Reference Guide for the

appropriate controller model on the https://portal.zebra.com/Support/US-EN site more detailed

directions.

Using the Initial Setup Wizard

Every controller is given the default address of 192.168.0.1. A PC or laptop may be reconfigured

with an IP that can access this address.

Using a DHCP Server

By default, a controller is set to be a DHCP client. Connect its GEx port to a DHCP server and it

will obtain an IP address. From the DHCP server, find the DHCP address lease using the MAC

address, which can be found on the back side of the device.



721-1005-000-E.docx December 2016 12

Logging in from GUI for the First Time:

Open a browser and enter in the address bar the address assigned using the wizard or by using

the cli and assigned to VLAN1.

1 Be sure that the browser has the latest Adobe Flash Player installed, which is required

for GUI access.

2 Enter default username and password of ‘admin’ and ‘motorola’ on the 5.5.5.0 version,

‘admin’ and ‘admin123’ on the 5.7.2.0 version. The GUI will prompt to enter a new

password.

3 A confirmation window appears after password change. Click OK to proceed. Now you

are connected to the AP via GUI.

4 A Wizard window pops up when you connect for the first time. The wizard is intended for

quick configuration, which does not cover some of VIEW Certification configurations.


721-1005-000-E.docx December 2016 13

Configuring Controller IP address through the GUI

From factory defaults, only the CLI can be used to initially configure a static

address for vlan1. Thereafter, the static address may be changed using the GUI.

1 To assign a static IP address, navigate to Configuration> Devices on a controller.

Select the Controller and click Edit located on the lower-right side of the screen.


721-1005-000-E.docx December 2016 14

2 Under Profile Overrides> Interface> Virtual Interfaces, select Vlan1 and click Edit.


721-1005-000-E.docx December 2016 15

3 Uncheck Use DHCP to Obtain IP, and manually enter an IP address. On Wing 5.7, also

click on the IPv4 or IPv6 tab, as appropriate. Click OK to accept the change.

1 Wing 5.5 Controller Static Address


721-1005-000-E.docx December 2016 16

2 Wing 5.7 Static Controller Address


721-1005-000-E.docx December 2016 17

4 Enter the default gateway address. Select Network> Routing> Static Routes from the

Device Panel. Click Add Row.

5 Enter a Network Address of 0.0.0.0/0 and enter the desired Default Gateway address

for the network. Use the down arrow by the network address to change the network

mask if necessary.

Adopting APs

For APs to be found by the controller, proper adoption settings must be supplied.

Adopting APs through the CLI for a controller

These directions define a generic “adopt all” policy. Facilities may want to use a more limited

policy to prevent rogue APs from joining the network.

rfs6000-17EC66(config)#auto-provisioning-policy <name of policy, eg

VIEW>

rfs6000-17EC66(config-auto-provisioning-policy-VIEW)#default-

adoption

Apply the auto-provisioning policy to the desired default controller policy and to the default

policies for each type of AP that will be attached.

rfs6000-17EC66(config-auto-provisioning-policy-VIEW)#exit

rfs6000-17EC66(config)#profile rfs6000 default-rfs6000


721-1005-000-E.docx December 2016 18

rfs6000-17EC66(config-profile-default-rfs6000)#use auto-

provisioning-policy VIEW

rfs6000-17EC66(config-profile-default-rfs6000)#exit

rfs6000-17EC66(config)#profile ap7532 default-ap7532 (for example)

rfs6000-17EC66(config-profile-default-ap7532)#use auto-provisioning-

policy VIEW

Adopting APs through the Web interface

1 Navigate to Configuration> Profiles and Click the row containing the profile for the

desired model of controller, eg default-rfs6000.

2 From Profile Overrides> Adoption, a specific adoption policy may be defined for all

controllers of this model. These directions define a generic “adopt all” policy.

3 Ensure that Access Points is checked by Controller Adoption Settings> Allow

Adoption of Devices.


721-1005-000-E.docx December 2016 19

4 Click the Create icon by Auto-Provisioning Policy. Enter a name and Click Continue.


721-1005-000-E.docx December 2016 20

5 Click the Default tab, check the radio box Adopt if No Rules Match, and Click OK.

6 Click OK on the Profile Overrides> Adoption menu and Commit and Save.

Installing a New Image

The VIEW Certified firmware release can be obtained from the support portal by searching for

the proper product at https://portal.zebra.com/Support/US-EN. It is necessary to have an

appropriate maintenance contract or recent purchase. Upgrading to the new firmware can be

done through the Web interface or through the command line interface (CLI). Place the image

on the FTP server or TFTP server depending on the file transfer mechanism chosen.

Installing controller firmware through the controller CLI

1 Enter your username and password to log into the CLI.

2 Connect the FTP/TFTP server to subnet 1.

3 For TFTP, issue the following commands:

rfs6000-17EC66>en



721-1005-000-E.docx December 2016 21

rfs6000-17EC66#upgrade

tftp://<TFTP_SERVER_IP_ADDR>/<FIRMWARE_FILENAME>

4 For FTP, issue the following commands:

rfs6000-17EC66>en

rfs6000-17EC66#upgrade

ftp://<FTP_USERNAME>:<FTP_PASSWD>@<FTP_SERVER_IP_ADDR>/

<FIRMWARE_FILENAME>

5 After the upgrade is successful issue the following command:

rfs6000-17EC66#reload

Installing firmware through the Web interface

1 Open the GUI by entering the IP address.

2 Navigate to Operations> Devices.

a On Wing 5.5: On the left pane, click System to expand the tree, and Default, then

select the desired controller. Click the right arrow. On the lower-right screen, click

Firmware Upgrade.

b On Wing 5.7: On the left pane, click System to expand the tree, and Default, then

select the desired controller. Click on the dropdown arrow beside the desired the

controller and select Firmware Upgrade


721-1005-000-E.docx December 2016 22

3 The Firmware Upgrade screen pops up.

4 Select protocol, enter host IP, and specify path/file name. Click Apply to start firmware

upgrade.

5 When finished, close the firmware upgrade screen.

6 Click Reload to reboot the device with new firmware.

Upgrading controller-managed AP firmware through the Controller CLI

1 First, load any necessary firmware images onto the controller. The images for advanced

AP models are not shipped with the controller and must be uploaded separately into the

controller.

rfs6000-17EC66#device-upgrade load-image ap<xxxx where xxxx is the

model number><IMAGE-URL>(IMAGE-URL is a tftp or ftp definition as

described above for installing controller firmware)

2 Enable automatic adopted device firmware upgrade if desired in the controller model

profile. This will cause APs to upgrade their image when they connect to the controller.

rfs6000-17EC66#config terminal

rfs6000-17EC66 config#profile rfs6000 default-rfs6000

rfs6000-17EC66 config-profile-default-rfs6000#device-upgrade add-

auto (apxxx|apxxx|…)

3 Alternatively, upgrade APs on demand.

rfs6000-17EC66#device-upgrade rf-domain all [all|apxxx] {reboot-time

<TIME>} {staggered-reboot}


721-1005-000-E.docx December 2016 23

Upgrading controller-managed AP firmware through the Web interface

1 First, load any necessary firmware images onto the controller. The images for advanced

AP models are not shipped with the controller and must be uploaded separately into the

controller.

a Navigate to Operations> Devices and Click the name of the controller.

b Select Adopted Device Upgrade in the right hand pane.

c Click on Device Image File.

d From the Device Image Type dropdown, select the model of AP.

e Enter the parameters for Protocol, Host, Path/File and Click Load Image.

f Repeat for all models of AP in the controller’s network.

2 Enable automatic adopted device firmware upgrade if desired. This will cause APs to

upgrade their image when they connect to the controller.

a Navigate to Configuration> Profiles and Click the default profile for the controller,

e.g. default-rfs6000.

b Expand the arrow by Management and Click Firmware.

c Check the radio box ALL by Automatic Adopted Device Firmware Upgrade.

d Click OK and Commit and Save.

3 Alternatively, upgrade APs on demand.


721-1005-000-E.docx December 2016 24

a Navigate to Operations> Devices, highlight the desired AP type, and select the tab

Adopted Device Upgrade in the right hand pane.

b Enter parameters as appropriate for Device Type List, time of upgrade, No Reboot,

Staggered Reboot, and Force Upgrade.

c Check the radio box by each AP to be upgraded or by All.

d Click Update Firmware.

721-1005-000-E.docx December 2016 25

Chapter 3: Configuring the Controller

and Access Point from Default

Configuration

SSID, QoS and Security Settings

Configuring SSID, QoS and security settings through the CLI

1 Set up Radius server policies .

rfs6000-17EC66(config)#aaa-policy <aaa policy name>

rfs6000-17EC66(config-aaa-policy-<aaa policy name>)#authentication

server 1 host 20.1.1.1-Secret <shared secret>

rfs6000-17EC66(config-aaa-policy-<aaa policy name>)#authentication

protocol chap

rfs6000-17EC66 (config-aaa-policy-<aaa policy name>)#authentication

server 1 proxy-mode through-controller

2 Create a WLAN QoS policy:

rfs6000-17EC66(config)#wlan-qos-policy default

rfs6000-17EC66(config-wlan-qos-default)#classification non-unicast

normal

rfs6000-17EC66(config-wlan-qos-default)#voice-prioritization

rfs6000-17EC66(config-wlan-qos-default)#qos trust dscp

rfs6000-17EC66(config-wlan-qos-default)#qos trust wmm

3 Set up admission control to control network loading. The percentage of bandwidth

entered for maximum airtime varies whether the network is using 2.4 GHz or 5 GHz,

whether 8020/8030 handsets or 84-Series handsets are in use, and which codec is

selected. On the 84-Series and PIVOT handsets, the high definition codecs G711 Mu,

G711-A, G722 use more bandwidth and the low definition codec G729AB uses less

bandwidth. The PIVOT handsets support admission control on PIVOT R1.5 and later.

rfs6000-17EC66(config)#radio-qos-policy <radio qos policy name>

a 2.4 GHz settings (allows 8 84-Series or PIVOT handsets if low definition codecs are

in use):

rfs6000-17EC66(config-radio-qos-8400BLD)#no admission-control

implicit-tspec

rfs6000-17EC66(config-radio-qos-8400BLD)#admission-control voice

max-airtime-percent 45


721-1005-000-E.docx December 2016 26


max-roamed-clients 100


reserved-for-roam-percent 10


rfs6000-17EC66(config-radio-qos-8400BLD)#admission-control video


rfs6000-17EC66(config-radio-qos-8400BLD)#admission-control video

b 2.4 GHz settings (allows 8 84-Series or PIVOT handsets if high definition codecs are

in use):

rfs6000-17EC66(config-radio-qos-8400BHD)#no admission-control

implicit-tspec

rfs6000-17EC66(config-radio-qos-8400BHD)#admission-control voice







rfs6000-17EC66(config-radio-qos-8400BHD)#admission-control video


rfs6000-17EC66(config-radio-qos-8400BHD)#admission-control video

c 2.4 GHz settings (allows 6 8020/8030 handsets):

rfs6000-17EC66(config-radio-qos-8020B)#no admission-control

implicit-tspec

rfs6000-17EC66(config-radio-qos-8020B>)#admission-control voice max-

airtime-percent 35

rfs6000-17EC66(config-radio-qos-8020B)#admission-control voice max-

roamed-clients 100

rfs6000-17EC66(config-radio-qos-8020B)#admission-control voice


rfs6000-17EC66(config-radio-qos-8020B>)#admission-control voice

rfs6000-17EC66(config-radio-qos-8020B>)#admission-control video max-

airtime-percent 15

rfs6000-17EC66(config-radio-qos-8020B>)#admission-control video

d 5 GHz settings for a network with 84-Series handsets (allows 10 84-Series or PIVOT

handsets if low definition codecs are in use):

rfs6000-17EC66(config-radio-qos-8020ALD)#no admission-control

implicit-tspec

rfs6000-17EC66(config-radio-qos-8400ALD>)#admission-control voice


rfs6000-17EC66(config-radio-qos-8400ALD)#admission-control voice



721-1005-000-E.docx December 2016 27

rfs6000-17EC66(config-radio-qos-8400ALD)#admission-control voice


rfs6000-17EC66(config-radio-qos-8400ALD>)#admission-control voice

rfs6000-17EC66(config-radio-qos8400ALD)#admission-control video max-

airtime-percent 15

rfs6000-17EC66(config-radio-qos8400ALD)#admission-control video

e 5 GHz settings for a network with 84-Series handsets (allows 10 84-Series or PIVOT

handsets if high definition codecs are in use):

rfs6000-17EC66(config-radio-qos-8020AHD)#no admission-control

implicit-tspec

rfs6000-17EC66(config-radio-qos-8400AHD)#admission-control voice


rfs6000-17EC66(config-radio-qos-8400AHD)#admission-control voice


fs6000-17EC66(config-radio-qos-8400AHD>)#admission-control voice


rfs6000-17EC66(config-radio-qos-8400AHD>)#admission-control voice

rfs6000-17EC66(config-radio-qos8400AHD)#admission-control video max-

airtime-percent 15

rfs6000-17EC66(config-radio-qos8400AHD)#admission-control video

f 5 GHz settings for a network with 8020/8030 handsets (allows 8 handsets):

rfs6000-17EC66(config-radio-qos-8020A)#no admission-control

implicit-tspec

rfs6000-17EC66(config-radio-qos-8400A)#admission-control voice max-

roamed-clients 100

rfs6000-17EC66(config-radio-qos-8400A)#admission-control voice


fs6000-17EC66(config-radio-qos-8020A)#admission-control voice max-

airtime-percent 20

rfs6000-17EC66(config-radio-qos-8020A)#admission-control voice

rfs6000-17EC66(config-radio-qos-8020A)#admission-control video max-

airtime-percent 15

rfs6000-17EC66(config-radio-qos-8020A)#admission-control video

g Settings for a network with PIVOT handsets on versions before R1.4

rfs6000-17EC66(config)#radio-qos-policy none

If both 84-Series or PIVOT and 8020/8030 Series handsets are in use on the same

5 GHz network, use the smaller max-airtime percent.

4 Configure a WLAN. Specify SSID, bridging mode, syslog host, and security settings

using following commands:

rfs6000-818170(config)#wlan <WLAN Name>

rfs6000-818170(config-wlan-<WLAN NAME>)#ssid <SSID name>


721-1005-000-E.docx December 2016 28

rfs6000-818170(config-wlan-<WLAN NAME>)#bridging-mode tunnel

rfs6000-818170(config-wlan-<WLAN NAME>)#wireless-client inactivity-

timeout 300

rfs6000-818170(config-wlan-<WLAN NAME>)#accounting syslog host

<syslog server IP>

rfs6000-818170(config-wlan-<WLAN NAME>)#ip arp trust

rfs6000-818170(config-wlan-<WLAN NAME>)#ip dhcp trust

a For WPA2-Enterprise security (PEAP, EAP-FAST, or TLS)

rfs6000-818170(config-wlan-<WLAN NAME>)#use aaa-policy <aaa-policy

name>

rfs6000-818170(config-wlan-<WLAN NAME>)#encryption-type ccmp

rfs6000-818170(config-wlan-<WLAN NAME>)#authentication-type eap

rfs6000-818170(config-wlan-<WLAN NAME>)#fast-bss-transition (Has no

effect but does no harm if other clients need it)

b WPA2-PSK security:

rfs6000-17EC66(config-wlan-<WLAN NAME>)#encryption-type ccmp

rfs6000-17EC66(config-wlan-<WLAN NAME>)#authentication-type none

rfs6000-17EC66(config-wlan-<WLAN NAME>)#wpa-wpa2 psk 0 12345678

c WPA-PSK security tkip:

rfs6000-17EC66(config-wlan-<WLAN NAME>)#encryption-type tkip-ccmp


rfs6000-17EC66(config-wlan-<WLAN NAME>)#wpa-wpa2 psk 0 12345678

d WEP:

The 8020/30 and 84-Series handsets must use the Authentication: Open System

setting with WEP on the Zebra products. (PIVOT handsets detect the Open/Shared

settings automatically.)

For 128 bit key (called 104 bit on 8020/8030)


rfs6000-17EC66(config-wlan-<WLAN NAME>)#encryption-type wep128

rfs6000-17EC66(config-wlan-<WLAN NAME>)#wep128 key <1-4>hex

012345678901234567890123456

or for 64 bit key (called 40 bit on 8020/8030)

rfs6000-17EC66(config-wlan-<WLAN NAME>)#encryption-type wep64

rfs6000-17EC66(config-wlan-<WLAN NAME>)#wep64 key <1-4>hex 0

0123456789


721-1005-000-E.docx December 2016 29


An Open security SSID must be followed by an unused SSID to work around an

issue that is disruptive to multicast and broadcast traffic. The issue is scheduled for

correction in future software releases.

Configuring SSID, QoS, and security settings through the Web interface

1 Create a WLAN QoS Policy: Navigate to Configuration> Wireless> WLAN QoS

Policy, double-click the default policy to edit it.


721-1005-000-E.docx December 2016 30

2 Check Enable Voice Prioritization, set Non-Unicast Classification to Normal. Ensure

that the other settings shown in the picture below are as shown.


721-1005-000-E.docx December 2016 31

3 Navigate to Configuration> Wireless> Radio QoS Policy, and click Add.

4 Set up admission control to control network loading. The percentage of bandwidth

entered for maximum airtime varies whether the network is using 2.4 GHz or 5 GHz,

whether 8020/8030 handsets or 84-Series handsets are in use, and which codec is

selected. On the 84-Series and PIVOT handsets, the high definition codecs G711 Mu,

G711-A, G722 use more bandwidth and the low definition codec G729AB uses less

bandwidth. Click the Admission Control tab and enter a name for the profile. Note that

Maximum Roamed Wireless Clients is set to 100 to avoid limiting by number of clients.

Implicit TSPEC must be unchecked so that data streams can pass while the TSPEC is

being negotiated. Note that the PIVOT handsets support Admission Control on PIVOT

R1.5 and later.


721-1005-000-E.docx December 2016 32

a 2.4 GHz settings (allows eight 84-Series handsets if low definition codecs are not in

use on the 84-Series). Enter 45 for Maximum Airtime for Voice and 15 for Video.


721-1005-000-E.docx December 2016 33

b 2.4 GHz settings (allows eight 84-Series or PIVOT handsets if high definition codecs

are in use). Enter 55 for Maximum Airtime for Voice and 15 for Video.


721-1005-000-E.docx December 2016 34

c 2.4 GHz settings (allows 6 8020/8030 handsets). Enter 35 for Maximum Airtime for

Voice and 15 for Video.


721-1005-000-E.docx December 2016 35

d 5 GHz settings for a network with 84-Series handsets (allows ten 84-Series or PIVOT

handsets if low definition codecs are in use). Enter 35 for Maximum Airtime for



721-1005-000-E.docx December 2016 36

e 5 GHz settings for a network with 84-Series handsets (allows 10 84-Series or PIVOT

handsets if high definition codecs are in use). Enter 35 for Maximum Airtime for



721-1005-000-E.docx December 2016 37

f 5 GHz settings for a network with 8020/8030 handsets (allows eight handsets). Enter

20 for Maximum Airtime for Voice and 15 for Video.

5 WLAN configuration: Under Configuration> Wireless> Wireless LANs, click Add to

create a new WLAN.

An Open security SSID must be followed by an unused SSID to work around an

issue that is disruptive to multicast and broadcast traffic. The issue is scheduled for

correction in future software releases.


721-1005-000-E.docx December 2016 38

6 Enter WLAN name, SSID.


721-1005-000-E.docx December 2016 39

7 Select Client Settings under the WLAN <WLAN name> panel. Enter 5 minutes for

Wireless Client Idle Time. This is to allow clients to time out gracefully if the battery is

removed or the phone goes out of range of all APs.


721-1005-000-E.docx December 2016 40

8 Define a syslog server if desired. Select Accounting under the WLAN <WLAN name>

panel. Check Enable Syslog Accounting. Enter the Syslog Host IP address or DNS

name.

9 Set WLAN security.

a For WPA2 Enterprise (PEAP, EAP-FAST, or TLS), under Security in the WLAN

<WLAN Name>panel, choose EAP as the authentication type, select the previously

defined AAA Policy <AAA Policy Name>. Use WPA2-CCMP as encryption type.

Scroll down and check Pairwise Master Key (PMK) Caching and Opportunistic

Key Caching.


721-1005-000-E.docx December 2016 41

b For WPA2-PSK under Security in the WLAN <WLAN Name> panel, choose

PSK/None as the authentication type. Use WPA2-CCMP as encryption type. Enter

the pre-Shared key. Ensure that Exclude WPA2 TKIP is checked and that both Key

Rotation items are unchecked.


721-1005-000-E.docx December 2016 42


721-1005-000-E.docx December 2016 43

c For WPA-PSK under Security in the WLAN <WLAN Name> panel, choose

PSK/None as the authentication type. Use TKIP-CCMP as encryption type. Enter

the pre-Shared key. Ensure that Exclude WPA2 TKIP is checked and that both Key

Rotation items are unchecked.


721-1005-000-E.docx December 2016 44


721-1005-000-E.docx December 2016 45

d For WEP under Security in the WLAN <WLAN Name> panel, choose PSK/None as

the authentication type. Use WEP64 or WEP128 as encryption type. Enter the WEP

key.

The handsets must use the Authentication: Open System setting with WEP on the

Zebra products.


721-1005-000-E.docx December 2016 46


721-1005-000-E.docx December 2016 47

10 Click Advanced in the WLAN <WLAN Name> panel. If this WLAN is intended for

Spectralink handset association, and uses b radio, set up a custom rate definition that

does not supply 1Mbps and 2 Mbps.

11 Create another WLAN following the same steps for background FTP/multicast traffic

use. No need to change default data rates for this WLAN. Radio Settings


721-1005-000-E.docx December 2016 48

AP and Radio Settings

Configuring radio and AP settings through the CLI

Smart RF Policy Defaults

The smart RF policy was left with the defaults of Sensitivity Medium, Scanning

Configuration: Client Aware Scanning not enabled, Power Save and Voice Aware

Scanning Dynamic. These are believed to be important for proper Spectralink

handset operation.

Set up a smart RF policy if desired (facility dependent). The following are examples:

rfs6000-818170(config)#smart-rf-policy VIEW40

rfs6000-818170(config-smart-rf-policy-VIEW40)#channel-list 5GHz

36,40,44,48,52,56,60,64,100,104,108,112,116,120,124,128,

132,136,140,149,153,157,161,165

rfs6000-818170(config)#smart-rf-policy VIEW80

rfs6000-818170(config-smart-rf-policy-VIEW80)# channel-width 5GHz

80MHz

Set up rf-domain general parameters.

rfs6000-818170(config)#rf-domain default

rfs6000-818170(config)#timezone America/Denver

rfs6000-818170(config-rf-domain-default)#country-code <country>

rfs6000-818170(config-rf-domain-default)#user smart-rf-policy

<smart-rf-policy-name>

rfs6000-818170(config-rf-domain-default)#control-vlan 1

rfs6000-818170(config-rf-domain-default)#controller-managed

rfs6000-818170(config-rf-domain-default)#exit

Set up AP model profile parameters that apply to all APs of that model type.

Assign previously created radio-profiles and WLANs. (Note: this example is from an AP that has

3 dual-band radios.)

rfs6000-818170(config)#profile <ap model>default-<ap model>

rfs6000-818170(config)#no ip igmp snooping (necessary for PTT

operation)

rfs6000-818170(config)#no ip igmp snooping forward-unknown-multicast

rfs6000-818170(config-profile-default-<ap model>)#interface radio 1

rfs6000-818170(config-profile-default-<ap model>-if-radio1)#data-

rates custom basic-5.5 basic-11 6 9 12 18 24 36 48 54 mcs-1s mcs-2s

mcs-3s

rfs6000-818170(config-profile-default-<ap model>-if-radio1)#beacon

dtim-period 1


721-1005-000-E.docx December 2016 49

rfs6000-818170(config-profile-default-<ap model>-if-radio1)#wlan

<WLAN NAME1>bss 1 primary



rfs6000-818170(config-profile-default-<ap model>-if-radio1)#use

radio-qos-policy <radio policy name>

rfs6000-818170(config-profile-default-<ap model>-if-radio1)#exit


rfs6000-818170(config-profile-default-<ap model>-if-radio2)#data-

rates custom basic-5.5 basic-11 6 9 12 18 24 36 48 54 mcs-1s mcs-2s

mcs-3s





rfs6000-818170(config-profile-default-<ap model>-if-radio3)#use

radio-qos-policy <radio policy name>

rfs6000-818170(config-profile-default-<ap model>-if-radio2)#exit


shutdown (this example is not using the monitor radio – not tested)

rfs6000-818170(config-profile-default-<ap model>)#exit

Set up parameters specific to a given AP.

rfs6000-818170(config)#ap<ap model><Mac address of AP model as XX-

XX-XX-XX-XX-XX>

rfs6000-818170(config-device-XX…)#use profile default-<ap model>

rfs6000-818170(config-device-XX…)#use rf-domain default

rfs6000-818170(config-device-XX…)#interface radio 1

rfs6000-818170(config-device-XX…-if-radio1)#no shutdown (enables

radio)

Specific AP settings can be determined from the results of a site design.

Automatic changes in channel may cause phone audio dropouts. Specific settings override the

smart RF policy described above and should be omitted if smart RF is desired.

rfs6000-818170(config-device-XX…-if-radio1)#channel 36w (w means 11n

channel of 40 MHz: 80Mhz channel is encoded as 36ww)

rfs6000-818170(config-device-XX…-if-radio1)#power 30

rfs6000-818170(config-device-XX…-if-radio1)#exit

rfs6000-818170(config-device-XX…)#exit

rfs6000-818170(config)#exit

rfs6000-818170#commit write

Configuring radio and AP settings through the Web interface

1 Set up a Smart RF policy, if desired.

a. Navigate to Configuration>Wireless>Smart RF Policy.


721-1005-000-E.docx December 2016 50

b. Click on Add.

c. Enter a name for the SMART RF Policy. Set up appropriate settings for the

facility.

Smart RF Policy Defaults

The smart RF policy should be left with the defaults of Sensitivity Medium,

Scanning Configuration: Client Aware Scanning not enabled, Power Save and

Voice Aware Scanning Dynamic. These are believed to be important for proper

Spectralink handset operation.


721-1005-000-E.docx December 2016 51

2 Set up rf-domain general parameters.


721-1005-000-E.docx December 2016 52

a Navigate to Configuration> RF Domains and double Click default.

b Select a Time Zone, Country, VLAN for Control Traffic, and check Controller

Managed.

c Choose the SMART RF Policy from the dropdown if desired

3 Set up AP model profile parameters that apply to all APs of that model type. Assign

previously created radio-profiles and WLANs. (Note: this example is from an AP that has

3 dual-band radios.)

a Navigate to Configuration> Profiles and select each AP model in the network.

b Navigate to Network> IGMP Snooping. Uncheck Enable IGMP Snooping and

Forward Unknown Multicast Packets. (Necessary for proper PTT – phone paging

– operation.). Click OK.


721-1005-000-E.docx December 2016 53

c Click OK.


721-1005-000-E.docx December 2016 54

4 Set up parameters specific to a given AP. These should be determined from the results

of a site design. Automatic changes in channel may cause phone audio dropouts.

a Under Configuration> Devices, double click the AP.

b Under Device> Interface> Radios, select the radio you would like to configure and

click Edit.


721-1005-000-E.docx December 2016 55

c On the Radio Settings tab, set Enabled for Admin Status, choose the appropriate

Radio QoS Policy from the dropdown box, and ensure the DTIM Interval is set to 1.

Set the value determined by the site design for the channel and power for this AP.

The quality of phone calls may be affected by dynamic channel changes.


721-1005-000-E.docx December 2016 56

d Click Select by the Data Rates selection. Define a custom selection that disables

1Mbps and 2 Mbps.


721-1005-000-E.docx December 2016 57

e On the WLAN Mapping/Mesh Mapping tab, use the arrows to activate the desired

WLANs on this radio.

f Click OK.

g Click Commit and Save.

****END OF DOCUMENT****