emc smarts voip availability manager · emc smarts voip availability manager version 3.0...

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

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

EMC® Smarts®

VoIP Availability ManagerVersion 3.0

Configuration GuideP/N 300-006-924

REV A01

EMC Smarts VoIP Availability Manager Version 3.0 Configuration Guide2

Copyright © 2007–2008 EMC Corporation. All rights reserved.

Published May, 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 Availability Manager Version 3.0 Configuration Guide 3

Preface

Chapter 1 Introduction Important terminology .......................................................................................... 18

What do system and device mean?................................................................ 18What does modeled topology mean? ............................................................ 18

Architectural and functional overview................................................................ 19IP Availability Manager................................................................................... 20VoIP Availability Manager ............................................................................. 20Global Manager ................................................................................................ 21Adapter Platform.............................................................................................. 22Global Console .................................................................................................. 22EMC Smarts Broker.......................................................................................... 22

Configuration roadmap ......................................................................................... 23VoIP Availability Manager configuration tasks........................................... 23IP Availability Manager configuration tasks................................................ 23Global Manager configuration tasks.............................................................. 24Adapter Platform configuration tasks........................................................... 24

What’s next after configuration? .......................................................................... 24

Chapter 2 Setting Configuration Parameters User configuration parameters ............................................................................. 26 Methods for modifying user configuration parameters ................................... 27

Editing configuration files to modify configuration parameters .............. 27Issuing the dmctl command to modify configuration parameters ........... 27

Description of domain.conf................................................................................... 29 Description of voip.conf ........................................................................................ 30 Adding IP Availability Manager as a topology and status source .................. 34 Disabling automatic synchronization .................................................................. 35 Enabling trap reception.......................................................................................... 36 Configuring security .............................................................................................. 37

Chapter 3 Opening the Global Console Global Console overview....................................................................................... 40 User accounts and passwords............................................................................... 40 Procedure for opening the Global Console......................................................... 40 Procedure for opening the Global Manager Administration Console............ 42

Contents


Contents

Procedure for opening the Domain Manager Administration Console.......... 43 Procedure for opening the Polling and Thresholds Console ............................ 43

Chapter 4 Configuring IP Availability Manager Configuration overview ......................................................................................... 46 Topology object import from IP Availability Manager...................................... 46 About the VoIP topology collection set................................................................ 47

Content of VoIP topology collection set ........................................................ 47ICIM modeling of devices in VoIP topology collection set ........................ 48Device-matching filters for the VoIP topology collection set ..................... 48

Customizing VoIP-related device-matching filters ............................................ 49

Chapter 5 Configuring the Global Manager Configuration overview ......................................................................................... 52 About the Global Manager .................................................................................... 52 IC Domain Configuration objects ......................................................................... 56

IC Domain Configuration creation wizards.................................................. 56IC Domain Configuration server reconfiguration........................................ 57

Specifying the underlying domains ..................................................................... 59Specifying the underlying domains for configuration scenario 1 ............. 59Specifying the underlying domains for configuration scenario 2 ............. 62

Loading the XML configuration file for VoIP-AM ............................................. 67 Configuring client tools for VoIP Availability Manager.................................... 69

Configuring client tools procedure ................................................................ 69Java requirements and web browser support............................................... 72Sample client tools ............................................................................................ 72

Chapter 6 Configuring the SNMP Trap Integration Configuration overview ......................................................................................... 76 SNMP trap integration components..................................................................... 77

Built-in trap receiver......................................................................................... 77VoIP Notification Trap Adapter ..................................................................... 78SNMP Trap Adapter......................................................................................... 78Adapter Platform .............................................................................................. 79

Trap adapter configuration file: trapd.conf ......................................................... 80 Configuring the SNMP trap integration components ....................................... 84

Configure the trap exploder ............................................................................ 84Configure the built-in trap receivers.............................................................. 90Configure the VoIP Notification Trap Adapter............................................ 90Configure the trap receiver.............................................................................. 91Configure the Adapter Platform..................................................................... 92

Starting the SNMP trap integration components ............................................... 93Start the trap exploder...................................................................................... 93Start the VoIP Notification Trap Adapter ..................................................... 95

Chapter 7 Using the Polling and Thresholds Console Opening the Polling and Thresholds Console .................................................... 98

Layout of the Polling and Thresholds Console ............................................ 99Polling and Thresholds Console toolbar buttons......................................... 99

Understanding groups and settings ................................................................... 100 Working with groups and settings ..................................................................... 101

How managed objects are assigned to groups ........................................... 101


Contents

Modifying the properties of a group ........................................................... 101Adding or removing settings........................................................................ 101Modifying the parameters of a setting ........................................................ 102Modifying the priority of groups ................................................................. 102Editing matching criteria............................................................................... 103Creating new groups...................................................................................... 104

Chapter 8 Configuring Polling Groups Viewing the Polling tab........................................................................................ 106 Understanding polling groups and settings..................................................... 107

Modifying polling groups ............................................................................. 107 Default polling groups and settings................................................................... 108

Default polling categories and groups ........................................................ 108Default polling settings.................................................................................. 111

Chapter 9 Configuring Polled Data Thresholds Viewing the Thresholds tab................................................................................. 116 Understanding threshold groups and settings................................................. 117

Modifying threshold groups......................................................................... 117 Default threshold groups and settings .............................................................. 118

Default threshold categories and groups.................................................... 118Default threshold settings ............................................................................. 122

Chapter 10 Creating Credential Sets Viewing the Device Access tab ........................................................................... 130 Understanding device access groups and settings .......................................... 131

Modifying and creating device access groups ........................................... 131 Default device access groups and settings........................................................ 132

Default device access groups ........................................................................ 132Default device access settings....................................................................... 132

Using the Device Access tab................................................................................ 134Creating a credential set ................................................................................ 134Overview of creating a device access group............................................... 134

Appendix A Wildcard Patterns Types of wildcard patterns .................................................................................. 138

Appendix B Polling for Analysis Polling overview................................................................................................... 142 SNMP poller .......................................................................................................... 142

Just-in-time polling......................................................................................... 142Request-consolidation polling ...................................................................... 142

Index


Contents


Title Page

1 VoIP Availability Manager architecture ............................................................................ 192 Topology Browser Console—example............................................................................... 413 Notification Log Console—example .................................................................................. 424 Domain Manager Administration Console—example.................................................... 435 Importing topology objects from IP Availability Manager............................................. 466 Topology objects imported from IP Availability Manager ............................................. 477 Global Manager Administration Console interaction with the Global Manager ........ 538 Domain configuration objects and their relationships .................................................... 549 Default domain configurations ........................................................................................... 5510 Global Manager Administration Console—example ...................................................... 5611 How reconfiguring the Global Manager works ............................................................... 5812 The displays before and after completing the configuration for scenario 1................. 5913 The displays before and after completing the configuration for scenario 2................. 6214 Using the Domain Creation Wizard to create the EAST-VoIP-AM domain ................ 6415 Using the Domain Creation Wizard to create the EAST-AM1 domain ........................ 6516 Access to Import XML Configuration server tools .......................................................... 6717 Recommended trap integration for a VoIP Availability Manager deployment .......... 7618 Configuration directory for an SNMP Trap Adapter configured as a trap exploder . 8019 Mapping of trap exploder configuration steps to configured forwarded trap paths . 8520 Polling and Thresholds Console—example ...................................................................... 9821 Relating managed objects to groups and settings .......................................................... 10022 Polling tab for VoIP Availability Manager...................................................................... 10623 Thresholds tab for VoIP Availability Manager............................................................... 11624 Device Access tab for VoIP Availability Manager ......................................................... 130

Figures


Figures


Title Page

1 User configuration files for VoIP Availability Manager ................................................. 262 Object in the domain.conf file ............................................................................................. 293 Parameters in the voip.conf file .......................................................................................... 304 VoIP client tools..................................................................................................................... 725 SNMP Trap Adapter translation of incoming traps to forwarded traps ...................... 796 Detailed descriptions of configuration parameters in the trapd.conf file..................... 827 Polling and Thresholds Console toolbar buttons ............................................................. 998 Default VoIP Application groups ..................................................................................... 1089 Default VoIP Card Services groups.................................................................................. 10910 Default VoIP Clusters ......................................................................................................... 10911 Default VoIP Network Service groups............................................................................. 11012 Default VoIP Process groups............................................................................................. 11013 Default VoIP Redundancy Groups................................................................................... 11114 Parameters for the VoIP Polling - SNMP setting............................................................ 11115 Parameters for the VoIP Performance Polling - External setting ................................. 11216 Parameters for the VoIP Polling - External setting......................................................... 11217 Parameters for the Redundancy Group - Analysis setting ........................................... 11318 Default Call Manager groups ............................................................................................ 11919 Default Call Manager Redundancy groups .................................................................... 12020 Default DS1 Service groups ............................................................................................... 12021 Default Gateway Service groups ...................................................................................... 12022 Default H.323 Gate Keeper groups................................................................................... 12123 Default H.323 Service groups............................................................................................ 12124 Default Signaling Service group ....................................................................................... 12125 Default VoIP Clusters group ............................................................................................. 12226 Parameters for the VoIP Nortel Backup Monitoring Options setting ......................... 12327 Parameters for the VoIP Nortel TLAN Monitoring Options setting ........................... 12328 Parameters for the VoIP Avaya Backup Monitoring Options setting ......................... 12429 Parameters for the Converged Call Manager Performance threshold setting ........... 12430 Parameters for the Call Manager Performance Thresholds setting............................. 12431 Parameters for the Conferencing Resource Performance Thresholds setting............ 12532 Parameters for the Media Resource Performance Thresholds setting ........................ 12533 Parameters for the DS1 Service Performance Thresholds setting................................ 12634 Parameters for the Gateway Service Performance Thresholds setting ....................... 12635 Parameters for the H323 Gate Keeper Performance Thresholds setting..................... 12636 Parameters for the H323 Service Performance Thresholds setting.............................. 12737 Parameters for the Redundancy Group Monitoring parameters setting.................... 12738 Parameters for the VoIP Cluster Performance Thresholds setting .............................. 12839 Default device access groups............................................................................................. 13240 Default values for the Nortel settings .............................................................................. 133

Tables


Tables

41 Default values for the VoIP PM Web Interface Access setting ..................................... 13342 Basic wildcard patterns....................................................................................................... 13843 Compound wildcard patterns ........................................................................................... 139


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 part of the EMC Smarts VoIP Management Suite documentation set, and is intended for use by administrators and integrators who need to configure and maintain EMC Smarts VoIP Availability Manager. Topics include editing control and configuration files, and configuring the EMC Smarts IP Availability Manager and the EMC Smarts Service Assurance Manager (Global Manager) to work with VoIP Availability Manager.

Readers of this document must have administrative privileges on the local host to perform the configurations presented in this document.

In addition, the following software must be installed:

◆ EMC Smarts VoIP Availability Manager (VoIP Availability Manager), including one or more enablement packs and the optional EMC Smarts VoIP Integration Pack for VoIP Performance Manager

◆ EMC Smarts IP Availability Manager (IP Availability Manager)

◆ EMC Smarts Service Assurance Manager (Global Manager)

◆ EMC Smarts Global Console

The EMC Smarts VoIP Availability Manager Installation Guide, the EMC Smarts IP Management Suite Installation Guide, and the EMC Smarts Service Assurance Management Suite Installation Guide provide information about installing these products.

The VoIP Performance Manager Integration Pack enables you to integrate the following installed products with VoIP Availability Manager:

◆ EMC Smarts VoIP Performance Manager for Cisco v4

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

The EMC Smarts VoIP Performance Manager for Cisco v4 Installation Guide and EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Installation Guide provide information about installing these products.


Preface

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

◆ 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

http://Powerlink.EMC.com


Preface

◆ 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

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


Preface

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.

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.

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

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.

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 17

1

This chapter provides an architectural and functional overview of EMC SmartsVoIP Availability Manager and highlights the configuration tasks needed to set up and maintain a VoIP Availability Manager deployment. It consists of the following sections:

◆ Important terminology................................................................................................. 18◆ Architectural and functional overview ...................................................................... 19◆ Configuration roadmap................................................................................................ 23◆ What’s next after configuration?................................................................................. 24

Introduction


Introduction

Important terminologyEMC® Smarts® VoIP Availability Manager is an EMC Smarts Domain Manager, where a Domain Manager is a service-assurance application associated with a particular type of information-technology domain (networks, systems, applications, application services). For VoIP Availability Manager, the domain is Voice over IP (VoIP) application services transport. Each Domain Manager is autonomous in the sense that it maintains its own data models, repository, and problem signatures, and monitors and analyzes the discovered objects in its own domain.

What do system and device mean?The term system, as used in this document, is a generic term representing a computer-based network entity, such as a host, a router, or a switch. The term device, as used in this document, has essentially the same meaning as system except that device also conveys the sense of a specific model, such as a specific model of host, router, or switch.

What does modeled topology mean?VoIP Availability Manager uses EMC Smarts ICIM class models to create within its repository instances of the managed network systems (hosts, routers, switches) and the managed VoIP application services (voice mail, teleconferencing), their relationships, and their dependencies. The modeled topology mirrors the real topology in the managed network.

Architectural and functional overview 19

Introduction

Architectural and functional overviewVoIP Availability Manager, working with EMC Smarts IP Availability Manager (IP Availability Manager) and the EMC Smarts Service Assurance Manager (Global Manager), manages VoIP networks and VoIP application services. Figure 1 on page 19 shows how VoIP Availability Manager interoperates with these components.

Figure 1 VoIP Availability Manager architecture

SNMP discovery& polling

Built-intrap

receiver

Cisco VoIPtopology &

status updates

VoIP PMtopology &

status updates


VoIP topology &status updates

Nortel VoIPtopology &

status updates

SNMP & CLIdiscovery

Global Manager

VoIP analysis traps

VoIP Availability Manager(Same server process)

VoIP topology,Root-cause problems,

& impacts

Topology & notifications VoIP & networkmaps

Trap notifications

Network topology,Root-cause problems,

& impacts

Global Console

* EnablementPack

SNMP traps

IP Availability Manager


Adapter Platform

Processed traps

SNMPTrap Adapter

(exploder)

VoIPNotification

Trap Adapter

VoIPinformational

traps

Networktraps

Topology

Cisco EP*

Discovery& monitoring

Avaya EP*


Avaya VoIPtopology &

status updates

VoIP Core

SNMPTrap Adapter

(receiver)

Processed traps

Nortel EP*


VoIP PM EP*

Monitoring

Non-VoIPinformational

traps

Topology

Data model repository

Analysis engine

VoIP devices

IP network

VoIP PerformanceManager traps


Introduction


IP Availability Manager diagnoses connectivity failures in multi-vendor, switched, and routed networks by discovering and monitoring Layer 2 (data-link) and Layer 3 (network) systems. Switches are examples of Layer 2 systems, and routers are examples of Layer 3 systems.

When included in a VoIP Availability Manager deployment, IP Availability Manager:

◆ Discovers and monitors via SNMP the underlying transport domain in the VoIP network.

◆ Analyzes the network connectivity to identify the root-cause problems and impacts of connectivity failures.

◆ Exports network topology, problem, and impact information to the Global Manager.

◆ 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 IP Availability Manager instance may consist of just an IP Availability Manager process, or may consist of an IP Availability Manager and an EMC Smarts IP Performance Manager (IP Performance Manager) or EMC Smarts IP Server Performance Manager (IP Server Performance Manager) running as a single process.

VoIP Availability Manager

VoIP Availability Manager relies on the topology, topology updates, and topology status updates received from IP Availability Manager to discover and monitor VoIP infrastructure devices, VoIP applications, and VoIP application services.

VoIP Availability Manager consists of up to five major components:

◆ VoIP Core

This component runs all of the installed vendor-specific enablement packs in a single-server process. It collects topology and status-update information from IP Availability Manager and the enablement packs to build and update a topology data model of the managed VoIP network; it uses the data model to perform root-cause and impact analysis.

◆ EMC Smarts VoIP Integration Pack for VoIP Performance Manager (VoIP Performance Manager Integration Pack)

This optional component responsible for discovering and monitoring VoIP Performance Manager topology and setting topology status in the topology data model. The VoIP Performance Manager Integration Pack enables you to integrate the following installed products with VoIP Availability Manager:

• EMC Smarts VoIP Performance Manager for Cisco v4

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

Architectural and functional overview 21

Introduction

The VoIP Performance Manager Integration Pack uses traps generated by the VoIP Performance Manager and sends performance metrics in the form of traps to VoIP Availability Manager. The traps are used by VoIP Availability Manager to update performance-type attributes in the classes of the VoIP Availability Manager data model.

◆ EMC Smarts Enablement Pack for Avaya (Avaya Enablement Pack)

An optional component responsible for discovering and monitoring Avaya VoIP topology and setting topology status in the topology data model. The Avaya Enablement Pack uses SNMP Management Information Base (MIB) discovery to discover the topology, and uses SNMP polling results and received SNMP traps to update the status of the discovered topology.

◆ EMC Smarts Enablement Pack for Cisco (Cisco Enablement Pack)

An optional component responsible for discovering and monitoring Cisco VoIP topology and setting topology status in the topology data model. The Cisco Enablement Pack uses SNMP MIB discovery to discover the topology, and uses SNMP polling results to update the status of the discovered topology.

◆ EMC Smarts Enablement Pack for Nortel (Nortel Enablement Pack)

An optional component responsible for discovering and monitoring Nortel VoIP topology and setting topology status in the topology data model. The Nortel Enablement Pack uses SNMP and Command Line Interface (CLI) to discover the topology, and uses received SNMP traps to update the status of the discovered topology.

Note: During a VoIP Availability Manager installation, a user must install at least one enablement pack and the optional VoIP Performance Manager Integration Pack. The VoIP Performance Manager Integration Pack is needed when the VoIP Performance Manager is installed.

Upon importing the initial VoIP-enabled device topology from IP Availability Manager, VoIP Availability Manager performs its own SNMP and CLI discovery to query the managed devices for VoIP topology information. Upon building its VoIP topology data model, VoIP Availability Manager exports the topology to the Global Manager.

VoIP Availability Manager monitors the status of the discovered VoIP topology objects and subscribes to certain network topology object status (attributes) from IP Availability Manager. It analyzes the received status to identify VoIP device and application availability problems and impacts, and exports the results of its analysis to the Global Manager.

Global ManagerThe 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.


Introduction

Adapter Platform

