WM4 4AndLaterServerAdministrationGuideIssue2 PDF

Cambium
Wireless
Manager
Server
Administration
Guide
System Release
4.4 and Later
Issue 2 October 2015

© 2015 Cambium Networks. All Rights Reserved.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Cambium Networks assumes
no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Cambium reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in
content hereof with no obligation to notify any person of revisions or changes. Cambium does not assume any
liability arising out of the application or use of any product, software, or circuit described herein; neither does it
convey license under its patent rights or the rights of others. It is possible that this publication may contain
references to, or information about Cambium products (machines and programs), programming, or services that
are not announced in your country. Such references or information must not be construed to mean that Cambium
intends to announce such Cambium products, programming, or services in your country.
Copyrights
This document, Cambium products, and 3rd Party Software products described in this document may include or
describe copyrighted Cambium and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Cambium, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to
copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any
copyrighted material of Cambium, its licensors, or the 3rd Party software supplied material contained in the
Cambium products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modified in any manner without the express written permission of Cambium. Furthermore, the
purchase of Cambium products shall not be deemed to grant either directly or by implication, estoppel, or
otherwise, any license under the copyrights, patents or patent applications of Cambium or other 3rd Party supplied
software, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale
of a product.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Cambium.
License Agreements
The software described in this document is the property of Cambium and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement. See Legal
Notices and License Agreements.
© 2015 Cambium Networks, Inc. All Rights Reserved.

Table of Contents
Accuracy ...................................................................................................................................... 2
Copyrights ................................................................................................................................... 2
Restrictions ................................................................................................................................. 2
License Agreements .................................................................................................................... 2
1 About This Administration Guide ................................................................. 15
1.1 New in This Issue........................................................................................................... 15
1.2 Chapters ........................................................................................................................ 16
1.3 References to Other WM Documents .......................................................................... 17
1.4 Links to Other Important Documents ........................................................................... 18
1.5 Feedback on This Guide ................................................................................................ 19
1.6 References to Starting and Stopping the WM Service ................................................. 19
2 Management of the WM Server Device ........................................................ 21
2.1 Server Requirements .................................................................................................... 21
2.1.1 Server Hardware Requirements ............................................................................................ 21
2.1.2 Server Software Requirements ............................................................................................. 22
2.2 Client Requirements ..................................................................................................... 23
2.2.1 Client Hardware Requirements ............................................................................................. 23
2.2.2 Client Software Requirements .............................................................................................. 23
2.3 Local Setup for Launches of Included Tools ................................................................. 24
2.4 Port Management ......................................................................................................... 25
2.5 Network Interface Management .................................................................................. 27
2.6 Memory Management .................................................................................................. 28
2.7 IP Address Change for the WM Server ......................................................................... 29
2.7.1 Address Change for the Server in Linux ................................................................................ 29
2.7.2 Address Change for the Server in Windows .......................................................................... 30
2.8 Use of an Uninterruptible Power Supply ...................................................................... 30
2.9 Placement of pkg3 Files for Network Element Upgrades ............................................. 30
3 MySQL Database Administration ................................................................... 33
3.1 Changing the Database Authentication in WM ............................................................ 33
3.2 Starting the Database ................................................................................................... 33
3.3 Re-initializing the Database .......................................................................................... 33
3.4 Restoring the WM Default Database Configuration ..................................................... 34
3.5 Backing Up the Entire Database ................................................................................... 34
3.6 Restoring the Entire Database ...................................................................................... 35
3.7 Maintaining the Integrity of the Database ................................................................... 35
3.7.1 Addressing Table Corruption on a Linux Platform ................................................................ 35
3.7.2 Addressing Continuous Growth of Data Files on a Windows Platform................................. 36
3.8 Repairing a Crashed Table ............................................................................................ 37
3.8.1 Repairing a Table in Linux...................................................................................................... 38
3.8.2 Repairing a Table in Windows ............................................................................................... 39
3.9 Tuning the Database Attributes for Optimal Use of Server Resources ........................ 40
4 Network Discovery Setup and Debug........................................................... 43
4.1 Reading Discovery Debug Messages ............................................................................ 43
4.2 Temporarily Disabling Updates to the Physical Map to Speed Up Discovery .............. 44
4.3 Getting Generic Elements Discovered .......................................................................... 45
4.4 Expanding or Shrinking Areas for Presumed Logical Relationships .............................. 45
5 Predefined Information Structures for Device Support ........................ 49
6 Fault Management Configuration .................................................................. 51
6.1 Opening Trap Ports ....................................................................................................... 51
6.2 Enabling Print for Events and Alarms ........................................................................... 51
6.2.1 Enabling Print in Windows .................................................................................................... 52
6.2.2 Enabling Print in Linux ........................................................................................................... 53
6.2.3 Enhancing the Printed Output .............................................................................................. 53
6.3 Configuring Fault Management Parameters ................................................................ 53
7 Performance Management Configuration .................................................. 59
7.1 Managed Objects .......................................................................................................... 59
7.2 Operator-defined Reports ............................................................................................ 62
7.3 Collected Statistics Plot for Poll Failure ........................................................................ 63
8 Security Management Configuration............................................................ 65
8.1 Defining and Managing a Group or a User ................................................................... 65
8.2 Defining and Managing Authorized and Custom View Scopes .................................... 66
8.3 Adding and Managing Operations ................................................................................ 66
8.4 Enabling the Authorized Mode for Security Operations .............................................. 66
8.5 Configuring Security Management Parameters ........................................................... 68
8.6 Configuring Password Complexity ................................................................................ 68
8.7 Enforcing a Password Change Requirement................................................................. 69
8.8 Enforcing One Session per User .................................................................................... 70
8.9 Managing Expiry for User Accounts and Passwords ..................................................... 70
8.10 Restoring a Deleted superuser Account ....................................................................... 70
9 Offline Physical Map Setup .............................................................................. 73
9.1 Deploying GeoServer .................................................................................................... 73
9.2 Creating Map Layers ..................................................................................................... 74
9.2.1 Creating a layer from an image file ....................................................................................... 74
9.2.2 Creating a layer from a shape file ......................................................................................... 76
9.3 Pre-caching the Map Images ........................................................................................ 81
9.4 Changing the Maximum Zoom Level ............................................................................ 82
10 Optimization of WM Server Performance............................................... 83
10.1 Optimizing MySQL Database Performance .................................................................. 83
10.2 Locking and Terminating Idle Client Sessions ............................................................... 84
11 User Scripts Setup ........................................................................................... 85
12 Management of WM Server Logs ................................................................ 87
13 WM Software Upgrades and Downgrades .............................................. 89
13.1 WM Upgrade................................................................................................................. 89
13.2 Migration of Operator Data Through WM Upgrade Plus OS Upgrade ......................... 98
13.3 WM Downgrade .......................................................................................................... 100
14 WM Software and Feature Licensing ..................................................... 105
14.1 License Types .............................................................................................................. 105
14.2 Calculation of the Number of Nodes to be Licensed .................................................. 105
14.3 Notifications of License Limits .................................................................................... 106
14.4 WM License Replacement .......................................................................................... 106
14.5 Recovery From Forgotten Password for the License Manager Administrator Tool ... 106
14.6 Deployment of Redundant License Manager Servers ................................................ 108
14.6.1 Purpose of Redundancy .................................................................................................. 108
14.6.2 Configuration of License Key Files for Redundancy ........................................................ 108
14.6.3 Redundancy Deployment Process .................................................................................. 109
14.7 Workaround for a License Server Failure ................................................................... 112
14.7.1 Failure or Reboot of a License Manager Server .............................................................. 112
14.7.2 Change in the IP Address of a License Manager Server.................................................. 112
14.7.3 Server Restarts in LM Redundancy ................................................................................. 112
15 WM Administrator Tool for Server Administration ......................... 113
15.1 Using the WM Server Panel ........................................................................................ 113
15.2 Configuring the BAM Panel ......................................................................................... 116
15.3 Configuring the Database Panel ................................................................................. 117
15.4 Using the Licensing Panel ........................................................................................... 118
15.5 Configuring the NBI Panel ........................................................................................... 121
15.6 Using the Offline Physical Map Panel ......................................................................... 122
15.7 Configuring the Email Configuration Panel ................................................................ 124
16 MIB Browser Usage...................................................................................... 127
16.1 Invoking the MIB Browser .......................................................................................... 127
16.2 Configuring the MIB Browser ..................................................................................... 128
16.2.1 Setting Common Parameters .......................................................................................... 128
16.2.2 Storing Table Entries in a Serialized File ......................................................................... 131
16.2.3 Storing Table Entries in a Database ................................................................................ 131
16.2.4 Setting MIB Parameters .................................................................................................. 132
16.2.5 Loading MIBs................................................................................................................... 132
16.2.6 Unloading MIBs ............................................................................................................... 134
16.2.7 Performing SNMP Operations ........................................................................................ 135
16.2.8 Setting SNMP Table Options ........................................................................................... 138
16.3 Interpreting MIB Browser Error Messages ................................................................. 141
16.4 FAQs ............................................................................................................................ 146
Legal Notices and License Agreements ............................................................ 149
CAMBIUM NETWORKS, LTD END USER LICENSE AGREEMENT............................................... 149
CAMBIUM PUBLICLY AVAILABLE SOFTWARE LEGAL NOTICES AND END USER LICENSE
AGREEMENTS FOR PUBLICLY AVAILABLE SOFTWARE ............................................................ 154
Software Included by Cambium.............................................................................................. 155
Packages That Use Apache License Version 2.0 ..................................................................... 159
THIRD PARTY PUBLICLY AVAILABLE SOFTWARE LEGAL NOTICES AND END USER LICENSE
AGREEMENTS FOR PUBLICLY AVAILABLE SOFTWARE ............................................................ 163
Software Included by Commercial Third Party Software ....................................................... 164
Packages That Use GNU Lesser General Public License Version 2.1 ...................................... 170
Packages That Use Apache Software License Version 1.1 ...................................................... 178
Abbreviations ........................................................................................................... 181
Technical Support ................................................................................................... 183
Running the Customer Support Tool ...................................................................................... 183
Options for Running the Support Tool.................................................................................... 183
Contacting Support Representatives ...................................................................................... 184
List of Figures
Figure 1: Security Administration Tree – Group Operations ...................................................................... 67
Figure 2: Command option to upload an individual license file to License Manager ................................. 96
Figure 3: Licensing Configuration panel in License Manager web server ................................................. 110
Figure 4: Licensing Status panel in License Manager web server ............................................................. 111
Figure 5: WM Server panel of WM Administrator Tool launched from executable ................................. 114
Figure 6: BAM panel of WM Administrator Tool ...................................................................................... 116
Figure 7: Database panel of WM Administrator Tool ............................................................................... 117
Figure 8: Licensing panel of WM Administrator Tool ............................................................................... 118
Figure 9: Upload License File dialog .......................................................................................................... 119
Figure 10: License Manager Status display window ................................................................................. 120
Figure 11: NBI panel of WM Administrator Tool, active SNMP V3 settings ............................................. 121
Figure 12: NBI panel of WM Administrator Tool, active SNMP V1/V2 settings ....................................... 122
Figure 13: Offline Physical Map panel of WM Administrator Tool ........................................................... 123
Figure 14: Email Configuration panel of WM Administrator Tool ............................................................ 125
Figure 15: MIB Browser main GUI............................................................................................................. 127
Figure 16: MibBrowser Settings dialog ..................................................................................................... 129
Figure 17: Load a MIB File Panel—MIB Settings Tab ................................................................................ 133
Figure 18: SNMP Table .............................................................................................................................. 138
Figure 19: SNMP Table Settings Panel ...................................................................................................... 139
List of Tables
Table 1: Hardware requirements for the WM server ................................................................................. 21
Table 2: Software requirements for the WM server .................................................................................. 22
Table 3: Hardware requirements for the WM client application ............................................................... 23
Table 4: Software requirements for the WM client application ................................................................. 23
Table 5: Ports that must be open ............................................................................................................... 25
Table 6: Structured information resources per general device type .......................................................... 49
Table 7: Fault Management configurable fields ......................................................................................... 54
Table 8: Performance Management configurable fields ............................................................................ 59
Table 9: Recommended MySQL parameter values..................................................................................... 83
Table 10: Log files present by default ......................................................................................................... 87
Table 11: MibBrowser General tab fields ................................................................................................. 129
Table 12: Security parameters for accessing SNMPv3 agents .................................................................. 130
Table 13: MibBrowser Error Messages ..................................................................................................... 141
List of Procedures
Procedure 1: To set up Windows to allow all Administrators to launch WM tools ................................... 24
Procedure 2: To configure server-client communications after installation .............................................. 26
Procedure 3: To assign a particular IP address to the WM server.............................................................. 27
Procedure 4: To set WM server as the first connection that Windows network services will access ....... 28
Procedure 5: To configure memory and daily backup ................................................................................ 28
Procedure 6: To change the IP address of the physical standalone server in Linux ................................... 29
Procedure 7: To change the IP address of the physical standalone server in Windows ............................ 30
Procedure 8: To start the MySQL daemon as a server on Linux ................................................................. 33
Procedure 9: To re-initialize the MySQL database ..................................................................................... 33
Procedure 10: To restore the installed WM database configuration ......................................................... 34
Procedure 11: To detect and repair corrupted MyISAM database tables .................................................. 36
Procedure 12: To reclaim hard drive space from burgeoning database files ............................................. 36
Procedure 13: To observe in the logs that a MySQL database table has become corrupted .................... 37
Procedure 14: To confirm in Linux that the table needs repair .................................................................. 38
Procedure 15: To repair a MySQL table in a Linux platform ....................................................................... 38
Procedure 16: To confirm in Windows that the table needs repair ........................................................... 39
Procedure 17: To repair a MySQL table in a Windows platform ................................................................ 39
Procedure 18: To adjust database values in Linux for optimal server performance .................................. 40
Procedure 19: To adjust database values in Windows for optimal server performance ........................... 40
Procedure 20: To temporarily disable updates to the physical map display .............................................. 44
Procedure 21: To display and store failed statistics polls ........................................................................... 63
Procedure 22: To enable authorization support......................................................................................... 66
Procedure 23: To add password complexity............................................................................................... 68
Procedure 24: To enforce the password change requirement for first-time users .................................... 69
Procedure 25: To prohibit multiple simultaneous sessions by any of the users ........................................ 70
Procedure 26: To restore the superuser account and the security tool cache .......................................... 70
Procedure 27: To deploy GeoServer ........................................................................................................... 73
Procedure 28: To create a layer from one image ....................................................................................... 74
Procedure 29: To create a data store for GeoServer workspace images ................................................... 74
Procedure 30: To verify that GeoServer connects to the image data store ............................................... 75
Procedure 31: To add an image to an existing layer................................................................................... 75
Procedure 32: To download a shape file .................................................................................................... 76
Procedure 33: To convert a .osm.pbf or .osm.bz2 file to .osm................................................................... 76
Procedure 34: To convert a .osm file to .shp using QGIS............................................................................ 77
Procedure 35: To create a data store for GeoServer workspace shapes ................................................... 78
Procedure 36: To configure the new layer ................................................................................................. 80
Procedure 37: To verify the new layer configuration ................................................................................. 80
Procedure 38: To pre-cache all tiles for all levels of zoom ......................................................................... 81
Procedure 39: To set a different max zoom level for the offline map........................................................ 82
Procedure 40: To optimize the MySQL database resources for WM ......................................................... 83
Procedure 41: To establish session idle time limits .................................................................................... 84
Procedure 42: To upgrade WM................................................................................................................... 89
Procedure 43: To migrate operator data in upgrade of WM plus the OS .................................................. 98
Procedure 44: To reset the License Manager Administrator Tool password ........................................... 107
Procedure 45: To deploy redundant license servers ................................................................................ 109
Procedure 46: To configure WM for offline physical map images ........................................................... 123
Procedure 47: To reconfigure offline physical map images in WM.......................................................... 124
Procedure 48: To configure server and admin email settings .................................................................. 125
Procedure 49: To invoke the MIB Browser ............................................................................................... 127
WM Release 4.4 and Later Server Administration Guide Issue 2
October 2015
1 About This Administration Guide

important ........... The installation tool for the WM server deposits an issue of the
Cambium Wireless Manager Release 4.2 and Later Server Administration Guide and
the Cambium Wireless Manager Release 4.2 and Later User Guide into the
...server/help directory on the WM server. These documents are
placeholders.
Immediately after your server installation is completed, visit

http://www.cambiumnetworks.com/support/management-tools/wireless-manager/.
If a later iteration of either or both of these documents is present there, download it
and delete the superseded book. Throughout the life of the current release, this web
site will always contain the latest supporting documents. Whenever the issue number
available at this site is greater than what you currently have, you need to download
the replacement.
All information pertaining to the WM server file system is presented for the server administrator
across the following documents:
 Cambium Wireless Manager Quick Start Guide. This guide documents
− the system requirements
− the procedure for a fresh installation
− client device setup
− SNMP broadcast toggling
− starting and stopping the WM service
− launching the client
− setting up, monitoring, and troubleshooting initial discovery
− licensing WM software and the physical map
 Cambium Wireless Manager Server Administration Guide. This guide documents
− starting and stopping the WM service
− port usage
− database administration
− server-side adjustments for
 discovery
 fault management
 performance management
 security management
 the offline physical map
− server logs
− licensing and upgrading WM software
− backing up the system
− using the MIB browser
1.1 New in This Issue

New in Wireless Manager 4.4:
15
Issue 2 WM Release 4.4 and Later Server Administration Guide
October 2015
 PTP 650 v01-40 Support

 ePMP 2.4 Support
 Canopy 13.4 Support
 Initial PMP 450i Support
 Bitrock Migration
 Ability to display device name in alarm view
 Ability to configure alarm levels for status poll failures
 Improve Dashboard API Performance
 WMNUT Improvements
 ePMP 2.5 Support
 PTP 700 Support
1.2 Chapters
This server administration guide is organized as follows:
This chapter describes the scope of this guide and provides

references and links to other important
documents that support WM and network
elements.
Chapter 2, Management of the WM Server Device lists the ports that must be open in the firewall
settings on the server device and describes the
configuration that the server requires for
executing tools, for using the proper network
interface card, and for adapting to a new IP
address. It also emphasizes the importance of
deploying an uninterruptible power supply and
provides the location for placement of device
firmware package files.
Chapter 3, MySQL Database Administration describes how to configure, start, and initialize
the database and how to restore the WM
configuration and back up the database.
Chapter 4, Network Discovery Setup and Debug describes how to make server-side adjustments
to the way WM is configured for Discovery and
where to find Discovery-related debug messages.
Chapter 5, Predefined Information Structures for Device Support lists the structured information resources for
support devices included in the server file system.
Chapter 6, Fault Management Configuration describes server-side adjustments to how WM

is configured for Fault Management.
Chapter 7, Performance Management Configuration describes server-side adjustments to how WM

is configured for Performance Management.
16
October 2015
Chapter 8, Security Management Configuration describes server-side adjustments to how WM

is configured for Security Management. This
discussion includes how groups and users,
authorized and custom view, and operations are
configured for security, how to set the
authorization for security administration,
configure certain security parameters, and set
when accounts and passwords are to expire.
Chapter 9, Offline Physical Map Setup describes how to install and configure GeoServer,
create map layers from images, and prepare
layers for efficient panning and zooming.
Chapter 10, Optimization of WM Server Performance provides specific MySQL database configuration
parameter values that are recommended for all
operators and strongly recommended for
operators who manage large networks, and also
describes how to limit idle client time by
configuring automatic lockups and terminations
for sessions that are idle too long.
Chapter 11, User Scripts Setup provides the proper path and mode for mounting
operator-defined scripts on the server.
Chapter 12, Management of WM Server Logs describes how to manage logs that the server
logs.
Chapter 13, WM Software Upgrades and Downgrades describes how to upgrade WM to the next
release.
Chapter 14, WM Software and Feature Licensing describes the licensing and license management
schemes that the current release supports:
license types (WM server, physical maps, and
node packs), how to calculate the needed
quantities of these, and how the WM client
cautions the user of approaching license
deficiencies. This chapter also includes
information on how to replace the server license.
Chapter 15, WM Administrator Tool for Server Administration shows default values for fields of the tool panels
and describes how to set up WM to connect to
GeoServer and retrieve map images from it.
Chapter 16, MIB Browser Usage describes how to invoke, configure, and
troubleshoot the embedded MIB browser.
1.3 References to Other WM Documents

If you are a client administrator or user, use the Cambium Wireless Manager User Guide for the
current release.
For high-level descriptions of new features included in the initial distribution of the current release,
or for all disclosures about features that this distribution supports, see the Cambium
Wireless Manager Release Notes for the current release.
17
October 2015
For documentation support with BAM integration, see the following documentation:
 Cambium Wireless Manager Quick Start Guide
 Procedure 42: To upgrade WM
 Cambium Wireless Manager User Guide
1.4 Links to Other Important Documents

For links to important documents about supported network elements, visit
https://support.cambiumnetworks.com/files. After logging into the Support Center at this address,
you will have access to the following types of documents:
 PTP device and PTP LINKPlanner user guides and release notes
 PMP device user guides, release notes, and MIBs
 a wide range of PMP 320 device documents
 CMM user guides and release notes
For links to important documents about management tools, visit the following web pages:
 Wireless Manager guides, release notes, and service pack notes at
http://www.cambiumnetworks.com/support/management-tools/wireless-manager/
 Cambium Network Updater Tool (CNUT) on-line help file and release notes at
http://www.cambiumnetworks.com/support/management-tools/cnut/
For links to network element features and specifications, visit the following web pages.
 Cambium PTP:
− the portfolio at http://www.cambiumnetworks.com/products/ptp
− PTP 100 at http://www.cambiumnetworks.com/products/ptp/ptp-100
− PTP 500 athttp://www.cambiumnetworks.com/products/ptp/ptp-500
− Cambium Networks LINKPlanner at
http://www.cambiumnetworks.com/products/planning-tools/link-planner
 Cambium ePMP 1000:
 the portfolio at http://www.cambiumnetworks.com/products/access/epmp-1000/
 Cambium PMP:
− the portfolio at http://www.cambiumnetworks.com/products/pmp
− PMP 100 at http://www.cambiumnetworks.com/products/pmp/pmp-100/
18
October 2015
 For declarations of conformity for individual network elements in their various frequency
band ranges, see
− http://www.cambiumnetworks.com/support/ec-doc for EC conformity
− http://www.cambiumnetworks.com/support/weee-compliance for WEEE compliance
1.5 Feedback on This Guide

We encourage feedback on our documentation, including
 opinions on the structure or content of the documents.
 a notification to us about a deficiency in accuracy or completeness.
 any other comments you have.
Please call with your feedback to the appropriate phone number from the list at
http://www.cambiumnetworks.com/support/contact-support.
1.6 References to Starting and Stopping the WM

Service
Some procedures in this guide (such as backup, restore, and upgrade) require start, stop, or restart of
the service. You also may also be asked to restart services as part of troubleshooting efforts under
the guidance of technical support staff. When you need to restart services, use the WM
Administrator Tool with its Java interface as described under Using the WM Server Panel.
19
October 2015
2 Management of the WM Server Device

This chapter documents certain setup and configuration steps that are required for proper operation
of the general functions of the WM server. Chapters that follow address requirements for specific
features of WM.
2.1 Server Requirements
2.1.1 Server Hardware Requirements

The WM server requires the following hardware characteristics for its proper operation.
Table 1: Hardware requirements for the WM server
Requirement type With ≤ 100 nodes With > 100 nodes Virtual machine
hardware class server, not desktop server, not desktop server, not desktop
RAM 4 GB 8 GB 8 GB for ≤ 100 nodes

12 GB for more
processor dual-core ≥ 2 GHz quad-core ≥ 2 GHz 2 GHz

dual-core for ≤ 100 nodes
quad-core for more
storage RAID 1 RAID 5, ≥ RAID 1 for ≤ 100 nodes

10,000-rpm drives
uninterruptible power highly recommended highly recommended highly recommended

supply (UPS)
scheme for graceful highly recommended highly recommended highly recommended

shutdown during
power outage
21
October 2015
2.1.2 Server Software Requirements

The WM server requires the following software versions or configurations for its proper operation.
Table 2: Software requirements for the WM server
Requirement type Version

1 2
Operating system Windows Server 2012 R2 Standard Edition
Windows Server 2008 R2
Red Hat Enterprise Linux 5.x 32-bit (not 64-bit) ES (not AS)
Red Hat Enterprise Linux 6.x 32-bit (not 64-bit) ES (not AS)
CentOS 5.x 32-bit (not 64-bit)
CentOS 6.x 32-bit (not 64-bit)
Firewall See Port Management.
Java Installed as part of the WM distribution
database MySQL Server Version 5.1, optionally installed by the WM

distribution tool
licensing License Manager, installed by the WM distribution tool
dos2unix package WM on Cent-OS requires that the dos2unix package is

installed before WM in installed. If it is not, then License
Manager, web server, and WM server services do not start;
and the scripts in the WM server are not properly read.
Special considerations for Certain packages are specifically considered problematic for
software installations a WM platform:
 XEN virtualization software, in any WM
configuration
 cluster packages, where the High Availability (HA)
configuration is implemented.
if virtualization is installed VMware vSphere. See

http://www.vmware.com/support/pubs/vsphere-esxi-
vcenter-server-pubs.html
NOTES:
1. Cambium Technical Support cannot help a network operator customize an OS, for
example obtain special Linux library packages, to make WM work on an unsupported
version.
2. Although this is a 64-bit OS, it detects that WM is a 32-bit application and runs WM in
a 32-bit emulation environment.
22
October 2015
2.2 Client Requirements
2.2.1 Client Hardware Requirements

The WM client requires the following hardware characteristics for its proper operation.
Table 3: Hardware requirements for the WM client application
Requirement Supported
type
hardware class any modern desktop or laptop
storage 15 MB
link speed 1 Mbps
screen resolution 1024 x 768
2.2.2 Client Software Requirements

The WM client requires the following software versions for its proper operation.
Table 4: Software requirements for the WM client application
Requirement Software and version

type
1
Operating system Windows 7 Professional, 32-bit
Windows Server 2008 R2 Enterprise
Red Hat Enterprise Linux 5.5 ES
Red Hat Enterprise Linux 6.x ES
Browser Mozilla Firefox 3, 32-bit, if the client is

on a Linux OS device
Internet Explorer 6, 7, or 8; 32-bit, if
the client is on a Windows OS device
2
Java JRE 1.6.0_10 or later
23
October 2015
NOTES:
1. MacOS is not supported. The following additional OSs
are expected to work but have not been tested with the
client application:
 Windows versions other than those shown above,
assuming they are 32-bit
 CentOS 5.5 or 6.x, 32-bit
2. Use of an earlier JRE version with WM Release 4.0 SP 3
or later can result in an OutOfMemory error.
2.3 Local Setup for Launches of Included Tools

By default, Windows 2008 imposes a security scheme that limits tool executions to the default
Administrator account, the Built-in account for administering the
computer/domain. It does not extend this privilege to other accounts that have been configured
in the BuiltinAdministrators group. To extend it to all of them, the following workaround sets up
the local Windows device to prompt those administrators, upon an attempt to launch a tool, for
whether to allow Java the write access required for the execution. This procedure is required once,
except if the parameters that it sets become reconfigured.
Procedure 1: To set up Windows to allow all Administrators to launch WM tools

1. Log into the server device as the Administrator with administrative privileges
(the Built-in account for administering the computer/domain).
2. Navigate to C:\Cambium\WM\jre\bin.
3. Right-click the file java.exe and select Properties.
4. In the resulting dialog, click the Compatibility tab.
5. Near the bottom of this dialog, click the Change setting for all users button.
6. Near the bottom of the resulting dialog, check the check box of the
Run this program as an administrator option.
7. Click OK to confirm and dismiss this latter dialog.
8. Click OK to dismiss the original dialog.
Now when any member of the BuiltinAdministrators group in the Active Directory Domain Services
area attempts to launch a tool from the C:\Cambium\WM\jre\bin folder (either double-clicks
the tool name or right-clicks it and selects Open), Windows will prompt that user for whether to allow
the program (Java) to make changes to the computer. The user should click the Yes button in
response to this prompt.
Other sections of this administration guide provide various procedures that invoke such tools. These
sections include but may not be limited to
 Re-initializing the Database
 Defining and Managing a Group or a User
 Restoring a Deleted superuser Account
 Invoking the MIB Browser
 Running the Tool from the Server
24
October 2015
2.4 Port Management

The following table shows a list of the specific port assignments in use by Wireless Manager
components. Each must be open in the firewall, if a firewall is implemented.
Table 5: Ports that must be open
Server Port Usage

1
25 Outbound connection to SMTP server for email configuration.
80 Outbound connection to BAM server to launch its interface.
161 Inbound UDP for the northbound interface (NBI).
161 Outbound UDP for device SNMP queries and configurations.
162 Inbound UDP for SNMP traps from devices.
1234 Inbound UDP for APs to request authentications from BAM.
1476 Configuration server.
1482 Socket server.
2000 Network management back-end server.
2501 To turn the SM Autoupdate feature on or off in APs.
WM 3306 Queries to the MySQL database.
6900 Inbound TCP for TFTP connections in the firmware upgrade process.
Outbound UDP for SNMP response over the northbound interface

8003
(NBI).
TCP connections by Tomcat and web server for access to device

8009 2
management web pages.
8090 Inbound data from the BAM server.
9090 Inbound TCP for the web server.
NMS Socket for TCP communication between the WM server and

32900 3
WM client.
NMS FE Secondary for TCP communication between the WM server

33100 4
and WM client.
61001 Outbound UDP from BAM to APs.

5
27000 WM to request licenses.
License Manager Secure communications between WM and the web server of License
27443 5
Manager.
25
October 2015
Server Port Usage
Optional Oracle Java Naming and Directory Interface (JNDI)

1521
connection pool via Tomcat.
GeoServer
Communications between WM and the web administration interface
8080
of GeoServer.
NOTES:
3. Port number is reconfigurable in .../server/conf/WibbWMSConfiguration.xml.
4. Port number is reconfigurable in .../server/Apache/Tomcat/conf/server.xml.
5. Must be configured in .../server/conf/transportProvider.conf with WM
server stopped after WM installation.
6. Must be configured in .../server/conf/serverparameters.conf with WM server
stopped after WM installation.
7. Port number is reconfigurable in .../server/conf/licensing.xml.
As indicated in Note 3 and Note 4 above, the NMS Socket port and NMS FE Secondary port must be
configured after WM has been installed and stopped. To do so, perform the following steps.
Procedure 2: To configure server-client communications after installation

1. If the WM server is running, launch the WM Administrator tool.
2. Stop the WM server, as described under Using the WM Server Panel.
3. Open the file .../server/conf/transportProvider.conf for editing.
4. Find the tag <PORT_TO_LISTEN>.
5. Change its value from 0 to that of any available TCP port (for example, 32900).
26
October 2015
6. Save and close the file.

7. Open the file .../server/conf/serverparameters.conf for editing.
8. Scroll to the bottom of the file.
9. Insert a line that has the following text:
NMS_FE_SECONDARY_PORT 33100
where 3100 is an example available TCP port.

11. Start the WM server, as described under Using the WM Server Panel.
2.5 Network Interface Management

The licenses that Cambium Networks provides depend on the particular network interface card (NIC)
that your License Manager server is using. If you add or remove a NIC on your License Manager server
device, your WM license may cease to be valid. If this occurs, contact Cambium Networks to request
a replacement license.
Valid licensing of WM requires that WM uses the network interface named eth0. Although this may
not be an issue for most operators whose WM server is on Version 5.x of Linux or CentOS, it is an
issue for those whose server is on 6.x of Linux or CentOS. For example, in CentOS Version 6.5, by
default the interface names are em1, em2, ...p3p1, p3p2, etc. To provide an interface for WM in an
OS that does not currently have an eth0
1. visit http://www.slashroot.in/how-convert-em0-eth0-centos-6-and-rhel-6.
2. perform the full procedure that this web site provides.
The existence of multiple NICs on your WM server device can populate the other (incorrect) NIC
IP address into the Java Web Start file. To fix and prevent this, perform the following procedure(s).
Procedure 3: To assign a particular IP address to the WM server

