emc smarts voip performance manager for cisco v5+, avaya ... · the emc smarts voip performance...

Installation Guide

EMC® Smarts®

VoIP Performance Managerfor Cisco v5+, Avaya and

Nortel CS1KVersion 2.0

Installation GuideP/N 300-006-055

REV A03

EMC Corporation Corporate Headquarters

Hopkinton, MA 01748-91031-508-435-1000www.EMC.com

EMC Smarts VoIP Performance Manager

of 204

Copyright © 2008 EMC Corporation. All rights reserved.

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 listing of EMC product names, see EMC Corporation Trademarks on EMC.com

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

Please refer to the Third Party Copyright Read Me document on the EMC Smarts VoIP Performance Manager installation CD for details of any third party software license notices.

Date of issue: 04 August 2008

Product Version: VoIP PM 2.0.2

Table of Contents

of 204

Table of Contents Introduction...............................................................................................................................5 About this Guide .......................................................................................................................6 Documentation Conventions .....................................................................................................8 Before you Start ......................................................................................................................10

System Requirements ............................................................................................................................11 Architectural Overview...........................................................................................................12 Dedicated Server Components ................................................................................................14 Client Component Requirements ............................................................................................15 Screen Size, Resolution & Colors ...........................................................................................16 Time Synchronization .............................................................................................................17 Supported Platforms................................................................................................................18

Deployment.............................................................................................................................................21 Deployment Procedures ..........................................................................................................22 Single Vendor Network - non CUCM 3.3 & 4........................................................................23 Single Vendor Network - CUCM 3.3 & 4...............................................................................25 Multi Vendor Network excluding CUCM 3.3 & 4..................................................................27 Multi Vendor Network including CUCM 3.3 & 4 ..................................................................29 Multiple Monitoring Servers...................................................................................................31 Monitoring Unity excluding CUCM 3.3 & 4 ..........................................................................33 Monitoring Unity including CUCM 3.3 & 4...........................................................................35

Installation..............................................................................................................................................37 Installation Procedures ............................................................................................................38 Prerequisites ............................................................................................................................39 Installing the Server Component.............................................................................................41 Installing the Client Only ........................................................................................................57 Nortel - Patch Installation .......................................................................................................63 HTTPS Web Interface Protocol ..............................................................................................65

Configuration .........................................................................................................................................69 Configuration Procedures........................................................................................................70 Logging On .............................................................................................................................71 Avaya Communications Manager ...........................................................................................74 Cisco Unified CallManager 3.3 & 4......................................................................................101 Cisco Unified Communications Manager .............................................................................114 Cisco Unity Integration .........................................................................................................145


of 204

Cisco Off Cluster CDRs........................................................................................................147 Nortel Communication Server ..............................................................................................149 Setting up Multiple Monitoring Servers................................................................................164 Setting up the Client (GUI) ...................................................................................................165

Additional Information........................................................................................................................167 Stopping the Service .............................................................................................................168 Upgrade Installation ..............................................................................................................173 Patch Installation...................................................................................................................179 Manual Start-Up....................................................................................................................181 Uninstalling...........................................................................................................................183

Technical Support ................................................................................................................................195 Support Procedures ...............................................................................................................196 IRFAX...................................................................................................................................197

Index......................................................................................................................................................199

Introduction

of 204

Introduction

EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya provides a comprehensive monitoring and management platform for the following IP telephony networks:

• Avaya Communications Manager

• Cisco Unified Communications Manager, versions 5 and 6

• Cisco CallManager version 3.3 and Cisco Unified CallManager version 4.x (as a Managing Node *)

• Nortel Communication Server 1000, versions 4.0, 4.5 and 5.0

* In order to monitor CallManager 3.3 and 4.x, Unity, TFTP and Exchange servers, EMC Smarts VoIP Performance Manager for Cisco v4 should be retained on these devices with EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya set up as a Managing Node. This Installation Guide contains the required information for this set up.

This Installation and Configuration Guide provides the necessary information to assist with the installation and setup of EMC Smarts VoIP Performance Manager. This information includes;

• Deployment check list

• Installation procedures

• Configuration requirements

• Instructions on how to apply subsequent patch files and Service packs

• Instructions on how to uninstall EMC Smarts VoIP Performance Manager

NOTE: Elements of this Installation Guide are also provided by way of an HTML Help file on the installation CD. This file is normally only accessed from the View Install Guide button on the Select Component dialog box of the InstallShield process. When viewing this file from the CD you should not encounter any difficulties, however, due to a previous Microsoft security update #896358 it may not be possible to view HTML Help files over a network connection. The Microsoft web site offers some suggestions of how to overcome this situation if it becomes a problem in your environment.


of 204

About this Guide Before reading this documentation it is expected that you will have an understanding of the environment, the hardware and the various software applications that you are intending to monitor. Where necessary this guide will cover the interaction between EMC Smarts VoIP Performance Manager and other hardware/software but it will not provide detailed information about their operations. Please refer to the individual hardware/software manuals and guides for such information.

Audience & Purpose This EMC Smarts VoIP Performance Manager Installation Guide is intended as a reference source for personnel who are responsible for installing and maintaining the system. It provides example deployment scenarios for various IP telephony network configurations and the associated installation and configuration steps. Information for subsequent patch installations and instructions on how to uninstall the product are also included.

Online Help The content of this PDF file is also contained in the VoIP Performance Manager Online Help System. The Online Help can be viewed by selecting the Help item from the VoIP Performance Manager menu bar and then selecting Contents.

Context sensitive help, which provides specific information about the function being performed, is also available by pressing the F1 key or, where available, the Help button on most VoIP Performance Manager windows and dialog boxes.

NOTE: The Online Help is provided by way of HTMLHelp (.chm files) which is installed locally into the User Interface folder of the EMC Smarts VoIP Performance Manager installation. It may not be possible to view this HTMLHelp over a network connection due to Microsoft security update #896358 . If this is an issue the Microsoft web site offers some suggestions of how to overcome this situation.

of 204

Other Documentation The complete set of PDF documentation is available from the Windows® operating system Start menu.

All Programs > EMC Smarts VoIP Performance Manager> EMC Smarts VoIP Performance Manager Documentation

The documentation provided includes:

Installation Guide This document.

System Guide Provides comprehensive details and instructions on the use of the VoIP Performance Manager user interfaces and the range of core functions, including detailed configuration syntax information.

User Guide Provides general information and instructions using the pre-packaged 'Knowledge Tools" that are provided with VoIP Performance Manager. It also included details on the range of EMC Smarts common features that are available for use with VoIP Performance Manager.

Record Guides The Record Guides supply detailed information about each of the records, and their associated fields, that are supplied with VoIP Performance Manager. Records are identified by both short names and long names, a guide is provided for each.

Third Party Software License Guide This guide provides copyright and licensing details of all third party open source software modules used within this VoIP Performance Manager product suite.


of 204

Documentation Conventions This guide makes use of the following documentation conventions:

Bold Bold text is used for emphasis and in a procedure indicates a key, link or menu option that is to be selected.

BoldItalic Bold and italic text in a procedure indicates a button that is to be selected.

Ctrl+V Indicates two keys that must be pressed sequentially.

Italic Indicates emphasis or a EMC Smarts VoIP Performance Manager document name (i.e. a Display, Analyst, etc).

Syntax Conventions Conventions for defining syntax in VoIP Performance Manager are as follows:

{Option A | Option B} Braces - A group of items included within braces and separated by vertical lines indicate a list from which one item is to be input (e.g. include either ‘Option A’ or ‘Option B’ but not both). The braces are not input.

| When shown within braces the vertical line separates mutually exclusive choices, the line is not included in the input. In other cases, without braces, the vertical line is used to separate multiple items and is included as part of the input.

Item A[, Item B] Brackets - Items included within brackets indicate options from which one or none may be input (often includes a comma (,) as the first character since a list of options will normally be separated by a comma). Except where otherwise noted the brackets themselves should not be input.

NOTE: Section names in INI files are enclosed by literal brackets, in these cases they do not represent options and form part of the input.

<value> The enclosed text describes a constant which should be substituted with an appropriate value. The <> characters are not input.

, ( ) / ; etc These general punctuation marks are included in the input exactly as they appear in the syntax.

"[" Quotation marks around a symbol indicate that the character is required and must be input as shown. The quotation marks are not input.

… Ellipsis - An ellipsis immediately following a pair of brackets or braces indicates that the enclosed sequence of syntax items can be repeated multiple times. For example, TME USER (<user>[, <user>]…)

of 204

For example, the following is a section of configuration syntax.

SUBSYS ABCD [AUTO-INV {HARDWARE|SOFTWARE|SCOBOL} ({ON|OFF})] [TME-USER ([<nt-host>\] <user>[, <user>])]

• The words AUTO-INV are options, but if you include them, then you MUST include ONE ONLY of HARDWARE, SOFTWARE, or SCOBOL and you must include one of ON or OFF surrounded by parenthesis.

• The words TME-USER are optional, but they must be followed by parenthesis which must contain the name of a user which can optionally be preceded by an NT host name followed by a \ and can optionally be followed by a comma and another user name.


of 204

Before you Start To successfully complete the EMC Smarts VoIP Performance Manager installation you will need the following items:

• Release Notes.

• Installation CD.

• For Nortel monitoring the EMC Smarts VoIP Performance Manager Nortel patch file will be required.

• License keys (see below).

• A separate Windows® operating system computer, outside of the IP telephony PBX/Cluster, onto which the EMC Smarts VoIP Performance Manager Monitoring Server can be installed. The EMC Smarts VoIP Performance Manager GUI may also be installed on this same machine or on a separate device.

IMPORTANT NOTE: Please refer to the Prerequisites section before attempting to start the EMC Smarts VoIP Performance Manager installation.

License Keys Product license keys are sent by email. This email contains two sets of license data, the inline text in the email and a series of attached text files. You can either:

1) Save the attached text files to a convenient location, then during the installation specify the location of where these have been saved, or

2) Copy the entire text contents from the email into the Clipboard (not the contents of the attached text files), then during the installation choose the Get License contents from Clipboard option and select the Paste from Clipboard button.

System Requirements

of 204

System Requirements


of 204

Architectural Overview The EMC Smarts VoIP Performance Manager architecture is made up of six different components, each of which serves a different purpose within the VoIP Performance Manager deployment.

The first component of is the VoIP Performance Manager Agent, provided by the VoIP Performance Manager for Cisco v4 product. This component should only be installed on Cisco Unified Call Manager 4, Unity and Exchange servers and is responsible for gathering metrics about the health and performance of these servers and the Cisco IP telephony applications running on them. Please refer to the EMC Smarts VoIP Performance Manager for Cisco v4 Installation Guide for further details.

When installing VoIP Performance Manager on any other server, you will be prompted to select which of the remaining five components are required.

It is possible to install all five components on one dedicated VoIP Performance Manager server, which may be appropriate in a small environment of less than 5,000 phones. In larger environments, it may be more appropriate to distribute the different components across two or more dedicated servers.

Three of these components should only be installed on a dedicated VoIP Performance Manager server. These are:

• Monitoring Server The purpose of the Monitoring Server component is to monitor the IP telephony appliance clusters by connecting to and polling their external APIs over the IP network. It is not necessary to install this component if there are no Avaya PBXs, Cisco Unified Communications Manager or Nortel appliances in the IP telephony environment under management.

System Requirements

of 204

• Managing Server The purpose of the Managing Server component is to aggregate and consolidate data from multiple Monitoring Servers (installed on other VoIP Performance Manager servers), Windows Servers and from VoIP Performance Manager agents installed on Cisco Unified Call Manager 4, Unity and Exchange servers.

• Web Server The purpose of the Web Server component is to provide read-only access to VoIP Performance Manager performance data via a Web Browser over the Internet or Intranet.

One dedicated VoIP Performance Manager server may host all or any combination of these three components, depending on the size of the IP telephony environment to be monitored.

The two remaining components may be installed either on a dedicated VoIP Performance Manager server or on any Windows server. These are:

• Client The Client is the Graphical User Interface (GUI) that is used to view real-time and historical data from the IP telephony environment. It is also used to configure VoIP Performance Manager. The Client may be installed on the same machine as other VoIP Performance Manager server components or on a separate machine. At least one copy of the Client must be installed somewhere in the monitoring environment in order to view performance data and configure VoIP Performance Manager.

• Windows Server The Windows Server component may be installed on any Windows server to monitor the health and performance of that server and any services running on it. It is used to supply performance data for any ancillary applications running on the Windows server which form part of the overall IP telephony environment.

See Dedicated Server Requirements and Client Component Requirements for system specifications.


of 204

Dedicated Server Components The system requirements for a dedicated EMC Smarts VoIP Performance Manager server are as follows:

Minimum Specification

Component Minimum Specifications

Processor (CPU): Intel Pentium® IV 2.4GHz Dual-core Processor

System Memory (RAM): 2GB

800MB for the base installation

Another 60MB of free disk space is required for temporary files during the installation.

Hard Drive Space (NTFS):

2.5GB for the MSDE database

Operating System: Microsoft Windows® XP Microsoft Windows Server® 2003 (recommended) Microsoft Windows 2000

Recommended Specification

Component Recommended Specifications

Processor (CPU): Intel Pentium® Xeon® 2.4GHz Dual-core Processor

System Memory (RAM): 4GB

800MB for the base installation


Hard Drive Space (NTFS):

2.5GB for the MSDE database

Operating System: Microsoft Windows XP Microsoft Windows Server 2003 (recommended) Microsoft Windows 2000

System Requirements

of 204

Client Component Requirements The system requirements for the EMC Smarts VoIP Performance Manager Client component, when installed on a Windows operating system machine that is not a dedicated EMC Smarts VoIP Performance Manager server, are as follows:

Component Minimum Specifications

Processor (CPU): Intel Pentium® III

System Memory (RAM): 128MB

GUI - 435MB (or FAT 870MB) Web Interface - 92MB (or FAT 184MB) Tomcat Web Server - 140MB (or FAT 280MB)

Hard Drive Space (FAT32 or NTFS):


Operating System: Microsoft Windows® XP Microsoft Windows Server® 2003 (recommended) Microsoft Windows 2000 Microsoft Windows Vista®


of 204

Screen Size, Resolution & Colors All EMC Smarts VoIP Performance Manager GUI and Web Displays have been designed to run at a screen resolution of 1024 x 768 pixels. Setting the monitor display properties to this resolution will ensure that all Displays are shown correctly.

If it is not possible to set the monitor to this resolution, normal Windows procedures can be used to re-size the Display to fit correctly so that all data is visible.

When using the VoIP Performance Manager Windows Alert Board maps it is recommended that a minimum 16-bit color mode be used on the display adapter. If the display adapter can only be set for 256 colors some palette switching may occur. The effects of this will be noticed as strange outlines and washed out or iridescent colors.

System Requirements

of 204

Time Synchronization Due to the time calculations that some pre-packaged Where Clauses use in EMC Smarts VoIP Performance Manager, it is important to ensure that all VoIP Performance Manager nodes in your environment are synchronized with a time server. This will avoid missing data from Displays and Database Collections, or Alerts from Thresholds and Analyst rules.


of 204

Supported Platforms Avaya Communications Manager

Software Version

Avaya Communication Manager 4.0, 3.x 2.x, 1.x

Hardware Model

Media Servers S8720, S8710, S8700, S8500, S8400, S8300

DEFINITY G3 running R9 or later

Media Gateways G700, G650, G350, G250, G1501

Phones 96xx IP Phones2 46xx IP Phones2 16xx IP Phones IP Softphone IP Agent Digital & Analog Phones

1. Support is pending field test validation 2. Some Avaya 46xx and 96xx handset models require firmware updates to send accurate Voice

Stream quality information. To assist in highlighting this issue, EMC Smarts VoIP Performance Manager includes a Display listing handsets with firmware versions known to produce erroneous data.

System Requirements

of 204

Cisco Unified Communications Manager

Software Version

Cisco Unified Communications Manager 5 and 6

Hardware Model

Cisco IP Phones 7902, 7905, 7910, 7911, 7912, 7920, 7940, 7941, 7960, 7961, 7970, 7985

Cisco Gateways 2600 series, 2800 series, VG series, AS5400

Cisco Analogue Telephone Adaptors ATA 186, ATA 188

Cisco Unified Video Advantage

Cisco Soft IP Phone Cisco IP Communicator

Nortel Communication Server PROGNOSIS IP Telephony Manager for Nortel currently supports the following Nortel software and hardware versions:

Software Version

Nortel Communication Server 1000 5.0

4.5

4.0

Hardware Model

Nortel Communication Server CS1000 E (Standard enterprise solution)

CS1000 S (Small business)

CS1000 M (Legacy Meridian upgraded to IP capabilities)

Deployment

of 204

Deployment


of 204

Deployment Procedures This section provides diagrams for a number of scenarios that illustrate suggested ways that EMC Smarts VoIP Performance Manager can be set up, based upon various IP telephony vendor environments.

Please ensure that these deployment scenarios are reviewed in order to gain a basic understanding of how EMC Smarts VoIP Performance Manager is setup to monitor various IP telephony vendor systems. These scenarios cover simple installations to monitor single vendor PBX /Cluster environments to more complex installations for multi-PBX/Cluster, multi-vendor environments. Detailed installation and configuration instructions are contained in other sections of this guide.

Deployment Scenarios:

Single Vendor Network (not CUCM 3.3 or 4)

Single Vendor Network (with CUCM 3.3 or 4)

Multi Vendor Network, excluding CUCM 3.3 & 4

Multi Vendor Network, including CUCM 3.3 & 4

Multiple Monitoring Servers

Monitoring Unity Servers excluding CUCM 3.3 & 4

Monitoring Unity Servers including CUCM 3.3 & 4

Deployment Considerations

In an environment containing one or more PBXs/Clusters, bandwidth usage on the WAN link between the Network Operations Center and a remote PBX/Cluster may be a concern. To minimize VoIP Performance Manager bandwidth usage on the WAN it is recommended to position an VoIP Performance Manager Monitoring Server close to (i.e. in the same LAN as) the PBX/Cluster being monitored. The result of configuring the VoIP Performance Manager deployment in this manner is that the higher bandwidth traffic between the Monitoring Server and the PBX/Cluster will be restricted to the LAN, while the metrics collected by the Monitoring Server will be passed from the Monitoring Server to the central VoIP Performance Manager Managing Server as low bandwidth, compressed binary data traffic, thus conserving VoIP Performance Manager bandwidth usage on the WAN link.

Deployment

of 204

Single Vendor Network - non CUCM 3.3 & 4 A single installation of the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Monitoring Server is capable of monitoring multiple IP telephony PBXs/Clusters. The Monitoring Server should be a standalone machine with a connection to each PBX/Cluster. The VoIP Performance Manager Client (GUI) can be installed on the same machine as the Monitoring Server or a copy can be installed on one or more separate machines that are connected to the Monitoring Server.

NOTE: In the case of Avaya up to 10 Avaya PBXs can be monitored by a single Monitoring Server installation. If you have a requirement to monitor more than 10 Avaya PBXs please contact your EMC Technical Support.


of 204

Deployment Steps Step 1 Install the Monitoring Server

On a Windows® machine that is separate from the IP telephony network devices install the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Monitoring Server application. The Client (GUI) component can also be included with this installation if required.

Step 2 Install the Client (Optional) Optionally, or in addition to, the Client (GUI) can be installed onto one or more separate machines that are linked to the IP address of the Monitoring Server.

Step 3 Configure the Monitoring Server The Monitoring Server will now need to be configured for the required vendor. Please consult the Configuration section of this guide for specific vendor configuration details.

Step 4 Check the Node Navigator From the GUI view the Node Navigator of the Monitoring Server and expand the Entire Network folder. Check that all vendor devices to be monitored are shown. If not recheck the configuration steps on the Monitoring Server.

Step 5 Start Alerts and Databases (if applicable) Depending upon the vendor type, certain Alerts and Databases may now need to be started. Where applicable these will be detailed in the Configuration section of this guide.

Deployment

of 204

Single Vendor Network - CUCM 3.3 & 4 EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya can be used to monitor Cisco CallManager 3.3 and Cisco Unified CallManager 4 clusters. However, this set up requires VoIP Performance Manager for Cisco v4 to be installed onto the Cisco CallManager 3.3/Cisco Unified CallManager 4 cluster components ('on-board' monitoring) and a separate machine used for an VoIP Performance Manager for Cisco v5+ and Avaya installation that will be used as the Managing Server to relay data to the Client (GUI).


of 204

Deployment Steps Step 1 Install and configure EMC Smarts VoIP Performance Manager for Cisco V4

If not already done so, install EMC Smarts VoIP Performance Manager for Cisco V4 onto each Cisco CallManager 3.3/Cisco Unified CallManager 4 Subscriber node and then on to the Publisher node. Please refer to the separate EMC Smarts VoIP Performance Manager for Cisco V4 Installation Guide for details.

Step 2 Install the Managing Server On a Windows® machine that is separate from the IP telephony network devices install the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Managing Server application. The Client (GUI) component can also be included with this installation if required.

Step 3 Install the Client (Optional) Optionally, or in addition to, the Client (GUI) can be installed onto one or more separate machines that are linked to the IP address of the Managing Server.

Step 4 Configure the Managing Server for CUCM 3.3 & 4 The Managing Server will now need to be configured for the Cisco CallManager 3.3 and/or Cisco Unified CallManager 4 network. Please consult the Configuration section of this guide for details.

Step 5 Check the Node Navigator for Cluster Node Groups From the Client (GUI), go to the Node Navigator of the Managing Server and confirm that:

a) New Node Groups for the various clusters are now visible.

b) All required IP telephony devices are shown.

A few minutes should be allowed for the information to propagate through to the Managing Server following completion of the configuration steps.


