EMC Smarts VoIP Management Suite · EMC Smarts VoIP Management Suite Version 3.0 Overview and Integration Guide 7 Preface EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC® Smarts®

VoIP Management SuiteVersion 3.0

Overview and Integration GuideP/N 300-006-921

REV A02

EMC Smarts VoIP Management Suite Version 3.0 Overview and Integration Guide2

Copyright © 2008 EMC Corporation. All rights reserved.

Published July, 2008

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC Smarts VoIP Management Suite Version 3.0 Overview and Integration Guide 3

Preface

Chapter 1 Introduction EMC Smarts VoIP Management Suite overview................................................ 12

Functionality ..................................................................................................... 12Products ............................................................................................................. 12Deployment ....................................................................................................... 12Platform support............................................................................................... 12User preference ................................................................................................. 13User documentation......................................................................................... 13

Additional products in a VoIP Management Suite deployment...................... 13 VoIP Management Suite deployment architecture ............................................ 14

VoIP Availability Manager ............................................................................. 15VoIP Performance Manager............................................................................ 15VoIP Performance Reporter ............................................................................ 16IP Availability Manager................................................................................... 17Global Manager ................................................................................................ 17Adapter Platform.............................................................................................. 17Global Console .................................................................................................. 17EMC Smarts Broker.......................................................................................... 18

Chapter 2 Integration Integration overview.............................................................................................. 20 VoIP Performance Manager traps and trap processing..................................... 21 VoIP client tools....................................................................................................... 22

VoIP Performance Manager’s Java-based GUI and displays..................... 23Global Console client tools.............................................................................. 23Client tools created to access VoIP Performance Manager data................ 24URL construction.............................................................................................. 27VoIP client tool invocation .............................................................................. 28Web browser operation and limitations........................................................ 29

Configuration procedures ..................................................................................... 29

Chapter 3 Configuring SNMP Trap Integration Configuration overview......................................................................................... 32 Copying, configuring, and starting PMT-THRESHOLD .................................. 32 Enabling the VoIP Availability Manager built-in trap receiver........................ 33

Contents


Contents

Controlling the processing of VoIP Performance Manager traps..................... 33 Customizing performance polling and thresholds ............................................ 34 Troubleshooting....................................................................................................... 34


Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

Audience This document is intended for IT managers seeking to better understand the value of the EMC Smarts VoIP Management Suite 3.0 products, for administrators configuring and using the VoIP Management Suite products, and for operators receiving and acting upon notifications analyzed by the VoIP Management Suite products. It provides an overview of the VoIP Management Suite products and discusses the integration of these products with each other and with the EMC Smarts IP Availability Manager and the EMC Smarts Service Assurance Management Suite.

EMC Smarts VoIPManagement Suite

installation directory

In this document, the term BASEDIR represents the location where EMC Smarts software is installed:

◆ For UNIX, this location is: /opt/InCharge<n>/<productsuite>.

◆ For Windows, this location is: C:\InCharge<n>\<productsuite>.

The <n> represents the EMC Smarts software platform version number. The <productsuite> represents the EMC Smarts product suite to which the product belongs. For example, on UNIX operating systems, EMC Smarts VoIP Management Suite is, by default, installed to: /opt/InCharge7/VoIP/smarts. On Windows operating systems, this product is, by default, installed to: C:\InCharge7\VoIP\smarts. This location is referred to as BASEDIR/smarts.

Optionally, you can specify the root of BASEDIR to be something different, but you cannot change the <productsuite> location under the root directory.

The EMC Smarts System Administration Guide provides detailed information about the directory structure for EMC Smarts software.

EMC Smarts VoIPManagement Suite

products

The EMC Smarts VoIP Management Suite includes the following:

◆ EMC Smarts VoIP Availability Manager

◆ EMC Smarts VoIP Integration Pack for VoIP Performance Manager

◆ EMC Smarts Enablement Pack for Avaya

◆ EMC Smarts Enablement Pack for Cisco


Preface

◆ EMC Smarts Enablement Pack for Nortel

◆ EMC Smarts VoIP Performance Manager for Cisco v4

◆ EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya

◆ EMC Smarts VoIP Performance Reporter

Relateddocumentation

In addition to this document, EMC Corporation provides a Help system for command line programs as well as product documentation.

Help for command line programsDescriptions of command line programs are available as HTML pages. The index.html file, which provides an index to the various commands, is located in the BASEDIR/smarts/doc/html/usage directory.

EMC Smarts documentationReaders of this guide may find the following related documentation helpful. It can be found in the BASEDIR/smarts/doc/pdf directory:

Note: These documents are updated periodically. Electronic versions of the updated manuals are available on the Powerlink website:http://Powerlink.EMC.com

◆ EMC Smarts Documentation Catalog

◆ EMC Smarts System Administration Guide

◆ EMC Smarts ICIM Reference

◆ EMC Smarts Common Information Model Infrastructure Models Chart

◆ EMC Smarts Common Information Model Application⁄Business Models Chart

◆ EMC Smarts ASL Reference Guide

◆ EMC Smarts Perl Reference Guide

◆ EMC Smarts MODEL Reference Guide

EMC Smarts VoIP Management Suite documentationThe following documents are relevant to users of the EMC Smarts VoIP Management Suite:

