wm4 0 releasenotesissue1

Cambium Wireless Manager Release Notes

System Release 4.0

Issue 1 May 2012 © 2012 Cambium Networks. All Rights Reserved.

Accuracy

While reasonable efforts have been made to assure the accuracy of this document, Cambium Networks assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. Cambium reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Cambium does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Cambium products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Cambium intends to announce such Cambium products, programming, or services in your country.

Copyrights

This document, Cambium products, and 3rd Party Software products described in this document may include or describe copyrighted Cambium and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Cambium, its licensors, and other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Cambium, its licensors, or the 3rd Party software supplied material contained in the Cambium products described in this document may not be copied, reproduced, reverse engineered, distributed, merged or modified in any manner without the express written permission of Cambium. Furthermore, the purchase of Cambium products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Cambium or other 3rd Party supplied software, except for the normal non‐exclusive, royalty free license to use that arises by operation of law in the sale of a product.

Restrictions

Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Cambium.

License Agreements

The software described in this document is the property of Cambium and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement. See the end user licenses published (redundantly) in the user guide or the server administration guide for Release 4.0.

© 2012 Cambium Networks, Inc. All Rights Reserved.

Table of Contents Accuracy...................................................................................................................................... 2

Copyrights ................................................................................................................................... 2

Restrictions ................................................................................................................................. 2

License Agreements.................................................................................................................... 2

1 Introduction................................................................................................... 5

2 Elements Supported in this Release................................................................... 7

2.1 All Supported Elements .................................................................................................. 7

2.2 Full Support for Operator‐defined Third‐party Elements............................................... 9

2.3 Limited Support for Generic Elements ........................................................................... 9

3 Features Introduced by This Release ................................................................11

4 Device and Software Requirements ..................................................................13

4.1 Network Management Capacity................................................................................... 13

4.2 Hardware Requirements............................................................................................... 13

4.2.1 Server Device Hardware Requirements ................................................................................ 13 4.2.2 Client Device Hardware Requirements ................................................................................. 13

4.3 Software Platforms, Compatibility, and Requirements................................................ 14

4.3.1 Supported Upgrade Paths ..................................................................................................... 14 4.3.2 Operating Systems ................................................................................................................ 14 4.3.3 Other Dependencies.............................................................................................................. 15 4.3.4 Database................................................................................................................................18

5 Installation Tool ............................................................................................19

6 Documentation .............................................................................................21

6.1 Release 4.0 Quick Start Guide....................................................................................... 21

6.2 Release 4.0 Administration Guide ................................................................................ 21

6.3 Release 4.0 User Guide ................................................................................................. 22

6.4 Links to Other Important Documents........................................................................... 22

7 Issues in WM Operation .................................................................................25

7.1 Issues Resolved With This Software Release................................................................ 25

7.2 Other Resolved Issues................................................................................................... 30

7.3 Issues Acknowledged With This Software Release....................................................... 33

Resources for Support ..........................................................................................37

Community Forum.................................................................................................................... 37

Technical Support ..................................................................................................................... 38

WM Release 4.0 Release Notes Issue 1 May 2012

5

1 Introduction Wireless Manager (WM) Release 4.0 continues full configuration and ongoing management

capabilities for the range of products that are listed under Elements Supported in this Release on

Page 7 and for non‐Cambium devices for which operators create their own valid device definition

templates. It also collects and displays events and alarms for the Cambium Point‐to‐Point (PTP) and

Point‐to‐Multipoint (PMP) products, thus providing a consolidated view of the status of the Cambium

networks in a single screen.

WM Release 4.0 continues the capability to overlay network elements onto an embedded Google

map. Maps like this allow you to visualize and analyze a wide range of crucial information, including

connectivity between nodes, link quality, range, and device and network availability. These graphical

representations help you quickly see network status, identify any problems, and assess the severity of

impact they will have on the network and its users.

This release has also kept stride with changes in device templates for elements that it has supported

and with new templates for elements that are introduced since the last release.

This document is intended to support only Release 4.0 of WM. All information pertaining to

operations on the client (those operations that are authorized or disallowed by the Operation Tree),

are described here in the user guide, regardless of the permission required to perform them.


7

2 Elements Supported in this Release

2.1 All Supported Elements WM Release 4.0 supports the following device specific types and versions:

Table 1: Supported Device Versions

(continued on next page)

Issue 1 WM Release 4.0 Release Notes May 2012

8


9

2.2 Full Support for Operator-defined Third-party Elements WM offers full SNMP discovery, monitoring, and management support for any non‐Cambium device

for which the operator creates a valid device definition template, and Cambium Networks supplies a

separate document with instructions for those who choose to create them. This release supports

these functions for all SNMPv1, v2, and v3 devices whose operator‐configured IP addresses are within

networked reach of the WM server.

2.3 Limited Support for Generic Elements WM discovers as a generic element any SNMP‐enabled1 non‐Cambium device for which no valid

device definition template exists. This is distinguished from a Cambium Networks device, for which a

device definition template is part of the WM software distribution, and from any third‐party devices2

for which the operator has created a valid device definition template.

A generic device that WM discovers counts against the node limit in the WMEMSPack license. For a

generic device, WM performs the following element management functions:

discovery regardless of SNMP version (v1, v2c, or v3)

configuration of name, location, contact information, and device description and the following geo‐location attributes:

− latitude

− longitude

− height above the ground

