Wireless Infrastructure

Interoperability Guide

Intermec Mobile Computer,

Mobile Terminal

Configuration and

Deployment Reference Guide.

For Use With Ruckus

Wireless Infrastructures.

Revision 1.15 – 3/26/2014

Rev 1.15 Page 1

Table of Contents

TABLE OF CONTENTS .............................................................................................................................................. 1

OVERVIEW .......................................................................................................................................................... 2

WHO SHOULD READ THIS MANUAL .......................................................................................................................... 2

ABOUT THIS GUIDE ................................................................................................................................................... 2

TESTING ENVIRONMENT DESCRIPTION .................................................................................................................... 3

RUCKUS WIRELESS INFRASTRUCTURE EQUIPMENT DESCRIPTION ......................................................................... 4

INTERMEC END DEVICE DESCRIPTION ..................................................................................................................... 4

COMMUNICATION TESTING METHODOLOGY, PRACTICE AND PROCEDURES .......................................................... 5

RECOMMENDED RUCKUS WIRELESS INFRASTRUCTURE CONFIGURATION SETTINGS ............................................ 5

RECOMMENDED INTERMEC END DEVICE CONFIGURATION SETTINGS .................................................................... 6

SUGGESTED TECHNOLOGY PREREQUISITES ........................................................................................................... 7

ZoneDirector Firmware Recommendations ............................................................................... 1011 Security .......................................................................................................................................... 1112 Beacon Interval ............................................................................................................................. 1112 Beacon data rate ........................................................................................................................... 1112 DTIM ................................................................................................................................................ 1112 Tunneling ....................................................................................................................................... 1213 802.11d ........................................................................................................................................... 1213 Background scanning .................................................................................................................. 1213 TX Power setting ........................................................................................................................... 1314 DFS/Channel selection ................................................................................................................. 1314 MRC ................................................................................................................................................ 1314 Management Tx Data Rate ........................................................................................................... 1415 Multicast ......................................................................................................................................... 1415

CONFIGURING THE RUCKUS ZONEDIRECTOR .................................................................................................... 1516

HOW TO CONFIGURE YOUR INTERMEC COMPUTER (CLIENTS) WITH RUCKUS .................................................. 2324

SUGGESTED INTERMEC COMPUTER DEVICE SETTINGS (CLIENTS) .................................................................... 2324

Intermec CN70 Series, CK3X/R, CN51 WM6.5 Mobile Computers ............................................ 2324 CV41 CE ......................................................................................................................................... 2425 CV41 WES(XP), CV61 Win7/XP .................................................................................................... 2627 CN50, CS40 WM 6.1/6.5 ................................................................................................................. 2930 CK3B, CN3, CN4 WM 6.1 Series Computers ............................................................................... 2930

802.1X ROAMING AND KEY CACHING TABLE. ..................................................................................................... 2930 Table 1.0 ....................................................................................................................................................................... 2930

SUMMARY ..................................................................................................................................................... 3031

Rev 1.15 Page 2

Overview

Who Should Read This Manual

This document is intended for the individuals responsible for designing, installing,

configuring, and maintaining Intermec by Honeywell mobile computers networked

through a Ruckus® Wireless LAN (WLAN) system.

About This Guide

The intent of this document is to provide you with information regarding the

interoperability testing of Intermec mobile computer and terminal devices with the

Ruckus Wireless 802.11 infrastructure when used in a typical warehouse

environment. As with any RF environment, there are numerous variables that have

to be taken into account and we could not duplicate every conceivable condition of

all RF deployments and or physical environments. These variables include host and

network CPU overhead, network load balancing, RF signal physical effects of

reflection, cancellation and absorption and end device antenna modulation

differences based on signal multipath effects.

However the engineering testing methods that were deployed are the same ones

that are used by Intermec RF engineering teams for new device system tests prior to

product launch and release to manufacturing.

The testing did take into account how sample devices would be used in a real-world