The EMC Smarts Service Assurance Manager Adapter Platform (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 Console

The 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 graphical user interface for VoIP Availability Manager but not for VoIP Performance Manager or VoIP Performance Reporter. (VoIP Performance Manager and VoIP Performance Reporter have their own graphical user interfaces.) The Global Console can be configured to open a web-browser Java-based graphical user interface to view VoIP Performance Manager data.

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

Configuration roadmap 23

Introduction

Configuration roadmapBefore you perform the configuration tasks that are outlined in this section, review the deployment considerations described in the EMC Smarts VoIP Management Suite Overview and Integration Guide and the compatibility requirements described in the EMC Smarts VoIP Management Suite Release Notes.

The following sections highlight the configuration tasks associated with the setup of the application components in a VoIP Availability Manager deployment. These tasks involve configuring the VoIP Availability Manager, IP Availability Manager, Global Manager, and Adapter Platform applications that are part of the deployment.

Some configuration tasks are performed before the applications are started, such as the editing of configuration files, and some are performed through the Global Console when the applications are up and running.

VoIP Availability Manager configuration tasksConfiguring VoIP Availability Manager consists of the following tasks:

◆ Add IP Availability Manager as a source from which VoIP Availability Manager imports topology and status updates (mandatory).

◆ Disable automatic topology synchronization with IP Availability Manager (optional).

◆ Enable SNMP trap reception so that traps issued by Avaya or Nortel devices can be received and processed by VoIP Availability Manager (mandatory if managed environment contains Avaya or Nortel devices).

◆ Configure SNMP trap integration to distribute Avaya or Nortel traps to VoIP Availability Manager (mandatory if managed environment contains Avaya or Nortel devices).

◆ Specify device access credentials using the Polling and Thresholds Console for client tools and Nortel devices (mandatory for client tools and if the managed environment contains Nortel devices).

◆ Customize SNMP polling (optional).

Chapter 2, “Setting Configuration Parameters,” Chapter 6, “Configuring the SNMP Trap Integration,” Chapter 8, “Configuring Polling Groups,” and Chapter 10, “Creating Credential Sets,” provide the procedures for performing these tasks.

IP Availability Manager configuration tasksIn addition to performing the configuration and administration tasks common to all IP Availability Managers, you perform the following additional tasks to set up IP Availability Manager in a VoIP Availability Manager deployment:

◆ Customize VoIP-related device-matching filters (optional).

◆ Exclude Avaya and Nortel floating IP addresses from the discovered topology (mandatory if managed environment contains Avaya or Nortel devices).

◆ Configure SNMP trap integration to distribute network traps to IP Availability Manager (mandatory).

Chapter 4, “Configuring IP Availability Manager,” and Chapter 6, “Configuring the SNMP Trap Integration,” provide the procedures for performing these tasks.


Introduction

Procedures for configuring all aspects of IP Availability Manager are provided in the EMC Smarts IP Management Suite Configuration Guide.

Global Manager configuration tasksIn addition to performing the configuration and administration tasks common to all Global Managers, you perform the following additional tasks to set up the Global Manager in a VoIP Availability Manager deployment:

◆ Set up a communication link between the Global Manager and the VoIP Availability Manager (mandatory).

◆ Set up a communication link between the Global Manager and the IP Availability Managers (mandatory).

◆ Set up a communication link between the Global Manager and the Adapter Platform (mandatory).

◆ Configure client tools to access VoIP Performance Manager data (optional).

Chapter 5, “Configuring the Global Manager,” provides the procedures for performing these tasks. Procedures for configuring all aspects of the Global Manager are provided in the EMC Smarts Service Assurance Manager Configuration Guide.

Adapter Platform configuration tasks Configure the Adapter Platform to forward traps to the Global Manager for display as EMC Smarts notifications in the Global Console. Chapter 6, “Configuring the SNMP Trap Integration,” provides the procedure for configuring the Adapter Platform to receive, convert, and forward traps to the Global Manager. Procedures for configuring all aspects of the Adapter Platform and the SNMP Trap Adapter are provided in the EMC Smarts Service Assurance Manager Adapter Platform User Guide.

What’s next after configuration?Upon configuring your VoIP Availability Manager deployment, you are ready to begin the discovery. The EMC Smarts VoIP Availability Manager Discovery Guide describes how to prepare for and initiate VoIP Availability Manager discovery.

Setting Configuration Parameters 25

2

This chapter identifies VoIP Availability Manager configuration parameters relevant to discovery, describes their settings, and provides instructions for changing their settings. It consists of the following sections:

◆ User configuration parameters ................................................................................... 26◆ Methods for modifying user configuration parameters.......................................... 27◆ Description of domain.conf ......................................................................................... 29◆ Description of voip.conf ............................................................................................... 30◆ Adding IP Availability Manager as a topology and status source......................... 34◆ Disabling automatic synchronization ........................................................................ 35◆ Enabling trap reception ................................................................................................ 36◆ Configuring security..................................................................................................... 37

Setting ConfigurationParameters


Setting Configuration Parameters

User configuration parametersA major part of configuring VoIP Availability Manager involves the setting of user configuration parameters in the files identified in Table 1 on page 26.

The BASEDIR/smarts/conf/voip directory contains the bootstrap and the configuration files for VoIP Availability Manager; the --config=voip option in a VoIP Availability Manager startup command points to the bootstrap and configuration files in the voip directory. The bootstrap and configuration files for a VoIP Availability Manager set up the environment for the application.

Table 1 User configuration files for VoIP Availability Manager

Directory under BASEDIR Filename Description

VoIP Core

smarts/conf/voip domain.conf(Described in “Description of domain.conf” on page 29.)

File in which you specify one or more IP Availability Managers as topology sources for VoIP Availability Manager.The parameters in the domain.conf file are used to set the Type and Name attributes for one or more Availability Manager “InChargeDomain” objects.

voip.conf(Described in “Description of voip.conf” on page 30.)

File in which you customize discovery and other aspects of VoIP Availability Manager behavior.The parameters in the voip.conf file are used to set attributes for the “VOIP-Manager” object, which is the object that manages the VoIP Availability Manager environment. The parameters and their values become attributes and values for the VOIP-Manager object.

VoIP Performance Manager Integration Pack

smarts/conf/voip voip.conf(Described in “Description of voip.conf” on page 30.)

File in which you customize trap and other aspects of VoIP Performance Manager behavior.

Avaya Enablement Pack

smarts/conf/voip avaya.conf*(Described in the EMC Smarts Enablement Pack for Avaya User Guide.)

File in which you modify Avaya discovery probing.

Cisco Enablement Pack

smarts/conf/voip cisco.conf*(Described in the EMC Smarts Enablement Pack for Cisco User Guide.)

File in which you modify Cisco discovery probing.

smarts/conf/voip/cisco phone-device-pool.conf*(Described in the EMC Smarts Enablement Pack for Cisco User Guide.)

File in which you specify the IP phone device pools assigned to the different Cisco CallManager groups (redundancy groups) in the managed VoIP network.

Nortel Enablement Pack

smarts/conf/voip nortel.conf*(Described in the EMC Smarts Enablement Pack for Nortel User Guide.)

File in which you modify Nortel discovery probing.

* This configuration file is present if the associated enablement pack was installed during the VoIP Availability Manager installation.

Methods for modifying user configuration parameters 27


Methods for modifying user configuration parametersThere are two methods for modifying user configuration parameters:

◆ Edit the user configuration files and modify configuration parameters.

◆ Issue the dmctl command to temporarily modify configuration parameters when VoIP Availability Manager is running.

Some configuration changes can only be made by modifying the parameter settings in the configuration files and then restarting VoIP Availability Manager. Every time that VoIP Availability Manager starts, it sets its configurations in accordance to the settings in the user (and other) configuration files.

Editing configuration files to modify configuration parameters

EMC Smarts provides the sm_edit utility to ensure that modified files are always saved to the appropriate local area and that original copies of the files remain unchanged.

To invoke the sm_edit utility from the command line, go to the BASEDIR/smarts/bin directory and specify the path and the name of the file (relative to the BASEDIR/smarts directory) that you want to edit. For example,

sm_edit conf/voip/voip.conf

opens a local copy of the voip.conf file in BASEDIR/smarts/local/conf/voip (or an original copy of the voip.conf file in BASEDIR/smarts/conf/voip if no local copy exists) in a text editor and saves the modified version of the file to the BASEDIR/smarts/local/conf/voip directory.

You can use the sm_edit utility to edit any text file (configuration file, rule set file, tool script, template) in the BASEDIR/smarts (or BASEDIR/smarts/local) directory. Because sm_edit assumes a starting point of BASEDIR/smarts, you specify the path and the name of the text file beginning with the directory name (conf, rules, script) under the BASEDIR/smarts directory.

The EMC Smarts System Administration Guide provides additional information about the sm_edit utility.

Note: Original versions of files may be changed or updated as part of an EMC Smarts software upgrade. However, files located in the BASEDIR/smarts/local directory are retained during an upgrade.

Issuing the dmctl command to modify configuration parameters

You can use the following dmctl command to change the value of any basic-type attribute (string, boolean, integer, float, and so on) defined in an ICIM class:

dmctl -s <Domain Manager instance name> [-b <broker>] put <class::instance::attribute> <value>

Note: The option -b <broker> is used to specify the host and port (<host:port>) location of the Broker if the Domain Manager instance is attached to a Broker other than "localhost:426" and the environment variable SM_BROKER is not set to that Broker.

Upon issuing a dmctl command, you will be prompted for a username and password. Respond with your administration account (for example, admin and changeme).



Using the dmctl command to modify a parameter setting is temporary in the following sense: When the Domain Manager is restarted, it reads the original parameter value in the configuration file. To make the change permanent, use the sm_edit utility to change the parameter setting in the configuration file.

As an example of using the dmctl command to modify a parameter setting, from the BASEDIR/smarts/bin directory in a VoIP Availability Manager installation area, you can issue the following dmctl command to temporarily overwrite the TraceEvents parameter setting specified in the voip.conf file:

dmctl -s VoIP-AM put VOIP_Manager::VOIP-Manager::TraceEvents TRUE

The parameters in the voip.conf file are defined as attributes of the object named VOIP-Manager. VOIP-Manager is an instance of the VOIP_Manager class.

Using the dmctl command will overwrite most parameter settings in the voip.conf file but not all. Any change to the following voip.conf parameters requires making the change in the voip.conf file and restarting VoIP Availability Manager.

◆ TrapPort

◆ AutoDiscover

The same can be said for making a change to an InChargeDomain object and its parameters in the domain.conf file:

InChargeDomain::InChargeDomain_INCHARGE-AM{ Type = “AM” DomainName = “INCHARGE-AM”}

For parameter settings that cannot be overwritten using the dmctl command, use the sm_edit utility to modify the settings in the appropriate configuration file and then restart VoIP Availability Manager.

Description of domain.conf 29


Description of domain.confThe domain.conf file contains an “InChargeDomain” object that you edit to specify an IP Availability Manager as a topology source for VoIP Availability Manager. If your deployment contains more than one IP Availability Manager source, you make copies of the object and edit the copies to specify the additional sources.

The Type and Name parameters for an IP Availability Manager InChargeDomain object in the domain.conf file are a subset of attributes defined for the object.

Table 2 on page 29 identifies the InChargeDomain object named InChargeDomain_INCHARGE-AM in the domain.conf file. The object, its parameters, and its parameter values are all case-sensitive.

The Type parameter can be AM or AM-PM, where AM represents an IP Availability Manager instance consisting of just an IP Availability Manager process, and AM-PM represents an IP Availability Manager and an IP Performance Manager or IP Server Performance Manager running as a single process.

Table 2 Object in the domain.conf file

Object Value Description


As shown The default IP Availability Manager from which VoIP Availability Manager in this deployment is to import topology.“Adding IP Availability Manager as a topology and status source” on page 34 clarifies the use of this option and its attributes.



Description of voip.confThe voip.conf file contains configuration parameters that you edit to customize discovery and other aspects of VoIP Availability Manager behavior. The parameters are a subset of attributes defined for the “VoIP-Manager” object that will run in the VoIP Availability Manager environment.

You use the voip.conf file to change discovery parameters, instrumentation parameters, and tracing and troubleshooting parameters. For example, you can change parameters in this file to accomplish tasks such as disabling automatic topology synchronization and enabling SNMP trap reception.

All of the parameters in the voip.conf file are commented-out (preceded with the # character). When changing the default value for a commented-out parameter, ensure that you also remove its # character.

Table 3 on page 30 describes the parameters in the voip.conf file. The parameters and their values are case-sensitive.

Table 3 Parameters in the voip.conf file (page 1 of 4)

Parameter Value Description

SNMP Discovery Parameters

SNMP_timeout Default: 1000 milliseconds Timeout for an SNMP poll during Phase 3 of discovery. Phase 3 of discovery is described in the EMC Smarts VoIP Availability Manager Discovery Guide.The SNMP_timeout parameter is comparable to the “defaultTimeout” parameter in the discovery.conf file of an IP Management Suite installation. The EMC Smarts IP Management Suite Discovery Guide provides recommendations about changing the defaultTimeout parameter value.

Note: SNMP_timeout = 0 defaults to 1000 milliseconds.

SNMP_retries Default: 5 retries Number of SNMP retry polls to use during Phase 3 of discovery. Phase 3 of discovery is described in the EMC Smarts VoIP Availability Manager Discovery Guide.The SNMP_retries parameter is comparable to the “defaultRetries” parameter in the discovery.conf file of an IP Management Suite installation. The EMC Smarts IP Management Suite Discovery Guide provides recommendations about changing the defaultRetries parameter value.

Note: SNMP_retries = 0 defaults to 5 retries.

NumberOfProbeThreads Default: 10 threads Number of discovery threads used by the discovery process. If you are experiencing slow response SNMP discovery polling and your current CPU usage is relatively low (say 5 to 10 percent) consider increasing the number of discovery threads to improve your discovery performance. Increasing this number is one of the best and simplest methods for improving discovery.Increasing threads to 20, 30 or even 50 discovery threads is acceptable, but keep in mind that more threads may require additional or more capable CPUs and that the requirements during discovery will increase. Increase threads conservatively while monitoring SNMP Processing Statistics changes.

Note: NumberOfProbeThreads = 0 defaults to 10 threads.

Description of voip.conf 31


PIDPollingInterval 0 to 3600Default: 240

Number of seconds to wait between attempts to probe the Host resource MIB to detect when an unresponsive process has been restarted.PIDPollingInterval = 0 disables polling.

ProhibitCLI TRUE,FALSEDefault: FALSE

Determines whether CLI discovery is enabled or disabled:• A value of TRUE indicates that CLI discovery is disabled.• A value of FALSE indicates that CLI discovery is enabled.

Note: CLI discovery is used to discover Nortel devices.

Instrumentation parameters

TrapPort 0, 9001, 2049 to 65534Default: 0

Enables the VoIP Availability Manager built-in trap receiver and specifies the port used by the trap receiver to receive traps:• TrapPort = 0 disables the built-in trap receiver.• TrapPort = 9001 or a value in the range 2049-to-65534

(inclusive) enables the built-in trap receiver and sets the trap port to the value specified for the parameter.

“Enabling trap reception” on page 36 clarifies the use of this parameter.

Note: The Avaya Enablement Pack uses the received Avaya-related traps to update the status of the attributes of Avaya topology instrumentation objects in the VoIP Availability Manager repository.

Note: Similarly, the Nortel Enablement Pack uses the received Nortel-related traps to update the status of the attributes of Nortel topology instrumentation objects in the VoIP Availability Manager repository.

Tracing and troubleshooting parameters

TraceSNMPInstrumentation TRUE,FALSEDefault: FALSE

Determines whether SNMP poll tracing is enabled or disabled:• A value of TRUE indicates that SNMP poll tracing is enabled.• A value of FALSE indicates that SNMP poll tracing is disabled.

TraceDiscovery TRUE,FALSEDefault: FALSE

Determines whether discovery probe tracing is enabled or disabled:• A value of TRUE indicates that discovery probe tracing is

enabled.• A value of FALSE indicates that discovery probe tracing is

disabled.

Note: When TRUE, the discovery probes and the post processing software print information about the discovery of topology.





TraceEvents TRUE,FALSEDefault: FALSE

Determines whether internal event subscriber tracing is enabled or disabled:• A value of TRUE indicates that internal event subscriber tracing

is enabled.• A value of FALSE indicates that internal event subscriber

tracing is disabled.

Note: When TRUE, each “event” activated by VoIP Availability Manager is printed. In addition, if the Nortel Enablement Pack is installed, a CLI log file is created for each CLI-discovered Nortel Signaling Server.

TraceSetting TRUE,FALSEDefault: FALSE

Determines whether settings tracing is enabled or disabled:• A value of TRUE indicates that settings tracing is enabled.• A value of FALSE indicates that settings tracing is disabled.

Note: When TRUE, the processing that occurs during reconfiguration is printed. Reconfiguration is described in “Polling and Thresholds Console toolbar buttons” on page 99.

TraceTraps TRUE,FALSEDefault: FALSE

Determines whether trap receiver tracing is enabled or disabled:• A value of TRUE indicates that trap receiver tracing is enabled.• A value of FALSE indicates that trap receiver tracing is

disabled.

IsDemo TRUE,FALSEDefault: FALSE

Controls whether external (stored) instrumentation is instantiated for demo and test scenarios:• A value of TRUE indicates that external instrumentation is

instantiated.• A value of FALSE indicates that external instrumentation is not

instantiated.

TracePIDMonitoring TRUE,FALSEDefault: FALSE

Determines whether monitoring tracing of the Host Resource MIB for restarted processes is enabled or disabled:• A value of TRUE indicates that tracing is enabled.• A value of FALSE indicates that tracing is disabled.

TracePMTraps TRUE,FALSEDefault: FALSE

Determines whether the tracing occurs of VoIP Performance Manager trap receiver processing.• A value of TRUE indicates that tracing is enabled.• A value of FALSE indicates that tracing is disabled.

IsPMTrapReceiverEnabled TRUE,FALSEDefault: TRUE

Determines whether the processing of traps from VoIP Performance Manager occurs. The traps from VoIP Performance Manager are used to enrich VoIP Availability Manager topology and to monitor select attributes.• A value of TRUE indicates that processing is enabled.• A value of FALSE indicates that processing is disabled.

SyncDelay 240 to 3600Default: 300

The number of seconds that the VoIP Performance Manager Trap Processor will wait after the initial VoIP Performance Manager related topology update (after the initial PNODES traps are processed).



Description of voip.conf 33


PMTraps_Timeout 240 to 3600Default: 240

The minimum value for VoIP Performance Manager Traps Timeout is 240 seconds (4 minutes). The recommended maximum value is 3600 seconds (1 hour).• If the assigned value is less than 240 seconds, it will be set to

240 seconds. • If the assigned value is not a multiple of 240, it will be rounded

up to the closest multiple of 240.

MaxNumPIDMonitors 0 to 500Default: 500 (maximum)

The maximum number of PID monitors invoked each minute.

ValidateTopology TRUE,FALSEDefault: TRUE

Controls whether a report containing topology sizing information is printed:• A value of TRUE indicates that the report is printed.• A value of FALSE indicates that the report is not printed.

AutoDiscover TRUE,FALSEDefault: TRUE

Controls whether VoIP Availability Manager automatically performs a topology synchronization to import topology from IP Availability Manager whenever IP Availability Manager completes a discovery cycle:• A value of TRUE indicates that automatic topology

synchronization does occur.• A value of FALSE indicates that automatic topology

synchronization does not occur.“Disabling automatic synchronization” on page 35 clarifies the use of this parameter.

DisableReconfigure TRUE,FALSEDefault: FALSE

Determines whether reconfiguration is enabled or disabled:• A value of TRUE indicates that reconfiguration is disabled.• A value of FALSE indicates that reconfiguration is enabled.

Note: When TRUE, no reconfiguration takes place. Reconfiguration is described in “Polling and Thresholds Console toolbar buttons” on page 99.





Adding IP Availability Manager as a topology and status sourceBy default, VoIP Availability Manager is configured to include an IP Availability Manager named INCHARGE-AM as a source of device topology and device topology status updates.

You can edit the domain.conf file and change this name or configure additional IP Availability Managers as sources for VoIP Availability Manager. The block of lines to be edited is:


To change the default IP Availability Manager name, or to add an additional IP Availability Manager as a topology and status source:

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

sm_edit conf/voip/domain.conf

2. On the InChargeDomain and DomainName lines, change INCHARGE-AM to the name of your IP Availability Manager. For example:

InChargeDomain::InChargeDomain_EAST-AM1{ Type = “AM” DomainName = “EAST-AM1”}

3. To configure additional IP Availability Manager sources, copy and paste additional instances of the InChargeDomain object and then follow the directions given in Step 2.

Here is an example of an additional IP Availability Manager instance in which Type = “AM-PM” indicates that an IP Availability Manager and an IP Performance Manager or IP Server Performance Manager are running as a single process:

InChargeDomain::InChargeDomain_EAST-AM2{ Type = “AM-PM” DomainName = “EAST-AM2”}

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

5. If VoIP Availability Manager was running before you edited the domain.conf file, restart VoIP Availability Manager.

At startup, VoIP Availability Manager reads the domain.conf file, saves the configuration information in its repository, and imports VoIP-enabled devices from the one or more IP Availability Manager sources.

Note: If an IP Availability Manager source is not running, VoIP Availability Manager will periodically attempt to connect to the IP Availability Manager.

Disabling automatic synchronization 35


Disabling automatic synchronizationBy default, automatic topology synchronization with the underlying IP Availability Manager is enabled, meaning that VoIP Availability Manager automatically imports topology from IP Availability Manager whenever IP Availability Manager completes a discovery cycle.

You can edit the voip.conf file and disable this behavior. The line to be edited is:

# AutoDiscover = FALSE

To disable automatic topology synchronization with IP Availability Manager:

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


2. Find the following line and then uncomment the line (shown uncommented):

AutoDiscover = FALSE

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

4. If VoIP Availability Manager was running before you edited the voip.conf file, restart VoIP Availability Manager.



Enabling trap receptionBy default, the built-in trap receiver for VoIP Availability Manager is disabled. If the Avaya Enablement Pack, the Nortel Enablement Pack, or both are installed, you need to enable the built-in trap receiver so that traps issued by Avaya and Nortel devices can be received and processed.

You can edit the voip.conf file and enable the built-in trap receiver. The parameter to be edited is:

# TrapPort = 9001

To enable trap reception:

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


2. Find the following line:

# TrapPort = 9001

Note: TrapPort = 0 disables the built-in trap receiver.

3. Uncomment the line (remove the # character) and change the value to 9001 or any value in the range 2049 to 65534 (inclusive). The value that you select becomes the port number on which the built-in trap receiver listens for traps.

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

5. If VoIP Availability Manager was running before you edited the voip.conf file, restart VoIP Availability Manager.

In addition to enabling trap reception, you need to configure SNMP trap integration to distribute Avaya or Nortel traps to VoIP Availability Manager, as explained in Chapter 6, “Configuring the SNMP Trap Integration.”

Configuring security 37


Configuring securityThe security configuration files, clientConnect.conf and serverConnect.conf, located in the BASEDIR/smarts/conf directory of each EMC Smarts software installation, allow you to set up secure connections between the component applications in a VoIP Availability Manager deployment. By default, the configuration option settings in the clientConnect.conf file and the serverConnect.conf files allow minimally secure connections between the components.

An VoIP Availability Manager deployment employing secure communications has the following environment variables set to the same value in each component application’s BASEDIR/smarts/local/conf/runcmd_env.sh file:

SM_INCOMING_PROTOCOL=[1,0 or 2,0 or 3,0]SM_OUTGOING_PROTOCOL=[1,0 or 2,0 or 3,0]

For example:

SM_INCOMING_PROTOCOL=2,0SM_OUTGOING_PROTOCOL=2,0

If you decide to configure client tools, you also need to create a secure connection between the Global Console and the Global Manager. To do so, you need to modify the clientConnect.conf file in the BASEDIR/smarts/conf directory in the Service Assurance Management Suite installation area for the Global Console. Client tools are described in “Configuring client tools for VoIP Availability Manager” on page 69.

The EMC Smarts System Administration Guide presents detailed information about EMC Smarts secure communications.

Opening the Global Console 39

3

This chapter includes procedures for opening the Global Console and describes consoles used to complete configuration and administration tasks. It consists of the following sections:

◆ Global Console overview ............................................................................................. 40◆ User accounts and passwords ..................................................................................... 40◆ Procedure for opening the Global Console ............................................................... 40◆ Procedure for opening the Global Manager Administration Console .................. 42◆ Procedure for opening the Domain Manager Administration Console................ 43◆ Procedure for opening the Polling and Thresholds Console .................................. 43

Opening the GlobalConsole


Opening the Global Console

Global Console overviewThe Global Console is a collection of many consoles that together enable administrators to manage EMC Smarts Domain Managers and Global Managers.

You will use the following three consoles to complete the configuration and administration tasks required to set up a VoIP Availability Manager deployment:

◆ Domain Manager Administration Console

Enables administrators to manage Domain Managers and to discover topology.

◆ Global Manager Administration Console

Enables administrators to configure the Global Manager (for example, to set up connections to underlying Domain Managers, to enable map types that are disabled by default, or to enable client tools and server tools).

◆ Polling and Thresholds Console

Enables administrators to control periodic polling and to set thresholds for polled data, and to specify device access credentials.

User accounts and passwordsAttaching the Global Console to a Domain Manager (such as VoIP Availability Manager) or to a Global Manager requires an EMC Smarts user account.

◆ The default administration account is username admin and password changeme.

◆ The default operator account is username oper and password oper.

For users logged in with an administration account, the Global Console includes a Configure menu, which enables administrators to open the Domain Manager Administration Console and the Global Manager Administration Console, to edit Map Icons, and so on.

The EMC Smarts System Administration Guide provides information about changing the password for the default administration account (recommended) and configuring access privileges. The EMC Smarts Service Assurance Manager Configuration Guide provides information about configuring user profiles and permissions to perform specific console operations.

Procedure for opening the Global ConsoleTo open the Global Console:

1. Start the Global Console.

• On a Windows system, select Start > Programs > InCharge 7 > EMC Smarts Global Console.

• On a UNIX system, go to the BASEDIR/smarts/bin directory in the Service Assurance Manager (Global Manager) installation area and type:

sm_gui

Press Enter.

The Attach Manager dialog box opens.

Procedure for opening the Global Console 41


2. In the dialog box:

a. Ensure that the EMC Smarts Broker for your deployment appears in the Broker text box.

b. Click the Manager list box or the Browse button to display a list of active (running) Smarts Managers, and from that list select a Domain Manager (for example, VoIP-AM) or a Global Manager (for example, INCHARGE-SA) in your deployment as the Smarts Manager to which you want to connect.

c. Type your login username and password. (The default administration login is username admin and password changeme.)

d. Click OK.

A console opens.

What console opens at this point depends on whether you selected a Domain Manager or a Global Manager application.

If you selected a Domain Manager, a Topology Browser Console opens by default as shown in Figure 2 on page 41. In this example, the Topology Browser Console is attached to a Domain Manager named VoIP-AM.

Figure 2 Topology Browser Console—example



If you selected a Global Manager, a Notification Log Console opens by default as shown in Figure 3 on page 42. In this example, the Notification Log Console is attached to a Global Manager named INCHARGE-SA.

Figure 3 Notification Log Console—example

Procedure for opening the Global Manager Administration ConsoleYou can open a Global Manager Administration Console from any Global Console (for example, the Notification Log Console) that is attached to a Global Manager by selecting the Configure > Global Manager Administration Console menu option. Figure 10 on page 56 is an example of a Global Manager Administration Console attached to a Global Manager named INCHARGE-SA.

Procedure for opening the Domain Manager Administration Console 43


Procedure for opening the Domain Manager Administration ConsoleYou can open a Domain Manager Administration Console from any Global Console (for example, the Topology Browser Console) that is attached to a Domain Manager by selecting the Configure > Domain Manager Administration Console menu option. Figure 4 on page 43 is an example of a Domain Manager Administration Console attached to a Domain Manager named VoIP-AM.

Figure 4 Domain Manager Administration Console—example

Procedure for opening the Polling and Thresholds ConsoleYou can open a Polling and Thresholds Console from any Domain Manager Administration Console by selecting the Configure > Polling and Thresholds menu option. Figure 20 on page 98 is an example of a Polling and Thresholds Console attached to a Domain Manager named VoIP-AM.

Configuring IP Availability Manager 45

4

This chapter provides instructions for configuring an IP Availability Manager in a VoIP Availability Manager deployment. It consists of the following sections:

◆ Configuration overview ............................................................................................... 46◆ Topology object import from IP Availability Manager............................................ 46◆ About the VoIP topology collection set...................................................................... 47◆ Customizing VoIP-related device-matching filters .................................................. 49

Configuring IPAvailability Manager


Configuring IP Availability Manager

Configuration overviewFor an IP Availability Manager in a VoIP Availability Manager deployment, an administrator performs the standard configuration tasks presented in the EMC Smarts IP Management Suite Configuration Guide to prepare the IP Availability Manager for SNMP discovery. The administrator also performs the following additional configuration tasks to prepare IP Availability Manager for operation in a VoIP Availability Manager deployment:

◆ Customize VoIP-related device-matching filters (optional)

This chapter provides the instructions for completing this task.

◆ Exclude Avaya and Nortel floating IP addresses from the discovered topology (mandatory if managed environment contains Avaya or Nortel devices)

The EMC Smarts Enablement Pack for Avaya User Guide and the EMC Smarts Enablement Pack for Nortel User Guide provide instructions for completing this task.

◆ Configure SNMP trap integration to distribute network traps to IP Availability Manager (mandatory if managed environment contains Avaya or Nortel devices)

Chapter 6, “Configuring the SNMP Trap Integration,” provides the instructions for completing this task.

Topology object import from IP Availability ManagerUpon adding IP Availability Manager as a source and every time thereafter when VoIP Availability Manager starts up, VoIP Availability Manager imports topology objects from IP Availability Manager in accordance with the data exchange adapter (DXA) configuration file shown in Figure 5 on page 46.

Figure 5 Importing topology objects from IP Availability Manager

Global Manager

Subset of

VoIP Topology Collection Set

NetworkTopology

Import topology according to

dxa-voip-from-am.conf file


VoIPTopology

UCS “in” FilterEnabled or Disabled

?

Enabled

Disabled (default)

FilterControl


UnitaryComputerSystem (UCS) “in” topology filter is part of dxa-voip-from-am.conf file.

Note:

About the VoIP topology collection set 47


As shown in Figure 5 on page 46, VoIP Availability Manager imports topology in accordance with the dxa-voip-from-am.conf file, which is located in the BASEDIR/smarts/conf/voip directory in the VoIP Availability Manager installation area. Figure 6 on page 47 shows how the UCS “in” filter influences the types of topology objects imported by VoIP Availability Manager from IP Availability Manager.

Figure 6 Topology objects imported from IP Availability Manager

Whether the UCS “in” filter is disabled or enabled, the topology import includes the Chassis, Card, IP, and SNMPAgent objects associated with the imported devices. VoIP Availability Manager imports only managed devices, that is, imports only device objects whose IsManaged attribute is set to TRUE.

About the VoIP topology collection setIP Availability Manager performs its traditional discovery of network objects and also creates a VoIP topology collection from the discovered network objects for VoIP Availability Manager. It queries the SNMP agent of every device in the managed network for VoIP support.

IP Availability Manager stores the VoIP topology collection set in the VOIP_TopologyCollection::VOIP-System-TopologyCollection object.

Content of VoIP topology collection setWhen querying Avaya MIBs, IP Availability Manager is highly successful at identifying VoIP-enabled devices. When querying Cisco or Nortel MIBs, IP Availability Manager is less successful at identifying VoIP-enabled devices. The degree of success depends on two factors:

◆ The amount of VoIP-related information provided by the MIB

◆ The type of device (general purpose or special purpose) running the VoIP application

Accordingly, the VoIP topology collection set created for an Avaya-only managed network will consist of just VoIP-enabled devices—and the Chassis, Card, IP, and SNMPAgent objects associated with the devices.

proxy UnitaryComputerSystem

class Chassis

class Card

class IP

#class DuplicateIP

#class SystemRedundancyGroup

class SNMPAgent

dxa-voip-from-am.conf file classes

UCS “in” Filter Disabled (Default): proxy UnitaryComputerSystem #in TopologyCollection ConsistsOf VOIP-System

Outcome: Import all devices

UCS “in” Filter Enabled: proxy UnitaryComputerSystem in TopologyCollection ConsistsOf VOIP-System

Outcome: Import only the devices in the VoIP topology collection set

UCS “in” filter operation



For a Cisco-only, Nortel-only, or Cisco/Nortel-only managed network, the VoIP topology collection set will consist of VoIP-enabled devices and most probably other devices that are not VoIP-enabled—and the Chassis, Card, IP, and SNMPAgent objects associated with the devices.

ICIM modeling of devices in VoIP topology collection set

IP Availability Manager represents a discovered VoIP-enabled device as one of the following subclasses of the UnitaryComputerSystem class:

◆ CallServer (Avaya only)

◆ Host (running telephony services)

◆ MediaGateway (Avaya only)

◆ Router

◆ Switch

Device-matching filters for the VoIP topology collection setDevice-matching filters defined in the following file in the IP Availability Manager installation area:

BASEDIR/smarts/conf/discovery/voip-topo-oid.conf

The file’s content is:

#Filter for VOIP Avaya devices# Format: VOIP-SYS-OID-IP-Pattern-.<System OID> <IP pattern>VOIP-SYS-OID-IP-Pattern-.1.3.6.1.4.1.6889.1.8.1.49 *VOIP-SYS-OID-IP-Pattern-.1.3.6.1.4.1.6889.1.8.1.50 *VOIP-SYS-OID-IP-Pattern-.1.3.6.1.4.1.6889.1.8.1.51 *VOIP-SYS-OID-IP-Pattern-.1.3.6.1.4.1.6889.1.8.1.52 *VOIP-SYS-OID-IP-Pattern-.1.3.6.1.4.1.6889.1.8.1.56 *

#Filter for VOIP Cisco devicesVOIP-SYS-OID-IP-Pattern-.1.3.6.1.4.1.9.* *

#Filter for VOIP Nortel devicesVOIP-SYS-OID-IP-Pattern-.1.3.6.1.4.1.562.3.21 *VOIP-SYS-OID-IP-Pattern-.1.3.6.1.4.1.562.37.1.4 *

VOIP-SYS-OID-IP-Pattern-<System OID> specifies the pattern for a device, where the device is identified by its system object identifier. The <IP Pattern> part specifies the IP-matching pattern for the filter’s device pattern.

Note: “*” matches anything. Wildcard syntax is discussed in Appendix A, “Wildcard Patterns.”

Any device discovered in the managed network that matches any device-matching pattern in the voip-topo-oid.conf file will be included in the VoIP topology collection set. Conversely, any device discovered in the managed network that does not match any of the device-matching patterns will be excluded from the VoIP topology collection set.

Customizing VoIP-related device-matching filters 49


Customizing VoIP-related device-matching filtersAs described in the previous section, you can change what devices are included in the VoIP topology collection set by changing, adding, or deleting device-matching filters in the voip-topo-oid.conf file.

To customize VoIP-related device-matching filters:

1. Go to the BASEDIR/smarts/bin directory in the IP Availability Manager installation area and issue the following command to open the voip-topo-oid.conf file:

sm_edit conf/discovery/voip-topo-oid.conf

2. Consult “Device-matching filters for the VoIP topology collection set” on page 48 and make your changes to the file.

Here is an example of a customized device-matching filter:

VOIP-SYS-OID-IP-Pattern-.1.3.6.1.4.1.9 10.10.*

The filter allows any discovered device having (1) system OID .1.3.6.1.4.1.9 and (2) an IP address beginning with 10.10. to be included in the VoIP topology collection set.

3. Save and close the file. The modified version of the voip-topo-oid.conf file is saved to the BASEDIR/smarts/local/conf/discovery directory.

4. If IP Availability Manager was running before you edited the voip-topo-oid.conf file, restart IP Availability Manager.

Configuring the Global Manager 51

5

This chapter provides instructions for configuring the Global Manager in a VoIP Availability Manager deployment. It consists of the following sections:

◆ Configuration overview ............................................................................................... 52◆ About the Global Manager .......................................................................................... 52◆ IC Domain Configuration objects ............................................................................... 56◆ Specifying the underlying domains ........................................................................... 59◆ Loading the XML configuration file for VoIP-AM ................................................... 67◆ Configuring client tools for VoIP Availability Manager.......................................... 69

Configuring the GlobalManager


Configuring the Global Manager

Configuration overviewVoIP Availability Manager is compatible with EMC Smarts Service Assurance Management Suite version 7.2 and 7.1.

For the Global Manager to import topology and events from the underlying components in a VoIP Availability Manager deployment, you must configure the Global Manager with the proper data exchange adapter (DXA) files. The Global Manager integrates and correlates the imported topology and events and relates the data to services and customers. To configure the Global Manager, you use the Global Console.

The EMC Smarts Service Assurance Manager Configuration Guide provides detailed instructions on using the Global Console to complete Global Manager configurations.

About the Global Manager Most of the configuration tasks for configuring the Global Manager in a VoIP Availability Manager deployment are accomplished using the Global Manager Administration Console. Figure 7 on page 53 summarizes the Global Manager Administration Console interaction with the Global Manager.

As shown in Figure 7 on page 53, the initial configurations for the Global Manager are stored in the ics-default.xml file and imported to the Global Manager’s repository when the Global Manager starts up. The configurations displayed in a newly started Global Manager Administration Console are exported from the Global Manager’s repository.

About the Global Manager 53


Figure 7 Global Manager Administration Console interaction with the Global Manager

Anyrepository file

?

--norestorein startup line

?

+

+

+

+

-

Escalation Policies Notification Lists Tools User Profiles Users ICS Configuration System Defaults Business Templates IC Domain Configuration Domains Domain Groups Domain Tags Domain Types

Global Manager

Repository

Objects

export(call)

export(call)

Get Config Objects

Yes

At Global Manager Startup

XMLStream

Load this file

No

ics-default.xmlfile

Yes

No

Do notload this

file

XMLStream

Objects to

XML

ConfigHandlers

= object

ConfigObjects

Global Console

Global Manager Administration Console

At ConsoleStartup

UserConfigurations

XML-to-GUIConversion

GUI-to-XMLConversion

XMLto

Objects

+

+

+

+

+

+

+

+

-

-

INCHARGE-SA-

+

+

+

+

-

Click object

Click Apply

ICS Configurationsformerly in the ics.conf file and

now in theics-default.xml file



Figure 8 on page 54 shows the relationships between Domain Group, Domain, Domain Type, and Domain Tag configuration objects. The intent of the Domain Group is to represent the server components of a split-server Domain Manager as a single entity. Doing so makes a split-server Domain Manager look just like a standalone Domain Manager to administrators and users.

Figure 8 Domain configuration objects and their relationships

Domain Group

TaggedBy(optional)

Domain Tags

Domain Tag3

Domain Tagn

Domain Tag2

Domain Tag1

Domain Type(Standalone-

Suite)


Suite)


Suite)

Domain Type(Topology-

Suite)

Domain Type(Analysis-

Suite)

Domain Type(Monitoring-

Suite)

Domain Managers

Standalone Domain Managers

Domain(Standalone)

Domain(Standalone)

Domain(Standalone)

Domain(Monitoring

Server)

Domain(Topology

Server)

Domain(AnalysisServer)

TopologyDomains

MonitoringDomains

AnalysisDomains

Split-Server Domain Manager

ConfiguredBy

ConfiguredBy

ConfiguredBy

Split-Server Domain Types

ConfiguredBy

ConfiguredBy

ConfiguredBy

Standalone Domain Types

TaggedBy(optional)

= Relationships

...

About the Global Manager 55


Figure 9 on page 55 identifies the default VoIP Availability Manager, IP Availability Manager, and Adapter Platform domain configurations held by the Global Manager. The default names for the respective domains are VoIP-AM, INCHARGE-AM, and INCHARGE-OI.

Figure 9 Default domain configurations

Domains

ConfiguredByConfiguredBy ConfiguredBy

INCHARGE-OIVoIP-AM INCHARGE-AM

= Relationships

Domain Types

INCHARGE-OI-SUITEVOIP-SUITE INCHARGE-AM-SUITE



IC Domain Configuration objectsFigure 10 on page 56 presents an example display of a Global Manager Administration Console attached to a Global Manager named INCHARGE-SA.

Figure 10 Global Manager Administration Console—example

Listed at the bottom of the configuration tree of the Global Manager Administration Console are the four categories of IC Domain Configuration objects: Domains, Domain Groups, Domain Tags, and Domain Types. Listed under each category are instances of these objects; for example, the default domains INCHARGE-AM, INCHARGE-OI, and VoIP-AM are listed under Domains. Selecting an object in the left panel displays its attributes and their values in the right panel.

IC Domain Configuration creation wizards

Each IC Domain Configuration category has an associated creation wizard to simplify the specifying of its configuration objects. You launch an IC Domain Configuration wizard by clicking the appropriate toolbar button (shown in Figure 10 on page 56), by right-clicking an IC Domain Configuration category name (for example, right-clicking Domains) and then clicking the pop-up menu, or by selecting New Domain, New Domain Group, New Domain Type, or New Domain Tag from the Edit menu.

IC DomainConfigurations

Toolbar Button for LaunchingServer Reconfiguration

Toolbar Buttons for LaunchingIC Domain Configuration Wizards

IC Domain Configuration objects 57


When creating a domain, the created domain is enabled automatically. Similarly, when creating a domain group, the created domain group and its server component domains are enabled automatically.

IC Domain Configuration server reconfiguration

Clicking the Apply button, which is available to all configuration categories, writes configuration changes to the Global Manager’s repository. Clicking the Reconfigure button, which is available only to the IC Domain Configuration categories, calls a “reconfigure” method that determines which underlying domains need synchronizing or resynchronizing—that is, determines which underlying domains topology or events need to be imported or reimported—and then initiates the needed data transfers. Calling the reconfigure method is referred to as “reconfiguring the Global Manager.”

In addition to clicking the Reconfigure button, the reconfigure method can be initiated in two other ways: by clicking the Reconfigure toolbar button (shown in Figure 10 on page 56) or by selecting Reconfigure Server from the Configure menu.

Figure 11 on page 58 demonstrates how reconfiguring the Global Manager works.



Figure 11 How reconfiguring the Global Manager works

Topology and Events

Global Manager

Compare

IC Domain Configuration Objects

Changes

Domain Tag Configuration Objects Domain Type Configuration Objects

Domain Group Configuration Objects Domain Configuration Objects

(Available only if differences exist between IC Domain Configuration objects and InCharge Domain and Domain Group objects)

Click Reconfigure

Domain or domain group configuration object was

deleted or disabled.

Response:

Delete domain or domain group object

Domain, domain group, domain type, or domain tag

configuration object’s attributes have changed.

Response:

Change domain or domain group object’s attributes

Domain or domain group configuration object was

created or enabled.

Response:

Create domain or domain group object

InCharge Domain and Domain Group Objects

InChargeDomainGroup ObjectsInChargeDomain Objects

Domain Managers

Standalone Domain Manager Split-Server Analysis Server

Split-Server Topology Server Split-Server Monitoring Server

Specifying the underlying domains 59


Specifying the underlying domainsAn administrator uses the IC Domain Configuration objects to specify the underlying VoIP Availability Manager, IP Availability Manager, and Adapter Platform domains in a VoIP Availability Manager deployment. Doing so provides the sources of topology and events for the Global Manager and associates each underlying domain with the proper DXA file.

The expectation is that a user will either accept the default VoIP Availability Manager named VoIP-AM or make a copy of the default to create a new VoIP Availability Manager having a different name, say EAST-VoIP-AM.

This section provides procedures for the following two configuration scenarios:

◆ Configuration scenario 1: A VoIP Availability Manager deployment containing a VoIP Availability Manager named VoIP-AM, an IP Availability Manager named INCHARGE-AM, and an Adapter Platform named INCHARGE-OI.

◆ Configuration scenario 2: A VoIP Availability Manager deployment containing a VoIP Availability Manager named EAST-VoIP-AM, two IP Availability Managers named EAST-AM1 and EAST-AM2, and an Adapter Platform named EAST-OI.

To specify the underlying domains in a more complex VoIP Availability Manager deployment, consult the EMC Smarts Service Assurance Manager Configuration Guide.

Specifying the underlying domains for configuration scenario 1

By default, VoIP-AM is disabled, INCHARGE-OI is disabled, and INCHARGE-AM is enabled. The names of disabled domains or domain groups appear as gray text in the Global Manager Administration Console, and the names of enabled domains or domain groups appear as black text.

Figure 12 on page 59 previews the configuration changes for configuration scenario 1.

Figure 12 The displays before and after completing the configuration for scenario 1

Note: If VoIP-AM does not appear in the Before column, perform the procedure in “Loading the XML configuration file for VoIP-AM” on page 67.

Before After



During its initial startup the Global Manager performs the following tasks:

◆ Creates an InChargeDomain object named INCHARGE-AM and starts the appropriate topology and event drivers.

◆ Consults the EMC Smarts Broker for the deployment and establishes a connection to the INCHARGE-AM application.

◆ Subscribes to and imports topology and events from the INCHARGE-AM application.

Every time that the Global Manager is restarted, it automatically initiates a server reconfiguration—called the reconfigure method—to align the IC domain and domain group configuration objects with the InCharge domain and domain group objects. For the initial startup, because the only IC Domain Configuration object enabled is INCHARGE-AM, the only alignment required is the one just described.

If the synchronization with the INCHARGE-AM application fails, or if no IP Availability Manager application named INCHARGE-AM exists in the deployment, the Global Manager writes an error message to its log file.

This section consists of three procedures:

◆ “Procedure for specifying the underlying VoIP-AM domain for configuration scenario 1” on page 60

◆ “Procedure for specifying the underlying INCHARGE-OI domain for configuration scenario 1” on page 61

◆ “Procedure for reconfiguring the Global Manager for configuration scenario 1” on page 61

Procedure for specifying the underlying VoIP-AM domain for configuration scenario 1To specify the underlying VoIP-AM domain for configuration scenario 1:

1. Attach the Global Manager Administration Console to the target Global Manager.

Note: Instructions for opening the Global Manager Administration Console are presented in Chapter 3, “Opening the Global Console.”

2. In the left panel of the Global Manager Administration Console, expand the configuration tree to display the Domains objects.

3. Select VoIP-AM to display its configuration window.

4. In the configuration window, select the Enabled checkbox.

5. In the configuration window, click Apply to save your configuration changes.

Note: If the Server Reconfiguration information dialog box appears, click OK.



Procedure for specifying the underlying INCHARGE-OI domain for configuration scenario 1To specify the underlying INCHARGE-OI domain for configuration scenario 1:

1. In the left panel of the Global Manager Administration Console, expand the configuration tree to display the Domains objects.

2. Select INCHARGE-OI to display its configuration window.

3. In the configuration window, select the Enabled checkbox.

4. In the configuration window, click Apply to save your configuration changes.

Note: If the Server Reconfiguration information dialog box appears, click OK.

Procedure for reconfiguring the Global Manager for configuration scenario 1To reconfigure the Global Manager for configuration scenario 1:

1. In the toolbar area of the Global Manager Administration Console, click the Reconfigure toolbar button.

2. In the Server Reconfiguration confirmation dialog box, click Yes.

3. In the Server Reconfiguration information dialog box, click Close.

In response, the Global Manager:

◆ Creates an InChargeDomain object named VoIP-AM and starts the appropriate topology and event drivers.

◆ Creates an InChargeDomain object named INCHARGE-OI and starts the appropriate notification drivers.

◆ Consults the EMC Smarts Broker for the deployment and establishes a connection to the VoIP-AM and INCHARGE-OI domains.

◆ Subscribes to and imports topology and events from the VoIP-AM domain.

◆ Subscribes to and imports notifications from the INCHARGE-OI domain.

The Global Manager will establish an additional connection to the VoIP-AM domain under any of the following circumstances:

◆ To obtain the latest object attribute values for display in the Details tab of a VoIP Notification Properties dialog box.

◆ To obtain the latest object attribute values for display in a VoIP Containment dialog box.



Specifying the underlying domains for configuration scenario 2

Figure 13 on page 62 previews the configuration changes for configuration scenario 2.

Figure 13 The displays before and after completing the configuration for scenario 2

This section consists of five procedures:

◆ “Procedure for specifying the underlying EAST-VoIP-AM domain for configuration scenario 2” on page 63

◆ “Procedure for specifying the underlying EAST-AM1 domain for configuration scenario 2” on page 63

◆ “Procedure for specifying the underlying EAST-AM2 domain for configuration scenario 2” on page 63

◆ “Procedure for specifying the underlying EAST-OI domain for configuration scenario 2” on page 63

◆ “Procedure for reconfiguring the Global Manager for configuration scenario 2” on page 66

Before After



Procedure for specifying the underlying EAST-VoIP-AM domain for configuration scenario 2To specify the underlying EAST-VoIP-AM domain for configuration scenario 2:



2. In the left panel of the Global Manager Administration Console, right-click Domains and then click the pop-up menu to launch the Domain Creation Wizard.

3. Consult Figure 14 on page 64 and follow the directions to create a VoIP Availability Manager domain named EAST-VoIP-AM.

Procedure for specifying the underlying EAST-AM1 domain for configuration scenario 2To specify the underlying EAST-AM1 domain for configuration scenario 2:


2. Consult Figure 15 on page 65 and follow the directions to create an IP Availability Manager domain named EAST-AM1.

Procedure for specifying the underlying EAST-AM2 domain for configuration scenario 2To specify the underlying EAST-AM2 domain for configuration scenario 2:


2. Consult Figure 15 on page 65 and use the directions as a guide to create an IP Availability Manager domain named EAST-AM2.

Procedure for specifying the underlying EAST-OI domain for configuration scenario 2To specify the underlying EAST-OI domain for configuration scenario 2:


2. In the Domain Creation Wizard, select INCHARGE-OI from the Copy Existing drop-down menu, type EAST-OI in the Domain Name text field, and click Next.

3. Consult Figure 15 on page 65 and use the directions as a guide to create the Adapter Platform domain named EAST-OI.



Figure 14 Using the Domain Creation Wizard to create the EAST-VoIP-AM domain

Click

Click

Click

(Leave empty)

An empty Tag String field causes the wizard to skip the Select Domain Tag

panel.

This panel is applicable to server component domains only. Click

Click

Click

(Do nothing)



Figure 15 Using the Domain Creation Wizard to create the EAST-AM1 domain

Click

Click

Click

(Leave empty)

An empty Tag String field causes the wizard to skip the Select Domain Tag

panel.

This panel is applicable to server component domains only. Click

Click

Click

(Do nothing)



Procedure for reconfiguring the Global Manager for configuration scenario 2To reconfigure the Global Manager for configuration scenario 2:

1. In the toolbar area of the Global Manager Administration Console, click the Reconfigure toolbar button.

2. In the Server Reconfiguration confirmation dialog box, click Yes.

3. In the Server Reconfiguration information dialog box, click Close.

In response, the Global Manager:

◆ Creates an InChargeDomain object named EAST-VoIP-AM and starts the appropriate topology and event drivers.

◆ Creates an InChargeDomain object named EAST-AM1 and starts the appropriate topology and event drivers.

◆ Creates an InChargeDomain object named EAST-AM2 and starts the appropriate topology and event drivers.

◆ Creates an InChargeDomain object named EAST-OI and starts the appropriate notification drivers.

◆ Consults the EMC Smarts Broker for the deployment and establishes a connection to the EAST-VoIP-AM, EAST-AM1, EAST-AM2, and EAST-OI domains.

◆ Subscribes to and imports topology and events from the EAST-VoIP-AM domain.

◆ Subscribes to and imports topology and events from the EAST-AM1 domain.

◆ Subscribes to and imports topology and events from the EAST-AM1 domain.

◆ Subscribes to and imports notifications from the EAST-OI domain.

The Global Manager will establish an additional connection to the EAST-VoIP-AM domain under any of the following circumstances:

◆ To obtain the latest object attribute values for display in the Details tab of a VoIP Notification Properties dialog box.

◆ To obtain the latest object attribute values for display in a VoIP Containment dialog box.

Similarly, the Global Manager will establish an additional connection to the EAST-AM1 or EAST-AM2 domain under any of the following circumstances:

◆ To obtain the latest object attribute values for display in the Details tab of an IP Notification Properties dialog box.

◆ To obtain the latest object attribute values for display in an IP Containment dialog box.

Note: Because no IP Availability Manager application named INCHARGE-AM is running in configuration scenario 2, users should disable the INCHARGE-AM domain for this scenario.

Loading the XML configuration file for VoIP-AM 67


Loading the XML configuration file for VoIP-AMBy default, the XML domain configuration file for VoIP-AM is loaded into the Global Manager, meaning that by default it is available to a Global Console attached to the Global Manager. If for some reason the XML domain configuration file for VoIP-AM is not available, perform the procedure in this section to load it.

Two server tools facilitate the loading of XML configuration files into the Global Manager. Both tools are launched from a Topology Browser Console (attached to the Global Manager) by right-clicking the local InChargeDomain object that represents the Global Manager (Figure 16 on page 67).

Figure 16 Access to Import XML Configuration server tools

Both server tools are described in the EMC Smarts Service Assurance Manager Configuration Guide. The server tool is used in the procedure that follows to load the XML domain configuration file for VoIP-AM.

After loading the file, VoIP-AM will appear in the Domains category on the Global Manager Administration Console. At that point, you should proceed with the procedures in “Specifying the underlying domains” on page 59.

To load the XML domain configuration file for VoIP-AM:



2. Select File > New > Topology Browser Console to launch a Topology Browser Console.

3. In the Topology Browser Console, expand the configuration tree to display the InChargeDomain objects.



4. Right-click the local InChargeDomain object representing the Global Manager—for example, INCHARGE-SA (Local)—and select Server Tools > Import XML Domain Configuration from the pop-up menu.

The Import XML Domain Configuration dialog box appears.

5. To load the XML domain configuration file for VoIP-AM, type voip in the Domain Type Descriptor field and click OK.

6. Switch back to the Global Manager Administration Console.

7. In the left panel of the Global Manager Administration Console, expand the configuration tree to display the Domains.

VoIP-AM appears in the Domains list. Since its name appears as black text, VoIP-AM is enabled.

8. Continue with the procedures in “Specifying the underlying domains” on page 59.

Configuring client tools for VoIP Availability Manager 69


Configuring client tools for VoIP Availability ManagerEMC Corporation provides sample server tools and client tools for EMC Smarts software. The primary resource for information about tools is the EMC Smarts Service Assurance Manager Configuration Guide. The guide describes how to use sample tool scripts and associate the tools with user profiles. This section describes information that is specific to the VoIP Management Suite.

The VoIP Management Suite provides samples of VoIP client tool scripts. You do not have to modify these scripts to use them, but you do need to perform some setup and configuration tasks. These predefined client tools enable Global Console operators to access VoIP Performance Manager data without having to open the VoIP Performance Manager’s graphical user interface. Client tools created to access VoIP Performance Manager data will be available only to certain topology objects imported by the Global Manager from VoIP Availability Manager.

This section describes:

◆ The procedure to configure sample client tools forVoIP Availability Manager (“Configuring client tools procedure” on page 69). The procedure can be used for Service Assurance Management Suite 7.1 or 7.2.

◆ JRE and web browser requirements (“Java requirements and web browser support” on page 72)

◆ Lists of available sample client tool scripts (“Sample client tools” on page 72)

Configuring client tools procedure

Configuring client tools involves modifying existing user profiles to use the client tools, copying the client tool scripts to the locations where Global Consoles reside (sometimes a Global Console resides on a remote host), specifying which web browser to use, setting up security, and verifying that the client tools launch from the Global Consoles.

Perform these steps to configure VoIP client tools:

1. Modify existing user profiles to enable client tools.

a. Import the configureVoipPMTools.xml file into the Global Manager. The configureVoipPMTools.xml file provides default settings for the client tools which appear in the Global Manager Administration Console.

Go to the BASEDIR/smarts/bin directory in the Service Assurance Management Suite installation area where the Global Manager is running and type this command:

▼ sm_config -s <Global Manager name> [-b <broker>] import --force configureVoipPmTools.xml ▲

Press Enter.

The option -b <broker> is used to specify the host and port (<host>:<port>) location of the Broker if the Global Manager is attached to a Broker other than "localhost:426."

Note: ▼▲ indicates the command must be typed as one line.



b. In the Global Console, select Configure > Global Manager Administration Console to open the Global Manager Administration Console for the attached Global Manager.

c. In the left panel tree, expand User Profiles and select the user profile to add the client tools to it and click Apply.

The EMC Smarts Service Assurance Manager Configuration Guide provides detailed information about using the Global Manager Administration Console to assign client tools to user profiles and, if necessary, to create new user profiles.

Note: Changes to a user profile may not be available to console users until they restart the Global Console.

2. Copy the client tool scripts into the Service Assurance Management Suite directory where the Global Consoles reside. Client tools must reside on the same hosts with the consoles.

a. Copy the entire voip subdirectory found in the VoIP Management Suite installation area (BASEDIR/smarts/actions/client/voip) to the BASEDIR/smarts/actions/client directory in the Service Assurance Management Suite installation area for the Global Console.

For UNIX, type:

▼ cp -r /opt/InCharge7/VoIP/smarts/actions/client/voip /opt/InCharge7/SAM/smarts/actions/client/voip ▲

Press Enter.

For Windows, copy the subdirectory using Windows Explorer or type the following commands from a DOS Window:

mkdir C:\InCharge7\SAM\smarts\actions\client\voip

▼ copy C:\InCharge7\VoIP\smarts\actions\client\voip C:\InCharge7\SAM\smarts\actions\client\voip ▲

Press Enter.

Note: ▼▲ indicates the command must be typed as one line.

3. If necessary, change the default location and the web browser. The default setting is Netscape Navigator for UNIX and Microsoft Internet Explorer for Windows.

a. Go to the BASEDIR/smarts/bin directory in the Service Assurance Management Suite installation area for the Global Console and use sm_edit to open the config.sh file for UNIX or the config.cmd file for Windows.

For example, type:

sm_edit actions/client/voip/config.sh

Note: This is the config file that resides with the client tool scripts in the BASEDIR/smarts/actions/client/voip directory for the Global Console.



b. Modify the browser setting in the config file.

For UNIX, replace the default path with the location for your web browser:

BROWSER=/usr/dt/bin/netscapeexport BROWSER

For Linux, the typical browser location is:

/usr/bin/mozilla

For Windows, replace the default path with the location and the executable for the web browser:

set "BROWSER=C:\Program Files\Internet Explorer\IEXPLORE.EXE"

c. Save and close the file. The file will be save to the local directory.

4. Set up security.

a. In the Global Console, select Configure > Domain Manager Administration Console > Polling and Thresholds to open the Polling and Thresholds Console for the attached VoIP Availability Manager. In the Device Access tab, select the setting for the VoIP PM Servers group and specify the login credentials.

The credentials (the user ID and password) are stored in an encrypted format in the VoIP Availability Manager and are used to access the web server running on the VoIP Performance Manager. “Creating a credential set” on page 134 provides more information.

b. Create a secure connection between the Global Console and the Global Manager. Modify the clientConnect.conf file in the BASEDIR/smarts/conf directory in the Service Assurance Management Suite installation area for the Global Console.

The EMC Smarts System Administration Guide describes security and the syntax of the clientConnect.conf file. The EMC Smarts Service Assurance Manager Configuration Guide describes security considerations for tools.

5. Verify that the client tools launch for the user profiles.

a. Log in as an operator, for example.

b. Open a Topology Browser Console attached to the Global Manager (for example, INCHARGE-SA) and right click on a target topology object to verify that the client tools appear in the Client Tools submenu. Topology objects are listed in Table 4 on page 72.

Note: Client tools are invoked under the username of the operator who started the Global Console. If the client tools do not display in the Client Tools submenu, detach and reattach the Global Console to the Global Manager.

c. Launch some or all of the client tools to confirm that the tool can access the web server running on the VoIP Performance Manager.



Java requirements and web browser support

When a user selects a client tool from the Client Tools submenu in the Global Console, the Global Console launches a URL from any host that contains the required JRE version and 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

Note: The number of windows which open on the client depends on the web browser. One window opens for Mozilla, Mozilla Firefox, and Netscape Navigator. Multiple windows open for Microsoft Internet Explorer.

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)

