FPMConfig 5.2

Avaya Integrated Management Release 5.2Fault and Performance ManagerConfiguration

Issue 11May 2009

© 2009 Avaya Inc.All Rights Reserved.

NoticeWhile 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 disclaimerAvaya 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 disclaimerAvaya 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.

WarrantyAvaya 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 supportAvaya 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

http://www.avaya.com/support

http://www.avaya.com/support/


May 2009 3

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . . . 7Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Product documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8How to access documents on the Web. . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 1: Resources and Notices . . . . . . . . . . . . . . . . . . . . . 9Avaya Technology and Consulting . . . . . . . . . . . . . . . . . . . . . . . . . 9Avaya Professional Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Avaya Global Services Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Avaya Global Technical Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Customized management solutions for Avaya Integrated Management. . . . . . 11Avaya contact information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Third-party resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12System security notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Network security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Toll fraud security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Avaya disclaimer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Toll fraud intervention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Product description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15What is new in this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Supported systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

LDAP support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Hardware certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 3: Configuring Fault and Performance Manager. . . . . . . . . 23Configuring a primary Fault and Performance Manager server . . . . . . . . . . 24Configuring a secondary Fault and Performance Manager server . . . . . . . . . 26

Contents

Contents

4 Avaya Fault and Performance Manager Configuration

Installing FPM in a customer specified directory . . . . . . . . . . . . . . . . . . 27Switching to the old Java plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 4: Customizing Fault and Performance Manager . . . . . . . . 29Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Setting up Communication Manager Sub Agent . . . . . . . . . . . . . . . . . . 29System commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Start and Stop commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30System status commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Backing up the FPM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Restoring the FPM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Easy backup and restoration of FPM configuration data . . . . . . . . . . . . 32

Chapter 5: Configuring SNMP traps . . . . . . . . . . . . . . . . . . . . 35Recommended software requirements. . . . . . . . . . . . . . . . . . . . . . . . 35Configuration procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Procedure 1: Launching the Maintenance Web Interface . . . . . . . . . . . . . . 36Procedure 2: Stopping the Master Agent . . . . . . . . . . . . . . . . . . . . . . 37Procedure 3: Configuring SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . 38Procedure 4: Starting the Master Agent . . . . . . . . . . . . . . . . . . . . . . . 40Procedure 5: Adding Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Testing the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 6: Getting started . . . . . . . . . . . . . . . . . . . . . . . . . 47Creating FPM logins and roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Procedure 1: Creating an FPM role . . . . . . . . . . . . . . . . . . . . . . . . . . 48Procedure 2: Adding a user and assigning an FPM role . . . . . . . . . . . . . . 49Procedure 3: Adding an LDAP group and assigning an FPM role . . . . . . . . . 50Starting the Fault and Performance Manager client . . . . . . . . . . . . . . . . . 51Configuring alarm filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring FPM in the event of an sshIOException . . . . . . . . . . . . . . 53DEFINITY_ARS script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54AUDIX_ARS script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55CMS_ARS script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56CONVERSANT_ARS script . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Starting the online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Exiting the Fault and Performance Manager client . . . . . . . . . . . . . . . . . 58Changing your FPM password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Contents

May 2009 5

RADIUS support for FPM user authentication . . . . . . . . . . . . . . . . . . . . 58RADIUS authentication with LDAP authorization . . . . . . . . . . . . . . 59RADIUS authentication with IMD authorization . . . . . . . . . . . . . . . 59Radius accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Methods used for FPM authentication and authorization . . . . . . . . . . 60

Integrating Fault and Performance Manager with an NMS . . . . . . . . . . . . . 60Configuring Select NMS to send Traps . . . . . . . . . . . . . . . . . . . . . 61

Viewing a managed element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Configuring DiskSpace Failure exceptions . . . . . . . . . . . . . . . . . . . . . 63Configuring Ping Failure exceptions . . . . . . . . . . . . . . . . . . . . . . . . . 64Configuring the order of carriers in G650 cabinets . . . . . . . . . . . . . . . . . 65

Glossary and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . 67

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Contents


May 2009 7

Preface

PurposeThis document explains how to configure Avaya Fault and Performance Manager (Fault and Performance Manager).

PrerequisitesConfiguring 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 audienceWe wrote this document for workstation or network administrators.

Conventions used in this documentIn this document, we use the following typographical conventions:

l We use bold type for emphasis and for any information that you should type, for example, save translation.

l We use Courier font for any information that the computer screen displays, for example, login.

l 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.

