Implementing Avaya Integrated Management Release 6.0
June 2010
Contents
Chapter 1: Preface...... 5 Purpose...... 5 Support resources...... 5 Avaya Professional Services...... 6 Avaya Global Services Delivery...... 7 Avaya Global Technical Services...... 7 Customized management solutions for Avaya Integrated Management...... 7 Contact information for Avaya support services...... 8 Related documentation...... 8 Chapter 2: Application environment...... 11 Integrated Management overview...... 11 Voice and messaging system compatibility...... 11 Hardware and software requirements...... 13 Site Administration: Client computer requirements...... 13 Performance and Administration: Server requirements...... 14 Performance and Administration: Client computer requirements...... 15 Network Management: server requirements...... 16 Network Management: client computer requirements...... 18 Connectivity requirements...... 19 Hardware and software requirements for remote access...... 19 Symmetric Multi-Processor support...... 19 Chapter 2: Implementation services...... 21 Product packaging...... 21 Customer implementation options...... 22 Overview of Avaya Implementation Services...... 22 Basic implementation...... 23 Services organizations involved in Avaya Integrated Management implementations...... 24 Service Request Documentation...... 25 Responsibilities of Customer and Avaya...... 27 Implementation tasks...... 29 Remote connectivity...... 30 Computing platform...... 31 IP connectivity...... 31 Application installation and configuration...... 32 Implementation verification...... 32 Accessing the Avaya Integrated Management Launch Products page...... 32 Verifying Avaya Fault and Performance Manager implementation...... 33 Verifying Avaya MultiSite Administration implementation...... 33 Verifying Avaya Integrated Management Database implementation...... 34 Verifying Site Administration implementation...... 35 Verifying Avaya Provisioning and Installation Manager for Branch Gateways implementation...... 35 Verifying Avaya Provisioning and Installation Manager for IP Office implementation...... 36 Verifying IP Office Manager implementation...... 36 Verifying Avaya Network Management Console implementation...... 36 Verifying Software Update Manager implementation...... 37 Verifying Avaya Configuration Backup Restore implementation...... 39
Implementing Avaya Integrated Management Release 6.0 June 2010 3 Verifying Avaya NM Backup Utility implementation...... 40 Verifying Avaya NM Easy Restore Utility implementation...... 40 Chapter 3: Linux Server installation...... 41 Installing Red Hat Enterprise Linux 5.4...... 41 Upgrading Red Hat Enterprise Linux ES 4.0 or AS 4.0 to Red Hat Enterprise Linux 5.4...... 44 up2date support for Red Hat Linux platforms...... 45 Proposed solution...... 46 Verifying installation of required RPM files...... 46 Red Hat Package Manager files...... 47 Installing required RPM files...... 47 RPM files installed by Performance and Administration release 6.0...... 48 Improving system security...... 49
Index...... 51
4 Implementing Avaya Integrated Management Release 6.0 June 2010 Chapter 1: Preface
Purpose
This book provides the customer with an overall strategy for implementation of Avaya Integrated Management applications. It describes the roles and responsibilities of the customer and Avaya Services in the implementation of the applications. This book addresses: • Pre-implementation requirements of the network management computing platforms • Pre-implementation installation of the operating system on the computing platforms • Post-implementation verification checklist The Avaya Data Network Implementation Engineering team (formerly RNIS) provides implementation services for Avaya Integrated Management applications. For more information about planning, consulting, and technical services available from Avaya, see Support resources on page 5. Avaya Authorized Business Partners may also provide implementation services. Details of implementation services offered by business partners must be obtained from the business partners and are not discussed in this book.
Support resources
Avaya provides a variety of planning, consulting, and technical services. The following sections describe the resources and services that are available.
Related topics: Avaya Professional Services on page 6 Avaya Global Services Delivery on page 7 Avaya Global Technical Services on page 7 Customized management solutions for Avaya Integrated Management on page 7 Contact information for Avaya support services on page 8
Implementing Avaya Integrated Management Release 6.0 June 2010 5 Preface
Avaya Professional Services
The Avaya Professional Services team of Avaya Integrated Management consultants offers the following services to the customers: • Platform-readiness verification • Avaya Integrated Management architectural planning, design, and overview • Remote turnkey implementation and installation • Avaya Integrated Management server configuration • Customer acceptance verification • Custom on-site services • Onsite and remote knowledge transfer The Avaya Professional Services Data Group consists of the following teams: • Avaya Integrated Management Consultants • Data Network Implementation Engineering The Avaya Professional Services Data Group provides support on a contract basis. Contact your local Avaya Account Team or Business Partner to purchase any implementation offer from the Avaya Professional Services Data Group. For more information, refer to Table 1: Contact information for Avaya support services on page 8 or contact Jon Machak at 248-213-3788 or [email protected]. Avaya Integrated Management Consultants The Avaya Integrated Management consulting team offers planning, design, implementation, consulting, and knowledge transfer services for the Avaya Integrated Management suite. This includes Site Administration, Val Manager, Network Management Console, Software Update Manager, MultiSite Administration (MSA), and Avaya Fault and Performance Manager (FPM). The thrust of the Avaya Professional Services 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 customer can leverage the Avaya Integrated Management suite to lower total cost of ownership, and proactively manage their VoIP network comfortably and confidently. Data Network Implementation Engineering The Data Network Implementation Engineering 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 creates the hardware and software installation specification required to implement data devices that include Cajun, VPN, Wireless LAN, Secure Gateways, Extreme, Juniper, and multivendor data equipment.
6 Implementing Avaya Integrated Management Release 6.0 June 2010 Support resources
Avaya Global Services Delivery
Avaya Global Services Delivery (GSD) team provides support to the Avaya Integrated Management client teams, field technicians, and customers. GSD charges customers for support on a time and materials basis if customers: • do not provide remote access • do not have a current maintenance agreement • do not procure and install the required systems and software as defined in the Integrated Management Services Support Plan • 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 to an associate who can answer questions about the products.
Customized management solutions for Avaya Integrated Management
The Integrated Management Product team understands the customer requirements and focuses on customer satisfaction. See Table 1: Contact information for Avaya support services on page 8 for contact information. This product team assists customers with Avaya Integrated Management projects and provides: • Project management: An Integrated Management project person works with the customer to access configuration and customization requirements for any or all applications within each Avaya Integrated Management offer. If customization is required, the evaluation includes a proposed statement of work and price. Note that this offer is not intended to provide installation for customers that choose to implement Integrated Management applications using Avaya Services or third-party implementation services. • Training: The product team usually conducts basic training remotely using an interactive medium to display the applications and a conference bridge for audio. The product team customizes the onsite training to meet the customer’s needs. Customized training focuses on application functionality that is relevant to the customer and provides focused knowledge transfer to facilitate application-specific training.
Implementing Avaya Integrated Management Release 6.0 June 2010 7 Preface
Contact information for Avaya support services
If you need assistance during installing and setting up Integrated Management System, use the following contact information: Table 1: Contact information for Avaya support services
Resource Contact Information Avaya Support Center http://www.avaya.com/support Avaya Global +1 800 242-2121, extension 15921 Technical Services Avaya Professional +1 800 730-9108, prompt 3 Services Integrated Send e-mail message to [email protected] Management Product Team Toll Fraud Intervention +1 800 643-2353, prompt 1
Related documentation
Avaya Integrated Management Release 6.0 documents, organized by offer, are: • Overview Guides, all offers: - Implementing Avaya Integrated Management Release 6.0 - Avaya Integrated Management Release 6.0 Overview • Site Administration Offer (formerly Administration Tools offer) (continued) - Installation guide and Release notes: • Avaya Integrated Management Release 6.0 Site Administration Installation and Upgrade • Avaya Integrated Management Site Administration Release 6.0 Release Notes - Standalone Help files: Avaya Integrated Management Release 6.0 Site Administration Standalone Help System
8 Implementing Avaya Integrated Management Release 6.0 June 2010 Related documentation
• Performance and Administration Offer (formerly System Management offer) (continued) - Installation guide and Release notes: • Avaya Integrated Management Release 6.0 Performance and Administration Installation and Upgrade • Avaya Integrated Management Performance and Administration Offer release 6.0 Release Notes - Configuration Guides: • Avaya Integrated Management Release 6.0 MultiSite Administration Configuration • Avaya Integrated Management Release 6.0 Avaya Fault and Performance Manager Configuration • Avaya Integrated Management Release 6.0 Integrated Management Database Configuration - Standalone Help files: • Avaya Integrated Management Release 6.0 MultiSite Administration Standalone Help System • Avaya Integrated Management Release 6.0 Avaya Fault and Performance Manager Standalone Help System • Avaya Integrated Management Release 6.0 Avaya Fault and Performance Manager MOs Help • Avaya Integrated Management Release 6.0 Integrated Management Database Standalone Help System • Network Management Offer (formerly Enterprise Network Management offer) - Installation guide and Release notes: • Avaya Integrated Management Release 6.0 Network Management Installation and Upgrade • Avaya Integrated Management Network Management Release 6.0 Release Notes - Configuration Guides: • Avaya Integrated Management Release 6.0 Network Management Configuration • Avaya Integrated Management Release 6.0 Network Management for Avaya Aura® Communication Manager Branch Configuration - Standalone Help files: • Avaya Integrated Management Release 6.0 Provisioning and Installation Manager for Gateways Standalone Help System • Avaya Integrated Management Release 6.0 Provisioning and Installation Manager for IP Office devices Standalone Help System
Implementing Avaya Integrated Management Release 6.0 June 2010 9 Preface
• Avaya Aura® Communication Manager Branch Release 2.0 Local Manager Standalone Help System - Network Management Application User Guides: • Avaya Integrated Management Release 6.0 Configuration Backup Restore User Guide • Avaya Integrated Management Release 6.0 Network Management Console User Guide • Avaya Integrated Management Release 6.0 Software Update Manager User Guide • Avaya Integrated Management Release 6.0 Avaya Secure Access Administration User Guide - Device Manager User Guides: • Avaya Integrated Management C360 Manager User Guide • Avaya Integrated Management G450/G350/250 Manager User Guide • Avaya Integrated Management G430 Manager User Guide • Avaya Integrated Management P330 Manager User Guide
10 Implementing Avaya Integrated Management Release 6.0 June 2010 Chapter 2: Application environment
Integrated Management overview
Avaya Integrated Management provides a standards-based infrastructure for an open application program interface and integrated network management in a converged, multi- vendor environment. Avaya Integrated Management comprises a set of applications that provide systems administration, network management, and business integration in a converged voice and data environment. While many of the individual management products are available on an individual basis, Avaya Integrated Management integrates voice-centric management products and data-centric management products and provides a common user interface.
Voice and messaging system compatibility
The Avaya Integrated Management products use IP to manage devices. Avaya Integrated Management is compatible with voice systems, messaging systems, and call management systems as shown in Table 2: Avaya Integrated Management system compatibility on page 11. Table 2: Avaya Integrated Management system compatibility
System Release DEFINITY R, DEFINITY SI, DEFINITY Release 9.5, 10 or MultiVantage (system must CSI, DEFINITY ONE, IP600 be configured for IP administration) S8100 Media Server MultiVantage S8300 Media Server MultiVantage and later or Avaya Aura™Communication Manager up to release 5.2.1 S8300B or S8300C Media Server Communication Manager up to release 5.2.1 S8300D Media Server Communication Manager up to release 5.2.1 S8400 Media Server Communication Manager up to release 5.2.1 S8500B or S8500C Media Server Communication Manager up to release 5.2.1
Implementing Avaya Integrated Management Release 6.0 June 2010 11 Application environment
System Release S8500 Media Server Communication Manager up to release 5.2.1 S8510 Media Server Communication Manager up to release 5.2.1 S8700 Media Server MultiVantage and later or Communication Manager release 5.2.1 S8710 Media Server MultiVantage and later or Communication Manager release 5.2.1 S8720 Media Server Communication Manager up to release 5.2.1 S8730 Media Server Communication Manager up to release 5.2.1 S8800 Next Gen Server Communication Manager release 6.0 INTUITY AUDIX Release 5.1 and later INTUITY AUDIX LX Release IA 1.0-17.X DEFINITY AUDIX Release 3.1 or later Modular Messaging Up to release 5.2 Multipoint Control Unit (MCU) Release 7.2 S8300 INTUITY AUDIX MultiVantage IP600/DEFINITY ONE AUDIX Release 9 or later INTUITY Interchange Release 5.1 or later Call Management System (CMS) Release 8.3 or later CONVERSANT Release 7.0 or later SIP Enablement Services (SES) Up to release 5.2.1 only Converged Communications Server Release 1.0 or later (CCS) Secure Services Gateway (SSG) Release 3.0 or later Secure Access Link gateway (SAL) Release 1.8
Note: Avaya does not guarantee that Avaya Integrated Management System release 6.0 applications functions properly with releases subsequent to Avaya Aura® Communication Manager release 6.0. Avaya recommends that you upgrade Integrated Management whenever the Avaya Aura® Communication Manager software is upgraded to ensure support.
12 Implementing Avaya Integrated Management Release 6.0 June 2010 Hardware and software requirements
Hardware and software requirements
Customers are responsible for the hardware platform, operating system, software, and network used to host the Avaya Integrated Management applications. The minimum hardware and software requirements needed to support the Avaya Integrated Management applications are provided according to the Avaya Integrated Management offers as follows: • Site Administration: Client computer requirements on page 13 • Performance and Administration: Server requirements on page 14 • Performance and Administration: Client computer requirements on page 15 • Network Management: server requirements on page 16 • Network Management: client computer requirements on page 18 In addition to the specifications provided in these tables, Avaya recommends the use of servers that are certified for use with Red Hat Enterprise Linux as listed on Hardware Compatibility List of Red Hat, which can be found at: http://hardware.redhat.com/hcl/. Use of a computing platform that is below the recommended configurations may result in poor performance.
Related topics: Site Administration: Client computer requirements on page 13 Performance and Administration: Server requirements on page 14 Performance and Administration: Client computer requirements on page 15 Network Management: server requirements on page 16 Network Management: client computer requirements on page 18
Site Administration: Client computer requirements
To install the applications provided in the Site Administration offer, the Microsoft Windows computer must meet the minimum requirements provided in Table 3: Site Administration: Microsoft Windows client computer requirements on page 14.
Note: See Avaya Integrated Management Release 6.0 Overview for a description of the applications included in the Site Administration offer.
Implementing Avaya Integrated Management Release 6.0 June 2010 13 Application environment
Table 3: Site Administration: Microsoft Windows client computer requirements
Component Required Comments Operating System Microsoft Windows XP Professional with Service Pack 3, 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) with Service Pack 2, Microsoft Windows Vista Enterprise (32- bit and 64-bit editions) with Service Pack 2, Microsoft Windows 7, Microsoft Windows 2008 Standard Edition server with Service Pack 2, or Microsoft Windows 2008 Enterprise Edition server with Service Pack 2 Processor latest Intel or AMD-based processors Hard Drive 1 GB Required to install all of the client components. Memory 512 MB RAM Monitor SVGA 1024 X 768 display Network TCP/IP 10/100 Network Card Connectivity Modem 56 Kbps Modem May be required for remote access to the computer. Other Software Internet Explorer 6.0 with Service Pack 1 Required to access the or Service Pack 2, Internet Explorer 7.0 Integrated Management Service Pack 1, or Internet Explorer 8.0, Launch Page and Web- Mozilla Firefox 3.0 or 3.5 and Java based clients. Runtime Environment 1.6.0_16.
Performance and Administration: Server requirements
To install the applications provided in the Performance and Administration offer (formerly System Management offer), the server must meet the minimum requirements provided in Table 4: Performance and Administration: Red Hat Enterprise Linux server requirements on page 15.
14 Implementing Avaya Integrated Management Release 6.0 June 2010 Hardware and software requirements
Note: See Avaya Integrated Management Release 6.0 Overview for a description of the applications included in the Performance and Administration offer. On Red Hat Enterprise Linux (RHEL), an incorrectly configuredetc/hosts file causes the failure of IMDAddApp or mfpmconfig. Before you install Performance and Administration, configure the etc/hosts file for Performance and Administration by adding the following lines at the end of the hosts file. • 127.0.0.1 localhost localhost.localdomain • 135.27.155.141 vmwaremsa1.ccdsv.com vmwaremsa1 Table 4: Performance and Administration: Red Hat Enterprise Linux server requirements
Component Required Comments Operating System RHEL release 5.4 or earlier (32-bit and Only English operating 64-bit x86 version) systems are supported Requires RHEL release Note: 5.4 for new installations You can install Performance and Supports RHEL release 4.x Administration on VMWare running for systems upgrading to one of the supported operating release 6.0 systems. Processor latest Intel or AMD-based processors Supports a maximum of two processors Hard drive 10 GB Memory 2.0 GB RAM Network TCP/IP 100 Mbit Network Card Connectivity Web Browser Not required Does not support Linux Web client Monitor SVGA 1024 X 768 display
Performance and Administration: Client computer requirements
Once you install the applications on the Linux server, you can access them from the Linux server, or from a Windows client computer using a Web browser. The client computer must meet the minimum requirements provided in Table 5: Performance and Administration: Microsoft Windows Client computer requirements on page 16.
Implementing Avaya Integrated Management Release 6.0 June 2010 15 Application environment
Table 5: Performance and Administration: Microsoft Windows Client computer requirements
Component Required Comments Operating System Microsoft Windows XP Professional with Service Pack 3, 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) with Service Pack 2, Microsoft Windows Vista Enterprise (32- bit and 64-bit editions) with Service Pack 2, Microsoft Windows 7, Microsoft Windows 2008 Standard Edition server with Service Pack 2, or Microsoft Windows 2008 Enterprise Edition server with Service Pack 2 Processor latest Intel or AMD-based processors Hard Drive 10 GB Required to install all of the client components. Memory 1 GB RAM Monitor SVGA 1024 X 768 display Network TCP/IP 10/100 Network Card Connectivity Modem 56 Kbps Modem Optional Other Software Internet Explorer 6.0 with Service Pack 1 Required to access the or Service Pack 2, Internet Explorer 7.0, Integrated Management or Internet Explorer 8.0. Launch Page and Web- Java Runtime Environment 1.6.0_16 based clients. Mozilla Firefox 3.0 or 3.5
Network Management: server requirements
To install the applications provided in the Network Management offer, the server must meet the minimum requirements provided in Table 6: Network Management: Microsoft Windows server requirements on page 17.
Note: Because Network Management release 6.0 supports VMWare-based installations, you can use the same hardware with multiple virtual machines to install Network Management on a
16 Implementing Avaya Integrated Management Release 6.0 June 2010 Hardware and software requirements
virtual machine. The system resources of the virtual machine must meet the minimum system requirements provided in Table 6: Network Management: Microsoft Windows server requirements on page 17. For a description of the applications included in the Network Management offer, see Avaya Integrated Management Release 6.0 Overview. Table 6: Network Management: Microsoft Windows server requirements
Component Required Comments Operating System Microsoft Windows XP Professional with Only English operating Service Pack 3, systems are supported. Microsoft Windows 2003 Standard Edition server with Service Pack 2, Microsoft Windows 2003 Enterprise Edition server with Service Pack 2, Microsoft Windows 7, Microsoft Windows Vista Business with Service Pack 2 (32-bit and 64-bit editions), Microsoft Windows Vista Enterprise Service Pack 2 (32-bit and 64-bit editions) Microsoft Windows 2008 Standard Edition server with Service Pack 2, or Microsoft Windows 2008 Enterprise Edition server with Service Pack 2
Note: You can install Network Management on VMWare running one of the supported operating systems. Processor latest Intel or AMD-based processors Supports a maximum of two processors Hard Drive 40 GB Memory for 2.0 GB RAM Network TCP/IP 100 Mbit Network Card Supports only one Connectivity network interface. Does not support dual network interface cards (NICs) or additional software network interfaces, such as a VPN interface. Modem 56 Kbps modem for remote access Optional Monitor SVGA 1024 X 768 display Web Browser Internet Explorer 6.0 with Service Pack 1 Required to access the or Service Pack 2, Internet Explorer 7.0 Integrated Management
Implementing Avaya Integrated Management Release 6.0 June 2010 17 Application environment
Component Required Comments with Service Pack 1, Internet Explorer 8.0 Launch Page and Web- or Mozilla Firefox 3.0 or 3.5. based clients.
Network Management: client computer requirements
Once you install the Network Management applications on the Windows server, you can access the applications from the Windows server, or from a Windows client computer using a Web browser. The client computer must meet the minimum requirements provided in Table 7: Network Management: Microsoft Windows client computer requirements on page 18. Table 7: Network Management: Microsoft Windows client computer requirements
Component Required Comments Operating System Microsoft Windows XP Professional with Service Pack 3, Microsoft Windows 2003 Standard Edition server with Service Pack 2, Microsoft Windows 2003 Enterprise Edition server with Service Pack 2, Microsoft Windows 7, Microsoft Windows 2008 Standard Edition server with Service Pack 2, or Microsoft Windows 2008 Enterprise Edition server with Service Pack 2 Processor latest Intel or AMD-based processors Hard Drive 10 GB Required to install all of the client components. Memory 1 GB RAM Monitor SVGA 1024 X 768 display Network TCP/IP 10/100 Network Card Connectivity Modem 56Kbps Modem Optional. May be required for remote access to the client computer. Other Software Internet Explorer 6.0 with Service Pack 1 Required to access the or Service Pack 2, Internet Explorer 7.0 Integrated Management with Service Pack 1, Internet Explorer 8.0, Launch Page and Web- Mozilla Firefox 3 or 3.5 and Java Runtime based clients. Environment 1.6.0_16
18 Implementing Avaya Integrated Management Release 6.0 June 2010 Connectivity requirements
Connectivity requirements
Avaya Integrated Management requires a local area or wide area network connection to all network devices and supporting databases. Customers are responsible for designing and implementing local area or wide area network connections. The network connections must be in place and tested prior to Integrated Management implementation. Assistance with network setup is not part of an Avaya Integrated Management offer but may be performed by Avaya Services under a different offer. Implementation requires the following network information: • IP address of each DEFINITY® system. • IP address of each INTUITY® Audix system. • IP address of each S8300X, S85XX, S87XX or S8800 media server. • C-LAN port used for SAT access on each DEFINITY® system, S8300X, S85XX, S87XX , or S8800 media server.
Hardware and software requirements for remote access
Table 4: Performance and Administration: Red Hat Enterprise Linux server requirements on page 15 and Table 6: Network Management: Microsoft Windows server requirements on page 17 provide the requirements for a modem and remote access software on Microsoft Windows and Red Hat Linux-based computing platforms. However, where multiple network management servers are present and connected through an IP network, only one network management server requires remote access capabilities. You can access the remaining network management servers through a Telnet session originating at the server with remote access. This arrangement is not dependent on the operating systems (Linux or Windows Server) of the network management servers. For more details on this topic, see Remote connectivity on page 30.
Symmetric Multi-Processor support
Linux-based applications in Avaya Integrated Management require the latest kernel from Red Hat to run in a Symmetric Multi-Processor (SMP) environment. Microsoft and Red Hat each provide a Web site where customers can download patches to the Windows and Linux operating systems, respectively. Avaya recommends that customers update their servers, as patches correct software bugs and also contain security updates.
Implementing Avaya Integrated Management Release 6.0 June 2010 19 Application environment
Note: There are known issues with the Linux SMP kernel and Equinox serial port card systems. Customers are responsible for serial port card systems, drivers, and issues related to their working with the Red Hat Linux operating system. Avaya support engineers do not diagnose or fix the issues related to the serial port card systems.
20 Implementing Avaya Integrated Management Release 6.0 June 2010 Chapter 2: Implementation services
Product packaging
Avaya Integrated Management offers: • Site Administration (formerly Administration Tools) • Performance and Administration (formerly System Management) • Network Management (formerly Enterprise Network Management) For more information about the offers, see Avaya Integrated Management Release 6.0 Overview. Irrespective of product packaging, Avaya provides implementation services for the following individual applications on the customer’s computing platform: • Avaya Network Management Console with VoIP System View • Avaya MultiSite Administration • Avaya Fault and Performance Manager • Avaya SMON Manager
Note: Avaya SMON Manager is not available for users installing Network Management release 6.0 for the first time. Avaya SMON Manager is still available to Network Management users if your system is upgraded from a previous release to Network Management release 6.0. • Avaya Site Administration • Avaya Provisioning and Installation Manager for Branch Gateways • Avaya Provisioning and Installation Manager for IP Office • IP Office Manager • Avaya Secure Access Administration • Avaya Software Update Manager • Avaya Configuration Backup Restore (formerly Avaya Configuration Backup and Restore Manager) • Avaya NM Backup Utility (formerly ENM Backup Utility) and NM Easy Restore Utility (formerly ENM Easy Restore Utility)
Implementing Avaya Integrated Management Release 6.0 June 2010 21 Implementation services
Customer implementation options
Customers can install most of the Avaya Integrated Management applications themselves. However, owing to the complexities in installing and configuring the applications, Avaya recommends that the customers seek support from Avaya Services to implement any of the following applications: • Site Administration • Performance and Administration • Network Management During installation, if the customers require assistance with the installation or configuration of an Avaya Integrated Management application, they can contact Avaya Global Technical Services.
Note: The charges may apply for Global Technical Services assistance with application installation or configuration. Avaya Global Technical Services also provide warranty and maintenance services after the application is installed and configured. An application is considered installed when the implementation verification tasks defined in Implementation verification on page 32 are successfully completed. Avail Avaya Global Technical Services support at 1-800-242-2121, and follow the prompts for “Avaya Integrated Management.”
Overview of Avaya Implementation Services
Avaya implementation services are available for individual or small groups of applications included in Avaya Integrated Management. Owing to installation and configuration complexities, it is recommended that Avaya Services implement Avaya MultiSite Administration and Avaya Fault and Performance Manager. The customer may choose to implement the remaining applications or have Avaya Services perform these implementations. Basic implementation services can be provided in the following ways: Remote implementation: Data Network Implementation Engineers can perform basic implementation remotely using remote access technology (for example, dial-up modem) to access the customer servers. The Data Network Implementation Engineer is in telephone contact with the designated customer
22 Implementing Avaya Integrated Management Release 6.0 June 2010 Overview of Avaya Implementation Services
representative as necessary during the remote implementation process. The customer representative provides the following assistance during implementation: • Verifies server readiness (system is turned on and the operating system is started). • Verifies availability of remote connectivity to the customer servers and managed devices. For example, voice systems. Once the customer representative verifies the above requirements, the Data Network Implementation Engineer remotely configures and customizes the application. Onsite installation: For customers in the United States, onsite installation is available for an additional charge. On customer request, a field technician is dispatched to the customer site to replace the customer representative. The field technician acts as the hands of the remote Data Network Implementation Engineer. The onsite field technician assists with the implementation as follows: • Verifies server readiness (system is powered-on and the operating system is booted) • Verifies availability of remote connectivity to the customer servers and managed devices. For example, voice systems. Once these activities are completed, the field technician leaves the customer site while the remote Data Network Implementation Engineer completes the configuration and customization of the application software. Onsite implementation: Onsite Implementation is an add-on offer. The Data Network Implementation Engineer performs the implementation at the customer site. Onsite installation and onsite implementation should never be ordered together.
Related topics: Basic implementation on page 23
Basic implementation
Basic implementation services include: • Installation of an Avaya Integrated Management application on a customer-supplied server. • Configuration of the application to operate with one voice or messaging system (DEFINITY or INTUITY) or one Avaya P330device or stack as appropriate for the application. • Verification that the application operates correctly with that managed device. Basic implementation services do not include setup of customer server hardware or operating environment, or design and implementation of network connectivity.
Implementing Avaya Integrated Management Release 6.0 June 2010 23 Implementation services
For Avaya Integrated Management applications that manage voice systems, you must configure some parameters on the voice system for it to operate with the application. For Avaya Integrated Management applications that manage voice systems, some parameters must be configured on the voice system for it to operate with the application. In particular, you require a login and password for all applications. Avaya recommends an application-specific login to enable appropriate access rights and to create an application-specific audit trail in the voice system log. In addition, some applications require configuration of the IP address of the network management server and alarm notification information into the voice system.
Note: In all cases, Data Network Implementation Engineering services described in this document do not include administration of configuration parameters on any Avaya ECLIPS or DEFINITY voice systems. Avaya provides the following additional services on customers' request: • Configuration of Managed Devices Offer: The customer can request Avaya Services to configure Avaya Integrated Management applications to work with additional managed devices. • Solution Evaluation Offer: The customer can request a Data Network Implementation Engineer to work with them through telephone for a 4-hour block of time to assess configuration and customization requirements for any or all Avaya Integrated Management applications. The customer can order this offer in multiple units if more time is required. Where custom work is required, the evaluation results in a proposed statement of work and price.
Services organizations involved in Avaya Integrated Management implementations
Avaya Communications, Solutions, and Integration (CSI) Group of Software Services provides implementation services for Avaya Integrated Management applications. The CSI Group consists of the following two teams: Converged Solutions Implementation Engineering: For more information about the CSI Group, see Avaya Professional Services on page 6. Data Network Implementation Engineering: The Data Network Implementation Engineering (formerly known as RNIS) team comprises the following service groups: • Data Help Desk (DHD): The primary objective of DHD is management and scheduling of Data Network Implementation Engineering resources. The DHD team:
24 Implementing Avaya Integrated Management Release 6.0 June 2010 Services organizations involved in Avaya Integrated Management implementations
- receives and tracks all requests to engage Data Network Implementation Engineering support. - reviews requests for assignment feasibility - enters requests into an internal tracking system - assigns request to an Implementation Engineer and a Case Implementation Coordinator (CIC) associate • Case Implementation Coordinator (CIC): An internal administrative group that tracks Data Network Implementation Engineering service orders from receipt to completion. The CIC team: - interfaces with all sales teams for service order accuracy - confirms or negotiates service delivery dates with customers - provides status on service progress throughout the life cycle of an order - where applicable, ensures that the necessary FSO/ISO resources are scheduled for service projects - at the completion of service, contacts the customer to gain acceptance of the work performed • Data Network Implementation Engineer: The Data Network Implementation Engineer: - receives the order documentation, including the Implementation Request Form (IRF) and Configuration Request Forms (CRFs) from the DHD team and creates the Installation Specification. - gathers additional information from the customer technical contact to add to the Installation Specification. The Installation Specification provides technical information to guide the implementation and is available to Avaya technical services teams that provide maintenance support for the applications. See Service Request Documentation on page 25 for more information about the IRF and CRFs.
Related topics: Service Request Documentation on page 25
Service Request Documentation
When a customer places an order for implementation services for Avaya Integrated Management applications, the customer must work with your account team to complete an Implementation Request Form (IRF) and applicable Configuration Request Forms (CRFs). These forms provide information that the Data Network Implementation Engineer uses to configure the Avaya Integrated Management software to meet customer requirements.
Implementing Avaya Integrated Management Release 6.0 June 2010 25 Implementation services
Related topics: Implementation Request Form on page 26 Configuration Request Form on page 26
Implementation Request Form
The Implementation Request Form (IRF) provides basic customer contact and site information, including the following: • Order and contact information • Product and services requested • Application description • General network information
Configuration Request Form
The CRF contains information that describes the customer requirements for the implementation of the specific application, for example: • Information on each voice system or data device to be configured • Filters for forwarding of alarms (for Avaya Fault and Performance Manager). Submit the Linux CRF for implementation of one or more of the following Linux-based applications: • Avaya Fault and Performance Manager • Avaya MultiSite Administration • Avaya Integrated Management Database Submit the Windows CRF for implementation of one or more of the following Windows- based applications: • Avaya Network Management Console with VoIP System View • Avaya Provisioning and Installation Manager for Branch Gateways • Avaya Provisioning and Installation Manager for IP Office • IP Office Manager
26 Implementing Avaya Integrated Management Release 6.0 June 2010 Responsibilities of Customer and Avaya
Responsibilities of Customer and Avaya
Table 8: Responsibilities: Customer and Avaya on page 27 summarizes the responsibilities of the customer and the Avaya Data Network Implementation Engineering team for implementation of Avaya Integrated Management applications.
Note: The customer must complete all requirements prior to the scheduled start date of implementation. For a complete list of customer responsibilities, contact the Data Help Desk. For all Data Network Implementation Engineering service orders, the customer must: • Identify a principal contact for this work • Schedule a time with the Data Network Implementation Engineering for the implementation • Complete and submit the Implementation Request Form (IRF) and Configuration Request Forms (CRFs) For remote implementation, the customer must provide an onsite contact to assist during the installation. For onsite installations or on-site implementations, the customer must provide Avaya personnel with the access to appropriate facilities and computer systems.
Note: If required documentation is not provided to the Implementation Engineer or dial-up connectivity is not verified at least five business days prior to the scheduled implementation date, the implementation will be rescheduled to the next available date.
Responsibilities of Customer and Avaya
Table 8: Responsibilities: Customer and Avaya
Task Task Customer Avaya no. 1 Software and Hardware Procurement:
Platform and Software Procurement
Server hardware ✓
Microsoft Windows Server Operating System ✓
Red Hat Linux Enterprise Server ✓
Implementing Avaya Integrated Management Release 6.0 June 2010 27 Implementation services
Task Task Customer Avaya no.
Connectivity Device Procurement
Remote access equipment to support product ✓ maintenance 2 Platform Installation and Configuration:
Microsoft Windows Installation and Configuration ✓
Hardware-specific patches and drivers installation ✓
LAN Interface Card configuration ✓
Platform Acceptance Test ✓
Verification of Platform Readiness ✓
Red Hat Linux Enterprise Server Installation and ✓ Configuration
Hardware-specific patches and drivers installation ✓
LAN Interface Card configuration ✓
Platform Acceptance Test ✓
Verification of Platform Readiness ✓
NMS O/S Installation and Configuration (optional) ✓
Hardware-specific patches and drivers installation ✓
LAN Interface Card configuration ✓
Install and Configure Trouble Ticketing software ✓
Platform Acceptance Test ✓
Verification of Platform Readiness ✓ 3 Switch and Connectivity Configuration and Testing:
Remote access (connected through phone line) ✓
LAN and IP connectivity ✓
Creation of application-specific administration user ID and ✓ password on managed voice and messaging systems
Administration of server IP addresses on voice systems ✓ (where required) 4 Avaya Integrated Management Application Installation and Configuration:
Site Administration ✓ ✓
28 Implementing Avaya Integrated Management Release 6.0 June 2010 Implementation tasks
Task Task Customer Avaya no.
Avaya Network Manager ✓ ✓
Avaya Integrated Management Database ✓ ✓
Avaya Fault and Performance Manager ✓
Avaya MultiSite Administration ✓
Avaya Provisioning and Installation Manager for Branch ✓ Gateways
Avaya Provisioning and Installation Manager for IP Office ✓
IP Office Manager ✓ 5 Avaya Integrated Management integration with NMS:
Avaya Network Manager ✓ ✓
Avaya Fault and Performance Manager ✓ 6 System Verification and Acceptance:
Verify proper operation of Avaya Integrated Management ✓ applications
Customer acceptance ✓
Implementation tasks
Implementation of Avaya Integrated Management applications includes the following additional tasks:
1. Platform and Network Readiness • Remote connectivity • Computing platform • IP connectivity 2. Installation and configuration of one or more of the Avaya Integrated Management applications on customer management servers 3. Implementation verification
Implementing Avaya Integrated Management Release 6.0 June 2010 29 Implementation services
Remote connectivity
For remote implementations, the Data Network Implementation Engineer must have remote access to the customer’s network management server(s). Avaya Services also requires remote access for ongoing maintenance support of the installed Avaya Integrated Management applications. The customer is responsible for the installation, configuration, and testing of modems on the server prior to implementation of the Avaya Integrated Management applications. Remote access is typically provided by an analog modem connected directly to the server in conjunction with an analog phone line with a telephone number accessible on the public phone network. Testing must include: • Establishing a dial-up connection and initiation of a pcAnywhere session on a Windows server, and • Establishing a dial-up connection and initiation of a Telnet session from the Linux command prompt on a Linux server. Where multiple network management servers are present and connected through an IP network, only one network management server requires remote access capabilities. The remaining network management servers may be accessed through a Telnet session originating at the server with remote access. This arrangement is not dependent on the operating systems (Linux or Windows Server) of the network management servers. If a Linux server hosts remote access, a modem must be connected to serial port COM1 (ttyS0). While internal and USB modems can be configured to work with Red Hat Linux, Avaya recommends a US Robotics Sportster 56k external modem to provide reliable remote connectivity to support remote implementation and maintenance services. No additional software is required on Linux servers because the Red Hat Linux installation loads Virtual Network Computing (VNC) software. The Implementation Engineer uses a modem to establish a dial-up point-to-point-protocol (PPP) connection. Once the PPP session is established, the Implementation Engineer can use VNC to continue installation, configuration, and verification of the Avaya Integrated Management applications. If a Windows server hosts remote access, it is the customer’s responsibility to obtain and load Symantec pcAnywhere remote control software version 10.0 or later. This enables the Implementation Engineer to accomplish remote implementation of Avaya Integrated Management applications, and it is also required for warranty and maintenance services provided by Avaya Services.
Note: Adjunct products such as INTUITY Audix and Call Management Systems send alarms to an Avaya Integrated Management server through Secure Access Link or Secure Services Gateway using a Network Interface Unit. Secure Access Link or Secure Services Gateway can also be used with legacy DEFINITY R9.5 and later systems that do not support sending SNMP data directly to the Avaya Integrated Management server running Avaya Fault and Performance Manager. The legacy DEFINITY systems can use the CLAN-based IP alarming
30 Implementing Avaya Integrated Management Release 6.0 June 2010 Computing platform
feature to send the alarms to Secure Services Gateway. Secure Services Gateway monitors port 5107 for incoming alarms from the legacy DEFINITY systems.
Computing platform
The customer is responsible for acquiring servers and loading the Microsoft Windows server or Red Hat Enterprise Linux server operating systems. The computing platform must meet the minimum requirements specified in the tables under Hardware and software requirements on page 13. Failure to meet these requirements may result in poor system performance. On customer request, Avaya Services team installs the Microsoft Windows server or Red Hat Enterprise Linux server operating systems at an additional charge.
Important: The default settings are not appropriate for the Linux-based applications in Avaya Integrated Management. When loading the Red Hat Enterprise Linux server operating system, you must follow the guidelines outlined in Installing Red Hat Enterprise Linux 5.4 on page 41. Linux-based applications may fail to operate on the server if you do not follow these guidelines. After you install and configure Red Hat Enterprise Linux server software on the computing platform, the customer must verify that a dial-up connection can be established by dialing into the server through a telephone line connected to the modem on serial port COM1 (ttyS0). On successful connection, the system displays a Linux login prompt. Remote connectivity is required as a condition of warranty and post-warranty service. Where Avaya Services provide remote implementation services, the customer must verify that a dial-up connection can be established prior to the scheduled date of implementation.
IP connectivity
Data Network Implementation Engineer performs network verification prior to implementation of any server-based application in Avaya Integrated Management. This test is performed to ensure that the network management servers have IP connectivity to all devices to be managed, including voice systems, messaging systems, and data switches. It is the customer’s responsibility to design and implement local and wide area networking such that each management server has IP connectivity to each device that it manages.
Implementing Avaya Integrated Management Release 6.0 June 2010 31 Implementation services
Application installation and configuration
Based on information on the customer’s Implementation Request Form (IRF) and Configuration Request Forms (CRFs) submitted with the order and direct communications with the customer technical contact, the Data Network Implementation Engineer creates an Installation specification document. This document provides technical information to guide implementation and is available to Avaya technical services teams that provide maintenance support for the applications.
Implementation verification
Once an application is installed and configured for operation with one or more managed devices, the Data Network Implementation Engineer performs an application-specific acceptance test to verify application implementation.
Related topics: Accessing the Avaya Integrated Management Launch Products page on page 32 Verifying Avaya Fault and Performance Manager implementation on page 33 Verifying Avaya MultiSite Administration implementation on page 33 Verifying Avaya Integrated Management Database implementation on page 34 Verifying Site Administration implementation on page 35 Verifying Avaya Provisioning and Installation Manager for Branch Gateways implementation on page 35 Verifying Avaya Provisioning and Installation Manager for IP Office implementation on page 36 Verifying IP Office Manager implementation on page 36 Verifying Avaya Network Management Console implementation on page 36 Verifying Software Update Manager implementation on page 37 Verifying Avaya Configuration Backup Restore implementation on page 39 Verifying Avaya NM Backup Utility implementation on page 40 Verifying Avaya NM Easy Restore Utility implementation on page 40
Accessing the Avaya Integrated Management Launch Products page
For some applications, the acceptance test requires launching the application from the Avaya Integrated Management Launch Products page.
32 Implementing Avaya Integrated Management Release 6.0 June 2010 Implementation verification
1. In the supported browser window, type the IP address or host name of the server running the Avaya Integrated Management applications. The system displays the Avaya Integrated Management Launch Products page. 2. Click the appropriate application.
Verifying Avaya Fault and Performance Manager implementation
Once Avaya Fault and Performance Manager is installed and configured, the Data Network Implementation Engineer performs the following steps to verify proper operation with each managed voice and messaging system for which the applications are configured:
1. Verify that each DEFINITY voice system or messaging system sends alarms through one of the following gateways and forwards them to INADS: • Secure Services gateway • Secure Access Link gateway 2. Verify that the Avaya Fault and Performance Manager server receives alarms from one of the following: • Secure Services Gateway, for each element supported by Secure Services gateway. • Secure Access Link Gateway, for each element supported by Secure Access Link gateway. 3. Verify that the Avaya Fault and Performance Manager server retrieves configuration data, alarms, and error information for each voice system. 4. Generate a test alarm for each managed node and verify that Avaya Fault and Performance Manager receives the alarm.
Result In addition to verification of the application, the Data Network Implementation Engineer assists the customer in understanding the basic operations of Avaya Fault and Performance Manager.
Verifying Avaya MultiSite Administration implementation
Once Avaya MultiSite Administration is installed and configured, the Data Network Implementation Engineer performs the following steps to verify that Avaya MultiSite
Implementing Avaya Integrated Management Release 6.0 June 2010 33 Implementation services
Administration functions with each managed voice system and each messaging system for which the application was configured:
1. Verify successful client configuration by launching Avaya MultiSite Administration from the Start menu and the Avaya Integrated Management Launch Products Page. 2. Change the default admin password and report the change to the customer. 3. Create at least one Avaya MultiSite Administration user for the customer in the Avaya Integrated Management Database application. In Avaya Integrated Management Database, assign a voice system to that user.
Note: Beginning from Integrated Management Release 3.2, you assign users to voice systems and other elements only from Avaya Integrated Management Database. You do not assign users to voice systems from Avaya MultiSite Administration. 4. Verify that the queue is running for each configured voice system and messaging system. 5. Start an initialization for each configured voice system. This takes several hours. 6. Add and delete a station on each voice system. 7. Add and delete a voice mail subscriber for each messaging system. 8. Ensure that a unique login for use by Avaya MultiSite Administration is administered on each voice system. This is necessary to ensure that the Avaya MultiSite Administration cache of system changes remains accurate. 9. Configure the Task Manager to run scheduled housekeeping tasks as recommended for each task and as directed by the customer.
Verifying Avaya Integrated Management Database implementation
For Avaya Fault and Performance Manager and Avaya MultiSite Administration to manage elements, Avaya Integrated Management Database must function properly. Once you verify these applications are working correctly, this implies that Avaya Integrated Management Database is working correctly. In addition, verify if Avaya Integrated Management Database is functioning properly:
1. Add a location record for the primary installation location. 2. Configure the SMTP e-mail server in Avaya Integrated Management Database.
34 Implementing Avaya Integrated Management Release 6.0 June 2010 Implementation verification
3. Configure default SNMP parameters in Avaya Integrated Management Database. 4. Create at least one customer user login in Avaya Integrated Management Database for use in Avaya Fault and Performance Manager and Avaya MultiSite Administration. 5. Configure default security settings. 6. Configure the RADIUS server. 7. Configure Authentication, Authorization, and Accounting.
Verifying Site Administration implementation
1. Verify successful installation of Site Administration by launching from Start menu and Avaya Integrated Management Launch Products Page. 2. For upgrades from an existing version of Site Administration, verify that all customer settings remain unchanged.
Verifying Avaya Provisioning and Installation Manager for Branch Gateways implementation
1. Verify successful installation by launching from Avaya Integrated Management Launch Products Page. 2. Verify that a simple Device Profile can be created and sent successfully. 3. Verify that a simple Template can be created and sent successfully
Implementing Avaya Integrated Management Release 6.0 June 2010 35 Implementation services
Verifying Avaya Provisioning and Installation Manager for IP Office implementation
1. Verify successful installation by launching the application from the Avaya Integrated Management Launch Products Page. 2. Create a simple Device Profile and verify that it is sent successfully. 3. Create a simple Template and verify that it is sent successfully.
Verifying IP Office Manager implementation
Verify successful installation of IP Office Manager by launching the application from the Start menu.
Verifying Avaya Network Management Console implementation
1. Verify that Avaya Services are running: From the Start menu, select Programs > Avaya > Tools > Avaya Network Management Server Status. 2. Verify that the installation is successful by launching Network Management Console from the Start menu and the Avaya Integrated Management Launch Product Page. To launch Network Management Console from the Start menu, select Start > All Programs > Avaya > Avaya Network Management Console. 3. Set the following parameters from the Options dialog box of Network Management Console: • SNMP Access Parameters • Connectivity Polling Parameters • Read/Write Defaults
36 Implementing Avaya Integrated Management Release 6.0 June 2010 Implementation verification
• Communication Manager Server Parameters • Syslog Server Parameters 4. Verify that you can configure the Discovery options and successfully discover your network: a. From the Actions menu, click Discovery. b. Verify that the system displays the devices in your network in a tree structure. 5. Verify that you can successfully discover your voice network: a. From the Actions menu, click Network Discovery Wizard. b. Verify that the devices in your network appear in a tree structure. 6. Verify that you can create a simple custom view: From the File menu, click New > View. 7. Verify that you can create a network map: From the File menu, click New > New Map. 8. Verify that you can launch various Device and Network-wide Applications from the Tools menu. 9. Verify that you can perform the following tasks: a. From the status bar of the Network Management Console window, launch the Quick Log Viewer. b. View and manage the logs in the Quick Log viewer table. 10. Verify that you can perform the following tasks: a. From the Actions menu, launch the NM Log Viewer. b. View and manage the logs in the NM Log viewer table.
Verifying Software Update Manager implementation
1. Verify that the Avaya services are running: From the Start menu, click Programs > Avaya > Tools > Avaya Network Management Server Status. 2. Verify successful installation by launching Avaya Network Management Console from the Start menu and the Avaya Integrated Management Launch Product Page.
Implementing Avaya Integrated Management Release 6.0 June 2010 37 Implementation services
3. Verify that you can successfully discover your voice network using Avaya Network Management Console. For more information, see Verifying Avaya Network Management Console implementation on page 36. 4. Verify that the devices in your network appear in the tree structure in one of the Avaya Network Management Console views. 5. Verify that you can successfully launch the Avaya Software Update Manager application from the Avaya Integrated Management Launch Product Page and from the Tools menu of the Avaya Network Management Console Web interface. 6. Verify that you can discover the information in the Device table in the Avaya Configuration Backup Restore: Click Action > Download Targets Detection.
Related topics: Defining Avaya Software and Firmware Access Policy login parameters on page 38
Defining Avaya Software and Firmware Access Policy login parameters
The Avaya Support Web site displays all software, firmware, and security downloads for Avaya supported devices. To retrieve the files you are entitled to, you must define Avaya Software and Firmware Access Policy (SFAP) authorization information for your account in Avaya Software Update Manager.
1. On the File menu, click Options. The system displays the Options window. 2. Click Avaya Support Web Site. To access the Avaya Support Web Site, you require a valid “Sold-To” account number for each location and a valid “Single Sign On” (SSO) account. Avaya Software Update Manager uses this information as SFAP login parameters for authorization to the Avaya Support Web Site. For more information on the Avaya Software and Firmware Access Policy (SFAP) and “Sold To’s”, go to http:// support.avaya.com/japple/css/japple? PAGE=OpenPage&temp.template.name=SFAP. 3. Complete the following fields in the SFAP Login Parameters dialog box: a. Select the Use SFAP check box. b. In the User Name field, enter a valid SSO user name. c. In the Password field, enter the corresponding SSO password. d. In the Confirm Password field, re-enter the SSO password.
38 Implementing Avaya Integrated Management Release 6.0 June 2010 Implementation verification
e. Click Retrieve Sold To’s. The system populates a list of Sold Tos in the Sold To’s field. A “Sold To” represents the location at which a device is installed. The association between device and location is taken into consideration when checking entitlements to install software onto that device. Avaya Software Update Manager downloads software only for devices associated with the selected “Sold To”. f. From the Sold To’s field, select a “Sold To” you want to use. 4. Complete one of the following: • Click OK. The system applies the changes and closes the dialog box. • Click Apply. The system applies the changes and keeps the dialog box open.
Verifying Avaya Configuration Backup Restore implementation
1. Verify that the Avaya Services are running: From the Start menu, click Programs > Avaya > Tools > Avaya Network Management Server Status. 2. Verify that the installation is successful by launching the Avaya Network Management Console from the Start menu and the Avaya Integrated Management Launch Product Page. 3. Verify that you can successfully discover your voice network using Avaya Network Management Console. For more information, see Verifying Avaya Network Management Console implementation on page 36. 4. Verify that the devices in your network appear in the tree structure in one of the Avaya Network Management Console views. 5. Verify that you can successfully launch the Avaya Configuration Backup Restore application from the Avaya Integrated Management Launch Product Page and from the Tools menu of the Avaya Network Management Console Web interface. 6. Verify that you can discover the information in the Device table in the Avaya Network Management Console application. To verify: Click Action > Detect Devices.
Implementing Avaya Integrated Management Release 6.0 June 2010 39 Implementation services
Verifying Avaya NM Backup Utility implementation
1. Verify that the installation is successful by launching NM Backup Utility from the Tools menu of the Network Management Console Web interface and the Avaya Integrated Management Launch Product Page. 2. Verify that you can configure the Backup Options and then successfully create a backup job using the NM backup Utility wizard. 3. Verify that you can edit a backup job that is scheduled to run periodically.
Verifying Avaya NM Easy Restore Utility implementation
1. Verify that the installation is successful by launching NM Easy Restore Utility from the Start menu of the Network Management server: Select Start > Programs > Avaya > Tools > NM Easy Restore. 2. Verify that you can successfully restore the backed up data using the NM Backup Utility.
40 Implementing Avaya Integrated Management Release 6.0 June 2010 Chapter 3: Linux Server installation
Installing Red Hat Enterprise Linux 5.4
1. Insert the first Red Hat Enterprise Linux 5.4 CD into the CD-ROM drive. 2. Restart the server, and run Red Hat Enterprise Linux System Installer in graphical mode. 3. Follow the prompts until the system displays the Red Hat Enterprise Linux page. 4. Click Next. The system displays the Language Selection page. 5. Select the appropriate language, and click Next. The system displays the Keyboard Configuration page. 6. Select the appropriate keyboard, and click Next. The system displays the Installation Number dialog box. 7. Enter your Red Hat installation number, and click OK. The system displays the Install or Upgrade page. 8. Click Install Red Hat Enterprise Linux Server, and click Next. The system displays the Disk Partitioning Setup page. 9. Select Create custom layout from the drop-down list box. 10. Click Next. The system displays the Disk Setup page. 11. On the Disk Setup page: a. Click Delete to delete any partitioning of the hard drive. b. Click New to add partitions as shown in the table below titled Hard Drive Partitions. c. When you have finished adding the hard drive partitions, click Next. The system displays the Boot Loader Configuration page.
Implementing Avaya Integrated Management Release 6.0 June 2010 41 Linux Server installation
Table 9: Hard Drive Partitions
Mount Point File System Partition Size (40 Proportion of Disk Type GB HD) Space (>40 GB HD) / ext3 800 MB 2% /boot ext3 100 MB 17% /home ext3 6000 MB 1% /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%
12. Click Next to accept the default settings. The system displays the Network Configuration page. 13. Click Edit. The system displays the Edit Interface eth0 dialog box . 14. In the Edit Interface eth0 dialog box: 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. 15. On the Network Configuration page: 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 IP addresses for gateway, primary, and secondary DNS server. c. Click Next. The system displays the Time Zone Selection page. 16. Set the time zone and click Next. The system displays the Set Root Password page. 17. Enter the root user password, enter it again for confirmation, and click Next. The system displays the Package Installation Defaults page. 18. Select the Software Development check box. 19. Select the Web server check box.
42 Implementing Avaya Integrated Management Release 6.0 June 2010 Installing Red Hat Enterprise Linux 5.4
20. Click Customize now and click New. The system displays the Package Group Selection page.
Note: Do not clear any check box that the system selects by default. 21. Select the following options in sequence:
Step Left list box Right list box no. 1 Desktop Environments KDE (K Desktop Environment) 2 Applications Editors 3 Development Legacy Software Development 4 Servers FTP Server 5 Base System System Tools and complete the following: a. Click Optional packages. The system displays the Packages in System Tools dialog box. b. Select the net-snmp-utils check box. c. Select the tsclient check box. d. Click Close.
Note: If you are installing the Red Hat Enterprise Linux 64-bit operating system, select the Compatibility Arch Support check box to install the 32-bit compatibility Red Hat Package Manager (RPM) files. 22. Click Next. The installer checks for any dependencies in the selected packages. The system displays the Begin Installation page. 23. Click Next. The system displays the Required Install Media dialog box. 24. Click Next. The system displays the installation status bar. 25. Continue with the installation. 26. When the installation is complete, click Reboot.
Implementing Avaya Integrated Management Release 6.0 June 2010 43 Linux Server installation
After the server reboots, the system displays the Welcome dialog box. 27. Click Forward. The system displays the License Agreement page. 28. Click Yes, I agree to the License Agreement and click Forward. The system displays the Firewall dialog box. 29. In the Firewall field, click Disabled and click Forward. The system displays the dialog box. 30. Click Yes. The system displays the SELinux dialog box. 31. From the SELinux Setting field, select Disabled and click Forward. The system displays the dialog box. 32. Click Yes. The system displays the Kdump dialog box. 33. Follow the prompts to continue initial configuration of the operating system (such as registering the system with Red Hat).
Note: Add at least one regular user account to the system.
Caution: Do not update postgres or any components related to postgres. Doing so can cause 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 the server. 34. Click OK. 35. Log on to the server and proceed with Verifying installation of required RPM files on page 46.
Upgrading Red Hat Enterprise Linux ES 4.0 or AS 4.0 to Red Hat Enterprise Linux 5.4
1. Insert the first Red Hat Enterprise Linux 5.4 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.4 page.
44 Implementing Avaya Integrated Management Release 6.0 June 2010 up2date support for Red Hat Linux platforms
3. Click Next. The system displays the Language Selection page. 4. Select the appropriate language and click Next. The system displays the Keyboard Configuration page. 5. Select the appropriate keyboard and 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, and then click Next. The system displays the Begin Upgrade page. 9. Click the Next. The system displays the Required Install Media dialog box. 10. Click Continue. The system displays the installation status bar. 11. Continue with the upgrade. 12. When the upgrade is complete, remove the CD, and click Reboot. 13. After the server reboots, go to Verifying installation of required RPM files on page 46.
up2date support for Red Hat Linux platforms
up2date, also known as the Red Hat Update Agent, is a tool used by Red Hat Enterprise Linux. The tool downloads and installs new software and upgrades to the operating system. up2date functions as a front-end to the Red Hat Package Manager (RPM) and adds advanced features such as automatic dependency resolution. The /etc/sysconfig/rhn/sources file specifies the location where up2date searches for packages.
Caution: When you update the version of Red Hat Linux , the configuration file changes. The configuration settings for tomcat, apache, and other third-party RPMs changes resulting in the application failure.
Implementing Avaya Integrated Management Release 6.0 June 2010 45 Linux Server installation
Related topics: Proposed solution on page 46
Proposed solution
For the application to function after you upgrade Red Hat Linux using up2date, perform the following steps:
1. From the main menu, click Avaya > Up2Date Config. 2. Wait until the terminal window exits. 3. Reboot the system to start Avaya services.
Verifying installation of required RPM files
To determine whether the Red Hat Package Manager (RPM) files listed in Red Hat Package Manager (RPM) files are installed, in the terminal emulation window, at the command prompt:
1. Type rpm –q
Next steps
Note: If you have installed the 64-bit version of the Red Hat Enterprise Linux release 5.4 operating system, install the Compatibility Arch Support RPM package. This package installs the 32- bit compatibility RPMs. If any of these RPM files are not installed, install them as outlined in Installing required RPM files on page 47.
Related topics: Red Hat Package Manager files on page 47 Installing required RPM files on page 47
46 Implementing Avaya Integrated Management Release 6.0 June 2010 Verifying installation of required RPM files
RPM files installed by Performance and Administration release 6.0 on page 48 Improving system security on page 49
Red Hat Package Manager files
While you install or upgrade the Red Hat Linux operating system, the system installs the following Red Hat Package Manager (RPM) files:
RPM file Description mgetty Avaya Services use the mgetty RPM file for remote maintenance activities. You do not require this RPM file if Avaya Services personnel provides an alternate remote network access (RAS/VPN). ppp Avaya Services use the ppp RPM file for remote maintenance activities. You do not require this RPM file if Avaya Services personnel provides an alternate remote network access (RAS/VPN). vnc (located in System Tools) Avaya Services use the vnc RPM file to remotely access the graphical user interfaces for troubleshooting purposes. You do not require this RPM file if Avaya Services personnel provides an alternate method for displaying the XWindow desktop of the Linux server. vnc-server (located in X Windows System) Avaya Services uses the vnc-server RPM file to remotely access the graphical user interfaces for troubleshooting purposes. You do not require this RPM file if Avaya Services personnel provides an alternate method for displaying the XWindow desktop of the Linux server.
Installing required RPM files
To install additional Red Hat Package Manager (RPM) files:
1. Insert the Red Hat installation CD in the CD-ROM drive. 2. Open a terminal emulation window.
Implementing Avaya Integrated Management Release 6.0 June 2010 47 Linux Server installation
3. Type cd /mnt/cdrom/RedHat/RPMS. If the Linux server displays the message “directory does not exist,” mount the CD- ROM drive manually using the following steps: a. Type mount /dev/cdrom. b. Type cd /dev/cdrom/RedHat/RPMS. 4. Type rpm –iv
RPM files installed by Performance and Administration release 6.0
When you install Avaya Integrated Management release 6.0 Performance and Administration, the system automatically installs the RPM files listed below. If any of these RPM files are already installed on the Linux server, the Performance and Administration installation wizard removes them and installs the appropriate version. • httpd Avaya Integrated Management Database requires the httpd RPM. • tomcat • php (located on Web Server) Avaya Integrated Management Database requires the php RPM. • php-pgsql (located on Web Server) Avaya Integrated Management Database requires the php-pgsql RPM. • openldap (2.0.23-4) (located on Network Server) Avaya MultiSite Administration requires the openldap RPM for Modular Messaging and SSH support. • cyrus-sasl (1.5.24-25) The Avaya MultiSite Administration requires the cyrus-sasl RPM for Modular Messaging and SSH support. • openssl (0.9.6b-18) Avaya MultiSite Administration requires the openssl RPM for Modular Messaging and SSH support.
48 Implementing Avaya Integrated Management Release 6.0 June 2010 Verifying installation of required RPM files
Improving system security
Prerequisites
• Close all related ports that provide the Remote Procedure Calls (RPC) service. • You must have root access to turn off the RPC service.
To strengthen system security, Avaya recommends that you turn off the Remote Procedure Calls (RPC) service on all Linux servers that run the Avaya Integrated Management applications. At the command line prompt in the terminal emulation window:
1. Type service portmap stop. 2. Type chkconfig -levels 12345 portmap off. This ensures that the service does not start again when the Linux server is restarted.
Implementing Avaya Integrated Management Release 6.0 June 2010 49 Linux Server installation
50 Implementing Avaya Integrated Management Release 6.0 June 2010 Index
A H Additional resources ...... 8 Avaya hardware and software requirements ...... 13 support resources ...... 5 Hardware and software requirements Avaya Configuration Backup Restore ...... 39 for remote access ...... 19 Avaya contact information ...... 8 Avaya implementation services I overview ...... 22 Avaya Integrated Management Launch Products page Implementation Request Form (IRF) ...... 26 ...... 32 Application Description ...... 26 Avaya Provisioning and Installation Manager for IP Office Order and Contact Information ...... 26 ...... 36 Product and Services Requested ...... 26 implementation services B onsite implementation ...... 22 onsite installation ...... 22 basic implementation services ...... 23 remote implementation ...... 22 additional services ...... 23 implementation tasks ...... 29 Improving system security C turn off the Remote Procedure Calls (RPC) service ...... 49 Case Implementation Coordinator (CIC) ...... 24 installing Client computer requirements ...... 13 Red Hat Enterprise Linux ...... 41 Client computer Requirements required RPM files ...... 47 for Network Management ...... 18 Integrated Management Compatibility applications ...... 21 messaging systems ...... 11 offers ...... 21 Configuration Request Form (CRF) ...... 26 services organizations ...... 24 Linux ...... 26 Integrated Management Compatibility Windows ...... 26 voice systems ...... 11 Connectivity or Network Connections ...... 19 Integrated Management Database ...... 34 contact information ...... 8 Integrated Management overview ...... 11 Customer implementation options ...... 22 INTUITY Audix system ...... 19 IP Office Manager ...... 36 D N Data Help Desk (DHD) ...... 24 Data Network Implementation Engineers ...... 24 Network Management ...... 16 defining SFAP login parameters ...... 38 P DEFINITY system ...... 19 Performance and Administration G client computer requirements ...... 15 computer requirements ...... 15 General Network Information ...... 26 server requirements ...... 14 Global Technical Services ...... 22 Proposed solution ...... 46
Implementing Avaya Integrated Management Release 6.0 June 2010 51 Provisioning and Installation Manager for Branch Specific implementation tasks Gateways ...... 35 application installation and configuration ...... 32 Purpose ...... 5 computing platform ...... 31 implementation verification ...... 32 IP connectivity ...... 31 R remote connectivity ...... 30 Symmetric Multi-Processor support ...... 19 Red Hat Package Manager (RPM) files ...... 47 resources U Avaya Global Services Delivery (GSD) ...... 7 up2date Avaya Global Technical Services ...... 7 support for Red Hat Linux platforms ...... 45 Avaya Professional Services ...... 6 Upgrading Customized management solutions for Avaya Red Hat Enterprise Linux ES 4.0 or AS 4.0 to Red Integrated Management ...... 7 Hat Enterprise Linux 5.4 ...... 44 Resources Customized management solutions for Avaya V Integrated Management ...... 7 Responsibilities verify implementation Avaya and Customer ...... 27 MultiSite Administration ...... 33 RPM files installed by verifying Performance and Administration ...... 48 Fault and Performance Manager ...... 33 Verifying Avaya Network Management Console ...... 36 S Avaya NM Backup Utility implementation ...... 40 S8300/S8500/S8700/S8710 media server ...... 19 Avaya NM Easy Restore Utility server requirements ...... 14, 16 implementation ...... 40 Service Request Documentation ...... 25 implementation ...... 36, 37 Site Administration ...... 13, 35 installation of required RPM files ...... 46 SMP ...... 19 Software Update Manager ...... 37 software requirements ...... 13 Voice and messaging system compatibility ...... 11
52 Implementing Avaya Integrated Management Release 6.0 June 2010