Installation Guide for Cisco Unified Service Monitor 2.3
Prerequisites
Downloads: This chapterpdf (PDF - 172.0KB) The complete bookPDF (PDF - 1.03MB) | Feedback

Prerequisites

Table Of Contents

Prerequisites

Product Overview

Server and Client System Requirements

Server Requirements

Client Requirements

VMware Guidelines

Terminal Server Support for Windows 2003 Server

Enabling and Disabling Terminal Services on Windows 2003 Server

Enabling and Disabling FIPS on Windows 2003 Server

Port Usage


Prerequisites


Product Overview

Server and Client System Requirements

Terminal Server Support for Windows 2003 Server

Port Usage

Product Overview

Cisco Unified Service Monitor (Service Monitor), a product from the Cisco Unified Communications Management Suite, receives and analyzes data from these sources when they are installed in your voice network and configured properly:

Cisco Unified Communications Manager (Unified Communications Manager) clusters—Retain Call Detail Records (CDRs) and Call Management Records (CMRs). CDRs include Mean Opinion Score (MOS) values that were calculated on IP phones and voice gateways using the Cisco Voice Transmission Quality (CVTQ) algorithm.

For Unified Communications Manager versions that Service Monitor supports, see Cisco Unified Service Monitor 2.3 Compatibility Matrix. For information about configuring Unified Communications Manager clusters to work with Service Monitor, see User Guide for Cisco Unified Service Monitor.

Sensors—Network Analysis Modules (NAMs) and Cisco 1040 Sensors (Cisco 1040s)—Compute MOS for each RTP stream. Service Monitor obtains data from sensors every 60 seconds.

Service Monitor compares MOS against a threshold value—default or user-specified—for the codec in use. When MOS drops below the threshold, Service Monitor generates SNMP traps and sends them to up to four recipients. Service Monitor stores the data that it obtains in the database, where it is available for display on Service Monitor reports. Service Monitor purges the database daily to maintain a configurable number of days of data. (For more information, see online help.)

If you configure Cisco Unified Operations Manager (Operations Manager) as a trap receiver for Service Monitor, Operations Manager can further analyze, display, and act on the traps that Service Monitor generates. Operations Manager can generate service quality events, display and track these events on a real-time dashboard, and display and store event history. You can configure additional event settings on Operations Manager to alert you if MOS drops below a threshold or if too many (configurable number) service quality events occur during a period of time (configurable number of minutes). In addition, you can configure Operations Manager to send notifications by e-mail, SNMP trap, and syslog message.

Server and Client System Requirements

Server Requirements

Client Requirements

VMware Guidelines

Server Requirements


NoteFor Service Monitor to coreside on a system with other applications in the Cisco Unified Communications Manager System, see the coresidence requirements in Installation Guide for Cisco Unified Operations Manager 2.3.

Service Monitor supports VMware for virtualization. For more information, see VMware Guidelines.


Table 1-1 lists minimum server requirements for installing Service Monitor alone for different levels of scale.

Table 1-1 Minimum Server Requirements 

Component
Minimum Requirement for Deployment with an Incoming Per-Minute Data Rate of up to...
1200 CDRs or
5000 NAM/1040 Streams or
666 CDRs and 1500 NAM/1040 Streams
1600 CDRs

Processor1

Two dual-core Xeon processors, 2.33 GHz or greater (for a total of four cores)

Two quad-core Xeon processors, 2.33 GHz or greater (for a total of eight cores)

Available memory (RAM)

4 GB

Hardware

Color monitor with video card capable of 256 colors or more

CD-ROM drive—Required if the order that you placed could not be filled using the eDelivery system

1 or 2 1 GB NICs—One is required, and the second is for failover support; both NIC cards must have the same IP address.

SAS hard disk drives

Note The Cisco MCS 7845-H2, MCS 7845-I2, and MCS 7845-I2-ECS3 (which has 8 cores) meet these specifications. These products come with 4 Serial Attached SCSI (SAS) hard drives configured using RAID1+0. For ordering information, see Cisco.com.

Software for Windows2 ,3

One of these:

Windows Server 2003 Service Pack 2, Standard or Enterprise edition

Windows Server 2003 R2 Service Pack 2, Standard or Enterprise edition

Note NTP-Configure the server to use Network Time Protocol (NTP) to synchronize with the time server that is used by Unified Communications Managers in your network. See NTP Configuration Notes, page 2-3.

Available disk space

70 GB minimum—SAS disks are required

Note Of this 70 GB, 26 GB is allocated to the qovr database

Virtual memory: 8 GB

NTFS file system4

Cisco Secure ACS (Optional)

Cisco Secure ACS 4.2