Sample client toolsTable 4 on page 72 lists the script names of sample client tools, their display names that appear in the Client Tools submenu of the Global Console, and the target topology object. A target topology object can be associated with one or more client tools.

For more information about the contents of the views or drill-down displays, consult the VoIP Performance Manager documentation that accompanied your version of the VoIP Performance Manager.

Table 4 VoIP client tools (page 1 of 3)

Client tool script Display name for tool Description

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

viewAvayaMedPro Launch MedPro View Target object: MediaProcessor—Avaya Media Processor cardOpens 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.

viewAvayaCLAN Launch CLAN View Target object: H323GateKeeper—Avaya Control LAN cardOpens 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.

viewAvayaDS1Service Launch DS1Service View Target object: DS1Service—Avaya Digital Signal 1 cardOpens 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 Target object: GatewayService—Avaya Media Gateway applicationOpens 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.

viewAvayaPortNetwork Launch Port Network View Target object: PortNetwork—A collection of Avaya Media Gateway port cardsOpens 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.

viewAvayaNetworkRegion Launch IP Network Region View Target object: ConvergedCallManager—Avaya Call ManagerOpens 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 Target object: ConvergedCallManager—Avaya Call ManagerOpens 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.

viewCiscoRoutePattern Launch Route Pattern View Target object: CallManager—Cisco Call ManagerOpens 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 Target object: CallManager—Cisco Call ManagerOpens 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

