WM4_0ServerAdministrationGuideIssue2 by Advantec Distribution

Cambium Wireless Manager Server Administration Guide System Release 4.0

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 on Page 133. © 2012 Cambium Networks, Inc. All Rights Reserved.

Table of Contents Accuracy...................................................................................................................................... 2 Copyrights ................................................................................................................................... 2 Restrictions ................................................................................................................................. 2 License Agreements.................................................................................................................... 2

About This Administration Guide ....................................................................13 1.1

Features New in Release 4.0......................................................................................... 14

1.2

Corrections in This Guide.............................................................................................. 14

1.3

Chapters........................................................................................................................ 15

1.4

References to Other WM Documents .......................................................................... 16

1.5

Links to Other Important Documents........................................................................... 16

1.6

Feedback on This Guide ................................................................................................ 17

1.7

References to Starting and Stopping the WM Service ................................................. 17

Management of the WM Server Device ............................................................19 2.1

Local Setup for Launches of Included Tools ................................................................. 19

2.2

Port Management......................................................................................................... 20

2.3

Network Interface Management .................................................................................. 22

2.4

IP Address Change for the WM Server ......................................................................... 22

2.5

Use of an Uninterruptible Power Supply...................................................................... 23

2.6

Placement of pkg3 Files for Network Element Upgrades............................................. 23

MySQL Database Administration .....................................................................25 3.1

Changing the Database Authentication in WM ............................................................ 25

3.2

Starting the Database ................................................................................................... 25

3.3

Re‐initializing the Database .......................................................................................... 25

3.4

Restoring the WM Default Database Configuration..................................................... 26

3.5

Backing Up the Entire Database ................................................................................... 26

3.6

Restoring the Entire Database...................................................................................... 27

3.7

Maintaining the Integrity of the Database ................................................................... 27

3.7.1 3.7.2

Addressing Table Corruption on a Linux Platform ................................................................ 27 Addressing Continuous Growth of Data Files on a Windows Platform................................. 28

Network Discovery Setup and Debug...............................................................31 4.1

Reading Discovery Debug Messages ............................................................................ 31

4.2

Temporarily Disabling Updates to the Physical Map to Speed Up Discovery .............. 32

4.3

Getting Generic Elements Discovered .......................................................................... 33

4.4

Expanding or Shrinking Areas for Presumed Logical Relationships.............................. 34

Predefined Information Structures for Device Support ........................................37

Fault Management Configuration .....................................................................39 6.1

Opening Trap Ports ....................................................................................................... 39

6.2

Enabling Print for Events and Alarms ........................................................................... 39

6.2.1 6.2.2 6.2.3

6.3

Enabling Print in Windows .................................................................................................... 40 Enabling Print in Linux ........................................................................................................... 41 Enhancing the Printed Output .............................................................................................. 41

Configuring Fault Management Parameters ................................................................ 41

Performance Management Configuration ..........................................................47 7.1

Managed Objects.......................................................................................................... 47

7.2

Operator‐defined Reports ............................................................................................ 50

Security Management Configuration.................................................................53 8.1

Defining and Managing a Group or a User ................................................................... 53

8.2

Defining and Managing Authorized and Custom View Scopes .................................... 54

8.3

Adding and Managing Operations ................................................................................ 54

8.4

Enabling the Authorized Mode for Security Operations .............................................. 54

8.5

Configuring Security Management Parameters ........................................................... 56

8.6

Managing Expiry for User Accounts and Passwords..................................................... 56

8.7

Restoring a Deleted superuser Account ....................................................................... 56

Offline Physical Map Setup .............................................................................59 9.1

Deploying GeoServer .................................................................................................... 59

9.2

Creating Map Layers ..................................................................................................... 60

9.3

Pre‐caching the Map Images ........................................................................................ 62

User Scripts Setup .....................................................................................63

Management of WM Server Logs..................................................................65

WM Software Upgrades and Downgrades......................................................67

12.1

WM Upgrade to Release 4.0......................................................................................... 67

12.2

Optimization of System Resources ............................................................................... 78

12.3

Optimization of Operator‐installed Database .............................................................. 79

12.4

Migration of Operator Data Through WM Upgrade Plus OS Upgrade......................... 80

12.5

Service Pack or Feature Pack Installation ..................................................................... 81

12.6

Service Pack or Feature Pack Uninstallation................................................................. 85

12.7

WM Downgrade from Release 4.0 ............................................................................... 87

WM Software and Feature Licensing .............................................................91

13.1

License Types ................................................................................................................ 91

13.2

Calculation of the Number of Nodes to be Licensed.................................................... 91

13.3

Notifications of License Limits ...................................................................................... 92

13.4

WM License Replacement ............................................................................................ 92

13.5

Recovery From Forgotten Password for the License Manager Administrator Tool..... 92

13.6

Deployment of Redundant License Manager Servers .................................................. 94

13.6.1 13.6.2 13.6.3

13.7

Workaround for a License Server Failure ..................................................................... 97

13.7.1 13.7.2 13.7.3

Purpose of Redundancy .................................................................................................... 94 Configuration of License Key Files for Redundancy.......................................................... 94 Redundancy Deployment Process .................................................................................... 95 Failure or Reboot of a License Manager Server................................................................ 97 Change in the IP Address of a License Manager Server.................................................... 98 Server Restarts in LM Redundancy ................................................................................... 98

WM Administrator Tool for Server Administration ..........................................99

14.1

Using the WM Server Panel .......................................................................................... 99

14.2

Configuring the BAM Panel......................................................................................... 101

14.3

Configuring the Database Panel ................................................................................. 102

14.4

Using the Licensing Panel ........................................................................................... 103

14.5

Configuring the NBI Panel........................................................................................... 106

14.6

Using the Offline Physical Map Panel ......................................................................... 107

14.7

Configuring the Email Configuration Panel ................................................................ 109

MIB Browser Usage..................................................................................111

15.1

Invoking the MIB Browser .......................................................................................... 111

15.2

Configuring the MIB Browser ..................................................................................... 112

15.2.1 15.2.2 15.2.3 15.2.4 15.2.5 15.2.6 15.2.7

Setting Common Parameters.......................................................................................... 112 Storing Table Entries in a Serialized File ......................................................................... 115 Storing Table Entries in a Database ................................................................................ 115 Setting MIB Parameters .................................................................................................. 116 Loading MIBs................................................................................................................... 116 Unloading MIBs............................................................................................................... 118 Performing SNMP Operations ........................................................................................ 119

15.2.8

Setting SNMP Table Options........................................................................................... 122

15.3

Interpreting MIB Browser Error Messages ................................................................. 125

15.4

FAQs ............................................................................................................................ 130

Legal Notices and License Agreements .................................................................133 CAMBIUM NETWORKS, LTD END USER LICENSE AGREEMENT............................................... 133 CAMBIUM PUBLICLY AVAILABLE SOFTWARE LEGAL NOTICES AND END USER LICENSE AGREEMENTS FOR PUBLICLY AVAILABLE SOFTWARE ............................................................ 138 Software Included by Cambium.............................................................................................. 139 Packages That Use Apache License Version 2.0 ..................................................................... 143 THIRD PARTY PUBLICLY AVAILABLE SOFTWARE LEGAL NOTICES AND END USER LICENSE AGREEMENTS FOR PUBLICLY AVAILABLE SOFTWARE ............................................................ 147 Software Included by Commercial Third Party Software ....................................................... 148 Packages That Use GNU Lesser General Public License Version 2.1 ...................................... 154 Packages That Use Apache Software License Version 1.1...................................................... 162

Abbreviations ....................................................................................................165 Technical Support..............................................................................................167 Running the Customer Support Tool ...................................................................................... 167 Options for Running the Support Tool.................................................................................... 167 Contacting Support Representatives...................................................................................... 168

List of Figures Figure 1: Security Administration Tree – Group Operations ...................................................................... 55 Figure 2: Command option to upload an individual license file to License Manager................................. 75 Figure 3: Update Manager interface........................................................................................................... 82 Figure 4: Service pack Installation Wizard .................................................................................................. 83 Figure 5: Service pack Readme window ..................................................................................................... 84 Figure 6: Service pack Uninstall window .................................................................................................... 85 Figure 7: Service pack Uninstallation status panel ..................................................................................... 86 Figure 8: Licensing Configuration panel in License Manager web server................................................... 96 Figure 9: Licensing Status panel in License Manager web server............................................................... 97 Figure 10: WM Server panel of WM Administrator Tool............................................................................ 99 Figure 11: BAM panel of WM Administrator Tool .................................................................................... 101 Figure 12: Database panel of WM Administrator Tool ............................................................................. 102 Figure 13: Licensing panel of WM Administrator Tool ............................................................................. 103 Figure 14: Upload License File dialog........................................................................................................ 104 Figure 15: License Manager Status display window ................................................................................. 105 Figure 16: NBI panel of WM Administrator Tool, active SNMP V3 settings ............................................. 106 Figure 17: NBI panel of WM Administrator Tool, active SNMP V1/V2 settings ....................................... 107 Figure 18: Offline Physical Map panel of WM Administrator Tool ........................................................... 108 Figure 19: Email Configuration panel of WM Administrator Tool ............................................................ 110 Figure 20: MIB Browser main GUI............................................................................................................. 111 Figure 21: MibBrowser Settings dialog ..................................................................................................... 113 Figure 22: Load a MIB File Panel—MIB Settings Tab ................................................................................ 117 Figure 23: SNMP Table.............................................................................................................................. 122 Figure 24: SNMP Table Settings Panel ...................................................................................................... 123