1 Processor can be Intel Xeon or AMD Opteron.

2 The system that you use for your Service Monitor server should meet all the security guidelines that Microsoft recommends for Windows 2003 Server. See the Microsoft website for security guidance:
http://www.microsoft.com/technet/security/prodtech/WindowsServer2003.mspx
(This website is Copyright © 2010, Microsoft Corporation.)

3 Windows Terminal Services is supported in remote administration mode only.Use of Windows Terminal Services or Remote Desktop and Virtual Network Computing (VNC) to remotely perform administrative tasks on the server is not recommended for performing day-to-day operations (such as running reports).For more information, see Terminal Server Support for Windows 2003 Server

4 Do not install Service Monitor on a FAT file system. To verify the file system, open My Computer on the Windows desktop, right-click the drive and select Properties from the popup menu. The file system field appears in the General tab of the Properties dialog box.


Client Requirements

Table 1-2 lists minimum client requirements for Service Monitor.

Table 1-2 Minimum Client Hardware and Software Requirements 

Component
Minimum Requirement

Hardware/software

Color monitor with video card set to 256 colors

Any PC or server platform with a Pentium IV processor, 1.0 GHz or greater, running one of the following:

Windows XP Professional Service Pack 2

Windows 2003 Server (Standard and Enterprise Editions) without Windows Terminal Services

Internet Explorer 6.0.28, 6.0.37, or 7.0

Note We strongly recommend that you use a browser from a client system to perform day-to-day operations (for example, running reports). Use of Windows Terminal Services, Remote Desktop, or VNC to perform day-to-day operations is not recommended.

Available disk space

1 GB virtual memory

Available memory (RAM)

512 MB minimum

We recommend that you set virtual memory to twice the size of RAM.



NoteIf your browser is configured to use a proxy server for your LAN, Service Monitor cannot open some report windows. Disable proxy server settings in Internet Options. (From the Connections tab, click LAN Settings.)

When using Service Monitor, disable any software on your desktop that you use to prevent popup windows from displaying. Service Monitor must be able to open multiple windows to display information.


VMware Guidelines

Service Monitor supports VMware ESX 3.5 and ESXi 4.x. Service Monitor must have the same system resources available to it inside the virtualization environment that it has for a standard (nonvirtual) installation. When determining the performance of Service Monitor in your virtual setup, you must take into account that the VMware instance will use some system resources that would normally be available to Service Monitor in a standard installation. Additional requirements for running Service Monitor in a virtualization environment might vary with your environment and system load. For more information, see Best Practices for Cisco Unified Communication Suite on Virtualization under this URL:

http://www.cisco.com/en/US/products/ps6535/prod_white_papers_list.html

The following configurations are supported for Service Monitor in a virtual environment:

An instance of Service Monitor, supporting up to 45,000 phones

Each of these products installed on a separate virtual machine:

Operations Manager

Service Monitor

Service Statistics Manager

Provisioning Manager

with each supporting up to 10,000 phones and 1,000 IP devices. (Running one instance of an application in one virtual machine is the only supported configuration.)


Note For more information, see Best Practices for Cisco Unified Communication Suite on Virtualization under this URL: http://www.cisco.com/en/US/products/ps6535/prod_white_papers_list.html.


When setting up Service Monitor in a VMware environment, keep in mind the following guidelines:

Resources must be reserved at 100% of requirements for the virtual machine.

To use a licensed Service Monitor in a VMware environment, you must configure your virtual machine with a static MAC address.


Note You can run Service Monitor in Evaluation mode with a dynamic MAC address. However, before you can run a licensed copy of Service Monitor, you must configure a static MAC address.


To set up a static MAC address, do the following:


Step 1 Power down the virtual machine.

Step 2 In the Inventory panel, select the virtual machine.

Step 3 Click the Summary tab and then click Edit Settings.

Step 4 In the Hardware list, select Network Adapter.

Step 5 For MAC address, select Manual.

Step 6 Change the current MAC address of the virtual machine to a static MAC address in the following range: 00:50:56:00:00:00 to 00:50:56:3F:FF:FF.

When assigning a static MAC address, we recommend choosing a complex address. An example of a complex MAC address is 00:50:56:01:3B:9F. A less complex MAC address is 00:50:56:11:11:11, because of the repeating ones (1).


Note Choosing a complex address makes it less likely that you will choose an address being used by another customer. This can prevent accidental licensing overlap between different customers.


Step 7 Click OK.


Terminal Server Support for Windows 2003 Server

You can install Service Monitor on a system with Terminal Services enabled in Remote Administration mode. However, you cannot install Service Monitor on a system with Terminal Services enabled in Application mode.