environment, under typical use case scenarios. RF to end device communication and

throughput was tested using a redundant network to end device network ping testing

methodology with each device validating receipt of such communication and results

recorded on an archival graph. Multiple modes of configurations were tested under

both the 2.4(802.11bgn) and 5Ghz(802.11an) bands as well as dual band operation.

Rev 1.15 Page 3

Testing Environment Description

Intermec devices are used in many types of warehouse, distribution center, and

manufacturing environments. These environments can often be RF challenging

when it comes to providing reliable RF coverage and expected signal saturation

performance especially where the physical environment changes with the dynamic

practices of product storage, put-away and retrieval come into play. The location for

these tests was a typical pre-cast concrete exterior, tilt-up wall building with a

structural steel truss and corrugated sheet roof with an approximate height of 30ft

from floor to ceiling.

This environment also contained free standing steel pallet racks filled with corrugated

boxes with processed food stuffs that consisted of various degrees of moisture

content. The middle sections and aisle ways of the warehouse contained free

standing stacked pallets of the same kind of warehoused goods as described above.

Warehouse workers transport, move, and place pallet quantity product using

motorized forklift trucks and non - motorized hand pallet jack carts.

Lighting consisted of single sodium vapor bulb light fixtures with aluminum reflector

shades located throughout the facility. Each fixture was located on a drop rod

approximately two feet from the inside ceiling surface.

A proper RF site survey was completed prior to infrastructure installation to determine

the number of required access points and physical location of each so as to provide

adequate signal coverage within the desired area of RF testing. The site survey

testing software used to produce the survey report was recommended by the

infrastructure manufacturer.

Infrastructure design layout and deployment should target a -70dBm signal reading

from each access point with a 5 dB overlap. Network design and deployment

considerations should also be flat so that device IP addresses should not have to

change when roaming from one access point to another minimizing network and

device CPU overhead.

Rev 1.15 Page 4

Ruckus Wireless Infrastructure Equipment Description

Ruckus Wireless supplied Intermec testing engineers with one (1), 3000 series

ZoneDirector ™ appliance and six (6) ZoneFlex 7372 access points. Full descriptions of

these components can be found at www.ruckuswireless.com

The appliance and access points were the latest SKU versions available from both a

hardware, and firmware revision level. Two Ruckus personnel were also on site, and

participated in the testing operations and practices, and also verified the results

published in this document.

Intermec End Device Description

Intermec Technologies provided the following end devices and equipment for testing:

Device Model And Description

Model CS40 mobile computer with Windows Mobile 6.5

Model CN50 mobile computer with Windows Mobile 6.5

Model CN51 mobile computer with Windows Mobile 6.5

Model CN51 mobile computer with Android

Model CK3B mobile computer terminal with Windows Mobile 6.1

Model CK3X mobile computer terminal with Windows Mobile 6.5

Model CN70 mobile computer terminal with Windows Mobile 6.5

Model CK71 mobile computer terminal with Windows Mobile 6.5

Model CV61 vehicle mount computer with Windows 7 Pro.

Model CV61 vehicle mount computer with Windows XP Pro.

Model CV41 vehicle mount computer with Windows CE.

Model CV41 WES vehicle mount computer with Windows Embedded XP.

Rev 1.15 Page 5

Communication Testing Methodology, Practice And Procedures

As described earlier, Intermec uses a defined procedure and battery of test practices to

properly system test WLAN capable devices. This testing consists of static and roaming

movement communication tests whereby device populations have automated

communication ping sequences sent and receipt validated. This enables us to

understand the communication dynamics of device characteristic differences, such as

processor load and overhead, WLAN radio chip module performance, and antenna array

modulation attributes. As you now can see, there can be many variables in how and

why a device may perform in any subjected RF WLAN environment. Performance of a

device is also reliant on how well the infrastructure performs and how it handles these

variations from device to device.

Recommended Ruckus Wireless Infrastructure Configuration Settings

