Avaya Integrated Management Release 6.0 Fault and Performance Manager Configuration

Avaya Integrated Management Release 6.0 Fault and Performance Manager Configuration June 2010

2010 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 Preface.................................. 7 Purpose......................................... 7 Prerequisites...................................... 7 Intended audience................................... 7 Conventions used in this document......................... 7 Additional resources................................. 8 Product documentation................................ 8 How to access documents on the Web........................ 8 Chapter 1: Resources and Notices..................... 9 Avaya Technology and Consulting......................... 9 Avaya Professional Services............................. 9 Avaya Global Services Delivery........................... 10 Avaya Global Technical Services........................... 10 Customized management solutions for Avaya Integrated Management...... 11 Avaya contact information.............................. 12 Third-party resources................................. 12 System security notices................................ 13 Network security.................................. 13 Toll fraud security................................. 14 Avaya disclaimer................................ 14 Toll fraud intervention............................. 14 Chapter 2: Overview............................. 15 Product description.................................. 15 What is new in this release.............................. 17 Avaya Fault and Performance Manager 6.0 enhancements......... 17 Supported systems.................................. 18 LDAP support................................... 19 System requirements................................. 19 Hardware.................................... 19 Hardware certification............................. 19 Software.................................... 19 Configuration overview................................ 20 Chapter 3: Configuring Fault and Performance Manager......... 21 Configuring a primary Fault and Performance Manager server.......... 22 Configuring a secondary Fault and Performance Manager server......... 24 June 2010 3

Contents Installing Fault and Performance Manager in a customer specified directory.. 25 Switching to the old Java plug-in........................... 25 Chapter 4: Customizing Fault and Performance Manager........ 27 Introduction...................................... 27 Setting up Communication Manager Sub Agent.................. 27 System commands.................................. 28 Start and Stop commands............................ 28 System status commands............................. 29 Backing up the Fault and Performance Manager database............. 29 Restoring the Fault and Performance Manager database............. 30 Easy backup and restoration of Fault and Performance Manager configuration data30 Chapter 5: Configuring SNMP traps.................... 33 Recommended software requirements........................ 33 Configuration procedures............................... 33 Procedure 1: Launching the Maintenance Web Interface.............. 34 Procedure 2: Stopping the Master Agent...................... 35 Procedure 3: Configuring SNMP Agent....................... 36 Procedure 4: Starting the Master Agent....................... 38 Procedure 5: Adding Nodes.............................. 39 Testing the SNMP Agent............................... 39 Glossary and Abbreviations........................ 45 Chapter 6: Getting started......................... 47 Creating Fault and Performance Manager logins and roles............ 47 Procedure 1: Creating a Fault and Performance Manager role........... 49 Procedure 2: Adding a user and assigning a Fault and Performance Manager role 49 Procedure 3: Adding an LDAP group and assigning a Fault and Performance Manager role51 Starting the Fault and Performance Manager client................. 52 Configuring alarm filters............................... 53 Configuring Fault and Performance Manager in the event of an sshioexception 53 DEFINITY_ARS script............................... 54 AUDIX_ARS script................................. 55 CMS_ARS script.................................. 56 CONVERSANT_ARS script............................ 57 Starting the online Help................................ 57 4 Avaya Fault and Performance Manager Configuration

Contents Exiting the Fault and Performance Manager client................. 58 Changing your Fault and Performance Manager password............ 58 RADIUS support for Fault and Performance Manager user authentication.... 58 RADIUS authentication with LDAP authorization.............. 59 RADIUS authentication with Integrated Management Database authorization 59 Radius accounts................................ 59 Methods used for Fault and Performance Manager authentication and authorization60 Integrating Fault and Performance Manager with a Network Management System 61 Configuring Select NMS to send Traps..................... 61 Viewing a managed element............................. 63 Configuring DiskSpace Failure exceptions..................... 64 Configuring Ping Failure exceptions......................... 65 Configuring the order of carriers in G650 cabinets................. 66 Index.................................. 69 June 2010 5

Contents 6 Avaya Fault and Performance Manager Configuration

Preface Purpose This document explains how to configure Avaya Fault and Performance Manager. Prerequisites Configuring Fault and Performance Manager (FPM) requires familiarity with network administration and knowledge of the Red Hat Linux operating system. Although the information is not included in this document, it is essential for a successful installation. It is for this reason that we recommend that workstation or network administrators take the primary role in installation. Intended audience We wrote this document for workstation or network administrators. Conventions used in this document In this document, we use the following typographical conventions: We use bold type for emphasis and for any information that you should type, for example, save translation. We use Courier font for any information that the computer screen displays, for example, login. We use arrows to indicate options that you should select on cascading menus; for example, Select File > Open means choose the Open option from the File menu. June 2010 7

Preface Additional resources You may find the following additional resources helpful. For help to use Avaya Fault and Performance Manager, see the Avaya Fault and Performance Manager online help. It explains how to perform basic administration tasks. To access the online help, start Avaya Fault and Performance Manager and click Help > Help Topics. For help with complex administration tasks, use the Administering Avaya Aura Communication Manager guide, which explains system features and interactions in detail. You can access this document from the Integrated Management home page. Product documentation The latest version of Avaya Integrated Management product documentation, including this document, is available from the Avaya Support Web site. To view or download these documents from the Web, you must have access to the Internet, an Internet browser, and Adobe Reader. Adobe Reader 8.0 is provided on the Avaya Integrated Management CD and is also available from http://www.adobe.com. See How to access documents on the Web for instructions on how to view or download these documents. How to access documents on the Web To view or download documents from the Avaya Support Web site, follow these steps: 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. 4. Click the Integrated Management - All Applications link. 5. Under DOCUMENT CATEGORIES, click View all documents for the system to display a list of available documents for that product or offer. 6. Click Title to view product specific documentation. 8 Avaya Fault and Performance Manager Configuration

Chapter 1: Resources and Notices Avaya provides a variety of planning, consulting, and technical services. The sections in this chapter briefly describe the resources and services that are available. Client executives are your primary contact to obtain information and explore options to meet your specific business needs. Avaya Technology and Consulting Avaya Technology and Consulting (ATAC) works with client teams to develop detailed solutions for connectivity to Avaya Aura Communication Manager solutions. ATAC also designs network configurations. Avaya Professional Services The Avaya Professional Services (APS) team of Avaya Integrated Management (AIM) consultants offers customers the following services: 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 onsite services Onsite and remote knowledge transfer The APS Data Group consists of the following teams: Avaya Integrated Management Consultants The Avaya Integrated Management consulting team offers planning, design, implementation, consulting, and knowledge transfer services for the entire Avaya Integrated Management suite. This includes Site Administration, Voice Announcement Manager, Network Management Console with Software Update Manager, MultiSite Administrator, and Fault and Performance Manager. 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 June 2010 9

Resources and Notices project. Through proper integration and consulting, our customers can leverage the Avaya Integrated Management suite to lower the total cost of ownership, and proactively manage their VoIP network comfortably and confidently. 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 12, or contact Jon Machak at 248-213-3788 or mjk@avaya.com. Avaya Global Services Delivery Avaya Global Services Delivery (GSD) provides support to the Avaya Integrated Management client teams, field technicians, and customers. The GSD team will bill customers for support on a time and materials basis if the following conditions exist: Customers do not provide remote access. Customers do not have a current maintenance agreement. Customers do not procure and install the required systems and software as defined in the Integrated Management Services Support Plan. 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. The team will either answer your questions directly or connect you with an associate who can answer questions about the products. 10 Avaya Fault and Performance Manager Configuration