If you have enabled Terminal Services in Application mode, you should disable the Terminal Server, reboot the system, and start the installation again.

Table 1-3 summarizes the Terminal Services features in Windows 2003 Server.

.

Table 1-3 Terminal Services on Windows 2003 Server

Windows 2003 Server
Features

Terminal Server

Remote access and virtual system. Each client has its own virtual OS environment.

Remote Desktop Administration

Remote access only. All clients use the same (and the only) operating system.

Note Do not use terminal services to perform day to day tasks in Cisco Unified Management Communications Suite applications, such as viewing the Service Level View in Operations Manager or viewing reports in Service Monitor.


Enabling and Disabling Terminal Services on Windows 2003 Server

To enable/ disable Terminal Server, go to Manage Your Server > Add or Remove a Role > Terminal Server.

To enable/ disable Remote Desktop Administration, go to Control Panel > System > Remote.

Enabling and Disabling FIPS on Windows 2003 Server

Sometimes, Federal Information Processing Standard (FIPS) compliant encryption algorithms are enabled for Group security policy on Windows server.

When the FIPS compliance is turned on, the SSL authentication may fail on the Service Monitor server. You should disable the FIPS compliance for the Service Monitor to work properly.

To enable/disable FIPS on Windows 2003 server:


Step 1 Go to Start > Settings > Control Panel > Administrative tools > Local Security Policy.

The Local Security Policy window appears.

Step 2 Click Local Polices > Security Options.

Step 3 Select System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.

Step 4 Right-click the selected policy and click Properties.

Step 5 Select Enabled or Disabled to enable or disable FIPS compliant algorithms.

Step 6 Click Apply.

You must reboot the server for the changes to take effect.


Port Usage

Before you install Service Monitor, ensure that the ports listed in Table 1-4 and Table 1-5 are free.


Note The ports in Table 1-4 and Table 1-5 should not be scanned.


Table 1-4 lists the ports that Service Monitor uses. Common Services is installed with Service Monitor. Table 1-5 lists the ports that Common Services uses.

Table 1-4 Service Monitor Port Usage 

Protocol
Port Number
Service Name

TCP

22

SFTP—Service Monitor uses SFTP to obtain data from Unified Communications Manager versions 5.x and later.

UDP

53

DNS.

UDP

67 and 68

DHCP.

TCP

2000

SCCP—Service Monitor uses SCCP to communicate with Cisco 1040s.

TCP

43459

Database.

UDP

5666

Syslog—Service Monitor receives syslog messages from Cisco 1040s.

TCP

5665-5680

Interprocess communication between the user interface and back-end processes.

These ports must be free.



Note Service Monitor uses TFTP to find the configuration file for a given Cisco 1040. Service Monitor by default uses port 69 on the TFTP servers.


Common Services is also installed on the Service Monitor system. Table 1-5 lists the ports used by Common Services.

Table 1-5 Common Services Port Usage 

Protocol
Port Number
Service Name

TCP

23

Telnet

TCP

25

Simple Mail Transfer Protocol (SMTP)

TCP

49

TACACS+ and ACS

UDP

69

Trivial File Transfer Protocol (TFTP)

UDP

161

Simple Network Management Protocol (SNMP)

TCP

443

Common Services HTTP server in SSL mode

If IIS is on your system, even when IIS is disabled, you will be asked if you want to select an HTTPS port other than 443 during installation or upgrade. To avoid port conflict, you should select another port.

TCP

514

Remote Copy Protocol

UDP

514

Syslog

UDP

1431

Trap Listener to MAC Notification Traps

TCP

1741

Common Services HTTP Protocol

2002

Communicate with Cisco Secure ACS server when AAA mode is ACS

TCP

8898

Log Server

TCP

9007

Tomcat shutdown

TCP

9009

Ajp13 connector used by Tomcat

TCP

15000

Log server

UDP

16236

UT Host acquisition

TCP

40050-
40070

CSTM ports used by Common Services applications, such as Device and
Credential Repository (DCR)

Note Service Monitor does not support DCR.

TCP

40401

LicenseServer

TCP

42340

Daemon Manager - Tool for Server Processes

UDP

42342

OSAGENT

TCP

42344

ANI HTTP Server

UDP

42350

Event Services Software (ESS)
(Alternate port is 44350/udp)

TCP

42351

Event Services Software (ESS) Listening
(Alternate port is 44351/tcp)

TCP

42352

ESS HTTP
(Alternate port is 44352/tcp)

TCP

42353

ESS Routing
(Alternate port is 44352/tcp)

TCP

43441

CMF Database

TCP

50001

SOAPMonitor