1. Prizm-to-WM Migration Guide Issue 3
February 2012
Prizm-to-
Wireless
Manager
Migration Guide
Prizm Release 3.3 to
WM Release 4.0
Issue 3 March 2012
© 2012 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 4.0.
© 2012 Cambium Networks, Inc. All Rights Reserved.

3. Table of Contents
Accuracy...................................................................................................................................... 2
Copyrights ................................................................................................................................... 2
Restrictions ................................................................................................................................. 2
License Agreements.................................................................................................................... 2
1 About Prizm Migration.................................................................................... 5
1.1 Prerequisites for Prizm Migration................................................................................... 5
1.2 Caveats for the Migration............................................................................................... 5
2 Exporting Data From Prizm.............................................................................. 7
3 Importing Prizm Data into WM .......................................................................11
Resources for Support ..........................................................................................13
Community Forum .................................................................................................................... 13
Technical Support ..................................................................................................................... 14

4. List of Figures
Figure 1: Step 1 dialog................................................................................................................................... 8
Figure 2: Step 2 dialog................................................................................................................................... 9
List of Procedures
Procedure 1: To generate the export files .................................................................................................... 7
Procedure 2: To import the data exported from Prizm .............................................................................. 11

5. Prizm-to-WM Migration Guide Issue 3
March 2012
1 About Prizm Migration
This guide supports operators who manage their networks with Prizm, want to now manage them
with Wireless Manager (WM), but want WM to reuse as much information as possible about
 the elements and their management access and history.
 the names of users and how they authenticate into the management system.
 the configurations that the BAM subsystem forces on the elements.
 customer contact information with its correlation to the individual elements.
Technical support for your migration is available through the sources described under Resources for
Support on Page 13.
1.1 Prerequisites for Prizm Migration
Successful migration of the data listed above requires the following conditions:
 Currently successful operation of Prizm Release 3.2 or 3.3
 Populated Prizm database in one of the following vendor versions:
− MySQL Server in Version 4.1.201 or 5.0 in a Prizm‐supported platform of Linux or
Windows
− PostgreSQL in Version 8.2 in a Prizm‐supported platform of Linux or Windows
− Microsoft SQL Server 2000 Enterprise Edition in a Prizm supported platform of Windows
 Migration tool
− specific to the OS on the Prizm server device
− downloaded from the Motorola web page
 Successfully installed instance of WM Release 3.0 as the target for the migrated data.
1.2 Caveats for the Migration
Notably not part of the migrated data are the following items from a Prizm deployment:
 licenses
− to use Prizm and/or its BAM subsystem
− to manage elements
 information that Prizm uses and WM requires for proper interaction with the BAM
subsystem
 configuration templates that Prizm pushes to its elements
 element account states (activated or suspended)
 element names, locations, and their contact (staff) information
 permissions as they relate in Prizm to the types of activities that Prizm allows per user
 how views have been filtered
 logs of operations and management error conditions.
5

7. Prizm-to-WM Migration Guide Issue 3
March 2012
2 Exporting Data From Prizm
The migration tool that Motorola provides launches and properly formats all of the exports that full
migration 1 to WM requires.
Procedure 1: To generate the export files
1. Download the migration tool (the one appropriate for the OS of the device on which Prizm
operates, either PrizmMigrationToolWindows.zip or
PrizmMigrationToolLinux.zip) and its associated MD5 validation file from
http://www.cambiumnetworks.com/support/planning/index.php?cat=1&type=1.
2. Run the MD5 validation (for example, in the checksum calculator that the Network Updater
tool provides in its Release 4.0 or later) to ensure that the migration tool was not corrupted
during its download.
3. If necessary, make the tool file executable.
4. With Prizm running in normal operation, use its GUI to ensure that
◦ all elements are discovered.
◦ connectivity issues for all of those elements are resolved.
◦ the desired elements are brought into networks.
◦ the elements that you do not want WM to manage are sent to the Ignored Elements list.
◦ the BAM subsystem, if deployed, operates as expected and succeeds.
◦ the logs suggest no management error conditions.
5. Open the PrizmEMS Administrator Tool.
6. From its main menu, select ActionWeb ServerStop.
7. Select ActionPrizmEMS ServerStop.
8. Select ActionLicense ManagerStop License Manager.
9. Close the PrizmEMS Administrator Tool interface.
10. Execute the downloaded migration tool.
The tool interface opens to its Step 1 interface screen.
1
as defined in About Prizm Migration on Page 5 and its sections.
7