Customized management solutions for Avaya Integrated Management Customized management solutions for Avaya Integrated Management The Integrated Management Product Team understands the needs of customers and is focused on customer satisfaction. See Table 1: Customer-Accessible Resources on page 12 for contact information. The Product Team assists customers with Avaya Integrated Management projects and provides: 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 that choose to implement Integrated Management applications using Avaya Services or third party implementation services. Training Basic training can be imparted remotely using an interactive medium to display the applications and a conference bridge for audio. Onsite training can be customized to meet the needs of customers. Customized training will focus on application functionality that is relevant to the customer and provide focused knowledge transfer to facilitate application specific training. June 2010 11

Resources and Notices Avaya contact information Table 1 provides contact information that you may use if you need assistance in installing and setting up Avaya Integrated Management. Table 1: Customer-Accessible Resources Resource Contact Information Avaya Support Center Avaya Global Technical Services Avaya Professional Services (APS) Integrated Management Product Team http://www.avaya.com/support +1 800 242-2121 x15921 +1 800 730-9108, prompt 3 Send email to: mjk@avaya.com Toll Fraud Intervention +1 800 643-2353, prompt 1 Third-party resources Table 2 lists contact information for third party vendors. Table 2: Vendor web sites Vendor Microsoft Red Hat Linux Web Sites Main site: http://www.microsoft.com Main site: http://www.redhat.com 12 Avaya Fault and Performance Manager Configuration

System security notices System security notices Customers are solely responsible for the security of their system, network, and access to hardware and software. The sections that follow define the precautions that all customers should take to maintain the security of their systems. Network security Fault and Performance Manager uses the standard security features on the Red Hat Linux. Avaya strongly recommends that customers use passwords to prohibit access to their systems and to routinely change those passwords to maintain security. SECURITY ALERT:! SECURITY ALERT: Customers should always change passwords immediately after external vendors complete installation, maintenance, troubleshooting, or other tasks on their systems. June 2010 13

Resources and Notices Toll fraud security Although Fault and Performance Manager is generally not at risk for toll fraud, customers are solely responsible for the security of their entire telecommunications system. Toll Fraud is the unauthorized use of a company s telecommunications system by unauthorized parties. Unauthorized parties are persons other than the company s employees, agents, subcontractors, or persons who work on behalf of the company. Toll fraud can result in substantial additional charges for the company s telecommunications services. The system manager of the company is responsible for the security of the company s system, which includes programming and configuring the equipment to prevent unauthorized use. Avaya disclaimer Avaya does not warrant that this product is immune from unauthorized use or will prevent unauthorized use of common carrier telecommunications services or facilities accessed through or connected to it. Avaya will not be responsible for any charges that result from such unauthorized use. Toll fraud intervention If customers suspect that they are victims of toll fraud and need technical assistance, they should refer to the phone number listed in Customer-Accessible Resources on page 12. 14 Avaya Fault and Performance Manager Configuration

Chapter 2: Overview Avaya Fault and Performance Manager provides a network map or system view of your converged network, and the tabular tools to monitor the status and performance of the devices on your network. Product description Fault and Performance Manager provides graphical and tabular tools to monitor the status and performance of a network of supported systems and external devices. Fault and Performance Manager collects configuration, fault, and performance data directly from an IP enabled voice system using OSSI, a proprietary management protocol, and then displays the data in text, tables, and graphic formats. The primary features of Fault and Performance Manager include: Graphical User Interface (GUI) : The main window provides the following views of the managed nodes in your network: - System Groups, a view with a navigation tree that lists all the supported systems, and displays a colored alert symbol that indicates the highest exception level. You can expand the list to view all the configuration components and specific alert symbols for each component. - DCS Trunk Connectivity that shows the DCS connectivity between the selected nodes. - IP Trunk Connectivity that shows the IP trunk connectivity between the selected nodes. - Clusters that shows the ESS clusters and LSP clusters. Configuration : You can view the configuration and administered properties of the supported systems and managed nodes, in both graphic and table views. June 2010 15

Overview Administration : You can define the system wide parameters for the following features: - Data collection : You can define the parameters for the data to be collected from each system. The parameters include the type of data, the schedule for collecting data, and the length of time to store the data. - Exception logging : You can define the conditions to log exceptions for performance thresholds, faults, and system errors. - Exception filtering : You can specify the filters for exceptions from each supported system. Your configuration of the filters can be based on any combination of the following parameters: Severity, Category, Maintenance Object Type and Maintenance Object Location or Maintenance Object Location. Additionally, you can configure the filters to perform any combination of the following actions: E-mail, Trap, Alert, and ARS Script, or ARS Script. - Exception alerting : You can specify the alert levels for exceptions from each supported system. Alert levels may include exceptions that are critical, major, minor, or warning. The alert level and location of the exception appear in the main window for the duration that the exception exists. Report Manager : You can define the parameters for individual reports for all or selected systems. The report options include: - Performance - Configuration - Exceptions You can view the reports on screen in both table and chart formats. You can also direct the reports to a printer, HTML file, GIF file, or ASCII file. Scheduled Reports : You can schedule reports to run on an hourly, daily, weekly, or monthly basis. You can also edit and delete schedules as needed. 16 Avaya Fault and Performance Manager Configuration

What is new in this release What is new in this release Avaya Fault and Performance Manager 6.0 enhancements Support for the following Avaya Aura Communication Manager servers: VCM on S8510 server VCM on 8300D server VCM on S8800 server Support for SNMP v3 Software Duplication Parity with Hardware Duplication for Duplex configuration AFS (Authentication File System) is used with AES encryption for ASG Authentication June 2010 17

Overview Supported systems Fault and Performance Manager Release 6.0 supports configuration, alarms, and performance data for the following systems: DEFINITY ECS Releases 9.5 through 10.x Survivable Remote Processors (SRPs) Multipoint Conferencing Unit (MCU) Release 7.2 Avaya G250, G350, G430, G450, G600, and G700 Media Gateways Communication Manager (Linux) Release 2.1, 3.0, 3.1, 4.0, 5.0 and 6.0 Communication Manager Releases up to 6.0 Juniper gateways:malibu JD1.1 and JD1.2 Fault and Performance Manager treats SRPs and MCUs as Communication Manager Feature servers. Fault and Performance Manager Release 6.0 supports only alarm traps for the following systems: Avaya SIP Enablement Services (SES) Server Release 3.1 and Avaya Converged Communications Server (CCS) Release 1.0 and later Interactive Response (IR) Releases 1.0 through 1.3 DEFINITY AUDIX Releases 3.1 through 4.0 INTUITY AUDIX Release 5.1 (with or without the remote maintenance board) INTUITY AUDIX on S8100 Media Server INTUITY AUDIX LX Release 1.0 through 17.X Modular Messaging Release 1.0 and later Call Management System (CMS) R3V8.3 through R3V11 S8100 Media Server INTUITY AUDIX INTUITY Interchange Release 5.1 through 5.4 CONVERSANT Release 7.0 through 9.0 IA770 INTUITY AUDIX Option for S8300 ICC Release 1.0 through 2.0 Message Networking Release 1.0 through 3.0 Secure Services Gateway (SSG) Avaya Expanded Meet-Me Conferencing (EMMC) server 18 Avaya Fault and Performance Manager Configuration

System requirements LDAP support The Avaya supported directories for Fault and Performance Manager are openldap and Microsoft Active Directory store. Note: Note: Avaya does not support Sun 1 LDAP. System requirements Hardware You should work with your Avaya client team to determine the hardware requirements that meet your business and performance specifications. Your client team has access to the Integrated Management Services Support Plan that contains the information that they need to help you determine hardware requirements in your situation. Hardware certification Avaya requires that Fault and Performance Manager hardware must be Red Hat Enterprise Linux 5.0 certified. For the Red Hat URL, see Third-party resources on page 12. CAUTION:! CAUTION: Customers are solely responsible for the upgrade of their network platforms to meet the platform requirements for Fault and Performance Manager Release 6.0. Software Fault and Performance Manager Release 6.0 operates on Red Hat Enterprise Linux R5.0. June 2010 19