Preface


Additional resourcesYou 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 Administrator’s Guide for Avaya Communication Manager, which explains system features and interactions in detail. You can access this document from the Integrated Management home page.

Product documentationThe 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 WebTo 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.

http://www.adobe.com


May 2009 9

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 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:

l Platform readiness verification

l AIM architectural planning, design, and overview

l Remote turnkey implementation and installation

l AIM server configuration

l Customer acceptance verification

l Custom onsite services

l Onsite and remote knowledge transfer

The APS Data Group consists of the following teams:

l Avaya Integrated Management ConsultantsThe Avaya Integrated Management (AIM) consulting team offers planning, design, implementation, consulting, and knowledge transfer services for the entire Avaya Integrated Management suite. This includes ASA, Val Manager, VMM, NMC with SUM, MSA, and FPM. The thrust of the APS team is to bring the correct methodology to these complex application deployments that span various regions, and to provide continuity to the overall project. Through

Resources and Notices


proper integration and consulting, our customers can leverage the AIM suite to lower the total cost of ownership, and proactively manage their VoIP network comfortably and confidently.

l Data Network Implementation EngineeringThe 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 [email protected].

Avaya Global Services DeliveryAvaya 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:

l Customers do not provide remote access.

l Customers do not have a current maintenance agreement.

l Customers do not procure and install the required systems and software as defined in the Integrated Management Services Support Plan.

l Customers request support that is outside the purchase agreement.

GSD does not support hardware or software that customers purchase from third party vendors.

Avaya Global Technical ServicesAvaya 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.

Customized management solutions for Avaya Integrated Management

May 2009 11

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:

l Project Management — An Integrated Management project person will work with the customer to access configuration and customization requirements for any or all applications within each Avaya Integrated Management offer. If custom work is required, the evaluation will include a proposed statement of work and price. Note that this offer is not intended to provide installation for customers that choose to implement Integrated Management applications using Avaya Services or third party implementation services.

l 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.



Avaya contact informationTable 1 provides contact information that you may use if you need assistance in installing and setting up Avaya Integrated Management.

Third-party resourcesTable 2 lists contact information for third party vendors.

Table 1: Customer-Accessible Resources

Resource Contact Information

Avaya Support Center http://www.avaya.com/support

Avaya Global Technical Services

+1 800 242-2121 x15921

Avaya Professional Services (APS)

+1 800 730-9108, prompt 3

Integrated Management Product Team

Send email to: [email protected]

Toll Fraud Intervention +1 800 643-2353, prompt 1

Table 2: Vendor web sites

Vendor Web Sites

Microsoft Main site: http://www.microsoft.com

Red Hat Linux Main site: http://www.redhat.com


http://www.microsoft.com

http://www.redhat.com

System security notices

May 2009 13

System security noticesCustomers 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 securityFault 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.



Toll fraud securityAlthough 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.

May 2009 15

Chapter 2: Overview

Avaya Fault and Performance Manager (FPM) 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 descriptionFPM provides graphical and tabular tools to monitor the status and performance of a network of supported systems and external devices. FPM 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:

l 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.

l Configuration : You can view the configuration and administered properties of the supported systems and managed nodes, in both graphic and table views.

Overview


l 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.

l 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.

l 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.

What is new in this release

May 2009 17

What is new in this releaseFault and Performance Manager release 5.2 introduces the following enhancements:

l Support for the RADIUS authentication of users

FPM provides support for the authentication of users against the external FreeRADIUS server.

l Support for S8400 as an Enterprise Survivable Server (ESS)

l Support for the S8300D internal call controller media server

l Support for the G430 media gateway with the Media Module MM118

l Support for FPM as a managed element

l Provision of ping service and device status notification

FPM provides basic ping polling of the managed elements that enables customers to be notified when a device is unreachable.

l Provision of easy backup and restoration of FPM configuration data

Information regarding entities like filters, collection data configuration, and scheduled reports are stored in a backup file and configured on a server. This information can be restored on a new server if the FPM server stops responding, or if the server is upgraded.

l Provision of a reorder functionality for carriers in the G650 cabinets

A Reorder button helps users, who have the PositionCarriers capability assigned to them in the FPM role, to specify the order of carriers in the G650 cabinets.

l Provision of greater clarity in the IP Trunk map display

FPM provides two buttons, Show Managed and Show All, on the IPT trunk display to enable or disable the display of far-end systems that are not managed by the FPM server. As FPM does not manage all IPT far-end systems, the new functionality lends clarity to the IPT displays.