8. Issue 3 Prizm-to-WM Migration Guide
March 2012
Figure 1: Step 1 dialog
11. For Server Location, browse ( ) to and select the path on the file system to the
...CanopyPrizm folder or .../canopy/prizm directory.
12. Enter values for the NBI Details block, consistent with your local configuration.
13. Leave the values of the Database Details block fields in the Step 1 dialog as the tool
automatically populated them.
14. Click the Next button.
The tool makes proper connection to Prizm and its database, and then opens the Step 2
interface screen.
8

9. Prizm-to-WM Migration Guide Issue 3
March 2012
Figure 2: Step 2 dialog
15. Based on your experience in checking Prizm operations (in Step 4 of this procedure),
uncheck any of the following Export Operation check boxes to suppress the export of any
type of information that is known to be incomplete or incorrectly configured:
◦ User account information
◦ Device discovery information
◦ Performance Data
◦ Customer Data
16. If BAM is not licensed for your Prizm deployment or if your experience in checking BAM
operations (in Step 4 of this procedure) indicated problems pushing VLAN and/or bandwidth
values, uncheck as appropriate the following Export Operation check boxes to suppress the
attempted export of any type of these templates:
◦ VLAN profiles
◦ Bandwidth service plans
17. Optionally, either
◦ browse ( ) to and specify and alternative path and directory to receive the exported
files.
◦ leave specified the directory that the Export Location field displays as the default
repository.
18. Click the Next button.
The tool opens a window that displays the results of the export operations.
9

11. Prizm-to-WM Migration Guide Issue 3
March 2012
3 Importing Prizm Data into WM
The exported data has the following uses for your operations in WM.
Export Operation Format Usefulness for WM Operations
User account
CSV To import directly into WM for all security management purposes.
information
Device discovery
CSV To import directly into WM for use in the Discovery Configurator.
information
To import directly into WM for use as configuration templates whose values WM can
VLAN profiles
push to devices via SNMP. This differs in both protocol and practice from how BAM
XML applies these profiles, which does not require device reboot and takes immediate
Bandwidth service effect. Also by contrast, when the templates instead of BAM profiles are applied, the
plans results are available in configuration reports.
To import into a relational database (spreadsheet) file and keep for reference and
Performance Data CSV
comparison against performance data that WM will generate for the devices.
To import directly into WM for use in any of the customer contact features that WM
Customer Data CSV
Release 3.0 includes and any future release will introduce.
To become generally familiar with the WM data file import feature, see the user guide section titled
"Importing Data Files Into WM." WM provides a separately selectable operation to launch the import
of each file type, and the user guide describes the import of each exported file type in a separate
section. References to these sections are included in Procedure 2 below. To import all but the
performance (historical) data, perform the following steps.
Procedure 2: To import the data exported from Prizm
1. From the Prizm server device, transfer the contents of the repository directory to within
network (file browser) reach of the WM client application that will be used for the import
operations.
2. To import the user information from Prizm, use the procedure described in the user guide
section titled "Importing User Account Information."
3. To import the device discovery information from Prizm, use the procedure described in the
user guide section titled "Importing Device Discovery Information."
4. To import the VLAN profiles and bandwidth service plans from Prizm as configuration
templates, use the procedure described in the user guide section titled "Importing a
Configuration Template."
note ............. To be able to use the VLAN profiles and bandwidth service plans as BAM profiles,
no import action is required, since the BAM subsystem as launched from the WM
client already stores these as profiles.
5. To import the customer data from Prizm, use the procedure described in the user guide
section titled "Importing a Customer Contact Database."
11

13. Prizm-to-WM Migration Guide Issue 3
March 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.
13

14. Issue 3 Prizm-to-WM Migration Guide
March 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 13.
 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.
14