Target object: CallManager—Cisco Call ManagerOpens 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

Target object: CallManager—Cisco Call ManagerOpens 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

Target object: CallManager—Cisco Call ManagerOpens 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

Target object: CallManager—Cisco Call ManagerOpens 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.





viewCiscoTranscoder Launch Transcoder View Target object: CallManager—Cisco Call ManagerOpens 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

Target object: CallManager—Cisco Call ManagerOpens 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

Target object: CallManager—Cisco Call ManagerOpens 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.



Configuring the SNMP Trap Integration 75

6

This chapter provides instructions for configuring the SNMP trap integration in a VoIP Availability Manager deployment. It consists of the following sections:

◆ Configuration overview ............................................................................................... 76◆ SNMP trap integration components........................................................................... 77◆ Trap adapter configuration file: trapd.conf ............................................................... 80◆ Configuring the SNMP trap integration components ............................................. 84◆ Starting the SNMP trap integration components ..................................................... 93

Configuring the SNMPTrap Integration


Configuring the SNMP Trap Integration

Configuration overviewThe recommended SNMP trap integration design for the 3.0 release of VoIP Availability Manager is shown in Figure 17 on page 76.

Figure 17 Recommended trap integration for a VoIP Availability Manager deployment

Configuring the SNMP trap integration involves configuring and starting the various components that receive, distribute, and process the traps within a VoIP Availability Manager deployment.

VoIP analysis traps(v1, v2c)

Traps(v1, v2c, v3)

AdapterPlatform

Processed traps

SNMPTrap Adapter

(exploder)

VoIPNotification

Trap Adapter

VoIPinformational traps

(v1, v2c)

Network traps

(v1, v2c)

Topology

Trap notificationsGlobal

Manager


Traps(v1, v2c)

SNMPTrap Adapter

(receiver)

Non-VoIPinformational traps

(v1, v2c)

Processed traps

Topology

IP network(with VoIP devices)

Discarded,unwanted

traps


VoIPPerformance

Manager

SNMP trap integration components 77


SNMP trap integration componentsThe SNMP trap integration in a VoIP Availability Manager deployment is accomplished using the following types of components:

◆ “Built-in trap receiver” — part of most EMC Smarts Domain Managers

◆ “VoIP Notification Trap Adapter” — part of the VoIP Management Suite

◆ “SNMP Trap Adapter” — part of the Service Assurance Management Suite

◆ “Adapter Platform” — part of the Service Assurance Management Suite

Built-in trap receiverFor the 3.0 release, VoIP Availability Manager’s built-in trap receiver collects SNMP trap messages from two sources:

◆ Managed network devices through the SNMP Trap Adapter configured as a trap exploder

The built-in trap receiver forwards these traps to the Avaya Enablement Pack and the Nortel Enablement Pack for processing. Configuring the deployment to distribute these traps is described in this chapter.

◆ VoIP Performance Manager

The built-in trap receiver forwards these traps to the VoIP Performance Manager Integration Pack for processing. Configuring the deployment to distribute these traps is described in the EMC Smarts VoIP Management Suite Overview and Integration Guide.

For either source, the built-in trap receiver receives SNMPv1 and v2c traps and forwards them to the appropriate enablement pack. The enablement pack, in turn, parses the traps for status updates and applies the updates to the appropriate attributes of the appropriate objects in the VoIP Availability Manager modeled topology.

By default, the built-in trap receiver is disabled, and should be enabled only when the Avaya Enablement Pack, Nortel Enablement Pack, or VoIP Performance Manager Integration Pack is installed:

◆ The Avaya Enablement Pack uses received Avaya (Avaya-device-issued) VoIP traps to update attributes of Avaya objects in the modeled topology.

◆ The Nortel Enablement Pack uses received Nortel (Nortel-device-issued) VoIP traps to update attributes of Nortel objects in the modeled topology

◆ The VoIP Performance Manager Integration Pack uses received VoIP Performance Manager traps to update performance-related attributes of certain Avaya and Cisco objects in the modeled topology.

The built-in trap receiver is enabled by uncommenting the “TrapPort = 9001” parameter line in the BASEDIR/smarts/conf/voip/voip.conf file in the VoIP Management Suite installation area.



VoIP Notification Trap Adapter

The VoIP Notification Trap Adapter, which is part of the VoIP Management Suite, can be configured to convert traps to EMC Smarts notifications.

The operation of the VoIP Notification Trap Adapter is based on the parameter settings in the following files located in the BASEDIR/smarts/conf/voip/icoi directory in the VoIP Management Suite installation area:

◆ avaya_trap_mgr.conf

◆ cisco_trap_mgr.conf

◆ nortel_trap_mgr.conf

◆ default_trap_mgr.conf

The VoIP Notification Trap Adapter collects and parses VoIP informational traps received from the trap exploder, and generates EMC Smarts notifications, through the Adapter Platform, for input to the Global Manager. Through the Global Console, administrators and operators view and acknowledge the trap notifications.

SNMP Trap Adapter

The SNMP Trap Adapter, which is part of the Service Assurance Management Suite, can be configured to forward traps received from the managed environment or configured to convert traps to EMC Smarts notifications. Two instances of the SNMP Trap Adapter appear in a VoIP Availability Manager deployment, one instance configured as a trap exploder, and the other instance configured as a trap receiver.

Trap exploder operationThe EMC Smarts Service Assurance Manager Adapter Platform User Guide describes the operation of an SNMP Trap Adapter configured as a trap exploder. The operation is based on the parameter settings in the trapd.conf file described in “Trap adapter configuration file: trapd.conf” on page 80.

Note: A trap exploder is also known as a “trap forwarder.”

In a VoIP Availability Manager deployment (Figure 17 on page 76), the SNMP Trap Adapter configured as a trap exploder receives SNMPv1 and v2c traps from the managed network devices on its trap listening port (9000 by default) and:

◆ Forwards copies of received Avaya and Nortel VoIP traps to VoIP Availability Manager—to be used by VoIP Availability Manager for analysis purposes.

◆ Forwards copies of received network traps to IP Availability Manager—to be used by IP Availability Manager for analysis purposes.

◆ Optional: Forwards copies of received useful or interesting VoIP traps to the VoIP Notification Trap Adapter—to be used by users for informational purposes.

◆ Optional: Forwards copies of received useful or interesting non-VoIP traps to the SNMP Trap Adapter configured as a trap receiver—to be used by users for informational purposes.

SNMP trap integration components 79


Note: The trap exploder can also be configured to authenticate and decrypt received SNMPv3 traps, convert them to SNMPv2c traps, and forward the SNMPv2c traps to one or more destinations.

When a trap arrives, the SNMP Trap Adapter translates the trap in accordance to Table 5 on page 79 and reads the uncommented FORWARD entries in the trapd.conf file to determine which destinations should receive the forwarded trap. When the criteria of the trap matches the criteria of a FORWARD entry, the SNMP Trap Adapter sends a copy of the forwarded trap to each destination specified in the FORWARD entry.

Trap receiver operationThe EMC Smarts Service Assurance Manager Adapter Platform User Guide describes the operation of a SNMP Trap Adapter configured as a trap receiver. The operation is based on the parameter settings in the trap_mgr.conf file located in the BASEDIR/smarts/conf/icoi directory in the Service Assurance Management Suite installation area.

The purpose of the SNMP Trap Adapter configured as a trap receiver is to collect and parse non-VoIP informational traps received from the trap exploder, and to generate EMC Smarts notifications, through the Adapter Platform, for input to the Global Manager. Through the Global Console, administrators and operators view and acknowledge the trap notifications.

Adapter PlatformThe 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.

Table 5 SNMP Trap Adapter translation of incoming traps to forwarded traps

Incoming trap message version Forwarded trap message version

v1 v1

v2c v2c

v3



Trap adapter configuration file: trapd.confThe trapd.conf file, by default located in the BASEDIR/smarts/conf/trapd directory of all EMC Smarts product installations, is a global configuration file used to configure most EMC Smarts built-in trap receivers and most trap adapters (sm_trapd). Only the PORT parameter in this file is applicable to built-in trap receivers because the built-in trap receivers are configured to receive and parse traps, but not to forward traps. The other parameters in the file are applicable for configuring trap adapters to forward traps.

Note: The built-in trap receiver for VoIP Availability Manager is not controlled by the trapd.conf file. The only user-configurable control for the built-in trap receiver is the “TrapPort = 9001” parameter line in the voip.conf file.

Figure 18 on page 80 shows the configuration directory and the trapd.conf file for the SNMP Trap Adapter configured as a trap exploder. (The configuration directory is in the Service Assurance Management Suite installation area.) A trapd.conf file in the local area, created using the sm_edit utility, takes precedence over the original file containing the installed defaults. A seedfile is required only if the trap exploder is to process SNMPv3 traps.

Figure 18 Configuration directory for an SNMP Trap Adapter configured as a trap exploder

BASEDIR

ics

conf

smarts

ics

conf

local

trapd.conf

trapd

trapd.conf

trapd

Original files Modified files

Trap exploderconfiguration

directory

Trap exploderconfiguration

directory(local)

seedfile

seedfile

Trap adapter configuration file: trapd.conf 81


The following portions of the trapd.conf file are of interest to this discussion. Table 6 on page 82 presents detailed descriptions of the configuration parameters in the trapd.conf file.

# trapd.conf - Configuration file for SNMP Trap Adapter...# Following is a list of parameters with a brief description.# More information is available at the end of this file.## PORT UDP port number the trap adapter listens to.## WINDOW De-duplication window, in seconds.## ASCII Controls formatting of non-printable characters.## TAG Enables tagging of varbind values.## ENABLE_FWD Enables trap forwarding.## MATCH Determines whether traps are tested against all forwarding # criteria or up to the first criterion that matches.## FORWARD Specifies matching criteria for traps and the forwarding # destinations for matched traps.

############ Set the parameters here.

PORT: 9000

#WINDOW: 10

#ASCII: FALSE

#TAG: FALSE

ENABLE_FWD: TRUE

#MATCH: all

#QUEUE_LIMIT_MEGS: 0

#QUEUE_LIMIT_SECONDS: 0...# Traps required by InCharge IP Availability Manager (AM)## Generic: coldStart, warmStart, LinkUp, LinkDown#FORWARD: * .* <0-3> * host:port...# Traps required by InCharge IP Performance Manager (PM)## Cisco: EnvMon Voltage, Temperature, Fan, RedundantSupply#FORWARD: * .1.3.6.1.4.1.9.9.13.3 6 <2-5> host:port...



Table 6 Detailed descriptions of configuration parameters in the trapd.conf file (page 1 of 2)

Parameter Description

PORT UDP port number on which the trap receiver or trap adapter listens for traps.Valid values are 0-65535. The default port is 9000.

WINDOW De-duplication window, in seconds. The maximum amount of time between receiving similar traps before the second trap is considered unique.Valid values are nonnegative integers, including 0. The default is 0.If not set or set to 0, the de-duplication feature is disabled, meaning that all traps are considered unique.

ASCII No longer used; should remain FALSE (default).

TAG Enables tagging of variable-binding (varbind) values.Valid values are TRUE and FALSE. The default is FALSE.• When TRUE, the type of the varbind value appears before each value; for example,

INTEGER-32 3.• When FALSE, the type of the varbind value does not appear before each value.

QUEUE_LIMIT_MEGS Limits the size of internal trap queue to the stated size, in megabytes.Valid values are nonnegative integers, including 0. The default is 0, which means that there is no limit on the size of the internal trap queue.

