Motorola Canopy Prizm Release 3.2 Server Setup Guide for Linux Platforms

Transcription

1 Motorola Canopy Prizm Server Setup Guide for Linux Platforms Issue 3 August 2009

2

3 TABLE OF CONTENTS 1 Using This Setup Guide Finding the Information You Need Becoming Familiar with This Setup Guide Searching This Setup Guide Interpreting Typeface and Other Conventions Getting Additional Help Sending Feedback Supported Platforms and Requirements Processor Operating Systems Database Applications Database (JDBC) Drivers ODBC Drivers for BAM Operations in Prizm ODBC Driver Installation for a MySQL Database Runtime Environment Element Loads Setting up the Prizm Server High-level Sequence of Setup Procedures Preparing for the Installations Installing Database Software Setting Up PostgreSQL Setting Up MySQL Setting Up Unidirectional MySQL Database Replication Installing the Prizm Server Installing the Prizm Server and Optional Components with X-Windows Installing the Prizm Server and Optional Components without X-Windows Installing the JDBC Driver(s) Using the Administrator Tool for Prizm Setup Optionally Adding a RADIUS Server... 66

4 4.5.1 Setting Up Prizm for RADIUS Setting Up a RADIUS Server for Prizm Example Setup of FreeRADIUS Version Example Setup of Steel-Belted Radius (SBR) Version Setting Up License Manager Server-based License Management Installing License Manager Finding the hostid (MAC Address) Removing the Inappropriate License Manager License Launching the License Manager Administrator Tool Configuring License Manager on the Licensing Servers Preparing Prizm for Licensing Starting License Manager Configuring and Installing License Files Checking the Status of License Manager and Licenses Setting Server Modes (Redundant Prizm Configuration) Syncing Time Optionally Reconfiguring Prizm Ports Client-Server Communications Server-Element Communications Complete List of Used Ports Performing the Initial Prizm Configuration Configuring Prizm for the Database Configuring Prizm for BAM Optionally Hosting Java VM Expanding the Criteria Field for a PostgreSQL DAtabase Starting the Prizm Server Uninstalling Prizm Obtaining Technical Support Preliminary Steps Technical Support Information Tool Appendix A: Reference Information License Agreement

5 Trademarks Appendix B: History of Documentation

6 LIST OF FIGURES Figure 1: Process for fresh installation Figure 2: Process for License Manager upgrade Figure 3: Contents of my.cnf file for Linux Version 4 and MySQL Server Version Figure 4: Replicated standby MySQL database in typical configuration Figure 5: InstallAnywhere Introduction panel Figure 6: InstallAnywhere License Agreement panel Figure 7: WMS Detected panel Figure 8: Select Prizm Features To Install panel Figure 9: License Manager Options panel Figure 10: PostgreSQL Database Password panel Figure 11: Example Pre-Installation Summary panel Figure 12: Please Wait panel Figure 13: Install Complete panel, success Figure 14: Example Install Complete panel, errors Figure 15: Example portion of installation log for successful installation Figure 16: Contents of the Prizm folder Figure 17: Server panel of Prizm Administrator Tool Figure 18: Example text-only mode of Administrator Tool, progression to License Manager configuration Figure 19: Example text-only mode of Administrator Tool, progression to server configuration...59 Figure 20: Example Server panel in Administrator Tool Figure 21: Example Database panel in Administrator Tool, ODBC driver not found Figure 22: Example Database pane in Administrator Tool, ODBC driver found Figure 23: Example Error window for failed JDBC connection test Figure 24: Example Error window for database password failure Figure 25: Success window for JDBC connection test Figure 26: Success window for database configuration by the Administrator Tool Figure 27: Default RADIUS configuration in bamconfig.xml file Figure 28: Contents of readme file for RADIUS users... 70

7 Figure 29: Contents of motcanopy.dct file for Steel-Belted RADIUS Figure 30: Contents of motcanopyfreeradius.dct for FreeRadius Figure 31: Example RADIUS configuration file Figure 32: License Manager Administrator Tool, opening web page Figure 33: Example Licensing Configuration panel Figure 34: Redundancy Syncronization panel Figure 35: Example License File Data panel in Prizm Administrator Tool Figure 36: Example Licensing Status panel... 97

8 LIST OF TABLES Table 1: Font types Table 2: Admonition types Table 3: Tested databases Table 4: Sequence of setup tasks Table 5: Integrated Installer options Table 6: Fields of bamconfig.xml file Table 7: Fields of motcanopy.dct on RADIUS server Table 8: Ports that Prizm uses by default Table 9: Configurable XML files on the Prizm server Table 10: Information collected by Technical Support Information Tool on server

9 LIST OF PROCEDURES Procedure 1: Preliminary steps Procedure 2: Downloading MySQL and creating the user Procedure 3: Preparing the.cnf file Procedure 4: Creating the MySQL database Procedure 5: Setting up MySQL database replication Procedure 6: Replacing failed MySQL database Server A with Server B Procedure 7: Replacing failed MySQL database Server B Procedure 8: Installing the server with X-Windows Procedure 9: Installing the server without X-Windows Procedure 10: Configuring the Prizm server for RADIUS server deployment Procedure 11: Setting up FreeRADIUS server for Prizm interaction and SM configuration. 75 Procedure 12: Installing the trial software of SBR Version Procedure 13: Setting up Steel-Belted Radius for Prizm interaction and SM configurations Procedure 14: Assigning service plans (profiles) to SMs Procedure 15: Deriving the hostid on Linux Procedure 16: Changing a host name Procedure 17: Adding license files Procedure 18: Specifying the server that should have full Prizm functionality Procedure 19: Changing ports for Prizm and services Procedure 20: Hosting a Client Java Runtime Installer on the Prizm server Procedure 21: Starting the Prizm server with X-Windows Procedure 22: Starting the Prizm server without X-Windows Procedure 23: Uninstalling Prizm

10

11 Prizm Setup Guide for Linux August USING THIS SETUP GUIDE This document should be used during installation and setup of Motorola Canopy Prizm. The audience for this document is limited to the Prizm server administrator and anyone that this person authorizes to perform the installation and setup. 1.1 FINDING THE INFORMATION YOU NEED Becoming Familiar with This Setup Guide This is a guide to the guide. A high-level overview of the guide and some examples of where to look provide insight into how information is arranged and labeled. The Table of Contents provides not only a sequential index of topics but also a visual glance at the organization of topics in this guide. A few minutes spent with the Table of Contents in either the paper or the electronic version of this guide can save much more time in finding information now and in the future Searching This Setup Guide To search this document and the software release notes of supported releases, look in the Table of Contents for the topic. in the Adobe Reader search capability for keywords that apply INTERPRETING TYPEFACE AND OTHER CONVENTIONS This document employs distinctive fonts to indicate the type of information, as described in Table 1. Table 1: Font types Font variable width bold constant width regular constant width italic constant width bold constant width bold italic Type of Information Selectable option in a graphical user interface or settable parameter in the web-based interface to a Canopy component. Literal system response in a command-line interface. Variable system response in a command-line interface. Literal user input in a command-line interface. Variable user input in a command-line interface. This document employs specific imperative terminology as follows: Type means press the following characters. Enter means type the following characters and then press Enter. 1 Reader is a registered trademark of Adobe Systems, Incorporated. Issue 3 11

12 August 2009 Prizm Setup Guide for Linux This document also employs a set of consistently used admonitions. Each type of admonition has a general purpose that underlies the specific information in the box. These purposes are indicated in Table 2. Table 2: Admonition types Admonition Label NOTE: General Message informative content that may defy common or cursory logic. describe a peculiarity of the Canopy implementation. add a conditional caveat. provide a reference. explain the reason for a preceding statement or provide background for what immediately follows. RECOMMENDATION: suggestion for an easier, quicker, or safer action or practice. IMPORTANT! informative content that may identify an indication that you should watch for. advise that your action can disturb something that you may not want disturbed. reiterate something that you presumably know but should always keep in mind. CAUTION! a notice that the risk of harm to equipment or service exists. WARNING! a notice that the risk of harm to person exists. 1.3 GETTING ADDITIONAL HELP Help is available for problems with supported products and features. Obtaining Technical Support on Page 111 provides the sequence of actions that you should take if these problems arise. 12 Issue 3

13 Prizm Setup Guide for Linux August SENDING FEEDBACK We welcome your feedback on Canopy system documentation. This includes feedback on the structure, content, accuracy, or completeness of our documents, and any other comments you have. Send your comments to Issue 3 13

14

15 Prizm Setup Guide for Linux August SUPPORTED PLATFORMS AND REQUIREMENTS 2.1 PROCESSOR Prizm supports only Intel x86 with Pentium P4 or greater processors and large amounts of the following: Level 2 memory cache (secondary cache) front side bus speed RAM. Lesser amounts support less than optimal performance, and low amounts cause severe operational problems. Prizm is a multi-threaded application. Processors such as the Intel Celeron or CPUs that otherwise do not provide good support for multiple simultaneous threads or processes will not adequately support the needs of this application. 2.2 OPERATING SYSTEMS The Prizm server functions on 32-bit Red Hat Enterprise Linux Version 4 ES or WS (but not AS) operating system. With this operating system, you must select the X-Windows system feature during the operating system installation. This feature installs the following required libraries: xorg-x11 xorg-x11-libs For any upgrades of Version 4 to work properly with Prizm, the following requirements must be met: The upgrades are made via the up2date tool. This ensures that the help and proxy functionalities will work properly. When you use the up2date tool, you must select all packages for upgrading, not merely the Firefox package. This ensures that Firefox will work properly. Use the up2date tool as follows: 1. Since up2date uses a GUI interface, either directly access the client device or have X-windows set up to direct the windows from the client device to the remote X-windows server. 2. At the command prompt, enter /usr/bin/up2date. 3. As you follow the on-screen instructions, select all of the available packages. 2.3 DATABASE APPLICATIONS Prizm accesses the customer databases through Java Database Connectivity (JDBC) application programming interfaces. Each database has a specified XML file for database configuration. Issue 3 15