Deployment

of 204

Multi Vendor Network excluding CUCM 3.3 & 4 EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya can be used to monitor different IP telephony vendor types through the same Monitoring Server. However, Cisco CallManager 3.3 and Cisco Unified CallManager 4 which require 'on-board' monitoring need a different set up which is covered in the next section.


of 204

Deployment Steps Step 1 Install the Monitoring Server

On a Windows® machine that is separate from the IP telephony network devices install the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Monitoring Server application. The Client (GUI) component can also be included with this installation if required.

Step 2 Install the Client (Optional) Optionally, or in addition to, the Client (GUI) can be installed onto one or more separate machines that are linked to the IP address of the Monitoring Server.

Step 3 Configure the Monitoring Server for Vendor A The Monitoring Server will now need to be configured for the first vendor type. Please consult the Configuration section of this guide for specific vendor configuration details.

Step 4 Configure the Monitoring Server for Vendor B The Monitoring Server will now need to be configured for the second vendor type.

Step 5 Check the Node Navigator From the Client (GUI) view the Node Navigator of the Monitoring Server and expand the Entire Network folder. Check that all vendor devices to be monitored are shown. If not recheck the configuration steps on the Monitoring Server.


Deployment

of 204

Multi Vendor Network including CUCM 3.3 & 4 EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya can also be used to monitor Cisco CallManager 3.3 and Cisco Unified CallManager 4 clusters together with the range of other supported IP telephony platforms. However, this set up requires VoIP Performance Manager for Cisco v4 to be installed onto the Cisco CallManager 3.3/Cisco Unified CallManager 4 cluster components ('on-board' monitoring) and a separate machine used for an VoIP Performance Manager for Cisco v5+ and Avaya installation that will be used as the Managing Server to combine data from all of the monitored platforms.


of 204


If not already done so, install EMC Smarts VoIP Performance Manager for Cisco V4 onto each Cisco CallManager 3.3/Cisco Unified CallManager 4 Subscriber node and then on to the Publisher node. Please refer to the separate EMC Smarts VoIP Performance Manager for Cisco V4 Installation Guide for details.



Step 4 Configure the Managing Server for the non CUCM 3.3 & 4 Vendor The Managing Server will now need to be configured for the non CallManager 3.3/4 vendor type. Please consult the Configuration section of this guide for specific vendor configuration details.







Deployment

of 204

Multiple Monitoring Servers EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya can be set up to use multiple Monitoring Servers. When multiple Monitoring servers are used, an VoIP Performance Manager Managing Server needs to be installed in order to combine data for display through the GUI.

NOTE: There must not be more than one Monitoring Server connected to the same PBX/Cluster, as this will negatively impact the performance of the PBX/Cluster. The same PBX/Cluster, device or node names must not be used in different PBX/Clusters. All PBX/Cluster, device and node names need to be unique across the entire monitoring network. The duplication of the names that VoIP Performance Manager allocates to two different PBX/Clusters can lead to the VoIP Performance Manager GUI showing the message “Data source unavailable”.


of 204

Deployment Steps Step 1 Install the Monitoring Server (for PBX/Clusters A & B)

On a Windows® machine that is separate from the IP telephony network devices install the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Monitoring Server application. This will be the Monitoring Server for PBX/Cluster A and B.

Step 2 Install the Monitoring Server (for PBX/Cluster C) On another Windows machine that is also separate from the IP telephony network devices install another copy of the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Monitoring Server application. This will be the Monitoring Server for PBX/Cluster C.

Step 3 Install the Managing Server On another separate Windows machine install the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Managing Server application. The Client (GUI) component can also be included with this installation if required.


Step 5 Configure the Monitoring Servers Each Monitoring Server will now need to be configured for the required vendor. Please consult the Configuration section of this guide for specific vendor configuration details.

Step 6 Configure the Managing Server Update the NETWORK Configuration on the Managing Server by adding a MANAGED-NODEs statement with the IP address of each Monitoring Server.

Step 7 Check the Node Navigator From the GUI view the Node Navigator of the Managing Server and expand the Entire Network folder to check that all vendor devices to be monitored are shown. If not recheck the configuration steps on each Monitoring Server.


Deployment

of 204

Monitoring Unity excluding CUCM 3.3 & 4 A stand-alone Unity server, with EMC Smarts VoIP Performance Manager for Cisco v4 installed, can be monitored directly by an VoIP Performance Manager for Cisco v5+ and Avaya Managing Server.


of 204


If not already done so, install EMC Smarts VoIP Performance Manager for Cisco V4 onto the Unity server as per the EMC Smarts VoIP Performance Manager for Cisco V4 Installation Guide.



Step 4 Configure the Managing Server The Managing Server will now need to be configured for the required IP telephony network vendor. Please consult the Configuration section of this guide for specific vendor configuration details.

Step 5 Configure the Managing Server for Cisco Unity Integration On the Managing Server amend the NETWORK and NODEGROUP Configurations to include the Unity Server.

Step 6 Check the Node Navigator From the Client (GUI) view the Node Navigator of the Managing Server and expand the Entire Network folder to check that all required nodes plus the Unity server are shown.


Deployment

of 204

Monitoring Unity including CUCM 3.3 & 4 The following scenario depicts monitoring a Unity server that is part of a Cisco CallManager 3.3 or Cisco Unified CallManager 4 environment together with another network running a different vendor environment. Using the following set up, data from all devices can be monitored by the VoIP Performance Manager for Cisco v5+ and Avaya Managing Server.


of 204

Cisco CallManager 3.3/Cisco Unified CallManager 4 devices and Unity servers can only be monitored by EMC Smarts VoIP Performance Manager for Cisco v4 installations. VoIP Performance Manager for Cisco v5+ and Avaya should not be installed onto any of these devices.

In this situation each CallManager 3.3 or 4 Subscriber and Publisher plus the Unity server will need to have EMC Smarts VoIP Performance Manager for Cisco v4 installed. The Publisher is then connected to the VoIP Performance Manager for Cisco v5+ and Avaya Managing Server. This connection will allow the Client (GUI) to display data from the CallManager 3.3 or 4 cluster and the Unity server together with data from any other connected network.


If not already done so, install EMC Smarts VoIP Performance Manager for Cisco V4 on to each Cisco CallManager 3.3/Cisco Unified CallManager 4 Subscriber node and then on to the Publisher node and the Unity server. Please refer to the separate EMC Smarts VoIP Performance Manager for Cisco V4 Installation Guide for details.



Step 4 Configure the Managing Server for the non CUCM 3.3 & 4 Vendor The Managing Server will now need to be configured for the non CallManager 3.3/4 vendor type. Please consult the Configuration section of this guide for specific vendor configuration details.







Installation

of 204

Installation


of 204

Installation Procedures EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya consists of the following components:

• Client (GUI)

• Monitoring Server

• Managing Server

• Windows Server

• Web Server

These EMC Smarts VoIP Performance Manager components are installed 'off-board' from the IP telephony network devices, that is they need to be installed on one or more Windows® operating system machines that are separate from the IP telephony PBXs/Clusters (see the Architectural Overview for further details).

For Cisco CallManager 3.3, Cisco Unified CallManager 4 and Cisco Unity devices which permit 'on-board' monitoring, that is where the software can be installed directly onto these devices, the EMC Smarts VoIP Performance Manager for Cisco v4 product needs to be used.

The EMC Smarts VoIP Performance Manager Client is the Graphical User Interface (GUI) that provides the Displays and reports to enable users to view performance data.

This chapter includes the following sections:

Prerequisites

Installing the Server Components

Installing the Client Only

Nortel - Patch Installation

HTTPS Web Interface Protocol

Installation

of 204

Prerequisites TIP: If you have a firewall in place between the IP telephony PBX/Cluster, and the EMC Smarts VoIP Performance Manager Server you will need to ensure that the HTTPS port 8443 (used to carry SOAP protocol) and UDP port 161 (SNMP) are enabled. If you have a firewall in place between the EMC Smarts VoIP Performance Manager Server and the Client (GUI) you must enable TCP ports 1960, 1961 and 1962. Please also refer to the following text for further vendor specific firewall requirements.

Cisco Unified Communications Manager Before commencing the installation of the EMC Smarts VoIP Performance Manager Server ensure that you have the following information.

1. The Administrator Password

2. The following information for each appliance to be monitored.

• Publisher name (this is the name to be used by EMC Smarts VoIP Performance Manager and does not have to correspond to the Cisco name).

• IP address

• Login name

• Password

• Cisco Unified Communications Manager version

Please also note the following requirements:

1. The following software should not be installed:

• Virus Checking Software

• Cygwin

2. McAfee VirusScan 8.0i (please refer to the Release Notes for the latest information) The SFTP server component will not run under McAfee VirusScan 8.0i with the result that CDR files will not be downloaded from the Cisco Unified Communications Manager appliances. The workaround is to disable McAfee VirusScan 8.0i or switch off the ‘Buffer Overflow Protection’ option.

To switch off the ‘Buffer Overflow’ Protection option, open the Virus Scan Console (Network Associates) from the Start > Programs menu, then right click on the ‘Buffer Overflow Protection’ line then choose ‘Properties’. On the ‘Buffer Overflow Protection’ tab, uncheck the box next to ‘Enable Buffer Overflow Protection’, click Apply then click OK.

More Details: http://forums.mcafeehelp.com/viewtopic.php?t=30980

http://forums.mcafeehelp.com/viewtopic.php?t=30980�


of 204

3. Firewall The following ports must be open between EMC Smarts VoIP Performance Manager and the Cisco Unified Communications Manager appliances being monitored.

22 SFTP used to transfer CDRs

80 HTTP polling of IP phones for real-time information.

161 SNMP

1960 Communication between EMC Smarts VoIP Performance Manager nodes as well as connecting the GUI to the Managing Server.

8443 HTTPS/SSL monitoring requests.

Cisco CallManager 3.3 and Cisco Unified CallManager 4.x 1. Ensure that unique device descriptions are entered into the CallManager configuration.

EMC Smarts VoIP Performance Manager requires that the CallManager be configured with unique descriptions for each associated device. However, the description field is free text and the use of unique descriptions cannot be authenticated. If a unique value is not assigned to this field then EMC Smarts VoIP Performance Manager will not be able to match perfmon status and statistics to the known devices. This leads to incorrect status being displayed and problems when converting between device and IP address.

2. Activate and run the CCM service on the publisher. If the publisher has its CCM process de-activated it causes the Cisco RIS service running on the publisher to be excluded from any information about devices registered with the cluster. In this situation when EMC Smarts VoIP Performance Manager queries the RIS service it will report the error message "RIS Information cannot be obtained from any node". This results in the IP address of devices not being determined by EMC Smarts VoIP Performance Manager causing some drill-downs not to work.

Installation

of 204

Installing the Server Component The EMC Smarts VoIP Performance Manager Installation includes the following Server options;

• Monitoring Server

• Managing Server

• Windows Server

• Web Server

If required, the Client (GUI) can be installed with the Server onto the same machine in the one installation. To do this, simply select the Client component along with the Server at Step 2.

The installation steps for each Server type are similar and are described in this section. For information about the use of each of these Server options please refer to the Architectural Overview section of this guide.

NOTE: You will need to have Administrator rights for the machine onto which you are installing the EMC Smarts VoIP Performance Manager Server. In addition you will also need SQL Administrator rights if you are using an existing SQL server installation.

Install the EMC Smarts VoIP Performance Manager Server on to a separate Windows® operating system machine from the IP telephony devices.


of 204

Procedure Step 1 Log on to the required machine as Administrator, or as a user with administrative privileges,

and then insert the installation CD into the CD-ROM drive.

If autorun is activated the CD will start the installation process automatically. However, if the install program does not start, go to My Computer, select the CD-ROM drive and then double-click on the file named Setup.exe.

The InstallShield program will now run and the following Welcome dialog will be presented:

Select the Next > button to continue.

Installation

of 204

Step 2 Select Components

This dialog box provides the options of installing the various EMC Smarts VoIP Performance Manager components.

From here select the check box for each component to be installed:

See the Architectural Overview section for details of the various options.



of 204

Step 3 Invalid License

The installation will now attempt to validate the EMC Smarts VoIP Performance Manager license files.

If the installation finds the valid license files they will be automatically installed and the installation will go directly to Step 5. However, if valid license files are not found the Invalid License dialog will be displayed and the following instructions will need to be carried out.

An email will be sent containing the license information. This email contains two sets of license data, the inline text in the email and a series of attached text files. You can either

a) Save the attached text files, then in the dialog box specify their location,

or

b) Copy the entire text contents from the email (not the contents of the attached text files) then choose the Get License contents from Clipboard option and select the Paste from Clipboard button.

When finished select the Next > button to continue.

Installation

of 204

Step 4 IP Telephony Platforms (Monitoring Server Only)

This dialog box is used to select which IP telephony platforms are to be monitored.

Check one or more supported appliances, as required, then select the Next > button to continue.


of 204

Step 5 Select SQL Server

The EMC Smarts VoIP Performance Manager Server requires an SQL database server to store CDR (Call Detail Records) data. A separate database with the appropriate user will be created under the SQL server selected. This step of the installation allows you to select any existing SQL database server that has been detected on the machine or you can choose to install a new copy by selecting the Install Microsoft SQL Server Desktop Engine (MSDE).

IMPORTANT NOTE: If a new instance of MSDE is selected then a machine reboot will be required after the installation has been completed. If a machine reboot is not desired then an existing copy of MSDE or SQL Server should be used.


If an existing SQL database server has been selected the installation will proceed directly to Step 7.

Installation

of 204

Step 6 End-User License Agreement

If a new MSDE installation was selected at Step 5 then the following screens will be displayed (Steps 6 and 6A)

If you have selected to install a new copy of MSDE the following End User Agreement will need to be read and acknowledged.

Select the Yes > button to accept the conditions and to continue with the installation.


of 204

Step 6A SQL Server Instance Name

If a new copy of MSDE has been installed the following dialog box will be displayed seeking a name for this SQL Server instance. You can choose to use the default name of VOIPPM or you can input your own name up to a maximum of 16 characters.


Installation

of 204

Step 7 Choose Destination Location

This dialog box is used to assign the folder path where this copy of EMC Smarts VoIP Performance Manager will be installed.

Check that the default path in the Destination Folder field is where you wish EMC Smarts VoIP Performance Manager is to be installed. If it is not, select the Browse button where an alternative folder path can be selected or a new folder name input.

Select the Next > button to continue. If a new folder name has been input EMC Smarts VoIP Performance Manager will now create the new folder.

IMPORTANT NOTE Absolute file name length cannot exceed 258 characters. As the relative path and file names of the EMC Smarts VoIP Performance Manager packaging can reach up to 210 characters, it is strongly recommended to limit the absolute path for the EMC Smarts VoIP Performance Manager GUI home installation folder to 45 characters.


of 204

Step 8 Choose Database Folder

The Choose Database Folder dialog box is used to specify a destination path for where the SQL database files will be stored.

You can select the default by clicking on the Next > button, or you can use the Browse button to set an alternative path.

Select the Next > button to proceed.

Installation

of 204

Step 9 Tomcat Web Server Port Number (Web Server Only)

If the Web Server option was not selected at Step 2 the installation will bypass Step 9 and proceed directly to Step 10.

If the option to install the EMC Smarts VoIP Performance Manager Tomcat Web Server has been selected at Step 2 the following window will be displayed.

The default port number 80 will be used for the Tomcat Web Server unless an alternative port number is added to this screen.



of 204

Step 10 Email Information

This dialog box is used to set up a default Profile for EMC Smarts VoIP Performance Manager Dispatch Manager. This is used to send alert messages and can be customized through the DISPMAN Configuration to send these messages to nominated people by email or pager.

Enter the IP address of your SMTP server and the email address of a default user to which system messages can be sent.


Installation

of 204

Step 11 Security Configuration

The Security Configuration provides the facility to allow or deny access to EMC Smarts VoIP Performance Manager functions or objects. This dialog box provides a limited range of security options that can be selected at this time. However, if required, security can be configured after installation, please refer to the Security section of the EMC Smarts VoIP Performance Manager System Guide or Online Help for full details.

IMPORTANT NOTE: Do not use the MAXIMUM security setting if you intend to run commands on this node from another node, e.g., if you are connected to the Publisher you will not be able to run commands on the other subscribers.



of 204

Step 12 Important Information

This dialog contains important information regarding the installation. Please review the contents carefully.


Installation

of 204

Step 13 Start Copying Files

This dialog box provides a list of all the installation settings that have been made. Review the settings, if any changes are required select the < Back button to return the required dialog and make the necessary adjustments.

If you are satisfied with the settings, select the Next > button to begin copying the installation files to your nominated directory.

Depending on the components selected at Step 2, the copying can take from 3 to 10 minutes. While the EMC Smarts VoIP Performance Manager files are being copied, you will see a progress indicator.

NOTE: Adobe Acrobat Reader - Some of the EMC Smarts VoIP Performance Manager documentation is distributed in Adobe Acrobat PDF format. If you do not have the Adobe Acrobat Reader installed, you will receive a prompt asking if you wish to install it.


of 204

Step 14 Installation Completed

When the installation is complete the final dialog box provides the option to Start the GUI and/or to open the Read me file.

If a new instance of MSDE was selected to be installed during the installation then the final dialog box provides the option to restart the computer now or restart it later. It is necessary to restart the computer so that all existing services continue to operate correctly.

Select the required options then click the Finish button to complete the EMC Smarts VoIP Performance Manager installation.

Installation

of 204

Installing the Client Only A copy of the EMC Smarts VoIP Performance Manager Client (GUI) needs to be installed so that the data being collected by the Managing/Monitoring Server can be viewed. The Client can be installed with the Server component onto the same machine or the Client can be installed onto a separate machine. This procedure outlines the steps to install the Client onto a machine that is separate from the Server components. To install the Client with the Server please refer to the Server installation section.

To install the Client carry out the following procedure.

Procedure Step 1 Log on to the required machine as Administrator, or as a user with administrative privileges,

then insert the installation CD into the CD-ROM drive.

If Autorun is activated the CD will start the installation process automatically. However, if the install program does not start, go to My Computer, select the CD-ROM drive and then double click on the file named Setup.exe.

The InstallShield program will now run and the following Welcome dialog will be presented.



of 204

Step 2 Select Components

The Select Component dialog box offers the option of installing the various EMC Smarts VoIP Performance Manager components.

Select the check box for the Client. If installing only the Client component ensure that the other options are unchecked.

See the Architectural Overview section for details of the various options.


Installation

of 204

Step 3 Choose Destination Location

This dialog box is used to assign the folder path where this copy of EMC Smarts VoIP Performance Manager will be installed.

Check that the default path in the Destination Folder field is where you wish IEMC Smarts VoIP Performance Manager to be installed. If it is not, select the Browse button where an alternative folder path can be selected or a new folder name input.

Select the Next > button to continue. If a new folder name has been input EMC Smarts VoIP Performance Manager will now create the new folder.

IMPORTANT NOTE Absolute file name length cannot exceed 258 characters. As the relative path and file names of the EMC Smarts VoIP Performance Manager packaging can reach up to 210 characters, it is strongly recommended to limit the absolute path for the EMC Smarts VoIP Performance Manager GUI home installation folder to 45 characters.


of 204

Step 4 Connection Details

This dialog box is used to specify the IP address of the EMC Smarts VoIP Performance Manager server that the GUI will connect to.

Enter the IP address of the server that has EMC Smarts VoIP Performance Manager installed.

NOTE: Where a Managing Server has been installed always connect the Client to this machine. This allows all configured nodes in the network to be seen by the Client. The Server to which the Client is connected can be changed at any time after installation by selecting ‘Connect’ from the File menu and entering a different IP address into the Logon dialog box.


Installation

of 204

Step 5 Start Copying Files

This dialog box provides a list of all the installation settings that have been made. Review the settings, if any changes are required select the < Back button to return the required dialog and make the necessary adjustments.

If you are satisfied with the settings, select the Next > button to begin copying the installation files to your nominated folder.

NOTE: Adobe Acrobat Reader - Some of the EMC Smarts VoIP Performance Manager documentation is distributed in Adobe Acrobat PDF format. If you do not have the Adobe Acrobat Reader installed, you will receive a prompt asking if you wish to install it.


of 204

Step 6 Installation Completed

When the installation is complete the final dialog box provides the option to Start the GUI and/or to open the Read me file.

Select the Finish button to start the EMC Smarts VoIP Performance Manager GUI. If you do not wish to start the GUI at this time, uncheck the Start GUI checkbox before selecting Finish.

Installation

of 204

Nortel - Patch Installation EMC Smarts VoIP Performance Manager has been upgraded with a patch installation that allows for the monitoring of Nortel IP telephony environments. A suite of pre-packaged Databases, Thresholds and Displays are included which allow for the immediate monitoring of data after installing the patch and carrying out some simple system configuration settings. EMC Smarts VoIP Performance Manager will monitor a range of Nortel data including Calls, Media Cards, Media Gateways, PBXs, Phones, QoS, Routes and Servers.

Deployment Checklist Before commencing this deployment please ensure that you have the following items:

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

• EMC Smarts VoIP Performance Manager License Key with Nortel Support.

• EMC Smarts VoIP Performance Manager Nortel patch

• Nortel PBX (aka switch) information

- A user-defined PBX name

- IP address of the PBX

- Log in credentials (admin)

Deployment Process The deployment process consists of the following three procedures, each of these are described in detail in this guide.

1. Install EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya and apply the patch file.

2. Configure EMC Smarts VoIP Performance Manager to monitor the PBX

3. Configure the Nortel PBX to send data to EMC Smarts VoIP Performance Manager.

Installing Nortel Monitoring To install the Nortel monitoring facility, carry out the following steps.

