Avalanche Manager System Manual Version 1.2 Users Guide R1-00001-02 March, 2001

Preliminary Items Covered: • Installation • Configuration and Usage of Avalanche Manager • Configuration and Usage of Avalanche Enabler

Copyright © 2001 by WaveLink Corporation All rights reserved. WaveLink Corporation - Utah Office 6985 South Union Park Avenue Suite 395 Midvale, Utah 84047 Telephone: (801) 255-1777 Fax: (801) 255-9699 WWW: http:\\www.roisys.com, http:\\www.wavelink.com Email: [email protected] No part of this publication may be reproduced or used in any form, or by any electrical or mechanical means, without permission in writing from WaveLink Corporation. This includes electronic or mechanical means, such as photocopying, recording, or information storage and retrieval systems. The material in this manual is subject to change without notice. The software is provided strictly on an “as is” basis. All software, including firmware, furnished to the user is on a licensed basis. WaveLink Corporation grants to the user a non-transferable and non-exclusive license to use each software or firmware program delivered hereunder (licensed program). Except as noted below, such license may not be assigned, sublicensed, or otherwise transferred by the user without prior written consent of WaveLink Corporation. No right to copy a licensed program in whole or in part is granted, except as permitted under copyright law. The user shall not modify, merge, or incorporate any form or portion of a licensed program with other program material, create a derivative work from a licensed program, or use a licensed program in a network without written permission from WaveLink Corporation. The user agrees to maintain WaveLink Corporation’s copyright notice on the licensed programs delivered hereunder, and to include the same on any authorized copies it makes, in whole or in part. The user agrees not to decompile, disassemble, decode, or reverse engineer any licensed program delivered to the user or any portion thereof. WaveLink Corporation reserves the right to make changes to any software or product to improve reliability, function, or design. WaveLink Corporation does not assume any product liability arising out of, or in connection with, the application or use of any product, circuit, or application described herein. No license is granted, either expressly or by implication under any WaveLink Corporation, intellectual property rights. Symbol, Spectrum One and Spectrum24 are registered trademarks of Symbol Technologies, Inc. A portion of this manual describes configurations that take place in the Microsoft Windows environment. Windows is a registered trademark of The Microsoft Corporation. The descriptions provided here are intended only to provide the information necessary to configure specific features of WaveLink Corporation’s Avalanche environment.

About This Manual This manual contains information regarding WaveLink Corporation’s new wireless network management system environment called “Avalanche”. The purpose of this document is to discuss the installation, configuration, and usage of the Avalanche system. In addition, information needed to obtain the product is provided. The target audience for this systems manual consists of Information Technology personnel and RF system administrators. For additional information regarding Microsoft configurations described in this manual, please refer to Microsoft Windows document resources.

ii

Conventions Keystrokes are indicated as follows:

ENTER

identifies a key.

Press A + B

identifies a key sequence. Press and release each key in turn.

FUNC, CTRL, R

identifies a key sequence. Press and release each key independently.

Hold A + B

press and hold the indicated keys while performing or waiting for another function. Used in combination with another keystroke.

Typeface conventions used include.

GUI Screen Text

indicates the name of a control in a GUI-based application or a sub-menu item.

Italics

indicates pop-up window titles, key terms and passwords.

ITALICS

indicates a main menu title.

Terminal

indicates text shown on a radio terminal screen.

URL

specifies a hyperlink to an Internet web site.

Cross-Reference

specifies a reference to another place in the document.

iii

iv

Table of Contents Chapter 1. Introduction to Avalanche How It Works.. .............................................................................................................................. Avalanche Manager ................................................................................................................... Concepts .................................................................................................................................. Avalanche Enabler ..................................................................................................................... System Requirements.. ................................................................................................................ Radio Terminals Supported.......................................................................................................... Why Use Avalanche?.. ................................................................................................................. Additional Information................................................................................................................... License Third Party Applications.. ................................................................................................ How To Acquire Avalanche.. ........................................................................................................ Licensed Version........................................................................................................................ Demo Version.............................................................................................................................

1-1 1-2 1-4 1-7 1-7 1-7 1-8 1-9 1-9 1-9 1-9 1-9

Chapter 2. Installing Avalanche Basic Overview of Avalanche Implementation.. ......................................................................... Install Avalanche Manager.. ....................................................................................................... Avalanche Enabler Setup........................................................................................................... Modify Communication Port Configurations ............................................................................. Setup Serial Ports for Use...................................................................................................... Port Settings........................................................................................................................... Load 3000 Series Mobile Devices with Avalanche Enabler ..................................................... Simultaneous HEX File Downloads.......................................................................................... Load 4000 and 5000 Series Mobile Devices with Avalanche Enabler ..................................... Load 7000 Series Mobile Devices with Avalanche Enabler ..................................................... Configure the Avalanche Enabler............................................................................................. Install Avalanche Software Packages.. ......................................................................................

1-11 1-11 1-12 1-13 1-13 1-13 1-14 1-18 1-19 1-20 1-25 1-25

Chapter 3. Using the Avalanche Manager Avalanche Manager Overview.. ................................................................................................. 1-27 Tree View .......................................................................................................................................................................................... 1-27 List View ........................................................................................................................................................................................... 1-27 Summary View ................................................................................................................................................................................. 1-28

Avalanche Manager Menus........................................................................................................ 1-28 v

File Menu .................................................................................................................................. 1-28 New Site Profile ...................................................................................................................... 1-29 Open Site Profile..................................................................................................................... 1-29 Rename Site Profile................................................................................................................ 1-29 Delete Site Profile ................................................................................................................... 1-30 Copy Site Profile ..................................................................................................................... 1-30 Exit.......................................................................................................................................... 1-30 HexFiles Menu.......................................................................................................................... 1-30 AdvancedAccess Menu ............................................................................................................ 1-30 Tools ......................................................................................................................................... 1-30 Client Update Controls............................................................................................................ 1-30 Show Client Update Monitor ................................................................................................... 1-32 Help Menu ................................................................................................................................ 1-33 About Manager ....................................................................................................................... 1-34 Server Management Tree View.. ................................................................................................ 1-34 Client Management Tree View.. ................................................................................................. 1-35 Software Collections.. ................................................................................................................. 1-35 Software Packages................................................................................................................... 1-36 Selection Criteria .................................................................................................................... 1-37 Selection Criteria Usage ......................................................................................................... 1-40 Terminal Selection within the List View .................................................................................. 1-40 Terminal Information from the List View ................................................................................. 1-42 Detailed Client Controls ............................................................................................................ 1-42 Removing Devices from List View ............................................................................................ 1-43 Deleting a Software Package from Terminal ............................................................................ 1-43 IP Configuration Profiles.. .......................................................................................................... 1-44 Client IP Address Assignment ................................................................................................ 1-44 IP Address Pools .................................................................................................................... 1-45 IP Address Pool Advantages .................................................................................................. 1-46 Miscellaneous Configurable IP Parameters........................................................................... 1-47

Appendix A. Troubleshooting (I can not Ping the Terminal).. ................................................................................................... SLAODI (i.e., Radio Driver) is not Loading .............................................................................. (The RF Terminal still doesn’t Communicate with the Network).............................................. TCP/IP Stack Fails to Load...................................................................................................... (I can not Perform a MAC Level Ping to the RF Terminal) ...................................................... (I can Ping the Terminal).. ......................................................................................................... Terminal IP Address Assignment Problem.. .............................................................................. IP Address not Allocated using Manager IP Pools .................................................................. IP Address is not Acquired via BOOTP ................................................................................... IP Address is not Acquired via DHCP...................................................................................... RF Terminal can not Connect to the Host.. ............................................................................... Software Package Download Problems.. .................................................................................. vi

A-55 A-55 A-55 A-56 A-57 A-59 A-60 A-60 A-61 A-61 A-62 A-64

Terminal does not Attach to the Console ................................................................................. When Using RF ...................................................................................................................... When Using Serial.................................................................................................................. Terminal Attaches but the Console doesn’t try to Download Anything..................................... Terminal Attaches and a Download Begins but Fails............................................................... Fails using RF Connection ....................................................................................................... Fails using Serial Connection................................................................................................... RF Terminal Flash Drive is Full.. ............................................................................................... Contact Us..................................................................................................................................

A-64 A-64 A-65 A-66 A-66 A-66 A-66 A-66 A-68

Appendix B. RF Firmware & Radio Updates RF Firmware and Driver Packages (1 or 2 Mb).......................................................................... B-69

Appendix C. RF Diagnostics Symbol RF Diagnostic Programs.. ............................................................................................ C-71

vii

viii

Chapter 1

Introduction to Avalanche The Avalanche system represents the latest advancements in the management of wireless devices. The improvements focus on ease of installation and on simplified maintenance (reducing total cost of ownership). In addition, many new capabilities are introduced which have never been possible under legacy systems.

How It Works Avalanche uses a form of "push/pull" technology to load software, configurations and other data into the mobile devices. There are three primary components associated with this product: • Avalanche Management Console, referred to as the "Avalanche Manager" • Avalanche Enabler • Packaged Software (e.g. WaveLink’s Telnet Emulation Clients) Figure 1.1 provides a physical overview of the Avalanche environment.

1

Avalanche System Manual

WaveLink's Spectrum24 Avalanche Environment Avalanche Client with Serial Connection

AP

Ethernet

Host T DA SER LD LA

TA

L INA RM TE

Avalanche Manager Avalanche Client with RF Connection Figure 1.1 The Avalanche Spectrum24 Environment

Avalanche Manager The Avalanche Manager consists of software running on a PC connected to a network using any Window Platforms starting with Windows 95. The Avalanche Manager is used for initial site installation and configuration as well as future software updates and device management. The Avalanche Manager network presence is not required for continued RF terminal operation. When present, the Manager may reside anywhere on the LAN with the Access Points or across a WAN if connected via routers. This means that upgrades can be performed from a corporate office rather than travelling to each branch location if the sites are connected to the network with IP protocol. Mobile devices attempt to connect to the Avalanche Manager each time they are booted. When a terminal connects to the Avalanche Manager, either across the network or through one of the attached cradles (using RS232 and/or using a Digiboard multi-port card), the console determines whether an update is available and immediately starts the software upgrade. Once the new software is enabled on the Manager and the terminal is booted, there is no additional user intervention required to start the software update.

2

Introduction to Avalanche

The Avalanche Manager employs site profiles, software collections, and software packages to determine the appropriate software for each particular terminal. A site profile represents a snapshot of all settings, software collections, software packages, and client databases for a particular site. The Tree View, Summary View, and a List View (See Figure 1.2) together provide the visible view of a site profile. A software collection (See Figure 1.2) contains one or more software packages. Software packages (See Figure 1.2) represent products such as the Telnet Clients or third party Avalanche-enabled software packages that run in the mobile devices. Software collections can be configured to restrict the use of the packages they contain to certain mobile devices. For details and examples surrounding the concepts of site profiles, software collections and software packages, refer to Concepts on page 4.

Site Profile Tree View

Summary View

Software Packages Software Collections

List View

Figure 1.2 Avalanche Manager Overview

3

Avalanche System Manual

Concepts Site Profiles A site profile contains all the setup information for a given site and is represented by the combination of the Tree View, Summary View, and List View (See Figure 1.2). This feature is extremely beneficial for those that want to perform mobile site management of the mobile devices using a portable laptop. To aide with the understanding of site profiles, the following example is given. Refer to subheadings within File Menu on page 28 section for more information on site profiles. Suppose a computer hardware distributor who will be referred to as Hardware Unlimited has a main distribution center (DC) in Chicago, and two other DCs in Los Angeles and New York. The company has made the decision to use the Avalanche VT/HP Telnet Clients. In addition, each of these sites are connected via a WAN (Wide Area Network). Furthermore, 6840 mobile devices will be used in Los Angeles, 4040 and 1040 mobile devices with their own special configurations will be used in Chicago, and 1040 mobile devices will be used in New York. Each site has its own customized needs. Here are some of the most common possibilities: • Create three separate site profiles to access a given profile when at the local site using a lap top. Figure 1.3, Figure 1.4, and Figure 1.5 show the three software profile views and their associated software collections. • Configure each site profile with separate software collections. Refer to Help Menu on page 35 for more information. Note: Only one profile view on the Avalanche Manager may be open at a given time.