◆ EMC Smarts VoIP Management Suite Release Notes

◆ EMC Smarts VoIP Availability Manager Installation Guide

◆ EMC Smarts VoIP Availability Manager Configuration Guide

◆ EMC Smarts VoIP Availability Manager Discovery Guide

◆ EMC Smarts VoIP Management Suite Overview and Integration Guide

◆ EMC Smarts VoIP Availability Manager User Guide

◆ EMC Smarts Enablement Pack for Avaya User Guide

◆ EMC Smarts Enablement Pack for Cisco User Guide

◆ EMC Smarts Enablement Pack for Nortel User Guide

◆ EMC Smarts VoIP Performance Manager for Cisco v4 Release Notes

◆ EMC Smarts VoIP Performance Manager for Cisco v4 Installation Guide

◆ EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Release Notes

◆ EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Installation Guide

http://Powerlink.EMC.com


Preface

◆ EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya System Guide

◆ EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya User Guide

◆ EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Records Guide—Short Record Names

◆ EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Records Guide—Long Record Names

◆ EMC Smarts VoIP Performance Reporter Release Notes

◆ EMC Smarts VoIP Performance Reporter Installation Guide

◆ EMC Smarts VoIP Performance Reporter User Guide

The EMC Smarts Documentation Catalog lists documentation resources provided with other EMC Smarts product suites.

Suggestions forsearching PDF files

You may search across multiple PDF files using the Adobe Acrobat Reader software:

1. If the documentation is not accessible to all users of the EMC Smarts product suite, copy the contents of the BASEDIR/smarts/doc/pdf directory to a central location, such as a shared drive on your LAN, that operators and others may view.

2. To search throughout the documentation library, open the Acrobat Reader software:

a. Select Edit > Search, and type a word or phrase.

b. Select All PDF Documents in, in the Where would you like to search option, and type the pathname of the location where the PDF documents reside.

If you have more than one EMC Smarts product suite installed, you can set up cross-product document searches by copying files from the BASEDIR/smarts/doc/pdf directory for each product suite into this common documentation directory path.

Conventions used inthis document

EMC uses the following conventions for special notices.

Note: A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment.

IMPORTANT!An important notice contains information essential to operation of the software.


Preface

Typographical conventionsEMC uses the following type style conventions in this document:

Pathname conventionsDirectory pathnames are shown with forward slashes (/). Users of the Windows operating systems should substitute back slashes (\) for forward slashes.

Graphical conventionsIf there are figures illustrating consoles in this document, they represent the consoles as they appear in Windows. Under UNIX, the consoles appear with slight differences. For example, in views that display items in a tree hierarchy such as the Topology Browser, a plus sign appears for Windows and an open circle appears for UNIX.

Smarts ManagerUnless otherwise specified, the term Smarts Manager is used to refer to EMC Smarts programs such as Domain Managers, Global Managers, and adapters.

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows, dialog boxes, buttons,

fields, and menus)• Names of resources, attributes, pools, Boolean expressions, buttons, DQL

statements, keywords, clauses, environment variables, functions, utilities• URLs, pathnames, filenames, directory names, computer names, filenames, links,

groups, service keys, file systems, notifications

Bold Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs, processes, services,

applications, utilities, kernels, notifications, system calls, man pages

Used in procedures for:• Names of interface elements (such as names of windows, dialog boxes, buttons,

fields, and menus)• What user specifically selects, clicks, presses, or types

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when shown outside of

running text

Courier bold Used for:• Specific user input (such as commands)

Courier italic Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example


Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information. For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:


Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:

[email protected]



Preface

Introduction 11

1

This chapter provides an architectural and functional overview of EMC Smarts VoIP Management Suite 3.0. It consists of the following sections:

◆ EMC Smarts VoIP Management Suite overview ...................................................... 12◆ Additional products in a VoIP Management Suite deployment ............................ 13◆ VoIP Management Suite deployment architecture................................................... 14

Introduction


Introduction

EMC Smarts VoIP Management Suite overviewThe EMC® Smarts® VoIP Management Suite provides enterprises with availability, fault management, and performance visibility across their Voice over IP (VoIP) infrastructures. It provides multivendor support and a comprehensive VoIP management solution.

FunctionalityThe VoIP Management Suite performs the following tasks:

◆ Discovers VoIP-enabled devices and VoIP applications

◆ Monitors the devices and applications and collects performance activity

◆ Correlates alerts and events

◆ Identifies failures and trends

◆ Analyzes and presents events and problems

ProductsThe VoIP Management Suite consists of the following products:

◆ EMC Smarts VoIP Availability Manager (VoIP Availability Manager)

◆ EMC Smarts VoIP Performance Manager for Cisco v4/ EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya (VoIP Performance Manager)

◆ EMC Smarts VoIP Performance Reporter (VoIP Performance Reporter)

VoIP Performance Reporter is an add-on module to VoIP Performance Manager.

DeploymentIn a medium to large deployment, VoIP Availability Manager, VoIP Performance Manager, and VoIP Performance Reporter are installed on separate hosts, to eliminate a single point of failure and to ensure that the applications are performing optimally.

VoIP Performance Manager must be running in order for VoIP Performance Reporter to run.

