Cambium Wireless Manager

Transcription

1 Cambium Wireless Manager Release Notes System Release 4.1 Issue Cambium Networks. All Rights Reserved.

2 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 Cambium Networks, Inc. All Rights Reserved.

3 Table of Contents Accuracy... 2 Copyrights... 2 Restrictions... 2 License Agreements Introduction Elements Supported in this Release All Supported Elements Support Added in this Release Fixes Included in this Release Full Support for Operator defined Third party Elements Limited Support for Generic Elements Device and Software Requirements Server Requirements Server Hardware Requirements Server Software Requirements Client Requirements Client Hardware Requirements Client Software Requirements Java Exception Configuration Port Availability and Assignments Database Supported Upgrade Paths Network Management Capacity Installation Tools Documentation Quick Start Guide for Release Server Administration Guide for Release User Guide for Release Links to Other Important Documents Issues in WM Operation Issues Resolved With This Release... 27

4 6.2 Issues Acknowledged With This Release Resources for Support...33 Community, PMP, and PTP Forums Technical Support... 35

5 WM Release 4.1 Release Notes Issue 3 1 Introduction Wireless Manager (WM) Release 4.1 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. This release 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. Issue 3 of these release notes is published to announce support for Windows Server 2012 R2 Standard Edition as the operating system for the WM server. This is stated in Table 3: Software requirements for the WM server under Server Software Requirements on Page 14. 5

6

7 WM Release 4.1 Release Notes Issue 3 2 Elements Supported in this Release 2.1 All Supported Elements WM Release 4.1 supports the following device specific types and versions: Table 1: Supported Device Versions (continued on next page) 7

8 Issue 3 WM Release 4.1 Release Notes (continued on next page) 8

9 WM Release 4.1 Release Notes Issue 3 (continued on next page) 9

10 Issue 3 WM Release 4.1 Release Notes 2.2 Support Added in this Release WM Release 4.1 introduces support for epmp 1000 AP and STA in their Release Fixes Included in this Release WM Release 4.1 fixes the issues that are described under Issues Resolved With This Release on Page 27. Other known issues are described under Issues Acknowledged With This Release on Page 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.5 Limited Support for Generic Elements WM discovers as a generic element any SNMP enabled 1 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 devices 2 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 1 Supporting RFC1213 MIB. 2 Cisco Router and Cisco Switch are third party devices for which the WM distribution provides valid device definition templates. 10

11 WM Release 4.1 Release Notes Issue 3 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. 11

12

13 WM Release 4.1 Release Notes Issue 3 3 Device and Software Requirements 3.1 Server Requirements Server Hardware Requirements The WM server requires the following hardware characteristics for its proper operation. Table 2: Hardware requirements for the WM server Requirement type With 100 nodes With > 100 nodes Virtual machine hardware class server, not desktop server, not desktop server, not desktop RAM 4 GB 8 GB 8 GB for 100 nodes 12 GB for more processor dual core 2 GHz quad core 2 GHz 2 GHz dual core for 100 nodes quad core for more storage RAID 1 RAID 5, 10,000 rpm drives RAID 1 for 100 nodes uninterruptible power supply (UPS) scheme for graceful shutdown during power outage highly recommended highly recommended highly recommended highly recommended highly recommended highly recommended 13

