VoIP Management Suite Overview and Integration Guide

VoIP Management Suite Overview andIntegration Guide

VMware Smart Assurance 10.1.0

You can find the most up-to-date technical documentation on the VMware website at:

https://docs.vmware.com/

If you have comments about this documentation, submit your feedback to

[email protected]

VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com

Copyright © 2019 VMware, Inc. All rights reserved. Copyright and trademark information.

VoIP Management Suite Overview and Integration Guide

VMware, Inc. 2


mailto:[email protected]

http://pubs.vmware.com/copyright-trademark.html

Contents

1 Preface 5Audience 5

VMware Smart Assurance VoIP Management Suite installation directory 5

VMware Smart Assurance VoIP Management Suite products 6

Related documentation 6

Help for command line programs 6

VMware Smart Assurance documentation 6

VMware Smart Assurance VoIP Management Suite documentation 7

Suggestions for searching PDF files 7

Where to get help 8

Conventions used in this document 8

Typographical conventions 8

Pathname conventions 9

Graphical conventions 9

Manager 9

2 Introduction 11VMware Smart Assurance VoIP Management Suite overview 11

Functionality 11

Products 11

Deployment 12

Platform support 12

User preference 12

User documentation 13

Additional products in a VoIP Management Suite deployment 13

VoIP Management Suite deployment architecture 13

VoIP Availability Manager 14

VoIP Performance Manager 15

VoIP Performance Reporter 15

IP Availability Manager 16

Global Manager 17

Adapter Platform 17

Business Impact Manager 17

Global Console 17

VMware Smart Assurance Broker 18

Implementation scenario: IP phones 18

3 Integration 22

VMware, Inc. 3

Integration overview 22

VoIP Performance Manager performance data and processing 23

Performance-related objects and attributes 25

MediaResourceAggregate objects 25

Performance-related attributes 26

Name mapping 28

VoIP client tools 28

VoIP Performance Manager’s Java-based GUI and displays 29

Global Console client tools 30

Client tools created to access VoIP Performance Manager data 30

URL construction 33

VoIP client tool invocation 33

Web browser operation and limitations 34

4 Configuring VoIP Performance Manager Integration 36Configuration overview 36

Automatically configuring the PMT-THRESHOLD process 36

Modify the VoIP Availability Manager domain.conf file 37

Verify that the PMT-THRESHOLD process is running 38

Enabling the VoIP Availability Manager built-in trap receiver 39

Controlling the processing of VoIP Performance Manager traps 39

Customizing performance polling and thresholds 39

Troubleshooting 39

5 Manual Method: Configuring Integration 41Configuration overview 41

Copying, configuring, and starting PMT-THRESHOLD 41

Enabling the VoIP Availability Manager built-in trap receiver 43

Controlling the processing of VoIP Performance Manager traps 43

Customizing performance polling and thresholds 43

Troubleshooting 44


VMware, Inc. 4

Preface 1As part of an effort to improve and enhance the performance and capabilities of its product lines, VMwareperiodically releases revisions of its hardware and software. Therefore, some functions described in thisdocument may not be supported by all versions of the software or hardware currently in use. For the mostup-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 contactyour VMware representative.

This chapter includes the following topics:

n Audience

n VMware Smart Assurance VoIP Management Suite installation directory

n VMware Smart Assurance VoIP Management Suite products

n Related documentation

n Suggestions for searching PDF files

n Where to get help

n Conventions used in this document

Audience

This document is part of the VMware Smart Assurance VoIP Management Suite 4.0 documentation set. Itis intended for IT managers seeking to better understand the value of the VMware Smart Assurance VoIPManagement Suite 4.0 products, for administrators configuring and using the VoIP Management Suiteproducts, and for operators receiving and acting upon notifications analyzed by the VoIP ManagementSuite products. It provides an overview of the VoIP Management Suite products and discusses theintegration of these products not only with each other but also with the VMware Smart Assurance IPAvailability Manager and the VMware Smart Assurance Service Assurance Manager.

VMware Smart Assurance VoIP Management Suiteinstallation directory

In this document, the term BASEDIR represents the location where VMware Smart Assurance software isinstalled:

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

VMware, Inc. 5

n The <productsuite> represents the VMware Smart Assurance product suite to which the productbelongs. For example, on UNIX operating systems, VMware Smart Assurance VoIP ManagementSuite is, by default, installed to: /opt/InCharge/VoIP/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 VMware Smart Assurance System Administration Guide provides detailed information about thedirectory structure for VMware Smart Assurance software.

VMware Smart Assurance VoIP Management Suiteproducts

The VMware Smart Assurance VoIP Management Suite includes the following:

n VMware Smart Assurance VoIP Availability Manager

n VMware Smart Assurance VoIP Integration Pack for VoIP Performance Manager

n VMware Smart Assurance Enablement Pack for Avaya

n VMware Smart Assurance Enablement Pack for Cisco

n VMware Smart Assurance Enablement Pack for Nortel

n VMware Smart Assurance VoIP Performance Manager

n VMware Smart Assurance VoIP Performance Reporter

Related documentation

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

Help for command line programs

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

VMware Smart Assurance documentation


VMware, Inc. 6

Readers of this guide may find the following related documentation helpful. It can be found in theBASEDIR/smarts/doc/pdf directory:

Note These documents are updated periodically. Electronic versions of the updated manuals areavailable on the VMware Docs website:

https://docs.vmware.com/n VMware Smart Assurance Documentation Catalog

n VMware Smart Assurance System Administration Guide

n VMware Smart Assurance ICIM Reference (in HTML format)

n VMware Smart Assurance ASL Reference Guide

n VMware Smart Assurance Perl Reference Guide

n VMware Smart Assurance MODEL Reference Guide

VMware Smart Assurance VoIP Management Suite documentation

The following documents are relevant to users of the VMware Smart Assurance VoIP Management Suite:

n VMware Smart Assurance VoIP Management Suite Release Notes (VMware Docs only)

n VMware Smart Assurance VoIP Availability Manager Installation Guide

n VMware Smart Assurance VoIP Availability Manager Configuration Guide

n VMware Smart Assurance VoIP Availability Manager Discovery Guide

n VMware Smart Assurance VoIP Management Suite Overview and Integration Guide

n VMware Smart Assurance VoIP Availability Manager User Guide

n VMware Smart Assurance Enablement Pack for Avaya User Guide

n VMware Smart Assurance Enablement Pack for Cisco User Guide

n VMware Smart Assurance Enablement Pack for Nortel User Guide