Because all devices have the possibility of behaving differently, it was the intent of our

testing to provide you with some baseline infrastructure settings that we recommend you

start with when installing Intermec devices with a Ruckus Wireless WLAN infrastructure.

Because the possibility exists for the variance in all RF environments these settings are

intended to be used as a “baseline” for setting up the initial communications for the

Ruckus ZoneDirector appliance and access points.

For best results we recommend that you precisely follow these instructions for setting up

the Ruckus WLAN infrastructure following the recommended RF site survey guidelines

provided by Ruckus, and after the necessary infrastructure components have been

installed in the intended permanent locations.

Rev 1.15 Page 6

Recommended Intermec End Device Configuration Settings

As referenced earlier, please remember and consider that many Intermec devices have

differences when it comes to 802.11 radios and chip sets, antenna arrays, processor

architectures and operating systems versions. Therefore the setting recommendations

that we have outline below should be considered as a baseline “starting point” for use

with Ruckus Wireless infrastructures. You may find that different environmental

conditions that affect RF cancellation, absorption, and reflection may exist that may

cause the need to change these settings. The good news is that the Ruckus Wireless

infrastructure can accommodate a wide array of dynamic RF challenges negating many

of these performance-impacting factors.

1. First start by making sure that all Intermec devices are configured in a

“factory default” state.

2. Make sure that you fully charged the batteries (where applicable).

3. Verify that you are running the latest version of firmware for that device.

4. Use Intermec “Scan And Go” to create configuration bar code labels for

specific devices. This is helpful for single and multi-site deployments where

little technical staff may be available to help set up the device populations.

5. Enable 2.4Ghz only – 5GHz settings and use will be covered in more detail

below.

6. Enable channel scans only for 1,6,11.

7. Use WPA v2 security on .1x

Use of 5GHz

In some installations it may become necessary to use the 5GHz band for RF

deployment. Please keep in mind that typically 5GHz RF signal saturation is less than

that of 2.4Ghz given the same physical environment. This means that 5GHz should

ideally be used in a designated area where the access point population might be greater

so as to provide a greater signal overlap for proper RF signal saturation.

Please also consider by enabling 5GHz and 2.4GHz simultaneously, you may cause

CPU processing overhead to increase thus affecting overall performance. This is

also dependent also on what application overhead and the necessary CPU allocation

needed for any resident programs needed in the use case scenario specified for the

deployment. Reduced roaming performance may also be observed.

Rev 1.15 Page 7

The bottom line is; application performance may be impacted by increases in CPU

overhead when redundant communications methodologies are deployed.

When enabling 5GHz, use channels 149,153,157,and 161. Do NOT use channel 165.

Ideally you would like to have the 5GHz device population deployed in a segregated

manner so that the performance of both devices and infrastructure components is

maximized, possibly enhancing the user experience.

Suggested Technology Prerequisites

Ruckus Wireless ZoneDirector User guide

Familiarity with 802.11 security implementation standards (it is recommended that

users of this guide enable the property 802.11 security measures necessary for

their operating environment) Please see the security section below for more detail.

Completed a recommended RF site survey for the installation site in questions

using the appropriate RF survey tools and methods recommended by Ruckus

Wireless.

Site Survey Overview And Recommended Procedures

7372/7982 Elevation coverage with horizontal mounting orientation

Rev 1.15 Page 8

7372/7982 Azimuth coverage

Rev 1.15 Page 9

7372/7982 vertical “wall mounted” orientation

Rev 1.15 Page 10

AP placement and appropriate coverage overlap

Site survey tools such as Airmagnet can be used to verify whether the deployment meets its

stated objectives i.e. -70 dBm coverage with 5 dB overlap.

Before you can configure your wireless network, you must install each these network components:

Ruckus 3000 series ZoneDirector

Ruckus 7372 Access Point(s)

Intermec Mobile computer(s)

ZoneDirector Firmware Recommendations