Platform supportVoIP Availability Manager is supported on Solaris, Windows, and Linux, whereas VoIP Performance Manager and VoIP Performance Reporter are supported on Windows only. The respective product installation guides specify the operating-system version and hardware requirements.

Additional products in a VoIP Management Suite deployment 13

Introduction

User preference

In general, NOC operators will use VoIP Availability Manager, and staff members will use VoIP Performance Manager and VoIP Performance Reporter. NOC operators are typically more interested in using VoIP Availability Manager to view the events and problems on screen, whereas staff members are typically more interested in using VoIP Performance Manager and VoIP Performance Reporter to manage the VoIP environment and to troubleshoot VoIP service-affecting issues.

User documentation

Each VoIP Management Suite product has its own user documentation set. Together, the user documentation sets provide the information that users will need to install, configure, administer, operate, and maintain the VoIP Management Suite products.

Additional products in a VoIP Management Suite deploymentBesides the installation of the VoIP Management Suite products, the following additional products are installed in a VoIP Management Suite 3.0 deployment:

◆ EMC Smarts IP Management Suite products

• EMC Smarts IP Availability Manager

• EMC Smarts IP Performance Manager (optional)

• EMC Smarts IP Server Performance Manager (optional)

◆ EMC Smarts Service Assurance Management Suite products

• EMC Smarts Global Manager

• EMC Smarts Global Console

• EMC Smarts Service Assurance Manager Adapter Platform

• EMC Smarts SNMP Trap Adapter configured as a trap exploder

• EMC Smarts SNMP Trap Adapter configured as a trap receiver

The EMC Smarts IP Management Suite Installation Guide and the EMC Smarts Service Assurance Management Suite Installation Guide provide information about installing these additional products.


Introduction

VoIP Management Suite deployment architectureFigure 1 on page 14 shows how the VoIP Management Suite products and the additional products interact in a VoIP Management Suite 3.0 deployment.

Figure 1 VoIP Management Suite deployment architecture

SNMP traps

VoIP analysis traps

Networktraps

Topology

Trap notifications

Network topology,root-cause problems,

& impacts

SNMP & CLI discovery& SNMP polling

VoIP topology,root-cause problems,

& impacts

Global Manager

VoIP topology &status updates

IPAvailability Manager

VoIP Availability Manager

Topology & notifications

VoIP & networkmaps

Global Console

Traps

Topology

VoIP devices

IP network

AdapterPlatform

Processed traps

SNMPTrap Adapter

(exploder)

VoIPNotification

Trap Adapter

VoIPinformational traps

SNMPTrap Adapter

(receiver)

Non-VoIPinformational traps

Processed traps

SNMP discovery& SNMP polling

VoIPPerformance

Manager

VoIPPerformance

Reporter

GUI GUI

VoIP performancemonitoring

Customer report portal

VoIP Management Suite deployment architecture 15

Introduction


VoIP Availability Manager discovers and monitors VoIP-enabled devices and VoIP applications. The VoIP-enabled devices can be a mixture of devices—such as call servers, media gateways, IP PBXs, routers, and IP phones—in one or more of the following vendor-specific environments:

◆ Avaya

◆ Cisco

◆ Nortel

The VoIP applications include VoIP network and telephony applications, as well as software services—such as phone registration, voice mail, music on hold, and call waiting.

Upon importing a list of VoIP-enabled devices from IP Availability Manager, VoIP Availability Manager performs its own discovery to query the managed devices for VoIP topology information. It monitors the VoIP topology, performs root-cause and impact analysis using vendor-specific hardware and software events, and exports the results of its analysis to the Global Manager.

VoIP Performance Manager

VoIP Performance Manager ensures that the entire Avaya or Cisco VoIP network is delivering an acceptable level of telephony services to the service subscribers. It verifies that all elements in the VoIP network are available and performing within acceptable limits.

VoIP Performance Manager accomplishes its mission by:

◆ Monitoring the CPU load, packet delays, VoIP Call Manager (soft switch) activity, and associated telephony service level indicators, such as call quality, activity, and duration across multiple servers and clusters.

◆ Managing the servers and associated network, hardware, and software components, including:

• Structured Query Language (SQL) servers

• Trivial File Transfer Protocol (TFTP) servers

• Gateways

• Devices

• Call Detail Records (CDRs)

• Call Maintenance Records (CMRs)

• Trace files

• Unity applications

VoIP Performance Manager captures and reports on call loads and utilization statistics for all devices in the VoIP environment. Administrators can use this data to identify trends in the usage of these devices, to identify over- and under-utilized devices, and to plan efficiently the increase of capacity.


Introduction

VoIP Performance Reporter

VoIP Performance Reporter is an add-on module to VoIP Performance Manager.

VoIP Performance Reporter is able to capture and record information from multiple devices and applications throughout the Avaya or Cisco VoIP network, to produce charts, graphs, and reports to help administrators visualize and understand important trends across the VoIP environment. This historical information is the lifeblood of capacity planning, trend analysis, and problem resolution.

Interactive charting for on-the-fly analysis, consolidated event and performance data reporting, and a comprehensive set of performance and service level reports help administrators measure, police, and manage the effectiveness of VoIP assets. Further, the accurate usage data provided in these reports make capacity planning, and thus the maximization of operational cost savings, a straightforward, low effort, low risk task.