14 Issue 3 WM Release 4.1 Release Notes Server Software Requirements The WM server requires the following software versions or configurations for its proper operation. Table 3: Software requirements for the WM server Requirement type Version Operating system 1 Windows Server 2012 R2 Standard Edition 2 Windows Server 2008 R2 Windows Server 2008 SP 2 (Standard, Enterprise, or Datacenter) Red Hat Enterprise Linux 5.x 32 bit (not 64 bit) ES (not AS) Red Hat Enterprise Linux 6.x 32 bit (not 64 bit) ES (not AS) CentOS 5.x 32 bit (not 64 bit) CentOS 6.x 32 bit (not 64 bit) Firewall See Port Availability and Assignments on Page 16. Java Installed as part of the WM distribution 3 database licensing dos2unix package Special considerations for software installations if virtualization is installed MySQL Server Version 5.1, optionally installed by the WM distribution tool. See Database on Page 18. License Manager, installed by the WM distribution tool WM on Cent OS requires that the dos2unix package is installed before WM in installed. If it is not, then License Manager, web server, and WM server services do not start; and the scripts in the WM server are not properly read. Certain packages are specifically considered problematic for a WM platform: XEN virtualization software, in any WM configuration cluster packages, where the High Availability (HA) configuration is implemented. VMware vsphere. See esxivcenter server pubs.html NOTES: 1. Cambium Technical Support cannot help a network operator customize an OS, for example obtain special Linux library packages, to make WM work on an unsupported version. 2. Although this is a 64 bit OS, it detects that WM is a 32 bit application and runs WM in a 32 bit emulation environment. 3. See Java Exception Configuration on Page

15 WM Release 4.1 Release Notes Issue Client Requirements Client Hardware Requirements The WM client requires the following hardware characteristics for its proper operation. Table 4: Hardware requirements for the WM client application Requirement type hardware class storage link speed Supported any modern desktop or laptop 15 MB 1 Mbps screen resolution 1024 x Client Software Requirements The WM client requires the following software versions for its proper operation. Table 5: Software requirements for the WM client application Requirement type Operating system 1 Browser Software and version Windows 7 Professional, 32 bit Windows Server 2008 R2 Enterprise Red Hat Enterprise Linux 5.5 ES, 32 bit Red Hat Enterprise Linux 6.x ES, 32 bit Mozilla Firefox 3, 32 bit, if the client is on a Linux OS device Internet Explorer 6, 7, or 8; 32 bit, if the client is on a Windows OS device Java JRE 1.6.0_10 or later 2 NOTES: 1. MacOS is not supported. The following additional OSs are expected to work but have not been tested with the client application: Windows versions other than those shown above, assuming they are 32 bit CentOS 5.5 or 6.x, 32 bit 2. Use of an earlier JRE version with WM Release 4.0 SP 3 or later can result in an OutOfMemory error. See also Java Exception Configuration on Page

16 Issue 3 WM Release 4.1 Release Notes 3.3 Java Exception Configuration An attempt to connect to the server from an otherwise supported client device may result in a Java warning message that states the following: Do you want to run this application? This application will be blocked in a future Java security update because the JAR file manifest does not contain the Permissions attribute. Please contact the publisher for more information. If you click Run in the Java window, an Application Error window pops up with the message Unable to launch the application. If you encounter this, perform the following steps: 1. If the client device OS is Windows a. Open the Control Panel. b. Double click Java. 2. If the client device OS is Linux, enter /usr/local/cambium/wm/jre/bin/jcontrol. 3. In the resulting Java Control Panel, click the Security tab. 4. Click the button for Edit Site List In the resulting Exception Site List dialog, click the Add button. 6. In the text box of the Location column, identify the server and port as follows: 7. Click OK. 8. Back in the Java Control Panel, click OK. 9. Direct your browser once again to In the Wireless Manager login page, click the button for Launch WM Client. RESULT: The Wireless Manager Authentication dialog opens for logging in. 3.4 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. 16

17 WM Release 4.1 Release Notes Issue 3 Table 6: Ports that must be open Server Port Usage 25 Outbound connection to SMTP server for configuration 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 Inbound UDP for APs to request authentications from BAM Configuration server Socket server Network management back end server. WM 2501 To turn the SM Autoupdate feature on or off in APs Queries to the MySQL database Inbound TCP for TFTP connections in the firmware upgrade process Outbound UDP for SNMP response over the northbound interface (NBI) TCP connections by Tomcat and web server for access to device management web pages Inbound data from the BAM server Inbound TCP for the web server NMS Socket for TCP communication between the WM server and WM client. 3 NMS FE Secondary for TCP communication between the WM server and WM client Outbound UDP from BAM to APs. License Manager WM to request licenses Secure communications between WM and the web server of License Manager. 5 17