16 TP PT Steel-Belted August 2009 Prizm Setup Guide for Linux For operator convenience, Canopy suggests some database configuration steps that you can take. However, Canopy does not provide direct support for any database. You should refer any problems that you encounter with the database to the vendor of the database. The databases that Prizm has been successfully tested with are listed in Table 3. Table 3: Tested databases Database MySQL Database Server Version or 5.0 Database Software JDBC Driver Provided by Installed by Provided by Installed by Linux operator operator operator PostgreSQL 7.4 Linux operator Canopy Prizm NOTES: 1. Any later iteration of Version 4.1 is expected to perform as well. If you choose to deploy another database that is not part of the list in Table 3, the database may work only if it provides adequate support of SQL, ODBC, and JDBC. This requires some configuration changes and an XML file that correctly maps the field type names and index syntax that Prizm uses to those that the database uses. For specific information on these configuration changes and the database mapping XML file, see the Prizm Software Development Kit (SDK). As database vendors publish later versions of databases that work today with Prizm, Canopy expects that these will also work. However, this depends on continued adequate support of SQL, ODBC, and JDBC. You can maintain SM authentication and bandwidth configuration on a Remote Authentication Dial-in User Service (RADIUS) server. In this case, Prizm acts as the proxy or network access server (NAS) between the AP and the RADIUS server. These releases are certified to support either FreeRADIUS (see TUhttp:// 2 Steel-Belted RadiusP P (see HTUhttp:// PT 2 Radius is a registered trademark of Funk Software, Inc. 16 Issue 3

17 Prizm Setup Guide for Linux August 2009 Regardless of the RADIUS server vendor, RADIUS should be configured such that no additional delay occurs between when a RADIUS reject occurs and when the RADIUS server responds to the next request. Prizm and Canopy system software do not introduce any new MIB objects for monitoring or managing data on the RADIUS server. do not support the RADIUS Authentication Client MIB, RFC do not support the RADIUS Authentication Server MIB, RFC DATABASE (JDBC) DRIVERS The database vendors include JDBC driver files with their database distributions. These files have.jar extensions. The driver and its precise position in your file system are required for Prizm operation. Prizm works with the following drivers: For PostgreSQL pg jdbc3.jar, which the Prizm setup tool automatically installs. See Installing the JDBC Driver(s) on Page 56. For MySQL any of the following three drivers: mysql-connector-java stable-bin.jar mysql-connector-java ga-bin.jar mysql-connector-java bin.jar You should install one of these after you install the Prizm server, but before you run the Administrator Tool. Then use the Administrator Tool to navigate to and select the.jar file. 2.5 ODBC DRIVERS FOR BAM OPERATIONS IN Prizm The drivers that BAM operations require depend on the database brand: For a PostgreSQL database, the PostgreSQL ODBC driver is required. This is available from the Red Hat Network. However, if you choose the default database while the integrated installation tool is running, then the tool installs the PostgreSQL ODBC driver for you on your Prizm server. For a MySQL database, the MyODBC driver is required. The MySQL driver that the Red Hat Network provides is out of date. Use MySQL support to obtain this driver. Unlike in pre-prizm BAM, support for RADIUS server also requires an ODBC driver on the Prizm server. Neither Prizm nor its Administrator Tool requires you to install the ODBC driver into a particular path. The vendors of the supported databases install the drivers into the /usr/lib directory. The Administrator Tool finds the driver and adds it to the drop-down list. Issue 3 17

18 August 2009 Prizm Setup Guide for Linux ODBC Driver Installation for a MySQL Database Typical installation of the ODBC driver for MySQL is as follows: 1. Log in as root. 2. Enter rpm Uvh ODBCConnectorName.rpm. However, the system may return an error similar to the following: error: Failed dependencies libstdc++.so6(glibcxx_3.4) is needed by ODBCConnectorName If this occurs, attempt to remedy the problem by executing the following command: rpm Uvh --nodeps ODBCConnectorName.rpm For further information, see ODBC Driver Selection for a MySQL Database on Page RUNTIME ENVIRONMENT The runtime environment that Prizm supports is only Java TM 2 Runtime Environment Version 1.5. For local operation, Prizm does not require web server software. The Java applet is downloaded in the first instance that a user accesses the Prizm system. This applet uses HTTP/SSL (as needed) to communicate with the Prizm server. The user access to Prizm is the web browser. Prizm access supports multiple simultaneous users. Requirements about port traffic inhibit running the client applet through an HTTP proxy server. 18 Issue 3

19 Prizm Setup Guide for Linux August ELEMENT LOADS The following considerations are determinants in the number of elements that a single Prizm server instance can support: Hardware considerations CPU capacity of the server number of CPUs on the server RAM on the server size of the hard drive (a lesser consideration) Prizm configuration considerations polling intervals for elements granularity of data gathered upon each polling interval how much of the RAM is dedicated to Prizm Prizm maintenance (the size of the event log that is available online) Network Architecture considerations whether the database is on the Prizm server or a separate server network interface to the database, if on separate server. For example, whether the interface is over the same LAN connection as SNMP traffic on a dedicated LAN off the SNMP traffic (using duel NICs in Prizm) any other applications that are running on the Prizm server device RECOMMENDATION: It is strongly recommended that no applications other than Prizm and the core operating system functions are running on the Prizm server device at any time. Under the following combined conditions, Prizm has successfully supported 5,000 elements: Pentium 4, 3.0-GHz processor 1 GB of RAM 40-GB hard drive 5-minute polling interval on all elements all data gathered at every interval database on local machine no other applications running Issue 3 19

20 August 2009 Prizm Setup Guide for Linux 512-MB maximum Prizm RAM logs available on line: 2-week event log 3-weeks alert log 2-weeks system log Changes in the considerations to more favorable conditions should increase the number of elements that a single Prizm server can support. In the future, Canopy/Motorola will provide additional data points and aids for determining server sizes. 20 Issue 3

21 Prizm Setup Guide for Linux August SETTING UP THE Prizm SERVER 4.1 HIGH-LEVEL SEQUENCE OF SETUP PROCEDURES The proper sequence of setup tasks documented in this appendix are as listed in Table 4. Table 4: Sequence of setup tasks Task Database Documented In On Page 1. Install the database server software. 2. Create a new database user. 3. Create a new database for Prizm. MySQL Procedure 2 29 MySQL Procedure 2 29 MySQL Procedure Install ODBC driver. PostgreSQL or MySQL ODBC Drivers for BAM Operations in Prizm Install Prizm server. PostgreSQL or MySQL PostgreSQL or MySQL Procedure 8 with X-Windows Procedure 9 without X-Windows Install JDBC driver. MySQL Installing the JDBC Driver(s) Launch the Server Administrator Tool. PostgreSQL or MySQL Using the Administrator Tool for Prizm Setup Test and save the database settings. PostgreSQL or MySQL Using the Administrator Tool for Prizm Setup Set up License Manager. PostgreSQL or MySQL Setting Up License Manager Prepare Prizm for licensing. PostgreSQL or MySQL Preparing Prizm for Licensing Set the server mode. 12. Sync the time among server(s) and client. PostgreSQL or MySQL PostgreSQL or MySQL Procedure Syncing Time Perform initial Prizm configuration. PostgreSQL or MySQL Performing the Initial Prizm Configuration 103 Issue 3 21

22 August 2009 Prizm Setup Guide for Linux Task Database Documented In On Page 14. Start the Prizm server. 15. Launch the Prizm client application. PostgreSQL or MySQL PostgreSQL or MySQL Procedure Motorola Canopy Prizm User Guide NOTES: PostgreSQL software is typically included in the Red Hat distribution, but is also available in the Prizm integrated installation tool for your convenience. The JDBC driver for a PostgreSQL database is provided by Canopy and installed by the Prizm setup tool. ODBC drivers, which are not listed in this table, are all provided by the respective database vendors. However, you can obtain the appropriate PostgreSQL ODBC driver from Red Hat. See ODBC Drivers for BAM Operations in Prizm on Page 17. Prizm has been successfully tested with the databases that are listed in this table. For operator convenience, the referenced procedures suggest some database configuration steps that you can take, and Prizm creates all the necessary tables in the database. However, Canopy does not provide direct support for any database. You should refer any problems that you encounter with the database to the vendor of the database. For further information on databases, see Database Applications on Page 15. The "Install Prizm server" step includes the use of the Administrator Tool. See Using the Administrator Tool on Page PREPARING FOR THE INSTALLATIONS The Prizm administration guide provides the procedure for upgrading the server from Release 3.1 to 3.2. This section is for only fresh installations of Prizm. The task or set of tasks that the integrated installation tool for Prizm offers to perform is based on what the tool detects on your device and what you indicate as you use the tool. The tool detects Prizm and License Manager, and relies on your response about the presence of a database, then offers to perform the tasks described in Table 5. Table 5: Integrated Installer options Prizm 3.1 Prizm 3.0 or Earlier What is Currently Installed License Manager 1.x PostgreSQL Database Other Database What the Tool Does at Your Option Upgrades Prizm to. Upgrades License Manager to 2.0. Installs Prizm 3.2. Installs License Manager 2.0. Installs PostgreSQL Issue 3

23 Prizm Setup Guide for Linux August 2009 Prizm 3.1 Prizm 3.0 or Earlier What is Currently Installed License Manager 1.x PostgreSQL Database Other Database What the Tool Does at Your Option Installs Prizm 3.2. Installs License Manager 2.0. Nothing. Cautions that you must upgrade Prizm to 3.1 before you use this tool. Then stops. The kind of information that the tool will prompt for depends on what is being installed. For example, where License Manager is being installed, the tool will ask for a Login, Password, LM Port, and Admin Port. One user account is stored for each Licensing Server. Prizm uses these accounts to authenticate itself on the License Manager web server. In a single license manager configuration, this account is required for remotely viewing license server status uploading and validating a license file starting, stopping, or restarting License Manager In a redundant License Manager configuration, these accounts are required for remotely viewing license server status starting, stopping, or restarting License Manager The Login and Password that the installation tool will ask for in its License Manager Options are for these accounts. The LM Port, with the default number 27000, is the port referred to as Licensing Port in the License Manager Administrator Tool. Server Port in the License Manager area of the Prizm Administrator Tool. This is the port to which Prizm will send its license requests and notifications of licenses forfeited. The Admin Port, with default number 27443, is the port referred to as Webserver Port in both of those other tools. This is the port for web access to the License Manager Administrator tool. Issue 3 23

24 August 2009 Prizm Setup Guide for Linux The installation tool will upgrade License Manager to Release 2.0 where it detects local Release 1.0. However, the tool will not upgrade remote License Manager. In this case, Prizm will work properly with License Manager Release 1.0, but operator tasks on this License Manager must be done according to procedures in Issue 2 of the Release 3 setup guides (without a GUI into License Manager). In the case of any Prizm server installation or upgrade, the tool prompts you at the end for whether to open the Prizm Server Administration Tool, in which you should specify important information about the server and the database. The tool does not install only a database. For a remote database, follow the database installation instructions in the Prizm setup guide. To allow Prizm to update the structure of an existing database, select 1. Use an Existing Database at the Please select Prizm installation options prompt. 2. the option to open the Prizm Server Administrator Tool after the installation tool has finished installing Prizm. In that administrator tool, provide the information that configures Prizm to use the remote database. With that information, Prizm initializes the databases and migrates its structure to compatible with when the Prizm server starts. This is a function of the Prizm server, not the integrated installation tool. The installation processes are illustrated in the following flowcharts. 24 Issue 3

25 Prizm Setup Guide for Linux August 2009 Detected: no Prizm and no License Manager. Install Components Install Prizm Server Install License Manager Items Selected No Prompt/Exit Installation Yes Install Prizm No Yes Prizm Options Install a Database(PostGreSQL) Use an Existing Database No Install LM No Install DB Yes Yes License Manager Options Login Enter Text Database Options Refer to Prizm 3.00 Quick Install Screen For DB Options Password LM Port Admin Port Enter Text Summarize Installation Perform Installation Installation Completed* Installed: Prizm if selected, License Manager if selected, PostgreSQL if selected. Figure 1: Process for fresh installation Issue 3 25

26 August 2009 Prizm Setup Guide for Linux Detected: License Manager Release 1.x and no Prizm License Manager Options Login Password LM Port Enter Text Enter Text Summarize Upgrade Uninstall Previous LM Version Admin Port Install New LM Version Migrate License Files Installation Completed Upgraded: License Manager Figure 2: Process for License Manager upgrade The defaults in a fresh installation are as follows: Panel Field Default Setting License Agreement Select Components To Install Select Prizm Options Installation and Use of Prizm Requires Acceptance of the Following License Agreement Please select the components to install Please select Prizm Installation Options Login I do NOT accept the terms of the License Agreement depends on what is detected Install a Default Database (PostgreSQL) lmadmin License Manager Options Password LM Port lmpassword Admin Port Issue 3

27 Prizm Setup Guide for Linux August 2009 Panel Field Default Setting PostgreSQL Database Passwords Prizm Server Admin Tool Password for Database User 'prizm' Would you like to run Prizm Server Admin Tool on installation complete? PrizmExpress123 Yes for fresh installation No for upgrade To prepare for software installations, perform the following steps. Procedure 1: Preliminary steps 1. Identify the computer(s) for the Prizm server and client. 2. Ensure that the operating system on the computer is supported by Prizm. (See Operating Systems on Page 15.) 3. If you want to run a local console on the server device, perform the preliminary steps that are documented in the section titled "Launching the Prizm Client" in the Motorola Canopy Prizm User Guide. 4. Order and/or obtain the database package as appropriate. (Depending on the brand of database server, the Prizm server installation software provides almost complete documentation and/or configuration setup support. See Database Applications on Page 15.) 5. If the computer has more than one network interface card (NIC), then you must note the MAC address of the eth0 card. IMPORTANT! The license file will need to use this MAC address. 6. With the MAC address of the NIC at hand, order the server and element pack licenses that you will need. NOTE: A single image of Prizm on the computer supports multiple users. end of procedure Issue 3 27

28 August 2009 Prizm Setup Guide for Linux 4.3 INSTALLING DATABASE SOFTWARE Use one of the following sections: Setting Up PostgreSQL (below) Setting Up MySQL on Page 29, then optionally Setting Up Unidirectional MySQL Database Replication on Page Setting Up PostgreSQL The Prizm integrated installation tool automatically sets up the PostgreSQL database if you choose that option during installation. You should have the PostgreSQL software from the Red Hat distribution. This setup creates the initial database, and provisions the service account password, the Superuser, and the database user. If you want to install a PostgreSQL database that is remote to the Prizm server device, perform the following steps in X-Windows: 1. On the Prizm server, run the integrated installation tool (Procedure 8 on Page 41), deselecting PostgreSQL Database in the Select Prizm Features To Install panel (Figure 8 on Page 45). 2. On the database server, run the integrated installation tool (Procedure 8 on Page 41), selecting only PostgreSQL Database in the Select Prizm Features To Install panel, if you do not want License Manager on the database server. PostgreSQL Database and License Manager in the Select Components To Install panel, if you do want License Manager on the database server. 3. On the database server, execute the following commands: chkconfig --level 2345 CanopyPrizmServer off chkconfig --level 2345 CanopyPrizmWebServer off 4. On the Prizm server, use the Administrator Tool (see Using the Administrator Tool for Prizm Setup on Page 56) to point to the database on the database server. If you do not have X-Windows, perform the following steps: 1. On the Prizm server, run the console version of the integrated installation tool (Procedure 9 on Page 54), not selecting the default database. 2. On the database server, run the console version of the integrated installation tool (Procedure 9 on Page 54), selecting to install only PostgreSQL Database, if you do not want License Manager on the database server. to install both PostgreSQL Database and License Manager, if you do want License Manager on the database server. to install the default database. 3. On the database server, execute the following commands: chkconfig --level 2345 CanopyPrizmServer off chkconfig --level 2345 CanopyPrizmWebServer off 28 Issue 3

29 Prizm Setup Guide for Linux August On the Prizm server, use the console version of the Administrator Tool (see Using the Administrator Tool for Prizm Setup on Page 56) to point to the database on the database server Setting Up MySQL NOTE: Except where otherwise noted, all installation steps should be executed by the root user. To download MySQL software, perform the following steps. Procedure 2: Downloading MySQL and creating the user NOTE: The package names in these initial steps are examples. These examples reflect successful testing of MySQL Version 4.1 database with Prizm and presume that the evolving versions from this vendor continue to adequately support SQL, ODBC, and JDBC. 1. From the Red Hat Enterprise Linux WS Extras channel, download the mysql-server rhel4.1.i386 package for Red Hat Enterprise Linux Version From the Red Hat Enterprise Linux WS channel, download the following packages for Red Hat Enterprise Linux Version 4: mysql-devel rhel4.1.i386 mysql rhel4.1.i In the Linux command-line interface, change directory to where the rhn-package files were downloaded. 4. If any packages in this directory have a.tar extension, untar those files into the same directory by entering tar xvf rhn-packages.tar. 5. In this directory, enter rpm -Uvh *.rpm. RESULT: All of the Red Hat packages are installed. 6. At the shell prompt, enter the following commands: /usr/bin/mysqladmin -u root password 'DesiredRootUserPassword' mysql --user=root p 7. When prompted for a password, enter DesiredRootUserPassword. RESULT: The MySQL monitor program opens. 8. Identify the user name and associated password that you want to assign for the MySQL database. NOTE: These must match the user name and password that are stored in the file database.xml on the Prizm server. In that file, the user name specified by default is bost_user, and the associated password specified by default is also bost_user. If you want any other user name or password for the database, then you must use the Administrator Tool to change these. (The password in database.xml is encrypted.) Issue 3 29

30 August 2009 Prizm Setup Guide for Linux 9. In the MySQL monitor program, enter the following commands with single quotes where shown and no line breaks within any of these: grant all privileges on *.* to identified by 'Password' with grant option; RESULT: A message states Query OK, 0 rows affected. grant all privileges on *.* to 'UserName'@'%' identified by 'Password' with grant option; RESULT: A message states Query OK, 0 rows affected, and the specified user account is created. grant all privileges on *.* to 'UserName'@'localhost.localdomain' identified by 'Password' with grant option; RESULT: A message states Query OK, 0 rows affected. exit; RESULT: This closes the MySQL monitor program and restores the command line prompt. EXAMPLE: In the previous step, you identified the user name Canopy and the password Canopy1234 to assign for the MySQL database. In this step, you must enter the commands as follows: grant all privileges on *.* to 'Canopy'@'localhost' identified by 'Canopy1234' with grant option; grant all privileges on *.* to 'Canopy'@'%' identified by 'Canopy1234' with grant option; grant all privileges on *.* to 'Canopy'@'localhost.localdomain' identified by 'Canopy1234' with grant option; end of procedure Before you run the setup tool for Prizm, you must edit the.cnf file on the database server as follows. Procedure 3: Preparing the.cnf file 1. If the MySQL database server is running, log in as root. 2. Enter /etc/rc.d/init.d/mysqld stop. 3. Open the file /etc/my.cnf for editing. 4. At the end of the [mysqld] section of the file, append the following line: innodb_data_file_path=ibdata1:10m:autoextend RESULT: The required transaction support for your version of MySQL is enabled. 5. Modify or append the default-storage-engine line as follows: default-storage-engine=innodb 30 Issue 3

31 Prizm Setup Guide for Linux August Modify or append the innodb_flush_log_at_trx_commit line as follows: innodb_flush_log_at_trx_commit=1 7. Verify that the contents of the file are similar to those shown in Figure 3. [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock innodb_data_file_path=ibdata1:10m:autoextend default-storage-engine=innodb innodb_flush_log_at_trx_commit=1 [mysql.server] user=mysql basedir=/var/lib [safe_mysqld] err-log=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid Figure 3: Contents of my.cnf file for Linux Version 4 and MySQL Server Version Enter /etc/rc.d/init.d/mysqld start. 9. Save and close the file /etc/my.cnf. 10. Enter /etc/rc.d/init.d/mysqld restart. NOTE: If the system returns a failure message, ignore the message. It simply indicates that the service was not running at the time that you executed the start command. end of procedure To create the MySQL database, perform the following steps. Procedure 4: Creating the MySQL database 1. At the shell prompt, enter mysql -u UserNameFrom<Procedure 2> p. RESULT: MySQL prompts for the password. 2. For the password, enter PasswordFrom<Procedure 2>. RESULT: The MySQL monitor program opens. Issue 3 31

32 August 2009 Prizm Setup Guide for Linux 3. In the MySQL monitor program, enter the following commands: create database DatabaseName; 3 RESULT: A message states Query OK, 1 row affected. exit; RESULT: This closes the MySQL monitor program and restores the Linux shell prompt. NOTE: The default port for a MySQL database is The file database.xml on the Prizm server should also specify this port for the PostgreSQL database. end of procedure Setting Up Unidirectional MySQL Database Replication Subject to specific rules and assumptions, MySQL database users can set up replication from a primary database to a slave database and use the slave for a continual data backup and for failover. The failover case would require either using the Administrator Tool to deliberately reconfigure Prizm for the former slave (new primary) database or changing the IP address of the former slave database server to that of the former primary database server. This configuration is illustrated in Figure 4. 3 DatabaseName is specified in the file database.xml (on the PrizmEMS server) by default or the administrator. The default database name (default value of dbname) in this file is prizm. 32 Issue 3

33 Prizm Setup Guide for Linux August 2009 PrizmEMSServerlicensed server writes data queries database responds to query Primary MySQL Database (Server A) BAMServerlicensed redundant server writes data queries database responds to query writes data Replicated Standby MySQL Database (Server B) Figure 4: Replicated standby MySQL database in typical configuration NOTE: The rules and procedures refer to using the Administrator tool to start and stop the Prizm server(s). These options are available from the main menu of the Administrator Tool as commands at Action PrizmEMS Server Start and Action PrizmEMS Server Stop, respectively. Rules The procedures in this section carry the following rules: 1. Use the same version of MySQL Database Server on both the master (Server A) and the slave (Server B). If you fail to do this, data may not be correctly replicated, in which case the only way to restore the data in the event of failure of Server A is to entirely rebuild the network in Prizm. 2. MySQL database replication does not automatically handle a failover. A failover situation requires deliberate reconfiguration steps, such as running the Administrator Tool to a. stop the Prizm server. b. change the IP address in the Host field of the Database pane. Issue 3 33

34 August 2009 Prizm Setup Guide for Linux c. restart the Prizm server. 3. The procedures set up two-way synchronization between the two database servers, but you should use only one server at a time. This is because the current design of table and column in Prizm does not support multiple Prizm servers running against multiple redundant databases, whereas the design of BAM did. 4. Canopy has tested and supports MySQL database replication. Canopy has not tested and does not support MySQL Cluster. Assumptions These procedures in this section carry the following assumptions: 1. You want to perform bidirectional replication between two and only two MySQL database servers. Canopy supports Prizm server attachment to only one database at a time and any redundant servers on BAM server licenses must attach to the same database. 2. You are not already performing replication on either of the two database servers for some other purpose (for example, databases maintained on these servers for another product and replicated on other servers). In this case, replication is possible, but may interrupt the ongoing replication. MySQL documentation or MySQL technical support may provide guidance for this case, but Canopy does not support it. 3. You already have a Prizm database set up on one of the servers (Server A), but not on the other (Server B). The name of the database on Server A is prizm. 4. Prizm server(s) are not running during the replication setup procedure, which involves manually copying some database files for the initial setup before replication begins. Updates that would occur between the manual copying and the activation of replication would not be copied to Server B. 5. A database user for Prizm to connect to already exists on both servers. The user name is bost_user. See Procedure 2: Downloading MySQL and creating the user on Page Your PATH environment variable has access to mysql command utilities on both Server A and Server B. Setting Up Replication The following procedure was tested and verified on the following platforms: On Server A Windows XP Professional MySQL Server a-nt On Server B Red Hat Enterprise Linux Version 4 MySQL Server Whenever you create or configure users or databases, refer to the latest documentation on the MySQL web site. To set up unidirectional MySQL database replication, perform the following steps. 34 Issue 3

35 Prizm Setup Guide for Linux August 2009 Procedure 5: Setting up MySQL database replication 1. Become familiar with the rules and assumptions listed above. 2. If Server A does not already have a Prizm database, perform the following steps: a. Create the database according to the procedure titled "Creating the MySQL Database" in Motorola Canopy Prizm Server Setup Guide for Windows Platforms. b. Start the Prizm server(s). c. Verify that the Prizm server(s) point to Server A as its database server. 3. If a database is present on Server B, perform the following steps, at the mysql command line prompt, enter drop database prizm. NOTE: If the database name is not prizm, substitute the database name that you chose. 4. If either server does not have the mysql PATH environment variable set, add it as follows: If on Windows, add MySQLInstallationFolder\bin to your path. If on Linux, add /usr/bin to your path. 5. If the Prizm server(s) are running, shut them down. 6. On Servers A and B, stop the MySQL service. 7. On Server A, open the file /etc/my.cnf (typical path) on Linux (or MySQLInstallationFolder\my.ini on Windows) for editing. 8. In the [mysqld] section of the file, add the following lines: server-id=1 log-bin=mysql-bin skip-slave-start 9. Save and close the file. 10. On Server A, restart the MySQL service. 11. On Server A, enter mysql -u bost_user p. 12. Enter the password that is associated with the user bost_user. RESULT: The system returns the MySQL prompt. 13. Enter the following command: GRANT REPLICATION SLAVE ON *.* to 'repl'@'%' IDENTIFIED BY 'slavepass'; RESULT: The user repl is allowed replicate data on Server A. 14. On server B, open the file /etc/my.cnf (typical path) on Linux (or MySQLInstallationFolder\my.ini on Windows) for editing. 15. In the [mysqld] section of the file, add the following lines: server-id=2 log-bin=mysql-bin skip-slave-start 16. Save and close the file. 17. On Server B, restart the MySQL service. Issue 3 35

36 August 2009 Prizm Setup Guide for Linux 18. On Server B, enter mysql -u bost_user p. 19. Enter the password that is associated with the user bost_user. RESULT: The system returns the MySQL prompt. 20. Enter the following command: GRANT REPLICATION SLAVE ON *.* to IDENTIFIED BY 'slavepass'; RESULT: The user repl is allowed to replicate data on Server B. 21. If the database on Server A is not empty, synchronize the databases (to ensure a common starting image) as follows: a. On Server A, perform the following steps: (1) Access the Windows or Linux command prompt. (2) Enter the following command: mysqldump -u bost_user -p prizm > prizmdb.sql (3) If prompted to, type in the appropriate password. b. RESULT: The file prizmdb.sql is created in the current directory. c. Copy the file prizmdb.sql from Server A to Server B. d. On Server B, perform the following steps: (1) Access the Windows or Linux command prompt. (2) Change directory to where you copied the prizmdb.sql file. (3) Enter mysql -u bost_user p. (4) If prompted to, type in the appropriate password. RESULT: The system returns the MySQL prompt. (5) Enter the following commands: create database prizm; exit; RESULT: An empty database is created. NOTE: This step was required because the prizmdb.sql file you created earlier describes what data to put into the database, but does not create the database. (6) At the Windows or Linux command prompt, enter the following command: mysql -u bost_user -p prizm < prizmdb.sql (7) If prompted to, type in the appropriate password. RESULT: The data is imported into the prizm database of Server B. 36 Issue 3

37 Prizm Setup Guide for Linux August On Server A, at the MySQL prompt, enter the following commands: RESET MASTER; SHOW MASTER STATUS; RESULT: The system returns a table similar to the following: File Position Binlog_Do_DB Binlog_Ignore_DB mysql-bin row in set (0.00 sec) Make a note of the filename (mysql-bin in this example) to later use as filenamea and the position (10380 in this example) to later use as positiona. 23. On Server B, at the MySQL prompt, enter the following commands: RESET MASTER; SHOW MASTER STATUS; RESULT: The system returns a table similar to the following: File Position Binlog_Do_DB Binlog_Ignore_DB mysql-bin row in set (0.00 sec) 24. Make a note of the filename and position to later use as filenameb and positionb. 25. On Server A, at the MySQL prompt, enter the following commands: CHANGE MASTER TO MASTER_HOST='<IP address of server B>', MASTER_USER='repl', MASTER_PASSWORD='slavepass', MASTER_LOG_FILE='<filenameB>', MASTER_LOG_POS=<positionB>; 26. On server B, at the MySQL prompt, enter the following commands: CHANGE MASTER TO MASTER_HOST='<IP address of server A>', MASTER_USER='repl', MASTER_PASSWORD='slavepass', MASTER_LOG_FILE='<filenameA>', MASTER_LOG_POS=<positionA>; 27. On Servers A and B, stop the MySQL service. 28. On Server A, open the file /etc/my.cnf (typical path) on Linux (or MySQLInstallationFolder\my.ini on Windows) for editing. 29. In the [mysqld] section of the file, remove the line skip-slave-start. 30. Save and close the file. 31. On Server B, open the file /etc/my.cnf (typical path) on Linux (or MySQLInstallationFolder\my.ini on Windows) for editing. 32. In the [mysqld] section of the file, remove the line skip-slave-start. 33. Save and close the file. 34. On Servers A and B, restart the MySQL service. 35. On Server A, at the MySQL prompt, enter start slave;. Issue 3 37

38 August 2009 Prizm Setup Guide for Linux 36. On Server B, at the MySQL prompt, enter start slave;. 37. Restart the Prizm server(s). end of procedure Any changes that Prizm makes to the database will be replicated into the database on Server B. Caveat After replication is setup, be careful about database maintenance operations. The purpose of the above procedure was to set up unidirectional replication to create a backup to use in case the primary database server fails, but those steps in fact set up bidirectional replication for quick and simple replacement of a down primary server. If you manually change the data in Server B, that change is copied into the database on Server A. This presents the hazard that, if an operator inadvertently executes the command drop database prizm on Server B, the result will be that the database is immediately removed from both Server A and Server B. The only recovery at that point would be to completely rebuild your network and all element settings in Prizm. Recovering in a Failover Scenario If Server A ever fails, you can quickly and simply begin using Server B as your database server. To do this, perform the following steps. Procedure 6: Replacing failed MySQL database Server A with Server B 1. If the Prizm server(s) are running, shut them down. NOTE: If Server A and Prizm server resided on the same device, then Prizm may also have failed when Server A failed. 2. On the Prizm server(s), launch the Administrator Tool. 3. In the Database pane, update the Host field to the IP address of Server B. 4. Restart the Prizm server(s). RESULT: What was Server B is now Server A, the primary database server. end of procedure For the remainder of this section, Server A refers to the primary database server, regardless of the role that it formerly served. This is consistent with Figure 4 on Page 33. If the failed server is irreparable and you thus need to replace it, you may want to have the now Server A replicate its data to a new Server B. This involves updating one server rather than both and assumes that the new Server B has the same IP address as Server A had in Procedure 5. To set up the new Server B for replication, perform the following steps. Procedure 7: Replacing failed MySQL database Server B 1. If the Prizm server(s) are running, shut them down. 2. On Servers A and B, stop the MySQL service. 38 Issue 3

39 Prizm Setup Guide for Linux August On the new Server B, open the file /etc/my.cnf (typical path) on Linux (or MySQLInstallationFolder\my.ini on Windows) for editing. 4. In the [mysqld] section of the file, add the following lines: server-id=1 log-bin=mysql-bin skip-slave-start 5. Save and close the file. 6. On the new Server B, restart the MySQL service. 7. On the new Server B, perform the following steps: a. Access the Windows or Linux command prompt. b. If prompted to, type in the appropriate password. c. At the MySQL prompt, enter the following command: GRANT REPLICATION SLAVE ON *.* to IDENTIFIED BY 'slavepass'; RESULT: The user repl is allowed to replicate data on the new Server B. 8. On Server A, open the file /etc/my.cnf (typical path) on Linux (or MySQLInstallationFolder\my.ini on Windows) for editing. 9. In the [mysqld] section of the file, add the following line: skip-slave-start 10. Save and close the file. 11. On Server A, restart the MySQL service. 12. On Server A, at the Windows or Linux command prompt, enter the following command: mysqldump -u bost_user -p prizm > prizmdb.sql 13. If prompted, type in the appropriate password. RESULT: The file prizmdb.sql is created in the current directory. 14. Copy the file prizmdb.sql from Server A to the new Server B. 15. On the new Server B, perform the following steps: a. Access the Windows or Linux command prompt. b. Change directory to where you copied the prizmdb.sql file. c. Enter mysql -u bost_user p. d. If prompted to, type in the appropriate password. RESULT: The system returns the MySQL prompt. e. Enter the following commands: create database prizm; exit; RESULT: An empty database is created. NOTE: This step was required because the prizmdb.sql file you created earlier describes what data to put into the database, but does not create the database. Issue 3 39

40 August 2009 Prizm Setup Guide for Linux f. At the Windows or Linux command prompt, enter the following command: mysql -u bost_user -p prizm < prizmdb.sql g. If prompted to, type in the appropriate password. RESULT: The data is imported into the prizm database of the new Server B. 16. On Server A, at the MySQL prompt, enter the following command: SHOW MASTER STATUS; RESULT: The system returns a table similar to the following: File Position Binlog_Do_DB Binlog_Ignore_DB mysql-bin row in set (0.00 sec) 17. Make a note of the filename and the position to later use as filenamea and positiona. 18. On the new Server B, at the MySQL prompt, enter the following commands: RESET MASTER; SHOW MASTER STATUS; RESULT: The system returns a table similar to the following: File Position Binlog_Do_DB Binlog_Ignore_DB mysql-bin row in set (0.00 sec) 19. Make a note of the filename and position to later use as filenameb and positionb. 20. On the new Server B, at the MySQL prompt, enter the following commands: CHANGE MASTER TO MASTER_HOST='<IP address of server A>', MASTER_USER='repl', MASTER_PASSWORD='slavepass', MASTER_LOG_FILE='<filenameA>', MASTER_LOG_POS=<positionA>; 21. On Server A, at the MySQL prompt, enter the following commands: CHANGE MASTER TO MASTER_HOST='<IP address of server B>', MASTER_USER='repl', MASTER_PASSWORD='slavepass', MASTER_LOG_FILE='<filenameB>', MASTER_LOG_POS=<positionB>; 22. On Servers A and the new Server B, stop the MySQL service. 23. On Server A, open the file /etc/my.cnf (typical path) on Linux (or MySQLInstallationFolder\my.ini on Windows) for editing. 24. In the [mysqld] section of the file, remove the line skip-slave-start. 25. Save and close the file. 26. On the new Server B, open the file /etc/my.cnf (typical path) on Linux (or MySQLInstallationFolder\my.ini on Windows) for editing. 27. In the [mysqld] section of the file, remove the line skip-slave-start. 40 Issue 3

41 Prizm Setup Guide for Linux August Save and close the file. 29. On Servers A and the new Server B, restart the MySQL service. 30. On the new Server B, at the MySQL prompt, enter start slave;. 31. On Server A, at the MySQL prompt, enter start slave;. 32. Restart the Prizm server(s). NOTE: The Prizm server(s) should still be pointing to Server A as the database server. end of procedure Any changes that Prizm makes to the database will be replicated into the database on the new Server B. 4.4 INSTALLING THE Prizm SERVER For a new installation of the Prizm server, use one of the following sections: Installing the Prizm Server and Optional Components with X-Windows (below) Installing the Prizm Server and Optional Components without X-Windows on Page Installing the Prizm Server and Optional Components with X-Windows For a new installation of the Prizm server, perform the following steps. (For an upgrade of the server, see the Motorola Canopy Prizm Server Administration Guide.) NOTE: At the end of the execution of the Prizm setup script, you will have the option to check a box that causes the installation tool to quit and the server Administrator Tool to launch. This tool allows you to configure the server and database, and start/stop the server, from a GUI or console interface. See Using the Administrator Tool on Page 56. Procedure 8: Installing the server with X-Windows 1. If you want to use a MySQL database that is not installed, install it now on this or another computer. NOTE: See Installing Database Software on Page 28. If you want to use a PostgreSQL database (that is not yet installed) on another computer, install it now. 2. If your database now exists, start the database process on the database computer. 3. On the machine where you are installing the Prizm server, log in as root. 4. Download prizm_linux32_3_2_13.tgz into the /tmp directory on the Prizm server. Issue 3 41

42 August 2009 Prizm Setup Guide for Linux 5. From the Linux command prompt, enter tar -zxvf /tmp/prizm_linux32_3_2_13.tgz. 6. From the Linux command prompt, execute the following commands: cd /tmp/prizm_linux32_3_2_13 chmod +x prizm_linux32_3_2_13.bin./prizm_linux32_3_2_13.bin NOTE: The installer installs its own web server, which uses Port 80 and, for secure connections, Port If either of these ports is in use, the installer prompts you to select an alternative port for the Prizm web server. RESULT: The installation tool opens to the Canopy logo. This gives way to the Introduction screen, shown in Figure 5. Figure 5: InstallAnywhere Introduction panel 42 Issue 3

43 Prizm Setup Guide for Linux August Read the introduction. 8. Click Next. RESULT: The wizard opens the License Agreement panel, shown in Figure 6. Figure 6: InstallAnywhere License Agreement panel 9. Using the vertical scrollbar, read the terms carefully and thoroughly. 10. Only if you agree to all of the terms and conditions, check I accept the terms of the License Agreement. 11. Click Next. RESULT: The wizard detects whether an earlier version of Prizm is currently installed. If it does detect either Release 3.0 or 3.1, it opens the Prizm 3.x Detected panel with a prompt to proceed with the removal of that release and the upgrade to. In this case, use the upgrade instructions in the Motorola Canopy Prizm Server Administration Guide. If the wizard does not detect an earlier version, continue with this procedure. The wizard detects whether Wireless Manager (WM) of the One Point Wireless Suite is present. If it is, then the wizard opens the WMS Detected panel, shown in Figure 7. Issue 3 43

44 August 2009 Prizm Setup Guide for Linux Figure 7: WMS Detected panel 12. To allow WM to receive the traps that are otherwise bound for Prizm (and then forward them to Prizm), check the Install Prizm as Sub System of the WMS option and click Next. RESULT: The installation of Prizm continues. To allow Prizm to listen for traps as it would in a standalone environment, leave that option unchecked and click Next. RESULT: The installation of Prizm continues. The wizard opens the Select Prizm Features To Install panel, shown in Figure Issue 3

45 Prizm Setup Guide for Linux August 2009 Figure 8: Select Prizm Features To Install panel 13. Check the check box of the component(s) that you want to install. NOTE: If this device is remote to your Prizm server, and you want to install only License Manager via this integrated installation tool, uncheck the option Install Prizm Server. See Installing License Manager on Page 89. IMPORTANT! Set the Install Set drop-down option as follows: If you want the tool to install a PostgreSQL database, select Custom. Then, if the tool detected both no instance of Prizm and no instance of PostgreSQL, the tool will install the database. After the next two panels (Choose Install Folder and License Manager Options), the wizard will open the PostgreSQL Database panel for you to configure passwords for the service, the superuser account, and the user account with associated password that Prizm uses for writing to and reading from PostgreSQL. If you do not want the tool to install a PostgreSQL database, leave Typical selected. 14. From the Install Set drop-down options, select either Typical or Custom. 15. Click Next. RESULT: The wizard the Choose Install Folder panel. 16. Specify the directory where you want the Prizm server installed. Issue 3 45

46 August 2009 Prizm Setup Guide for Linux 17. Click Next. RESULT: If you selected Install Canopy License Manager in Step 12, the wizard opens the License Manager Options panel, shown in Figure 9. Figure 9: License Manager Options panel 18. Keep the default values for now. 19. Click Next. NOTE: You can change any of these later, but if you do, you must identically change them in each License Manager web server and in the Prizm Administrator Tool. RESULT: If you selected Custom in Step 14, the wizard opens the PostgreSQL Database Passwords panel, similar to that shown in. 46 Issue 3

47 Prizm Setup Guide for Linux August 2009 Figure 10: PostgreSQL Database Password panel 20. Change or keep any of these passwords. IMPORTANT: Regardless of whether you change it, you will need to later ensure that the same user password is populated in the User field of the Database Configuration panel in the Prizm Administrator Tool. 21. Click Next. NOTE: The installer installs its own web server, which uses Port 80 and, for secure connections, Port If either of these ports is in use, the installer may prompt you to select an alternative port for the Prizm web server. NOTE: The wizard opens the Pre-Installation Summary panel, similar to the one shown in Figure 10. Issue 3 47

48 August 2009 Prizm Setup Guide for Linux Figure 11: Example Pre-Installation Summary panel 22. Click Install. RESULT: The wizard opens the Installing Prizm panel and provides messages there as it installs the program. These messages may include the following: Installing Uninstaller.exe Installing x32 Installing FLEXnet Updating licensing.xml (in a pop-up window) Installing Refreshing Environment Installing postgresql-8.2-int.msi Installing Execute Script/Batch file: PostgreSQL Installing database.xml & bamconfig.xml Installing Execute Script/Batch file: Windows DB Configuration Updating Keystore (in a pop-up window) 23. After displaying the series of messages, the wizard opens the Please Wait panel, shown in Figure Issue 3

49 Prizm Setup Guide for Linux August 2009 Figure 12: Please Wait panel NOTE: At the end of the Prizm installation, the Install Complete panel indicates success (Figure 13) or the fact that errors occurred (Figure 14). Figure 13: Install Complete panel, success Issue 3 49

50 August 2009 Prizm Setup Guide for Linux Figure 14: Example Install Complete panel, errors This refers to the log that you can find at /usr/local/canopy/prizm in the file Prizm_InstallLog.log following the installation. Example contents that may be present in this file (for a successful installation) are shown in Figure Issue 3

51 Prizm Setup Guide for Linux August 2009 Figure 15: Example portion of installation log for successful installation Other contents of the /usr/local/canopy/prizm directory are shown in Figure 16. Issue 3 51

52 August 2009 Prizm Setup Guide for Linux Figure 16: Contents of the Prizm folder 24. Back in the Install Complete panel, click Done. RESULT: A Please Wait window may open before the Administrator Tool opens to its Server Configuration pane. NOTE: If you answered yes to the prompt Would you like to run Prizm Server Admin Tool after installation is complete, the tool opens its interface to the Server panel, shown in Figure Issue 3

53 Prizm Setup Guide for Linux August 2009 Figure 17: Server panel of Prizm Administrator Tool 25. Install the JDBC driver(s), as described in the next section, Installing the JDBC Driver(s) on Page 56. IMPORTANT: You must use the Administrator Tool in Step 30 to automatically update the file database.xml. 26. If the appropriate ODBC driver (as indicated in ODBC Drivers for BAM Operations in Prizm on Page 17) does not already exist on your server, install it now, referring to driver installation instructions for additional information. 27. At the Linux command prompt, enter the following commands: cd /usr/local/canopy/prizm/bin./serveradmintool.sh. RESULT: The GUI interface of the Administrator Tool opens. IMPORTANT: The Admin Tool must run, and you must confirm and save your database settings in it. This is because Release 3.1 requires encrypted passwords in the xml files, and only the Admin Tool can set these passwords. 28. Use the Administrator Tool to configure the server and database files in Prizm, as described under Using the Administrator Tool for Prizm Setup on Page 56. IMPORTANT: User is the user name that you created in the database software. Password is the password that the Prizm user will use. Issue 3 53

54 August 2009 Prizm Setup Guide for Linux 29. When you have finished updating the Database Configuration pane of the Administrator Tool, perform the following steps: a. Click Test. NOTE: This launches a test of the JDBC connection. b. If the tool indicates that the test was not successful, troubleshoot the JDBC driver, as described under Database (JDBC) Drivers on Page 17. If the tool returns an indication of success, click Save. end of procedure After the installation(s), the integrated installer tool places in the same directory as itself a file named installer.properties. If you ever need to rerun the installation tool and select a different set of options in the tool GUI, you must first delete this file. Otherwise, the new installation will be corrupted Installing the Prizm Server and Optional Components without X-Windows For a new installation of the Prizm server, perform the following steps. (For an upgrade of the server, see the Motorola Canopy Prizm Server Administration Guide.) Procedure 9: Installing the server without X-Windows 1. If you want to use a MySQL database that is not installed, install it now on this or another computer. NOTE: See Installing Database Software on Page 28. If you want to use a PostgreSQL database (that is not yet installed) on another computer, install it now. 2. If your database now exists, start the database process on the database computer. 3. On the machine where you are installing the Prizm server, log in as root. 4. Download prizm_linux32_3_10_r4.tgz. 5. Use ftp or sftp to Transfer prizm_linux32_3_10_r4.tgz into the /tmp directory of the server device. 6. From the Linux command prompt, enter tar -zxvf /tmp/prizm_linux32_3_10_r4.tgz. 7. From the Linux command prompt, execute the following commands: cd /tmp/prizm_linux32_3_10_r4 chmod +x prizm_linux32_3_10_r4.bin./ prizm_linux32_3_10_r4.bin -- i console RESULT: The installer tool installs Prizm into the directory /usr/local/canopy/prizm. If the system does not return an error, skip the following numbered step. NOTE: The installer installs its own web server, which uses Port 80 and, for secure connections, Port If either of these ports is in use, the installer may prompt you to select an alternative port for the Prizm web server. 54 Issue 3

55 Prizm Setup Guide for Linux August If no database currently exists, allow the installation tool to install a default PostgreSQL database. 9. If you did not choose to allow the installation tool to install and configure a default PostgreSQL database, perform the following steps: a. If the appropriate ODBC driver (as indicated in ODBC Drivers for BAM Operations in Prizm on Page 17) does not already exist on your server, install it now, referring to driver installation instructions for additional information. b. Install the JDBC driver(s), as described in the next section, Installing the JDBC Driver(s). IMPORTANT: You must use the Administrator Tool to automatically update the file database.xml. 10. When the setup tool execution has concluded, at the Linux command prompt, enter the following commands: cd /usr/local/canopy/prizm/bin./serveradmintool_console.sh RESULT: The console interface of the Administrator Tool opens. 11. At the Please enter your option prompt, enter 5 for Configure Server/Database. 12. At the Please enter your option prompt, enter 1 for Configure Server. 13. Verify server settings, as described under Using the Administrator Tool on Page For any server setting that you need to edit, enter the setting number at the prompt (for example, enter 6, then change Element Web Proxy to enabled). 15. When you have finished specifying server information, enter 7 for Save. 16. If you chose to allow the installation tool to install and configure a default PostgreSQL database, perform the following steps: a. Back in the previous menu of the Administrator Tool, enter 2 for Configure Database. b. Verify/enter database settings as described under Using the Administrator Tool on Page 56. IMPORTANT: User is the user name that you created in the database software. Password is the password that the Prizm user will use. c. When you have finished specifying database information, enter the number that corresponds to the Save option. 17. At the Please enter your option prompt, enter Quit. end of procedure After the installation(s), the integrated installer tool places in the same directory as itself a file named installer.properties. If you ever need to rerun the installation tool and select a different set of options in the tool GUI, you must first delete this file. Otherwise, the new installation will be corrupted. Issue 3 55

56 August 2009 Prizm Setup Guide for Linux Installing the JDBC Driver(s) The brand of database you have chosen determines whether and how you need to install one or more JDBC drivers: For a PostgreSQL database, the Prizm integrated installation tool installs the correct JDBC driver and properly configures the postgresql.xml file that it installs. This file points to the driver. For a MySQL database, the JDBC driver is included with the MySQL Database Server distribution, but not installed by the Prizm installer. The distribution refers to the driver as MySQL Connector/J. You must untar the driver and use the Administrator Tool to navigate to and select the.jar file Using the Administrator Tool for Prizm Setup The prizmsetup installation tool prompts you to optionally select the Administrator Tool to launch. The Administrator Tool can perform all of the following functions through either a console interface or a GUI in the Prizm server: start, stop, and restart the server. In the GUI, these options are available as commands from the main menu at Action PrizmEMS Server Start and Action PrizmEMS Server Stop. The proper shutdown sequence to be performed before rebooting the Prizm server is as follows: IMPORTANT! This shutdown sequence is essential for avoiding corruption of the Prizm database. Then later, the proper restart sequence is as follows: update the configuration files of the server. In the GUI, these options are available in the Server pane. update the configuration files of the database. In the GUI, these options are available in the Database pane. 56 Issue 3

57 Prizm Setup Guide for Linux August 2009 With the Administrator Tool, you can update the server configuration to select the server mode that is licensed to you. change the server port and the ports that services use. See Optionally Reconfiguring Prizm Ports on Page 84. entirely enable or disable the Northbound Interface feature: separately enable or disable the SOAP API, if the Northbound Interface is enabled. separately enable or disable the SNMP agent in Prizm, if the Northbound Interface is enabled. enable or disable the element web proxy. The Administrator Tool configures the ODBC driver for the BAM subsystem as follows: Linux GUI users should launch the tool from the directory /usr/local/canopy/prizm/bin directory, entering ServerAdminTool.sh. The GUI version of the Administrator Tool opens. Linux console users should launch the tool from the directory /usr/local/canopy/prizm/bin directory, entering ServerAdminTool_Console.sh. 4 The text-only mode of the Administrator Tool opens in the Linux console. An example of the text-only interface is shown in Figure 18 and Figure During the installation, the prizmsetup tool placed this tool in the bin directory and made it executable. Issue 3 57

58 August 2009 Prizm Setup Guide for Linux Figure 18: Example text-only mode of Administrator Tool, progression to License Manager configuration 58 Issue 3

59 Prizm Setup Guide for Linux August 2009 Figure 19: Example text-only mode of Administrator Tool, progression to server configuration A GUI example of the Server panel with pre-filled values is shown in Figure 20. Issue 3 59

60 August 2009 Prizm Setup Guide for Linux Figure 20: Example Server panel in Administrator Tool The Reset button restores all of the fields in this pane to their pre-filled values. The Save button puts your changes into effect. Similarly, with the Administrator Tool, you can update the Java database connectivity (JDBC) configuration to select from database brands. identify the IP address of the host. specify the port number for the JDBC connection. type in the name of the database. specify the user. store the associated password. browse to select the JDBC driver file(s). (You can select multiple jar files.) See Database (JDBC) Drivers on Page 17. A GUI example of the Database panel with pre-filled dialog values is shown in Figure Issue 3

61 Prizm Setup Guide for Linux August 2009 Figure 21: Example Database panel in Administrator Tool, ODBC driver not found Occasionally, selecting a Database Type stalls the Administrator Tool. To work around a stall, you can either switch between the options in the left pane (Server and Database) or switch database types, ending with your type. In the example Database Configuration pane shown in Figure 21 above, since the tool did not find an appropriate ODBC driver, it provides the message Please install an ODBC Driver as a reminder. If you have a PostgreSQL database and select PostgreSQL from the drop-down for Database Type, then the resulting pane may appear as shown in Figure 22. Issue 3 61

62 August 2009 Prizm Setup Guide for Linux Figure 22: Example Database pane in Administrator Tool, ODBC driver found For the JDBC Driver field, if you browse to and select a jar file that is in a path other than the path that the file database.xml specifies, then after you click the Save button, the Administrator Tool copies the jar file to the latter path. Thereafter the JDBC Driver field points to the file in the new path. The Test button launches a connection attempt to ensure that the selected JDBC driver works properly. The test may trigger a firewall alert that indicates that Java is attempting to access the Internet. If this occurs, allow Java to do so. If the test of the JDBC connection fails, then the tool reports the failure in an Error window, as shown in Figure 23. Figure 23: Example Error window for failed JDBC connection test This may be an indication that the database service is not running. If it is not, start the service. If after you do, you may see a different error, as shown in Figure Issue 3

63 Prizm Setup Guide for Linux August 2009 Figure 24: Example Error window for database password failure Possible reasons for the password error include the database user password in the file database.xml is not yet configured on the Prizm server. the user and password in that file, the user and password in the Database pane of the Administrator Tool GUI, and the user and password in the database GUI do not all match each other. When they do, and you click the Test button, the tool opens the Success window, as shown in Figure 25. Figure 25: Success window for JDBC connection test The Reset button restores all of the fields in this pane to their pre-filled values. You can also update the Open Database Connectivity (ODBC) configuration to select the proper ODBC driver to associate with a Datasource Name (DSN). This driver is available either through Red Hat (for PostgreSQL) or through the database vendor (for MySQL). type in the Datasource Name (DSN). This will become the contents of the Data Source field, not the Description Field, in the PostgreSQL ODBC driver. The ODBC Driver field is only a drop-down selection menu, not also a dialog. This is to prevent you from specifying a driver file that you think is installed, but is not. Only installed files are listed. Issue 3 63

64 August 2009 Prizm Setup Guide for Linux ODBC Driver Selection for a MySQL Database Typically, your rpm execution on the driver would have downloaded multiple iterations of library files, although you must select only one. Observe the following recommendations for driver selection: wherever possible, select a driver whose name has the syntax libmyodbc*_r.so. does not contain a version number. does not have the syntax libmyodbc*s*.so. Links to driver names that contain version numbers typically are not updated for driver upgrades. However, over time you may want to upgrade your driver. In this case, when you upgrade, you must also use the Administrator Tool provided with Prizm to select the new driver. Otherwise, Prizm will not function properly. Links to driver names that do not contain version numbers typically are updated to link to upgraded files. In this case, when you upgrade, the driver that you pointed to in the Administrator Tool is still the valid driver name, and the connection to Prizm continues to function properly. Two examples of good selections, based on these recommendations, are highlighted below: MySQL:libmyodbc3.so MySQL:libmyodbc3S.so MySQL:libmyodbc so MySQL:libmyodbc3S so MySQL:libmyodbc3.so MySQL:libmyodbc3_r so MySQL:libmyodbc3S.so MySQL:libmyodbc so MySQL:libmyodbc3S so MySQL:libmyodbc3_r.so 64 Issue 3

65 Prizm Setup Guide for Linux August 2009 If the ODBC driver that you select does not work properly, 5 then for each of the drivers (in order preferred to not preferred, based on the recommendations above), perform the following steps: The Save button (1) At the command prompt, enter ldd /usr/lib/driverfilename. RESULT: The system response is a block of information that is similar to the following. libcrypt.so.1 => /lib/libcrypt.so.1 (0x00fb0000) libnsl.so.1 => /lib/libnsl.so.1 (0x00dc7000) libm.so.6 => /lib/tls/libm.so.6 (0x ) libltdl.so.3 => /usr/lib/libltdl.so.3 (0x ) libdl.so.2 => /lib/libdl.so.2 (0x ) libodbcinst.so.1 => /usr/lib/libodbcinst.so.1 (0x006a4000) libc.so.6 => /lib/tls/libc.so.6 (0x ) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x ) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x ) (2) If any line included not found (for example, libcrypt.so.1 => not found), contact Red Hat and/or MySQL technical support to find where and how to obtain missing dependencies that the ODBC driver needs. NOTE: This can occur if the --nodeps option prevented the rpm program from detecting that a dependency was missing when you installed the driver. See ODBC Driver Installation for a MySQL Database on Page 18. (3) If no line includes not found, select the driver in the Administrator Tool and try various database functions in Prizm again. puts your changes into effect without a connection test. copies the jar file to the default driver path, which is specified in the file database.xml, if the file that you browsed to and selected was not in that path. When you have clicked the Save button, look for a Success window to pop up, as shown in Figure 26. Figure 26: Success window for database configuration by the Administrator Tool This does not indicate that the JDBC connection is working. You still need to get that connection to pass the test. 5 Typically, if the ODBC driver does not work properly, then Prizm server fails to start. Issue 3 65

