Wm4 0 quickstartguideissue1

Cambium
Wireless
Manager

Quick Start
Guide
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 About this Guide............................................................................................ 5
2 Wireless Manager (WM) Requirements .............................................................. 7
2.1 Hardware Requirements................................................................................................. 7
2.1.1 Server Requirements............................................................................................................... 7
2.1.2 Client Requirements................................................................................................................ 7
2.2 Server Operating System Requirements ........................................................................ 8
2.3 Firewall Considerations................................................................................................... 8
2.4 Linux‐specific installation instructions............................................................................ 9
2.5 Installing WM with Prizm on the same server.............................................................. 10
2.6 Client Requirements ..................................................................................................... 10
3 WM Installation.............................................................................................11
3.1 Licensing........................................................................................................................ 11
3.2 Upgrading...................................................................................................................... 11
3.2.1 Upgrading from a previous version of Wireless Manager .................................................... 11
3.2.2 Upgrading from Prizm ........................................................................................................... 11
3.3 Linux.............................................................................................................................. 12
3.4 Windows ....................................................................................................................... 12
3.5 Installation screens ....................................................................................................... 13
3.6 Service Packs................................................................................................................. 17
4 BAM Installation............................................................................................19
4.1 ODBC Installation .......................................................................................................... 19
4.2 Prizm/BAM Download and Install................................................................................. 19
4.3 BAM Documentation .................................................................................................... 26
5 Post Installation.............................................................................................27
5.1 Configuring the Proxy on a WM Client ......................................................................... 27
5.2 Set Proxy Information in the Java Control Panel .......................................................... 27
5.3 Set the Proxy Information in the Web Browser ........................................................... 30
5.4 Unable to launch the application Error ........................................................................ 31

6 Starting and Stopping the WM Service .............................................................33
7 Starting the WM Client...................................................................................35
8 Device Discovery ..........................................................................................39
8.1 Discovery Example ........................................................................................................ 39
8.2 Monitoring the Discovery Process................................................................................ 41
8.3 Discovery Troubleshooting ........................................................................................... 42
9 Physical Map.................................................................................................43
9.1 Placing Devices on the Physical Map............................................................................ 43
9.2 Physical Map Troubleshooting...................................................................................... 44
Resources for Support ..........................................................................................45
Community Forum .................................................................................................................... 45
Technical Support ..................................................................................................................... 46

WM Release 4.0 Quick Start Guide Issue 1
May 2012

1 About this Guide
This document is intended for Wireless Manager users as they
 prepare a computer and operating system for WM install.
 install or upgrade WM.
 set up any necessary proxy information.
 discover devices on the network.
 use WM basic functions for the first time.
This is a supplement to the Wireless Manager user guide and Wireless Manager server administration
guide, which provide more information. The goal of this quick start guide is to get a user up and
running quickly, by providing step‐by‐step instructions that apply to most situations. The How‐to‐
License Guide provides information on the license process and upgrade procedures. The WM 4.0 FAQ
addresses common questions that include the upgrade paths. All of these documents can be found at
http://www.cambiumnetworks.com/support/planning/index.php?cat=1&type=0.

5

May 2012

2 Wireless Manager (WM) Requirements
Wireless Manager is a client‐server application that uses a java thick‐client connection. The WM
Server should be located on a part of the network that can connect to the hardware devices to be
managed and monitored. The WM client also requires a network connection to the WM server.
The Physical Map overlays network elements onto a embedded Google map. This allows you to
visualize and analyze a wide range of crucial information including connectivity between nodes, link
quality, range, and device and network availability. Graphical representations of data help you quickly
determine network status, identify problems, and determine the severity of impact on the network
and end users. In this map‐based view, you can scale and pan to view an entire city or a specific area.
Intuitive, context‐sensitive bubbles appear over the map and give quick access to key management
functions. If the Physical Map feature is to be used, then the WM client requires an Internet
connection.

2.1 Hardware Requirements

2.1.1 Server Requirements
Server class hardware, as opposed to desktop hardware, is recommended.
 the following minimum server requirements:
− 4 GB RAM
− Dual‐core processor, at least 2 GHz
− RAID 1 storage
 the following large server requirements (for more than 100 nodes):
− 8 GB RAM
− Quad‐core processor, at least 2 GHz
− RAID 5 Storage, at least 10,000‐rpm drives
 an uninterruptible power supply
If the server is shut down abruptly (loss of power), it can result in corruption of the database.
This can have a catastrophic effect on Wireless Manager. A UPS is highly recommended,
along with a scheme to shut the server down gracefully during a power outage.

2.1.2 Client Requirements
Any modern desktop or laptop hardware that can run a web browser and Java 1.6 should be able to
run the WM client. The only officially supported operating systems for the WM client are Windows XP
and Linux. The client does not support MacOS.

7

Issue 1 WM Release 4.0 Quick Start Guide
May 2012

2.2 Server Operating System Requirements
The following operating systems are supported:
 Windows Server 2008 R2 or Windows Server 2008 SP 2 (Standard, Enterprise, or Datacenter)
 Red Hat Enterprise Linux 5.x 32‐bit (not 64‐bit) ES (not AS) or CentOS 5.x 32‐bit (not 64‐bit)
note ............. a graphical user interface environment is required for installation of Wireless Manager.

Can I use a different version of Red Hat Enterprise Linux, or Linux from a different company?
This is not supported. Wireless Manager requires specific versions of libraries to be located in certain
places. Cambium Technical Support cannot help a user customize an OS to meet the requirements.

How many devices can Wireless Manager support?
Wireless Manager supports up to 10,000 devices. The total number of devices supported will vary
with the following:
 types of devices being monitored.
 speed of the network between the WM Server and the devices being monitored
 polling frequency
 speed of the WM server hardware

2.3 Firewall Considerations
In order for the WM server to be able to communicate with both the managed devices and the WM
client, certain network ports must be open for inbound traffic. If a firewall is being used for the WM
server, the following ports must be opened.
 Port 6900/tcp inbound is required for correct use of the TFTP connection by the firmware
upgrade process.
 Port 9090/tcp inbound is used to access the initial web page on the WM Server.
 Port 161/udp inbound is used by the Northbound Interface (NBI).
There are two tcp ports (NMS FE Secondary and NMS Socket) required for communication between
the WM server and WM client. As shipped, the WM server uses random port numbers. Alternatively,
these two ports can be specified in order to be used with a firewall. A free port number must be
assigned to each. Any free tcp ports can be used. In the following example, Port 33100 is assigned for
NMS FE Secondary, and Port 32900 is assigned for NMS Socket.
The following steps describe how to specify these ports, which must be done only after WM has been
installed:
1. Stop the server. (See Starting and Stopping the WM Service on Page 33.)
2. Locate the serverparameters.conf file in the conf directory. After a standard
installation, this file is located at
◦ /usr/local/cambium/wm/server/conf/ in Linux.
◦ C:CambiumWMserverconf in Windows.

8

May 2012

3. At the bottom of serverparameters.conf, add the following text:
1
NMS_FE_SECONDARY_PORT 33100
4. Locate the transportProvider.conf file in the conf directory. After a standard
installation, this file is located at
◦ /usr/local/cambium/wm/server/conf/ in Linux.
◦ C:CambiumWMserverconf in Windows.
5. Edit the transportProvider.conf and locate the tag <PORT_TO_LISTEN>.
6. Replace the value 0 with the port of your choice, as demonstrated in red below.

<?xml version="1.0" encoding="ISO-8859-1"?>
<TRANSPORT>
<PROTOCOL
NAME = "TCP"
SERVER_CLASS_NAME = “com.adventnet.management.transport.TcpServerTransportImpl"
CLIENT_CLASS_NAME = "com.adventnet.management.transport.TcpClientTransportImpl" >
<PORT_TO_LISTEN> 32900 </PORT_TO_LISTEN>
<SERVER_BACK_LOG> 300 </SERVER_BACK_LOG>