Table 1 on page 16 shows the high-level report types created by VoIP Performance Reporter and the functional areas where each report type can be used.

Table 1 VoIP Performance Reporter reports and their use

Domain Report Service level Capacity planning Troubleshooting

Voice Voice Quality x x

Voice Quality Exception

x

Calls PBX Call Load x x

Call Failure x

Long Duration x

Location Calls x x x

Routing Route Pattern Availability

x x x

IP Trunk Availability x x x

IP Trunk Utilization x x

PSTN Trunk Availability

x x x

PSTN Trunk Utilization

x x

Hardware Phone Report x x

Node Utilization x x

VoIP Management Suite deployment architecture 17

Introduction

IP Availability Manager

IP Availability Manager discovers the underlying transport domain in the VoIP network, monitors availability, and analyzes the network connectivity to identify the root-cause problems and impacts of connectivity failures. It exports network topology, problem, and impact information to the Global Manager, and exports VoIP-enabled device topology and status information to VoIP Availability Manager.

VoIP-enabled device topology includes call servers, media gateways, hosts, routers, switches, and nodes. Device status information consists of status changes associated with the VoIP-enabled device topology imported by VoIP Availability Manager.

A VoIP Availability Manager deployment may contain one or more IP Availability Managers. An IP Availability Manager instance may consist of just an IP Availability Manager process, or may consist of an IP Availability Manager and an IP Performance Manager or IP Server Performance Manager running as a single process.

Global Manager

The Global Manager integrates the topology, problem, and impact information imported from IP Availability Manager and VoIP Availability Manager and relates the information to services and customers. It also provides cross-domain and end-to-end impact analysis.

The Global Manager displays the topology, problem, and impact information through the Global Console.

Adapter Platform

The Adapter Platform imports and normalizes topology from IP Availability Manager and VoIP Availability Manager, and imports and normalizes events of interest from EMC Smarts adapters such as the SNMP Trap Adapter and the VoIP Notification Trap Adapter. Normalize means to convert topology or event information into a common form understood by the Global Manager. The normalized event information is transferred as EMC Smarts notifications to the Global Manager.

Through the Adapter Platform, the Global Manager receives informational traps issued by the devices in the managed environment. Informational traps provide information that might be of interest to users.

Global ConsoleThe Global Console provides a graphical user interface for configuring and administering Global Managers, Adapter Platform Servers, Domain Managers, and externally running EMC Smarts adapters such as the SNMP Trap Adapter and the VoIP Notification Trap Adapter. In addition, when the Global Console is attached to the Global Manager, a user can browse the discovered topology in various forms, including maps, and to view notifications about problems that impact availability and performance.

In a VoIP Management Suite deployment, the Global Console is the GUI for VoIP Availability Manager but not for VoIP Performance Manager or VoIP Performance Reporter. (VoIP Performance Manager and VoIP Performance Reporter have their own GUIs.) The Global Console can be configured to open a web-browser Java-based GUI to view VoIP Performance Manager data.


Introduction

EMC Smarts Broker

The EMC Smarts Broker facilitates Global Console connections to the component applications in an EMC Smarts system deployment.

When a user starts a Global Console process, the process connects to the Broker, and the Global Console process displays a window through which the user views and selects any component application registered with the Broker. After the user selects an application, the Global Console connects to the application and disconnects from the Broker.

Integration 19

2

This chapter describes the integration of VoIP Performance Manager with VoIP Availability Manager in a VoIP Management Suite 3.0 deployment. It consists of the following sections:

◆ Integration overview .................................................................................................... 20◆ VoIP Performance Manager traps and trap processing ........................................... 21◆ VoIP client tools ............................................................................................................. 22◆ Configuration procedures ............................................................................................ 29

Integration


Integration

Integration overviewThe integration of VoIP Performance Manager with VoIP Availability Manager consists of two capabilities:

◆ The processing of VoIP Performance Manager traps by VoIP Availability Manager. The traps carry performance-oriented data and serve as points of integration between VoIP Performance Manager and VoIP Availability Manager.

◆ The launching of Global Console client tools for a selected VoIP Availability Manager topology object to open a web interface that loads a VoIP Performance Manager drill-down display relevant to the selected object. The drill-down display contain a collection of performance metrics associated with the object.

The first capability, available when the EMC Smarts VoIP Integration Pack for VoIP Performance Manager (VoIP Performance Manager Integration Pack) is installed, sends performance metrics in the form of VoIP Performance Manager traps to VoIP Availability Manager. The traps are used by VoIP Availability Manager to update new performance-related attributes in the following classes of the VoIP Availability Manager data model:

◆ CallManager (Cisco)

◆ ConvergedCallManager (Avaya)

◆ DS1Service (Avaya) (new class)

◆ GatewayService (Avaya, Cisco)

◆ H323GateKeeper (Avaya)

◆ H323Service (Cisco)

◆ MediaProcessor (Avaya)

◆ MediaResourceAggregate (Cisco) (new class)

◆ VoipCluster (Avaya, Cisco)

Note: In addition, VoIP Availability Manager uses a new class named VoipPerformanceManager to discover and monitor VoIP Performance Manager applications in the managed environment.