66 August 2009 Prizm Setup Guide for Linux After you have saved the Database pane contents, you can confirm that the Administrator Tool created the data source: enter isql DatabaseName. If an SQL prompt is returned, then the data source was created. If an error is returned, the operation failed. The console mode of the Administrator Tool displays the fields in the same sequence as the GUI mode does. In the console mode, the following commands apply: To accept the value in any pre-filled field in the console mode, press Enter. To go back, enter 0. To exit, enter quit. 4.5 OPTIONALLY ADDING A RADIUS SERVER Setting Up Prizm for RADIUS If your BAM operations data will be on a RADIUS server, then you must configure the Prizm server file /usr/local/canopy/prizm/config/bamconfig.xml to enable communication with the RADIUS server. The default values of this file are displayed in Figure 27. Procedure 10: Configuring the Prizm server for RADIUS server deployment 1. Open the file bamconfig.xml for editing. 2. Find the contents of the tag radius. Figure 27: Default RADIUS configuration in bamconfig.xml file Definitions of the RADIUS-specific fields in this file are provided in Table Issue 3

67 Prizm Setup Guide for Linux August 2009 Table 6: Fields of bamconfig.xml file Tag <radius>contents</radius> <enabled>contents</enabled> <primaryserver>contents </primaryserver> <secondaryserver>contents </secondaryserver> <portalias>radius</portalias> <sharedsecret>contents</sharedsecret> <maxretries>contents </maxretries> <timeout>contents</timeout> <networkinterface>contents </networkinterface> <canopyuserpassword>contents </canopyuserpassword> <lowercaseusernames>contents </lowercaseusernames> RADIUS-specific properties Meaning of Value Whether RADIUS is enabled. true means radius is enabled. You must populate this with either a valid IP address or a resolvable hostname. If you fail to do this, then the BAM subsystem in Prizm will crash when the first authentication attempt is made, and no authentications will occur. When the BAM engine starts, the RADIUS configuration is not validated. Canopy will continue to track this concern under Item ID IP Address of the secondary RADIUS server. See the explanation above for primaryserver. Service name (always radius) for RADIUS service. Shared secret between Prizm and the RADIUS Server. (This same secret is also specified on the RADIUS server.) Must be a string of 32 hexadecimal characters. Number of retries for the Prizm to send a message to the RADIUS server. Time to elapse between retries. Identifies network access server. This field identifies the network access server in access request messages. You must populate this field with a valid network interface name that is bound to an IP address (for example, eth0 or lo). Prizm finds the IP address that is associated with the network interface that you set in this field. Typically, this is the IP address of the device on which Prizm server runs. If you fail to set this field, then Prizm identifies the network access server as in access request messages. If you fail to set this field properly, then the BAM subsystem in Prizm will crash when the first authentication attempt is made, and no authentications will occur. The RADIUS configuration is not validated during the startup of the BAM engine. Canopy will continue to track this concern under Item ID Password value that is common to every subscriber, for Prizm to send to the RADIUS server. Does not need to be identical to the Administrator account password configured in the SMs. To RADIUS, the user name is the ESN (MAC address) of the SM. The value of this tag specifies whether BAM should use lowercase when it writes into its database the ESNs that it receives from the RADIUS server (and when it responds about the SMs to the RADIUS server). Issue 3 67