List of Tables Table 1: Ports that must be open ............................................................................................................... 20 Table 2: Structured information resources per general device type.......................................................... 37 Table 3: Fault Management configurable fields ......................................................................................... 41 Table 4: Performance Management configurable fields ............................................................................ 47 Table 5: Log files present by default ........................................................................................................... 65 Table 6: Recommended MySQL parameter values..................................................................................... 79 Table 7: MibBrowser General tab fields ................................................................................................... 113 Table 8: Security parameters for accessing SNMPv3 agents .................................................................... 114 Table 9: MibBrowser Error Messages ....................................................................................................... 125

List of Procedures Procedure 1: To set up Windows to allow all Administrators to launch WM tools ................................... 19 Procedure 2: To configure server‐client communications after installation .............................................. 21 Procedure 3: To start the MySQL daemon as a server on Linux................................................................. 25 Procedure 4: To re‐initialize the MySQL database ..................................................................................... 25 Procedure 5: To restore the installed WM database configuration ........................................................... 26 Procedure 6: To detect and repair corrupted MyISAM database tables.................................................... 28 Procedure 7: To reclaim hard drive space from burgeoning database files............................................... 29 Procedure 8: To temporarily disable updates to the physical map display................................................ 32 Procedure 9: To enable authorization support........................................................................................... 54 Procedure 10: To restore the superuser account and the security tool cache .......................................... 57 Procedure 11: To deploy GeoServer ........................................................................................................... 59 Procedure 12: To create a layer from one image ....................................................................................... 60 Procedure 13: To create a data store for GeoServer workspace images ................................................... 60 Procedure 14: To verify that GeoServer connects to the image data store ............................................... 61 Procedure 15: To add an image to an existing layer................................................................................... 61 Procedure 16: To pre‐cache all tiles for all levels of zoom ......................................................................... 62 Procedure 17: To upgrade WM to Release 4.0........................................................................................... 68 Procedure 18: To optimize the system resources for WM ......................................................................... 78 Procedure 19: To optimize your custom database for WM Release 4.0 .................................................... 80 Procedure 20: To migrate operator data in upgrade of WM plus the OS .................................................. 80 Procedure 21: To install a service pack or feature pack ............................................................................. 82 Procedure 22: To uninstall a service pack or feature pack ......................................................................... 85 Procedure 23: To reset the License Manager Administrator Tool password ............................................. 93 Procedure 24: To deploy redundant license servers .................................................................................. 95 Procedure 25: To configure WM for offline physical map images ........................................................... 108 Procedure 26: To reconfigure offline physical map images in WM.......................................................... 109 Procedure 27: To configure server and admin email settings .................................................................. 110 Procedure 28: To invoke the MIB Browser ............................................................................................... 111

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

1 About This Administration Guide important ........... The installation tool for the WM server deposits an issue of the Cambium Wireless Manager Release 4.0 Server Administration Guide and the Cambium Wireless Manager Release 4.0 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/planning/index.php?cat=1&type=0. 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 Release 4.0, 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 4.0 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

Wireless Manager Release 4.0 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

Issue 2 April 2012

1.1

WM Release 4.0 Server Administration Guide

Features New in Release 4.0 Release 4.0 introduces the following features: 

elimination of the need for operators to have their own physical map licenses. This is reflected in −

License Types on Page 91.

−

Notifications of License Limits on Page 92

−

Procedure 17: To upgrade WM to Release 4.0 on Page 68



a system‐configured view of events that are related to discovery. As with items that the Network Events view lists, these Discovery Events view items are stored in the database for seven days, unless operator configured for removal at a shorter or longer interval, which can be accomplished by editing the value of the CLEAN_EVENT_INTERVAL parameter in the NmsProcessesBE.conf file in the WM server. See Configuring Fault Management Parameters on Page 41.



synchronization functions (buttons) added to the WM Server panel of the WM Administrator Tool to launch removal of all events, alarms, and traps in process, while leaving all elements' statistics untouched. See Using the WM Server Panel on Page 99.



removal of the System Administration web interface. This affects Procedure 10: To restore the superuser account and the security tool cache on Page 57, which is revised to use the Security Administration tool in the WM client application.



various other improvements that are documented in the release notes and/or the user guide.

For existing WM operators, the upgrade path to Release 4.0 and upgrade procedure are provided under WM Upgrade to Release 4.0 on Page 67.

1.2

Corrections in This Guide Step 8 of Procedure 7: To reclaim hard drive space from burgeoning database files on Page 29 has been removed. The backup files that Step 8 advised the operator to create are in fact created by MySQL when it restarts. Using any other backups for these can cause problems.

WM Release 4.0 Server Administration Guide

1.3

Issue 2 April 2012

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. 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, User Scripts Setup provides the proper path and mode for mounting operator‐defined scripts on the server. Chapter 11, Management of WM Server Logs describes how to manage logs that the server logs. Chapter 12, WM Software Upgrades and Downgrades describes how to upgrade WM to Release 4.0.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Chapter 13, WM Software and Feature Licensing describes the licensing and license management schemes that Release 4.0 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 14, 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 15, MIB Browser Usage describes how to invoke, configure, and troubleshoot the embedded MIB browser.

1.4

References to Other WM Documents If you are a client administrator or user, use the Cambium Wireless Manager Release 4.0 User Guide. For high‐level descriptions of new features included in the initial distribution of Release 4.0, or for all disclosures about features that this distribution supports, see the Cambium Wireless Manager Release 4.0 Release Notes. For documentation support with BAM integration, see the following documentation:

1.5



Cambium Wireless Manager 4.0 Quick Start Guide



Procedure 17: To upgrade WM to Release 4.0 on Page 68 of this server administration guide



Cambium Wireless Manager 4.0 User Guide

Links to Other Important Documents For links to important documents about supported network elements, visit the following web pages: 

PTP device and PTP LINKPlanner user guides and release notes at http://www.cambiumnetworks.com/support/ptp/software/index.php?tag=linkplanner



PMP device user guides, release notes, and MIBs at http://www.cambiumnetworks.com/support/pmp/software/index.php



a wide range of PMP 320 device documents at http://www.cambiumnetworks.com/support/pmp/software/index.php



CMM user guides and release notes at http://www.cambiumnetworks.com/support/pmp/software/index.php

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/planning/index.php?cat=1&type=0



Cambium Network Updater Tool (CNUT) on‐line help file and release notes at http://www.cambiumnetworks.com/support/planning/index.php?cat=3&type=0



Prizm guides, release notes, and its SDK at http://www.cambiumnetworks.com/support/planning/index.php?cat=2&type=0

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

For links to network element features and specifications, visit the following web pages. 



Cambium PTP: −

the portfolio at http://www.cambiumnetworks.com/solutions/ptp_overview.php

−

PTP 100 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp100

−

PTP 200 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp200

−

PTP 300 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp300

−

PTP 500 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp500

−

PTP 600 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp600

−

PTP 800 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp800

−

Cambium Networks LINKPlanner at http://www.cambiumnetworks.com/solutions/products.php?id=linkplanner

Cambium PMP: −

the portfolio at http://www.cambiumnetworks.com/solutions/pmp_overview.php

−

PMP 100 at http://www.cambiumnetworks.com/solutions/products.php?id=pmp100

−

PMP 320 at http://www.cambiumnetworks.com/solutions/products.php?id=pmp320

−

PMP 400 at http://www.cambiumnetworks.com/solutions/products.php?id=pmp400

−

PMP 430 at http://www.cambiumnetworks.com/solutions/products.php?id=pmp430

−

PMP 450 at http://www.cambiumnetworks.com/solutions/products.php?id=pmp450

For declarations of conformity for individual network elements in their various frequency band ranges, see http://www.cambiumnetworks.com/doc.php.

1.6

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 send your feedback to support@cambiumnetworks.com.

1.7

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 on Page 99.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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

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).

Navigate to C:\Cambium\WM\jre\bin.

Right‐click the file java.exe and select Properties.

In the resulting dialog, click the Compatibility tab.

Near the bottom of this dialog, click the Change setting for all users button.

Near the bottom of the resulting dialog, check the check box of the Run this program as an administrator option.

Click OK to confirm and dismiss this latter dialog.

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 on Page 25



Defining and Managing a Group or a User on Page 53



Restoring a Deleted superuser Account on Page 56



Service Pack or Feature Pack Installation on Page 81



Invoking the MIB Browser on Page 111



Running the Tool from the Server on Page 167

Issue 2 April 2012

2.2

WM Release 4.0 Server Administration Guide

Port Management The following list 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 1: 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.

3306 Queries to the MySQL database. 6900 Inbound TCP for TFTP connections in the firmware upgrade process. 8003