n VMware Smart Assurance VoIP Availability Manager Certification Matrix (VMware Docs only)

n VMware Smart Assurance VoIP Performance Manager and Performance Reporter Certification Matrix(VMware Docs only)

n VMware Smart Assurance VoIP Management Suite Certification Framework Technical Notes(VMware Docs only)

n VMware Smart Assurance VoIP Availability Manager Third-Party Copyright Read Me

The VMware Smart Assurance Documentation Catalog lists documentation resources provided withother VMware Smart Assurance product suites.

Suggestions for searching PDF files


VMware, Inc. 7


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 VMware Smart Assurance product suite,copy the contents of the BASEDIR/smarts/doc/pdf directory to a central location, such as a shareddrive on your LAN, that operators and others may view.

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

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

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

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

Where to get help

VMware support, product, and licensing information can be obtained as follows.

Product information

For documentation, release notes, software updates, or for information about VMware products, licensing,and service, go to VMware Online Support at:

http://support.vmware.com

http://docs.vmware.com

Technical support

VMware Online Support and click Service Center. You will see several options for contacting VMwareTechnical Support. Note that to open a service request, you must have a valid support agreement.Contact your VMware sales representative for details about obtaining a valid support agreement or withquestions about your account.

Conventions used in this document

VMware uses the following conventions for special notices.

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

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

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

Typographical conventions

VMware uses the following type style conventions in this document:


VMware, Inc. 8

http://support.vmware.com

http://docs.vmware.com

Normal Used in running (nonprocedural) text for:

n Names of interface elements (such as names of window, dialog boxes, buttons, fields, andmenus)

n Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements,keywords, clauses, environment variables, functions, utilities

n URLs, pathnames, filenames, directory names, computer names, filenames, links, groups,service keys, file systems, notifications

Bold Used in procedures for:

n Names of interface elements (such as names of window, dialog boxes, buttons, fields, andmenus)

n What user specifically selects, clicks, presses, or types

Italic Used in text for:

n Full titles of publications referenced in text

n Emphasis (for example a new term)

CourierUsed for:

n System output, such as an error message or script

n URLs, complete paths, filenames, prompts, and syntax when shown outside of running text

Courier bold

Used for:

n Specific user input (such as commands)

Courier italic

Used in procedures for:

n Variables on command line

n 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

Pathname conventions

Directory pathnames are shown with forward slashes (/).

Graphical conventions

If there are figures illustrating consoles in this document - under UNIX, the consoles appear with slightdifferences. For example, in views that display items in a tree hierarchy such as the Topology Browser, anopen circle appears for UNIX.

Manager


VMware, Inc. 9

Unless otherwise specified, the term Manager is used to refer to VMware Smart Assurance programssuch as Domain Managers, Global Managers, and adapters.


VMware, Inc. 10

Introduction 2This chapter includes the following topics:

n VMware Smart Assurance VoIP Management Suite overview

n Additional products in a VoIP Management Suite deployment

n VoIP Management Suite deployment architecture

n Implementation scenario: IP phones

VMware Smart Assurance VoIP Management Suiteoverview

The VMware Smart Assurance VoIP Management Suite provides enterprises with availability, faultmanagement, and performance visibility across their Voice over IP (VoIP) infrastructures. It providesmulti-vendor support and a comprehensive VoIP management solution. It enables enterprises to performIP phone management, service management, and voice mail management. For Cisco Call Manager UnityExpress (CUE) devices, it also provides voice mailbox management.

Functionality

The VoIP Management Suite performs the following tasks:

n Discovers VoIP-enabled devices and VoIP applications

n Monitors the devices and applications and collects performance metrics

n Correlates alerts and events

n Identifies failures and trends

n Analyzes and presents events and problems

Products

The VoIP Management Suite consists of the following products:

n VMware Smart Assurance VoIP Availability Manager (VoIP Availability Manager)

n VMware Smart Assurance VoIP Integration Pack for VoIP Performance Manager

n VMware Smart Assurance Enablement Pack for Avaya

n VMware Smart Assurance Enablement Pack for Cisco

VMware, Inc. 11

n VMware Smart Assurance Enablement Pack for Nortel

n VMware Smart Assurance VoIP Performance Manager (VoIP Performance Manager)

n VMware Smart Assurance VoIP Performance Reporter (VoIP Performance Reporter)

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

Deployment

A VoIP Management Suite 4.0 deployment consists of:

n One VoIP Availability Manager configured to receive from one VoIP Performance Manager

n One VoIP Performance Reporter

n The VMware Smart Assurance VoIP Integration Pack for VoIP Performance Manager

n One or more enablement packs

n One or more VMware Smart Assurance IP Manager products described in “Additional products in aVoIP Management Suite deployment” on page 14.

n All of the VMware Smart Assurance Service Assurance Manager products described in “Additionalproducts in a VoIP Management Suite deployment” on page 14.

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

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

Also, you need to satisfy these prerequisites:

n The VoIP Performance Manager must have the latest patch applied. For requirements regarding VoIPPerformance Manager, consult the VMware Smart Assurance VoIP Management Suite ReleaseNotes.

n For Cisco Unified Contact Center Enterprise (CUCCE) version 7 and later, the Cisco Contact CenterSNMP Agent must be running in order for the Cisco MIB to return values for the discovery probe andfor monitoring.

The service name for this Cisco-specific agent is Cisco Contact Center SNMP Management.

Platform support

VoIP Availability Manager is supported on Solaris and Linux. The respective product installation guidesspecify the operating system version and hardware requirements.

User preference


VMware, Inc. 12

In general, NOC operators will use VoIP Availability Manager and staff members will use VoIPPerformance Manager and VoIP Performance Reporter. NOC operators are typically more interested inusing VoIP Availability Manager to view the events and problems on screen. Staff members are typicallymore interested in using VoIP Performance Manager and VoIP Performance Reporter to manage theVoIP environment and to troubleshoot VoIP issues that affect service.

User documentation

Each VoIP Management Suite product has its own user documentation set. Together, the userdocumentation 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 Suitedeployment

Besides the installation of the VoIP Management Suite products, the following additional products areinstalled in a VoIP Management Suite 4.0 deployment:

n VMware Smart Assurance IP Manager products

n VMware Smart Assurance IP Availability Manager

n VMware Smart Assurance IP Performance Manager (optional, recommended)

n VMware Smart Assurance IP Server Performance Manager (optional)

n VMware Smart Assurance Service Assurance Manager products

n VMware Smart Assurance Global Manager

n VMware Smart Assurance Global Console