collection and display of operational state performance statistics (number of ports, in‐ and out‐octets, and in‐ and out‐errors)

collection and processing of cold start, link up, link down, and authentication failure traps

representation with the generic device icon ( ) in

− the physical map

− parent‐child and extended family views

− the Inventory

− the Applications tree

− viewers for alarms and events

WM also allows them to be members of user‐defined device groups. WM keeps their IP addresses

and for each, provides a dashboard (as it does for Cambium device types) to display current alarms

and events with some configured attributes and statistics.

1 Supporting RFC1213‐MIB. 2 Cisco Router and Cisco Switch are third‐party devices for which the WM distribution provides valid device definition templates.


11

3 Features Introduced by This Release WM Release 4.0 introduces the following features:

a user interface for cloning device configurations with values, from either a selected device or the database, either pushed to destination devices of the same device type or saved to a template you will later push to them, without touching attributes that should be excluded from cloning; for example, without

− those that are not readable from the source, such as keys and passwords.

− others that could fail the operation, such as Device Region Code and Device Default Reset.

− optionally, those that should in most cases remain unique, such as IP, DHCP, NAT, and bridge mode attributes.

a system‐configured view of events that are related to discovery.

device type graphical summary reports for

− PMP 320 AP

− PMP 320 CPE

− PMP AP

− PMP backhaul

− PMP FSK SM

− PMP OFDM SM

− PTP

support for multiple default configuration templates per device type to be applied during discovery.

added support for

− PTP 250 Master and Slave as read‐only elements.

− PTP 300, PTP 500, and PTP 800 Master and Slave as Version 05‐00. This includes new OIDs for PTP 300 and PTP 500 location attributes in their v05‐00 releases. The user guide provides a workaround.

− PTP 400 Master and Slave as Version 09‐01.

− more attributes of the Extreme Switch.

− PMP 320 Release e2.3. For the AP, this includes

Network Configuration attributes for SNMP version (v1/2c or v3), web access security (HTTPS or HTTP), and serial interface (CLI or uGPS).

read‐only attributes for GPS location, the active service flow count, and the frequency range and restriction mode of the AP.

performance tables for UL and DL MCS counters of registered CPE's MCS and HARQ stats.

a frame utilization table used by the native Frame Utilization tool in WM but hidden from user configuration templates.

updates to the Upload AAA Certificate utility, tables for user management and trap destinations, and the Slots Measurement, MAC Version, backoff values (for DL, UL, and ECINER), Sync Source, Selected DL/UL Ratio, and Sync Status attributes.


12

commands that Save Configuration Command, Reboot Device, Clear [service flow] Counters, and Clear [MCS] Statistics.

introduction of performance statistics for the following data:

‐ received/transmit data rate

‐ received IP packets with and without VLAN tag

‐ received non‐IP packets with and without VLAN tag

‐ received packets classified and unclassified

‐ DL and UL MCS state of each registered CPE

‐ antenna method of each registered CPE.

elimination of the need for operators to have their own physical map licenses.

a means to terminate a rogue or runaway client session while other concurrent sessions continue.

changes in the integrated software upgrade utility.

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.

removal of trap port configurability and trap parser interfaces.

removal of the System Administration web interface from the WM client application.

elimination of all support for mesh elements. This is reflected in

− removal of

the capability to identify, monitor, and configure any mesh element device types, including RFMS and ADSP.

their templates of all kinds.

the mesh‐specific system reports that previously supported their management.

the Historical Client Statistics feature, except that the HistoricalClientStatisticsCleanUp policy is still available for adding to automate the removal of legacy records from previously managed mesh elements for operators who upgrade to Release 4.0.

the Search for Client Station feature.

Layer 2 Ping.

Sleep Mode.

the VAP feature.

− changes to

the Device Group feature.

Wireless Manager Ultralight.

the Physical Map feature.

the treatment of mesh elements as generic, in that

− if the Discovery Configurator is properly set, Release 4.0 can discover them as generic elements.

− the Manage Multi‐Agents feature is still in place.

− each agent in a mesh device will be discovered as an individual generic element.

− for licensing purposes, each will count as an individual device against the license capacity.


13

4 Device and Software Requirements

4.1 Network Management Capacity Where the requirements that are listed in this section are met or exceeded, the WM Release 4.0

server can concurrently monitor and manage as many as 5,000 network elements, with the following

upper limits for each supported network element type:

1,000 PMP APs

4,000 PMP SMs

1,000 PTP links (2,000 PTP elements)

This release supports as many as

1,000 traps per second.

20 concurrent client connections.

4.2 Hardware Requirements Requirements for the server and client devices are distinguished as follows. Devices that are used for

both must meet both sets of requirements.

4.2.1 Server Device Hardware Requirements

The following specifications are recommended as minimum hardware requirements for the

WM Release 4.0 server:

a server‐class CPU, as distinguished from a desktop computer

4 GB RAM

a dual‐core processor, 2 GHz+

RAID storage (all collected data is stored in the MySQL database on the server)

4.2.2 Client Device Hardware Requirements

Any modern desktop or laptop that meets the following minimum standards can run the WM

Release 4.0 client application:

15 MB storage space

a high‐speed link of at least 1 Mbps. (Slower connection speed causes slow startup and the possibility of other problems after startup.)

screen resolution setting of 1024 x 768


14

4.3 Software Platforms, Compatibility, and Requirements

4.3.1 Supported Upgrade Paths