1. Open the WM Administrator Tool. (See WM Administrator Tool for Server Administration).
2. In the WM Server panel of the WM Administrator Tool, click the Stop WM Server button.
3. In the WM server file system, navigate to the directory
wm_server_install_directory/server/bin in Linux or the folder
C:\Cambium\WM\server\bin in Windows.
4. Open the file startWM.sh in Linux (or startWM.bat in Windows) for editing.
5. Find the string com.adventnet.nms.startnms.NmsMainBE.
27
October 2015
6. Immediately before this string, add

-Dnms.server.host="IP_Address_you_want_to use_for_WM_server"
followed by a space.
EXAMPLE: The finished line looks like this:
$JAVA_HOME/bin/java -cp $CLASS_PATH -Dcatalina.home=$TOMCAT_HOME
-Dmysql.home=$MYSQL_HOME -Dwebserver.port=$WEBSERVER_PORT
-Dresource_check="$WEBSERVER_PORT,$WEBCONTAINER_PORT,$TOMCAT_SHUTDOWNPORT"
-Dwebserver.rootdir=$WEBSERVER_HOME -Djava.rmi.server.codebase="$CODEBASE_LIST"
-Xmx$MAX_HEAP_SIZE_STR -Dcom.sun.management.jmxremote.port=16000
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.snmp.interface=`hostname`
-Dcom.sun.management.snmp.acl=false -Dcom.sun.management.snmp.port=16500
-Dnms.server.host="IP_Address_you_want_to_use_for_WM_server"
com.adventnet.nms.startnms.NmsMainBE NMS_BE_PORT 2000 ROOT_DIR $NMS_HOME
NATIVE_PING false $*
8. In the WM Server panel of the WM Administrator Tool, click the Start WM Server button.
Procedure 4: To set WM server as the first connection that Windows network

services will access
1. Open the Control Panel.
2. In the left panel, click Switch to Classic View.
3. In the right panel, double-click Network Connections.
4. From the main menu of the Network Connections window, select
AdvancedAdvanced Settings.
5. In the Adapters and Bindings tab of the Advanced Settings window, use the up or down
arrow to ensure that the connection of the WM server NIC is higher in the list than the other
NIC.
2.6 Memory Management

Use the following steps to increase server memory and keep it efficiently used.
Procedure 5: To configure memory and daily backup

1. Stop the WM server.
2. Open the Windows folder C:\Cambium\WM\server\bin\ or the Linux directory
\usr\local\cambium\wm\server\bin\.
3. Open the file startWM.bat or startWM.sh for editing.
4. Search for the following text in the file: set MAX_HEAP_SIZE_MB=1024.
(Here, 1024 represents, in Megabytes, the memory WM is using.)
5. Increase this value to 1280, 1536 or 1756.
7. Start the WM server.
RESULT: The server memory has been reconfigured.
8. Open the Windows folder C:\Cambium\WM\server\conf or the Linux directory
\usr\local\cambium\wm\server\conf.
28
October 2015
9. Open the file BackUp.conf for editing.

10. Search for the following text in the file:
BACKUP className="jdbc.CustomBackupDB"
11. If the DAILY attribute in the same line is set to true, change it to false.
12. Restart the WM server.
RESULT: Automatic backups have been suppressed.
2.7 IP Address Change for the WM Server

This section provides a set of instructions specific to the operating system of the WM server device.
2.7.1 Address Change for the Server in Linux

On a Linux platform, where the WM server IP address differs from that of its previous deployment,
some further action is required:
 If the IP address is dynamic, then a reboot of the server device allows the server to update
its information.
 If the IP address is static, then the /etc/hosts file must be updated to contain a valid
mapping of its IP address to its host name (localhost.localdomain is not valid).
Procedure 6: To change the IP address of the physical standalone server in Linux

3. In the left panel of the WM Administrator Tool, click Licensing.
4. In the Licensing panel, click the Stop LM button.
5. Use the method appropriate to your Linux version to change the IP address of the physical
server.
6. At the Linux OS prompt, enter service network restart.
7. In the Hostname / IP field of the Licensing panel in the WM Administrator Tool, replace the
host name or IP address with the address configured in Step 5 above.
8. Click the Save Configuration button.
9. Click the Restart LM button.
10. Click the License Status button.
11. Check the system response to verify that License Manager is running properly.
12. If the license was not retrieved, return to Step 7 of this procedure and enter the correct new
IP address.
13. In the left panel of the WM Administrator Tool, click WM Server.
14. In the WM Server panel, click the Start WM Server button.
29
October 2015
2.7.2 Address Change for the Server in Windows

Procedure 7: To change the IP address of the physical standalone server in Windows
3. In the left panel of the WM Administrator Tool, click Licensing.
4. In the Licensing panel, click the Stop LM button.
5. Use the method appropriate to your Windows version to change the IP address of the
physical server.
6. In the Hostname / IP field of the Licensing panel in the WM Administrator Tool, replace the
host name or IP address with the address configured in Step 5 above.
8. Click the Restart LM button.
9. Click the License Status button.
10. Check the system response to verify that License Manager is running properly.
11. If the license was not retrieved, return to Step 6 of this procedure and enter the correct new
IP address.
12. In the left panel of the WM Administrator Tool, click WM Server.
13. In the WM Server panel, click the Start WM Server button.
2.8 Use of an Uninterruptible Power Supply

As with any software that keeps a database, an interruption of power to the host device of the
software can result in corruption of the database that renders its contents irretrievable or useless,
because the software cannot close the database in proper sequence. Historical data about devices
that WM will continue to manage is lost. To keep the data safer from corruption, an operator can
deploy any of the following:
 the WM High Availability feature with database redundancy (see Cambium High Availability
for Wireless Manager Server on a Linux Platform Setup Guide)
 operator-managed database redundancy on a Windows platform
 an uninterruptible power supply (UPS)
A UPS device is recommended for at least minimal protection.
2.9 Placement of pkg3 Files for Network Element

Upgrades
Place and keep in the .../server/Tftp directory of the server file system all .pkg3 files that
need to be available to the client application. These will be automatically loaded for possible
selection from Package Manager by the authorized client user. In that utility, the client
 is not capable of browsing in the server file system.
30
October 2015
 may browse the client device file system to find and load additional .pkg3 files. The server
will allow those files to be then uploaded into the .../server/Tftp directory so that
they are listed the next time that Package Manager is launched in the client.
Given the two repositories for package files, each has the following potential advantage:
 the files in the .../server/Tftp directory of the server are always automatically loaded
into Package Manager selection, regardless of any problems the operator may experience
with the Add operation in that utility.
 the files selected in the client from anywhere in the client file system are available for
loading regardless of the any networking constraints or conditions that would inhibit
downloads from the server to the client.
31
October 2015
3 MySQL Database Administration

This chapter explains how to configure Wireless Manager to support the MySQL database.
3.1 Changing the Database Authentication in WM