7. Start the server. (See Starting and Stopping the WM Service on Page 33.)

2.4 Linux-specific installation instructions
If a new OS installation will be performed for the WM server, here are instructions that will help
configure the OS for WM:
1. Disable the firewall and SE Linux.
2. Install the following software packages:
◦ the basic default packages from Red Hat
◦ Mozilla for graphical Internet access
note ............. The recommendations listed above are based on configurations that Cambium has tested.
Any configurations that differ from these, such as additional loaded packages, may not
work.

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.
note ............. It is not necessary to install Apache, MySQL, or Java during the OS installation. These are
automatically installed as part of the WM installation process.

1
Any tcp port number can be used for this.

9

May 2012

2.5 Installing WM with Prizm on the same server
Wireless Manager does not support co‐installation with Prizm EMS. However, Prizm in BAM‐only
mode co‐installation is supported. See the BAM Installation on Page 19.

2.6 Client Requirements
The WM client requires the following:
 JRE 1.6 or greater
 Mozilla version 2 or 3, or Internet Explorer version 6, 7, or 8
 Windows XP, Windows Vista Business, Windows 7, or Red Hat Enterprise Linux. Other
versions of Windows and Linux can be attempted, but are not supported. MacOS is not
supported.

10

May 2012

3 WM Installation
Except for Upgrading on Page 11, these instructions assume a fresh WM installation.

3.1 Licensing
Obtain your license prior to installation of the software. See the How‐to‐License guide, available at
Obtain your license prior to installation of the software.

3.2 Upgrading
There are certain upgrade paths both from previous versions of Wireless Manager. These are
explained in the Cambium Wireless Manager Server Administration Guide for Release 4.0. For an
upgrade from Prizm, see the Prizm‐to‐Wireless Manager Migration Guide (Prizm Release 3.3 to WM
Release 4.0).

3.2.1 Upgrading from a previous version of Wireless Manager
Wireless Manager Release 3.0 with Service Pack 3 is required to upgrade to Release 4.0. Service Packs
are available at http://www.cambiumnetworks.com/support/planning/index.php?cat=1&type=1.
important ........... Do not uninstall Wireless Manager 3.0 on your server. Instead, apply Service Pack 3
and allow the Wireless Manager 4.0 installation tool to detect Release 3.0 and
upgrade WM. This ensures a seamless transition. If you uninstall the older version,
the database will need to be destroyed, and you will lose all previous data and risk
corruption of the InstallAnywhere Registry file. The upgrade process and its inherent
uninstallation of the previous release are the purview of the administration guide.

3.2.2 Upgrading from Prizm
There is not a direct upgrade path from Prizm to Wireless Manager. They are completely different
platforms.
Prizm in BAM‐only mode can run concurrently with WM 4.0 on the same server, however Prizm EMS
cannot. If you wish to install WM Release 4.0 on a Prizm server, first put the server in BAM‐only mode
using Prizm’s License Manager.
A migration tool is provided to assist in exporting data from Prizm and importing that data into
Wireless Manager. See the Prizm‐to‐Wireless Manager Migration Guide at

11

May 2012

3.3 Linux
A few items must be set regarding the hostname prior to install. The procedure depends on whether
your system is using a static IP address or an address from a DHCP Server. If you are not sure which
your system is using, consult your network administrator.
 For static IP systems, the /etc/hosts file must be edited prior to WM installation. The goal
is to remove the hostname from the loopback (127.0.0.1) and to assign a unique hostname
for each network card or IP address. The hostnames can be whatever you like.
1. In /etc/hosts, set 127.0.0.1 localhost.localdomain localhost.
2. Substitute the IP address of each card, and choose a hostname, according to the
following examples:
[ip_address_of_card] [hostname_of_your_choice]
[ip_address_of_card2] [hostname_of_your_choice2]
3. Save and close the file /etc/hosts.
4. Reboot the server.
 For DHCP systems:
1. In /etc/nsswitch.conf, find the hosts: line.
2. Move files to the end of the list on that line.
Example: hosts: dns files
3. Save and close the file /etc/nsswitch.conf.
4. Reboot the server.
Then launch the installation tool as follows:
1. Move the installation tool file WM_Installer_*.bin to the /usr/local directory.
2. Right‐click on the desktop.
3. Select Open Terminal to launch a new terminal shell.
4. Use the md5 file to verify that the installation tool file has not encountered damage.
5. Execute the following commands:
cd /usr/local
/usr/local/WM_Installer_*.bin

3.4 Windows
No special hostname procedures are needed under Windows. Launch the installation tool as follows:
1. Move the installation tool file WM_Installer_*.exe to the C: folder.
2. From the Desktop menu, select StartRun.
3. In the C: folder, double‐click on the md5 file to verify that the installation tool file has not
encountered damage.
4. In the C: folder, double‐click on the WM_Installer_*.exe file.

12

May 2012

3.5 Installation screens

Click Next.

Accept the License Agreement and click Next.

13

May 2012

All three of these components are required. If you are upgrading from WM Release 3.0, uncheck
MySQL Database.
If you are using Windows, you will now have the opportunity to define the path for the installation.
The rest of this document assumes the default path C:CambiumWM for Windows and
/usr/local/cambium/wm for Linux.

You may either accept he defaults for database access or enter your own. If you change these, make
note of your changes. They will be required for access to the database.

14

May 2012

You may either accept the default read‐only username and password or customize them.

Check the installation information, then click Install. The Wireless Manager installation will finish.

15

May 2012

If this is a new installation, the License Manager and the Server Administration Tool will now be
installed. If the Server Administration Tool was previously installed, it will remain as is. In any case,
this pop‐up will appear at the end. Click Yes.

The installation is complete. Click Done.
The Server Administration Tool opens and includes License Manager configuration and the ability to
start the server. You must apply your license before the server can start.

16

May 2012

In the WM Administrator Tool, perform the following steps:
1. In the left panel, select Licensing.
2. Click the Upload License button.
3. Browse to your license file or files. (See Licensing on Page 11 for more information.)
4. Upon successful installation of the license file, select WM Server in the left panel.
5. Click Start WM Server.
note ............. both the Apache Service and the WM Service should show as Started.

WM installation is complete, license is loaded, and the service is started. The server is ready for a WM
client to connect.

3.6 Service Packs
Navigate to http://www.cambiumnetworks.com/support/planning/index.php?cat=1&type=1 and
check for any available service packs to apply. Apply them after the server has been given an
opportunity to start up and initialize everything.

17

May 2012

4 BAM Installation
If the WM/BAM combination package was purchased, the BAM portion should be installed after WM
has been installed and licensed. For BAM functionality, the Prizm software is used in BAM‐only mode.
If BAM was not purchased, proceed to Post Installation on Page 27.

4.1 ODBC Installation
The MySQL ODBC Driver must be installed before the Prizm installation. This driver is not provided
with the installation, but is available at http://dev.mysql.com/downloads/connector/odbc/3.51.html.
Follow the instructions to obtain either the Linux or Windows version of the ODBC Driver and install
it.

4.2 Prizm/BAM Download and Install
Prizm can be downloaded from
http://www.cambiumnetworks.com/support/planning/index.php?cat=2&type=1. The file to
download is “Prizm 3.3.10 Installer for Linux (or Windows)”. Be sure to choose the correct platform
for your server, Linux or Windows.
Run the file on your server.

Click Next.

19

May 2012

This dialog will be shown for only Windows installations. If Wireless Manager was installed on this
server, this package has already been installed. The second option can be selected. This package will
show up in Add/Remove Programs as Microsoft Visual C++ 2005 Redistributable.
Click Next.

Read and accept the License Agreement, then click Next.

20

May 2012

Select only Prizm EMS and User Guides. Do not select the License Manager and PostgreSQL Database
options.
Click Next.

Inspect the Pre‐Installation Summary, then click Install.

21

May 2012

This screen may appear. Selection should be your preference, based on local operations.