Outbound UDP for SNMP response over the northbound interface (NBI).

8009

TCP connections by Tomcat and web server for access to device management web pages.2

8090 Inbound data from the BAM server. 9090 Inbound TCP for the web server. 32900

NMS Socket for TCP communication between the WM server and WM client.3

33100

NMS FE Secondary for TCP communication between the WM server and WM client.4

61001 Outbound UDP from BAM to APs. 5

27000 WM to request licenses.

License Manager 27443

Secure communications between WM and the web server of License Manager.5

WM Release 4.0 Server Administration Guide

Server

Port

Issue 2 April 2012 Usage

1521

Optional Oracle Java Naming and Directory Interface (JNDI) connection pool via Tomcat.

8080

Communications between WM and the web administration interface of GeoServer.

GeoServer

NOTES: 1.

Port number is reconfigurable in .../server/conf/WibbWMSConfiguration.xml.

Port number is reconfigurable in .../server/Apache/Tomcat/conf/server.xml.

Must be configured in .../server/conf/transportProvider.conf with WM server stopped after WM installation.

Must be configured in .../server/conf/serverparameters.conf with WM server stopped after WM installation.

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.

Stop the WM server, as described under Using the WM Server Panel on Page 99.

Open the file .../server/conf/transportProvider.conf for editing.

Find the tag <PORT_TO_LISTEN>.

Change its value from 0 to that of any available TCP port (for example, 32900).

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Save and close the file.

Open the file .../server/conf/serverparameters.conf for editing.

Scroll to the bottom of the file.

Insert a line that has the following text: NMS_FE_SECONDARY_PORT 33100 where 3100 is an example available TCP port.

10. Save and close the file. 11. Start the WM server, as described under Using the WM Server Panel on Page 99.

2.3

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 LM server device, your WM license may cease to be valid. If this occurs, contact Cambium Networks to request a replacement license. Multiple NICs on your WM server may populate the incorrect (other NIC) IP address into the Java Web Start file. To fix and prevent this on a Windows platform, perform the following steps:

2.4

Open the Control Panel.

In the left panel, click Switch to Classic View.

In the right panel, double‐click Network Connections.

From the main menu of the Network Connections window, select AdvancedAdvanced Settings.

In the Adapters and Bindings tab of the Advanced Settings window, ensure that the connection of the WM server NIC is higher in the list than the other NIC.

IP Address Change for the WM Server 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).

WM Release 4.0 Server Administration Guide

2.5

Issue 2 April 2012

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.6

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.



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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 on Page 102. 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 3: To start the MySQL daemon as a server on Linux

3.3

Enter $ /etc/rc.d/init.d/mysql start.

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 4: 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.

If Wireless Manager is already installed, run the reinitialize_database script file located in the /usr/local/cambium/wm/server/bin directory in Linux

Issue 2 April 2012

WM Release 4.0 Server Administration Guide (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.

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 5: 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.

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).

If using SNMP v3, add database connection information to the SnmpDefaultProperties.xml file in the /usr/local/cambium/wm/server/conf directory in Linux (or the C:\Cambium\WM\server\conf folder in Windows).

3.5

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.

Make sure that the MySQL process is running.

Start the Wireless Manager server.

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. 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 on Page 99.

WM Release 4.0 Server Administration Guide

3.6

Issue 2 April 2012

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 on Page 99. 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:

3.7.1



Addressing Table Corruption on a Linux Platform on Page 27



Addressing Continuous Growth of Data Files on a Windows Platform on Page 28

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.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide note ............. The process above requires stopping the MySQL service. The following does not.



Use Procedure 6: To detect and repair corrupted MyISAM database tables on Page 28 to detect and repair corrupted tables without the need to stop the MySQL service.

Procedure 6: To detect and repair corrupted MyISAM database tables 1.

See References to Starting and Stopping the WM Service on Page 17.

Stop the WM service.

At your Linux shell prompt, enter one of the following commands: mysqldump --user=root --password=public --databases wmsdb >wm_databases.sql mysqldump --user=root --password=public --databases wmsdb backedupdb1 [backedupdb2 ...backedupdb3] >wm_databases.sql mysqldump --user=root --password=public –all-databases >wm_databases.sql

Log into MySQL.

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.

To detect table corruption in each table, enter the following command at the mysql> prompt: CHECK TABLE tablename;

Review http://dev.mysql.com/doc/refman/5.0/en/repair‐table.html.

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;

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 7: To reclaim hard drive space from burgeoning database files on Page 29.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Procedure 7: 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.

Review References to Starting and Stopping the WM Service on Page 17.

Stop the WM service.

At your DOS command utility prompt, enter one of the following commands: mysqldump --user=root --password=public --databases wmsdb >wm_databases.sql mysqldump --user=root --password=public --databases wmsdb backedupdb1 [backedupdb2 ...backedupdb3] >wm_databases.sql mysqldump --user=root --password=public –all-databases >wm_databases.sql

Stop the MySQL service.

Navigate to the MySQL data folder.

Find all existing tablespace files.

note ............. In the default WM implementation, these files are ib_logfile0, ib_logfile1, and ibdata1.

Delete all existing tablespace files from this folder, including the ibdata* and ib_log* files.

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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 processing.

20:58:00:765]

DISCOVERY using a maximum of 6 threads for Deep Discovery

[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 valid MAC.

20:58:02:359]

DISCOVERY(10.60.2.35:258): setNameToMac: MO name is a

[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] 57 20 15 4e to database

DISCOVERY(10.60.2.35:258): Successfully added object 64 ed

[16 Feb 2012

20:58:02:468]

DISCOVERY using PDU max size 512 during deep discovery

[16 Feb 2012 for device

20:58:02:468]

DISCOVERY(10.60.2.35:258): Creating Deep Discovery thread

[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.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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 8: To temporarily disable updates to the physical map display 1.

Stop the WM server. See References to Starting and Stopping the WM Service on Page 17.

Navigate to the /usr/local/cambium/wm/server/conf directory in Linux (or the C:\Cambium\WM\server\conf folder in Windows).

Open the file NmsprocessesBE.conf for editing.

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

Set the value of INCREMENTAL_DEVICE_UPDATE_ON to false.

Save and close the file.

Start the server. See References to Starting and Stopping the WM Service on Page 17.

Notify the client application user that this feature is disabled.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

After the discovery (or other operation for which you temporarily disabled the feature) is completed, perform the following steps:

10. Stop the WM server. 11. Reopen the NmsprocessesBE.conf file for editing. 12. Reset the value of INCREMENTAL_DEVICE_UPDATE_ON to true. 13. Save and close the file. 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.

If an entry is associated with that IP address, note whether the entry indicates that WM regarded the device as unmanaged.

If the entry does, open the file ...server\conf\devices\Generic_Element.xml for editing.

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" />

Validate the xml content.

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.

Issue 2 April 2012

4.4

WM Release 4.0 Server Administration Guide

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).

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" theirSpecificType="any" tolerance_m="0.0" />

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

- <DefineTemplate name="ptp.slave.location.proximity.logical.family"> -  - <!--

BHS not included because they have different location attributes

--> <KinLocation allowSingleChildOnly="true" kinshipType="child" myFieldSource="customUserProperties" myLatitudeName="latitude" myLongitudeName="longitude" theirDeviceType="PMP.CMM3" theirFieldSource="customUserProperties" theirLatitudeName="latitude" theirLongitudeName="longitude" theirSpecificType="any" tolerance_m="0.0" />

Â - <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" theirLatitudeName="latitude" theirLongitudeName="longitude" theirSpecificType="any" tolerance_m="0.0" />

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

5 Predefined Information Structures for Device Support The server file system includes structured information resources to support devices as indicated in Table 2.

Table 2: Structured information resources per general device type Predefined Structured Information Resource

Path to Resource ...WM/server/

Device definition template1

conf/devices/

Configuration values push template

Default Templates/Configuration Templates/

Configured values report template Default Templates/Report Templates/ System report2

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.

Unlike the templates, these reports do not support generic elements.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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:

6.2



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.

