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