The software upgrade paths to this release are strictly limited as are those of successive service packs

when they are made available. 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.

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

2. Install Release 3.0 SP 3 as described in the service pack notes for Service Pack 3.

3. Start the WM server process as described in the server administration guide for Release 3.0.

4. Stop the WM server process as described in the server administration guide for Release 3.0.

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

Future Release 4.0 service packs will be supported for only Release 4.0.

4.3.2 Operating Systems

OS Platforms for the Server

The following are supported for the Release 4.0 server:

Windows Server 2008 R2 Enterprise

CentOS 5.x, 32‐bit

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

note .............A server on a Linux or CentOS operating system requires the installation of a GUI windowing environment.

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.

For OS‐specific installation instructions, see the Cambium Wireless Manager 4.0 Quick Start Guide.


15

important ........... This is an advisory to an operator who has backed up the server data from the previous release in order to manually restore it on a different server device, one that runs an OS version that Release 4.0 supports. (As stated in the server administration guide, the Restore System command option is not supported for restoring the data onto a different server device, but you can restore data according to procedure titled "To migrate operator data in upgrade of WM plus the OS" in that guide.) You must assign the old server IP address to the server on the new device. One problem that this will avoid is a plotted display of data from both servers being rendered in the "WM Monitoring" Collected statistics window when you launch HelpDiagnosticsServer Health Diagnostics.

VMware on the Server

VMware vSphere is supported on the Release 4.0 server device.

OS Platforms for the Client

The WM Release 4.0 client application supports any of the following operating systems:

Windows 7 Professional, 32‐bit

Windows Server 2008 R2 Enterprise

Red Hat Enterprise Linux Version 5.5 ES, 32‐ bit.

The following other OSs are expected to work but were not tested with the client application:

other 32‐bit Windows versions

CentOS 5.5, 32‐bit.

4.3.3 Other Dependencies

Java in the Server

The server requires Java 1.6.

Java Runtime Environment in the Client

The WM client application supports the 32‐bit platform of either of the following operating systems:

Windows 7 Professional.

Red Hat Enterprise Linux Version 5.5 ES.


16

The client is launched using the Java Web Start Application Manager. The client requires Java 1.6,

which is satisfied as follows:

Where Java 1.4.2 or later is present in the client device, WM automatically attempts to install Java 1.6:

− If security applications and setting on the client device allow the installation, no further action is required of the client device administrator.

− If they do not allow it, then proceed as described in the following bullet.

Where 1.4.2 or later is not present, you must install Java 6 and then launch the client, which will then use Java Web Start to install itself.

The client‐related jar files are downloaded when the client connects to the server for the first time.

Every subsequent time the client connects to the same server, WM verifies these downloaded files

for updates.

Browsers

The client device requires one of the following HTTP browsers:

Mozilla Firefox 3, if the client is on a Linux device

MS‐Internet Explorer 7, if the client is on a Windows device

Port Availability and Assignments

Communications between the server and client require that two port assignments (for

NMSSocketPort and NMS_FE_SECONDARY_PORT) are made in the server file system after WM

installation or upgrade. Instructions for how to configure server‐client communications after

installation are documented in both the quick start guide and the server administration guide.

The port assignments that the Wireless Manager components use must be open in the firewall,

where a firewall is implemented.


17

Table 2: Ports that must be open

Server Port Usage

25 Outbound connection to SMTP server for email configuration.1

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

WM

61001 Outbound UDP from BAM to APs.

27000 WM to request licenses.5

License Manager 27443

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

5


18

Server Port Usage

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

GeoServer

8080 Communications between WM and the web administration interface of GeoServer.

NOTES:

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

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

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

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

5. Port number is reconfigurable in .../server/conf/licensing.xml.

4.3.4 Database

The installation tool for WM Release 4.0 installs a MySQL Server Version 5.1 database whose service

name is WMSMySQL. During the installation, the tool prompts you to input the root password for

MySQL Server and the username and password for the WMSDB database. Although the tool installs

this database on the WM server device, Release 4.0 supports the database being on a device remote

to the server.


19

5 Installation Tool Cambium Networks provides the installation tool for this release as an available download during the

license procurement process.

This tool supports both

fresh installation. See the Cambium Wireless Manager 4.0 Quick Start Guide.

upgrades from only Release 3.0 with Service Pack 3. See the Cambium Wireless Manager Release 4.0 Server Administration Guide.

The distribution from this tool includes

License Manager, software application that is required for

− validating the WM server license.

− allocating WM management licenses to devices against the total available license count.

− validating the physical maps license.

− validating the BAM server license, where BAM is deployed.

− allocating licenses for authentication and for pushes of bandwidth service plans and VLAN profiles to PMP slave devices, where BAM is deployed.

the option to install Network Updater (CNUT).

the script to install the MySQL database for fresh installations or to migrate it (make it adaptable to new field definitions and field sizes and to all new queries) for upgrades.

the scripts to configure connections to License Manager, the database, optional BAM, and the optional system to be accessed via the northbound interface from WM.

an MD5 checksum to verify that the tool did not experience corruption during its download.

the initial versions of the software product documentation. See Documentation on Page 21.

For information on licensing the software products

see the Cambium Wireless Manager 4.0 Quick Start Guide.

contact your Cambium Networks representatives.

for the upgrade case, see the Cambium Wireless Manager Release 4.0 Server Administration Guide.