The VoIP Performance Manager traps are predefined by EMC and are generated periodically—every four minutes by default—by VoIP Performance Manager. Each predefined trap is given a name that identifies the category, or view, of the collected performance metrics contained in the trap.

Together, the enhanced data model and the periodic reception of VoIP Performance Manager traps—the monitoring of performance data—enable VoIP Availability Manager to generate performance-related events.

The second capability enables Global Console users to access VoIP Performance Manager drill-down displays associated with the VoIP Availability Manager topology objects stored in the Global Manager repository. This capability enables Global Console users to troubleshoot alarms involving specific VoIP Availability Manager topology objects.

VoIP Performance Manager traps and trap processing 21

Integration

VoIP Performance Manager traps and trap processingFigure 2 on page 21 shows how VoIP Performance Manager traps are processed by VoIP Availability Manager.

Figure 2 Processing of VoIP Performance Manager traps

Predefined VoIP Performance Manager traps are periodically sent by VoIP Performance Manager to the VoIP Availability Manager built-in trap receiver. The built-in trap receiver reads the enterprise OID (.1.3.6.1.4.1.6102) field of the received traps and forwards the traps to the PM Trap Processor.

For each received trap, the PM Trap Processor determines which PM trap handler to invoke based on the name of the trap. The selected PM trap handler parses the trap for performance metrics and applies their values to the appropriate attributes of the corresponding object in the VoIP Availability Manager modeled topology.

Note: With a few exceptions, a predefined trap contain metrics for just one object.

If the corresponding object cannot be found in the topology, the PM trap handler discards the trap. Media resource type traps are exceptions to this rule. For a received media resource type trap having no corresponding object in the topology, the PM trap handler creates a corresponding MediaResourceAggregate object in the topology.

Note: VoIP Availability Manager does not discover MediaResourceAggregate objects.

Traps


VoIP Performance

Manager

OID .1.3.6.1.4.1.6102

Built-intrap

receiver

PM Trap Processer

No

Find trapsource device* in

topology?

Discard trap

YesInvoke PM trap handler

Apply metric values to appropriate attributes of object

Locate corresponding object in topology

Parse trap for performance metrics

* Trap source device is VoIP Performance Manager.

VoIP Performance Manager Integration Pack


Integration

VoIP client toolsClient tools, as well as server tools, enable Global Console users to invoke programs in response to a particular target object, such as a notification object, a topology object, or a map object. Right-clicking a target object launches a pop-up menu that lists the available tools for the target object.

Client tools created to access VoIP Performance Manager data, referred to as VoIP client tools in this document, will be available only to certain topology objects imported by the Global Manager from VoIP Availability Manager. They will enable Global Console users to access drill-down displays available through the Java-based GUI of the VoIP Performance Manager’s web server, such as the Apache Tomcat server shown in Figure 3 on page 22.

Figure 3 VoIP client tool operation

Thresholds

VoIP topology

Performancetraps

HTTP connection

VoIPAvailabilityManager

Call Manager Cluster 1Managed by VoIP

Performance Manager

Call Manager Cluster 2Managed by VoIP

Performance Manager

Call Manager Cluster nManaged by VoIP

Performance Manager

VoIP Performance Managerintercommunication

...

VoIP Performance Managerintercommunication

VoIP Performance Manager

Managing Node

Thresholds

HTTP port

VoIP Performance

ManagerTomcat

Global Manager

VoIP topology

Global Console

NativeWin32

Console

Java-based GUI

(drill down)

URL launch

VoIP client tools 23

Integration

Invoking a VoIP client tool for a particular VoIP Availability Manager topology object opens a web browser that loads the VoIP Performance Manager drill-down display associated with the object and the tool itself. The name of the tool indicates the category (view) of collected performance data that the tool will display for the object.

VoIP Performance Manager’s Java-based GUI and displays

The VoIP Performance Manager Java-based GUI has the same performance and status displays as the native Win32 GUI, including the drill-down capability. The Java-based GUI is read-only and does not provide administrative configuration capabilities. As such, Global Console users can open the Java-based GUI to drill down for more detail without affecting the configuration of the VoIP environment.

In Figure 3 on page 22, the Java-based GUI is launched through a URL that points to the IP address of the Apache Tomcat server on the VoIP Performance Manager managing node. The managing node may be any host, other than a Call Manager’s host, that is running VoIP Performance Manager.

Web browser supportThe URL can be launched from any host that is network-reachable to the VoIP Performance Manager’s web server.

The Java 2 Platform Standard Edition version 5.0 (also known as JRE 1.5) is required.

The following web browsers are supported for accessing VoIP Performance Manager:

◆ Microsoft Internet Explorer 6.0

◆ Mozilla 1.7 and Mozilla Firefox 1.0

◆ Netscape Navigator 7.2

In addition, your web browser must support:

◆ Java Applets (Java Plug-in/ JRE version 5.0 or later recommended)

◆ JavaScript and Applet Scripting (native object scripting in Netscape)

◆ Cookies (only per-session cookies for originating web site are necessary)

Note: Important web browser information is given in “Web browser operation and limitations” on page 29.

Java-based GUI documentationThe VoIP Performance Manager Java-based GUI is described in the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya User Guide and the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya System Guide.