Enabling Print for Events and Alarms note ............. See also the section titled "Printing Events" in the Cambium Wireless Manager Release 4.0 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 /usr/local/cambium/wm/server/conf directory in Linux (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: #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]

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.



user1 is the device to which the printer is connected.



HPLaserJ is the name of the share.

WM Release 4.0 Server Administration Guide

6.2.2

Issue 2 April 2012

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 /usr/local/cambium/wm/server/conf directory in Linux (or the C:\Cambium\WM\server\conf folder in Windows). 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.

Table 3: Fault Management configurable fields Arguments

Values

Description Options

EVENT_DEBUG

SAVE_DIR

As of this Release, this parameter is not in use.

‐

Used to specify the directory in which Events and Alerts viewed by the client are to be saved, when the 'Save' option is invoked from the client.

A valid & existing directory name, with the path, relative to WM_Home

Default

Notes

‐

state

PRINT_COMMAND is dependent on SAVE_DIR. When Print action is invoked from the client, the contents will be temporarily saved in a file printfile.tmp file under <SAVE_DIR> and then printed.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Arguments

Values

Description Options

PRINT_COMMAND

CLEAN_EVENT_INTERVAL

Used to specify the command to be executed, when the user invokes the Print option from the Event Viewer/Alert Viewer of Applet client.

Used to specify the number of days after which the Events have to be cleaned up.

The Operating System specific command that could invoke print action from the system.

Any positive integer value.

Default

‐

* 7 days

Notes

PRINT_COMMAND is dependent on SAVE_DIR.

The Events older than this number of days, will be removed from the system. Once in every hour, a check for older Events will be done. When negative value is specified for the parameter, Events will not be deleted based on time interval. 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.

EVENT_WINDOW_SIZE

Used to specify the number of events that need to be actively managed by the system.

Any positive integer value.

10000

However, the total number of Events in the Client may exceed the EVENT_WINDOW_SIZE, until you refresh it manually or navigate the 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.

WM Release 4.0 Server Administration Guide

Arguments

Issue 2 April 2012 Values

Description Options

MAX_EVENT_PROCESS_QUEUE

TRANSIENT_TRAP_PDU_IN_EVENT

DROP_TRAP_WHILE_UNMANAGED

When the rate of incoming Events is higher compared to the processing rate, the additional Events may have to be buffered in memory which will lead to an increased usage of memory. At one point of time, there is a possibility of an OutofMemory Error being thrown.

Any positive integer value.

Default

* 500

Notes 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 adding those Events, after checking the queue size using the is_inQ_SizeBeyondLimit() method. If the Event queue size is exceeded, wait for some time (say 1 sec) before retrying to add Events. MAX_EVENT_PROCESS_Q 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.

Whether to maintain the received SNMP Trap PDU reference in the Event or not.

true/false

Whether to drop or continue processing the SNMP trap, if its corresponding managed object is in unmanaged state.

true/false

* false

The Trap PDU information in the Events can be used to effectively parse and filter events.

* false

‐

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Arguments

Values

Description Options

AUTHORIZATION

Whether to enable / disable authorization check ,when a user tries to perform a fault management operation, like picking up alerts, and so on.

true/false

Default

true

Notes Authorization is the way in which an authenticated user is validated if he is authorized (has been granted the necessary permission) when he tries to perform a specific operation.

V3_AUTH

Whether to enable / disable authentication for SNMP v3 traps.

true/false

GRACEFUL_SHUT_DOWN

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 them ‐ whether to (gracefully) shutdown after completing the further processing of these Notifications or to stop processing and allow for abrupt shut down.

true/false

BATCH_UPDATE

Batch update is used when Events are to be added to the database as a batch so as to decrease the number of queries, thereby enabling an increase in performance.

‐ Inform Requests are unsolicited notifications sent by

Whether to enable/disable WM to send acknowledgment, for the Inform requests from the Agents.

NEED_INFORM_ACK

* false

 an Agent to Manager. * false

 a Manager to Manager. In both cases, an acknowledgment will be sent by the Manager after it receives the notification.

true ‐ batch processing of Events is enabled false ‐ batch processing of Events is disabled.

false

‐

*false

‐

WM Release 4.0 Server Administration Guide

Arguments

Issue 2 April 2012 Values

Description Options

Default

Notes

Any value from 1‐24

*1 hour

If invalid or negative value is specified, WM will take the default 1hour

* ‐

‐

CLEANUP_QUERY_INTERVAL

Valid from 4.7 SP1 only Parameter to configure the frequency of CLEAN_EVENT_INTERVAL check. By default, this check will be made every one hour.

PERSISTENCE_CLASS

Used to specify the user classes generated by Generated extending the UserClass HbnEventPersistence class.

NOTE: * indicates that the option will not be present in NmsProcessesBE.conf by default.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 /usr/local/cambium/wm/server/conf directory in Linux (or the C:\Cambium\WM\server\conf folder in Windows). 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 4: Performance Management configurable fields Parameter

CLEAN_DATA_INTERVAL

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 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

STATUS_POLL_PING_RETRIES

This specifies the maximum number of times the system can try to ping the device to retrieve its status. This indicates that request will be sent for STATUS_POLL_PING_RETRIES + 1 times. Default value : 0

STATUS_POLL_SNMP_RETRIES

This specifies the maximum number of times the system can try to perform SNMP ping to the device to retrieve its status. This indicates that request will be sent for STATUS_POLL_SNMP_RETRIES + 1 times Default value : 0

STATUS_POLL_PING_TIMEOUT

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 disabled Default value: 1 (i.e., will wait for one second if a particular node is not reachable).

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Parameter

DATA_COLLECTION_SNMP_RETRIES

Description This specifies the maximum number of times the system can try to ping the device to perform data collection (Polling). This indicates that request will be sent for DATA_COLLECTION_SNMP_RETRIES + 1 times. Default value : 0

MAX_OIDS_IN_ONE_POLL

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 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

CUSTOMIZED_DATA_COLLECTOR

POLLING_POLICY_CUSTOMIZER

This specifies the fully qualified class name which has implemented 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 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

DEBUGGING_MODE

be turned on/off using the method setDebugMode() in the 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

SEND_MULTIPLE_REQUEST

When this parameter is set as false, the Multiple PolledData from a single table will be polled separately. Default value : true

STATUS_POLL_QUERY_INTERVAL

This specifies the interval between two successive queries to the database, for status polling. Default value : 1500 This specified the interval between two successive queries for retrieving polling units to be polled.

DATA_COLLECTION_QUERY_INTERVAL

AUTHORIZATION

note………………This parameter has been deprecated in later releases. The interval is now the value of the 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 requests or not. Default value : false

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Parameter

PASS_THRO_ALL_POLLING_OBJECTS

Description 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 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. Default value : false

RECOVER_DELETED_PDATAS

When this parameter is set as "true", the Poll ID and its corresponding key will be stored in the PollIDToKeyMap table. This will be useful, if you want to access the collected data for the deleted PolledData. Default value : false 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.

BULK_INSERT_INTERVAL

For e.g. if BULK_INSERT_INTERVAL is set to 30, then for every thirty 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.

MAX_ALLOWABLE_INSERT

note………………When MAX_ALLOWABLE_INSERT value is reached, the interval set for Bulk insert is not taken 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

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Parameter

Description 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

STATUS_POLL_DELAY

This parameter can be used in cases where you have large networks 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

DATA_COLLECTION_SNMP_TIMEOUT

◦

the agent might be down

◦

the agent might be delaying the response

◦

there is packet loss while data is transferred.

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

DATA_COLLECTION_STARTUP_DELAY

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 zero , data collection will start immediately. Note that this setting is common for all PolledData created in the system. Default value : 5 minutes

ENABLE_STATUS_POLL_BATCH

7.2

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 processed in batches also. To enable this, add a new parameter ENABLE_STATUS_POLL_BATCH (not available by default) and set it to true.

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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Each of these custom reports must then be imported into the client application through a client session from the server device, following 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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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:

8.1



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.

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.

Issue 2 April 2012

8.2

WM Release 4.0 Server Administration Guide

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 9: 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. Find the following process: com.adventnet.nms.security.authorization.NmsAuthManager

Configure the argument authorization_for_security_administration to true. By default, this value is set to false.

Save and close the file.

Start the Wireless Manager server.

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 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.

WM Release 4.0 Server Administration Guide

2. 3.

Issue 2 April 2012

Start the Wireless Manager server. Log in to the client as an administrator with the default user ID of root and a password of public.

From the main menu, select ToolsSecurity Administration.

Right‐click on the Groups node in Security tree and select AddGroup.

Create a new group called Group1.

Click Next.

In the Permissions tree hierarchy, enable the Security Administration node.

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. 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.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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:

8.6



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

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.7

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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Procedure 10: 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.

If the server device is on a Linux OS, perform the following steps: a.

Enter cd /usr/local/cambium/wm/server/bin.

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.

In the Open field of the Run dialog, type in cmd.

Click OK.

At the DOS prompt, enter cd C:\Cambium\WM\server\bin.

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.

Launch a session in the WM client interface, logging in as new_superuser with the password public.

Select ToolsAdministrationSecurity Administration.

In the left panel of the Security Administration window, click to highlight GroupsAdmin.

In the right panel, click the Members tab.

Click the Setting Users button.

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.

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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 on Page 107.

9.1

Deploying GeoServer To deploy GeoServer, perform the following steps.

Procedure 11: To deploy GeoServer 1.

Visit http://geoserver.org.

Download the latest version of the GeoServer software.

Download its associated documentation.

Install GeoServer according to its documentation.

Launch your web browser.

Navigate to http://GeoServerHost:8080/geoserver/web/. The web interface to GeoServer opens. 59

Issue 2 April 2012

9.2

WM Release 4.0 Server Administration Guide

Creating Map Layers To create an offline physical map layer from a single image, perform the following steps.

Procedure 12: To create a layer from one image 1.

Under Data in the left panel, click Workspaces. The Workspaces panel opens to the right.

Click the link for Add new workspace.

In the Name text box, compose a name by which you will later recognize this workspace.

In the Namespace URI text box, type in any functional URL.

Check the Default workspace check box.

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 13: To create a data store for GeoServer workspace images 1.

On the GeoServer host, create the directory GeoServer_Version/data_dir/data/WorkspaceDirectory.

Copy the image from which you want to create a layer into this new directory.

In the left panel of the GeoServer interface, click Stores.

In the Stores panel to the right, click Add new Store.

Under New data source in the resulting right panel, click the type of image that you copied to the directory.

In the Add Raster Data Source panel, use the drop‐down menu to select the Workspace name.

In the Data Source Name text box, compose a name by which you will recognize the data source.

In the associated Description text box, compose a description that will help you distinguish this data source from others that create.

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. 13. Click the Save button. 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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

To verify that GeoServer is properly connected to the stored image file, perform the following steps.

Procedure 14: 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.

Under Automatically Generated Demos, click A list of all the layers and automatic demos.

In the resulting table, find the layer that you created in this procedure.

Click one of the file formats in the OpenLayers column for your layer.

Inspect the image to verify that it is as intended.

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 15: To add an image to an existing layer 1.

Perform Procedure 13 on Page 60 except that, instead of creating a Workspace directory, use the Workspace directory that you created to store the first image. Then proceed as follows.

In the left panel, click Layer Groups.

In the Layer Groups panel to the right, click Add new layer group.

In the Name text box, compose a name by which you will recognize the new layer group.

Click the Submit button.

note ............. Delay the Generate Bounds operation until all intended layers have been added.

Beneath the Generate Bounds button, click Add Layer.

In the Choose new layer pop‐up window, click the name of the first layer to be included in this layer group.

Click Add Layer again.

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. 12. Click the Save 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.

Issue 2 April 2012

9.3

WM Release 4.0 Server Administration Guide

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 16: To pre-cache all tiles for all levels of zoom 1.

In the left panel of the GeoServer web interface, click WCS.

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.

For Number of threads to use, select the desired number (for example, 16, recommended for the maximum).

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.

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.

For Format, always select image/png for maximum compatibility with WM.

For Zoom start, always select 00 as the lowest zoom level.

For Zoom stop, always select 16 as the highest zoom level.

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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

10 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.

execute the script. (See the user guide section titled "Running a User‐defined Script.")

review the results of the execution. (See the user guide procedure titled "To view results of last execution of a task.")

inform the client administrator(s) that authorized users will now be able to launch this script from the task scheduler interface.

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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

11 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 /usr/local/cambium/wm/server/conf directory in Linux (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 5: 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.

confChange_<SP Version>.log

This log file is created whenever Service Pack update is performed. The update details are printed in this file.

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.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Log file name

Contents

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.

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>

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

12 WM Software Upgrades and Downgrades 12.1 WM Upgrade to Release 4.0 Upgrade to WM Release 4.0 is supported only from Release 3.0 with Service Pack 3 

on Red Hat Enterprise Linux 5.x ES, 32‐bit



on CentOS 5.x, 32‐bit



on Windows Server 2008 R2 Enterprise

The two possible upgrade paths to Release 3.0 with Service Pack 3 are as follows: 



starting with Release 2.2 with no patch or any patch other than Patch 8: 1.

Install Release 2.2 Patch 8 as described in the associated README file.

Continue with the following path.

starting with Release 2.2 Patch 8: 1.

Upgrade to Release 3.0 as described in the server administration guide for Release 3.0.

Install Release 3.0 SP 3 as described in Service Pack or Feature Pack Installation on Page 81.

Start the WM server process as described under Using the WM Server Panel on Page 99.

Stop the WM server process as described under Using the WM Server Panel on Page 99.

Upgrade to Release 4.0 as described in Procedure 17: To upgrade WM to Release 4.0 on Page 68.

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 Release 4.0 server device. 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 on Page 91 and Calculation of the Number of Nodes to be Licensed on Page 91.

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 on Page 91 of this guide. important ........... The following procedure presumes that the previous release with its latest service pack is already installed on the device and that you are merely upgrading the server software. For instructions on a fresh installation, including where one of these releases had been present and has been uninstalled, use the Cambium Wireless Manager Quick Start Guide for Release 4.0.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Procedure 17: To upgrade WM to Release 4.0 1.

Download the WM integrated installation tool for your platform (WM_Installer_4_0_x.exe or WM_Installer_4_0_x.bin).

Use the MD5 checksum provided at the download web site to verify that the tool was not corrupted by the download.

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. 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. 4.

disable the firewall on the device.

Launch the installation tool. The interface provides a progress bar for the status of its preparations.

Then the Introduction panel opens.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Read the Introduction panel and click Next. The License Agreement panel opens.

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.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

..................... 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 on Page 80.

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.

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 Release 4.0 installation tool detects their presence.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

When the tool prompts for whether you want to continue given that the previous release was detected, click OK.

10. When the tool indicates the components that will not be installed, confirm that you chose to not install them. 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. Type in your database‐specific username and passwords, and then click Next. The tool provides a summary of what it is ready to do.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

12. Review the contents of the Pre‐Installation Summary panel (scrolling to see the entire contents). 13. Click the Install button. If the WM server is running, the tool stops it. Then the tool provides a confirmation that it is active.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

The tool backs up certain configuration files and the database and places the backups into a new directory that it creates immediately beneath the system drive, for example ◦

\WM_x.x.x_BACKUP in Windows

◦

/WM_Release vx.x_BACKUP in Linux

The tool uninstalls the previous WM release, then installs Release 4.0 as it provides various progress/confirmation messages. 14. If your firewall asks whether to allow jre-6u6-x-exe, allow it. The installation wizard prompts for whether you want to start the Administrator Tool.

15. Copy your purchased licenses to the WM server device and note their path. 16. In the Run Server Administration Tool? window, click the Yes button. The wizard responds with the Install Complete panel.

17. Click the Done button. The WM Administrator Tool opens.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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 on Page 103.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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.

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.

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.

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.

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 14 on Page 104. 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 15 on Page 105. 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 on Page 99.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide 29. Check the file ...cambium\wm\Uninstall\installvariables.properties for any errors that occurred during the upgrade/installation.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

30. If you want WM to process authentication requests for PMP slave devices a.

procure a license to use BAM.

download Prizm software from http://www.cambiumnetworks.com/support/planning/index.php?cat=2&type=1.

install Prizm Release 3.3 without the optional License Manager and Database installations that the installation tool offers.

download Prizm documentation from the same site.

navigate to the .../Canopy/Prizm_bin directory.

launch the PrizmEMS Administrator Tool.

in the Server panel of the tool interface, set the Server Mode to BAM Only and click the Save button.

from the main menu, select ActionPrizmEMS ServerStop.

verify that the services for License Manager and MySQL database are running.

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.

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.

in the License Actions block of the Licensing panel of the WM Administrator Tool, select Upload License. (See Using the Licensing Panel on Page 103)

m. upload all of the following licenses 

BAM server license



BAM packs

31. In the Server Actions block of the WM Server panel in the WM Administrator Tool, click the Start WM Server button. 32. Optionally, close the WM Administrator Tool. 33. Launch your web browser. 34. Navigate to http://localhost:9090. If the server has been properly configured, your browser will be redirected to the launch web page.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.

12.2 Optimization of System Resources 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 18: To optimize the system resources for WM 1.

Stop the service for MySQL Server.

In the MySQL server file system, find either the file my.cnf or the file my.ini.

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-innodb-heavy-4G and edit them.

For any of the following attributes whose value is smaller than the corresponding value recommended here, increase it to the recommended value.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Table 6: Recommended MySQL parameter values back_log=50 max_connections=100 max_connect_errors=10 table_open_cache=2048 max_allowed_packet=64M binlog_cache_size=1M max_heap_table_size=64M sort_buffer_size=16M join_buffer_size=16M thread_cache_size=8 thread_concurrency=32 query_cache_size=64M query_cache_limit=2M ft_min_word_len=4 thread_stack=192K transaction_isolation=REPEATABLE-READ tmp_table_size=64M log-bin=mysql-bin binlog_format=mixed slow_query_log long_query_time=2 key_buffer_size=64M read_buffer_size=2M read_rnd_buffer_size=16M bulk_insert_buffer_size=128M myisam_sort_buffer_size=128M myisam_max_sort_file_size=10G myisam_repair_threads=1 myisam_recover innodb_additional_mem_pool_size=20M innodb_buffer_pool_size=2G innodb_data_file_path=ibdata1:10M:autoextend innodb_file_io_threads=4 innodb_thread_concurrency=16 innodb_flush_log_at_trx_commit=1 innodb_log_buffer_size=8M innodb_log_file_size=256M innodb_log_files_in_group=3 innodb_max_dirty_pages_pct=90 innodb_lock_wait_timeout=120

Save and close the file.

Restart the service for MySQL Server.

12.3 Optimization of Operator-installed Database If you installed and have kept your own MySQL database (left the database deselected as a component of the upgrade package that the WM installation wizard offered), then certain database optimizations that the installation bypassed for your upgrade are important for you to make. To do so, perform the following steps:

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Procedure 19: To optimize your custom database for WM Release 4.0 1.

In the MySQL server file system, find either the file my.cnf or the file my.ini.

Open the file for editing.

Find the attribute query_cache_size.

Set its value to 100 million (query_cache_size=100000000).

Find the attribute query_cache_limit.

Set its value to 5 million (query_cache_limit=5000000).

Find the attribute max_allowed_packet.

Set its value to 8M (max_allowed_packet=8M).

Save and close the file.

10. Restart the service for MySQL Server.

12.4 Migration of Operator Data Through WM Upgrade Plus OS Upgrade To preserve configuration and performance data from the previous release into Release 4.0 while also upgrading the OS of the server device, perform the following high‐level process.

Procedure 20: To migrate operator data in upgrade of WM plus the OS 1.

If Release 4.0 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 on Page 22 and License Types on Page 91.

According to the section WM Upgrade to Release 4.0 on Page 67, upgrade the WM software to Release 4.0.

Using the Release 4.0 user guide, verify that Release 4.0 is operating as expected.

Double‐click the desktop icon

In the left panel of the resulting WM Administrator Tool dialog, select WM Server. (See Using the WM Server Panel on Page 99.)

In the right panel, click the Server Actions block Stop WM Server button and leave the WM Administrator Tool open.

labeled WM Server Administration.

note ............. This breaks the connection of the client session. A pop-up confirmation asks whether you want to exit the client.

Click the Yes button to remove all the open client interface windows.

In the System Backup block of the right panel in the WM Administrator Tool, click the System Backup button.

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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 Release 4.0 quick start guide procedure for a fresh installation, install all three components: WM Release 4.0, 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 on Page 103, 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. 19. Using the Release 4.0 user guide, verify that Release 4.0 is operating as expected. 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 Release 4.0. 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. 26. Using the Release 4.0 user guide, verify that Release 4.0 is operating as expected.

12.5 Service Pack or Feature Pack Installation When Cambium Networks makes a new WM service pack or feature pack available for download, you can launch the Update Manager tool from the server file system to automatically and selectively replace some of the files and add new ones that support new devices and/or provide new capabilities, without installing a full WM software version. At any time (for example, before and/or after you install or uninstall a service pack or feature pack, you can check the current value of the Service Pack Version in the file /usr/local/cambium/wm/server/logs/wmsout.txt or C:\Cambium\WM\server\logs\wmsout.txt.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

To install a service pack or feature pack, perform the following steps.

Procedure 21: To install a service pack or feature pack 1.

Download the new service pack or feature pack from the Cambium Networks web site, noting its destination path.

In the server device, navigate to /usr/local/cambium/wm/server/bin in Linux or C:\Cambium\WM\server\bin in Windows.

Launch the tool ServerAdminTool.sh or ServerAdminTool.bat.

Stop the WM server, as described under Using the WM Server Panel on Page 99.

Launch the tool UpdateManager.sh or UpdateManager.bat. RESULT: The interface to the tool opens. If any previously installed service packs and/or feature packs are currently deployed, then they are listed in the Installed Patches panel of the window. An example of this window is shown in Figure 3.

Figure 3: Update Manager interface

In the update panel, click the Browse button.

Browse to and select the downloaded .ppm service pack or feature pack file.

Click the Readme button to see a summary of the changes that the service pack or feature pack will install.

Click the Preview button to see the contents of the service pack or feature pack.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

10. Click the Install button to deploy the service pack or feature pack. RESULT: The Installation Wizard opens. An example is shown in Figure 4.

Figure 4: Service pack Installation Wizard

11. If you want to see the list of files and review the Readme text, check the check box for View Readme and Installed files. NOTE: An example of the Readme window, with Readme and Installed files tabs, is shown in Figure 5.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Figure 5: Service pack Readme window

12. Click the Close button to complete the installation. RESULT: The service pack or feature pack is deployed, and the files that were replaced by it have been moved to /usr/local/cambium/wm/patch/PatchName or C:\Cambium\WM\Patch\PatchName directory for automatic restore in case you ever uninstall the patch that superseded these files. 13. In the Server Actions block of the WM Server panel in the WM Administrator Tool, click the Start WM Server button. caution............... If you are applying more than one service pack, then the next step (restarting UpdateManager) is required. Skipping this step between consecutive service pack installations will result in both a pop-up error stating that the .ppm file of the next installation is not compatible with the product and the loss of the previous service pack, if the next one were installed.

14. If you want to use the UpdateManager tool to install yet another service pack, close the tool and reopen it before repeating this procedure.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

12.6 Service Pack or Feature Pack Uninstallation If you ever want to uninstall a service pack or feature pack that you previously installed, perform the following steps.

Procedure 22: To uninstall a service pack or feature pack 1.

In the server device, navigate to /usr/local/cambium/wm/server/bin in Linux or C:\Cambium\WM\server\bin in Windows.

Launch the tool ServerAdminTool.sh or ServerAdminTool.bat.

In the Server Actions block of the WM Server panel in the WM Administrator Tool, click the Stop WM Server button.

Launch the tool UpdateManager.sh or UpdateManager.bat. RESULT: The interface to the tool opens. An example is shown in Figure 3 on Page 82.

Click to highlight the service pack or feature pack that you want to remove from deployment.

Optionally, click the Details button to see information about the service pack or feature pack.

Click the Uninstall button to remove the service pack or feature pack from deployment. RESULT: The Uninstall window opens as shown in Figure 6, listing the service packs or feature packs that will be uninstalled.

Figure 6: Service pack Uninstall window

Issue 2 April 2012

WM Release 4.0 Server Administration Guide important ........... If you proceed by clicking the Finish button, then all service packs or feature packs that are later (higher-numbered than your selected one) will be automatically uninstalled as well.

If you want to abort the uninstallation, click the Cancel button.

If you want to execute the uninstallation(s), click the Finish button. RESULT: The Uninstallation status panel opens to display progress. An example is shown in Figure 7.

Figure 7: Service pack Uninstallation status panel

10. Either ◦

check the check box for Automatically close after uninstallation and then click the Finish button.

◦

wait until the progress is shown as 100% Completed and then click the Close button to dismiss the window.

11. In the Server Actions block of the WM Server panel in the WM Administrator Tool, click the Start WM Server button.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

12.7 WM Downgrade from Release 4.0 No downgrade path exists to retreat from WM Release 4.0 to any earlier release. To do this, you must uninstall Release 4.0 and then re‐install the earlier release. The Release 4.0 installation tool 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.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

- <product name="Cambium Networks Wireless Manager 4.0" id="c45ac526-1ee9-11b2-b9f1da59c1a72547" 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[ <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="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[ <Enter Product Feature description here -- do not forget to assign this Feature to desired Install Sets> ]]> <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[ <Enter Product Feature description here -- do not forget to assign this Feature to desired Install Sets> ]]> <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[ <Enter Product Feature description here -- do not forget to assign this Feature to desired Install Sets> ]]> <component ref_id="dad51170-1ef3-11b2-8422-c06f25b923f3" version="1.0.0.0" location="C:\Cambium\WM\license_manager.exe" /> </feature> </product>

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

</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="AGApplication, Install" location="C:\wmserver" /> <component id="d303eec7-1ee9-11b2-857a-da59c1a72547" version="1.0.0.0" name="AGInstall, 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="AGLicense" 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="AGInstall, 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- MSVC++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="AGPrizmEMS, LicMgr, Postgres" location="C:\Cambium\LicenseManager\Uninstall\Uninstaller.exe" vendor="Cambium Networks" /> </components>

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.

From the main Windows menu, select ToolsFolder Options.

Click the View tab.

Select Hidden files and foldersShow hidden files and folders.

Click the Apply button.

Open the file .com.zerog.registry.xml for editing.

Remove the contents described above.

Save and close the file.

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 WM Release 4.0 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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

13 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.

13.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.

13.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

Issue 2 April 2012

WM Release 4.0 Server Administration Guide 

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 to Release 4.0 1.

the operator should upload a valid license of appropriate device count.

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.

during the first and any subsequent auto discovery, all new discovered nodes that WM Release 4.0 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.

13.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.

13.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 17 on Page 68 of this guide provides, beginning with its Step 13.

13.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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Procedure 23: 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.

Select Switch to Classic View.

Double‐click Administrative Tools.

Double‐click Services.

Click the column head Name .

Click to highlight WM License Manager Web Server.

In the left panel, click Stop the service.

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==" />

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"/>

Save and close the file.

Restart the License Manager web server. NOTE: This causes the web server to read the null current contents of the password attribute.

Launch the License Manager web site.

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. 13. Click the Save Configuration button.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.

13.6 Deployment of Redundant License Manager Servers 13.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.

13.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.

WM Release 4.0 Server Administration Guide

13.6.3

Issue 2 April 2012

Redundancy Deployment Process To deploy redundant License Manager servers, perform the following steps.

Procedure 24: 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).

Ensure that the WM License Manager is installed on each of the three machines.

Stop the License Manager service.

In the License Manager web server, navigate to the LicenseManager\FLEXnet\api\www\config directory.

Open the file licensing.xml for editing.

Change host="localhost" to host="MachineIPAddress".

Write and close the file. In the steps that follow, refer also to Using the Licensing Panel on Page 103.

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.

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.

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.

If the latter file is present, rename it to dummy.lic.

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.

Click the Licensing Configuration link.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Figure 8: Licensing Configuration panel in License Manager web server

In the Licensing Configuration web page, select the Redundant Server check box.

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.

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:

Log on to the web server interface of the primary license server.

Click the Licensing Status link.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Figure 9: Licensing Status panel in License Manager web server

Check that the status report shows the total number of licenses that you expect to see.

Log on to the web server interface of the secondary server.

Check the status report for consistency with that from the primary server.

Log on to the web server interface of the tertiary server.

Check the status report for consistency with those from the other two servers.

13.7 Workaround for a License Server Failure 13.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.

Issue 2 April 2012

WM Release 4.0 Server Administration Guide 

A standalone server is down because of a failure or reboot.

Whenever you have restarted License Manager, restart the WM server.

13.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.

Stop the License Manager service on all three servers.

In the WM server, navigate to the …/LicenseManager/FLEXnet/license_files directory.

If the name of the dummy.lic file changed to dummy.lic.RENAMED, then rename it to dummy.lic.

Except for dummy.lic, delete the existing license files in the folder.

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.

13.7.3

Upload these changed license files.

Start the License Manager in the order primary, then secondary, and then tertiary server.

In the Licensing Status link (Figure 9 on Page 97), verify that all the licenses are properly uploaded.

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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

14 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:

14.1 Using the WM Server Panel 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 WM Server.

Figure 10: WM Server panel of WM Administrator Tool

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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. 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. 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.

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.

100

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

14.2 Configuring the BAM Panel 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 BAM.

Figure 11: 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.

101

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

14.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 on Page 99.

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 Database.

Figure 12: 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

102

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

configuration that the WM installation tool had installed, perform the steps of Procedure 5: To restore the installed WM database configuration on Page 26. 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:

14.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 on Page 91. 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 ToolsAdministrationServer Administration; in the left panel of the resulting WM Administrator Tool dialog, select Licensing.

Figure 13: 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.

103

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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 14: Upload License File dialog

An example of License Status information is as follows.

104

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Figure 15: License Manager Status display window

...

105

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

14.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 16: 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.

106

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Figure 17: 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.

14.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 on Page 59. 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 Offline Physical Map.

107

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Figure 18: 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 25: To configure WM for offline physical map images 1.

Check the Enable offline physical map check box.

Click the Add Layer button.

In the new null row of the Offline Map Layers table, click in the Display Name column.

Compose a name by which you will recognize the layer.

Click in the Layer Name column.

Type in the name of the layer or layer group as it was specified in GeoServer.

Click in the GeoServer Host / IP column.

Type in the IP address of remote GeoServer or localhost, if GeoServer is local to the WM server.

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.

108

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 18 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 26: To reconfigure offline physical map images in WM 1.

Click the cell that you want to edit.

Overwrite its textual contents.

Click the Apply button.

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.

14.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.

109

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Figure 19: Email Configuration panel of WM Administrator Tool

To configure these settings, perform the following steps.

Procedure 27: To configure server and admin email settings

110

For SMTP Server Host, replace SMTP_SERVER_HOST with the host name of your local SMTP server.

If its port is other than 25, highlight and overwrite 25 with the number of the port that is locally reserved for the SMTP host.

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.

For Login, specify the SMTP username for WM to authenticate itself to the SMTP server.

For Password, specify the SMTP password for WM to authenticate itself to the SMTP server.

Type the same string into the Confirm Password text box.

Click to check the check box associated with Authentication required.

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.

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).

Click the Test button to ensure that the SMTP server and its port are properly configured in this panel.

If the test is successful, click the OK button to apply its settings.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

15 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.

15.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 28: 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.

Ensure that the JAVA_HOME path is set properly.

Run MibBrowser.exe or MibBrowser.bat.

Figure 20: MIB Browser main GUI

111

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.

15.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:

15.2.1



General



MIB Settings

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.

112

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 21: MibBrowser Settings dialog

Table 7: MibBrowser General tab fields Options

Default Values

Other Options

SNMP Version

v2c or v3

Timeout1

5 sec

any user‐defined value

Retries1

any user‐defined value

Encoding2

ISO8859_1

any encoding scheme that supports text format

113

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Options

Default Values

Other Options

Max Repetitions3

any user‐defined value

Non Repeaters3

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.

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.

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 8: Security parameters for accessing SNMPv3 agents Options

114

Default Values

Other Options

User name

null

any user‐defined value

Security level

noAuth noPriv

Auth noPriv and Auth Priv

Authentication Protocol

MD5 (if authentication is chosen in security level)

SHA

Privacy Protocol

CBC‐DES (if privacy is chosen in security level)

not available

WM Release 4.0 Server Administration Guide

Options

Issue 2 April 2012 Default Values

Other Options

Authentication password

any user defined value

‐

Privacy password

any user defined value

‐

Target host

localhost

any host with SNMPV3 agent 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:

15.2.2



a serialized file



a database

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.

15.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.

115

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.

15.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.

15.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. 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.

There are other options for loading the MIB file. Click the Recent tab to load the recently loaded MIB files.

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.

116

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 22: 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.

117

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.OracleDriver

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:

15.2.6



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

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.

118

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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.

15.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.

119

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.

Select the desired node in the MIB tree.

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.

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.

To delete the varbind(s) from the list, select the varbind(s) from the list and click the Delete button.

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.

120

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 on Page 120. 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 on Page 120 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.

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.

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.

121

Issue 2 April 2012

15.2.8

WM Release 4.0 Server Administration Guide

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.

Load the MIB file in MIB Browser.

Specify a valid OID or select the OID by traversing through the MIB Tree. The OID should be a valid table OID.

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.

The SNMP Table for the specified OID is displayed.

Figure 23: SNMP Table

122

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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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.

Click the StopPolling button to stop the polling.

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 24: 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.

123

Issue 2 April 2012

WM Release 4.0 Server Administration Guide ◦

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:

124

◦

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.

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

15.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 9: 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.

Host Name Should Be Entered.

SnmpTable is started without specifying the host name. The specified OID is not a valid one. Before making any query, Invalid OID Format exception is thrown.

Invalid OID Format

It should be either Integer type or String type. It will be thrown during instantiating Line/Bar Graph, SnmpTable, and operations, such as GET, GETNEXT, GETBULK, SET, etc.

Invalid Table OID

SnmpTable is started after specifying an invalid OID in the OID Textfield.

Table OID should be specified

Snmptable started without specifying any Table OID

Error Loading MIB: xyz java.io.FileNotFoundException:

Invalid file is loaded in the LoadMibDialog TextField for loading MIBs File.

Could not Open stream for home/../AdventNet/SNMPv3/mibs/xyz.parser

But in the description TextField of MIB Browser, the 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.

125

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Error Message

When it is displayed The error message is thrown when doing set operation If, the OID is not instrumented by the agent for which it is setting value. If the agent queried is not present in the network.

RequestFailed: Get Response PDU received from 192.168.1.001

If the WriteCommunity specified is not right one.

Error Indication In Response: There is no such variable name in this mib.

If the Syntax of the value you are setting is not as 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 Error Indication In Response: A not writable error occurred.

The leafNode or OID for which you are setting value has no read/write access.

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: DataException: Error: Creating Variable

LineGraphBean Error: cannot plot string value Root.....

If setting value for a columnnode of a table does not have rowstatus. The exception is thrown when plotting Graph for a leafNode, 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 ................................................: value

PhysAddress, NetworkAddress, IP Address, OBJECT IDENTIFIER.

Error: com.adventnet.snmp.beans.DataException: InvalidTable OID:(oid chosen)

SnmpTable is started with OID which is not a Table OID.

ErrorSendingPDU: Failed to Authenticate the Security Parameters, for user SnmpEngineEntry not found for address( hostname) port(portNo.)

The exception is thrown while creating SnmpTable,

LineGraphBeanError: cannot plot string value xyz.

126

If the host name specified, is of different version than v3 which is set in settings table. If the OID/LeafNode chosen for plotting Graph is of String Type.

WM Release 4.0 Server Administration Guide

Error Message

Issue 2 April 2012 When it is displayed

Discovery failed for address (hostname) port (portno.)

If wrong port number is set in the MIB Settings panel.

Time Sync Failed for user (user name)

If wrong username/user password/priv password/ TargetHost/SecurityLevel is set in the MIB Settings panel

Error in Getting DataBase Connection:Please check the jdbc parameters: com.adventnet.snmp.beans.MibException: java.lang.ClassNot FoundException:

If DriverName/URL/User Name/Password has been set wrong when loading MIBs from database

Error in Getting DataBase Connection:Please check the jdbc parameters: java.lang.ClassNotfoundException: (DriverName set) Please enter the UserName

If the mysql.jar class is not present in the classes directory. If the Username is not set for the v3 User.

Sent request to hostName:port no. Request Failed :SNMPv3 Error in Response. usmStatsUnknownUserNames(.1.3.6.1.2.1.1...) Counter value = 2HostName Enter the FileName of MIB Module

If Security parameters are set after setting the version v3 for a v1/v2 agent and request is made.

While loading the MIBs file if OK button is clicked without selecting any file in "LoadMibDialog".

Error Loading MIB:(filename) java io FileNotFoundException: Couldn't open stream for filename.cmi Error Loading MIB:(filename with full path from home dir).cds 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 for this user. TimeSynchronizationFailure could have occurred.

If any file chosen from outside the MIBs directory.

When a .cds file is loaded.

If ContextName/ContextEngineID is not set before making query for SnmpTable.(Database Mode)

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

127

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Error Message

When it is displayed get Request for a v3 User(Database mode)

Error in get request from < hostname >: 161 Unable to encode PDU.

AuthProtocol: MD5 Context Name, ContextEngineID are not specified. 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 privuser authKey length has to be 20.

AuthProtocol: SHA

can not plot the chosen variable: iso.org.dod.internet.mgmt.mib2.interfaces.ifTable sent get request to tonyjpaul:161

Context Name, ContextEngineID are not specified. If IfTable OID is chosen for plotting Graph. The Error will be thrown if the OID chosen is not a leaf OID. 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 Request Failed: Get Response PDU received from 127.0.0.1. Error Indication in response : This is a end of MIB View. ObjectID: .1.3.6.1.2.1.1.9.1.4.9 NULLOBJECT:NULL Error Sending set Request: com.adventnet.snmp.beans.DataException: Error: Mib node unavailable for OID.

If getBulk Operation is done for "org".(setting version v2/v3 for a v1 host) if the OID/LeafNode selected is the last node of the mib. The same Exception will be thrown for operations like getNext, getBulk also. Setting value for an OID which is not having any leafnode. 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 MIB.

This Error is thrown if the leafnode sysServices is not implemented by the agent.

ObjectID: .1.3.6.1.2.1.1.9.1.4.9 NULLOBJECT:NULL

128

WM Release 4.0 Server Administration Guide

Error Message

Issue 2 April 2012 When it is displayed

sent get request to <hostname>:161 Request Failed: Get Response PDU received from 192.168.1.182 Error Indication in response : A no creation error occurred.

During set operation on ipRouteDest which has read‐ write access & syntax of datatype:IP Address for a v3 user. As values cannot be set if the column is not of Row‐ Status type.

Errindex:1 sent get request to <hostname>:161 No data available in this subtree Error in getting Database Connection . Please check the jdbc Parameters: com.adventnet.snmp.mibs.MibException: java.sql.SQL Exception: No suitable Driver. Error in Getting DataBase Connection:Please check the jdbc Parameters: java.sql.SQLException: No suitable Driver.

When doing a get request for a v2 agent at OID "transmission"(.1.3.6.1.2.1.10) Exception is thrown when no data is available for that particular instance of OID. Error is thrown when connecting to the database for an agent of any version, if the DriverName set is not correct.

This error is thrown when the URL set is not a valid URL for connecting to database.(mysql‐>msql)

Error in Getting DataBase Connection:Please check the 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‐ >smplinux) to? (java.net.UnknownHostException) Error in Getting DataBase Connection:Please check the jdbc Parameters: java.sql.SQLException: General error: Unknown database "<tst>"

This error is thrown when the URL set is not a valid URL for connecting to database.(test‐>tst)

sent set request to <hostname>:161 Request Failed: SNMPv3 Error in Response : usmStatsNotInTimeWindows(.1.3.6.1.6.3.15.1.1.2.0)Coun ter value = 75 <hostname>

Error thrown if the request is made after a certain interval of time..

sent get request to <hostname>:161 Request Failed: Get Response PDU received from 192.168.1.182 Error Indication in response : There is no such object in this MIB.

This OID is not instrumented for the agent you are querying for or no data is available in this OID.

ObjectID: .1.3.6.1.2.1.8.1.0 NULLOBJECT:NULL

129

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

15.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.

Select the Table node from the tree and the Table button from the toolbar to display the corresponding table.

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

Select Add a New Row to the Table. It displays a window for entering the values of the table.

The value for the column with RowStatus syntax should be 4 for creating a new row.

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.

130

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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.

131

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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.

133

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.

134

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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

135

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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‐

136

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 2012 Cambium Networks, Ltd All rights reserved.

137

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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. WIRELESS MANAGER™, CAMBIUM™, CAMBIUM NETWORKS™, and the Cambium Networks Logo are trademarks of 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.

138

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 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. 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)