68 August 2009 Prizm Setup Guide for Linux 3. Set the following values for the fields of the radius tag: a. Set enabled to true. b. Set primaryserver to the dotted IP address of your RADIUS server. NOTE: The primaryserver and secondaryserver fields identify the RADIUS server. You must populate these with either a valid IP address or a resolvable hostname. If you fail to do this, then the BAM subsystem in Prizm will crash when the first authentication attempt is made, and no authentications will occur. The RADIUS configuration is not validated during the startup of the BAM engine. Until this problem is resolved, Canopy will continue to track it under Item ID c. Set sharedsecret to the same string of thirty-two hexadecimal characters that will be configured as the shared secret in also the RADIUS server. IMPORTANT! The upcoming sections of this procedure discuss the vendor attribute Motorola-Canopy-Shared-Secret, which by unfortunate coincidence also contains the expression shared secret but has no relationship to the bamconfig.xml tag described here. d. Set networkinterface to the dotted IP address of your RADIUS server. NOTE: The networkinterface field identifies the network access server in access request messages. You must populate this field with a valid network interface name that is bound to an IP address (for example, eth0 or lo). Prizm finds the IP address that is associated with the network interface that you set in this field. Typically, this is the IP address of the device on which Prizm server runs. If you fail to set this field, then Prizm identifies the network access server as in access request messages. If you fail to set this field properly, then the BAM subsystem in Prizm will crash when the first authentication attempt is made, and no authentications will occur. e. The RADIUS configuration is not validated during the startup of the BAM engine. Until this problem is resolved, Canopy will continue to track it under Item ID f. Set canopyuserpassword to the string that is common to every subscriber. g. Set lowercaseusernames as follows: FreeRADIUS does not convert case in the user names that are configured in it. A consistent policy and practice with respect to case in ESNs (user names in RADIUS) that are added to RADIUS is necessary in the FreeRADIUS implementation. The FreeRADIUS operator should either enter all ESNs in lowercase and set this value to true. enter all ESNs in uppercase and set this value to false. 68 Issue 3