l Provision of the additional Assistant Maintenance Objects: H323-SGR, PKT-BUS, PKT-INT and SIP-SGRP

l Provision of four performance report types:

l Performance: IP VoiceStats Jitter

l Performance: IP VoiceStats Delay

l Performance: IP VoiceStats PktLoss

l Performance: IP VoiceStats Data

The FPM Report Manager lists the four reports in the GUI under the Performance category.

l FPM support for connections to either IP Addresses or Fully Qualified Domain Names (FQDN)

Overview


l Addition of two options, Store Only and None, to the Report Definition Level tab

l Addition of the Run Hourly option to schedule reports

l Support for the installation of FPM in a customer specified directory

Supported systems

May 2009 19

Supported systemsFault and Performance Manager Release 5.2 supports configuration, alarms, and performance data for the following systems:

l DEFINITY® ECS Releases 9.5 through 10.x

l Survivable Remote Processors (SRPs)

l Multipoint Conferencing Unit (MCU) Release 7.2

l Avaya G250, G350, G430, G450, G600, and G700 Media Gateways

l Communication Manager (Linux) Release 2.1, 3.0, 3.1, 4.0, and 5.0

l Communication Manager Releases up to 5.2

l 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 5.2 supports only alarm traps for the following systems:

l Avaya SIP Enablement Services (SES) Server Release 3.1 and Avaya Converged Communications Server (CCS) Release 1.0 and later

l Interactive Response (IR) Releases 1.0 through 1.3

l DEFINITY AUDIX® Releases 3.1 through 4.0

l INTUITY AUDIX® Release 5.1 (with or without the remote maintenance board)

l INTUITY™ AUDIX® on S8100 Media Server

l INTUITY™ AUDIX® LX Release 1.0 through 17.X

l Modular Messaging Release 1.0 and later

l Call Management System (CMS) R3V8.3 through R3V11

l S8100 Media Server INTUITY AUDIX

l INTUITY™ Interchange Release 5.1 through 5.4

l CONVERSANT® Release 7.0 through 9.0

l IA770 INTUITY AUDIX® Option for S8300 ICC Release 1.0 through 2.0

l Message Networking Release 1.0 through 3.0

l Secure Services Gateway (SSG)

l Avaya Expanded Meet-Me Conferencing (EMMC) server

Overview


LDAP supportThe Avaya supported directories for FPM 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 AS R4.0 or 5.0 certified or Red Hat Enterprise Linux ES 4.0 or 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 5.2.

Software

Fault and Performance Manager Release 5.2 operates on:

l Red Hat Enterprise Linux R5.0

l Red Hat Enterprise Linux AS R4.0

l Red Hat Enterprise Linux ES R4.0

Configuration overview

May 2009 21

Configuration overviewFPM 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 24.

- 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 26.

2. If you use SNMP traps, use the configuration procedure in Configuring SNMP traps on page 35.

3. If you want to integrate FPM with an NMS, see Integrating Fault and Performance Manager with an NMS on page 60 for the integration procedure.

Overview


May 2009 23

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 FPM server, see the procedure Configuring a primary Fault and Performance Manager server on page 24.

If you want to configure a secondary FPM server, see the procedure Configuring a secondary Fault and Performance Manager server on page 26.

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 FPM 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 5.2 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 FPM 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.

Configuring a primary Fault and Performance Manager server

May 2009 25

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 FPM is configured, the system displays the following message:

Avaya Fault and Performance Manager software configuration was successful.



Configuring a secondary Fault and Performance Manager server

After you install Fault and Performance Manager, to configure a secondary FPM 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 5.2 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 FPM 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 FPM 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- [ ]?

Installing FPM in a customer specified directory

May 2009 27

7. Enter the FQDN for the secondary FPM server, and press Enter.Once FPM is configured, the system displays the following message:

Avaya Fault and Performance Manager software configuration was successful.

Installing FPM in a customer specified directoryIM release 5.2 supports the installation of FPM in a customer specified directory. The default directory continues to be /opt, but the System Management installer makes provision for users to specify an alternate directory to install FPM on the Linux server.

Note:Note: The equivalent for /opt in Release 5.2 is <install location>.

Switching to the old Java plug-inIM ensures that fresh or upgrade installations of SM 5.2.13 on RHEL 5, 32 or 64 bits, display the JRE version as 1.6.0_11. JDK 1.6.0_05 has been replaced with JRE 1.6.0_11.

SM 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.

May 2009 29

Chapter 4: Customizing Fault and Performance Manager

IntroductionOnly 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:

l Set up the Avaya Sub Agent on your Communication Manager server.

l Execute system commands to start and stop Fault and Performance Manager and to view the system health status.

l Execute database commands.

l Edit system configuration files to customize Fault and Performance Manager.

l Integrate third party products for alarm notification.

Setting up Communication Manager Sub AgentFor instructions to set up the Avaya Sub Agent on your Communication Manager server, see the Administrator Guide for Avaya Communication Manager, 03-300509.

Customizing Fault and Performance Manager


System commands

Start and Stop commandsFault 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.

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.

Table 3: Start and Stop commands

Command Description

service mfpm-server stop Stops the Fault and Performance Manager system and prevents it from starting at system boot.

service mfpm-server start Starts a stopped Fault and Performance Manager system and enables it to start at system boot.

service mfpm-server restart Stops and immediately restarts the Fault and Performance Manager system.

Backing up the FPM database

May 2009 31

System status commandsTable 4 provides system status commands.

Backing up the FPM databaseOnly the root user can perform the procedure to back up the FPM database.

Please refer to the Linux backup procedure in Avaya Integrated Management Release 5.2 System Management Installation and Upgrade.

Table 4: System status commands

Command Description

service mfpm-server statusFrom a web browser:http://fpmserver/cgi-bin/mfpm/Status.sh

Displays Fault and Performance Manager system process status

/opt/avaya/mfpm/bin/mfpm gui Opens a graphical monitor of process status

mfpmconfig showFrom a web browser:http://fpmserver/cgi-bin/mfpm/Config.sh

Displays the configuration of the Fault and Performance Manager server

CollStatus statusFrom a web browser:http://fpmserver/cgi-bin/mfpm/CollStatus.sh?cmd=status

Displays the current collection queues of the Fault and Performance Manager server

CollStatus scheduleFrom a web browser:http://fpmserver/cgi-bin/mfpm/CollStatus.sh?cmd=schedule

Displays the current scheduled collection items on the Fault and Performance Manager server



Restoring the FPM databaseOnly the root user can perform the procedure to restore the FPM database.

Please refer to the Linux restore procedure in Avaya Integrated Management Release 5.2 System Management Installation and Upgrade.

Easy backup and restoration of FPM configuration dataFPM provides the ability to restore user administrable data from a backup copy in the FPM 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:

l Configuration Collection Schedule - default and per switch

l Alarm Filter and Collection schedule - default and per switch

l Performance Threshold and Alerting configuration - default and per switch

l 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 FPM 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. FPM provides the user the ability to back up all user administrable application data within FPM.

The types of data that FPM can back up and restore are:

l 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

- IP Trunk Groups

- Voice System Parameters

- Voice Adjunct Parameters

Restoring the FPM database

May 2009 33

l Report Manager

- Report Definitions

- Scheduled Reports

- Trunk Group Lists

FPM 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.

BackUpMFPMConfigDataThe 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.

RestoreMFPMConfigDataThe 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 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 FPM server.

May 2009 35

Chapter 5: Configuring SNMP traps

Avaya 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 requirementsWe recommend that users fulfil the following software requirements for complete FPM support and functionality:

l Avaya Integrated Management Release 5.2

l Avaya Communication Manager Release 5.2

Configuration proceduresTo configure traps for FPM, you must perform the following procedures:

1. Launch the Maintenance web interface. See Procedure 1: Launching the Maintenance Web Interface on page 36 for more information.

2. Stop the Master Agent in Avaya Communication Manager. See Procedure 2: Stopping the Master Agent on page 37 for more information.

3. Configure the SNMP Agent to use Avaya Fault and Performance Manager filtering. See Procedure 3: Configuring SNMP Agent on page 38 for more information.

4. Start the Master Agent. See Procedure 4: Starting the Master Agent on page 40 for more information.

5. Add nodes that you want to manage. See Procedure 5: Adding Nodes on page 41 for more information.

Configuring SNMP traps


Procedure 1: Launching the Maintenance Web InterfaceTo launch the Maintenance web interface:

1. Log into the server that runs Avaya Communication Manager Release 5.2.

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.

Procedure 2: Stopping the Master Agent

May 2009 37

Procedure 2: Stopping the Master AgentTo stop the Master Agent:

1. Click Agent Status under Alarms on the navigation pane.

The system displays the Agent Status page.

Figure 2: Agent Status2. Click Stop Agent .



Procedure 3: Configuring SNMP AgentTo configure the SNMP Agent that helps you use FPM filtering:

1. Click SNMP Agents under Alarms on the navigation pane.

The system displays the SNMP Agents page.

Figure 3: SNMP Agents2. 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.

Procedure 3: Configuring SNMP Agent

May 2009 39

4. Scroll down and select the Enable SNMP Version 1 check box.

Figure 4: Fields on SNMP Agents5. 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 IMD 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 IMD 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 IMD SNMP Configuration page.



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 IMD SNMP Configuration page.

10. Scroll down and click Submit.

Procedure 4: Starting the Master AgentTo start the Master Agent:

1. Click Agent Status under Alarms on the navigation pane.

The system displays the Agent Status page.

Figure 5: Agent Status2. Click Start Agent.

Procedure 5: Adding Nodes

May 2009 41

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 41 for more information.

Procedure 5: Adding NodesTo 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 5.2 Configuration or the Integrated Management Database online help for information on how to add nodes.

Testing the SNMP AgentUse this procedure to determine whether you have properly configured Avaya Communication Manager Release 5.2 or a later version, and Avaya Fault and Performance Manager, for alarm filtering. Before you begin the procedure, make sure that you have:

l Configured the SNMP Agent in Avaya Communication Manager.

l Configured alarm filtering in Avaya Fault and Performance Manager. See Configuring alarm filters on page 53 for the configuration procedure.



To test the SNMP agent:

1. Log in to the server that runs Avaya Communication Manager Release 5.2.

The system displays the Integrated Management Standard Management Solutions page.

Figure 6: Integrated Management Standard Management Solutions

Testing the SNMP Agent

May 2009 43

2. Click Launch Maintenance Web Interface.

The system displays the Maintenance Web Interface page.

Figure 7: Maintenance



3. Click SNMP Test under Alarms on the navigation pane.

The system displays the SNMP Test page.

Figure 8: SNMP Test

Testing the SNMP Agent

May 2009 45

4. Click Generate Test Trap.

The system displays the SNMP Test Results page.

Figure 9: SNMP Test ResultsThe system should display the trap that is received in Avaya Fault and Performance Manager.



Figure 10 displays a sample trap in Avaya Fault and Performance Manager.

Figure 10: Sample trap in FPM

May 2009 47

Chapter 6: Getting started

This chapter describes how to:

l Create logins and assign roles to FPM users.

l Start the Fault and Performance Manager client from a web browser.

l Configure alarm filters in FPM.

l Access the FPM online help.

l Quit the Fault and Performance Manager client from a web browser.

l Change your FPM password.

l Integrate FPM with an NMS.

Creating FPM logins and rolesYou must log in to FPM to use the FPM user interface. Use Integrated Management Database (IMD) to:

l Create FPM roles

l Add FPM users

l Assign FPM roles to FPM users

You can assign one or more of the following capabilities to an FPM role:

l 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 FPM user interface.

l BusyoutReleaseThis capability enables the user to busyout and release boards, trunks, trunk groups, stations and ports from the FPM user interface.

l AcknowledgeThis capability enables the user to acknowledge alerts within the FPM user interface.

l ReadOnlyThis capability enables the user to run the FPM user interface with a read-only permission. The user cannot configure voice systems or schedule reports.

Getting started


l CreateReportsThis capability enables the user to:

- Create new reports that will be stored on the FPM server for future use

- Schedule the reports to be run automatically in the background by the FPM server

l MovePNThis capability enables the user to move the port networks in an ESS cluster.

l HelperThis capability enables the user to access the Helpdesk feature from the FPM user interface.

l AssistThis capability enables the user to automatically run the Avaya Communication Manager commands that are recommended by the Helpdesk feature when an alarm is received.

l PositionCarriersThis capability enables the user to assign permissions to change the order of carriers in the G650 cabinets.

IMD automatically installs and configures the following default FPM roles:

l FPMbrowseThe FPMbrowse role has the ReadOnly capability.

l FPMadminThe FPMadmin role has the CreateReports, Admin, BusyoutRelease, Acknowledge, MovePN, Helper and Assist capabilities.

You can either assign these default roles to FPM users or you can create and assign custom roles.

To create FPM roles and logins:

1. Create FPM roles.

2. Add FPM users, and assign FPM roles to those users.

Procedure 1: Creating an FPM roleTo create an FPM role:

1. Log in to Integrated Management Database (IMD), and click FPM Roles on the navigation pane of the Integrated Management Database Administrator page.

The system displays the FPM Roles page.

Procedure 2: Adding a user and assigning an FPM role

May 2009 49

2. Click Add.