Overview Configuration overview Fault and Performance Manager configuration includes the following procedures: 1. During the software installation, use one of the following procedures. - If you want to configure a primary Fault and Performance Manager server, use the procedure in Configuring a primary Fault and Performance Manager server on page 22. - If you want to configure a secondary Fault and Performance Manager server, use the procedure in Configuring a secondary Fault and Performance Manager server on page 24. 2. If you use SNMP traps, use the configuration procedure in Configuring SNMP traps on page 33. 3. If you want to integrate Fault and Performance Manager with a Network Management System, see Integrating Fault and Performance Manager with a Network Management System on page 61 for the integration procedure. 20 Avaya Fault and Performance Manager Configuration

Chapter 3: Configuring Fault and Performance Manager This chapter explains how to configure Avaya Fault and Performance Manager during the software installation. If you want to configure a primary Fault and Performance Manager server, see the procedure Configuring a primary Fault and Performance Manager server on page 22. If you want to configure a secondary Fault and Performance Manager server, see the procedure Configuring a secondary Fault and Performance Manager server on page 24. June 2010 21

Configuring Fault and Performance Manager Configuring a primary Fault and Performance Manager server After you install the Fault and Performance Manager, to configure a primary Fault and Performance Manager server: 1. Log on to the Linux system as root. 2. At the Linux prompt type /usr/sbin/mfpmconfig and press Enter. The system displays an explanation of the reasons to enable (default) or disable SNMP Polling. The system then displays the current setting and the prompt: Do you want to reconfigure the Avaya Fault and Performance Manager 6.0 software [yes]? 3. Type yes and press Enter. The system displays the prompt: Enter FPM server IP or FQDN: [ ]? 4. Type the IP address or the fully qualified domain name (FQDN) of the Fault and Performance Manager server, and press Enter. The system displays the prompt: Shutting down FPM Server services: Configuring environment: Primary FPM server is "xxx.xxx.xxx.xxx" --------------------------------------------- Avaya Fault and Performance Manager provides for the capability of a distributed Data Collection Network of servers. This server is currently configured as a Primary data collection server. There may only be 1 Primary collection server in a network of FPM servers, and any number of Secondary data collection servers. Configure this server as the Primary Data Collection Server [yes]? 5. Type yes and press Enter. The system displays the message: Avaya Fault and Performance Manager requires a print command to be specified. This command will be used by the application when attempting to print reports to a printer. The keyword %file can be used in the print command to represent the temporary filename created for printing purposes. If %print does not appear here, the filename will be appended to the print command. 22 Avaya Fault and Performance Manager Configuration

Configuring a primary Fault and Performance Manager server Please enter a default print command to be used by the FPM applications Enter printer command [ ]? 6. Type the print command, and press Enter. The system displays the following messages: Enter the FQDN of this server to be used by the Integrated Management Database to locate this FPM application server. Enter the FQDN for FPM- [ ]? 7. Enter the FQDN of this server, and press Enter. Once Fault and Performance Manager is configured, the system displays the following message: Avaya Fault and Performance Manager software configuration was successful. June 2010 23

Configuring Fault and Performance Manager Configuring a secondary Fault and Performance Manager server After you install Fault and Performance Manager, to configure a secondary Fault and Performance Manager server: 1. Log on to the Linux system as root. 2. At the Linux prompt, type /usr/sbin/mfpmconfig and press Enter. The system displays an explanation of the reasons to enable (default) or disable SNMP Polling. The system then displays the current setting and the prompt: Do you want to reconfigure the Avaya Fault and Performance Manager 6.0 software [yes]? 3. Type yes and press Enter. The system displays the prompt: Enter FPM server IP/FQDN: [ ]? 4. Type the IP address or the fully qualified domain name (FQDN) of the Fault and Performance Manager server, and press Enter. The system displays the prompt: Shutting down FPM Server services: Configuring environment: Avaya Fault and Performance Manager provides for the capability of a distributed Data Collection Network of servers. This server is currently configured as a Primary data collection server. There may only be 1 Primary collection server in a network of FPM servers, and any number of Secondary data collection servers. Configure this server as the Primary Data Collection Server [yes]? 5. Type no and press Enter. The system displays the message: Avaya Fault and Performance Manager Secondary Data Collection Server. Enter FPM Secondary Collector Service name for this server [ ]? 6. Enter the name for the secondary Fault and Performance Manager server, and press Enter. The system displays the prompt: Enter the FQDN of this server to be used by the Integrated Management Database to locate this FPM application server. Enter the FQDN for FPM- [ ]? 24 Avaya Fault and Performance Manager Configuration

Installing Fault and Performance Manager in a customer specified directory 7. Enter the FQDN for the secondary Fault and Performance Manager server, and press Enter. Once Fault and Performance Manager is configured, the system displays the following message: Avaya Fault and Performance Manager software configuration was successful. Installing Fault and Performance Manager in a customer specified directory IM release 6.0 supports the installation of Fault and Performance Manager in a customer specified directory. The default directory continues to be /opt, but the Performance and Administration installer makes provision for users to specify an alternate directory to install Fault and Performance Manager on the Linux server. Note: Note: The equivalent for /opt in Release 6.0 is <install location>. Switching to the old Java plug-in IM ensures that fresh or upgrade installations of Performance and Administration 6.0 on RHEL 5, 32 or 64 bits, display the JRE version as 1.6.16. JRE 1.6.0_11 has been replaced with JRE 1.6.16. Performance and Administration enables the new Java Plug-in by default. However, if the user encounters problems when running the applets with the new Java Plug-in, the user can switch to the old Java plug-in. To switch to the old Java plug-in: 1. Click Start. 2. Click Control Panel. 3. Double-click Java Control Panel. 4. Click the Advanced tab on Java Control Panel. 5. Scroll to the Java Plug-in entry. 6. Clear the Enable next-generation Java Plug-in check box. 7. Click OK and restart the browser. June 2010 25

Configuring Fault and Performance Manager 26 Avaya Fault and Performance Manager Configuration

Chapter 4: Customizing Fault and Performance Manager Introduction Only the system administrator or a root user should edit the files that makes it possible for you to customize Avaya Fault and Performance Manager. The information in this chapter allows system administrators to manage the following options: Set up the Avaya Sub Agent on your Communication Manager server. Execute system commands to start and stop Fault and Performance Manager and to view the system health status. Execute database commands. Edit system configuration files to customize Fault and Performance Manager. Integrate third party products for alarm notification. Setting up Communication Manager Sub Agent For instructions to set up the Avaya Sub Agent on your Communication Manager server, see the Administering Avaya Aura Communication Manager guide. June 2010 27

Customizing Fault and Performance Manager System commands Start and Stop commands Fault and Performance Manager processes normally start automatically at Linux boot time. The commands in Table 3 give the system administrator additional control of the Fault and Performance Manager processes. Table 3: Start and Stop commands Command service mfpm-server stop service mfpm-server start service mfpm-server restart Description Stops the Fault and Performance Manager system and prevents it from starting at system boot. Starts a stopped Fault and Performance Manager system and enables it to start at system boot. Stops and immediately restarts the Fault and Performance Manager system. System administrators can view a log of the system startups and shutdowns from /var/avaya/ mfpm/logs/msglog_[0-30]. The default number of MsgLog files is 30. You can change this value. 28 Avaya Fault and Performance Manager Configuration