For information about migrating data from Prizm to WM, see the Prizm‐to‐Wireless Manager

Migration Guide.


21

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

6.1 Release 4.0 Quick Start Guide The quick start guide supports only Release 4.0 and documents

the system requirements

the procedure for a fresh installation

client device setup

port configurations to set for client‐server communications after the server installation

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

6.2 Release 4.0 Administration Guide This administration guide supports only Release 4.0 and documents

port usage

database administration

paths to templates that configure information structures for

− device definition

− configuration values to push to elements

− reports in the client application that display current values of configurable attributes in the elements being managed

server‐side adjustments for

− discovery

− fault management

− performance management

− security management

− physical map features

http://www.cambiumnetworks.com/support/planning/index.php?cat=1&type=0�


22

server logs

licensing and upgrading WM software

default values for

− connections to License Manager, the database, and BAM

− SNMP settings to use in the northbound interface to another system

backing up the WM system

using the MIB browser

6.3 Release 4.0 User Guide If you are a client administrator or user, use the user guide. The Cambium Wireless Manager Release

4.0 User Guide describes and provides procedures for operations in the WM client interface for

Release 4.0. Only authorized users can log into a WM client and access specific features, based on

assigned user privileges. Contact your system administrator for help with your authorized user

privileges.

Device‐specific information is provided in the documents that support the devices. This includes

definitions for configurable attributes. However, the WM user guide describes how to compose a

configuration template, assuming that you know what attributes and values you want to configure,

and describes how to use WM to push those values to the elements.

All information pertaining to operations on the client (those operations that are authorized or

disallowed by the Operation Tree) is provided in the user guide, regardless of the permission required

to perform them.

This construction for the user guide allows client administrators to use the whole book and all of its

cross‐references, whether they link to complex and restricted operations or to simple operations that

are universally permitted across the operating staff. At the same time, users with relatively low

permissions can view procedures that only client administrators can execute. The rich security

features of WM make this a practical design for the user guide.

6.4 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

http://www.cambiumnetworks.com/support/ptp/software/index.php?tag=linkplanner�

http://www.cambiumnetworks.com/support/pmp/software/index.php�




23

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

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






− 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





For declarations of conformity for individual network elements in their various frequency band

ranges, see http://www.cambiumnetworks.com/doc.php.




http://www.cambiumnetworks.com/solutions/ptp_overview.php�



http://www.cambiumnetworks.com/solutions/products.php?id=ptp100�






http://www.cambiumnetworks.com/solutions/products.php?id=linkplanner�

http://www.cambiumnetworks.com/solutions/pmp_overview.php�



http://www.cambiumnetworks.com/solutions/products.php?id=pmp100�





http://www.cambiumnetworks.com/doc.php�


25

7 Issues in WM Operation

7.1 Issues Resolved With This Software Release The following issues are resolved in Release 4.0:

Issue Description of Resolved Issue Item ID

Physical map throws AJAX errors.

This issue was seen in servers on a Spanish/German/Russian OS platform (based on the value of Locale), for devices that return RSSI as a pure float value. These errors will not be seen in Release 4.0 and later.

0017963

Configuration properties for criteria‐based device group definitions can slow down system performance.

The query has been streamlined such that this type of group definition no longer affects the system performance.

0017920

WM is not discovering PTP devices that are running unbranded firmware.

WM now discovers all supported PTP devices, regardless of whether their firmware is branded or unbranded.

0017893

Discovery probes of write community should be improved.

Device discovery now includes the following functions:

1. Test each read community.

2. For any read community that fails, fail the discovery and generate an event.

3. Test each write community.

4. For any case where all write community strings are attempted and none succeed, generate an event.

5. When defaulting to the global community string, generate an event for any device in which this fails.

6. For any case where write community fails, reset it to either null or the same as the read community.

0017867

Syntax of EtherWAN switch version stored by WM does not reflect increments.

The version syntax that WM stores for the PMP.Switch.14Port device type now matches the available version updates.

0017858

Configuration report from Device for child WM displays NA for attribute values.

When Source data from was set to Device in the Select Configuration Report Data interface for a report on a child WM, the report displayed NA for the values. The report now properly displays attribute values, regardless of whether it is set to Device or Database.

0017841


26


Modify Group fails to change dynamic group definition for a change in Device Height value.

For a criteria‐based device group created from Dynamic Selection, a change in the attribute value of Device Height did not change the constituency of device group.

0017598

The Export Events operation is not functioning.

Both the ActionExport Events and the ActionExport Alerts operations failed to generate a CSV file and caused an exception to be logged, regardless of whether Displayed Custom View Data or Entire Custom View Data is selected.

0017484

The dimensions of the Trap Parser Configuration tool cannot be expanded.

The contents of this tool dialog now expand as the window is resized, and tooltips have been added to it.

0017391

The Collected statistics graph for an SM that has experienced down time does not reflect the missed poll.

A graph in this case would omit plotting data for the poll instance that occurred while the SM was not registered to its AP. Instead, the graph was using averaging to span from data in a successful poll to data in the next successful poll. The graph will now plot the data for the unsuccessful poll.

0017349

The SM registration event filter is no longer available.

This filter has been re‐added to the default Event Filter list as SmRegRediscoveryFilter.

0017324

Current statistics exclude string data.

These graphs were not displaying data that WM receives as data of SNMP String type.

0017320

Consider v1 & v2 check box setting does not persist.