The system displays the Add FPM Role page.

3. In the Enter Role Name field, enter the name for the FPM 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 FPM role you want to create.

When finished, add a user. For more information, see Procedure 2: Adding a user and assigning an FPM role on page 49.

Procedure 2: Adding a user and assigning an FPM roleUse this procedure to:

l Add a user account that can access FPM

l Assign an FPM role to this user

To add a group of LDAP users, see Procedure 3: Adding an LDAP group and assigning an FPM role on page 50.

To add a user and assign the user an FPM 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.

Getting started


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 FPM 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 FPM user you want to add.

When you want to quit IMD, click Exit on the navigation pane.

Procedure 3: Adding an LDAP group and assigning an FPM role

Use this procedure to:

l Add an LDAP group that can access FPM

l Assign an FPM role to the group

Note:Note: The settings you specify for an LDAP group applies to all the members of the

group.

Starting the Fault and Performance Manager client

May 2009 51

To add an LDAP group and assign an FPM 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 FPM 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.

When you want to quit IMD, click Exit on the navigation pane.

Starting the Fault and Performance Manager clientTo 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 or a later version, or the Firefox Web browser.

The system displays the Integrated Management Launch Products page.

Getting started


2. Click the System Management tab on the Integrated Management web page.

3. Click Avaya 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 FPM logins and passwords are administered through Integrated Management

Database (IMD).

6. In the Password box, enter your password.

7. Click Login.

The system displays the Fault and Performance Manager window.

Configuring alarm filters

May 2009 53

Configuring alarm filtersTo 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 Avaya Communication Manager.

If an error occurs when Avaya Fault and Performance Manager attempts to send the alarm filter to Avaya Communication Manager, the system displays an error message. Most errors that occur at this point are related to the SNMPv2c settings in IMD and Avaya Fault and Performance Manager not matching the SNMPv2c settings in Avaya Communication Manager. For more information, see Procedure 3: Configuring SNMP Agent on page 38.

Configuring FPM in the event of an sshIOExceptionTo configure FPM in the event of an sshIOException:

1. Log in as root on the FPM server.

2. Execute the following commands:

cd /opt/avaya/mfpm/data

vi PMProp

3. At the end of the file, enter:

MFPM.socketReadTimeout=300000

Getting started


4. Execute the following command:

mfpmconfig

DEFINITY_ARS scriptFPM looks for the DEFINITY_ARS script when one of the following events occurs:

l FPM receives an alarm trap from the following managed nodes:

- Communication Manager Feature Servers

- MCU

l FPM receives an exception event from Fault and Performance Manager for these managed nodes

FPM 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, FPM 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

18. Restart carrier

19. Restart craft demand

Configuring alarm filters

May 2009 55

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 scriptFPM looks for the AUDIX_ARS script if it receives an alarm trap or an exception event mentioned in the following list.

l FPM receives an alarm trap from the following managed nodes:

- DEFINITY AUDIX

- Intuity AUDIX

- Intuity Interchange

l FPM receives an exception event from Fault and Performance Manager for these managed nodes



1. System name

2. Product ID

3. Alarm sequence number

4. Source of the alarm:

- DEFINITY (for DEFINITY AUDIX)

- Intuity Interchange




8. Alarm location

9. Alarm date

Getting started


10. Alarm time

11. Resource

12. Fault code

13. Module ID

14. Event number

15. Count number

CMS_ARS scriptFPM looks for the CMS_ARS script when one of the following events occurs:

l FPM receives an alarm trap from the Call Management System (CMS)

l FPM receives an exception event from Fault and Performance Manager for the CMS



1. System name

2. Product ID

3. Alarm sequence




7. Product type

8. Version

9. ID value

10. Number

11. Name

Starting the online Help

May 2009 57

CONVERSANT_ARS scriptFPM looks for the CONVERSANT_ARS script when one of the following events occurs:

l FPM receives an alarm trap from the CONVERSANT system

l FPM receives an exception event from Fault and Performance Manager for the CONVERSANT system



1. System name

2. Product ID

3. alarm number




7. Location

8. Date

9. Time

10. Resource

11. Fault code

12. Module ID

13. Event number

14. Count number

Starting the online HelpThe online help system describes how to use Fault and Performance Manager. To start the online help, log in to FPM 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.

Getting started


Exiting the Fault and Performance Manager clientTo quit the Fault and Performance Manager client, click File > Exit.

Changing your FPM passwordTo 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 or a later version, or the Firefox web browser.

The system displays the Avaya Integrated Management Launch Products page.

