Installation Guide for IP Communications Operations Manager
Downloads: This chapterpdf (PDF - 162.0 KB) The complete bookPDF (PDF - 0.97 MB) | Feedback


Table Of Contents


Product Overview

Server Requirements

Client Requirements

Supported Devices


This chapter describes the prerequisites for installing IP Communications Operations Manager (with IP Communications Service Monitor) on a Windows system. It includes:

Product Overview

Server Requirements

Client Requirements

Supported Devices

Product Overview

IP Communications Operations Manager (Operations Manager) monitors and evaluates the current status of both the IP communications infrastructure and the underlying transport infrastructure in the network. Operations Manager uses open interfaces such as Simple Network Management Protocol (SNMP) and Hypertext Transfer Protocol (HTTP) to remotely poll data from different devices in the IP communications deployment.

Note Operations Manager does not deploy any agent software on the devices being monitored and thus is nondisruptive to system operations.

Operations Manager increases productivity of network managers, enabling them to isolate problems more quickly using:

Contextual diagnostic tools:

Diagnostic tests provide performance and connectivity details about different elements of the converged IP communications infrastructure.

Synthetic tests replicate end-user activity and verify gateway availability and other configuration and operational aspects of the IP communications infrastructure.

IP service-level agreement (SLA)-based diagnostic tests can measure the performance of WAN links and node-to-node network quality.

Clickable information in notification messages—Includes context-sensitive links to more detailed information about service outages.

Context-sensitive links to other CiscoWorks tools and Cisco tools—For managing IP communications implementations.

Operations Manager also does the following:

Presents service-quality alerts—Uses information from CiscoWorks IP Communications Service Monitor 1.0, when it is also deployed, to:

Display mean opinion scores (MOSs) associated with poor voice quality between pairs of endpoints (Cisco IP Phones, Cisco Unity messaging systems, or voice gateways) involved in a call and other associated details about the voice-quality problem.

Enable you to perform a probable path trace between the two endpoints and reports on any outages or problems on intermediate nodes in the path.

Highlights current connectivity-related and registration-related outages affecting Cisco IP Phones in the network—In addition, provides contextual information that enables locating and identifying the IP phones involved.

Tracks IP communications devices and IP phone inventory—Tracks Cisco IP Phone status changes and creates a variety of reports that document move, add, and change operations on Cisco IP Phones in the network.

Provides real-time notifications—Uses SNMP traps, syslog notifications, and e-mail to report the status of the network being monitored to a higher-level entity (typically, to a manager of managers).

Server Requirements

Table 1-1 lists the minimum server system requirements for installing Operations Manager.

Table 1-1 Server System Requirements 

Requirement Type
Minimum Requirements

System Hardware

IBM PC-compatible computer with one of the following:

Small deployments (fewer than 1,000 phones)—2.0-GHz Intel processor, 2 GB RAM, 60-GB hard disk drive.

Medium deployments (1000 to 10,000 phones)—3.0-GHz Intel processor, 4 GB RAM, 60-GB hard disk drive.

Large deployments (over 10,000 phones)—Dual 3.0-GHz Intel processors, 4 GB RAM, 60-GB hard disk drive.

Color monitor.

CD-ROM drive.

Support one or two 10/100 NICs (one required, one for failover support).

Memory (RAM)

One of the following:

2 GB—Minimum for small deployment.

4 GB—Minimum for medium deployment.

4 GB—Minimum for large deployment.

Available Drive Space1

60 GB hard disk space.

Virtual memory equal to double the amount of memory (RAM). For example, if your system has 2 GB of RAM, you need 4 GB of virtual memory.

NTFS file system (required for secure operation).

At least 16 MB in Windows temporary directory (%TEMP%).

System Software2 , 3

ODBC Driver Manager4 3.5.10 or later.

Windows Server 2003 with Service Pack 1, Standard and Enterprise Editions.

Note Windows Terminal Services is supported in remote administration mode only.

1 Do not install Operations Manager on a FAT file system.

2 You must install Operations Manager on a dedicated system. Do not install Operations Manager on a Primary Domain Controller (PDC) or Backup Domain Controller (BDC). Do not install Operations Manager in an encrypted directory. CiscoWorks does not support directory encryption.

3 The default locale for your Windows operating system must be set to either US-English or Japanese.

4 To verify the version of ODBC Driver Manager, from the Windows desktop, select Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). Select the About tab. If necessary, install Microsoft Data Access Component (MDAC) 2.5 or later.

Client Requirements

Table 1-2 shows the minimum system requirements for CiscoWorks clients.

Table 1-2 Client System Requirements 

Requirement Type
Minimum Requirements

System hardware and software

IBM PC-compatible system with one 1.0-GHz processor running one of the following:

Windows XP with Service Pack 2.

Windows Server 2003 Standard or Enterprise Edition without Windows Terminal Services.

Color monitor with video card set to 24 bits color depth.

Screen resolution of 1024 x 768 dpi.

Note Not every LCD projector or monitor provides a clear display at the minimum resolution. On LCD projectors and monitors, dot pitch impacts the readability of the screen.

Memory (RAM)

512 MB memory (RAM) (1 GB recommended).

Additional Software

Internet Explorer 6.0.28 or 6.0.37.

Adobe Macromedia Flash Player 8.0 or higher.


Clients must be able to access Operations Manager:

From outside a firewall—Refer to documentation for your firewall for how to configure client access.

Across a Virtual Private Network (VPN)—The VPN tunnel should connect the client and a VPN router or similar device.

Supported Devices

Device adapter packages for all supported devices are installed when you install Operations Manager. Information about devices installed with Operations Manager can be found on

As additional device adapter packages become available, you can download the IDUs that contain them, by logging into