Backing up the Fault and Performance Manager database System status commands Table 4 provides system status commands. Table 4: System status commands Command service mfpm-server status From a web browser: http://fpmserver/cgi-bin/mfpm/status.sh /opt/avaya/mfpm/bin/mfpm gui mfpmconfig show From a web browser: http://fpmserver/cgi-bin/mfpm/config.sh CollStatus status From a web browser: http://fpmserver/cgi-bin/mfpm/collstatus.sh?cmd=status CollStatus schedule From a web browser: http://fpmserver/cgi-bin/mfpm/collstatus.sh?cmd=schedule Description Displays Fault and Performance Manager system process status Opens a graphical monitor of process status Displays the configuration of the Fault and Performance Manager server Displays the current collection queues of the Fault and Performance Manager server Displays the current scheduled collection items on the Fault and Performance Manager server Backing up the Fault and Performance Manager database Only the root user can perform the procedure to back up the Fault and Performance Manager database. Please refer to the Linux backup procedure in Avaya Integrated Management Release 6.0 Performance and Administration Installation and Upgrade. June 2010 29

Customizing Fault and Performance Manager Restoring the Fault and Performance Manager database Only the root user can perform the procedure to restore the Fault and Performance Manager database. Please refer to the Linux restore procedure in Avaya Integrated Management Release 6.0 Performance and Administration Installation and Upgrade. Easy backup and restoration of Fault and Performance Manager configuration data Fault and Performance Manager provides the ability to restore user administrable data from a backup copy in the Fault and Performance Manager application. Note: Note: The version of the software that you use to copy the backup data must correspond to the version of the software that you use to restore it. Entities that need backup include: Configuration Collection Schedule - default and per switch Alarm Filter and Collection schedule - default and per switch Performance Threshold and Alerting configuration - default and per switch Custom reports that users define The data is stored in a backup file and configured on a server. You can restore the data on a new server in the case of Fault and Performance Manager server unresponsiveness or server upgrades. Users who require a new server may want to retrieve information from a previously configured server and restore the information on the new server. Fault and Performance Manager provides the user the ability to back up all user administrable application data within Fault and Performance Manager. The types of data that Fault and Performance Manager can back up and restore are: Administration - Default Parameters such as Configuration Collection, Trunk Exceptions, Alarms or Errors, Performance Collection, Processor Occupancy Exceptions, Trunk Group Exceptions and Adjuncts Alarms or Errors - System Exceptions - System Groups - DCS Groups 30 Avaya Fault and Performance Manager Configuration

Restoring the Fault and Performance Manager database - IP Trunk Groups - Voice System Parameters - Voice Adjunct Parameters Report Manager - Report Definitions - Scheduled Reports - Trunk Group Lists Fault and Performance Manager provides two scripts for the backup and restoration of customer administrable data. The backup script is called BackUpMFPMConfigData and the restoration script is called RestoreMFPMConfigData. The permissions for these scripts ensure that only a root user has the ability to run them. BackUpMFPMConfigData The BackUpMFPMConfigData script takes the directory names and file names as arguments so that the data can be stored at a location that the user chooses. If the user does not enter any file name, along with a path, the backup will be stored at the default location. The default backup location is /var/avaya/mfpm/dbbkup and the default file name is configbackup.tar. The system displays a message that provides the user information about the location of the backed up data. The backup script checks for disk space and then takes the backup in the specified directory. Script usage: /opt/avaya/mfpm/bin/backupmfpmconfigdata output_directory/ output_filename The script executes the following steps for the backup of data when the BackupMFPMConfigData command is run as a root user. 1. Checks if the script is run by a root user. If the script is not run as root, the script exits with an error. 2. When the script is run using the h option, the system displays the usage. 3. If you have not specified a directory in the argument, the script runs a check to find the default directory. If /var/avaya/mfpm/dbbkup does not exist, the directory is created. 4. Runs a check to ensure that the postgresql service is running. 5. Checks the database size. The user receives a warning. The warning message advises the user to have at least one-tenth the space of the database size on the disk. It advises the user to quit the script if the user does not have the requisite disk space. 6. Takes all the temporary files together to create a tar file as a backup. If no argument is specified, the backup file will be configbackup.tar in /var/avaya/mfpm/dbbkup. RestoreMFPMConfigData The RestoreMFPMConfigData script takes the directory names and file names as arguments, so that the backed up data can be taken from the location the user wants. If the user does not June 2010 31

Customizing Fault and Performance Manager enter any file name, along with a path, the backed up data will be taken from the default location. The default backup location is /var/avaya/mfpm/dbbkup and the default file name is configbackup.tar. The system displays a message that asks the user if the user wants to continue with the restoration based on the file selected. Script usage: /opt/avaya/mfpm/bin/restoremfpmconfigdata input_directory/ input_file The script executes the following steps for the restoration of data. 1. Checks if the script is run by a root user. If not run as root, the script exits displaying an error. 2. When the script is run using the h option, the system displays the usage. 3. Warns the user who runs this script that the database will be cleaned when the script is run. The user gets the options of either a timout of 30 seconds to quit, or a yes or no option to continue. 4. Stops the mfpm-server. 5. Deletes the existing database. 6. Extracts the tar file. 7. Runs Updateschema u to create all the other tables. 8. Starts the Fault and Performance Manager server. 32 Avaya Fault and Performance Manager Configuration

Chapter 5: Configuring SNMP traps Communication Manager provides a method for sending traps to Avaya Fault and Performance Manager. This chapter describes how to configure the traps to be sent to Avaya Fault and Performance Manager. Recommended software requirements We recommend that users fulfil the following software requirements for complete Fault and Performance Manager support and functionality: Avaya Integrated Management Release 6.0 Communication Manager Release 6.0 Configuration procedures To configure traps for Fault and Performance Manager, you must perform the following procedures: 1. Launch the Maintenance web interface. See Procedure 1: Launching the Maintenance Web Interface on page 34 for more information. 2. Stop the Master Agent in Communication Manager. See Procedure 2: Stopping the Master Agent on page 35 for more information. 3. Configure the SNMP Agent to use Avaya Fault and Performance Manager filtering. See Procedure 3: Configuring SNMP Agent on page 36 for more information. 4. Start the Master Agent. See Procedure 4: Starting the Master Agent on page 38 for more information. 5. Add nodes that you want to manage. See Procedure 5: Adding Nodes on page 39 for more information. June 2010 33

Configuring SNMP traps Procedure 1: Launching the Maintenance Web Interface To launch the Maintenance web interface: 1. Log into the server that runs Communication Manager Release 6.0. The system displays the Integrated Management Standard Management Solutions page. Figure 1: Integrated Management Standard Management Solutions 2. Click Launch Maintenance Web Interface. The system displays the Maintenance Web Interface page. 34 Avaya Fault and Performance Manager Configuration

Procedure 2: Stopping the Master Agent Procedure 2: Stopping the Master Agent To stop the Master Agent: 1. Click Agent Status under Alarms on the navigation pane. The system displays the Agent Status page. Figure 2: Agent Status 2. Click Stop Agent. June 2010 35

Configuring SNMP traps Procedure 3: Configuring SNMP Agent To configure the SNMP Agent that helps you use Fault and Performance Manager filtering: 1. Click SNMP Agents under Alarms on the navigation pane. The system displays the SNMP Agents page. Figure 3: SNMP Agents 2. Click Following IP addresses. 3. In the IP address/fqdn field, enter the IP address or the FQDN of the server that runs Fault and Performance Manager. 36 Avaya Fault and Performance Manager Configuration

Procedure 3: Configuring SNMP Agent 4. Scroll down and select the Enable SNMP Version 1 check box. Figure 4: Fields on SNMP Agents 5. Enter the read_community_name in the Community Name (read-only) field. This string must match the information that you specified in the SNMP Read Community field on the Integrated Management Database SNMP Configuration page. 6. Enter the read-write_community_name in the Community Name (read-write) field. This string must match the information that you specified in the SNMP Write Community field on the Integrated Management Database SNMP Configuration page. 7. Select the Enable SNMP Version 2c check box. 8. Enter the read_community_name in the Community Name (read-only) field. This string must match the information that you specified in the SNMP Read Community field on the Integrated Management Database SNMP Configuration page. June 2010 37