1. Install EMC Smarts VoIP Performance Manager for Cisco v5 + Avaya

• Before commencing the installation you will require the EMC Smarts VoIP Performance Manager license keys that include Nortel support.

• Refer to the standard Installation Procedures contained in this guide to install EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya.


of 204

2. Apply the patch file To install the patch proceed as follows:

Step 1 Copy the patch file to a temp folder on the Windows server.

Step 2 Go to the temp folder and double-click on the patch file name or icon.

Step 3 The InstallShield application will commence at the ‘Welcome’ page. Select the Next> button and follow the screen prompts to complete the patch installation.

Installation

of 204

HTTPS Web Interface Protocol The default Windows installation of EMC Smarts VoIP Performance Manager includes Sun JRE 1.3.1 and the Apache Tomcat Web server. These components are used to run the EMC Smarts VoIP Performance Manager Web interface, which by default uses HTTP protocol. However, should you require secure HTTPS protocol some additional configuration is required.

Running the Web interface over HTTPS To utilize HTTPS the following steps need to be completed:

A. Add SSL support to the JRE 1.3.1.

B. Generate your own or purchase the SSL certificate for your Web site and place it into Java keystore used by Tomcat.

C. Configure SSL connector in Apache Tomcat.

D. Instruct operators to use the HTTPS URL for access to the Web interface (most likely the normal HTTP access would be disabled).

These steps are detailed below:

Part A - Add Secure Sockets support to JRE 1.3.1

Step 1 Download JSSE from the Sun Web site. Go to: http://java.sun.com/products/jsse/index-103.html Scroll down and choose the required version. The 'domestic' version can only be downloaded in the USA and Canada. Either version provides sufficient stength of encryption for the purpose of running this Web interface. You will need to have an account with Sun, the registration is free.

Step 2 Extract 3 JAR files - jcert.jar, jnet.jar and jsse.jar from the downloaded ZIP file. The ZIP file has an internal directory structure and the JAR files are located in the jsse1.0.3_02/lib directory.

Step 3 Place these 3 JAR files into the directory: $EMC_Smarts_HOME/www/webserver/jre/lib/ext This adds SSL support to the Java Runtime Environment.


of 204

Part B - Generate or purchase the SSL certificate

The procedures for purchasing a real SSL certificate depend upon the provider you prefer to use. The following describes the simplest procedure for generating the security keys you can use to test your HTTPS setup. Note that this will result in browser warnings. A purchased certificate needs to be imported into Java keystore, as used by Tomcat. For details of ordering and importing the certificate see the documentation on Sun's keytool utility which is available on the Sun web site. For example, for version 1.3.1 you can use:

http://java.sun.com/j2se/1.3/docs/tooldocs/win32/keytool.html

To generate a key pair run the keytool.exe utility (located in $EMC_Smarts_HOME/www/webserver/jre/bin) using the following command lines:

C:\> Cd C:\Program Files\EMC Smarts VoIP Performance Manager\www\webserver\jre\bin

C:\Program Files\EMC Smarts VoIP Performance Manager\www\webserver\jre\bin> keytool -keystore ../../tomcat/conf/keystore -genkey -alias tomcat -keyalg RSA

Here the path after the filename 'keystore' is the name of the new keystore file. For the purpose of these instructions we assume that you have chosen your new keystore file to be located in the configuration directory of Tomcat ($EMC_Smarts_HOME/www/webserver/tomcat/conf/keystore) and that EMC Smarts VoIP Performance Manager is installed in the default location.

The keytool will ask you several questions. By default, Tomcat expects passwords 'changeit' for both keystore file and its entry in the keystore. If you use a different password, you will need to specify it later in the Tomcat configuration. It is important that you use the same password for both keystore and the Tomcat entry. When prompted for your first/last name type in the host name instead.

Part C - Configure SSL connector in Apache Tomcat

Open <EMC_Smarts_HOME>/www/webserver/tomcat/conf/server.xml in a plain text editor, such as Notepad, and add one more Connector element under the existing HTTP Connector. The following shows the text that you need to insert:

<Connector className="org.apache.catalina.connector.http.HttpConnector" port="8443" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="10" debug="0" scheme="https" secure="true"> <Factory className="org.apache.catalina.net.SSLServerSocketFactory" clientAuth="false" protocol="TLS" keystoreFile="conf/keystore" keystorePass="changeit" /> </Connector>

This instructs Tomcat to listen for SSL connections on port 8443 and assumes that the keystore file is located in Tomcat's conf directory. If you used a password other than 'changeit' when generating the key, you will also need to change the keystorePass value. When finished, restart Tomcat.

Further details are available at the Apache Tomcat site: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/ssl-howto.html

Installation

of 204

Part D - Use HTTPS URL

Start your browser and request https://<hostname>:8443/prognosis. The browser will warn you about self-signed certificate it cannot verify, but you will be able to establish a connection.

Configuration

of 204

Configuration


of 204

Configuration Procedures Once the EMC Smarts VoIP Performance Manager software has been installed on the required machines, it is now necessary to carry out some configuration procedures so that EMC Smarts VoIP Performance Manager is aware of the various devices that are to be monitored. This section outlines the various configuration steps that are required.

This chapter contains the following sections:

Logging On

Avaya Communications Manager

Cisco CallManager 3.3 & Cisco Unified CallManager 4

Cisco Unified Communications Manager

Cisco Unity Integration

Cisco Off Cluster CDRs

Nortel Communication Server

Setting up Multiple Monitoring Servers

Setting up the Client (GUI)

Configuration

of 204

Logging On In order to carry out the EMC Smarts VoIP Performance Manager configuration steps it will be necessary to log on to the Client (GUI).

Procedure Step 1 If on the final screen of the installation you have selected the ‘Start GUI’ option proceed to

Step 2, otherwise continue with the following procedure.

Start the GUI from the Windows® operating system Start menu, by selecting:

All Programs >EMC Smarts VoIP Performance Manager> VoIP Performance Manager GUI

Step 2 This will open the Server Logon dialog box.

The Server field shows the local server’s name, local host IP address and port number.

Step 3 Input your User ID and Password. This should be the same User ID and Password used to log on to your network. In the above example only the local user name is being specified; alternatively, you can log on in the format:

\<ms-domain>.<user>


of 204

Step 4 Select the Logon button and the Graphical User Interface will open.

The GUI is made up of the following components;

Step 5 If it has not already opened automatically, manually open the Welcome to EMC Smarts VoIP Performance Manager Display by clicking on the VoIP PM-Welcome document in the Document Navigator, you should see it as the very last item in the list.

Links in the ‘Configure’ section at the top of the Welcome to EMC Smarts VoIP Performance Manager Display provide access to instructions and, where applicable, configuration scripts for setting up specific IP telephony vendors.

For Avaya and Nortel this panel provides links to view the steps to Add, Edit and Delete devices. In addition the 'Manage' link will open a Display containing directions on how to configure the VoIP Performance Manager Managing Server.

Configuration

of 204

For Cisco Unified CallManager 4 and Cisco Unified Communications Manager links are provided which lead to Displays containing configuration instructions and options to run the necessary scripts to complete the configuration setup.

For Management Reporter the 'Manage' link will open a Display that provides current database status. If the databases are stopped an option is provided to start each one.

In some cases scripts are not available to complete certain configuration procedures, in these cases the set up is completed by using Configuration files which can be found in the Node Navigator located in the bottom left hand side of the GUI. Should the Node Navigator panel not be visible press the F4 key which will toggle the Node Navigator open/closed (alternatively you can select Managed Nodes from the View Menu).


of 204

Avaya Communications Manager After installing the EMC Smarts VoIP Performance Manager components, as described in the Installation section, a number of configuration procedures will need to be completed in order for the Monitoring Server to see the Avaya appliances. These procedures set up the system components to communicate with each other. This section provides step by step instructions on how to carry out these configurations.

Configuration Procedures

Step 1 PBX Configuration From the Node Navigator on the Monitoring Server update the following configuration files to add details of each PBX to be monitored. AVAYA_PBX Configuration for Avaya version 3 and 4 appliances. AVAYA_LEGACY Configuration for Avaya version 1 and 2 appliances AVAYA_DEFINITY Configuration for Avaya DEFINITY devices

Step 2 LSP Configuration If applicable, from the Node Navigator on the Monitoring Server update the AVAYA_LSP Configuration file to add details of each LSP to be monitored.

Step 3 RTCP Configuration Optional setting used to update the Call Quality of Service (QoS) levels. This only needs to be undertaken if your QoS criteria is different to the default settings.

Step 4 PASSWORDS Configuration Using the PASSWORDS Configuration file on the Monitoring Server add read-only logon details to allow VoIP Performance Manager access to the Avaya PBX.

Step 5 Create an Avaya Login account It is recommended to set up a separate login account for VoIP Performance Manager to use in order to access the Avaya PBX.

Step 6 Configure Avaya to send RTCP data In order for VoIP Performance Manager to receive RTCP data the Avaya PBX needs to be configured to send the reporting data to the IP address of the VoIP Performance Manager Server.

Step 7 Enable CDRs on Avaya In order for VoIP Performance Manager to provide a full range of call metrics, the Avaya PBX needs to be configured so that Call Detail Records (CDRs) are sent to the VoIP Performance Manager IP address.

Step 8 Check PBX Settings Check that the Avaya SAT program is set for the recommended System Parameters and Trunk Groups settings.

Step 9 Start the Alerts and Databases From the VoIP Performance Manager Client (GUI)I go to the Avaya Monitoring Node Display and select the Alerts and Databases that are to be run.

Configuration

of 204

AVAYA_PBX Configuration The AVAYA_PBX Configuration file is used to add the node name and IP address of each PBX that is to be monitored. Up to 10 PBXs can be monitored from a single EMC Smarts VoIP Performance Manager Monitoring Server.

This configuration file is accessed from the Node Navigator of the Monitoring Server by opening the Configurations folder. If the Node Navigator panel is not visible press the F4 key.

Right click on the AVAYA_PBX document then select Properties from the Context menu to open the Configuration screen as shown below.


of 204

NOTE: For each PBX added to the AVAYA_PBX Configuration a corresponding PASSWORDS Configuration entry needs to be made in order to allow EMC Smarts VoIP Performance Manager access to the required data. See PASSWORDS Configuration for Avaya for details.

ADD PBX (<pbxname>, ip=<ip_address>) DEFINE CDR (<pbxname>, format=<format_type>, timezone=<timezone>, ) DEFINE SAT_PROFILE (<pbxname>, mode=<modetype>)

The ADD PBX entry is used to add a PBX name and its corresponding IP address.

The DEFINE CDR statement is optional and is used to define the CDR format type plus a range of optional parameters. See the DEFINE_CDR section.

The DEFINE SAT_PROFILE statement is optional and is only used if the Avaya PBX has special settings or requirements. See the DEFINE SAT_PROFILE section.

Optional Parameters Optional parameters are available to add a customer and/or site name to a node/IP address. This information can be then used to assist in identifying data in the EMC Smarts VoIP Performance Manager Displays.

ADD PBX (<pbxname>, ip=<ip_address>)[, customer=<customer_name>][, site=<site_name>]) [DEFINE SAT_PROFILE (<pbxname>[, mode=telnet|ssh][, port=<port_number>])]

Configuration Syntax <pbxname> Name given to the PBX device.

<ip_address> IP address of the PBX device.

<customer_name> A customer name to associate with the PBX.

<site_name> A site (location) name to associate with the PBX.

<port_number> The SAT connection port on the PBX.

NOTE: A ‘-PBX’ suffix attached to the node name is a recommended convention for easy identification, but it is not mandatory.

Configuration

of 204

DEFINE CDR The DEFINE CDR statement in the AVAYA_PBX Configuration is optional and is used to define the CDR format type plus a range of optional parameters. Each of these parameters are described below.

Changing CDR Formats

The CDR format type that EMC Smarts VoIP Performance Manager expects from the PBX can be changed. Normally the PBX should be set to “unformatted” and VoIP Performance Manager will use that format by default since it contains the most data fields without any customization.

DEFINE CDR ( <pbxname>, format=unformatted )

However, the following formats can also be handled by EMC Smarts VoIP Performance Manager.

expanded Expanded format.

expanded-enhanced Expanded format with enhanced option.

unformatted Unformatted format.

unformatted-enhanced Unformatted format with enhanced options.

Format name options should be used with lower case letters.

Changing Time Zones

To adjust the static configuration for different time zones for each PBX, the following input can be used:

DEFINE CDR ( <pbxname>, timezone=+10.0 )

Where time zone can be set to any value from -12.0 to +12.0. This is the time zone set for the PBX – that is, in the example, the PBX is set in GMT+10. Decimal values can be specified for the time zone, e.g. timezone=-5.5. The value is always represented in hours from GMT.

Changing default EMC Smarts VoIP Performance Manager CDR device server port

To change the default TCP port of 50,000 used by EMC Smarts VoIP Performance Manager, you can edit the static configuration with an option similar to the following:

DEFINE CDR ( #GlobalDefault, port=49999 )

This changes the default port used by EMC Smarts VoIP Performance Manager for ALL PBXs being monitored. #GlobalDefault is a special key word used by EMC Smarts VoIP Performance Manager to denote that this option applies to ALL PBXs configured.

EMC Smarts VoIP Performance Manager currently does not support multiple ports for CDR collection, so individual PBX port settings cannot be specified.


of 204

Specifying a different MONTH/DAY ordering for a PBX

Avaya PBXs send a Date Record upon connection to EMC Smarts VoIP Performance Manager. The Date record specification can be found in the appendix. However the date itself is specified depending on locale options stored in the “change sys cdr” SAT command. If this is different from the default of “Month/Day” (i.e. “Day/Month”) then you can specify here:

DEFINE CDR ( \PBX, DDMM=true )

The default value is “false”.

Specifying a different IP address for CDRs than PBX IP address

Normally Avaya PBXs without CLAN (control-lan) cards will send CDRs along the same IP address as the PBX is configured on for SAT connections. However, with CLAN cards, EMC Smarts VoIP Performance Manager should be able to auto-detect the CLAN card and figure out which IP address the CDRs will be sent from.

In the event that EMC Smarts VoIP Performance Manager fails to detect the IP address, or the IP address is different (but not due to a CLAN card) then you can manually override the expected IP address for CDR records.

ADD PBX ( \PBX, ip=1.2.3.4 ) DEFINE CDR ( \PBX, ip=1.2.3.5 )

This specifies that the PBX is on 1.2.3.4 and will send CDRs from 1.2.3.5.

Configuration

of 204

DEFINE SAT_PROFILE The default PBX connections are secure (SSH) on port 5022. However, non-default connections can also be accommodated and the configuration settings for these are included in the optional DEFINE SAT_PROFILE statement.

Each PBX to be monitored can be added in one of the following formats;

Plain text (telnet) Connection - Port 5023 (Default)

ADD PBX (<pbxname>, ip=<ip_address>) DEFINE SAT_PROFILE (<pbxname>, mode=telnet)

Secure (SSH) Connection - Custom Port

ADD PBX (<pbxname>, ip=<ip_address>) DEFINE SAT_PROFILE (<pbxname>, port=<port_number>)

Plain text (telnet) Connection - Custom Port

ADD PBX (<pbxname>, ip=<ip_address>) DEFINE SAT_PROFILE (<pbxname>, mode=telnet, port=<port_number>)


of 204

AVAYA_DEFINITY Configuration The AVAYA_DEFINITY Configuration is used for Avaya DEFINITY® devices. The content of this configuration file is identical to the AVAYA_PBX Configuration. Please refer to the AVAYA_PBX Configuration section for details of how to complete the configuration syntax.

Configuration

of 204

AVAYA_LEGACY Configuration The AVAYA_LEGACY Configuration is used for Avaya Communication Manager version 1.x and 2.x devices. The content of this configuration file is identical to the AVAYA_PBX Configuration. Please refer to the AVAYA_PBX Configuration section for details of how to complete the configuration syntax.


of 204

AVAYA_LSP Configuration The AVAYA_LSP Configuration file is used to add the node name, IP address and primary-controller of each LSP that is to be monitored. Up to 20 LSPs can be monitored from a single EMC Smarts VoIP Performance Manager Monitoring Server.

This configuration file is accessed from the Node Navigator of the Monitoring Server by opening the Configurations folder. If the Node Navigator panel is not visible press the F4 key.

Right click on the AVAYA_LSP document then select Properties from the Context menu to open the Configuration screen as shown below.

Configuration

of 204

NOTE: For each LSP added to the AVAYA_LSP Configuration a corresponding PASSWORDS Configuration entry needs to be made in order to allow EMC Smarts VoIP Performance Manager access to the required data. See PASSWORDS Configuration for Avaya for details.

The default LSP connections are secure (SSH) on port 5022. However, non-default connections can be accommodated and the configuration settings for these are included in the following examples.

Each LSP to be monitored is added to the AVAYA_LSP Configuration in one of the following formats;

Secure (SSH) Connection - Port 5022 (Default)

ADD LSP (<lspname>, ip=<ip_address>, primary-controller=<pbxname>)

Plain text (telnet) Connection - Port 5023 (Default)

ADD LSP (<lspname>, ip=<ip_address>, primary-controller=<pbxname>) DEFINE SAT_PROFILE (<pbxname>, mode=telnet)

Secure (SSH) Connection - Custom Port

ADD LSP (<lspname>, ip=<ip_address>, primary-controller=<pbxname>) DEFINE SAT_PROFILE (<pbxname>, port=<port_number>)

Plain text (telnet) Connection - Custom Port

ADD LSP (<lspname>, ip=<ip_address>, primary-controller=<pbxname>) DEFINE SAT_PROFILE (<pbxname>, mode=telnet, port=<port_number>)

NOTE: An ‘-LSP’ suffix attached to the node name is a recommended convention for easy identification, but it is not mandatory.

Optional Parameters Optional parameters are available to add a customer and/or site name to a node/IP address. This information can be then used to assist in identifying data in the EMC Smarts VoIP Performance Manager Displays.

ADD LSP (<lspname>, ip=<ip_address>) [, customer=<customer_name>][, site=<site_name>]) [DEFINE SAT_PROFILE (<pbxname>[, mode=telnet|ssh][, port=<port_number>])]


of 204

Configuration Syntax <lspname> Name given to the LSP device.

<ip_address> IP address of the LSP device.

<pbxname> The name of the PBX to which the LSP is registered.

<customer_name> A customer name to associate with the LSP.

<site_name> A site (location) name to associate with the LSP.

<port_number> The SAT connection port on the LSP.

Configuration

of 204

RTCP_MONITOR Configuration This is an optional configuration that can be used to setup the initial call QoS (Quality of Service) levels for MOS (Mean Opinion Score), Latency, Jitter and Packet Loss. This configuration should only be changed if your QoS criteria are different to the default settings.

The MOS is an overall QoS rating which ranges from 0 to 5, the higher the MOS level the better the QoS. The values specified in the configuration profile represent the worst (lowest) value for the rating category. The default MOS profile is;