2. On the System Management tab, 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 FPM user authenticationFPM users have to be authenticated and granted user permissions. A new feature of FPM 5.2 is the RADIUS authentication of FPM users. RADIUS supports FPM user authentication alone. Authorization or permissions for users is provided either through LDAP or locally from IMD. MSA and IMD must also support RADIUS if FPM is to provide support for user authentication.

FPM support for RADIUS authentication requires the configuration of RADIUS in IMD and applies to both MSA and FPM. For more information, see Avaya Integrated Management Release 5.2 Integrated Management Database Configuration.

RADIUS support for FPM user authentication

May 2009 59

Two scenarios are possible for RADIUS authentication:

l RADIUS authentication with LDAP authorization that uses the Group ID

l RADIUS authentication with IMD authorization

RADIUS authentication with LDAP authorization

The authentication proceeds in the following sequence:

1. RADIUS authenticates the login and password of the user.

2. FPM 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 IMD authorization

The authentication proceeds in the following sequence:

1. RADIUS authenticates the login and password of the user.

2. FPM matches the FPM role to the login ID of the user in IMD.

This authorization process works the same way as authorization does when IMD or FPM provides the local authentication and authorization.

Radius accounts

FPM support for RADIUS authentication extends to the following requirements:

l Local FPM roles as defined in IMD

l LDAP store from open LDAP

l Microsoft Active Directory store

FPM 5.2 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, FPM 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 FPM authenticates with the RADIUS server through the use of a shared secret. FPM 5.2 interacts with the external RADIUS server through a LAN.

Note:Note: FPM logs all user access attempts that are authenticated externally through

RADIUS. FPM logs successful and failed attempts.

Getting started


Methods used for FPM authentication and authorization

FPM authenticates and authorizes a user through the defined method within IMD. 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 FPM attempts to authenticate the user locally through IMD.

IMD authenticates and authorizes FPM users in two ways:

l 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 FPM.

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 IMD. IMD holds the FPM 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.

l Using matches for local IMD permissions

The procedure that is used to authenticate and authorize FPM users with matches for local IMD permissions is as follows:

1. A user accesses FPM.

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 IMD 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 IMD database. Access to FPM is also denied if no match is found in the IMD database.

In all cases of failure, the last search will be conducted in the local IMD database. If no matching user name is found in IMD, the user will be denied access to FPM.

Integrating Fault and Performance Manager with an NMSFault 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 an NMS. For more information, see “Add an NMS Configuration” in Avaya Integrated Management Release 5.2 Integrated Management Database Configuration.

Integrating Fault and Performance Manager with an NMS

May 2009 61

Configuring Select NMS to send TrapsUse the following procedure to configure the Select NMS to send Traps feature in the FPM 5.2 Build 8 UI.

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:

l Trunk Exceptions

- Lightly Used Trunk Exceptions

- Trunk Outages Exceptions

- Holding Times Exceptions

l Processor Occupancy Exceptions

l Trunk Group Exceptions

l Adjuncts Alarms/Errors

- Major Alarm Exceptions

- Minor Alarm Exceptions

- Warning Exceptions

- Inads Exceptions

l 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 FPM 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:

l Store Exception?

l Alert?

l Email notification

l ARS Script

Getting started


l Select NMS to send Traps

After you install FPM 5.2 Build 8 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.

FPM 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 FPM.

Viewing a managed elementSupport for FPM as a managed element enables FPM to log exceptions and handle alerts like the /var partition running out of disk space, postgresql shutting down, collections stopping, or the FPM 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 FPM stops responding and stops processing traps or collections.

If an adjunct is a managed node, its description reads FPM Managed Node. The prefix FPM is added to the name of an FPM 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

Configuring DiskSpace Failure exceptions

May 2009 63

6. Click Exceptions.

The system displays the Adjuncts Exception Report. It tabulates information under the following heads:

l Severity

l Type

l Voice System

l NMS Start

l NMS End

l Description: describes the nature of the exception, for example, DiskSpace Failure: FPM Server disk usage is 21%.

7. Click Acknowledge.

The system displays the Request box with the message Exceptions Acknowledged successfully.

8. Click OK.

Configuring DiskSpace Failure exceptionsIM 5.2 addresses the acute need to support the FPM 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 FPM stops responding and stops processing traps or collections.

FPM logs these exceptions and handles alerts for these eventualities. FPM itself facilitates sending traps to NMSs and sending e-mails to administrators for exceptions alerted against the FPM 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.

Getting started


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:

l The default Level 1 Severity is Minor.