ZD code 9.7.1.0 build 5 or higher.

Rev 1.15 Page 11

Security

Intermec by Honeywell and Ruckus Wireless recommend WLAN security based on the IEEE 802.11i standard. The 802.11i standard defines two authentication methods, commonly called by their Wi-Fi alliance certifications: WPA2-Enterprise and WPA2- Personal (or WPA2-PSK for ‘pre-shared key’). WPA2-Enterprise is extremely secure and is built around the 802.1X port authentication standard. WPA2-Enterprise requires a RADIUS server (or RADIUS proxy) and a database of users with their corresponding credentials. For less complex WLAN deployments, WPA2-PSK uses a single passphrase, the PSK, to access the WLAN. Ruckus has introduced a valuable innovation to enable more robust security on a WLAN without the need for a RADIUS server or other additional infrastructure. Ruckus Dynamic-PSK (DPSK) creates a unique 63-byte encryption key for each user. No end users share a key, so if one leaves the organization, only that key needs to be deleted from the ZoneDirector. Additional security options are available. Please consult with your organization’s security policy in order to determine the appropriate security mechanisms for your WLAN.

Beacon Interval

The Beacon interval is the amount of time that elapses between consecutive Beacon

frames that are transmitted by the AP. All APs transmit beacons for every SSID that they

are configured for. The more SSIDs that are added, equates to more Beacon frames

being transmitted. It is recommended that a default beacon interval of 100ms be used

for up to 4 SSID’s and use 200ms for 5+ SSID’s up to a max of 8.

Beacon data rate

A typical warehouse user desires maximum range while using a very small amount of

network bandwidth. In this situation, the data rate at which the AP sends its beacons

should be set to 1Mbps. (Please see “Management Tx Data Rate” section below.)

DTIM

DTIM has to do with power management activities and the delivery of multicast frames.

The recommended DTIM setting is “2”. With higher beacon interval times (150ms+), the

DTIM used should be set to “1”.

Rev 1.15 Page 12

Tunneling

The primary function of tunneling solves a problem that can occur when clients roam between APs on different subnets. This is for the case when a dedicated VLAN is not assigned to the WLAN. Users must typically re-associate, re-authenticate and obtain a new IP address. This process is unacceptable as it causes interruptions and latencies that can ruin delay-sensitive applications such as VoIP. In addition, tunneling traffic through the ZoneDirector assists with an issue that may occur with traffic forwarding on certain switches and in mobile environments. As an example, in environments where mobile computers roam quickly between APs, some switches may not update their forwarding databases as quickly as needed in order to provide uninterrupted data service to the roaming clients. By tunneling traffic through the ZoneDirector, the switch infrastructure is not required to forward data as application traffic is tunneled between the APs and ZoneDirector. Another consideration for tunneling (or not tunneling) is if large data transfers and high usage is common in the warehouse. It is suggested that either tunneling be disabled or an appropriate ZoneDirector be selected such that higher traffic loads can be tunneled without issue. Please contact your Intermec by Honeywell Systems Engineer, Ruckus Systems Engineer or Ruckus Technical Support for assistance in ZD scaling for tunneling applications.

802.11d

Most Intermec devices use 802.11d by default. 802.11d has to do with setting certain

criteria for channelization and transmit power unique for certain countries. If this is

disabled, the transmit power of the client device will have to operate at the lowest

common denominator and reduction in range and performance can occur. It is

recommended that 802.11d be enabled.

Background scanning

Many controller based APs have a Background Scanning feature that allows the AP to

go “off channel” every configured interval in order to collect environmental RF

information that it sends to the ZoneDirector for computation and system-wide analysis.

Background scanning enables the APs and ZD to compile an AP neighbor list (per AP)

for Opportunistic Key Caching (OKC), as well as detect potential issues such as co-

channel interference and rogue APs. Background scanning requires the AP to go off

channel for a very brief amount of time (~20ms) every specified/configured interval. If the