DEFINE MOS_PROFILE (#GlobalDefault, Good=4.0, Fair=3.6, Poor=3.0

Latency refers to the delay in packet delivery in milliseconds. Latency is half of the Round Trip Time (RTT). The lower the Latency the better the QoS. The Configuration profile values specify the worst (highest) value for the rating category. The default Latency profile is;

DEFINE LATENCY_PROFILE (#GlobalDefault, Good=50, Fair=100, Poor=150)

Jitter is the variation in time (milliseconds) between packets arriving, caused by network congestion, timing drift or route deviation. A Jitter buffer which temporarily stores arriving packets is often used in order to minimise delay variations and Jitter will only affect the QoS once it becomes greater than the Jitter buffer. The lower the Jitter the better the QoS. The profile values specify the worst (highest) value for the rating category. The default setting for Jitter is;

DEFINE JITTER_PROFILE (#GlobalDefault, Good=20, Fair-=100, Poor=150)


of 204

Packet Loss is the percentage of packets lost in transmission. The lower the Packet loss the better the QoS. The configuration profile values specify the worst (highest) value for the rating category. The default setting is;

DEFINE PACKETLOSS_PROFILE (#GlobalDefault, Good=1.0, Fair=2.0, Poor=3.0)

Configuration

of 204

PASSWORDS Configuration for Avaya Login credentials for all PBXs and LSPs are stored in the PASSWORDS Configuration of the Monitoring Server. An entry must exist for every configured PBX and LSP.

This is done using the following steps.

Step 1 On the EMC Smarts VoIP Performance Manager Client (GUI) go to the Nodes Navigator and right click on the PASSWORDS Configuration file on the Monitoring Server.

Step 2 From the context menu select 'Properties' to open the Configuration Properties dialog box.

Step 3 Passwords Tab To add a new password entry select the icon or press the Insert key on the keyboard (otherwise an existing password entry may be overwritten). This will create a blank line with a drop-down list on the 'Entry Name' field.

Step 4 From the drop-down list in the 'Entry Name' field select: Avaya-SAT:<voip-pm-pbx-name>.


of 204

Step 5 Replace <voip-pm-pbx-name> with the name of the particular PBX or LSP. This must be the same as the details entered into the AVAYA_PBX or AVAYA_LSP Configuration files.

Step 6 In the adjacent fields input the applicable Username (User-Id) and Password. Upon selecting

the Password field a separate dialog box will open where the Password in entered twice in order to ensure accuracy.

Step 7 If multiple PBXs and/or LSPs need to be configured, repeat this procedure for each one.

Step 8 When complete select the Start button which will run the configuration and save the changes.

Configuration

of 204

Create an Avaya Login Account EMC Smarts VoIP Performance Manager needs to log into Avaya Communications Manager in order to obtain the required data. It may be desirable to create a login account specifically for EMC Smarts VoIP Performance Manager with limited permissions. To do this use the following procedures.

Avaya 3.x

Account Setup Procedure

Step 1 Login to the SAT Shell

Step 2 Execute the command: add login <login name>

It is recommended that the <login name> of 'progiptm' be used. The <login name> must be between 2 - 8 characters using 0-9, a-z or A-Z.

Step 3 This will open the Login Administration screen.

Set the Login Type to customer and the Service Level to non-super-user. Complete the password details for the login.

Step 4 When finished press Esc+e to submit the changes and then proceed to set the 'Permissions' (see the following instructions).


of 204

Change Permissions Procedure

Once the login account has been created the permissions need be set through the SAT shell.

Step 1 Login to the SAT shell.

Step 2 Execute the command: change permissions <login name>

Step 3 This will open the Command Permission Categories screen.

On this screen set the Display Admin. and Maint. Data? field to y (yes) and the System Measurements? field to y (Yes)

Step 4 When complete press Esc+e to submit the changes

Configuration

of 204

Avaya 4.x

Account Setup Procedure - Avaya 4.x

Step 1 Login to the Linux Shell

Step 2 To setup a new login account execute the following command:

cmuseradd <type> [-C profile] [P[key]|p[password]] <username>

type: This is the type of login. Valid values are: super-user, nonsuper-user, cm-only, remote and craft2

C: Profile for new login. Logins of type cm-only are required to have a profile. Logins of type remote can never have a profile.

For EMC Smarts VoIP Performance Manager, profile 18 (Customer super-user) is recommended.

P[key]: The login is asg authenticated. If no key is specified on the command line, one will be generated automatically. Not valid with -p

p[pass]: The login is password authenticated and pass is the encrypted password. Not valid with -P. Because this option requires an encrypted password, it is highly recommended that this option be used without a password, then the cmpasswd command be used to set the password

Example

> cmuseradd nonsuper-user -C 18 progiptm

It is recommended that the <username> of 'progiptm' be used.

Step 3 Once the login account has been entered the password needs to be set. To do this run the command;

cmpasswd <username>

The system will then prompt for a password to be entered twice.

NOTE: The cmpasswd entry may object to the strength of the password entered, however the password has been accepted and can be entered again at the re-enter prompt.

For more detailed information please refer to the 'User Profile' topics in the Avaya ACM 4.0 documentation


of 204

Configure Avaya to Send RTCP Data EMC Smarts VoIP Performance Manager monitors the Avaya IP telephony network by collecting Real-Time Control Protocol (RTCP) packets that are sent by Avaya endpoints, such as IP phones, IP Media Processor Boards and Media Gateways. These RTCP packets contain data about the performance of sessions running between the endpoints including QoS measurements such as, network latency, jitter and loss which can be reported for each leg of a call.

In order for EMC Smarts VoIP Performance Manager to receive this RTCP data the Avaya PBX needs to be configured to send the reporting data to the IP address of the EMC Smarts VoIP Performance Manager server.

To do this carry out the following procedure.

Procedure to Setup the PBX Step 1 Telnet into the Avaya PBX

Step 2 Log into the PBX using a login with administrative rights.

Step 3 To configure the PBX default RTCP report destination, execute the command;

change system-parameters ip-options

Step 4 In the RTCP Monitor section input the following values;

Set the Default Server IP Address field to the IP address of the EMC Smarts VoIP Performance Manager server Set the Default Server Port to 5005 Set the Default RTCP Report Period (secs) to 5.

When finished press Esc+e to submit the changes

Configuration

of 204

Procedure to Setup the Network Regions Once the EMC Smarts VoIP Performance Manager IP address has been set up on the Avaya PBX the associated network regions can then be set to either use this IP address as their default setting or an individual IP addresses can be added to each region.

Step 1 To configure the RTCP report destination for a specific network region, execute the command;

change ip-network-region <n> (where 'n' is the IP network region number to be monitored)

a) To use the IP address as set on the PBX set the Use Default Server Parameters? field to y

(Yes)

b) To nominate a specific IP address for this region set the Use Default Server Parameters? field to n (No) and then complete the following fields; Set the Server IP Address field to the IP address of the EMC Smarts VoIP Performance Manager server, Set the Server Port to 5005, Set the RTCP Report Period (secs) to 5 .

Step 2 When finished press Esc+e to submit the changes. The RTCP changes will take effect immediately for all calls, including those already in progress.


of 204

Enabling CDRs on Avaya In order for EMC Smarts VoIP Performance Manager to provide a full range of call metrics, the Avaya PBX needs to be configured so that Call Detail Records (CDRs) are sent to the IP address of the EMC Smarts VoIP Performance Manager Monitoring Server. To enable CDRs use the following procedure on the Avaya PBX.

Procedure to Add Node Names The steps below will configure EMC Smarts VoIP Performance Manager to receive CDRs via the PBX's CDR2 IP service.

Step 1 Log into the Avaya PBX using either SSH or Telnet. Ensure that the login is a user with administrator-level privileges.

Step 2 To add the EMC Smarts VoIP Performance Manager Monitoring Server to the list of system node names, execute the command: change node-names ip

Step 3 Under "Name", add a name which describes the Monitoring Server. Under "IP Address", add the IP address of the Monitoring Server.

Step 4 Save the changes.

NOTE: If the PBX has an S85xx or S87xx series Media Server, then ensure that a valid node name for the CLAN board exists as well. If it has an S8300 series Media Server, then ensure that a valid node name for the PROCR exists as well.

Procedure to Add an IP CDR Service The following steps will create an IP service for the CDRs using the added EMC Smarts VoIP Performance Manager IP address.

Step 5 To add the CDR IP service titled 'CDR2" execute the command: change ip-services Under "Service Type" add "CDR2 " if it does not already exist. Under "Local", add the node name for the CLAN (S85xx or S87xx series) or PROCR (S8300 series). Under "Remote Node", add the node name for the EMC Smarts VoIP Performance Manager server. Under "Remote Port" enter 50000 for AVAYA_PBX, 50001 for AVAYA_LEGACY, or 50002 for AVAYA_DEFINITY.


Configuration

of 204

Procedure to Activate CDRs The following steps are used to set up the system CDR configuration using the created CDR IP service.

Step 7 To edit the System CDR Properties to send CDRs to the configured CDR2 IP Service execute the command: change system-parameters cdr Set "Primary Output Format" to unformatted. Set "Primary Output Endpoint" to CDR


NOTE: There are other formats which could be used. For more information, please refer to the Avaya documentation.

NOTE: If CDRs are required for intra-PBX calls, then the "Intra-switch CDR?" option (second column, third row) must be set to "y".

The Avaya Communication Manager should start sending CDRs to EMC Smarts VoIP Performance Manager.

Intraswitch CDRs CDRs are usually only sent when calls are made through a Trunk. In the case where a call is an 'Intraswitch" call (that is, a call that goes to another phone directly connected to the PBX) then it will not send a CDR for it, unless Intraswitch CDR has been enabled. Intraswitch CDRs are only available if enabled for a particular extension. The command to use on the Avaya PBX to enable Intraswitch CDRs is;

change intraswitch

Then add the required extension numbers.


of 204

Recommended PBX Settings System Parameters The CDR SYSTEM PARAMETERS area (access using 'change system-parameters cdr') of the Avaya SAT program should be set up with the following recommended settings when using EMC Smarts VoIP Performance Manager.

This is the recommended PBX setting, although setting 'n' to all options is also possible. By using these recommended settings CDRs will be sent for most types of calls (conference calls, transfers, attendant) and intra-switch. Unless there is a requirement for any other particular option, the default should be 'n'.

Trunk Groups In the Trunk Group area (access using 'change trunk-group <n>') there is a setting for CDR reports to be generated for that trunk group. This should be set to 'y'.

Configuration

of 204

Starting Alerts and Databases EMC Smarts VoIP Performance Manager includes a number of Database documents that are used in monitoring Avaya call data plus Threshold Alerts that monitor the health of PBXs. These documents are not started by default and can be activated from the Avaya Monitoring Node Display which is accessible from the Avaya PBX Display by selecting the Configuration link.

The Avaya PBX/LSP Alerts can be started from the Start link on the Avaya Monitoring Node Display.

The Databases are started from the Avaya Databases Display. This Display can be accessed by clicking on the Configure link in the Avaya Databases window of the Avaya Monitoring Node Display.

Clicking on the Configure Link will open the Avaya Databases Display. From here indicators will show whether each Database is running or stopped. If any are stopped a Start Link will also be shown..


of 204

The following documents can be started from this Display;

Voice Streams Historical Database This database records details of each Voice Stream upon completion over the past 48 hours..

Voice Streams Replay Database This database records live data from all Voice Streams for 48 hours, enabling them to be replayed.

Network Hops Historical Database This database records historical information on Network Hops for the past 48 hours.

Start Log Database Records status changes for devices in the Avaya environment using the PROBSUM record.

Utilization Reporting Database This database records availability and performance data for short and long term utilization and SLA reports.

Troubleshooting Database Records performance statistics to troubleshoot the monitoring of the Avaya environment.

To start any of these Thresholds and Databases click on the Start link that is located to the right of the required document.

Configuration

of 204

SAT Performance Profiles System Access Terminal (SAT) performance profiles have been included with EMC Smarts VoIP Performance Manager in order to control the frequency and number of scheduled SAT commands being run between the EMC Smarts VoIP Performance Manager Monitoring Server and the Avaya PBX. This facility helps to scale back the demand placed on the PBX by reducing the number of commands being run and thereby spreading the command load over an extended period. This is particularly useful in the case of earlier Avaya Communication Manager version 1 and 2 devices and DEFINITY hardware which may have limited resources to support the standard level of command polling.

SAT commands are divided into two types; STATUS commands, which are dynamic and continually pull in constantly changing data; and CONFIGURATION commands, that are associated with static configuration data which changes infrequently. Each of these two command types have three SAT profile levels that define the frequency that EMC Smarts VoIP Performance Manager commands are run. The following table shows the three levels and how often the EMC Smarts VoIP Performance Manager will run the commands.

HIGH MEDIUM LOW

Status 1 minute 2 minutes 5 minutes

Configuration 1 hour 6 hours 24 hours

Default settings are provided based upon the Avaya equipment versions being used. The equipment version determines which EMC Smarts VoIP Performance Manager configuration file is used (as shown in the chart below) and are automatically established by the EMC Smarts VoIP Performance Manager configuration file that has been setup. These default settings are as follows;

Configuration File Avaya Version

Status Configuration

AVAYA_PBX 3.x , 4.x HIGH HIGH

AVAYA_LSP All LOW LOW

AVAYA_LEGACY 1.x and 2.x MEDIUM MEDIUM

AVAYA_DEFINITY DEFINITY LOW LOW

The Avaya SAT Performance Profile Display provides a link that will run a command to obtain and show the current SAT profile settings for the PBX. This Display can be accessed by selecting the Configuration Link on the Avaya PBX Display, then selecting the SAT Link from the Avaya Monitoring Node Display and then selecting the SAT Performance Profiles Link on the Avaya SAT PBX Status Display.


of 204

Modifying the Profile Levels

IMPORTANT NOTE: The default settings are normally sufficient for the device types specified by the particular configuration file. It should not normally be necessary to change the defaults and any changes should only be done in consultation with EMC Technical Support.

If required, changes can be made to the SAT Performance Profile configurations by using the Avaya SAT Performance Profile Display. This Display can be accessed by selecting the Configuration Link on the Avaya PBX Display, then selecting the SAT Link from the Avaya Monitoring Node Display and then selecting the SAT Performance Profiles Link on the Avaya SAT PBX Status Display.

The profile can be changed for either Status or Configuration separately, for example a Status profile can be left at a HIGH setting while the Configuration profile can be changed to MEDIUM

NOTE: Changing the SAT profile will stop and restart the Collectors.

Configuration

of 204

Cisco Unified CallManager 3.3 & 4 After installing the EMC Smarts VoIP Performance Manager for Cisco v4 on to the Cisco CallManager 3.3 & Cisco Unified CallManager 4 devices, as described in the Deployment section, you will now need to carry out some configuration procedures. These steps set up the system components to communicate with each other. This section provides step by step instructions on how to carry out these configurations.

Configuration Steps

These steps assume that the Cisco CallManager 3.3 or Cisco Unified CallManager 4 environment has already been set up with EMC Smarts VoIP Performance Manager for Cisco v4. If this is not the case please complete this setup first by referring to the separate EMC Smarts VoIP Performance Manager for Cisco v4 Installation Guide.

NOTE: The following configuration procedures need to be carried out from a Client (GUI) connected to the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Managing Server.

Step 1 NETWORK Configuration - Managing Server Update the NETWORK Configuration on the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Managing Server by adding a MANAGED-NODES statement for each Publisher node to be monitored.

Step 2 Check the Node Navigator for the Publisher From Node Navigator of the Client (GUI) expand the Entire Network node group tree and confirm that all Publishers added to the NETWORK Configuration at Step 1 are visible. Allow a few minutes for the node information to propagate through to the Managing Server following the NETWORK Configuration update.

Step 3 NETWORK Configuration - Publisher In the Node Navigator of the Client (GUI), expand the Configurations tree for the Publisher.

a) Update the NETWORK Configuration to add a MANAGED-NODE statement for each Subscriber and ancillary node in the cluster.

b) Add a ROUTE-TO statement with the Managing Server name (do not use IP address here).

When finished select the Start button to run the new configuration.

Step 4 If you have multiple Publishers repeat Step 3 on each Publisher.

Step 5 Check the Node Navigator for all Nodes From Node Navigator of the Client (GUI) expand the Entire Network node group tree and confirm that all Publishers and their associated nodes are now visible. A few minutes should be allowed for node information to propagate through to the Monitoring Server.

Step 6 PASSWORDS Configuration If required, the PASSWORDS Configuration may need to be set up for components such as Exchange and SQL servers.


of 204

Step 7 NODEGROUP Configuration - Managing Server Now update the NODEGROUP Configuration on the Managing Server. A link on the Configurations for Monitoring CUCM4 Clusters Display in the Client (GUI) provides an easy method to do this.

Step 8 Check the Node Navigator for Cluster Node Groups From Node Navigator of the Managing Server confirm that the new Node Groups for the various clusters are now visible. Allow a few minutes for the information to propagate through to the Managing Server following the NODEGROUP Configuration update.

Step 9 Managing Server - EMC Smarts VoIP Performance Manager Memory Limit The SET MEM-SIZE statement in the PROGNOSIS Configuration is automatically set for an IP telephony network of 5,000 devices or less. If the network has more than 5,000 devices the SET MEM-SIZE statement will need to be adjusted. Please contact EMC Technical Support for specific details.

Further details and instructions about these configurations can be found in the following topics.

Configuration

of 204

NETWORK Configuration - Managing Server From the Client (GUI) connected to the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Managing Server update the NETWORK configuration on the Managing Server to add a MANAGED-NODES statement for each Publisher to be monitored.

To do this carry out the following procedure:

Procedure Step 1 From the Client (GUI) go to the Node Navigator and expand the Configurations tree of the

Managing Server.

Step 2 Right click on the NETWORK Configuration file and select Properties from the context menu.

This will open the NETWORK Configuration Properties dialog.


of 204

Step 3 Modify the NETWORK Configuration by adding one or more MANAGED-NODES statements to define one or more Publisher nodes.

This done by adding statement lines such as:

MANAGED-NODES (10.1.1.6) !PUB2 MANAGED-NODES (10.2.2.6) !PUB1 MANAGED-NODES (10.3.3.6) !PUB3

Step 4 Select the Start button to run the new configuration

After the NETWORK Configuration has been successfully restarted go to the Node Navigator of the Managing Server and expand the Entire Network node group tree. From here you can confirm that all Publishers that were added to the NETWORK Configuration are visible. You should allow a few minutes for the node information to propagate to the Managing Server.

Configuration

of 204

NETWORK Configuration - Publisher From the Client (GUI) connected to the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Managing Server update the NETWORK configuration of each Publisher by adding the following;

1) A MANAGED-NODES statement for each subscriber and ancillary node that forms part of the cluster.

2) A ROUTE-TO statement containing the Managing Server name (do not use the IP address).

To do this carry out the following procedure:

Procedure Step 1 From the Entire Network section of the Node Navigator, locate the Publisher Node and expand

the Configurations tree.

Step 2 Right click on the NETWORK Configuration file and select Properties from the context menu.

This will open the NETWORK Configuration Properties dialog.


of 204

Step 3 MANAGED-NODES Statement

NOTE: The “Out of the box” installation will automatically populate the MANAGED-NODES statement on the Publisher with a list of all subscribers that are part of the Publisher-Cluster. You will only need to add extra statements for ancillary nodes such as Unity and Exchange servers which are considered as part of this particular CallManager cluster.

Modify the NETWORK Configuration by updating the MANAGED-NODES statement to define all ancillary nodes that have the EMC Smarts VoIP Performance Manager for Cisco v4 Agent installed and are a logical part of the CallManager cluster (Unity, mail servers, etc.). Also check that the details of all Subscribers that have been automatically added are correct.

Add the ancillary devices by including a MANAGED-NODES statement for each device, as shown in the example below. Make sure that these statements are added outside of the "Auto_Config_Section".

MANAGED-NODES (10.2.2.4) !Unity MANAGED-NODES (10.2.2.5) !Exchange

These devices will now become visible to the Publisher node and can be viewed in the Node Navigator under the Entire Network folder.

Configuration

of 204

Step 4 ROUTE-To Statement Complete a NETWORK Configuration on each Publisher by updating the “ROUTE-TO” statement with the EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Managing Server name (do not use an IP address here). This will let the Client (GUI) connected to the Managing Server see all nodes that the Publisher node can see.

Such as:

ROUTE-TO (NODE-A) !Managing Server

The Publisher in each cluster is required to send virtual connection information and actual collection data to the Managing Server on behalf of the managed nodes. Only the Publishers will have physical connections to the Managing Server.

Step 5 Select the Start button to run the new configuration.

After the NETWORK Configuration has been successfully restarted go to the Node Navigator of the Publisher and expand the Entire Network node group tree. From here you can confirm that all devices that were added to the NETWORK Configuration are visible. You should allow a few minutes for the node information to propagate to the Publisher.


of 204

PASSWORDS Configuration for CUCM4 The installation process will automatically populate the PASSWORDS Configuration with the necessary credentials for Exchange and SQL servers. However, sometimes it may be necessary to adjust the PASSWORD Configuration on each of these servers, such as if a password changes, so that mailbox and database information continues to be obtained.

Procedure Step 1 From the Entire Network section of the Nodes Navigator, expand the Configurations tree of the

required Exchange or SQL server node, i.e. the node on which the PASSWORDS Configuration is to be updated.

Step 2 Right click on the PASSWORDS Configuration file and select Properties from the context

menu. This will open the PASSWORDS Configuration Properties dialog box.

Step 3 Add the required password details to the configuration by selecting the required device from the 'Entry Name' field, then complete the username and password details.

Configuration

of 204

The following chart describes the PASSWORD Configuration entries.

Entry Name Username Password

COMMAND:PROGNOSIS This is a system default setting that should not be changed.

Exchange Username details are initially taken from values input into the Exchange Administrator dialog of the EMC Smarts VoIP Performance Manager installation.

Password details are initially taken from values input into the Exchange Administrator dialog of the EMC Smarts VoIP Performance Manager installation.

snmp V2c:<cluster_name>

Note: Extra Community SNMP Strings may be added to the PASSWORDS Configuration in the form of:

snmpv2c:<cluster>:<node>

This is to enable the use of different community strongs per node or H.323 Gateway.

Not applicable.

IMPORTANT NOTE: The SNMP Community String must be set the same for all Publishers and Subscribers in the cluster.

The default Community String of 'public' is automatically added to this entry. This should be changed to your own SNMP Community String.

Note that EMC Smarts VoIP Performance Manager for Cisco v4 only supports SNMP version 2c.

Step 4 When finished save the configuration file using the Save As... button then start the Configuration using the Start button.


of 204

NODEGROUP Configuration - Managing Server Update the NODEGROUP configuration of the Managing Server to create Node Groups for the clusters that have been set up.

Procedure Step 1 Open the Welcome to EMC Smarts VoIP Performance Manager Display then select the Cisco

UCM 3.3 & 4 Manage Link in the Configure panel.

This will open the Configuring EMC Smarts to Monitor a CUCM 4 Cluster Display which provides a Link to automatically update the NODEGROUP Configuration at Step 3.

Configuration

of 204

Step 2 Click the Build Cluster Link to run the “Refresh Nodegroup Configuration on this Managing Node” command. This will refresh the NODEGROUP Configuration on the current node to include the CUCM 4 cluster node groups and any lower level node groupings.

After the NODEGROUP Configuration has been successfully updated and restarted go to the Node Navigator of the Managing Server and confirm that new Node Groups for the various clusters are now visible. You should allow a few minutes for the node information to propagate to the Managing Server.

Step 3 Click the Start Monitoring Link to start collections of the CUCM 4 cluster data that will populate the multi-vendor Monitor Entire Network Displays.

Multi Level Managing Server Hierarchy If there is one or more higher level Managing Servers in the hierarchy of the IP telephony environment, i.e. other Managing Servers above the current server, then the following steps need to be completed on each higher level server.

Step 4 Log on to each higher level Managing Server then open the Configuring EMC Smarts to Monitor a CUCM 4 Cluster Display.

Step 5 Click on the Re-Discover Clusters Link, this will enable the Managing Server to see any lower level Managing Servers and receive CallManager data from them.

Change CUCM 4 Cluster Name Any available clusters will be shown in this windows as a Link which will open the Change Node Name Prompt Form. This Prompt Form is used to change an existing Cluster name. The name format can include a customer name and a site name if required. Keep in mind that each Cluster name must be unique to this EMC Smarts VoIP Performance Manager installation. Also note that changing a Cluster node name will not be applied retrospectively to any report data prior to the change. Please refer to Changing Cluster Names for details.


