Wavelink Avalanche Mobility Center Web Console User Guide Version 5.
ii Copyright © 2010 by Wavelink Corporation All rights reserved. Wavelink Corporation 6985 South Union Park Avenue, Suite 335 Midvale, Utah 84047 Telephone: (801) 316‐9000 Fax: (801) 316‐9099 Email: customerservice@wavelink.com Website: http:\\www.wavelink.com Email: sales@wavelink.com 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.
Table of Contents 1 Table of Contents Chapter 1: Introduction 7 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Managing Networks with Avalanche . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Components of Avalanche . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Location Management: Server Locations and Regions . . . . . . . . . . . . 10 Mobile Manager . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 2 Viewing Region Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Server Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining Server Placement . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 3 Creating Device Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applying Device Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying the Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pinging the Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rebooting the Device. . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 4 Deleting Mobile Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Custom Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Device Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Custom Device Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 5 Editing Alert Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing and Exporting E‐mail Addresses . . . . . . . . . . . . . . . . . . . . . Importing E‐mail Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting E‐mail Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Alert Profiles to a Region . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 6 Appendix D: Supported Firmware 181 Appendix E: Wavelink Contact Information 190 Glossary 192 Index 199
Chapter 1: Introduction 7 Chapter 1: Introduction This document is a guide to the functions and components of Wavelink Avalanche. This document presents: • An introduction to the Avalanche Web Console and conceptual information about Avalanche. • Detailed information on the components of Avalanche. • Tasks for creating an effective, secure wireless network. NOTE The instructions contained in this guide pertain to the Avalanche Web Console.
Chapter 1: Introduction 8 This document uses the following typographical conventions: Courier New Any time you interact with the physical keyboard or type information into a text box that information appears in the Courier New text style. This text style is also used for any file names or file paths listed in the text. Examples: The default location is C:\Program Files\Adobe\FrameMaker7.1. Press CTRL+ALT+DELETE.
Chapter 1: Introduction 9 • Location Management: Server Locations and Regions • Mobile Manager Components of Avalanche Avalanche is an integrated system of several components, which together allow you to manage your wireless network quickly and efficiently. The primary components of Avalanche include: • Avalanche Java Console. The Avalanche Java Console is your interface with wireless network components.
Chapter 1: Introduction 10 • Enablers. Mobile devices require additional software, called an Enabler, in order to be managed by Avalanche. An Enabler relays information between the mobile device and the Mobile Device Server. With the Enabler installed, the mobile device can receive configuration instructions that you create in the Avalanche Console. NOTE Some features of the Avalanche Console are only available with recent versions of the Enabler.
Chapter 1: Introduction 11 Manager Administrator. The Administrator is a tool designed to manage infrastructure devices at a specific server location. For more information about Mobile Manager, refer to the Mobile Manager User’s Guide or contact Wavelink Customer Service. Getting Started To better manage your Avalanche installation and configuration and to ensure optimal performance, Wavelink recommends you perform the following steps in order: 1 Install Avalanche.
Chapter 1: Introduction 12 server location. For more information, refer to Building Server Deployment Packages on page 42. 8 Perform Updates. To deploy settings to the selected regions and server locations, perform an update through the Task Scheduler. For more information refer to Performing a Server Synchronization on page 155. Once you assign and deploy a profile, the Server and/or devices retain their configuration values until you change the profile or assign a new profile with a higher priority.
Chapter 2: Avalanche Web Console 13 Chapter 2: Avalanche Web Console You interact with your wireless network primarily using the Avalanche Console. The Avalanche Console allows you to control global characteristics of your wireless network. These characteristics include creating profiles, assigning IP addresses, and monitoring network performance. The Avalanche Console is traditionally accessed from a computer where the Console has been installed. This installed Console is the Java Console.
Chapter 2: Avalanche Web Console 14 • The web components installed at the same location as the enterprise server. If you performed a custom installation, you should have selected the Web Components option to be installed. If you did not perform a custom installation, the web components were installed automatically. NOTE If you choose to use a certificate to create a secure connection, see Appendix A: SSL Certificates on page 165 for information on launching the Web Console.
Chapter 2: Avalanche Web Console 15 1 The alerts overview shows the number of critical, error, and warning alerts current in the user’s home region. 2 The management tabs provide access to maps, inventories, alerts, and other properties of your enterprise. The Tools menu provides you with access to the Reports tool, scheduled tasks, Wavelink Remote Control, system support, information, and settings. 3 The search box allows you to search content in the Web Console.
Chapter 2: Avalanche Web Console 16 NOTE If you want to further filter the information displayed by region or location, use the context links to navigate. There are five management tabs and the Tools menu: • Maps • Locations • Inventory • Profiles • Alerts • Tools Menu Maps The Maps tab provides a map displaying your regions, server locations, and sites. You can also view the location of alerts and device GPS position or history.
Chapter 2: Avalanche Web Console 17 locations as necessary. The Applied Profiles panel displays the profiles that are currently applied to the selected region and the type, status, and priority of those profiles. The Available Profiles panel displays all profiles that are available to be applied to the selected region. NOTE For information about specific profiles, see the Table of Contents. For information on applying a profile to a region or location, see Assigning Profiles on page 31.
Chapter 2: Avalanche Web Console 18 Region Navigation You can navigate to a specific region or location in your network and then display only the information applicable to that region by using the context links. By selecting a region or location and then using the context links, the Console will display only information pertinent to the selected location. To navigate to a region or location to view: • Click the arrow to the right of the home location.
Chapter 2: Avalanche Web Console 19 Other tasks that can be performed in most panels include: • Paging through Panels • Sorting by Column Paging through Panels Some panels include large lists of information. By default, Avalanche generally displays the first ten items and then allows you to page through the rest of the list. You can change the number of items displayed per page, however, by clicking the preset number at the top of the panel. The options are 10, 25, 50, 100, or All.
Chapter 2: Avalanche Web Console 20 Viewing and Configuring System Settings From the Web Console, you can view system information and perform tasks related to managing the enterprise server.
Chapter 2: Avalanche Web Console 21 A user can select criteria he wishes the server to filter log‐retrieval with, allowing the user to retrieve the entire log or just the entries that pertain to the specified criteria. To view the audit log: 1 Click Tools > Support. The System Information page appears. 2 Click Audit Log. The Audit Log page appears. 3 Select the filter(s) you want to use: • To filter events by date, enable Date Range and use the calendar buttons to select the beginning and end dates.
Chapter 2: Avalanche Web Console 22 2 If you don’t want profiles to be applied at My Enterprise, enable the Do not allow profiles to be applied at root level option. 3 If you want to configure the length of time before an inactive Web Console user is logged off, type the number of minutes in the text box under Session Timeout. 4 If you want to configure how many days an alert is displayed or how many alerts are stored in the database, type the appropriate numbers in the text boxes under Alert Settings.
Chapter 2: Avalanche Web Console 23 Restricting Server-to-Server Communication From the Web Console, you can suspend or throttle communication between the enterprise server and distributed servers. When communication is suspended, the distributed servers are not allowed to contact the enterprise server until the connection is resumed. When communication is throttled, the distributed servers will no longer send device statistics updates to the enterprise server.
Chapter 3: Managing User Accounts 24 Chapter 3: Managing User Accounts A user account is required to log into the Avalanche Console. User accounts allow you to define who can access components and perform tasks. Users will not be able to access the Console without an account. There are two types of accounts: Administrator and Normal. An Administrator account can access and modify all the configurations in Avalanche associated with his home region.
Chapter 3: Managing User Accounts 25 • Profile Permissions. These permissions allow the user complete global access to the specified profile. Administrators can grant read or read/write access for each type of profile. Read/write allows the user to manage all aspects of the profile, from configuration to application. Read‐only allows the user to view the profile, but does not allow any editing. For details on each permission allowed, see Assigning User Permissions on page 26.
Chapter 3: Managing User Accounts 26 These user groups are set with a series of default permissions. You can modify the groups to suit your needs. A user group must be created from the Java Console. See the Java Console help file for instructions on creating a new user group. Assigning User Permissions If you have an Administrator account, you have unlimited permissions, and can assign and change permissions for Normal user accounts. Permissions must be configured from the Java Console.
Chapter 3: Managing User Accounts 27 The user is added to the list of authorized users for that region or location. Assigning Authorized Users to Profiles You can assign administrative privileges for a specified profile to a user that has Normal user rights and is not assigned permissions to profiles. To add an authorized user you must have at least one user configured with Normal permissions. Users that have permission for the profile will not appear in the list of available users.
Chapter 4: Location Management 28 Chapter 4: Location Management One of the key aspects of Avalanche is location management. Avalanche divides locations into two categories: server locations and regions. A server location is the basic component of the Avalanche Console. Each server location contains at least one server that communicates with specific wireless components.
Chapter 4: Location Management 29 optimal performance, Wavelink recommends you perform the following steps in order: 1 Install Avalanche. For more information, see the Java Console help file. 2 Activate Mobile Device Server and Infrastructure Server licenses for Avalanche. You should activate the number of licenses based on the number of devices you want to manage. For more information, see the Java Console help file. 3 Create regions.
Chapter 4: Location Management 30 region, the Avalanche Console applies the configurations to every server location within that region. Avalanche allows you to create nested regions, enhancing your region and network control. A nested region is a region that is placed within another region and appears a step below that region in the Enterprise List. When a profile is applied to a region, it is also applied to, or “inherited” by, all the associated sub‐regions and server locations.
Chapter 4: Location Management 31 3 In the Sub‐locations panel, click New. 4 The New Subordinate Location dialog box appears. Click Region. 5 The Location: New Region page appears. The region on the page contains fields for entering information about your new region. 6 Enter the name of your region, the latitude and longitude, and any notes in the provided text boxes and click Save. The new region is created.
Chapter 4: Location Management 32 the assigned region. You can apply multiple alert profiles to one region at a time. • Network Profiles. You can assign as many network profiles to a region as you desire. The profiles are applied to the mobile devices based on selection criteria for the profile and the order in which the profiles are listed in the Avalanche Console. • Software Profiles.
Chapter 4: Location Management 33 Deleting Regions You can delete unused regions from the Web Console at any time. Any server locations associated with a region automatically return to the Deleted dServer Locations folder when you delete that region. NOTE Deleting a region is permanent. There is no way to retrieve a deleted region. You must recreate the region. To delete a region: 1 Navigate to the region containing the region you want to delete. 2 Click the Profiles context link.
Chapter 4: Location Management 34 to communicate past a given subnet. This type of configuration takes place at the server location level, using the Mobile Manager Administrator. See the Mobile Manager User’s Guide for more information. To ensure that all wireless devices are managed at a particular server location, you can do one of the following: • Configure your network hardware to allow infrastructure and mobile device broadcasts to reach the Servers.
Chapter 4: Location Management 35 Centralized Server Method In centralized Server installations, a single Server is responsible for managing all of the infrastructure devices on the network. Centralized Server installations are typically found in environments where specific locations within a network might be unable to support their own Servers. An example of this environment is a collection of retail stores.
Chapter 4: Location Management 36 • You must know what switches and routers reside between the Server and infrastructure devices. (This is particularly helpful should any troubleshooting be necessary.) • You must have a general understanding of the overall performance of the wireless network, to ensure that specific time‐based features (such as WEP key rotation) are configured correctly. Distributed Server Method In distributed Server installations, a Server resides on each network subnet.
Chapter 4: Location Management 37 Figure 4-2. A Distributed Installation of Avalanche (Simplified) For information about how to deploy Infrastructure Servers, refer to the Java Console help. If the location already contains one or more Servers, you do not need to create a new server location. However, you must ensure that the Server installed at the server location is compatible with the Avalanche Console.
Chapter 4: Location Management 38 3 In the Sub‐locations panel, click New. 4 Select dServer from the dialog box. The New Server Location page appears. 5 Type the name of the new server in the provided text box. 6 In the City, State, Country, Latitude and Longitude text boxes, enter the physical location of your server. 7 Select the time zone from the Time zone drop‐down list. 8 Type the IP address of the system which contains (or will contain) a Server in the IP Address text box.
Chapter 4: Location Management 39 Server locations restored from the Deleted dServer Locations folder to the Unassigned dServer Locations folder retain their last configuration. Moving Server Locations to Regions A server location must belong to a region before you can manage its settings. You may need to move an existing server location if the location was never assigned to a region, if a region was deleted, or if you want to restructure your network hierarchy.
Chapter 4: Location Management 40 3 Click Edit. 4 Edit the information as needed. 5 Save your changes. Assigning Profiles to Server Locations You can assign any configured profile to a server location from the Profiles page. You use the same method to assign profiles to a server as you do to assign profiles to regions. For detailed steps of assigning a profile, refer to Assigning Profiles on page 31. Managing Sites Sites are groups of mobile devices that share the same Mobile Device Server.
Chapter 4: Location Management 41 5 Click Launch Wizard to use the Selection Criteria Builder to configure selection criteria for the site. For more information on using selection criteria, see Chapter 14: Using Selection Criteria on page 139. 6 Enter any notes for the site in the provided Notes text box. 7 When you are finished, click Save. A site appears under the server location. The mobile devices meeting the specified selection criteria will be assigned to the site.
Chapter 4: Location Management 42 Building Server Deployment Packages To build server deployment packages and deploy them to your server locations, you must use the Java Console. See the Java Console help for details. Server Auto-Discovery If you have installed Avalanche and deployed a Mobile Device Server, an Infrastructure Server, or both, the Servers are continually attempting to contact Avalanche.
Chapter 4: Location Management 43 Configuring Infrastructure Servers at Server Locations Although you manage much of your wireless network with the Avalanche Console, certain server locations might require additional infrastructure configuration or management. The Infrastructure Site Console allows you to fine‐tune your wireless network by configuring your wireless network components and mobile device software at the server location level.
Chapter 5: Managing Network Profiles 45 Chapter 5: Managing Network Profiles A network profile is a group of configurations that you can apply to your wireless devices. Once the wireless devices are configured with the network values configured in the network profile, you can manage the devices through the Avalanche Console. If your wireless devices do not have the appropriate network values, you will not be able to manage them.
Chapter 5: Managing Network Profiles 46 To create a network profile from the Web Console: 1 From the Profiles tab, click New Profile. The New Profile dialog box appears. 2 Select Network Profile. The New Profile Details page appears. 3 Type a name for the profile in the Name text box. 4 If desired, enable the profile or set the profile to override any manual settings on the mobile device.
Chapter 5: Managing Network Profiles 47 The available addresses and the mask will appear in the table to the left. This list will display all entered addresses. NOTE If you want to delete addresses from the address pool, enable the checkbox to the left of the address and click Delete. 11 Click Save to return to the New Profile Details page. 12 If desired, type any Notes in the text box. 13 If you want the profile to manage WLAN IP, WLAN, or WWAN settings, enable the appropriate check box.
Chapter 5: Managing Network Profiles 48 • Configuring WLAN IP Settings • Configuring WLAN Settings • Configuring WWAN Settings • Scheduled Profile Changes Configuring WLAN IP Settings From a network profile, you can configure WLAN IP settings for your devices. These settings will be deployed with the profile and applied on the device.The options include: Server Address This option provides mobile devices with the server address. You can provide the address, DNS name, or choose to Use server address.
Chapter 5: Managing Network Profiles 49 Secondary Provides mobile devices with the IP address for a secondary DNS (used if the primary DNS is unavailable). Tertiary Provides mobile devices with the IP address for a tertiary DNS (used if the primary and secondary DNS are unavailable). Manage IP Assignment This option allows you to manage the IP addresses assigned to your mobile devices. You can choose to use either a DHCP server or IP pool assignment.
Chapter 5: Managing Network Profiles 50 Configuring WLAN Settings From a network profile, you can configure WLAN settings for your devices. These settings will be deployed with the profile and applied on the device. The options include: SSID This option provides wireless devices with the SSID. The SSID is a service set identifier that only allows communication between devices sharing the same SSID. Encryption This option allows you to enable encryption between your devices and the server.
Chapter 5: Managing Network Profiles 51 WEP Key Rotation. WEP key rotation employs four keys which are automatically rotated at specified intervals. Each time the keys are rotated, one key is replaced by a new, randomly generated key. The keys are also staggered, meaning that the key sent by an infrastructure device is different than the one sent by a mobile device. Because both infrastructure and mobile devices know which keys are authorized, they can communicate securely without using a shared key.
Chapter 5: Managing Network Profiles Custom Properties 52 This option allows you to add custom properties to the devices that receive this network profile. By clicking defined, you can add, edit, and delete properties and their values. Authentication Settings The authentication type available depends on the encryption you are using and what is supported by your Enabler and hardware. Authentication options include: EAP. Extensible Authentication Protocol.
Chapter 5: Managing Network Profiles 53 • LEAP. (Lightweight Extensible Authentication Protocol) LEAP requires both client and server to authenticate and then creates a dynamic WEP key. Pre‐Shared Key (PSK). PSK does not require an authentication server. A preset authentication key (either a 8‐63 character pass phrase or a 64 character hex key) is shared to the devices on your network and allows them to communicate with each other. TTLS/MS‐CHAPv2.
Chapter 5: Managing Network Profiles 54 • If you are using PEAP or TTLS authentication, you can provide a path to the certificate. • If you are using EAP_FAST, you can provide a path to a PAC (Protected Access Credential). • If you are using an EAP method or LEAP, you can configure whether the User Credentials are Prompt (user is prompted when credentials are required) or Fixed (credentials are automatically sent when required).
Chapter 5: Managing Network Profiles Credentials 55 Sets the method for sending EAP credentials. Prompt. When the credentials are needed, the user is prompted with a dialog box to enter the information. Fixed. When the credentials are needed, the information is automatically sent without prompting the user. Custom Properties This option allows you to add custom properties to the devices that receive this network profile. By clicking Edit/View, you can add, edit, and delete properties and their values.
Chapter 5: Managing Network Profiles 56 4 Configure the WWAN settings as desired. 5 Click Save to save your changes. Scheduled Profile Changes Epochs allow you to change the settings for a network profile and apply those changes at a specific time. When you configure WLAN IP, WLAN, and WWAN settings, you can select which epoch those settings are effective for. 1 From the Available Profiles panel on the Profiles tab, click on the network profile you want to edit. The Network Profile Details page appears.
Chapter 6: Managing Scan to Configure Profiles 57 Chapter 6: Managing Scan to Configure Profiles Avalanche allows you to create Scan to Config Profiles (barcode profiles) that are configured with network settings. You can then print the profiles as barcodes and a mobile device with an Enabler 3.5 (or later versions) can scan these barcodes. The information from the scanned barcodes is used to configure the network settings on the device.
Chapter 6: Managing Scan to Configure Profiles 58 Adding Scan to Config Profiles When you create a Scan to Config Profile, you can configure the maximum barcode length and network settings such as the IP address, subnet mask, and gateway. You also have the option of using the network settings contained in a Network Profile. When you create a Scan to Config Profile, you can also configure a passcode for the profile. The passcode is used to encrypt the barcode data.
Chapter 6: Managing Scan to Configure Profiles 59 7 If you want to set a static IP address for the device, enable Assign static IP address and type the IP Address, Subnet Mask and Gateway in the appropriate boxes. 8 If desired, type any notes in the Notes text box. 9 Click Save. The profile is created and appears in the Profiles tab. Editing Registry Keys for Scan to Config Profiles You can add registry keys and values to a Scan to Config Profile.
Chapter 6: Managing Scan to Configure Profiles 60 5 Type the name of the new key in the Key text box. 6 Type the value of the key in the Name text box. 7 Enter the data for the value in the Data text box. 8 Select the Type of the value from the drop‐down list. 9 Select Create key as the Action. 10 Click Add to add the registry key and value to the list. 11 When you are done, click Save. The key and value are saved to the profile.
Chapter 6: Managing Scan to Configure Profiles 61 8 Select the Type of the value from the drop‐down list. 9 If you are editing the key or key value, select Create key as the Action. If you are deleting the key or key value, select Delete key. 10 Click Save. The task is added to the list in the Registry keys region. The value will be edited when the barcodes are scanned by the mobile device.
Chapter 6: Managing Scan to Configure Profiles 62 The New Property dialog box appears. 4 Type the category to which you want to add the property in the Optional group text box. 5 Type the Property Name and Property Value in the text boxes. 6 Select Create property as the Action. 7 Click Save. The task is added to the list in the Device Properties region. The property will be added when the barcodes are scanned by the mobile device.
Chapter 6: Managing Scan to Configure Profiles 63 The task is added to the list in the Device Properties region. The property will be added when the barcodes are scanned by the mobile device. Adding Scan to Config Profiles to Regions Once you have configured your Scan to Config Profile, you can apply that profile to any region in the Console. When you apply a profile to a region, the users who have permissions for that region can make changes as necessary.
Chapter 6: Managing Scan to Configure Profiles 64 Scanning Barcodes To scan and apply a Scan to Config Profile, you must open the Scan Configuration dialog box from the Enabler on the mobile device. Use the mobile device to scan the barcodes in any order. This sends the configurations to the Enabler and updates the network profile. You must have an Enabler 3.5 or later version to use the scan to configure functionality. Contact Wavelink Customer Service for information about obtaining an Enabler 3.5.
Chapter 7: Managing Infrastructure Devices 65 Chapter 7: Managing Infrastructure Devices Infrastructure devices can be managed through the Inventory tab on the Web Console. The Infrastructure Devices panel in the Inventory tab shows a set or subset of infrastructure devices based on the currently selected region or location. If you use the Inventory tab, it shows all infrastructure devices.
Chapter 7: Managing Infrastructure Devices 66 • Querying the Device • Pinging the Device • Resetting Access Points • Changing Access Point Firmware • Deleting Devices • Viewing Infrastructure Device Details NOTE All tasks are available for both switches and access points. Some tasks may not be available for access ports. Using Device Filters You can filter which devices are listed in the Infrastructure Devices panel with device filters.
Chapter 7: Managing Infrastructure Devices 67 To create a filter: 1 In the Infrastructure Devices panel, click Edit Filters. The Modify Filters page appears. 2 Enter a name for the filter in the Filter Name text box. 3 Click the Launch wizard button. The Selection Criteria Builder dialog box appears, allowing you to create a filter based on a variety of device characteristics. See Building Selection Criteria on page 140 for more information on using the Selection Criteria Builder.
Chapter 7: Managing Infrastructure Devices 68 Querying the Device When a query occurs, an Infrastructure Server updates the statistical data and configuration settings of an infrastructure device. These queries occur at specific intervals—either an interval that you established for the Server, or the default interval of once every 10 minutes. Occasionally you might want to force a Server to query a device—for example, if you want a specific configuration change to become effective immediately.
Chapter 7: Managing Infrastructure Devices 69 Rebooting the Device You can reboot an infrastructure device from the Web Console’s Inventory tab. NOTE You cannot reset Symbol access points to factory defaults if a router, or any network equipment that blocks layer 2 protocols, exists between the Server and the access points. To reboot the device: 1 Enable the check box to the left of the desired device in the Infrastructure Devices panel. 2 Click Reboot.
Chapter 7: Managing Infrastructure Devices 70 To reset an access point to its factory defaults: 1 In the Infrastructure Devices panel, click the name of the device you want to reset. The Device page appears. 2 In the Tools panel, click Reset Factory. A dialog box appears, asking you to confirm that you want to reset the access point. 3 Click Yes. The Server resets the access point. While the device resets, its status appears as Resetting.
Chapter 7: Managing Infrastructure Devices 71 NOTE There are some devices, when connected to the network, that may be immediately rediscovered. Viewing Infrastructure Device Details You can view details about the infrastructure devices managed by Avalanche from the Web Console. The Device page displays information about the device properties and associated WLANs, mobile devices, and alerts.
Chapter 8: Managing Mobile Device Distributed Servers 72 Chapter 8: Managing Mobile Device Distributed Servers The Mobile Device Server is distributed server software that lets you remotely manage and configure mobile devices. Although you can use multiple Servers at different Server Locations or on different network segments, you can manage all of your Servers from the Avalanche Console, regardless of where you access the Console.
Chapter 8: Managing Mobile Device Distributed Servers 73 For information on deploying a Mobile Device Distributed Server, see Building Server Deployment Packages on page 42. Creating Mobile Device Server Profiles Mobile Device Server Profiles are used to manage your Mobile Device Servers.
Chapter 8: Managing Mobile Device Distributed Servers 74 • Mobile Device Authentication. This option requires mobile devices to connect to the network through a wired connection (such as a cradle) and receive an authentication key. When you enable this option, the Mobile Device Server will challenge any device attempting to connect to the Server for a password. If the mobile device does not have the correct password, the Mobile Device Server will not allow a TCP/IP connection.
Chapter 8: Managing Mobile Device Distributed Servers 75 NOTE Serial connections are required to implement Mobile Device and Server Authentication. You can also restrict the number of devices that can update concurrently. These details can be configured from the Mobile Device Server Profile Details page. License Return From the Mobile Device Server Profile Details page, you can configure the return of licenses to the unused pool when a device has not contacted a server after a period of time.
Chapter 8: Managing Mobile Device Distributed Servers 76 would generate IDs such as Seattle-4, and Seattle-%05d would generate IDs such as Seattle-00004. Server Logging The log file records actions that have occurred on the Mobile Device Server. You can set the maximum log size and the log level for the file from the Mobile Device Server Profile Details page. You can set the log function to the following levels: • Critical.
Chapter 8: Managing Mobile Device Distributed Servers 77 Device Statistics From the Mobile Device Server Profile Details page, you can configure whether mobile devices upload statistics, inventory, and properties to the Mobile Device Server. The options include: • Suppress radio statistics collection. When this option is enabled, the Mobile Device Server will discard radio statistics data collected from the devices rather than transmitting it to the enterprise server.
Chapter 8: Managing Mobile Device Distributed Servers 78 • For Server Security, enable the desired options. If you choose to enable authentication, create a password and confirm it. You can turn off the password masking by enabling the Show passwords option. • For Server Resources, type the serial ports you want to reserve for Avalanche’s use in the text box. If desired, enable the Restrict number of concurrent devices and type a maximum number in the text box.
Chapter 8: Managing Mobile Device Distributed Servers 79 Communications Restrictions To allow you more control over bandwidth usage, Avalanche uses communication restrictions. During a server‐to‐server blackout, the Mobile Device Server is not allowed to communicate with the Enterprise Server. During a device‐to‐server exclusion, the Mobile Device Server is not allowed to communicate with mobile devices.
Chapter 8: Managing Mobile Device Distributed Servers 80 When you configure a Mobile Device Server update, you have the following options: • Event Type. You can select a one‐time event, a recurring event, or a post‐ synchronization event. A post‐synchronization event will take place after each synchronization between the Enterprise Server and the Mobile Device Server. This ensures that each time the Server is updated, the devices are as well. • Time Constraints.
Chapter 8: Managing Mobile Device Distributed Servers 81 NOTE If you chose a post‐synchronization event, the start and stop time options do not apply. 6 If desired, enable the Stop if not completed by option. Set the stop date and time. NOTE Selecting an end time is not required. This allows you to create events that recur indefinitely. 7 Enable the other update options as desired. 8 Click Save. The update appears in the Device Update Schedule region.
Chapter 8: Managing Mobile Device Distributed Servers 82 1 In the Authorized Users region, click Add. The New Authorized User dialog box appears. 2 From the user/group list, select the user. 3 From the permission list, choose Read/Write or Read‐only. 4 Click Save. The user is added to the Authorized Users region and has permissions for the profile. Secondary Mobile Device Servers Avalanche allows you to configure Mobile Device Server profiles with secondary server support.
Chapter 8: Managing Mobile Device Distributed Servers 83 3 The Mobile Device Server Details page appears. This page displays the server version, start time, status, and information about current licenses and serial ports. 4 If you want to view the licensing messages associated with the server, click License Messages.
Chapter 9: Managing Software Profiles 84 Chapter 9: Managing Software Profiles A software profile is a configuration profile containing software packages. The packages associated with the profile are installed on all devices meeting the selection criteria. Software profiles allow you to organize and configure software packages for deployment to multiple devices.
Chapter 9: Managing Software Profiles 85 7 The software profile is created and can be configured and assigned to a region or location. Applying Software Profiles Once you have created a software profile and added software packages to the profile, you can assign that profile to a region. The profile will then be deployed to all the Server locations in that region when you perform a server synchronization. For information about applying software profiles to regions, refer to Assigning Profiles on page 31.
Chapter 9: Managing Software Profiles 86 Field Description Type Displays the type of the software package. Software packages are divided into the following categories: • Control. An internally used package specific to the Avalanche Console. A network profile is an example of a control package. • Application. These packages install an application which can be run from the Application Menu screen on the mobile device. An example of an application package is the Telnet Client. • Support.
Chapter 9: Managing Software Profiles 87 Adding a Software Package Once you create a software profile, you must add the software packages to that profile. Through the software profile you can configure the software package settings and then deploy the packages to specific mobile devices. You can add packages, copy packages from another profile, or create custom software packages from the Web Console. Before you create a custom package, ensure you know the location of all the files you want to include.
Chapter 9: Managing Software Profiles 88 8 When you are finished configuring, click Finish to complete the installation. After software packages are configured and enabled, you can deploy the software profile and the packages will be distributed to all devices in the applied region(s) that meet the selection criteria. Building New Software Packages The Add Device Software Wizard allows you to compile files to create a new software package.
Chapter 9: Managing Software Profiles 89 • Vendor. Enter the package vendor. • Install Drive. Specify the drive on the mobile device where you to install the package. • Install Path. Specify the exact installation path for the package. • Post Install Options.You can specify if you want the device to perform a warm boot or cold boot after installation has completed. You can also specify a program to run once installation is complete.
Chapter 9: Managing Software Profiles 90 Installing CAB or MSI Packages You can use Avalanche to install .cab or .msi files on your mobile devices. When you install a .cab file, the file automatically installs. It can also be configured to uninstall once the program information is retrieved by the mobile device. To install .cab or .msi packages: 1 From the Available Profiles panel on the Profiles tab, click on the software profile you want to add the package to. The Software Profile Details page appears.
Chapter 9: Managing Software Profiles 91 software package just once and then copy it into all the profiles that require that package. To copy a software package: 1 From the Available Profiles panel on the Profiles tab, click on the software profile you want to add the package to. The Software Profile Details page appears. 2 In the Software Packages panel, click New. The Add Device Software page appears.
Chapter 9: Managing Software Profiles 92 Configuring Software Packages with a Utility Some software packages come with configuration utilities that allow you to configure options before the packages are installed on a mobile device. These utilities must be accessed from the Java Console. For more information, see the Java Console help. Configuring Software Packages for Delayed Installation Software packages can be configured to install on a delayed basis.
Chapter 9: Managing Software Profiles 93 • To further delay the package installation after it has been activated, enable and configure the Install delay option. This will delay the installation of the package after it has been downloaded. • If you want the package to be activated during a certain time window, enable the Install window option and configure the hours during which the package will activate.
Chapter 9: Managing Software Profiles 94 Field Description Only distribute to proxy devices until Enable this option to configure the time at which a non-proxy device can contact a proxy device to receive an update. A nonproxy device refers to a mobile device that is not being used to update other mobile devices. Enforce proxy distribution until Enable this option to configure the time at which a non-proxy mobile device can contact the Server to update and receive this package.
Chapter 9: Managing Software Profiles 95 If Then Proxy Devices And Non-proxy Devices Only distribute to proxy devices until is enabled and Enforce proxy distribution until is enabled and the configured time has been reached Can contact the Server for updates at any time. Can contact proxy devices to receive updates. No options are enabled Can contact the Server for updates at any time.
Chapter 10: Managing Mobile Devices 96 Chapter 10: Managing Mobile Devices This section provides information about the following mobile device topics: • Mobile Devices Panel • Managing Device Filters • Mobile Device Details Page • Configuring Mobile Device Properties • Contacting a Mobile Device • Mobile Device Profiles Mobile Devices Panel The Mobile Devices panel on the Inventory page shows a set of mobile devices based on the currently selected region or location.
Chapter 10: Managing Mobile Devices 97 Last Contact The date and time of the last contact the mobile device had with Avalanche. Recent Activity The status of a mobile device with respect to Avalanche. For example, when the mobile device receives new software, the activity status is Downloading. Above the Mobile Device panel on the Inventory tab, there are two buttons: Update Now and Send Message. These buttons are global and not site‐specific.
Chapter 10: Managing Mobile Devices 98 Mobile Devices Panel Tasks The Mobile Devices panel allows you to perform tasks to communicate with your devices. You can select to perform each task for one device, selected devices, or all devices currently listed. The following table provides descriptions of the tasks available in the Mobile Devices panel: Update When you click Update, the device is updated with the current configurations.
Chapter 10: Managing Mobile Devices 99 will display until the icons are available at the Console. Once the icons become available, they will display the next time the inventory list is loaded or refreshed. The icons will display in the Mobile Device Details dialog box the next time it opens. Enablers that support this must make two icons available to the Console. The large icon must be a .png image. It is recommended that the small icon be a .png image as well.
Chapter 10: Managing Mobile Devices 100 3 To remove columns from the Selected Columns list, select the column you want to remove and click [ < ]. The column name returns to the Available Columns list. 4 Use Move Up and Move Down to modify the order in which the columns appear in the Mobile Devices panel. 5 When you are finished, click Save. The columns are rearranged to reflect your modifications.
Chapter 10: Managing Mobile Devices 101 8 Select the column name and click [ > ] to move the property to the Selected Columns list. 9 When you are finished, click Save. The columns are arranged to reflect your modifications. Managing Device Filters You can filter which devices are displayed in the Mobile Devices panel by applying mobile device filters. When a filter is applied, only the devices meeting the criteria associated with that filter will be displayed.
Chapter 10: Managing Mobile Devices 102 The selection criteria appear in the Filter Expression text box. 5 Click Add Filter. The filter is added to the Existing Filters list and is available to use. 6 Click Save. You can now select the filter from the Use Custom Filter drop‐down list located in the Mobile Devices panel. Applying Device Filters Device filters can be applied in the Mobile Devices panel.
Chapter 10: Managing Mobile Devices 103 • Properties panel. Displays the properties last reported from the mobile device. These will include custom properties. For information on configuring properties for a mobile device, see Configuring Mobile Device Properties on page 106. • Applied Profiles panel. Displays the profiles that are applied to this device. You can filter the applied profiles by using the check boxes at the left of the panel. • Installed Software panel.
Chapter 10: Managing Mobile Devices 104 2 In the Tools panel, click Send Message. The Send Text Message dialog box appears. 3 Type a message in the Text Message field. 4 Enable the Provide Audible Notification option if you want a sound to play when the mobile device receives the message. 5 Click OK. The Status field in the Activity region displays the status of the text message request.
Chapter 10: Managing Mobile Devices 105 NOTE The rules that govern which mobile devices can receive a particular update are determined by the selection criteria. See Building Selection Criteria on page 140 for more information on building selection criteria. To update a mobile device: 1 From the Inventory tab, click the device you want to update in the Mobile Devices panel. The Mobile Device Details page appears. 2 In the Tools panel, click Update Now. The Update Now dialog box appears.
Chapter 10: Managing Mobile Devices 106 Locating a Device From the Web Console, you can view the most recently reported location of a mobile device with GPS capabilities. The device is displayed as an icon on the map with its GPS details in a callout box. In order to use this option, you must have a statistics server running, and statistics reporting must be enabled. To view the location of a mobile device: 1 Click the Inventory tab.
Chapter 10: Managing Mobile Devices 107 Properties can be used as selection variables in selection criteria to control which devices receive particular updates. NOTE Refer to Building Selection Criteria on page 140 for more information on using properties as selection variables.
Chapter 10: Managing Mobile Devices 108 Creating Custom Properties From the Web Console, you can create custom properties on the mobile devices. These properties can then be used to build selection criteria for software updates or a filter. NOTE Like the pre‐defined properties, custom properties appear as selection variables in the Selection Criteria Builder. You can add custom properties to individual mobile devices or to mobile device groups.
Chapter 10: Managing Mobile Devices 109 NOTE It is important to note that the Avalanche Enabler sends device‐side properties to the Enterprise Server; it does not collect the information. Vendors must create their own applications and utilities to gather the required information and write it to a plain‐text file on the device. Device‐side properties must be written in key‐value pairs to a plain‐text file with a .prf extension and one vendor entry.
Chapter 10: Managing Mobile Devices 110 • Editing Custom Properties for Mobile Device Profiles • Configuring Mobile Device Profile Advanced Settings Creating and Configuring Mobile Device Profiles When you create a mobile device profile, you can enable it, and define orphan package removal and selection criteria.
Chapter 10: Managing Mobile Devices 111 For information about adding authorized users, refer to Assigning Authorized Users to Profiles on page 27. Editing Registry Keys for Mobile Device Profiles You can add registry keys to a mobile device profile. Once you add a registry key to the profile, you can add values for the key. You also have the option to edit or remove existing registry keys or values on the device. You must know the name and location of the key or value in order to edit or remove it.
Chapter 10: Managing Mobile Devices 112 Removing a Registry Key You can remove an existing registry key on a mobile device through a Mobile Device Profile. You must know the name of the key/value to remove it. To remove a registry key: 1 From the Profiles tab, click the name of the mobile device profile you want to configure. 2 The Mobile Device Profile Details page appears. 3 In the Registry Entries panel, click New. The New Registry Entry dialog box appears. 4 Select the Root from the drop‐down list.
Chapter 10: Managing Mobile Devices 113 Adding a Custom Property You can add a custom property to a mobile device through a Mobile Device Profile. Add the property to the profile, then deploy the profile to the device. To add a custom property: 1 From the Profiles tab, click the name of the mobile device profile you want to configure. 2 The Mobile Device Profile Details page appears. 3 In the Properties panel, click New. The New Property dialog box appears.
Chapter 10: Managing Mobile Devices 114 5 Type the current Property Name and Value in the text boxes. 6 Select Delete property as the Action. 7 Click Add and Save. The task is added to the list in the Device Properties region. The property will be removed when the profile is deployed to the mobile devices. Configuring Mobile Device Profile Advanced Settings You can configure GPS reporting, geofence areas, time zone settings and update restrictions for your mobile devices from a Mobile Device Profile.
Chapter 10: Managing Mobile Devices 115 • Prompt user to initiate GPS acquisition. Prompts the mobile device user to go outside when the device is trying to acquire GPS coordinates. • Notify user after __ consecutive GPS failures. Provides a notification to the mobile device user after the device has failed to acquire GPS coordinates the specified number of times. To configure location-based services: 1 From the Profiles tab, click the name of the mobile device profile you want to configure.
Chapter 10: Managing Mobile Devices 116 The area is added to the list. Regional Settings You can set the region and time zone for your mobile devices from a Mobile Device Profile. To change the regional settings of a Mobile Device Profile: 1 From the Profiles tab, click the name of the mobile device profile you want to configure. The Mobile Device Profile Details page appears. 2 Enable the Manage regional settings check box and select the region from the drop‐down menu.
Chapter 11: Managing Mobile Device Groups 118 Chapter 11: Managing Mobile Device Groups To better organize your wireless network, you can use the Web Console to create collections of mobile devices, called mobile device groups. These groups allow you to manage multiple devices simultaneously, using the same tools available for managing individual mobile devices. Mobile device groups can include devices from the entire network, regardless of the region or location of the device.
Chapter 11: Managing Mobile Device Groups 119 created, and then the devices currently in the Mobile Device Inventory that match the selection criteria are added to the group. If a new device matching the selection criteria for a static mobile device group connects to the Avalanche Console, it will not automatically be placed in the mobile device group.
Chapter 11: Managing Mobile Device Groups 120 Adding Devices to a Static Group A static mobile device group does not change when the device inventory changes. If you want to add devices to a static group, you must do it manually. To add devices to a static group: 1 Click the Inventory tab. 2 In the Mobile Device Groups panel, click the name of the group you want to modify. The Mobile Device Group page appears. 3 Click Edit.
Chapter 11: Managing Mobile Device Groups 121 The Mobile Device Group page appears. 3 Select the check box to the left of the name of the device you want to remove from the group. 4 Click Remove. 5 The device is removed from the group. Adding Mobile Device Group Authorized Users Avalanche allows you to assign administrative privileges for a specified mobile device group to a user that has Normal user rights.
Chapter 11: Managing Mobile Device Groups 122 Pinging Mobile Devices within Mobile Device Groups You can use mobile device groups to ping a collection of mobile devices simultaneously. You can ping mobile devices that are currently in range and running the Avalanche Enabler, an Avalanche‐enabled application, or in some cases a configuration utility. NOTE This is not an ICMP‐level ping, but rather an application‐level status check. This feature indicates whether the mobile device is active or not.
Chapter 11: Managing Mobile Device Groups 123 3 In the Mobile Device Groups panel, click the name of the group you want to send a message to. The Mobile Device Group page appears. 4 In the Mobile Devices panel, enable the check box to the left of the name of the devices you want to send a message to. 5 Click Message. The Send Message dialog box appears. 6 Type the message in the text box and click Send. The Recent Activity column reports the status of the message for each device in the group.
Chapter 12: Managing Alert Profiles 124 Chapter 12: Managing Alert Profiles You can manage alerts in Avalanche using Alert Profiles. An Alert Profile gives you options for configuring what events generate an alert and who is notified when an alert is generated. Examples of what might generate an alert might be if a server goes offline or if a new mobile device is discovered.
Chapter 12: Managing Alert Profiles 125 The settings that can be configured for an alert profile include: Email Settings If you plan to use an SMTP server, you must enter the name or address of the server, a username and password, and a reply‐to e‐mail address. Email Recipients Each alert profile can notify one or more e‐mail addresses when specified events occur.
Chapter 12: Managing Alert Profiles 126 • To add an e‐mail recipient, click New in the Email Recipients panel. NOTE You must have the SMTP server settings configured if you want to send alert e‐mails. • To add an SNMP address, click Add in the SNMP Forwarding panel. • To add events to the Alert Profile, select the checkbox next to the event in the Available Alerts panel. Use the arrows to page through the events, or use the filters to restrict which events appear. 6 Click Save.
Chapter 12: Managing Alert Profiles 127 • To delete an e‐mail recipient or SNMP proxy, enable the checkbox next to it and click Delete at the top of the appropriate panel. • To add or delete events, select the checkbox next to the event in the Available Alerts panel. Use the arrows to page through the events, or use the filters to restrict which events appear in the list. 4 Click Save to return to the Alert Profile Details page.
Chapter 12: Managing Alert Profiles 128 5 Click Open. The file name appears in the Upload Email Recipients text box. 6 Click Save. The contacts display in the Profiled Contacts list. Exporting E-mail Addresses You can export e‐mail addresses from the Email Recipients list of an Alert Profile to a .csv file. To export e-mail addresses: 1 From the Available Profiles panel on the Profiles tab, click on the Alert Profile you want to edit. The Alert Profile Details page appears.
Chapter 12: Managing Alert Profiles 129 You can assign more than one Alert Profile to a region. Each profile will generate alerts based on the events assigned to that profile. If you have specified the same alert in two different profiles assigned to the same region, only one alert for a matching event will be generated. For more information about assigning Alert Profiles to a region, refer to Assigning Profiles on page 31.
Chapter 12: Managing Alert Profiles 130 Viewing Where Alert Profiles Are Applied When you have selected an Alert Profile, the Applied Locations panel allows you to see exactly where the profile is applied. For information on applying a profile, refer to Assigning Profiles on page 31. To view where an Alert Profile is applied: • From the Profiles tab, click on the Alert Profile you want to view. The Alert Profile Details page appears.
Chapter 12: Managing Alert Profiles 131 To acknowledge an alert: • From the Alerts tab, select the check boxes next to the alerts you want to acknowledge and click Ack. ‐Or‐ • From the Alerts tab, click Ack All. Clearing Alerts When the Alert Browser begins to fill with alerts, you may want to remove acknowledged alerts that are no longer relevant. To clear alerts: • From the Alerts tab, select the check boxes next to the alerts you want to clear and click Clear.
Chapter 12: Managing Alert Profiles Figure 12-2. Alert Settings on the System Settings page 2 Under Alert Settings, use the Days of alerts to display and Number of alerts to store boxes to configure the alert settings. 3 Click Save to save your changes. The Alerts tab will update to reflect your changes.
Chapter 13: Using Maps and Floorplans 133 Chapter 13: Using Maps and Floorplans The Web Console provides a scalable world map to help you view where your servers and devices are located. Additionally, you have the option of importing a floorplan and mapping where your infrastructure devices are located on your own map.
Chapter 13: Using Maps and Floorplans 134 Servers. When this option is enabled, all server locations that have defined GPS locations will be displayed on the map. You can view location‐specific information in a callout box when you click on a server location. Sites. When this option is enabled, all sites that have defined GPS locations will be displayed on the map. You can view site‐specific information in a callout box when you click on a site. Show Alert Levels Critical Alerts.
Chapter 13: Using Maps and Floorplans 135 To view the map on the Web Console: • Click the Maps tab or Maps context link. Using Floorplans With the Web Console, you can import floorplans, plot where your infrastructure devices are located, and view radio coverage and associated mobile devices on the map. You can have multiple floorplans and associate an infrastructure device with more than one floorplan. The user must have regional permissions in order to view and configure floorplans.
Chapter 13: Using Maps and Floorplans 136 4 Click Browse to navigate to the location of the floorplan image file. When you have selected the image file, click Next. NOTE You can use the same image file to create multiple floorplans with different device mapping. The Set Floorplan Scale page appears. 5 Click to set a start point and an end point for a known distance on the floorplan. 6 After the start and end points have been set, the Enter actual distance options appear.
Chapter 13: Using Maps and Floorplans 137 Adjusting the Floorplan Display A floorplan can display the location of your infrastructure devices, their estimated radio range, and the associated mobile devices. The predicted radio range is an estimation that does not take physical obstructions into account. It is based on the radio type and power level reported by the device. When associated mobile devices are displayed, they appear near the infrastructure device with which they are associated.
Chapter 13: Using Maps and Floorplans 138 Mobile Devices — Show unmanaged Displays mobile devices not being managed by Avalanche. Limit to Plotted Infrastructure Devices selected below Displays only those devices that have the check box next to their name in the Plotted Infrastructure panel enabled. NOTE If the current power level for a device is reported as 0, you will not be able to view predicted coverage for that device. The reported power level may be 0 if the device is disabled.
Chapter 14: Using Selection Criteria 139 Chapter 14: Using Selection Criteria Selection criteria are sets of rules which you can apply to individual software collections and individual network profiles. These criteria define which mobile devices or infrastructure devices will receive designated updates. For a software collection, the selection criteria determine which mobile devices can receive the software packages contained in the collection.
Wavelink Avalanche Mobility Center You can use the selection criteria builder to build a valid selection criteria string. You can also use the selection criteria builder to test the selection criteria string on specific mobile devices that appear in the Mobile Device Inventory tab.
Chapter 14: Using Selection Criteria 141 NOTE Parentheses are recommended when multiple operators are involved. Nesting of parentheses is allowed. • Actual values that are assigned to a selection variable. For example, if you assign a value of 6840 to a ModelName variable by building the string ModelName = 6840, then you will restrict packages or profiles to model 6840 mobile devices. To build selection criteria: 1 Access the Selection Criteria Builder by clicking the Launch wizard button.
Wavelink Avalanche Mobility Center Building Custom Properties You can build custom properties to use in your selection criteria. To build custom properties: 1 From the Selection Criteria Builder, select New Property. The Add Custom Property dialog box appears. 2 Enter the name for the custom property and click OK. The new property is added to the drop‐down list. Selection Variables Selection criteria are based on the use of selection variables.
Chapter 14: Using Selection Criteria 143 Series = 3 | (MAC = 00-A0-F8-27-B5-7F | MAC = 00-A0-F8-80-3D4B | MAC = 00-A0-F8-76-B3-D8 | MAC = 00-A0-F8-38-11-83 | MAC = 00-A0-F8-10-24-FF | MAC = 00-A0-F8-10-10-10) Selection variables for the selection criteria string are as follows: Columns The number of display columns the mobile device supports. The possible value range is 1 – 80. Example: Columns > 20 EnablerVer Predefined Enabler version number.
Wavelink Avalanche Mobility Center KeyboardCode A number set by the device manufacturer and used internally by the BIOS to identify the keyboard type. Supported values include: 0 = 35‐Key 1 = More than 35 keys and WSS1000 2 = Other devices with less than 35 keys Example: KeyboardCode = 0 KeyboardName A value indicating which style of keyboard the mobile device is using (46key, 35key, etc.). This selection variable is not valid for CE devices.
Chapter 14: Using Selection Criteria Last Contact 145 The parser for the LastContact property is unique because it not only allows specifying absolute time stamps, but also relative ones, forcing their constant reevaluation as the time‐base changes.
Wavelink Avalanche Mobility Center MAC MAC address of the mobile device. Enter any MAC addresses as a string of hexadecimal digits. Dashes or colons between octets are optional. For example: MAC = 00:A0:F8:85:E8:E3 ModelName The standard model name for a mobile device. This name is often a number but it can be alphanumeric. Examples include 6840, 3940, and 4040. If the model number is unknown, it might appear in one of the views when the mobile device is selected.
Chapter 14: Using Selection Criteria ModelCode 147 A number set by the device manufacturer and used internally by the BIOS to identify the hardware. Supported values include: 1= LRT 38xx/LDT 2 = VRC39xx/69xx 3 = PDT 31xx/35xx 4 = WSS1000 5 = PDT 6800 6 = PDT 6100 Example: ModelCode <= 2 This matches all 38xx, 39xx, and 69xx devices. OSVer Predefined property designated by the Enabler. Values with decimals in them must be surrounded by double quote marks. OSVer = “4.
Wavelink Avalanche Mobility Center Assigned IP IP address of the mobile device. Enter all IP addresses using dot notation. IP addresses can be written 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 as IP = 10.1.1.5 – 15.) • Comparison with a subnet. This is done by supplying the network number along with the subnet mask or CIDR value.
Chapter 14: Using Selection Criteria Rows 149 The number of display rows the mobile device supports. The possible value range is 1 to 25. Example: (KeyboardName=35Key)&(Rows=20) This example matches all mobile devices with 20 rows and 35‐key keyboards. Syncmedium The type of synchronization medium for the mobile device to use. Supported values include: any ip serial Terminal ID The unique ID for the mobile device that Avalanche generates.
Wavelink Avalanche Mobility Center Operators All selection criteria strings are evaluated from left to right, and precedence of operations is used when calculating the selection criteria. When more than one operator is involved, you must include parentheses in order for the selection criteria string to be evaluated properly.
Chapter 14: Using Selection Criteria AND (&) 151 Binary operator that results in TRUE if and only if the expressions before and after it are also both TRUE. Example: (ModelName=3840) | ((ModelName=6840) & (KeyboardName= 46Key)) OR (|) Binary operator that results in TRUE if either of the expressions before and after it are also TRUE. (ModelName =6840) | (ModelName = 3840) 6840 and 3840 mobile devices can receive the software package.
Wavelink Avalanche Mobility Center >= Binary operator that results in TRUE if the expression on the left is greater than or equal to the expression on the right. Example: Rows >= 21 <= Binary operator that results in TRUE if the expression on the left is less than or equal to the expression on the right. Example: Rows <= 20 (*) Wildcard operator. Wildcard expressions should be quoted and must be used with either an EQ or NE operator.
Chapter 15: Using the Task Scheduler 153 Chapter 15: Using the Task Scheduler The Task Scheduler enables you to schedule network management activities for your server locations and regions. When you configure an aspect of your wireless network using the Avalanche Console, those configurations are not immediately sent to the rest of your network. Instead, you can schedule specific times during which the new configurations are sent.
Chapter 15: Using the Task Scheduler 154 Use local time of server location. Uses the time local to the specified server(s) rather than the local time of the enterprise server. Schedule a recurring event for the task Performs the task repeatedly at the scheduled times. This selection allows you to configure the following options: Start time. The time of day the event will begin. Use end time. The time of day the event will end.
Chapter 15: Using the Task Scheduler 155 • Run every __ week(s) on. This option allows you to configure whether the task is run weekly or at a longer interval. For example, if you want the task to run every other Saturday, type 2 in the text box and enable the SAT checkbox. • [days of the week]. These checkboxes allow you to specify which days of the week the task is performed. Monthly. The task is performed on a monthly basis.
Chapter 15: Using the Task Scheduler 156 To perform a server synchronization: 1 Click Tools > Scheduled Tasks. The Scheduled Task Wizard page appears. 2 From the Task Type drop‐down list, select Server Synchronization and click Next. 3 To add a server location to the list, click Add and select the location from the list that appears. When you are finished adding server locations, click Next. The Scheduling Options screen appears. 4 Determine when the event will occur and click Next.
Chapter 15: Using the Task Scheduler 157 The Create A System Backup screen appears. 3 In the Name of new backup text box, enter an identifier for the system backup and click Next. This tag is used to select the correct file when restoring the system. It is not the same as the name of the zip file. The Scheduling Options screen appears. 4 Determine when the event will occur and click Next. 5 The Review Your Task screen appears. Review your task to ensure that it is correct and click Finish.
Chapter 15: Using the Task Scheduler 158 • Select Restore the most recent system backup to restore Avalanche to the latest backup file. • Select Restore by path to specify the file name and path of the desired system backup. • Select Restore selected to choose the desired system backup according to the identifier tag. The Review Your Task screen appears. 4 Review your task to ensure that it is correct and click Finish. The Task Scheduled dialog box appears.
Chapter 16: Avalanche Reports 159 Chapter 16: Avalanche Reports The Avalanche Reports tool can help you organize information about the activity or status of devices or software on your network. These reports are generated from the information Avalanche stores in its database. You can create reports with an Avalanche template or you can create a custom report to display the desired information.
Chapter 16: Avalanche Reports 160 The columns displayed in these panels include the following: Name Displays the name of the report. Template Displays the template used for the report. Location Indicates the location(s) involved in the report. Completed Displays when the report was completed. Frequency Displays how frequently the scheduled report will be run. Category Displays the category to which the report belongs. To access the Reports tool: 1 Access the Web Console.
Chapter 16: Avalanche Reports 161 Figure 16-1. Create a New Report page 3 Click on the desired template from the list of preexisting Avalanche report templates. 4 Depending on the template, the Reports tool will guide you through configuring the available options for the report. These will always include the name and output format, but may also include the scope or the time period to be included in the report. • Name. You must have a unique name for each configured report. • Output Format.
Chapter 16: Avalanche Reports 162 Generating Reports After a report has been configured, it can be generated immediately or scheduled for a specific time. When a report is scheduled, it can be set to run once or on a recurring basis. This section includes instructions for the following: • Running a Report • Scheduling a Report Running a Report After a report has been configured, you can generate it at any time.
Chapter 16: Avalanche Reports 163 4 From the drop‐down list, select how frequently you want the report to run. 5 Type the date and time you want the report to run in the text boxes. For the date, use a mm/dd/yyyy format. 6 Click Next. 7 A summary of report appears. Click Done to return to the Reports tool. Creating Custom Reports The Reports tool allows you to create custom reports using information from your databases. In order to utilize custom reports, you must be familiar with SQL query statements.
Chapter 16: Avalanche Reports 164 5 Select the database table on which you would like to report, and then enable the checkboxes for the columns which you want to include. Click Next. A Summary page appears. 6 If you want to include information from a different table, click Add Table. When you are finished adding tables, click Next. 7 Type a Report Name in the text box and select the Output Format for the report. Click Next. 8 A summary of the report appears.
Appendix A: SSL Certificates 165 Appendix A: SSL Certificates The Avalanche Web Console uses Hypertext Transfer Protocol (http) by default, which is not encrypted. If you want your information to be encrypted, you can configure Avalanche to use https with an SSL certificate instead.
Appendix A: SSL Certificates 166 • server.xml This section contains the following tasks for obtaining an SSL certificate from a certificate authority: • Creating a Keystore • Generating the Certificate Signing Request • Importing an Intermediate Certificate • Importing a Certificate • Activating SSL for Tomcat • Accessing the Web Console over a Secure Connection • Troubleshooting Creating a Keystore To create a keystore for the certificate, use the keytool.exe utility.
Appendix A: SSL Certificates 167 NOTE The Common Name (domain name) you enter should be one that your company owns. Add a DNS entry if needed to resolve this computer to the Common Name. 5 At the prompts, enter your organizational unit, organization, city, state, and the country code. 6 When you are prompted to review your information, type yes to confirm that it is correct. If you type no, you will be guided through the prompts again.
Appendix A: SSL Certificates 168 Generating the Certificate Signing Request Once you have created the keystore, you can use the keytool.exe utility to generate a certificate signing request (certreq.csr) file to send to a certificate authority. To generate a certificate signing request: 1 From a command line, navigate to: [Avalanche installation directory]\JRE\Bin 2 Use the command: keytool -certreq -keyalg RSA -alias amccert -file certreq.
Appendix A: SSL Certificates 169 3 Enter your keystore password. The intermediate certificate is added to the keystore. Importing a Certificate Once you have received your certificate, you need to import it into the keystore. Your certificate will probably come as a file with the extension .cer or in the body of an e‐mail. If it comes in the body of an e‐mail, copy the contents to a text editor and save the file with a .cer extension.
Appendix A: SSL Certificates 170 3 Remove the comment markers so that the section is not commented out. 4 Modify the section to contain the following information: PAGE 171Appendix A: SSL Certificates 171 C:\Program Files\Wavelink\AvalancheMC\WebUtilities\Tomcat\logs to find Catalina Tomcat logs. NOTE You need to stop the Tomcat service to get all the log messages. Example log file: catalina.2010-02-24.log Implementing a Self-Signed Certificate These instructions explain how to generate a self‐signed certificate in the Apache Tomcat environment.
Appendix A: SSL Certificates 172 to provide a keystore name and passwords for the keystore and alias. These are arbitrary, but should be noted for future reference. To generate a self-signed certificate: 1 From a command line, navigate to: [Avalanche installation directory]\JRE\Bin 2 Use the command: keytool -genkey -alias amcselfcert -keyalg RSA -keystore selfsignkeystore.keystore 3 At the prompt Enter keystore password, type the keystore password. When prompted, re‐enter the password.
Appendix A: SSL Certificates 173 What is the name of your organization? [Unknown]: Wavelink Corporation What is the name of your City or Locality? [Unknown]: Midvale What is the name of your State or Province? [Unknown]: Utah What is the two-letter country code for this unit? [Unknown]: US Is CN=avaself.wavelink.
Appendix A: SSL Certificates 174 keystorePass=”avalanche” NOTE If you are not using port 443 for any other applications, you can change the connector port to 443. Changing the port to 443 will allow you to access the Web Console without entering the port within the URL. 5 Save your changes to the file. 6 Restart the Apache Tomcat for Wavelink service.
Appendix B: Avalanche Services 175 Appendix B: Avalanche Services This appendix lists all of the Avalanche services. Under each service title, you’ll find the file path where the service is located and which type of server (Enterprise Server, Infrastructure Server or Mobile Device Server) uses the service. Wavelink Authentication Service C:\Program Files\Wavelink\AvalancheMC\CESecureServer.exe Enterprise Server Apache Tomcat C:\Program Files\Wavelink\AvalancheMC\WebUtilities\Tomcat\bin\ tomcat6.
Appendix B: Avalanche Services Wavelink Avalanche Enterprise Server C:\Program Files\Wavelink\AvalancheMC\eserver.exe Enterprise Server Wavelink Information Router C:\Program Files\Wavelink\AvalancheMC\WLInfoRailService.exe Enterprise Server Wavelink License Server C:\Program Files\Wavelink\AvalancheMC\WLLicenseService.exe Enterprise Server Wavelink Service Manager C:\Program Files\Wavelink\MM\Program\svcmgr.
Appendix B: Avalanche Services 177 Infrastructure Server Wavelink Avalanche Agent C:\Program Files\Wavelink\Avalanche\Service\WLAvalancheService.
Appendix : Database Ports 178 Appendix C: Port Information This appendix provides information about the ports used in Avalanche MC. The information provided includes: • Database Ports • Enterprise Server Ports • Infrastructure Server Ports • Mobile Device Server Ports • The following table provides a list of the ports that the Mobile Device Server uses. NOTE Except where noted, the ports listed are all inbound ports.
Appendix : Infrastructure Server Ports 179 NOTE The Enterprise Server also listens on 8443 for a Tomcat connection with an SSL certificate. You can change this to 443 in the server.xml file if no other program is using 443. Infrastructure Server Ports The following table provides a list of the ports that the Infrastructure Server uses.
Appendix : Mobile Device Server Ports 180 Mobile Device Server Ports The following table provides a list of the ports that the Mobile Device Server uses. Port Description Port Type 1777 Protocol Service TCP/UDP 1778 Services persistent connections to mobile devices TCP Wavelink Products Used with Avalanche The following table provides a list of the ports that are used by Wavelink products often used in conjunction with Avalanche.
Appendix D: Supported Firmware 181 Appendix D: Supported Firmware Avalanche is not packaged with any firmware files. You must obtain supported firmware from the manufacturer and then import the files into Avalanche. The following table lists the vendor, hardware and firmware versions supported in Avalanche. Vendor Hardware Supported Versions Avaya AP-3 2.5.2 2.4.11 2.4.5 2.3.3 2.3.2 AP-4/5/6 2.5.2 2.4.11 2.4.5 2.3.3 2.3.2 AP-8 2.5.2 2.4.11 1100 IOS 12.3-8JED 12.3-8JEC3 12.3-8JEC 12.3-8JEB1 12.
Appendix D: Supported Firmware 182 Vendor Hardware Supported Versions Cisco 1130 12.4.21a-JA1 12.4.10b-JDA3 12.4.10b-JA 12.4-3gJA1 12.4-3gJA 12.3-8JEA3 12.3-8JEA2 12.3-11JA4 12.3-11JA1 12.3-8JEB 12.3-8JEA1 12.3-8JEA 12.3-8JA 12.3-7JA3 12.3-7JA 12.3-4JA 12.3-2JA 12.3-2JA2 1200 12.05 12.04 12.03T 12.02T1 12.01T1 11.56 11.42T 1200 IOS 12.3-8JED 12.3-8JEC3 12.3-8JEC 12.3-8JEB1 12.3-8JEA3 12.3-8JEA2 12.3-8JEB 12.3-8JEA1 12.3-8JEA 12.3-8JA 12.3-7JA3 12.3-7JA 12.3-4JA 12.3-2JA 12.3-2JA2 12.2-15JA 12.
Appendix D: Supported Firmware 183 Vendor Hardware Supported Versions Cisco 1240 IOS 12.4.21a-JA1 12.4.10b-JDA3 12.4.10b-JA 12.4-3gJA1 12.4-3gJA 12.3-8JEA3 12.3-8JEA2 12.3-11JA4 12.3-11JA1 12.3-8JEB 12.3-8JEA1 12.3-8JEA 1310BR 12.4.21a-JA1 12.4.10b-JDA3 12.4.10b-JDA2 12.4.10b-JA 12.4.3g-JA1 12.3-8JEA3 12.3-8JEA2 12.3-11JA4 12.3-11JA1 12.3-8JEB 12.3-8JEA1 12.3-8JEA 12.2(15)JA 10.4-3g-JA 340 AP 12.05 12.04 12.03T 12.02T1 12.01T1 11.23T 11.10T1 350 AP 12.05 12.04 12.03T 12.02T1 12.01T1 11.23T 11.
Appendix D: Supported Firmware 184 Vendor Hardware Supported Versions Cisco 350 IOS 12.3-8JEA3 12.3-8JEA2 12.3-8JEA1 12.3-8JEA 12.3-8JA 12.3-7JA3 12.3-7JA 12.3-4JA 12.3-2JA 12.3-2JA2 12.2-15JA 12.2-13JA2 12.2-13JA1 Dell TrueMobile 1170 2.2.2 HP ProCurve 520wl 2.4.5 2.1.2 Meru MC1000 3.6-111(via Extended Device Support) Motorola/Symbol AP-3020 04.02-19 AP-4121 02.70-12 02.70-06 02.52-13 02.51-23 AP-4131 03.95-04 03.94-15a 03.93-00 03.92-21 03.70-77 03.70-46a 03.50-26 03.
Appendix D: Supported Firmware 185 Vendor Hardware Supported Versions Motorola/Symbol AP-5181 2.3.1.0-004R 2.3.0.0-019R 2.2.2.0-001R 2.2.1.0-007R 2.2.0.0-023R 2.1.1.0-001R 2.1.0.1-003R 2.1.0.0-030R 2.0.0.0-045R 1.1.2.0-005R 1.1.1.0-020R AP 7131 4.0.3.0-010R 4.0.2.0-003R 4.0.1.0-019R 4.0.0.0-057R 3.2.2.0-005R 3.2.1.0-012R 3.2.0.0-067R 3.0.2.0-028R 3.0.0.0-039R RFS 7000 4.2.0.0-024R 4.1.0.0-042R 4.0.2.0-001R 4.0.1.0-005R 4.0.0.0-067R 1.3.2.0-010R 1.3.1.0-003R 1.3.0.0-029R 1.2.0.0-040R 1.1.1.
Appendix D: Supported Firmware 186 Vendor Hardware Supported Versions Motorola/Symbol WS2000 2.4.3.0-020R 2.4.1.0-005R 2.4.0.0-023R 2.3.2.0-003R 2.3.1.0-012R 2.3.0.0-035R 2.3.0.0-034R 2.2.3.0-020R 2.2.2.0-003R 2.2.1.0-018R 2.2.0.0-021R 2.1.1.0-009R 2.1.0.0-035R 2.0.0.0-036R 1.5.0.0-216r 1.0.10.08 WS5000 1.2.0.39o 1.2.0.39f 1.1.4.30f 1.1.4.30SP1 WS5000 v1.2+ 2.1.5.0-003R 2.1.4.0-001R 2.1.3.0-010R 2.1.2.0-010R 2.1.1.0-006R 2.1.0.0-029R 2.0.0.0-034R 1.4.3.0-012R 1.4.2.0-005R 1.4.1.0-014R 1.2.5.
Appendix D: Supported Firmware 187 Vendor Hardware Supported Versions Motorola/Symbol WS5100 v3.0+ 3.3.3.0-006R 3.3.2.0-010R 3.3.1.0-003R 3.3.0.0-029R 3.2.0.0-040R 3.1.0.0-045R 3.0.4.0-004R 3.0.3.0-003R 3.0.2.0-008R 3.0.1.0-145R 3.0.0.0-267R Proxim 2000 2.5.5 2.5.3 2.5.2 2.4.11 2.4.5 2.4.4 2.3.3 2.3.1 2.2.2 4000 4.0.3 4.0.2 4.0.0 3.7.0 3.6.3 3.4.0 3.2.1 3.1.0 2.6.0 2.5.2 2.4.11 2.4.10 4900 4.0.9 4.0.3 4.0.2 4.0.0 3.7.0 3.6.3 3.4.0 3.2.1 3.1.
Appendix D: Supported Firmware 188 Vendor Hardware Supported Versions Proxim 600 2.5.5 2.5.3 2.5.2 2.4.11 2.4.5 2.4.4 2.3.3 2.3.1 2.2.2 700 4.0.3 4.0.2 4.0.1 4.0.0 3.7.0 3.6.6 3.4.0 3.2.1 3.1.0 2.6.0 2.5.2 AirSPEED AP 541 2.6.0 2.5.2 AirSPEED AP 542 2.6.0 2.5.2 2.4.11 Systimax Transitional Firmware Transitional firmware refers to the rare cases when a particular firmware version is required when updating to a newer revision of firmware. For example, when updating the WS5100 v1.
Appendix D: Supported Firmware Cisco 1200 • 12.2‐11JA1 Motorola/Symbol WS2000 • 2.0.0.0‐036R Motorola/Symbol WS5000 • 1.1.4.30SP1 Motorola/Symbol WS5100 • 2.1.1.0‐006R • 3.0.0.
Appendix E: Wavelink Contact Information 190 Appendix E: Wavelink Contact Information If you have comments or questions regarding this product, please contact Wavelink Customer Service. E‐mail Wavelink Customer Support at: CustomerService@wavelink.com For customers within North America and Canada, call the Wavelink Technical Support line at 801‐316‐9000 (option 2) or 888‐699‐9283. For international customers, call the international Wavelink Technical Support line at +800 9283 5465.
Glossary 192 Glossary ActiveSync A synchronization program developed by Microsoft. It allows a mobile device synchronize with either the machine running Avalanche. Administrator User Accounts Users assigned as Administrator Accounts have unlimited permissions, and can assign and change permissions for Normal user accounts. Alert Profile A collection of traits that define a response to a specific network or statistical alert.
Glossary 193 Client A mobile device with an installed Avalanche Enabler, which allows the client to communicate with an Server and to be configured and managed through Avalanche. Default Profile A profile that the Servers automatically assign to network infrastructure or mobile devices. The Servers apply these default profiles to any devices discovered that are not assigned to a profile.
Glossary 194 Distributed Server Locations Also known as Server Locations. These are locations within your network where you want to manage mobile and infrastructure devices. You must deploy either a Infrastructure Server or a Mobile Device Server to a Server Location. DNS Domain Name System. A service that provides host name‐to‐IP address mapping. Enabler The software installed on a mobile device that allows Avalanche to manage it.
Glossary 195 Infrastructure Device Infrastructure devices include access points, routers and switches. Infrastructure Server Profile Infrastructure Server Profiles allow you to define device access privileges for your Infrastructure Servers.
Glossary 196 Orphan Packages A software package that has been deployed to a client through Avalanche, but has been disabled or is not recognized by the Server. You must orphan a software package before you can use Avalanche to delete it from the client. Ping An IP service that is used to test IP connectivity. Part of the ICMP service. Profile A collection of configuration settings that can be applied to multiple access points simultaneously.
Glossary 197 Scan to Configure The ability to configure barcode profiles that contain network profile settings. You can then print the profiles as barcodes and scan the barcodes with a mobile device with an Enabler 3.5 (or later versions). The information configures the network profile of the mobile device. Secondary Servers If configured and assigned, secondary servers allow mobile devices to attempt to connect to a secondary Mobile Device Server if the primary server is not available.
Glossary 198 Terminal ID The identification number of a specific (physical) terminal or workstation on the network. Very Large Access Control List A Very Large Access Control List (or VLACL), is a list of MAC addresses that are allowed to communicate through a specific access point. Unlike an Access Control List, which is managed by the access point, a VLACL is managed by an Agent, allowing it to support thousands of MAC addresses.
Index 199 Index A server deployment packages 42 alert profiles Server Locations 37 applying 130 removing 130 alerts user accounts 25 custom reports 163 acknowledging 130 D applying profiles 130 default login 14 clearing 131 delayed software package installation 92 configuring profiles 126 deploying servers 156 managing 124 applying profiles 31 universal updates 155 authorized users 26 distribution, package 93 profiles 27 regions 26 Avalanche backing up 156 components 9 launching the Web
Index 200 distributed Server 36 ping 104 software packages 87 profile updates 79 properties 106 L reporting statistics 77 license return 75 text message 103 location management 10 updating 104 login, default 14 viewing Mobile Device Details 102 M map 133 viewing properties 107 Mobile Devices panel 96 custom columns 100 Mobile Device Details page 102 custom properties 101 mobile device groups 118 device filters 101 additional functions 123 editing columns 99 creating 118 pinging clients
Index 201 region 31 server deployment packages 42 Server Locations 10, 33 Q creating 37 querying infrastructure devices 68 moving 39 R properties 39 regional permissions 24 regions 10, 29 adding 30 applying profiles 31 unassigned 38 services, Avalanche 175 sites 40 software packages configuring 92 deleting 33 copying 90 properties 31 delayed installation 92 reports enabling 91 custom 163 exporting 164 Reports Tool, accessing 159 installing 87 software profiles adding 84 resetting access
Index 202 WLAN IP settings 48 WLAN settings 50 WWAN settings 54