Configuring SNMP traps 9. Enter the read-write_community_name in the Community Name (read-write) field. This string must match the information that you specified in the SNMP Write Community field on the Integrated Management Database SNMP Configuration page. 10. Scroll down and click Submit. Procedure 4: Starting the Master Agent To start the Master Agent: 1. Click Agent Status under Alarms on the navigation pane. The system displays the Agent Status page. Figure 5: Agent Status 2. Click Start Agent. 38 Avaya Fault and Performance Manager Configuration

Procedure 5: Adding Nodes If you want to use alarm filtering, you must configure alarm filters in Avaya Fault and Performance Manager. See Configuring alarm filters on page 53 for the configuration procedure. If you want to add nodes that you want to manage, see Procedure 5: Adding Nodes on page 39 for more information. Procedure 5: Adding Nodes To add nodes like voices systems and adjuncts that you want to manage, you must use the Integrated Management Database (IMD). See Avaya Integrated Management Database Release 6.0 Configuration or the Integrated Management Database online help for information on how to add nodes. Testing the SNMP Agent Use this procedure to determine whether you have properly configured Communication Manager Release 6.0 or a later version, and Avaya Fault and Performance Manager, for alarm filtering. Before you begin the procedure, make sure that you have: Configured the SNMP Agent in Communication Manager. Configured alarm filtering in Avaya Fault and Performance Manager. See Configuring alarm filters on page 53 for the configuration procedure. June 2010 39

Configuring SNMP traps To test the SNMP agent: 1. Log in to the server that runs Communication Manager Release 6.0. The system displays the Integrated Management Standard Management Solutions page. Figure 6: Integrated Management Standard Management Solutions 40 Avaya Fault and Performance Manager Configuration

Testing the SNMP Agent 2. Click Launch Maintenance Web Interface. The system displays the Maintenance Web Interface page. Figure 7: Maintenance June 2010 41

Configuring SNMP traps 3. Click SNMP Test under Alarms on the navigation pane. The system displays the SNMP Test page. Figure 8: SNMP Test 42 Avaya Fault and Performance Manager Configuration

Testing the SNMP Agent 4. Click Generate Test Trap. The system displays the SNMP Test Results page. Figure 9: SNMP Test Results The system should display the trap that is received in Avaya Fault and Performance Manager. June 2010 43

Configuring SNMP traps Figure 10 displays a sample trap in Avaya Fault and Performance Manager. Figure 10: Sample trap in Fault and Performance Manager 44 Avaya Fault and Performance Manager Configuration

Glossary and Abbreviations A APS Avaya Professional Services ATAC See Avaya Technology and Consulting on page 9. C Communication Manager Communication Manager Feature Server M managed node N Network Management Server Network Management System S SNMP Performance and Administration Server The call processing software that runs on Communication Manager Feature Servers. Formerly known as DEFINITY software. Any of the products that run Communication Manager. Formerly known as DEFINITY system, DEFINITY ECS, switch, PBX, or voice system. In this document, a managed node is any system (voice system or otherwise) that can be viewed and monitored using Fault and Performance Manager. This is the Windows server on which you can install Integrated Management applications. A system that lets you monitor the health and status of devices on your data network. Simple Network Management Protocol. This is the Linux server on which you install Fault and Performance Manager. June 2010 45

Performance and Administration Server 46 Avaya Fault and Performance Manager Configuration

Chapter 6: Getting started This chapter describes how to: Create logins and assign roles to Fault and Performance Manager users. Start the Fault and Performance Manager client from a web browser. Configure alarm filters in Fault and Performance Manager. Access the Fault and Performance Manager online help. Quit the Fault and Performance Manager client from a web browser. Change your Fault and Performance Manager password. Integrate Fault and Performance Manager with a Network Management System. Creating Fault and Performance Manager logins and roles You must log in to Fault and Performance Manager to use the Fault and Performance Manager user interface. Use Integrated Management Database to: Create Fault and Performance Manager roles Add Fault and Performance Manager users Assign Fault and Performance Manager roles to Fault and Performance Manager users You can assign one or more of the following capabilities to a Fault and Performance Manager role: Administration (Admin) This capability enables the user to access the FPM Administration menu item for the scheduling of data collection and reports, system groups, and trunk group lists from the Fault and Performance Manager user interface. BusyoutRelease This capability enables the user to busyout and release boards, trunks, trunk groups, stations and ports from the Fault and Performance Manager user interface. Acknowledge This capability enables the user to acknowledge alerts within the Fault and Performance Manager user interface. June 2010 47

Getting started ReadOnly This capability enables the user to run the Fault and Performance Manager user interface with a read-only permission. The user cannot configure voice systems or schedule reports. CreateReports This capability enables the user to: - Create new reports that will be stored on the Fault and Performance Manager server for future use - Schedule the reports to be run automatically in the background by the Fault and Performance Manager server MovePN This capability enables the user to move the port networks in an ESS cluster. Helper This capability enables the user to access the Helpdesk feature from the Fault and Performance Manager user interface. Assist This capability enables the user to automatically run the Communication Manager commands that are recommended by the Helpdesk feature when an alarm is received. PositionCarriers This capability enables the user to assign permissions to change the order of carriers in the G650 cabinets. Integrated Management Database automatically installs and configures the following default Fault and Performance Manager roles: FPMbrowse The FPMbrowse role has the ReadOnly capability. FPMadmin The FPMadmin role has the CreateReports, Admin, BusyoutRelease, Acknowledge, MovePN, Helper and Assist capabilities. You can either assign these default roles to Fault and Performance Manager users or you can create and assign custom roles. To create Fault and Performance Manager roles and logins: 1. Create Fault and Performance Manager roles. 2. Add Fault and Performance Manager users, and assign Fault and Performance Manager roles to those users. 48 Avaya Fault and Performance Manager Configuration

Procedure 1: Creating a Fault and Performance Manager role Procedure 1: Creating a Fault and Performance Manager role To create a Fault and Performance Manager role: 1. Log in to Integrated Management Database, and click FPM Roles on the navigation pane of the Integrated Management Database Administrator page. The system displays the FPM Roles page. 2. Click Add. The system displays the Add FPM Role page. 3. In the Enter Role Name field, enter the name for the Fault and Performance Manager role. 4. In the Available Capabilities list box, select the capability you want to assign to this role. If you want to assign multiple capabilities to this role, press and hold the Ctrl key and click on each capability that you want to select. 5. Click the directional arrows to transfer the capabilities to the Capabilities assigned to this role list box. The system displays the selected capabilities in the Capabilities assigned to this role list box. 6. Click Add. The system displays a page confirming that the role was added successfully. 7. Click OK. 8. Repeat Steps 2 through 7 for every Fault and Performance Manager role you want to create. When finished, add a user. For more information, see Procedure 2: Adding a user and assigning a Fault and Performance Manager role on page 49. Procedure 2: Adding a user and assigning a Fault and Performance Manager role Use this procedure to: Add a user account that can access Fault and Performance Manager Assign a Fault and Performance Manager role to this user June 2010 49

Getting started To add a group of LDAP users, see Procedure 3: Adding an LDAP group and assigning a Fault and Performance Manager role on page 51. To add a user and assign the user a Fault and Performance Manager role: 1. Click Users on the navigation pane of the Integrated Management Database Administrator page. The system displays the Users page. 2. Click New User. The system displays the Add User page. 3. In the Login field, enter the login for the user. 4. In the User Name field, enter the name of the user. 5. In the Email Address field, enter the e-mail address of the user. 6. In the Phone Number field, enter the telephone number of the user. 7. In the Password field, enter the password for the user's login. 8. In the Re-type Password field, re-enter the password for the user's login. 9. If you want to prevent this user from logging in, select the Login Disabled check box. 10. The Failed Attempts box indicates the number of failed login attempts of the user. The Default value is 0. The value increases every time the user fails in a login attempt. Security defaults, where you decide how many login failures the user is allowed, decides the maximum number of attempts a user can make to log in. 11. Select the FPM check box. The system displays the Roles button next to the FPM check box. 12. Click Roles. The system displays the Assign FPM Roles to a User page. 13. Select the check box of each role you want to assign to this user. You can assign multiple Fault and Performance Manager roles to a user. 14. Click Save. The system displays a page that confirms the role was updated successfully. 15. Click OK. 16. From the Allowed Elements box, select the elements you want this user to access. To select multiple elements, press and hold the Ctrl key, and then click on the elements. 17. Click Add. 18. Repeat Steps 2 through 17 for every Fault and Performance Manager user you want to add. When you want to quit Integrated Management Database, click Exit on the navigation pane. 50 Avaya Fault and Performance Manager Configuration