of 204

Changing Cluster Names The default cluster name convention used by EMC Smarts VoIP Performance Manager is <Publisher Name>-Cluster, for example:

SOUTH-Cluster

However, in large environments this may give rise to duplicate cluster names which will cause data conflicts.

An option is made available during the installation of EMC Smarts VoIP Performance Manager for Cisco v4 on to the Publisher to create a unique alternative cluster name. However, should a change in cluster name be required after installation then the Change CUCM 4 Cluster Name option on the Configuring EMC Smarts to Monitor a CUCM4 Cluster Display can be used.

WARNING: Changing a CUCM 4 Cluster name will result in subsequent data for the cluster being based on the new cluster name. Old data already collected for this cluster will continue to exist but can only be referenced under the old cluster name.

The Change CUCM 4 Cluster Name window will show a list of each monitored cluster. Clicking on the cluster name that is to be changed will display the following warning message:

Configuration

of 204

Continuing by selecting the Yes button will open the Change Cluster Name prompt form which is used to create an alternative cluster name by adding the required name details.

The name format can include a cluster name, customer name and a site name if required. Keep in mind that each Cluster name must be unique to this EMC Smarts VoIP Performance Manager installation. Also note that changing a Cluster name will not be applied retrospectively to any report data prior to the change.

The alternative cluster name will be in the following format:

<Cluster Name>-<Customer Name>-<Site Name>

Example:

ClusterA-Acme-London


of 204

Cisco Unified Communications Manager After installing the EMC Smarts VoIP Performance Manager components, as described in the Installation Section, a number of configuration procedures will need to be completed in order for the EMC Smarts VoIP Performance Manager Monitoring Server (or Managing Server where applicable) to see the Cisco Unified Communications Manager devices. These procedures set up the system components to communicate with each other. This section provides step by step instructions on how to carry out these configurations.

Configuration Steps

Step 1 Add Clusters and Nodes The EMC Smarts VoIP Performance Manager Monitoring/Managing Server requires IP connectivity to each Cisco Unified Communications Manager Appliance.

Step 2 Update the PASSWORDS Configuration On the EMC Smarts VoIP Performance Manager Monitoring/Managing Server the Cisco Username and Password details need to be updated in the PASSWORD Configuration in order to allow access for cluster monitoring.

Step 3 Set up Cisco Administration Console A number of parameters within the Cisco Unified Communications Manager Console will need to be set up so that EMC Smarts VoIP Performance Manager can obtain the data required for system management and monitoring. These parameters include;

CallManager Service Activation Setting the SNMP Community String Setting the CDR Cluster Name Enabling CDRs for Voice Quality Data Enabling Valid Namespaces CDR Disk Space.

Further details and instructions about these configurations can be found in the following topics.

Configuration

of 204

Add Clusters and Nodes The EMC Smarts VoIP Performance Manager Monitoring Server (or Managing Server where applicable) requires IP connectivity to each Cisco Unified Communications Manager Appliance. To make this configuration process as simple as possible a configuration script is provided with the EMC Smarts VoIP Performance Manager installation. This script will automatically create/update the EMC Smarts VoIP Performance Manager NODEGROUP and WWW Configurations plus the required Analysts, Thresholds and Databases. The script can be run through a Link on the Configurations for Monitoring Cisco CallManager 5 Clusters Display.

Procedure Step 1 From the Welcome to EMC Smarts VoIP Performance Manager Display click on the Manage

Link in the Configure panel for Cisco UCM 5 & 6.

Step 2 This will open the Configurations for Monitoring CUCM 5 & 6 Clusters Display that includes

a range of Links for each of the configuration functions.


of 204

Step 3 Selecting the required link on the right hand side will run the configuration script and you will be prompted to input the required details, these will normally include the cluster name and its IP address.

The options available on this Display include:

Add Cluster Online This will add a specified cluster name and all the nodes within that cluster to the EMC Smarts VoIP Performance Manager configurations by automatically searching the Publisher's database. After selecting this Link the following Prompt form will be displayed which will need to be completed;

In the Cluster name field you may enter ‘-‘ for the system to automatically create a Cluster name of <Publisher Name>-Cluster. Alternatively, you can input your own cluster name format, for example <Customer Name>-<Site Name>-<Cluster Name>.

The 'Enter a Customer name for the PBX' and 'Enter a Site name for the PBX' fields are optional and are used for grouping purposes only, they do not effect the cluster name. If these are not required input N/A. If these fields are completed the details will be visible in the Monitor Entire Network and Browse Entire Network Displays and will group like customer and site named clusters together.

Configuration

of 204

NOTE: When adding clusters online, Cisco devices that are peers of the CallManager may appear as subscribers in the CCM Administration page, for example Cisco Presence Servers. When these are present they will be auto-discovered as subscribers in the cluster. To work around this the VoIP Performance Manager Cluster Configuration should be manually edited to remove the ADD APPLIANCE statement that points to the device that was incorrectly added as a subscriber.

Add Cluster Offline This will add a specific cluster name only. All nodes that are part of this cluster will have to be added separately using ‘Add Node Offline’ Link or when the Cluster comes online you can use the Update Cluster Online Link and the system will automatically obtain the node names.

Add Node Offline This will add a specified node into a cluster. Only one node can be added at a time.

Update Cluster Online This will automatically update the nodes for a specified cluster. If nodes have been added manually to the CallManager SQL database but they are currently offline, the system will ask for the IP addresses to be added.

Remove Cluster This will remove a specified cluster and all its nodes from the EMC Smarts VoIP Performance Manager configurations. Associated Thresholds and Analysts will also be removed, however, the database for this cluster will be retained

Remove Node This will delete a specific node from the EMC Smarts VoIP Performance Manager configurations for the specified cluster.

Reject Pending Changes This will remove all pending changes, anything that has already been submitted will have to be removed using ‘Remove Cluster’ or ‘Remove Node’ functions.

Step 4 After an initial configuration entry has been made, a Submit Pending Changes link will be shown at the top of the Display.


of 204

Each configuration entry will be batched and then when all entries have been completed the Submit Pending Changes Link at the top of the screen must be selected to apply all changes to EMC Smarts VoIP Performance Manager. This batch process requires only a single restart of EMC Smarts VoIP Performance Manager to enable all processed changes.

NOTE: If you receive the error message, "Cannot Connect to a Cluster Database using IP address : ....." please refer to the Enabling Valid Namespaces section of this Guide for the appropriate action to take.

Step 5 Once these pending changes have been processed successfully a message will be shown in the top right corner of the Display.

Configuration

of 204

PASSWORDS Configuration On the Monitoring Server (or Managing Server, where applicable) the Cisco Username and Password details need to be updated in the PASSWORD Configuration to allow access for cluster monitoring. This is done by using the following procedure.

Procedure Step 1 From the Node Navigator, expand the Configurations tree of the Monitoring or Manager

Server.

Step 2 Right click on the PASSWORDS Configuration file and select Properties from the context

menu. This will open the PASSWORDS Configuration properties dialog box.

Default password details are added to the PASSWORDS Configuration dialog box automatically by the configuration script.


of 204

Step 3 A number of the entries will be created with default system names and passwords. Some of these, as indicated below, may need to be changed to suit your own system requirements.


COMMAND:PROGNOSIS This is a system default setting that should not be changed.

cdrsql This entry is used to access the database created to store Call Details Records (CDRs) on the SQL server selected at install time. The username of 'user' is the default for this entry and should not be changed.

The password of 'password' is the default for this entry and should not be changed.

sftp This entry is used to access the SFTP server on the monitoring node which is used to collect CDRs. The username pf 'PrognosisCDR' is the default for this entry and should not be changed.

The password of 'Prognosis_CDR' is the default for this entry and should not be changed.

cmsql:<cluster_name> Username details are taken from values input into the dialog box after selecting the Add Cluster Online/Offline links on the CallManager 5 Configuration Display.

Password details are taken from values input into the dialog box after selecting the Add Cluster Online/Offline links on the CallManager 5 Configuration Display.

cdrondemand:<cluster_name> Username details are taken from values input into the dialog box after selecting the Add Cluster Online/Offline links on the CallManager 5 Configuration Display.


Configuration

of 204


cmperf:<clusrer_name> Username details are taken from values input into the dialog box after selecting the Add Cluster Online/Offline links on the CallManager 5 Configuration Display.


snmpv2c:<cluster_name> Note: Extra SNMP Community strings may be added to the PASSWORDS Configuration in the form of: snmpv2c:<cluster>:<node> This is to enable the use of different community strings per node or H.323 Gateway.

No applicable.

IMPORTANT NOTE: The SNMP Community String must be set the same for all Publishers and Subscribers in the cluster.

The default Community String of 'public' is automatically added to this entry. This should be changed to your own SNMP Community String. See Setting the SNMP Community String for details. Note that EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya only supports SNMP version 1 and 2c.

Step 4 When finished save the configuration file using the Save As... button then start the Configuration using the Start button.


of 204

Cisco Administration Console Setup A number of parameters within the Cisco Unified Communications Manager Console will need to be set up so that EMC Smarts VoIP Performance Manager can obtain the data required for system management and monitoring.

CallManager Service Activation

Setting the SNMP Community String

Setting the CDR Cluster Name

Enabling CDRs for Voice Quality Data

Enabling Valid Namespaces

CDR Disk Space

To access the Cisco Unified CM Administration module proceed as follows:

Procedure Step 1 Using your preferred Web Browser, enter https://<server name or IP address>:8443. Where

server name or IP address equals the server where the Cisco Unified Communications Manager service is running and 8443 equals the port number for HTTPS.

Step 2 Click the Cisco Unified Communications Manager Administration link.

Step 3 The system will prompt for your Cisco Administrator username and password. After this has been entered the Cisco Unified CM Administration window will open.

Configuration

of 204

CallManager Service Activation To enable EMC Smarts VoIP Performance Manager to monitor the CallManager network three services need to be activated in the Cisco Unified Serviceability screen. These are:

• Cisco SOAP CDR on Demand service (Activate only on ‘First’ node).

• Cisco AXL Web service (Activate on all servers in the cluster).

• Cisco CallManager SNMP service (Activate on all servers in the cluster).

Procedure Step 1 From the Navigation box in the upper right corner of the Administration window select the

‘Cisco Unified Serviceability’ option then click the Go button.

The Cisco Unified Serviceability window will open.

Step 2 From the Menu bar select: Tools > Service Activation

The Cisco Unified Serviceability ‘Service Activation’ window will open.


of 204

Step 3 From the Select Server drop down list, click on the server to be configured.

Step 4 The Service data for the requested server will be displayed. Scroll down to the following sections:

CDR Services - check that Cisco SOAP - CDRonDemand Service is ‘Activated’.

Database and Admin Services - check that Cisco AXL Web Service is ‘Activated’.

Performance and Monitoring Services - check that Cisco CallManager SNMP Service is ‘Activated’.

Step 5 If any of these services are deactivated, tick the adjoining check box then scroll to the bottom

of the page and select the Save button.

NOTE: Have the Network Administrator check that the network is set up for SNMP traffic between CallManager and the EMC Smarts VoIP Performance Manager Server (Monitoring Node). If it is not, it will need to be implemented in order to receive data.

Configuration

of 204

Setting the SNMP Community String The SNMP agent provides security by using community strings. In order to access any management information base (MIB) in a CallManager system it is necessary to configure the community string in the Cisco Unified CallManager Administration module.

Procedure Step 1 From the Cisco Unified CallManager Serviceability window select:

Snmp > V1/V2c > Community String

NOTE: EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya does not currently support SNMP v3.

Step 2 From the Server drop-down list box, choose the server for which you want to configure a community string and select the Find button.

The Search Results panel at the bottom of the page will show any community string Names that have already been set up on the selected server.

NOTE: If an existing community string is to be used, it will be necessary to ensure that the same name exists on all nodes in the cluster. If it does not, it will need to be added to each node.


of 204

Step 3 To add a new community string, click the Add New button to open the SNMP Community String Configuration window.

Step 4 In the Community String Name field, enter a name for the community string. The name can

contain up to 32 characters and can contain any combination of alphanumeric characters, hyphens (-), and underscore characters (_).

NOTE: The community string name must match the SNMP Entry Name in the EMC Smarts VoIP Performance Manager PASSWORD Configuration. See PASSWORDS Configuration for CMA Monitoring for details.

It is recommended that all other settings be left as the default.

Step 5 From the Access Privileges drop-down list box, choose the appropriate access level from the following list. EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya requires at least Read access to the MIBS.

ReadOnly Community string can only read the values of MIB objects.

ReadWrite Community string can read and write the values of MIB objects.

ReadWriteNotify Community string can read and write the values of MIB objects and send MIB object values for a trap and inform messages.

Configuration

of 204

Access Privileges must not be set to either of the following for EMC Smarts VoIP Performance Manager;

NotifyOnly Community string can only send MIB object values for a trap and inform messages.

None Community string cannot read, write, or send trap information.

Step 6 The same community string must be applied to all nodes in the cluster, to do this tick the Apply To All Nodes check box.

IMPORTANT NOTE: The SNMP community string must be set the same for all Publishers and Subscribers in the cluster.

Step 7 Click Insert to save a new community string.

Step 8 A message indicates that changes will not take effect until you restart the SNMP master agent. To restart the SNMP master agent service, click OK.


of 204

Setting the CDR Cluster Name Once you have added a cluster name to the EMC Smarts VoIP Performance Manager Managing Server configuration (see Add Clusters and Nodes) you will need to add this same cluster name to the Cisco Enterprise Parameters Configuration. This is also done through the Cisco Unified CM Administration module.

Procedure Step 1 From the menu bar of the Cisco Unified CM Administration window choose:

System > Enterprise Parameters

The ‘Enterprise Parameters Configuration’ window will open.

Configuration

of 204

Step 2 Scroll down to the CDR Parameters box.

Step 3 In the Cluster ID field insert the name that you have given to this Cisco Cluster. This should be

the same Cluster name as used previously when adding Cluster names to the EMC Smarts VoIP Performance Manager Managing Server (see Add Clusters and Nodes).

NOTE: If it is not desirable to modify this setting then an alternative is to manually modify the following value in the Cluster INI file (ir<cluster>.ini) to the value that is set in the Cluster Id field of the Cisco Enterprise parameters. [PACE] CiscoClusterId=<cluster_id> However, it is important that the value of the Cluster Ids remain unique to the EMC Smarts VoIP Performance Manager Managing Server.

Step 4 When finished scroll down to the bottom of the page and select the Save button.


of 204

Enabling CDRs In order for EMC Smarts VoIP Performance Manager to provide a full range of call metrics, Call Detail Records (CDRs) need to be enabled on each Cisco Unified Communications Manager node. By default, CDRs are initially disabled. To enable CDRs use the following procedure for each node in the cluster.

NOTE: You may wish to leave CDRs disabled in order to minimize the impact on call processing. However, in the disabled state EMC Smarts VoIP Performance Manager will be unable to provide voice quality metrics.

Procedure Step 1 From the menu bar on the Cisco Unified CM Administration window choose:

System > Service Parameters

Step 2 The ‘Service Parameter Configuration’ window will open.

From the Select Server and Service field choose an active Cisco node from the Server drop down list box.

Configuration

of 204

Step 3 In the subsequent Service field ensure that ‘Cisco CallManager (Active)’ has been selected.

Step 4 Scroll down to the CDR Enabled Flag field and from the drop down list box change the

setting to TRUE to enable CDRs.

Step 5 Next scroll down further to the Call Diagnostics Enabled field and ensure that this is set to

‘Enable Only When CDR Enabled Flag is True”. This is a Clusterwide setting and so only needs to be set on one node in the cluster.



of 204

Enabling Valid Namespaces EMC Smarts VoIP Performance Manager requires valid AXL/SOAP namespace information in order for SOAP data to be obtained and to ensure that online cluster scripts auto-discover nodes. In Cisco Unified Communications Manager 5.0(x) this requires the facility to be activated manually, in Cisco Unified Communications Manager 5.1(x) a flag was introduced in the Administration Console for this function, however, due to a bug on some Cisco versions this Console setting needs to be adjusted. Please carry out the following procedures as applicable.

Cisco Unified Communications Manager 5.0(x) In order to enable valid AXL/SOAP namespace responses on Cisco Unified Communications Manager 5.0(x) systems, add the following entry to the SQL section of the cluster .ini file, e.g. 'ir<cluster-name>.ini', which is located in the /Server/Configuration folder of the EMC Smarts VoIP Performance Manager installation directory.

SendValidNamespace=0

In addition a new file titled, 'irsqltool.ini' will need to be created in the same folder in order for the online cluster scripts to work. This file needs to only contain the following text and can be created using any text editor.

[SQL] SendValidNamespace=0

This solution can also be used on Cisco Unified Communications Manager 5.1(x) systems instead of the following procedure to update the Administration Console, if preferred.

Cisco Unified Communications Manager 5.1(x) There is a bug in certain Cisco Unified Communications Manager 5.1(x) systems that causes incorrect namespace data to be returned in AXL/SOAP responses. Please refer to Cisco defect: #CSCse41911 for full details and a list of which releases this is applicable to.

In order for EMC Smarts VoIP Performance Manager to correctly parse AXL/SOAP responses, the Send Valid Namespace in AXL Response parameter in the Service Parameter Configuration window needs to be set to 'TRUE' on all Cisco Unified Communications Manager nodes that are being monitored.

NOTE: The default setting for Cisco Unified Communications Manager version 6 is 'TRUE', please ensure that this has not been changed.

Please use the following procedure to carry out this task.

Configuration

of 204

Procedure

Step 1 From the menu bar on the Cisco Unified CM Administration window choose:

System > Service Parameters

Step 2 The ‘Service Parameter Configuration’ window will open.

From the Select Server and Service field choose an active CallManager node from the Server drop down list box.

Step 3 In the Service field ensure that ‘Cisco Database Layer Monitor’ has been selected.


of 204

Step 4 Select the Advanced button at the bottom of the screen.

Step 5 On the next screen set the Send Valid Namespace in AXL Response parameter to TRUE.


Configuration

of 204

CDR Disk Space Should you find a problem where Call Detail Records (CDRs) are not being downloaded to the EMC Smarts VoIP Performance Manager database, it may be due to insufficient disk space on the Cisco node to preserve all records in the specified timeframe.

Although this is not a normal situation it can be rectified by reducing the ‘Preservation Time’ or increasing the ‘Disk Allocation’ under the CDR Management module. To do this proceed as follows:

Procedure Step 1 From the Cisco Unified Serviceability window select the Tools menu then choose CDR

Management.

This will open the CDR Management window.


of 204

Step 2 In the General Parameters box click on any one of the parameters to open the Update screen.

Step 3 Increase the Disk Allocation and/or change the CDR/CMR Files Preservation Duration to the

required period, the default is 30 days and it is suggested that this be changed to 2 days.

Step 4 When finished click the Update button.

Step 5 A prompt may be displayed warning that there may be CDR/CMR files outside of the new preservation duration and that these files will be deleted.

Select the OK button to continue.

Configuration

of 204

Advanced Configuration The following sections detail a number of configuration settings that may be required on certain Cisco Unified Communications Manager environments.

• Cluster Static Configuration

• NAT Static Configuration

• Secure FTP Address for CDR Retrieval


of 204

Cluster Static Configuration The Cisco Unified Communications Manager Configuration set up, (see Add Clusters and Nodes) will automatically create one static configuration for each cluster similar to the following example.

Certain parameters within these static configurations can be modified manually to suit specific needs. These parameters are described here.

IMPORTANT NOTE: This configuration file should only be modified with instructions from EMC personnel as incorrect settings on this file can disable your Cisco Unified Communications Manager monitoring.