Figure 1.3 Los Angeles Site Profile

4

Introduction to Avalanche

Figure 1.4 Chicago Site Profile

Figure 1.5 New York Site Profile

Software Collections A software collection is an accumulation of software packages. When Avalanche is installed on a system for the first time, no software collections exist. Software collections are added by either right-clicking on the Software Collections tree item and selecting the appropriate option or installing software packages. Clicking on a software collection displays software collection attributes within the summary view (See Figure 1.5). Status, software package count and target selection are among these attributes. In order for mobile devices to receive software from a software collection, the software collection must be in the Active state. Software collections are set to the Active state when they are created. A target selection for a particular software collection is comprised of conditions that need to be met so that software package(s) within the software collection may be downloaded to a terminal. The number of terminal display rows and the type of terminal keyboard are examples of selection criteria items that may be used. See Help Menu on page 35, for information regarding the usage of software collections in Avalanche.

5

Avalanche System Manual

Software Packages A software package is a product that consists of software files and utilities. Software packages are not hex files, but consist of a group of files. Although Telnet Client software packages contain many of the components found in the LWP versions of the Telnet Client products, LWP Telnet Client products are not supported with Avalanche. It should also be noted that neither LWP nor other support images beyond the enabler are needed in the Avalanche environment. The Telnet Clients and Avalanche-enabled third party software are considered to be software packages. Some of the files a typical Telnet Client software package may contain are: • Configuration files • Batch files • The emulation executable • Host Profile Configuration Utility • Terminal Configuration Utility • Localization Utility Each software package represents an independent application environment within the terminal. Configuration utilities are associated with a given software package, but are typically executed on the Avalanche Manager so as to modify application configuration files. Each software package is usually pre-assigned with a default target selection. For example, a 6840 Telnet Client software package has a target selection of Modelname=6840. This means only 6840 mobile devices can receive this software package. There are software packages that target a complete series of mobile devices. The ATI3000 is such a package. It is targeted for the entire 3000 series line of mobile devices. The Avalanche software packages use the following naming convention: • First letter A stands for Avalanche. • The second letter is for the software product: – T stands for Telnet product. – N stands for Network Controller product. • The third letter is for Emulation type: – I stands for 5250/3270 (IBM) emulation. – V stands for VT/HP emulation. – A stands for all-in-one (5250/3270/VT/HP). • The numbers represent the targeted terminal type(s).

6

Introduction to Avalanche

Click on a software package to view its summary view (See Figure 1.2). Items such as file count, version and software package status are provided. All software packages must be enabled before they may be used. Software packages, by default, are initially disabled so they can be configured before they are downloaded. Software packages can be downloaded via the RF or over a serial connection. For details on how software packages are used within Avalanche, refer to Software Packages on page 36.

Avalanche Enabler The Avalanche Enabler is software that is initially loaded into the RF terminal via a serial connection to the Avalanche Manager on the PC. The Avalanche Enabler enables a managed terminal to receive software packages over RF and permits more than one application to be installed on the terminal. In addition, the Avalanche Enabler allows the user to choose which application to run when more than one is present. See Figure 1.1 for a better understanding of the Avalanche environment.

System Requirements This section discusses what is needed to operate the Avalanche environment. • Any 32-bit Windows Platform (95/98/NT/2000) • A network configured to use TCP/IP protocol • RS232 serial port and/or RS232 digiboard port • Wireless Access Points (Ethernet or Token-Ring) • Symbol mobile devices

Radio Terminals Supported WaveLink’s emulation products are already supported under Avalanche, including 5250, 3270, VT and HP for both TN (standalone) and NC (through a WaveLink gateway) environments. The list of terminal models supported at this time includes: • 46-key PDT 3140 • 35-key PDT 3140 • 46-key LRT 3840 • 46-key PDT 6840 • 35-key PDT 6840 • 47-key PDT 3540 • 54-key VRC 3940

7

Avalanche System Manual

• 54-key VRC 6940 • 27-key WSS 1040 • 35-key PDT 6140 • 46-key PDT 6140 • VRC4040 • VRC5040 • 35-Key PDT 7540 • 46-Key PDT 7540 As new mobile devices are supported by WaveLink, they will automatically include support for Avalanche, with the rare exception of mobile devices without dynamic storage ability. For example, WaveLink is currently working on packages for 3Com Palm Pilot and Symbol CE (Windows Compact Edition) mobile devices. Check the Avalanche web site for the most up to date list of supported devices.

Why Use Avalanche? The Avalanche environment provides the following benefits: • More efficient site installations and software upgrades. • Multiple applications on the same terminal - With appropriate licensing, non-WaveLink applications are supported. • Hands-off updates - No need to gather all mobile devices to perform a software update. • Firmware changes can be done with ease. • Multiple terminal architectures - Palm OS, Windows CE and DOS-based mobile units. • Avalanche Enabler supports BOOTP. • The mobile units can be configured to become a DHCP client. Support includes automatic lease renewal when used with a WaveLink emulation package. • The ability to use a true GUI user interface to modify current emulation parameters in each Telnet Client software package is now available. This new interface is seamlessly integrated with the Management own’s interface. • Host profiles for the Telnet Client software packages can now be configured on the Avalanche Manager. Configuration change is made in one place and received by the mobile devices on their next boot. • The Enabler can use a local broadcast to locate a Avalanche Manager if one was not already assigned. • Multiple cradles can be used to download software using RS232 serial/Digiboard ports.

8

Introduction to Avalanche

Additional Information Please refer to the following resources for additional information regarding the Spectrum24 environment. Some of these documents are referenced in this manual. Part Number

Document Title

70-20244-02

Spectrum24 Telnet Clients for 3270/5250 and VT/HP

70-19725-01

VRC 4000 Product Reference Guide

70-20689-01

VRC 4040 Telnet Client User Guide

Visit the web site of WaveLink Corporation - Utah Office at http://avalanche.roisys.com.

License Third Party Applications Third party applications can be modified to make use of the capabilities the Avalanche environment offers. Contact WaveLink Corporation - Utah Office by email at: [email protected] or (801) 255-1777 to inquire about the details.

How To Acquire Avalanche Licensed Version Contact WaveLink Corporation - Utah Office at [email protected] or (801) 255-1777 (USA) to obtain licensed versions of Avalanche.