n VMware Smart Assurance Service Assurance Manager Adapter Platform

n VMware Smart Assurance SNMP Trap Adapter configured as a trap exploder

n VMware Smart Assurance SNMP Trap Adapter configured as a trap receiver

n VMware Smart Assurance Business Impact Manager (optional)

The VMware Smart Assurance Installation Guide for SAM, IP, ESM, MPLS, and NPM Managersand the VMware Smart Assurance Installation Guide for SAM, IP, ESM, MPLS, and NPMManagers provide information about installing these additional products.

VoIP Management Suite deployment architecture

VoIP Management Suite deployment architecture shows how the VoIP Management Suite and additionalproducts interact in a VoIP Management Suite 4.0 deployment.


VMware, Inc. 13

Figure 2-1. VoIP Management Suite deployment architecture

VoIP Availability Manager

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:

n Avaya

n Cisco

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


VMware, Inc. 14

Upon importing a list of VoIP-enabled devices from IP Availability Manager, VoIP Availability Managerperforms its own SNMP, SOAP, and CLI discovery to query the managed devices for VoIP topologyinformation. 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.

In addition, if Business Impact Manager Integration is enabled, VoIP Availability Manager associatesVoIP objects with Business objects by using the BIM model. VoIP Availability Manager exports theseobjects to the Global Manager for subsequent impact analysis by Business Impact Manager.

VoIP Performance Manager

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

VoIP Performance Manager accomplishes its mission by:

n Monitoring the CPU load, packet delays, VoIP Call Manager (soft switch) activity, and associatedtelephony service-level indicators, such as call quality, activity, and duration across multiple serversand clusters.

n Monitoring the servers and associated network, hardware, and software components, including:

n Structured Query Language (SQL) servers

n Trivial File Transfer Protocol (TFTP) servers

n IP PBX

n Gateways

n Additional devices

n Signaling Services

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

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 andapplications throughout the Avaya or Cisco VoIP network, to produce charts, graphs, and reports to helpadministrators visualize and understand important trends across the VoIP environment. This historicalinformation is the lifeblood of capacity planning, trend analysis, and problem resolution.


VMware, Inc. 15

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

VoIP Performance Reporter reports and their use shows the high-level report types created by VoIPPerformance Reporter and the functional areas where each report type can be used.

Table 2-1. VoIP Performance Reporter reports and their use

Domain Report Service level Capacity planning Troubleshooting

Voice Voice Quality x x

Voice QualityException

x

Calls PBX Call Load x x

Call Failure x

Long Duration x

Location Calls x x x

Routing Route PatternAvailability

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

IP Availability Manager

IP Availability Manager discovers the underlying transport domain in the VoIP network, monitorsavailability, and analyzes the network connectivity to identify the root-cause problems and impacts ofconnectivity 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 signaling servers, 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 IPAvailability Manager instance may consist of just an IP Availability Manager process, or may consist of anIP Availability Manager and an IP Performance Manager or IP Server Performance Manager running as asingle process.


VMware, Inc. 16

Global Manager

The Global Manager integrates the topology, problem, and impact information imported from the IPAvailability Manager and VoIP Availability Manager, and relates the information to services andcustomers. 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 AvailabilityManager, and imports and normalizes events of interest from VMware Smart Assurance adapters such asthe SNMP Trap Adapter and the VoIP Notification Trap Adapter. Normalize means to convert topology orevent information into a common form understood by the Global Manager. The normalized eventinformation is transferred as VMware Smart Assurance notifications to the Global Manager.

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

Business Impact Manager

Business Impact Manager is a Service Assurance Manager component which imports topological objects.It determines how VoIP root-cause events affect business services and their customers, and reports theresults of its analysis in the form of impacted events and colored nodes in Business Service Maps.Operators can also view the topological objects in the Global Console. In addition, features likecustomizations with Topology Builder, impact calculation, and weight assignment are also available.

Depending upon your Service Assurance Manager version, Business Impact Manager exists as aseparate underlying domain, INCHARGE-MBIM (for Service Assurance Manager version 8.0), or as partof the Global Manager.

In order for VoIP Availability Manager to associate discovered VoIP topology with BIM service offerings,you need to set the EnableBIMIntegration parameter to TRUE in the voip.conf file located in theBASEDIR/smarts/conf/voip directory. This parameter and other tasks for configuring Business ImpactManager are described in the VMware Smart Assurance VoIP Availability Manager Configuration Guide.

The VMware Smart Assurance Business Impact Manager User Guide provides complete informationabout ServiceOffering and ServiceSubscriber classes, Business maps, customizations with TopologyBuilder, impact calculation, and weight assignment.

Global Console

The Global Console provides a graphical user interface for configuring and administering GlobalManagers, Adapter Platform Servers, Domain Managers, and externally running VMware SmartAssurance 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 topologyin various forms, including maps, and to view notifications about problems that impact availability andperformance.


VMware, Inc. 17

In a VoIP Management Suite deployment, the Global Console is the GUI for VoIP Availability Manager butnot for VoIP Performance Manager or VoIP Performance Reporter. (VoIP Performance Manager and VoIPPerformance Reporter have their own graphical user interfaces.) The Global Console can be configuredto open a web-browser Java-based GUI to view VoIP Performance Manager data.

VMware Smart Assurance Broker

The VMware Smart Assurance Broker facilitates Global Console connections to the componentapplications in an VMware Smart Assurance system deployment.

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

Implementation scenario: IP phones

An IP phone is a physical instrument that acts as a telephone that uses Voice over IP technology. In theVoIP environment, the medium used to transmit the telephone service are the cables of the computernetwork. An IP phone can transmit audio-only information, or video and audio information.

The VoIP Management Suite supports IP phones for these vendors: Avaya, Cisco, and Nortel.

For example, below image illustrates an example of a VoIP deployment that uses a Cisco Call Managercluster.

A VoIP deployment may contain many hardware entities, including call servers and media servers, mediagateways, media modules, circuit packs, telephones including speakerphones, and Ethernet switches.Some host servers, such as the call server providing the call manager service, contain applications fordatabase management, device initialization, device control, voice mail, and software conferencing. Whileother host servers, called dedicated servers, run only a single application.


VMware, Inc. 18

Figure 2-2. Single-site deployment discovered by VoIP Availability Manager—example

In VoIP Availability Manager topology, an IP phone is:

n Associated with its physical switch port

n A member of a logical IP phone group

IP Phone Scenario image illustrates IP phones that are members of a logical IP phone group. IPphones are associated with a call agent using RegisteredTo relationships. Conversely, the call agentis associated with IP phones using RegisteredFrom relationships.