background scanning interval is left at default (20 seconds), there is a higher likeliness

that multimedia sessions may be disrupted with this very brief service interruption if the

Rev 1.15 Page 13

AP goes off channel during a multimedia (voice/video) session. For brief multimedia

sessions such as PTT-voice, the statistical likeliness of being interrupted by background

scanning is far less than that of longer sessions, e.g. standard voice calls. Data

applications are not likely to experience any issues when a more aggressive background

scanning interval is configured. With that being said, it has been our experience that in a

warehouse setting, this scanning interval can be significantly increased or even disabled.

Recommended value during normal operation; 1-12 hours, or disabled (this is specific to

to what might be recommended for the RF environment).

TX Power setting

A typical warehouse may move a large amount of product in a short amount of time. It has been our experience that the use of any Radio Resource Management (RRM) for Transmit Power may have a negative impact on performance. It is suggested that any RRM dealing with AP or client power be disabled and the client and infrastructure devices be locked at the Max Transmit power setting. If the environment has a lot of overlapping coverage because of a large number of AP’s and max power is not desired, try reducing the Tx power on the AP’s instead of enabling RRM.

DFS/Channel selection

The Ruckus 7372 and 7982 support the use of multiple channels in the DFS frequency

range. Availability of specific DFS channels in the AP is country code dependent. Please

confirm channel availability in advance.

MRC

By default, Ruckus APs do not perform MRC (Maximal Ratio Combining) on 1 & 2Mbps

frames. Maximal ratio combining (MRC) is a way to exploit spatial diversity at the

receiver. In MRC, a weighted sum of signals received on all antennas results in the

combined signal being stronger than the signal received with maximum power. The

improved signal-to-noise ratio leads to better reception range. However, in certain

environments that contain neighboring 802.11 2.4GHz networks, performing MRC on 1

& 2Mbps frames will increase the reception range of the unwanted neighbor WiFi

network signals as well, causing the AP to experience increased interference and a

reduced SINR (Signal-to-Interference+Noise-Ratio). Enabling MRC for 1 & 2Mbps

frames can be highly beneficial in environments that do not have sufficient coverage and

have little to no external interference from neighboring 802.11 2.4GHz networks. Please

Rev 1.15 Page 14

use caution and evaluate the system and environment when determining whether or not

to enable MRC on 1 & 2Mbps frames.

Management Tx Data Rate

The “management Tx data rate” is the data rate used by the AP to transmit management

frames, e.g. beacons, probe responses, association responses, etc. The default is

2Mbps for WLANs on the 2.4GHz radio and 6Mbps for WLANs on the 5GHz radio.

In a warehouse environment and for maximum range, it is recommended that the

Management Tx Data Rate be set to 1Mbps on the 2.4Ghz band.

Multicast

Ruckus APs transmit multicast traffic at the highest basic rate. For 2.4GHz, when

802.11b rates are available- 1, 2, 5.5, and 11Mbps are set as “basic rates” for the

WLAN. This results in multicast transmissions at 11Mbps. In the absence of 802.11b

rates, or “OFDM-only” mode, 6, 12, and 24Mbps are set as the “basic rates” of the

WLAN. This results in multicast transmissions at 24Mbps. The same is true for 5GHz- 6,

12, and 24Mbps are set as the “basic rates” and 24Mbps is the rate used for multicast. If

multicast applications will be used on the WLAN, please keep the multicast rate in mind

when designing RF coverage for the WLAN system. The client devices (receivers of

multicast traffic) need to be in proper coverage at all times in order to demodulate

multicast traffic sent at the highest basic rate. Additional (and robust) multicast

transmission options are available with the Ruckus Directed-Multicast and Directed-

Threshold features.

Rev 1.15 Page 15

Configuring the Ruckus ZoneDirector

Most of the general settings discussed above are the default settings on the Ruckus Zone

Director and do not need to be changed. Nevertheless, for reference purposes, the screen shots