SUBSYS HOWCUST_HOWSITE_HOWELL !----------------------------------------------------------------------------- ! HOWCUST-HOWSITE-HOWELL Cluster Configuration !----------------------------------------------------------------------------- ! To configure monitoring nodes use: ! DEFINE CLUSTER_PROFILE(<profile type>, <name>=<value>[, <name>=<value>] ) ! ! To configure monitoring a specific node use: ! DEFINE APPLIANCE_PROFILE(<profile type>, node=<\node-name>, <name>=<value>[, <name>=<value>] ) ! ccmweb profile DEFINE CLUSTER_PROFILE(ccmweb, port=8443, protocol=https) ! DEFINE CLUSTER_PROFILE(ccmweb, port=8443, protocol=https) ! cmsql profile DEFINE CLUSTER_PROFILE (cmsql, Timeout=3600) !DEFINE CLUSTER_PROFILE (cmsql, Url=axl:https://<ip>:8443/axl) !DEFINE CLUSTER_PROFILE (cmsql, ProxyAddr=<ip>, ProxyPort=<port>, Timeout=120) !DEFINE CLUSTER_PROFILE (cmsql, BackOffTime=4, BackOffMultiplier=2.0, BackOffRetries=5) !DEFINE CLUSTER_PROFILE (cmsql, RunTimes=04:00|22:59) ! cmperf profile !DEFINE CLUSTER_PROFILE (cmperf, Url=https://<ip>:8443/perfmonservice/services/PerfmonPort) !DEFINE CLUSTER_PROFILE (cmperf, ProxyAddr=<ip>, ProxyPort=<port>) !DEFINE CLUSTER_PROFILE (cmperf, Timeout=120, InstanceInterval=120,TeardownInterval=3600) !DEFINE CLUSTER_PROFILE (cmperf, BackOffTime=4, BackOffMultiplier=2.0, BackOffRetries=5) ! snmp profile ! DEFINE CLUSTER_PROFILE (snmp, Port=161, Version=2c) ! DEFINE CLUSTER_PROFILE (snmp, Timeout=10, Retries=5)

Configuration

of 204

!cdrutility profile DEFINE CLUSTER_PROFILE(cdrutility, Dir=D:\Program Files\EMC Smarts VoIP Performance Manager\3rdparty\copssh\home\PrognosisCDR) !DEFINE CLUSTER_PROFILE (cdrutility, SoapUrl=http://<ip>:8080/CDRonDemandService/services/CDRonDemand) !DEFINE CLUSTER_PROFILE (cdrutility, CDRDownload=1, Url=odbc:IPTMCDRDSN) !DEFINE CLUSTER_PROFILE (cdrutility, BudgetedBandwidth=100) !DEFINE CLUSTER_PROFILE (cdrutility, CDRListRefreshOnRestart=0) !DEFINE CLUSTER_PROFILE (cdrutility, DbCullHour=20, DbDaysHighwater=3, DbDaysLowwater=2, DbSizeHighwater=50000000, DbSizeLowwater=10000000) !cdrutility profile DEFINE CLUSTER_PROFILE(mosthreshold, Thresh=3.6, Poor=3.0, Fair=3.6, Good=4.0) !------------------------------------------------------------------------------ ! DO NOT EDIT ANY SETTINGS BELOW THIS LINE! !------------------------------------------------------------------------------ ! ! ODBC DSN used to access local CDR Database DEFINE CLUSTER_PROFILE(cdrsql, Url=odbc:IPTMCDRDSN) ! This section below is created by the cma-config script. It should not be ! directly edited by a user. Each "ADD APPLIANCE" statement configures ! a CallManager 5.0 Node to be monitored by VoIP Performance Manager for Cisco v5+ and Avaya. ADD APPLIANCE (\HOWELL:HOWELL, ip=10.1.1.60, version=5.0, localhost=HOWELL, customer=HOWCUST, site=HOWSITE)

EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya accesses monitoring information from all nodes in the CallManager Cluster according to the specified Profile.

There are two classes of Profile that can be made.

1) The first is 'CLUSTER_PROFILE'. This is a configuration statement that allows you to set values for monitoring every CallManager Appliance in the cluster within one statement. Cluster profile configurations can be provided in the following format: DEFINE CLUSTER_PROFILE (<profile type>, <name>=<value>[, <name>=<value>)] The <name>=<value> pairs can be listed all on the same line, or can be split over multiple Cluster profile statements on separate lines.

2) The second is the "APPLIANCE_PROFILE". This allows you to override the configuration values for an individual CallManager Appliance in the cluster. You do not have to provide a Cluster profile in order to specify an Appliance profile. If no Cluster profile is set and an Appliance profile is provided, then the Appliance profile overrides the product's default settings. If a Cluster profile is provided, then the Appliance profile will be used instead of the Cluster profile's settings. Appliance profile configurations can be provided in the format: DEFINE APPLIANCE_PROFILE (<profile type>, <node=\node-name>[, <name>=<value>])


of 204

The following profile types can be specified for the entire Cluster or individual appliances:

• ccmweb - Settings used for the web interface.

• cmsql - Settings used in the collection of device configuration data.

• cmperf - Settings used in the monitoring of device performance data.

• snmp - Settings used to access SNMP information.

• cdrutility - Settings used in the collection of CDR records.

The following sections describe each of the profile types and all <name>=<value> pair values associated to each profile type. The values listed show the product defaults.

ccmweb ! ccmweb profile DEFINE CLUSTER_PROFILE (ccmweb, port=8443, protocol=https)

port - The web interface port used by cdrutility, sqlgatherer and perfmongatherer.

protocol - The web interface protocol used by cdrutility, sqlgatherer and perfmongatherer.