Procedure 3: Adding an LDAP group and assigning a Fault and Performance Manager role Procedure 3: Adding an LDAP group and assigning a Fault and Performance Manager role Use this procedure to: Add an LDAP group that can access Fault and Performance Manager Assign a Fault and Performance Manager role to the group Note: Note: The settings you specify for an LDAP group applies to all the members of the group. To add an LDAP group and assign a Fault and Performance Manager role: 1. Click LDAP Groups on the navigation pane of the Integrated Management Database Administrator page. The system displays the LDAP Groups page. 2. Click New Group. The system displays the Add LDAP Group page. 3. In the Group Number field, enter the number for the LDAP group. 4. In the Group Description field, enter a description of this group. 5. If you want to prevent members of this group from logging in, select the Group Disabled check box. 6. Select the FPM check box. The system displays the Roles button next to the FPM check box. 7. Click Roles. The system displays the Assign FPM Roles to a User window. 8. Select the check box of each role you want to assign to this group. You can assign multiple Fault and Performance Manager roles to a group. 9. Click Save. The system displays a page that confirms the role was updated successfully. 10. Click OK. 11. From the Allowed Elements box, select the element or elements that this group will be able to access. To select multiple elements, press and hold the Ctrl key, and then click on the elements. 12. Click Add. 13. Repeat Steps 2 through 12 for every LDAP group you want to add. June 2010 51

Getting started When you want to quit Integrated Management Database, click Exit on the navigation pane. Starting the Fault and Performance Manager client To start the Fault and Performance Manager client: 1. Enter the IP address or the hostname of the Linux server in a browser to access the Avaya Integrated Management Launch Products page. You can either use Microsoft Internet Explorer, 6.0 SP1 or a later version, or the Firefox Web browser. The system displays the Integrated Management Launch Products page. 2. Click the Performance and Administration tab on the Integrated Management web page. 3. Click Fault and Performance Manager. The system displays the Java Plugin Security Warning. 4. Click Grant this Session. The system displays the FPM Login dialog box. 5. In the Login Name box, enter your login. Note: Note: All Fault and Performance Manager logins and passwords are administered through Integrated Management Database. 6. In the Password box, enter your password. 7. Click Login. The system displays the Fault and Performance Manager window. 52 Avaya Fault and Performance Manager Configuration

Configuring alarm filters Configuring alarm filters To configure alarm filters in Avaya Fault and Performance Manager: 1. Access the Avaya Fault and Performance Manager window. 2. Click File > Administration. 3. When the system displays the administration pane, click Default Parameters > Alarms/ Errors. The system displays the Alarms/Errors page. 4. Select the alarm filter you want to change, and then click Modify. The system displays the Alarm Filter Configurator page. 5. Select the appropriate parameters. 6. When finished, click OK. The system displays the Alarms/Errors page. 7. Repeat Steps 2 through 6 for every alarm filter you want to change. 8. When finished, click Save. The filter parameters are saved in Avaya Fault and Performance Manager and updated in Communication Manager. If an error occurs when Avaya Fault and Performance Manager attempts to send the alarm filter to Communication Manager, the system displays an error message. Most errors that occur at this point are related to the SNMPv2c settings in Integrated Management Database and Avaya Fault and Performance Manager not matching the SNMPv2c settings in Communication Manager. For more information, see Procedure 3: Configuring SNMP Agent on page 36. Configuring Fault and Performance Manager in the event of an sshioexception To configure Fault and Performance Manager in the event of an sshioexception: 1. Log in as root on the Fault and Performance Manager server. 2. Execute the following commands: cd /opt/avaya/mfpm/data vi PMProp 3. At the end of the file, enter: MFPM.socketReadTimeout=300000 June 2010 53

Getting started 4. Execute the following command: mfpmconfig DEFINITY_ARS script Fault and Performance Manager looks for the DEFINITY_ARS script when one of the following events occurs: Fault and Performance Manager receives an alarm trap from the following managed nodes: - Communication Manager Feature Servers - MCU Fault and Performance Manager receives an exception event from Fault and Performance Manager for these managed nodes Fault and Performance Manager then calls the script and passes the values in the alarm notification values list to the alarm notification program. If a value is not defined, Fault and Performance Manager assigns the alarm the string NULL_FIELD. Alarm notification values: 1. System name 2. Error description 3. New status severity 4. Old status severity 5. Product ID 6. Alarm sequence number 7. Alarming Port 8. Maintenance object name 9. On board fault 10. Type of alarm 11. Alternate name for the device 12. Describes the external device 13. Product Identifier of external device 14. Building location of external device 15. Address of external device 16. Restart date time 17. Restart level 54 Avaya Fault and Performance Manager Configuration

Configuring alarm filters 18. Restart carrier 19. Restart craft demand 20. Restart escalated 21. Restart interchange 22. Restart unavailable 23. Restart cause 24. Restart spea release 25. Restart speb release 26. Restart spea update 27. Restart speb update AUDIX_ARS script Fault and Performance Manager looks for the AUDIX_ARS script if it receives an alarm trap or an exception event mentioned in the following list. Fault and Performance Manager receives an alarm trap from the following managed nodes: - DEFINITY AUDIX - Intuity AUDIX - Intuity Interchange Fault and Performance Manager receives an exception event from Fault and Performance Manager for these managed nodes Fault and Performance Manager then calls the script and passes the values in the alarm notification values list to the alarm notification program. If a value is not defined, Fault and Performance Manager assigns the alarm the string NULL_FIELD. Alarm notification values: 1. System name 2. Product ID 3. Alarm sequence number 4. Source of the alarm: - DEFINITY (for DEFINITY AUDIX) - Intuity Interchange 5. Error description 6. New status severity June 2010 55

Getting started 7. Old status severity 8. Alarm location 9. Alarm date 10. Alarm time 11. Resource 12. Fault code 13. Module ID 14. Event number 15. Count number CMS_ARS script Fault and Performance Manager looks for the CMS_ARS script when one of the following events occurs: Fault and Performance Manager receives an alarm trap from the Call Management System (CMS) Fault and Performance Manager receives an exception event from Fault and Performance Manager for the CMS Fault and Performance Manager then calls the script and passes the values in the alarm notification values list to the alarm notification program. If a value is not defined, Fault and Performance Manager assigns the alarm the string NULL_FIELD. Alarm notification values: 1. System name 2. Product ID 3. Alarm sequence 4. Error description 5. New status severity 6. Old status severity 7. Product type 8. Version 9. ID value 10. Number 11. Name 56 Avaya Fault and Performance Manager Configuration

Starting the online Help CONVERSANT_ARS script Fault and Performance Manager looks for the CONVERSANT_ARS script when one of the following events occurs: Fault and Performance Manager receives an alarm trap from the CONVERSANT system Fault and Performance Manager receives an exception event from Fault and Performance Manager for the CONVERSANT system Fault and Performance Manager then calls the script and passes the values in the alarm notification values list to the alarm notification program. If a value is not defined, Fault and Performance Manager assigns the alarm the string NULL_FIELD. Alarm notification values: 1. System name 2. Product ID 3. alarm number 4. Error description 5. New status severity 6. Old status severity 7. Location 8. Date 9. Time 10. Resource 11. Fault code 12. Module ID 13. Event number 14. Count number Starting the online Help The online help system describes how to use Fault and Performance Manager. To start the online help, log in to Fault and Performance Manager and click Help > Help Topics or Help > Current Panel. A Help button is also available on many tabs, panels, and dialog boxes. Click the Help button so that the system displays the help topic for the screen. June 2010 57