139

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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 Description: Java library for Geo spatial data manipulation Software site: http://javolution.org/ Source Code: The source packages for Javolution 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: Javolution ‐ Java(tm) Solution for Real‐Time and Embedded Systems Copyright (c) 2005 ‐ 2007 Javolution (http://javolution.org/). 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. 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.

140

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

JScience Version: 4.3.1 Description: Java library for Geo spatial data manipulation Software site: http://jscience.org Source Code: The source packages for JScience 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: JScience ‐ Java(TM) Tools and Libraries for the Advancement of Sciences Copyright (C) 2006 ‐ JScience (http://jscience.org/). All rights reserved. Redistribution and use 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 and include this license agreement. * 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. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY 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 ONANY 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. 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 from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in the preamble of this document. 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. Redistribution and use 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 XStream 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 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.

141

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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 from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in the preamble of this document. 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 acquired from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in the preamble of this document. 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. 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,

142

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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. 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 from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in the preamble of this document. 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. Redistribution and use 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 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. 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. 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 Description: Used to access Prizm APIs exposed through Web Services from WM Software site: http://ws.apache.org/axis/

143

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Source Code: The source packages for JAX RPC 1.1 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. log4j‐1.2.12.jar Version: 1.2.12 Description: Used to access Prizm APIs exposed through Web Services from WM 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 acquired from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in the preamble of this document. wsdl4j‐1.5.1.jar Version: 1.5.1 Description: Used to access Prizm APIs exposed through Web Services from WM 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 acquired from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in the preamble of this document. commons‐logging‐1.0.4.jar Version: 1.0.4 Description: Used to access Prizm APIs exposed through Web Services from WM 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 Description: Used to access Prizm APIs exposed through Web Services from WM 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