Global Console client toolsClient tools are invoked and executed on the host where the Global Console is running. Thus all files created for a client tool must be located in the Service Assurance Management Suite installation area from which the Global Console is invoked.

A client tool consists of one or more executable tool script files. On Windows systems, a tool is typically invoked by the Windows command interpreter (cmd.exe), and on UNIX systems, a client tool is typically invoked by a shell script (/bin/sh).


Integration

EMC Smarts provides a number of sample tool scripts in the BASEDIR/smarts/actions/client directory that, with minor modifications, work on most systems.

Client tools created to access VoIP Performance Manager data

Included in the BASEDIR/smarts/actions/client/voip directory in the VoIP Availability Manager installation area is a set of client tools created to access VoIP Performance Manager data. The VoIP client tools are described in Table 2 on page 24. To use these client tools, a user must copy the entire voip directory to the BASEDIR/smarts/actions/client directory in the Service Assurance Management Suite installation area from which the Global Console is invoked.

Table 2 VoIP client tools (page 1 of 3)

Client tool script Display name for tool Target object Description

viewCiscoRoutePattern Launch Route Pattern View CallManager(Cisco Call Manager)

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “Route Pattern” performance metrics relevant to the target CallManager object.

viewCiscoLocation Launch Location View Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “Location” performance metrics relevant to the target CallManager object.

viewCiscoConfBridge Launch Hardware Conference Bridge View

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “Hardware Conference Bridge” performance metrics relevant to the target CallManager object.

Launch Software Conference Bridge View

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “Software Conference Bridge” performance metrics relevant to the target CallManager object.

viewCiscoMusicOnHold Launch Multicast Music on Hold View

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “Multicast Music on Hold” performance metrics relevant to the target CallManager object.

Launch Unicast Music on Hold View

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “Unicast Music on Hold” performance metrics relevant to the target CallManager object.


Integration

viewCiscoTranscoder Launch Transcoder View CallManager(Cisco Call Manager)(continued)

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “Transcoder” performance metrics relevant to the target CallManager object.

viewCiscoMediaTermPoint Launch Media Termination Point View

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “Media Termination Point” performance metrics relevant to the target CallManager object.

viewCiscoProcessor-memory Launch Processor and Memory View

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “Processor and Memory” performance metrics relevant to the target CallManager object.

viewAvayaNetworkRegion Launch IP Network Region View ConvergedCallManager(Avaya Call Manager)

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “IP Network Region” performance metrics relevant to the target ConvergedCallManager object.

viewAvayaProcessor Launch Processor View Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing “Processor” performance metrics relevant to the target ConvergedCallManager object.

viewAvayaDS1Service Launch DS1Service View DS1Service(Avaya Digital Signal 1 card)

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing performance metrics relevant to the target DS1Service object.

viewAvayaMediaGateway Launch Media Gateway View GatewayService(Avaya Media Gateway application)

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing performance metrics relevant to the target GatewayService object.

viewAvayaCLAN Launch CLAN View H323GateKeeper(Avaya Control LAN card)

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing performance metrics relevant to the target H323GateKeeper object.




Integration

Each VoIP client tool specifies a web browser and the URL associated with the target object. The name of a client tool indicates the category (view) of collected performance data that the tool will display for its particular target object. For example, the client tool named “Launch Hardware Conference Bridge View” will display a collection of hardware conference bridge performance data relevant to the selected Cisco CallManager object.

Table 3 on page 26 identifies the context filter for each VoIP client tool. A tool’s context filter specifies the tool’s target object and certain target object attribute values.

viewAvayaMedPro Launch MedPro View MediaProcessor(Avaya Media Processor card)

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing performance metrics relevant to the target MediaProcessor object.

viewAvayaPortNetwork Launch Port Network View PortNetwork(A collection of Avaya Media Gateway port cards)

Opens a web browser and loads a URL that points to the VoIP Performance Manager drill-down display containing performance metrics relevant to the target PortNetwork object.

viewVoipPM Launch Voip PM View VoipPerformanceManager Opens a web browser and loads a URL that points to the VoIP Performance Manager “All Clusters Central” display.



Table 3 Context filters for VoIP client tools (page 1 of 2)

Context filter

Available client toolsTarget object Target object attributes

CallManagerA Call Manager application representing a Cisco CallManager (4.0) or a Cisco Unified CallManager (5.0).

Vendor = CISCO,ExternalName = <not empty>

Launch Route Pattern View

Launch Location View

Launch Hardware Conference Bridge View

Launch Software Conference Bridge View

Launch Multicast Music on Hold View

Launch Unicast Music on Hold View

Launch Transcoder View

Launch Media Termination Point View

Launch Processor and Memory View

ConvergedCallManagerA Call Manager application representing an Avaya Communication Manager.

Vendor = AVAYA,ExternalName = <not empty>,NetworkRegion = <not empty>

Launch IP Network Region View

Vendor = AVAYA,ExternalName = <not empty>

Launch Processor View

DS1Service Vendor = AVAYA,Location = <not empty>

Launch DS1Service View


Integration