If you unchecked this check box in the Node Discovery tab of the Discovery Configurator, saved and applied this setting, and then closed and reopened the configurator to this tab, the check box would be checked. The setting now will persist.

0017313

Some operations take much too long.

Examples include Start Discovery and Stop Discovery. Where typical execution time had been 5 seconds, times of around 2 minutes were being experienced. The cause has been identified and fixed.

0017271

SM graphical summary report fails after hours of execution attempt.

The execution of PmpFskSmGraphicalSummaryReport.php was seen to run for more than 5 hours and then throw the error Unable to execute report. The cause has been identified and fixed.

0017262

Inventory view does not persist after being filtered for a node in Applications tree.

The Inventory view now remains filtered to the node selected (highlighted) under Inventory in the Applications tree.

0017240

Duplicate discovery occurs when a generic device is rediscovered as its device type.

This occurred for PMP 320 devices that were running Version e2.2.2 and were rediscovered as their type. The instance of the generic type persisted in the Inventory view.

0017233


27


Operators can apply a configuration template to more than one version of the device.

Previous limitation prevented only applying a template to an inappropriate device type. This is because, in some cases, it is much more convenient for an operator to use a template across multiple version of the same device type. They are still able to do so, but will need to click through confirmation against a pop‐up warning.

0017198

Upgrades to WM Release 3 SP 2 hangs for days while statistics migrate.

This no longer occurs. 0017186

Custom views that were configured for SP 1 device groups persist into SP 3.

Upgrades to service packs no longer perpetuate custom views for device groups.

0017178

Configured Collection view fails for large networks at maximum page length.

This problem was seen for a network of more than 2,500 devices when the page length was increased to 50000, at which the view failed to populate. To resolve this issue, the maximum for page length has been reduced to 1000 records.

0017170

Direct Assignment for permissions of a new user spawns an error.

It was proper for WM to throw the warning, since any new user must belong to at least one group. However, the warning said the group, which was misleading. Now the warning states User should be present in at least one of the groups or in a new group, and the Direct Assignment check box is inactive for a user without group association.

0017127

Rediscovery replaces a managed device with a later device having the same IP address.

In this case, the previously Managed device was reset to the Unmanaged state, and the later‐discovered device was automatically set to the Managed state. Now the previously Managed device retains its Managed state.

0017079

The count in the Results tab of the Search utility is cold for device groups.

This count should have been a hot link, as are all other counts expressed in this tab. An example of this issue is shown in the figure titled “Search for input Location contents” in the user guide. (The count is not underscored and is black, not blue.) This count is now linked.

0016992

Restore of backup data that includes a scheduled task causes the server to reject client connection.

This type of data no longer causes problems in the backup/restore process.

0016946

An event that is thrown to the event log sometimes fails to propagate to the Status column of the Inventory view.

This occurred for child devices when their parent devices lost communication with WM, and status polling for those parents timed out.

0016599


28


KDE Linux environment does not support the icon to launch the WM Administrator Tool.

This issue is resolved, so the previous workaround involving Gnome is not longer necessary.

0016435

A user can change permissions for a group of the same name after WM upgrade.

After WM was upgraded from Release 2.2 to 3.0, a user whose user name was identical to a pre‐existing group name in the local system was able to modify the permissions of that group. The client interface now makes unavailable (grays out) the option to access the permissions of all groups, except for users whose account allows this access.

0015875

Invalid‐length messages are accepted by Threshold Properties dialog, but not saved in the database.

If you clicked Modify in this dialog after adding exceptionally long content to the Message and/or Clear Message field, and the length exceeded what could be stored in either of these fields of the database, then a subsequent command option to edit the threshold (ActionsManage Threshold selection, followed by click of the Edit Threshold button), returned an error that the threshold was not found. WM was not applying the threshold. Only messages of fewer than 128 characters are supported for these fields in the database.

Error messages have been added to accurately describe the disposition of the threshold and any reason for a failure to create it.

0015867

Update Manager interface Help button throws error.

The Help button in the interface of this tool for service pack or feature pack installation threw an exception. Help is now properly invoked.

0014861

Property time for a Custom View Scope is ignored.

No filtering was applied based on a time filter defined in the Scope Settings dialog. All filtering based on time works properly now.

0014626

Property severity, previousSeverity, or status for a Custom View Scope generates an error.

For the user whose group had the Custom View Scope assigned, this generated Error while fetching data when the user attempted to open a view such as Inventory, Network Events, Alarms, or Stats Admin.

0014623

Error message for deleting a user from System Administration has no explanatory text.

When the user cannot be deleted, the error now provides an explanation of the reason for which the target user is not being deleted.

0014495

Contents of server file may override user input for discovery and configuration via SNMP v3.

WM was using the contents of a file in the server file system

for Context Name during SNMP v3 discovery, if the user did not populate this field in the SNMP V3 Properties dialog.

for credentials during device configurations via SNMP v3. In this case, the configuration did not succeed if the database credentials from client operations did not match the credentials that this server file stored.

0014455


29


Typical attempts to create a template from a configured device fail.

The Clone Device functionality has been added to device menus, with Save To Template and Device(s) as options for Destination. Input for the configuration data can be the Database or the Device itself. See the user guide section titled “Cloning a Device Configuration.”

0014290

The Configuration Report run in a MoM for a child WM reports incorrect values for rediscovery.