l The default Level 1 Percentage is 70.

l The default Level 2 Severity is Major.

l 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 FPM online help.

Configuring Ping Failure exceptionsFPM has implemented a ping service that periodically sends ICMP Ping packets to the different switches and adjuncts that the FPM server manages and gets ICMP responses. In the event the ICMP request fails, FPM 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 FPM, 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.

Configuring the order of carriers in G650 cabinets

May 2009 65

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.

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 FPM online help.

Configuring the order of carriers in G650 cabinetsWith 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.

Getting started


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.

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 FPM role.

May 2009 67

Glossary and Abbreviations

AAPS Avaya Professional ServicesATAC See Avaya Technology and Consulting on page 9.

CCommunication Manager

The call processing software that runs on Communication Manager Feature Servers. Formerly known as DEFINITY software.

Communication Manager Feature Server

Any of the products that run Communication Manager. Formerly known as DEFINITY system, DEFINITY ECS, switch, PBX, or voice system.

Mmanaged node In this document, a managed node is any system (voice system or otherwise)

that can be viewed and monitored using Fault and Performance Manager.

NNetwork Management Server

This is the Windows server on which you can install Integrated Management applications.

Network Management System

A system that lets you monitor the health and status of devices on your data network.

SSNMP Simple Network Management Protocol.System Management Server

This is the Linux server on which you install Fault and Performance Manager.

System Management Server


May 2009 69

Index

AAvaya Professional Services . . . . . . . . . . . . . 9Avaya Technology and Consulting (ATAC) . . . . . . 9

BBackup and Restore . . . . . . . . . . . . . . . . 32backup, database . . . . . . . . . . . . . . . . . 31books

on the web . . . . . . . . . . . . . . . . . . . . 8

Ccommands . . . . . . . . . . . . . . . . . . . . 30

system health . . . . . . . . . . . . . . . . . 31configuring a primary FPM server . . . . . . . . . . 24configuring a secondary FPM server . . . . . . . . 26contact information

third party . . . . . . . . . . . . . . . . . . . 12contact information for Avaya . . . . . . . . . . . . 12customer specified directory . . . . . . . . . . . . 27

Ddatabase

backup. . . . . . . . . . . . . . . . . . . . . 31restoring . . . . . . . . . . . . . . . . . . . . 32

DiskSpace Failure . . . . . . . . . . . . . . . . . 63DiskSpace Failure exceptions . . . . . . . . . . . 63documentation

on the web . . . . . . . . . . . . . . . . . . . . 8

FFPM Managed Node . . . . . . . . . . . . . . . . 62

MMicrosoft web site . . . . . . . . . . . . . . . . . 12

Nnetwork

security . . . . . . . . . . . . . . . . . . . . 13NMS . . . . . . . . . . . . . . . . . . . . . . . 60

Index

70

Oorder of G650 carriers . . . . . . . . . . . . . . . 65

Ppasswords

changing . . . . . . . . . . . . . . . . . . . . 13ping failure exceptions . . . . . . . . . . . . . . . 64primary FPM server . . . . . . . . . . . . . . . . 24

RRADIUS authentication. . . . . . . . . . . . . . . 58Red Hat web site . . . . . . . . . . . . . . . . . 12requirements . . . . . . . . . . . . . . . . . . . 20resources

Avaya Global Technical Services . . . . . . . . 10Customized Management Solutions for Avaya Integrated Management11

restore database. . . . . . . . . . . . . . . . . . 32

Ssecondary FPM server . . . . . . . . . . . . . . . 26security

Avaya disclaimer . . . . . . . . . . . . . . . . 14for networks . . . . . . . . . . . . . . . . . . 13network . . . . . . . . . . . . . . . . . . . . 13notices . . . . . . . . . . . . . . . . . . . . . 13toll fraud . . . . . . . . . . . . . . . . . . . . 14toll fraud intervention . . . . . . . . . . . . . . 14

system commands . . . . . . . . . . . . . . . . . 30system health . . . . . . . . . . . . . . . . . . . 31system requirements . . . . . . . . . . . . . . . . 20

Ttoll fraud. . . . . . . . . . . . . . . . . . . . . . 14

Avaya disclaimer . . . . . . . . . . . . . . . . 14intervention. . . . . . . . . . . . . . . . . . . 14

typographical conventions . . . . . . . . . . . . . . 7

Wweb sites

third-party . . . . . . . . . . . . . . . . . . . 12

FPMConfig 5.2

Documents

Transcript of FPMConfig 5.2