144

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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

145

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.

146

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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. WIRELESS MANAGER™, CAMBIUM™, CAMBIUM NETWORKS™, and the Cambium Networks Logo are trademarks of 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.

147

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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 acquired from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in this document. License: The OpenORB Community Software License, Version 1.0 Copyright (C) 2002 The OpenORB 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 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 soft‐ ware itself, if and wherever such third‐party acknowledgments normally appear. 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 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</a>). 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.

148

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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. 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 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 from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in 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

149

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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. Redistribution and use 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 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 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 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 from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in 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. 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.

150

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

3. The end‐user documentation included with the redistribution, if any, must include the following 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. 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 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 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. 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

151

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

Software Site: http://www.zlib.net Source Code: The source packages for ZLib 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: 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 acquired from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in this document. 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

152

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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

153

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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 Software Site: http://sourceforge.net/project/showfiles.php?group_id=36382&package_id=28579 Source Code: The source packages for jasperreports.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 this document.

154

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Jfreechart.jar Version: 0.9.15 Description: Charting tool Software Site: http://sourceforge.net/project/showfiles.php?group_id=15494&package_id=12428 Source Code: The source packages for Jfreechart.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 this document. 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 acquired from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in this document. 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 Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in this 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 Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in this 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 from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in 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 acquired from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in this document.