Note: The limit is not exact: The queue may grow slightly larger than the value specified.

When the limit is reached, some traps will be discarded.

QUEUE_LIMIT_SECONDS Limits the time that a trap can spend in the internal trap queue, in seconds.Valid values are nonnegative integers, including 0. The default is 0, which means that there is no limit on the time that a trap can spend in the internal trap queue.

Note: This limit is even less exact than the limit set for QUEUE_LIMIT_MEGS. In general, you should specify values for both QUEUE_LIMIT_MEGS and QUEUE_LIMIT_SECONDS.

When the limit is reached, some traps will be discarded.

ENABLE_FWD Determines whether uncommented FORWARD parameters are enabled or disabled.Valid values are TRUE and FALSE. The default is TRUE.• When TRUE, uncommented FORWARD parameters are enabled: Trap forwarding statements

specified in uncommented FORWARD parameters are read.• When FALSE, uncommented FORWARD parameters are disabled: Trap forwarding statements

specified in uncommented FORWARD parameters are not read.

MATCH Determines whether traps are tested against all matching criteria specified in an uncommented FORWARD parameter, or tested up to the first criterion that matches.Valid values are “all” or “first.” The default is “first.”If no uncommented FORWARD parameters are specified, the MATCH parameter is ignored.

Trap adapter configuration file: trapd.conf 83


FORWARD Specifies matching criteria for traps and the forwarding destinations for matched traps.Valid syntax is:

<source device address> <OID> <generic type> <specific type> \<destination host address>[:<port>|:<port>:<community>] \

[<destination host address>[:<port>|:<port>:<community>]] ...where:• <source device address> is the IP address of the object (SNMP agent) generating the trap.• <OID> is the sysObjectID of the type of object generating the trap.• <generic type> is the generic trap type:

0 coldStart1 warmStart2 linkDown3 linkUp4 authenticationFailure5 egpNeighborLoss6 enterpriseSpecific

Valid syntax for <generic type> is a generic specific trap number (for example, 3), a range of generic specific trap numbers (for example, <3-5>), or any generic specific trap number (for example, *). An asterisk is a wildcard character that matches any arbitrary string of characters.

• <specific type> is the specific trap code, present even if <generic type> is not enterpriseSpecific (6).Valid syntax for <specific type> is an enterprise specific trap number (for example, 733), a range of enterprise specific trap numbers (for example, <130-156>), or any enterprise specific trap number (for example, *).

• <destination host address> is the IP address (for example, 192.35.144.12) or the hostname (for example, myserver.example.com) of the destination host.

• <port> is the trap listening port on the destination host. Port is optional; if not specified, port defaults to 162.

• <community> is the community string to be assigned to the community string field in the forwarded traps. Community is optional; if not specified, community defaults to the value specified in the community string field of the incoming v1 or v2c trap, and defaults to an empty string for an incoming v3 trap.

Wildcards (for globbing) are allowed for all fields except destination host address, port, and community. Wildcard syntax is discussed in Appendix A, “Wildcard Patterns.”

Examples:

FORWARD: * .* * * snake:9099:public1All traps received from all network devices will be sent to port 9099 on a host named “snake”; the community string “public1” will be assigned to the forwarded traps.

FORWARD: 193.20.*.* .* <0-5> * obelix:7000 surya 194.56.78.23:9000All generic traps (0 to 5) from network devices whose address matches 193.20.*.* will be sent to port 7000 on a host named “obelix”; to port 162 on a host named “surya”; and to port 9000 on a host identified by address 194.56.78.23.

Other trap forwarding examples are presented at the end of the trapd.conf file.

Table 6 Detailed descriptions of configuration parameters in the trapd.conf file (page 2 of 2)

Parameter Description



Configuring the SNMP trap integration componentsBefore starting the SNMP trap integration components in a VoIP Availability Manager deployment, you must configure them so that they can receive, distribute, and process traps properly at startup.

The configuration steps are:

◆ “Configure the trap exploder” to receive traps from the managed network devices and to distribute Avaya and Nortel VoIP traps to VoIP Availability Manager, network traps to IP Availability Manager, VoIP informational traps to the VoIP Notification Trap Adapter, and non-VoIP informational traps to the SNMP Trap Adapter configured as a trap receiver.

◆ “Configure the built-in trap receivers” of VoIP Availability Manager and IP Availability Manager to receive the traps forwarded by the trap exploder.

◆ “Configure the VoIP Notification Trap Adapter” to receive the VoIP informational traps forwarded by the trap exploder and to convert the traps into EMC Smarts notifications.

◆ “Configure the trap receiver” to receive the non-VoIP informational traps forwarded by the trap exploder and to convert the traps into EMC Smarts notifications.

◆ “Configure the Adapter Platform” to import topology from VoIP Availability Manager and IP Availability Manager for the purpose of associating EMC Smarts notifications with the appropriate topology objects.

Configure the trap exploderTo configure the SNMP Trap Adapter configured as a trap exploder, you open and edit the Service Assurance BASEDIR/smarts/conf/trapd/trapd.conf file to forward the appropriate traps to VoIP Availability Manager, IP Availability Manager, the VoIP Notification Trap Adapter, and the SNMP Trap Adapter configured as a trap receiver. You use the FORWARD parameter in the trapd.conf file to determine which incoming traps are sent to what destinations. The traps to be forwarded to VoIP Availability Manager and to the VoIP Notification Trap Adapter are listed in the following files in the VoIP Management Suite installation area:

◆ BASEDIR/smarts/conf/voip/avaya/avaya-trapd.conf

Contain a list of Avaya VoIP traps to be used by VoIP Availability Manager for analysis purposes, and a list of Avaya VoIP informational traps to be converted to notifications by the VoIP Notification Trap Adapter and used by console users for informational purposes.

◆ BASEDIR/smarts/conf/voip/nortel/cisco-trapd.conf

Contain a list of Cisco VoIP informational traps to be converted to notifications by the VoIP Notification Trap Adapter and used by console users for informational purposes.

◆ BASEDIR/smarts/conf/voip/cisco/nortel-trapd.conf

Contain a list of Nortel VoIP traps to be used by VoIP Availability Manager for analysis purposes, and a list of Nortel VoIP informational traps to be converted to notifications by the VoIP Notification Trap Adapter and used by console users for informational purposes.

Configuring the SNMP trap integration components 85


In addition to configuring the trapd.conf file, you need to configure the managed network devices to forward SNMP traps to the host where the trap exploder is running, and to the port on which the trap exploder is listening for traps.

If the --port=<port number> option is not specified in the trap exploder’s startup command, the trap exploder listens for traps on the port specified by the PORT parameter in the trapd.conf file (port 9000 by default), or port 162 if no PORT value is specified in the trapd.conf file. The trap exploder startup options are described in “Start the trap exploder” on page 93.

Figure 19 on page 85 maps the steps (circled numbers) in the trap exploder configuration procedure to the configured forwarded trap paths.

Figure 19 Mapping of trap exploder configuration steps to configured forwarded trap paths

VoIP analysis traps(v1, v2c)

Traps(v1, v2c)

SNMPTrap Adapter

(exploder)

VoIPNotification

Trap Adapter

VoIPinformational traps

(v1, v2c)

Network traps

(v1, v2c)


SNMPTrap Adapter

(receiver)

Non-VoIPinformational traps

(v1, v2c)

IP network(with VoIP devices)

Discarded,unwanted

traps


2

3

45



To configure the trapd.conf file for the trap exploder:

1. Go to the BASEDIR/smarts/bin directory in the Service Assurance Management Suite installation area and type the following command to open the trapd.conf file:

sm_edit conf/trapd/trapd.conf

Press Enter.

2. To forward Avaya and Nortel VoIP traps to VoIP Availability Manager, copy and paste the following FORWARD entries from the avaya-trapd.conf and nortel-trapd.conf files to the trapd.conf file.