69 Prizm Setup Guide for Linux August 2009 The SBR implementation differs: regardless of whether the SBR operator uses upper or lower case to enter ESNs, SBR converts them all to uppercase before sending them to BAM. The SBR operator should set this value to false. CAUTION! Following any change that you make in the bamconfig.xml file, you must restart each of the following: License Manager PrizmEMS Server Web Server the RADIUS Server each AP in which a configured SM (username) is registered each SM whose user information has been added or changed in RADIUS Setting Up a RADIUS Server for Prizm The installation tool for Prizm placed important files for RADIUS integration onto the Prizm server in the /usr/local/canopy/prizm/config/radius directory. These files are motcanopy.dct motcanopyfreeradius.dct radius_users_readme.txt samplefreeradiususer.txt The dictionary (dct) files are for transfer to the RADIUS server. The file radius_users_readme.txt explains the purpose of each of the others. This file is shown in Figure 28. Issue 3 69

70 August 2009 Prizm Setup Guide for Linux Figure 28: Contents of readme file for RADIUS users Configuration parameters that enable the RADIUS server to properly communicate with the Prizm server are specified in the Canopy dictionary file. Vendor-specific processes dictate precisely how the RADIUS server should be configured, which includes how to install the dictionary file. how to inform the RADIUS server about all of the servers that will send Access Request messages. each shared secret between the RADIUS server and the Prizm server. An example of the contents of the motcanopy.dct file is shown in Figure Issue 3

71 Prizm Setup Guide for Linux August 2009 Figure 29: Contents of motcanopy.dct file for Steel-Belted RADIUS Issue 3 71

72 August 2009 Prizm Setup Guide for Linux Figure 30: Contents of motcanopyfreeradius.dct for FreeRadius NOTE: The RADIUS integration does not support obtaining VLAN settings from RADIUS. Definitions of the Prizm-specific fields in this file are provided in Table 7. Table 7: Fields of motcanopy.dct on RADIUS server Prizm-specific Configuration Attribute Motorola-Canopy-Shared-Secret 1 Motorola-Canopy-SULDR Motorola-Canopy-SDLDR Motorola-Canopy-ULBA Motorola-Canopy-DLBA Motorola-Canopy-Enable 2 Motorola-Canopy-LPSULDR Corresponding Prizm GUI Parameter Authentication Key Bandwidth Uplink Sustained Rate Bandwidth Downlink Sustained Rate Bandwidth Uplink Burst Allocation Bandwidth Downlink Burst Allocation Authentication Account State Bandwidth Low Priority Uplink CIR 72 Issue 3

73 Prizm Setup Guide for Linux August 2009 Prizm-specific Configuration Attribute Motorola-Canopy-LPSDLDR Motorola-Canopy-HPCENABLE 3 Motorola-Canopy-HPSULDR Motorola-Canopy-HPSDLDR Motorola-Canopy-HIGHERBW 4 Motorola-Canopy-CIRENABLE 5 Corresponding Prizm GUI Parameter Bandwidth Low Priority Downlink CIR Is High Priority Channel Enabled Bandwidth High Priority Uplink CIR Bandwidth High Priority Downlink CIR Bandwidth Allow License Use none NOTES: 1. The Motorola-Canopy-Shared-Secret parameter is not the same as the shared secret between Prizm and RADIUS. The dictionary file provides this key to RADIUS so that RADIUS can pass the key to the AP, which will then validate the SM. 2. The Motorola-Canopy-Enable parameter is used to enable or suspend a user account without having to entirely delete the entry in the RADIUS server. For backward compatibility with user accounts that were already provisioned in a RADIUS server for BAM Release 2.0, the absence of this field for a user means that the account is Active. The value of this parameter is a string, where "0" = Suspend and "1" = Active. 3. The Motorola-Canopy-HPCENABLE parameter toggles whether the high priority CIR is enabled for the SM. 4. For backward compatibility with user accounts that were already provisioned in a RADIUS server for BAM Release 2.0, the absence of this field for a user means No, since BAM Release 2.0 did not support floating Cap 2 licenses. The value of this parameter is a string, where "0" = No and "1" = Yes. 5. The value of this parameter is a string, where "0" translates to 0 values for Bandwidth Low Priority Uplink CIR and Bandwidth Low Priority Downlink CIR, and the value Disabled for Is High Priority Channel Enabled. The value "1" translates to use the values of Motorola-Canopy-LPSULDR, Motorola-Canopy-LPSDLDR, and Motorola- Canopy-HPCENABLE. Issue 3 73

74 August 2009 Prizm Setup Guide for Linux The example configuration file is shown in Figure 31. Figure 31: Example RADIUS configuration file Example Setup of FreeRADIUS Version IMPORTANT! The following procedure is recommended for before setting up Prizm for RADIUS. This procedure is an example, based on FreeRADIUS Version If your RADIUS server is other than this version, then the paths to the files clients.conf, users, and dictionary (including the file names), as well as the path into which you should transfer the file motcanopyfreeradius.dct from the Prizm server, likely differ from those stated in this procedure. To set up RADIUS to interact with Prizm and store SM configuration data, perform the following steps. RECOMMENDATION: This procedure instructs you to add some exact lines of text to files. Rather than type the content of all these lines, you can use the Select Text tool in Adobe Reader. Select Tools Basic Select. Use the mouse cursor to highlight the content you wish to copy from this document, then copy and paste the highlighted content. 74 Issue 3

75 Prizm Setup Guide for Linux August 2009 Procedure 11: Setting up FreeRADIUS server for Prizm interaction and SM configuration 1. With an editor utility, open the file /usr/local/etc/raddb/clients.conf. 2. For the Prizm server and each redundant BAM server, insert the following block of lines: client PrizmServerIPAddress { secret = sharedsecret 6 shortname = DesiredAliasForPrizmServer } NOTE: Ensure that the shortname value is unique for each redundant server. 3. Save and close the file /usr/local/etc/raddb/clients.conf. 4. Open the file /usr/local/etc/raddb/users. 5. For each SM for which Prizm will forward authentication requests, insert the following block of lines: SM_MACAddress Auth-Type := Local, User-Password = "canopyuserpassword" 7 Motorola-Canopy-Shared-Secret = "AuthenticationKey", Motorola-Canopy-SULDR = "SustainedUplinkDataRate", Motorola-Canopy-SDLDR = "SustainedDownlinkDataRate", Motorola-Canopy-ULBA = "UplinkBurstAllocation", Motorola-Canopy-DLBA = "DownlinkBurstAllocation", Motorola-Canopy-Enable = "1or0", Motorola-Canopy-LPSULDR = "LowPrioritySULDR", Motorola-Canopy-LPSDLDR = "LowPrioritySDLDR", Motorola-Canopy-HPCENABLE = "1or0", Motorola-Canopy-HPSULDR = "HighPrioritySULDR", Motorola-Canopy-HPSDLDR = "HighPrioritySDLDR", Motorola-Canopy-HIGHERBW = "1or0", Motorola-Canopy-CIRENABLE = "1or0", Fall-Through = "YesOrNo" IMPORTANT! If you do not insert at least one leading tab or space on the second line of each user definition in the users file, then FreeRADIUS will fail to start and will instead return a parse error. 6 Contents of the sharedsecret tag in the bamconfig.xml file. Shared secret between BAM and RADIUS. This is a string of thirty-two hexadecimal characters. 7 Contents of the canopyuserpassword tag in the bamconfig.xml file. Common to all SMs. This is a string of any number of text characters. Issue 3 75