In IP Phone Scebario image, IP phone A is registered to a call agent. Depending on the vendor, a callagent can be an Avaya Converged Call Manager, a Cisco Call Manager, or a Nortel Signaling Server.

An IP phone is also associated with a port on a switch using the ConnectedPort relationship. The portis associated with the IP phone using the ConnectsPhone relationship.

A logical IP phone group corresponds to:

n A configuration for Avaya. The IP phones configured to register to a specific converged call managerare treated as an IP phone group. The phone-related information is stored in G3 MIB tables. Duringthe VoIP Availability Manager discovery, the information is accessed using SNMP.

n A device pool for Cisco. The Cisco system administrator assigns IP phones to device pools. Thephone-related information is stored in Cisco-CCME-MIB and Cisco-CCM-MIB tables. During the VoIPAvailability Manager discovery, the information is accessed using SNMP and Simple Object AccessProtocol (SOAP).


VMware, Inc. 19

n A zone for Nortel. The Nortel system administrator defines zones of managed IP phones. The phone-related information is stored in a Nortel signaling server and call server. During the VoIP AvailabilityManager discovery, the information is accessed using Nortel CLI commands.

Figure 2-3. IP phone scenario

VoIP Availability Manager discovers, monitors, and performs root-cause analysis on VoIP-enableddevices like IP phones, logical components like IP phone groups, and services like media servers.

The following are analysis examples:

n When a network segment fails, the IP phones in the segment are unavailable to make and receivephone calls. Their RegistrationStatus attribute changes to the Unregistered value.

As a result, the VoIP Availability Manager generates Unregistered events for the individual IP phonesand a RegistrationExceptions aggregate for the phone group. The events and aggregate appear asnotifications in the Global Console. To view the component notifications of an aggregate, open theNotification Properties dialog box.

n For an IP phone group, when the percentage of IP phones with an unregistered status exceeds theUnregisteredThreshold threshold, the VoIP Availability Manager generates an Impacted aggregateconsisting of a Degraded event. The aggregate appears in the Global Console.

n If the switch port is down, the VoIP Availability Manager generates an Unregistered event for the IPphone.


VMware, Inc. 20

VMware Smart Assurance VoIP Availability Manager User Guide provides more information about theevents that are generated for phone and voice mailbox monitoring.

Note The discovery of IP phones and voice mailboxes needs to be enabled during configuration. Bydefault, discovery for these devices and services is not enabled. Modify the parameters in theBASEDIR/smarts/conf/voip/voip.conf file, as described in the VMware Smart Assurance VoIPAvailability Manager Configuration Guide.


VMware, Inc. 21

Integration 3This chapter includes the following topics:

n Integration overview

n VoIP Performance Manager performance data and processing

n Performance-related objects and attributes

n VoIP client tools

Integration overview

The integration of VoIP Performance Manager with VoIP Availability Manager involves two areas offunctionality:

n The processing of VoIP Performance Manager performance data by VoIP Availability Manager. VoIPPerformance Manager traps carry performance-oriented data and serve as points of integrationbetween VoIP Performance Manager and VoIP Availability Manager.

n The launching of Global Console client tools for a selected VoIP Availability Manager topology objector a selected notification to open a web interface that loads a VoIP Performance Manager drill-downdisplay relevant to the selected object. The drill-down display contains a collection of performancemetrics associated with the object.

For integration to occur, you need to satisfy the following prerequisites:

n The VMware Smart Assurance VoIP Integration Pack for VoIP Performance Manager is installed.

n VoIP Availability Manager is configured.

n The VoIP Performance Manager integration is configured, as described in Chapter 4 Configuring VoIPPerformance Manager Integration

n VoIP Availability Manager discovery is completed and that VoIP Availability Manager discovered VoIPPerformance Manager.

For the first functionality, performance metrics are sent in the form of VoIP Performance Managertraps to VoIP Availability Manager. VoIP Availability Manager uses the performance data to updateperformance-related attributes in classes of the VoIP Availability Manager data model. “Performance-related objects and attributes” on page 26 describes the classes that are updated.

VMware, Inc. 22

VMware predefines the VoIP Performance Manager traps and VoIP Performance Manager generatesthem periodically—every four minutes by default. Each predefined trap is given a name that identifiesthe category, or view, of the collected performance metrics contained in the trap. The periodicreceiving of performance metrics enriches the VoIP Availability Manager topology. Together, theenhanced data model and the periodic updates of performance data, enable VoIP AvailabilityManager to generate performance-related events.

For the second functionality, Global Console users access VoIP Performance Manager drill-downdisplays associated with the VoIP Availability Manager topology and notifications. This allows GlobalConsole users to troubleshoot alarms which involve specific VoIP Availability Manager topologyobjects and selected notifications. VoIP client tools describes how client tools interact and the clienttools that are available.

VoIP Performance Manager performance data andprocessing

Processing of VoIP Performance Manager performance data shows how VoIP Availability Managerprocesses the performance data from VoIP Performance Manager. The mechanism that conveysperformance data is a VoIP Performance Manager trap. The integration procedure is provided in Chapter4 Configuring VoIP Performance Manager Integration


VMware, Inc. 23

Figure 3-1. Processing of VoIP Performance Manager performance data

VoIP Performance Manager periodically sends predefined traps to the VoIP Availability Manager built-intrap receiver. The built-in trap receiver reads the Integrated Research 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 thename of the trap. The selected PM trap handler parses the trap for performance metrics and applies theirvalues to the appropriate attributes of the corresponding object in the VoIP Availability Manager modeledtopology.

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


VMware, Inc. 24

If the corresponding object cannot be found in the topology, the PM trap handler discards the trap. Mediaresource type traps are exceptions to this rule. MediaResourceAggregate objects describes how mediaresource data is processed.

Note The VoIP Performance Manager traps that convey the performance data should not be confusedwith VoIP Performance Manager threshold traps which are informational traps. Performance data trapsprovide performance-oriented data for object attributes. Informational traps do not. The VoIP NotificationTrap Adapter collects and parses informational traps, and then the Adapter Platform processes them astrap notifications. VMware Smart Assurance VoIP Availability Manager Configuration Guide providescomplete information about traps that are converted to notifications.

Performance-related objects and attributes

After completing its discovery, VoIP Availability Manager creates an instance of theVoipPerformanceManager class to discover and monitor VoIP Performance Manager applications in themanaged environment. The instance is a VoIP Performance Manager application known as the VoIPPerformance Manager managing node. This application is represented as a VoipPerformanceManagerobject in VoIP Availability Manager’s topology, and the object’s Type attribute is set to Manager.