cmsql ! cmsql Profile DEFINE CLUSTER_PROFILE (cmsql, Url=axl:https://<ip>:8443/axl/ ProxyAddr=<ip>, ProxyPort=<port>)

Url - The format of the URL required to access CallManager for device configuration data.

ProxyAddr - The IP address of the proxy server used (if any).

ProxyPort - The port of the proxy server used (if any).

cmperf ! cmperf DEFINE CLUSTER_PROFILE (cmperf, Url=https://<ip>:8443/perfmonservice/ services/PerfmonPort) DEFINE CLUSTER_PROFILE (cmperf, ProxyAddr=<ip>, ProxyPort=<port>) DEFINE CLUSTER_PROFILE (cmperf, Timeout=120, InstanceInterval=120, TeardownInterval=3600) DEFINE CLUSTER_PROFILE (cmperf, BackOffTime=4, BackOffTimeMultiplier=2.0, BackOffRetries=5)

Url - The URL required to access CallManager for device performance data.

ProxyAddr - The IP address of a proxy server if a proxy server is used to access the CallManager.

ProxyPort - The port of a proxy server if a proxy server is used to access the CallManager Timeout - Request timeout (in seconds) for all Cisco SOAP queries.

InstanceInterval - Refresh interval (in seconds) of the counter instance list for SOAP sessions.

Configuration

of 204

TeardownInterval - The interval (in seconds) between SOAP session teardown and reconstruction to maintain session query integrity. TeardownInterval=0 means never.

BackOffTime - The base time (in seconds) to back off when a rate control fault is received from CallManager.

BackOffRetries - The number of times to retry collecting data for a counter.

BackOffTimeMultiplier - For each successive retry, this multiplier is used to calculate the next backoff interval. Backoff times grow exponentially from the base backoff time.

snmp ! snmp DEFINE CLUSTER_PROFILE (snmp, Port=161, Version=2c) DEFINE CLUSTER_PROFILE (snmp, Timeout=10, Retries=5)

Port - The SNMP port to use to collect SNMP data from CallManager.

Version - The SNMP version to use. Only versions 1 and 2c are currently valid.

Timeout - The time (in seconds) to wait before retrying an SNMP get request.

Retries - The number of retries permitted before aborting SNMP get request.

cdrutility ! cdrutility DEFINE CLUSTER_PROFILE (cdrutility, CDRDownload=1) DEFINE CLUSTER_PROFILE (cdrutility, Url=http://<ip>:8080/CDRonDemandService/ services/CDRonDemand, Dsn=odbc:IPTMCDRDSN) DEFINE CLUSTER_PROFILE (cdrutility, ProxyAddr=10.2.1.1, ProxyPort=8080, Dir=C:\\cdr_rep\\) DEFINE CLUSTER_PROFILE (cdrutility, BudgetedBandwidth=100, SqlDbMaxSize=2000, CDRListRefreshOnRestart=0) DEFINE CLUSTER_PROFILE (cdrutility, SftpLocation=10.226.67.127)

CDRDownload - Switches the CDR download functionality on (= 1) and off (= 0).

Url - The format of the URL required to access CallManager for device configuration data.

ProxyAddr - The IP address of a proxy server if a proxy server is used to access the CallManager.

ProxyPort - The port of a proxy server if a proxy server is used to access the CallManager.

Dir - The local directory where CDR files are deposited.

BudgetedBandwidth - The throttled average bandwidth in kilobits to use for downloading CDR files.

SqlDbMaxSize - The maximum size (in Megabytes) the local CDR database is allowed to grow to before data purging occurs.

CDRListRefreshOnRestart - Switches on (= 1) or off (= 0) a complete refresh of the CallManager CDR file list on every re-start. This should be used if CDRs appear to be missing for a past time period.

SftpLocation - Used to set up a secure FTP address for retrieving CDR data, see the Secure FTP address for CDR Retrieval topic for details.


of 204

NAT Static Configuration The H.323 and Voice Gateway polling and the Phone polling features require direct access to these devices. Environments that employ Network Address Translation (NAT) between the EMC Smarts VoIP Performance Manager Monitoring Server and the gateways and/or phones will require additional manual configuration. The NAT static configuration provides a means of specifying the mapping between the IP addresses of the devices, as seen by CUCM, and the IP addresses as seen by the Monitoring Server.

SUBSYS NAT ! Define your NAT configurations here. ! For cluster specific translations, use the following format: ! NAT-MAP CLUSTER(<id>, name=<cluster>, source=<sourceIP>, dest=<destIP>, mask=<subnet>) ! ! For NAT mappings that are not cluster specific, use the following format: ! NAT-MAP GLOBAL(<id>, source=<sourceIP>, dest=<destIP>, mask=<subnet> ! where ! <id> = any unique Id, suggest using sequential numbers ! <cluster> = Name of the cluster that this NAT mapping is specific to ! <sourceIP> = IP address as seen by the CallManager ! <destIP> = IP address as seen from the managing node ! <subnet> = Subnet mask range ! ! e.g. ! NAT-MAP CLUSTER(1, name=CCM5_Clust, source=10.3.0.0, dest=10.4.0.0, mask=255.255.0.0) ! NAT-MAP CLUSTER(2, name=CCM5_Clust, source=10.1.1.0, dest=10.3.1.0, mask=255.255.255.0) ! NAT-MAP CLUSTER(3, name=CMC6_Clust, source=10.1.1.0, dest=10.3.1.0, mask=255.255.255.0) ! NAT-MAP GLOBAL(4, source=10.1.1.0, dest=10.2.1.0, mask=255.255.255.0) ! !** NOTE **! ! 1. Cluster NAT mappings take precedence over Global NAT mappings. ! 2. For a given cluster, source or destination IP addresses must not overlap ! or the configuration will not start. ! 3. For global NAT mappings, source or destination IP addresses must not ! overlap or the configuration will not start.

Mapping in the NAT static configuration may be specified as:

1. Cluster wide using the format:

NAT-MAP CLUSTER

This defines a translation that is applicable to a single cluster within a Cisco Unified CallManager environment.

2. Globally to the EMC Smarts VoIP Performance Manager Monitoring Server as:

NAT-MAP GLOBAL

This defines a translation that is applicable to all clusters within a EMC Smarts VoIP Performance Manager environment. If there is a global default and an override for a specific cluster, then the overridden value is used in the translation.

Configuration

of 204

name - name of the cluster to which this mapping shall be limited.

source - IP address as seen by the CUCM.

dest - IP address as seen by the EMC Smarts VoIP Performance Manager Monitoring Server.

mask - subnet mask range to be used by the mapping.


of 204

Secure FTP address for CDR Retrieval Sometimes the advertised IP address of the EMC Smarts VoIP Performance Manager Monitoring Server is not reachable from the CallManager due to NAT (Network Address Translation) or other networking issues. It is important that the CallManager is able to reach the Monitoring Server for the purpose of CDR uploads. Therefore in these situations, an extra line must be added to the static configuration for the cluster (i.e. if a cluster named HOWELL has been added, then open the static configuration named HOWELL in the Node Navigator). Here an IP address can be added that the CallManager can reach the Monitoring Server on.

To do this add the following line to the configuration:

DEFINE CLUSTER_PROFILE (cdrutility, SftpLocation=<ip_address>)

<IP Address> IP address of the Monitoring Server as seen by the CallManager. This will be the translated address in the case of NAT. The <IP Address> should be in decimal dot notation.

Example;

DEFINE CLUSTER_PROFILE (cdrutility, SftpLocation=10.226.67.127)

Configuration

of 204

Cisco Unity Integration Unity servers and any other related servers, such as Unity mail store, that have EMC Smarts VoIP Performance Manager for Cisco v4 installed can be linked directly to the VoIP Performance Manager for Cisco v5+ and Avaya Monitoring Server.

Although VoIP Performance Manager for Cisco v5+ and Avaya cannot be installed onto a Unity server, it is possible to integrate the Unity server data into the VoIP Performance Manager Displays. In addition, as Unity servers can be integrated with Exchange Mail servers, the mail server data can also be included in the Displays. This creates a seamless integration of all IP telephony plus related Unity and mail store servers under one node group.

NOTE: Please refer to the EMC Smarts VoIP Performance Manager for Cisco v4 Installation Guide for instructions on installing the VoIP Performance Manager Agent on to a Unity server.

NETWORK Configuration

(a) If the Unity machine (with VoIP Performance Manager for Cisco v4 installed) is connected to a CUCM 4 Publisher that also has VoIP Performance Manager for Cisco v4 installed then the NETWORK Configuration on the Publisher should have a MANAGED-NODES (<unity-ip-address>) statement added. This should have automatically occurred if VoIP Performance Manager was installed on the Unity machine prior to VoIP Performance Manager being installed on the Publisher. Therefore, in this case, the VoIP Performance Manager for Cisco v5+ and Avaya Monitoring Server that is monitoring the Publisher will need a MANAGED-NODES (<publisher-ip-address>) in its NETWORK Configuration and the Publisher will need a ROUTE-TO (managing-node-ip-address>) statement in its NETWORK Configuration.

(b) If the Unity machine (with VoIP Performance Manager for Cisco v4 installed) is not connected to a CUCM 4 Publisher but is being monitored directly by an VoIP Performance Manager for Cisco v5+ and Avaya Monitoring Server, then the Monitoring Server will need its NETWORK Configuration updated to point to the Unity server. Do this by adding the following statement then restarting the configuration:

MANAGED-NODES (<unity-ip address>)

All relevant Unity servers and exchange servers should now appear under the ‘Entire Network’ tree in the Nodes Navigator window of the VoIP Performance Manager for Cisco v5+ and Avaya Client (GUI).


of 204

Exchange Server Configuration

Please refer to the VoIP Performance Manager for Cisco v5+ and Avaya User Guide, Exchange Management section.

Configuration

of 204

Cisco Off Cluster CDRs EMC Smarts VoIP Performance Manager supports the monitoring of Cisco Call Detail Records (CDRs) and Call Management Records (CMRs) that are written to a remote Microsoft SQL Server hosting a CDR database (Off Cluster CDR database).

Cisco Configuration To configure an Off Cluster CDR database carry out the following steps:

Step 1 Replicate the CDR database schema to a remote Microsoft SQL server for the Cisco CallManager version deployed. CDR database schemas may be different between CallManager versions.

NOTE: Cisco Unified CallManager 4.1(x) cannot write to the CDR database schema for Cisco CallManager 3.3(x).

Step 2 Create a user on the remote Microsoft SQL server with read/write access to the CDR database it now hosts. It is recommended to use SQL Server Authentication for this user’s security. The suggested user-name is 'CiscoCCMCDR'.

Step 3 Using the Cisco Unified CM Administration web interface, configure the CDR Off Cluster settings via the System > Enterprise Parameters menu.

A unique Cluster ID is required for each Cisco cluster in your network which is to be configured for Off Cluster CDR records. Enter this value into the “Cluster ID” field.

The 'Off Cluster CDR Connection String' field contains a DSN string for the ODBC connection to the Off Cluster CDR database. Parameters required are server-name for the remote Microsoft Windows server hosting the CDR database, database-name for the Microsoft SQL server Off Cluster CDR database, user-name with read/write access to the Off Cluster CDR database and password for the user. The format of the “Off Cluster CDR Connection String” for a user with SQL server authentication rights is:

”DRIVER={SQL Server}; SERVER=server-name; DATABASE=database-name; UID=user-name; PWD=password”

eg. “DRIVER={SQL Server}; SERVER=NORTH-2; DATABASE=CDR; UID=CiscoCCMCDR; PWD=cisco”

Step 4 Save the settings by clicking “Update” on the Enterprise Parameters Configuration web page.

Step 5 Restart the Service “Cisco CDR Insert” on the Publisher.

Step 6 Check the Application Log in the Windows Event Viewer to see that there are no error notifications for the 'Cisco CDR Insert' service. Information notifications are ok. If there are errors with the 'Cisco CDR Insert' service for the CDR Off Cluster configuration please contact Cisco TAC.


of 204

VoIP Performance Manager Configuration Step 1 Install VoIP Performance Manager on each Publisher that is configured for 'Off Cluster CDRs'.

Step 2 Install the VoIP Performance Manager CDR Monitor on to the Windows server that is hosting the Microsoft SQL server 'Off Cluster CDR database'.

The installer CDRMonitorSetup.exe can be found in the CDR Monitor folder under the EMC Smarts VoIP Performance Manager installation directory.

e.g. C:\Program Files\EMC Smarts VoIP Performance Manager\CDR Monitor

Copy the CDRMonitorSetup.exe file to the Off Cluster CDR server before installing.

Step 3 Restart VoIP Performance Manager on each Publisher configured for Off Cluster CDRs.

If CDR and CMR records fail to be processed by VoIP Performance Manager after completing these configuration steps, please contact EMC Technical Support.

Configuration

of 204

Nortel Communication Server After installing the EMC Smarts VoIP Performance Manager components, as described in the Installation section, a number of configuration procedures will need to be completed in order for EMC Smarts VoIP Performance Manager to see the Nortel PBXs. This section provides step by step instructions on how to carry out these configurations.

Configuration Procedures

Step 1 Nortel CLI Configuration Inventory reporting and multi-user login need to be setup on the Nortel PBX. Both of these are completed through the Nortel CLI interface.

Step 2 Nortel Element Manager Configuration The SNMP Traps from the Nortel PBX need to be directed to a specific port. This is set up through the Nortel Element Manager on the SNMP Configuration page through the 'SNMP trap destination address' field.

Step 3 Add the NORTEL_PBX Collector A PBX Collector needs to be started on each Monitoring Server. This is done by running the addNORTEL_PBX batch file from the \Server\Configuration folder in the installation path.

Step 4 Update the NORTEL_PBX Configuration Once the Collector has been installed, the corresponding Configuration file on the Monitoring Server needs to be updated with the details of each PBX to be monitored.

Step 5 Update the PASSWORDS Configuration The Nortel password needs to be added to the PASSWORDS Configuration file in the format nortel-cli:\<pbx-name>. An SNMP Community String may also need to be configured in the PASSWORDS Configuration.

Step 6 Start Databases and Thresholds Once the configuration is complete two pre-packaged Database Collections and one Alert should be started. All of these can be started from the Nortel Monitoring Node Display which is accessed through the Client (GUI).


of 204

Nortel CLI Configuration The Nortel PBX needs to be setup so that phone and card inventory data and multi-user login are available. Both of these features are configured through the Nortel CLI interface.

1. Access the Nortel CLI Interface Use standard procedures to Telnet to the Nortel CLI interface on the Signalling Server.

2. Enabling Inventory Reporting EMC Smarts VoIP Performance Manager utilizes the Inventory Reporting feature to obtain information from the phone and card inventory. This feature is described in the Nortel Communication Server 1000 Features and Services Fundamentals guide (NN43001-106). To enable Inventory Reporting carry out the following steps;

Step 1 Log on to the Call Server.

Step 2 At the command prompt enter: LD117

Step 3 (Optional) At the command prompt enter: INV PRT SETS

Use this command if it is uncertain whether an inventory has been previously generated. If an inventory is found then the inventory data will be displayed. If an inventory is not found then the response 'Sets file is Non-existent, try again later' will be returned and the next step will be to generate the inventory.

Step 4 At the command prompt enter: INV GENERATE ALL This command will initiate the generation of both card and telephone Inventory files immediately.

Step 5 At the command prompt enter: INV PRT SETS Use this command once again to check that the inventory has now been generated.

Step 6 At the command prompt enter: INV MIDNIGHT ALL Use this command to schedule automatic inventory generation. This is recommended so that most up-to-date inventory will always be available.

3. Multi-user Login Setup EMC Smarts VoIP Performance Manager utilizes the CLI interface to gain access to both the Call Server and the Signalling Server, in order to do this it is necessary to activate multi-user login. The Multi-user logon feature is described in the Nortel Communication Server 1000 System Management Reference guide (NN43001-600).

Multi-user login can be activated by carrying out the following steps;

Step 1 Log on to the Call Server.

Step 2 At the command prompt enter: LD 17

Configuration

of 204

Step 3 The following prompts will be returned on the command line. Use the corresponding user inputs to complete the Multi-user login process.

Command Line Prompt User Input Description

REQ CHG Change

TYPE OVLY Overlay

SID <cr> System ID number

MULTI USER ON Activate multi-user login

Multi-user login enables up to five users to log in, load, and execute overlays simultaneously. These five users are in addition to an attendant console or maintenance terminal. Without this option turned on, EMC Smarts VoIP Performance Manager will fail to login to the Call Server especially when Nortel Element Manager is being used.

With multiple overlays operating concurrently, there is the potential for a database conflict if two or more overlays attempt to modify the same data structure. Multi-user Login software prevents such conflicts. When a user requests that an overlay be loaded, the software determines if it could pose a potential conflict with an overlay that is already executing. If no conflict exists, the requested overlay is loaded and if a conflict does exist the system issues the following message:

OVL429-OVERLAY CONFLICT

EMC Smarts VoIP Performance Manager will retry the request should an overlay conflict occur.


of 204

Nortel Element Manager Configuration EMC Smarts VoIP Performance Manager needs the SNMP traps from the PBX to be directed to it on a specific port (as set in the ‘DEFINE TRAPPORT’ statement of the NORTEL_PBX Configuration). This is essential in order for the Quality of Service records to obtain data. The Nortel Element Manager is used to add an entry to the list of trap destinations. The steps below outline the process of adding a new trap destination:

1. Log into Nortel Element Manager In a Web browser, browse to the IP address of the Nortel Signalling server (same IP address as used in the ADD PBX entry of the NORTEL_PBX Configuration). For example:

http://10.118.10.5/

Log in to Nortel Element Manager with the administrative login (same credentials used in the PASSWORDS nortel-cli configuration entry).

2. Configure the SNMP Trap Destination EMC Smarts VoIP Performance Manager needs to be a configured SNMP trap destination. To do this proceed as follows;

Step 1 Go to the menu on the left and select System – SNMP, this will open the SNMP Configuration page.

Step 2 Go to the last entry on the page, SNMP trap destination address (OPEN_ALARM). This list supports up to 10 destination IP addresses. Use the drop list to locate an empty slot and then enter into the IP address field the IP address of the EMC Smarts VoIP Performance Manager Monitoring server.

Step 3 When finished select the Submit button to save the changes.

Configuration

of 204

3. Configure the QoS Thresholds Nortel makes the following Threshold settings available to determine the warning and error status of calls. However, as EMC Smarts VoIP Performance Manager uses its own configuration settings to determine call quality and calculate MOS scores, these Nortel threshold settings are used to obtain the required level of voice quality sample data. Therefore these Nortel threshold settings can be adjusted to lower levels than normal in order to allow a sample of 'normal' as well as 'poor' voice quality.

Step 1 Go to the menu on the left and select IP Telephony – QoS Thresholds, this will open the QoS Thresholds Configuration page.

Step 2 In the 'QoS Call Basis Threshold Parameters' section of the page adjust the following fields to

the following recommended settings:

Call Latency Warning Threshold 20

Call Jitter Warning Thresholds 20

Call Packet Loss Warning Threshold 5 (minimum setting allowed)

Call R Factor Warning Threshold As required - not used by PROGNOSIS

Call Latency Unacceptable Threshold 50

Call Jitter Unacceptable Threshold 30

Call Packet Loss Unacceptable Threshold

20 (Unacceptable setting must be larger than Warning)

Call R Factor Unacceptable Threshold As required - not used by PROGNOSIS

Sampling Period As required - not used by PROGNOSIS


of 204

These settings will not generate alerts for 'perfect' calls, or those approaching perfection, but will generate alerts if calls start to deteriorate. This done for efficiency reasons. However, if required, these recommended settings can be lowered to increase the sampling ratio, or raised to reduce the sampling ratio. Raising these figures may be required for larger deployments.

Step 3 When finished select the Submit button to save the changes.

The EMC Smarts VoIP Performance Manager for Nortel configuration is now complete and will now be ready to collect data.

Configuration

of 204

Add the NORTEL_PBX Collector A PBX collector, named NORTEL_PBX, needs to be added before EMC Smarts VoIP Performance Manager can start monitoring the Nortel environment. This collector is added by running the following batch file from the EMC Smarts VoIP Performance Manager Installation path in the \Server\Configuration folder:

addNORTEL_PBX.bat

Simply double-click on the batch file name to install the collector.


of 204

Update the NORTEL_PBX Configuration After adding the Collector a new NORTEL_PBX Configuration file will be created. This will be visible in the Configurations folder of the Node Navigator in the GUI.

This NORTEL_PBX Configuration will now need to be updated with details of each PBX to be monitored. To update the configuration, right click on the NORTEL_PBX configuration name in the Nodes Navigator and then select ‘Properties’ from the context menu. This will open the Configuration Properties dialog box.

Configuration

of 204

An ADD PBX statement needs to be added to the Configuration for each PBX that is to be monitored, up to 10 ADD_PBX statements can be included. A user-defined PBX name and its applicable IP address needs to be input, it is also recommended to include a customer name and a site name as these will assist in identifying individual PBXs in the various data Displays.

SUBSYS <PBX_Name> ADD PBX (<pbxname>, ip=<ipaddress>[, customer=<customer>][, site=<site>])

<pbxname> Mandatory field. Input a user-defined name for this PBX with a -PBX suffix, e.g. \CS1000S-PBX.

ip=<ipaddress> Mandatory field. Add the IP address of the Signalling server, e.g. 10.118.10.5.

customer=<customer> Optional but recommended field. Add a customer name to associate with the PBX, e.g. JR Parvis.

site=<site> Optional but recommended field. Input a site name associated with this PBX, e.g. HQ.

In addition a DEFINE CLI_PROFILE statement is also required for CS1000 4.0 and 5.0 PBXs. This is not required for CS1000 4.5 PBXs.

SUBSYS <PBX_Name> ADD PBX (<pbxname>, ip=<ipaddress>[, customer=<customer>][, site=<site>]) [DEFINE CLI_PROFILE (<pbxname>[, cslogin-profile=<login-profile>])

The DEFINECLI-PROFILE statement requires the following parameters.

cslogin-profile=<login-profile> The cslogin-profile MUST be set if running with a Nortel 4.0 or 5.0 system. For either of these systems input the applicable profile name: ‘CS_CS1000E50Login’ for CS1000 5.0 or ‘CS_CS1000E40Login’ for CS1000 4.0 The DEFINE CLI_PROFILE can be omitted for CS1000 4.5 PBXs as the default cslogin-profile setting of ‘CS_DefaultLogin’ will be applicable.

NOTE: The profile name must match an entry in Server\Configuration\IPTM\Nortel\Nortel-CLI-Login.xml. If there are problems connecting to a PBX, a custom entry can be added to the xml file.

The configuration details shown in this topic reflect the mandatory parameters that are required for Nortel PBX monitoring. Further optional configuration parameters are available and these are described in the NORTEL_PBX Configuration section.


of 204

Example Configurations Example - Monitoring CS1000E 5.0:

SUBSYS NORTEL_PBX ADD PBX( \NORTEL50-PBX, ip=10.118.10.5, customer=XYZ, site=Washington) DEFINE CLI_PROFILE (\NORTEL50-PBX, cslogin-profile=CS_CS1000E50Login)

Example - Monitoring CS1000E 4.5 (note that no DEFINE CLI_PROFILE is required in this case)

SUBSYS NORTEL_PBX ADD PBX( \NORTEL45-PBX, ip=10.118.10.7, customer=ABC, site=London)

Example - Monitoring CS1000E 4.0:

SUBSYS NORTEL_PBX ADD PBX( \NORTEL40-PBX, ip=10.118.10.9, customer=DEF, site=Sydney) DEFINE CLI_PROFILE (\NORTEL40-PBX, cslogin-profile=CS_CS1000E40Login)

Configuration

of 204

PASSWORDS Configuration for Nortel The next step is to add the Nortel password to the PASSWORDS Configuration. The entry includes the PBX name and is added in the following format:-

nortel-cli:\<pbx-name>

For the Username and Password fields input your Nortel administrative login and password details as used to access the Nortel PBX.

An SNMP community string is also required. However, EMC Smarts VoIP Performance Manager will assume a default SNMP community string of ‘public’. If ‘public’ is NOT a community string defined in the ADMIN_COMM section of the Nortel Element Manager (located on the SNMP Configuration page, check all slots) the PASSWORDS Configuration will require an entry (password only), as shown below to be added in order to specify the required community string.

snmp:\<pbx-name>

When the PASSWORDS Configuration screen has been completed select the Start button which will save the settings and start the configuration.


of 204

Databases and Thresholds The EMC Smarts VoIP Performance Manager for Nortel product includes two pre-packaged Databases and a pre-packaged Threshold. These are not started by default and, if required, will need to be manually started from the Nortel Monitoring Node Display.

While these two Databases and the Threshold are optional it is recommended that they be started in order to obtain full data collection from the Nortel environment.

The Database Collections include:

Utilization Reporting Database (NTL-Reporting) This records availability and performance data for short and long term utilization and Service Level Agreement (SLA) reports. Data collected includes details of the routes in the PBX, summary of voice quality exception information for zone-zone pairs and a list of all zones in the PBX together with a range of zone parameters.

Status Log Database (NTL-Status Log) This database records status changes for devices in the Nortel environment using the PrognosisAutomationProblemSummaryOpen (PROBSUM) record.

Configuration

of 204

The Threshold is:

Nortel PBX Alerts (Nortel_Alert) This Threshold contains a range of conditions that monitor the health of each PBX in the Nortel environment and provides alerts and availability information. Areas monitored include the Gateway, Media Card, PBX CLI, Routes, Server and Zones.

To start each of these simply click on the Start link in the respective window on the right side of the Display.


of 204

NORTEL_PBX Configuration The section describes all of the parameters that are contained in the EMC Smarts VoIP Performance Manager NORTEL_PBX Configuration document. In normal operations many of these parameters can be left at the default settings.

SUBSYS NORTEL_PBX ! ! SNMP TRAP IN processing DEFINE TRAPPORT(#GlobalDefault, port=162) DEFINE BURSTFILTER(#GlobalDefault, period=30, number=1000, restart=30) ! ! Nortel PBX Configuration (Nortel Communications Server) ! ---------------------------------------------------------------------- ! For each PBX: ! ! ADD PBX (<pbxname>, ip=<ipaddress>[, customer=<customer>] ! [, site=<site>]) ! [DEFINE CLI_PROFILE (<pbxname>[, port=<port>][, snmp=1|2c] ! [, sslogin-profile=<login-profile>] ! [, cslogin-profile=<login-profile>] ! [, cslogin=<cslogin>]) ! ! Sample configuration ! ADD PBX( \CS1000S-PBX, ip=10.118.10.5, customer=JR Parvis, site=HQ) ! DEFINE CLI_PROFILE (\CS1000S-PBX, cslogin-profile=CS_CS1000E50Login)

Syntax DEFINE BURSTFILTER & DEFINE TRAPPORT

Settings for both of these statements are placed into the configuration by default and normally should not be changed. The Trapport statement defines the port that PROGNOSIS will listen on for SNMP Traps and this should only be changed if the PBX is reconfigured to send traps to a port other than the default of 162.

ADD PBX Up to 10 Nortel PBXs can be added by using one ADD PBX statement for each PBX.


ip=<ipaddress> Mandatory field. Add the IP address of the Signalling server.

customer=<customer> Optional but recommended field. Add a customer name to associate with the PBX, e.g. ABC Inc.

site=<site> Optional but recommended field. Input a site name associated with this PBX, e.g. Washington..

Configuration

of 204

DEFINE CLI_PROFILE The DEFINE CLI_PROFILE can be omitted for CS1000 4.5 PBXs as default settings will be applicable. It must be added when running a Nortel software release other version 4.5, or if EMC Smarts VoIP Performance Manager fails to login to the PBX and a specific login profile is required.


port=<port> Do not use.

snmp=1|2c The default value is 1. The only other value supported by EMC Smarts VoIP Performance Manager is 2c. However all Nortel equipment only supports 1, so this parameter may be omitted for Nortel installations.

sslogin-profile=<login-profile> Login sequence to use for connection to a Signalling server. As the default setting of ‘SS_DefaultLogin’ is applicable for Nortel CS1000 4.0, 4,5, 5.0 this parameter may be omitted.

cslogin-profile=<login-profile> The cslogin-profile MUST be set if running with a Nortel 4.0 or 5.0 system. For either of these systems input the applicable profile name:

‘CS_CS1000E50Login’ for CS1000 5.0 or

‘CS_CS1000E40Login’ for CS1000 4.0

This parameter can be omitted for Nortel CS1000 4.5 as the default setting of ‘CS_DefaultLogin’ will be applicable.

NOTE: The profile name must match an entry in Server\Configuration\IPTM\Nortel\Nortel-CLI-Login.xml. If there are problems connecting to a PBX, a custom entry can be added to the xml file and then configured via the ss or cs-login-profile.

cslogin=<cslogin> Do not use this statement unless under the guidance of EMC Technical Support in a troubleshooting situation.


of 204

Setting up Multiple Monitoring Servers A separate additional server installation, known as a Managing Server, is required if more than one EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Monitoring Server is being used to monitor multiple IP telephony PBXs/Clusters. This is used so that data can be combined for the Client (GUI). An example deployment is shown below.

After installing the EMC Smarts VoIP Performance Manager Monitoring Server application on to each Monitoring Server and then installing the Managing Server application onto a separate machine, the NETWORK Configuration on the Managing Server will need to be updated with a MANAGED-NODES statement for each Monitoring Server.

Example:

MANAGED NODES (10.1.1.190) !Monitoring Server A MANAGED-NODES (10.1.1.191) !Monitoring Server B

When complete start the NETWORK Configuration then check the Nodes Navigator of the Managing Server to see that each Monitoring Server is now included. A few minutes should be allowed for the information to propagate through to the Managing Server following the NETWORK Configuration update.

Configuration

of 204

Setting up the Client (GUI) The EMC Smarts VoIP Performance Manager for Cisco v5+ and Avaya Client (GUI) needs to be linked to the VoIP Performance Manager for Cisco v5+ and Avaya Monitoring or Managing Server.

This is done automatically if you are including the Client in the same installation on the same machine as the Server. However, if the Client is being installed by itself on a stand-alone machine, the installation will ask for the IP address of the Server to be specified. No other configuration is required.

Additional Information

of 204



of 204

Stopping the Service Should it ever be necessary to shut down EMC Smarts VoIP Performance Manager you can use this section to choose the appropriate method. There are four methods by which the VoIP Performance Manager server may be shut down.

• Via the VoIP Performance Manager Service Control Panel

• Via the Windows Services Control Panel applet

• Via the command line

• Via the VoIP Performance Manager Client (GUI)

NOTE: Stopping or starting VoIP Performance Manager is independent of stopping or starting Microsoft SQL Server Desktop Engine (MSDE). In order shut down all components of VoIP Performance Manager you may need to also consider shutting down the VoIP Performance Manager Tomcat Web Server application and the MSDE, if these were included in the original VoIP Performance Manager installation.


of 204

Method 1: Service Control Panel The EMC Smarts VoIP Performance Manager Service Control Panel is a small application that comes with VoIP Performance Manager and can be accessed from the Start Menu. Use the following procedure:

Procedure Step 1 From the Windows® operating system Start Menu select

All Programs >EMC Smarts VoIP Performance Manager > VoIP Performance Manager Service Control Panel.

Step 2 On the Service Control Panel click on the button for EMC Smarts VoIP Performance Manager. When VoIP Performance Manager is stopped the status indicator will show red.

The Tomcat Web Server can also be stopped by selecting the stop button for this application.


of 204

Method 2: Windows Services Control Panel EMC Smarts VoIP Performance Manager runs as a Windows service and can be shut down using the standard Services Control Panel applet. Use the following procedure to shut down VoIP Performance Manager using this method:

Procedure Step 1 From the Windows Start Menu select Control Panel.

Step 2 From the Control Panel window double-click on Administrative Tools.

Step 3 Double click on Services to open the Services Window.

Step 4 Scroll down and click on the service called EMC Smarts VoIP Performance Manager.

Step 5 From the side panel select Stop the Service to shut down VoIP Performance Manager.

Alternatively, right click on EMC Smarts VoIP Performance Manager then select Stop from the context menu.


of 204

Method 3: Command Line To stop EMC Smarts VoIP Performance Manager from the command line you must be at the VoIP Performance Manager Server. Use the following procedure:

Procedure Step 1 From the Windows Start Menu select Run.

Step 2 At the Run dialog, enter cmd in the Open edit box.

Step 3 When the command window opens, type the command net stop "emc smarts voip

performance manager".

Step 4 VoIP Performance Manager will stop within several seconds as shown below.


of 204

Method 4: Client (GUI) You can shutdown the EMC Smarts VoIP Performance Manager server from any other computer that can run the VoIP Performance Manager Client and which has TCP/IP connectivity to the Server. To do this use the following procedure:

Procedure Step 1 From the Windows Start Menu select:

All Programs/EMC Smarts VoIP Performance Manager/VoIP Performance Manager GUI

Step 2 When the logon dialog appears, log on as Administrator or as a user with administrator privileges using the appropriate password.

Step 3 When the GUI has started, go to the Nodes Navigator and right-click on the VoIP Performance Manager Server that you wish to stop.

Step 4 Select the command Stop EMC Smarts and either Warm Restart or Cold Restart. Warm

Restart ensures that when you later restart VoIP Performance Manager (or reboot), databases and analysts that were running before you shut VoIP Performance Manager down will also restart. If you do not want VoIP Performance Manager to restart these services, select Cold Restart.


of 204

Upgrade Installation The Upgrade facility provides an easy method of moving from your existing EMC Smarts VoIP Performance Manager version to the latest version which will offer new and enhanced features. This section provides detailed information on how to upgrade to the latest version.

VoIP Performance Manager for Cisco v5 and Avaya version 1.0 can only be upgraded to VoIP Performance Manager for Cisco v5+ and Avaya version 2.0, do not attempt to upgrade to and from any other versions.

IMPORTANT NOTE: Prior to attempting an upgrade please ensure that you request a new version of the EMC Smarts VoIP Performance Manager license keys from EMC Technical Support if the monitoring of off-board systems (e.g. Avaya and Cisco Communications Manager 5) is required.

Important Points Please note the following points:

• It is advisable to back-up the current installation before installing an upgrade. This then provides the opportunity to rollback to the existing installation if required (see Backup Instructions).

• Normally all running Databases, Thresholds and Analysts will be automatically restarted after completing an upgrade. However, to check this you can open the Status Display from the connected GUI prior to commencing the upgrade and take note of all the Databases, Thresholds and Analysts that are currently running. After the upgrade has been completed reopen this Display and if necessary restart any Databases, Thresholds and Analysts that have not been automatically restarted.


of 204

Upgrade Installation Order The upgrade should be completed top/down from the GUI, the highest level Managing server and Reporter server to any lower-level Managing servers and Monitoring servers:

1. Upgrade EMC Smarts VoIP Performance Manager on the GUI, the top-level Managing server and, if applicable, the Reporter server.

2. Upgrade any mid-level Managing servers.

3. Upgrade EMC Smarts VoIP Performance Manager on the lower-level Managing servers, the Monitoring servers and any Web or Windows servers.


of 204

Procedure Step 1 Stop the EMC Smarts VoIP Performance Manager service.

Step 2 Paste new license files into the <installation-folder>\Server\Configuration directory (only if the monitoring of off-board systems is required) .

Step 3 Place the EMC Smarts VoIP Performance Manager Upgrade CD into the CD-ROM drive.

If Autorun is activated the CD will start the InstallShield program automatically.

If Autorun does not function select the Windows Start button and from the menu select Run. Browse for the CD Drive then select the file Setup.exe. Select the OK button to run the InstallShield program.

Step 4 Setup will prompt with the option Upgrade Installation.

Step 5 Ensure that Upgrade Installation is checked then select the Next> button. The Upgrade

Installation will continue automatically, or select the Cancel button to abort the Upgrade.


of 204

What DOES happen on Upgrade • Static configurations are maintained. However, the Availability Configuration on CallManager

machines is overwritten with a new Availability Configuration.

• HTML templates are maintained.

• The following statistics will be reset; Availability, Dispatch Manager logs, Problem logs and File Manager logs

• The wvlog.txt log file is deleted.

• iradicol.ini, iravcol.ini, ircsctrc.ini, irlancol.ini, irpag.ini, irtecad.ini, nslookup.ini, prgnini.ini, trace.ini are merged on upgrade (old values are kept on upgrade).

• Software inventory history is maintained on upgrade (file SWINVDB).

• Old UDEFSREC is merged with new UDEFSREC (old records replaced with newer ones).

• irgui.ini is restored on upgrade.

• Standard back end packaging is overwritten with new packaging.

What DOES NOT happen on Upgrade • New versions of static configurations are not supplied (except Extractor which contains new SNMP

items). New ones are readily available in the Configuration folder.

• No changes to the service are done. Service name is not changed.

• Modifications to standard packaging are not kept.

• File Manager logs are NOT maintained.

• Availability logs are NOT maintained. However, any availability data recorded in EMC Smarts VoIP Performance Manager databases is maintained. Fields such as “Mean Time Between Failure” (MTBF) are reset.


of 204

Backup Instructions When an upgrade is performed the current installation will be upgraded 'in place', it is therefore highly recommended that a backup be made of the existing EMC Smarts VoIP Performance Manager application prior to starting the upgrade. This provides an opportunity to roll back to the existing system should any problems or incompatibilities occur.

The backup procedure should be carried out on each server.

NOTE: All of the following components may not be installed; therefore you may not need to back up all of these files. The following examples are based on a default installation.

Step 1 Back-up the whole EMC Smarts VoIP Performance Manager installation folder

(i.e: C:\Program Files\EMC Smarts VoIP Performance Manager)

Step 2 Back-up the EMC Smarts VoIP Performance Manager Start Menu folder.

Step 3 Back-up the Registry Key (Old installation log data):

HKEY_LOCAL_MACHINE\Software\IntegratedResearch\PROGNOSIS\ServiceName

i.e. HKEY_LOCAL_MACHINE\Software\IntegratedResearch\PROGNOSIS\EMC Smarts VoIP Performance Manager

Step 4 Back-up the Registry Key (Old Uninstall settings for InstallShield):

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\PRODUCT_GUID

i.e. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{2B10....1B}

or,

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{2B10....1C}

NOTE: Check the “LogFile” registry key to verify that the path specified matches with the installation being backed-up, this will help to identify the corresponding PRODUCT_GUID to use.


of 204

RollBack Instructions Should it become necessary, it is possible to rollback to the previous EMC Smarts VoIP Performance Manager installation as long as the files have been backed up as described in the previous section.

Restore only the items below that you have installed or backed up previously. The following is based on a default installation.

Carry out the following steps on each server that needs to be rolled back.

Step 1 Stop all running EMC Smarts VoIP Performance Manager processes.

Step 2 Delete all files from the EMC Smarts VoIP Performance Manager folder,

i.e. C:\Program Files\EMC Smarts VoIP Performance Manager

Step 3 Delete the Start Menu EMC Smarts VoIP Performance Manager item.

(Note: There could be some locked files/folders - delete as much as you can. Locked files/folders are released if you simply reboot your machine.)

Step 4 Delete the newly created uninstall registry key, once again, verifying the LogFile key for the Installed Directory.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\PRODUCT_GUID.

Step 5 Expand your backed-up VoIP Performance Manager into the folder path,

C:\Program Files\EMC Smarts VoIP Performance Manager

Step 6 Restore the start menu item.

Step 7 Restore the exported registry keys by double clicking on the ".reg" file.


of 204

Patch Installation From time to time EMC Smarts VoIP Performance Manager patch files will become available. These normally contain updates and/or fixes to correct reported problems.

Patch Installation Order Patch files should be installed top/down from the GUI, the highest level Managing server and the Reporter server to any lower-level Managing servers and the Monitoring servers:

1. Patch EMC Smarts VoIP Performance Manager on the GUI, top-level Managing server and, if applicable, the Reporter server.

2. Patch any mid-level Managing servers.

3. Patch EMC Smarts VoIP Performance Manager on the lower-level Managing servers, the Monitoring servers and any Web or Windows servers.


of 204

Installing a Patch Step 1 Copy the patch file to a temp folder on the Windows server (e.g. C:\EMC Smarts VoIP

PerformanceManager-Temp).

Step 2 Go to the folder and double-click on the patch file name or icon.

Step 3 The InstallShield process will commence and the ‘Welcome’ dialog will be displayed. Select the Next > button and follow the screen prompts to complete the installation.

Support Files Upon installation of a patch file two log files will be created. These files can be useful to refer to in case of any unexpected problems with the patch installation or to determine which patches have already been installed. The following files will be created in the Patches folder of the installation directory:

Patchlog-m<patch issue number> (e.g. Patchlog-m001) This file provides a detailed log of the installation of each individual patch.

Audit.log This file provides a single audit trail of each patch that has been installed.

Uninstalling a Patch This procedure will always uninstall the last patch that was installed. It may be repeated to uninstall more than one patch but will only ever uninstall in the reverse order of installation. Therefore there is no option to specify which patch is to be uninstalled.

Step 1 Start a command shell (cmd.exe)

Step 2 Change to the patches directory that is underneath the EMC Smarts VoIP Performance Manager install directory.

E.g. if EMC Smarts VoIP Performance Manager is installed in C:\Program Files\EMC Smarts VoIP Performance Manager, issue the commands:

C: \>cd \Program Files\EMC Smarts VoIP Performance Manager\Patches

Step 3 Uninstall the patch using the -u option of irpatch:

irpatch -u

You will need to respond “Y” to confirm the uninstall but this can be avoided by using the optional ‘-n’ command line switch if you want to automate this task.

The latest patch will now be uninstalled.


of 204

Manual Start-Up If you do not want EMC Smarts VoIP Performance Manager to start automatically at system start up, it can be set to manual through the Windows Services dialog by using the following procedure;


Step 2 From the Control Panel window double-click on Administrative Tools.

Step 3 Double click on Services to open the Services Window.

Step 4 Scroll down and right click on EMC Smarts VoIP Performance Manager then select Properties

from the context menu.


of 204

Step 5 On the General tab of the EMC Smarts VoIP Performance Manager Properties dialog change the Startup Type from 'Automatic' to 'Manua'.

Step 3 Select the OK button.

Tomcat Web Server and MSDE If the Tomcat Web Server and MSDE applications were included in the original EMC Smarts VoIP Performance Manager installation you may also wish to set these to manual start up as well. This is done in the same manner as the EMC Smarts VoIP Performance Manager application through the Services applet by selecting EMC Smarts VoIP Performance Manager Tomcat Web Server and Microsoft SQL Server Desktop Engine (MSDE) and setting the Startup Type to 'Manual'.


of 204

Uninstalling In most cases EMC Smarts VoIP Performance Manager can be easily uninstalled by using the Windows Control Panel. However, in those cases where this is not possible this section contains full details of the manual uninstallation procedure.


of 204

Using Windows Control Panel EMC Smarts VoIP Performance Manager can be removed from the server using the standard Windows Control Panel applet.

NOTE: Shutting down EMC Smarts VoIP Performance Manager has almost the same effect as complete removal. If VoIP Performance Manager is shutdown it does not participate in the operation of Windows 2000 or the CallManager in any way. You should only need to uninstall VoIP Performance Manager if your license has expired and you wish to return the disk space that VoIP Performance Manager is using to the operating system. See the section “Stopping the Service” for details on how to shutdown VoIP Performance Manager.

Use the following procedure to remove VoIP Performance Manager from your server:


Step 2 From Control Panel, double-click on Add or Remove Programs.

Step 3 Scroll down and click on EMC Smarts VoIP Performance Manager.

Step 4 Click the Change/Remove button. The setup program will start.


of 204

Step 5 The following confirmation dialog will be presented.

Click the OK button to confirm the removal of VoIP Performance Manager. Setup will shutdown VoIP Performance Manager and proceed to remove all programs and data collected since the product was installed.

Step 6 The next dialog box will ask you to select any components from the VoIP Performance Manager installation that you wish to retain.

Check the required items then click the Next> button to proceed.

NOTE: Removing VoIP Performance Manager databases - The Setup program can only remove databases collected underneath the installation folder (e.g. C:\Program Files\EMC Smarts VoIP Performance Manager). If you have collected databases to another location you must remove these files manually.


of 204

Step 7 A progress dialog will appear as shown below.

Step 8 When the setup program has completed the file removal, you will be presented with the

following dialog.

Select the Finish button to complete the uninstall.


of 204

Manual Uninstall This section is relevant to users who are unable to uninstall EMC Smarts VoIP Performance Manager through the Add or Remove Programs screen of the Windows Control Panel applet. It provides step by step instructions for removing VoIP Performance Manager completely from the system.

The following procedure assumes that VoIP Performance Manager is installed at a location that will be referred to as <VoIPPM_Install_Home>. If a default installation was originally performed then the value of <VoIPPM_Install_Home> will be; C:\Program Files\EMC Smarts VoIP Performance Manager.

Procedure These steps describe in chronological order the actions needed to remove VoIP Performance Manager manually from the system.

Step 1 Close and Stop all EMC Smarts VoIP Performance Manager processes Stop the VoIP Performance Manager service and close any VoIP Performance Manager processes including the Service Control Panel and GUI.

Step 2 EMC Smarts VoIP Performance Manager Server Service If you have installed the VoIP Performance Manager server component the installation would have created a service on your system. The name of this service can be found by opening the Service.ini file from the <VoIPPM_Install_Home> folder.

For example: C:\Program Files\EMC Smarts VoIP Performance Manager\Service.ini

[Services] service1=EMC Smarts VoIP Performance Manager service2=EMC Smarts VoIP Performance Manager Tomcat Web Server

To remove this service from your system, open a command prompt and change to the server folder of your VoIP Performance Manager installation and type the following:

…\EMC Smarts VoIP Performance Manager\Server> irinstall remove "EMC Smarts VoIP Performance Manager" Removing service EMC Smarts VoIP Performance Manager ... Service removed successfully. …\EMC Smarts VoIP Performance Manager\Server>

Where “EMC Smarts VoIP Performance Manager” is the name found in the service.ini file.

Tip: How to load the command prompt: START Menu > Run > type in cmd

Tip: Obtaining irinstall.exe Your installation may not have irinstall.exe, if this is so, please contact EMC Technical Support for a copy of this executable.


of 204

Step 3 RegistryVoIP Performance Manager saves installation settings in the registry to be later used during uninstallation. Follow these instructions carefully to safely remove the registry entries corresponding to the VoIP Performance Manager installation you are removing. You will need to load the registry editor first.

Tip: How to load the Registry Editor: START Menu > Run > type in regedit

VoIP Performance Manager Registry Keys: - Expand HKEY_LOCAL_MACHINE - Expand SOFTWARE - Expand IntegratedResearch - Expand PROGNOSIS

Under this PROGNOSIS sub key is a list of all VoIP Performance Manager installations on this system. If you only have one installation then you would probably only have the version key and the name of your service, which in this example is EMC Smarts VoIP Performance Manager.

Click on the EMC Smarts VoIP Performance Manager folder and verify that the Working_Dir value corresponds to the VoIP Performance Manager installation you wish to uninstall.

If this is not the case then click on each of the sub keys under HKEY_LOCAL_MACHINE\Software\IntegratedResearch\PROGNOSIS until you find a corresponding Working_Dir.


of 204

Once you have found the key then delete the entire sub key contents:

i.e. HKEY_LOCAL_MACHINE\Software\Integrated Research\PROGNOSIS \EMC Smarts VoIP Performance Manager

Also delete the version sub key (It does not matter if there are still other versions, nothing uses this sub key).

i.e. HKEY_LOCAL_MACHINE\Software\IntegratedResearch\PROGNOSIS\2.0.2

Finally if no sub keys are left in the HKEY_LOCAL_MACHINE\Software\Integrated Research\PROGNOSIS path, then delete the entire HKEY_LOCAL_MACHINE\Software\IntegratedResearch key.

Step 4 InstallShield Registry Keys Following a similar pattern to the previous instructions, also delete the following sub keys:

App Paths: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion \App Paths\EMC Smarts VoIP Performance Manager

Uninstall: (This entry depicts what you see in Add/Remove Programs applet) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{2B10CE30-4318-11D0-86A0-00C0F00326XX}

Where XX is generated at install time. You may have to scroll through a list of {2B10…326XX} entries to find the one that corresponds to the product you are uninstalling. You can match this uninstall key to your installation by checking either the:

LogFile, which should contain C:\Program Files\EMC Smarts VoIP Performance Manager\setup.ilg,

or,

ServiceName value, which should contain the name EMC Smarts VoIP Performance Manager.


of 204

Step 5 Shared DLLs: (Note: Read this step CAREFULLY before action!) The EMC Smarts VoIP Performance Manager server installs only one shared file ‘irswinv.dll’. Even if multiple copies of VoIP Performance Manager are installed, only one copy of the irswinv.dll will exist. It will only be when the last copy of VoIP Performance Manager is removed that the irswinv.dll file will be automatically uninstalled. As you are uninstalling a copy of VoIP Performance Manager, you will need to decrement the shared counter value. This shared counter is kept in the registry under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls\

Double-click on the value “C:\WINDOWS\System32\irswinv.dll” and decrement its value.

If the decremented value is now 0, then it is safe to delete the following line: “C:\WINDOWS\System32\irswinv.dll” (Just this line not the entire key !)


of 204

Step 6 In addition, if the decremented value of “C:\WINDOWS\System32\irswinv.dll” is 0, then go to the following folder;

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\

Double-click on “AppInit_DLLs”, then remove the irswinv.dll entry.

NOTE: Remove only the irswinv.dll entry leaving the AppInit_DLLs key defined even if it is empty!


of 204

Step 7 Shared Files There is only one shared file, ‘irswinv.dll’ which is installed into the following folder path:

..\Program Files\Windows\system32

Try to delete it if you can, but if it is locked, you will need to reboot before being able to remove it.

NOTE: You can only remove irswinv.dll if the counter for this shared dll has been deleted and the AppInit_Dll’s no longer references this file. See steps 5 and 6.

Step 8 Start Menu Right Click on your Start menu and click Explore All Users. Expand the Documents and Settings folder. Locate the Start Menu folder that corresponds to your installation. This should be the same name as the name of value found in your service.ini file.

Delete this folder to remove this item from your Start Menu.

Step 9 EMC Smarts VoIP Performance Manager Files Finally, you need to remove all the files installed by VoIP Performance Manager onto your system. Please note that all Displays and HTML Published documents will be removed so back them up if you wish to retain a copy of these documents.

Once you have backed up everything, simply delete the EMC Smarts VoIP Performance Manager folder and your system will be clean of the


of 204

Manual Uninstall of CopSSH The procedure to manually uninstall CopSSH is dependent on any previous attempts to uninstall EMC Smarts VoIP Performance Manager. In order to undertake this uninstall procedure it is necessary to be logged in as either a local Administrator or a member of an administrative group.

The unistallation options are shown in the following two scenarios.

Scenario 1 - EMC Smarts VoIP Performance Manager uninstallation has not been attempted

Follow these steps if you have not attempted to uninstall VoIP Performance Manager. The CopSSH installation should be intact.

Step 1 De-activate the PrognosisCDR user account:

cd <VoIPPM_Install_Home>\3rdparty\CopSSH\bin bash.exe --login -c "ir-noninteractive-deactivate-user.sh PrognosisCDR"

Step 2 Uninstall CopSSH

cd <VoIPPM_Install_Home>\3rdparty\CopSSH uninstall.exe

Step 3 The CopSSH uninstallation leaves some files behind which will need to be removed manually.

(a) Check that the "copSSHD" NT service has been removed by either opening the Services control panel, or use the command line interface to the Service Control:

sc query copSSHD

The service can be deleted with the command:

sc delete copSSHD

(b) Clean up the Windows Registry. Remove the following keys in the undermentioned Registry node: My Computer\HKEY_LOCAL_MACHINE SOFTWARE\\Cygnus Solutions SOFTWARE\Itefix SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\COPSSH SYSTEM\\CurrentControlSet\\Services\\copSSHD

(c) Remove the Start Menu item. If COPSSH was installed manually then the Start Menu item will be present, otherwise it will be absent. To do this check the location of the shortcut by viewing the value of the registry "Programs" under Registry key: HKCU->Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folders


of 204

This will provide details of where the shortcut "COPSSH" is present. If the "COPSSH" directory exists, then delete it.

(d) Delete the environment variable "CYGWIN" from the system.

(e) Remove the directory <Install_Home>\3rdparty\CopSSH if it is still present;

(f) Remove the following local user accounts: - PrognosisCDR - sshd - SvcCOPSSH To do this the net command can be used, for example:

netuser sshd /delete

(g) Remove local user profile: "Documents and Settings\SvcCOPSSH".

Scenario 2 - EMC Smarts VoIP Performance Manager uninstallation was attempted but failed

In this situation the VoIP Performance Manager uninstallation was attempted but failed to uninstall CopSSH. It is possible the CopSSH installation may be corrupted by this partial uninstallation.

The procedure for uninstalling is to follow step 3 from the previous section, i.e. omit the first two steps and proceed with the instructions in the third step.

It is possible that some directories and files under the COPSSH installation directory are owned by either the SvcCOPSSH or PrognosisCDR user and cannot be deleted. You will need to change the owner of the files under COPSSH to your login name. This can be done by opening the "Properties" applet for the highlighted directory, then select the "Security" tab and choose "Owner". On some machines the effect of this change may not be apparent straight away. Restarting Windows Explorer or rebooting the machine may be required.

Technical Support

of 204

Technical Support


of 204

Support Procedures This section provides information on the procedures to be taken if a problem is encountered with your EMC Smarts VoIP Performance Manager installation. Contact details are provided along with instructions on how to generate a document called IRFAX which may be required by EMC Technical Support staff in order to analyze your problem and provide a resolution.

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:

http://Powerlink.EMC.com

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.

Technical Support

of 204

IRFAX Should you encounter problems with your EMC Smarts VoIP Performance Manager installation, EMC Technical Support staff may ask you to create an IRFAX document and send it via email for analysis. The following information explains how to create an IRFAX.

Issuing an IRFAX from the Windows Operating System The quickest method to create an IRFAX, or if you are unable to log on to the VoIP Performance Manager GUI, is to generate it from the Windows operating system by using the following procedure.

Step 1 Go to the EMC Smarts VoIP Performance Manager\Server\Configuration folder path.

Step 2 Double-click on IRFAX.bat.

The document IRFAX.txt will be created in the same directory with all the required information for your environment.

Step 3 Email the IRFAX document to your EMC Technical Support Center.

Issuing an IRFAX from the GUI If you prefer, and if you can log on to your VoIP Performance Manager GUI, the IRFAX can be generated from the EMC Smarts Error Log Display by using the following procedure.

Step 1 Log on to the GUI and have the Welcome to EMC Smarts VoIP Performance Manager Display open

Step 2 Click on the Cisco UCM 3.3 & 4 Link in the Monitor window.

Step 3 The All Clusters Central Display will open. Click on the required node name in the All Server Central window.

Step 4 The Server Central Display will open. Click on the EMC Smarts Status link.

Step 5 On the next Display double-click on the EMC Smarts Error Log link which will open the Error Log Display.

Step 6 From the Error Log Display click on the Generate an IRFax link.

Step 7 After a few moments the User Command Output Window will open showing the status of your IRFAX. When completed the IRFAX document will be placed in the EMC Smarts VoIP Performance Manager\ Server\Configuration folder path.

Step 8 Email the IRFAX document to your EMC Technical Support Center.

Index

of 204

Index

A

About ................................................................ 6

Add ............................................................... 155

NORTEL_PBX Collector ......................... 155 Add Clusters ................................................. 115

Advanced Configuration............................... 137

Alerts .............................................................. 97

Starting........................................................ 97 Architectual Overview.................................... 12

Avaya.................................................. 74, 87, 94

Configuration .............................................. 74 Avaya Login Account..................................... 89

Create .......................................................... 89 AVAYA_DEFINITY Configuration .............. 80

AVAYA_LEGACY Configuration ................ 81

AVAYA_LSP Configuration.......................... 82

AVAYA_PBX Configuration......................... 75

B

Backup Instructions ...................................... 177

Before ............................................................. 10

C

CallManager Service Activation................... 123

CDR Cluster Name ....................................... 128

Setting ....................................................... 128 CDR Disk Space ........................................... 135

CDR Retrieval............................................... 144

Secure FTP address ................................... 144 CDRs....................................................... 94, 130

Enabling .............................................. 94, 130 Changing....................................................... 112

Cluster Names ........................................... 112 Cisco Administration Console Setup ............ 122


of 204

Cisco Off Cluster CDRs ............................... 147

Cisco Unity Integration................................. 145

Client ............................................................ 165

Client Component Requirements.................... 15

Client Only ..................................................... 57

Installing ..................................................... 57 Cluster Names............................................... 112

Changing ................................................... 112 Cluster Static Configuration ......................... 138

CMA-PASSWORDS Configuration............. 119

Colors ............................................................. 16

Command Line ............................................. 171

Configuration...........................74, 101, 114, 149

Avaya .......................................................... 74 CUCM....................................................... 114 CUCM 3.3................................................. 101 Nortel ........................................................ 149

Configuration Procedures ............................... 70

Configure...................................................... 152

Nortel PBX................................................ 152 Configure Avaya............................................. 92

Send RTCP Data ......................................... 92 CopSSH ........................................................ 193

Manual Uninstall....................................... 193 Create.............................................................. 89

Avaya Login Account ................................. 89 CUCM ....25, 103, 105, 110, 112, 114, 115, 130,

137, 138, 142, 144

Configuration ............................................ 114 CUCM 3.3 .......................25, 27, 29, 33, 35, 101

Configuration ............................................ 101 CUCM4 ........................................................ 108

PASSWORDS Configuration ................... 108

D

Databases ................................................ 97, 160

Dedicated Server Components........................ 14

DEFINE CDR................................................. 77

DEFINE SAT_PROFILE................................ 79

Deployment Procedures .................................. 22

Documentation Conventions............................. 8

DOES happen on Upgrade............................ 176

DOES NOT happen on Upgrade................... 176

E

Enabling.......................................... 94, 130, 132

CDRs................................................... 94, 130 Valid Namespaces ..................................... 132

G

GUI ....................................................... 165, 172

Guide................................................................. 6

H

HTTPS Web Interface Protocol ...................... 65

I IClient ........................................................... 172

Installation Procedures.................................... 38

Installing ................................................... 41, 57

Client Only .................................................. 57 Server Component....................................... 41

Introduction....................................................... 5

IRFAX .......................................................... 197

L

Logging........................................................... 71

On................................................................ 71 M

Managing Server................................... 103, 110

Index

of 204

Manual Start ................................................. 181

Manual Uninstall .................................. 187, 193

CopSSH..................................................... 193 Method...................................169, 170, 171, 172

Monitoring................................................ 33, 35

Unity ..................................................... 33, 35 Multi Vendor Network ............................. 27, 29

Multiple Monitoring Servers .................. 31, 164

N

NAT Static Configuration............................. 142

NETWORK Configuration................... 103, 105

NODEGROUP Configuration ...................... 110

Nodes............................................................ 115

Nortel.............................................. 63, 149, 159

Configuration ............................................ 149 PASSWORDS Configuration ................... 159

Nortel PBX ................................................... 152

Configure .................................................. 152 NORTEL_PBX Collector ............................. 155

Add............................................................ 155 NORTEL_PBX Configuration ............. 156, 162

Update ....................................................... 156 O

On

Logging ....................................................... 71 P

PASSWORDS Configuration......... 87, 108, 159

CUCM4..................................................... 108 Nortel ........................................................ 159

Patch Installation .................................... 63, 179

Prerequisites.................................................... 39

Procedure...................................................... 175

Publisher ....................................................... 105

R

Recommended PBX Settings.......................... 96

Resolution ....................................................... 16

RollBack Instructions.................................... 178

RTCP_MONITOR Configuration................... 85

S

SAT Performance Profiles .............................. 99

Screen Size...................................................... 16

Secure FTP address....................................... 144

CDR Retrieval ........................................... 144 Send RTCP Data............................................. 92

Configure Avaya ......................................... 92 Server Component .......................................... 41

Installing...................................................... 41 Service .......................................................... 168

Stopping .................................................... 168 Service Control Panel ................................... 169

Setting ................................................... 125, 128

CDR Cluster Name.................................... 128 SNMP Community String ......................... 125

Single Vendor Network ............................ 23, 25

SNMP Community String............................. 125

Setting ....................................................... 125 Starting...................................................... 10, 97

Alerts ........................................................... 97 Stopping........................................................ 168

Service....................................................... 168 Support Procedures ....................................... 196

Supported Platforms ....................................... 18

T

Thresholds..................................................... 160


of 204

Time Synchronization..................................... 17

U

Uninstalling .................................................. 183

Unity ......................................................... 33, 35

Monitoring ............................................ 33, 35 Update........................................................... 156

NORTEL_PBX Configuration.................. 156

Upgrade Installation...................................... 173

Using Windows Control Panel...................... 184

V

Valid Namespaces......................................... 132

Enabling .................................................... 132 W

Windows Services Control Panel.................. 170

of 204