Select Yes to run the Server Admin tool after installation.

22

May 2012

The installation is complete. Click Done.
The Prizm Server Admin Tool will run. The following steps illustrate the method of configuring Prizm
to run in BAM‐only mode and to use the infrastructure provided by Wireless Manager.
For Server Mode, select BAM Only as illustrated.

23

May 2012

Select Database from the column on the left.

Select MySQL as the Database Type.
Use the ODBC Driver pull‐down menu and select the driver installed earlier.
Create a user and database for Prizm in the existing MySQL installation.
MySQL will need to be used from the command line.

Linux: run /usr/bin/mysql –user=root -p
Windows: run c:MySQL Server 5.0binmysql –user=root –p
The system will prompt for the MySQL root password. The default password is public.

24

May 2012

Create the Prizm database via create database prizm; as shown.
Verify the current database list via show databases;

Create the user expected by Prizm.
Grant the user access to the Prizm database as follows:
GRANT ALL on prizm.* to 'bost_user'@localhost IDENTIFIED BY 'bost_user';

The database and user have now been created. Use quit; to close mysql.

The JDBC driver must be loaded. These drivers are included in the Wireless Manager install.
Click Browse and navigate to the following location:
Windows:  C:CambiumWMservermysqldriver
Linux:   /usr/local/cambium/wm/server/mysql/driver

Click the Test button to verify the connection to the MySQL database. If the connection is
unsuccessful, ensure that the database, user, and password created match those that were expected
by Prizm.

25

May 2012

4.3 BAM Documentation
Documentation for Prizm/BAM is provided as the "Using the Bandwidth and Authentication Manager
(BAM) Subsystem" section of the WM user guide.

26

May 2012

5 Post Installation
5.1 Configuring the Proxy on a WM Client
If the WM client does not need a proxy server to reach the Internet, this section may be skipped
entirely.
If a Proxy Server is used to access the Internet, there are a few issues that must be addressed before
both the Physical Map and client/server connection will operate properly. Two possibilities exist:
 Case 1 where the client and server are on separate machines
 Case 2, where server and client are on the same machine
Directly after installation, most users will be under Case 2, as they will want to try to run the client on
the same machine as the server. This means that all these instructions must be followed, as the
machine is performing both client and server duties.

If a proxy is needed for Internet connectivity, this information must be entered in both the Java
Control Panel and the web browser.

5.2 Set Proxy Information in the Java Control Panel
Launch the Java Control Panel:
Windows ‐ StartSettingsControl PanelJava
Linux ‐ /usr/local/cambium/wm/jre/bin/jcontrol

27

May 2012

Click Network Settings from the General
tab.

Select Use proxy server and enter your
proxy information (what is shown is only
an example).
Often, you will need to specify that the
proxy not be used for local addresses, of
which the WM Server might be.
Check Bypass proxy server for local
addresses, then click Advanced.

28

May 2012

Enter the IP address or IP mask that will
match the address(es) on your server.
Your network administrator will be able to
help you with this.
Remember this must be followed for each
client machine where a proxy will be used.






29

May 2012

5.3 Set the Proxy Information in the Web Browser

When a Proxy Server is used, an
exception is usually specified so
that the WM Server can be
reached. The following example
explains how to do this in Mozilla
Firefox 3 in Windows. Other web
browsers will also have a facility
for this; your network
administrator should be able to
help with this setup.
In Firefox, select ToolsOptions.
Select the Network tab and click
Settings in the Connection section.

The HTTP Proxy information would
most likely already exist here. If it
does not, it would need to be
added, otherwise the web
browser would not be able to
reach the Internet.
At No Proxy for:, enter the IP
address or IP Mask that matches
the server IP. This will be the same
information as was entered in the
Java Control Panel, however the
format might be slightly different.
In this example, we used
10.0.0.0/8, which means the
computer will look not look to the
Proxy for any IP address matching
10.x.x.x.
Different web browsers will have a
similar method for adding
exceptions, but it might look
slightly different.

30

May 2012

5.4 Unable to launch the application Error