Then, VoIP Availability Manager begins processing performance-related data from VoIP PerformanceManager. Specifically, the VoIP Performance Manager Integration Pack extracts the performance datafrom traps and uses it to update new performance-related attributes in the following classes of the VoIPAvailability Manager data model:

n CallManager (Cisco)

n ConvergedCallManager (Avaya)

n DS1Service (Avaya)

n GatewayService (Avaya, Cisco, Nortel)

n H323GateKeeper (Avaya)

n H323Service (Cisco)

n MediaProcessor (Avaya)

n MediaResourceAggregate (Cisco)

n SignalingService (Nortel)

n VoipCluster (Avaya, Cisco, Nortel)

If necessary, VoIP Availability Manager also creates a two-way Monitors/MonitoredBy relationshipbetween the object and the VoipPerformanceManager managing node object.

MediaResourceAggregate objects


VMware, Inc. 25

As described in VoIP Performance Manager performance data and processing, a PM trap handler parsesthe incoming performance data trap and applies the values to the appropriate object. If a correspondingobject cannot be found in the topology, a trap handler discards the trap.

Media resource traps, which are applicable to Cisco only, are exceptions to this rule. For a receivedmedia resource trap having no corresponding object in the topology, the trap handler creates acorresponding MediaResourceAggregate object in the topology and associates the created object with itsVoipCluster instance.

Note VoIP Availability Manager does not discover MediaResourceAggregate objects.

A MediaResourceAggregate object contains summary performance data for a specific type of registeredmedia device, where the Type attribute is one of the following values:

n HardwareConference

n SoftwareConference

n VideoConference

n Annunciator

n MediaTerminationPoint

n Transcoder

n MusicOnHold (MOH)

n MOH-Unicast

n MOH-Multicast

Each MediaResourceAggregate object has a one-way, one-to-many ConsumedBy relationship withMediaService objects of the same type. Each MediaResourceAggregate object also has a two-wayProvidesDataFor/ProvidesDataBy relationship with CallManager objects.

MediaService objects represent applications that handle functions like:

n Decoding DTMF tones

n Transmitting dial tones, busy signals, and announcements

n Bridging multiple media streams into a conference

For a MusicOnHold (MOH) trap, the trap handler creates three MediaResourceAggregate objects:

n The first object has Type=MusicOnHold.

n The second object has Type=MOH-Multicast (and holds multicast data).

n The third object has Type=MOH-Unicast (and hold unicast data).

The first MusicOnHold object has a ComposedOf relationship with the other two.

Performance-related attributes


VMware, Inc. 26

Some of the performance-related attributes are informational. Others are instrumented or computedattributes based on the performance data received from VoIP Performance Manager. Some reflect thethreshold values set for performance threshold groups, which are accessible through a Polling andThresholds Console attached to VoIP Availability Manager. The attributes that are updated by theperformance data received from VoIP Performance Manager are listed in Attributes that are updated withperformance data.

If the VoIP Performance Manager Integration Pack is not installed, performance-related attributes willeither show default values (0; 0.0; false) or appear grayed-out in the Global Console.

If the VoIP Performance Manager Integration Pack is installed and no VoIP Performance Manager trapsare received for the amount of time specified by the PMTraps_Timeout parameter, the controller for thepack disconnects VoIP Performance Manager instrumentation, which deactivates the performance-related attributes and suspends the generation of performance-related events. The VMware SmartAssurance VoIP Availability Manager Configuration Guide provides information about thePMTraps_Timeout parameter.

Table 3-1. Attributes that are updated with performance data

Vendor Class Attribute

Avaya ConvergedCallManager ProcessorOccupancy

DS1Service DownTrunks, TotalTrunks, ActiveTrunks

GatewayService Status

H323GateKeeper RegisteredPhones, PhoneRegistrationChanges

MediaProcessor ControlLinkStatus, EthernetLinkStatus

VoipCluster TotalRoutePatterns

TotalTrunkGroups

TotalDegradedRoutePatterns

TotalDegradedTrunkGroups

TotalDownRoutePatterns

TotalDownTrunkGroups

Cisco CallManager RegisteredAnalogAccessDevices

RegisteredDigitalAccessDevices

RegisteredHardwarePhones

RegisteredOtherStationDevices

ActiveCalls

CallsInProgress

ActiveVideoCalls

CompletedVideoCalls

RegisteredPhonesPrimary

RegisteredPhonesSecondary

RegisteredPhonesTertiary

GatewayService (Cisco Version 4) Status, ChannelUtilization, FailedOutboundCalls

GatewayService (Cisco Version 5 andabove)

Status, ChannelsInService,ChannelUtilization,PortlUtilization, FailedOutboundCalls


VMware, Inc. 27

Vendor Class Attribute

H323Service ActiveCalls, CallsInProgress, ActiveVideoCalls

MediaResourceAggregate Active, Available, Total

VoipCluster MosAverage

MosAboveThresholdCalls

MosBelowThresholdCalls

MosAboveGoodThresholdCalls

MosBetweenGoodFairThresholdCalls

MosBetweenFairPoorThresholdCalls

MosBelowPoorThresholdCalls

MosThreshold

MosGoodThreshold

MosFairThreshold

MosPoorThreshold

Nortel GatewayService Status

SignalingService Status

VoipCluster TotalRoutes,TotalDegradedRoutes,TotalDownRoutes,TotalTrunks,TotalDownTrunks

Name mapping

To map object names, VoIP Availability Manager receives performance data from VoIP PerformanceManager and uses that information and VoIP Availability Manager discovery information to build systemor cluster name-mapping tables.

Some attributes are needed to bridge the gap between the device-naming schemes used by both VoIPAvailability Manager and VoIP Performance Manager. A good example is the ExternalName attribute,which has been added to the VoipCluster, CallManager, and ConvergedCallManager classes to denotethe names of these objects as known to VoIP Performance Manager.

VoIP client tools

Client tools, as well as server tools, enable Global Console users to invoke programs in response to aparticular target object, such as a notification object, a topology object, or a map object. Right-clicking atarget object displays 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 thisdocument, are available only to certain topology objects which are imported by the Global Manager fromVoIP Availability Manager. They enable Global Console operators to use the Java-based GUI availablefrom the VoIP Performance Manager to access drill-down displays. For example, VoIP client tooloperation image, Global Console operators access drill-down displays from the VoIP PerformanceManager’s web server, in this case, an Apache Tomcat server.