below depict where these settings are available in the ZoneDirector.

1. Make sure the Zone Director appliance settings are all in a default factory state and

that the firmware is version 9.7.1.0 build 5 or higher. As shown below, the firmware

version is available from the Dashboard Tab.

Rev 1.15 Page 16

2. After all access points have been installed, change the background scanning interval to

a short time interval (suggest 10 seconds). This allows the infrastructure to quickly

locate and build an AP neighbor list. Let this configuration process for about 10 minutes,

and then change the setting to 1 hour. As shown below, this setting is available from the

Configuration->Services page.

Rev 1.15 Page 17

3. Set 2.4GHz channels use to 1,6,11 only. Assuming that all the Access Points belong to

the “Default” Group, this can be done from the Configure->Access Points->Edit Default

Group page.

Rev 1.15 Page 18

4. As shown below, the 802.11d setting is enabled by default and needs no changes.

However, it can be found in the “Advanced” section of the WLAN settings.

5. As described above, set background scanning to 3600 seconds (1 hour)

Rev 1.15 Page 19

6. As shown below, set the Tx Power to be “Full”. This is done from the Configure->Access

Points->Edit Default Group page.

Rev 1.15 Page 20

7. The TX management data rate is set through the CLI as opposed to the GUI. If need be,

it can be set to 1 Mbps as shown below..

8. If required, enable MRC via the CLI. As shown below, this is done via the ZD CLI as a

remote CLI call to all the Access Points. (Please see notes in the MRC section above on

whether or not to enable this setting.)

Rev 1.15 Page 21

9. Enable tunneling on WLANs.

This is done when creating the WLAN and the setting can be accessed from the

“Advanced” settings for the same.

10. The default beacon interval is 100ms and does not need to be changed. However, it can

be accessed/changed via the CLI as shown below.

Rev 1.15 Page 22

11. Ruckus uses either PMK caching or OKC on a per WLAN basis. If the WLAN

uses dot1x, make sure that OKC is enabled. This is done by disabling PMK

caching via the CLI.

12. If so desired, change the DTIM period to the desired value. This is done via a CLI

command to all the APs connected to the Zone Director. In the example below, the

desired WLAN has an index of wlan0.

Rev 1.15 Page 23

How to configure your Intermec Computer (Clients) with Ruckus

Step-by-step instructions on how to configure your Intermec device is beyond the scope

of this document. Configuration instructions via the corresponding Users Guide may be

obtained by visiting the Intermec web site at www.Intermec.com.

Some recommended device settings for various installations can be found in the

“Suggested Intermec Computer device settings (Clients)” area below.

Suggested Intermec Computer device settings (Clients)

Intermec CN70 Series, CK3X/R, CN51 WM6.5 Mobile Computers

These devices use an Intermec patented dynamic roaming threshold that adjusts its roaming

characteristics based upon its environment so no roaming related tweaks need to be made. For

802.1x quick roaming on these devices, static PMK caching will need to be enabled on the

controller as Opportunistic Key Caching (OKC) is not supported. Configure the WLAN settings

for the network the device will be connected to. (See the Intermec Users Guide for

configuration assistance)

The 802.11a(5Ghz) band is disabled by default. If the environment the device is operating in

doesn’t contain AP’s on the 5Ghz band, leave it disabled. Note that enabling 2.4 Ghz and 5Ghz

bands at the same time will have an impact on roaming performance. If you wish to optimize

roaming on the device, you can use the below registry keys to set the device to only use the

specified channels. Typically 1,6 and 11 are used for the 2.4Ghz band and 149, 153, 157, 161.

(ch 165 is not supported) Channels 36, 40,44,and 48 can also be used but they are lower

powered channels and your performance may not be as good. It is recommend not to use

Radar channels(52, 56, 60,64, 100, 104, 108, 112, 116, 132, 136, 140) if at all possible.

To optimize roaming to use only certain channels, you will need to set the registry settings