The Rediscovery Configuration (WM Server) section of the report showed values that did not match those configured in the Initial Parameters dialog and Rediscovery Scheduler window of the child WM. In some cases, the reported values were nonsensical (-1, for example) or omitted.

Where values are applicable, correct values are now shown. Where values are not applicable, NA is now shown in their place.

0014137

Configure operation from Configure Device can be cancelled by dismissing the Edit window (X button) but not by clicking Close.

Clicking either the window operator (X button) or the Close button spawns a confirmation window that warns of a configuration in progress and requires that the operator click Yes to both

risk the results of interrupting that configuration

dispose of the Edit window.

0013687

Create Template via Template Operations option results in no attribute tables.

When Create Template was launched from the applications tree by selecting Configuration TemplatesTemplate Operations, the resulting template lacked attribute tables. However, when it was launched from a right‐click on an element of the desired device type (and then Configuration TemplatesCreate Template), the resulting template does contained the tables. The tables are now present regardless of the work flow.

0013595

Scrolling the Hosts column in the Configured Collection takes too long.

This delay no longer occurs. 0013205

Thresholds do not support floating point values.

Although certain use cases that involve rolling experience from Configured Collection views into new thresholds require support for floating point values, thresholds still did not support them. Now they do.

0011135

The physical map in a new client session does not default to the position from the user's last session.

For convenience, WM now saves the location when the user exits the client application.

0009499


30

7.2 Other Resolved Issues The following other issues are also resolved:


Configuration reports composed of multiple attributes yield a single column and null details.

Any configuration report template constructed to pull the values of more than one attribute should return a report that includes one column for each attribute. Further, if you clicked the Details button in the Configuration Report View dialog, the client returned no data in the response dialog; the Execute Report window was blank.

0016103

Criteria‐based device groups revert to manually selected.

Upon subsequent discovery, members that were rediscovered remained in the device group, but non‐member devices that matched the criteria were not added to the device group. In addition, the Device Group OperationsModify Group command option opened the Details tab of the Edit Device Group dialog with its device selection drop‐down list set at Select Device Manually and did not reflect the criteria to which the group had been configured.

0016102

Email notifications are not sent for exceeding JVM memory in client.

When the destination and sender addresses were valid, and the SMTP server was appropriately configured, the destination address should have received email from the WM server, announcing the threshold violation. Instead, the following type of Java exception (excerpted here) was thrown to the stderrN.txt file:

...SMTPMailer.sendMessage(SmtpMailer.java:351)

0015939

Height for AP‐7181 device is changed to 10 m upon any geolocation change.

When a user changed the value for latitude, longitude, and/or height for a device of this type, WM set its height value to 10 meters.

0015928

Leaving Current statistics window open for hours will lock up the WM client.

When a user launched the PlotCurrent Statistic command option and then did not close the resulting Current statistics window within a few hours, the client session froze and WM threw a Java error to the log.

0015898

Configuration template created in LA version throws an error in the GA version.

If one or more attributes that were present in a configuration template created in WM Release 3.0.15 were renamed or no longer existed in Release 3.0.19, then an attempt to edit the configuration task threw the following error:

You selected device(s) which have a different type than the device used to create the template. As a result, some of the template fields may be missing from the view and will not be mapped to the selected device(s).

0015879

The NBI does not update the value of rediscovery interval.

When a user changed the value of Network Rediscovery Interval, WM did not propagate the new value on the northbound interface, so the higher‐tier manager retained the previous setting for this field.

0015878


31


Column errors may be present in System report dumps to CSV.

If you clicked the Export button associated with CSV in a *Report Result window, WM created a comma‐separated values (CSV) file of the data from the report, as it should. However for some device rows, this report was improperly delimited, such that data types were displayed in the wrong columns. This occurred where the value that WM stored for an attribute of the device included one or more commas.

0015871

Classification Rules are not configurable for PMP 320 AP devices in L3 mode.

Since WM Release 2.2 Service Pack 5, WM returned configuration errors for attempts to push Classification Rules to PMP 320 AP devices. The specific errors are

Error in creating variable.

Invalid Data Type for oid.

0015864

Loading the WM MIB causes values that match OIDs to be converted into their textual‐context form.

For example, the framework interpreted .1.3.6.1.4.1.17713.8 as .iso.org.dod.internet.private.enterprises.17713.8, which caused the discovery filter to discover the corresponding device as generic.

0015835

WM may occasionally report Status major for a device whose status is clear.

In this case, the status poll had not occurred on schedule, likely because of the volume of status polling that was occurring at the scheduled time. The larger the network, the likelier this issue was to occur. The workaround is no longer required.

0015640

Agent in child WM rejects SNMP PUT for tftpMode 2.

The following error was encountered and will no longer be seen:

Sent set request to localhost : 8001

Request Failed: Get Response PDU received from 127.0.0.1

Error Indication in response: The value given has wrong type or length.

Errindex: 1

0015545

Node discovery may hang after discovering the first node.

The workaround for this issue no longer required. 0015542

Some keyboard shortcuts are not working.

Ctrl+I was not launching the Configure Device dialog, and Ctrl+W was not launching the device management web page.

0015353

WM establishes no automatic logical link between a PTP 100 slave device and a CMM4 in the physical map.

Even though the link existed and was reflected in the Inventory and Extended Family views, the physical map did not reflect the link between these device types.

0015030

Client logs show a sleep interrupted error when the user closes the Discovery Configurator.