VMware, Inc. 28

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

Figure 3-2. VoIP client tool operation

VoIP Performance Manager’s Java-based GUI and displays

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

In VoIP Overview Integrate, the Java-based GUI is launched through a URL that points to the IP addressof the Apache Tomcat server on the VoIP Performance Manager managing node. The managing nodemay be any host, other than a call manager’s host, that is running VoIP Performance Manager.

Web browser support

The URL can be launched from any host that is network-reachable to the VoIP Performance Manager’sweb 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:

n Microsoft Internet Explorer 6.0

n Mozilla 1.7 and Mozilla Firefox 1.0

n Netscape Navigator 7.2


VMware, Inc. 29

In addition, your web browser must support:

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

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

n Cookies (only per-session cookies for originating website are necessary)

Note Important web browser information is given in Web browser operation and limitations.

Java-based GUI documentation

The VoIP Performance Manager Java-based GUI is described in the VMware Smart Assurance VoIPPerformance Manager User Guide and the VMware Smart Assurance VoIP Performance ManagerSystem Guide.

Global Console client tools

Client tools are invoked and executed on the host where the Global Console is running. Thus, all filescreated for a client tool must be located in the Service Assurance Manager installation area from whichthe Global Console is invoked.

A client tool consists of one or more executable tool script files. On UNIX systems, a client tool is typicallyinvoked by a shell script (/bin/sh).

VMware Smart Assurance provides a number of tool scripts in the BASEDIR/smarts/actions/clientdirectory 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 installationarea is a set of client tools created to access VoIP Performance Manager data. The VoIP client tools aredescribed in VoIP client tools.

To use these client tools, a user must copy the entire voip directory as a subdirectory under theBASEDIR/smarts/actions/client directory in the Service Assurance Manager installation area from whichthe Global Console is invoked. Procedures for configuring VoIP client tools are provided in the VMwareSmart Assurance VoIP Availability Manager Configuration Guide.


VMware, Inc. 30

Table 3-2. VoIP client tools

Client tool script Display name for tool Target object

Opens a web browser and loads aURL that points to the VoIPPerformance Manager drill-downdisplay that contains thefollowing:

viewAvayaNetworkRegion Launch IP Network RegionView

ConvergedCallManager

(Avaya Call Manager)

“IP Network Region” performancemetrics relevant to the targetConvergedCallManager object.

viewAvayaProcessor Launch Processor View “Processor” performance metricsrelevant to the targetConvergedCallManager object.

viewAvayaDS1Service Launch DS1Service View DS1Service

(Avaya Digital Signal 1card)

Performance metrics relevant to thetarget DS1Service object.

viewAvayaMediaGateway Launch Media Gateway View GatewayService

(Avaya Media Gatewayapplication)

Performance metrics relevant to thetarget GatewayService object.

viewAvayaCLAN Launch CLAN View H323GateKeeper

(Avaya Control LAN card)

Performance metrics relevant to thetarget H323GateKeeper object.

viewAvayaMedPro Launch MedPro View MediaProcessor

(Avaya Media Processorcard)

Performance metrics relevant to thetarget MediaProcessor object.

viewAvayaPortNetwork Launch Port Network View PortNetwork

(A collection of AvayaMedia Gateway port cards)

Performance metrics relevant to thetarget PortNetwork object.

viewCiscoRoutePattern Launch Route Pattern View CallManager

(Cisco Call Manager)

“Route Pattern” performance metricsrelevant to the target CallManagerobject.

viewCiscoLocation Launch Location View “Location” performance metricsrelevant to the target CallManagerobject.

viewCiscoConfBridge Launch Hardware ConferenceBridge View

“Hardware Conference Bridge”performance metrics relevant to thetarget CallManager object.

Launch Software ConferenceBridge View

“Software Conference Bridge”performance metrics relevant to thetarget CallManager object.

viewCiscoMusicOnHold Launch Multicast Music onHold View

“Multicast Music on Hold”performance metrics relevant to thetarget CallManager object.

Launch Unicast Music onHold View

“Unicast Music on Hold” performancemetrics relevant to the targetCallManager object.


VMware, Inc. 31

Client tool script Display name for tool Target object

Opens a web browser and loads aURL that points to the VoIPPerformance Manager drill-downdisplay that contains thefollowing:

viewCiscoTranscoder Launch Transcoder View “Transcoder” performance metricsrelevant to the target CallManagerobject.

viewCiscoMediaTermPoint Launch Media TerminationPoint View

“Media Termination Point”performance metrics relevant to thetarget CallManager object.

viewCiscoProcessor-memory

Launch Processor andMemory View

CallManager

(Cisco Call Manager)

“Processor and Memory”performance metrics relevant to thetarget CallManager object.

viewNortelPBX Launch PBX View SignalingService “Nortel PBX” performance metricsrelevant to the targetSignalingService object. This viewprovides an overview of the NortelPBX.

viewNortelServerDetails Launch Server Details View SignalingService “Nortel Server Details” performancemetrics relevant to the targetSignalingService object.

viewNortelGatewayDetails Launch Gateway Details View GatewayService—NortelGateway Service runningon the VGMC card

“Nortel Gateway Details”performance metrics relevant to thetarget GatewayService object.

viewNortelMediaCardDetails

Launch Media Card DetailsView

GatewayService—NortelGateway Servicerepresenting the VGMCcard

“Nortel Media Card Details”performance metrics relevant to thetarget GatewayService object.

Note This view does not appear forMGC or signaling server cards.

viewVoipPM Launch Voip PM View VoipPerformanceManager Opens a web browser and loads aURL that points to the VoIPPerformance Manager “All ClustersCentral” display.

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

In a Global Console, when a target object is right-clicked, the Client Tools menu automatically lists theVoIP client tools that are available. The context filter is the mechanism that determines whether the VoIPclient tool is listed as a selection choice in the Client Tools menu. If the context filter criteria is satisfied,the client tool is listed in the Client Tools menu. The context filter criteria for each tool is described in theVMware Smart Assurance VoIP Availability Manager Configuration Guide.


VMware, Inc. 32

URL construction

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

n Device_User_ID

n Password (read-only)

n WebServerIPAddress

n WebServerPort

The tool uses these values to populate destination address, destination port, and login fields in theURL and to access the web server on the VoIP Performance Manager managing node. These valuesare user-configured, as explained in the VMware Smart Assurance VoIP Availability ManagerConfiguration 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 theMonitoredBy relationship between the target object and the VoipPerformanceManager managingnode object.