Getting started Exiting the Fault and Performance Manager client To quit the Fault and Performance Manager client, click File > Exit. Changing your Fault and Performance Manager password To change your Fault and Performance Manager password: 1. Enter the IP address or hostname of the Linux server in a browser. You can either use Microsoft Internet Explorer 6.0 SP1 or a later version, or the Firefox web browser. The system displays the Avaya Integrated Management Launch Products page. 2. In the Performance and Administration box, click Avaya Integrated Management Database. The system displays the Logon window. 3. Click Change Password. The system displays the Change Password page. 4. In the User ID field, enter your Fault and Performance Manager login. 5. In the Current Password field, enter the current password for your login. 6. In the New Password field, enter the new password you want to use for your login. 7. In the Re-Type New Password field, re-enter the new password you want to use for your login. 8. Click Change Password. 9. Click Cancel to return to the Logon page. RADIUS support for Fault and Performance Manager user authentication Fault and Performance Manager users have to be authenticated and granted user permissions. A new feature of Fault and Performance Manager 6.0 is the RADIUS authentication of Fault and Performance Manager users. RADIUS supports Fault and Performance Manager user authentication alone. Authorization or permissions for users is provided either through LDAP or locally from Integrated Management Database. MultiSite Administrator and Integrated 58 Avaya Fault and Performance Manager Configuration

RADIUS support for Fault and Performance Manager user authentication Management Database must also support RADIUS if Fault and Performance Manager is to provide support for user authentication. Fault and Performance Manager support for RADIUS authentication requires the configuration of RADIUS in Integrated Management Database and applies to both MultiSite Administrator and Fault and Performance Manager. For more information, see Avaya Integrated Management Release 6.0 Integrated Management Database Configuration. Two scenarios are possible for RADIUS authentication: RADIUS authentication with LDAP authorization that uses the Group ID RADIUS authentication with Integrated Management Database authorization RADIUS authentication with LDAP authorization The authentication proceeds in the following sequence: 1. RADIUS authenticates the login and password of the user. 2. Fault and Performance Manager retrieves the Group ID from the LDAP server. This authorization works the same way as authorization does when LDAP is used for both authentication and authorization. RADIUS authentication with Integrated Management Database authorization The authentication proceeds in the following sequence: 1. RADIUS authenticates the login and password of the user. 2. Fault and Performance Manager matches the Fault and Performance Manager role to the login ID of the user in Integrated Management Database. This authorization process works the same way as authorization does when Integrated Management Database or Fault and Performance Manager provides the local authentication and authorization. Radius accounts Fault and Performance Manager support for RADIUS authentication extends to the following requirements: Local Fault and Performance Manager roles as defined in Integrated Management Database LDAP store from open LDAP Microsoft Active Directory store June 2010 59

Getting started Fault and Performance Manager 6.0 software can be initially configured to use only the local host account, that is, the default administration account. However, clients for the supported external Authentication, Authorization and Accounting (AAA) services will be resident. Upon an upgrade, Fault and Performance Manager software is configured to use both local host accounts and LDAP. For proper functioning of the authentication mechanism, users must define a RADIUS server for RADIUS authentication and authorization. The RADIUS client of Fault and Performance Manager authenticates with the RADIUS server through the use of a shared secret. Fault and Performance Manager 6.0 interacts with the external RADIUS server through a LAN. Note: Note: Fault and Performance Manager logs all user access attempts that are authenticated externally through RADIUS. Fault and Performance Manager logs successful and failed attempts. Methods used for Fault and Performance Manager authentication and authorization Fault and Performance Manager authenticates and authorizes a user through the defined method within Integrated Management Database. The authentication mechanisms possible include: Local, LDAP and RADIUS. The authorization mechanisms possible include: local and LDAP. If the primary method has not found the user, then Fault and Performance Manager attempts to authenticate the user locally through Integrated Management Database. Integrated Management Database authenticates and authorizes Fault and Performance Manager users in two ways: Using the login group number The procedure that is used to authenticate and authorize users with the login group number is as follows: 1. A user with a user account and assigned role accesses Fault and Performance Manager. 2. The application queries RADIUS for the authentication of the user. The application uses a user name and password. 3. The application queries the LDAP server for the profile number and login group number of the user, if LDAP is configured as the authorization mechanism. The profile number is used to select a user profile within Integrated Management Database. Integrated Management Database holds the Fault and Performance Manager profile.the user profile controls the access to be provided to the user: If no group number matches the value obtained from the LDAP server, the application denies access to the user. Using matches for local Integrated Management Database permissions The procedure that is used to authenticate and authorize Fault and Performance Manager users with matches for local Integrated Management Database permissions is as follows: 1. A user accesses Fault and Performance Manager. 60 Avaya Fault and Performance Manager Configuration

Integrating Fault and Performance Manager with a Network Management System 2. The application queries RADIUS for the authentication of the user. The application uses a user name and password. 3. The application checks the local Integrated Management Database permissions for a match to the authenticated user name and uses that role for authorization, if local authorization is configured. If no matching user name is found in the RADIUS server, then a match is looked for in the local Integrated Management Database. Access to Fault and Performance Manager is also denied if no match is found in the Integrated Management Database. In all cases of failure, the last search will be conducted in the local Integrated Management Database. If no matching user name is found in Integrated Management Database, the user will be denied access to Fault and Performance Manager. Integrating Fault and Performance Manager with a Network Management System Fault and Performance Manager can send traps to any SNMP based trap receiver. You must use Avaya Integrated Management Database to integrate Avaya Fault and Performance Manager with a Network Management System. For more information, see Add a Network Management System Configuration in Avaya Integrated Management Release 6.0 Integrated Management Database Configuration. Configuring Select NMS to send Traps Use the following procedure to configure the Select NMS to send Traps feature in the Fault and Performance Manager 6.0. You can use the procedure for all the exceptions in the list because the Select NMS to send Traps check box is common to all these exceptions. The exceptions include: Trunk Exceptions - Lightly Used Trunk Exceptions - Trunk Outages Exceptions - Holding Times Exceptions Processor Occupancy Exceptions Trunk Group Exceptions Adjuncts Alarms/Errors June 2010 61

Getting started - Major Alarm Exceptions - Minor Alarm Exceptions - Warning Exceptions - Inads Exceptions System Exceptions - Data Collection Failure Exceptions - Scheduled Report Failure Exceptions - Scheduled Ping Failure Exceptions - Disk Space Failure Exceptions To configure Select NMS to send Traps: 1. Log in to the Fault and Performance Manager application. 2. Click File > Administration > Administration Root > System Exceptions. The system displays the System Exceptions page in the right contents pane. Besides tabs for DiskSpace Failure, Ping Failure, Collection Failure and Report Failure, the page displays the following check boxes: Store Exception? Alert? Email notification ARS Script Select NMS to send Traps After you install Fault and Performance Manager 6.0 and log in to the application for the first time, you will find the Select NMS to send Traps check box already selected. 3. Click the Details button beside the Select NMS to send Traps check box. The system displays the NMS Selection box. 4. Click OK. Fault and Performance Manager clears and disables the Select NMS to send Traps check box. 5. Click Save. Note: Note: Use the Select NMS to send Traps configuration procedure for both initial and upgrade installations of Fault and Performance Manager. 62 Avaya Fault and Performance Manager Configuration