below. (NOTE: The device will not roam to an AP that is not using one of the designated

channels so use this with caution!) A reboot will be required for the changes to take effect.

[HKEY_LOCAL_MACHINE\Comm\TIWLN1\Parms]

"SmeScanGChannelList"="1,6,11"

"SmeScanAChannelList"="149,153,157,161"

By default, the devices will issue a DHCP request on every roam. This is useful if the device is

roaming to a different subnet. Disabling this feature may slightly increase roam times or help

reduce the amount of traffic sent across a slow network link.

(Note that if the device is suspended for a long period of time and the DHCP lease expired, the

IP may be given to another device and an IP conflict could occur when the device is resumed.)

Rev 1.15 Page 24

To disable DHCP on roam, use the below registry key and reboot the device.

[HKEY_LOCAL_MACHINE\Comm\TIWLN1\Parms\TcpIp]

DisableDHCPMediaSense= “1”

CV41 CE

The CV41 with Windows CE has a 802.11abg radio and Intermec settings can be use to

configure the WLAN settings. A Summit Client Utility exists in the background that can be used

to optimize the system.

To setup the WLAN radio on the CV41 CE, use Intermec Settings to configure the device for

your WLAN settings. Under the \Windows\Programs\Summit directory, is a file called “scu.exe”,

find that file and click on it. (Note that this file is in a hidden directory).

Select “Admin Login” and login to the Summit Client Utility. The default Password is “SUMMIT”

but it is recommended that you change it.

Under the Profile tab make these changes:

Radio Mode = “BG rates full” (Only if the 5Ghz band will not be used.) Power Save = “”CAM” Tx Power = “Maximum”

Rev 1.15 Page 25

Under the “Global” tab make these changes:

Roam Trigger = “-70 dBm” (Set this option to work best for your environment)

Roam Delta = “5dBm”

Roam Period = “5 sec”

BG Channel Set = “1,6,11” (This is optional and should not be set if other channels are used.)

PMK Caching = “OPMK” (Set this if 802.1x is being used)

Admin Password = “Your Password” (Optional but recommended)

Don’t forget to click “Commit” or your setting won’t get saved.

Rev 1.15 Page 26

CV41 WES(XP), CV61 Win7/XP

The CV41 WES and CV61 Win7/XP use the Summit Client Utility to configure the 802.11 abgn

radio. Load the Summit Client Utility from the Start>All Programs>Summit>Summit Client Utility

on the device.

Select “Admin Login” and login to the Summit Client Utility. The default Password is “SUMMIT”

but it is recommend that you change it. If needed, follow the CV41 CE Users Guide for

additional assistance with configuring the device for your WLAN.

Rev 1.15 Page 27

Under the Profile tab make these changes:

Radio Mode = “BG rates full” (Only if the 5Ghz band will not be used.) Power Save = “”CAM” Tx Power = “Maximum”

Rev 1.15 Page 28

Under the “Global” tab make these changes:

Roam Trigger = “-70 dBm” (Set this option to work best for your environment)

Roam Delta = “5dBm”

Roam Period = “5 sec”

BG Channel Set = “1,6,11” (This is optional and should not be set if other channels are used.)

PMK Caching = “OPMK” (Set this if 802.1x is being used)

Admin Password = “Your Password” (Optional but recommended)

Don’t forget to click “Commit” or your setting won’t get saved.

Rev 1.15 Page 29

CN50, CS40 WM 6.1/6.5

The CN50 and CS40 can be configured via Intermec settings. Refer to the User Guide for configuration assistance is needed. These devices don’t have any user configurable roaming options available.

CK3B, CN3, CN4 WM 6.1 Series Computers

The CK3B, CN3 and CN4 are legacy WM 6.1 devices and not much will be discussed in this

document. If help is needed to configure a device, refer to the products User Guide. There are

two options that can be set in the registry that may prove valuable in some specific conditions.