Uncomment (remove the leading # character from) the forwarding statements that you would like to use. For the uncommented forwarding statements, specify the <host name>:<port no> (for example, myserver.example.com:9001) of the VoIP Availability Manager destination that is to receive the trap messages.

Note: By default, the VoIP Availability Manager built-in trap receiver is disabled. The procedure to enable the built-in trap receiver and to set a trap listening port is given in “Configure the built-in trap receivers” on page 90.

Note: FORWARD entry examples and their definitions are given in Table 6 on page 82.

# Avaya VoIP analysis traps copied from avaya-trapd.conf file# Forward Avaya Media Server Traps#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.1.8.1 6 0

<host name>:<port no> ## Clear#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.1.8.1 6 1

<host name>:<port no> ## Critical#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.1.8.1 6 2

<host name>:<port no> ## Major#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.1.8.1 6 3

<host name>:<port no> ## Minor#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.1.8.1 6 4

<host name>:<port no> ## Warning#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.1.8.1 6 12

<host name>:<port no> ## Resolved

# Forward Avaya Media Gateway Traps#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.2.9.1.5.2.2 6 73

<host name>:<port no> ## cmgRegistrationSuccess#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.2.9.1.5.2.2 6 106

<host name>:<port no> ## cmgRegistrationFault#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.2.9.1.5.2.2 6 102

<host name>:<port no> ## cmgPrimaryControllerFault#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.2.9.1.5.2.2 6 103

<host name>:<port no> ## cmgNoControllerFault#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.2.9.1.5.2.2 6 105

<host name>:<port no> ## cmgNoControllerClear#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.2.9.1.5.2.2 6 108

<host name>:<port no> ## cmgH248LinkDown#FORWARD: *.*.*.* .1.3.6.1.4.1.6889.2.9.1.5.2.2 6 109

<host name>:<port no> ## cmgH248LinkClear#FORWARD: *.*.*.* .1.3.6.1.4.1.1751.2.9.1.5.2.2 6 73

<host name>:<port no> ## cmgRegistrationSuccess#FORWARD: *.*.*.* .1.3.6.1.4.1.1751.2.9.1.5.2.2 6 106

<host name>:<port no> ## cmgRegistrationFault#FORWARD: *.*.*.* .1.3.6.1.4.1.1751.2.9.1.5.2.2 6 102

<host name>:<port no> ## cmgPrimaryControllerFault#FORWARD: *.*.*.* .1.3.6.1.4.1.1751.2.9.1.5.2.2 6 103

<host name>:<port no> ## cmgNoControllerFault



#FORWARD: *.*.*.* .1.3.6.1.4.1.1751.2.9.1.5.2.2 6 105 <host name>:<port no> ## cmgNoControllerClear

#FORWARD: *.*.*.* .1.3.6.1.4.1.1751.2.9.1.5.2.2 6 108 <host name>:<port no> ## cmgH248LinkDown

#FORWARD: *.*.*.* .1.3.6.1.4.1.1751.2.9.1.5.2.2 6 109 <host name>:<port no> ## cmgH248LinkClear

# Nortel VoIP analysis traps copied from nortel-trapd.conf file#FORWARD: *.*.*.* .1.3.6.1.4.1.562.3.3.5 6 10

<host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.562.3.21.5.4.1 6 1



<host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.562.37.3.1 6 3

<host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.562.3.10.10.1 6 1



<host name>:<port no>

3. To forward network traps to IP Availability Manager, add your choice of FORWARD entries to the trapd.conf file.

The following commented-out lines are the predefined FORWARD statements for IP Availability Manager and IP Performance Manager in the trapd.conf file.

Uncomment the forwarding statements that you would like to use. For the uncommented forwarding statements, specify the <host>:<port> (host name and port number) of the IP Availability Manager destination that is to receive the trap messages.

Note: By default, the IP Availability Manager built-in trap receiver listens for traps on port 9000. The procedure to change this port number is given in “Configure the built-in trap receivers” on page 90.

# Traps required by InCharge IP Availability Manager (AM)## Generic: coldStart, warmStart, LinkUp, LinkDown#FORWARD: * .* <0-3> * host:port

# Cisco: STACK module inserted, removed#FORWARD: * .1.3.6.1.4.1.9.5 6 <3-4> host:port

# 3Com: CoreBuilder 9000 module inserted#FORWARD: * .1.3.6.1.4.1.43.28.2 6 6 host:port

# AI: SLC card down, up#FORWARD: * .1.3.6.1.4.1.539 6 10 host:port#FORWARD: * .1.3.6.1.4.1.539 6 111 host:port#FORWARD: * .1.3.6.1.4.1.629 6 10 host:port#FORWARD: * .1.3.6.1.4.1.629 6 111 host:port

## Cisco ISDN demandNbrLayer2Change##FORWARD: * .1.3.6.1.4.1.9.9.26.2 6 3 host:port

#



# Cisco cHsrpStateChange##FORWARD: * .1.3.6.1.4.1.9.9.106.2 6 1 host:port

## Traps required by InCharge IP Performance Manager (PM)## Cisco: EnvMon Voltage, Temperature, Fan, RedundantSupply#FORWARD: * .1.3.6.1.4.1.9.9.13.3 6 <2-5> host:port

4. To forward Avaya, Cisco, and Nortel VoIP traps to the VoIP Notification Trap Adapter, copy and paste the following FORWARD entries from the avaya-trapd.conf, cisco-trapd.conf, and nortel-trapd.conf files to the trapd.conf file.

Uncomment the forwarding statements that you would like to use. For the uncommented forwarding statements, specify the <host name>:<port no> of the VoIP Notification Trap Adapter destination that is to receive the trap messages.

Note: By default, the VoIP Notification Trap Adapter listens for traps on port 9000. Insight into how to change this port number is given in “Configure the VoIP Notification Trap Adapter” on page 90.

# Avaya VoIP informational traps copied from avaya-trapd.conf file#FORWARD: *.*.*.*

.1.3.6.1.4.1.311.1.13.1.10.103.118.95.118.115.101.114.118.101.114 6 2147482634 <host name>:<port no>

#FORWARD: *.*.*.* .1.3.6.1.4.1.311.1.13.1.10.103.118.95.118.115.101.114.118.101.114 6 1073742834 <host name>:<port no>




#FORWARD: *.*.*.* .1.3.6.1.4.1.311.1.13.1.11.103.118.95.99.109.115.101.114.118.101.1146 101 <host name>:<port no>



# Cisco VoIP informational traps copied from cisco-trapd.conf file# Cisco CallManager Express Traps#FORWARD: *.*.*.* .1.3.6.1.4.1.562.3.3.5 6 10 <host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.562.3.3.5 6 7 <host name>:<port no>

# Cisco Unity Express Traps#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.420 6 1 <host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.420 6 2 <host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.420 6 4 <host name>:<port no>

# Cisco Survivable Remote Site Telephony Traps#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.441 6 1 <host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.441 6 2 <host name>:<port no>



#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.190.2 6 2 <host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.190.2 6 1 <host name>:<port no>

#FORWARD: *.*.*.* .1.3.6.1.4.1.515.1004 6 1 <host name>:<port no>

# Content Engine Traps Traps#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.178.2 6 7 <host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.178.2 6 8 <host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.178.2 6 9 <host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.178.2 6 10 <host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.178.2 6 11 <host name>:<port no>#FORWARD: *.*.*.* .1.3.6.1.4.1.9.9.178.2 6 12 <host name>:<port no>

# Nortel VoIP informational traps copied from nortel-trapd.conf file#FORWARD: *.*.*.* .1.3.6.1.4.1.562.3.21.5.4.1 6 1





<host name>:<port no>

5. To forward non-VoIP informational traps to the SNMP Trap Adapter configured as a trap receiver, add your choice of FORWARD entries to the trapd.conf file. Specify the <host name>:<port no> of the trap receiver destination that is to receive the trap messages.

Note: By default, the trap receiver listens for traps on port 9000. Insight into how to change this port number is given in “Configure the trap receiver” on page 91.

# Traps for Trap Receiver and Adapter Platform<Add your matching criteria for the traps and the forwarding destination: the IP address and trap port of the trap receiver.>

6. Ensure that the ENABLE_FWD parameter is TRUE (default).

7. Save the file. The modified version of the trapd.conf file is saved to the BASEDIR/smarts/local/conf/trapd directory in the Service Assurance Management Suite installation area.

Any received trap not matching any of the FORWARD entries is discarded.



Configure the built-in trap receivers

To configure the VoIP Availability Manager built-in trap receiver:

Follow the procedure in “Enabling trap reception” on page 36 to enable the built-in trap receiver and to set its port number to the destination port specified for VoIP Availability Manager in the trap exploder’s trapd.conf file.

To configure the IP Availability Manager built-in trap receiver:

1. Go to the BASEDIR/smarts/bin directory in the IP Management Suite installation area and type the following command to open the trapd.conf file:

sm_edit conf/trapd/trapd.conf

Press Enter.

2. Set the port number of the following PORT entry to the destination port specified for IP Availability Manager in the trap exploder’s trapd.conf file:

PORT: <port number>

Note: A valid port number is 162 or any value in the range 2049 to 65534 inclusive.

3. Save and close the file. The modified version of the trapd.conf file is saved to the BASEDIR/smarts/local/conf/trapd directory in the IP Management Suite installation area.

4. If IP Availability Manager was running before you edited the trapd.conf file, restart IP Availability Manager.

Configure the VoIP Notification Trap AdapterNo configuration is required for the VoIP Notification Trap Adapter to process VoIP informational traps received from the SNMP Trap Adapter configured as a trap exploder, unless you choose to customize the trap definitions in one or more of the following trap_mgr.conf files in the VoIP Availability Manager BASEDIR/smarts/conf/voip/icoi directory:

◆ avaya_trap_mgr.conf

◆ cisco_trap_mgr.conf

◆ nortel_trap_mgr.conf

◆ default_trap_mgr.conf

Each vendor-specific trap to be transformed into a notification has an uncommented trap definition entry in the corresponding <vendor>_trap_mgr.conf file. The default_trap_mgr.conf file contains (1) BATCH_NOTIFY_INTERVAL configurations, which can be used to define the Batch Notify Interval to batch the updates to notifications, and (2) default rules, which can be used to define trap definitions that are not defined in the <vendor>_trap_mgr.conf files. Trap definitions are described in the EMC Smarts Service Assurance Manager Adapter Platform User Guide.

A <vendor>_trap_mgr.conf file contains rules that the VoIP Notification Trap Adapter uses to map incoming traps into the data fields of an EMC Smarts notification. The Adapter Platform, in turn, creates the EMC Smarts notification object from the data fields and exports the notification to the Global Manager.



If the --port=<port number> option is not specified in the VoIP Notification Trap Adapter’s startup command, the trap exploder listens for traps on the port specified by the PORT parameter in the VoIP Availability Manager BASEDIR/smarts/conf/voip/trapd.conf file (port 9000 by default), or port 162 if no PORT value is specified in the trapd.conf file. The VoIP Notification Trap Adapter startup options are described in “Start the VoIP Notification Trap Adapter” on page 95.

To customize trap definitions in a <vendor>_trap_mgr.conf file:

1. Go to the BASEDIR/smarts/bin directory in the VoIP Management Suite installation area and type the following command to open the target <vendor>_trap_mgr.conf file:

sm_edit conf/voip/icoi/<vendor>_trap_mgr.conf

Press Enter.

2. Make your changes to the trap definitions.

3. Save the file. The modified version of the <vendor>_trap_mgr.conf files is saved to the BASEDIR/smarts/local/conf/voip/icoi directory in the VoIP Management Suite installation area.

Configure the trap receiverTo configure an SNMP Trap Adapter as a trap receiver to process non-VoIP informational traps received from the SNMP Trap Adapter configured as a trap exploder, you edit the Service Assurance BASEDIR/smarts/conf/icoi/trap_mgr.conf file to define how the trap receiver processes traps into notifications. Each trap to be transformed into a notification requires a trap definition entry in the trap_mgr.conf file.

The trap_mgr.conf file contains rules that the trap receiver uses to map incoming traps into the data fields of an EMC Smarts notification. The Adapter Platform, in turn, creates the EMC Smarts notification object from the data fields and exports the notification to the Global Manager.

If the --port=<port number> option is not specified in the trap receiver’s startup command, the trap receiver listens for traps on the port specified by the PORT parameter in the Service Assurance BASEDIR/smarts/conf/icoi/trapd.conf file (port 9000 by default), or port 162 if no PORT value is specified in the trapd.conf file. The trap exploder startup options are described in the EMC Smarts Service Assurance Manager Adapter Platform User Guide and the EMC Smarts Service Assurance Management Suite Installation Guide.

To configure the trap_mgr.conf file for the trap receiver:

1. Go to the BASEDIR/smarts/bin directory in the Service Assurance Management Suite installation area and type the following command to open the trap_mgr.conf file:

sm_edit conf/icoi/trap_mgr.conf

Press Enter.



2. Define a trap definition for each received trap.

For each SNMP trap, you must specify how the information in the trap maps to objects in the Global Manager repository and how the notification should appear at the Global Console.

3. Save the file. The modified version of the trap_mgr.conf file is saved to the BASEDIR/smarts/local/conf/icoi directory in the Service Assurance Management Suite installation area.

Configure the Adapter Platform

To configure the Adapter Platform, you attach the Global Manager to the Adapter Platform and specify the underlying IP Availability Manager and VoIP Availability Manager domains. Doing so enables the Adapter Platform to import hostnames and IP addresses from the underlying domains so that it can accurately relate events in received traps to the devices (systems) associated with the events. The Adapter Platform creates EMC Smarts notification objects from the events and exports the notifications to the Global Manager.

The procedure is identical to the procedure for specifying underlying domains for the Global Manager. That procedure is presented in “Specifying the underlying domains” on page 59.

To attach the Global Manager Administration Console to your Adapter Platform:

1. In the Global Manager Administration Console, select Manager > Attach to display the Attach Manager dialog box.

2. In the Attach Manager dialog box, enter the Adapter Platform name and the login information (for example, admin and changeme) and click OK.

3. In the Global Manager Administration Console, select the Adapter Platform name from the Manager drop-down menu.

The EMC Smarts Service Assurance Manager Adapter Platform User Guide provides a complete description of the Adapter Platform.

Starting the SNMP trap integration components 93


Starting the SNMP trap integration componentsIn a VoIP Availability Manager deployment, you install the EMC Smarts Broker, VoIP Availability Manager, IP Availability Manager, Global Manager, Global Console, Adapter Platform, and SNMP Trap Adapter (receiver) products as services so that the host system automatically starts them as processes running in the background each time that the system boots. The respective installation guides—EMC Smarts VoIP Availability Manager Installation Guide, EMC Smarts IP Management Suite Installation Guide, and EMC Smarts Service Assurance Management Suite Installation Guide—for these products describe the services in detail.

Currently, you cannot install the SNMP Trap Adapter (exploder) and the VoIP Notification Trap Adapter as services, but you can use the sm_service command to register these adapters as services after the installation. This section describes how to create and start services for these two adapters.

Note: Typically, in any EMC Smarts deployment, the order in which the applications are started is not important, except that the Broker must be started first.

Start the trap exploder

Use the sm_service command to manually create a service for the SNMP Trap Adapter configured as a trap exploder. A typical service command on a UNIX host would look like this:

/opt/InCharge7/SAM/smarts/bin/sm_service install--force--unmanaged--startmode=runonce--name=ic-trap-exploder--description=”EMC Smarts SNMP Trap Exploder”/opt/InCharge7/SAM/smarts/bin/sm_trapd--name=INCHARGE-EXPLODER--config=trapd--port=162--rules=default--output

where:

◆ --name=<name>

(Second --name option in service command): Specifies the trap exploder name to be registered with the Broker for the deployment. Also -n <name>.

◆ --config=<cfg>

Specifies the configuration directory in which the trapd.conf file for the trap exploder is located. The trapd.conf file is loaded from the BASEDIR/smarts/local/conf/<cfg> directory, or from the BASEDIR/smarts/conf/<cfg> directory if the trapd.conf file is not present in the local directory. The default configuration (<cfg>) directory for the trap exploder is trapd.

Note: Ensure that --config is set to trapd in the trap exploder service command.



◆ --port=<trap listening port>

Specifies the port number to which the managed network devices send traps and on which the trap exploder listens for traps. Also -p <trap listening port>.

The default trap listening port is the PORT parameter value in the <cfg>/trapd.conf file (port 9000 by default), or port 162 if no PORT value is specified in the <cfg>/trapd.conf file.

◆ --sport=<Remote API listening port>

Specifies the port number on which the trap exploder listens for Remote API connections from other EMC Smarts programs—the Global Console, servers, and utilities such as dmctl. This option is meaningful only if the --name option is specified. Also -P <Remote API listening port>.

The --sport option for the sm_trapd program plays the same role as the --port option plays for any other EMC Smarts program. The --sport option is unique to the sm_trapd program and defaults to 0.

Note: --sport=0 is interpreted by the host operating system as meaning “assign this program a unique, unused port number.” Typically, the operating system responds by assigning a unique, unused port number in the range 40000–65535.

◆ --rules=default

Specifies the rule set to be used by the trap exploder. The default rule set is defined in the BASEDIR/smarts/rules/trapd/trapParse.asl file.

◆ --output

Specifies that the stdout and stderr output for the trap exploder should be redirected to a log file in the BASEDIR/smarts/local/logs directory. The name of the log file is INCHARGE-EXPLODER.log.

The command for starting the example service is:

/opt/InCharge7/SAM/smarts/bin/sm_service start ic-trap-exploder

At startup, the trap exploder reads the trapd.conf file and saves the configuration information in its repository.

Note: The EMC Smarts System Administration Guide provides more details about sm_service.

Starting the SNMP trap integration components 95


Start the VoIP Notification Trap Adapter

Use the sm_service command to manually create a service for the VoIP Notification Trap Adapter. A typical service command on a UNIX host would look like this:

/opt/InCharge7/VoIP/smarts/bin/sm_service install--force--unmanaged--startmode=runonce--name=ic-voip-notification-trapd-receiver--description=”EMC Smarts VoIP Notification Trap Adapter”/opt/InCharge7/VoIP/smarts/bin/sm_trapd--name=TRAP-INCHARGE-VOIP--server=INCHARGE-OI--config=voip--port=162--model=sm_actions--rules=voip/trap_mgr_parse.asl--output

where:

◆ --name=<name>

(Second --name option in service command): Specifies the VoIP Notification Trap Adapter name to be registered with the Broker for the deployment. Also -n <name>.

◆ --server=<name>

Specifies the name of the Adapter Platform that is to receive the processed traps from the VoIP Notification Trap Adapter. The Adapter Platform uses the processed traps to create EMC Smarts notification objects.

◆ --config=<cfg>

Specifies the configuration directory in which the icoi/avaya_trap_mgr.conf, icoi/cisco_trap_mgr.conf, icoi/nortel_trap_mgr.conf, and trapd.conf configuration files for the VoIP Notification Trap Adapter are located. A configuration file is loaded from the BASEDIR/smarts/local/conf/<cfg> directory, or from the BASEDIR/smarts/conf/<cfg> directory if the configuration file is not present in the local directory. The default configuration (<cfg>) directory for the VoIP Notification Trap Adapter is voip.

Note: Ensure that --config is set to voip in the VoIP Notification Trap Adapter service command.

◆ --port=<trap listening port>

Specifies the port number to which the managed network devices send traps and on which the VoIP Notification Trap Adapter listens for traps. Also -p <trap listening port>.

The default trap listening port is the PORT parameter value in the <cfg>/trapd.conf file (port 9000 by default), or port 162 if no PORT value is specified in the <cfg>/trapd.conf file.



◆ --sport=<Remote API listening port>

Specifies the port number on which the VoIP Notification Trap Adapter listens for Remote API connections from other EMC Smarts programs—the Global Console, servers, and utilities such as dmctl. This option is meaningful only if the --name option is specified. Also -P <Remote API listening port>.

The --sport option for the sm_trapd program plays the same role as the --port option plays for any other EMC Smarts program. The --sport option is unique to the sm_trapd program and defaults to 0.

Note: --sport=0 is interpreted by the host operating system as meaning “assign this program a unique, unused port number.” Typically, the operating system responds by assigning a unique, unused port number in the range 40000–65535.

◆ --model=sm_actions

Specifies the name of the model library to be loaded by the VoIP Notification Trap Adapter.

◆ --rules=voip/trap_mgr_parse.asl

Specifies the rule set to be used by the VoIP Notification Trap Adapter. The rule set used is defined in the BASEDIR/smarts/rules/voip/trap_mgr_parse.asl file.

◆ --output

Specifies that the stdout and stderr output for the VoIP Notification Trap Adapter should be redirected to a log file in the BASEDIR/smarts/local/logs directory. The name of the log file is TRAP-INCHARGE-VOIP.log.

The command for starting the example service is:

/opt/InCharge7/SAM/smarts/bin/sm_service start ic-voip-notification-trapd-receiver

At startup, the VoIP Notification Trap Adapter reads its configuration files and saves the configuration information in its repository.

Using the Polling and Thresholds Console 97

7

This chapter introduces the Polling and Thresholds Console, defines groups and settings, and provides instructions on using the Polling and Thresholds Console to work with groups and settings. It consists of the following sections:

◆ Opening the Polling and Thresholds Console .......................................................... 98◆ Understanding groups and settings ......................................................................... 100◆ Working with groups and settings ........................................................................... 101

Using the Polling andThresholds Console


Using the Polling and Thresholds Console

Opening the Polling and Thresholds ConsoleThe Polling and Thresholds Console is used to display groups and modify their properties. In the example display in Figure 20 on page 98, the Polling and Thresholds Console is attached to a VoIP Availability Manager named VoIP-AM.

Note: Instructions for opening the Polling and Thresholds Console are presented in Chapter 3, “Opening the Global Console.”

Figure 20 Polling and Thresholds Console—example

Group Tree Group Configuration Window

Opening the Polling and Thresholds Console 99


Layout of the Polling and Thresholds Console

What tabs appear on a Polling and Thresholds Console depends on the type of Domain Manager to which the console is attached. When attached to IP Availability Manager or IP Performance Manager, for example, the Polling and Thresholds Console contains four tabs:

◆ Polling

Enables administrators to control the polling of the managed objects for monitoring purposes.

◆ Thresholds

Enables administrators to set thresholds for the polled data.

◆ Device Access

Enables administrators to specify an access protocol and credentials (such as login credentials) for device access.

◆ Tagging

Enables administrators to create IP tagging filters.

Note: When attached to other Domain Managers, the Polling and Thresholds Console contains the Polling, Thresholds, and Device Access tabs or just the Polling tab. The Tagging tab are unique to IP Availability Manager and IP Performance Manager.

The Polling and Thresholds Console is divided into two panels.

◆ The left panel displays the icon for the Domain Manager in the upper-left corner and provides one, two, or four tabs, depending on the Domain Manager to which the Polling and Thresholds Console is attached. Selecting a tab shows what groups, settings, and members are available on the tab.

◆ The right panel remains blank until a group, setting, or member is selected in the left panel. When an item is selected in the left panel, the right panel displays additional information regarding that item.

Polling and Thresholds Console toolbar buttonsThe toolbar of the Polling and Thresholds Console provides quick access to the commands described in Table 7 on page 99.

Table 7 Polling and Thresholds Console toolbar buttons

Button Description

Attach to a Smarts Manager

Detach from a Smarts Manager

Reconfigure: reapply polling/threshold values, update instrumentation, recompute codebook, and so on

Delete the selected item



Understanding groups and settingsA group contains one or more settings, and a setting contains one or more parameters. Managed objects (systems discovered in the managed environment) become members of a group based on the matching criteria defined for the group.

Figure 21 on page 100 illustrates the relationships between managed objects, groups, and settings.

Figure 21 Relating managed objects to groups and settings

◆ The EMC Smarts ICIM core class for group (in the sense of "groups and settings") is ICIM_Configuration. This class is the parent of all group classes used by VoIP Availability Manager or any other EMC Smarts Domain Manager.

◆ The ICIM core class for setting is ICIM_Setting. This class is the parent of all setting classes used by VoIP Availability Manager or any other EMC Smarts Domain Manager.

◆ The ICIM core class for managed object is ICIM_ManagedElement. This class is the parent of all managed object classes used by VoIP Availability Manager or any other EMC Smarts Domain Manager.

A setting consists ofone or more parameters

(attributes)

ConfiguredByICIM_ManagedElement

SettingsAppliedTo

ICIM_Configuration

ICIM_Setting

ComposedOf

When a managed object matchesthe matching criteria defined for a group,

it becomes a member of that group

A group consists ofone or more settings

The setting parameters for a groupof which the managed object is a member

are applied to the managed object

Working with groups and settings 101


Working with groups and settingsUsing the Polling and Thresholds Console, you can change the parameter values for a group. You can also:

◆ Add settings to a group.

◆ Remove settings from a group.

◆ Change the matching criteria defined for a group.

◆ Create new groups.

◆ Prioritize the order of groups within a group category.

How managed objects are assigned to groupsWhen VoIP Availability Manager performs discovery, it automatically assigns each managed object to one or more groups based on:

◆ The matching criteria defined for a group.

◆ The priority of a group, which determines membership when an object meets the matching criteria for more than one group within a particular group category.

A managed object may be a member of one and only one group within a particular group category.

Modifying the properties of a groupA group’s matching criteria and priority determine which managed objects become members of the group.

When a group is selected in the left panel of the Polling and Thresholds Console, four tabs appear in the right panel of the console:

◆ Settings

◆ Priorities

◆ Matching Criteria

◆ Description

Modifying the properties in the Settings, Priorities, or Matching Criteria tab changes the configuration of the group. When you finish editing the properties of a group, click the Apply button to save the changes, and then click the Reconfigure toolbar button or select Reconfigure from the Group menu to make the configuration changes take effect.

Adding or removing settingsA group’s settings determine what parameters are applied to the managed objects that are members of the group.

The Settings tab is divided into two sections: Current Settings and Available Settings. The Current Settings section lists the settings that are applied to the group. The Available Settings section lists additional available settings.



To add or remove a setting:

1. In the Settings tab, select a setting in the Available Settings list or in the Current Settings list.

2. Click Add to move an available setting to the Current Settings list, or click Remove to move a current setting to the Available Settings list.

3. Click Apply to save your changes.

4. Click Reconfigure to implement your changes.

Modifying the parameters of a setting

The parameters of a setting are changed in one of two ways:

◆ By choosing a value from a drop-down menu

◆ By entering a value in a Value field or adjusting a slider bar representing a range of values

Changing the parameters of a settingTo change the parameters of a setting:

1. In the left panel of the Polling and Thresholds Console, select the setting to display the parameters of the setting in the right panel of the console.

2. Change the value of a parameter using one of the following methods:

For a drop-down menu, click the menu and select a value.

For a slider bar presentation,

• Type a value into the Value field and press Enter or

• Select the slider bar and drag its handle with the mouse to change the value or select the slider bar and use the arrow keys to move its handle to change the value.



Restoring the default values of a settingTo restore the default values of a setting:

1. In the left panel of the Polling and Thresholds Console, select the setting to display the parameters of the setting in the right panel of the console.

2. Click Restore Defaults.


Modifying the priority of groups

In any group category, you can arrange the groups in a high-to-low priority. A candidate member object is compared against the highest priority group first and becomes a member of the first group for which there is a criteria match.

The Priorities tab shows groups in the order of their priority, from highest to lowest.

Working with groups and settings 103


To change the priority of a group:

1. In the Priorities tab, select the group for which you want to change the priority.

2. Click the up or down arrow to change its position relative to the other groups.



Editing matching criteria

A group’s matching criteria, which appear at the top of the Matching Criteria tab, are defined using the attributes of the target class associated with the group. Each matching criterion has three fields: Name, Description, and Value.

◆ Name identifies the name of the target class attribute.

◆ Description is the description of the target class attribute.

◆ Value is the value of the target class attribute, which can be any combination of text, integers, and wildcards. The Value field for a matching criterion is not case-sensitive.

As an example of a matching criterion for target class UnitaryComputerSystem, if you specify "Router" for the Type attribute, only routers become members of the group; if you specify "R1*" for the Name attribute, only routers having names beginning with the string R1 become members of the group. Appendix A, “Wildcard Patterns,” discusses wildcard syntax.

When a managed object matches a group’s target class and matches all of the attributes defined for the target class, the managed object becomes a member of the group.

Adding or removing matching criteriaTo add or remove matching criteria:

1. In the Disabled Criteria area of the Matching Criteria tab, select a matching criterion.

2. Click Enable to make the criterion active, moving it to the top of the Matching Criteria tab.

Use Disable to deactivate the criterion, moving it to the Disabled Criteria area of the Matching Criteria tab.

3. If you are adding a matching criterion, type a matching pattern in the Value field.



Changing the value of a matching criterionTo change the value of a matching criterion:

1. In the Matching Criteria tab, select the string in the Value field or double-click the Value field to highlight the current value.

2. Type the new value.





VoIP Availability Manager compares a managed object against the matching criteria of the group with the highest priority. If an object matches all the criteria, VoIP Availability Manager adds the object as a member of the group. Otherwise, VoIP Availability Manager compares the object against the matching criteria of the group with the second highest priority, and so on.

Creating new groups

You can create additional groups within any group category.

Creating a new group enables you to customize the settings for a group of managed objects. You can use two methods to create a new group:

◆ Copy an existing group. The new group contains the same settings and thresholds as the original group. Matching criteria are not copied.

◆ Create an empty group. The new group does not contain any settings or members. You must add settings and matching criteria, and set the priority of the new group.

After you create a new group, use the procedures previously described in this chapter to add settings and matching criteria and to set the priority of the new group.

Copying an existing groupTo copy an existing group:

1. In the left panel of the Polling and Thresholds Console, right-click the group that you want to copy.

2. Select Copy from the pop-up menu to display the Copy Group dialog box.

3. In the dialog box, type a name and an optional description for the new group and click OK.

The new group contains the same settings and thresholds as the group you copied.

4. Edit the settings, matching criteria, and priority of the new group. Change the value of any parameters as necessary.


Creating an empty groupTo create an empty group:

1. In the left panel of the Polling and Thresholds Console, right-click the group for which you want to create a new group.

2. Select New Group from the pop-up menu to display the New Group dialog box.

3. In the dialog box, type a name and an optional description for the new group and click OK.

4. Add settings and matching criteria, and set the priority of the new group. Change the values of any thresholds or parameters as necessary.


Configuring Polling Groups 105

8

This chapter describes how to configure polling groups for VoIP Availability Manager. It consists of the following sections:

◆ Viewing the Polling tab .............................................................................................. 106◆ Understanding polling groups and settings ........................................................... 107◆ Default polling groups and settings ......................................................................... 108

Configuring PollingGroups


Configuring Polling Groups

Viewing the Polling tabFigure 22 on page 106 shows the Polling tab of a Polling and Thresholds Console connected to a VoIP Availability Manager named VoIP-AM. The right panel of the console identifies two default settings, “VoIP Performance Polling - External” and “VoIP Polling - External,” for a default polling group named "Avaya Card Based Services."

Figure 22 Polling tab for VoIP Availability Manager

Note: Instructions for opening the Polling and Thresholds Console are presented in Chapter 3, “Opening the Global Console.”

Polling Group Tree Polling Group Configuration Window

Understanding polling groups and settings 107


Understanding polling groups and settingsVoIP Availability Manager monitors the network by sending Simple Network Management Protocol (SNMP) polls and by processing SNMP traps, and by processing information from the VoIP Performance Manager. The results of the polling and trap processing are then compared to threshold values that define acceptable and unacceptable levels of availability. The polling and trap processing results, in conjunction with the status updates received from IP Availability Manager, are used to diagnose the failed objects that interrupt network service connectivity.

VoIP Availability Manager uses settings to assign polling and threshold parameters to groups of managed objects. From a polling and threshold perspective, a setting is a collection of parameters common to a particular type of analysis (for example, network services polling).

Using the Polling and Thresholds Console (shown in Figure 22 on page 106), you can customize SNMP polling and trap processing for VoIP Availability Manager by modifying default polling groups or by creating new polling groups. The polling groups periodically poll—or receive traps from—the managed devices to collect availability data for application services, network services, and other VoIP-related objects. The data serves as input to the correlation analysis function of VoIP Availability Manager.

Note: Appendix B, “Polling for Analysis,” describes SNMP polling for correlation analysis.

Modifying polling groupsProcedures for modifying existing polling groups and creating new ones are given in “Working with groups and settings” on page 101.

When you finish editing the properties of a group, you:

1. Click Apply to save the configuration changes to an existing group object or to a newly created group object in the repository of VoIP Availability Manager.

2. Click the Reconfigure toolbar button or select Reconfigure from the Group menu to make the configuration changes take effect.

When the reconfiguration completes, VoIP Availability Manager applies/reapplies the polling configured for the group object.



Default polling groups and settingsThe default polling categories, groups, and settings for VoIP Availability Manager are accessible via the Polling tab of the Polling and Thresholds Console.

Default polling categories and groupsVoIP Availability Manager provides the following polling group categories:

◆ VoIP Application Groups

◆ VoIP Card Services

◆ VoIP Clusters

◆ VoIP Network Service Groups

◆ VoIP Process Groups

◆ VoIP Redundancy Groups

Each category contains one or more default polling groups.

Note: In your Polling and Threshold Console, the polling categories, groups, and settings that appear will vary depending on the installed VoIP Management Suite products (the VoIP Performance Manager Integration Pack and enablement packs).

VoIP Application GroupsPolling groups for VoIP applications are used by VoIP Availability Manager to monitor the availability of VoIP application instances discovered on Cisco, Nortel, or Avaya devices. VoIP Availability Manager monitors the instances by probing the SNMP tables on the devices that are hosting the VoIP applications or by processing traps.

Table 8 on page 108 lists the default VoIP application polling groups, their matching criteria, and their settings. The matching-criteria target class for VoIP application polling groups is VoipApplication.

Two things to note about this table and the tables that follow:

◆ “SNMP” in “VoIP Polling - SNMP” implies status input obtained from SNMP polling, and “External” in “VoIP Polling - External” implies status input obtained from an external source. For the Nortel Applications group, for example, the status input is obtained from processing traps generated by the managed Nortel devices.

Table 8 Default VoIP Application groups

Polling group Matching criteria Settings

Cisco Applications VoipApplication attributes:• Vendor = CISCO

VoIP Polling - SNMP

Nortel Applications VoipApplication attributes:• Vendor = NORTEL

VoIP Polling - External

Avaya Applications VoipApplication attributes:• Vendor = AVAYA

VoIP Polling - SNMP

Default polling groups and settings 109


◆ Only a discovered object of the target type (or one of its subclasses) and matching the matching-criteria attribute(s) for a particular polling group becomes a member of that group. For the Cisco Applications group, for example, only a discovered object of type “VoipApplication” (or one of its subclasses) with attribute Vendor = CISCO becomes a member of the group.

You can specify additional matching criteria for a polling group to limit its membership, as explained in “Editing matching criteria” on page 103.

VoIP Card ServicesPolling groups for VoIP card services are used by VoIP Availability Manager to monitor the availability of the following card service instances discovered on Avaya S8x00 Media Servers:

◆ Control LAN (C-LAN)—a circuit card that provides an H.323 gatekeeper service

◆ Media Processor (MedPro)—a circuit card that provides a media processor service

◆ IP Server Interface (IPSI)—a circuit card that provides an IPSI service

◆ Voice Announcement on LAN (VAL)—a circuit card that provides a VAL service

VoIP Availability Manager monitors the card service instances by processing traps received from the card-service circuit cards, themselves, or from the hosting S8x00 Media Servers.

Table 9 on page 109 lists the default VoIP card service polling groups, their matching criteria, and their settings. The matching-criteria target class for VoIP card service polling groups is VoipCardService.

VoIP ClustersPolling groups for VoIP clusters are used by VoIP Availability Manager to monitor the availability of VoIP cluster instances discovered on Cisco or Avaya devices. VoIP Availability Manager monitors the instances by probing the SNMP tables on the devices that are hosting the VoIP applications or by processing traps.

Table 10 on page 109 lists the default VoIP cluster polling groups, their matching criteria, and their settings. The matching-criteria target class for VoIP cluster polling groups is VoipCluster.

Note: “External” in “VoIP Performance Polling - External” implies status input is obtained from VoIP Performance Manager. Nortel devices are not supported as members of VoIP clusters.

Table 9 Default VoIP Card Services groups


Avaya Card Based Services VoipCardService attributes:• Vendor = AVAYA• Type =

CLAN|MEDPRO|IPSI|VAL|DS1

• VoIP Polling - External• VoIP Performance Polling - External

Table 10 Default VoIP Clusters


VoIP Clusters VoipCluster attributes:• CreationClassName = VoipCluster

VoIP Performance Polling - External



VoIP Network Service GroupsPolling groups for VoIP network services are used by VoIP Availability Manager to monitor the availability of VoIP network service instances discovered on Cisco, Nortel, or Avaya devices. VoIP Availability Manager monitors the instances by probing the SNMP tables on the devices that are hosting the VoIP network services or by processing traps.

Table 11 on page 110 lists the default VoIP network service polling groups, their matching criteria, and their settings. The matching-criteria target class for VoIP network service polling groups is VoipNetworkService.

VoIP Process GroupsPolling groups for VoIP processes are used by VoIP Availability Manager to monitor the availability of VoIP process instances discovered on Cisco, Nortel, or Avaya devices. VoIP Availability Manager monitors the instances by probing the SNMP Resource MIB tables on the devices hosting the VoIP processes or by processing traps.

Table 12 on page 110 lists the default VoIP process polling groups, their matching criteria, and their settings. The matching-criteria target class for VoIP process polling groups is VoipProcess.

VoIP Redundancy GroupsPolling groups for VoIP redundancy groups are used by VoIP Availability Manager to monitor the availability of Call Manager group instances discovered on Cisco, Nortel, or Avaya devices. VoIP Availability Manager monitors the instances by probing the SNMP tables on the devices hosting the Call Manager groups.

Table 11 Default VoIP Network Service groups


Cisco Network Services VoipNetworkService attributes:• Vendor = CISCO

• VoIP Polling - SNMP• VoIP Performance Polling - External

Nortel Network Services VoipNetworkService attributes:• Vendor = NORTEL


Avaya Network Services VoipNetworkService attributes:• Vendor = AVAYA• Type =

MAIN|LSP|ESS|MEDIAGATEWAY

• VoIP Polling - SNMP• VoIP Performance Polling - External

Table 12 Default VoIP Process groups


Critical Processes with SNMP Instrumentation

VoipProcess attributes:• IsCritical = TRUE

VoIP Polling - SNMP

Critical Processes with External Instrumentation

VoipProcess attributes:• IsCritical = TRUE


Non-Critical Processes VoipProcess attributes:• IsCritical = FALSE

VoIP Polling - SNMP



Table 13 on page 111 lists the default VoIP Call Manager group polling groups, their matching criteria, and their settings. The matching-criteria target class for VoIP Call Manager group polling groups is VoipCallManagerRedundancyGroup or ConvergedCallManagerRedundancyGroup.

Default polling settings

VoIP Availability Manager provides the following default polling settings:

◆ VoIP Polling - SNMP (default setting for most of the polling groups)

◆ VoIP Performance Polling - External (default setting for the VoIP clusters and Cisco and Avaya network service polling groups)

◆ VoIP Polling - External (default setting for the Nortel application and network service polling groups, and for the Avaya card service polling group)

◆ Redundancy Group - Analysis (default setting for the Cisco, Nortel, and Avaya redundancy group polling groups)

Note: One or more default polling settings may be active at the same time.

VoIP Polling - SNMP settingThe VoIP Polling - SNMP setting configures availability monitoring of discovered VoIP applications, network services, and processes. The monitoring is accomplished by sending periodic SNMP requests to the managed VoIP devices to obtain application, network service, and process status.

Table 14 on page 111 lists the parameters for the VoIP Polling - SNMP polling setting.

Table 13 Default VoIP Redundancy Groups


Cisco CallManager RedundancyGroups VoipCallManagerRedundancyGroup attributes:

• Vendor = CISCO

Redundancy Group-Analysis

Nortel CallManager RedundancyGroups VoipCallManagerRedundancyGroup attributes:

• Vendor = NORTEL


Avaya CallManager RedundancyGroups ConvergedCallManagerRedundancyGroup attributes:

• Vendor = AVAYA


Table 14 Parameters for the VoIP Polling - SNMP setting (page 1 of 2)

Parameter Default value Description

AnalysisMode ENABLED,DISABLEDDefault: ENABLED

Enables or disables availability polling.

PollingInterval 30 to 3600 secondsDefault: 240 seconds

Time between successive availability polls.



VoIP Performance Polling - External settingThe VoIP Performance Polling - External setting determines the initial states of the instrumentation data provided by VoIP Performance Manager to be analyzed by VoIP Availability Manager. No SNMP polling is performed.

Table 15 on page 112 lists the parameters for the VoIP Performance Polling - External polling setting.

VoIP Polling - External settingThe VoIP Polling - External setting determines the initial states of the instrumentation data to be analyzed by VoIP Availability Manager. No SNMP polling is performed.

Table 16 on page 112 lists the parameters for the VoIP Polling - External polling setting.

Retries 0 to 10 retriesDefault: 3

Number of retry connectivity polls to perform when the initial poll fails.

Timeout 10 to 10000 millisecondsDefault: 700 milliseconds

Amount of time to wait for the poll response before the first poll request times out. The timeout value doubles for each successive retry.For Timeout=700 msec (0.7 sec) and Retries=3:• 0.7 seconds for first retry• 1.4 seconds for second retry• 2.8 seconds for third retry

Table 14 Parameters for the VoIP Polling - SNMP setting (page 2 of 2)


Table 15 Parameters for the VoIP Performance Polling - External setting



Enables or disables the availability analysis of data collected by an external source such as vendor (third party) generated traps.Instrumentation data is implemented using stored attributes provided for status input from the external source.

InitialStatus UNKNOWN,RESPONSIVE,UNRESPONSIVEDefault: RESPONSIVE

Determines the desired initial state for the stored instrumentation objects. Initial status value can be UNKNOWN, RESPONSIVE, or UNRESPONSIVE

Table 16 Parameters for the VoIP Polling - External setting



Enables or disables the availability analysis of data collected by an external source such as vendor (third party) generated traps.Instrumentation data is implemented using stored attributes provided for status input from the external source.

InitialStatus UNKNOWN,RESPONSIVE,UNRESPONSIVEDefault: RESPONSIVE

Determines the desired initial state for the stored instrumentation objects. Initial status value can be UNKNOWN, RESPONSIVE, or UNRESPONSIVE.



Redundancy Group - Analysis settingThe Redundancy Group - Analysis setting controls whether VoIP Availability Manager performs availability analysis of Call Manager redundancy groups.

Table 17 on page 113 lists the parameters for the Redundancy Group - Analysis polling setting.

Table 17 Parameters for the Redundancy Group - Analysis setting

Parameter Values Description


Enables or disables the availability analysis of Call Manager redundancy groups.

Configuring Polled Data Thresholds 115

9

This chapter describes the default threshold groups and settings for VoIP Availability Manager. It consists of the following sections:

◆ Viewing the Thresholds tab ........................................................................................ 116◆ Understanding threshold groups and settings ........................................................ 117◆ Default threshold groups and settings...................................................................... 118

Configuring PolledData Thresholds


Configuring Polled Data Thresholds

Viewing the Thresholds tabFigure 23 on page 116 shows the Thresholds tab of a Polling and Thresholds Console connected to a VoIP Availability Manager instance named VoIP-AM. The right panel of the console identifies "Redundancy Group Monitoring parameters" as the default setting for a default threshold group named "Cisco CallManager Redundancy Groups."

Figure 23 Thresholds tab for VoIP Availability Manager

Thresholds Group Tree Thresholds Group Configuration Window

Understanding threshold groups and settings 117


Understanding threshold groups and settingsVoIP Availability Manager monitors the network by sending SNMP polls and by processing SNMP traps, and by processing information from the VoIP Performance Manager. The results of the polling and trap processing are then compared to threshold values that define acceptable and unacceptable levels of availability. The polling and trap processing results, in conjunction with the status updates received from IP Availability Manager, are used to diagnose the failed objects that interrupt network service connectivity.

VoIP Availability Manager uses settings to assign polling and threshold parameters to groups of managed objects. From a polling and threshold perspective, a setting is a collection of parameters common to a particular type of analysis (for example, network services polling).

Using the Polling and Thresholds Console (shown in Figure 23 on page 116), you can customize SNMP polling result thresholds—and SNMP trap processing result thresholds—for VoIP Availability Manager by modifying default threshold groups or by creating new threshold groups.

Modifying threshold groupsProcedures for modifying existing threshold groups and creating new ones are given in “Working with groups and settings” on page 101.

When you finish editing the properties of a group, you:

1. Click Apply to save the configuration changes to an existing group object or to a newly created group object in the repository of VoIP Availability Manager.

2. Click the Reconfigure toolbar button or select Reconfigure from the Group menu to make the configuration changes take effect.

When the reconfiguration completes, VoIP Availability Manager applies/reapplies the thresholds configured for the group object.



Default threshold groups and settingsThe default threshold categories, groups, and settings for VoIP Availability Manager are accessible via the Thresholds tab of the Polling and Thresholds Console.

Default threshold categories and groupsVoIP Availability Manager provides the following threshold group categories:

◆ Call Manager Thresholds

◆ Call Manager Redundancy Group Thresholds

◆ DS1 Service Thresholds

◆ Gateway Service Thresholds

◆ H323 Gate Keeper Thresholds

◆ H323 Service Thresholds

◆ Signaling Service Thresholds

◆ VoIP Clusters Thresholds

Each category contains one or more default threshold groups.

Note: In your Polling and Threshold Console, the threshold categories, groups, and settings that appear will vary depending on the installed VoIP Management Suite products (the VoIP Performance Manager Integration Pack and enablement packs).

Default threshold groups and settings 119


Call Manager ThresholdsThreshold groups for Call Managers are used to configure parameters for Call Manager analysis.

For Avaya Call Managers, membership is restricted to the following disaster-prevention types of Call Managers:

◆ Local Survivable Processor (LSP)

A Call Manager application, running on a remote H.248 Media Gateway, that preserves client device connections during a primary Call Manager server failover.

◆ Enterprise Survivable Server (ESS)

A Call manager application, running on a Media Server, that provides survivability to local or remote Media Gateways and port networks during a primary Call Manager server failover.

Table 18 on page 119 lists the default Call Manager threshold groups, their matching criteria, and their settings. The matching-criteria target class for Call Manager threshold groups is VoipNetworkService or ConvergedCallManager.

One thing to note about this table and the tables that follow:

Only a discovered object of the target type (or one of its subclasses) and matching the matching-criteria attribute(s) for a particular threshold group becomes a member of that group.

For the Nortel CallManagers Configuration group, for example, only a discovered object of type “VoIPNetworkService” (or one of its subclasses) with attribute Vendor = NORTEL and attribute CreationClassName = CallManager becomes a member of the group.

You can specify additional matching criteria for a threshold group to limit its membership, as explained in “Editing matching criteria” on page 103.

Table 18 Default Call Manager groups

Call Manager group Matching criteria Settings

Nortel Call Managers VoipNetworkService attributes:• Vendor = NORTEL• CreationClassName = CallManager

• VoIP Nortel Backup Monitoring Options

• VoIP Nortel TLAN Monitoring Options

Avaya Communication Managers ConvergedCallManager attributes:• Vendor = AVAYA• Type = LSP|ESS• CreationClassName = ConvergedCallManager

• Converged Call Manager Performance Thresholds

• VoIP Avaya Backup Monitoring Options

Cisco Call Managers ConvergedCallManager attributes:• Vendor = CISCO• CreationClassName = CallManager

• Call Manager Performance Thresholds

• Conferencing Resource Performance Thresholds

• Media Resource Performance Thresholds



Call Manager Redundancy Group ThresholdsThreshold groups for Call Manager redundancy groups are used to configure parameters for redundancy group analysis.

Table 19 on page 120 lists the default Call Manager redundancy group threshold groups, their matching criteria, and their settings. The matching-criteria target class for Call Manager redundancy group threshold groups is VoipCallManagerRedundancyGroup.

DS1 Service ThresholdsThreshold groups for DS1 Service are used to configure parameters for DS1 Service performance monitoring.

Table 20 on page 120 lists the default DS1 Service threshold groups, their matching criteria, and their settings. The matching-criteria target class for a DS1 Service threshold group is DS1Service.

Gateway Service ThresholdsThreshold groups for Gateway Service are used to configure parameters for Gateway Service performance monitoring.

Table 21 on page 120 lists the default Gateway Service threshold groups, their matching criteria, and their settings. The matching-criteria target class for a Gateway Service threshold group is Gateway.

Table 19 Default Call Manager Redundancy groups

Interface Group Matching criteria Settings

Cisco CallManager Redundancy Groups VoipCallManagerRedundancyGroup attributes:

• Vendor = CISCO

Redundancy Group Monitoring Parameters

Nortel CallManager Redundancy Groups VoipCallManagerRedundancyGroup attributes:

• Vendor = NORTEL


Avaya CallManager Redundancy Groups VoipCallManagerRedundancyGroup attributes:

• Vendor = AVAYA


Table 20 Default DS1 Service groups

Network Service Group Matching criteria Settings

DS1 Services DS1Service attributes:• CreationClassName = DS1Service

DS1 Service Performance Thresholds

Table 21 Default Gateway Service groups


Gateway Services GatewayService attributes:• CreationClassName = GatewayService

Gateway Service Performance Thresholds



H323 Gate Keeper ThresholdsThreshold groups for H.323 Gate Keeper are used to configure parameters for H.323 Gate Keeper performance monitoring.

Table 22 on page 121 lists the default H.323 Gate Keeper threshold groups, their matching criteria, and their settings. The matching-criteria target class for a H.323 Gate Keeper threshold group is H323GateKeeper.

H323 Service ThresholdsThreshold groups for H.323 Service are used to configure parameters for H.323 Service performance monitoring.

Table 23 on page 121 lists the default H.323 Service threshold groups, their matching criteria, and their settings. The matching-criteria target class for a H.323 Service threshold group is H323Service.

Signaling Service ThresholdsThreshold groups for signaling services are used to configure parameters for Nortel Signaling Server analysis.

Table 24 on page 121 lists the default signaling services threshold groups, their matching criteria, and their settings. The matching-criteria target class for signaling services threshold groups is VoIPNetworkService.

Table 22 Default H.323 Gate Keeper groups


H323 Gate Keepers H323GateKeeper attributes:• CreationClassName = H323GateKeeper

H323 Gate Keeper Performance Thresholds

Table 23 Default H.323 Service groups


H323 Services H323GateKeeper attributes:• CreationClassName = H323Service

H323 Service Performance Thresholds

Table 24 Default Signaling Service group


Nortel Signaling Service VoipNetworkService attributes:• Vendor = NORTEL• CreationClassName = SignalingService

VoIP Nortel TLAN Monitoring Options



VoIP Clusters ThresholdsThreshold groups for VoIP clusters are used to configure parameters for VoIP Cluster performance monitoring.

Table 25 on page 122 lists the default signaling services threshold groups, their matching criteria, and their settings. The matching-criteria target class for VoIP Clusters threshold groups is VoipCluster.

Default threshold settings

VoIP Availability Manager provides the following default threshold settings:

◆ VoIP Nortel Backup Monitoring Options (default setting for the Nortel Call Managers threshold group)

◆ VoIP Nortel TLAN Monitoring Options (a second default setting for the Nortel Call Managers threshold group)

◆ VoIP Avaya Backup Monitoring Options (default setting for the Avaya Communication Managers threshold group)

◆ Converged Call Manager Performance threshold setting (default setting for the Avaya Communication Managers threshold group)

◆ Call Manager Performance Thresholds (default setting for the Cisco Communication Managers threshold group)

◆ Conferencing Resource Performance Thresholds (default setting for the Cisco Communication Managers threshold group)

◆ Media Resource Performance Thresholds setting (default setting for the Cisco Communication Managers threshold group)

◆ DS1 Service Performance Thresholds setting (default setting for the Avaya Communication Managers threshold group)

◆ Gateway Service Performance Thresholds setting (default setting for gateway services discovered on Cisco, Nortel, or Avaya devices)

◆ H323 Gate Keeper Performance Thresholds setting (default setting for the H.323 gateway service)

◆ H323 Service Performance Thresholds setting (default setting for the H.323 Service used by a Cisco Call Manager.)

◆ Redundancy Group Monitoring parameters (default setting for the Cisco, Nortel, and Avaya redundancy group threshold groups)

◆ VoIP Cluster Performance Thresholds setting (default setting for VoIP clusters discovered on Cisco or Avaya devices)

Table 25 Default VoIP Clusters group


VoIP Clusters VoipCluster attributes:• CreationClassName = VoIPCluster

VoIP Cluster Performance Thresholds



VoIP Nortel Backup Monitoring Options threshold settingThis threshold setting configures the monitoring of a Nortel Call Manager’s standby state. Table 26 on page 123 lists the parameters for the VoIP Nortel Backup Monitoring Options threshold setting.

VoIP Nortel TLAN Monitoring Options threshold settingThis threshold setting configures the monitoring of a Nortel Call Manager’s Telephony LAN (TLAN) interfaces. Table 27 on page 123 lists the parameters for the VoIP Nortel TLAN Monitoring Options threshold setting.

Table 26 Parameters for the VoIP Nortel Backup Monitoring Options setting


StandBy_Reset_Mode true,falseDefault: false

Applicable to failover and to the active Nortel Call Manager that is now in Standby mode:Controls whether VoIP Availability Manager transitions the Standby state of the Call Manager from TRUE to FALSE when the time specified in the Standby_Reset_Time_AtSec parameter expires.• True enables the automatic transitioning.• False disables the automatic transitioning.This parameter is used to clear the Call Manager Down notification (resulting from Standby = TRUE) when no trap is received to clear the notification.

Standby_Reset_Time_AtSec 240 seconds(4 minutes)

Specifies the Call Manager’s Standby = TRUE time, in seconds, after which VoIP Availability Manager transitions the Standby state to FALSE.

Table 27 Parameters for the VoIP Nortel TLAN Monitoring Options setting


TLANStatus_Reset_Mode true,falseDefault: false

Applicable to a Nortel Call Manager whose TLAN status = Unresponsive:Controls whether VoIP Availability Manager transitions the TLAN status from Unresponsive to Unknown when the time specified in the TLANStandby_Reset_Time_AtSec parameter expires.• True enables the automatic transitioning.• False disables the automatic transitioning.This parameter is used to clear the Call Manager Down notification (resulting from TLAN status = Unresponsive) when no trap is received to clear the notification.

TLANStatus_Reset_Time_AtSec 240 seconds(4 minutes)

Specifies the Call Manager’s TLAN status = Unresponsive time, in seconds, after which VoIP Availability Manager transitions the TLAN status from Unresponsive to Unknown.



VoIP Avaya Backup Monitoring Options threshold settingThis threshold setting configures the monitoring of an Avaya Call Manager’s standby state. Table 28 on page 124 lists the parameters for the VoIP Avaya Backup Monitoring Options threshold setting.

Converged Call Manager Performance threshold settingThis threshold setting configures the performance monitoring of an Avaya Call Manager’s CPU processor occupancy usage. Table 29 on page 124 lists the parameters for the Converged Call Manager Performance threshold setting.

Call Manager Performance ThresholdsThis threshold setting configures the performance monitoring of a Cisco Call Manager. Table 30 on page 124 lists the parameters for the Call Manager Performance thresholds setting.

Table 28 Parameters for the VoIP Avaya Backup Monitoring Options setting


StandBy_Reset_Mode true,falseDefault: false

Applicable to failover and the active Avaya Call Manager that is now in Standby mode:Controls whether VoIP Availability Manager transitions the Standby state of the Call Manager from TRUE to FALSE when the time specified in the Standby_Reset_Time_AtSec parameter expires.• True enables the automatic transitioning.• False disables the automatic transitioning.This parameter is used to clear the Call Manager Down notification (resulting from Standby = TRUE) when no trap is received to clear the notification.

Standby_Reset_Time_AtSec 240 seconds(4 minutes)

Specifies the Call Manager’s Standby = TRUE time, in seconds, after which VoIP Availability Manager transitions the Standby state to FALSE.

Table 29 Parameters for the Converged Call Manager Performance threshold setting


Processor_Occupancy_Threshold 80 Set to a value representing the CPU processor occupancy usage (being used against the number of calls and connections).

Table 30 Parameters for the Call Manager Performance Thresholds setting


Calls_In_Progress_Threshold 50 Specifies the number of calls in progress.

Call_Load_Threshold_Percent 80 Specifies the call load percentage.

Registered_Hardware_Phones_Threshold 3 Set to a value representing the difference between the number of provisioned hardware phones and the number of registered hardware phones in Call Manager.



Conferencing Resource Performance ThresholdsThis threshold setting configures the performance monitoring of a Cisco Call Manager. Table 31 on page 125 lists the parameters for the Conferencing Resource Performance Thresholds setting.

Media Resource Performance ThresholdsThis threshold setting configures the performance monitoring of a Cisco Call Manager. Table 32 on page 125 lists the parameters for the Media Resource Performance Thresholds setting.

Table 31 Parameters for the Conferencing Resource Performance Thresholds setting


Hardware_Conference_Load_Threshold_Percent 80 Set to a value representing the ratio of the active media resource to the total resource of type Hardware Conference.

Hardware_Conference_Resource_Exception_Window 1 Specifies the number of polling cycles to retain the threshold crossing indicator.

Software_Conference_Load_Threshold_Percent 80 Set to a value representing the ratio of the active media resource to the total resource of type Software Conference.

Software_Conference_Resource_Exception_Window 1 Specifies the number of polling cycles to retain the threshold crossing indicator.

Video_Conference_Load_Threshold_Percent 80 Set to a value representing the ratio of the active media resource to the total resource of type Video Conference.

Video_Conference_Resource_Exception_Window 1 Specifies the number of polling cycles to retain the threshold crossing indicator.

Table 32 Parameters for the Media Resource Performance Thresholds setting (page 1 of 2)


Annunciator_Load_Threshold_Percent 80 Set to a value representing the ratio of the active media resource to the total resource of type Annunciator.

Annunciator_Resource_Exception_Window 1 Specifies the number of polling cycles to retain the threshold crossing indicator.

Media_Termination_Point_Load_Threshold_Percent 80 Set to a value representing the ratio of the active media resource to the total resource of type Media Termination Point.

Media_Termination_Point_Resource_Exception_Window 1 Specifies the number of polling cycles to retain the threshold crossing indicator.

Music_On_Hold_Load_Threshold_Percent 80 Set to a value representing the ratio of the active media resource to the total resource of type Music On Hold.



DS1 Service Performance ThresholdsThis threshold setting configures the performance monitoring of a Avaya Communication Managers threshold group. Table 33 on page 126 lists the parameters for the DS1 Service Performance Thresholds setting.

Gateway Service Performance ThresholdsThis threshold setting configures the performance monitoring of gateway services discovered on Cisco, Nortel, or Avaya devices. Table 34 on page 126 lists the parameters for the Gateway Service Performance Thresholds setting.

H323 Gate Keeper Performance ThresholdsThis threshold setting configures the performance monitoring of the H.323 Gate Keeper service. Table 35 on page 126 lists the parameters for the H323 Gate Keeper Performance Thresholds setting.

Music_On_Hold_Resource_Exception_Window 1 Specifies the number of polling cycles to retain the threshold crossing indicator.

Transcoder_Load_Threshold_Percent 80 Set to a value representing the ratio of the active media resource to the total resource of type Transcoder.

Transcoder_Load_Resource_Exception_Window 1 Specifies the number of polling cycles to retain the threshold crossing indicator.

Table 32 Parameters for the Media Resource Performance Thresholds setting (page 2 of 2)


Table 33 Parameters for the DS1 Service Performance Thresholds setting


Trunk_Usage_Threshold_Percent 80 Specifies the active trunks percentage.

Table 34 Parameters for the Gateway Service Performance Thresholds setting


Channel_Utilization_Threshold_Percent 80 Specifies the channel utilization percentage.

Port_Utilization_Threshold_Percent 80 Specifies the port utilization percentage.

Resource_Exception_Window 1 Specifies the number of polling cycles to retain the threshold crossing indicator.

Table 35 Parameters for the H323 Gate Keeper Performance Thresholds setting


Phone_Registration_Changes_Threshold -1 Set to a value representing the changes in PhoneRegistration for this service.



H323 Service Performance ThresholdsThis threshold setting configures the performance monitoring of the H.323 Service used by a Cisco Call Manager. Table 36 on page 127 lists the parameters for the H323 Service Performance Thresholds setting.

Redundancy Group Monitoring parameters threshold settingThis threshold setting configures the AtRisk threshold value of Cisco, Nortel, and Avaya Call Manager redundancy groups. The AtRisk threshold value may be set using a numeric or percent assignment.

Table 37 on page 127 lists the parameters for the Redundancy Group Monitoring parameters threshold setting.

VoIP Availability Manager uses the specified AtRisk threshold value to determine the state of a Call Manager redundancy group. Possible states are:

◆ AllComponentsDown

◆ AtRisk

◆ ReducedRedundancy

◆ Normal

Table 36 Parameters for the H323 Service Performance Thresholds setting


Call_Load_Threshold_Percent 80 Specifies the call load percentage for a H.323 service used by a Cisco Call Manager.

Calls_In_Progress_Threshold 50 Specifies the number of calls in progress for this call manager.

Table 37 Parameters for the Redundancy Group Monitoring parameters setting


AtRiskNumericalThreshold 1 Set to a value representing the number of responsive or operational member objects in a redundancy group.

AtRiskPercentThreshold 50% Set to a value representing the percentage of responsive or operational member objects in a redundancy group. Calculated as:Number of responsive or operational member objectsdivided byTotal number of member objects multiplied by 100

IsPercentUsed true,falseDefault: true

Determines whether AtRiskNumericalThreshold or AtRiskPercentThreshold is used as the AtRisk threshold in redundancy group analysis.• True indicates that the percent assignment is used.• False indicates that the number assignment is used.



VoIP Cluster Performance ThresholdsThis threshold setting configures the performance monitoring of VoIP clusters discovered on Cisco or Avaya devices. Table 38 on page 128 lists the parameters for the VoIP Cluster Performance Thresholds setting.

Table 38 Parameters for the VoIP Cluster Performance Thresholds setting


Poor_MOS_Call_Percent 0 Set to a value representing the percentage of calls whose MOS (Mean Opinion Score) is less than acceptable (poor) during the last sampling interval.

Creating Credential Sets 129

10

This chapter describes the default device access groups and settings for VoIP Availability Manager. It consists of the following sections:

◆ Viewing the Device Access tab.................................................................................. 130◆ Understanding device access groups and settings................................................. 131◆ Default device access groups and settings .............................................................. 132◆ Using the Device Access tab ...................................................................................... 134

Creating CredentialSets


Creating Credential Sets

Viewing the Device Access tabFigure 24 on page 130 shows the Device Access tab of a Polling and Thresholds Console connected to a VoIP Availability Manager instance named VoIP-AM. In this example, the right panel of the tab identifies the default setting "VoIP PM Web Interface Access" and its parameters for a default device access group named "VoIP PM Servers."

Figure 24 Device Access tab for VoIP Availability Manager

Understanding device access groups and settings 131


Understanding device access groups and settingsLogin credentials (user ID and password) that are specified using the Device Access tab are stored in the VoIP Availability Manager. The password is stored in an encrypted format. EMC Smarts client tools, Nortel signaling servers, and Nortel call servers use login credentials in the following manner:

◆ For a client tool, login credentials are initially stored in the VoIP Availability Manager as attributes of the class VoipPerformanceManager. During topology synchronization with the Global Manager, the VoIP Availability Manager transfers the credentials with the class to the Global Manager. When a client tool is launched, the login credentials are retrieved from the Global Manager and used to access the VoIP Performance Manager's web server.

◆ For Nortel signaling servers and call servers, Command Line Interface (CLI) login credentials are stored with Settings objects in the VoIP Availability Manager. Nortel-specific probes use these credentials to log on to Nortel signaling servers and call servers.

This chapter describes how to specify login credential sets using the Device Access tab, default device access groups and their settings, and how to create different sets of device access credentials.

Note: If you installed the Nortel Enablement Pack for your VoIP Availability Manager deployment, you must specify CLI login credentials for signaling servers and call servers.

Modifying and creating device access groupsProcedures for modifying existing device access groups and creating new ones are given in “Working with groups and settings” on page 101.



Default device access groups and settingsThrough the default device access groups, you create sets of login credentials needed to access systems in the managed network environment.

Default device access groupsThe VoIP Availability Manager provides the following default device access groups:

◆ Nortel Signaling Servers

◆ VoIP PM Servers

Table 39 on page 132 lists the matching criteria and the default settings for the default device access groups. The matching-criteria target class for:

◆ Nortel Signaling Servers is Signaling Service.

◆ VoIP PM Servers is VoipPerformanceManager.

The matching criteria defined for each of the groups limits the group’s members to the appropriate servers.

Default device access settings

This section describes the parameters that are used in the default device access settings.

Nortel settingsFor the Nortel Signaling Servers device access group, there are two default settings, Nortel Call Server Access and Nortel Signaling Server Access. Table 40 on page 133 lists the parameters used for both default settings.

Table 39 Default device access groups

Device access group Matching criteria Default settings

Nortel Signaling Servers Signaling Service attributes:• SystemObjectID = .1.3.6.1.4.1.562.3.21

• Nortel Call Server Access• Nortel Signaling Server Access

VoIP PM Servers VoipPerformanceManager attributes:• Type = ~Agent

VoIP PM Web Interface Access

Default device access groups and settings 133


You must specify CLI login credentials for both default settings, Nortel Call Server Access and Nortel Signaling Server Access.

VoIP PM Web Interface settingFor the VoIP PM Servers device access group, there is one default setting, VoIP PM Web Interface Access. Table 41 on page 133 lists the parameters used for the VoIP PM Web Interface Access setting.

Table 40 Default values for the Nortel settings

Parameter Default Value Description

User_ID String of unspecified lengthDefault: null string (empty)

Specifies the username (user ID) for the managed devices that belong to this group. There must be an entry for this parameter.

Password String of unspecified lengthDefault: null string (empty)

Specifies the password for the managed devices that belong to this group. Type the password value twice to confirm the password value.There must be an entry for this parameter.

Note: VoIP Availability Manager uses the site key to encrypt the entered password value. As explained in EMC Smarts System Administration Guide, the site key is created during the installation of EMC Smarts applications.

Table 41 Default values for the VoIP PM Web Interface Access setting

Parameter Default Value Description

User_ID String of unspecified lengthDefault: null string (empty)

Specifies the username (user ID) for the managed devices that belong to this group.There must be an entry for this parameter. If no username is configured on the devices that belong to this group, type the username of the VoIP Performance Manager's web server.

Password String of unspecified lengthDefault: null string (empty)

Specifies the password for the managed devices that belong to this group. Type the password value twice to confirm the password value.There must be an entry for this parameter.

Note: VoIP Availability Manager uses the site key to encrypt the entered password value. As explained in EMC Smarts System Administration Guide, the site key is created during the installation of EMC Smarts applications.



Using the Device Access tabIn an environment managed by VoIP Availability Manager, you, as the VoIP Availability Manager administrator, need to perform the following tasks:

◆ Specify the login credentials for the VoIP Performance Manager as described in “Creating a credential set” on page 134. Since there is only one VoIP Performance Manager that communicates with VoIP Availability Manager and the default device access group, VoIP PM Servers, already exists, you only need to specify the login credentials for its setting, VoIP PM Web Interface Access.

◆ Specify the CLI login credentials for the default device access group, Nortel Signaling Servers, and its settings, Nortel Call Server Access and Nortel Signaling Server Access, as described in “Creating a credential set” on page 134.

◆ Optional, create one or more additional device access groups for each group of managed Nortel servers configured with a different set of CLI login credentials. The matching criteria defined for each of the groups limits the group’s members to the appropriate servers. “Overview of creating a device access group” on page 134 describes the procedure.

Creating a credential set

The steps for creating a credential set for a default device access group are:

1. In a Polling and Thresholds Console attached to a VoIP Availability Manager, click the Device Access tab to display the device access group tree.

2. In the device access group tree, select the existing default device access group and expand the Settings object.

3. Select the setting (for example, VoIP PM Web Interface Access) and specify the parameters for it in the right panel.

4. Click Apply to save the changes.

If a default access group has more than one default device access setting, repeat the above steps for each setting.

5. Click Reconfigure or select Reconfigure from the Group menu to make the configuration changes take effect.

Note: When you click Reconfigure, the credentials are initially stored in the VoIP Availability Manager. When the next topology synchronization occurs, the credentials are stored in the Global Manager.

Overview of creating a device access group

The basic steps for creating and configuring access groups are:

1. In a Polling and Thresholds Console attached to a VoIP Availability Manager, click the Device Access tab to display the device access group tree.

2. In the device access group tree, use the existing default device access group, Nortel Signaling Servers, to create another access group for each group of Nortel servers that has a different set of CLI login credentials. One way to create a new access group is to right-click Nortel Signaling Servers and select Copy. (“Creating new groups” on page 104 describes procedures for creating empty groups and groups based on existing groups.)

Using the Device Access tab 135


3. Edit the parameters as appropriate in each of the device access groups.

4. Define matching criteria for each of the device access groups to limit each group’s membership to the Nortel server or group of Nortel servers for which the parameters specified in step 3 apply.

Start by defining Vendor = NORTEL. Then, define other variables and values to refine the membership; for example, Name = Nortel*, which limits the membership to only those devices having names that begin with the string Nortel.

5. Change the priority of the device access group as needed. Typically, the default access group is placed at the bottom of the priority list. (The procedure for changing the priority of groups is given in “Modifying the priority of groups” on page 102.)

Modify the properties of a device access group in the same way that you modify the properties of a polling or threshold group: through the Settings, Priorities, and Matching Criteria tabs, available when the group name is selected in the left panel of the Polling and Thresholds Console. After customizing the properties of a group, click Apply to save the changes and then click Reconfigure or select Reconfigure from the Group menu to make the configuration changes take effect.

Wildcard Patterns 137

A

This appendix shows you how to use a wildcard pattern in a text field to match a number of objects instead of specifying each object by name. (EMC Smarts programs, such as the Global Console, enable you to specify wildcard patterns in text fields.) It consists of the following sections:

◆ Types of wildcard patterns ........................................................................................ 138

Wildcard Patterns


Wildcard Patterns

Types of wildcard patternsA wildcard pattern is a series of characters that are matched against incoming character strings. You can use these patterns when you define pattern matching criteria.

Matching is done strictly from left to right, one character or basic wildcard pattern at a time. Basic wildcard patterns are defined in Table 42 on page 138. Characters that are not part of match constructs match themselves. The pattern and the incoming string must match completely. For example, the pattern abcd does not match the input abcde or abc.

A compound wildcard pattern consists of one or more basic wildcard patterns separated by ampersand (&) or tilde (~) characters. A compound wildcard pattern is matched by attempting to match each of its component basic wildcard patterns against the entire input string. Compound wildcard patterns are listed in Table 43 on page 139.

If the first character of a compound wildcard pattern is an ampersand (&) or tilde (~) character, the compound is interpreted as if an asterisk (*) appeared at the beginning of the pattern. For example, the pattern ~*[0-9]* matches any string not containing any digits. A trailing instance of an ampersand character (&) can only match the empty string. A trailing instance of a tilde character (~) can be read as “except for the empty string.”

Note: Spaces are interpreted as characters and are subject to matching even if they are adjacent to operators like “&”.

Table 42 Basic wildcard patterns (page 1 of 2)

Character Description

? Matches any single character. For example, server?.example.com matches server3.example.com and serverB.example.com, but not server10.example.com.

* Matches an arbitrary string of characters. The string can be empty. For example, server*.example.com matches server-ny.example.com and server.example.com (an empty match).

[set] Matches any single character that appears within [set]; or, if the first character of [set] is (^), any single character that is not in the set. A hyphen (-) within [set] indicates a range, so that [a-d] is equivalent to [abcd]. The character before the hyphen (-) must precede the character after it or the range will be empty. The character (^) in any position except the first, or a hyphen (-) at the first or last position, has no special meaning. For example, server[789-].example.com matches server7.example.com through server9.example.com, but not server6.example.com. It also matches server-.example.com.For example, server[^12].example.com does not match server1.example.com or server2.example.com, but will match server8.example.com.

Types of wildcard patterns 139

Wildcard Patterns

Special characters for compound wildcard patterns are summarized in Table 43 on page 139.

<n1-n2> Matches numbers in a given range. Both n1 and n2 must be strings of digits, which represent nonnegative integer values. The matching characters are a non-empty string of digits whose value, as a nonnegative integer, is greater than or equal to n1 and less than or equal to n2. If either end of the range is omitted, no limitation is placed on the accepted number.For example, 98.49.<1-100>.10 matches a range of IPv4 addresses from 98.49.1.10 through 98.49.100.10. Example of an omitted high end of the range: <50-> matches any string of digits with a value greater than or equal to 50. Example of an omitted low end of the range: <-150> matches any value between zero and 150.For a more subtle example: The pattern <1-10>* matches 1, 2, up through 10, with * matching no characters. Similarly, it matches strings like 9x, with * matching the trailing x. However, it does not match 11, because <1-10> always extracts the longest possible string of digits (11) and then matches only if the number it represents is in range.

| Matches alternatives. For example,”ab|bc|cd” without spaces matches exactly the three following strings: “ab”, “bc”, and “cd”. A | as the first or last character of a pattern accepts an empty string as a match.Example with spaces “ab | bc” matches the strings “ab” and “ bc”.

\ Removes the special status, if any, of the following character. Backslash (\) has no special meaning within a set ([set]) or range (<n1-n2>) construct.

Table 42 Basic wildcard patterns (page 2 of 2)


Table 43 Compound wildcard patterns


& “And Also” for a compound wildcard pattern. If a component basic wildcard pattern is preceded by & (or is the first basic wildcard pattern in the compound wildcard pattern), it must successfully match. Example: *NY*&*Router* matches all strings that contain NY and also contain Router. Example: <1-100>&*[02468] matches even numbers between 1 and 100 inclusive. The <1-100> component only passes numbers in the correct range and the *[02468] component only passes numbers that end in an even digit. Example: *A*|*B*&*C* matches strings that contain either an A or a B, and also contain a C.

~ “Except” for a compound wildcard pattern (opposite function of &).If a component basic wildcard pattern is preceded by ~, it must not match. Example: 10.20.30.*~10.20.30.50 matches all devices on network 10.20.30 except 10.20.30.50.Example: *Router*~*Cisco*&*10.20.30.*~10.20.30.<10-20>* matches a Router, except a Cisco router, with an address on network 10.20.30, except not 10.20.30.10 through 10.20.30.20.


Wildcard Patterns

Polling for Analysis 141

B

This appendix describes how VoIP Availability Manager uses Simple Network Management Protocol (SNMP) polling to obtain data for its correlation analysis. It consists of the following sections:

◆ Polling overview ......................................................................................................... 142◆ SNMP poller................................................................................................................. 142

Polling for Analysis



Polling overviewAfter the initial discovery and modeling of the VoIP networks, VoIP Availability Manager monitors the status of certain VoIP objects by periodically sending SNMP polls to the VoIP-enabled devices in the managed VoIP network. VoIP Availability Manager uses an IPv4 SNMP poller, which sends SNMPv1 or v2c messages for use with IP version 4.

SNMP pollerThe SNMP poller is a synchronous, multi-threaded poller that currently uses 10 synchronous polling threads.

The SNMP poller fully supports the SNMPv1 and v2c protocols. With SNMPv1, the correlation model uses 32-bit counters in its correlation analysis. With SNMPv2c, the correlation model uses high-capacity 64-bit counters in its correlation analysis. Using 64-bit counters is critical for performance analysis of high-speed data links because using 32-bit counters might result in wrapping (overflow) of the counters between polls.

Polling for devices with multiple IP addresses is supported because the SNMP poller supports multiple IP addresses for each SNMP agent. The SNMP poller automatically switches to an alternate IP address during failures, thereby ensuring the integrity of the VoIP Availability Manager correlation analysis during an outage.

Just-in-time polling

The SNMP poller’s MIB variable poll list is driven by a Just-In-Time polling algorithm, which ensures that only those MIB variables needed for correlation are polled. For example, if a port monitored for performance data is disabled, or goes down, the SNMP poller automatically removes the relevant MIB variables from the poll list. If the port is re-enabled, or comes back up, the variables are automatically put back onto the MIB poll list.

Request-consolidation polling

Issuing a single SNMP GET request that requests 10 variables is more efficient than issuing 10 GET requests each requesting a single variable. The SNMP poller consolidates as many variables as possible into a single SNMP GET request. The consolidation is not restricted to variables from the same SNMP table. Polling consolidation continually adapts to changes in the MIB variable poll list.

Upon encountering a non-fatal error during polling consolidation, the SNMP poller responds differently to an SNMPv1 agent than to an SNMPv2 agent for the following reason: Where an SNMPv1 agent stops processing a request upon encountering an error, an SNMPv2c agent continues processing a request upon encountering an error. An SNMPv2c agent handles errors on a per-OID basis.

SNMP poller 143


If a nonfatal error is encountered by an SNMPv1 agent during a GET request seeking multiple variables, the SNMP poller suspends the polling of the affected variable. It suspends polling to prevent reduced performance of the SNMPv1 agent, since continuous polling of the affected variable would require the resending of the remainder of the request after receiving the error. The SNMP poller continues to poll the unaffected variables. (An example of an affected variable is one that has become unavailable due to a configuration change.) This behavior enables the SNMP poller to operate efficiently with an SNMPv1 agent during unexpected changes to a device’s configuration.

In contrast, if a non-fatal error is encountered by an SNMPv2c agent during a GET request seeking multiple variables, the SNMP poller continues the polling of the affected variable as well as the unaffected variables.


AAdapter Platform 22, 24, 79Adding or removing matching criteria 103AllComponentsDown 127Architecture, VoIP 19AtRisk 127AtRiskThreshold 127Avaya Enablement Pack 21avaya.conf file 26

BBroker 22

CChanging matching criteria 103Changing priority of a group 103Changing setting parameters 102Cisco Enablement Pack 21cisco.conf file 26CLI discovery 31Client tool 69

Configuring 69Java requirement 72List of 72Login credentials 131Supported web browsers 72

Configuration roadmap 23Configure IP Availability Manager as a source 34Copying a group 104Creating a group 104

DDevice access

Credentials 131Group 132Settings 132, 133

Device Access tab 99, 130Discovery

AutoDiscover 33domain.conf file 29voip.conf file 30

dmctl command 27

Domain Manager Administration Console 98domain.conf file 26, 29

define IP Availability Manager sources 34

EEnable trap reception

TrapPort 36Enablement Pack

Avaya 21Cisco 21Nortel 21

EventRedundancy group

AllComponentsDown 127AtRisk 127ReducedRedundancy 127

FFORWARD entries 86, 88

GGlobal Console 22

Opening 40Overview discussion 40Type of

Domain Manager Administration 40Global Manager Administration 40, 42, 56Polling and Thresholds 40, 99Topology Browser Console 67

Global Manager 21, 24Configuration 52

GroupsChanging priority 103Copying 104Creating 104Definition of 100Polling 108Properties 101Threshold 118

Index


Index

IImporting

Topology elements 92IP Availability Manager 20

Configuration 46Topology import 46

LLogin credential set 131

Password 133Specifying 134User_ID 133

MMatching

Pattern 138Matching criteria

Adding or removing 103Changing 103Device access group 132

NNortel

Login credentials 131Nortel Enablement Pack 21Nortel Signaling Servers device access group 132nortel.conf file 26NumberOfProbeThreads 30

OOperator

Wildcard 138

PPassword 133Pattern 138Pattern matching 138phone-device-pool.conf file 26Polling

GroupsVoIP Application Groups 108VoIP Card Services 109VoIP Clusters 109VoIP Network Service Groups 110VoIP Process Groups 110VoIP Redundancy Groups 110

SettingsRedundancy Group - Analysis 113VoIP Performance Polling - External 112VoIP Polling - External 112VoIP Polling - SNMP 111

SNMP 107, 142Polling and Thresholds Console 98

Device Access tab 99, 130Layout 99Polling tab 99Tagging tab 99

Thresholds tab 99Toolbar buttons 99

PriorityChanging 103

RRedundancy groups

AtRiskThreshold 127States

AllComponentsDown 127AtRisk 127ReducedRedundancy 127

Removing or adding matching criteria 103Restoring default values of a setting 102

SSecurity 37

clientConnect.conf file 37, 71For client tools 71serverConnect.conf file 37, 71

Server tool 69Service Assurance Manager

See Global ManagerSetting

Changing parameters 102Definition of 100Polling 111Restoring default values 102Threshold 122

sm_edit utility 27sm_service install command 93, 95sm_service start command 94, 96SNMP

Polling 142Polls 107SNMP_retries 30SNMP_timeout 30TraceSNMPInstrumentation 31Trap messages 77TrapPort 28

SNMP Trap Adapter 22, 77SNMP_retries 30SNMP_timeout 30Status

Configure sources 34

TTagging tab 99Threshold

AtRiskThreshold 127Groups

Call Manager 119Call Manager Redundancy Group 120DS1 Service 120Gateway Service 120H.323 Gate Keeper 121Signaling Services 121VoIP Clusters 122


Index

SettingsCall Manager Performance 124Conferencing Resource Performance 125Converged Call Manager Performance 124DS1 Service Performance 126Gateway Service Performance 126H323 Service Performance 127Media Resource Performance 125Nortel Call Server Access 132Nortel Signaling Server Access 132Redundancy Group Monitoring parameters 127VoIP Avaya Backup Monitoring Options 124VoIP Cluster Performance 128VoIP Nortel Backup Monitoring Options 123VoIP Nortel TLAN Monitoring Options 123VoIP PM Web Interface Access 132

Thresholds tab 99Topology

Configure sources 34Topology Browser Console 41, 67Topology synchronization 35Tracing

SNMP polling 31TraceDiscovery 31TraceEvents 32TracePIDMonitoring 32TracePMTraps 32TraceSetting 32TraceTraps 32

TrapIsPMTrapReceiverEnabled 32Overview 76PMTraps_Timeout 33PORT parameter 80Processing 77SNMP messages 77SNMP Trap Adapter 77SyncDelay 32TracePMTraps 32TraceTraps 32Translation of incoming 79TrapPort 31, 36Versions 79

Trap exploder 77Creating a service for 93, 95Starting a service for 94, 96

Trap receiver 77, 80trapd.conf file

FORWARD entries 86, 88TrapPort 28, 31Traps required for IP Availability Manager 87Traps required for VoIP Availability Manager 86Traps selected for the trap receiver 88, 89

UUser account

Default password 40Default username 40

User profile 40User_ID 133

VVoIP architecture 19VoIP Availability Manager 18, 19, 20VoIP Integration Pack for VoIP Performance Manager 20VoIP Notification Trap Adapter 22VoIP Performance Manager 20

Accessing with client tools 69VoIP PM Servers device access group 132voip.conf file 26, 30

DisableReconfigure 33IsDemo 32MaxNumPIDMonitors 33NumberOfProbeThreads 30PIDPollingInterval 31ProhibitCLI 31SNMP_retries 30SNMP_timeout 30TrapPort 28, 31ValidateTopology 33

voip-topo-oid.conf file 48, 49

WWeb browser

Configuring for client tools 70Wildcard 138

Chart of operators 138

XXML domain configuration file 67


Index