You will also receive this error if any of
the proxy information (Java or web
browser) is incorrect. See the Configuring
the Proxy on a WM Client on Page 27.
If you have already configured the proxy
information, you might need to flush
Java’s file cache, so the new file can be

loaded.

From the Java Control Panel, select
Settings from the Temporary Internet
Files section.

31

May 2012

Click Delete Files, and delete both
Applications and Applets and Trace and
Log Files.
Click OK.
Try to launch the Web Start Client again.

32

May 2012

6 Starting and Stopping the WM Service
The proper method of starting and stopping the WM Service differs depending on the operating
system. This section refers to the service that is running on the server, not the client application.
 Linux, from the command line of the server:
− service wmserver start will start the server
− service wmserver stop will stop the server
− service wmserver restart will stop, then start the server
− service wmserver status will return the current server status
 Windows, from the command line of the server:
− net start wmserver will start the server
− net stop wmserver will stop the server
Alternatively, you can use Window’s GUI:
Control PanelAdministrative ToolsServices. The service name is wmserver.

33

May 2012

7 Starting the WM Client
After any necessary post‐installation tasks are completed, and the WM Service is started, the client
can be launched. Ensure the client computer meets the requirements as outlined under Client
Requirements on Page 7.
1. From the client, launch a web browser.
2. Find the IP address of the WM Server.
3. Type and open this URL in the web browser:
http://WMServerIPAddress:9090.

4. If you do not see a page as pictured above, ensure that the WM Server is running, that the IP
address is correct, and that you have followed the information in Configuring the Proxy on a
WM Client on Page 27.
5. Click the Web Start Client button. Depending on your browser, the next dialog box might
look slightly different. The goal is to open the WebNMS.jnlp file with Java. In the case
below, click OK.

35

May 2012

 If the option to open with Java is not available, ensure you have installed Java as noted
under Client Requirements on Page 7.
 If you see the following error dialog, this indicates that exceptions were not set correctly on
the web browser’s proxy, or the Java cache must be purged. See Unable to launch the
application Error on Page 31.

If all is well, the WM client authentication dialog should appear. Enter the User ID and Password as
shown below , then click Connect.

The default User ID is root and the associated Password is public.
Upon successful authentication, the WM client opens.

36

May 2012

37

May 2012

8 Device Discovery
Upon initial launch of the WM Client, the Inventory will be empty. You now need to use Discovery to
find and add your devices to WM. Here is what is needed for this process:
 You must know the IP addresses of the devices, or on which subnet(s) the devices reside.
 The devices must be reachable from the WM Server. Otherwise, no communication can take
place.
 You must know the SNMP port, community, and any authentication information
(if necessary) for the devices. WM supports SNMP v1, v2c, and v3.
The following information is used in the Discovery example:
 device IP = 10.24.1.1
 SNMP info
− version = SNMP v1
− Community string = pubic
− Port = 161

8.1 Discovery Example

From the main menu, select ToolsDiscovery
Configurator.

On the General tab, check these boxes:
 AutoDiscovery
 Rediscovery Already Discovered
 Enable Log

39

May 2012

Select the Node
Discovery tab. For
this example, we
only discover a
single node as a
test.
Enter the
IP Address,
SNMP Version, and
SNMPAgentPort
that corresponds to
a device on your
network.

Click Add.
The information you
entered should
appear in the table
at the top of the In the above example, a single IP has been submitted for Discovery. The Network Discovery
dialog box. tab works the same way; however, with this method an entire IP subnet can be scanned at
Click Apply.
one time. For a large group of devices that all reside on the same subnet, use Network
Discovery, e.g. 10.24.1.x.

40

May 2012

8.2 Monitoring the Discovery Process
After applying a new Discovery set, the results can be monitored elsewhere in WM. This continues
from the example above.

From the left‐side
tree, expand
Inventory and
select Networks.

The Networks
window will show
all Discoveries
that have been
submitted and
their current
status.