This error appeared in the AggregatedDiscoveryLogN.txt file as java.lang.InterruptedException: sleep interrupted. The occurrence of this error was intermittent, but independent of the number of devices discovered.

0014826


32


Expired or imported user new password configuration with expiry throws exception.

When this occurred, the system rejected the next login attempt, as if the new password had expired, even when the expiry that the user configured had not been reached.

0014676

With no Performance Polling enabled, WM still shows performance data collected from some device types.

This issue appeared to be limited to servers that had been upgraded to Release 3.0.

0014629

Error is thrown unnecessarily for restore Configuration Point Selection.

WM internally encountered a time out condition too soon after a Restore configuration from Configuration Control for a PMP 320 AP. When this occurred, the error thrown was Restore Configuration failed.

0014541

Device type selection for a scheduled task takes too long and can result in the wrong types selected.

Configuration and Reports Task Types for a scheduled task accepted Specific Type or Device Type for device selection, but each of these criteria required selection from the entire uncategorized list of supported types, which was a time‐consuming and sometimes confusing review of formal, arcane type names.

0014522

System Administration disallows user creation without a group association. Security Administration allows it.

Now, properly, both System Administration and Security Administration will disallow it.

0014496

Modify custom view criteria character limit not supported.

For the uClass, sysOID, sysDescr, and community properties for a custom Inventory view, an entry of the maximum supported number of characters caused the Apply Filter operation to throw the following error:

Data truncation: Data too long for column...

0014243

Initially opened view window sizes do not relate to the size of the view panel.

Some opened wider than and some narrower than the view frame. The workaround is no longer required.

0014080

Tables in configuration templates do not interface well.

Sometimes two clicks were required in a cell to focus the mouse cursor. It was also not obvious enough which cells can be edited.

0012068

Rediscovery Scheduler dialog discards the Regular Interval setting when Specific Dates or Days of Week is selected.

The value of Network Rediscovery Interval (h:m:s) for Regular Interval is now restored to the default value (48:0:0) when Specific Dates or Days of Week is configured.

0011787

Click in report template stalls WM.

WM sometimes temporarily hanged when it encountered a random click in a report template that was being viewed in the client.

0011638


33

7.3 Issues Acknowledged With This Software Release The following issues are acknowledged in WM Release 4.0:

Issue Description of Acknowledged Issue Item ID

Name and Description of PMP 320 AP on e2.3 are rendered in wrong format.

These values of the Active alarms table in the AP should be rendered in ASCII, but are instead rendered in hexadcimal value.

0017990

RF Link Availability for PTP 500 is rendered in wrong format.

This should be rendered as a percent, but has been seen rendered as 1,000 times the percentage.

0017979

WM fails to launch the LINKPlanner application.

The workaround is to directly launch the application by executing C:\Program Files\Cambium Networks\LINKPlanner\LinkPlanner.exe or /usr/bin/cambiumnetworks/LINKPlanner/LinkPlanner.bin.

0017943

Attributes are redundantly shown in a Dynamic Selection.

When the device type for a Dynamic Selection device group being defined is PMP.OFDM.SM with v11.1, the interface provides more than one instance of attributes including the latitude, longitude, IP address, and bandwidth.

0017925

Configuration report for child WM displays inactive rediscovery schedule attributes.

This report should display the value of only the currently active rediscovery schedule attribute. Instead, it displays values of all three attributes: Regular Interval, Specific Dates, and Days of Week.

0017842

After poll failure, Collected statistics displays no data.

The workaround for this issue is to either

wait until after at least one successful poll.

In the Poll Details interface of the client application, for each Data Identifier manually update the value of

− Stats Data Table Name to table STATSFLOATDATA% or

− String Data Table Name to STATSSTRINGDATA%.

See the user guide section titled “Selecting the Data Identifier for Data Collection.”

0017762

Execution of X Top 25 performance report appears to hang.

Although the appearance is that the report hangs, it indeed continues to execute, but at a pace that may require several days to complete.

0017641

Client may not reopen when closed after significant load increase on server.

This issue has been experienced where Comodo firewall is active. The error message thrown when the client fails to reopen may not point to the cause, but WM does not have the capability to change or suppress it.

0017631


34


No error is thrown when a threshold without data is added.

The creation of the threshold fails, as it should, but no indication of the failure to create it is provided to the user.

0017602

Permitted Operations for Group retains some SP 3 permissions through retreat to SP 2.

Following the retreat, groups and their users who had been assigned Create User Script Task and/or Credential Manager permissions continue to have these in the Permitted Operations for Group window, even though these operations are properly excluded from the Permissions tree hierarchy in WM Release 3.0 with Service Pack 2.

This problem does not exist in Service Pack 3 or in Release 4.0.

0017307

PMP 320 devices do not report their RF throughput to WM.

When these devices are in their Layer 2 mode, they do not respond to SNMP queries for the value of this attribute.

0017266

Network Discovery tab changes do not trigger rediscovery.

If you make any change in the Network Discovery tab of the Discovery Configurator, the change does not trigger immediate rediscovery. By contrast, any change in the Node Discovery tab triggers immediate node rediscovery.

0017257

WM may be erratic in detecting and displaying PMP 320 links.

By default, PMP 320 APs include the address of all CPEs of the network in their MAC address tables since all CPEs exist within the same subnet, and WM reads these tables and often shows links between APs and CPEs that are not in link with each other.