If the database user name and password in MySQL are ever changed (for example, through the
command-line interface to MySQL Server), then you must make the corresponding change(s) in the
Database panel of the WM Administrator Tool. See Configuring the Database Panel. These
parameters can be edited, but ultimately must match the username and password configured in the
database itself. Edits in the Database panel and corresponding changes via the command-line
interface to MySQL can also be used to overcome from a forgotten password or user name for the
database.
important ........... Do not make any changes by directly editing the file
/usr/local/cambium/wm/server/conf/database_params.conf in Linux
(or the C:\Cambium\WM\server\conf\database_params.conf in Windows.
WM encrypts the database password that is configured in the WM Administrator Tool. So, the
password string does not appear human readable anywhere in the server file system or the client
application.
3.2 Starting the Database

Wireless Manager starts and initializes the MySQL database before starting Wireless Manager
modules. The MySQL daemon is started when the startWMS script file located in the
C:\Cambium\WM\server\bin folder in Windows is invoked.
In Linux, you need to start the MySQL daemon as a service before starting the Wireless Manager
Server.
Procedure 8: To start the MySQL daemon as a server on Linux

1. Log in as a superuser.
2. Enter $ /etc/rc.d/init.d/mysql start.
3.3 Re-initializing the Database

Perform the following procedure if you have modified any of the default settings and need to re-
initialize the MySQL database. Be aware that this procedure removes all of data that your database is
currently storing. All discovered elements and all of the historical information that is associated with
them will be deleted.
Procedure 9: To re-initialize the MySQL database

1. If the Wireless Manager Server is already started, do a proper shutdown of server.
Do not terminate the process abnormally or abruptly.
2. If Wireless Manager is already installed, run the reinitialize_database script file
located in the /usr/local/cambium/wm/server/bin directory in Linux
33
October 2015
(or the C:\Cambium\WM\server\bin folder in Windows) to clean up the tables in the

database.
3. Make sure that the MySQL process is running.
4. Start the Wireless Manager Server.
Now all of the elements must be rediscovered, and all performance data charts and other historical
information will initially not exist.
3.4 Restoring the WM Default Database Configuration

Perform the following procedure only in the unlikely event that you changed the table structure or
deliberately altered any other SQL settings and now want to revert to the configuration that the WM
installation tool had installed.
Procedure 10: To restore the installed WM database configuration

1. If the Wireless Manager server is already started, do a proper shutdown of server.
Do not terminate the process abnormally or abruptly.
2. Copy the database_params.conf and snmpDatabaseSchema.conf files located in
the /usr/local/cambium/wm/server/conf/MySQL directory in Linux
(or the C:\Cambium\WM\server\conf\MySQL folder in Windows) to the
/usr/local/cambium/wm/server/conf/ directory in Linux
(or the C:\Cambium\WM\server\conf folder in Windows).
3. If using SNMP v3, add database connection information to the
SnmpDefaultProperties.xml file in the
/usr/local/cambium/wm/server/conf directory in Linux
4. In database_params.conf file in the conf directory, specify the machine name where
the database is to run, the user name, and the password for the database.
5. Make sure that the MySQL process is running.
6. Start the Wireless Manager server.
3.5 Backing Up the Entire Database

Good practice is to periodically perform backups of your WM database. This section describes how to
create a backup copy of your entire database (its configuration and its contents) and the entire WM
system in a single operation. No database-only backup is supported, and none would also back up the
essential information that is stored in files in the WM server file system.
important ........... Do not launch a backup while the WM server is running, because this can result in
inconsistency between the contents of the backup and the contents of the database.
note ............. Although the backup utility supports running while the WM service is up, it cannot keep
stride with changes made via the Web Start client while the script is running. Thus, it is
necessary to ensure that no Web Start client session is in progress at any time between
when this script is launched and when it is finished. If a client session is running during the
execution of the script, then a warning message informs the user of the backup operation
and advises that all current requests will be satisfied when the backup is complete.
The only supported backup is available as a click option (System Backup) in the WM Administrator
Tool. See Using the WM Server Panel.
34
October 2015
3.6 Restoring the Entire Database

Restoring the MySQL database is as effective as the database snapshot that was backed up
(see Backing Up the Entire Database above). No database-only backup is supported, and none would
also back up the essential information that is stored in files in the WM server file system.
note ............. To avoid confusion, ensure that no Web Start client session is in progress at any time
between when the restore command option is launched and when it is finished.
The only supported restore is available as a click option (Restore System) in the WM Administrator
Tool. See Using the WM Server Panel. This option restores not only the database snapshot, but also
the essential files from the WM server file system.
3.7 Maintaining the Integrity of the Database

WM is designed to properly populate and read its own updates from the WM database. Any change
in database contents that an operator directly makes is expressly not supported and is likely to result
in a failure of some proportion in the system.
It is strongly recommended that you deploy an uninterruptible power supply (UPS) for the WM server
device. Either a power outage or a hard restart of the device while it is operating can result in
corruption of the database tables and may require reinitializing the database and rediscovering all of
the elements in your network. A UPS can supply enough power to allow WM to properly shut down
and avoid damage to the database.
Despite good practices, over time WM databases will likely require local maintenance. Use one of the
following sections to avoid or correct WM database problems:
 Addressing Table Corruption on a Linux Platform
 Addressing Continuous Growth of Data Files on a Windows Platform
3.7.1 Addressing Table Corruption on a Linux Platform

The default database engine for MySQL on a Linux platform is MyISAM. With this engine, database
tables can become corrupted, regardless of good operator practices. Unexpected errors such as the
following may signal that this has occurred:
Table './WMSDB/WMS_CUSTOMUSERPROPS' is marked as crashed
and should be repaired
Periodically search the contents of the file .../server/logs/stderr*.txt for the presence
of errors like this. When these are present, use one or more of the following procedures to find the
corrupted table(s) and make appropriate repairs:
 Review the descriptions of the tools and procedures:
http://www.databasejournal.com/features/mysql/article.php/3300511/Repairing-Database-
Corruption-in-MySQL.htm.
 Use a process of one or more of the four stages for checking all tables at once and repairing
corrupted tables: http://dev.mysql.com/doc/refman/5.0/en/myisam-repair.html.
note ............. The process above requires stopping the MySQL service. The following does not.
 Use Procedure 11: To detect and repair corrupted MyISAM database tables to detect and
repair corrupted tables without the need to stop the MySQL service.
35
October 2015
Procedure 11: To detect and repair corrupted MyISAM database tables

1. See References to Starting and Stopping the WM Service.
2. Stop the WM service.
3. At your Linux shell prompt, enter one of the following commands:
mysqldump --user=root --password=public --databases wmsdb
>wm_databases.sql
backedupdb1 [backedupdb2 ...backedupdb3] >wm_databases.sql
mysqldump --user=root --password=public –all-databases
>wm_databases.sql
4. Log into MySQL.
5. Review http://dev.mysql.com/doc/refman/5.0/en/check-table.html.
note ............. In Steps 6, 8, and 9, the commands shown are to be executed on each table separately,
not all tables in a single execution. The variable tablename represents the an individual
table, such as wms_customuserprops.
6. To detect table corruption in each table, enter the following command at

the mysql> prompt:
CHECK TABLE tablename;
7. Review http://dev.mysql.com/doc/refman/5.0/en/repair-table.html.
8. To repair a table that was found in the step above to be corrupted, enter the following
command at the mysql> prompt:
REPAIR TABLE tablename;
9. To verify that the repaired table is no longer corrupted, enter the following command
at the mysql> prompt:
CHECK TABLE tablename;
10. If any table remains corrupted, see
http://www.databasejournal.com/features/mysql/article.php/3300511/Repairing-Database-
Corruption-in-MySQL.htm and
http://dev.mysql.com/doc/refman/5.0/en/myisam-repair.html.
11. When all tables have been checked and successfully repaired, start the WM service.
12. Resume normal operations.
3.7.2 Addressing Continuous Growth of Data Files on a

Windows Platform
The default database engine for MySQL on a Windows platform is InnoDB. With this engine, certain
data files continuously grow and eventually use a significant amount of hard drive space. Nothing,
even deleting data from the database, causes their size to shrink or level out. At least annually,
reclaim this storage space by performing Procedure 12: To reclaim hard drive space from burgeoning
database files.
Procedure 12: To reclaim hard drive space from burgeoning database files
1. Review http://dev.mysql.com/doc/refman/5.0/en/innodb-data-log-reconfiguration.html.
36
October 2015
2. Review References to Starting and Stopping the WM Service.

3. Stop the WM service.
4. At your DOS command utility prompt, enter one of the following commands:
>wm_databases.sql
backedupdb1 [backedupdb2 ...backedupdb3] >wm_databases.sql
mysqldump --user=root --password=public –all-databases
>wm_databases.sql
5. Stop the MySQL service.
6. Navigate to the MySQL data folder.
7. Find all existing tablespace files.
note ............. In the default WM implementation, these files are ib_logfile0, ib_logfile1, and
ibdata1.
8. Delete all existing tablespace files from this folder, including the ibdata* and ib_log*
files.
9. If you want to retain copies of the database folders that correspond to the WM database(s)
that you backed up with the mysqldump command in Step 4, copy them to portable media.
10. Delete those database folders from the hard drive.
11. Start the MySQL service.
12. Enter the following command to import the dump file that you created with the mysqldump
command in Step 4:
mysql --user=root --password=public < wm_databases.sql
13. If applications in addition to WM are using the instance of MySQL, use this procedure to
back up, delete, and restore their schemas as well.
14. Start the WM service.
3.8 Repairing a Crashed Table

Both of the following instances are among possible causes of MySQL table corruption:
 an abrupt shutdown of the WM server (upon a sudden power outage, for example)
 insufficient hard disk space.
When corruption in a MySQL database table has occurred, the WM operator may recognize this by
observing that
 the WM service hangs during startup.
 the WM server crashes after startup.
If you observe either of these, perform the following steps.
Procedure 13: To observe in the logs that a MySQL database table has become
corrupted
1. Navigate to the directory /usr/local/cambium/wm/server/logs in Linux or
C:\Cambium\WM\server\logs in Windows.
2. Look in the lo files for any of the following indications of table damage:
37
October 2015
◦ tbl_name.frm is locked against change

◦ Can't find file tbl_name.MYI (Errcode: nnn)
◦ Unexpected end of file
◦ Record file is crashed
◦ Got error nnn from table handler
Use one of the following OS-dependent procedures to repair a corrupted table.
3.8.1 Repairing a Table in Linux

You must repair your tables using myisamchk, a tool provided by MySQL which can usually detect
and fix most problems that occur. To repair the crashed tables, perform the steps given below:
Procedure 14: To confirm in Linux that the table needs repair

3. Log into the Linux system as root.
4. At the Linux command prompt, enter the following command:
service mysqld stop
5. Enter the following command:
myisamchk –e –update-state /var/lib/mysql/WMSDB/*.MYI >/usr/local/db_check.txt
6. If the system returns no output, stop. (No tables are corrupted.)
If the system returns any output, perform Procedure 15: To repair a MySQL table in a Linux
platform.
Procedure 15: To repair a MySQL table in a Linux platform

1. If Procedure 14 has not been performed, perform it now.
myisamchk –r -q –update-state /var/lib/mysql/WMSDB/*.MYI >/usr/local/db_repair.txt
3. Allow time sufficient for tables to be repaired.
4. If the system returns no output, stop.
If the system returns any output, enter the following command:
myisamchk –o -f –update-state /var/lib/mysql/WMSDB/*.MYI >/usr/local/db_repair.txt
service mysqld start
38
October 2015
3.8.2 Repairing a Table in Windows

Procedure 16: To confirm in Windows that the table needs repair
2. In the WM Server panel, click the Stop WM Server button.
3. From the Windows OS menu, open StartRun.
4. In the Open field of the Run dialog, enter services.msc.
5. In the resulting Services dialog, click the Standard tab.
6. Click to highlight the row of the WMMySQL service that is running.
7. Right-click the row and select Stop from the drop-down list of options.
8. Navigate the file system to the folder C:\MySQL Server 5.1\.
9. Right-click the file my.ini and select Open WithNotepad.
10. Select EditFind.
11. In the Find what text box, type default-storage-engine.
12. Click the Find Next button.
13. If the value of this option is not set to INNODB, advance to Step 14.
If the value of this option is set to INNODB, perform the following steps now:
a. Scroll to the bottom of the file.
b. Fix the cursor at the left edge.
c. Type in the following new line of text:
innodb_force_recovery=6
d. In the Services dialog, click to highlight the row of the WMMySQL service.
e. Right-click the row and select Start from the drop-down list of options.
f. If WMMySQL successfully starts, click the Start WM Server button in the WM
Administrator Tool and stop this procedure.
If WMMySQL fails to start, continue.
14. In the Open field of the Run dialog, enter cmd.
15. At the resulting command prompt, enter cd C:\MySQL Server 5.1\bin.
16. Enter myisamchk –e ..\data\wmsdb\*.MYI > db_check.txt.
If the system returns any output, perform Procedure 17: To repair a MySQL table in a
Windows platform.
Procedure 17: To repair a MySQL table in a Windows platform

1. If Procedure 16 has not been performed, perform it now.
2. At the Windows command prompt, enter the following command:
myisamchk –r -q –update-state /var/lib/mysql/WMSDB/*.MYI > db_repair.txt
If the system returns any output, enter the following command:
39
October 2015
myisamchk –o -f –update-state /var/lib/mysql/WMSDB/*.MYI > db_repair.txt

5. In the Services dialog, click to highlight the row of the WMMySQL service.
6. Right-click the row and select Start from the drop-down list of options.
7. Click the Start WM Server button in the WM Administrator Tool.
3.9 Tuning the Database Attributes for Optimal Use of

Server Resources
Dramatic improvement in the use of system resources for the WM server is possible through the
adjustment of the values for certain attribute that control the database. The procedure for adjusting
these values is specific to the operating system.
Procedure 18: To adjust database values in Linux for optimal server performance
3. Log into the Linux system as root.
service mysqld stop
mysqld_safe –key_buffer_size=2G
service mysqld start
Procedure 19: To adjust database values in Windows for optimal server performance
1. In the WM Administrator Tool. (See WM Administrator Tool for Server Administration).
2. In the WM Server panel, click the Stop WM Server button.
3. From the Windows OS menu, open StartRun.
4. In the Open field of the Run dialog, enter services.msc.
5. In the resulting Services dialog, click the Standard tab.
6. Click to highlight the row of the WMMySQL service that is running.
7. Right-click the row and select Stop from the drop-down list of options.
8. Navigate the file system to the folder C:\MySQL Server 5.1\.
9. Right-click the file my.ini and select Open WithNotepad.
10. Select EditFind.
11. In the Find what text box, type innodb_.
12. Click the Find Next button.
13. Reset innodb attributes to the following values:
innodb_flush_log_at_at_trx_commit=2
innodb_log_buffer_size=1M
40
October 2015
1
innodb_buffer_pool_size=2G
innodb_thread_concurrency=8
innodb_file_per_table=1
14. In the Services dialog, click to highlight the row of the WMMySQL service.
15. Right-click the row and select Start from the drop-down list of options.
16. When WMMySQL starts, click the Start WM Server button in the WM Administrator Tool.
1
Or 80% of the size of the physical memory in the machine, except not greater than 3.5G (GB) of user-level memory per
process in a 32-bit system.
41
October 2015
4 Network Discovery Setup and Debug

All changes that are made in the Discovery Configurator tool of the Web Start client are immediately
reflected in the WM server file system. On subsequent startups, the Wireless Manager server reads
the discovery configuration information, even if the database is not reinitialized.
4.1 Reading Discovery Debug Messages

By default, detailed discovery-related debug messages are logged in the
AggregatedDiscoveryLogN.txt file under the /usr/local/cambium/wm/server/logs
directory in Linux (or the C:\Cambium\WM\server\logs folder in Windows). Excerpts from this
log are as follows:
[16 Feb 2012 20:58:00:750] ==================================================

Begin Basic Discovery Of: 10.60.2.35
==================================================
[16 Feb 2012 20:58:00:750] DISCOVERY(10.60.2.35:258): APDiscoveryFilter
attempting discovery of [64 ed 57 20 15 4e] (isDHCP=true)
[16 Feb 2012 20:58:00:765] DISCOVERY using a maximum of 6 threads for Deep
Discovery processing.
[16 Feb 2012 20:58:00:906] DISCOVERY(10.60.2.35:258): Device matched all 7
probes for device type PMP.320.AP (PMP.320.AP(e2.1.x)).
[16 Feb 2012 20:58:00:906] DISCOVERY(10.60.2.35:258): Device has 7 Named
Field(s)
[16 Feb 2012 20:58:02:359] DISCOVERY(10.60.2.35:258): setNameToMac: MO name
is a valid MAC.
[16 Feb 2012 20:58:02:359] DISCOVERY(10.60.2.35:258): validateExistingNode:
No nodes exist with IP: [10.60.2.35] having invalid names.
[16 Feb 2012 20:58:02:453] DISCOVERY(10.60.2.35:258): Successfully added
object 64 ed 57 20 15 4e to database
[16 Feb 2012 20:58:02:468] DISCOVERY using PDU max size 512 during deep
discovery
[16 Feb 2012 20:58:02:468] DISCOVERY(10.60.2.35:258): Creating Deep Discovery
thread for device
[16 Feb 2012 20:58:02:468] DISCOVERY(10.60.2.35:258): APDiscoveryFilter
completed shallow discovery of [64 ed 57 20 15 4e] (isDHCP=true)
[16 Feb 2012 20:58:02:468] ==================================================
End Basic Discovery Of: 10.60.2.35
==================================================
After the Discovery module is initialized, some discovery event messages are available in the client
among the other network event messages. The Discovery Log tab of the Discovery Configurator in the
client provides the full set of discovery messages, as it displays the full contents of the
discoveryLogs.txt server file. However, for running scripts or making selected dumps, you may
find that access to this server file is more convenient.
43
October 2015
In addition, some other Discovery-related messages are logged in the file stdoutN.txt in the same
directory. The following are example messages from this log:
[24 Aug 2010 03:14:11:103] DISCOVERY(10.100.13.92:213): Unable to write to
device while testing Write Community. Device is currently not writeable.
Device's Write Community must be set manually.
[24 Aug 2010 03:41:42:206] DEEPDISCOVERY(10.100.13.73:264): Device is 99%
discovery complete. OIDs timed out: 280
[24 Aug 2010 03:41:43:123] ERRORLOG_POLLMGR(83): Polling Delayed for 5
minutes. Deep Discovery is still running for 4 devices.
4.2 Temporarily Disabling Updates to the Physical Map

to Speed Up Discovery
The physical map may sometimes noticeably lag behind these core systems. This behavior is designed
so that updates in the physical map do not interfere with WM core data gathering and processing. In
typical networks, the delay may be imperceptible but, especially while WM is initially discovering
thousands of devices in a very large network, the physical map may display the updated information
only after minutes or even hours have elapsed.
Temporarily disabling the capability of the physical map to display changes can speed the initial
device discovery process by a factor of 3. For your operations, this may be more advantageous than
experiencing the designed lag. As server administrator, you can do so as follows.
Procedure 20: To temporarily disable updates to the physical map display

See References to Starting and Stopping the WM Service.
2. Navigate to the /usr/local/cambium/wm/server/conf directory in Linux (or the
C:\Cambium\WM\server\conf folder in Windows).
3. Open the file NmsprocessesBE.conf for editing.
4. Find the following lines:
PROCESS com.motorola.wibb.ems.platform.server.starleaf.core.StarleafManager
ARGS INCREMENTAL_DEVICE_UPDATE_ON true FULL_DATA_REFRESH_INTERVAL 86400
5. Set the value of INCREMENTAL_DEVICE_UPDATE_ON to false.

7. Start the server.
See References to Starting and Stopping the WM Service.
8. Notify the client application user that this feature is disabled.
9. After the discovery (or other operation for which you temporarily disabled the feature) is
completed, perform the following steps:
44
October 2015
11. Reopen the NmsprocessesBE.conf file for editing.

12. Reset the value of INCREMENTAL_DEVICE_UPDATE_ON to true.
14. Start the server.
4.3 Getting Generic Elements Discovered

WM discovers as a generic element any SNMP-enabled non-Cambium device for which no valid
device definition template exists. This is distinguished from a Cambium devices, for which a device
definition template is part of the WM software distribution, and from any third-party devices for
which the operator has created a valid device definition template.
However, generic element discovery depends also on the following workaround. Check to see
whether WM has discovered all of the generic devices in the network. For any that WM did not
discover, perform the following steps:
1. Search the client log for the IP address of the device.
2. If an entry is associated with that IP address, note whether the entry indicates that WM
regarded the device as unmanaged.
3. If the entry does, open the file ...server\conf\devices\Generic_Element.xml
for editing.
4. In the Element tag, add disableDHCP="true", as shown in the following edited excerpt:
- <ElementDefinition>
- <Element type="Generic Element" specificType="Generic Element" version="1.0"
treeIcon="images/Unknown_Device_16.png"
mapIcon="Unknown_Device_55.png" vendor="Cambium Networks"
disableDHCP="false" combined="false" relation="false"
enableRelationshipCustomViews="true">
<IncludeTemplate name="templates/PhysicalMapBase.xml" />
<IncludeTemplate name="templates/GenericDashboardBase.xml" />
<ElementGroup name="Devices" displayName="Devices"
treeIcon="images/Devices.png" mapIcon="Devices.png" />
5. Validate the xml content.
6. Write and close the file.
The result is that WM succeeds in discovering all generic elements in your network. However, WM
will use the MAC address as the Name(ID) of any that support and properly implement DHCP.
4.4 Expanding or Shrinking Areas for Presumed

Logical Relationships
Based on comparisons of certain settings in device templates on the server and the geo-locations
defined for devices in your network, the discovery engine in WM presumes logical relationships
among devices and displays these. The presumptions are made whenever both
 the geo-locations lie within template-defined positions (tolerances) that establish four
corners of a rectangle
 the devices are of device types that together have a presumable hierarchical relationship
(would constitute an extended family).
45
October 2015
Per device type, the tolerances can be either the defaults that the device template has defined or
new ones that the server administrator has edited into the device template. Administrators who edit
device templates should keep in mind that the edits apply to all devices of the device type until
further edits are made.
The tolerance that you set is the distance in meters to the northwest, northeast, southwest, and
southeast from an element of this device type. WM will logically link the element to any element
configured by the attribute theirDeviceType in a KinLocation tag, if discovery finds that its geo-
location is within the tolerance (the value of the attribute tolerance_m in the tag). The following are
examples of tag contents in the context of their device specific template names:
- <DefineTemplate name="pmp.ap.location.proximity.logical.family">
- 
<KinLocation kinshipType="parent"
myFieldSource="customUserProperties" myLatitudeName="Device
Latitude" myLongitudeName="Device Longitude"
theirDeviceType="PMP.CMM3" theirFieldSource="customUserProperties"
theirLatitudeName="latitude" theirLongitudeName="longitude"
theirSpecificType="any" tolerance_m="0.0" />
- <DefineTemplate name="cmm.location.proximity.logical.family">
- 
<KinLocation kinshipType="parent"
myFieldSource="customUserProperties" myLatitudeName="latitude"
myLongitudeName="longitude" theirDeviceType="PMP.BHS"
theirFieldSource="customUserProperties" theirLatitudeName="Device
Latitude" theirLongitudeName="Device Longitude"
46
October 2015
- <DefineTemplate
name="ptp.slave.location.proximity.logical.family">
- 
- 
<KinLocation allowSingleChildOnly="true" kinshipType="child"
myFieldSource="customUserProperties" myLatitudeName="latitude"
myLongitudeName="longitude" theirDeviceType="PMP.CMM3"
theirFieldSource="customUserProperties"
- <DefineTemplate name="BHS.location.proximity.logical.family">
- 
<KinLocation allowSingleChildOnly="true" kinshipType="child"
myFieldSource="customUserProperties" myLatitudeName="Device
Latitude" myLongitudeName="Device Longitude"
theirDeviceType="PMP.CMM3" theirFieldSource="customUserProperties"
47
October 2015
5 Predefined Information Structures for

Device Support
The server file system includes structured information resources to support devices as indicated in
Table 6.
Table 6: Structured information resources per general device type
Predefined Structured Path to Resource

Information Resource ...WM/server/
1
Device definition template conf/devices/
Configuration values Default Templates/Configuration

push template Templates/
Configured values report template Default Templates/Report Templates/

2
System report Default Templates/System Reports/
NOTES:
1. These templates configure how WM will recognize the device type during discovery and
how WM should represent the device type in the user interface. The templates in this
directory refer to and pull information from Base files in the templates subdirectory.
2. Unlike the templates, these reports do not support generic elements.
49
October 2015
6 Fault Management Configuration

Fault Management handles error conditions that cause loss of functionality of network resources and
it provides event management, including
 alert generation
 automated actions
 event correlation
 filtering for traps, events, and alerts
 parsing for traps and events
These features enable network operators to detect, isolate, and repair malfunctions in the network
and in its control subsystem.
6.1 Opening Trap Ports

A trap port is the port on which the Wireless Manager Server listens for SNMP notifications. As the
server administrator, you can configure the trap ports in the file
/usr/local/cambium/wm/server/conf/trapport.conf in Linux
(or the C:\Cambium\WM\server\conf\trapport.conf in Windows). The following caveats
apply:
 The specified ports are not associated with a particular Trap Parser, but a general
configuration.
 When no port is specified, traps will not be received at all.
 Multiple ports can be specified using a comma separator, for example 8001,8002.
 Ensure that the specified ports are free.
 The default trap port is 162.
6.2 Enabling Print for Events and Alarms

note ............. See also the section titled "Printing Events" in the Cambium Wireless Manager User
Guide.
By default, the print option for Events and Alarms in Wireless Manager is not configured. To enable
printing, configuration must be done in NmsProcessesBE.conf file in the
(or the C:\Cambium\WM\server\conf folder in Windows). This will allow the current columns
of an alerts or events panel to be sent to a printer that exists in the network of the WM server (and
printing to a file in the file system of, or greater network of, the WM server). The following is an
excerpt from the NmsProcessesBE.conf file:
51
October 2015
#java com.adventnet.nms.eventdb.EventMgr [EVENT_DEBUG true/false]

[SAVE_DIR save_dir] [PRINT_COMMAND print_command]
[CLEAN_EVENT_INTERVAL num_days] [ALERT_DELETE_INTERVAL num_hours]
[EVENT_WINDOW_SIZE logsize] [EVENT_OBJECTS_IN_MEMORY num]
[MAX_EVENT_PROCESS_QUEUE num] [ALERT_OBJECTS_IN_MEMORY num]
[EVENT_JDBC true/false] [ALERT_JDBC true/false]
[ALERT_TO_MANAGEDOBJECT_PROPOGATION max/latest/none]
[GROUP_ALERTS_MODE none/max/latest][ALERTS_USER_PROPERTY
none/latest/append]
The print file argument should be configured based on the value specified for SAVE_DIR parameter.
When you execute the print functionality from the client, WM temporarily stores all the Event/Alarm
details in a file named printfile.tmp in the SAVE_DIR directory. When Print is invoked the
next time, the details in the printfile.tmp are replaced by those corresponding to the next
request.
note ............. The following sections include example values for print_command. All of these values
are enclosed in double quotes, which are required for WM to read. When double quotes
are not present, the system throws a TimedOutException 60 seconds after the client
users launches the Print operation.
6.2.1 Enabling Print in Windows

For a WM server on Windows, the print command should be configured as follows:
PRINT_COMMAND "lpr -S server -P printername filename"
where
 server is the name of the host that provides lpd service.
 printername is the name of the print queue, which is maintained by the printer to put
the job in the print queue and process.
 filename is the name of the temporary file that WM should write into the SAVE_DIR
directory.
Examples
SAVE_DIR state PRINT_COMMAND "lpr -S Duplex1 -P test
state\\printfile.tmp"
where
 Duplex1 is the host name of the server.
 test is the name of the print queue.
 printfile.tmp is the file to be printed in the state directory.
For a server that uses the shared printer of another device, the print command should be configured
as follows:
SAVE_DIR state PRINT_COMMAND "cmd /c copy state\\printfile.tmp
\\\\user1\HPLaserJ"
where
 printfile.tmp is the file to be printed in the state directory.
52
October 2015
 user1 is the device to which the printer is connected.

 HPLaserJ is the name of the share.
6.2.2 Enabling Print in Linux

For a WM server on Windows, the print command should be configured as follows:
PRINT_COMMAND "lpr filename"
where
filename is the name of the temporary file that WM should write into the SAVE_DIR
directory (for example, save_dir//printfile.tmp).
6.2.3 Enhancing the Printed Output

You may wish to have the content formatted before it is sent for the print process. To do so, you can
script your own print.bat or print.sh command, which calls the fmt command first and then the print
command as documented above. For this case in Linux, for example, the print command should be
configured as follows:
PRINT_COMMAND "sh print.sh"
6.3 Configuring Fault Management Parameters

The Fault Management module can be administered by configuring the following parameters in
EventMgr process in the NmsProcessesBE.conf file in the
note ............. If you configure any parameter, you must restart the Wireless Manager server to put the
new value into effect.
The following descriptions apply to the configurable parameters.
53
October 2015
Table 7: Fault Management configurable fields
Values
Arguments Description
Defaul
Options Notes
t
As of this Release, this

EVENT_DEBUG - - -
parameter is not in use.
PRINT_COMMAND is
A valid & dependent on SAVE_DIR.
Used to specify the
existing When Print action is
directory in which Events
directory invoked from the client,
and Alerts viewed by the
SAVE_DIR name, with state the contents will be
client are to be saved,
the path, temporarily saved in a file
when the 'Save' option is
relative to printfile.tmp file under
invoked from the client.
WM_Home <SAVE_DIR> and then
printed.
The
Operating
Used to specify the
System
command to be executed,
specific
when the user invokes the PRINT_COMMAND is
PRINT_COMMAND command -
Print option from the dependent on SAVE_DIR.
that could
Event Viewer/Alert Viewer
invoke print
of Applet client.
action from
the system.
The Events older than this

number of days, will be
removed from the system.
Once in every hour, a
Used to specify the check for older Events will
Any positive
number of days after be done.
CLEAN_EVENT_INTERVAL integer * 7 days
which the Events have to
value. When negative value is
be cleaned up.
specified for the
parameter, Events will not
be deleted based on time
interval.
54
October 2015
Values
Defaul
Options Notes
t
Only the latest number of

events specified by this
option will be managed by
the system. All other
events will be in the
database, but cannot be
viewed or managed.
However, the total
number of Events in the
Client may exceed the
Used to specify the EVENT_WINDOW_SIZE,
number of events that Any positive until you refresh it
EVENT_WINDOW_SIZE need to be actively integer 10000 manually or navigate the
managed by the system. value. tree nodes/pages and
then revisit the concerned
panel.
This is because, once the
total event count reaches
EVENT_WINDOW_SIZE,
then for each and every
new Event added, an old
Event should be fetched
from DB for deletion,
which will have a bearing
on Performance.
55
October 2015
Values
Defaul
Options Notes
t
If the size of the queue is

more than this number,
the System input will be
suspended until the
queued Events are
processed. The Events
that you try to add at this
point of time will not be
added into the System.
You have to take care of
When the rate of incoming adding those Events, after
Events is higher compared checking the queue size
to the processing rate, the using the
additional Events may is_inQ_SizeBeyondLimit()
have to be buffered in Any positive method. If the Event
MAX_EVENT_PROCESS_QUEUE memory which will lead to integer * 500 queue size is exceeded,
an increased usage of value. wait for some time (say 1
memory. At one point of sec) before retrying to add
time, there is a possibility Events.
of an OutofMemory Error MAX_EVENT_PROCESS_Q
being thrown. UEUE parameter is
provided to avoid such
problems and to keep the
memory under control.
You can configure the
Event queue size (i.e., the
maximum number of
Events that can be queued
when they are added into
the system) using this
parameter.
The Trap PDU information

Whether to maintain the in the Events can be used
received SNMP Trap PDU to effectively parse and
TRANSIENT_TRAP_PDU_IN_EVENT true/false * false
reference in the Event or filter events.
not.
Whether to drop or
continue processing the
SNMP trap, if its
DROP_TRAP_WHILE_UNMANAGED true/false * false -
corresponding managed
object is in unmanaged
state.
56
October 2015
Values
Defaul
Options Notes
t
Authorization is the way in

Whether to enable / which an authenticated
disable authorization user is validated if he is
check ,when a user tries to authorized (has been
AUTHORIZATION perform a fault true/false true granted the necessary
management operation, permission) when he tries
like picking up alerts, and to perform a specific
so on. operation.
Whether to enable /
V3_AUTH disable authentication for true/false * false -
SNMP v3 traps.
Inform Requests are

unsolicited notifications
sent by
Whether to enable/disable
WM to send  an Agent to Manager.
NEED_INFORM_ACK acknowledgment, for the true/false * false  a Manager to Manager.
Inform requests from the
In both cases, an
Agents.
acknowledgment will be
sent by the Manager after
it receives the notification.
When an interrupt is
received to shut down the
Server, where some
Notifications are still
pending to be parsed and
filtered, how to deal with
GRACEFUL_SHUT_DOWN them - whether to true/false false -
(gracefully) shutdown
after completing the
further processing of these
Notifications or to stop
processing and allow for
abrupt shut down.
true - batch
Batch update is used when processing of
Events are to be added to Events is
the database as a batch so enabled
BATCH_UPDATE as to decrease the number *false -
of queries, thereby false - batch
enabling an increase in processing of
performance. Events is
disabled.
57
October 2015
Values
Defaul
Options Notes
t
Valid from 4.7 SP1 only

Parameter to configure
the frequency of If invalid or negative value
Any value
CLEANUP_QUERY_INTERVAL CLEAN_EVENT_INTERVAL *1 hour is specified, WM will take
from 1-24
check. By default, this the default 1hour
check will be made every
one hour.
Used to specify the user

classes generated by Generated
PERSISTENCE_CLASS *- -
extending the UserClass
HbnEventPersistence class.
NOTE: * indicates that the option will not be present in NmsProcessesBE.conf by default.
58
October 2015
7 Performance Management
Configuration
7.1 Managed Objects
The main input to the performance module is the Managed Objects that are created to represent
network devices. These Managed Objects are created by the Wireless Manager Topology module
when the discovery process takes place. Managed Objects hold details of network elements such as:
Name, Type, status, etc. Data collection is configured for these Managed objects in the Performance
module.
The startup options of the Performance Management module can be modified by editing the
parameters of the Collector process in the NmsProcessesBE.conf file located in the
note ............. If you have updated any of the configuration parameters, be sure to restart the Wireless
Manager Server.
The following are the parameters that you, as an administrator of the file system, can adjust after
deployment.
Table 8: Performance Management configurable fields
Parameter Description
This specifies the number of days after which the data collected
during polling (string data or stats data) have to be cleaned up. The
data older than the specified number of days will be removed from
CLEAN_DATA_INTERVAL the system. This deletes the table after the specified days that are
appended with the date. If a single table is used to store the data for
all the days, then that will not get deleted.
Default value : 7
This specifies the maximum number of times the system can try to
ping the device to retrieve its status. This indicates that request will
STATUS_POLL_PING_RETRIES be sent for STATUS_POLL_PING_RETRIES + 1 times.
Default value : 0
perform SNMP ping to the device to retrieve its status. This indicates
STATUS_POLL_SNMP_RETRIES that request will be sent for STATUS_POLL_SNMP_RETRIES + 1 times
Default value : 0
To specify the time in seconds for the server to wait for the request
from host. This value is configured for ICMP Ping when native ping is
STATUS_POLL_PING_TIMEOUT disabled
Default value: 1 (i.e., will wait for one second if a particular node is
not reachable).
59
October 2015
ping the device to perform data collection (Polling). This indicates
DATA_COLLECTION_SNMP_RETRIES that request will be sent for DATA_COLLECTION_SNMP_RETRIES + 1
times.
Default value : 0
PolledData with the same Agent, Protocol and Period (APP) are
combined and depending on this parameter, number of polls to the
agent will be done. For example, if the MAX_OIDS_IN_ONE_POLL is
10 and the number of PolledData with the same APP is 20, then two
MAX_OIDS_IN_ONE_POLL sets of polls with the first set containing 10 and second with 10 will be
done, and the values will be stored in the table in which they are
intended to go.
Default value : 15
This specifies the fully qualified class name which has implemented
CUSTOMIZED_DATA_COLLECTOR
the interface CustomDataCollection.
This is a customizer (basically the GUI) that is to be brought up while

adding or modifying a polling object. This parameter allows the user
POLLING_POLICY_CUSTOMIZER to have his/her own Property for the polling policies instead of the
one provided by default.
This parameter is deprecated in later releases.
The parameter, when set as "true" prints out debugging statements

in the log file which can be used to analyze the data collection. It can
be turned on/off using the method setDebugMode() in the
DEBUGGING_MODE PollAPI. While developing an application, these debugging statements
will be of great use to the developer to know about the problem that
has occurred.
Default value : false
When this parameter is set as false, the Multiple PolledData from a

SEND_MULTIPLE_REQUEST single table will be polled separately.
Default value : true
This specifies the interval between two successive queries to the

STATUS_POLL_QUERY_INTERVAL database, for status polling.
Default value : 1500
This specified the interval between two successive queries for

retrieving polling units to be polled.
note………………This parameter has been deprecated in later
releases. The interval is now the value of the
DATA_COLLECTION_QUERY_INTERVAL GlobalPerformancePollingInterval tag in the
.../WM/server/conf/
WibbWMSConfiguration.xml file. However, the
interval should be set in the Polling Configuration
dialog, not in this configuration file on the server.
This specifies whether authorization is required for all the client

AUTHORIZATION requests or not.
60
October 2015
Whenever a managed object is passed through Polling.conf, and
when it satisfies the match criteria specified in the first PollingObject,
PolledData will be created and will not check the match criteria given
in other PollingObjects. Setting the value as "true" for this parameter
PASS_THRO_ALL_POLLING_OBJECTS will make the ManagedObject to check all the match criteria in all the
PollingObjects. In this case, even if the match criteria of the first
PollingObject gets matched, the ManagedObject will be passed to the
subsequent PollingObjects also.
When this parameter is set as "true", the Poll ID and its

corresponding key will be stored in the PollIDToKeyMap table. This
RECOVER_DELETED_PDATAS will be useful, if you want to access the collected data for the deleted
PolledData.
This parameter is used when you want the collected values to be

updated in a database, after a specified time interval. This parameter
takes its value in seconds. The inserts for the collected values will be
stored in a temporary memory till this time, and will get updated as a
bulk in the database.
For e.g. if BULK_INSERT_INTERVAL is set to 30, then for every thirty
BULK_INSERT_INTERVAL seconds the collected data will be stored in memory as a single insert
statement. As soon as thirty seconds get elapsed, the insert
statements will be executed and data will be inserted into database.
Default value : 0
By default, collected data is inserted as soon as it is collected and not
accumulated in memory as a bulk.
This parameter is used when you want the collected values to be

updated in a database, after a specified number of inserts getting
accumulated in the temporary memory. This parameter will take an
integer value and many inserts will be stored in the memory, before it
writes into the database. To use this parameter, the
BULK_INSERT_INTERVAL parameter should also be used.
note………………When MAX_ALLOWABLE_INSERT value is
reached, the interval set for Bulk insert is not taken
MAX_ALLOWABLE_INSERT into consideration and the insertion takes place
immediately.
For e.g. if BULK_INSERT_INTERVAL is set to 30 seconds and
MAX_ALLOWABLE_INSERT is set to 10 then if the number of insert
statements in memory goes above 10 then though
BULK_INSERT_INTERVAL is not reached, insert statements will be
executed and data will be transferred to database.
Default value : 0
61
October 2015
This parameter is used to specify the time period for which the server
has to wait (after it has got started) to start the status polling of
managed objects
This parameter can be used in cases where you have large networks
STATUS_POLL_DELAY to be discovered during server startup and you do not want the
server to be loaded with both discovery and status polling. By
configuring this parameter, you can postpone the status polling for
sometime.
Default value : 5 minutes
During data collection there is possibility that

◦ the agent might be down
◦ the agent might be delaying the response
◦ there is packet loss while data is transferred.
DATA_COLLECTION_SNMP_TIMEOUT
In all such circumstances, the delay caused can be indefinite. Hence
you can set a Time out which will indicate that Poll Engine should wait
for that number of seconds. If requested data is not received before
that time, an error message is registered.
Default value : 5 seconds
When a PolledData is created, you may wish to start data collection

for it immediately or induce a delay. This can be specified in this
parameter. Numeric values starting from 0 is allowed. If you specify
DATA_COLLECTION_STARTUP_DELAY zero , data collection will start immediately. Note that this setting is
common for all PolledData created in the system.
Default value : 5 minutes
By default, status polling is performed for each of the MOs, whereby

a query is sent to each of the MOs. The status polling of MOs can be
ENABLE_STATUS_POLL_BATCH processed in batches also. To enable this, add a new parameter
ENABLE_STATUS_POLL_BATCH (not available by default) and set it to
true.
7.2 Operator-defined Reports

Network operators can add their own custom-defined reports for launching from the client. These
can be crafted by either
 copying existing reports in the System Reports folder and then editing them to the type
and amount of customization desired.
 composing them without the re-use of any pre-existing (furnished) report.
The custom-defined report is then placed into either
 the ...server\Default Templates\System Reports folder, for a device-
specific report
 the ...server\PHP Reports\System Reports folder, for a generic report, which
will be valid for a device of any type.
62
October 2015
Each of these custom reports must then be imported into the client application through a client
session from the server device, performing the user guide procedure titled "To import system
reports" and browsing to one or both of the folders whose path is noted above.
Any context or other problems in an operator-defined report may prevent the report from being
listed in, and thus available for launch from, the client. When you mount a custom report, you may
want to send a message to the clients (see the user guide section titled "Broadcasting a Message"),
advising users of the new report and reminding them to import it into the System Reports panel of
the client so that they will have access to it.
7.3 Collected Statistics Plot for Poll Failure

By default, collected statistics graphs in the WM client application omit data from failed polling
attempts and plot the average across the missing point in the graph, and WM does not log events for
failed statistics polls. This can make issues such as an element being out of service difficult to detect
in the graph or stats table and show up only later in the log. This treatment is because the value of
the PollFailedActionEnable flag is preset to false. To change this setting so that WM will
display and store 0 for the float value received and Not polled for the string value received, and
will generate and event that throws the failed poll to the log, perform the following steps.
Procedure 21: To display and store failed statistics polls

1. Browse to the /usr/local/cambium/wm/server/conf directory in Linux
or the C:\Cambium\WM\server\conf folder in Windows.
2. In the text editor of your choice, open the file WibbWMSConfiguration.xml file for
editing.
3. Search for PollFailedActionEnable.
4. Change its value from false to true.
5. Write and save the file.
63
October 2015
8 Security Management Configuration

The Security Management module of WM maintains and configures security information, including
definitions of users and groups and their permissions. Security Management provides the following
flexibility in controlling access to WM and your networks:
 By defining and managing groups and users, you can authorize users to perform only certain
functions, based on whether they are members of a group for which you have defined the
permissions.
 You can specify access for only a certain user or group to be able to see a particular view.
 You can limit the WM experience for a user to a specific device type.
8.1 Defining and Managing a Group or a User

A group is a set of permissions that a specific set of associated users carry as they use the WM Web
Start client. A group is defined by a user who has administrative permissions in the Web Start client
and accesses the Security Administration area via its Tools menu. A wizard accepts the group name
from the administrator and displays the Operations Tree Root. The administrator confirms and at any
later time can configure the group, who is now listed in the Security Tree.
In the Security Tree, the administrator can check the check box for any specific function to allow and
any to disallow. For any function that the administrator makes no check marks, the parent functional
area permission (allowed or disallowed) is inherited for all members of the group.
The process of adding and managing a user is similar, except that WM applies the result of the
administrator-specified permissions to only the individual user. To add a user from the command-line
interface on the WM server, you can execute the UserConfig.sh or UserConfig.bat file
located in /usr/local/cambium/wm/server/bin/admintools directory in Linux (or the
C:\Cambium\WM\server\bin\admintools folder in Windows) from the command line as
follows:
UserConfig.sh/bat
Add > WirelessManager UserName Password Group
where:
UserName is the user name of the new user.
Password is the password to authenticate the user during his login.
Group is the group to which the user should belong.
Example:
UserConfig.sh/bat
Add > C:\program files\adventnet\webnms guest xyz Admin 1100
where a new user named guest is added to Admin group with a password of xyz to the
database.
65
October 2015
8.2 Defining and Managing Authorized and Custom

View Scopes
Scopes that a Web Start client administrator defines allow or disallow the members of any group(s)
an activity based on the values of specific properties. In the case of Custom Views, the permissions
are enforced on what sets of data and representations the groups and users will be allowed to see in
WM.
8.3 Adding and Managing Operations

Yet another way to cordon off users from the full set of functions in WM is for a Web Start client
administrator to specify, by operation in a tree of possible operations, which group(s) and which
user(s) are permitted to perform them. Although most of the operations in the operations tree will
always be present by default in WM, the administrator can add operations (for added sub-
applications, for example) in which to grant specific permission levels.
8.4 Enabling the Authorized Mode for Security

Operations
The security management module in Wireless Manager provides an authorized mode of performing
security operations for a group or user. This feature is facilitated by configuring the startup options of
the security module.
Procedure 22: To enable authorization support

1. Before you start the Wireless Manager server, open the file NmsProcessesBE.conf
present in the /usr/local/cambium/wm/server/conf directory in Linux (or the
C:\Cambium\WM\server\conf folder in Windows) for editing.
2. Find the following process:
com.adventnet.nms.security.authorization.NmsAuthManager
3. Configure the argument authorization_for_security_administration to
true. By default, this value is set to false.
After setting the authorization_for_security_administration to true, the
authorization support is enabled for all security operations. This action will cause all users to not be
able to perform the operations and set permissions (for which they are not authorized to do) in the
Security Administration UI.
Example
This example captures two different scenarios: authorized mode for security operations and
unauthorized mode of security operations. This example reveals the difference between an
authorized and an unauthorized mode of performing security operations. Follow the steps given
below to accomplish the task.
1. Before starting the Wireless Manager server, set the
authorization_for_security_administration argument to true in
66
October 2015
NmsProcessesBE.conf file present in the

/usr/local/cambium/wm/server/conf directory in Linux (or the
C:\Cambium\WM\server\conf folder in Windows). This is the authorized mode.
3. Log in to the client as an administrator with the default user ID of root and a password of
public.
4. From the main menu, select ToolsSecurity Administration.
5. Right-click on the Groups node in Security tree and select AddGroup.
6. Create a new group called Group1.
7. Click Next.
8. In the Permissions tree hierarchy, enable the Security Administration node.
9. Disable Add Group, Remove Group, and Remove Operation operations.
A graphic depicting this configuration is shown below.
Figure 1: Security Administration Tree – Group Operations
10. Right-click on the Users node in Security tree and click AddUser.
11. Create a new user Group1User with the password group.
12. In the final screen of the wizard, select Group1 under Assign Groups for the user field.
13. Click Finish.
You have now associated the user Group1User with the group Group1.
14. Click Finish to quit the Security Administration UI and the Wireless Manager client.
15. Log in to the client again, but this time with a user ID of Group1User and a password
of group.
16. Select ToolsSecurity Administration. The Security Administration window is displayed.
17. Select FileAddGroup.
67
October 2015
Wireless Manager displays a warning popup with the message Group1User is not
authorized to perform the operation. This occurs because we have disabled
this particular user from adding a new group.
18. Similarly, try removing an existing group. The same message is displayed.
19. Try removing an existing operation. The same message is displayed.
20. Close the client and shut down the server.
21. Set the authorization_for_security_administration argument to false in
NmsProcessesBE.conf file present in the
/usr/local/cambium/wm/server/conf directory in Linux (or the
C:\Cambium\WM\server\conf folder in Windows). This is the unauthorized mode.
22. Restart the server .
23. Log in to the client with user ID Group1User and password group.
24. Select ToolsSecurity Administration. The Security Administration window is displayed.
25. Try to add a new group.
You will be able to create the group and no error message is displayed. This is because no
authorization support is provided for performing the security operations alone.
8.5 Configuring Security Management Parameters

The startup options of the Security Management module can be modified by editing the parameters
of NmsAuthenticationManager and NmsAuthManager processes in the
NmsProcessesBE.conf file located in the /usr/local/cambium/wm/server/conf
directory in Linux (or the C:\Cambium\WM\server\conf folder in Windows).
note ............. You must restart the Wireless Manager server if any of the configurable Security
parameters have been updated.
The parameters that can be configured by administrators are as follows:

 To set the count for maximum allowed unsuccessful login attempts:
maximum_allowed_login_failed_count in NmsAuthenticationManager
 To set the time interval in milliseconds for the security scheduler:
time_interval_for_security_scheduler in NmsAuthManager
 To change the password after the first time logging in:
change_password_for_firsttime_login in NmsAuthManager
8.6 Configuring Password Complexity

A WM operator can optionally set up WM to req uire that the passwords for all new accounts meet a
complex standard, such as contain at least one of each of certain types of characters. A commented
out configuration is provided and can be easily put into effect, as is or modified. To change password
requirements for all users, perform the following steps.
Procedure 23: To add password complexity

1. Navigate to the following directory in the server file system:
/usr/local/cambium/wm/server/conf/ in Linux or
C:\Cambium\WM\server\conf\ in Windows.
68
October 2015
2. In the editor of your choice, open the file WibbWMSConfiguration.xml.

3. Find and uncomment the following lines:
<PasswordComplexityExpression value="((?=.*[a-z])(?=.*[A-Z])(?=.*\d)(?=.*[@#$]).{5,24})" />
<PasswordComplexityErrMsg value="Password can have minimum 5 characters and maximum
24; It must contain at least One uppercase character from 'A-Z' AND One lowercase
character from 'a-z' AND One digit from '0-9' AND One special character from '@#$'" />
4. To remove or modify any of these requirements, update both the expression value and the
error message value.
5. To enforce these requirements, save and close the file.
Since the implementation of this feature is subject to specific options of the operator, the User
Administration dialog in the client application is unchanged, except that the error message that you
configured in Step 3 will be thrown for passwords entered that fail to comply.
So, operators who enforce new requirements will need to inform all the users about the changes. The
changes take effect the next time that the server is restarted.
8.7 Enforcing a Password Change Requirement

By default, WM does not require a first-time user to change password upon successful log in. You can
change this behavior to force all first time users to change their passwords. To do so, perform the
following steps:
Procedure 24: To enforce the password change requirement for first-time users
2. In the text editor of your choice, open the file NmsProcessesBE.conf for editing.
69
October 2015
3. Search for change_password.

4. Reset change_password_for_firsttime_login false to
change_password_for_firsttime_login true.
6. Restart the WM server.
8.8 Enforcing One Session per User

By default, WM allows any user to have multiple simultaneous client sessions open. WM allows the
operator to configure WM to limit all users to a single session at any given time. To configure this
limit, perform the following steps.
Procedure 25: To prohibit multiple simultaneous sessions by any of the users

2. In the text editor of your choice, open the file WibbWMSConfiguration.xml for
editing.
3. Search for IsAllowedMultipleInstances.
4. Change its value from true to false.
8.9 Managing Expiry for User Accounts and Passwords

User account expiry and password expiry are two different entities. You can separately give a user
name and a password expiry. Password expiry is checked only when the user tries to log in. The user
account expiry is checked at a regular time interval. This time interval check works only if
time_interval_for_security_scheduler_in_ms parameter in
NmsProcessesBE.conf file located in the /usr/local/cambium/wm/server/conf
directory in Linux (or the C:\Cambium\WM\server\conf folder in Windows) is configured
(in milliseconds). By default, the value is set to 0, which will cause the scheduler to not start and the
user expiration check to not be performed.
8.10 Restoring a Deleted superuser Account

The user guide section titled "Deleting a User" cautions against deletion of the superuser (initially,
root) account in the WM client interface unless another user with the same capabilities currently
exists. If a user does so despite the caution, use the following procedure to restore a superuser
account to the system and return the group Admin accounts to their previous configurations.
Procedure 26: To restore the superuser account and the security tool cache
1. Ensure that the WM server is running.
note ............. The following step asks you to input a new superuser account name. Using the name
root is discouraged.
2. If the server device is on a Linux OS, perform the following steps:
a. Enter cd /usr/local/cambium/wm/server/bin.
70
October 2015
b. Enter ./createSuperUser.sh db_user db_password new_superuser.

If the server device is on a Windows OS, perform the following steps:
a. Select StartRun.
b. In the Open field of the Run dialog, type in cmd.
c. Click OK.
d. At the DOS prompt, enter cd C:\Cambium\WM\server\bin.
e. Enter createSuperUser.bat db_user db_password new_superuser.
RESULT: The superuser account new_superuser is provisioned with the initial WM
client password public, even though it is not initially displayed in the Security tree of the
interface, and the group settings for the Admin group are restored to defaults.
3. Launch a session in the WM client interface, logging in as new_superuser with the

password public.
4. Select ToolsAdministrationSecurity Administration.
5. In the left panel of the Security Administration window, click to highlight GroupsAdmin.
6. In the right panel, click the Members tab.
7. Click the Setting Users button.
8. Move users to and from the Selected Users block until the list in that block consists of the
same set of users who belonged to the Admin group before the lone superuser account was
deleted and then restored.
9. Click OK in the Select Users window.
10. In the left panel of the Security Administration window, click to highlight
Usersnew_superuser.
11. Select Edit-Change Password.
12. Type a new password twice to supersede the default password public.
13. Click OK in the Change Password window.
71
October 2015
9 Offline Physical Map Setup

This feature supports operators who use WM where no connection to the Internet is available and
provides for them a geo-referenced representation of the entire network in the WM client, while not
specifically disabling the online physical map. Compared to the online map, the offline map differs in
that it does not include
 link profiles
 Google search
 the Show Address capability
 Google Street View
 drag-and-drop device positioning
This release supports GeoServer as the map tile server local or remote (especially for large networks)
to the WM server. Geoserver does not limit how many images a WM operator can use for layers of
the offline map. Both the source images and the cached image tiles should be stored on a drive of the
computer where GeoServer resides. WM supports layers that are created from any of the following
source file types:
 GeoTIFF
 WorldImage
 ArcGrid
 Java Property file
 Web Feature Server
 Directory of spatial files
 Gtopo30
 ImageMosaic
 PostGIS Database
 Shapefile
Instructions for using setting up WM to use the map images created according to this chapter are
provided under Using the Offline Physical Map Panel .
9.1 Deploying GeoServer

To deploy GeoServer, perform the following steps.
Procedure 27: To deploy GeoServer

1. Visit http://geoserver.org.
2. Download the latest version of the GeoServer software.
3. Download its associated documentation.
4. Install GeoServer according to its documentation.
5. Launch your web browser.
6. Navigate to http://GeoServerHost:8080/geoserver/web/.
The web interface to GeoServer opens.
73
October 2015
9.2 Creating Map Layers
9.2.1 Creating a layer from an image file

To create an offline physical map layer from a single image, perform the following steps.
Procedure 28: To create a layer from one image

1. Under Data in the left panel, click Workspaces.
The Workspaces panel opens to the right.
2. Click the link for Add new workspace.
3. In the Name text box, compose a name by which you will later recognize this workspace.
4. In the Namespace URI text box, type in any functional URL.
5. Check the Default workspace check box.
6. Click the Submit button.
When the Workspaces panel repaints, it includes the new name in the list of workspace
names. Now a data store is needed for the images that this workspace will use.
To create a data store for the image that you will create, perform the following steps.
Procedure 29: To create a data store for GeoServer workspace images

1. On the GeoServer host, create the directory
GeoServer_Version/data_dir/data/WorkspaceDirectory.
2. Copy the image from which you want to create a layer into this new directory.
3. In the left panel of the GeoServer interface, click Stores.
4. In the Stores panel to the right, click Add new Store.
5. Under New data source in the resulting right panel, click the type of image that you copied
to the directory.
6. In the Add Raster Data Source panel, use the drop-down menu to select the Workspace
name.
7. In the Data Source Name text box, compose a name by which you will recognize the data
source.
8. In the associated Description text box, compose a description that will help you distinguish
this data source from others that create.
9. Under Connection Parameters, use the URL text box to paste the
WorkspaceDirectory/ImageFileName onto the end of the supplied string
file:data/.
10. Click the Save button.
The New Layer chooser panel opens on the right.
11. In the table of layers, click the Publish button in the row of the layer that you just created.
12. Review the information provided in the resulting WorkspaceDirectory:LayerName
panel.
The resulting right panel displays a table of all of the published layers. Now you need to
verify that GeoServer can connect to the data store.
74
October 2015
To verify that GeoServer is properly connected to the stored image file, perform the following steps.
Procedure 30: To verify that GeoServer connects to the image data store
1. Under Services in the left panel of the GeoServer web interface, click GWC, which represents
GeoServer Web Cache.
The GeoWebCache web page opens.
2. Under Automatically Generated Demos, click A list of all the layers and automatic demos.
3. In the resulting table, find the layer that you created in this procedure.
4. Click one of the file formats in the OpenLayers column for your layer.
5. Inspect the image to verify that it is as intended.
6. Use the back button in your browser to return to the Layers web page.
To create an offline physical map layer from multiple images, perform the following steps.
Procedure 31: To add an image to an existing layer

1. Perform Procedure 29 except that, instead of creating a Workspace directory, use the
Workspace directory that you created to store the first image. Then proceed as follows.
2. In the left panel, click Layer Groups.
3. In the Layer Groups panel to the right, click Add new layer group.
4. In the Name text box, compose a name by which you will recognize the new layer group.
5. Click the Submit button.
note ............. Delay the Generate Bounds operation until all intended layers have been added.
6. Beneath the Generate Bounds button, click Add Layer.
7. In the Choose new layer pop-up window, click the name of the first layer to be included in
this layer group.
8. Click Add Layer again.
9. Click the name of the second layer to be included.
10. In the Layers table of the Layer group panel, toggle the positions of the images until the
desired base image is in the top row, the image that you want imposed on that one is in the
second-from-the-top row, and so forth.
11. Now click the Generate Bounds button.
13. In the left panel, click WCS.
14. Ensure that the new layer group name is listed among the layer names.
15. Click one of the file formats in the OpenLayers column for your layer group.
16. Inspect the layer group to verify that it is as intended.
17. Use the back button in your browser to return to the Layers web page.
75
October 2015
9.2.2 Creating a layer from a shape file

This section cover downloading, and possibly needing to convert the format of, a shape file and then
using the shape file to create layers in Geoserver.
Obtaining a shape file

This section provides guidance for obtaining a shape file of the format (.shp) that Geoserver uses. The
method to obtain it may be as simple as downloading it in this format already or as complex as
downloading it in the .pbf or .bz2 compressed format of .osm (an xml version that OpenStreetMap
provides) and then converting the .osm file to .shp.
Procedure 32: To download a shape file

1. Open the web site http://wiki.openstreetmap.org/wiki/Main_Page.
2. Become familiar with the OpenStreetMap project.
3. Open the web site http://download.geofabrik.de/.
RESULT: The prominent features of this site are an interactive map and a table.
4. Open the web site http://wiki.openstreetmap.org/wiki/Planet.osm#Downloading.
5. Scan the tables of Worldwide data and Country and area extracts to see whether any of the
maps that are currently available would suit your needs.
6. If so, click the associated link in the Mirror column and follow download instructions at the
called site.
7. If the desired map was not available through the preceding steps, click the .osm.pbf link for
the target continent in the Quick Links column of the regional map links table.
note ............. Typically, the .bz2 version of the same data is significantly larger.
8. Save the file.
Procedure 33: To convert a .osm.pbf or .osm.bz2 file to .osm

1. Open the web site http://wiki.openstreetmap.org/wiki/Osmconvert.
2. Read the documentation that this site provides for the Osmconvert tool.
3. Establish a local directory (for example, OSM_Convert) in which to prepare map files.
4. Download into OSM_Convert the version of the tool that is compatible with your
operating system.
5. Navigate to the directory OSM_Convert.
76
October 2015
6. At the operating system command prompt, enter

osmconvert region.osm.pbf > region.osm.
7. Wait until the new file (region.osm) is visible in the directory contents.
note ............. Depending on the volume of data available for your region. a considerable amount of time
may be required to complete the conversion.
The following procedure is only one of various to perform a .osm-to-.shp conversion.
Procedure 34: To convert a .osm file to .shp using QGIS

1. Open the web site http://www.qgis.org/.
2. Click their download link.
3. Read the OS-specific documentation at
http://hub.qgis.org/projects/quantum-gis/wiki/Download.
4. Download QGIS 1.8.0 software.
5. Launch QGIS.
6. In the QGIS window, select PluginsManage Plugins.
7. Select the OpenStreetMap plugin in the list and click OK.
RESULT: The OSM Feature panel opens in the right side of the tool's interface.
8. Click the icon for Load OSM from file. (See the capture below.)
9. For Add columns for tags, select as many columns as would suit your needs.
10. Wait until the layers display in the Layers panel on the left side of the tool's interface.
11. Use Ctrl-click to select the layers whose names end with a polygon, then right-click and
select Save As.
12. For Format in the resulting dialog for Save vector layer as, select ESRI Shapefile.
13. Browse to and select the directory for the new .shp file.
77
October 2015
Creating the layers with the shape file

Procedure 35: To create a data store for GeoServer workspace shapes
1. On the GeoServer host, create the directory
GeoServer_Version/data_dir/data/WorkspaceDirectory.
2. Copy the shape file from which you want to create a layer into this new directory.
3. In the left panel of the GeoServer interface, click Stores.
4. In the Stores panel to the right, click Add new Store.
5. Under New data source in the resulting right panel, click either
◦ Shapefile for one
◦ Directory of spatial files for more than one.
6. Under Basic Store Info in the New Vector Data Source page
◦ if you selected Shapefile in Step 5, perform the following steps:
a) use the drop-down list to select the directory from Step 1.
b) for Data Source Name, type a memorable name into the text box.
c) for Description, type text that describes this data source.
◦ if you selected Directory of spatial files in Step 5, use the drop-down list to select the
directory that holds all the shape files.
78
October 2015
7. For Shapefile location under Connection Parameters, specify the path and file name of the
shape file from Step 2:
GeoServer_Version/data_dir/data/workspace_name/copied_shapefile.shp
RESULT: The New Layer panel opens on the right.
79
October 2015
Procedure 36: To configure the new layer

1. If you have not performed Procedure 35, perform it now.
2. In Name text box of the Data tab, type a name that will apply to the layer being configured.
3. In the Title text box, type the phrase that this layer will show as its title.
4. In the Abstract text box, type general information such as the purpose of the layer.
5. Click the Publishing tab.
6. Next to the Declared SRS field, click the Find button.
7. In the resulting dialog, select the coordinate system with code 4326.
note ............. WM server uses the EPSG:4326 coordinate system to display offline maps, and
EPSG:4326 appears in Declared SRS field.
8. Under Native Bounding Box, click Compute from data.
9. Under Lat/Lon Bounding Box, click Compute from native bounds.

RESULT: The software generates the bounds for the shape file layer.
RESULT: The layer configuration is finalized, and a page opens to a list of all layers that are
currently configured in Geoserver.
Procedure 37: To verify the new layer configuration

1. In the left panel Layer Preview, verify that the latest configured layer is present in the list.
2. In the Common Formats column, double-click its OpenLayers link.
RESULT: If an OpenLayers map opens, then the configuration was successful.
80
October 2015
9.3 Pre-caching the Map Images

At this point in the process, you could retrieve the layer group that you have created and view it,
panning and zooming at will. However, if you did, you would observe that the interface encounters
delays as it paints zoomed levels of a layer. Pre-caching images mitigates these delays.
In the directory data_dir/GWC on the GeoServer host computer, GeoServer has stored stores pre-
cached output from the layers that you loaded into its system, each in a subdirectory named from the
layer name, with lower directories for each view (tile) that you rendered while zooming and panning.
This automatic function of GeoServer facilitates speedy loading of all of these tiles as you demand
them in the future, but only those tiles that you viewed are represented at this point. To ensure that
the map will properly and quickly display all levels of zoom of all tiles, you need to pre-cache them in
GeoServer. To do so, perform the following steps.
Procedure 38: To pre-cache all tiles for all levels of zoom

1. In the left panel of the GeoServer web interface, click WCS.
2. Click the Seed this layer link associated with the layer that you want to pre-cache.
This opens a task page in which you can configure the pre-caching of the layer.
3. For Number of threads to use, select the desired number (for example, 16, recommended
for the maximum).
4. For Type of operation, select either Seed to generate only those tiles that have not been
cached yet or Reseed (recommended) to generate caches of all tiles.
5. For Grid Set, select ESPG:4326.
important ........... No other setting will work with the physical map in WM. This is the only setting that
employs a latitude/longitude format that is compatible with WM.
6. For Format, always select image/png for maximum compatibility with WM.
7. For Zoom start, always select 00 as the lowest zoom level.
8. For Zoom stop, always select 16 as the highest zoom level.
9. Ignore the Bounding box text fields.
10. Click Submit.
A Task submitted page opens and lists all of the threads that GeoServer is executing based
on the task that you just defined. This page removes threads as they are completed.
tip ................ Attempt to avoid using the GeoServer computer resources for other purposes during the
caching operations.
11. To optionally monitor the progress of these threads, click the Refresh list link beneath the
list of threads.
81
October 2015
9.4 Changing the Maximum Zoom Level

The maximum zoom level of the offline (static) physical map is operator configurable. Where the
default highest level of zoom is insufficiently magnified, changing the whole scale by redefining a
greater maximum can make the map more useful. To do so, perform the following steps.
Procedure 39: To set a different max zoom level for the offline map
1. Navigate to C:\Cambium\WM\server\webclient\oakleaf\conf\ in Windows
or /usr/local/cambium/wm/server/webclient/oakleaf/conf/ in Linux.
2. Open the file AxelConfig.xml for editing.
3. Find the attribute maxZoomLevel.
4. Overwrite the current value with the desired value.
note ............. The default value is 16.
82
October 2015
10 Optimization of WM Server
Performance
10.1 Optimizing MySQL Database Performance
The following are general recommendations for all operators, very strongly recommended for
operators of large networks. However, these recommendations apply only where the attribute is
currently set to a value that is smaller than the recommended value.
Procedure 40: To optimize the MySQL database resources for WM

1. Stop the service for MySQL Server.
2. In the MySQL server file system, find either the file my.cnf or the file my.ini.
3. Open the file for editing.
note ............. A simple and fast way to accomplish the next step is to initially use the contents of the file
my-huge and edit them.
4. For any of the following attributes whose value is smaller than the value recommended
here, increase it to the recommended value:
Table 9: Recommended MySQL parameter values

back_log=50
binlog_cache_size=1M
bulk_insert_buffer_size=128M
join_buffer_size=16M
key_buffer_size=512M
max_connections=150
max_connect_errors=10
max_allowed_packet=512M
max_heap_table_size=64M
query_cache_size=128M
query_cache_limit=4M
read_buffer_size=4M
read_rnd_buffer_size=8M
sort_buffer_size=2M
table_open_cache=512
thread_cache_size=8
thread_stack=192K
tmp_table_size=64M

6. Restart the service for MySQL Server.
83
October 2015
10.2 Locking and Terminating Idle Client Sessions

A configurable file in the WM file system includes two parameters for the operator to set as the
maximum idle time for an individual client session. The rules for this parameter are as follows:
 Upon server startup, the values of x in ALLOWED_IDLE_TIME_BEFORE_LOCKOUT="x"
and y in ALLOWED_IDLE_TIME_BEFORE_TERMINATION="y" are read from the
clientparameters.conf file in the following directories of the server file system:
− /usr/local/cambium/wm/server/conf/ in Linux or
C:\Cambium\WM\server\conf\ in Windows
− /usr/local/cambium/wm/server/users/root/ in Linux or
C:\Cambium\WM\server\users\root\ in Windows
− /usr/local/cambium/wm/server/users/guest/ in Linux or
C:\Cambium\WM\server\users\guest\ in Windows
− /usr/local/cambium/wm/server/users/EachOtherUser/ in Linux or
C:\Cambium\WM\server\users\EachOtherUser\ in Windows
 Although WM enforces the value that is read in the conf directory, it is recommended to
keep the values consistent in all three directories.
 Where x is 0, WM will never lock out any user for idle time.
 Where x is a number other than 0, WM will lock out any user whose session idle time
exceeds x minutes.
 Where y is 0, WM will never kill the session of any user for idle time.
 Where y is a number other than 0, WM will kill the session of any user whose session idle
time exceeds y minutes.
 Where both are non-zero and x is greater than y, a session will never be locked because the
session termination point is reached first.
 Where both are non-zero and y is greater than x, a session will first be locked, then
terminated after more idle time.
To set these values, perform the following steps.
Procedure 41: To establish session idle time limits

1. Open the first instance of the file clientparameters.conf.
2. Observing the rules stated above, change the value of x and/or y to a non-zero number of
minutes to enforce.
4. Open the second instance of the file.
5. Change x and/or y to values that are identical to those you set in Step 2.
7. Open the third instance of the file.
8. Change x and/or y to values that are identical to those you set in Step 2.
84
October 2015
11 User Scripts Setup

WM supports the execution of user-defined scripts as immediate or schedulable tasks. This feature
requires
 users authorized by a WM client administrator in the permissions tree of the client
application.
 tools that are
− properly scripted to execute the desired task.
− mounted in the ...\server\UserScripts directory by you, the server
administrator.
− made executable in their mode setting by you, the server administrator.
When you have mounted these scripts at the specified path
1. open a session in the WM client application.
2. execute the script. (See the user guide section titled "Running a User-defined Script.")
3. review the results of the execution. (See the user guide procedure titled "To view results of
last execution of a task.")
4. inform the client administrator(s) that authorized users will now be able to launch this script
from the task scheduler interface.
5. ensure that authorized users are informed that they are able to view and select the script
from the Details tab of the task scheduler interface.
85
October 2015
12 Management of WM Server Logs

The logging service is useful for various purposes such as identifying bugs, configuration errors,
and performance blockades; creating audits; and tracking user activities.
All messages are stored in the form of text files (.txt). All configuration information related to these
log files is available in the logging_parameters.conf file located in the
(or the C:\Cambium\WM\server\conf folder in Windows). The
logging_parameters.conf file contains the entries of various user-specified .txt files, such
as the maximum number of lines to be read from a file and the number of files to be included. The
following are among the most important attributes for which you may set values in this file:
 LogLevel
 FileName
 LogsDirectory
 MaxLines
 MaxLinesCached
You can configure the logging settings by editing the logging_parameters.conf file using the
Runtime Administration tool. Using this tool updates the file at runtime and eliminates the need for
a Wireless Manager Server restart after configuration. But if you have edited the file directly through
an editor, be sure to restart the Server.
Table 10: Log files present by default

Log file name Contents
alert_audit.txt In this file, information about all the alerts that are updated through events
are logged. New alert generation, alert deletion etc., are printed.
discoveryLogs.txt In this file, all discovery related happenings are logged. Addition/removal of
Networks/nodes, starting of NetSearcher, nodes or networks discovered etc.,
are logged in this file.
mserr.txt MangementServer Framework related error messages are stored in this file.
msout.txt ManagementServer Framework related output messages are stored here.
nmserr.txt All important Web NMS related error messages are logged into this file.
nmsout.txt All important Web NMS related output messages are printed in this file. This
is quite a comprehensive log file which holds record of happenings right from
server startup to the shut down. Module specific output message belonging
to "POLL""POLICY" "TOPO"EVENT" "ALERT" "MAP" "CONFIG" "PROV" "MISC"
"AGENT" "CLI" modules are logged by default.
stderr.txt By default, System Error messages are directed to this file. That is, if you use
System.err.println("Message") in your module, the error messages are
directed to this file, by default.
87
October 2015
Log file name Contents
stdout.txt By default, System Output messages are directed to this file. That is, if you
use system.out.println("Message") in your module, the output messages are
printed in this file, by default.
transactionLogs.txt All Prepared Statements obtained using the Connection Pool are recorded in
this file. By default, logging into transactionLogs.txt is disabled. To
enable it, edit the log4j.xml file and set Logging="true" for the
transactionLogs.txt entry.
By default, the following log files are present on the WM server in the
/usr/local/cambium/wm/server/logs directory in Linux
(or the C:\Cambium\WM\server\logs folder in Windows).
Although most of the important attributes to set are in the logging_parameters.conf file,
if you want WM to be able to send email, you will need to configure some attribute values in the file
/usr/local/cambium/wm/server/conf/log4j_conf.xml file in Linux
(or the C:\Cambium\WM\server\conf\log4j_conf.xml file in Windows).
These include
 the value for the SMTPHost parameter. This is the IP address of the SMTP server that will
handle outbound email from the WM server.
 the value of the To parameter. This is the account name and domain of the recipient of email
from the WM server.
 the value of the From parameter. This is the account name and domain that WM will use for
itself as the sender.

<appender name="mail" class="org.apache.log4j.net.SMTPAppender">
<param name="EvaluatorClass"
value="com.adventnet.management.log.MessageBasedTEE"/>
<param name="To" value="webnms-admin@adventnet.com"/>
<param name="From" value="webnms-admin@adventnet.com"/>
<param name="BufferSize" value="512"/>
<param name="Subject" value="LOG4j mail testing"/>
<param name="SMTPHost" value="192.168.4.41"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="[%d{dd MMM yyyy
HH:mm:ss:SSS}] %-5c{2}: %m%n"/>
</layout>
</appender>

88
October 2015
13 WM Software Upgrades and

Downgrades
13.1 WM Upgrade
Upgrade to WM Release 4.4 or later is supported from only the next earlier sequential release on
 Red Hat Enterprise Linux 5.x ES, 32-bit
 Red Hat Enterprise Linux 6.x ES, 32-bit
 CentOS 5.x, 32-bit
 CentOS 6.x, 32-bit
 Windows Server 2008 R2 Enterprise
 Windows Server 2012 R2 Standard Edition
No later version of Red Hat Enterprise Linux or of Linux from a different vendor is supported. Wireless
Manager requires specific versions of libraries to be located in certain places. Even later versions of
Red Hat Enterprise Linux fail to satisfy these library requirements. Cambium technical support cannot
help a user customize an OS to meet the requirements.
VMware vSphere is supported on the server device. When WM operates on a virtual machine,
additional RAM, above the RAM that is allocated to Virtual Machine and regardless of what actual OS
runs on the physical machine, is required for system performance. The amount of additional RAM
required is 4 GB.
Do not remove the previous release or any of the files that it created.
note ............. The following procedure includes the step "Copy your purchased licenses…" See License
Types and Calculation of the Number of Nodes to be Licensed.
Cambium Networks provides an integrated installation tool for Linux platforms and a similar tool for
Windows platforms for downloading by operators who want to install WM and optionally Prizm. This
tool is made available as part of the license procurement process. For information on licensing the
software products, contact your Cambium representatives. Also see the section titled WM Software
and Feature Licensing of this guide.
important ........... For instructions on a fresh installation, use the Cambium Wireless Manager Quick
Start Guide for the release being installed.
Procedure 42: To upgrade WM

1. Download the WM integrated installation tool for your platform (WMInstaller-4.4.x-
windows-installer.exe or WMInstaller-4.4.x-linux-installer.run).
2. Use the MD5 checksum provided at the download web site to verify that the tool was not
corrupted by the download.
3. If the device on which you are ready to upgrade WM software runs on a Linux OS
a. perform the following steps:
1) Log into the OS as root.
89
October 2015
2) At the OS command prompt, enter /usr/sbin/sestatus.

If Security-Enhanced Linux (SELinux) is already disabled (the system returns
-256), skip to Step 8.
If it is enabled (the system returns 0) continue.
3) Open the file /etc/selinux/config for editing.
4) Search for the string that begins with SELINUX=.
5) Revise the full string to SELINUX=disabled.
6) Search for the string that begins with SELINUXTYPE=.
7) Revise the full string to SELINUXTYPE=targeted.
8) Save and close the conf file.
9) Reboot the device to effect the change.
b. disable the firewall on the device.
4. Launch the installation tool.
Then the Introduction panel opens.
5. Click Next.
The License Agreement panel opens.
6. If you agree to the terms written in the License Agreement panel (scroll to read the entire
text), click the radio button for I accept the terms of the License Agreement and click Next.
note ............. If your OS is not explicitly supported for this WM release, the wizard provides the following
pop-up message.
90
October 2015
..................... If you want to install an explicitly supported OS in conjunction with the WM upgrade, see
Migration of Operator Data Through WM Upgrade Plus OS Upgrade.
7. Review the options in the Feature Selection panel.
note ............. In the next step, the tool detects the presence of the previous WM release,
License Manager, a MySQL Database on the device. Where these are present, the tool
will upgrade only Wireless Manager and leave the others as they presently exist.
Uncheck MySQL Database. If License Manager is already installed, uncheck it as well.
8. Leave the check box checked for each component that you want to install and click Next.
note ............. In the typical upgrade case, License Manager and the MySQL Database are still present
from the previous release, and the installation tool detects their presence.
91
October 2015
9. When the tool prompts for whether you want to continue given that the previous release
was detected, click OK.
10. After the confirmation(s), the tool prompts for your current database authentication
information, which it requires for proper installation of the System Reports feature in this
release.
11. Either accept the default root password by clicking Next or overwrite it, then click Next.
12. Either accept the default database username and password by clicking Next or overwrite
them, then click Next.
92
October 2015
13. Either accept the default read-only username and password and then click Next or overwrite
them, then click Next.
14. Ready to install panel opens. Click Next.
IT will install Wireless Manager on your system.
15. If your firewall asks whether to allow jre-6u6-x-exe, allow it.
93
October 2015
The installation wizard prompts for whether you want to start the Administrator Tool on the
final action page.
16. Mark the checkbox, if you want to launch Server Administration Tool after the installation is
finished. Do not mark it if you don’t want to launch the Server Administration Tool.
17. Click Finish.
The WM Administrator Tool opens if marked the checkbox to launch the Server Administration
Tool.
94
October 2015
18. In the left panel of the WM Administrator Tool interface, click Licensing.
The Licensing configurator open in the right panel of the tool interface.
19. If you are deploying three license servers, click the Redundant License Server radio button.
If not, leave the License Server button checked.
In the steps that follow, refer also to Using the Licensing Panel.
95
October 2015
20. For each License Manager (LM) server you are deploying, perform the following steps:
a. In the Hostname / IP text box, either
 leave localhost, if the LM server is local to the WM server.
 replace localhost with the dotted IP address of the LM server, if it is remote to
the WM server.
b. In the Server Port text box, either
 leave the default 27000 as the server port of the LM server, where license
requests from WM will be processed.
 replace 27000 with a port number that is unused in the LM server, if 27000 is or
may be used by another program.
c. In the Login Name text box, either leave the default lmadmin as the ID for the WM
Server Administrator Tool to use in authenticating itself to the LM server or replace it
with another ID.
d. In the Password text box, either leave the preconfigured password that is associated
with the lmadmin ID or replace it with another password for the Server Administrator
Tool to use in authenticating itself to the LM server.
e. In the Webserver Port text box, either
 leave the default 27443 for secure connections from the WM server to the LM
web server.
 replace 27443 with 27100 for non-secure connections to the LM web server.
21. In the License File Data panel of the WM Administrator Tool, click the Save Configuration
button.
The Administrator tool confirms the save operation.
22. In the License Actions block of the Licensing panel in the WM Administrator Tool interface,
click the Upload License button.
Figure 2: Command option to upload an individual license file to License Manager
23. Browse to and select a license to upload, then click Open.

See Figure 9.
note ............. If the file that you select is not a valid license file, the tool responds with an error.
24. In the Upload License File window, click the Upload button.
25. Repeat the above three steps until all WM-related licenses have been uploaded
(WMServerVx and WMEMSPackVx).
26. Confirm the license uploads by clicking the License Status button in the License Actions block
of the Licensing panel.
For an example of the resulting display, see Figure 10.
27. In the left panel of the WM Administrator Tool window, select WM Server.
28. In the Server Actions block of the WM Server panel, click the Stop WM Server button.
See Using the WM Server Panel.
96
October 2015
29. If you want WM to process authentication requests for PMP slave devices
a. procure a license to use BAM.
b. download Prizm software from
http://www.cambiumnetworks.com/support/management-tools/prizmbam/.
c. install Prizm Release 3.3 without the optional License Manager and Database
installations that the installation tool offers.
d. download Prizm documentation from the same site.
e. navigate to the .../Canopy/Prizm_bin directory.
f. launch the PrizmEMS Administrator Tool.
g. in the Server panel of the tool interface, set the Server Mode to BAM Only and click the
Save button.
h. from the main menu, select ActionPrizmEMS ServerStop.
i. verify that the services for License Manager and MySQL database are running.
j. in the License Manager panel of the PrizmEMS Administrator Tool, configure Prizm to
connect to the instance of License Manager that the WM installation tool installed.
k. in the Database panel of the PrizmEMS Administrator Tool
 configure Prizm to connect to the MySQL database that the WM installation tool
installed.
 if your WM server is on a Windows platform, then for Datasource Name (DNS),
enter prizm_mysql into the text box.
l. in the License Actions block of the Licensing panel of the WM Administrator Tool, select
Upload License. (See Using the Licensing Panel)
m. upload all of the following licenses
 BAM server license
 BAM packs
30. In the Server Actions block of the WM Server panel in the WM Administrator Tool, click the
Start WM Server button.
31. Optionally, close the WM Administrator Tool.
32. Launch your web browser.
33. Navigate to http://localhost:9090.
If the server has been properly configured, your browser will be redirected to the launch
web page.
97
October 2015
If a problem exists, then this web page includes a warning. In this warning case, the Launch
WM Client operation may open an error message instead of the client interface. If this
occurs, click the license log link to troubleshoot the licensing configuration.
13.2 Migration of Operator Data Through WM Upgrade

Plus OS Upgrade
To preserve configuration and performance data from the previous release into the new release
while also upgrading the OS of the server device, perform the following high-level process.
Procedure 43: To migrate operator data in upgrade of WM plus the OS

1. If the new release will be installed on a computer other than where your current WM
release is installed, order a full set of replacement licenses.
important ........... See Network Interface Management and License Types.
2. According to the section WM Upgrade, upgrade the WM software.
3. Using the WM user guide that supports the new release, verify that the new release is
operating as expected.
4. Double-click the desktop icon labeled WM Server Administration.
5. In the left panel of the resulting WM Administrator Tool dialog, select WM Server.
(See Using the WM Server Panel.)
6. In the right panel, click the Server Actions block Stop WM Server button and leave the
WM Administrator Tool open.
note ............. This breaks the connection of the client session. A pop-up confirmation asks whether you
want to exit the client.
7. Click the Yes button to remove all the open client interface windows.
8. In the System Backup block of the right panel in the WM Administrator Tool, click the
System Backup button.
98
October 2015
note ............. This backs up the server data to a new directory that the operation creates:
C:\Cambium\WM\server\backup\WM_Data_Backup\ or
/usr/local/cambium/wm/server/backup/WM_Data_Backup. The data file
that it places in the new directory is *.WMBACK.
9. Copy the following data to a repository on other than the server device:
◦ the output file *.WMBACK produced in Step 10
◦ all licenses
◦ any other files that are important to your operations
10. Close the WM Administrator Tool.
11. Upgrade the OS (or install the new OS).
12. Copy the license files from the repository onto the device on which you installed the new OS.
13. According to the procedure in the quick start guide that supports a fresh installation of the
new release, install all three components: the new WM release, MySQL database server, and
License Manager.
important ........... Do not start the WM service yet.
14. Double-click the desktop icon labeled WM Server Administration.

15. In the left panel of the WM Administrator Tool interface, select Licensing.
16. According to the section Using the Licensing Panel, upload your licenses to License Manager
and leave the WM Administrator Tool open.
17. In the left panel of the WM Administrator Tool, select WM Server.
18. In the right panel, click the Server Actions block Start WM Server button and leave the
WM Administrator Tool open.
20. Open the WM Administrator Tool to its WM Server panel.
21. In the WM Administrator Tool, click the Stop WM Server button and leave the WM
Administrator Tool open.
22. Copy the remaining contents of the repository (including the file *.WMBACK) to the
directory C:\Cambium\WM\server\backup\WM_Data_Backup\ or
/usr/local/cambium/wm/server/backup/WM_Data_Backup in the new
instance of WM.
23. In the WM Administrator Tool, click the System Backup button.
24. Point the backup utility to the file *.WMBACK.
25. When the utility is finished, click the Start WM Server button in the WM Administrator Tool.
99
October 2015
13.3 WM Downgrade
note ............. In case you elect to restore your system to a backed up copy in connection with the
downgrade, be aware that network element performance data that was collected between
the time of a backup and the time of its restore is present after the restore.
No downgrade path exists to retreat from the current release to any earlier release. To do this, you
must uninstall the current release and then re-install the earlier release. The installation tool for the
current release placed its uninstallation tool at
 C:\Cambium\WM\Uninstall\Uninstaller.exe in Windows.
 /usr/local/cambium/wm/Uninstall/Uninstaller.bin in Linux.
note ............. After the uninstallation tool finishes, you may or may not encounter the following error
message in a pop-up window: Unknown or newerVersion Installation
Detected. An instruction to remove the /etc/init.d/wmserver file may be
included in this window, regardless of whether the OS is Windows or Linux. This error may
be thrown under a variety of circumstances such as low resources, competing processes,
or an interruption of uninstallation tool processes. Typically though, regardless of what
circumstance triggers the error, the result that triggers the error is corruption of the
InstallAnywhere Registry file. Continue through this section to resolve the error.
If you ran the Uninstaller script to remove WM and to remove License Manager at the same time,
then you must remove from the registry file the feature tags for product names
...Wireless Manager... , ...License Manager, and for component name LinLIC or
WinLIC. This is essential for any subsequent installation that checks for the presence of License
Manager to succeed. Examples of the contents from a registry file follow.
100
October 2015
- <product name="Cambium Networks Wireless Manager 4.0" id="c45ac526-1ee9-11b2-b9f1-

da59c1a72547" version="4.0.4.0" copyright="2012" info_url="" support_url=""
location="C:\Cambium\WM" last_modified="2012-02-16 20:46:32">
<vendor name="" id="c45ac516-1ee9-11b2-b9f1-da59c1a72547" home_page="" email="" />
- <feature short_name="WMS" name="WMS" last_modified="2012-02-16 20:45:27">
- <![CDATA[
<Enter Product Feature description here -- do not forget to assign this Feature to desired Install Sets>
]]>
<component ref_id="d34cf756-1ee9-11b2-bf14-da59c1a72547" version="1.0.0.0"
location="C:\Cambium\WM\perl-DBI-1.40-8.i386.rpm" />
<component ref_id="c45ac565-1ee9-11b2-b9fb-da59c1a72547" version="1.0.0.0"
location="C:\Cambium\WM\jre" />
<component ref_id="c4633bf4-1ee9-11b2-bbdf-da59c1a72547" version="1.0.0.0"
location="C:\wmserver" />
</feature>
- <feature short_name="MySQL S" name="MySQL Server" last_modified="2012-02-16 20:46:08">
- <![CDATA[
]]>
<component ref_id="d34cf756-1ee9-11b2-bf14-da59c1a72547" version="1.0.0.0"
location="C:\Cambium\WM\perl-DBI-1.40-8.i386.rpm" />
<component ref_id="c45ac565-1ee9-11b2-b9fb-da59c1a72547" version="1.0.0.0"
location="C:\Cambium\WM\jre" />
<component ref_id="d303eec7-1ee9-11b2-857a-da59c1a72547" version="1.0.0.0"
location="C:\Cambium\WM\mysql-enterprise-5.1.48-win32.msi" />
</feature>
- <feature short_name="JRE" name="JRE" last_modified="2012-02-16 20:46:09">
- <![CDATA[
]]>
<component ref_id="6140fa12-1eee-11b2-a328-c06f25b923f3" version="1.0.0.0"
location="C:\Cambium\WM\jre-6u6-linux-i586.rpm" />
</feature>
- <feature short_name="MS-VC++2005" name="MS-VC++2005" last_modified="2012-02-16
20:46:17">
- <![CDATA[
]]>
<component ref_id="de73334a-1ef3-11b2-832f-c06f25b923f3" version="1.0.0.0"
location="C:\Cambium\WM\visual_c_plusplus_2005_sp1_redist_x86.exe" />
</feature>
- <feature short_name="License" name="License Manager" last_modified="2012-02-16 20:46:32">
- <![CDATA[
]]>
<component ref_id="dad51170-1ef3-11b2-8422-c06f25b923f3" version="1.0.0.0"
location="C:\Cambium\WM\license_manager.exe" />
</feature>
</product>
101
October 2015
</product>
- <product name="WM License Manager" id="925168a8-1ef3-11b2-b8b7-c06f25b923f3"
version="4.0.1.0" copyright="2004-2012" info_url="www.canopywireless.com"
support_url="www.canopywireless.com/support" location="C:\Cambium\LicenseManager"
last_modified="2012-02-16 20:49:29">
<vendor name="Cambium Networks" id="5678ffb6-1ee9-11b2-8d91-da59c1a72547"
home_page="www.cambiumnetworks.com" email="technical-support@canopywireless.com" />
- <feature short_name="LicMgr" name="License Manager" last_modified="2012-02-16 20:49:29">
- <![CDATA[
Install Prizm License Manager Server and License Manager Admin Web Server.
]]>
<component ref_id="6ed1feae-1eed-11b2-9b06-a704e97cb190" version="4.0.1.0"
location="C:\Cambium\LicenseManager\Uninstall\Uninstaller.exe" />
<component ref_id="6effe344-1ee8-11b2-b1bf-da59c1a72547" version="4.0.1.0"
location="C:\Cambium\LicenseManager\_jvm" />
<component ref_id="1a26b7de-1ef5-11b2-843b-c06f25b923f3" version="4.0.1.0"
location="C:\Documents and Settings\Administrator\Start Menu\Programs\Cambium
Networks\LicenseManager\License Files.lnk" />
</feature>
</product>
- <components>
<component id="1a26b7de-1ef5-11b2-843b-c06f25b923f3" version="4.0.1.0" name="WinLIC"
location="C:\Documents and Settings\Administrator\Start Menu\Programs\Cambium
Networks\LicenseManager\License Files.lnk" />
<component id="6effe344-1ee8-11b2-b1bf-da59c1a72547" version="4.0.1.0"
name="InstallAnywhere VM Component" location="C:\Cambium\LicenseManager\_jvm"
vendor="Cambium Networks" />
<component id="c4633bf4-1ee9-11b2-bbdf-da59c1a72547" version="1.0.0.0" name="AG-
Application, Install" location="C:\wmserver" />
<component id="d303eec7-1ee9-11b2-857a-da59c1a72547" version="1.0.0.0" name="AG-
Install, MySQL D" location="C:\Cambium\WM\mysql-enterprise-5.1.48-win32.msi" />
<component id="dad51170-1ef3-11b2-8422-c06f25b923f3" version="1.0.0.0" name="AG-
License" location="C:\Cambium\WM\license_manager.exe" />
<component id="c45ac565-1ee9-11b2-b9fb-da59c1a72547" version="1.0.0.0"
name="InstallAnywhere VM Component" location="C:\Cambium\WM\jre" />
<component id="d34cf756-1ee9-11b2-bf14-da59c1a72547" version="1.0.0.0" name="AG-
Install, MySQL D" location="C:\Cambium\WM\perl-DBI-1.40-8.i386.rpm" />
<component id="6140fa12-1eee-11b2-a328-c06f25b923f3" version="1.0.0.0" name="AG- JRE"
location="C:\Cambium\WM\jre-6u6-linux-i586.rpm" />
<component id="de73334a-1ef3-11b2-832f-c06f25b923f3" version="1.0.0.0" name="AG- MS-
VC++2005" location="C:\Cambium\WM\visual_c_plusplus_2005_sp1_redist_x86.exe" />
<component id="6ed1feae-1eed-11b2-9b06-a704e97cb190" version="4.0.1.0" name="AG-
PrizmEMS, LicMgr, Postgres" location="C:\Cambium\LicenseManager\Uninstall\Uninstaller.exe"
vendor="Cambium Networks" />
</components>
102
October 2015
In Windows, this file is

C:\Program Files\Zero G Registry\.com.zerog.registry.xml. Access to both
this folder and this file require that Explorer is configured to display hidden folders. If it is not already
configured to display them, perform the following steps:
1. Navigate to the folder Zero G Registry.
2. From the main Windows menu, select ToolsFolder Options.
3. Click the View tab.
4. Select Hidden files and foldersShow hidden files and folders.
5. Click the Apply button.
6. Open the file .com.zerog.registry.xml for editing.
7. Remove the contents described above.
9. Optionally, back in the Folder Options window, select Do not show hidden files and folders.
In Linux, this file is /var/.com.zerog.registry.xml.
If you ran the Uninstaller script to remove the WM release that was installed as an upgrade, then the
script did not prompt for whether to uninstall MySQL Server. The following remaining packages could
interfere with a subsequent WM installation and cause the installation tool to throw the error
MySQL server detected:
 MySQL-server-enterprise-version.rhel4
 MySQL-client-enterprise-version.rhel4
If you uninstalled MySQL Server without using the WM Uninstallation script, then be aware that your
uninstallation did not remove the data directory.
103
October 2015
14 WM Software and Feature Licensing

WM requires License Manager software, distributed by Cambium Networks, to enforce the license
requirements and to broker flexible unused licenses. License Manager server itself does not require a
license to function. However, the licenses that WM requires are locked to the MAC address of the
device(s) where License Manager resides. One single or three redundant License Manager servers are
supported.
Operators must ensure that the License File Data panel of the WM Administrator Tool continuously is
populated with correct information for
 either the host name or the IP address of each License Manager server.
 port numbers for each License Manager server and its web server.
 the login name and password for WM to use from its API when returning to and requesting
from each License Manager server any flexible licenses that are not currently in use.
Operators may deploy License Manager local or remote to the WM server.
If all License Manager servers fail or lose connectivity with the WM server, licenses that are already
checked out by managed devices remain valid and WM continues to manage the licensed elements
without restriction or interruption, but any attempts by WM to check out an unused license will fail
until the server or its connection recovers. Attempts to return a license that had been used by a now-
deleted element or a newly unmanaged element will succeed and will be re-synced with License
Manager when its server comes back up.
14.1 License Types

The WM server itself requires the purchased license type WMServer. This type is ordered and
deployed in a denomination based on a count of the number of servers that will share the license.
An installed WM server will not start if it is not licensed by this scheme. All licenses of all three types
are locked to the MAC address of the WM server that will use and manage them.
The features supported by WM are licensed by a practicable number of WMEMSPack purchased
licenses, one for each device of a licensed device type. When no free floating license of this type is
available and a new element is discovered, WM automatically generates a major alert stating that a
license checkout attempt for the element failed. When one becomes available, WM on subsequent
discovery automatically obtains it from License Manager and begins to manage the element.
14.2 Calculation of the Number of Nodes to be Licensed

The WMEMSPack license counts are hosted from only the machine that hosts License Manager.
To order a license of this type, you must know the number of nodes that you need it to cover.
The following factors affect that number:
 the device type determines whether and how a node is counted against the WM license
limit.
 each network element of the following types is not counted as a node:
− PMP Series SM
− PTP Series slave, except for PTP 810 slaves
105
October 2015
 each device of a multi-agent device is counted as one node:

 each Cambium device of a type not specifically noted in this list counts as one node.
 each third-party device (SNMP-enabled non-Cambium device) for which you have created a
valid device definition template.
 each generic device (SNMP-enabled non-Cambium device for which no valid device
definition template exists) counts as one node.
Following the upgrade
1. the operator should upload a valid license of appropriate device count.
2. during server startup, the number of devices that are already stored in the database is
counted against the device license count. If a sufficient count is not available for them, then
the server startup fails.
3. during the first and any subsequent auto discovery, all new discovered nodes that the new
WM release classifies as countable are licensed and added to that count, even if some pre-
existing nodes in the database are yet to be rediscovered.
Following the first auto discovery, the count of licensed nodes is no longer affected by the number of
nodes that had been contained in the database in the previous release.
14.3 Notifications of License Limits

A WM server checks out one count of the license specified in the WMEMSPack license whenever a
device other than a PMP Series SM or PTP Series Slave is discovered and managed by WM. When the
number of checked out license counts at the license server reaches 90% of the total license counts,
WM throws a modal dialog window to users in current sessions and to users who are launching the
client application, warning that more WMEMSPack license capacity will be required. When the
number exceeds the total of licenses, no license will be made available for check out until a licensed
device is deleted from a network and thereby forfeits the floating license that it held.
14.4 WM License Replacement

If you are using a time-bound license to operate the WM application, plan ahead and have a
replacement license ready by the time the existing one expires. WM does not warn the operator that
a license is near expiration and will not restart after it does expire.
This section assumes that the replacement license has been procured and copied to a folder on the
server, and that an active Ethernet connection exists in the server device. To replace a WM server
license, use the instructions that Procedure 42 of this guide provides, beginning with its Step 13.
14.5 Recovery From Forgotten Password for the License

Manager Administrator Tool
If you ever forget the password of the License Manager Administrator Tool, you will need to reset it in
the License Manager server. To do so, perform the following steps.
106
October 2015
Procedure 44: To reset the License Manager Administrator Tool password

1. On the License Manager web server device, stop the service WM License Manager Web
Server. How to do this depends on your OS and, in the case of Windows, your Control Panel
view toggle. An example for Windows XP Professional is as follows:
a. Select StartControl Panel.
b. Select Switch to Classic View.
c. Double-click Administrative Tools.
d. Double-click Services.
e. Click the column head Name .
f. Click to highlight WM License Manager Web Server.
g. In the left panel, click Stop the service.
2. If your License Manager Administrator Tool is on a Windows device, open the file
C:\Cambium\LicenseManager\FLEXnet\api\www\config\licensing.xml
on that Windows server.
If your License Manager Administrator Tool is on Linux, open the file licensing.xml
in/usr/local/cambium/LicenseManager/FLEXnet/api/www/config/ on
that Linux server.
3. Find the line that is similar to the following:
<server port="27000" webServerPort="27443" username="lmadmin"
host="localhost" password="mypXJ8T7AW3GXzK+NvSzeg==" />
4. Delete the contents of the password attribute of the server tag and the admin tag.
RESULT: The line now reads as follows:
<server port="27000" webServerPort="27443" username="lmadmin"
host="localhost" password="" />
<admin password="" username="lmadmin"/>
6. Restart the License Manager web server.
NOTE: This causes the web server to read the null current contents of the password
attribute.
7. Launch the License Manager web site.
8. Log in, leaving the password field blank.
9. Click the Password button in the License Manager panel.
10. Populate the password.
Launch the WM Server Administrator Tool.
11. In the left panel of tool interface, click on License Manager.
12. Update the contents of the Password field in the License File Data panel.
RESULT: The Administrator Tool will be able to use this new password to upload future
license files into License Manager.
107
October 2015
After you have reset the password but before you use the License Manager Administrator Tool web
site to configure and install license files, you must click the link for Licensing Configuration, then
change the password for the local server and click the Save Changes button. Then you can upload the
license to the local License Manager.
14.6 Deployment of Redundant License Manager

Servers
14.6.1 Purpose of Redundancy

Redundancy of License Manager servers is an advanced form of deployment, used only to provide
protection in failover cases. This deployment is not for load sharing.
The administrator must configure and maintain a set of three license servers that together serve a
single set of licenses. Only the one that is designated as the master supplies the licenses to WM. In a
three-server deployment, at least two license servers are required for licenses to be served. If two of
the servers go down via failure and/or reboots, the deployment fails and can be reestablished only by
properly restarting the servers. During the outage, licenses cannot be checked out, but previously
assigned licenses remain assigned.
14.6.2 Configuration of License Key Files for Redundancy

When you identify three servers for License Manager redundancy, you must ensure that they meet
the following standards:
 They share fast and reliable links.
 They all exist within the same subnet.
 Each has a valid hostname other than localhost or localhost.localdomain.
When you request licenses to be managed by redundant servers, you must provide the MAC address
of each of the three servers.
By the time that you upload these licenses into the three servers, the MAC address of all License
Manager servers must be listed in identical order in every license key file on each server. Example
contents of a license key file is as follows:
SERVER 172.16.5.8 0019bbdc013c 27000
SERVER 172.16.3.33 000bdbc56b9b 27000
SERVER 172.16.4.108 001ec938a5d9 27000
VENDOR motocnpy
USE_SERVER
The server details must be in the primary, secondary, and tertiary license server order. If their
sequential order in any file differs from the order in any other license file held among the three
servers, license administration fails. If you wish, you can change the server list to an order different
from the order you received from Cambium Networks. However, if you do, you must make identical
changes to all licenses on all servers.
108
October 2015
14.6.3 Redundancy Deployment Process

To deploy redundant License Manager servers, perform the following steps.
Procedure 45: To deploy redundant license servers

1. On each of the three machines, ensure that the hosts file contains a valid mapping of its
IP address to its host name (localhost.localdomain is not valid).
2. Ensure that the WM License Manager is installed on each of the three machines.
3. Stop the License Manager service.
4. In the License Manager web server, navigate to the
LicenseManager\FLEXnet\api\www\config directory.
5. Open the file licensing.xml for editing.
6. Change host="localhost" to host="MachineIPAddress".
7. Write and close the file.
In the steps that follow, refer also to Using the Licensing Panel.
8. Upload the license files, even if they were previously uploaded.
note ............. This step resolves the this_host entry for SERVER in each license to the appropriate
IP address.
9. Start the License Manager service.
10. Check whether more than one license has been uploaded into any of the three machines.
note ............. This can be done by checking the license status page of the three machines. Only one
license should be available for the dummy feature.
11. If any machine has more than one uploaded license, perform the following steps:
a. Stop the License Manager web server and License Manager.
b. From the directory
C:\Cambium\LicenseManager\FLEXnet\license_files in Windows
(or /usr/local/cambium\LicenseManager\FLEXnet\license_files
in Linux), delete every license file except dummy.lic or dummy.lic.RENAMED.
c. If the latter file is present, rename it to dummy.lic.
d. Start the two servers.
12. On each License Manager web server that will be used as the redundant server, perform the
following steps:
a. Log on to the License Manager web server.
b. Click the Licensing Configuration link.
109
October 2015
Figure 3: Licensing Configuration panel in License Manager web server
c. In the Licensing Configuration web page, select the Redundant Server check box.
d. Enter the license server IP, license server port, license web server user name, password,
and port.
important ........... Ensure that the IP addresses are in sequence of primary, secondary, and then tertiary
server and that the order is identical in every license file among the three servers.
Also ensure that all IP addresses are routable from each of the servers.
e. Click the Save Changes button.
13. Log on to the web server interface of the primary license server.
14. Click the Upload License File link.
15. Upload the license files.
16. Repeat Steps 6 and 7 on the secondary and tertiary servers.
17. All the licenses should be uploaded to the required license servers.
18. Check the directory C:\Cambium\LicenseManager\FLEXnet\license_files
in Windows or
/usr/local/cambium\LicenseManager\FLEXnet\license_files in Linux to
ensure that the file names are present.
note ............. Do not use simple file copying to place these files into the directory. Use the scripted
Upload License File selection.
19. Further check the licenses for their status as follows:
a. Log on to the web server interface of the primary license server.
b. Click the Licensing Status link.
110
October 2015
Figure 4: Licensing Status panel in License Manager web server
c. Check that the status report shows the total number of licenses that you expect to see.
d. Log on to the web server interface of the secondary server.
e. Check the status report for consistency with that from the primary server.
f. Log on to the web server interface of the tertiary server.
g. Check the status report for consistency with those from the other two servers.
111
October 2015
14.7 Workaround for a License Server Failure
14.7.1 Failure or Reboot of a License Manager Server

Restarting License Manager is necessary in any of the following cases:
 Two of three servers go down because of a failure or a reboot.
 Only two servers were deployed, and one is down because of a failure or reboot.
 A standalone server is down because of a failure or reboot.
Whenever you have restarted License Manager, restart the WM server.
14.7.2 Change in the IP Address of a License Manager Server

If the IP address of any of the three redundant licensing servers changes, perform the following steps:
1. Update the redundant server configuration on each of the license web server.
2. Stop the License Manager service on all three servers.
3. In the WM server, navigate to the …/LicenseManager/FLEXnet/license_files
directory.
4. If the name of the dummy.lic file changed to dummy.lic.RENAMED, then rename it to
dummy.lic.
5. Except for dummy.lic, delete the existing license files in the folder.
6. In all license files received from Cambium Networks, update the IP address of the machine
whose address changed.
note ............. Ensure that the changed line has the MAC address of that machine only.
7. Upload these changed license files.
8. Start the License Manager in the order primary, then secondary, and then tertiary server.
9. In the Licensing Status link (Figure 4), verify that all the licenses are properly uploaded.
14.7.3 Server Restarts in LM Redundancy

For restarting the redundant License Manager, all three must be restarted so that the whole setup is
ready to be used. The order of restarting must be primary, then secondary, and then tertiary server.
112
October 2015
15 WM Administrator Tool for Server

Administration
To launch this panel from the main menu in the WM client, select
ToolsAdministrationServer Administration.
The defaults for the various panels of the WM Administrator Tool are as shown in this section. The
fields that require attention in a typical setup are noted in other sections of this guide.
If you perform any action in one of these panels and then attempt to leave the tool or access another
panel with applying your changes, the GUI prompts you for whether you want to apply them:
15.1 Using the WM Server Panel

The WM Server panel contents depend on whether you launch the WM Administrator Tool from
 the bin directory in the server file system (run or ServerAdminTool.bat or
ServerAdminTool.exe). This version of the panel includes the backup and restore
options as described in this section.
 the main menu in the WM client (select ToolsAdministrationServer Administration; in
the left panel of the resulting WM Administrator Tool dialog, select WM Server), even if the
device you are launching it on is the device where the server resides. This version of the
panel excludes the backup and restore options, includes resync options instead, and is as
described in the section of the user guide that covers this panel.
113
October 2015
Figure 5: WM Server panel of WM Administrator Tool launched from executable
The System Backup option copies all information that is necessary to later return the system to the
current state. This includes the entire database and all essential files of the WM server file system.
important ........... Do not launch a backup while the WM server is running, because this can result in
inconsistency between the contents of the backup and the contents of the database.
note ............. Although the backup utility supports running while the WM service is up, it cannot keep
stride with changes made via the Web Start client while the script is running. Thus, it is
necessary to ensure that no Web Start client session is in progress at any time between
when this script is launched and when it is finished. If a client session is running during the
execution of the script, then a warning message informs the user of the backup operation
and advises that all current requests will be satisfied when the backup is complete.
The Restore System option replaces the current database and all essential files of the WM server file
system with the those that were last copied using the System Backup command option. However,
network element performance data that was collected between the time of backup and the time of
restore is present after the restore.
These operations cannot be performed in the client unless the client is local to the WM server. Other
client sessions that continue to run during the System Backup cause at least confusion about what
has been backed up, in that the results of its current and later operations are not recorded into the
backup. For this reason, WM throws an error into those client sessions, indicating that it will pause
until the remote backup (on the server device) has concluded.
The following are not supported restore scenarios, although they may succeed in certain cases:
 Restore System of the backup data that was created on another machine.
 Restore System on the same machine, but where the database backed up was of a different
MySQL version from the MySQL version that is on the target device.
114
October 2015
Although the remote clients have this panel in their version of the WM Administrator Tool, the panel
there does not include the System Backup block shown above.
The Server Actions block of this panel is also specific to whether the server is local:
 In a client session on the local WM server
− Stop WM Server is active when the server is running. When this option is invoked,
WM proceeds to shut down without throwing a warning or a confirmation.
− Start WM Server is active when the server is not running.
− Restart WM Server is active when the server is running. When this option is invoked,
WM throws a pop-up message into client, saying that the connection has been lost and
prompting for whether to close the client or resume the session when the server comes
back up.
note ............. Start differs from restart as follows: Start commands start the service; in a two-step
automatic operation, Restart commands stop the running service and then restart it.
 In a client session remote to the WM server, neither the Server Actions block nor any of the
command options described above are present.
The function invoked by the NE Re-Sync and NE Re-Sync after backup buttons is to remove the
events and alarms of all the managed elements as well as their traps that WM is currently processing,
and to refresh their status, but to allow their statistics to continue to be stored. If you select either of
these, WM throws a warning.
This amount of status polling consumes a significant amount of resources. Consider this advisory
carefully before you consider confirming by clicking the Yes button.
115
October 2015
15.2 Configuring the BAM Panel

ToolsAdministrationServer Administration; in the left panel of the resulting WM Administrator
Tool dialog, select BAM.
Figure 6: BAM panel of WM Administrator Tool
The BAM Configuration block defaults to the following attribute values.
To make any changes from the defaults, click in the Value cell. This transforms the cell from read-only
data into a text box. Type in the substitute value. Then, to return the cell to read-only, click elsewhere
in the table (in the Attribute column or one of the column headings, for example).
BAM privileges are essential to its management functionalities, and each mapped privilege must be at
the System Administration (A) level.
116
October 2015
15.3 Configuring the Database Panel

note ............. Although the WM Administrator Tool provides GUI access to execute database backup
and restore, these options are not included in the Database panel. See Using the WM
Server Panel.
Tool dialog, select Database.
Figure 7: Database panel of WM Administrator Tool
WM encrypts the database Password such that it is never readable in either the WM server file
system or the WM client. However, any change that you make in the Password field of this panel
must reflect the password that is configured in MySQL.
The Reset button returns all of the values to their defaults. Since these are all connection-related
attributes, the Reset operation does not return the original database schema as well. If you changed
the table structure or deliberately altered any other SQL settings and now need to revert to the
117
October 2015
configuration that the WM installation tool had installed, perform the steps of Procedure 10: To
restore the installed WM database configuration.
The Test button launches a test of the connection between WM and the database, using the current
settings in this panel. When the values are properly set, the expected result of the connection test is
the following pop-up message:
15.4 Using the Licensing Panel

One single or three redundant License Manager servers are supported. One of these may be local to
the WM server. See WM Software and Feature Licensing.
This panel configures how WM communicates with the licensing server(s) and also provides options
to start, stop, and restart License Manager, and to upload license files into License Manager. To
launch this panel from the main menu in the WM client, select
Tool dialog, select Licensing.
Figure 8: Licensing panel of WM Administrator Tool
note ............. Start differs from restart as follows: Start commands start the service; in a two-step
automatic operation, Restart commands stop the running service and then restart it.
118
October 2015
Changes that you save and licenses that you upload are reflected in the file
.../server/conf/licensing.xml. Restart LM is not necessitated by license uploads.
The Upload License option opens a browser to the local file system.
Figure 9: Upload License File dialog
An example of License Status information is as follows.
119
October 2015
Figure 10: License Manager Status display window
...
120
October 2015
15.5 Configuring the NBI Panel

The Northbound Interface (NBI) provides an SNMP-based Java Management Extension (JMX) agent
for other management systems to poll WM for information about its managed objects, events,
alarms, and performance data.
The NBI panel configures the agent of WM. To launch this panel from the main menu in the WM
client, select ToolsAdministrationServer Administration; in the left panel of the resulting WM
Administrator Tool dialog, select NBI.
Figure 11: NBI panel of WM Administrator Tool, active SNMP V3 settings
The NBI panel allows you to change the NBI passwords for SNMPv3-based security.
 The Auth Password field is the SNMPv3 Authentication password.
 The Priv Password field is the SNMPv3 Privacy password.
To use the V3 agent, you must provide both. The default passwords are authPassword and
privPassword, respectively.
The two SNMP settings blocks of this dialog are active only if they have context in the selected
SNMP Version.
121
October 2015
Figure 12: NBI panel of WM Administrator Tool, active SNMP V1/V2 settings
To make any change in the Trap Forwarding Configuration table, you must first check the
Enable Trap Forwarding check box. After this is done
 to change an existing configuration, double-click the cell whose contents you want to change
and type the new content into the resulting text box there.
 to remove an existing configuration, click the highlight the configuration you want to delete;
then click the Remove Trap Forwarding button.
 to add a configuration, click the Add Trap Forwarding button; then for each column, double-
click in the blank cell and type the contents into the resulting text box.
To enforce all of the changes you have made in this dialog, click the Apply button. To dismiss the
dialog, click the OK button.
important ........... To ensure WM security, these passwords should be changed soon after installing
WM.
15.6 Using the Offline Physical Map Panel

The use of this tool interface presumes that you have configured offline map layers in GeoServer. This
tool makes those layers available to WM by specifying the image layers, pointing WM to the proper
connection parameters for communication with GeoServer, and switching on the optional offline
physical map feature. Instructions and background information for the GeoServer setup are provided
under Offline Physical Map Setup.
Tool dialog, select Offline Physical Map.
122
October 2015
Figure 13: Offline Physical Map panel of WM Administrator Tool
note ............. The following operations require both a click of the Apply button and a new client session
in order to be reflected in the client: Enable offline physical map, Add Layer, and
Delete Layer.
To set up WM to use the image layers that you have configured in GeoServer, perform the following
steps:
Procedure 46: To configure WM for offline physical map images

1. Check the Enable offline physical map check box.
2. Click the Add Layer button.
3. In the new null row of the Offline Map Layers table, click in the Display Name column.
4. Compose a name by which you will recognize the layer.
5. Click in the Layer Name column.
6. Type in the name of the layer or layer group as it was specified in GeoServer.
7. Click in the GeoServer Host / IP column.
8. Type in the IP address of remote GeoServer or localhost, if GeoServer is local to the WM
server.
9. Click in the GeoServer Port column.
10. Type in 8080.
11. Click the Test Layer button.
This launches the demo view of the GeoServer web cache for the currently selected layer or
layer group.
123
October 2015
12. For any layer or layer group that is not yet seeded in GeoServer, optionally click the
Seed Layer button and configure the threads as described above.
13. To optionally launch the GeoServer home web page, click the Launch GeoServer button.
14. Click the Update button (not shown in Figure 13 above) to write the layer information to
an xml file in the WM server file system for use from the WM client application.
The system responds with the Information message
Successfully updated offline maps configuration. Please
restart your client for the changes to take effect.
To later make changes in the configuration of a layer, perform the following steps.
Procedure 47: To reconfigure offline physical map images in WM

1. Click the cell that you want to edit.
2. Overwrite its textual contents.
3. Click the Apply button.
4. When finished in the Offline Physical Map Configuration panel, either
◦ click another link in the left panel to work in the desired other panel of the tool.
◦ click the OK button to dismiss the WM Administrator Tool interface.
15.7 Configuring the Email Configuration Panel

For several various purposes, the WM client allows you to compose email to configurable recipient
addresses for immediate, delayed, or conditional sending. These instances include email
 triggered by
− an event filter.
− an alarm filter.
− an escalation policy.
 to communicate a notice to one or more customers of your network services.
 to accompany data gathered to inform technical support efforts.
In a single panel, the WM administrator tool allows you to specify or reconfigure the settings that
determine how these emails will be processed. To launch this panel from the main menu in the WM
client, select ToolsAdministrationServer Administration; in the left panel of the resulting WM
Administrator Tool dialog, select Email Configuration.
124
October 2015
Figure 14: Email Configuration panel of WM Administrator Tool
To configure these settings, perform the following steps.
Procedure 48: To configure server and admin email settings

1. For SMTP Server Host, replace SMTP_SERVER_HOST with the host name of your local
SMTP server.
2. If you want to reconfigure the port attributes, perform the following steps:
important ........... The remaining fields of the SMTP Server block in this tool are read-only by default.
The following substeps optionally insert a set of values into two separate executable
files. The set of values must be identical in each file, as in the examples provided with
the substeps. If you want to keep the default read-only values, proceed to Step 3
now.
a. Open the ServerAdminTool.sh or ServerAdminTool.bat file located in
/usr/local/cambium/wm/server/bin/ directory in Linux (or the
C:\Cambium\WM\server\bin\ folder in Windows).
b. Search for the following string:
com.motorola.wibb.ems.platform.servertools.serveradmintool.ui.ServerAdminTool.
c. Prepend the following:
-Dsmtp.port=port -Dsmtp.sslport=sslport -Dsmtp.secure=true|false
Example:
-Dsmtp.port=25 -Dsmtp.sslport=465 -Dsmtp.secure=true
com.motorola.wibb.ems.platform.servertools.serveradmintool.ui.ServerAdminTool
sets the SMTP port to 25, the SSL port to 465, and SSL to enabled.
125
October 2015
d. Write and close this file.

e. Open the startWM.sh or startWM.bat file located in
/usr/local/cambium/wm/server/bin/ directory in Linux (or the
C:\Cambium\WM\server\bin\ folder in Windows).
f. Search for the string com.adventnet.nms.startnms.NmsMainBE.
g. Prepend the following:
-Dsmtp.port=port -Dsmtp.sslport=sslport -Dsmtp.secure=true|false
Example:
-Dsmtp.port=25 -Dsmtp.sslport=465 -Dsmtp.secure=true
com.adventnet.nms.startnms.NmsMainBE
sets the SMTP port to 25, the SSL port to 465, and SSL to enabled.
h. Write and close the file.
3. If you want WM to require users to authenticate themselves before they are allowed to send
email or configure email for later sending, perform the following steps:
a. Click to check the check box associated with Authentication required.
b. For Login, specify the SMTP username for WM to authenticate itself to the SMTP server.
c. For Password, specify the SMTP password for WM to authenticate itself to the SMTP
server.
d. Type the same string into the Confirm Password text box.
4. For From Mail ID, highlight wm_server@company.com and overwrite this placeholder
address with the FROM address that the SMTP server should mark in the outbound email
that is triggered by an escalation policy or an event or alarm filter.
5. For To Mail ID, highlight wm_admin@company.com and overwrite this placeholder
address with the FROM address that the SMTP server should mark in the outbound email
that is addressed to either customers or technical support staff (possibly in addition to
others added to the support tool because they are to be copied on support emails).
6. Click the Test button to ensure that the SMTP server and its port are properly configured in
this panel.
7. If the test is successful, click the OK button to apply its settings.
126
October 2015
16 MIB Browser Usage

MIB Browser also enables viewing and operating the data available through an SNMP agent in a
managed device. This can be helpful if you doubt that WM is performing properly and, through SNMP
queries via the MIB browser, want to verify configuration and performance data that you are seeing
in WM. WM supports the Windows version of the MIB Browser that is embedded in WM.
16.1 Invoking the MIB Browser

You can invoke the embedded MIB Browser as an application or an applet from the WM server file
system.
Procedure 49: To invoke the MIB Browser

1. In the /usr/local/cambium/wm/server/bin directory in Linux
(or the C:\Cambium\WM\server\bin folder in Windows, open the file
MibBrowser.exe or MibBrowser.bat for editing.
2. Ensure that the JAVA_HOME path is set properly.
3. Run MibBrowser.exe or MibBrowser.bat.
Figure 15: MIB Browser main GUI
127
October 2015
The image above depicts the primary window of the MIB Browser. The browser consists of the
following items:
 Menu Bar: Displays a list of commands to perform various operations.
 Tool Bar: Displays buttons with images that act as shortcuts to the menu options.
 Left Frame: Holds the MIB tree. A MIB tree is a structure that displays all the loaded MIBs.
The MIB tree enables to traverse the tree, view the loaded MIBs, and the definition of each
node.
 Right Frame: Contains text fields to specify the basic parameters, such as host, community,
and so on. It also contains a text area to display the results.
There are three ways in which the primary window of the MIB Browser can be displayed. They are the
Result Display, MIB Description, and Multi-Varbind. To change the display, select ViewDisplay and
select the desired view. By default, the MIB Description display is visible in the MIB Browser.
16.2 Configuring the MIB Browser

The MIB Browser can be used to view and operate on the data available through an SNMP agent. The
MIB Browser can be configured in tune with performing SNMP operations.
To configure the MIB Browser, click the MIB Browser Settings button or select Edit > Settings
from the menu. You can also use the shortcut key combination Alt + S.
The MIB Browser Settings dialog box will be displayed. The dialog has two tabs:
 General
 MIB Settings
16.2.1 Setting Common Parameters

The parameters, such as host, port, and community, can be set in the MIB Browser's main window.
Applications use the host name or the IP address of the device to communicate with the agent of the
device in a particular port number. This remote port number is the UDP Port 161. By default, all the
SNMP request messages are received in this port.
SNMP mandates that the SNMP agents should accept request messages only if the community string
in the message matches its community name. Therefore, the management application should always
communicate with the agents along with the associated community name. The default SNMP
community names are "public" for read-only (GET) operations and "private" for read-write (SET)
operations. The management applications should have provision to include the community names in
their request messages.
Community strings are used to authenticate SNMP PDUs. Since SNMP packets are usually sent using
UDP packets, there is no connection established as in the case of TCP/IP packets. Therefore, when a
UDP packet is sent to the agent, the agent validates the packet. It accepts and sends a response if the
community string of the PDU is equal to that set on the agent, or else drops the packet. The agent
does not change the community name after communicating. Applications typically communicate with
the SNMP agents by specifying the community name of the agent.
128
October 2015
The default community string is "public" and the default Write Community string is null. When Write
Community is null, community itself is used for SET operations. Therefore, applications should
explicitly set the Write Community, before they can use it for SET operations.
The other parameters are set in the General tab of the MIB Browser Settings frame. The general
settings include the basic protocol options related to SNMP, the display options, and a section for
encoding field. The image depicted below shows the General tab of the MIB Browser Settings dialog
box.
Figure 16: MibBrowser Settings dialog
Table 11: MibBrowser General tab fields
Options Default Values Other Options
SNMP Version v1 v2c or v3

1
Timeout 5 sec any user-defined value
1
Retries 0 any user-defined value
2
Encoding ISO8859_1 any encoding scheme that supports text format
129
October 2015

3
Max Repetitions 50 any user-defined value
3
Non Repeaters 0 any user-defined value
NOTES:
1. Timeout is the time interval that an application waits for a response message from
an agent before timing out. Retries is the number of times a request is sent when a
timeout occurs. If the Retries value is 0, the request is re-transmitted on Timeout.
2. Encoding, in general, means, modifying information into the required transmission
format. Computers around the world store information using a variety of encoding
schemes. The MIB Browser supports the ISO8859_1, which means the ISO 8859_1
and the Latin alphabet No.1. There are various other encoding schemes that
support various text formats. You can use the encoding scheme that best suits your
requirement while performing SNMP operations.
3. The Max Repetitions and Non Repeaters options are enabled only when the SNMP
version is set to either v2c or v3. This is because the GETBULK operation is available
only in v2c and v3. A GETBULK request is performed by giving an OID along with
two other parameters, Max Repetitions value and Non Repeaters value.
The Validate Broadcast Address check box enables you to check the validity of the broadcast address
provided. You need to provide the Net Mask address to validate the broadcast address. A Net Mask is
a string of 0's and 1's that hides the network part of the IP address and allows only the host ID to
remain.
In the V3 Options section, Context Name and the Context ID are to be provided as additional
parameters for an SNMPv3 request. An SNMP context name is a collection of management
information accessible by an SNMP entity. An item of management information may exist in more
than one context. An SNMP entity potentially has access to many contexts. In other words, if
management information has been defined under certain context by an SNMPv3 entity, any
management application can access that information by giving that context name. The Context ID
uniquely identifies an SNMP entity that may recognize an instance of a context with a particular
context name within an administrative domain.
Next is the V3 Settings section. The following are the security-related parameters for accessing the
SNMPv3 agents. You can add, modify, or delete users by clicking the Add, Modify, or Delete buttons.
Table 12: Security parameters for accessing SNMPv3 agents
User name null any user-defined value
Security level noAuth noPriv Auth noPriv and Auth Priv
MD5 (if authentication is

Authentication Protocol SHA
chosen in security level)
CBC-DES (if privacy is

Privacy Protocol not available
chosen in security level)
130
October 2015
Authentication
any user defined value -
password
Privacy password any user defined value -
any host with SNMPV3 agent

Target host localhost
or proxy agent
Target port 161 any user-defined port
If the security level is "NoAuthNoPriv", no additional parameters are required. If the security level is
"AuthNoPriv", the parameters AuthProtocol and AuthPassword are set. If the user security level is
"AuthPriv", the privacy password needs to be set in addition to the other parameters.
The V3 Settings section has an option for storing the v3 table entries. The v3 table entries can be
stored in:
 a serialized file
 a database
16.2.2 Storing Table Entries in a Serialized File

To enable serialization of v3 table entries, select the Save v3 Settings to File option. If this option is
selected, the user information is stored in the serialized files namely UserEntry.ser and
EngineEntry.ser. When the MIB Browser is invoked the next time, the serialized files are de-serialized
and the v3 table is updated. The advantage of storing table entries in serialized files is that the
operation is faster.
16.2.3 Storing Table Entries in a Database

To store v3 table entries in a database, select the Save v3 Settings to Database option. To use this
option, the database connection has to be established. Clicking on the "Database Settings" button
displays the Database Parameters dialog box.
Enter the necessary database parameters in the Database Parameters dialog box, and click the OK
button. If the database connection is established successfully, all the user information entered is
saved in the database. When the MIB Browser is invoked the next time, v3 details will be restored
and the v3 table will be updated.
The advantages of storing v3 table entries in a database include:
 Scalability - Any number of entries can be maintained in the database.
 Accessibility - All the authenticated users of the database can access the entries.
The last section is the field entry section in which the corresponding fields in the v3 table are
displayed for data entry. The various buttons available in the field entry section are Add, Modify, and
Delete.
131
October 2015
To add an entry, enter the required parameters in the respective fields and click the Add Entry
button. Based on the parameters and the security level, Discovery and Time Synchronization are done
and USM Table is updated and listed in the v3 table.
To modify an entry, select the entry in the v3 table, modify the required fields, and click the Modify
button. Time Synchronization is done and the USM table is updated and listed in the v3 table.
note ............. The NoAuthNoPriv entry cannot be modified. Only the password fields in the AuthNoPriv
entry and AuthPriv entry can be modified.
To delete an entry in the v3 table, select the entry in the v3 table and click the Delete button. The
entry is removed from the USM table.
note ............. The settings are saved only on exiting the MIB Browser application and not every time the
settings are modified.
The 'Save v3 Settings to File' option is enabled only in the MIB Browser application and
not in the MIB Browser applet because of certain security restrictions in applets.
The Restore Defaults button is used to reset the default parameters.
16.2.4 Setting MIB Parameters

The MIB Settings tab is used to load MIBs in MIB Browser. The first section gives the MIB loading
options. The next section displays the various parsing levels.
16.2.5 Loading MIBs

The basic MIB operations are loading, unloading, and parsing MIB files. A MIB file can be loaded
directly, from compiled files, or from a database. Follow the steps given below to load a MIB file.
1. Click the Load MIB Module button or select FileLoad MIB from the menu.
Alternatively, you can use the shortcut combination Ctrl+O. This displays the Load a MIB File
dialog box.
2. In the Load a MIB File dialog box, select the MIB file from the
/usr/local/cambium/wm/server/mibs directory in Linux (or the
C:\Cambium\WM\server\mibs folder in Windows).
note ............. If MIB Browser is used as an applet, the URL should be relative to the Web server path. If
MIB Browser is used as an application, the specified URL can be absolute or relative.
When you use the MIB Browser applet, it is not possible to read a file on some host that is
not the applet's host because of the browser security. In the MIB Browser applet, remote
browsing of MIB file is supported through SAS.
3. There are other options for loading the MIB file. Click the Recent tab to load the recently
loaded MIB files.
4. Select the check box next to the MIB that is to be loaded and click Open to load the MIB file.
note ............. The Load All MIBs option in the File menu loads all the recently loaded MIBs.
The following sections provide a general overview of the various options available in the MIB Settings
section of the Load a MIB File dialog box.
132
October 2015
MIB Loading Options

The various options available for loading MIBs are:
 Load MIBs directly
 Load MIBs from compiled files
 Load MIBs from a database
The following image depicts the MIB Settings tab in the Load MIB dialog box.
Figure 17: Load a MIB File Panel—MIB Settings Tab
Load MIBs Directly

The MIB file is usually read and parsed into MIB modules and displayed in the MIB tree. In this case,
when you load a MIB file, it is parsed and then loaded. This is time consuming because parsing is
done every time a MIB file is loaded.
Loading MIBs from a Database

Another option is loading of the MIB files from a database. The MIB files can be stored in any RDBMS
such as MySQL or Oracle. Applications can load these MIB files directly from the database. This
feature is particularly useful when the MIB files to be loaded are more in number.
The MIB Browser uses JDBC (Java Database Connectivity) for the database support. Applications
should use a valid JDBC driver of the respective databases to enable the database support.
133
October 2015
Selecting the option Load MIBs from Database enables the text fields in the JDBCParams section. On
initializing the necessary database parameters in this section, the database support can be provided
for loading MIBs. The required JDBCParams are:
 Drivername - name of the database driver.
 URL - URL pointing to the database filename.
 UserName - name of the user.
 Password - password for the user.
After selecting this loading option, select the required MIB file to be loaded from the Open tab of the
Load a MIB File dialog box. If the selected MIB file is already present in the database, the MIB file is
read, parsed, and loaded from the database. If the MIB file does not exist in the database, the MIB
Browser will parse the MIB file, write the output to the database, and then load the MIB file.
note ............. The recently loaded MIBs can be loaded automatically at startup by selecting the option
Load recently loaded Mibs at startup.
The loading of MIB files from the Oracle database has been tested. The following database
parameters are to be configured in the application.
 driver name - org.jdbc.driver.OracleDriver
 url - jdbc:oracle:thin:@<machine name>:1521:<database name>
 username - a valid user name
 password - password for the user
The Oracle driver has to be included in the CLASSPATH. If the jar is not present in the CLASSPATH, the
following exception is thrown:
Java.lang.ClassNotFoundException:oracle.jdbc.driver.OracleDriv
er
For other databases, use the equivalent parameters.
A few MIB files are provided in the mibs directory, i.e., RFC1213-MIB, RFC1271-RMON, RFC1155-SMI,
RMON2-MIB, TOKEN-RING-RMON-MIB, and RFC1315-FRAME. It may be convenient to copy your MIB
module files that are to be loaded into the "mibs" directory.
MIBs are always parsed before loading when the following operations are performed:
 Loading MIBs directly
 Loading MIB from Compiled File for the first time
 Selecting the "Overwrite existing compiled MIB files" option
 Loading MIB from database for the first time
16.2.6 Unloading MIBs

The next basic MIB operation is unloading. To unload the MIB, select the node of the MIB tree and
click the Unload MIB Module button or select File-->UnLoad MIB from the menu. Alternatively,
you can press the Delete key.
Performing any of the above prompts you for a confirmation. Selecting 'Yes' unloads the MIB module.
If no module is selected in the MIB tree, all the loaded MIB modules are unloaded.
134
October 2015
The Load All MIBs option in the menu bar would load all the previously loaded MIBs and Unload All
MIBs would unload all the loaded MIBs in the MIB tree.
16.2.7 Performing SNMP Operations

MIB Browser allows the user to perform the typical SNMP operations. The operations are categorized
as:
 Retrieving Data - GET, GETNEXT, GETBULK
 Altering Variables - SET
 Receiving Unsolicited Messages - Traps
To perform any basic operation as categorized above, it is essential to specify the Object ID, the
instance, host name, and the community string. Changes can also be made to the parameters in the
MIB Browser Settings dialog box
Specifying the Index

To specify an object to an SNMP agent, both the Object ID (which defines the type of object) and the
instance (the specific object of the given type) need to be provided. From the MIB you can get the
Object ID, to which an instance needs to be added to completely identify the object of interest.
For non-tabular or scalar objects, the instance is 0. For example, sysDescr is a scalar object under the
system group in the RFC1213-MIB and it should be specified as sysDescr.0 in the Object ID field of the
MIB Browser. In the MIB Browser, this does not need to be specified if the MIB is loaded, i.e., the
RFC1213-MIB. The MIB Browser adds it to the selected node while performing the GET operation.
For tabular objects, the instance is defined in the MIB as index, and it is a sequence of one or more
objects. For example, ifInOctets of ifTable defined in the RFC1213-MIB, the index is labeled as ifIndex
(INTEGER) and may be specified as ifInOctets.1 provided that there exists a row with index 1 in the
querying agent.
Another example is tcpConnState of tcpConnTable under tcp group of RFC1213-MIB. The indexes of
the tcpConnTable are tcpConnLocalAddress (IpAddress), tcpConnLocalPort (INTEGER),
tcpConnRemAddress (IpAddress) , tcpConnRemPort (INTEGER) and may be specified as
tcpConnState.179.74.15.126.1192.225.226.126.197.80 provided that there exists a row with Index
179.74.15.126.1192.225.226.126.197.80 in the querying agent where:
 179.74.15.126 represents the value of the first index tcpConnLocalAddress (IpAddress),
 1192 represents the value of the second index tcpConnLocalPort (INTEGER),
 225.226.126.197 represents the value of the third index tcpConnRemAddress (IpAddress)
 80 represents the value of the fourth index tcpConnRemPort (INTEGER).
To get the information about the MIB Node in the MIB Tree, click the Description icon or choose
ViewDescription menu item or use a shortcut of Alt + R. This gives a list of all the vital
characteristics of the node such as the Node, OID, Path, MIB Module, Syntax, Status, etc.
135
October 2015
Executing SNMP GET

The GET operation is performed to get one or more values from the managed objects. Follow the
steps to perform this operation.
1. Load the MIB file. The loading of MIBs and the options available has been dealt with in detail
in the Loading and Unloading MIBs section.
2. Select the desired node in the MIB tree.
3. Click the "Get SNMP Variable" icon on the toolbar or select OperationsGet from the
menu bar. Alternatively, you can use the shortcut key combination Ctrl + G.
This operation gets all objects under the selected MIB object, or the specific object if the MIB node
and instance are specified.
note ............. If the selected node in the MIB tree has child nodes or columnar nodes, the GET
operation is performed as an SNMP walk. The values for all the nodes under that sub-tree
are retrieved.
If the MIB is not loaded in the MIB Browser, then the exact numbered OID with full
instance (for example 1.3.0 for sysUpTime) should be specified and the GET
operation should be performed.
Performing a Multi-Varbind Request

To perform the Multi-Varbind request, follow the steps given below:
1. Make the Multi-Varbind display visible in the MIB Browser. This can be made visible by
selecting ViewDisplayMulti-Varbind from the menu. You can also use the General
Settings tab in the MIB Browser Settings panel.
2. Select the leaf node and append the instance by clicking the Add button. It will add the OID
given in the Object Identifier field and the value given in the SetValue field both separated
with a colon to the list. If value is not given in the SetValue field, NULL value is appended.
Similarly, you can add as many number of OIDs and values as required.
note ............. Ensure you select the Multi-var check box before doing an SNMP operation for multiple
varbind SNMP request. Otherwise, it does a request for the OID in the Object Identifier
field.
3. To delete the varbind(s) from the list, select the varbind(s) from the list and click the Delete
button.
4. To edit the varbind, select a varbind and click the Edit button. It shows an OID and the value
of the varbind in the text fields to edit. Edit it and click the OK button to modify the OID and
value or click the Cancel button to restore the old values.
note ............. When the request is sent under Multi-varbind mode, it goes as a single PDU irrespective
of the number of OIDs added.
If you want to communicate with a v3 agent, you have to select the v3 option in the MIB
Browser Settings dialog box and also make sure that the v3 parameters are set. Then
perform the above steps for each of the operations.
136
October 2015
Finding MIB Nodes

You can find a specific node in the MIB tree using the Find dialog box. This is invoked by selecting
EditFind Node from the menu. Use the Find in All option in the Find dialog box to find a node in all
the loaded MIB modules.
Executing SNMP GETNEXT

This operation is similar to the SNMP GET operation, but retrieves the value of the next OID in the
tree. This operation is used for traversing the MIB tree. To perform this operation, perform Steps 1
and 2 of Executing SNMP GET. Then proceed with the following step:
Click the Get Next SNMP Variable button on the toolbar or select OperationsGetNext from
the menu bar. Alternatively, you can use the shortcut key combination Ctrl+N.
This operation will get the next object after the specified object, or the specific object instance, if a
MIB node is specified. The instance may or may not be specified. You can also perform a multi-
varbind GETNEXT request.
Executing SNMP GETBULK

To retrieve voluminous data from a large table, the GETBULK operation is performed. A GETBULK
request is performed by giving an OID along with two other parameters, namely a Max Repetitions
value and a Non Repeaters value. The GETBULK operation is performed only on SNMPv2c and
SNMPv3.
To perform this operation, perform Steps 1 and 2 as in Executing SNMP GET and then continue with
the following steps.
1. Configure the MIB Browser to either SNMPv2c or SNMPv3 as desired. This can be done using
either the EditSettings option in the menu bar or the MIB Browser Settings icon on the
toolbar. You can also use the shortcut key combination Alt+S.
2. Under the same MIB Browser Settings panel, the Max Repetitions field and the
Non Repeaters field are enabled. The Max Repetitions value specifies the number of
lexicographic successors to be returned for the remaining variables in the variable-bindings
list. The default value in this field is 50. The Non Repeaters value specifies the number of
variables in the variable-bindings list for which a single lexicographic successor is to be
returned. The default value in this field is 0. Specify the values for these two parameters if
you need to and then proceed with the operation.
3. Click the Get Bulk SNMP data button or icon on the toolbar or choose
OperationGetBulk from the menu bar. Alternatively, you can use the shortcut key
combination Ctrl+B.
This will get a sequence of Next Objects immediately after the specified object. The number of Object
instances returned is equal to the Max Repetitions field.
137
October 2015
16.2.8 Setting SNMP Table Options

The MIB Browser enables you to view the SNMP Table data in a separate window called the SNMP
Table Panel. The table has a very user-friendly profile. The SNMP Table panel has various options
using which you can add and delete rows, view graphs, and use index editor.
Retrieving Table Data

The data in the table can be retrieved with ease. The following steps give insight into how to open the
Data Table panel and work on it using the various options.
1. Specify the proper agent host name or IP address in the Host field of MIB Browser.
2. Load the MIB file in MIB Browser.
3. Specify a valid OID or select the OID by traversing through the MIB Tree.
The OID should be a valid table OID.
4. Click the View SNMP data table button on the toolbar or choose ViewSnmp Table
from the menu. You can also use the shortcut key combination Alt+T.
5. The SNMP Table for the specified OID is displayed.
Figure 18: SNMP Table
6. Click the Start button at the bottom of the SNMP Table panel.
The retrieval of data begins and the columnar objects are obtained and displayed in the
table.
138
October 2015
7. Click the StartPolling button to start the polling of the table.

The polling interval is based on the Polling Interval value set using the Settings option.
8. Click the StopPolling button to stop the polling.
9. When you do not use the polling option, click the Refresh button to refresh the table.
The SNMP Table panel might retrieve more data so that the frame depicting the columnar
objects would run to pages.
10. When you need to navigate through the pages (rows), use the Next and Prev button.
The Page option at the bottom of the panel is used to specify how the table retrieval needs
to be done. If the option is origin, the table is retrieved from the origin. If the option is index,
the user can set an index value from which the table can be retrieved. The host name as
specified in MIB Browser will be displayed in the Host field. The page number and the
number of rows in that page are displayed next to it. It is possible to configure the SNMP
Table panel.
11. Click the Settings button.
This displays a dialog box with various options to configure the Table panel. The figure below
depicts the SNMP Table Settings panel.
Figure 19: SNMP Table Settings Panel
The various options available are listed below:

◦ PollingInterval - This specifies the time interval between each retrieval of data. The
default value is 5 secs.
◦ Page Size (Rows) - The number of rows to be retrieved is set here. The default value is
50.
◦ No Of Column View - This specifies the number of columns to be displayed in the SNMP
Table panel. The default is 5.
139
October 2015
◦ Split Columns - When the size of the PDU exceeds the limit, the agent sends the error
message "Too Big PDU Error". This field serves as an option for splitting the PDU. By
default, the PDU is split into half. If the number of varbinds is set by the user, then
multiple request with PDU containing number of varbinds set is sent.
◦ No of Columns/Request - This field is enabled on selecting the Split Columns check box.
You can specify the number for splitting of columns.
◦ Port - This field specifies the port to which the request is made.
◦ Table - The table OID is specified here.
◦ Max-Repetitions - This value specifies the number of lexicographic successors to be
returned for the remaining variables in the variable-bindings list. The default value is 5.
This is enabled only when the Retrieval Mode option is set to GetBulk.
◦ SnmpVersion - This gives the option to switch to any of the three versions of SNMP-v1,
v2c, and v3.
◦ Graph Type - This gives the option to switch between Line Graph and Bar Graph.
◦ Retrieval Mode - By default, GETNEXT is enabled. The GETBULK option is enabled only
on selecting v2c or v3.
12. If you need to view the graph, click the button.
13. Optionally, add rows.
14. Optionally, delete rows.
In a table, if one of the index columns is an external index (if the index value is shared by
some other table), then the table is called augmented, and a dependency exists between
rows of two tables. This situation might arise when a particular MIB imports another MIB
and shares a single table. For example, ifXTable defined in IF-MIB is an augmented table,
which has an external index ifIndex augmented from ifTable.
15. To see the columns of the table that augments the index from the original table, click the
Augmented Table button.
16. Click the Index Editor button to edit the index and view the rows from corresponding index.
17. To make changes to a particular column's values, right-click the column.
The various options available are:
◦ view column node details - This option gives the MIB Node Information of the selected
column.
◦ edit the header name for selected column - This invokes a dialog box in which you can
change the header for the selected column.
◦ view graph for selected cell(s) - This option invokes the graph. It is possible to view the
graphical representation for more than one cell by multiple selection of desired cells.
◦ add a new row to the table - This option is the same as the Add option available in the
Table panel.
◦ delete the selected rows from - This option is the same as the Delete option available in
the Table panel.
◦ view the not-accessible index - A request cannot be sent to an index that is not
accessible. In the table, the not-accessible index is not visible. Selecting this option
would enable you to view the not-accessible index values.
140
October 2015
16.3 Interpreting MIB Browser Error Messages

The following table lists MIB Browser related Error Messages and the different scenarios at which
they will be displayed.
Table 13: MibBrowser Error Messages
Error Message When it is displayed
No ObjectID Specified. OID is not specified before making a request.
No Host Specified. HostName is not specified before making a query.
SnmpTable is started without specifying the host

Host Name Should Be Entered.
name.
The specified OID is not a valid one. Before making

any query, Invalid OID Format exception is thrown.
It should be either Integer type or String type.
Invalid OID Format
It will be thrown during instantiating Line/Bar Graph,
SnmpTable, and operations, such as GET, GETNEXT,
GETBULK, SET, etc.
SnmpTable is started after specifying an invalid OID

Invalid Table OID
in the OID Textfield.
Table OID should be specified Snmptable started without specifying any Table OID
Error Loading MIB: xyz Invalid file is loaded in the LoadMibDialog TextField
java.io.FileNotFoundException: for loading MIBs File.
Could not Open stream for But in the description TextField of MIB Browser, the
home/../AdventNet/SNMPv3/mibs/xyz.parser message thrown is "Loading Mibs: xyz"
The error message is thrown when doing the

operations such as GET, GETNEXT, and SET and for
creating SnmpTable, LineGraph or BarGraph
window.
If the agent does not implement the OID that is
queried.
RequestFailed: Error: Request TimedOut To LocalHost If the agent queried is not present in the network.
If the port number set is not valid for the agent
queried.
If the Community and Write Community specified
are not correct.
If the OID queried does not contain any data.
If for v3 agents security parameters are not set.
141
October 2015
The error message is thrown when doing set

operation
If, the OID is not instrumented by the agent for
which it is setting value.
RequestFailed: Get Response PDU received from If the agent queried is not present in the network.
192.168.1.001 If the WriteCommunity specified is not right one.
Error Indication In Response: There is no such variable If the Syntax of the value you are setting is not as
name in this mib. that required by the OID.
ErrIndex: The same Exception is also thrown when plotting a
Graph for a leafNode is not performed by the agent
for whom it is setting a value.
And also when querying for data in an SnmpTable
If data is not available.
RequestFailed: Get Response PDU received from

192.168.1.001
The leafNode or OID for which you are setting value
Error Indication In Response: A not writable error
has no read/write access.
occurred.
ErrIndex: 1
ErrorSending Set Request :

The Error Message is thrown during set operation, if
com.adventnet.snmp.beans.DataException: Error: OID not
the OID selected is not a leaf node.
a leafnode.
Error sending set request: com.adventnet.snmp.beans: If setting value for a columnnode of a table does not
DataException: Error: Creating Variable have rowstatus.
The exception is thrown when plotting Graph for a

leafNode,
LineGraphBean Error: cannot plot string value Root.....
If value of OID selected is not of Integer/TimeTicks/
type.
LineGraphBean Error: cannot plot these values While plotting Line/Bar Graph,
.1.3..6.1.2.1..........................: value if the selected OID/LeafNode has syntax
................................................: value PhysAddress, NetworkAddress, IP Address, OBJECT
................................................: value IDENTIFIER.
Error: com.adventnet.snmp.beans.DataException: SnmpTable is started with OID which is not a Table

InvalidTable OID:(oid chosen) OID.
ErrorSendingPDU: Failed to Authenticate the Security The exception is thrown while creating SnmpTable,
Parameters, for user SnmpEngineEntry not found for If the host name specified, is of different version
address( hostname) port(portNo.) than v3 which is set in settings table.
If the OID/LeafNode chosen for plotting Graph is of

LineGraphBeanError: cannot plot string value xyz.
String Type.
142
October 2015
If wrong port number is set in the MIB Settings

Discovery failed for address (hostname) port (portno.)
panel.
If wrong username/user password/priv password/

Time Sync Failed for user (user name) TargetHost/SecurityLevel is set in the MIB Settings
panel
Error in Getting DataBase Connection:Please check the

jdbc parameters: If DriverName/URL/User Name/Password has been
com.adventnet.snmp.beans.MibException: set wrong when loading MIBs from database
java.lang.ClassNot FoundException:

jdbc parameters: java.lang.ClassNotfoundException: If the mysql.jar class is not present in the classes
directory.
(DriverName set)
Please enter the UserName If the Username is not set for the v3 User.
Sent request to hostName:port no.

Request Failed :SNMPv3 Error in Response. If Security parameters are set after setting the
usmStatsUnknownUserNames(.1.3.6.1.2.1.1...) Counter version v3 for a v1/v2 agent and request is made.
value = 2HostName
While loading the MIBs file if OK button is clicked

Enter the FileName of MIB Module
without selecting any file in "LoadMibDialog".
Error Loading MIB:(filename)

java io FileNotFoundException: Couldn't open stream for If any file chosen from outside the MIBs directory.
filename.cmi
Error Loading MIB:(filename with full path from home

dir).cds
When a .cds file is loaded.
com.adventnet.snmp.mibs.MibException:The .cds file
could not be loaded.
Error Sending PDU: Failed to Authenticate the Security

Parameters for user authUser USMUserEntry not found If ContextName/ContextEngineID is not set before
for this user. TimeSynchronizationFailure could have making query for SnmpTable.(Database Mode)
occurred.
Error in (get/getNext/getBulk)request to hostName:port

no.
If ContextName/ContextEngineID is not set before
Failed to Authenticate the Security Parameters for user making get/getNext/getBulk request
authUser USMUserEntry not found for Address hostname:
161
143
October 2015
get Request for a v3 User(Database mode)

AuthProtocol: MD5
Error in get request from < hostname >: 161
Context Name, ContextEngineID are not specified.
Unable to encode PDU.
Same exception is thrown for getnext, getbulk and
set operation also.(for AuthProtocol MD5&SHA)
Error in get request from < hostname >: 161 get Request for a v3 User(Database mode)
Failed to authenticate the security parameters for user AuthProtocol: SHA
privuser authKey length has to be 20. Context Name, ContextEngineID are not specified.
If IfTable OID is chosen for plotting Graph.

can not plot the chosen variable:
iso.org.dod.internet.mgmt.mib2.interfaces.ifTable The Error will be thrown if the OID chosen is not a
leaf OID.
sent get request to tonyjpaul:161 During getRequest for a v3 user

Request Failed: SNMPv3 Error in Response: usm Stats Not Context Name, ContextEngineID not specified.
InTimeWindows(.1.3.6.1.6.3.1.5.1.1.2.0) CounterValue Same Error Message is Thrown for other operations
=13 tonyjpaul like getNext, getBulk, set
sent getbulk request to localhost:161 If getBulk Operation is done for "org".(setting

Request Failed: Get Response PDU received from version v2/v3 for a v1 host)
127.0.0.1. if the OID/LeafNode selected is the last node of the
Error Indication in response : This is a end of MIB View. mib.
ObjectID: .1.3.6.1.2.1.1.9.1.4.9 The same Exception will be thrown for operations
NULLOBJECT:NULL like getNext, getBulk also.
Setting value for an OID which is not having any

Error Sending set Request: leafnode.
com.adventnet.snmp.beans.DataException: Error: Mib
node unavailable for OID. Now it's thrown if we are choosing any OID from
"enterprises".
sent get request to < hostname >:161

Request Failed: Get Response PDU received from
192.168.1.182 Get Operation on sysServices node for a v3 agent.
Error Indication in response : There is no such instance in This Error is thrown if the leafnode sysServices is not
this MIB. implemented by the agent.
ObjectID: .1.3.6.1.2.1.1.9.1.4.9
NULLOBJECT:NULL
144
October 2015
sent get request to <hostname>:161

During set operation on ipRouteDest which has read-
write access & syntax of datatype:IP Address for a v3
192.168.1.182
user.
Error Indication in response : A no creation error
As values cannot be set if the column is not of Row-
occurred.
Status type.
Errindex:1
When doing a get request for a v2 agent at OID

sent get request to <hostname>:161 "transmission"(.1.3.6.1.2.1.10)
No data available in this subtree Exception is thrown when no data is available for
that particular instance of OID.
Error in getting Database Connection . Please check the

jdbc Parameters: Error is thrown when connecting to the database for
an agent of any version, if the DriverName set is not
com.adventnet.snmp.mibs.MibException: java.sql.SQL correct.
Exception: No suitable Driver.

This error is thrown when the URL set is not a valid
jdbc Parameters: java.sql.SQLException: No suitable
URL for connecting to database.(mysql->msql)
Driver.

jdbc Parameters: java.sql.SQLException: Cannot connect
to MYSQL sever on smplinux:3306. Is there a mysql server This error is thrown when the URL set is not a valid
is running in the machine/port you are trying to connect URL for connecting to database.(snmplinux-
to? >smplinux)
(java.net.UnknownHostException)

jdbc Parameters: java.sql.SQLException: General error: This error is thrown when the URL set is not a valid
URL for connecting to database.(test->tst)
Unknown database "<tst>"
sent set request to <hostname>:161

Request Failed: SNMPv3 Error in Response : Error thrown if the request is made after a certain
usmStatsNotInTimeWindows(.1.3.6.1.6.3.15.1.1.2.0)Coun interval of time..
ter value = 75 <hostname>
sent get request to <hostname>:161

192.168.1.182
This OID is not instrumented for the agent you are
Error Indication in response : There is no such object in
querying for or no data is available in this OID.
this MIB.
ObjectID: .1.3.6.1.2.1.8.1.0
NULLOBJECT:NULL
145
October 2015
16.4 FAQs
How do I give Hex strings for SET values in MIB Browser?
The SnmpString class accepts Hex strings in a certain format. Any string that starts and ends with a
single quote(') is interpreted as an Hex string. The individual bytes should be separated using a
colon(:). For example, if you need to enter 0x2a304cab, it should be supplied as '2a:30:4c:ab'.
How do I give Hex values in the ContextEngineID or in the ContextName text

fields?
The Hex values should start with a 0x or 0X. Therefore, if you set a value for contextID or
contextName, it should be 0xHHHHHH.
What are the units for timeout and retry values?

Both the timeout and retry values should be given in seconds. If you give the timeout value in
milliseconds, it takes much time to get timed out. For example, a value of 1000 waits for 1000
seconds.
How do I set values for the table variables?

To create a new row in a table:
1. Define a column with SYNTAX RowStatus, and the definition for the table should have
RowStatus object defined.
2. Select the Table node from the tree and the Table button from the toolbar to display the
corresponding table.
3. Right-click on the table header where the name of the column is displayed.
It displays a menu with the following options:
◦ View Graph for Selected Rows
◦ Add a New Row to the Table
◦ Delete the Selected Rows from the Table
4. Select Add a New Row to the Table.
It displays a window for entering the values of the table.
5. The value for the column with RowStatus syntax should be 4 for creating a new row.
6. Click OK after entering all the values.
If RowStatus is not present in the table definition, you can only modify the existing row by double-
clicking the corresponding cell in the table.
If I load the MIB Browser applet, I get the error "Error Sending PDUSecurity
Exception connecting to remote host" in the browser. Why is this so?
Applets are not allowed to talk to any host apart from the Web server from which they were
downloaded. Make sure that SAS is also running along with the Web server.
146
October 2015
I do not get the "NO HOST Specified" error. What should I do?
Before making any request, the host name or the IP address of the machine in which the agent is
running should be specified in the "Host" text field of MIB Browser.
How can I load multiple MIB files in MIB Browser?

To load multiple MIBs, files should be separated by a blank space and be given within double quotes.
For example:
java MibBrowserApplication -m "mibs/RFC1213-MIB mibs/RFC1271-
MIB mibs/RFC1155-MIB" -h localhost -c public
If you use MibBrowser.sh, edit the file accordingly.
When I ask for 10 rows in an SNMP table, the GETBULK returns only 6 rows and
the last attribute of the sixth row is null. The sixth row seems to be truncated.
What should I do?
The number of rows you get back may be limited by the PDU size permitted by your agent, manager,
or transport.
I use JDK 1.2. How do I invoke MIB Browser as an applet through applet viewer?
From JDK1.1, the appletviewer no longer takes the CLASSPATH setting into consideration. Therefore
for the applets, the following command is to be given.
appletviewer -J-Xbootclasspath:.;
..\..\jars\AdventNetSnmp.jar;..\..\jars\AdventNetLogging.jar;
..\..\sasapps.jar; c:\jdk1.2\jre\lib\rt.jar
To load from the browsers, the HTML file should also be changed accordingly.
Applets could instead be packaged into jar files for easy use. Also, with JDK1.2, you can specify
dependencies on other jars through extensions. Therefore, if you create an applet that uses
AdventNet Beans and the target platform is the JDK1.2-plug-in, you need to include the CLASSPATH.
147
October 2015
Legal Notices and License Agreements

CAMBIUM NETWORKS, LTD
END USER LICENSE AGREEMENT
CAMBIUM NETWORKS, LTD (“Cambium”) is willing to license its Wireless Manager™ software and the
accompanying documentation (collectively, the “Software,” as further defined below) to you only on the condition
that you accept all the terms in this End User License Agreement (this “Agreement”).
IMPORTANT: READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING THE SOFTWARE AND ANY
EQUIPMENT AND/OR PRODUCTS THAT ACCOMPANY THE SOFTWARE.
BY CLICKING ON THE “ACCEPT” BUTTON DURING INSTALLATION, YOU ACKNOWLEDGE THAT YOU HAVE READ
THIS AGREEMENT, UNDERSTAND IT AND AGREE TO BE BOUND BY THE TERMS OF THIS AGREEMENT.
IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, CAMBIUM IS NOT WILLING TO LICENSE THE
SOFTWARE TO YOU AND YOU SHOULD CLICK ON THE “DO NOT ACCEPT” BUTTON TO DISCONTINUE THE
INSTALLATION PROCESS. IF YOU DO NOT AGREE TO THESE TERMS AND CONDITIONS, YOU MAY, FOR A FULL
REFUND: (I) RETURN THE SOFTWARE TO THE ENTITY FROM WHOM YOU PURCHASED IT; OR, (II) FOR
DOWNLOADED SOFTWARE, PROVIDE TO THE ENTITY FROM WHOM YOU PURCHASED THE SOFTWARE YOUR
WRITTEN VERIFICATION OF DELETION OF ALL COPIES OF THE SOFTWARE.
1. Definitions. In this Agreement, the word “Software” refers to the set of instructions for computing devices, in
executable form and in any media (which may include diskette(s), CD-ROM(s), downloadable Internet file(s),
hardware, firmware, etc.), and includes without limitation interfaces, content, fonts, images, photographs,
animations, video, audio, music text, “applets” and included data, as well as the accompanying documentation,
such as manuals and instructional aids, whether in printed or electronic form, for the software product identified
above.
2. General. The Software is licensed, and not sold, to you by Cambium for use only under the terms of this
Agreement. Cambium and/or Cambium’s licensor(s) retain all right, title and interest in and to the Software, and
the copyrights and other intellectual property rights therein and thereto, and reserve all rights not expressly
granted to you in this Agreement. The terms of this Agreement will govern any update(s) and/or upgrade(s) to the
Software provided by Cambium that replace and/or supplement the original Software, unless such update(s)
and/or upgrade(s) are accompanied by a separate license in which case the terms of that license will govern.
3. Grant of License. Cambium grants you (“Licensee” or “you”) a limited, personal, nonexclusive and non-
transferable (except as otherwise provided herein) license to use the Software subject to the Conditions of Use set
forth in Section 4 and the remaining terms and conditions of this Agreement. Any terms or conditions appearing on
the face or reverse side of any purchase order, purchase order acknowledgment or other order document that are
different from, or in addition to, the terms of this Agreement will not be binding on the parties, even if payment is
accepted.
4. Conditions of Use; Restrictions on Use. The Software is protected by international intellectual property laws and
treaties, and other applicable laws. Any use of the Software in violation of the terms and conditions set forth in
this Agreement is strictly prohibited and will be deemed a breach of this Agreement. In addition to the other terms
and conditions of this Agreement, you agree to the following specific conditions and restrictions:
4.1. You will use the Software in compliance with all applicable laws, including local laws of the country or
region in which you reside or in which you use the Software.
4.2. Only you, your employees or agents may use the Software. You will take all necessary steps to insure
that your employees and agents abide by the terms of this Agreement.
4.3. You will use the Software: (i) only for your internal business purposes; (ii) only as described in the
Software; and, (iii) in strict accordance with this Agreement.
149
October 2015
4.4. You will install and use the Software on a single computing device.
4.5. To the extent the Software includes features involving maps, you will take all reasonable efforts not
exceed 20,000 map page views per year. Cambium reserves the right to disable the usage of features
involving maps if your annual usage of map page views exceeds 20,000 map page views.4.6. You will
not, and you will not enable others to, copy (except for back-up purposes as expressly permitted by
this Agreement), decompile, bootleg, reverse engineer, disassemble, attempt to derive the source
code of, decrypt, modify, translate, or create derivative works from the Software, or any part thereof
(except as, and only to the extent, any foregoing restriction is prohibited by applicable law). Any
attempt to do so is a violation of the rights of Cambium and/or its licensor(s) in the Software.
4.7. You will not attempt to defeat any copy protection device included with the Software.
4.8. If the Software is provided on multiple types of media, you will use only the media that best meets
your specific needs, and you will not loan, rent, lease or transfer the other media contained in the
package without Cambium’s written consent.
4.9. You will not remove any proprietary notices, marks, labels, or logos from the Software.
4.10 Unless otherwise provided herein, you will not rent, lease, sublicense or transfer the Software, or any
part thereof, to any other party without Cambium’s prior written consent.
4.11. You will not use the Software for any purposes prohibited by applicable law, including without
limitation the development, design, manufacture or production of nuclear, missiles, or chemical or
biological weapons.
USE OF THE SOFTWARE IN ANY MANNER OTHER THAN AS PROVIDED HEREIN IS STRICTLY PROHIBITED
AND MAY INFRINGE ON THE INTELLECTUAL PROPERTY RIGHTS OF CAMBIUM AND/OR ITS LICENSOR(S),
SUBJECTING YOU TO CIVIL AND CRIMINAL PENALTIES, INCLUDING WITHOUT LIMITATION MONETARY
DAMAGES AND IMPRISONMENT FOR COPYRIGHT INFRINGEMENT.
5. Back-Ups. Notwithstanding anything to the contrary in this Agreement, you may make one (1) copy of the
Software in machine-readable form for back-up purposes only. If the documentation for the Software is in printed
form, it may not be copied. With regard to all copies of the Software permitted herein, you agree to reproduce on
such copies all Cambium copyright notices, and other proprietary notices appearing on and in the original
Software.
6. Export. You may not export, re-export or transfer, directly or indirectly, the Software except as authorized by
United States law or by the laws of the jurisdiction(s) in which the Software was obtained. By way of example, but
without limitation of the foregoing, if your Software was obtained in the United States, the Software may not be
exported, re-exported or transferred: (a) into any U.S. embargoed countries; or, (b) to anyone on the U.S. Treasury
Department's list of Specially Designated Nationals or the U.S. Department of Commerce Denied Person’s List or
Entity List. By using the Software, you represent and warrant that you are not located in any such country or on
any such list.
7. Confidentiality. You acknowledge that the Software contains valuable proprietary information and trade secrets
and that unauthorized or improper use of the Software will result in irreparable harm to Cambium for which
monetary damages would be inadequate and for which Cambium will be entitled to immediate injunctive relief.
Accordingly, you will limit access to the Software to those of your employees and agents who need to use the
Software for your internal business purposes, and you will take appropriate action with those employees and
agents to preserve the confidentiality of the Software, using the same degree of care to avoid unauthorized or
improper disclosure as you use for the protection of your own proprietary software, but in no event less than
reasonable care. You have no obligation to preserve the confidentiality of any information that: (i) was in the
public domain at the time of disclosure; (ii) entered the public domain through no fault of yours; (iii) was given to
you free of any obligation to keep it confidential; (iv) is independently developed by you; or, (v) is disclosed as
required by law provided that you notify Cambium prior to such disclosure and provide Cambium with a
reasonable opportunity to respond.
150
October 2015
8. Right to Use Cambium’s Name. Except as required in Section 5 above, you will not, during the term of this
Agreement or thereafter, use any trademark of Cambium, or any word and/or symbol likely to be confused with
any Cambium trademark, either alone or in any combination with other words and/or symbols.
9. Transfer. In the case of Software designed to operate on Cambium equipment, you may not transfer the
Software to another party except: (i) if you are an end-user, when you are transferring the Software together with
the Cambium equipment on which it operates; or, (ii) if you are a Cambium authorized distributor, when you are
transferring the Software either together with such Cambium equipment or are transferring the Software as a
licensed duly paid-for upgrade, update, patch, new release, enhancement or replacement of a prior version of the
Software. If you are a Cambium authorized distributor, when you are transferring the Software as permitted in this
Agreement, you agree to transfer the Software with a license agreement having terms and conditions no less
restrictive than those contained in this Agreement. All transfers of the Software under this Section 9 are strictly
subject to the conditions precedent that: (iii) the other party agrees to accept the terms and conditions of this
Agreement; and, (ii) you destroy any copy of the Software you do not transfer to that party. Unless otherwise
provided herein, the Software may not be transferred, and this Agreement may not be assigned, by you without
Cambium’s prior written consent.
10. Upgrades and Updates. If the Software is licensed to you as an upgrade or update to software previously
licensed to you, you must destroy the software previously licensed to you, including any copies, within 30 days of
your receipt of the Software.
11. Maintenance and Support. Cambium is not responsible for maintenance or support of the Software, or the
equipment on which the Software resides or is used, under this Agreement. By accepting the license granted under
this Agreement, you agree that Cambium will be under no obligation to provide any support, maintenance or
service in connection with the Software or such equipment. Maintenance and support of the Software and/or such
equipment by Cambium may be available under the terms of a separate agreement.
12. Limited Warranty. All physical media, such as diskettes or CD-ROMS, on which the Software is furnished by
Cambium (the “Media”) are warranted to be free from manufacturing and material defects for ninety (90) days
after the shipment date of the Media to you. Media that becomes defective during such period will be repaired or,
at Cambium’s option, replaced. This limited warranty is contingent upon proper use of the Media and does not
cover Media that has been tampered with, modified or subjected to unusual physical or electrical stress.
Tampering with or removing any factory seal or label on any Media voids this warranty and releases Cambium
from any and all liability. The entire liability of Cambium, and your exclusive remedy under the warranty provided
in this Section 12 will be, at Cambium’s option, to repair or replace any Media found to be defective within the
warranty period, or to refund the purchase price and terminate this Agreement. To seek such a remedy, you must
return the Software to Cambium, with a copy of the original purchase receipt, within the warranty period.
13. Disclaimer. EXCEPT FOR THE ABOVE EXPRESS LIMITED WARRANTY FOR THE MEDIA, AND TO THE MAXIMUM
EXTENT PERMITTED BY APPLICABLE LAW, THE SOFTWARE IS PROVIDED "AS IS" AND “AS AVAILABLE”, WITHOUT
WARRANTY OF ANY KIND, AND CAMBIUM ON BEHALF OF ITSELF AND ITS LICENSOR(S) HEREBY DISCLAIMS ALL
WARRANTIES AND CONDITIONS WITH RESPECT TO THE SOFTWARE, EXPRESS, IMPLIED OR STATUTORY, INCLUDING
WITHOUT LIMITATION THE IMPLIED WARRANTIES AND/OR CONDITIONS OF MERCHANTABILITY, OF SATISFACTORY
QUALITY, OF FITNESS FOR A PARTICULAR PURPOSE, OF ACCURACY, OF QUIET ENJOYMENT, AND OF NON-
INFRINGEMENT OF THIRD PARTY RIGHTS. CAMBIUM ALSO DOES NOT WARRANT THAT THE FUNCTIONS
CONTAINED IN, PERFORMED AND/OR PROVIDED BY THE SOFTWARE WILL MEET YOUR REQUIREMENTS, THAT THE
OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, THAT THE SOFTWARE WILL BE
COMPATIBLE OR WORK WITH ANY THIRD PARTY SOFTWARE, APPLICATIONS OR DEVICES, OR THAT DEFECTS IN THE
SOFTWARE WILL BE CORRECTED. CAMBIUM MAKES NO WARRANTY WITH RESPECT TO THE CORRECTNESS,
ACCURACY, OR RELIABILITY OF THE SOFTWARE, AND YOU EXPRESSLY ACKNOWLEDGE AND AGREE THAT, TO THE
EXTENT PERMITTED BY APPLICABLE LAW, YOUR USE OF THE SOFTWARE IS AT YOUR SOLE RISK AND THAT THE
ENTIRE RISK AS TO SATISFACTORY QUALITY, PERFORMANCE, ACCURACY AND EFFORT IS WITH YOU. YOU FURTHER
ACKNOWLEDGE AND AGREE THAT THE SOFTWARE IS NOT INTENDED OR SUITABLE FOR USE IN SITUATIONS OR
ENVIRONMENTS WHERE THE FAILURE OR TIME DELAYS OF, OR ERRORS OR INACCURACIES IN THE CONTENT, DATA
OR INFORMATION PROVIDED BY THE SOFTWARE COULD LEAD TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL
151
October 2015
OR ENVIRONMENTAL DAMAGE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY CAMBIUM OR AN

AUTHORIZED CAMBIUM REPRESENTATIVE SHALL CREATE A WARRANTY.
SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR LIMITATIONS ON APPLICABLE
STATUTORY RIGHTS OF A CONSUMER, SO THE ABOVE EXCLUSION AND LIMITATIONS MAY NOT APPLY TO YOU.
14. Limitation of Liability. THE TOTAL LIABILITY OF CAMBIUM FOR ANY DAMAGES UNDER THIS AGREEMENT WILL
NOT EXCEED THE TOTAL AMOUNT PAID BY YOU FOR THE SOFTWARE LICENSED UNDER THIS AGREEMENT. TO THE
EXTENT NOT PROHIBITED BY APPLICABLE LAW, IN NO EVENT SHALL CAMBIUM BE LIABLE FOR PERSONAL INJURY,
OR ANY INCIDENTAL, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING WITHOUT
LIMITATION DAMAGES FOR LOSS OF PROFITS, LOSS OF DATA, BUSINESS INTERRUPTION OR ANY OTHER
COMMERCIAL DAMAGES OR LOSSES, ARISING OUT OF OR RELATED TO YOUR USE OR INABILITY TO USE THE
SOFTWARE, OR ANY THIRD PARTY SOFTWARE, APPLICATIONS AND/OR DEVICES IN CONJUNCTION WITH THE
SOFTWARE, HOWEVER CAUSED, REGARDLESS OF THE THEORY OF LIABILITY (CONTRACT, TORT OR OTHERWISE)
AND EVEN IF CAMBIUM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS DO
NOT ALLOW THE LIMITATION OF LIABILITY FOR PERSONAL INJURY, OR OF INCIDENTAL OR CONSEQUENTIAL
DAMAGES, SO THIS LIMITATION MAY NOT APPLY TO YOU.
15. U.S. Government End Users. The Software is a “Commercial Item,” as that term is defined at 48 C.F.R. §2.101,
consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such
terms are used in 48 C.F.R. §12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48
C.F.R. §227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial
Computer Software Documentation are being licensed to U.S. Government end users: (i) only as Commercial
Items; and, (ii) with only those rights as are granted to all other end users pursuant to the terms and conditions
herein, notwithstanding any other FAR or other contractual clause to the contrary in any agreement into which this
Agreement may be incorporated or which Cambium may provide to Government end user. Use of the Software
constitutes agreement by the U.S. Government that the Software is Commercial Computer Software and
Commercial Computer Software Documentation, and constitutes acceptance of the rights and restrictions herein.
Unpublished rights ARE reserved under the copyright laws of the United States. The name and address of the
contractor for United States Government end users is: Cambium Networks, Ltd, a company registered in England
and Wales under company number 07752773, with an address at 1299 E. Algonquin Road, Schaumburg, IL 60196.
16. Term and Termination. This Agreement, and your right to use the Software, will begin when you click the
“ACCEPT” button, which constitutes acceptance of the terms and conditions in this Agreement, and will continue in
perpetuity unless terminated as follows. This Agreement will terminate immediately and automatically without
notice upon a breach of this Agreement by you. You may also terminate this agreement by ceasing use of the
Software. Upon the termination of this Agreement for any reason, you must cease all use of the Software and
destroy all copies of the Software in your possession or control.
17. Governing Law and Severability. This Agreement is governed by the laws of the United States of America, to
the extent that they apply, and otherwise by the laws of the State of Illinois, excluding its conflicts of laws
principles. This Agreement shall not be governed by the United Nations Convention on Contracts for the
International Sale of Goods, the application of which is expressly excluded. If for any reason a court of competent
jurisdiction finds any provision of this Agreement, or portion thereof, to be unenforceable, the remainder of this
Agreement shall continue in full force and effect.
18. Survival. The parties agree that where the context of any provision indicates an intent that it survives the term
of this Agreement, then it will survive.
19. Entire Agreement. This Agreement constitutes the entire agreement between you and Cambium relating to
the Software licensed hereunder and supersedes all prior or contemporaneous understandings regarding such
subject matter. No amendment to or modification of this Agreement will be binding unless in writing and signed by
Cambium, except that Cambium may modify and/or translate this Agreement as necessary to comply with
applicable laws. In the event of a dispute between the English version and any non-English versions, the English
version of this Agreement shall govern, to the extent not prohibited by the local law in your jurisdiction.
20. Third-Party Software. The Software may contain one or more items of third-party software supplied by third-
party suppliers (collectively, “Third-Party Software”). The terms of this Agreement govern your use of any Third-
152
October 2015
Party Software UNLESS A SEPARATE THIRD-PARTY SOFTWARE LICENSE IS INCLUDED, IN WHICH CASE YOUR USE OF
THE THIRD-PARTY SOFTWARE WILL THEN BE GOVERNED BY THE SEPARATE THIRD-PARTY LICENSE. Use of the
Google Maps service is subject to the following additional terms: Google Maps Terms of Service available at
http://maps.google.com/help/terms_maps.html and Google Maps Legal Notices at
http://maps.google.com/help/legalnotices_maps.html. By using the Software you are agreeing be bound by the
terms of use for all Third-Party Software. If the Software licensed under this Agreement contains publicly available
(open source) Third-Party Software, the terms and conditions governing the use of such publicly available Third-
Party Software are in the software licenses of the copyright owner(s) of such software and not this Agreement. If
there is a conflict between the terms and conditions of this Agreement and the terms and conditions of the
publicly available Third-Party Software license(s) governing your use of the publicly available Third-Party Software,
the terms and conditions of the license of the applicable publicly available Third-Party Software license(s) will take
precedence over the license granted in this Agreement. The license agreements for publicly available Third-Party
Software included by Cambium are available in the file Cambium Publicly Available Software Legal Notices.htm
installed in the server file system during installation of the Software. The software license agreements for publicly
available Third-Party Software included by third parties are available in the file Third Party Publicly Available
Software Legal Notices.htm installed in the server file system during installation of the Software.
21. Privacy. Your use of the Software is subject to Cambium’s Privacy Policy available at:
http://cambiumnetworks.com/legal/terms_of_use.php as well as the Google Maps privacy policy described at
http://www.google.com/privacy.html, the terms of which are incorporated herein by reference.
IF THE FOREGOING TERMS AND CONDITIONS ARE ACCEPTABLE TO YOU, PLEASE INDICATE YOUR AGREEMENT
AND ACCEPTANCE BY CLICKING ON THE BUTTON LABELED “ACCEPT.” IF THE FOREGOING TERMS AND
CONDITIONS ARE NOT ACCEPTABLE TO YOU, PLEASE CLICK ON THE “DO NOT ACCEPT” BUTTON.
WIRELESS MANAGER™, CAMBIUM™, CAMBIUM NETWORKS™, and the Cambium Networks Logo are trademarks of
Cambium Networks, Ltd.
© Copyright 2015 Cambium Networks, Ltd All rights reserved.
153
October 2015
CAMBIUM PUBLICLY AVAILABLE SOFTWARE LEGAL NOTICES AND END USER LICENSE
AGREEMENTS FOR PUBLICLY AVAILABLE SOFTWARE
The Wireless Manager™ software may include Cambium software, commercial third party software, and/or
publicly available (open source) software.
The Cambium software included in the Wireless Manager™ software is copyright (c) by Cambium Networks, LTD
(“Cambium”), and its use is subject to the licenses, terms and conditions of the agreement in force between the
purchaser of the Wireless Manager™ software and Cambium. The commercial third party software that may be
included in or with the Wireless Manager™ software is subject to the licenses, terms and conditions of the
agreement in force between you and Cambium, unless a separate commercial third party software license is
included, in which case, your use of the commercial third party software will then be governed by the separate
commercial third party license. The publicly available software that may be included in or with the Wireless
Manager™ software is listed below. The use of the listed publicly available software is subject to the licenses,
terms and conditions of the agreement in force between you and Cambium, as well as the terms and conditions of
the license of each publicly available software package. Copies of the licenses for the listed publicly available
software, as well as, all attributions, acknowledgements, and software information details, are included below.
Cambium is required to reproduce the software licenses, acknowledgments and copyright notices as provided by
the authors and owners, thus, all such information is provided in its native language form, without modification or
translation.
The publicly available software in the list below includes the publicly available software included by Cambium. The
publicly available software included by commercial third party software that is used in the Wireless Manager™
software is disclosed in the Third Party Publicly Available Software Legal Notices accompanying the Wireless
Manager™ software.
For instructions on how to obtain a copy of any source code being made publicly available by Cambium related to
software used in the Wireless Manager™ software you may send your request in writing to:
Cambium Networks, LTD
Attention: Open Source Software Manager
1299 E. Algonquin Road
Schaumburg, IL 60196
In your request, please include the version of the Wireless Manager™ software, along with the publicly available
software specifics, such as the publicly available software name and version.
Note: the source code for the publicly available software may be resident on the Cambium product installation
media, or on supplemental Cambium product media and/or Cambium websites. Please reference and review these
entire Cambium Publicly Available Software Legal Notices and End User License Agreements for Publicly Available
Software for the details on location and methods of obtaining the source code.
Note: dependent on the license terms of the publicly available software, source code may not be provided. Please
reference and review these entire Cambium Publicly Available Software Legal Notices and End User License
Agreements for Publicly Available Software for the details on location and methods of obtaining the source code.
To view additional information regarding licenses, acknowledgments and required copyright notices for publicly
available software used in the Wireless Manager™ software, please select “Legal Notices” display from the GUI (if
applicable), or review the legal notices and end user license agreements in the README files or other files created
during installation, in the documentation, on the installation media, or resident in the Wireless Manager™
software.
Cambium Networks, LTD. All other trademarks, logos, and service marks are the property of the respective third
party owners. You are not permitted to use any marks without the prior written consent of Cambium or such third
party which may own the marks.
154
October 2015
Software Included by Cambium
The following are the end user license agreements for publicly available software that Cambium has included.
Ant Contrib
Version: 1.0b3
Description: The Ant-Contrib project is a collection of tasks (and at one point maybe types and other tools) for
Apache Ant. Used to facilitate automation of build scripts.
Software site: http://sourceforge.net/projects/ant-contrib
Source Code: The source packages for Ant Contrib 1.0b3 are available from the original software site, or may be
acquired from Cambium. To obtain the software from Cambium, please contact Cambium using the methods
described in the preamble of this document.
License: The Apache Software License, Version 1.1
Copyright (c) 2001-2003 Ant-Contrib project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following
acknowledgment:
"This product includes software developed by the Ant-Contrib project
(http://sourceforge.net/projects/ant-contrib)."
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party
acknowledgments normally appear.
4. The name Ant-Contrib must not be used to endorse or promote products derived from this software without
prior written permission. For written permission, please contact http://sourceforge.net/.
5. Products derived from this software may not be called "Ant-Contrib" nor may "Ant-Contrib" appear in their
names without prior written permission of the Ant-Contrib project.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE ANT-CONTRIB PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Geo API
Version: 2.1
Description: Java library for Geo spatial data manipulation
Software site: http://geoapi.sourceforge.net/
Source Code: The source packages for Geo API are available from the original software site, or may be acquired
from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in
the preamble of this document.
License: OGC (Open Geospatial Consortium)
155
October 2015
This OGC work (including software, documents, or other related items) is being provided by the copyright holders
under the following license. By obtaining, using, and/or copying this work, you (the licensee) agree that you have
read, understood, and will comply with the following terms and conditions: Permission to use, copy, and modify
this software and its documentation, with or without modification, for any purpose and without fee or royalty is
hereby granted, provided that you include the following on ALL copies of the software and documentation or
portions thereof, including modifications, that you make:
1. The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
2. Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice
of the following form (hypertext is preferred, text is permitted) should be used within the body of any
redistributed or derivative code: "Copyright © [$date-of-document] Open Geospatial Consortium, Inc. All Rights
Reserved. http://www.opengeospatial.org/Legal/ (Hypertext is preferred, but a textual representation is
permitted.)
3. Notice of any changes or modifications to the OGC files, including the date changes were made. (We
recommend you provide URLs to the location from which the code is derived.)
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKENO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITEDTO, WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THATTHE USE OF THE SOFTWARE OR
DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTYPATENTS, COPYRIGHTS, TRADEMARKS OR OTHER
RIGHTS. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL ORCONSEQUENTIAL
DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the
software without specific, written prior permission. Title to copyright in this software and any associated
documentation will at all times remain with copyright holders.
Javolution
Version: 5.2.5
Software site: http://javolution.org/
Source Code: The source packages for Javolution are available from the original software site, or may be acquired
License: Javolution - Java(tm) Solution for Real-Time and Embedded Systems
Copyright (c) 2005 - 2007 Javolution (http://javolution.org/). All rights reserved.
disclaimer.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
156
October 2015
JScience
Version: 4.3.1
Software site: http://jscience.org
Source Code: The source packages for JScience are available from the original software site, or may be acquired
License: JScience - Java(TM) Tools and Libraries for the Advancement of Sciences
Copyright (C) 2006 - JScience (http://jscience.org/). All rights reserved.
* Redistributions of source code must retain the above copyright notice and include this license agreement.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY EXPRESS OR
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ONANY THEORY OF LIABILITY,
XStream
Version: 4.2.6
Description: Java, JSON and XML serialization library
Software site: http://xstream.codehaus.org/
Source Code: The source packages for XStream are available from the original software site, or may be acquired
License: XStream is open source software, made available under a BSD license.
Copyright (c) 2003-2006, Joe Walnes
Copyright (c) 2006-2007, XStream Committers
All rights reserved.
following conditions are met: Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation and/or other materials provided with the
distribution. Neither the name of XStream nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH.
157
October 2015
NetCDF
Version: 2.2.22
Description: Used to calculate latitude/longitude points
Software site: http://www.unidata.ucar.edu/software/netcdf-java/
Source Code: The source packages for NetCDF are available from the original software site, or may be acquired
License: Copyright 1993-2008 University Corporation for Atmospheric Research/Unidata
Portions of this software were developed by the Unidata Program at the University Corporation for Atmospheric
Research. Access and use of this software shall impose the following obligations and understandings on the user.
The user is granted the right, without any fee or cost, to use, copy, modify, alter, enhance and distribute this
software, and any derivative works thereof, and its supporting documentation for any purpose whatsoever,
provided that this entire notice appears in all copies of the software, derivative works and supporting
documentation. Further, UCAR requests that the user credit UCAR/Unidata in any publications that result from the
use of this software or in any product that includes this software, although this is not an obligation. The names
UCAR and/or Unidata, however, may not be used in any advertising or publicity to endorse or promote any
products or commercial entity unless specific written permission is obtained from UCAR/Unidata. The user also
understands that UCAR/Unidata is not obligated to provide the user with any support, consulting, training or
assistance of any kind with regard to the use, operation and performance of this software nor to provide the user
with any updates, revisions, new versions or "bug fixes."
THIS SOFTWARE IS PROVIDED BY UCAR/UNIDATA "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL UCAR/UNIDATA BE LIABLE FOR ANY SPECIAL,
INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE ACCESS, USE OR PERFORMANCE OF THIS SOFTWARE.
Yahoo Yui widgets
Version: 2.5.2
Description: Javascript based client mapping log widget
Software site: http://developer.yahoo.com/yui/
Source Code: The source packages for Yahoo Yui Widgets are available from the original software site, or may be
License: Software License Agreement (BSD License)
Copyright (c) 2009, Yahoo! Inc. All rights reserved.
Redistribution and use of this software in source and binary forms, with or without modification, are permitted
provided that the following conditions are met: Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution. Neither the name of Yahoo! Inc. nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior written permission of Yahoo! Inc.
158
October 2015
dnsjava
Version: 2.0.6
Description: dnsjava is an implementation of DNS in Java. It supports all defined record types (including the
DNSSEC types), and unknown types. It can be used for queries, zone transfers, and dynamic updates.
Software site: http://www.dnsjava.org/
Source Code: The source packages for dnsjava are available from the original software site, or may be acquired
License: dnsjava is placed under the BSD license. Several files are also under additional licenses; see the individual
files for details.
Copyright (c) 1999-2005, Brian Wellington. All rights reserved.
following conditions are met: Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation and/or other materials provided with the
distribution. Neither the name of the dnsjava project nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
Final notes:
- Thanks to Network Associates, Inc. for sponsoring some of the original dnsjava work in 1999-2000.
- Thanks to Nominum, Inc. for sponsoring some work on dnsjava from 2000 to the present.
Packages That Use Apache License Version 2.0
The following six packages use the Apache License, Version 2.0, January 2004, whose full text is provided under
Apache License Version 2.0, January 2004.
Axis.jar
Version: 1.4
Description: Used to access Prizm APIs exposed through Web Services from WM
Software site: http://ws.apache.org/axis/
Source Code: The source packages for Axis are available from the original software site, or may be acquired from
Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in the
preamble of this document.
JAX RPC 1.1
Version: 1.1
Software site: http://ws.apache.org/axis/
159
October 2015
Source Code: The source packages for JAX RPC 1.1 are available from the original software site, or may be
log4j-1.2.12.jar
Version: 1.2.12
Software site: http://sourceforge.net/projects/log4j
Source Code: The source packages for log4j-1.5.12.jar are available from the original software site, or may be
wsdl4j-1.5.1.jar
Version: 1.5.1
Software site: http://sourceforge.net/projects/wsdl4j
Source Code: The source packages for wsdl4j-1.5.1.jar are available from the original software site, or may be
commons-logging-1.0.4.jar
Version: 1.0.4
Software site: http://commons.apache.org/logging/
Source Code: The source packages for commons-logging-1.0.4.jar are available from the original software site, or
may be acquired from Cambium. To obtain the software from Cambium, please contact Cambium using the
methods described in the preamble of this document.
commons-discovery-0.2.jar
Version: 0.2
Software site: http://commons.apache.org/discovery/
Source Code: The source packages for commons-discovery-0.2.jar are available from the original software site, or
may be acquired from Cambium. To obtain the software from Cambium, please contact Cambium using the
methods described in the preamble of this document.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by
Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the
copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other
entities that control, are controlled by, or are under common control with that entity. For the purposes of this
definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity,
whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii)
beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising
permissions granted by this License. "Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation source, and configuration files. "Object" form
shall mean any form resulting from mechanical transformation or translation of a Source form, including but not
limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall
160
October 2015
mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by
a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the
Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole,
an original work of authorship. For the purposes of this License, Derivative Works shall not include works that
remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works
thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any
modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for
inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or
written communication sent to the Licensor or its representatives, including but not limited to communication on
electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf
of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is
conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been
received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants
to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce,
prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such
Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to
You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section)
patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such
license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was
submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit)
alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent
infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the
date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any
medium, with or without modifications, and in Source or Object form, provided that You meet the following
conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,
trademark, and attribution notices from the Source form of the Work, excluding those notices that do
not pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You
distribute must include a readable copy of the attribution notices contained within such NOTICE file,
excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the
following places: within a NOTICE text file distributed as part of the Derivative Works; within the
Source form or documentation, if provided along with the Derivative Works; or, within a display
generated by the Derivative Works, if and wherever such third-party notices normally appear. The
contents of the NOTICE file are for informational purposes only and do not modify the License. You
may add Your own attribution notices within Derivative Works that You distribute, alongside or as an
addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot
be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license
terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works
161
October 2015
as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions
stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for
inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any
additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of
any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or
product names of the Licensor, except as required for reasonable and customary use in describing the origin of the
Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work
(and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF
ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-
INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for
determining the appropriateness of using or redistributing the Work and assume any risks associated with Your
exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract,
or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in
writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or
consequential damages of any character arising as a result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction,
or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of
such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You
may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations
and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own
behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such
Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by
brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be
enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and
description of purpose be included on the same "printed page" as the copyright notice for easier identification
within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License,
Version 2.0 (the "License"); you may not use this file except in compliance with the License.
You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on
an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
for the specific language governing permissions and limitations under the License.
162
October 2015
THIRD PARTY PUBLICLY AVAILABLE SOFTWARE LEGAL NOTICES AND END USER LICENSE
AGREEMENTS FOR PUBLICLY AVAILABLE SOFTWARE
The Wireless Manager™ software may include Cambium software, commercial third party software, and/or
publicly available (open source) software.
The Cambium software included in the Wireless Manager™ software is copyright (c) by Cambium Networks, LTD
(“Cambium”), and its use is subject to the licenses, terms and conditions of the agreement in force between the
purchaser of the Wireless Manager™ software and Cambium. The commercial third party software that may be
included in or with the Wireless Manager™ software is subject to the licenses, terms and conditions of the
agreement in force between you and Cambium, unless a separate commercial third party software license is
included, in which case, your use of the commercial third party software will then be governed by the separate
commercial third party license. The publicly available software that may be included in or with the Wireless
Manager™ software is listed below. The use of the listed publicly available software is subject to the licenses,
terms and conditions of the agreement in force between you and Cambium, as well as the terms and conditions of
the license of each publicly available software package. Copies of the licenses for the listed publicly available
software, as well as, all attributions, acknowledgements, and software information details, are included below.
Cambium is required to reproduce the software licenses, acknowledgments and copyright notices as provided by
the authors and owners, thus, all such information is provided in its native language form, without modification or
translation.
The publicly available software in the list below includes the publicly available software included by commercial
third party software that is used in the Wireless Manager™ software. The publicly available software included by
Cambium that is used in the Wireless Manager™ software is disclosed in the Cambium Publicly Available Software
Legal Notices and End User License Agreements for Publicly Available Software accompanying the Wireless
Manager™ software.
For instructions on how to obtain a copy of any source code being made publicly available by Cambium related to
software used in the Wireless Manager™ software you may send your request in writing to:
Cambium Networks, LTD
Attention: Open Source Software Manager
1299 E. Algonquin Road
Schaumburg, IL 60196
In your request, please include the version of the Wireless Manager™ software, along with the publicly available
software specifics, such as the publicly available software name and version.
Note: the source code for the publicly available software may be resident on the Cambium product installation
media, or on supplemental Cambium product media and/or Cambium websites. Please reference and review these
entire Third Party Publicly Available Software Legal Notices and End User License Agreements for Publicly Available
Software for the details on location and methods of obtaining the source code.
Note: dependent on the license terms of the publicly available software, source code may not be provided. Please
reference and review these entire Third Party Publicly Available Software Legal Notices and End User License
Agreements for Publicly Available Software for the details on location and methods of obtaining the source code.
To view additional information regarding licenses, acknowledgments and required copyright notices for publicly
available software used in the Wireless Manager™ software, please select “Legal Notices” display from the GUI (if
applicable), or review the legal notices and end user license agreements in the README files or other files created
during installation, in the documentation, on the installation media, or resident in the Wireless Manager™
software.
Cambium Networks, LTD. All other trademarks, logos, and service marks are the property of the respective third
party owners. You are not permitted to use any marks without the prior written consent of Cambium or such third
party which may own the marks.
163
October 2015
Software Included by Commercial Third Party Software
The following are the end user license agreements for publicly available software that commercial third party
software has included.
openorb_tools-1.2.0.jar
Version: 1.2
Description: CORBA
Software Site: http://sourceforge.net/project/showfiles.php?group_id=43608&package_id=36153
Source Code: The source packages for openorb_tools are available from the original software site, or may be
described in this document.
License:
The OpenORB Community Software License, Version 1.0
Copyright (C) 2002 The OpenORB Project. All rights reserved.
disclaimer.
acknowledgment: "This product includes software developed by the OpenORB Community Project
(http://sourceforge.net/projects/openorb/)." together with the due credit statements listed below. Alternately,
this acknowledgment and due credits may appear in the software itself, if and wherever such third-party
acknowledgments normally appear.
DISCLAIMED. IN NO EVENT SHALL THE MEMBERS OF THE OPENORB COMMUNITY PROJECT OR ITS CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals to the OpenORB Community Project.
For more information on the OpenORB Community Project, please refer to
http://sourceforge.net/projects/openorb/.
Due Credits
This product includes software developed by the Apache Software Foundation (http://www.apache.org/),
including the Avalon Framework, Avalon Logkit, and related Excalibur utilities. Due credit to the Apache Software
Foundation is hereby acknowledged.
This product is derived from initial works published under the Exolab Group, (http://www.exolab.org). Due credit
to the Exolab Group is hereby acknowledged. Parts of this software are derived from and subject to the terms of
the Exolab license. A copy of the Exolab license is contained in respective distributions.
Exolab Group License
Copyright (C) 1999-2001 Intalio, Inc. All Rights Reserved.
164
October 2015
Redistribution and use of this software and associated documentation ("Software"), with or without modification,
are permitted provided that the following conditions are met:
1. Redistributions of source code must retain copyright statements and notices. Redistributions must also contain a
copy of this document.
3. The name "ExoLab" must not be used to endorse or promote products derived from this Software without prior
written permission of ExoLab Group. For written permission, please contact info@exolab.org.
4. Products derived from this Software may not be called "ExoLab" nor may "ExoLab" appear in their names
without prior written permission of ExoLab Group. Exolab is a registered trademark of ExoLab Group.
5. Due credit should be given to the ExoLab Group (http://www.exolab.org).
THIS SOFTWARE IS PROVIDED BY INTALIO, INC. AND CONTRIBUTORS ''AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL INTALIO, INC. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
jython.jar
Version: 2.1
Description: Jython is an implementation of the high-level, dynamic, object-oriented language Python written in
100% Pure Java, and seamlessly integrated with the Java platform. It thus allows you to run Python on any Java
platform.
Software Site: http://www.jython.org
Source Code: The source packages for Jython are available from the original software site, or may be acquired
this document.
License:
A. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING JYTHON PYTHON SOFTWARE FOUNDATION
LICENSE VERSION 2
1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or
Organization ("Licensee") accessing and otherwise using this software ("Jython") in source or binary form and its
associated documentation.
2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive,
royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative
works, distribute, and otherwise use Jython alone or in any derivative version, provided, however, that PSF's
License Agreement and PSF's notice of copyright, i.e., "Copyright (c) 2007 Python Software Foundation; All Rights
Reserved" are retained in Jython alone or in any derivative version prepared by Licensee.
3. In the event Licensee prepares a derivative work that is based on or incorporates Jython or any part thereof, and
wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include
in any such work a brief summary of the changes made to Jython.
4. PSF is making Jython available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR
WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS
165
October 2015
ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR

THAT THE USE OF JYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.
5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF JYTHON FOR ANY INCIDENTAL, SPECIAL, OR
CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING JYTHON,
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
6. This License Agreement will automatically terminate upon a material breach of its terms and conditions.
7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint
venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or
trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party.
8. By copying, installing or otherwise using Jython, Licensee agrees to be bound by the terms and conditions of this
License Agreement.
Jython 2.0, 2.1 License
Copyright (c) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Jython Developers. All rights reserved.
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the Jython Developers nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS'' AND ANY EXPRESS OR
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
p6spy.jar
Version: 1.3
Description: Debug Tool
Software Site: http://www.p6spy.com/
Source Code: The source packages for p6spy.jar are available from the original software site, or may be acquired
this document.
License:
The P6Spy Software License, Version 1.2
This license is derived and fully compatible with the Apache Software license, see
http://www.apache.org/LICENSE.txt. Copyright (c) 2001-2003 Andy Martin, Ph.D. and Jeff Goke All rights reserved.
disclaimer.
166
October 2015
acknowledgment:
The original concept and code base for P6Spy was conceived and developed by Andy Martin, Ph.D. who
generously contributed the first complete release to the public under this license. This product was due to
the pioneering work of Andy that began in December of 1995 developing applications that could seamlessly
be deployed with minimal effort but with dramatic results. This code is maintained and extended by Jeff Goke
and with the ideas and contributions of other P6Spy contributors. (http://www.p6spy.com) Alternately, this
acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments
normally appear.
4. The names "P6Spy", "Jeff Goke", and "Andy Martin" must not be used to endorse or promote products derived
from this software without prior written permission. For written permission, please contact license@p6spy.com.
5. Products derived from this software may not be called "P6Spy" nor may "P6Spy" appear in their names without
prior written permission of Jeff Goke and Andy Martin.
DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
Trademark Notices
Sun, the Sun logo, Sun Microsystems, JavaSoft, JavaBeans, JDK, Java, HotJava, HotJava Views, Visual Java, Solaris,
NEO, Joe, Netra, NFS, ONC, ONC+, OpenWindows, PC-NFS, SNM, SunNet Manager, Solaris sunburst design,
Solstice, SunCore, SolarNet, SunWeb, Sun Workstation, The Network Is The Computer, ToolTalk, Ultra,
Ultracomputing, Ultraserver, Where The Network Is Going, Sun WorkShop, XView, Java WorkShop, the Java Coffee
Cup logo, and Visual Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States
and other countries.
Windows, WindowsNT, and Win32 are registered trademarks of Microsoft Corp.
JBoss and JBoss Group are trademarks of Marc Fleury under operation by JBoss Group, LLC.
Sybase, SQL Anywhere, and Adaptive Server Anywhere are trademarks of Sybase, Inc.
Microsoft SQL Server is a trademark of the Microsoft Corporation.
BEA, WebLogic, Tuxedo, and Jolt are registered trademarks, and How Business Becomes E-Business, BEA WebLogic
E-Business Platform, BEA Builder, BEA eLink, BEA WebLogic Enterprise, BEA WebLogic Express, BEA WebLogic
Integration, BEA WebLogic Personalization Server, BEA WebLogic Portal, and BEA WebLogic Server are trademarks
of BEA Systems, Inc.
Oracle is a registered trademark, and ConText, Oracle Alliance and Oracle8 are trademarks or registered
trademarks of Oracle Corporation.
DB2, DB2 OLAP Server, WebSphere, and IBM are trademarks or registered trademarks of International.
Business Machines Corporation in the United States, other countries or both.
MySQL is a trademark of MySQL AB in the United States and other countries.
Other product names mentioned herein and throughout the this web site are the trademarks of their respective
owners.
Zlib
Version: 1.1.14
Description: Compression library used by libpng
167
October 2015
Software Site: http://www.zlib.net

Source Code: The source packages for ZLib are available from the original software site, or may be acquired
this document.
License:
License zlib.h -- interface of the 'zlib' general purpose compression library
version 1.2.2, October 3rd, 2004
Copyright (C) 1995-2004 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held
liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to
alter it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original
software. If you use this software in a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original
software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly jloup@gzip.org
Mark Adler madler@alumni.caltech.edu
Org.w3c.dom
Version: 1
Description: Document Object Model
Software Site: http://www.w3.org/DOM
Source Code: The source packages for Org.w3c.dom are available from the original software site, or may be
License: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
This work (and included software, documentation such as READMEs, or other related items) is being provided by
the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee)
agree that you have read, understood, and will comply with the following terms and conditions.
Permission to copy, modify, and distribute this software and its documentation, with or without modification, for
any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of
the software and documentation or portions thereof, including modifications:
The full text of this NOTICE in a location viewable to users of the redistributed or derivative work. Any pre-existing
intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C Software Short Notice
should be included (hypertext is preferred, text is permitted) within the body of any redistributed or derivative
code.
Notice of any changes or modifications to the files, including the date changes were made.
(We recommend you provide URLs to the location from which the code is derived.)
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR
DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER
168
October 2015
RIGHTS. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the
software without specific, written prior permission. Title to copyright in this software and any associated
documentation will at all times remain with copyright holders.
LibPNG
Version: 1.2.5
Description: PNG encoding/decoding
Software Site: http://www.libpng.org/pub/png/libpng.html
Source Code: The source packages for PNG are available from the original software site, or may be acquired from
Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in this
document.
License:
This copy of the libpng notices is provided for your convenience. In case of any discrepancy between this copy and
the notices in the file png.h that is included in the libpng distribution, the latter shall prevail.
COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
If you modify libpng you may insert additional notices immediately following this sentence.
libpng versions 1.2.6, August 15, 2004, through 1.2.35, February 14, 2009, are Copyright (c) 2004, 2006-2008 Glenn
Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-1.2.5 with the
following individual added to the list of Contributing Authors:
Cosmin Truta
libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are Copyright (c) 2000-2002 Glenn Randers-
Pehrson, and are distributed according to the same disclaimer and license as libpng-1.0.6 with the following
individuals added to the list of Contributing Authors:
Simon-Pierre Cadieux
Eric S. Raymond
Gilles Vollant
and with the following additions to the disclaimer:
There is no warranty against interference with your enjoyment of the library or against infringement. There is
no warranty that our efforts or the library will fulfill any of your particular purposes or needs. This library is
provided with all faults, and the entire risk of satisfactory quality, performance, accuracy, and effort is with
the user.
libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are Copyright (c) 1998, 1999 Glenn Randers-
Pehrson, and are distributed according to the same disclaimer and license as libpng-0.96, with the following
individuals added to the list of Contributing Authors:
Tom Lane
Glenn Randers-Pehrson
Willem van Schaik
libpng versions 0.89, June 1996, through 0.96, May 1997, are Copyright (c) 1996, 1997 Andreas Dilger Distributed
according to the same disclaimer and license as libpng-0.88, with the following individuals added to the list of
Contributing Authors:
John Bowler
Kevin Bracey
Sam Bushell
Magnus Holmgren
169
October 2015
Greg Roelofs
Tom Tanner
libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright (c) 1995, 1996 Guy Eric Schalnat, Group
42, Inc. For the purposes of this copyright and license, "Contributing Authors" is defined as the following set of
individuals:
Andreas Dilger
Dave Martindale
Guy Eric Schalnat
Paul Schmidt
Tim Wegner
The PNG Reference Library is supplied "AS IS". The Contributing Authors and Group 42, Inc. disclaim all warranties,
expressed or implied, including, without limitation, the warranties of merchantability and of fitness for any
purpose. The Contributing Authors and Group 42, Inc. assume no liability for direct, indirect, incidental, special,
exemplary, or consequential damages, which may result from the use of the PNG Reference Library, even if
advised of the possibility of such damage.
Permission is hereby granted to use, copy, modify, and distribute this source code, or portions hereof, for any
purpose, without fee, subject to the following restrictions:
1. The origin of this source code must not be misrepresented.
2. Altered versions must be plainly marked as such and must not be misrepresented as being the original source.
3. This Copyright notice may not be removed or altered from any source or altered source distribution.
The Contributing Authors and Group 42, Inc. specifically permit, without fee, and encourage the use of this source
code as a component to supporting the PNG file format in commercial products. If you use this source code in a
product, acknowledgment is not required but would be appreciated.
A "png_get_copyright" function is available, for convenient use in "about" boxes and the like:
printf("%s",png_get_copyright(NULL));
Also, the PNG logo (in PNG format, of course) is supplied in the files "pngbar.png" and "pngbar.jpg (88x31) and
"pngnow.png" (98x31).
Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a certification mark of the Open Source
Initiative.
Glenn Randers-Pehrson
glennrp@users.sourceforge.net
February 14, 2009
Packages That Use GNU Lesser General Public License Version 2.1
The following nine packages use the GNU LESSER GENERAL PUBLIC LICENSE, Version 2.1, February 1999, whose full
text is provided under GNU Lesser General Public License Version 2.1, February 1999.
jasperreports.jar
Version: 1.0
Description: Jasper Reports
Source Code: The source packages for jasperreports.jar are available from the original software site, or may be
170
October 2015
Jfreechart.jar
Version: 0.9.15
Description: Charting tool
Source Code: The source packages for Jfreechart.jar are available from the original software site, or may be
bsh-1.2b3.jar
Version: 1.2
Description: Scripting files
Software Site: Source code not available from AdventNet
Source Code: The source packages for bsh-1.2b3.jar are available from the original software site, or may be
jvcs.jar
Version: 2.1
Description: Scripting tool
Software Site: http://www.jcvs.org/download/jcvs/jcvs-522.tgz
Source Code: The source packages for Jvcs are available from the original software site, or may be acquired from
document.
ftp.jar
Version: 2.1
Description: FTP package
Software Site: http://www.enterprisedt.com/downloads/ftp/ftp-1.1.tar.gz
Source Code: The source packages for FTP are available from the original software site, or may be acquired from
document.
jcommon
Version: 1.0.0
Description: General purpose classes used by Jfree chart
Software Site: http://www.jfree.org/jcommon/download/
Source Code: The source packages for jcommon are available from the original software site, or may be acquired
this document.
MySQL Connector
Version:
Linux-MM.MySQL - 3.0.8
Solaris-MM.MySQL - 3.0.8
Windows-MM.MySQL - 3.0.8
Description: JDBC Driver
Software Site: http://Mysql.com
Source Code: The source packages for MySQL Connector are available from the original software site, or may be
171
October 2015
itext-1.02b.jar
Version: 1.0.2
Description: Text Parser
Software Site: http://www.lowagie.com/iText/
Source Code: The source packages for itext are available from the original software site, or may be acquired from
document.
j2ssh-common.jar, j2ssh-core.jar (SSHTools)
Version: j2ssh0.2.7
Description: SSH Tools
Source Code: The source packages for SSH Tools are available from the original software site, or may be acquired
this document.
GNU Lesser General Public License
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not
allowed.
[This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public
License, version 2, hence the version number 2.1.]
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the
GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make
sure the software is free for all its users.
This license, the Lesser General Public License, applies to some specially designated software packages--typically
libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we
suggest you first think carefully about whether this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are
designed to make sure that you have the freedom to distribute copies of free software (and charge for this service
if you wish); that you receive source code or can get it if you want it; that you can change the software and use
pieces of it in new free programs; and that you are informed that you can do these things.
To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you
to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of
the library or if you modify it.
For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the
rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other
code with the library, you must provide complete object files to the recipients, so that they can relink them with
the library after making changes to the library and recompiling it. And you must show them these terms so they
know their rights.
We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license,
which gives you legal permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the
library is modified by someone else and passed on, the recipients should know that what they have is not the
172
October 2015
original version, so that the original author's reputation will not be affected by problems that might be introduced
by others.
Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a
company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent
holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with
the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license,
the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the
ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries
into non-free programs.
When a program is linked with a library, whether statically or using a shared library, the combination of the two is
legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore
permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License
permits more lax criteria for linking other code with the library.
We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the
ordinary General Public License. It also provides other free software developers Less of an advantage over
competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for
many libraries. However, the Lesser license provides advantages in certain special circumstances.
For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain
library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the
library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case,
there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free programs enables a greater number of people to
use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables
many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.
Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of
a program that is linked with the Library has the freedom and the wherewithal to run that program using a
modified version of the Library.
The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the
difference between a "work based on the library" and a "work that uses the library". The former contains code
derived from the library, whereas the latter must be combined with the library in order to run.
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or other program which contains a notice placed by the
copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General
Public License (also called "this License"). Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with
application programs (which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work which has been distributed under these terms. A
"work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a
work containing the Library or a portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is included without limitation in the term
"modification".)
"Source code" for a work means the preferred form of the work for making modifications to it. For a library,
complete source code means all the source code for all modules it contains, plus any associated interface
definition files, plus the scripts used to control compilation and installation of the library.
Activities other than copying, distribution and modification are not covered by this License; they are outside its
scope. The act of running a program using the Library is not restricted, and output from such a program is covered
173
October 2015
only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does and what the program that uses the Library
does.
1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any
medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice
and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the Library.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty
protection in exchange for a fee.
2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library,
and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also
meet all of these conditions:
* a) The modified work must itself be a software library.
* b) You must cause the files modified to carry prominent notices stating that you changed the files and the
date of any change.
* c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of
this License.
* d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application
program that uses the facility, other than as an argument passed when the facility is invoked, then you must
make a good faith effort to ensure that, in the event an application does not supply such function or table,
the facility still operates, and performs whatever part of its purpose remains meaningful.
(For example, a function in a library to compute square roots has a purpose that is entirely well-defined
independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table
used by this function must be optional: if the application does not supply it, the square root function must still
compute square roots.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived
from the Library, and can be reasonably considered independent and separate works in themselves, then this
License, and its terms, do not apply to those sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole
must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus
to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather,
the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.
In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on
the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this
License.
3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given
copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the
ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not
make any other change in these notices.
Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public
License applies to all subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or
executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete
corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2
above on a medium customarily used for software interchange.
174
October 2015
If distribution of object code is made by offering access to copy from a designated place, then offering equivalent
access to copy the source code from the same place satisfies the requirement to distribute the source code, even
though third parties are not compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by
being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a
derivative work of the Library, and therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the
Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is
therefore covered by this License. Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for
the work may be a derivative work of the Library even though the source code is not. Whether this is true is
especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for
this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and
small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of
whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still
fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the
terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked
directly with the Library itself.
6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the
Library to produce a work containing portions of the Library, and distribute that work under terms of your choice,
provided that the terms permit modification of the work for the customer's own use and reverse engineering for
debugging such modifications.
You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its
use are covered by this License. You must supply a copy of this License. If the work during execution displays
copyright notices, you must include the copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one of these things:
* a) Accompany the work with the complete corresponding machine-readable source code for the Library
including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above);
and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses
the Library", as object code and/or source code, so that the user can modify the Library and then relink to
produce a modified executable containing the modified Library. (It is understood that the user who changes
the contents of definitions files in the Library will not necessarily be able to recompile the application to use
the modified definitions.)
* b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1)
uses at run time a copy of the library already present on the user's computer system, rather than copying
library functions into the executable, and (2) will operate properly with a modified version of the library, if
the user installs one, as long as the modified version is interface-compatible with the version that the work
was made with.
* c) Accompany the work with a written offer, valid for at least three years, to give the same user the
materials specified in Subsection 6a, above, for a charge no more than the cost of performing this
distribution.
* d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent
access to copy the above specified materials from the same place.
* e) Verify that the user has already received a copy of these materials or that you have already sent this user
a copy.
175
October 2015
For an executable, the required form of the "work that uses the Library" must include any data and utility
programs needed for reproducing the executable from it. However, as a special exception, the materials to be
distributed need not include anything that is normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that
component itself accompanies the executable.
It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not
normally accompany the operating system. Such a contradiction means you cannot use both them and the Library
together in an executable that you distribute.
7. You may place library facilities that are a work based on the Library side-by-side in a single library together with
other library facilities not covered by this License, and distribute such a combined library, provided that the
separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and
provided that you do these two things:
* a) Accompany the combined library with a copy of the same work based on the Library, uncombined with
any other library facilities. This must be distributed under the terms of the Sections above.
* b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library,
and explaining where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this
License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will
automatically terminate your rights under this License. However, parties who have received copies, or rights, from
you under this License will not have their licenses terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not signed it. However, nothing else grants you
permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do
not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you
indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or
modifying the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a
license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and
conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with this License.
11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not
limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that
contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations,
then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit
royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the
only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the
section is intended to apply, and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to
contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software
distribution system which is implemented by public license practices. Many people have made generous
contributions to the wide range of software distributed through that system in reliance on consistent application
of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other
system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted
interfaces, the original copyright holder who places the Library under this License may add an explicit geographical
distribution limitation excluding those countries, so that distribution is permitted only in or among countries not
thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
176
October 2015
13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License
from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Library specifies a version number of this License
which applies to it and "any later version", you have the option of following the terms and conditions either of that
version or of any later version published by the Free Software Foundation. If the Library does not specify a license
version number, you may choose any version ever published by the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are
incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of
promoting the sharing and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE
EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY
IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT
HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE,
BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF
THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend
making it free software that everyone can redistribute and change. You can do so by permitting redistribution
under these terms (or, alternatively, under the terms of the ordinary General Public License).
To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each
source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright"
line and a pointer to where the full notice is found.
one line to give the library's name and an idea of what it does.
Copyright (C) year name of author
This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General
Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option)
any later version.
This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the
implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General
Public License for more details.
You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to
the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Also add information on how to contact you by electronic and paper mail.
177
October 2015
You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright
disclaimer" for the library, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in
the library `Frob' (a library for tweaking knobs) written by James Random Hacker.
signature of Ty Coon, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!
Packages That Use Apache Software License Version 1.1
The following four packages use the Apache Software License, Version 1.1, © 2001-2003, whose full text is
provided under Apache Software License Version 1.1.
Log4j
Version: 1.2.12
Description: Log Framework
Software Site: http://logging.apache.org/log4j/1.2/index.html
Source Code: The source packages for Log4j are available from the original software site, or may be acquired from
document.
Struts
Version: 1.1
Description: Web Framework
Software Site: http://www.apache.org/dist/jakarta/struts/binaries/jakarta-struts-1.1.zip
Source Code: The source packages for Struts are available from the original software site, or may be acquired from
document.
Apache
Version: 2.0.47
Description: The Apache HTTP Server provides a secure, efficient and extensible server that provides HTTP
services in sync with the current HTTP standards.
Software Site: http://www.apache.org/dist/httpd/
Source Code: The source packages for Apache are available from the original software site, or may be acquired
this document.
TomCat
Version: 4.1.27
Description: Apache Tomcat is an implementation of the Java Servlet and JavaServer Pages technologies. The Java
Servlet and JavaServer Pages specifications are developed under the Java Community Process.
Software Site: http://tomcat.apache.org/download-41.cgi
Source Code: The source packages for TomCat are available from the original software site, or may be acquired
this document.
Apache Software License
Version 1.1
Copyright (c) 2001-2003 Ant-Contrib project. All rights reserved.
178
October 2015
disclaimer.
acknowledgment:
"This product includes software developed by the Ant-Contrib project
(http://sourceforge.net/projects/ant-contrib)." Alternately, this acknowledgment may appear in the software
itself, if and wherever such third-party acknowledgments normally appear.
4. The name Ant-Contrib must not be used to endorse or promote products derived from this software without
prior written permission. For written permission, please contact ant-contrib-developers@lists.sourceforge.net.
5. Products derived from this software may not be called "Ant-Contrib" nor may "Ant-Contrib" appear in their
names without prior written permission of the Ant-Contrib project.
DISCLAIMED. IN NO EVENT SHALL THE ANT-CONTRIB PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
179
October 2015
Abbreviations
API Application Programming Interface
BZ2 BZIP2 compression scheme for file data; not as efficient as PBF for offline map
data
DHCP Dynamic Host Configuration Protocol
DNS Domain Name Server
EMS Element Management System
GUI Graphical User Interface
IP Internet Protocol
JDBC Java database Connectivity
MAC Media Access Control
WMSDB Wireless Manager Database
MIB Management Information Base
NBI North Bound Interface
NMI Network Management Information (Server)
NMS Network Management System
OID Object Identifier
OSM OpenStreetMap file type for offline map data
PBF File type for high-compression vector offline maps
RDBMS Relational Database Management System
SMI Structure Management Information
SNMP Simple Network Management Protocol
UDP User Datagram Protocol
UI User Interface
VLAN Virtual Local Area Network
181
October 2015
Technical Support
Before you contact the Cambium Networks support representatives, it is typically advisable to run the
Support Tool and avoid deleting any of the files that it generates. After you run the tool and attempt
to solve the problem by using the documentation and the troubleshooting methods that its
procedures and descriptions imply, you can contact your designated representative as indicated in
Contacting Support Representatives.
Running the Customer Support Tool

WM provides a tool for users on the client application or the administrator on the server to launch
when trouble exceeds local diagnostic efforts. This tool assembles into one or more encryptable files
most of the information that Support representatives require to diagnose typical problems
encountered in WM operations. The tool also allows the operator to split the file to
 enable transmittal of files that the tool outputs as larger than 1.5 MB.
 speed up transmittal of files that are between 1 and 1.5 MB in size.
Options for Running the Support Tool

Depending on whether the tool is launched from the client application or the WM server, the data
may include
 various WM log files.
 license file contents and usage, if WM and License Manager run on the same machine.
 the platform and environment on which the WM server operates.
 device templates, including any that were locally created or modified.
 WM configuration (all xml) files.
 installation logs.
 the identification of all running processes.
 individual device data for selected devices.
 additional information that you voluntarily enter in the interface to the tool.
If the tool is launched from both the client and the server, then the composite of the data files that
the tool produces can include all of the above listed information. By default, the tool stores the
output in the file system of the server device.
Running the Tool from the Server

When run from the server (by executing C:\Cambium\WM\server\bin\SupportTool.bat
or /usr/local/cambium/WM/server/bin/SupportTool.sh), the tool does not collect
information from the database. Typically, this is recommended only when the server process is not
running. The resulting data is limited to information about the environment, WM configuration files,
and extra logs. However, the server administrator can attach additional, locally written scripts in
VisualBasic, Perl, shell, and or SQL by adding their file names to an externalscripts list in the server.
This is especially useful under the direction of a Cambium Networks support representative.
183
October 2015
Instructions for running the tool from the client application are provided in the user guide section
titled "Technical Support."
Contacting Support Representatives

You can obtain support for Wireless Manager from any or all of the following sources:
 Wireless Manager setup guide, administration guide, and release notes.
 Cambium Networks support web page: http://www.cambiumnetworks.com/support.
This page provides links to information on all products and tools, as well as access to
customer support materials and interactive support forums. Some of these resources are
restricted to registered users and channel partners.
 the Community Forum. Visit http://community.cambiumnetworks.com/ .
 direct contact with Cambium Networks Technical Support. This contact is available 7 days
a week, 24 hours a day. To find the appropriate phone number based on your country or
region, visit http://www.cambiumnetworks.com/support/contact-support/.
 a technical support case, which you can open at
http://www.cambiumnetworks.com/support/open-a-support-case. The case captures basic
information about answers you are seeking or the problem that your network is
experiencing and provides this to the support team, who are available 7 days a week,
24 hours a day, and will respond. They will also provide a case number by which you and
they can continue to track progress on issues that require deeper investigation.
184

WM4 4AndLaterServerAdministrationGuideIssue2 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WM4 4AndLaterServerAdministrationGuideIssue2 PDF

Uploaded by

Copyright:

Available Formats

Cambium

Issue 2 October 2015

© 2015 Cambium Networks, Inc. All Rights Reserved.

1 About This Administration Guide

Immediately after your server installation is completed, visit

1.1 New in This Issue

 PTP 650 v01-40 Support

This chapter describes the scope of this guide and provides

Chapter 6, Fault Management Configuration describes server-side adjustments to how WM

Chapter 7, Performance Management Configuration describes server-side adjustments to how WM

Chapter 8, Security Management Configuration describes server-side adjustments to how WM

1.3 References to Other WM Documents

1.4 Links to Other Important Documents

− PMP 450 at http://www.cambiumnetworks.com/products/pmp/pmp-450/

1.5 Feedback on This Guide

1.6 References to Starting and Stopping the WM

2 Management of the WM Server Device

2.1 Server Requirements

2.1.1 Server Hardware Requirements

Table 1: Hardware requirements for the WM server

RAM 4 GB 8 GB 8 GB for ≤ 100 nodes

processor dual-core ≥ 2 GHz quad-core ≥ 2 GHz 2 GHz

storage RAID 1 RAID 5, ≥ RAID 1 for ≤ 100 nodes

uninterruptible power highly recommended highly recommended highly recommended

scheme for graceful highly recommended highly recommended highly recommended

2.1.2 Server Software Requirements

Table 2: Software requirements for the WM server

Requirement type Version

Firewall See Port Management.

Java Installed as part of the WM distribution

database MySQL Server Version 5.1, optionally installed by the WM

licensing License Manager, installed by the WM distribution tool

dos2unix package WM on Cent-OS requires that the dos2unix package is

if virtualization is installed VMware vSphere. See

2.2 Client Requirements

2.2.1 Client Hardware Requirements

Table 3: Hardware requirements for the WM client application

hardware class any modern desktop or laptop

link speed 1 Mbps

screen resolution 1024 x 768

2.2.2 Client Software Requirements

Table 4: Software requirements for the WM client application

Requirement Software and version

Browser Mozilla Firefox 3, 32-bit, if the client is

2.3 Local Setup for Launches of Included Tools

Procedure 1: To set up Windows to allow all Administrators to launch WM tools

2.4 Port Management

Table 5: Ports that must be open

Server Port Usage

80 Outbound connection to BAM server to launch its interface.

161 Inbound UDP for the northbound interface (NBI).

161 Outbound UDP for device SNMP queries and configurations.

162 Inbound UDP for SNMP traps from devices.

1234 Inbound UDP for APs to request authentications from BAM.

1476 Configuration server.

1482 Socket server.

2000 Network management back-end server.

2501 To turn the SM Autoupdate feature on or off in APs.

WM 3306 Queries to the MySQL database.

Outbound UDP for SNMP response over the northbound interface

TCP connections by Tomcat and web server for access to device

8090 Inbound data from the BAM server.

9090 Inbound TCP for the web server.