18 Issue 3 WM Release 4.1 Release Notes Server Port Usage GeoServer Optional Oracle Java Naming and Directory Interface (JNDI) connection pool via Tomcat. 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. 3.5 Database The installation tool for WM Release 4.1 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.1 supports the database being on a device remote to the server. 3.6 Supported Upgrade Paths Software upgrade paths to this release are unlimited with respect to previous release or service pack. For OS specific installation instructions, see the Cambium Wireless Manager Quick Start Guide for Release 4.1. 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.1 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 Help Diagnostics Server Health Diagnostics. 18

19 WM Release 4.1 Release Notes Issue Network Management Capacity note...neither WM software nor Cambium Networks impose hard limits on the maximum number of devices that WM will manage or support. The recommendations in this section are based on observations and the general experience that WM performance is more sensitive to device load in Windows than in Linux. Where the requirements that are listed in this chapter are met or exceeded, this release can concurrently monitor and manage as many as 10,000 devices in Linux or 7,000 devices in Windows, when the device variety resembles the following: 4 SMs per AP a master and slave PTP device per AP This release supports as many as 1,000 traps per second. 20 concurrent client connections. 19

20

21 WM Release 4.1 Release Notes Issue 3 4 Installation Tools 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 Quick Start Guide for Release 4.1. upgrades from only Release 4.0 Service Pack 5. See the Cambium Wireless Manager Server Administration Guide for Release 4.1. 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 23. For information on licensing the software products see the Cambium Wireless Manager Quick Start Guide for Release 4.1. contact your Cambium Networks representatives. for the upgrade case, see the Cambium Wireless Manager Server Administration Guide for Release 4.1. For information about migrating data from Prizm to WM, see the Prizm to Wireless Manager Migration Guide. 21

22

23 WM Release 4.1 Release Notes Issue 3 5 Documentation important... The installation tool for the WM server deposits an issue of the Cambium Wireless Manager Server Administration Guide for Release 4.1 and the Cambium Wireless Manager User Guide for Release 4.1 into the...server/help directory on the WM server. These documents are placeholders. Immediately after your server installation is completed, visit 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.1, 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. 5.1 Quick Start Guide for Release 4.1 The quick start guide for Release 4.1 supports only this release and it 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 5.2 Server Administration Guide for Release 4.1 The server administration guide for Release 4.1 supports only this release and it 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 23

24 Issue 3 WM Release 4.1 Release Notes server side adjustments for discovery server logs fault management performance management security management physical map features 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 5.3 User Guide for Release 4.1 If you are a client administrator or user, use the user guide. The Cambium Wireless Manager User Guide for Release 4.1 describes and provides procedures for operations in the WM client interface for Release 4.1. 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. 5.4 Links to Other Important Documents For links to important documents about supported network elements, visit After logging into the Support Center at this address, you will have access to the following types of documents: PTP device and PTP LINKPlanner user guides and release notes PMP device user guides, release notes, and MIBs a wide range of PMP 320 device documents CMM user guides and release notes 24

25 WM Release 4.1 Release Notes Issue 3 For links to important documents about management tools, visit the following web pages: Wireless Manager guides, release notes, and service pack notes at tools/wireless manager/ Cambium Network Updater Tool (CNUT) on line help file and release notes at tools/cnut/ Prizm guides, release notes, and its SDK at tools/prizm bam For links to network element features and specifications, visit the following web pages. Cambium PTP: the portfolio at PTP 100 at PTP 200 at PTP 500 athttp:// 500 PTP 600 at PTP 650 at PTP 800 at PTP 810 at Cambium Networks LINKPlanner at tools/link planner Cambium PMP: the portfolio at epmp 1000 at PMP 100 at 100/ PMP 320 at 320/ PMP 400 at 400/ PMP 430 at 430/ PMP 450 at 450/ For declarations of conformity for individual network elements in their various frequency band ranges, see doc for EC conformity 25