These settings have to do with changing the default RSSI level at which the device looks to

roam and how strong the signal from a different AP needs to be to roam to it. If operating

continually in a marginal coverage area(-75dBm or weaker) these settings can help with

performance because the device will aggressively try to roam. Increase or decrease these

values to reflect the working environment.

[HKEY_LOCAL_MACHINE\Comm\BCMCF1\Parms] RoamTrigger = “-70” (“ “ not needed, look to roam when RSSI is -70dBm) RoamDelta = “5” (“ “ not needed, AP must be 5dBm stronger for device to roam to it)

802.1x Roaming and Key caching table. For 802.1x optimum roaming, it is important to know the type of key caching that is supported on the device. Table 1.0 provides a quick summary of the devices that support OKC as well as suggest RSSI roaming values. When mixing 802.1x devices that support OKC with devices that only support PMK, set the controller to use PMK Caching as PMK caching is supported by all devices.

Table 1.0

Device

Supports Opportunistic Key Caching

(OKC)

Dynamic Scanning

Suggested RSSI roaming

threshold

Roam Delta

Roam Time

CK7x series No X NA NA NA

CN7x series No X NA NA NA

CK3X/CK3R No X NA NA NA

CN51 WM 6.5 No X NA NA NA

CN51 Android TBD NA NA NA

CN50/CS40 No NA NA NA

CV41 CE/WES Yes -70 5 dBm 5 sec

CV61 Win XP/7 Yes -70 5 dBm 5 sec

CK3B/CN3/CN4 Yes -70 5 dBm NA

Rev 1.15 Page 30

Summary

When designing and deploying any WLAN environment, start with the end user

experience in mind. In many cases the Intermec devices along with the Ruckus Wireless

infrastructure are being used in a “mission critical” manner. This means that these

deployments have meaningful impact to the business and the resources using the

technologies. Device connectivity and line of business application performance is

paramount over data throughput for most of these kind of installations.

About the authors and contributors that made this document possible

Clark Richter – Wireless Channels Manager – Intermec by Honeywell

Clark Richter has twenty-four years of experience in the mobile computing and automated data

collection industry. His knowledge and expertise center on the application of specific

technologies, and applied operational business practices for automating mobile and supply

chain workforces. He is an experienced resource for the application of cellular and 802.11

wireless technologies for vertical market mobile computing applications in the distribution,

transportation, field service and direct store delivery application markets.

Randy Rayman – Lead Test Engineer, CNE – Intermec by Honeywell

Randy Rayman is a Lead Test Engineer, CNE at Intermec by Honeywell and has worked at

Intermec since August of 1995. Prior to that, Randy had worked as a Network Engineer,

Systems Analyst and Service Manager at several other companies. Randy's experience

includes extensive work with designing, installing, testing, troubleshooting and supporting any

LAN/WLAN based system down to the protocol level. He is a CNE professional and has held

past IBM, AT&T, and HP/Compaq service certifications. He currently performs all the Wi-Fi

certifications for the Mobile/RFID division of Intermec by Honeywell.

Rev 1.15 Page 31

Deepak Sant – Senior Technical Marketing Engineer – Ruckus Wireless

Deepak Sant is a Sr. Technical Marketing Engineer at Ruckus Wireless and has more than 20

years of experience in wireless communication networks.

John Antoniadis – Pre-Sales Systems Engineer – Ruckus Wireless

John Antoniadis is a Pre-Sales Systems Engineer at Ruckus Wireless. Prior to Ruckus, John

worked at Motorola in various product and system organizations within the Government and

Enterprise Wireless divisions. John's experience includes extensive work with large-scale

systems under development, focused on sub-system integration, protocol analysis and

verification, and interoperability testing. In addition, John has worked extensively with

802.11a/b/g/n systems during the definition and development phases through product launch.

Responsibilities included requirements definition, tools development, sub-system integration,

feature verification, stress and performance testing, interoperability testing, trial support and

troubleshooting.