Avaya Integrated Management Release 5.2 System Management Installation and Upgrade
Issue 5 May 2009
© 2009 Avaya Inc. All Rights Reserved.
Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases.
For full legal page information, please see the complete document, Avaya Legal Page for Software Documentation, Document number 03-600758. To locate this document on the website, simply go to http://www.avaya.com/support and search for the document number in the search box.
Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User.
Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages.
Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site: http://www.avaya.com/support
Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law.
Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://www.avaya.com/support
Contents
Chapter 1: Introduction ...... 5 Purpose...... 5 Prerequisites ...... 5 Intended audience ...... 5 Conventions used in this book ...... 6 Support resources...... 6 Avaya Technology and Consulting ...... 6 Avaya Professional Services ...... 6 Avaya Global Services Delivery ...... 8 Avaya Global Technical Services...... 8 Customized management solutions for Avaya Integrated Management. . . . 8 Avaya contact information ...... 9 Product documentation ...... 9 How to access books on the Web ...... 9
Chapter 2: Overview ...... 11 System Management ...... 11 New SM installation and upgrade features...... 11 System Management CD ...... 11 Preinstallation tasks ...... 12
Chapter 3: System Management Installation ...... 13 Overview ...... 13 Linux server requirements ...... 13 Client PC requirements ...... 14 Verifying the current Red Hat Linux version ...... 15 Configuring the /etc/hosts file ...... 15 Configuring the openLDAP server ...... 16 Installating an SM application in a customer specified directory ...... 16 Generating a random password for the SM administrator user ...... 16 Using the randomly generated password ...... 17 System Management upgrade installations ...... 18 Upgrading multiple Linux servers ...... 19 Installing the software in console mode ...... 20 Upgrading to Release 5.2 ...... 21 Installing Release 5.2 ...... 27 Auditing the Fault and Performance Manager database ...... 32 Configuring the Integrated Management Database ...... 32
Issue 5 May 2009 3 Contents
Backing up System Management...... 33 Backing up data using the GUI utility ...... 33 Scheduling backups using the GUI utility ...... 34 Cancelling scheduled backups using the GUI utility ...... 36 Backing up data using the Command Line method ...... 36 Restoring System Management ...... 37 Restoring data using the GUI utility ...... 37 Restoring data using the Command Line method...... 38 up2date or YUM support for Red Hat Linux platforms ...... 39 Issue ...... 39 Resolution ...... 39 Uninstalling System Management ...... 40 Allowing Avaya Services remote access...... 41 Configuring the Integrated Management server ...... 42 Changing an application link on the Avaya Integrated Management Launch Page ...... 42 Changing security settings ...... 43
Appendix A: Linux server installation ...... 45 Overview ...... 45 Installing Red Hat Enterprise Linux 5.0 ...... 45 Installing RHEL in the text mode ...... 49 Upgrading Red Hat Enterprise Linux ES 4.0 or AS 4.0 to Red Hat Enterprise Linux 5.0 ...... 50 Using kickstart for Red Hat Enterprise Linux installations ...... 51 Selecting an installation method ...... 51 CD-ROM ...... 51 HTTP ...... 52 Diskette ...... 52 Initiating a kickstart installation ...... 52 Starting a kickstart installation ...... 53 Verifying installation of required RPM files ...... 53 Installing required RPM files ...... 54 RPM files installed by System Management R5.2 ...... 55 Warning for unsupported versions of third-party RPMs ...... 55 Security considerations ...... 56
Index ...... 57
4 Avaya Integrated Management System Management Installation and Upgrade Chapter 1: Introduction
Purpose
This book provides the following information:
l Hardware and software requirements for Linux servers.
l Preinstallation tasks to be completed before installation.
l Procedure to install System Management products on the Linux server.
Prerequisites
System administrators who install the System Management software should be experienced in installing software on Linux operating systems in a converged network environment.
Intended audience
This guide is meant for the use of system administrators who are responsible for installing software on Linux servers.
May 2009 5 Introduction
Conventions used in this book
The following typographical conventions are used:
l Bold type is used to indicate selections from menus, buttons in a window, and the Enter key on the keyboard. It is also used for emphasis.
l Courier bold font is used to indicate commands that you type.
l Courier bold italic font is used to indicate variable information within the commands that you type.
l Courier font is used to indicate information that appears as command results, or ouput.
l Arrows indicate options that you select from cascading menus; for example, Click File > Open means click the Open option from the File menu.
Support resources
Avaya provides many planning, consulting, and technical services. The following sections describe the resources and services that are available to Avaya customers.
Avaya Technology and Consulting
Avaya Technology and Consulting (ATAC) works with client teams to develop detailed solutions for connectivity to Avaya Communication Manager solutions. ATAC also designs network configurations. Due to configuration complexities, we strongly recommend that you contract for professional implementation services for the following Avaya Integrated Management products:
l Avaya MultiSite Administration
l Avaya Fault and Performance Manager
Avaya Professional Services
The Avaya Professional Services (APS) team of Avaya Integrated Management (AIM) consultants offers customers the following services:
l Platform readiness verification
l AIM architectural planning, design, and overview
6 Avaya Integrated Management System Management Installation and Upgrade Avaya Professional Services
l Remote turnkey implementation and installation
l AIM server configuration
l Customer acceptance verification
l Custom on-site services
l On-site and remote knowledge transfer The APS Data Group consists of the following teams:
l Avaya Integrated Management Consultants The Avaya Integrated Management (AIM) consulting team offers planning, design, implementation, consulting, and knowledge transfer services for the entire Avaya Integrated Management suite. This includes ASA, Val Manager, VMM, NMC with SUM, MSA, and FPM. The thrust of the APS team is to bring the correct methodology to these complex application deployments that span various regions, and to provide continuity to the overall project. Through proper integration and consulting, our customers can leverage the AIM suite to lower the total cost of ownership, and proactively manage their VoIP network comfortably and confidently.
l Data Network Implementation Engineering The Data Network Implementation Engineering (formerly RNIS) team implements and upgrades or upgrades, existing or new data networks. This team analyzes the network design requirements and performance expectations of the customer. The team then creates the hardware and software installation specification used to implement data devices that include Cajun, VPN, Wireless LAN, Secure Gateways, Extreme, Juniper, and multivendor data equipment. The APS Data Group provides support on a contract basis. Contact your local Avaya Account Team or Business Partner to purchase any implementation offer from the team. For more information, see Table 1: Customer-Accessible Resources on page 9, or contact Jon Machak at 248-213-3788 or [email protected]
May 2009 7 Introduction
Avaya Global Services Delivery
Avaya Global Services Delivery (GSD) provides support to the Avaya Integrated Management client teams, field technicians, and customers. GSD will bill customers for support on a time and materials basis if the following conditions exist:
l Customers do not provide remote access.
l Customers do not have a current maintenance agreement.
l Customers do not procure and install the required systems and software as defined in the Avaya Integrated Management Services Support Plan.
l Customers request support that is outside the purchase agreement. GSD does not support hardware or software that customers purchase from third-party vendors.
Avaya Global Technical Services
Avaya Global Technical Services answers customer calls about products in Avaya Integrated Management. They will either answer your questions directly, or connect you with an associate who can answer questions about the products.
Customized management solutions for Avaya Integrated Management
The Integrated Management Product Team understands customers’ needs and is focused on customer satisfaction. See Table 1: Customer-Accessible Resources on page 9 for contact information. The Product Team assists customers with Avaya Integrated Management projects and provides:
l Project Management — An Integrated Management project person will work with the customer to access configuration and customization requirements for any or all applications within each Avaya Integrated Management offer. If custom work is required, the evaluation will include a proposed statement of work and price. Note that this offer is not intended to provide installation for customers who choose to implement Integrated Management applications using Avaya Services or third-party implementation services.
l Training — Basic training can be performed remotely using an interactive medium to display the applications and a conference bridge for audio. On-site training can be customized to meet the customer’s needs. Customized training will focus on application functionality that is relevant to the customer and provide focused knowledge transfer to facilitate application-specific training.
8 Avaya Integrated Management System Management Installation and Upgrade Product documentation
Avaya contact information
Table 1 provides contact information that you may use if you need assistance during the process of installing and setting up Avaya Integrated Management.
Table 1: Customer-Accessible Resources
Resource Contact Information
Avaya Support Center http://www.avaya.com/support Avaya Global Technical +1 800 242-2121, extension 15921 Services Avaya Professional +1 800 730-9108, prompt 3 Services (APS) Integrated Management Send email to: [email protected] Product Team Toll Fraud Intervention +1 800 643-2353, prompt 1
Product documentation
The latest version of Avaya Integrated Management product documentation, including this guide, is available from the Avaya Support Web site. To view or download these books from the Web, you need access to the Internet, an Internet browser, and Adobe Reader. Adobe Reader 8.0 is provided on the System Management CD and is also available from http:// www.adobe.com. See How to access books on the Web for instructions on how to view or download these books.
How to access books on the Web
To view or download books from the Avaya Support Web site: 1. Access http://www.avaya.com/support. 2. Click Find Documentation and Technical Information by Product Name. 3. Click the letter I in the alphabet listing.
May 2009 9 Introduction
4. Click the Integrated Management - All Applications link under the letter I in the alphabet listing. 5. Under DOCUMENT CATEGORIES, click View all documents to display a list of available books for the offer. 6. Click on any title under Title to view a particular document.
10 Avaya Integrated Management System Management Installation and Upgrade Chapter 2: Overview
System Management
Avaya Integrated Management Release 5.2 System Management is the premier solution to manage large converged networks. This offer includes Avaya Integrated Management advanced management tools. It is designed to run on the Red Hat Linux operating system. Combined with the other Avaya Integrated Management Release 5.2 offers (Administration Tools, Enterprise Network Management, and VoIP Monitoring Manager) you have the full complement of products to administer the myriad of features in Avaya Communication Manager; monitor your entire voice and data network from a central location; and manage the Avaya network switches and IP endpoints. For highlights of the new and enhanced features, or enhanced features provided in Avaya Integrated Management Release 5.2 System Management, see Avaya Integrated Management Release 5.2 Overview, document number 14-601718.
New SM installation and upgrade features
SM release 5.2 introduces the following enhancements:
l Support for installations of the SM applications, IMD, MSA and FPM, in customer specified directories
l up2date or YUM support for Red Hat Linux platforms
l Ability to issue warnings to users for unsupported versions of third party RPMs
l Ability to generate random passwords for the SM administrator users
System Management CD
The System Management CD provides the following Integrated Management applications:
l Avaya Multisite Administration
l Avaya Fault and Performance Manager
l Avaya Integrated Management Database
May 2009 11 Overview
The System Management CD also provides the following components:
l PostgreSQL Database System
l PHP support for PostgreSQL
l Integrated Management Linux Maintenance Package
l Avaya Integrated Management Launch Page
l Red Hat Linux Binary Compatibility Libraries
l Java Runtime Environment
l Apache Tomcat Web Server
l Adobe Reader (required to view documents)
Preinstallation tasks
Before you install Avaya Integrated Management Release 5.2 System Management, you must complete the following preinstallation tasks. 1. Check the minimum hardware and software requirements for the Linux server. For details see Linux server requirements on page 13. 2. Check that there are installations of all previous sequential upgrades and major releases, or the major releases, before you install this release. 3. Configure the /etc/hosts file. For configuration details, see Configuring the /etc/hosts file on page 15.) 4. Carefully review Avaya Integrated Management Implementation Guidelines, document number 555-233-163. This document is available on the Avaya Support Web site. For instructions to access books, see How to access books on the Web on page 9. This document describes server configuration requirements and provides preinstallation forms that must be completed before you begin the installation of the Avaya Integrated Management products. 5. If a previous release of any product included in the System Management (SM) offer is already installed, those products will be upgraded to the current release when you install the Avaya Integrated Management 5.2 System Management CD. 6. Carefully review this book before you start the Linux server installation.
12 Avaya Integrated Management System Management Installation and Upgrade Chapter 3: System Management Installation
Overview
This chapter describes the minimum hardware requirements for the Linux server and Client PC and provides the procedure to install System Management Release 5.2 on the Linux server. It also provides procedures for upgrade and new installations.
Linux server requirements
Table 2 provides the minimum requirements for the Linux servers.
! WARNING:
WARNING: You must install the latest bug fixes and security patches in order to keep your Linux operating system up to date. Failure to do so may leave your server vulnerable to attack and possible compromise.
Table 2: Red Hat Enterprise Linux Server Minimum Requirements
Component Required Comments
Operating Red Hat Enterprise Linux R5.0 Supports only English operating System (32-bit and 64-bit x86 version) systems. Red Hat Enterprise Linux ES R4.0 Red Hat Enterprise Linux R5.0 (32-bit and 64-bit x86 version), or is required for new installations. Red Hat Enterprise Linux AS R4.0 For more information, see (32-bit and 64-bit x86 version) Verifying the current Red Hat Linux version on page 15. Note: You can install System Management on VMWare that runs one of the supported operating systems. Processor 3.0 GHz Pentium® 4 or AMD equivalent Supports a maximum of two processors. Hard drive 40 GB Memory 2.0 GB RAM 1 of 2
May 2009 13 System Management Installation
Table 2: Red Hat Enterprise Linux Server Minimum Requirements (continued)
Component Required Comments
Network TCP/IP 100 Mbit Network Card Connectivity Modem 56K external modem connected to Optional COM1 for remote access Web Browser (Optional) Mozilla Firefox 3.0 Linux Web client is not supported. CD-ROM Drive Required for installation. Monitor SVGA 1024 X 768 display 2 of 2
Client PC requirements
After you install the applications on the Linux server, you can either access the applications from the Linux server or use a Web browser to access the applications from a Windows client PC. The client PC must meet the minimum requirements listed in Table 3. Table 3: Microsoft Windows Client PC Minimum Requirements for System Management
Component Required Comments
Operating System Microsoft Windows 2000 server with Service Pack 4, Microsoft Windows 2000 Professional with Service Pack 4, Microsoft Windows XP Professional with Service Pack 2, Microsoft Windows 2003 Standard Edition server with Service Pack 2, Microsoft Windows 2003 Enterprise Edition server with Service Pack 2, Microsoft Windows Vista Business (32-bit and 64-bit editions), or Microsoft Windows Vista Enterprise (32-bit and 64-bit editions) Processor 1.5 GHz Pentium® 1 of 2
14 Avaya Integrated Management System Management Installation and Upgrade Verifying the current Red Hat Linux version
Table 3: Microsoft Windows Client PC Minimum Requirements for System Management
Component Required Comments
Hard Drive 40 GB Required to install all of the client components Memory 1 GB RAM For Microsoft Windows Vista Business or Vista Enterprise operating system, the minimum memory requirement is 2 GB RAM. Monitor SVGA 1024 X 768 display Network TCP/IP 10/100 Network Card Connectivity Modem 56K Modem (Optional) May be required for remote access to the client PC CD-ROM Drive Required for installation Other Software Internet Explorer 6.0 with Service Pack 1 Required to access the or Internet Explorer 7.0 and Java Runtime Integrated Management Environment 1.5.0_11 (Java Runtime Launch Page and Environment 1.5.0_11 is provided.) Web-based clients Mozilla Fiefox version 3.0 2 of 2
Verifying the current Red Hat Linux version
To verify the current Red Hat Linux version: 1. Right-click the mouse and select Open Terminal to display a terminal emulation window. 2. In the terminal emulation window, type rpm -qa | grep -i redhat-release. 3. Press Enter.
Configuring the /etc/hosts file
On RHEL, an incorrectly configured /etc/hosts file occasionally causes IMDAddApp or mfpmconfig failure.
May 2009 15 System Management Installation
Before you install SM, ensure that you configure the etc/hosts file for SM the following way. 127.0.0.1 localhost.localdomain localhost 135.27.155.141 vmwaremsa1.ccdsv.com vmwaremsa1
Configuring the openLDAP server
You must exercise caution when you configure the openLDAP server.
! CAUTION:
CAUTION: Do not configure the OpenLDAP or any other server on a machine where you installed SM applications. If you configure the openLDAP server on the server on which you configured MSA or FPM, the configuration does not work.
Installating an SM application in a customer specified directory
IM Release 5.2 supports the installation of a System Management (SM) application, IMD, MSA or FPM, in a customer specified directory. The default directory continues to be /opt/avaya, but the System Management installer makes provision for users to specify an alternate directory to install third party applications on the Linux server. Note:
Note: The equivalent for the directory /opt in release 5.2 is < install location >.
Generating a random password for the SM administrator user
Earlier versions of IM had admin123 as the predefined password for the administrator password. This predefined password compromised password security. IM 5.2 enhances password security with a mechanism that replaces the predefined password for the administrator user in the SM 5.2 installer. The new mechanism provides the user the options to:
l specify a password
16 Avaya Integrated Management System Management Installation and Upgrade Generating a random password for the SM administrator user
l leave the password field blank so that the system can generate a randon password Note:
Note: Support for this feature is available only for fresh IM 5.2 installations and the system displays a message to this effect on the installer screen. The system also displays the message during an installation in the console mode. Support for this feature does not extend to upgrades. During the SM installation, the system displays a prompt for the administrator user. At the prompt, the administrator user can specify a password. The password that the user specifies must be alphanumeric, atleast eight characters long, without special characters, and without spaces. If the user leaves the password field blank, the system generates the IMD administrator a random password and the user can retrieve it as the variable AIM_ADMIN from the file /opt/ avaya/VisAbility/html/im_env.props. During the installation, the IMD Location selection screen displays the following information:
l The location of the administrator password The system stores the password as the variable AIM_ADMIN in the file /opt/avaya/ VisAbility/html/im_env.props.
l The information that helps the user use the password Note:
Note: The equivalent for the directory /opt in release 5.2 is < install location >.
Using the randomly generated password
To use the randomly generated password: 1. Complete a fresh IM 5.2. installation. 2. Retrieve the random password from the file im_env.props as the variable AIM_ADMIN. 3. Use this password to log in to IMD. IMD accepts this password and the system displays the change password message.
May 2009 17 System Management Installation
System Management upgrade installations
If the Linux server already has Avaya MultiSite Administration, or Avaya Fault and Performance Manager, and Avaya Integrated Management Database installed on it, the Avaya Integrated Management Release 5.2 System Management CD will upgrade the products to the current release. You must install Integrated Management Database on the same server where you installed the previous release. If you installed it on a remote computer, be sure to install the new release on the same computer. When the system prompts you for the location of the Integrated Management Database, accept the default setting. Note:
Note: Use the command, IMDLocation -c to determine the current location of Integrated Management Database. You will find this command in the < install location > imd/bin/ directory. The Linux operating system offers two options for an upgrade installation:
l You may upgrade the System Management products to the current release on the same operating system.
l You may upgrade the System Management products to the current release and a new operating system needs to be installed. See Table 2: Red Hat Enterprise Linux Server Minimum Requirements on page 13 for supported operating systems. For both options, you must back up the database and configuration information for any product already installed. If you want to upgrade the System Management applications to Integrated Management 5.2 and the operating system to Red Hat Enterprise Linux R5.0, use the following steps: 1. Upgrade the System Management applications to Integrated Management 5.2. For upgrade instructions, see Upgrading to Release 5.2 on page 21. 2. After you complete the upgrade, back up the Integrated Management 5.2 data, and send this backup via FTP to an alternate machine. 3. Upgrade your operating system to Red Hat Enterprise Linux R5.0. For upgrade instructions, see Upgrading Red Hat Enterprise Linux ES 4.0 or AS 4.0 to Red Hat Enterprise Linux 5.0 on page 50. 4. After you complete the upgrade, reinstall Integrated Management 5.2. 5. After you reinstall Integrated Management 5.2, restore the Integrated Management 5.2 data you backed up in Step 2 of this procedure.
18 Avaya Integrated Management System Management Installation and Upgrade Upgrading multiple Linux servers
Note:
Note: When you upgrade the Linux operating system, the system name, IP address, and DNS domain on the new operating system must be the same as on the old operating system. If you change this information during a Linux operating system upgrade, the change may render the new Integrated Management 5.2 upgraded system unusable. For information on upgrading the Linux server, refer to Upgrading Red Hat Enterprise Linux ES 4.0 or AS 4.0 to Red Hat Enterprise Linux 5.0 on page 50 . For additional support, refer to your Red Hat operating system documentation or contact your Red Hat support vendor. Recommendation: Avaya recommends that you install Linux-based products on Red Hat Enterprise Linux R5.0 servers as described in the following supported configurations: Support for up to 120 voice systems (single server) — Avaya MultiSite Administration, Avaya Fault and Performance Manager, and Avaya Integrated Management Database installed on one Linux server can support up to 120 voice systems.
l Support for up to 300 voice systems (multiple servers) — install the Linux-based products on a primary Linux server and two secondary Linux servers as follows: - Primary Linux server — Avaya Integrated Management Database supporting 300 voice systems and Avaya Fault and Performance Manager supporting 100 voice systems. - Secondary Linux server — Avaya Fault and Performance Manager supporting 100 voice systems. - Secondary Linux server — Avaya Fault and Performance Manager supporting 100 voice systems.
Upgrading multiple Linux servers
If the System Management applications run on multiple Linux servers in your enterprise, install the System Management Release 5.2 applications on the servers in the order given. This means that you install System Management Release 5.2 and run the installation wizard several times in order to install each application in the correct order, on the correct server. Install the System Management Release 5.2 applications in the following order: 1. Avaya Integrated Management Database 2. Avaya Fault and Performance Manager (primary data collection server) 3. Avaya Fault and Performance Manager (secondary data collection server) 4. Avaya Multisite Administration
May 2009 19 System Management Installation
Installing the software in console mode
You can install System Management Release 5.2 from the terminal emulation window instead of using the graphical user interface (GUI) installation wizard. The terminal emulation window provides prompts and questions identical to those of the GUI installation wizard except that the prompts are text based. To install System Management Release 5.2 in console mode, use the following steps: 1. Ask all users to log off the system. 2. Log in as root on the Linux server where the System Management applications reside. Note:
Note: If you are not logged in as root, execute the su - root command to enable root permissions and the root environment. 3. Insert the Avaya Integrated Management 5.2, System Management CD into the CD-ROM drive of the Linux server. 4. Right-click the mouse and select Open Terminal to open a terminal emulation window. 5. Perform one of the following steps:
l If you install the software on a Linux server that runs Red Hat Enterprise Linux Release 4.0: a. In the terminal emulation window, type mount /media and press Enter. Note:
Note: Depending on your operating system settings, the CD may mount automatically. b. Type cd /media/cdrom and press Enter.
l If you install the software on a Linux server that runs Red Hat Enterprise Linux Release 5.0: a. In the terminal emulation window, type mount /media/Avaya_System_Mgmt and press Enter. Note:
Note: Depending on your operating system settings, the CD may mount automatically. b. Type cd /media/Avaya_System_Mgmt and press Enter. 6. In the terminal emulation window type bash ./IM5.2_setup.bin -- -console and press Enter.
20 Avaya Integrated Management System Management Installation and Upgrade Upgrading to Release 5.2
7. Use one of the following steps:
l If this is an upgrade installation, see Step 6 in Upgrading to Release 5.2 on page 21.
l If this is a new installation, see Step 6 in Installing Release 5.2 on page 27. The prompts are identical to those the GUI provides, except that they are text based. Note:
Note: If you install Avaya Fault and Performance Manager, you must configure Fault and Performance Manager after you install System Management Release 5.2. The terminal emulation window does not display prompts to configure Fault and Performance Manager during the installation as the GUI installation wizard does. See Avaya Fault and Performance Manager Release 5.2 Configuration, document number 555-233-130, to configure Fault and Performance Manager.
Upgrading to Release 5.2
! SECURITY ALERT:
SECURITY ALERT: During the installation, the installation wizard turns off the internal firewall around the Linux server. This allows internal users to telnet to the Linux server and to use their Web browser to access the Windows clients. Do not turn on the internal Linux firewall after the installation. Your network firewall provides the needed security to prohibit access to the Linux server to outsiders. This section describes how to install System Management Release 5.2 on a Linux server where you already installed System Management Release 5.0. 1. Ask all users to log off the system. 2. Log in as root on the Linux server where the System Management applications reside. Note:
Note: If you are not logged in as root, execute the su - root command to enable root permissions and the root environment. 3. Insert the Avaya Integrated Management 5.2, System Management CD into the CD-ROM drive of the Linux server. 4. Right-click the mouse and select Open Terminal to open a terminal emulation window.
May 2009 21 System Management Installation
5. Use one of the following steps:
l If you install the software on a Linux server that runs Red Hat Enterprise Linux Release 4.0: a. In the terminal emulation window, type mount /media and press Enter. Note:
Note: Depending on your operating system settings, the CD may mount automatically. b. Type cd /media/cdrom and press Enter.
l If you install the software on a Linux server that runs Red Hat Enterprise Linux Release 5.0: a. In the terminal emulation window, type mount /media/Avaya_System_Mgmt and press Enter. Note:
Note: Depending upon your operating system settings, the CD may mount automatically. b. Type cd /media/Avaya_System_Mgmt and press Enter. 6. In the terminal emulation window, type bash ./IM5.2_setup.bin and press Enter. The system displays the Welcome dialog box. 7. Click Next. The system displays the Backup Integrated Management Data dialog box. 8. Use one of the following steps:
l To back up the application data, click Back up the application data. The system stores the data locally at /var/avaya/IM5.2.
l To proceed without backing up the application data, click Do NOT back up the application data. 9. Click Next.
l If you chose to proceed without backing up the application, the system displays the Backup Location for Integrated Management Data dialog box. For directions, see Step 10. a. IWhen the back up is complete, the system displays the Backup Location for Integrated Management Data dialog box. For directions, see Step 10. 10. Use one of the following steps:
l To store the data locally, click Store the data locally on this computer.
l To store the data on another computer, click Store the data remotely on another computer.
22 Avaya Integrated Management System Management Installation and Upgrade Upgrading to Release 5.2
Note:
Note: If you choose to store this data on another computer, make sure there is sufficient space on the computer. 11. Click Next.
l If you chose to store the data locally, the system displays the Selection Installation Type dialog box. For directions, see Step 12.
l If you chose to store the data on another computer, the system displays the Remote Machine Information dialog box. Use the following steps: a. Enter the IP address for the remote machine. b. Enter the FTP login name for the remote machine. c. Enter the FTP password for this login name. d. Enter the Destination folder where the data will be stored on the remote machine. Note:
Note: The system must have a Destination folder. If access restriction applies, make sure you specify the full path. e. Click Next when you are finished entering the remote computer information. The system displays the Select Installation Type dialog box. 12. Perform one of the following steps:
l To install all of the applications, click All, and then click Next. The system displays the Location of the Integrated Management Database dialog box. For directions, see Step 13.
l To specify the applications you want to install: a. Click Custom, and then click Next. The system displays the Select Products to be Installed dialog box. b. Select the check box for each application you want to install, and then click Next. The system displays the Location of the Integrated Management Database dialog box. For directions, see Step 13.
May 2009 23 System Management Installation
13. Perform one of the following steps:
l To install Integrated Management Database on this computer, click Install the database locally on this machine, and then click Next.
l If you installed Integrated Management Database on a remote computer, click Install the database remotely on another machine. Enter the IP address of the remote computer, and click Next. Note:
Note: If you select this option, it does not install the Integrated Management Database on a remote computer. However, the wizard requests the IP address of the remote computer so that the products on this computer can connect to Integrated Management Database on the remote computer. Install the new release of Integrated Management Database in the same location where you installed the previous release. If you installed the previous release of Integrated Management Database on a remote computer, when the system displays the prompt for the IP address of the remote computer, accept the default setting that appears. The system displays the Fully Qualified Domain Name dialog box. 14. Enter the fully qualified domain name if the system displays the incorrect name, and click Next. The system displays the Choose your Security Mode dialog box. Note:
Note: The new implementation of the IMR5.2 launch pages necessitates either of two actions when you want to launch MSA, IMD or FPM on any Windows client when you install System Management in the SSL mode:
l make the entry in drivers\etc\hosts Enter the server IP address and server host name, for example, 135.27.155.101 rhel4es32-1.apac.avaya.com, in the hosts file in the etc folder within Drivers.
l register the machine in the DNS server Alternatively, you can ask the DNS administrator to add the machine to DNS. 15. Read about SSL. Then click Secure Socket Layer (SSL) enabled or Secure Socket Layer (SSL) disabled, and click Next. The default is Secure Socket Layer (SSL) enabled. The system displays the Windows Server Application Information dialog box. 16. Perform the following steps: a. Enter the IP address/FQDN of the Windows server running Network Management , if installed. b. Enter the IP address/FQDN of the Windows server running the VoIP Monitoring Manager, if installed.
24 Avaya Integrated Management System Management Installation and Upgrade Upgrading to Release 5.2
c. Enter the IP address/FQDN of the server running SIP Enablement Services, if installed. d. Enter the IP address/FQDN of the server running PIM, if installed. e. Click Next. Note:
Note: The IP Address for any remote server you identify is automatically pinged. If it is determined that the server is not available, the system displays a warning message. Click Back to confirm the IP address/FQDN is correct, or click Next to continue. The system displays the Windows Application Server Information Continued dialog box.
May 2009 25 System Management Installation
17. Perform the following steps: a. Enter the IP address/FQDN of the server that runs Modular Messaging, if installed. b. Enter the IP address/FQDN of the server that runs Avaya easy Management, if installed. c. Enter the IP address/FQDN of the server that runs Communication Manager Branch Edition Central Manager, formerly DOCM, if installed. d. Enter the IP address/FQDN of the server that runs Secure Services Gateway, if installed. e. Enter the IP address/FQDN of the server that runs Message Networking, if installed. f. Click Next. The system displays the License Agreement dialog box. 18. Read the license agreement. 19. Click I accept the terms of the license agreement, and then click Next. Note:
Note: You must accept the terms of the license agreement in order to continue with the installation. The system displays the Summary Information dialog box. 20. Click Install. When the installation of System Management Release 5.2 is complete, the system displays the Summary Information dialog box. 21. Click Next. The system displays the Restore dialog box. Note:
Note: If you select Restore data now, the system will restore old IM application data. On the other hand, if you select Do not restore data, then you can use the Avaya > Integrated Management Data Backup and Restore utility to restore IM data. 22. Click Finish to quit the installation wizard. 23. In the terminal emulation window, perform the following tasks: a. Type cd and press Enter. b. Type eject and press Enter to remove the CD from the drive. c. Type reboot and press Enter to reboot the computer. Note:
Note: If you upgraded Avaya Fault and Performance Manager, Avaya recommends that you run the FixCounts command to audit and repair inconsistencies in the Avaya Fault and Performance Manager database. See Auditing the Fault and Performance Manager database on page 32 for the procedure to run the FixCounts command.
26 Avaya Integrated Management System Management Installation and Upgrade Installing Release 5.2
For more information about an Avaya Integrated Management product, access the online help after you start the application. Refer to the Avaya Integrated Management Launch Page for documentation on the applications you installed. Also, the latest versions of these books are available on the Avaya Support Web site. For information to access books, see How to access books on the Web on page 9. The documents are in the PDF format. To view a PDF document, you must install Adobe Reader on your computer. The System Management CD provides Adobe Reader. Note:
Note: Regularly check the Avaya Support Web site for software updates.
Installing Release 5.2
! SECURITY ALERT:
SECURITY ALERT: During the installation, the installation wizard turns off the internal firewall around the Linux server. This allows internal users to telnet to the Linux server and to use their Web browser to access the Windows clients. Do not turn on the internal Linux firewall after the installation. Your network firewall provides the needed security to prohibit outsiders access to the Linux server. This section describes how to install System Management Release 5.2 on a new system where there are no previous releases of System Management installed. 1. Ask all users to log off the system. 2. Log in as root on the Linux server where the System Management applications reside. Note:
Note: If you are not logged in as root, execute the su - root command to enable root permissions and the root environment. 3. Insert the Avaya Integrated Management 5.2, System Management CD into the CD-ROM drive of the Linux server. 4. Right-click the mouse and select Open Terminal to open a terminal emulation window. 5. Use one of the following steps:
l If you install the software on a Linux server that runs Red Hat Enterprise Linux Release 4.0: a. In the terminal emulation window, type mount /media and press Enter. Note:
Note: Depending on your operating system settings, the CD may mount automatically. b. Type cd /media/cdrom and press Enter.
May 2009 27 System Management Installation
l If you install the software on a Linux server that runs Red Hat Enterprise Linux Release 5.0: a. In the terminal emulation window, type mount /media/Avaya_System_Mgmt and press Enter. Note:
Note: Depending on your operating system settings, the CD may mount automatically. b. Type cd /media/Avaya_System_Mgmt and press Enter. 6. In the terminal emulation window, type bash ./IM5.2_setup.bin and press Enter. The system displays the Welcome dialog box. 7. Click Next.
l If you use a supported version of Linux, the system displays the Welcome dialog box. For directions, see Step 8.
l If you use an unsupported version of Linux, the system displays the Unsupported Linux Version dialog box. To upgrade the Linux operating system, perform the following tasks:
l If you use an RHEL 4.0 for a fresh installation, system displays a dialog box with the following warning: RHEL 4.0 supported only for upgrade. Fresh installation is supported on RHEL 5.0 system .You may proceed with installation. a. Click Exit installation, and then click Next. The system displays the Finish dialog box. b. Click Finish. c. See Upgrading Red Hat Enterprise Linux ES 4.0 or AS 4.0 to Red Hat Enterprise Linux 5.0 for information on how to upgrade the Linux operating system. d. After the upgrade of the Linux operating system, start the System Management 5.2 installation again. Note:
Note: You require Red Hat Enterprise Linux R5.0 for new installations. 8. Click Next. The system displays the Select Installation Type dialog box. 9. Perform one of the following steps:
l If you want to install all of the products, click All, and then click Next. The system displays the Location of the Integrated Management Database dialog box. For directions, see Step 10.
l If you do not want to install all of the products, click Custom, and then perform the following tasks: a. Click Next.
28 Avaya Integrated Management System Management Installation and Upgrade Installing Release 5.2
b. In the Select the Products to be Installed dialog box, click the products you want to install, and then click Next. The system displays the Location of the Integrated Management Database dialog box. 10. Use one of the following steps:
l To install Integrated Management Database on this computer, click Install the database locally on this machine, and then click Next.
l If you installed Integrated Management Database on a remote computer, click Install the database remotely on another machine, enter the IP address or fully qualified domain name of the remote computer, and then click Next. Note:
Note: If you select this option, it does not install Integrated Management Database on a remote computer. However, the wizard prompts you for the IP address of the remote computer so that the products on this computer can connect to Integrated Management Database on the remote computer. The system displays the Fully Qualified Domain Name dialog box. 11. Enter the fully qualified domain name if system displays the incorrect name, and click Next. The system displays the Choose Your Security Mode dialog box . Note:
Note: The new implementation of IMR5.2 launch pages necessitates either of two actions when you want to launch MSA, IMD or FPM on any Windows client when you install System Management in the SSL mode:
l make the entry in drivers\etc\hosts - Enter the server IP address and server host name, for example,135.27.155.101 rhel4es32-1.apac.avaya.com, in the hosts file in the etc folder within Drivers.
l register the machine in the DNS server - Alternatively, you can ask the DNS administrator to add the machine to DNS. 12. Read about SSL. Then click Secure Socket Layer (SSL) enabled or Secure Socket Layer (SSL) disabled, and click Next. The default is Secure Socket Layer (SSL) enabled. If you chose to install all the System Management applications, the system displays the Windows Server Application Information dialog box. For directions, see Step 13.
May 2009 29 System Management Installation
If you chose a Custom installation and did not install all the System Management products, the system prompts you for the IP Address/fully qualified domain name of the System Management applications that you are not installing on the local Linux server. This ensures that the Integrated Management Launch Page provides the correct links to the System Management applications that may be installed on a remote Linux server. Perform the following steps: a. When system displays the prompt, enter the IP address of the remote Linux server that runs the System Management application. If you did not install the application on a remote Linux server, leave the IP address field blank. b. Click Next. c. Repeat Steps a and b for each application. After you finish entering the IP address/fully qualified domain name (FQDN), the system displays the Windows Server Application Information dialog box. 13. Use the following steps: a. Enter the IP address/FQDN of the Windows server that runs Network Management, if installed. b. Enter the IP address/FQDN of the Windows server that runs the VoIP Monitoring Manager, if installed. c. Enter the IP address/FQDN of the server that runs SIP Enablement Services, if installed. d. Enter the IP address/FQDN of the server that runs PIM, if installed. e. Click Next. Note:
Note: The IP Address for any remote server you identify is automatically pinged. If it is determined that the server is not available, the system displays a warning message. Click Back to confirm the IP address/FQDN is correct, or click Next to continue. The the system displays Windows Application Server Information Continued dialog box. 14. Use the following steps: a. Enter the IP address/FQDN of the server that runs Message Networking, if installed. b. Enter the IP address/FQDN of the server that runs Modular Messaging, if installed. c. Enter the IP address/FQDN of the server that runs Avaya easy Management, if installed. d. Enter the IP address/FQDN of the server that runs Communication Manager Branch Edition Central Manager, formerly DOCM, if installed. e. Enter the IP address/FQDN of the server that runs Secure Services Gateway, if installed. f. Click Next. The the system displays the License Agreement dialog box.
30 Avaya Integrated Management System Management Installation and Upgrade Installing Release 5.2
15. Read the license agreement. 16. Click I accept the terms of the license agreement, and then click Next. Note:
Note: You must accept the terms of the license agreement in order to continue with the installation. The system displays the Summary Information dialog box. 17. Click Install. The system displays a progress message showing the installation of the selected products and required components. The installation can take several minutes. When the installation is complete, the system displays the Summary Information dialog box. 18. Click Next. If you installed Fault and Performance Manager, the system displays the Avaya Fault and Performance Manager Configuration window. 19. In the Avaya Fault and Performance Manager Configuration window, press Enter. 20. See Avaya Fault and Performance Manager Release 5.2 Configuration, document number 555-233-130, to configure Fault and Performance Manager. After you configure Avaya Fault and Performance Manager, the system displays the Reboot May be necessary dialog box. 21. Click Next. The system displays the Finish dialog box. 22. Click Finish to quit the installation wizard. 23. In the terminal emulation window, type the following commands: a. Type cd and press Enter. b. Type eject and press Enter to remove the CD from the drive. c. Type reboot and press Enter to reboot the computer. Note:
Note: See Configuring the Integrated Management Database on page 32 for procedures that you must perform before you use the Integrated Management applications. For more information about an Avaya Integrated Management product, access the online help after you start the application. Refer to the Avaya Integrated Management Launch Page for documentation on the applications you installed. Also, the latest versions of these books are available on the Avaya Support Web site. For information on how to access books, see How to access books on the Web on page 9. The documents are PDF documents. To view a PDF document, you must install Adobe Reader on your computer. The System Management CD provides Adobe Reader.
May 2009 31 System Management Installation
Note:
Note: Regularly check the Avaya Support Web site for software updates.
Auditing the Fault and Performance Manager database
If you upgraded Avaya Fault and Performance Manager to Release 5.2, Avaya recommends that you run the FixCounts command to audit and repair inconsistencies in the Avaya Fault and Performance Manager database.
! WARNING:
WARNING: This audit can take an extremely long period of time to run, several days on large databases. In addition, you must stop Fault and Performance Manager services before you run this command and then restart the services afterwards. To run the FixCounts command, follow these steps: 1. Log in as root on the Linux server where you installed Avaya Fault and Performance Manager Release 5.2. 2. Right-click the mouse and select Open Terminal to open a terminal emulation window. 3. In the terminal emulation window, type service mfpm-server stop and then press Enter to stop the Fault and Performance Manager services. 4. Type FixCounts -a and press Enter. 5. After the audit has finished running, type service mfpm-server start and then press Enter to restart the Fault and Performance Manager services.
Configuring the Integrated Management Database
In Avaya Integrated Management, the device data, such as configurations of voice systems, messaging systems, system adjuncts, and managed applications, and user accounts are stored in the Integrated Management Database and shared by System Management applications, for example, Avaya MultiSite Administration and Avaya Fault and Performance Manager. The System Management applications retrieve this data and verify user accounts from the Integrated Management Database. If this is a new installation, you must configure Integrated Management Database before you can use the Integrated Management applications. See Avaya Integrated Management Release 5.2 Integrated Management Database Configuration, document number 14-300039, for the procedures you must follow.
32 Avaya Integrated Management System Management Installation and Upgrade Backing up System Management
If this is an upgrade installation, you do not need to configure Integrated Management Database. The system will restore data from the previous release.
Backing up System Management
You can use the Graphical User Interface (GUI) utility or the command line method to get a backup of the System Management data . You can also use the GUI utility to schedule backups to run automatically on a daily, weekly, or monthly basis. This section provides these procedures.
Backing up data using the GUI utility
To use the GUI utility to back up System Management data on the Linux server, follow these steps: 1. Ask all users to log off the system. 2. Log in as root on the Linux server. 3. Select Applications > Avaya > Integrated Management Data Backup & Restore. The system displays the Integrated Management Backup and Restore dialog box. 4. Click the Backup/Restore Data Now tab. 5. Click Backup. 6. Select the check boxes for the applications you want to back up. 7. Enter a filename for the Integrated Management data backup file. 8. Use one of the following steps:
l To store the backup file on this machine, click Local, and then perform the following tasks: a. Click Browse. The system displays the Select Directory dialog box. b. Select the directory where you want to store the backup file. c. Click Select Directory. The Integrated Management Backup and Restore dialog box displays the directory you selected.
May 2009 33 System Management Installation
d. Click Backup Data. The system displays the Backing up Data dialog box while the data is backed up. When the backup procedure is complete, the system displays the message Local Data Operation Successful. e. Click OK. f. In the Integrated Management Backup and Restore dialog box, click Close.
l To store the backup file on a remote machine, click Remote, and then perform the following tasks: a. Enter the IP address of the remote computer. b. Enter the FTP user ID. c. Enter the password. d. Enter the name of the folder where you want to store the backup file. e. Click Backup Data. The system displays the Backing up Data dialog box while it performs the data backup procedure . When the backup procedure is complete, the system displays the message Remote Data Operation Successful. f. Click OK. g. In the Integrated Management Backup and Restore dialog box, click Close.
Scheduling backups using the GUI utility
To use the GUI utility to schedule automatic backups of the System Management data on the Linux server, follow these steps: 1. Ask all users to log off the system. 2. Log in as root on the Linux server. 3. Select Applications > Avaya > Integrated Management Data Backup & Restore. The system displays the Integrated Management Backup and Restore dialog box. 4. Click the Automatic Data Backups tab. 5. Enter the email address of the administrator. 6. Click the check boxes for the applications you want to back up. 7. Select the frequency—daily, weekly, or monthly—at which you want the backup to run. 8. Depending upon your selection, select the following:
l If you want the backup to run daily, specify the Hour.
l If you want the backup to run weekly, specify the Day and Hour.
34 Avaya Integrated Management System Management Installation and Upgrade Backing up System Management
l If you want the backup to run monthly, specify the Date and Hour. 9. Choose one of the following steps:
l To store the backup file on this machine, click Local, and then complete the following step: a. Click Browse. The system displays the Select Directory dialog box. b. Select the directory where you want to store the backup file. c. Click Select Directory. The directory you selected appears in the Integrated Management Backup and Restore dialog box. d. Click Schedule Backup. e. In the Integrated Management Backup and Restore dialog box, click Close.
l To store the backup file on a remote machine, click Remote, and then enter the following values: a. Enter the IP address of the remote computer. b. Enter the FTP user ID. c. Enter the password. d. Enter the name of the folder where you want to store the backup file. e. Click Schedule Backup. f. In the Integrated Management Backup and Restore dialog box, click Close.
May 2009 35 System Management Installation
Cancelling scheduled backups using the GUI utility
To cancel the schedule of automatic backups of System Management data on the Linux server, follow these steps: 1. Ask all users to log off the system. 2. Log in as root on the Linux server. 3. Select Applications > Avaya > Integrated Management Data Backup & Restore. The system displays the Integrated Management Backup and Restore dialog box. 4. Click the Automatic Data Backups tab. 5. Click Unschedule at the bottom of the Integrated Management Backup and Restore dialog box. 6. Click Close.
Backing up data using the Command Line method
To use the command line method to back up System Management data on the Linux server, follow these steps: 1. Ask all users to log off the system. 2. Log in as root on the Linux server. 3. Perform one of the following steps:
l To back up all Integrated Management application data, type /usr/sbin/IMbackup
l To back up specific Integrated Management application data, type /usr/sbin/ IMbackup
36 Avaya Integrated Management System Management Installation and Upgrade Restoring System Management
Restoring System Management
You can perform a restore of System Management data using the Graphical User Interface (GUI) utility or the command line method. This section provides the steps for both procedures. When you restore the System Management data, the system reads the data from the backup input file and then imports it into the applications. You can restore selective applications from the backup input file. For example, if you backed up all the System Management applications, you can restore specific applications or restore all the applications from the backup file.
Restoring data using the GUI utility
To use the GUI utility to restore System Management data on the Linux server, follow these steps: 1. Ask all users to log off the system. 2. Log in as root on the Linux server. 3. Select Applications > Avaya > Integrated Management Data Backup & Restore. The system displays the Integrated Management Backup and Restore dialog box. 4. Click the Backup/Restore Data Now tab. 5. Click Restore. 6. Select the check boxes for the applications you want to restore. 7. Use one of the following procedures:
l If the backup file is on this machine, click Local, and then follow the steps given: a. Click Browse. The system displays the Select File dialog box. b. Select the backup file that contains the data you want to restore. c. Click Select File. The system displays the file you selected in the Integrated Management Backup and Restore dialog box. d. Click Restore Data. The system displays the Restoring Data dialog box while the data restoration procedure is in progress. When the restore procedure is finished, the system displays the message Local Data Operation Successful. e. Click OK. f. In the Integrated Management Backup and Restore dialog box, click Close.
May 2009 37 System Management Installation
l If the backup file is one a remote machine, click Remote, and then follow these steps: a. Enter the IP address of the remote computer. b. Enter the FTP user ID. c. Enter the password. d. Enter the name of the folder where the backup file is located. e. Click Restore Data. The system displays the Restoring Data dialog box while the data restoration procedure is in progress.When the restore procedure is finished, the system displays the message Remote Data Operation Successful. f. Click OK. g. In the Integrated Management Backup and Restore dialog box, click Close.
Restoring data using the Command Line method
To use the command line method to restore the System Management data on the Linux server, follow these steps: 1. Ask all users to log off the system. 2. Log in as root on the Linux server. 3. Perform one of the following steps:
l To restore all Integrated Management application data, type /usr/sbin/IMrestore
l To restore specific Integrated Management application data, type /usr/sbin/ IMrestore
38 Avaya Integrated Management System Management Installation and Upgrade up2date or YUM support for Red Hat Linux platforms up2date or YUM support for Red Hat Linux platforms
up2date, also known as the Red Hat Update Agent, is a program for updating packages on Red Hat Linux. It downloads and installs new software and upgrades the operating system. It functions as a front-end to the RPM Package Manager and adds advanced features such as automatic dependency resolution. The file /etc/sysconfig/rhn/sources specifies where up2date will search for packages. Note:
Note: Avaya supports RHEL 5 and the update utility on it is called Yellow dog Updater, Modified (YUM).
Issue
When you update the Red Hat Linux version, the configuration file changes. It changes the configuration settings for tomcat, apache, and other third party RPMs, and causes application failure.
Resolution
To resolve the issue: 1. From the main menu, click Avaya > Up2Date Config. Wait until the terminal window closes. 2. Reboot the system to start Avaya services.
May 2009 39 System Management Installation
Uninstalling System Management
To uninstall System Management 5.2 on the Linux server, follow these steps: 1. Ask all users to log off the system. 2. Log in as root on the Linux server. 3. In the terminal emulation window, type cd / and press Enter. 4. In the command line, type install_location/avaya/uninstall.bin and press Enter. The system displays the wizard to uninstall Integrated Management System Management 5.2. 5. Click Next. The system displays the Select Features to Uninstall dialog box. 6. Select the products you want to uninstall, and click Next. If you did not select Integrated Management Database, the system displays the Summary Information dialog box. Proceed to Step 7. If you selected Integrated Management Database, one of the following occurs:
l If the Integrated Management Database server runs on the local machine, the system displays a message that recommends you to perform a database backup before you uninstall the database. Use one of the following steps: - Select Uninstall the Integrated Management Database, and click Next. The system displays the Summary Information dialog box. Proceed to Step 7. - Select Do not uninstall the Integrated Management Database, and click Next. The system displays the Summary Information dialog box. Proceed to Step 7. If either Avaya Fault and Performance Manager or Avaya MultiSite Administration are not selected to be uninstalled, the system displays a dialog box with the request for the IP address or the fully qualified domain name of the machine that runs the Integrated Management Database server. Enter the IP address or the fully qualified domain name of the machine that runs the Integrated Management Database server, and then click Next. The uninstaller configures the remaining applications to use this remote server. Note:
Note: You cannot leave the IP address/fully qualified domain name field blank. You must enter a valid IP address or the fully qualified domain name of the machine that runs the Integrated Management Database server. The system displays the Summary Information dialog box.
40 Avaya Integrated Management System Management Installation and Upgrade Allowing Avaya Services remote access
l If the Integrated Management Database server runs on a remote machine, the following occurs: If either Avaya Fault and Performance Manager or Avaya MultiSite Administration are not selected to be uninstalled, the system displays a dialog box with the message that you either go back and clear the Integrated Management Database server selection or select all the available applications on the machine to be uninstalled. Perform either step, and then click Next. The system displays the Summary Information dialog box. Note:
Note: The Integrated Management Launch Page can remain on the system after you uninstall Integrated Management Database. 7. Click Uninstall. When the products have been uninstalled, the system displays the Summary Information dialog box. 8. Click Next. The system displays the Finish window. 9. Click Finish.
Allowing Avaya Services remote access
If you want Avaya Services to have remote access to your system, you must install the following Red Hat Package Manager (RPM) files:
l mgetty (install first)
l ppp
l vnc
l vnc-server See Avaya Integrated Management Release 5.2 Configuring Red Hat Linux, document number 555-233-152, for more information. If these RPM files are not installed, you must provide another way to allow Avaya Services remote access.
May 2009 41 System Management Installation
Configuring the Integrated Management server
A server configuration tool that allows you to make changes to the server settings after you install the Integrated Management applications is available. Use the server configuration tool to perform the following tasks:
l Change the application links on the Integrated Management Launch Page after the applications have been installed. For steps to change an application link, see Changing an application link on the Avaya Integrated Management Launch Page on page 42.
l Change the security setting of your server. For steps to change the security settings, see Changing security settings on page 43.
Changing an application link on the Avaya Integrated Management Launch Page
To change an application link on the Avaya Integrated Management Launch Page after the installation of an application: 1. From the main menu, click Avaya > Configure Integrated Management. The system displays the Configure Integrated Management 5.2 dialog box. 2. To change the link of an Integrated Management application, click the System Management tab and change the IP address of the application. 3. If you want the system to display application links for Voice Announcement Manager and Avaya Site Administration on the Avaya Integrated Management Launch Page, select the check boxes for those applications. 4. Click Save Settings. 5. To change the link of an adjunct application, click the Adjunct Management tab and change the IP address of the application. 6. If you want the application link for Mailbox Manager to appear on the Avaya Integrated Management Launch Page, select the check box for the application. 7. Click Save Settings. 8. Click Close when finished.
42 Avaya Integrated Management System Management Installation and Upgrade Configuring the Integrated Management server
Changing security settings
To change the security settings of your server, follow these steps: 1. From the main menu, click Avaya > Configure Integrated Management. The system displays the Configure Integrated Management 5.2 dialog box. 2. Click the Configure Security tab. 3. Select SSL Enabled or SSL Disabled. The system provides a brief explanation about each setting. The default is SSL Enabled. 4. Click Save Settings. 5. Click Close when finished. Note:
Note: If you change the security setting and Fault and Performance Manager is installed on your local machine, the Fault and Performance Manager configuration tool will run automatically after you change the security setting. Also note that all the Linux servers in the cluster with Avaya Integrated Management applications installed must share the same security settings.
May 2009 43 System Management Installation
44 Avaya Integrated Management System Management Installation and Upgrade Appendix A: Linux server installation
Overview
This appendix specifies the options that you must select during the installation of Red Hat Enterprise Linux 5.0 (RHEL 5.0) to support Avaya Fault and Performance Manager, Avaya MultiSite Administration, and Avaya Integrated Management Database. The appendix also provides the procedure to upgrade Red Hat Enterprise Linux ES 4.0 or Red Hat Enterprise Linux AS 4.0 to Red Hat Enterprise Linux 5.0. Note:
Note: You require RHEL 5.0 for new installations. There is support for Red Hat Enterprise Linux ES 4.0 or Red Hat Enterprise Linux AS 4.0 only if you upgrade from Avaya Integrated Management Release 5.0 to Avaya Integrated Management Release 5.2. Make sure you attach a modem to COM 1 (ttyS0) of the Linux server for dial-in access and keep it turned on while you install Red Hat Enterprise Linux.
Installing Red Hat Enterprise Linux 5.0
To perform a new installation of RHEL 5.0: 1. Insert the first RHEL 5.0 CD into the CD-ROM drive, restart the server, and run Red Hat Enterprise Linux System Installer in the graphical mode. 2. Follow the prompts until the system displays the Red Hat Enterprise Linux 5 page. 3. Click Next. The system displays the Language Selection page. 4. Select the appropriate language, and then click Next. The system displays the Keyboard Configuration page. 5. Select the appropriate keyboard, and then click Next. The system displays the Installation Number dialog box . 6. Enter your Red Hat installation number, and then click OK. The system displays the Install or Upgrade page.
May 2009 45 Linux server installation
7. Click Install Red Hat Enterprise Linux Server, and then click Next. The system displays the Disk Partitioning Setup page. 8. Select Create custom layout from the drop-down list box. 9. Click Next. The system displays the Disk Setup page. 10. Perform the following steps: a. Click Delete to delete any partitions displayed for the hard drive. b. Click New to add partitions as shown in Table 4.
Table 4: Hard Drive Partitions
File Proportion of Mount System Partition Size Disk Space Point Type (40 GB HD) (>40 GB HD)
/ ext3 800 MB 2% /boot ext3 100 MB 1% /home ext3 6000 MB 17% /usr ext3 6000 MB 15% /opt ext3 10000 MB 26% /var ext3 10000 MB 26% swap swap 2048 MB 2048 MB /tmp ext3 3000 MB 8% Total 37948 MB 100%
Note:
Note: The precise partition sizes are shown for a 40 GB hard drive. Note that a 40 GB hard drive partitions to approximately 38 GB. If the hard drive is bigger than 40 GB, use the proportion column to partition the hard drive. c. When you finish adding the hard drive partitions, click Next. The system displays the Boot Loader Configuration page. 11. Click Next to accept the default settings. The system displays the Network Configuration page. 12. Click Edit. The system displays the Edit Interface eth0 dialog box.
46 Avaya Integrated Management System Management Installation and Upgrade Installing Red Hat Enterprise Linux 5.0
13. In the Edit Interface eth0 dialog box, follow these steps: a. Clear the Use dynamic IP configuration (DHCP) check box. b. Clear the Enable IPv6 support check box. c. Enter the static IP address and subnet mask for IPv4. d. Click OK. 14. In the Network Configuration page, follow these steps: a. In the Hostname section of the page, enter the fully qualified domain name. b. In the Miscellaneous Settings section of the page, enter the gateway, primary, and secondary DNS server IP addresses. c. Click Next. The system displays the Time Zone Selection page. 15. Set the time zone and then click Next. The system displays the Set Root Password page. 16. Enter the root user password, enter it again for confirmation, and then click Next. The system displays the Package Installation Defaults page. 17. Select the Software Development check box. 18. Select the Web server check box. 19. Click Customize now, and then click Next. The system displays the Package Group Selection page. Note:
Note: Do not select any check box that is enabled, that is, selected by default. 20. Perform the following steps: a. Click Desktop Environments in the left list box, and click KDE (K Desktop Environment) in the right list box. b. Click Applications in the left list box, and ensure that Editors is selected in the right list box. c. Click Development in the left list box, and click Legacy Software Development in the right list box. d. Click Servers in the left list box, and click FTP Server in the right list box. e. Click Base System in the left list box, click System Tools, and then use the following steps: 1. Click Optional packages. The system displays the Packages in System Tools dialog box. 2. Select the net-snmp-utils check box.
May 2009 47 Linux server installation
3. Select the tsclient check box. 4. Click Close. Note:
Note: If you install the Red Hat Enterprise Linux 64-bit operating system, select the check box for the Compatibility Arch Support package. This package installs the 32-bit compatibility RPMs. 21. In the Package Group Selection page, click Next. The installer checks for dependencies in the selected packages, and then the system displays the Begin Installation page. 22. Click Next. The system displays the Required Install Media dialog box. 23. Click Continue. The system displays the installation status bar. 24. Continue with the installation. 25. When the installation is complete, click Reboot. After the server reboots, the system displays the Welcome dialog box. 26. Click Forward. The system displays the License Agreement page. 27. Click Yes, I agree to the License Agreement, and then click Forward. The system displays the Firewall dialog box. 28. From the Firewall drop-down list box, select Disabled, and click Forward. The system displays a dialog box. 29. Click Yes. The system displays the SELinux dialog box. 30. From the SELinux Setting drop-down list box, select Disabled, and click Forward. The system displays a dialog box. 31. Click Yes. The system displays the Kdump dialog box.
48 Avaya Integrated Management System Management Installation and Upgrade Installing RHEL in the text mode
32. Follow the prompts to continue the initial configuration of the operating system such as registering the system with Red Hat. Note:
Note: Be sure to add at least one regular user account to the system. Do not update postgres or any components related to postgres. Doing so will result in serious problems in the Avaya Fault and Performance Manager and Avaya Integrated Management Database applications. After the server is configured, the system prompts you to reboot. 33. Click OK. 34. After the server reboots, log in and see Verifying installation of required RPM files on page 53 for steps to verify the installation of RPM files.
Installing RHEL in the text mode
You can install Red Hat Enterprise Linux (RHEL) in the text or nongraphical mode. Use the procedure in this section to install RHEL in the text mode. See Installing Red Hat Enterprise Linux 5.0 on page 45 for the detailed RHEL installation procedure. To install RHEL in the text mode: 1. Enter linux text at the installation boot prompt. The installation program prompts you to insert a CD. 2. Insert the CD in your CD-ROM drive and boot your system from the CD-ROM. Proceed with the installation tasks to the Time zone configuration. Note:
Note: Ensure that you clear System Clock uses UTC on the Time zone configuration screen during the Time zone configuration. Continue with the tasks in the installation. 3. Set up a root account and password and click Next. The system displays the Package Installation Defaults screen that details the default package set for your RHEL installation. 4. Select the following additional tasks for your system:
l Software Development
l Web Server 5. Select Customize now to customize your package set further.
May 2009 49 Linux server installation
6. Click Next. The system displays the Package Group Selection screen. 7. Select the following:
l KDE (K Desktop Environment)
l Legacy Software Development
l FTP Server
l System Tools 8. Reboot the system after you complete the installation.
Upgrading Red Hat Enterprise Linux ES 4.0 or AS 4.0 to Red Hat Enterprise Linux 5.0
To upgrade Red Hat Enterprise Linux ES 4.0 or Red Hat Enterprise Linux AS 4.0 to Red Hat Enterprise Linux 5.0, perform the following steps: 1. Insert the first Red Hat Enterprise Linux 5.0 CD into the CD-ROM drive, restart the server, and start the Red Hat Enterprise Linux System Installer in graphical mode. 2. Follow the prompts until the system displays the Red Hat Enterprise Linux 5 page. 3. Click Next. The system displays the Language Selection page. 4. Select the appropriate language, and then click Next. The system displays the Keyboard Configuration page. 5. Select the appropriate keyboard, and then click Next. The system displays the Installation Number dialog box. 6. Enter your Red Hat installation number, and then click OK. The system displays the Install or Upgrade page. 7. Click Upgrade an existing installation, and click Next. The system displays the GRUB Boot Loader page. 8. Click the appropriate option button, and then click Next. The system displays the Begin Upgrade page. 9. Click Next. The system displays the Required Install Media dialog box.
50 Avaya Integrated Management System Management Installation and Upgrade Using kickstart for Red Hat Enterprise Linux installations
10. Click Continue. The system displays the installation status bar. 11. Proceed with the upgrade. 12. When the upgrade is complete, remove the CD, and click Reboot. 13. After the server reboots, verify whether the necessary Red Hat Package Manager (RPM) files are installed. For the required information, see Verifying installation of required RPM files on page 53.
Using kickstart for Red Hat Enterprise Linux installations
Kickstart for RHEL installations provides a way for system administrators to automate an RHEL installation. Kickstart makes installation easy for network and system administrators because it can support the use of a single kickstart file to install RHEL on multiple machines. This installation method also frees RHEL installations of the configuration errors that can occur during a nonautomated installation.
Selecting an installation method
To use kickstart to perform a new installation, select the type of kickstart installation you want from the following options:
l boot CD-ROM
l network
l boot diskette
CD-ROM
Select this option to perform an installation from the Red Hat Enterprise Linux CD-ROMs. To use this option: 1. Insert the CD-ROM into the system. 2. Boot the system. 3. Enter the following command at the boot prompt: linux ks=cdrom:/ks.cfg Note:
Note: ks.cfg is the name of the kickstart file.
May 2009 51 Linux server installation
HTTP
Select this option to perform an installation from an HTTP server. To use this option: 1. In the text field for the HTTP server, enter the fully-qualified domain name or IP address. 2. In the field for the HTTP directory, enter the name of the HTTP directory. For example, if the HTTP server contains the directory /mirrors/redhat/i386/Server/, enter /mirrors/redhat/i386/Server/. 3. Use the command: linux ks = http://< server >/< path > If the HTTP server is server.example.com and the kickstart file is located in the HTTP directory mydir/ks.cfg, use the following boot command: linux ks = http:// server.example.com/ mydir/ks.cfg
Diskette
Select this option to perform an installation from a diskette. To use this option: 1. Locate the ks.cfg file on a vfat or ext2 file system on a diskette. 2. Boot from the first Red Hat Enterprise Linux CD-ROM. 3. Use the linux ks = floppy command. Note:
Note: Diskette-based booting is no longer supported in Red Hat Enterprise Linux. Installations must use CD-ROM or flash memory products for booting. However, the kickstart file may still reside on the top-level directory of a diskette, and must be named ks.cfg.
Initiating a kickstart installation
You can perform a kickstart installation with a local CD-ROM, a local hard drive, or via NFS, FTP, or HTTP. To initiate a kickstart installation: 1. Create a kickstart file. 2. Create a boot media with the kickstart file or make the kickstart file available on the network. 3. Make the installation tree available.
52 Avaya Integrated Management System Management Installation and Upgrade Verifying installation of required RPM files
4. Start the kickstart installation.
Starting a kickstart installation
To begin a kickstart installation: 1. Boot the system from the boot media you made or the Red Hat Enterprise Linux CD-ROM. 2. Enter a special boot command at the boot prompt. linux ks= < a method > / < path of the kickstart file > The installation program looks for a kickstart file, ks.cfg, if the ks command line argument is passed to the kernel. Detailed information on kickstart installations is available at: http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/ s1-kickstart2-startinginstall.html
Verifying installation of required RPM files
After you install or upgrade the Red Hat Linux operating system, verify whether the Red Hat Package Manager (RPM) files listed below are installed.
l mgetty Avaya Services require the mgetty RPM for remote maintenance. Avaya Services personnel may not require this RPM if there is provision for alternate remote network access (RAS/VPN).
l ppp Avaya Services require the ppp RPM for remote maintenance. Avaya Services personnel may not require this RPM if there is provision for alternate remote network access (RAS/ VPN).
l vnc (located in System Tools) Avaya Services require the vnc RPM for remote maintenance, to access graphical user interfaces for troubleshooting purposes. Avaya Services personnel may not require this RPM if there is provision for an alternate method to display the XWindow desktop of the Linux server.
l vnc-server (located in X Windows System) Avaya Services require the vnc-server RPM for remote maintenance to access graphical user interfaces for troubleshooting purposes. Avaya Services personnel may not require
May 2009 53 Linux server installation
this RPM if there is provision for an alternate method to display the XWindow desktop of the Linux server. To determine whether these RPM files are installed, use the following steps: 1. In the terminal emulation window, at the command prompt, type rpm –q
Note: If you installed the 64-bit version of the Red Hat Enterprise Linux Release 5.0 operating system, you must install the Compatibility Arch Support RPM package, if you did not do so when you installed the operating system. This package installs the 32-bit compatibility RPMs.
Installing required RPM files
To install additional RPM files, perform the following steps: 1. Insert the Red Hat installation CD in the CD-ROM drive. 2. Open a terminal emulation window. 3. Type cd /mnt/cdrom/RedHat/RPMS. Note:
Note: If Linux responds directory does not exist, you may have to manually mount the CD-ROM drive. To do so, perform the following steps: a. Type mount /dev/cdrom. b. Type cd /dev/cdrom/RedHat/RPMS. 4. At the command prompt, type rpm –iv
54 Avaya Integrated Management System Management Installation and Upgrade RPM files installed by System Management R5.2
RPM files installed by System Management R5.2
When you install Avaya Integrated Management Release 5.2 System Management, the RPM files in the list in this section are automatically installed. If any of these RPM files are already installed on the Linux server, the System Management installation wizard removes them and installs the appropriate version.
l httpd Avaya Integrated Management Database requires the httpd RPM.
l tomcat
l php (located on Web Server) Avaya Integrated Management Database requires the php RPM.
l php-pgsql (located on Web Server) RPM Avaya Integrated Management Database requires the php-pgsql.
l openldap (2.3.27) (located on Network Server) Avaya MultiSite Administration requires the openldap RPM for Modular Messaging and SSH support.
l cyrus-sasl (2.1.22-4) Avaya MultiSite Administration requires the cyrus-sasl RPM for Modular Messaging and SSH support.
l openssl (0.9.6b.22) Avaya MultiSite Administration requires the openssl RPM for Modular Messaging and SSH support.
Warning for unsupported versions of third-party RPMs
The SM Installer installs versions of third-party RPMs that Integrated Management 5.2 supports, for example, Apache 2.0.52 for RHEL 4 and Apache 2.2.x for RHEL 5. If the installer detects an unsupported version of a third-party RPM during an SM installation, it issues the user a warning. If the user agrees to continue the installation, the installer downgrades the RPM to the supported version on the Linux server. Otherwise, the user can choose to quit the installation.
May 2009 55 Linux server installation
Security considerations
In order to strengthen system security, Avaya recommends that you turn off the Remote Procedure Calls (RPC) service on all Linux servers that run Avaya Integrated Management applications. To turn off the RPC service, you must close all related ports that provide the service. Note:
Note: You must have root access to turn off the RPC service. Perform the following steps: 1. To turn off the service, at the command prompt in the terminal emulation window, type service portmap stop. 2. To turn off the service so that it does not start again when the Linux server is restarted, at the command prompt in the terminal emulation window, type chkconfig -levels 12345 portmap off.
56 Avaya Integrated Management System Management Installation and Upgrade Index
Index
Symbols K >, meaning of in text ...... 6 kickstart ...... 51
A L Avaya Linux server support web site ...... 9 internal firewall ...... 21, 27 Avaya Professional Services ...... 6 P B prerequisites, for installing ...... 5 backups primary Linux server ...... 19 using command line method...... 36 using GUI ...... 33 bold text, meaning of ...... 6 R random password ...... 17 Red Hat Linux, verifying current version ...... 15 C Red Hat Package Manager files ...... 41 commands remote access FixCounts ...... 32 for Avaya Services ...... 41 su - root ...... 20, 21, 27 requirements Configuring openLDAP server ...... 16 Linux server...... 13 console mode ...... 20 resources contact information for Avaya ...... 9 Avaya Global Services Delivery (GSD) ...... 8 courier bold font, meaning of ...... 6 Avaya Global Technical Services ...... 8 courier bold italic font, meaning of...... 6 Avaya Technology and Consulting (ATAC) . . . . . 6 courier font, meaning of ...... 6 Customized Management Solutions for Avaya Integrated customer specified directory ...... 16 Management ...... 8 restore data using command line method ...... 38 F using GUI ...... 37 Restoring ...... 37 Fault and Performance Manager primary data collection server ...... 19 secondary data collection server ...... 19 S FixCounts command ...... 26 scheduled backups cancelling...... 36 I using GUI ...... 34 Security settings installation changing ...... 43 Linux server ...... 27 supported configurations ...... 19 multiple Linux servers ...... 19 Integrated Management Database co-resident with an FPM secondary collection server19 T IP address changing launch page links after application is installed text mode RHEL installation ...... 49 42 typographical conventions...... 6
Issue 5 May 2009 57 Index
U up2date ...... 39
58 Avaya Integrated Management System Management Installation and Upgrade