Demo Version See WaveLink Corporation - Utah Office’s Avalanche web page (http://avalanche.roisys.com) to acquire a demo version of Avalanche.

9

Avalanche System Manual

10

Chapter 2

Installing Avalanche Basic Overview of Avalanche Implementation 1. Acquire a licensed copy of Avalanche from WaveLink or a demonstration copy from the http://www.roisys.com web site. 2. Install the Avalanche Manager on a Windows PC. 3. Detect ports or add serial ports manually to prepare for the Avalanche Enabler HEX file download. 4. Download the Avalanche Enabler to the RF terminal(s). 5. Configure the terminal’s networking parameters. This can be done on the terminal or through the Avalanche Manager. See IP Configuration Profiles on page 44 details. 6. Install the desired terminal software package(s) onto the Avalanche Manager. If using a Telnet Client software package, configure the host profiles and emulation parameters. Ensure that the desired package(s) is/are enabled. 7. Boot the RF terminal to receive the terminal software package(s). a.

Take the RF terminal out of the cradle to receive the update over the RF.

b. Leave the RF terminal in the cradle to receive the update through the cradle.

Install Avalanche Manager This section describes in detail how to install the Avalanche Manager software. 1. Acquire the Avalanche software. Licensed Avalanche software can be purchased from WaveLink. Demo software is also available on the WaveLink Web Site. SeeHow To Acquire Avalanche on page 9 for more information. Avalanche software is typically distributed in the form of a self-extracting install program. 2. Click on the Start button and then select the Run option. 3. Next, use the Browse button to find the location of the install program. 4. Then click on the program and select OK to start the install process. 5. Follow the instructions on the installation screens. During the install process, The install may detect that the comctl32.dll requires updating. This update must be accepted for Avalanche to function properly.

11

Avalanche System Manual

6. Respond accordingly to the request to place a shortcut on the desktop for the Avalanche Manager. 7. The option to place the Avalanche Manager in the Startup Menu is also presented. Adding the Avalanche Manager to the Startup Menu will cause the Manager to start automatically each time the PC is booted. 8. Check the appropriate boxes near the end of the install to start the Avalanche Manager immediately and view the readme.txt file. The readme.txt file will contain the most recent product information and troubleshooting tips. 9. A dialog box will appear for first time installations asking if the Manager should Auto-detect com ports. Click Yes. Enter in the Advanced Access password access, when prompted. 10. The following screen should appear when the Avalanche Manager has been installed and launched correctly.

Figure 2.1 Avalanche Manager

Avalanche Enabler Setup The Avalanche Enabler is the software that allows mobile devices to communicate with the Avalanche Manager. The Enabler for the Symbol 3000 Series mobile devices comes with the Avalanche Manager. The Enablers for the other series must be obtained seperately. Currently, the Enablers needed for the various other terminal types can be obtained from the http://avalanche.roisys.com web site. This section describes how to download the initial copy of this Enabler. If the user wishes to use features within Avalanche to configure the mobile devices, please see IP Configuration Profiles on page 44 Note: If using a 4000 or 5000 series terminal, continue with Load 4000 and 5000 Series Mobile Devices with Avalanche Enabler on page 19

12

Installing Avalanche

Modify Communication Port Configurations Setup Serial Ports for Use To download HEX images from the console, first tell the console which com ports to use. Note that communication ports used by other software programs or hardware peripherals should be removed from the list of available serial ports. The Avalanche Manager has the ability to download through multiple serial ports at any given time. In addition, the use of Digiboards (Digiboards provide multiple RS232 serial ports) is supported by the Manager. Advance Access mode is required to configure the console. To enter Advanced Access 1. Use the ADVANCEDACCESS pulldown menu. 2. Select the Enable menu item. 3. Enter the default password, access. Click on OK. Automatically Detecting Available Ports

After the installation of the Avalanche Manager, the user is prompted as to whether available communications ports should be detected and used by the Manager. Note that the installer must enter the password, access, to authorize the action. To detect available communication ports on the Manager after it is installed, do the following: Right Click Communications icon in the Tree View and select Auto-detect Available Ports. A message box displaying the results of the port detection will then appear. Manually Adding a Port

To add serial ports available for the Avalanche Manager to use, perform the steps shown here. 1. Right Click on the Communications item in the Tree View. 2. Select Manually Add a Port to add communication ports. Check the status field within the Summary View to verify the availability of a new port added. Removing a Port

To remove serial ports from the Avalanche Manager’s communication tree view, perform the steps shown here. 1. Right Click on the port targeted for removal within the Tree View. 2. Select Delete Port to remove the communication port. A message box appears requesting confirmation of the port deletion. Respond accordingly.

Port Settings Port settings should not be modified from their default setting. The default port communication settings are 38,400 bps, 8 data bits, no parity, and no flow control. Use the Windows utility developed by WaveLink Corporation, called Winhex.exe, for other settings. Winhex, for example, can make connections up to 115,200 bps.

13

Avalanche System Manual

Load 3000 Series Mobile Devices with Avalanche Enabler Follow the steps described here to download a HEX file to a 3000 series terminal. A 3000 series terminal is basically any Symbol terminal which relies on a HEX image for its initial software download. The actual model numbers are 1XXX, 3XXX, and 6XXX. Some example model numbers are 1040, 3840, and 6940. 1. Determine the HEX file needed for implementation. – Use the Ava3-spr_vXX.hex for 3000 series mobile devices with Pre-802.11 firmware. – Use the Ava3-802_vXX.hex for 3000 series mobile devices with 802.11 firmware. Note: The Ava3-spr.hex and Ava3-802.hex are only attempts to match the firmware in the RF terminal. If the terminal radio is not working as expected, the RF update software package (RF3_vXX.exe, XX represents the version) should be downloaded in addition to the Avalanche Enabler because it contains the most recent radio drivers and firmware. When the RF Update software package is used with a serial connection, either Ava3-spr.hex or Ava3802.hex may be used regardless of the firmware type found in the RF terminal. – Use the Ava3-hr_vXX.hex for 3000 series mobile devices using the "High Rate" (11Mb) firmware.

2. To access the Download HEX Files pop-up dialog box, select HEX files and then Download from the Avalanche Manager or right-click the corresponding com port icon and choose Download Hex File. See Figure 2.2.

Figure 2.2 Console Setup with COM1 and COM2

14

Installing Avalanche

3. Specify a com port, a HEX file and an optional WAV file in this dialog figure to download a HEX file to a Series 3000 RF terminal. The port settings are listed to aide in ensuring the same settings are selected on the terminal. A brief description of each of the parameters shown in Figure 2.3 is provided here.

Figure 2.3 Download HEX file Dialog Box

– Communications Port - The physical serial port selected to perform the HEX file download. – Communication Port Status Box - This box displays the current status of the port. Some of the most common messages are available, listening (i.e., waiting for a terminal to communicate with the serial port), and downloading. Error messages are also displayed here when they occur. – HEX file to be Downloaded - This is the name of the HEX file to be downloaded to the RF terminal. The path of this HEX file is also displayed. The path to the 3000 Series Enablers is, by default, Program Files/ROISYS/Avalanche/Client. – Notification Sound - This is optional. Select a sound file (WAV) to play after a download has completed. – Port Settings - The default settings shown below should normally be used to achieve maximum download capacity. Note that some mobile devices default to 7 data bits. In the recent past, multiple RF terminal downloads at 38400 were not possible. Now, using the Avalanche HEX file download utility simultaneous HEX file downloads at 38400 bps with flow control disabled are possible. Refer to Port Settings on page 13 for more information. – Baud:

38400

– Data

8 Bits

– Parity None – Flow

None.

4. Once a valid communications port and HEX file are selected the Download button will become enabled.

15

Avalanche System Manual

5. When the Download button is selected, a pop-up dialog box named after the com port and HEX file name will appear. See Figure 2.4.

Figure 2.4 COM Port and HEX File Dialog Box

6. Now, verify the terminal is turned off by pressing PWR or ON/OFF. 7. Boot the terminal into Command Mode.: 46-key LRT 3840 46-key PDT 3140 47-key PDT 3540 46-key PDT 6840 46-key PDT 6140 54-key VRC 3940 54-key VRC 6940

35-key PDT 6140 35-key PDT 3140

27-key WSS 1040

Power off the terminal. Hold F+I. Press and release PWR. Release F+I. Power off the terminal. Hold A+D. Press and release ON/OFF. Release A+D. Power off the terminal. Hold BKSP+SHIFT. Press and release ON/OFF. Release BKSP+SHIFT. Power off the terminal. Hold FUNC+ENTER. Press and release PWR. Release FUNC+ENTER.

Table 2.1 Command Boot Sequences 8. Use the UP ARROW/DOWN ARROW to select the Program loader function. At any time, press TAB/CLEAR to exit/abort a selection. 9. Place the terminal in the cradle.

16

Installing Avalanche

10. Press ENTER on the terminal to display: Program loader WARNING: EEPROM WILL BE ERASED CONTINUE? Figure 2.5 Program Loader EEPROM Erase

11. Press ENTER to erase the NVM (i.e., Non-Volatile Memory). After erasing the NVM the terminal displays: Comm Parameters Baud 4 9600 Figure 2.6 Program Loader Baud Parameter

12. Use UP ARROW/DOWN ARROW to select the communication parameters. Press ENTER at the end of the selection to accept each selection. Baud Data Bits Parity Flow Control

38400 8 None None

Table 2.2 Download Communication Parameters The terminal displays: Comm Parameters Start? Figure 2.7 Program Loader - Comm Parameters

Note: If the cradle supports multiple mobile devices, prepare each in the same manner.

13. Press ENTER on the mobile devices to display: Program loader Receiving: Figure 2.8 Program Loader - Receiving

14. The Download button on the Avalanche Manager’s COM port/HEX file pop-up window should be enabled at this point. If the Download button fails to become enabled, refer to Troubleshooting on page A-49. Select the Download button to begin the HEX file transfer to the terminal(s). Note: Do not take mobile devices out of cradle during download.

Following a successful download, the Avalanche Manager’s download pop-up window indicates that a successful download has taken place. The terminal displays a status code of 0000 to indicate a successful file transfer. If the terminal displays a status code other than 0000 or times out during download, refer to Troubleshooting on page A-49.

17

Avalanche System Manual

15. Cold boot the terminal after download. To perform a cold boot: 46-key LRT 3840 46-key PDT 3140 47-key PDT 3540 46-key PDT 6840 46-key PDT 6140 54-key VRC 3940 54-key VRC 6940

35-key PDT 3140 35-key PDT 6140

27-key WSS 1040

Power off the terminal. Hold A+B+D. Press and release PWR. Release A+B+D. Power off the terminal. Hold F1+F4+ENTER. Press and release ON/OFF. Release F1+F4+ENTER. Power off the terminal. Hold SPACE+FUNC+UP ARROW. Press and release ON/OFF. Release SPACE+FUNC+UP ARROW. Power off the terminal. Hold RIGHT ARROW+ENTER Press and release PWR. Release RIGHT ARROW+ENTER

Table 2.3 Cold Boot Sequences The Avalanche Enabler should now be installed on the Series 3000 terminal. Proceed to Configure the Avalanche Enabler on page 25.

Simultaneous HEX File Downloads The Avalanche Manager supports the ability to download HEX files to more than one cradle from multiple serial ports simultaneously. For example, to download a HEX file using COM2 while COM1 is being used to download HEX files, do the following: 1. Select another available communications port from the Download HEX files dialog box. 2. Browse to choose another HEX file or the same HEX file being downloaded on COM1. 3. Press the Download button and another dialog box named after the com port and HEX file to be downloaded will appear. See Figure 2.9.

18

Installing Avalanche

4. At this point, prepare the terminal as described in Load 3000 Series Mobile Devices with Avalanche Enabler on page 14 and then press the Download button.

Figure 2.9 Concurrent HEX File Downloads

5. The Enabler is now loaded into the terminal’s NVM drive. The terminal is ready to be cold-booted to activate

Load 4000 and 5000 Series Mobile Devices with Avalanche Enabler Follow these steps to load the Avalanche Enabler into a 4000 or 5000 Series terminal. Note: The Avalanche Enabler for the VRC4040 is called ava4040.exe and for the VRC5040

it is called ava5040.exe. The Series 7000 mobile devices use an Avalanche Enabler with a similar naming convention (e.g. ava7540.exe). Series 3000 mobile devices use ava3-802.exe for 802.11 support and ava3-spr for Pre-802.11 support. This is due to operating system and protocol distinctions. 1. Insert the floppy disk containing the Ava4040.exe or Ava5040.exe file into the external floppy disk drive. The external floppy drive is typically configured as the A: drive. Refer to the VRC 4040 Telnet Client User Guide (Symbol Part Number: 70-20689-01) for more information. 2. Type the following on the VRC 4040 or VRC 5040 command line to install the Enabler from the a:\ prompt. AVA4040 -d or AVA5040 -d c:\

19

Avalanche System Manual

3. The Avalanche Enabler should now be loaded on the VRC terminal. If 802.11 is needed, the RF update software package (RF4_vXX.exe, XX represents the version) must also be installed from the Avalanche Manager using a serial connection. Proceed to Configure the Avalanche Enabler on page 25.

Load 7000 Series Mobile Devices with Avalanche Enabler Follow these steps to load the Avalanche Enabler into a 7000 Series terminal. 1. Run the executable Ava7XXX.exe (where the XXX delineates the specific terminal type) from the temporary directory where it resides. This will create three files within the same directory. – Readme.txt – Hex-kit.exe – Install.bat

2. Run the install.bat file. This will extract the files onto the C: drive into a directory of the same root name (e.g. Ava7540). 3. Boot the terminal into Command Mode.: 7000 Series mobile devices

Power off the terminal. Hold Scan Button + PWR. After approximately 15 seconds, the terminal will boot into Command Mode.

Table 2.4 Series 7000 Command Boot Sequence 4. Observe the first screen that appears. It will resemble Figure 2.10. Elan IPL Ver. 0.28 Copyright 95-98 Symbol Tech Inc Flash Type 0808A Figure 2.10 First Screen after Command Boot

The flash type determines the disk space available: 0400 - 2 Megabytes of disk. 0800 - 4 Megabytes of disk. 0808 - 8 Megabytes of disk. 0818 - 16 Megabytes of disk.

20

Installing Avalanche

5. Select the appropriate baud rate for downloading. Use the Up and Down Arrows to navigate through the screen. Note that the 7000 Series mobile devices have the capability of downloading at rates up to 115,200 bps. This can be successfully done only through the Symbol’s cable P/N 25-37380-01. The optical cradle currently only supports downloading speeds up to 38,400 bps. To download at speeds other than 38,400 bps, it is recommended that the Winhex Utility is used. This can be obtained from the www.roisys.com web page. Otherwise, modify the port settings in the Avalanche Manager to be able to download at speeds other than 38,400. This will take a System Analyst level of access to perform. Note: To obtain this access level, disable the current access level. Then click on ADVANCEDACCESS then click on Enable. The password is fix. Click on OK. a.

Once Systems Analyst access level is obtained, right click on the com port, located in the Tree View, that will be used in downloading.

b. Click on Port Settings. Figure 2.11 is the dialog box that appears.

Figure 2.11 Edit Port Settings

Note: The download acceleration can be modified from here. c.

Click on Modify. A box will pop up asking about disconnecting the com port. Click on Yes.

d. Modify port settings. Only modify the baud rate. All other settings normally will remain the same. e.

Click on Save. Then, click on OK to accept the changes.

21

Avalanche System Manual

Note: Remember to change these settings back to the default settings after downloading the hex files. The default settings are necessary for normal operations.

6. Select Multiple Images from the screen on the terminal. This will allow multiple downloads without having to reboot. 7. Ensure proper connections with cradle or cable. Terminal screen will appear as Figure 2.12 with an improper connection and like Figure 2.13 with a good connection: Insert in Cradle or Connect Power Supply Figure 2.12 Improper Connection on 7000 Series Terminal

Waiting for data Multiple Images 38400 Figure 2.13 Good Connection on 7000 Series Terminal

8. Access the Download HEX Files pop-up dialog box, select HEX files and then Download from the Avalanche Manager or right-click the corresponding com port icon and choose Download Hex File. The box shown in Figure 2.14 will appear. 9. Specify the correct communications port. Browse to the folder created when the executable was ran in step 1 to obtain the correct HEX file. Click on the subfolder Hexfiles and select the correct partition file for the terminal’s flash type. Click Open to select the file.

22

Installing Avalanche

Figure 2.14 Download HEX files Box

Note: If a notification is desired when the downloading is complete, browse for an optional .wav file.

23

Avalanche System Manual

10. Click on Download.When the Download button is selected, a pop-up dialog box named after the com port and HEX file name will appear. See Figure 2.15.

Figure 2.15 COM Port and HEX File Dialog Box with System Analyst Access

Note: Notice the Download Acceleration bar in System Analyst mode.

11. The Download button on the Avalanche Manager’s COM port/HEX file pop-up window should be enabled at this point. Select the Download button to begin the HEX file transfer to the terminal(s). If any problems occur consult Troubleshooting on page A-49. Note: Do not take mobile devices out of cradle during download.

12. Repeat steps 9 through 11, selecting the appropriate Enabler hex file to download. 13. Cold boot the terminal after download. To perform a cold boot: 7000 Series mobile devices

Power off the terminal. Hold PWR. After approximately 15 seconds, the terminal will cold boot.

14. The Avalanche Enabler should now be loaded on the 7000 Series terminal. Proceed to Configure the Avalanche Enabler on page 25.

24

Installing Avalanche

Configure the Avalanche Enabler The mobile devices can be configured manually or through the Avalanche Manager. Refer to the appropriate client user guide to do a manual configuration. To configure the terminal through the Avalanche Manager, an IP Configuration Profile must be created. This will be described in full detail in Chapter 3. Within this profile, a dialog box opens allowing a user to input configuration data which will be downloaded the next time the terminal is booted. Please see IP Configuration Profiles on page 44.

Install Avalanche Software Packages All software packages and configurations targeted for the mobile devices must be installed on the Avalanche Manager. The Manager will distribute software packages and configurations to the mobile devices. See Using the Avalanche Manager on page 27 for information regarding how software packages are managed. Software packages may come on floppy disk or CD media. Each package is a self-installing executable file. Simply execute the package executable and follow the directions on the screen to install a software package. During the software-package installation, the user will be asked to designate a site profile and software collection. Using the tree view of the Manager, a user will be able to perform any configuration needed on each package. Please note that software packages are disabled when they are first installed. This will prevent unwanted downloading of packages before they are properly configured. Refer to the Avalanche section of the www.roisys.com web site for help identifying the software packages that are needed.

25

Avalanche System Manual

26

Chapter 3

Using the Avalanche Manager Avalanche Manager Overview The Avalanche Manager display is segmented into three sections. The sections are the Tree View, List View and Summary View. The information in these views comprises a site profile.

Tree View The Tree View is located on the left. This view shows a hierarchical view of the entire system. The Tree View is divided into two major branches:

Figure 3.1 Main Branches

• Server Management: A list of all Communication Ports, including a list of mobile devices currently associated with each port are displayed. A port may be either a standard serial port, a digiboard serial port or a network connection (IP). Note that all RF communications occur over the network connection. • Client Management: Under this node are listed all of the software collections which are in this site profile. Each collection may contain multiple software packages. Use the right click menus to create/delete/rename collections as well as to copy software packages between them. In addition, the IP configuration profiles are listed and maintained here. Address pools and IP configurable parameters are provided under this branch. Address pools are used to automatically assign IP addresses to mobile devices. While multiple pools can be created, only one will be active at any one time.

List View The List View is located on the bottom right. This view shows a list of known mobile devices which are associated with the currently highlighted item in the Tree View. For instance, when highlighting a particular communications port, all mobile devices which are currently communicating through that port are shown. To see a list of all known mobile devices, highlight the Communications node in the tree. See Figure 3.2.

27

Avalanche System Manual

Figure 3.2 List View

– Type: This displays the terminal type of a given terminal (i.e., 6840, 1040, etc.). – MAC Address: The Media Access Control address of a terminal. This address uniquely identifies this terminal on a network from a physical standpoint. – IP Address: The Internet Protocol Address assigned to the terminal. – Updated?: The check mark means that the terminal is up to date while the universal not symbol indicates that an update is available for the terminal. – Acitivity: The current status of a terminal with respect to the Avalanche Manager. For example, if the terminal is receiving new software, this display item will indicate Downloading. – Details: Software update status is displayed in real time.

Summary View The Summary View is located on the upper right. This view may display more detailed information about the currently highlighted item in the Tree View. If a software package is highlighted, for example, the package type, version number, the number of files included in the package and the Target Selection information is given. In addition, whether the package is On Hold (disabled) or Active (enabled) is listed. Information for a particular terminal is also given if selected from either the Tree View or from the List View. See Figure 3.3. For more details about the terminal, including a list of all packages the terminal should have and the update status of each, click on the More button.

Figure 3.3 Summary View

Avalanche Manager Menus File Menu The Avalanche Manager File pulldown menu is shown in Figure 3.4.

28

Using the Avalanche Manager

Figure 3.4 File Menu

New Site Profile Select New Site Profile from the File Menu or hold the CTRL key while pressing the N key to create a new site profile. Advanced access is required for this operation.

Open Site Profile Select Open Site Profile from the File Menu or hold the CTRL key while pressing the O key to open and use an existing site profile. A list box similar to the one shown in Figure 3.5 will appear when selecting the Open Site Profile option. Advanced access is required for this operation.

Figure 3.5 Site Profile List Box

Note: Only one site profile may be open at a given time.

Rename Site Profile Select Rename Site Profile from the FILE Menu to rename an existing site profile. Enter the new profile name and press the OK button to accept or press the Cancel button to abort the operation. Advanced access is required for this operation.

29

Avalanche System Manual

Delete Site Profile Select Delete Site Profile from the FILE Menu to delete the current site profile. Advanced access is required for this operation.

Copy Site Profile Select Copy Site Profile from the File Menu to make copy of the current site profile. Enter the name of the new profile. Press the OK button to accept or press the Cancel button to abort the operation. Advanced access is required for this operation. After a copy, the new profile can be independently modified without affecting the original.

Exit Select Exit from the File Menu to close the Avalanche program.

HexFiles Menu Select Download to transfer a HEX file to a series 3000 terminal. Refer to Load 3000 Series Mobile Devices with Avalanche Enabler on page 14 for details on downloading.

AdvancedAccess Menu Use the AdvancedAccess Menu to toggle the authority level between advanced access and default access. The sub-menu below advanced access will display enable when the authority level is at default access or disable when using advanced access. Many critical operations require advanced access. Select the Enable item under the AdvancedConfig pulldown menu to enter the password. For advanced access, type access in the password field. For Systems Analyst access, the password is fix.

Tools This menu contains the tools for scheduling and monitoring of software package updates and deletions.

Client Update Controls Within the Tools Menu, select this option to schedule software package updates, manage orphaned packages, and also an option to manage the network bandwidth by limiting the number of simultaneous downloads. See Figure 3.6.

30

Using the Avalanche Manager

Figure 3.6 Client Update Controls Network Bandwidth Management

These options allow an adminstrator to restrict the maximum amount of network bandwidth that will be used at any one time for client updates. These configurations apply to both client and server initiated updates. In the absence of critical bandwidth shortage, unrestricted updates can be safely allowed. In addition to this option, other methods can be used to help minimize network impact: • Rely on client-initiated updates. After performing updates at the console, allow each client to receive the changes when they next synchronize. The progress may be checked at the console at any time to see which mobile devices have contacted the console and which are yet to be updated. • Schedule a server-initiated update for off-peak hours. Using the options described below, the console can update all the mobile devices during the night or at any convenient time when the network and the clients are not otherwise being used. Scheduled Client Updates

This option allows the administrator to schedule a server-initiated global update. Click the box next to Schedule an update to start the process. Now click on the arrow next to the date to select a day from a pop-up calendar (or directly edit the date fields.) Click on the time fields and use the arrow buttons to select the time of day or night when the updates should occur. To monitor the status of a current update or to see the results of one that previously completed, select Show Client Update Monitor from the Tools pull-down menu. See Show Client Update Monitor on page 32 for more details.

31

Avalanche System Manual

Note: Note: For clients which go to sleep when idle to preserve battery life, a certain level of Access Point (AP) firmware is required to allow the console to wake the clients up. Contact a Symbol or reseller representative to see if the APs already have the appropriate update. If a firmware update is required, it is a very simple process that can be done without removing any equipment. Cleanup of Unused Packages

If there are downloaded software packages on the mobile devices which are no longer needed, Avalanche can delete them. To perform this process, follow these steps: 1. Make sure the configuration currently on the console exactly matches what is expected of each client to have. 2. Review the information on the console about the mobile devices to confirm that the correct software will be removed. To do this double-click on the mobile devices from the List View and observe the list of current packages shown. Those packages that the terminal has which the console thinks it should not have are marked as Orphaned. 3. Go back to the Client Update Controls dialog and select Mark all orphaned packages in the clients for deletion. Note that a user can also select Delete Orphaned Packages in individual clients’ control dialog as well. 4. The packages will be deleted the next time each client is synchronized. A button is also supplied to cancel all scheduled deletions in case of an error.

Show Client Update Monitor This window, under the TOOLS menu item, shows the current status of an ongoing global update or the results of a previous one if an update has completed. See Figure 3.7

Figure 3.7 Client Update Monitor

The fields shown include:

32

Using the Avalanche Manager

Total # of Clients

The total number of clients registered with the console at the start of the update.

Scheduled for Update

How many clients were seen as needing an update.

Updated So Far

How many clients have completed the update so far. (Only applies while an update is active.)

Currently Updating

How many clients are updating right now (Only applies while an update is active.)

Failed Update Count

How many clients (so far) have failed to respond to the update command. These may be out of range or completely powered down. The main display’s List View will show which clients still need updating and they can be handled independently or by scheduling another global update.

Help Menu Choose the Help Topics menu item to access help information for the Avalanche Manager. See Figure 3.8. The Help Topics item is divided into three sections: • Contents - This section provides an overview of the program purpose and basic functionality of the Avalanche Manager. • Index - The index provides reference material associated with topics relevant to the Avalanche Manager. Enter the letters associated with the topic under investigation and the highlight bar within the list box moves to the closest possible match. • Find - Use keywords to search for a desired topic.

33

Avalanche System Manual

Figure 3.8 Help Dialog Box

About Manager Select this submenu to find the version number of the Avalanche Manager. For demo releases, this screen indicates the number of days remaining before the demonstration period expires.

Server Management Tree View The Server Management branch of the Tree View provides access to the communications resources on the console. An RF LAN icon will always be present under the Communications tree in addition to one or more serial ports. Click on the RF LAN icon to view the MAC address and IP address of the LAN adapter within the Avalanche Manager. Right click the Communications icon to autodetect or manually add com ports. Right click com port icons to access the following functions: • Download Hex File • Delete Port • Port Settings

34

Using the Avalanche Manager

Refer to Modify Communication Port Configurations on page 13 for more details on these functions.

Figure 3.9 Server Management Tree

Client Management Tree View The Client Management branch of the Tree View provides the ability to manage software collections and IP Address Pools. A software collection contains one or more software packages. Software packages represent products such as the Telnet Clients or third party Avalanche-enabled packages that run in the mobile devices. Software collections can be configured to restrict the use of the packages they contain to certain mobile devices. The selection criteria can also be based upon IP or MAC addresses. In addition, most packages already restrict themselves to the appropriate terminal type. IP Pooling allows the Avalanche Manager to automatically assign IP information such as the IP Address to mobile devices through a serial connection.

Software Collections Opening a software collection branch shows all the software packages associated with that collection. In Figure 3.10 the Summary View shows the software package count, the target selection and status of a software collection. The target selection specifies the conditions that need to be met for the software package in the software collection to be downloaded to a terminal. Notice the example shown in Figure 3.10 does not have a target selection configured. In this case, any terminal may receive those packages, however the packages themselves may provide further target selection criteria. Furthermore, clicking on the software collection will show all the mobile devices eligible (based upon target selection of software collection only) to receive software packages from the collection.

35

Avalanche System Manual

.

Figure 3.10 Software Collection - Main

Right-clicking on the software collection displays the software collection context menu (See Figure 3.11). This context menu allows the user to perform such functions as configure the collection, enable/disable the collection, rename the collection, delete the collection, or copy the collection. Advanced access is required to perform any of these functions.

Figure 3.11 Software Collection Context Menu

Right-click on the software collection and select Configure Collection from the context menu to specify the selection criteria for the software collection. Selection criteria is displayed with the target selection prompt on the Summary View screen. Refer to Software Packages on page 37 for help constructing a selection criteria string.

Software Packages A software package consists of an application and support files it requires. There are three types of software packages: • Application • Support • Auto Application software packages are added to the APPLICATION MENU in the terminal. Support packages typically contain updates to existing software packages or to the Avalanche

Enabler. They do not add new items to the mobile devices application menu. The Ava3 DHCP update software package is an example of a support package. Auto packages are software packages that are downloaded to the RF terminal and executed

immediately upon successful download. Like the support packages, Auto packages do not modify the application menu. RF firmware upgrade packages are examples of Auto packages.

36

Using the Avalanche Manager

Click on a software package to see the Summary View for the software package. The Summary View indicates the package type, version, file count, target selection, and status of the software package (See Figure 3.12). Target selection is set to the terminal type or types the software package will service. For example: a VRC 4040 software package will automatically prevent itself from downloading to a PDT 6840. All mobile devices that meet the target selection of the software collection and software package are displayed in the List View when clicking on a given software package.

Figure 3.12 Software Package - ATV1040

Right-click on the software package and its context menu appears as displayed in Figure 3.13. This menu provides the ability to configure, enable/disable, delete, and copy software packages. Advanced access is required to perform any of these functions. The Configure Package context menu item is enabled when configuration utilities are available for the software package.

Figure 3.13 Software Package Context Menu

Selection Criteria A set of rules (referred to as Selection Criteria) may be applied to software packages and/or to groups of packages (software collections) to direct which mobile devices need to receive that software. Software collections by default have an empty selection criteria (meaning they apply to all mobile devices) but criteria can be added or modified at any time by the user. The selection criteria associated with a particular software package is set by WaveLink and can not be modified by the user. The following gives a brief description of how to form a criteria expression. A Criteria String is a single expression (much like a mathematical expression) which takes a set of variables which correspond to different aspects of a terminal and compares them to fixed values. The syntax includes parenthesis and boolean operators to allow flexible combination of multiple variables.

37

Avalanche System Manual

Selection Variables

– IP: IP address of the terminal. – MAC: MAC address of the terminal. – ModelName: The standard model name for a device. This is often a number but it can be alphanumeric as well. Examples include 6840, 3940, 4040. If the model number is unknown, it may be in the views when the terminal is highlighted. For a quick summary of all the following values, highlight a terminal in the List View, then choose “More...” from the top-right of the Summary View. – KeyboardName: A string depicting which style of keyboard the terminal is using (46key, 35key etc.) – Series: The general series of a device. This is a single letter: ‘3’ for Symbol ‘3000’ series mobile devices, ‘7’ for Symbol ‘7000’ series mobile devices, etc. – ModelCode: A number which is used internally by Symbol’s terminal BIOS to identify the hardware. – KeyboardCode: A number which is used internally by Symbol’s terminal BIOS to identify the keyboard type. – Rows: The number of display rows the terminal supports. – Columns: The number of display columns the terminal supports.

Other variables may be added in future releases. Check the on-line help on the console for the most recent list. Syntactical Symbols

The following operators can be used along with any number of parenthesis to combine multiple variables. (Nesting of parenthesis is allowed.)

Not (or !)

Unary operator which negates the boolean value that follows it.

And (or &)

Binary operator which results in TRUE if and only if the expressions before and after it are also both TRUE.

Or (or |)

Binary operator which results in TRUE if either of the expressions before and after it are also TRUE.

Eq (or =)

Binary operator which results in TRUE if the two expressions on either side of it are equivalent.

Table F.5 Selection Criteria Boolean Operators Numbers and strings can be placed directly in the expressions, with or without quotes. Expression variable names and values are not case sensitive. For instance:

38

Using the Avalanche Manager

modelname=6840, ModelName=6840, ModelName = 6840, and ModelName="6840" are all valid expressions. All expressions are evaluated from left to right. There is no operator precedence. In more complex expressions, parenthesis must be used for the expression to be evaluated properly. For example: ModelName=3840 or ModelName=6840 and KeyboardName= 46Key In this example, the logical operators do not take precedence over the evaluation of the individual arguments (i.e., ModelName=3840 is considered an argument) because there are no parenthesis surrounding the individual arguments. The same expression with Parenthesis: (ModelName=3840) or (ModelName=6840) and (KeyboardName= 46Key) Here the and operation is performed with 6840 and 46Key and the or operation is performed on the result. In English terms, the expression states that either 3840 mobile devices regardless of keyboard type or 46Key 6840 mobile devices will receive the software package. Additional Examples: The illustration shown here will allow either 6840 or 3840 mobile devices to receive software packages. Note that the spaces around the equals and other operators is optional. (ModelName =6840) or (ModelName = 3840) All mobile devices with 20 rows will receive the software packages within the collection except for those with 35Key keyboards in the following example. Not (KeyboardName = 35Key) and (Rows = 20) IP Addresses are entered in dotted notation. They can be compared in three ways:Direct comparison with a single IP address. For example “IP = 10.1.1.1”. • Comparison with an arbitrary address range. For example, “IP = 10.1.1.5 – 10.1.1.15” (This can also be written “IP = 10.1.1.5 – 15”.) • Comparison with a subnet number. This is done by supplying the network number along with the netmask or CIDR value. For example, “IP = 10.1.1.0/255.255.255.0”. Using CIDR notation, this can also be written as “IP = 10.1.1.0/24”.

MAC Addresses are entered as a string of hexadecimal digits. Dashes or colons between octets are optional. For convenience, the address can be shortened by entering just the rightmost portion (any number of digits, up to 12.) For example: “MAC = 00:A0:F8:85:E8:E3”, or “MAC = 85E8E3”

39

Avalanche System Manual

Selection Criteria Usage Use these steps to add or modify selection criteria for a given software collection. 1. Click on the software collection to be configured. 2. Right-Click on the software collection to access its context menu. 3. Select Configure Collection from the context menu. 4. Enter the appropriate selection criteria for the software collection and press the OK button. Refer to Figure 3.14.

Figure 3.14 Software Collection Selection Criteria

Note: Having difficulties remembering the syntax and this manual isn’t present? Press F1 for an Avalanche Console Help window to pop up. Click on the Using Software Collections and Selection Criteria link and read the instructions found there.

Terminal Selection within the List View The subset of mobile devices seen in the List View is dependent upon the current selection made in the Tree View. Clicking on a software collection will show all the mobile devices in the List View that match that collection’s selection criteria. Clicking on a software package in the tree will show all the mobile devices in the List View that match both the selection criteria of that package and that of the software collection which contains the package.are eligible to be serviced by the software package. The basis for service in this case is based upon the target selection of the software collection and the software package. Figure 3.15 shows the mobile devices in the List View that meet the target selection for the ATV1040 software package. Figure 3.16 shows the mobile devices in the List View that meet the target selection for the 4040 software package. Figure 3.17 shows the mobile devices in the List View that meet the target selection for the Main software collection. Notice that the Main software collection has no target selection so all mobile devices known to the Avalanche Manager will be shown.

40

Using the Avalanche Manager

Figure 3.15 Filter of 1040 mobile devices

Figure 3.16 Filter of 4040 mobile devices

Figure 3.17 Filter of Main Software Collection

41

Avalanche System Manual

Terminal Information from the List View Click on an RF terminal within the List View to show more specific data about the RF terminal in the Summary View. The Summary View displays items such as the model and the date and time the RF terminal was last active. Click on the More button to view Detailed Client Controls for the RF terminal (See ). This window displays items such as the software packages available for the RF terminal, software package status with respect to the RF terminal (i.e., Active, Update Pending, etc.), and the associated version numbers of the software packages. Right-clicking or double-clicking on an RF terminal also provides access to Detailed Client Controls. For further information on the other features found within this window, see Detailed Client Controls on page 42 .

Figure 3.18 Detailed Client Controls Window

Detailed Client Controls The Detailed Client Controls window contains, in addition to specific information about the RF terminal, features that interact with the RF terminal. This window contains the following features, starting from the top down. • Detailed information about the RF terminal. • List boxes informing the user as to the current activity or status of the RF terminal. This is the same information given under the Activity and Detail columns under the List View of the Avalanche Manager. • List box listing current packages installed on the RF terminal with revision information and status.

42

Using the Avalanche Manager

• Check box to allow for the deletion of orphaned packages (packages which have been disabled). The status of the package will change to "Deletion Pending." The package will then be deleted after the terminal reboots. See Terminal Information from the List View on page 43. • A Send a Text Message area which allows a message to be entered and sent to the RF terminal with an option to send a continuous beep. This option will continue to send a beep until the user hits the CLEAR button. • A button to "ping" the terminal, Ping Client. This is not an "ICMP"-level ping, but rather an application level status check. This feature will tell whether the RF terminal is active or not. • A button to force an update, Update Now. This will cause the RF terminal to reboot. There is a check box to allow the user to have an opportunity to override this command, in case he may be in a critical point of operation. The user has 15 seconds to override the reboot command. Note: The Control Status field on the bottom of the window allows for monitoring of the status of the control feature being used

The options that communicate directly with the mobile unit (Text Messaging, "Ping", Forced Update) will only respond if the terminal is currently running an Avalanched-enabled application or certain configuration utilities. To close the Detailed Client Controls window, click on the Close button.

Removing Devices from List View Under normal operation, the console maintains a device in its database to help track current softwae levels, etc. However, If removing the record from the database is desired, a method is provided. Perform the following steps to remove a mobile unit from the List View. 1. Right-click on the RF terminal targeted for removal within the List View and select the Remove Client from Database item from the context menu. 2. A prompt appears asking for confirmation of this operation. Press the Yes button to confirm removal of the RF terminal from the Avalanche Manager database or no to keep the RF terminal in the database.

Deleting a Software Package from Terminal Perform the following steps to delete a specific software package from a terminal. 1. Locate the software package you want to delete from the Tree View. 2. Right-click on the software package icon and select Disable Package from the context menu. The software package should display an orphaned status in the Detail Client Controls Window. See Figure 3.18. Disabling a package will cause the List View to go blank, indicating that no devices are directed to use this application. 3. Click on the software collection where the software package resides to regain mobile devices’ visibility in the List View.

43

Avalanche System Manual

4. Right-click on the terminal withing the List View and select Detail Client Controls. See Figure 3.18. 5. Check the Delete Orphaned Packages checkbox. Click Close. 6. Cold or warm boot the terminal to initiate the deletion of the software package from the terminal.

IP Configuration Profiles This option under the Client Management branch of the Tree View allows a user to download configuration information for the RF Terminal through the Avalanche Manager. Please see Client IP Address Assignment on page 44 for information on obtaining a client IP address. For further configuration parameters, see Miscellaneous Configurable IP Parameters on page 47.

Client IP Address Assignment There are four options for obtaining a client IP address. See Figure 3.19 • Manual entry of IP address onto RF terminal. • Obtaining IP address from a created IP Address Pool. • Obtaining IP address from a DHCP server. • Obtaining IP address from a BOOTP server.

For more information on the advantages of using the IP Address Pool option, see IP Address Pool Advantages on page 46. Please note that IP Addresses must be downloaded through a serial connection.

44

Using the Avalanche Manager

Figure 3.19 Client IP Configuration Profile

IP Address Pools IP Pooling uses configured IP ranges on the Avalanche Manager to assign an IP Address to an RF terminal. For convenience, multiple pools can be created, though only one is active at any one time. Perform the following steps to add and activate an IP Address Pool. 1. Right-click on the IP Configuration Profiles icon to create an IP Address Profile. 2. Enter the name for the new IP Address Profile in the field provided. 3. Expand the IP Configuration Profiles branch to view the new IP Address Profile. 4. Right-click on the newly created IP Address Profile and choose View/Edit this profile. The Client IP Configuration Profile window will open. See Figure 3.19. Note: This window can also be opened by double-clicking on the IP Address Pool or by highlighting the pool and clicking on the View/Edit Configuration button located in the Summary View.

5. Press the Manage IP Address Pool Button to add IP Addresses to the pool (see Figure 3.20). Select the Add button on this dialog box to add a single IP address or a range. A range can be specified by providing the first and last addresses in the range, separated by either a space or a dash.

45

Avalanche System Manual

6. To remove addresses, select one or more from the list and select the Remove button. The following. When removing IP Address entries, Windows selection conventions are supported by this list box. Common selection conventions are described here. • Press and hold the Ctrl key and click on specific non-contiguous IP Address entries. • Press and hold the Shift key and click on the first and last entry of a contiguous block of IP Addresses.

Figure 3.20 IP Address Pool

7. Close the IP Address Pool dialog box. 8. Right-click on the IP Address Profile to designate it as the default profile. 9. Right-click on the IP Address Profile to activate, delete, or rename it. Refer to the Summary View for IP Address Pool status information.

IP Address Pool Advantages Avalanche fully supports BOOTP and DHCP, but there are advantages to using an IP Address Pool over the other methods: 1. There is no server that has to remain up as a “weak link”. If a BOOTP or DHCP server goes down then all clients who use it become inoperable when the lease expires. 2. All networking parameters can be configured through the connection to the console. It becomes possible to set up an entire site without typing anything into any terminal. 3. Easy to manage IP addresses. This especially becomes critical if IP addresses are used for Selection Criteria. See Selection Criteria on page 37.

46

Using the Avalanche Manager

Miscellaneous Configurable IP Parameters The following parameters can be configured from this part of the Client IP Configuration Profile window. • Router Address • Netmask • ESS ID (RF Domain) • Avalanche Manager (IP Address of where the Avalanche Manager resides) • Default DNS Domain • Up to three DNS Server addresses

To download any or all of these parameters, simply click on the check box to the right which will enable the parameter. This will ungray the box enabling the input of the appropriate data. Once all the desired boxes are filled in, click the OK button to accept the changes. The next time a RF terminal is rebooted, it will receive these parameters. ESS_IDs, netmask, router address, DNS information, and the address of where the Avalanche Manager resides can all be downloaded via a serial or RF connection. A terminal must be properly configured before a RF connection can be performed. Note: IP addresses must be downloaded through a serial connection at this time.

47

Avalanche System Manual

48

Appendix A

Troubleshooting This section is designed to assist system administrators with the most common problems encountered when using the Avalanche product. The first portion of this appendix displays a summary of problems while the second portion provides additional details to resolve them. The summary is grouped in the following manner. • Problems Downloading a Hex File - Page A-49 • Problems Synchronizing with the Console - Page A-51 • Enabler Configuration Problems - Page A-53 • Host Communication Problems - Page A-54

Problems Downloading a HEX File Problem: Download button is gray or not enabled on the Download HEX files dialog box.

Possible Cause: • Incorrect Port Selected • No hex file selected

Problem: Download button is gray or not enabled on the communications port dialog box (See Figure A.1).

Possible Cause: • Null modem cable is not found, not connected properly, defective or damaged. • Cradle is not powered or powered with the wrong power supply. • The RF terminal is not seated properly within the cradle.

A-49

Avalanche System Manual

Figure A.1 Communications Port Dialog Box with Configuration Problem

Problem: Download button is gray or not enabled on the communications port dialog box on the Avalanche Manager (See Figure A.1). Awaiting DSR appears momentarily on the RF terminal and then Status 0020 is displayed.

Possible Cause: • A straight through cable is employed rather than a null modem cable..

Problem: Communications port dialog box on the Avalanche Manager displays a status of "Download Aborted - Lost DSR" and the terminal shows a status of 0004.

Possible Cause: • The parity setting on the RF terminal does not match that of the Avalanche Manager.

Problem: One of the status codes in Table A.1 appears on the RF terminal.

Possible Cause: • Refer to Table A.1 for status code meanings. • Status code 0200 during download indicates poor communications between the Avalanche Manager and the cradle. This may be due to the integrity or length of the cable.

A-50

Troubleshooting

. Status Code Meaning

0000 0002 0004 0008 0010 0020 0080 0100 0200 0400 0600 0800 1000 2000 4000

Download was successful Receive overrun error Receive parity error Receive framing error Programming voltage not present DSR or CD not detected on open ABORT key hit during comm CD lost during session Illegal Intel hexadecimal record Unsupported Intel record NVM EEPROM failed to erase Receive time-out error Control start character time-out Clear To Send inactive time-out error Receive buffer full

Table A.1 Download HEX file Communication Status Codes

Problem:

Communications port dialog box on the Avalanche Manager displays a status of "Download Aborted - Lost DSR" and the terminal shows a status of 0040 after a download has begun.

Possible Cause: • The terminal was pulled out of the cradle during the middle of the file transfer. • The cradle lost power during the file transfer.

Problems Synchronizing with the Console Problem: Terminal does not attach to the console using RF.

Possible Cause: • Network setup is configured incorrectly on the Avalanche Manager. • Terminal network setup is incorrect. • Either the Avalanche Manager’s or Terminal’s IP Address is already used. • The Avalanche Manager configuration within the terminal is wrong.

A-51

Avalanche System Manual

Solution! – Refer to When Using RF section under Terminal does not Attach to the Console on page A-64 to determine what the problem is.

Problem:

Terminal does not attach to the console using a serial connection.

Possible Cause: • A full null modem cable is not being used. • Cable is defective.

Solution! – Refer to When Using Serial section under Terminal does not Attach to the Console on page A-64 to determine what the problem is.

Problem:

Terminal attaches but the console doesn’t try to download anything.

Possible Cause: • The software package is not enabled. • The Software Collection is not enabled. • The software package may have already been downloaded to the terminal. • Target selection configuration for the software collection or software package may exclude the terminal from receiving the software package.

Solution! – Refer to Terminal Attaches but the Console doesn’t try to Download Anything on page A-66 for details.

Problem:

Terminal attaches and a download begins but fails when using serial or RF connection.

Possible Cause: • Poor network conditions exist. • Cradle or null modem may not meet the necessary specifications.

Solution! – See Terminal Attaches and a Download Begins but Fails on page A-66 for details.

A-52

Troubleshooting

Problem:

Terminal will not receive a software package that the console is trying to send.

Possible Cause: • Terminal flash disk is full.

Solution! – See RF Terminal Flash Drive is Full on page A-66 to resolve this issue.

Enabler Configuration Problems Problem: I can not ping the terminal. The RF terminal is not communicating at all.

Possible Cause: • There is a mismatch between firmware and the RF Driver. • TCP/IP Stack is configured improperly. • TCP/IP Address assignment method (i.e., IP Pooling, BOOTP, DHCP) is not set up correctly. • The Network ID (i.e., ESS_ID) does not match that of the RF network. • APs in the vicinity may not have antennas connected. • The terminal MAC Address may not be included in an enabled AP Access Control List.

Solution! – See (I can not Ping the Terminal) on page A-55 to assist with the solution. – See Terminal IP Address Assignment Problem on page A-60 to assist with the answer.

Problem: I can ping the terminal but the RF terminal is not communicating.

Possible Cause: • No host profile is configured for the Telnet Client software application selected. • The IP Address is also used by another node on the network.

A-53

Avalanche System Manual

Solution! – See (I can Ping the Terminal) on page A-59 to assist with the solution.

Host Communications Problem: RF Terminal can not connect to the host.

Possible Cause: • No Telnet software packages are found on the RF terminal. • A host profile is not configured for the Telnet software package in use. • An error message has occurred after an attempt to connect to the host was made.

Solution! – Refer to RF Terminal can not Connect to the Host on page A-62 for resolution assistance.

A-54

Troubleshooting

RF Terminal is not Communicating at all (I can not Ping the Terminal) SLAODI (i.e., Radio Driver) is not Loading • This is most likely due to a firmware mismatch. Refer to RF Firmware and Driver Packages (1 or 2 Mb) on page B-69. Figure A.2 shows an example of a unsuccessful radio driver load when the RF terminal boots. Watch an RF terminal carefully after a boot is performed to view the data indicating an unsuccessful radio driver load. Furthermore, when accessing the Radio Configuration function in this state, the Terminal Info item within the Radio Parameters sub-menu displays a screen similar to that shown in Figure A.3. SLAODI-DOS-6: The ad apter did not initia lize. SLAODI did no t load. Strike a key when re ady . . . Figure A.2 Unsuccessful Radio Driver Load

S24CFG V5.27 Radio Driver Not Loaded Press a key. . . Figure A.3 Terminal Info Also Displays Unsuccessful Radio Driver

SLAODI (i.e., Radio Driver) Driver Loads (The RF Terminal still doesn’t Communicate with the Network) • The SLAODI (i.e., radio driver) driver loaded, but the terminal can not be pinged. Perform the steps described here to determine whether the problem is an RF problem or a TCP/IP configuration issue. 1. Telnet to the AP from a TCP/IP network node that has a VT100 Telnet Client. 2. After logging into the AP, select Show Mobile Units from the MAIN MENU. If the MAC Address does not reside in the Mobile Units table, proceed to (I can not Perform a MAC Level Ping to the RF Terminal) on page A-57. If the MAC Address does appear in the Mobile Units table, highlight the MAC address in the Mobile Units table and select the AP ping option to perform a MAC Address ping to the RF terminal. Once the ping is started a screen similar to the one in Figure A.4 appears.

A-55

Avalanche System Manual

3. Follow the instructions on the screen to perform the ping. Note the number of pings transmitted and received. If no pings are received from the RF terminal, proceed to (I can not Perform a MAC Level Ping to the RF Terminal) on page A-57. 4. If the MAC level ping is successful, confirm the IP Address, the Subnet Mask, and IP Router Address with the Network Administrator.

Figure A.4 AP Ping Function Screen

TCP/IP Stack Fails to Load Review the following items in the order presented when this condition occurs. • No Terminal IP Address is specified in the Radio Configuration function. • BOOTP/DHCP setting does not acquire the IP Address. Refer to Terminal IP Address Assignment Problem on page A-60. • The IP Address assigned to the RF terminal is already assigned to another RF terminal. Perform the following steps to confirm. 1. Power the RF terminal off. 2. Ping the RF terminal from another TCP/IP node on the network. The example shown in Figure A.5 demonstrates a ping performed from the Run dialog box on a PC using Windows NT 4.0.

A-56

Troubleshooting

3. If a response is achieved, this signifies another network node is using this IP Address. Contact the Network Administrator to attain a new IP assignment for the RF terminal.

Figure A.5 Successful Ping from Windows NT 4.0 Machine

SLAODI (i.e., Radio Driver) Driver Loads (I can not Perform a MAC Level Ping to the RF Terminal) Check the following items in the order described: • The RF driver and firmware could be mismatched. For example, the RF terminal could be using 802.11 firmware and the radio drivers could be Pre-802.11. Perform the steps displayed here to determine whether the RF terminal is using 802.11 or Pre-802.11 (i.e., Spring) firmware. 1. Access the AVALANCHE CLIENT CONFIGURATION (i.e., CONFIG MENU), FUNC, CTRL, R. Enter password, system. Type ’Y’ to confirm terminating an active session. 2. From the CONFIG MENU, choose Radio Parameters. 3. At the RADIO MENU, select Terminal Info. 4. Verify the Firmware Version displayed on this screen. A version beginning with 3 indicates the RF terminal is utilizing Pre-802.11 (i.e., Spring protocol) whereas a firmware version beginning with a 4 specifies 802.11 protocol usage. See Figure A.6. S24CFG V5.27 Spr MAC Address: 00-A0-F8-10-2E-6B Firmware Version: V3.21 970819 Diagnostics eXit Figure A.6 RF Terminal Info Screen

5. Press the X key to exit this screen..

• There may be a mismatch between the Access Points and the mobile devices. In this case, the AP may employ 802.11 radio protocol and the RF terminal may employ the Pre802.11 protocol or vice versa. Do the following to verify the type of AP: 1. Telnet to the AP from a TCP/IP network node that has a VT100 Telnet Client. 2. Type the password, Symbol, at the prompt to log into the AP. Press ESC to bring up the MAIN MENU of the AP.

A-57

Avalanche System Manual

3. Select Show System Summary from the MAIN MENU. Note the AP Firmware Ver. A version beginning with 3 indicates the Access Point is utilizing Pre-802.11 (i.e., Spring protocol) whereas an AP Firmware Ver. beginning with a 4 specifies an AP using the 802.11 protocol. See Figure A.7. 4. Press CTRL + D to terminate the Telnet Session.

Figure A.7 System Summary of 802.11 Access Point

• The Access Points may not have an antenna attached or an incorrect antenna may be installed. • The Network ID (i.e., ESS ID) may be configured incorrectly. a.

Check the Network ID on the RF Terminal. 1. Access the AVALANCHE CLIENT CONFIGURATION (i.e., CONFIG MENU),FUNC, CTRL, R. Enter password, system. Type ’Y’ to confirm terminating an active session. 2. From the CONFIG MENU, choose Radio Parameters. 3. At the RADIO MENU, select Radio Parameters. 4. Note the active RF Network ID. This must match the Network ID being used in the Access Point.

Note: Within the CONFIG MENU, Function 1 provides help to maneuver on appropriate screens b. Check the Network ID within the Access Point. 1. Telnet to the AP from a TCP/IP network node that has a VT100 Telnet Client. 2. Type the password, Symbol, at the prompt to log into the AP. Press ESC to bring up the MAIN MENU of the AP. 3. Select Show System Summary from the MAIN MENU. Note the AP Net_ID. It should match the Network ID configured in the RF terminal. See Figure A.7.

A-58

Troubleshooting

4. Press CTRL + D to terminate the Telnet Session.

• Verify if the Access Control List Feature is being used in the Access Point. If it is, confirm that the MAC Address of the RF terminal is in the Allowed Mobile Units list. Use theses steps to confirm: 1. Telnet to the AP from a TCP/IP network node that has a VT100 Telnet Client. 2. Type the password, Symbol, at the prompt to log into the AP. Press ESC to bring up the MAIN MENU of the AP. 3. Select Show System Summary from the MAIN MENU. Note whether Access Control is enabled or not. Now, choose Select Access Control List to view the Allowed Mobile Units for the AP. If the RF terminal being used is not in the list it will not be able to communicate with the network. See Figure A.8. 4. Press CTRL + D to terminate the Telnet Session.

Figure A.8 AP Access Control List

RF Terminal is not Communicating (I can Ping the Terminal) Check the following items in the order mentioned. • No host profile is configured for the Telnet Client software package. Please see RF Terminal can not Connect to the Host on page 62. • The IP Address of the RF terminal is assigned to another RF terminal. Use these steps to determine if this is the problem. a.

If the RF terminal boots, do the following: 1. Power off the RF terminal.

A-59

Avalanche System Manual

2. Ping the RF terminal. See Figure A.5 for sample ping. 3. If the terminal can be pinged while the RF terminal is in the off position, another terminal or network node shares this IP Address. Contact your Network Administrator to get this problem fixed. b. If the RF terminal does not boot, perform the step outlined here. 1. If the RF terminal displays a message similar to that seen in Figure A.9 at boot time, the terminal is sharing an IP Address with another node on the network. Contact your Network Administrator. Novell TCP/IP Transpo rt v4.12 (930928) (C) Copyright 1992 No vell, Inc. All Right s Reserved. FATAL: IP address ass igned is already in u se by: 0020af27270d Strike a key when rea dy . . . Figure A.9 Duplicate IP Address Message

Terminal IP Address Assignment Problem IP Address not Allocated using Manager IP Pools Check to see if an IP Address Pool exists on the Avalanche Manager. A plus sign in front of the IP Address Pools icon indicates the presence of at least one IP Pool. See Figure A.10.

Figure A.10 IP Address Pools with Plus Sign

• Confirm the following three items: – The IP Pool is activated. – Only one IP Pool Address is activated. – IP Addresses are available for RF terminal (i.e., MAC Address) assignment.

Use the procedures shown here to verify the above items.

A-60

Troubleshooting

1. Right-click on the IP Address Pools within the Avalanche Manager Tree View. 2. Click on all defined IP Address Pools to determine which one displays a status of Active in the Summary View. If more than one IP Address Pool displays a status of Active, disable one of the IP Address Pools. If none of the IP Address Pools are Active, enable one of them. 3. Select the active IP Address Pool and press the Manage IP Address Pool button within the Summary View. Note whether there are available IP Addresses that can be assigned to mobile devices. See IP Configuration Profiles on page 44 for more information.

• The RF terminal is not in a cradle. The Avalanche Manager must assign the IP Address via the serial connection when using this option. • The RF terminal does not attach to the Avalanche Manager. See Terminal does not Attach to the Console on page A-64 and refer to the When Using Serial section.

IP Address is not Acquired via BOOTP • Review the Radio Configuration setup within the RF terminal to ensure that BOOTP is selected in the Terminal IP Address field. Refer to the appropriate Avalanche emulation client user guide for details. • Contact the Network Administrator to verify that either a BOOTP server or BOOTP Relay Agent reside on the local network segment when a message similar to the one shown in Figure A.11 appears. In addition, determine whether IP Addresses are available on the BOOTP server. Requesting my IP addr ess from a BOOTP serv er ... Requesting my IP addr ess from a RARP server ... FATAL: Unable to dete rmine this station's IP address. Strike a key when rea dy . . . Figure A.11 BOOTP Failure Message

IP Address is not Acquired via DHCP • Make sure the AVA3 update kit has been downloaded to the RF terminal. Refer to the appropriate Avalanche emulation client user guide for details on performing this task.

A-61

Avalanche System Manual

• Review the Radio Configuration setup within the RF terminal to ensure that dhcp is selected in the Terminal IP Address field. Refer to the appropriate Avalanche emulation client user guide for details. • Contact the Network Administrator to verify that a DHCP server resides on the local network segment when a message similar to the one shown in Figure A.12 appears. In addition, determine whether IP Addresses are available on the DHCP server. FATAL: Unable to determine this station’s IP address Strike a key when ready Figure A.12 IP Address not Assigned via DHCP

RF Terminal can not Connect to the Host Review this section to determine what may be inhibiting the RF terminal from communicating to the host. • When accessing the Host Profiles sub-menu from the Radio Configuration function menu, the screen shown in Figure A.13 is displayed. No application select an application from the App. Menu and return to Host Config. Press a key. . . Figure A.13 No Application Selected Screen

This means no software applications have been selected. For example, the Avalanche Enabler has been loaded and configured, but there are no Telnet Client software packages residing on the terminal. Download a Telnet Client software package to the RF terminal and add a host profile to resolve this issue. Review the appropriate Avalanche emulation client user guide for more information. • A message appears after an application is selected indicating that the RF terminal can not communicate with the host. This means there is no host profile configured with this application. See Figure A.14. To resolve this condition, do the following: 1. Access the AVALANCHE CLIENT CONFIGURATION (i.e., CONFIG MENU), FUNC, CTRL, R. Enter password, system. Type ’Y’ to confirm terminating an active session. 2. At the CONFIG MENU, select Host Profiles and press ENTER. 3. Press the ENTER key or use CTRL + A to add a new host profile.

A-62

Troubleshooting

4. Save the new host profile and exit the Radio Configuration function. Note: Within the CONFIG MENU, Function 1 provides help to maneuver on appropriate screens Remote IP Address information not configured! Update the TCP Configuration before attempting to connect again. Figure A.14 No Host Profile Created Message.

• The RF terminal uses the following standard telnet messages to inform the user of their connection progress and any error conditions that may occur. This section is intended to help diagnose any problems associated with error messages that are displayed when the terminal is attempting to communicate with the host. a.

"No host connection" 1. This is the standard "not connected" message. No errors are indicated.

b.

"Connection to xxxx Refused" 1. A connection to the host was made, but the host refused the connection--typically because it is out of resources, the telnet server software is down or it is not running on the port which was selected.

c.

"Connection to xxxx has Timed Out" 1. The host could not be located. Common reasons include: – – – – –

The host is down. The configured host address is incorrect. The Enabler’s Netmask and/or Router Address are incorrect. The physical network is down. The Spectrum 24 network is down (The Access Point is down or the Spectrum 24 Network ID is incorrectly configured). – Some hosts may cause a time out during connection if they are very busy, even though there are no configuration or hardware errors. d. "Negotiated emulation (xxxx) is not supported" 1. An emulation type has been negotiated with the host, but it is not a type that this client can support. Either the emulation type has been incorrectly configured, or the host does not support the type which was selected and has therefore negotiated down to another type. e.

"Connection to xxxx has been terminated", or "Connection closed by foreign host"

A-63

Avalanche System Manual

1. The host closed the session, either by the user’s request or for its own reasons (inactivity timeout, host is going down etc.) This message may also occur if communications fail while the session is up; either in the physical or the Spectrum 24 network. f.

"Invalid server address: xxxx", or "Invalid remote IP address" There are two possibilities: 1. If the host profile contains the "name" of the host, then this happened because the "name" could not be resolved into the IP address. Either the name is wrong, or the name server(s) are down. HINT: If there is a long delay before getting this message, then the name server is most likely down. If the message comes back within a few seconds, then the name is mostly likely wrong. 2. If the host profile contains the IP address of the host, then the address string contained an invalid character.

• This section is intended to help diagnose any problems associated with RF terminal messages that are displayed when the session is establishing a connection. a.

"Looking up host xxxx" 1. The client is checking DNS to resolve a host name.

b. "Trying to connect to xxxx" 1. The client is currently attempting to connect to the host. This message will remain until a socket-level connection is made. c.

"Connected to xxxx" 1. A socket-level connection has been made but the client is still waiting for the host to complete the telnet negotiations and send out the first screen. The screen may arrive quickly or if the host is slow it may take a moment. If the screen does not arrive at all, then the host is having problems internally.

Software Package Download Problems Review these items in the order they are presented.

Terminal does not Attach to the Console When Using RF • Verify the network setup on the console. Make sure the adapter is functioning properly and the IP configuration is correct. Consult your Windows Operating System Manual for more information. • Ping the RF terminal from the Avalanche Manager. If the ping is unsuccessful, proceed with the steps shown here. 1. Ensure that the following terminal network parameters are configured properly. These are: –

A-64

IP Address

Troubleshooting

–

Subnet Mask

–

IP Router Address

–

Network ID (i.e., ESS ID)

2. Check the network configuration of the Avalanche Manager.

• When the ping from the Avalanche Manager to the RF terminal is successful, check for duplicate IP Addresses on the RF terminal and the Manager. Follow these steps: a.

If the RF terminal boots, do the following: 1. Power off the RF terminal or Avalanche Manager depending on which IP Address is being verified. 2. Ping the RF terminal or Avalanche Manager from another network node. See Figure A.5 for sample ping. If the RF terminal or Manager can be pinged while the RF terminal or Manager is in the off position, another terminal or network node shares this IP Address. Contact your Network Administrator to get this problem fixed.

b. If the RF terminal does not boot, perform the step outlined here. 1. If the RF terminal displays a message similar to that seen in Figure A.9 at boot time, the terminal is sharing an IP Address with another node on the network. In this case, the TCP/IP stack did not load. Contact your Network Administrator.

• Verify the Avalanche configuration. The Avalanche menu item within the AVALANCHE CLIENT CONFIGURATION contains the IP configuration for the Avalanche Manager. The IP Address of the Manager is not required if the Manager and the mobile devices reside in the same network segment because the RF terminal performs a broadcast to find the Manager in this instance. When the Manager resides in one segment and the RF terminal resides in another, the IP Address of the Manager must be entered in the Version Control configuration form and the appropriate Router IP Address is needed. Refer to an appropriate Avalanche emulation client user guide for more information.

When Using Serial • The serial connection is usable when downloading a HEX file, however, the RF terminal can not communicate to the Avalanche Manager. In this case, the null modem cable being used is not a full null modem (i.e., null modem that meets the specifications the cradle or terminal demands). The null modem cable used must not block or loop back DSR since this is used by the Enabler to detect the presence of the Manager. • The serial connection does not allow HEX file downloads. The cable may be bad or the incorrect type of cable for this type of communication. Refer to Problems Downloading a HEX File on page A-49 for more information.

A-65

Avalanche System Manual

Terminal Attaches but the Console doesn’t try to Download Anything • Click on the software package and confirm that it is enabled. The upper right portion of the Summary View on the Avalanche Manager displays the status of the software package. For a software package to download to the RF terminal, the status must display Active. Refer to Software Packages on page 36 for more information. • Check to see if the software package was already downloaded to the RF terminal. To do this, use this procedure. 1. Click on the RF terminal in the List View to highlight it. 2. Click on the More Button in the Summary View. 3. Review the Client Communications Details dialog box to see the status of software packages assigned to the RF terminal. Refer to Software Packages on page 42 for more information.

• The target selection of the software collection or the software package may be set to exclude this terminal from the download of the software package. Click on the software collection and software package separately to view the current target selection. See Software Packages on page 37 for information regarding target selection.

Terminal Attaches and a Download Begins but Fails Fails using RF Connection • Poor network conditions may be causing the symptom to occur. See your Network Administrator. To confirm this condition, isolate the RF terminal, an Access Point, and the Manager from the rest of the network and restart the RF download.

Fails using Serial Connection • Some older cradles tend to have difficulty with downloads. Make sure the cradle and null modem cable meet the specifications the RF terminal demands. See When Using Serial under Terminal does not Attach to the Console on page A-64 for more details.

RF Terminal Flash Drive is Full • The Avalanche Enabler will display a message when the flash drive is full. See Figure A.15. Follow these steps to recover from this situation. Looking up console. Contacting console. Updating software. Please wait.... UPDATE INCOMPLETE: Disk is full. Press a key... Figure A.15 Flash Drive Full Message

A-66

Troubleshooting

– Use these steps for Series 3000 mobile devices: 1. Coldboot the terminal so that the App. Menu as seen in Figure A.16 will appear. When no application software packages are loaded on the RF terminal, Figure A.17 is displayed. Skip the next step if Figure A.18 is presented. App. Menu 5250/3270 Telnet VT/HP Telnet

Item 1 of 3 Figure A.16 App. Menu

No application selected Options Configure IP

Item

1 of 1

Figure A.17 No Application Loaded

2. Press the ESC key (i.e., CLEAR on most mobile devices) from the screen shown in Figure A.16. The following figure is presented. No application selected Options Configure IP

Item

1 of 1

Figure A.18 No Application Selected

3. Use FUNC, CTRL, F to clear the flash drive. Type flash at the password prompt to confirm the operation. – Use these steps for Series 4040 and 5040 mobile devices: 1. Boot the RF terminal. 2. Press ESC at the access menu to use other applications installed on the RF terminal. See Figure A.19. 3. When no application software packages are loaded on the RF terminal, Figure A.17 is displayed. Skip the next step if Figure A.17 is presented. 4. Press the ESC key from the screen shown in Figure A.17 and Figure A.18 is presented. 5. Use ALT, F to delete the apps directory and the temp directory on the 4040 and 5040 mobile devices.

A-67

Avalanche System Manual

Start Application (ENTER) Exit to Main Menu (ESC)

Figure A.19 VRC 4040/5040 App Access Menu

Contact Us For questions or problems with Avalanche, contact WaveLink Corporation at [email protected] or call 801-255-1777. In addition, see our web site at: http://www.roisys.com/contact/contact.htm.

A-68

Appendix B

RF Firmware & Radio Updates RF Firmware and Driver Packages (1 or 2 Mb) RF Firmware packages are currently available for Series 3000, Series 4000 and Series 7000 mobile devices. These packages provide the means to change a terminal’s protocol from Pre802.11 firmware to 802.11 firmware and vice versa. The names of the firmware packages are: • RF3.exe for Series 3000 mobile devices • RF4.exe for Series 4000 mobile devices • RF7.exe for Series 7000 mobile devices. Do the following to change the firmware within the RF terminal:

WARNING If the firmware update procedures are not followed carefully, terminal may become inoperable. mobile devices should not be powered off during the firmware upgrade.

1. Install the packages to the appropriate software collection and profile on the Avalanche Manager. Click on the firmware package icon and the Summary View indicates that it is an Auto software package type. This means the package will run immediately after it is successfully downloaded on the RF terminal. For more information regarding software packages, see Software Packages on page 36. 2. Right-click the package and select whether this will be a Pre-802.11 firmware update or an 802.11 firmware update. 3. The target selection of the firmware update package is set at default to Series=3 for 3000 series mobile devices, (ModelName=4040) or (ModelName=5040) for 4040 and 5040 mobile devices and (ModelName=7540) or (ModelName=7240) for 7540 and 7240 mobile devices. These target selections can not be modified so as to assure that these packages will not download to the incorrect mobile devices. Modify the target selection of the software collection to further restrict which mobile devices will receive this firmware update package. 4. Right-click the firmware package to enable it.

B-69

Avalanche System Manual

5. Make sure that other mobile devices residing in the same software collection are not booted while updating mobile devices needing firmware upgrades. 6. If the RF terminal is currently operating at a given site, use the RF to download the firmware upgrade package. The Access Points will require firmware updates for the mobile devices to communicate. If the RF terminal is not currently operating and doesn’t match the firmware at the site, employ the cradle to download the firmware upgrade. 7. Perform a cold boot or warm boot on the RF terminal to receive the firmware package from the Avalanche Manager. Once the firmware update package is downloaded successfully to the RF terminal, it is executed automatically on the RF terminal. 8. After the firmware update has been performed, access the AVALANCHE CLIENT CONFIGURATION (i.e., CONFIG MENU). 9. Modify the Network ID to correspond to the appropriate AP network. In the 802.11 environment, the Network ID is also referred to as the ESS ID. The Network ID in the Pre802.11 environment supports three characters whereas the ESS ID (i.e., Network ID) allows 32 characters in the 802.11 environment. Note that the Network ID field scrolls when the terminal is setup for 802.11 so that Network IDs greater than 3 characters may be entered.

RF Firmware and Driver Packages (11 Mb) Some mobile devices use the 802.11B protocol. This protocol supports 11Mb transfer rates. As hardware improves, new firmware is implemented into mobile devices causing, occasionally, incompatibilities between the firmware and radio drivers. As this occurs, WaveLink creates new packages to update the software to match the radio drivers with the firmware. For example, the PDT7546 terminal contained radio driver 1.15-02 and firmware version 1.0003. The radio driver 1.15-02 is compatible with the firmware version 1.00-03. However, when Symbol Technologies installed the newer firmware version 2.20-01 into the 11Mb 7540 series mobile devices, an incompatibility issue was created. WaveLink Corporation created the RF7-11_v20 software package which upgrades the radio driver to version 2.23-00 which is compatible with the newer firmware. To assess which firmware and radio driver is loaded on the terminal, access the AVALANCHE CLIENT CONFIGURATION (i.e., CONFIG MENU),FUNC, CTRL, R. Enter password, system. Type ’Y’ to confirm terminating an active session. Select Radio Parameters. Select Terminal Info. Note: If, after implementing the new firmware, the terminal is flash formatted, this package may need to be reapplied to assure that compatible radio drivers and firmware are loaded.

Contact WaveLink-Utah at 801-255-1777 regarding the latest information on which packages are available. Currently, the following packages are available.

B-70

– RF3-11_v20.exe

for 3000 Series mobile devices

– RF7-11_v20.exe

for 7000 Series mobile devices

Appendix C

RF Diagnostics Symbol RF Diagnostic Programs Avalanche software packages for the Symbol RF diagnostic tools are available. The Diag24 software package is called Diag24_3.exe for the Series 3000 mobile devices and Diag24pc.exe for the Symbol radio PC card. These software packages are installed on the Avalanche Manager in the same manner as the Telnet Client software packages. In addition, these software packages download to the RF terminal through enabling and booting the mobile devices. Contact your Symbol representative for questions regarding Diag24 usage. Coldboot on a Series 3000 terminal to access the Diag24 package. On Series 4000 and Series 5000 mobile devices, use the Diag24pc.exe software package and use VRC 4040/5040 App Access Menu to access Diag24 at boot time. App. Menu 5250/3270 Telnet VT/HP Telnet Diag24 for 3000

Item 1 of 3 Figure A.20 App. Menu with Diag24

C-71

Avalanche System Manual

C-72

SPT1740 Client User Guide

Numerics 3000 Series Enablers Location of ....................................... 15 3000 Series Mobile Units ......................14 3270 .................................................... ii, 7 4000 Series Mobile Devices ..................19 5000 Series Mobile Devices ..................19 5250 .................................................... ii, 7 7000 Series Mobile Devices ..................20

A About Manager ......................................34 Acquiring Avalanche Demo Version .................................... 9 Licensed Version ............................... 9 Active .....................................................28 Activity ..................................................28 AdvancedAccess Menu ..........................30 Application (Software Package) ............36 Auto (Software Package) .......................36 Automatic Detecting Serial Ports ..........13 Avalanche Implementation ................................ 11 Avalanche Enabler ...................................7 Configure ......................................... 25 Setup ................................................ 12 Avalanche Management Console.see Avalanche Manager Avalanche Manager ...........................2, 27 Install ............................................... 11

B Benefits ....................................................8

C Cleanup of Unused Packages .................32 Client IP Address Assignment ...............44 Client Management ................................35 Tree View ........................................ 35 Client Update Controls ..........................30 Cold Boot 3000 Series Terminals ............... 18, 24 Command Mode 3000 Series Terminals ..................... 16

7000 Series Terminals ..................... 20 Communication Port Setup ................................................ 13 Communications Port ............................15 Communications Port Status Box ..........15 Concepts ...................................................4 Configurable IP Parameters ...................47 Configure Avalanche Enabler ................25 Console .see Avalanche Manager Criteria String ........................................37 Currently Updating ................................33

D Delete Port .............................................34 Detailed Client Controls ........................42 Details ....................................................28 Digiboard .................................................7 Download Hex File ................................34 Download Status Codes .........................51 Downloading Status Codes ....................51

E Emulation Client ......................................1 Enabler.See Avalanche Enabler

F Failed Update Count ..............................33 File Menu ...............................................28 Firmware Updates ..................................69

H Help Menu .............................................33 HEX File to Download ..........................15 HexFile Menu ........................................30 HP ............................................................7

I Install Avalanche Manager ....................11 Install Software Packages ......................25 IP Address ..............................................28 IP Address Assignment ..........................44 IP Address Pool Advantages ..................46 IP Address Pools ....................................45 IP Configuration Profiles .......................44 IP Parameters .........................................47

Index - 1

SPT1740 Client User Guide

L

S

List View ................................................27 Activity ............................................ 28 Details .............................................. 28 IP Address ........................................ 28 MAC Address .................................. 28 Removing Terminals ........................ 43 Terminal Selection ........................... 40 Type ................................................. 28 Updated? .......................................... 28 Loading Avalanche Enabler 3000 Series Terminals ..................... 14 4000 and 5000 Series Terminals ...... 19 7000 Series Terminals ..................... 20 LWP Telnet Clients .................................6

Schedule for Update ...............................33 Schedule for Updates .............................33 Scheduled Client Updates ......................31 Selection Criteria ...................................37 Selection Variables .......................... 38 Syntactical Symbols ......................... 38 Selection Criteria Usage ........................40 Selection Variables ................................38 Columns ........................................... 38 IP ...................................................... 38 KeyboardCode ................................. 38 KeyboardName ................................ 38 MAC ................................................ 38 ModelCode ....................................... 38 ModelName ..................................... 38 Rows ................................................ 38 Series ................................................ 38 Serial Port Automatic Detecting ........................ 13 Manually Adding ............................. 13 Removing ......................................... 13 Setup ................................................ 13 Serial Port Settings .................................13 Server Management ...............................34 Tree View ........................................ 34 Show Client Update Monitor .................32 Simultaneos HEX File Downloads ........18 Site Profile Copy ................................................. 30 Delete ............................................... 30 New .................................................. 29 Open ................................................. 29 Rename ............................................ 29 Site Profiles ..........................................3, 4 Software Collections ......................3, 5, 35 Software Packages ...........................1, 3, 5 Application ....................................... 36 Auto ................................................. 36 Install ............................................... 25 Support ............................................. 36 Status Codes ...........................................51 Downloading .................................... 51

M MAC Address ........................................28 Manager.see Avalanche Manager Manually Adding Serial Port .................13 Menus .....................................................28 Modify Communication Port .................13

N NC ............................................................7 Network Bandwidth Management .........31 Notification Sound .................................15

O On Hold ..................................................28

P Port Settings ...............................13, 15, 34 Program Loader Status Code ...................................... 51 Terminal Communication ................ 16

R Radio Terminals Supported .....................7 Removing Serial Port .............................13 Removing Terminals from List View ....43 RF Diagnostics .......................................71 RS232 .......................................................7

Index - 2

SPT1740 Client User Guide

Summary View ......................................28 Support (Software Package) ..................36 Supported Terminals ................................7 Syntactical Symbols ...............................38 And (&) ............................................ 38 Eq (=,==) .......................................... 38 Not (!) .............................................. 38 Or ( | ) ............................................... 38 System Requirements ..............................7

T Target Selection .................................6, 28 Terminal Communication Program Loader ............................... 16 Terminal Selection with List View ........40 Terminal Type ........................................28 TN ............................................................7 Tools ......................................................30 Total # of Clients ...................................33 Tree View ..............................................27 Troubleshooting .....................................49 Enabler Configuration Problems ..... 53 Flash Drive Full ............................... 66 IP Address Assignment .................... 60 Problems Synchronizing with Console 51 RF Terminal no Communicating ..... 55 Software Package Download ........... 64

U Updated So Far ......................................33 Updated? ................................................28

V VT ............................................................7

W Why Avalanche? ......................................8 Winhex ...................................................13

Index - 3

SPT1740 Client User Guide

Index - 4