A tool’s context filter enables the tool to appear in the Client Tools menu when one of its target objects is right-clicked. For example, “Launch Hardware Conference Bridge View” will appear in the Client Tools menu for any Cisco CallManager object having a Vendor attribute of CISCO and an ExternalName attribute that is NOT empty.

In contrast, “Launch Hardware Conference Bridge View” will NOT appear in the Client Tools menu for any Cisco CallManager object having a Vendor attribute of CISCO and an ExternalName attribute that IS empty. Why? Because not having a populated ExternalName attribute indicates that no trap information was ever received from VoIP Performance Manager for this particular object.

URL construction

When constructing a URL for the target object, a VoIP client tool reads the following attributes of the VoipPerformanceManager managing node object:

◆ IPAddress

◆ User_ID

◆ EncryptedPassword (read-only)

The tool uses these values to populate destination address and login fields in the URL, to point to and access the web server on the VoIP Performance Manager managing node. The User_ID and EncryptedPassword values are user-configured, as explained in the EMC Smarts VoIP Availability Manager Configuration Guide.

A VoIP client tool uses different methods to obtain this information, depending on the target object. Other than a target VoipPerformanceManager managing node object, central to these methods is the MonitoredBy relationship between the target object and the VoipPerformanceManager managing node object.

To populate certain prompt-value fields in the URL, the tool reads the target object attributes identified in Table 3 on page 26. For example, if the target object is a CallManager object, the tool reads the object’s ExternalName attribute to learn the name of the VoIP cluster to which the Call Manager belongs, as known to VoIP Performance Manager, and then populates the appropriate prompt-value fields in the URL with that value.

GatewayService Vendor = AVAYA,GatewayNumber = <not empty>

Launch Media Gateway View

H323GateKeeper Vendor = AVAYA,Location = <not empty>,IPAddress = <not empty>

Launch CLAN View

MediaProcessor Vendor = AVAYA,Location = <not empty>,IPAddress = <not empty>

Launch MedPro View

PortNetwork DisplayName = *AVAYA*,PortNetworkNo = <not empty>

Launch Port Network View

VoipPerformanceManager IPAddress = <not empty> Launch Voip PM View

Table 3 Context filters for VoIP client tools (page 2 of 2)

Context filter

Available client toolsTarget object Target object attributes


Integration

VoIP client tool invocation

When the VoIP client tools are configured, they are invoked by-right clicking a target VoIP topology object in a Topology Browser attached to the Global Manager, then selecting Client Tools > <VoIP client tool name> in the pop-up menu.

For example, right-clicking a Cisco CallManager object in the Topology Browser and selecting Client Tools > Launch Location View from the pop-up menu opens a web browser and loads the Locations drill-down display shown in Figure 4 on page 28.

Figure 4 VoIP Performance Manager’s Locations drill-down display—example

Configuration procedures 29

Integration

Web browser operation and limitations

If you configure Internet Explorer as your browser of choice, as explained in the EMC Smarts VoIP Availability Manager Configuration Guide, you can invoke one VoIP client tool after another without closing the browser instance opened by the previously invoked client tool. Each invocation of a VoIP client tool opens another web browser instance, which establishes a new session with VoIP Performance Manager.

If you configure Mozilla or Mozilla Firefox as your browser of choice, you must close the web browser instance opened by the previously invoked client tool before invoking another client tool. Otherwise, you will receive the following error:

javax.servlet.ServletException: Already connected from this browser

The reason for this error is that instead of opening another web browser instance for each VoIP client tool invocation, Mozilla or Mozilla Firefox attempts to establish a new session with VoIP Performance Manager using the web browser instance opened by the previously invoked client tool.

During a session with VoIP Performance Manager using any web browser, be it Internet Explorer, Netscape Navigator, Mozilla, or Mozilla Firefox, you will receive this same error message if you try to open a link in a new window or open a new tab, for the same reason previously stated. To avoid this error, use a web browser to log in just once to VoIP Performance Manager, and use the navigation within the VoIP Performance Manager interface to view other pages, instead of changing the URL to view other pages.

Configuration proceduresThe procedures for configuring SNMP trap integration are given in Chapter 3, “Configuring SNMP Trap Integration,” and the procedures for configuring VoIP client tools are given in the EMC Smarts VoIP Availability Manager Configuration Guide.


Integration

Configuring SNMP Trap Integration 31

3

This chapter provides instructions for configuring the SNMP trap integration in a VoIP Management Suite 3.0 deployment in which VoIP Performance Manager is integrated with VoIP Availability Manager. It consists of the following sections:

◆ Configuration overview ............................................................................................... 32◆ Copying, configuring, and starting PMT-THRESHOLD ........................................ 32◆ Enabling the VoIP Availability Manager built-in trap receiver .............................. 33◆ Controlling the processing of VoIP Performance Manager traps........................... 33◆ Customizing performance polling and thresholds .................................................. 34◆ Troubleshooting............................................................................................................. 34

Configuring SNMP TrapIntegration


Configuring SNMP Trap Integration

Configuration overviewConfiguring SNMP trap integration consists of the following steps:

1. “Copying, configuring, and starting PMT-THRESHOLD” to initiate the sending of the VoIP Performance Manager traps required by VoIP Availability Manager.

2. “Enabling the VoIP Availability Manager built-in trap receiver” to receive and process VoIP Performance Manager traps.