76 August 2009 Prizm Setup Guide for Linux For example: 0a003e000b4d 8 Auth-Type := Local, User-Password = "please_change_me" Motorola-Canopy-Shared-Secret = "e3f9bb28de", Motorola-Canopy-SULDR = "2200", Motorola-Canopy-SDLDR = "7800", Motorola-Canopy-ULBA = "4400", Motorola-Canopy-DLBA = "15600", Motorola-Canopy-Enable = "1" Motorola-Canopy-LPSULDR = "10000", Motorola-Canopy-LPSDLDR = "10000", Motorola-Canopy-HPCENABLE = "1", Motorola-Canopy-HPSULDR = "20000", Motorola-Canopy-HPSDLDR = "20000", Motorola-Canopy-HIGHERBW = "1", Motorola-Canopy-CIRENABLE = "0", Fall-Through = "Yes" 6. Save and close the file /usr/local/etc/raddb/users. 7. Open the file /usr/local/etc/raddb/dictionary. 8. Insert the following line: $INCLUDE /usr/local/etc/raddb/motcanopyfreeradius.dct 9. Save and close the file /usr/local/etc/raddb/dictionary. 10. In directory /usr/local/etc/raddb, copy the file motcanopyfreeradius.dct from /usr/local/canopy/prizm/config/radius. NOTE: This file specifies the bandwidth parameter types that are assigned values in the users file above. The motcanopyfreeradius.dct file is specifically set up to work with FreeRADIUS. IMPORTANT! The directory path to which you copy the file /etc/canopy/motcanopyfreeradius.dct should be the path in which you found the users file. 11. Open the file /usr/local/etc/raddb/radiusd.conf. 12. Find the line reject_delay = Edit the line to read reject_delay = Save and close the file /usr/local/etc/raddb/radiusd.conf. end of procedure 8 When the User-Name attribute in a received Access Request message matches this MAC address, RADIUS will retrieve the data from this particular block of lines. 76 Issue 3

77 Prizm Setup Guide for Linux August 2009 CAUTION! Following any change that you make in clients.conf, users, or dictionary, you must restart each of the following: License Manager PrizmEMS Server Web Server FreeRADIUS Server each AP in which a configured SM (username) is registered each SM whose user information has been added or changed in RADIUS Example Setup of Steel-Belted Radius (SBR) Version 6.1 If Steel-Belted Radius is already installed, skip to Procedure 13: Setting up Steel-Belted Radius for Prizm interaction and SM configurations on Page 82. If not, continue with Procedure 12. Procedure 12: Installing the trial software of SBR Version 6.1 NOTE: For brevity, some steps are omitted from this procedure. 1. When the InstallShield wizard for the trial software of this version prompts for the edition that you want to install, Select Enterprise Edition. Issue 3 77

78 August 2009 Prizm Setup Guide for Linux 2. Indicate your agreement with the terms of the end user license 3. When the wizard prompts for the feature that you want, highlight to select Radius Service. 78 Issue 3

79 Prizm Setup Guide for Linux August Optionally, to browse to a path, other than the default, where the wizard should install SBR, click the Change button and specify the path. 5. In the Custom Setup panel, click Next. RESULT: The wizard takes note of the desired destination for the software and proposes to use the Administrator of your local device as the account name for the SBR Administrator: Issue 3 79

80 August 2009 Prizm Setup Guide for Linux 6. If you want this account to have a different name, overwrite the local device Administrator name in the Account text box. 7. In the Windows Account panel, click Next. RESULT: The wizard asks which server edition you want it to configure: 80 Issue 3

81 Prizm Setup Guide for Linux August Select Install as Standalone SBR Server and click Next. RESULT: The wizard asks whether to start the service: Issue 3 81

82 August 2009 Prizm Setup Guide for Linux 9. Leave the Yes, start the Steel-Belted Radius service option checked and click Next. RESULT: The wizard prompts for whether to register the software with an RSA server: 10. Leave the Yes, I'd like to register option unchecked and click Next. 11. When the wizard prompts for whether to begin the installation, click the Install button. 12. When it indicates completion, click the Finish button. end of procedure Procedure 13: Setting up Steel-Belted Radius for Prizm interaction and SM configurations 1. Copy the file motcanopy.dct from the /usr/local/canopy/prizm/config/radius directory on the Prizm server to the /Juniper Networks/Steel-Belted Radius/Service directory. 2. Open the file /Juniper Networks/Steel-Belted Radius/Service/vendor.ini for text editing. RESULT: The displayed file contents list the vendor-product blocks in alphabetical order, as in the following example. 82 Issue 3

83 Prizm Setup Guide for Linux August At the vertical place in the file where the vendor-product Canopy would be alphabetically positioned, add the following block of content: vendor-product = Canopy dictionary = motcanopy ignore-ports = no port-number-usage = per-port-type help-id = 4. Save and close the file. 5. Open the file /Juniper Networks/Steel-Belted Radius/Service/dictiona.dcm for text editing. RESULT: The displayed contents list the available dictionary file names in alphabetical order, as in the following example: 6. At the vertical place in the file where motcanopy.dct would be alphabetically positioned, add the following 7. Reboot the device (to restart the services for both Steel-Belted Radius and Prizm). Issue 3 83

84 August 2009 Prizm Setup Guide for Linux 8. In the web browser, navigate to NOTE: If you perform this step remote to the Radius server device, use the dotted IP address of that server device in place of localhost. 9. In the web interface, click the Launch Steel-Belted Radius Administrator button. 10. Right-click on Radius Clients and select Add. 11. Enter the name, description, and IP address of the Prizm server. 12. Enter the same shared secret password that is configured in the Prizm server (see Procedure 10 on Page 66). 13. From the Make or Model drop-down options list, select Standard Radius. 14. Click OK. end of procedure Procedure 14: Assigning service plans (profiles) to SMs 1. With a session open in the Radius server interface at Port 1812, click the Launch Steel-Belted Radius Administrator button. 2. Right-click on Profiles and select Add. 3. Enter a Name and Description for the profile. 4. In the Attributes section, click on the Return List tab. 5. Click Add. 6. In the Attributes box, scroll to find attributes that begin with Motorola-Canopy-. NOTE: Table 7 on Page 72 correlates the attributes list in this box to the names that the Prizm user interface uses for them, and provides special notes about some. 7. For each attribute that you want to include in the profile, add the attribute and your desired value for it. IMPORTANT: Interactions between Radius server and Prizm server will not work unless the attribute Motorola-Canopy-Shared-Secret is added and populated by either a string of thirty-two zeros. a string identical to the Authentication Key value that has been configured into the SMs. 8. For each other profile that you want to define, repeat Steps 2 through To associate an individual SM with this profile, perform the following steps: a. Expand the Users group. b. Right-click on Native and select Add. c. For Name, enter the ESN of the SM. d. For Description, enter an expression that will help you continue to distinguish this SM from others. EXAMPLE: The value of the Site Name attribute for the SM in Prizm is distinctive and can be helpful as you later correlate Prizm data to Radius data, and thus would constitute a logical Description in Radius. 84 Issue 3

85 Prizm Setup Guide for Linux August 2009 e. For Password, enter the value of the sharedsecret tag from the bamconfig.xml file in the Prizm server. NOTE: See Procedure 10: Configuring the Prizm server for RADIUS server deployment on Page 66. f. In the Attributes box, scroll to find and select the name of the profile that you created in Steps 2 through 7 of this procedure. g. Click OK. 10. For each other SM that you want to associate with a defined profile, repeat Step 9 of this procedure. 11. Close the Administrator session in the Radius client. 12. Launch a client session in Prizm and log in. 13. For each AP in which an SM that you associated with a Radius profile is registered, perform the following steps: a. In a network browser view, select the AP. b. From the main menu, select Edit Configure Authentication Settings AP Authentication. RESULT: A Task Attributes window opens and includes an Authentication Control block of Prizm attributes in its General tab. c. From the Authentication Mode drop-down options, select Authentication Enabled. d. From the Device Configuration Source drop-down options, select BAM. e. In the Authentication Server 1 attribute, enter the IP address of the BAM server or the full Prizm server (not of the Steel-Belted Radius server). f. If you have redundant BAM capability, use the Authentication Server 2 and 3 attributes to enter the IP address of the redundant BAM server(s). g. Above the Authentication Control block, select the check box for Reboot Network Elements after update (if required to activate changes). h. Click the Run Now button. end of procedure CAUTION! Following any change that you make in the Steel-Belted Radius interface or in the motcanopy.dct file, you must restart each of the following: License Manager PrizmEMS Server Web Server each AP in which a configured SM (username) is registered each SM whose user information has been added or changed in Steel-Belted Radius Issue 3 85

86 August 2009 Prizm Setup Guide for Linux In an alternative to configuring the attributes for an SM by associating a profile with it, you can set each individual Radius attribute for the SM. However, this alternative is more time-consuming for both the initial configuration and will be more time-consuming and possibly more error-prone for the ongoing changes that follow. 4.6 SETTING UP LICENSE MANAGER Prizm Release 3.1 introduced a License Manager Administrator Tool and a similar extension to the Prizm Administrator Tool that together automate many of the administration functions that earlier required file editing and command-line execution. This setup guide presumes that you are upgrading to or you are a first-time Prizm operator setting up Server-based License Management License management technology from Macrovision, based on a FLEXnet Publisher license management model 9, provides the platform for Canopy server-based licensing. 10 Any Canopy capability that is authorized by a license on this platform is, in the lexicon of Macrovision, a FLEXenabled product. In this platform, the license management server checks for and then either assigns or declines to assign a license in real time whenever the Canopy device 11 requests one. Assigns means serves in the lexicon of Macrovision. Canopy supplies the FLEXenabled application on the Canopy device or network server. the floating license file (key) for the licensing server(s). a tool on the License Manager server(s) to give web access to an authorized administrator to set up accounts for Prizm on each of the licensing servers. validate the syntax of a new license file, push that file to all of the licensing servers, and provide a warning about any non-license files found in the license directory of any of the servers. 12 start, stop, or restart the License Manager service on the local licensing server on demand. 9 FLEXnet is a trademark of Macrovision Corporation. 10 An odd number of servers running this software is required for license assignments and license checking and a majority of these must agree on any assignment determination. 11 Canopy device or network server in this document is any whose license to operate and/or license for a particular capability is managed by the license manager under Canopy server-based license management. 12 For simplicity, the procedures that follow instruct you to use the tool embedded in the Prizm Administrator Tool to handle your license file(s). This is because you need to start the License Manager service on all licensing servers first, and that tool can do so with a single command. 86 Issue 3

87 Prizm Setup Guide for Linux August 2009 a tool embedded in the Prizm Administrator Tool to configure Prizm for License Manager. validate the syntax of a new license file, push that file to the licensing server, and provide a warning about any non-license files found in the license directory of any of the servers. start, stop, or restart the License Manager service on all of the licensing servers. provide status information for License Manager and the managed licenses. License Management Sequence The process for floating license acquisition and usage under Canopy server-based license management is as follows: 1. The operator a. designates one or three servers to act as license management servers in addition to possible other functions. NOTE: Any of these servers can operate on the Red Hat Enterprise Linux Version 4, or MS-Windows XP, or Server 2003 operating system. b. identifies the count of floating licenses required. c. submits an order that indicates both the types and counts of purchased licenses (total to be shared among the license management servers) and the hostid (MAC address) of each server that will be used as a license management server (typically, a single server; three for redundancy of licensing servers). d. receives the purchased license keys. e. installs the license manager software onto each designated licensing server (identified in Step 1a). f. uses the License Manager Administrator Tool on the web server associated with each licensing server to configure it to interact properly with Prizm and the other licensing servers (if others are deployed). g. starts the license manager service. h. uses the Prizm Administrator Tool on the Prizm server to (1) configure it to interact properly with the licensing server(s). (2) upload, configure, and push to the licensing server(s) all purchased licenses. NOTE: Although the run-time use of these licenses is floating in the network, these licenses are node locked to the hostid (MAC address) of the license management server. 2. The Canopy device requests a floating license. 3. If the majority of licensing servers find that no floating license of the type requested remains unassigned, then they reject the license request. If the majority of licensing servers find that a floating license of that type is unassigned, then they assign a license. Issue 3 87

88 August 2009 Prizm Setup Guide for Linux NOTE: Where three licensing servers are deployed, if one goes out of service, the two that remain in service continue license management because a majority (quorum) of the deployment is available. When a majority of licensing servers are not available, requests for new licenses are rejected, but previously assigned licenses remain effective. 4. The licensing server maintains a heartbeat relationship with the Canopy device. 5. If the licensed Canopy device goes out of service, then the licensing server detects this and makes the corresponding license available for reassignment. Deployment of Redundant Servers A three-server redundancy is the optimal deployment. The licensing servers share a heartbeat relationship. For this reason, ensure that they also share fast and reliable links. exist in the same subnet. have valid hostnames. NOTE: A valid hostname is the name of the machine other than localhost or localhost.localdomain. NOTE: This deployment is not for load sharing. In three-server installations, the License Manager section of the Prizm Administrator Tool automatically installs selected license files onto all three licensing servers when you perform the Action Upload License File operation. If two of the servers go down (because of failure or a reboot), the quorum is lost and can be reestablished only by restarting the servers properly. Licenses cannot be checked out, but previously assigned licenses remain assigned. Redundancy that consists of only two servers is a degraded mode of License Manager. This mode requires three-server licenses, but under three-server licensing, License Manager cannot function on a standalone server. Thus, when one of two servers goes out of service, a quorum is not automatically reestablished, and License Manager shuts down. Licenses cannot be checked out, but previously assigned licenses remain assigned. Software and License Distribution Licensing server software is available for download from the Canopy web site at the convenience of the operator, as is other Canopy software. License distribution is order based. To acquire licenses, the operator must provide to the Canopy representative the number of license management servers deployed in the Canopy network. the hostid/mac addresses of those license management servers. the number of each type of floating license desired for that Canopy network. 88 Issue 3

89 Prizm Setup Guide for Linux August Installing License Manager IMPORTANT! All servers in a redundant-server configuration must be on the same LAN. Further, license management messaging requires that their firewalls are set up for completely open port communication among them all. License Manager is supported on only x86 platforms. To install the Canopy License Manager on a device other than the one that has the Prizm server, use Procedure 8: Installing the server with X-Windows on Page 41 or Procedure 9: Installing the server without X-Windows on Page 54, selecting only the Canopy License Manager component. When the program is completed, ancillary documentation that relates to License Manager is available in the /usr/local/canopy/prizm/flexnet/docs folder. However, the Canopy License Manager implementation does not support the entire range of features and options that the document describes. For example, the procedure provided in this guide for installing licenses has precedence over any procedures that the ancillary document provides Finding the hostid (MAC Address) To derive the hostid of a server that is operating on Linux, perform the following steps. Procedure 15: Deriving the hostid on Linux 1. Log in as root. 2. At the command prompt, enter /usr/local/canopy/prizm/flexnet/lmutil lmhostid. RESULT: The system returns the MAC address in the proper form; for example: The FLEXnet Licensing hostid of this machine is 00065b40bfea. end of procedure Provide the resulting number as the hostid, along with other required data described in the following section, to the Canopy representative when ordering floating licenses Removing the Inappropriate License Manager License The installer executable for Canopy License Manager installs the configuration as single server by placing the file dummy.lic on the server(s). This allows you to verify whether each server properly performs as a standalone License Manager server after the installation. Issue 3 89