Viewing a managed element Viewing a managed element Support for Fault and Performance Manager as a managed element enables Fault and Performance Manager to log exceptions and handle alerts like the /var partition running out of disk space, postgresql shutting down, collections stopping, or the Fault and Performance Manager service failing. A managed element with alerting notifies customers of disk space running low. It also alerts an administrator about disk space running out before Fault and Performance Manager stops responding and stops processing traps or collections. If an adjunct is a managed node, its description reads Fault and Performance Manager Managed Node. The prefix FPM is added to the name of a Fault and Performance Manager managed node. To view a managed element: 1. Click the System Groups tab in the FPM administration window. The system displays the System Groups page in the right contents pane. The navigation tree in the left pane displays the System groups node. 2. Click the System Groups node. The navigation tree displays the Systems node. 3. Click the Systems node. The navigation tree displays the Voice Systems and Voice Adjuncts. 4. Click the Voice Adjuncts node. The navigation tree displays all the voice adjuncts. 5. Click a Voice Adjunct with the name FPM-<fpm server name>. The system displays the Voice Adjuncts page in the right contents pane. This page provides the following details: Location, Name and Description of the selected voice adjunct 6. Click Exceptions. The system displays the Adjuncts Exception Report. It tabulates information under the following heads: Severity Type Voice System NMS Start NMS End Description: describes the nature of the exception, for example, DiskSpace Failure: FPM Server disk usage is 21%. June 2010 63

Getting started 7. Click Acknowledge. The system displays the Request box with the message Exceptions Acknowledged successfully. 8. Click OK. Configuring DiskSpace Failure exceptions IM 6.0 addresses the acute need to support the Fault and Performance Manager application as a managed element. Users need to receive alerts to any new exceptions or alarms like the /var partition running out of disk space. The user needs to be notified of disk space running low, or an administrator needs to be alerted about disk space running out before Fault and Performance Manager stops responding and stops processing traps or collections. Fault and Performance Manager logs these exceptions and handles alerts for these eventualities. Fault and Performance Manager itself facilitates sending traps to NMSs and sending e-mails to administrators for exceptions alerted against the Fault and Performance Manager adjunct. To configure DiskSpace Failure exceptions: 1. Click File > Administration > Administration Root. The system displays the Administration Root page in the right contents pane. 2. Double-click System Exceptions on the Administration Root page. The system displays the System Exceptions page. 3. Click DiskSpace Failure on the System Exceptions page. The system displays the Disk Space Failure Exceptions box. 4. Configure the following parameters: a. Select the Store Exception? check box. b. Select the Alert? check box, if needed. c. Select the Email Notification check box, if needed. If you select the check box, enter your e-mail address in the e-mail definition box. d. Select the ARS Script check box, if needed. e. Select the Select NMS to send traps check box, if needed. f. Click Details to select the available NMSs. g. You can change the following default values if necessary: The default Level 1 Severity is Minor. 64 Avaya Fault and Performance Manager Configuration

Configuring Ping Failure exceptions The default Level 1 Percentage is 70. The default Level 2 Severity is Major. The default Level 2 Percentage is 90. 5. Click Save. You can click Reset to discard any changes to the panel and reload the panel from the database. Click Help if you want to access the Fault and Performance Manager online help. Configuring Ping Failure exceptions Fault and Performance Manager has implemented a ping service that periodically sends ICMP Ping packets to the different switches and adjuncts that the Fault and Performance Manager server manages and gets ICMP responses. In the event the ICMP request fails, Fault and Performance Manager attempts to establish a TCP connection on the Echo port of the destination host. If the element is reachable, no further action is taken. If the element is not reachable, a ping successful trap is generated for the system. In Fault and Performance Manager, Ping Failure is placed under System Exceptions for a device. To configure ping failure exceptions in a device: 1. Click File > Administration > Administration Root. The system displays the Administration Root page in the right contents pane. 2. Double-click System Exceptions on the Administration Root page. The system displays the System Exceptions page. 3. Click Ping Failure. The system displays the Schedule Ping Failure Exceptions box. 4. Configure the following parameters: a. Select the Store Exception? check box. b. Select the Alert? check box, if needed. c. Select the Email Notification check box, if needed. If you have selected the check box, enter your e-mail address in the e-mail definition box. d. Select the ARS Script check box, if needed. e. Select the Select NMS to send traps check box, if needed. f. Click Details to select available NMSs. g. Set the Severity level. 5. Click Save. June 2010 65

Getting started You can click Reset to discard any changes to the panel and reload the panel from the database. Click Help if you want to access the Fault and Performance Manager online help. Configuring the order of carriers in G650 cabinets With the Graphic View display of the carriers in the G650 cabinets, a user can configure and save the order of carriers. Use the new Reorder functionality to specify the order of the carriers in the G650 cabinets. To configure and save the order of carriers: 1. Click the System Groups tab on the FPM administration screen. The system displays the System Groups page in the right contents pane and the System Groups node in the left navigation pane. The System Groups page lists the system names. 2. Click the System Groups node in the left navigation pane. The system displays the system group names on the navigation tree. 3. Click the Systems node on the navigation tree. The navigation tree displays the Voice Systems and Voice Adjuncts in the system group. 4. Click Voice Systems. The navigation tree displays the names of all the voice systems. 5. Click the name of a Voice System. The system displays the System Configuration page. 6. Click Details on the System Configuration page. The navigation pane displays a list of details for the voice system. 7. Click Cabinets on the details list. The system displays the Cabinets Configuration and Status page with the Cabinets table. 8. Click the name of any G650 cabinet in the Layout column of the Cabinets table. The system displays the FPM: <Voice System name>: Cabinet Configuration and Status page. The left pane of the page displays a table for Cabinet Configuration and Status and another table for Carriers. The right pane displays the Boards table. 9. Click Graphic View under the Carriers table. The system displays the graphical view of the carriers in the right pane. This view includes a Reorder button. 66 Avaya Fault and Performance Manager Configuration

Configuring the order of carriers in G650 cabinets 10. Click Reorder. The system displays the Reorder Carriers box. The box displays the carriers, labeled A to E along with their positions. Each carrier label appears next to a combo box with available positions numbered 1 to 5. 11. Configure the required order. 12. Click OK. Note: Note: This functionality is available only to the administrator or a user who has the PositionCarriers capability assigned in the Fault and Performance Manager role. June 2010 67

Getting started 68 Avaya Fault and Performance Manager Configuration

Index A Avaya Professional Services............. 9 Avaya Technology and Consulting (ATAC)...... 9 B Backup and Restore................ 30 backup, database................. 29 books on the web.................... 8 C commands.................... 28 system health................. 29 configuring a primary Fault and Performance Manager server22 configuring a secondary Fault and Performance Manager server24 contact information third party................... 12 contact information for Avaya............ 12 customer specified directory............ 25 D database backup..................... 29 restoring.................... 30 DiskSpace Failure................. 64 DiskSpace Failure exceptions........... 64 documentation on the web.................... 8 F Fault and Performance Manager Managed Node.. 63 M Microsoft web site................. 12 N network security.................... 13 Network Management System........... 61 June 2010 69

Index O order of G650 carriers............... 66 P passwords changing.................... 13 ping failure exceptions............... 65 primary Fault and Performance Manager server... 22 R RADIUS authentication............... 58 Red Hat web site................. 12 requirements................... 19 resources Avaya Global Technical Services........ 10 Customized Management Solutions for Avaya Integrated Management11 restore database.................. 30 S secondary Fault and Performance Manager server.. 24 security Avaya disclaimer................ 14 for networks.................. 13 network.................... 13 notices..................... 13 toll fraud.................... 14 toll fraud intervention.............. 14 system commands................. 28 system health................... 29 system requirements................ 19 T toll fraud...................... 14 Avaya disclaimer................ 14 intervention................... 14 typographical conventions.............. 7 W web sites third-party................... 12 70