3. “Controlling the processing of VoIP Performance Manager traps” through parameter settings in the voip.conf file.

4. “Customizing performance polling and thresholds” through a Polling and Thresholds Console attached to VoIP Availability Manager.

Copying, configuring, and starting PMT-THRESHOLDVoIP Performance Manager provides a comprehensive SNMP Traps Out functionality for sending traps to other management systems, such as VoIP Availability Manager. The traps are defined in the Integrated Research Enterprise OID .1.3.6.1.4.1.6102.

Using the SNMP Traps Out functionality, EMC has created documents that define the VoIP Performance Manager traps required by VoIP Availability Manager. The documents, contained in a single binary file named PMT-THRESHOLD.thr, is located in the BASEDIR/smarts/voip-pm directory in the VoIP Availability Manager installation area.

You copy this file where the EMC Smarts VoIP Performance Manager GUI resides, then use the VoIP Performance Manager GUI to configure it and start the PMT-THRESHOLD process. Configuring PMT-THRESHOLD involves pointing to the host and trap listening port of the host running VoIP Availability Manager.

To copy, configure, and start PMT-THRESHOLD:

1. In the VoIP Availability Manager installation area, copy the PMT-THRESHOLD.thr file located in the BASEDIR/smarts/voip-pm directory to the ${VOIP-PM-HOME}\User Interface\My Displays & Configurations folder where the VoIP Performance Manager GUI is running. The default value for ${VOIP-PM-HOME} is:

C:\Program Files\EMC Smarts VoIP Performance Manager

2. Start the EMC Smarts VoIP Performance Manager GUI.

3. Refresh the document navigator pane if the GUI does not show the PMT-THRESHOLD document.

Enabling the VoIP Availability Manager built-in trap receiver 33


4. Right-click the PMT-THRESHOLD document and select Properties from the pop-up menu to display the document’s Properties window.

5. In the Properties window, update the Default Destinations properties as follows:

• In the SNMP Trap Host field, change 127.0.0.1 to the hostname or IP address of the host on which VoIP Availability Manager is installed.

• In the SNMP Trap Port field, change 9001 (if need be) to the trap listening port configured for the VoIP Availability Manager built-in trap receiver.

6. Click OK to save your changes.

7. Start the PMT-THRESHOLD process in one of two ways:

• Double-click PMT-THRESHOLD in the navigator pane.

• Drag PMT-THRESHOLD over VoIP Performance Manager in the node navigator pane.

8. Verify that the PMT-THRESHOLD process is running in one of two ways:

• Examine the event history under the File menu.

• Check for the running process name under Thresholds.

Enabling the VoIP Availability Manager built-in trap receiverYou enable the VoIP Availability Manager built-in trap receiver so that it can receive and process VoIP Performance Manager traps. You do so by uncommenting the “TrapPort = 9001” parameter line in the BASEDIR/smarts/conf/voip/voip.conf file in the VoIP Availability Manager installation area.

The EMC Smarts VoIP Availability Manager Configuration Guide describes this parameter and provides instructions on modifying it.

Controlling the processing of VoIP Performance Manager trapsYou control the processing of VoIP Performance Manager traps through the following parameter settings in the BASEDIR/smarts/conf/voip/voip.conf file in the VoIP Availability Manager installation area:

◆ IsPMTrapReceiverEnabled

◆ PMTraps_Timeout

◆ SyncDelay

◆ TracePMTraps



The EMC Smarts VoIP Availability Manager Configuration Guide describes these parameters and provides instructions on modifying them.

Customizing performance polling and thresholdsYou customize performance polling for Avaya and Cisco network services, and customize performance thresholds, through a Polling and Thresholds Console attached to VoIP Availability Manager.

The EMC Smarts VoIP Availability Manager Configuration Guide describes the performance polling and threshold groups, settings, and parameters and provides instructions on modifying them.

TroubleshootingIf VoIP Availability Manager does not discover VoIP Performance Manager:

◆ Verify that VoIP Performance Manager is running.

◆ Verify that the SNMP service is running on VoIP Performance Manager.

◆ Verify that VoIP Performance Manager’s host is discovered by IP Availability Manager; if not, rediscover VoIP Performance Manager’s host in IP Availability Manager.

If VoIP Availability Manager is not receiving any traps:

◆ Verify that the PMT-THRESHOLD process is running on VoIP Performance Manager.

◆ Verify that the following PMT-THRESHOLD trap destinations are set correctly:

• SNMP Destination Host

• SNMP Trap Port

◆ Verify that the trap listening port for the VoIP Availability Manager built-in trap receiver is set to a valid port number: 162 or any value in the range 2049 to 65534 inclusive.

◆ Verify that the SNMP Trap Port destination and the built-in trap receiver are set to the same port.

◆ Verify that the built-in trap receiver is running.

Note: Although unlikely, the built-in trap receiver might not start due to a port conflict.

To confirm that the built-in trap receiver is running, go to the BASEDIR/smarts/bin directory in the VoIP Availability Manager installation area and type the following command on one line:

dmctl -s <VoIP AM instance name> get VOIP_Manager::VOIP-Manager::IsTrapReceiverRunning

Press Enter.

The response is TRUE if the built-in trap receiver is running.