To populate certain fields in the URL, the tool reads the target object attributes. For example, if thetarget object is a CallManager object, the tool reads the object’s ExternalName attribute to learn thename of the call manager, as known in the VoIP Performance Manager, and not the cluster name towhich it belongs. Then, the tool populates the appropriate fields in the URL with that value. Targetobjects and context filter criteria are described in the VMware Smart Assurance VoIP AvailabilityManager Configuration Guide.

VoIP client tool invocation

Assuming the VoIP client tools are configured and Global Console user profiles enable the use of clienttools, users invoke a client tool from a pop-up menu. To do so, right-click a target VoIP topology object ina Topology Browser Console attached to the Global Manager, then select Client Tools > <client toolname> in the pop-up menu.

For example, right-click a Cisco CallManager object in the Topology Browser and select Client Tools >Launch Location View to open a web browser and load the Locations drill-down display shown in VoIPPerformance Manager’s Locations drill-down display—example.


VMware, Inc. 33

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

Web browser operation and limitations

If you configure Internet Explorer as your browser of choice, as explained in the VMware SmartAssurance VoIP Availability Manager Configuration Guide, you can invoke one VoIP client tool afteranother without closing the browser instance opened by the previously invoked client tool. Eachinvocation of a VoIP client tool opens another web browser instance, which establishes a new sessionwith VoIP Performance Manager.


VMware, Inc. 34

If you configure Mozilla or Mozilla Firefox as your browser of choice, you must close the web browserinstance opened by the previously invoked client tool before invoking another client tool. Otherwise, youwill 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 toolinvocation, Mozilla or Mozilla Firefox attempts to establish a new session with VoIP Performance Managerusing 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 toopen 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. Then, use the navigation within theVoIP Performance Manager interface to view other pages, instead of changing the URL to view otherpages.


VMware, Inc. 35

Configuring VoIP PerformanceManager Integration 4This chapter includes the following topics:

n Configuration overview

n Automatically configuring the PMT-THRESHOLD process

n Enabling the VoIP Availability Manager built-in trap receiver

n Controlling the processing of VoIP Performance Manager traps

n Customizing performance polling and thresholds

n Troubleshooting

Configuration overview

Integrating VoIP Performance Manager with VoIP Availability Manager consists of the following steps:

1 Specifying information in the VoIP Availability Manager domain.conf file as described in“Automatically configuring the PMT-THRESHOLD process” on page 38 to identify the VoIPPerformance Manager’s IP address and GUI location.

As an alternative, the manual steps to configure the PMT-THRESHOLD process are provided inChapter 5 Manual Method: Configuring Integration

2 Enabling the VoIP Availability Manager built-in trap receiver to receive and process VoIP PerformanceManager traps that convey performance data.

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

4 Customizing performance polling and thresholds through a Polling and Thresholds Console attachedto VoIP Availability Manager.

Note For discussion purposes, the term PMT-THRESHOLD process refers to the VoIP thresholdprocess with the naming convention PMT<IPv4Address> where IPv4Address is the VoIPPerformance Manager’s IPv4 address.

Automatically configuring the PMT-THRESHOLD process

VMware, Inc. 36

VoIP Performance Manager provides a comprehensive SNMP Traps Out functionality for sending traps toother management systems, such as VoIP Availability Manager. The traps are defined in the IntegratedResearch Enterprise OID .1.3.6.1.4.1.6102. Using the SNMP Traps Out functionality, VMware has createddocuments that define the VoIP Performance Manager traps required by VoIP Availability Manager.

VMware provides an automated procedure to use the predefined trap definitions and to configure thePMT-THRESHOLD process.

For the automated procedure, you need to modify the domain.conf file as described in Modify the VoIPAvailability Manager domain.conf file.

Also, you need to satisfy these prerequisites:

n The VoIP Performance Manager must have the latest patch applied. For requirements regarding VoIPPerformance Manager, consult the VMware Smart Assurance VoIP Management Suite ReleaseNotes.

n The SNMP Agent for the VoIP Performance Manager host must be configured to accept SNMPpackets. The host on which VoIP Performance Manager is running must be discovered and managedby IP Availability Manager. The VMware Smart Assurance IP Management Suite Discovery Guideprovides information about the SNMP Agent.

After you modify the domain.conf file and restart VoIP Availability Manager, the following occurs:

n The proper SNMP destination and port are configured for the PMT-THRESHOLD process on VoIPPerformance Manager.

n The PMT-THRESHOLD process receives new parameters and is then restarted on VoIP PerformanceManager.

Modify the VoIP Availability Manager domain.conf file

To automatically configure the PMT-THRESHOLD process, you need to specify the IP address of theVoIP Performance Manager. To do so, perform these steps:

1 Go to the BASEDIR/smarts/conf/voip directory in the VoIP Availability Manager installation area andissue the following command to open the domain.conf file:

sm_edit conf/voip/domain.conf

2 Find this section in the file and specify the IPv4 address of the VoIP Performance Manager.

If necessary, specify a different directory where the VMware Smart Assurance VoIP PerformanceManager GUI resides.

# To enable auto-configuration of VoIP-PM, set the parameters below.

# The installation directory refers to the location on the VoIP PM

# installation. The required notation for this parameter is

# the cygwin style. The parameter ManagingServerIPAddress should be set

# with the value of the IPAddress of the managing node. This IP address

# will be used in performing a cygwin "scp" command from the VoIP AM


VMware, Inc. 37

# host to the managing node.