Until the PMP 320 APs support automatic configuration of only the linked BSIDs, operators should manually configure these in the APs.

0016840

WM cannot configure multiple devices for VLAN membership.

Apart from through a VLAN profile in the BAM subsystem, WM has no way to configure VLAN membership for multiple devices.

0016648

Plotted and tabular data in spectrum analyzer results vary from those on the device.

In some cases, this is seen for the Instant, Avg, and Max tabular values and also for the number of the various frequencies plotted. These cases are the result of WM filtering out frequencies that are legitimately rendered in the device's management web interface but changed to 0.00 with incorrect dBm values in the XML file that WM uses for rendering its results.

0016260

$message contents are null when email notifications sent from Event Filter Action are received.

Until this issue is resolved, the following practices are recommended:

When defining email notifications from Event Filter Action, use $text instead of $message.

When defining email notifications from Alert Filter Action, continue to use $message.

0016147

Some BsID resets fail. Sometimes and without pattern, except apparently more often with Priority 1, an attempt to set the Configuration GroupGeneral ConfigurationBSID attribute to the value 00:00:00:00:00:00 fails.

0016131


35


When the QOS State attribute is set to Disable for a 14‐port EtherWAN switch, its management web interface fails to sync up with changes made via its SNMP interface.

Conversely, when this attribute is set to Enable, the GUI properly reflects SNMP changes for the values of objects ewnQoSWRRqueueCoSmap and ewnQoSWRRqueueDSCPmap.

At Disable, the GUI does not reflect the changed values.

0016091

Alarms do not automatically clear for devices whose IP address changed.

For any device that generated an alarm, then whose IP address changed, and then whose alarm condition experienced a clear event, the alarm does not automatically clear, since the Failure Object that associated the alarm with the device was tied to its IP address. The workaround is to perform the following steps:

1. click to highlight the target alarm in the Alarms view.

2. press Ctrl+E.

3. scan the Network Events view of events that have the same Failure Object.

4. find a corresponding clear event.

5. bring the Alarms view back to the top in the view frame.

6. with the target alarm still highlighted, press Ctrl+L to deliberately clear the alarm.

0015639

Child node permission defies parent node setting.

In the permissions tree hierarchy (alternatively called the Operation tree in the WM client) for a group, a denied setting for a parent node does not necessarily preclude a permitted setting for one or more of its child nodes. Moreover, a saved set of group permissions that includes a child setting in conflict with its parent setting may result in the child setting being not editable in permissions for a user who is assigned to that group.

0015486

Reports and WM Ultralight improperly render table data.

In device summary reports and in Wireless Manager Ultralight, table data that devices provides is expressed raw and is not human readable. For example, the whispBoxBridgeTable leads with all of the MAC addresses and is not rendered tabular.

0015002

WM updates User Management table in PMP 320 AP, but not its own table also.

WM throws a no creation error occurred message when you configure the device for a change in its User Management table. The device is successfully updated, but WM continues to display the previous user management data.

0014825

Attempts to delete and to disable a user of a PMP 320 AP fail.

Attempts to delete the user result in A commit failed error occurred. This would be seen in the Details column for the Configuration Result.

Attempts to change the account state to Disabled show Success in the Details column for the Configuration result, but fail to disable the user in the radio.

Any SNMP manager will experience these results, since the errors occur in the radio itself.

0014824


36


WM applies Users group permissions to users whose groups are both Users and Admin.

Each of the three means by which you may assign a user to specific groups may produce this general result:

In the User Administration dialog, a user for whom both the Users and the Admin check boxes are checked for Assign groups for the user will have only the permissions that are configured for the Users group.

Different but still wrong behavior may occur when these two groups are moved from All Groups to Selected Groups in a Setting Groups operation.

Also, moving Admin and Users from Available groups to Enrolled groups in the web‐based User Configuration tool can result in less than admin permissions.

Presently, the only way to assure that WM will apply admin permissions to a user is to ensure that no other group is selected along with Admin for users who should have full admin‐level permissions.

0013992

When the WM server is on a Linux platform, the WM Administrator Tool shows the status of the Linux Apache service.

Unlike in Windows, where the status shown is of the WM Apache service, in Linux it is an unrelated, superfluous, and confusing indication, and it should be removed from the tool. Whenever the WM server is up (WM Service: Started, as the tool indicates), its Apache service is up as well.

0013451


37

Resources for Support

Community Forum The technical support Community Forum is part of the support web site and can be used for asking

questions directly to the support team. Questions and answers are accessible to all so that any

customer can benefit from the same dialogue. To access this forum, visit

http://www.cambiumnetworks.com/forum/. The following is an example of the contents of the

forum page:

This forum requires authentication for posting.

http://www.cambiumnetworks.com/forum/�


38

Technical Support You can obtain support for Wireless Manager from any or all of the following sources:

Wireless Manager setup guide, administration guide, and release notes.

Cambium Networks support web page: http://www.cambiumnetworks.com/support. This page provides links to information on all products and tools, as well as access to customer support materials and interactive support forums. Some of these resources are restricted to registered users and channel partners.

the Community Forum. Visit http://www.cambiumnetworks.com/forum/. See Community Forum on Page 37.

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.

http://www.cambiumnetworks.com/support�

http://www.cambiumnetworks.com/forum/�

http://www.cambiumnetworks.com/support/technical.php�

http://www.cambiumnetworks.com/support/support_case.php�



wm4 0 releasenotesissue1

Technology