90 August 2009 Prizm Setup Guide for Linux Where you intend to deploy License Manager as a three-server configuration, after you verify proper performance, you must 1. install the three-server licenses that Canopy provides onto all License Manager servers. 2. remove any inappropriate license file(s) that the tool advises that you remove Launching the License Manager Administrator Tool The installation tool for Prizm installs the License Manager Administrator Tool and a web server on each licensing server when it installs License Manager. After the installation, invoke the tool on each licensing server and complete the Licensing Configuration form identically on each, before you move to the Prizm Administrator Tool (where you will complete a very similar form identically and upload the license[s]). For initial access to the License Manager Administrator tool on each licensing server, perform the following steps: 1. Open a browser. 2. Enter for example, The default port is Use lmadmin for username and lmpassword for password to authenticate into the tool (unless you used other than the defaults during installation. The tool opens as a web interface, as shown in Figure 32. Figure 32: License Manager Administrator Tool, opening web page The buttons in the right panel invoke the same commands as do the corresponding links in the left. The remainder of the screen captures in this section focus on the right panel. 90 Issue 3

91 Prizm Setup Guide for Linux August Configuring License Manager on the Licensing Servers When the Prizm Administrator Tool later edits a license file to reflect how to contact redundant or single-server License Manager in your system, it uses the same server ID(s), port number(s), and web server port number(s) that you enter into the Licensing Configuration panel of this tool. To access this panel, click the Configure button in the Prizm(tm) License Manager panel. An example of the resulting Licensing Configuration panel is shown in Figure 33. Figure 33: Example Licensing Configuration panel This panel sets up a single-server or redundant server configuration. Communications among the licensing server(s) and Prizm depend on the data that you enter in this form. If you check the check box for Redundant Server, the Redundancy Synchronization link is added to the left panel. This link opens the following window, which allows you to specify that the changes that you make on this server will be propagated to the other licensing servers that you have identified to the tool. Issue 3 91

92 August 2009 Prizm Setup Guide for Linux Figure 34: Redundancy Syncronization panel As in previous releases, you can identify a local or remote Licensing Server by its dotted IP address, a local server by localhost, or a remote server by its hostname. Getting or Setting a hostname on Each Licensing Server As in previous releases, you can identify a local or remote Licensing Server by its dotted IP address, a local server by localhost, or a remote server by its hostname. If you need to set or change the hostname of a computer, perform the following steps. Procedure 16: Changing a host name 1. For each license management server, choose and note a hostname to designate the server. 2. Log in as root. 3. Enter hostname <new host name>. 4. Browse to the /etc/hosts directory. 5. In an ASCII editing utility, open the file hosts. 92 Issue 3

93 Prizm Setup Guide for Linux August Beneath the line <Static IP Address> localhost, for each license management server (local and remote), add a line with the following format: <Static IP Address> <new host name> #<optional comment> NOTE: Use one or more spaces as the delimiter between these input items. EXAMPLE: lmfoo.com # my canopy lic server foo lmbar.com # my canopy lic server bar lmbaz.com # my canopy lic server baz where each line represents a different license management server. 7. If you are deploying License Manager in a redundant-server configuration, repeat this procedure (using another unique name) in every other license management server. 8. Keep note of the new host name to use as hostname in the license configuration procedure. end of procedure Configuring the Computer for Proper Port Usage Canopy License Manager uses three ports: (by default) or other designated port when configuring licenses. The Licensing Port is the one to which Prizm will send its license requests and notifications of licenses forfeited (by default) or other designated port for web access to the tool. The Webserver Port is the one that provides access when a browser navigates to the port that the vendor daemon uses. This port appears in the process list as motocnpy. The port number that motocnpy uses can change each time it is launched, which can cause a problem for some firewall users. Either of the following solutions is available for these users. Filtering Traffic by IP Address The preferred way to solve the firewall problem is to change the firewall configuration to let all traffic pass from only those IPs that must communicate with that license server: all redundant license servers any clients of the license manager (for example, PrizmEMS servers). Issue 3 93

94 August 2009 Prizm Setup Guide for Linux Configuring the Vendor Daemon for a Fixed Port CAUTION! This solution is advisable only where the firewall does not support filtering by IP address. If the fixed port you specify is already in use, 13 then the vendor daemon reverts to random port selection. The firewall may block traffic on the randomly selected port. When this occurs, License Manager fails on the server, but the daemon runs without error indication. You may be unaware that License Manager has failed. The risky way to solve the firewall problem is to configure the motocnpy vendor daemon to use a fixed port number, and then change the firewall rules to allow traffic to pass on that port. To do this, you need to use the License Manager Administrator Tool to 1. Enable Vendor Port. 2. specify the Vendor Port number. 3. Save Changes. 4.7 PREPARING Prizm FOR LICENSING Release 3.1 expanded the Prizm Administrator Tool to include a License Manager section, selectable in the left panel of the tool. This selection opens a License File Data panel on the right side of the tool interface, as shown in Figure This can occur when another program seizes the port before License Manager can or when the operating system failed to release the port after the last previous instance of running License Manager, for example. 94 Issue 3

95 Prizm Setup Guide for Linux August 2009 Figure 35: Example License File Data panel in Prizm Administrator Tool Labels in this panel are slightly different from corresponding labels in the License Manager Administrator Tool (shown in Figure 33 on Page 91). This panel configures Prizm for License Manager and enables this tool to properly edit your file(s) before propagating the license(s) to the licensing server(s). Populate this form with entries that exactly match those in the License Manager Administrator Tool on the licensing server(s). When this form is properly completed, click the Save Configuration button Starting License Manager With the proper configuration saved in the Prizm Administrator tool, select Action License Manager Start License Manager from the main menu. This starts the service on each of the licensing servers. As with any service, you can verify whether the process is running as expected Configuring and Installing License Files The License Manager section of the Prizm Administrator Tool automates the process of editing the file so that it correctly points to the license server(s). ensuring that the syntax of the file contents are appropriate. placing the license file into the appropriate directory on each licensing server. checking the expiration date of the license against the current date. Issue 3 95

96 August 2009 Prizm Setup Guide for Linux To add (configure and install) files, perform the following steps. Procedure 17: Adding license files 1. Copy the purchased license key file to anywhere that is within explore or network reach of your Prizm server. 2. Ensure that the web servers are running on the web ports of all of your licensing servers. 3. From the main menu of the License Manager section of the Prizm Administrator Tool, select Action Upload License File. 4. Browse to and select the individual file. 5. Click the Upload License File button. NOTE: If the license file is invalid, then the tool displays a message similar to If the license file is valid, then tool displays the following message: If the file dummy.lic exists in the file system, then the tool throws the following error: 6. In this case, dismiss the error window, explore to C:\Canopy\Prizm FLEXnet\license_files, and delete or rename the file dummy.lic. Then reattempt the upload of the valid license. 7. Repeat these steps for any other key files that need to be added. end of procedure 96 Issue 3

97 Prizm Setup Guide for Linux August Checking the Status of License Manager and Licenses After you use the Prizm Administrator Tool to upload and configure your license(s), use it to review status information on License Manager and your license(s). To do so, select the View License Status option from the main menu. An example of the resulting Licensing Status panel is shown in Figure 36. Figure 36: Example Licensing Status panel Issue 3 97

98 August 2009 Prizm Setup Guide for Linux 4.8 SETTING SERVER MODES (REDUNDANT Prizm CONFIGURATION) Either of the following modes is available for the Prizm server, subject to licensing: BAM-only, with a BAM server license, which manages only authentication, bandwidth service plans, and VLAN profiles of SMs. Prizm EMS, with an EMS server license, which manages attributes and data for all elements, but does not manage authentication, bandwidth service plans, or VLAN profiles. Server Redundancy Redundancy typically takes one of two forms: Full Prizm functionality with redundant BAM functionality. This is achieved by using one EMS server license and one, two, or three BAM server licenses. Only BAM functionality with redundancy. This is achieved by using two or three BAM server licenses. If you use full Prizm functionality, you should always access the GUI of the server that holds the EMS server license. This server logs the performance statistics files and defaults to its local directory. However, since this mode is enabled by a floating license, if all servers are configured to request an EMS server license (as they do by default), and if only one such license is available, then the first server that requests it is granted the only such license. You can control which server is granted the license, so that you always know what GUI to access. To do so, perform the following steps. Procedure 18: Specifying the server that should have full Prizm functionality 1. Choose the server that you want to have full Prizm functionality. 2. For this server, perform the following steps: a. Launch the Administrator Tool as follows: Linux GUI users should launch the tool from the directory /usr/local/canopy/prizm/bin directory, entering ServerAdminTool.sh. Linux console users should launch the tool from the directory /usr/local/canopy/prizm/bin directory, entering ServerAdminTool_Console.sh. b. Open the Server pane. c. For the Server Mode field, ensure that Full (EMS, BAM) is still selected. d. Click the Save button. 3. For each other server, perform the following steps: a. Launch the Administrator Tool. b. Open the Server pane. c. For the Server Mode field, change the selection from Full (EMS, BAM) to BAM Only. d. Click the Save button. 98 Issue 3

99 Prizm Setup Guide for Linux August In any order, start the servers. RESULT: The server that you want to have full Prizm functionality requests both an EMS server license and a BAM server license. The other servers each request a BAM server license. end of procedure 4.9 SYNCING TIME Appropriately interpreting trends and reports can depend on time being in sync across the network elements and the Prizm server and clients. For example, event time stamps can be unreliable for comparison where the time difference between the client and server is greater than the polling interval. Moreover, all servers that together constitute a redundant setup of at least one server under a EMS server license and a BAM server license, and at least one server under a BAM server license, must all be synchronized by Network Time Protocol (NTP) for proper interactions among each other. If you need to change the hardware time on the server clock to a setting that is more than 4 hours behind the current setting, change the setting in increments. If you set this clock to more than 4 hours behind current, you may encounter a failure of Prizm, Tomcat, and/or your database server to start upon the next boot. You can use an NTP server (in CMMmicro, for example) to provide time to not only network elements, but also your Prizm server and clients OPTIONALLY RECONFIGURING Prizm PORTS Client-Server Communications The file /usr/local/canopy/prizm/config/prizmconfig.xml contains the following default port designations: for Prizm server the range to for remote services in Prizm You can change the designations from these defaults but, in any case, you should ensure that no contention for these ports exists. If any remote service in Prizm cannot bind to a port in the designated range, the service quits. Similarly, if the Prizm server cannot bind to the single designated port, then the server process quits. When this occurs, the system displays the following type of message. 10/24/04 14:36:19 SEVERE SYSTEM Unable to bind server 10/24/04 14:36:19 SEVERE SYSTEM java.rmi.connectexception: Connection refused to host: x.x.x.x; nested exception is: java.net.connectexception: Connection refused: connect 10/24/04 14:36:19 SEVERE SYSTEM java.net.connectexception: Connection refused: connect 10/24/04 14:36:19 SEVERE SYSTEM PrizmEMS Server Failed to Start. See above errors. Issue 3 99

100 August 2009 Prizm Setup Guide for Linux This can occur because another application is launched before Prizm and binds to the port. In this case, before you attempt to restart Prizm, either edit the file /usr/local/canopy/prizm/config/prizmconfig.xml as described below, to change the port for Prizm server. end the process for this other application and, if possible, change the port that it will attempt to bind to when launching in the future. Providing remote access to Prizm from outside the firewall is not recommended. However, if you do configure Prizm for remote access, then both select non-default ports for your Prizm installation. add firewall entries such that access to these ports is limited to only the client devices that require the remote access. To change the designations from the defaults, perform the following steps. Procedure 19: Changing ports for Prizm and services 1. On the Prizm server computer, access the command prompt Enter netstat an. RESULT: The system returns a list, showing the ports that are used, with each line containing at least the following tab-separated types of fields: Protocol Local IP Address:Port Number Foreign IP Address:Port Number State 3. Examine the port numbers that are associated with Local Addresses. 4. If any are in conflict with Prizm or its local services, perform the following steps: a. Open the file /usr/local/canopy/prizm/config/prizmconfig.xml. b. If you need to change the port for Prizm server, find and edit <Prizm port="12800" >. IMPORTANT: If you change the port number, this changes access from the client browser from to c. If you need to change the range of port numbers from which services that run on Prizm can select a port to use, find and edit <services firstport="12801" lastport="12900">. d. Save and close the file. 14 In lieu of Steps 1 and 2, you may be able to obtain and use a freeware utility to display port usage in a GUI. 100 Issue 3

101 Prizm Setup Guide for Linux August 2009 e. Ensure that these newly designated ports are accessible from outside your firewall. f. Launch the Prizm server. end of procedure Server-Element Communications Prizm requires that Port 162 is open to internal networks. SNMP traps that Canopy devices send to Prizm must travel through Port 162 on the Prizm server. If a firewall on the server blocks this port, traps will not arrive and management of the system can be affected. Ensure that Port 162 is open to your Canopy management network and closed to external networks. To do this, you may find Procedure 19 helpful. Similarly, the following other ports must be open to the internal networks. Port 161 for SNMP queries and element configuration. Port 80 for browser access to element web pages. Port 23 or non-default designated port for telnet access to modules Complete List of Used Ports All ports that Prizm uses are listed in Table 8. Table 8: Ports that Prizm uses by default By default, Port is configured here and used for 20 cannot be changed active FTP in an update task. 21 cannot be changed active or passive FTP in an update task. 23 cannot be changed Prizm to access elements by telnet. 25 /config/smtp.xml Prizm to communicate with the SMTP server. 69 cannot be changed TFTP in an update task. 1 non-secure connections by the web server in 80 /bin/tomcat/conf/server.xml Prizm. 161 cannot be changed 162 cannot be changed 1080 cannot be changed 1234 cannot be changed Prizm to send SNMP queries and configurations to agents. SNMP agents to respond to queries and send traps to Prizm. SNMP proxy through the master device to the slave device web interface for discovery and refresh operations and LUID access from the AP to the SM. device authentication UDP traffic from master elements to the BAM subsystem /config/bamconfig.xml 2 RADIUS 2501 cannot be changed enabling and disabling the SM Autoupdate feature for an update task. Issue 3 101

102 August 2009 Prizm Setup Guide for Linux By default, Port is configured here and used for 3306 /config/database.xml Prizm to query a MySQL database /config/database.xml Prizm to query a PostgreSQL database. 1 non-secure connections by the web server in 7080 /bin/tomcat/conf/server.xml Prizm if Port 80 is already in use /bin/tomcat/conf/server.xml Tomcat SSL to validate requests for web proxy. 1 connections by Tomcat and the web server in 8009 /bin/tomcat/conf/server.xml Prizm /bin/tomcat/conf/server.xml 1 secure connections by the web server in Prizm /config/prizmconfig.xml client browser to access Prizm to /config/prizmconfig.xml remote services to access Prizm /config/licensing.xml Prizm to address its requests for licenses /FLEXnet/api/www/bin/ tomcat/conf/server.xml /FLEXnet/api/www/bin/ tomcat/conf/server.xml 1 /FLEXnet/api/www/bin/ tomcat/conf/server.xml 1 Tomcat server control port for License Manager web server. Local use only. No firewall access required. non-secure connections to the license web server. secure connections to the license web server /bin/tomcat/conf/server.xml Tomcat server control port for Prizm. Local use only. No firewall access required /config/prizmconfig.xml and the canopyapi entry in /etc/services EMS to BAM communication cannot be changed cannot be changed device authentication UDP traffic from BAM subsystem to master elements. SNMP proxy requests to the SM, through the AP from Prizm. NOTES: 1. Can be changed when prompted during Prizm server installation if another application is using the default port. 2. If you deploy RADIUS, create a radius entry with Port 1812 in the file /etc/services. This maps to the tag <portalias xsi:type="xsd:string">radius</portalias> in the bamconfig.xml file. 102 Issue 3

103 Prizm Setup Guide for Linux August PERFORMING THE INITIAL Prizm CONFIGURATION The installation process deposits several XML files onto the Prizm server at /usr/local/canopy/prizm/config/. Each of them contains configurable settings that you can manipulate. Those that you do not necessarily have to edit during the initial Prizm server setup are documented in the Motorola Canopy Prizm Server Administration Guide. 15 Those that are critical to the server setup are listed in Table 9. Table 9: Configurable XML files on the Prizm server Filename Controlling Described In On Page bamconfig.xml database host, user, and driver information for BAM operations Configuring Prizm for BAM 104 database.xml database host, user, and driver information for Prizm operations Configuring Prizm for the Database Configuring Prizm for the Database It is recommended that you use the server Administrator Tool to configure Prizm for the database. See Using the Administrator Tool on Page 56. A file on the Prizm server allows you to edit settings that configure Prizm for your database. You can find this file at /usr/local/canopy/prizm/config/database.xml. An example of the contents of this file are as follows: <database host=" " port="3306" user="username" password="password" dbname="prizmems" driver="mysql"> <driver name="sqlserver" driverpath="%base%/3rdparty/java/jdbc_drivers/sqlserver" profile="sqlsvr.xml"/> <driver name="mysql" driverpath="%base%/3rdparty/java/jdbc_drivers/mysql" profile="mysql.xml"/> <driver name="postgresql" driverpath="%base%/3rdparty/java/jdbc_drivers/postgresql" profile="postgresql.xml"/> </database> NOTE: The username and password in this file configure the ability for the Prizm server to connect to the database. They do not provision a user for the Prizm client. 15 These include alert.xml, maintenance.xml, networkdirectory.xml, northboundinterface.xml, notification.xml, prizmconfig.xml, and smtp.xml. Issue 3 103

104 August 2009 Prizm Setup Guide for Linux For database host, you can use an alias (a host name) instead of a fixed IP address, and then associate that alias with the IP address in the hosts file on the server. This makes later changing the IP address easy. When you do, you need to reflect the new IP address in only one file the hosts file on the server, on the line that contains the alias. For information on how to edit the hosts file, see the Motorola Canopy Prizm User Guide. Comment out the driver elements that do not apply and update your ODBC DSN. Switching from one database to another can be problematic because of how Prizm arbitrarily names and writes to statistics files. To avoid problems of data about one element being deposited into the statistics file of another when you switch to a different database while Prizm is stopped, at the same time remove all of the *.rrd files from the directory /usr/local/canopy/prizm/modules/performance/data Configuring Prizm for BAM NOTE: Unless you are deploying RADIUS, it is recommended that you skip this section and automatically update the file database.xml by using the Administrator Tool, as described under Using the Administrator Tool on Page 56. A file on the Prizm server allows you to edit settings that configure Prizm for your BAM operations. You can find this file at /usr/local/canopy/prizm/config/bamconfig.xml. The contents of this file are as follows. 104 Issue 3

105 Prizm Setup Guide for Linux August 2009 <config xsi:type="canopy:config"> <database xsi:type="canopy:database"> <driver xsi:type="xsd:string">mysql</driver> <dsn xsi:type="xsd:string">mysql</dsn> <username xsi:type="xsd:string">bost_user</username> <password xsi:type="xsd:string">bost_user</password> </database> <api xsi:type="canopy:api"> <countapiclientthreads xsi:type="xsd:int">10</countapiclientthreads> <secondsbetweenbindretrys xsi:type="xsd:int">10</secondsbetweenbindretrys> <pingtime xsi:type="xsd:int">2</pingtime> </api> <radius xsi:type="canopy:radius"> <enabled xsi:type="xsd:boolean">false</enabled> <primaryserver xsi:type="xsd:string">localhost</primaryserver> <secondaryserver xsi:type="xsd:string">localhost</secondaryserver> <portalias xsi:type="xsd:string">radius</portalias> <sharedsecret xsi:type="xsd:string">unsafe_password</sharedsecret> <maxretries xsi:type="xsd:int">3</maxretries> <timeout xsi:type="xsd:int">3</timeout> <networkinterface xsi:type="xsd:string">eth0</networkinterface> <canopyuserpassword xsi:type="xsd:string">please_change_me</canopyuserpassword> <lowercaseusernames xsi:type="xsd:boolean">true</lowercaseusernames> </radius> <server xsi:type="canopy:server"> <licenseretrievaltimeout xsi:type="xsd:int">3600</licenseretrievaltimeout> <allowlicenseunderutilization xsi:type="xsd:boolean">true</allowlicenseunderutilization> </server> </config> This file serves the same purpose in Prizm as the file canopyapi.xml did in BAM. Most tags in the radius section are defined in Table 6 on Page 67. One tag can eliminate failed authentication attempts where RADIUS servers default to case sensitive. This tag is <lowercaseusernames xsi:type="xsd:boolean">true</lowercaseusernames> If this tag is set to true, Prizm assumes that the RADIUS server is configured with MAC addresses that use lowercase alpha characters in the hexadecimal string (0 9 and a f). If it is set to false, Prizm assumes that the addresses use uppercase characters (0 9 and A F). BAM Releases 2.x assumed lowercase. So, for an upgrade from BAM and continued use of RADIUS, the default value true should be kept in this tag. Issue 3 105

106 August 2009 Prizm Setup Guide for Linux In the server section, the licenseretrievaltimeout element sets how often Prizm begins the messaging process that results in Prizm returning to License Manager any floating licenses that are no longer used. The default value for this element is 3600 seconds (1 hours). The process consumes network resources. For this reason, the value should be set to 3600 or greater. Shorter intervals put a heavy load on the network and cause frequent computation on the server. Prizm database access for BAM relies on the file /usr/local/etc/odbc.ini. In this file, you can use an alias (a host name) instead of a fixed IP address, and then associate that alias with the IP address in the hosts file on the server. This makes later changing the IP address easy. When you do, you need to reflect the new IP address in only one file the hosts file on the server, on the line that contains the alias. For information on how to edit the hosts file, see the Motorola Canopy Prizm User Guide OPTIONALLY HOSTING JAVA VM You can host Java Virtual Machine (VM) installers by setting up a folder on the Prizm server as described in Step 1 below. This sets up the server to provide Java installations to client devices that attempt server access with an unsupported or no Java version. When this occurs, the main Prizm page provides links to Download from Java Web Site (recommended) Download Virtual Machine X (as hosted on the PrizmEMS server) This makes it easier to isolate the Prizm server to a private network-only environment, without stranding clients that do not already have Java and do not have access to the Internet. To set this up in the Prizm server, perform the following steps. Procedure 20: Hosting a Client Java Runtime Installer on the Prizm server 1. On the Prizm server, create the directory %CODE_BASE/bin/tomcat/webapps/PrizmEMS/vmdownload/linux. 2. Navigate to the Java web site at 3. Download the appropriate Java Runtime Environment installer for the desired client platform. EXAMPLE: Download JRE 5.0 Update 9 as follows: a. On the client machine, create a new folder for the installer. b. Right click on the Download button for your platform. c. Select Save Target As. IMPORTANT: This alternative to a left click of the Download button prevents the.bin file for a Linux platform from being automatically opened as if it were plain text. d. Store the installer in the new folder that you created in Step 3a. 4. Also in the new folder, create a txt or html file with instructions for the platform. NOTE: These instructions are available on the download site. 106 Issue 3

107 Prizm Setup Guide for Linux August Again in the new folder, create a text file named vminfo.txt. 6. In this vminfo.txt file, add the following information: displayname=<the platform name to display> downloadfile=<the name of the installer file from Step 3d> instructions=<the name of the instructions file from Step 4> For example: displayname=windows XP/2000 (x86) downloadfile=jre-1_5_0_09-windows-i586-p.exe instructions=installwindows.txt RESULT: The Management Server (startup) page will provide a download link for the hosted installer. 7. For the other client platform (if any), repeat Steps 3 through Open your browser. 9. Launch Prizm again. 10. Verify that all of the installers are available. end of procedure 4.13 EXPANDING THE CRITERIA FIELD FOR A PostgreSQL DATABASE Operators who deploy a PostgreSQL relational database will notice over time that, upon deactivating alerts, the system throws a Java remote exception error. This results from insufficient data space in the criteria field of the table. Canopy continues to track this problem under Item ID The release notes describe the workaround for alerts that are already defined. This following workaround prevents the problem in alerts that you will be defining. Either use the PostgreSQL Administrator Tool to 1. open the Prizm database table named alert_manager_01_10_ change specifications for the column named criteria from varchar(4096) to varchar(8192) use psql to enter the following PostgreSQL command: ALTER TABLE alert_manager_01_10_00 MODIFY criteria varchar(8192) 4.14 STARTING THE Prizm SERVER Before you need the system to structure and populate the database, use one of the following two procedures. Procedure 21: Starting the Prizm server with X-Windows 1. Launch the Prizm Administrator Tool. 2. In the main menu, select Action License Manager Start License Manager. Issue 3 107

108 August 2009 Prizm Setup Guide for Linux 3. Select Action PrizmEMS Server Start. 4. Select also Action Web Server Start. end of procedure Procedure 22: Starting the Prizm server without X-Windows 1. Enter./ServerAdminTool_Console.sh to restart the Administrator Tool. RESULT: The tool opens to the first of its Menu Options consoles, as shown in Figure 19 on Page At the Please enter your value prompt, enter 7 for License Manager. RESULT: The Configure Server console opens, as shown in Figure 18 on Page In the Configure Server console, enter 1 for Start License Manager. 4. Enter 0 for Back. 5. Back in the Menu Options console, enter 1 for Start PrizmEMS Server. 6. Enter 3 for Start Web Server. end of procedure After Prizm server installation is complete, the CanopyLicenseManagerWebServer, and CanopyPrizmWebServer, and lmgrd services will automatically start. After subsequent reboots, these services and the CanopyPrizmServer will automatically start. CanopyPrizmServer does not automatically start after the installation because the values for licensing and database have not yet been set in the Administrator Tool at that point. You can also use the Administrator Tool to stop and then restart these services. This tool will always be aware of the current names for these services. 108 Issue 3

109 Prizm Setup Guide for Linux August UNINSTALLING Prizm If you ever need to uninstall Prizm, perform the following steps. Procedure 23: Uninstalling Prizm 1. Log in as root. 2. Enter cd /usr/local/canopy/prizm/flexnet/license_files. 3. If your License Manager is on the same device as Prizm, copy all of your license files (./*.*) to a safe storage directory that is not under /usr/local/canopy. 4. Enter cd /usr/local/canopy/prizm/uninstaller. 5. Enter either of the following:./uninstaller or GUI mode, or for console mode if you originally installed License Manager in console mode../uninstaller i console for console mode if you originally installed License Manager in GUI mode. RESULT: The uninstall program launches and provides on-screen instructions. 6. If prompted about any files that have been modified during installation, click Yes to All. RESULT: The uninstall program will indicate when it is finished. NOTE: If, during the original installation procedure, you specified that you wanted the setup tool to configure Firefox (to use the Java plugin that the setup tool can provide), then the uninstaller.bin tool here removed that Java plugin. 7. Click the Uninstall button. 8. Reboot the device. NOTE: This step may be required to release Port 27000, which the Prizm Administrator Tool refers to as the Server Port in its License Manager area. end of procedure Under certain circumstances, the tool may throw error messages, such as the following: Unable to remove directory: C:\Canopy\Prizm\FLEXnet Unable to remove directory: C:\Canopy\Prizm\config Unable to remove directory: C:\Canopy\Prizm\bin\tomcat\work\Catalina\localhost Regardless of whether you see messages like these, delete any contents of the Canopy directory, except the subdirectory Canopy/NetworkUpdater (if present) and its contents. Issue 3 109

110

111 Prizm Setup Guide for Linux August OBTAINING TECHNICAL SUPPORT NOTE: The contact information for Canopy Technical Support staff is included here. In most cases, you should follow the procedure of this section before you contact them. 6.1 PRELIMINARY STEPS To get information or assistance as soon as possible for problems that you encounter, use the following sequence of actions: 1. If the problems constitute an emergency, call Canopy Technical Support at (or ) or contact another technical support organization if one has been designated for you. 2. Search this user guide and the software release notes of supported releases a. in the Table of Contents for the topic. b. in the Adobe Reader search capability for keywords that apply Visit to view the Canopy Knowledge Base. 4. Ask your Canopy products supplier to help. 5. If any logs and messages have been generated, view and analyze event logs, error messages, and debug messages to help isolate the problem. 6. Check Canopy system release notes to verify that all of your Canopy equipment is on the correct software release. 7. Where appropriate a. verify element connectivity (physical cabling). b. at the SM level, minimize your network configuration (remove home network devices to help isolate problem). c. perform site verification checklist(s). 8. If you are a Linux GUI user, attempt to launch the Administrator Tool from the directory /usr/local/canopy/prizm/bin directory, entering ServerAdminTool.sh. If you are a Linux console user, attempt to launch the tool from the directory /usr/local/canopy/prizm/bin directory, entering ServerAdminTool_Console.sh Reader is a registered trademark of Adobe Systems, Incorporated. 17 During the installation, the prizmsetup tool placed this tool in the bin directory and made it executable. Issue 3 111

112 August 2009 Prizm Setup Guide for Linux 9. If the Administrator Tool launches, either select Help Support Information from the tool GUI or use the console to select options for starting the Prizm server and accessing the support tool. 10. Refer to the following section, Technical Support Information Tool, to determine how to best use this tool, based on the symptoms that you are experiencing in Prizm. end of procedure 6.2 TECHNICAL SUPPORT INFORMATION TOOL Prizm provides a tool for the administrator on the server to launch when trouble exceeds local diagnostic efforts. This tool assembles into a single encryptable file most of the information that Canopy Technical Support requires to diagnose typical problems encountered in Prizm installation and setup. The tool also allows the administrator to split the file to enable or speed up transmittal for data that exceeds 1 MB. IMPORTANT! If your file is 1.5 MB or greater in size, you must use the split option. The resulting files must be smaller than 1.5 MB. Otherwise, the tool will throw an error, and the file will not be sent by . Depending on whether the tool is launched from the client application or the Prizm server, the data may include element web pages from elements that are selected in the interface when the tool is launched. whatever data Prizm stores about those selected elements. event logs, if elements are selected. the system log. license file contents and usage. the platform and environment on which the Prizm server operates. device templates, including any that were locally created or modified. Prizm configuration (all xml) files. installation logs. the identification of all running processes. additional information that you voluntarily enter in the interface to the tool. So, if the tool is launched from both the client and the server, then the composite of the data files that the tool produces can include all of the above listed information. By default, the tool stores the output file(s) under the directory where you installed Prizm on the server, in the subdirectory...modules/supportinfo/files/login_id. From the server, the tool specifically collects the types of information that are listed in Table Issue 3

113 Prizm Setup Guide for Linux August 2009 Table 10: Information collected by Technical Support Information Tool on server Information Type Configuration Database Device Licensing Log Network Information Collected Server Configuration Configuration Data JDBC Information ODBC Configuration Device Template MIB Files Licensing Information License Status Server Logs Installation Logs Network Configuration Network Service Information Boot Information Environment Information Disk File System Information Kernel Information Server Platform OS Log Data Mail Information Miscellaneous Data Process Information RPM Information Services Information Documentation on the tool interface in the Prizm server is provided in the Motorola Canopy Prizm Server Administration Guide. Issue 3 113

114

115 Prizm Setup Guide for Linux August 2009 APPENDIX A: REFERENCE INFORMATION LICENSE AGREEMENT The use of of the Prizm product is only under the terms and conditions that are quoted in the section titled "License Agreement" of the Motorola Canopy Prizm User Guide and in the click-wrap version of the same. TRADEMARKS MOTOROLA and the stylized M Logo are registered in the U.S. Patent & Trademark Office. All other product or service names are the property of their respective owners. Java and all other Javabased marks are trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation; and Windows XP is a trademark of Microsoft Corporation. Netscape is a registered trademark of Netscape Communication Corporation. Canopy is a registered trademark of Motorola, Inc. Motorola, Inc Canopy Wireless Broadband 1299 East Algonquin Road Schaumburg, IL USA Motorola, Inc Issue 3 115

116

117 Prizm Setup Guide for Linux August 2009 APPENDIX B: HISTORY OF DOCUMENTATION This section is a placeholder for the event that this guide is reissued twice with new or corrected information. Issue 3 117