26

27 WM Release 4.1 Release Notes Issue 3 6 Issues in WM Operation 6.1 Issues Resolved With This Release The following issues are resolved in Release 4.1: Issue Description of Resolved Issue Item ID Network elements are not completely wiped from the physical map by the hide function. Device Uptime in one dashboard is inherited by the other. None of the attributes in an event notification provide the Device Name. Device rediscovery yield erratic results. System reports that were not previously imported are imported. The operation Status Filter Hide All Status Levels now completely removes all of the element icons from the map. After having two network element dashboards simultaneously open for some length of time, one of the dashboards was inheriting its Device Uptime value from the other. The Device Name (the left column value of the Inventory view) has been added to the Node attribute. The Entity and Source attributes continue to provide the MAC address of the element. Some devices are rediscovered as generic, then have their proper device type instance reset to unmanaged. Ultimately, both instances are set to unmanaged and status polling for the devices is automatically disabled. Although the cause lies in SNMP timeouts, the fix is a workaround to be undertaken when this has occurred. The problem is flagged by a rereg trap: If you receive this trap, perform the following workaround: 1. Stop the WM server. 2. Open file <server>/conf/event.filters for editing. 3. Search for the string SmRegRediscoveryFilter, as shown in the following example: <FILTER name="smregrediscoveryfilter" enable="true" category="pmp" text="completed registration of physical address*"> <FILTER_ACTION classname="com.adventnet.nms.eventdb.userfilter" name="smregrediscoveryaction" userclass="com.motorola.wibb.ems.canopy.server.fault. SmRegRediscoveryFilter"/> </FILTER> 4. Change the value of enable to false. 5. Start the WM server. All system reports were imported after upgrading. Now, only those that had been under the previous release are imported

28 Issue 3 WM Release 4.1 Release Notes Issue Description of Resolved Issue Item ID Upgrade does not carried forward the contents of the UserScripts directory or its Results subdirectory. Configuration report for child WM displays inactive rediscovery schedule attributes. These were being deleted from the WM server file system during an upgrade. Now, these are preserved. It displayed values of all three attributes: Regular Interval, Specific Dates, and Days of Week. This report now displays the value of only the currently active rediscovery schedule attribute Issues Acknowledged With This Release The following issues are acknowledged in WM Release 4.1: Issue Description of Acknowledged Issue Item ID WM shows some statistics for epmp devices in the negative. An element for which a duplicate entry exists as generic is not configurable by template. Where the database is remote to the WM server, discovery configurations do not survive the migration to this release. This can be seen in the RF Throughput graph in the device's dashboiard and in its collected statistics. The configuration template is applied instead to the generic duplicate. Also, the original device's events are logged against the generic instance. Then, if the duplicate is deleted from the Inventory, the template can be successfully applied to the original device. During the upgrade, the contents of the Netowrk Discovery dialog and the Node Discovery dialog in the configurator are lost