155

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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 Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in this document. j2ssh‐common.jar, j2ssh‐core.jar (SSHTools) Version: j2ssh0.2.7 Description: SSH Tools Software Site: http://sourceforge.net/project/showfiles.php?group_id=60894&package_id=57233 Source Code: The source packages for SSH Tools 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. 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

156

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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

157

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.

158

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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.

159

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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.

160

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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.

161

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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 Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in this document. Struts Version: 1.1 Description: Web Framework Software Site: http://www.apache.org/dist/jakarta/struts/binaries/jakarta‐struts‐1.1.zip http://www.ibiblio.org/pub/packages/infosystems/WWW/servers/apache/jakarta/struts/binaries/jakarta‐struts‐ 1.1‐rc1.zip Source Code: The source packages for Struts 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. 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 from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in 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 from Cambium. To obtain the software from Cambium, please contact Cambium using the methods described in this document.

162

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 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. 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.

163

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

Abbreviations API

Application Programming Interface

DHCP

Dynamic Host Configuration Protocol

DNS

Domain Name Server

EMS

Element Management System

GUI

Graphical User Interface

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

RDBMS

Relational Database Management System

SMI

Structure Management Information

SNMP

Simple Network Management Protocol

UDP

User Datagram Protocol

User Interface

VLAN

Virtual Local Area Network

165

WM Release 4.0 Server Administration Guide

Issue 2 April 2012

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 on Page 168.

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,

167

Issue 2 April 2012

WM Release 4.0 Server Administration Guide

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. 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:

168



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://www.cambiumnetworks.com/forum/.



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/technical.php.



a technical support case, which you can open at http://www.cambiumnetworks.com/support/support_case.php. 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.