VOIP_PMDomain::VOIP-PM{

InstallationDirectory

= "/cygdrive/c/Program\ Files/PROGNOSIS\ IP\ Telephony\ Manager"

ManagingServerIPAddress = ""

Table 4-1. Automatic configuration parameters in the domain.conf file

Parameter Default value Description

InstallationDirectory Default:

"/cygdrive/c/Program\ Files/PROGNOSIS\ IP\Telephony\ Manager"

The directory on the VoIP Performance Managerinstallation where the VMware Smart AssuranceVoIP Performance Manager GUI resides.

The required notation for this parameter is thecygwin style.

One space is required between the backslashand the words Files, IP, Telephony, and Manager.

ManagingServerIPAddress Default: None The IPv4 address of the VoIP PerformanceManager. A value is required; there is no default.Only one IPv4 address for one VoIPPerformance Manager should be specified.

This parameter enables the automaticconfiguration of VoIP Performance Manager.

The IP address will be used in performing acygwin "scp" command from the VoIP AvailabilityManager host to the VoIP Performance Managermanaging node.

1 Save and close the file. The modified version of the domain.conf file is saved to the BASEDIR/smarts/local/conf/voip directory.

2 If VoIP Availability Manager was running before you edited the domain.conf file, stop and restart VoIPAvailability Manager service.

For UNIX, type these commands and press Enter:

/opt/InCharge/VoIP/smarts/bin/sm_service stop ic-voip-server

/opt/InCharge/VoIP/smarts/bin/sm_service start ic-voip-server

C:\InCharge\VoIP\smarts\bin\sm_service stop ic-voip-server

C:\InCharge\VoIP\smarts\bin\sm_service start ic-voip-server

After you modify the domain.conf file and restart VoIP Availability Manager, the PMT-THRESHOLDprocess on the VoIP Performance Manager is automatically configured and the PMT-THRESHOLDprocess is started.

Verify that the PMT-THRESHOLD process is running

To validate the values of the InstallationDirectory and ManagingServerIPAddress parameters, view thecorresponding attributes for the VOIP_PMDOMAIN class using the Topology Browser Console.


VMware, Inc. 38

In the VMware Smart Assurance VoIP Performance Manager GUI, verify that the PMT-THRESHOLDprocess is running in one of two ways:

n Examine the event history from the File menu.

n Check for the name of the running process under Thresholds.

Enabling the VoIP Availability Manager built-in trapreceiver

You enable the VoIP Availability Manager built-in trap receiver so that it can receive and process VoIPPerformance Manager traps. To do so, uncomment the

TrapPort = 9001 parameter line in the BASEDIR/smarts/conf/voip/voip.conf file in the VoIP AvailabilityManager installation area.

The VMware Smart Assurance VoIP Availability Manager Configuration Guide describes this parameterand provides instructions on modifying it.

Controlling the processing of VoIP Performance Managertraps

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

n PMTraps_Timeout

n SyncDelay

n TracePMTraps

The VMware Smart Assurance VoIP Availability Manager Configuration Guide describes theseparameters and provides instructions on modifying them.

Customizing performance polling and thresholds

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

The VMware Smart Assurance VoIP Availability Manager Configuration Guide describes the performancepolling and threshold groups, settings, and parameters, and provides instructions on modifying them.

Troubleshooting

If VoIP Availability Manager does not discover VoIP Performance Manager:

n Verify that VoIP Performance Manager is running.


VMware, Inc. 39

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

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

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

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

n SNMP Destination Host

n SNMP Trap Port

n Verify that the trap listening port for the VoIP Availability Manager built-in trap receiver is set to port9001.

n Verify that the SNMP Trap Port destination in VoIP Performance Manager and the built-in trapreceiver in VoIP Availability Manager are set to the same port.

n 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 theVoIP Availability Manager installation area and type the following command on one line:

dmctl -s <

VoIP AM instance name

> get

VOIP_Manager::VOIP-Manager::IsTrapReceiverRunning


VMware, Inc. 40

Manual Method: ConfiguringIntegration 5This chapter includes the following topics:

n Configuration overview

n Copying, configuring, and starting PMT-THRESHOLD

n Enabling the VoIP Availability Manager built-in trap receiver

n Controlling the processing of VoIP Performance Manager traps

n Customizing performance polling and thresholds

n Troubleshooting

Configuration overview

Manually integrating VoIP Performance Manager with VoIP Availability Manager consists of the followingsteps:

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

2 Enabling the VoIP Availability Manager built-in trap receiver to receive and process VoIP PerformanceManager traps that convey performance data.

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

4 Customizing performance polling and thresholds through a Polling and Thresholds Console attachedto VoIP Availability Manager.

Copying, configuring, and starting PMT-THRESHOLD

VoIP Performance Manager provides a comprehensive SNMP Traps Out functionality for sending traps toother management systems, such as VoIP Availability Manager. The traps are defined in the IntegratedResearch Enterprise OID .1.3.6.1.4.1.6102.

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

VMware, Inc. 41

You copy this file where the VMware Smart Assurance VoIP Performance Manager GUI resides, then usethe VoIP Performance Manager GUI to configure it and start the PMT-THRESHOLD process. ConfiguringPMT-THRESHOLD involves pointing to the host and trap listening port of the host running VoIPAvailability Manager.

To copy, configure, and start PMT-THRESHOLD:

1 In the VoIP Availability Manager installation area, copy the PMT-THRESHOLD.thr file located in theBASEDIR/smarts/conf/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\PROGNOSIS IP Telephony Manager

2 Start the VMware Smart Assurance VoIP Performance Manager GUI.

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

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

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

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

n In the SNMP Trap Port field, change 9001 (if need be) to the trap listening port configured forthe 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:

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

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

n Examine the event history from the File menu.

n Check for the name of the running process under Thresholds.


VMware, Inc. 42

Enabling the VoIP Availability Manager built-in trapreceiver

You enable the VoIP Availability Manager built-in trap receiver so that it can receive and process VoIPPerformance Manager traps. To do so, uncomment the

TrapPort = 9001 parameter line in the BASEDIR/smarts/conf/voip/voip.conf file in the VoIP AvailabilityManager installation area.

The VMware Smart Assurance VoIP Availability Manager Configuration Guide describes this parameterand provides instructions on modifying it.

Controlling the processing of VoIP Performance Managertraps

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

n PMTraps_Timeout

n SyncDelay

n TracePMTraps

The VMware Smart Assurance VoIP Availability Manager Configuration Guide describes theseparameters and provides instructions on modifying them.

Customizing performance polling and thresholds


VMware, Inc. 43

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

The VMware Smart Assurance VoIP Availability Manager Configuration Guide describes the performancepolling and threshold groups, settings, and parameters and provides instructions on modifying them.

Troubleshooting

If VoIP Availability Manager does not discover VoIP Performance Manager:

n Verify that VoIP Performance Manager is running.

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

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

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

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

n SNMP Destination Host

n SNMP Trap Port

n Verify that the trap listening port for the VoIP Availability Manager built-in trap receiver is set to port9001.

n Verify that the SNMP Trap Port destination in VoIP Performance Manager and the built-in trapreceiver in VoIP Availability Manager are set to the same port.

n 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 theVoIP Availability Manager installation area and type the following command on one line:

dmctl -s <

VoIP AM instance name

> get

VOIP_Manager::VOIP-Manager::IsTrapReceiverRunning


VMware, Inc. 44

VoIP Management Suite Overview and Integration Guide

Documents

Transcript of VoIP Management Suite Overview and Integration Guide