Right‐click on a
line to reveal
options for that
Discovery
(Stop Discovery
or Start
Discovery).
Delete Object
and Traces will
delete that
Discovery.

To watch the
results of the
Discovery
process, expand
Fault
Management
from the left‐side
tree, and select
Discovery Events.

41

May 2012

In this example the node at 10.24.1.1 was successfully discovered, and then went into “Clear” status.

8.3 Discovery Troubleshooting
If a Discovery is not successful, perform the following checks:
 Confirm that the device exists.
 Confirm that it is reachable from the WM Server.
Devices must be reachable via the network from the WM server. Being reachable from the
WM client is irrelevant. From the WM server, try to ping the device’s IP address or pull up its
web page, if applicable.
 Verify that the following SNMP credentials used were correct:
− SNMP version
− SNMP port
− SNMP community string (case‐sensitive)
− in SNMP v3, all the security credentials.
 Check the Discovery logs.
Looking at the Discovery logs can be very helpful in determining what is happening on the
server. The logs provide much more information than is given in the WM client GUI. Look for
the latest discoverylogs*.txt file at
Linux ‐ /usr/local/cambium/wm/server/logs
Windows – C:CambiumWMserverlogs

42

May 2012

9 Physical Map
Wireless Manager has a Physical Map module that allows operators to place their devices with
respect to real‐world location, visualize the devices geographically, and see the consequences of
problems. For the Physical Map to operate, the WM Client must have an Internet connection with
correct proxy settings, if applicable. See Configuring the Proxy on a WM Client on Page 27.

9.1 Placing Devices on the Physical Map
There are a few methods of placing devices on the physical map.
 Individual devices can be manually placed. From the Inventory screen, right‐click on a device
and select Set Location in Physical Map. The device will appear in the Physical Map and a
variety of options will be presented, including click and drag, address search, and
latitude/longitude entry.
 PMP devices will be placed on the Physical Map automatically after Discovery if the Latitude,
Longitude, and Altitude fields are already populated with valid data in the correct format.
Latitude and Longitude are in decimal degrees, with Southern and Western Hemispheres as
negative numbers. For example, New York City would be represented as:
Latitude: 40.756
Longitude: ‐73.986
The Altitude field is interpreted as the device height above terrain, in meters.
 Devices can be placed on the Physical Map by creating a geo‐location file and importing it.
This will work for any set of devices.
The format for the geo‐location file is a comma‐delimited text file as follows:
Version: <version>
Create Date: <mm/dd/yy>
Name(ID), latitude, longitude, height, description (optional)
Name(ID), latitude, longitude, height, description (optional)
[etc]
note ............. The 2-line header must be present in the file.

The Name(ID) column must correspond to the values as they appear in the device’s Name(ID) column
in the Inventory.

43

May 2012

To place these items, a geo‐location file would look like this:
Version: 1
Create Date: 01/24/09
02 05 12 10 09 40, 30.27715,-97.69645,8
02 05 12 10 42 f1, 30.26291,-97.74009,10
02 05 12 10 43 b4, 30.27248,-97.73625,20

Alternatively, colons can be used as the delimiter instead of spaces for the MAC address:
Version: 1
Create Date: 01/24/09
02:05:12:10:09:40, 30.27715,-97.69645,8

After the location file is created, import it via ToolsPhysical MapGeo‐location Import (CSV).

9.2 Physical Map Troubleshooting
If you see the following message in the Physical Map panel, it indicates a failure to connect due to
network problems. Verify your Internet connection and proxy, if applicable. See Configuring the Proxy
on a WM Client on Page 27.

If you see the following message, it means that the system clock is set incorrectly on the server. Be
sure to check time zone as well.

44

May 2012

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.

45

May 2012

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

46

Wm4 0 quickstartguideissue1

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (15)

Andere mochten auch

Andere mochten auch (9)

Ähnlich wie Wm4 0 quickstartguideissue1

Ähnlich wie Wm4 0 quickstartguideissue1 (20)

Mehr von Advantec Distribution

Mehr von Advantec Distribution (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Wm4 0 quickstartguideissue1