Cambium Networks Services Server: Release Notes
Cambium Networks Services Server: Release Notes
Services Server
Release Notes
• Product
System Release 1.2
Description
• Installation
•• Product Description
Fixed Issues
•• Known
Installation
Issues
• Fixed Issues
• Known Issues
CAMBIUM NETWORKS
TABLE OF CONTENTS
2
CAMBIUM NETWORKS
General information
Version information
2B
Feedback
We appreciate feedback from the users of our products. This includes feedback on the quality and content of our
software as well as the structure, content, accuracy, or completeness of our documents. Send feedback to
[email protected].
3
CAMBIUM NETWORKS
Product Description
Overview
The Cambium Networks Services (CNS) Server is a network management application provided by Cambium
Networks to manage ePMP devices.
Release 1.2 of the CNS Server introduces the following features and enhancements:
• Configure: Simplify network configuration and maintain consistency by centrally managing device settings
via user-defined templates.
o Create configuration templates for AP and STA
o Create configuration templates for specific functional groups (i.e. RF, networking)
o Push configuration templates to individual or batches of radios
o View current configuration of devices on demand.
• Native 64 bit support: CNS Sever now supports native 64-bit installations.
o Simplifies deployment and improves performance
o Note that if users of CNS Server 1.1 choose to retain existing data (i.e. discovered devices,
historical performance, etc.) a manual migration procedure is available below. Future releases of
CNS Server will provide automatic migration of this database.
o Starting with the CNS Server 1.2 (official release), 32-bit installations will no longer be
supported.
• HTTPS: The CNS Server can now use HTTPS for improved security.
• ePMP 2.0 Support: Full support for the 2.0 firmware. Firmware greater than 2.0 will also be supported, but
new features introduced after 2.0 will not be available.
• Cambium Networks Device (CND) support file imports: Import device updates without having to do a
complete installation of the CNS Server.
For additional information on the features please review the CNS Server Quick Start Guide as well as the
documentation available from the CNS Server user interface.
Supported Devices
The table below shows the devices and software versions supported for this release.
Device Version
ePMP AP/STA 2.0 or greater. Note: The Configuration feature requires that the
ePMP devices be running version 2.0 software or greater to work
properly.
4
CAMBIUM NETWORKS
CMM 3 3.0
CMM 4 4.0
Other versions of the devices listed above may be supported, however certain functionality may not be available, or
they will be discovered as generic devices.
Any device not listed in the table above will be discovered as a generic device provided that:
For devices discovered as generic devices, management capabilities are limited to the Monitor application. The
device will be periodically polled for reachability, the traps defined by RFC 1215 will be interpreted, and the interface
table will be polled for key statistics. Software upgrade and device configuration are not supported for non-ePMP
devices.
Client/Server Requirements
Refer to the CNS Server 1.2 Quick Start Guide for details on the client and server requirements as well as
recommendations for deployment/security setup and configuration. The quick start guide is available at
https://support.cambiussmnetworks.com/files/cnss.
Installation
Important – the CNS Server must be installed using a login with either Administrator or root level
permissions. When installing on Linux systems, either login as root, or use sudo when executing the
installer.
5
CAMBIUM NETWORKS
3. STOP: On the new (or existing) 64 bit server, follow the steps in the “Installing CNS Server 1.2” section
below before moving on to step 4.
4. After installing CNS Server 1.2, stop the CNS Server Service as follows:
a. Linux: service cnsserver stop (run service cnsserver status to verify the service is
down)
b. Windows: sc stop cnsserver (run sc query cnsserver to verify it is down)
5. Restore the database
a. Copy the cns_db_backup.sql file from step 1 above to <server install directory>/backups.
b. Open a command shell and change to <server install directory>/scripts.
c. Drop and create a fresh database by running the following scripts from the command shell:
i. Linux
1. drop_database.sh
2. create_database.sh
ii. Windows
1. drop_database.bat
2. create_database.bat
d. In the command shell, change to <server install directory>/stack/posgresql/bin.
e. Run the following command to import the old data: psql –username=postgres --
dbname=cnss < “<server install directory>/backups/cnss_db_backup.sql”
f. Change to <server install directory>/scripts.
g. Migrate the data by running the following scripts:
i. Linux: migrate_database.sh
ii. Windows: migrate_database.bat
6. IMPORTANT: If HTTP (not HTTPS) was selected during the install, prior to starting the server go to the
Admin page and update the HTTP Mode, HTTP Port, and HTTPS Port to the values specified during initial
installation.
7. Start the CNS Server Service using the following commands:
a. Linux: service cnsserver start (run service cnsserver status to verify it is
operational)
b. Windows: sc start cnsserver (run sc query cnsserver to verify it is operational)
On Windows:
• sc query wappstackApache
6
CAMBIUM NETWORKS
• sc query wappstackPostgreSQL
• sc query cnsserver
If the service is not running it can be started by typing the following commands:
On Linux:
On Windows:
• sc start wappstackApache
• sc start wappstackPostgreSQL
• sc start cnsserver
How can I view the active/inactive software versions, or the GPS firmware version, of all the “GPS Sync
Radios” in the network ?
In CNS Server Upgrade, click on the left-side menu “Reports”. Then select the report with the title “Devices with
Active/Inactive Software Versions”. Click the right-mouse button and select “Launch Report”. A report will be
generated in a new browser with each GPS Sync radio and its IP, MAC, device name, Active/Inactive software and
GPS firmware version and hardware type.
If CNS Server is deployed behind a NAT, are there any additional parameters that must be configured in
CNS Server ?
Yes, please configure this parameter: “ADMINGENERAL “Device Accessible IP Address””.
If CNS Server is deployed behind a NAT, this parameter ensures that ePMP upgrades and configuration changes
are successful since the devices are explicitly instructed to download the files from the CNS Server.
In CNS Server, the ePMP device names in the Inventory list all show up as “CambiumNetworks”. How can I
make sure they each have a unique name ?
The “Device Name” in CNS Server is derived from the following fields on ePMP devices.
7
CAMBIUM NETWORKS
This assumes that ePMP ver 2.0 (or later) and CNS Server 1.2 (or later) are used.
ID Summary
21726 [Monitor]WAN Packets Dropped for STA device is showing 200% value
21724 [Monitor] View device toolbar button in inventory view not working.
21654 [Adviser] Fault Dashboard's right click menu does not work
21629 [Performance] - Map response is sluggish for 800 and more devices
21622 [Performance] - Client's response time is significantly high for 2500 devices
21611 [Adviser] Not all legend colors viewable for proxy poll charts in Probes page
21528 [Installer] Even when CNSS backend server fails to start, CNSS server is shown as running
Known Issues
The following issues are currently open and will be addressed in a subsequent release.
Id Summary
CNS-1811 [Migration]View Configuration is not populating Name, device type, version fields
CNS-1803 Verify credential of generic device is showing green color for any login/password
CNS-1758 [Performance] cnsserver service takes unusually higher time to stop on Linux
8
CAMBIUM NETWORKS
CNS-1653 [Monitor] Conflict between configuring lat/lon and using drag and drop.
CNS-1516 [Provision]After configuring Community String, Configuration status does not show Success message
[Generic] PostgreSQL server failed to stop while running manager-Linux.run script and clicking Stop All
CNS-1377
button.
CNS-1278 [General] Do not open a RMI port for the Java backend
CNS-1014 [Monitor] [Fault dashboard] Filter not working for events listed in pie-charts and bar graphs.
CNS-751 [Discover] Log file names and events still use the name Finder.logs instead of Discover
CNS-736 [Customer Found, Installer] Bitnami fails to install on Windows Server 2008 R2 standard SP1