29 WM Release 4.1 Release Notes Issue 3 Issue Description of Acknowledged Issue Item ID On Windows Server 2012, the MySQL will not be created by command line execution. Total packets stats are negative for epmp AP. CMM4 device templates should allow read/write for location attributes. WM detects and displays PMP 320 AP CPE connections, but the PMP 320 AP and MIB browser do not. Windows Server 2012 is not one of the OSs that WM supports. However, one of the following workarounds will prevent this problem: Create the database through the WM installation script. OR Perform the following steps: 1. Open the file <server>\bin\reinitialize_database.bat for editing. 2. Search for the string %JAVA_HOME%. %JAVA_HOME%\bin\java -Dmysql.home=%MYSQL_HOME% - Dwebnms.rootdir=%NMS_HOME% jdbc.dropschema %1 %2 %3 %4 3. Immediately before -Dmysql.home=%MYSQL_HOME%, type in -Dos.name="Windows XP", followed by a space. %JAVA_HOME%\bin\java -Dos.name="Windows XP" -Dmysql.home=%MYSQL_HOME% -Dwebnms.rootdir=%NMS_HOME% jdbc.dropschema %1 %2 %3 %4 4. Save and close the file. 5. Open the file <server>\bin\startwm.bat for editing. 6. Search for the string %JAVA_HOME%. 7. After each instance of %JAVA_HOME%\bin\java (there are eight), place your cursor immediately ahead of cp, then type in -Dos.name="Windows XP", followed by a space. 8. Save and close the file. This can be seen in the collected statistics and in the network element dashboard at both the RF Throughput and Ethernet Throughput graphs numeric Packet Statistics block. The affected statistics are Ethernet Rx Packets Ethernet Tx Packets RF UL Packets RF DL Packets. The default latitude and longitude for these devices makes mapping them correctly impossible. Cambium technical support may provide a detailed workaround upon request. In WM, this causes at least the following fields for to display null results in the dashboard of a PMP 320 AP: Connected CPEs [table] Channel Measurement Table Usage Record Table

30 Issue 3 WM Release 4.1 Release Notes Issue Description of Acknowledged Issue Item ID The dashboard for PMP 320 CPE devices display no values for Ethernet statistics. Some Device Groups are not carried forward in a WM software upgrade. Time stamps for alarms and events from PMP.320.APv(e2.3x) devices are incorrect as displayed in WM. PMP 320 devices do not report their RF throughput to WM. WM may be erratic in detecting and displaying PMP 320 links. WM cannot configure multiple devices for VLAN membership. The Packet Statistics and Status blocks of the network element dashboard for devices of this type state Unable to read from device for all of their Ethernet values. The radios are failing to provide these values to WM. The following behaviors apply: Device Group definitions that do not include a device type or device specific type as a criterion are removed during the WM upgrade, with the following qualifications: Those that are not checked Public survive the upgrade (except for those defined for only Mesh device types or only Mesh device specific types). For these previously unchecked Device Groups, If Public is checked after an upgrade, the system removes their definitions. Device Group definitions that do include a device type or device specific type as a criterion survive the WM upgrade. All expressions of times associated with alarms and events for a PMP 320 AP running e2.3 are likely incorrect and should not be trusted until further notice. When these devices are in their Layer 2 mode, they do not respond to SNMP queries for the value of this attribute. 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. Apart from through a VLAN profile in the BAM subsystem, WM has no way to configure VLAN membership for multiple devices Some BsID resets fail. Sometimes and without pattern, except apparently more often with Priority 1, an attempt to set the Configuration Group General Configuration BSID attribute to the value 00:00:00:00:00:00 fails 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

31 WM Release 4.1 Release Notes Issue 3 Issue Description of Acknowledged Issue Item ID WM updates User Management table in PMP 320 AP, but not its own table also. Attempts to delete and to disable a user of a PMP 320 AP fail. 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. 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

32

33 WM Release 4.1 Release Notes Issue 3 Resources for Support Community, PMP, and PTP Forums The following forums 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: the Community Forum. Visit 33

34 Issue 3 WM Release 4.1 Release Notes the PMP Forum. Visit 34

35 WM Release 4.1 Release Notes Issue 3 the PTP Forum. Visit Technical Support You can obtain support for Wireless Manager from any or all of the following sources: Wireless Manager quick start guide, server administration guide, user guide, and release notes. See tools/wireless manager. Cambium Networks support web page: 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 technical forums. See Community, PMP, and PTP Forums on Page 33. 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 support/. a technical support case, which you can open at a support case. The case captures basic information about answers you are seeking or the problem that your network is experiencing and provides this to the support team, who are available 7 days a week, 24 hours a day, and will respond. They will also provide a case number by which you and they can continue to track progress on issues that require deeper investigation. 35