Installation Guide for Cisco Unified Provisioning Manager
Prerequisites
Download this chapter
PrerequisitesPrerequisites
Download the complete book
Installation Guide for Cisco Unified Provisioning ManagerInstallation Guide for Cisco Unified Provisioning Manager (PDF - 750 KB)
give_us_feedback

Table Of Contents

Prerequisites

Product Overview

New Features in Cisco Unified Provisioning Manager 1.2

Server Requirements

Client Requirements

Additional Server Software


Prerequisites

This chapter describes the prerequisites for installing Cisco Unified Provisioning Manager on a Windows system. It includes:

•Product Overview

•New Features in Cisco Unified Provisioning Manager 1.2

•Server Requirements

•Client Requirements

•Additional Server Software

Product Overview

Cisco Unified Provisioning Manager (Provisioning Manager) provides a scalable web-based solution to manage a company's next-generation communication services. Provisioning Manager manages IP communication services in an integrated IP telephony, voicemail, and unified messaging environment that includes Cisco Unified Communications Manager, Cisco Unified Communications Manager Express, Cisco Unity, Cisco Unity Express, and Cisco Unity Connection systems.

Provisioning Manager is a product from the Cisco Unified Communications Management Suite. It provides provisioning for Cisco Unified Communications initial deployments and implementations, and then remains deployed to provide ongoing operational provisioning and activation services for individual subscriber changes. Provisioning Manager provides a single, consolidated view of subscribers across the organization. It provides a set of business-level management abstractions, which are policy-driven through the use of automation, for managing subscriber services across the Cisco Unified Communications infrastructure.

A template capability permits defining standard configurations that can be reused for new sites or location deployments. Batch provisioning permits the rollout of large numbers of subscribers at the same time.

Administrators can configure policy at various levels to determine who can do delegated management, for whom that delegation applies, and how business-level services apply to Cisco Unified Communications voice and messaging applications and which types of end users (subscribers) are permitted to order which standard services. Through the use of this policy and standard configuration approach, provisioning and activating subscriber services is greatly simplified, while retaining the overall ability to manage and provide services that make use of the underlying Cisco Unified Communications applications.

New Features in Cisco Unified Provisioning Manager 1.2

Cisco Unified Provisioning Manager adds the following:

•Support for Cisco Unified Communications Manager 6.1.

•Support for Cisco Unified Communications Manager Express 4.2.

•Support for Cisco Unity Connection 2.1.

•Support for Cisco Unity Express 3.1.

•Line Group as a provisioning attribute on a line.

•The ability to change the attributes of a Line.

•Support for the Cisco Unified Communications Manager Auto-Register Phone Tool in Cisco Unified Communications Manager.

•CTI Route Point as a new configuration template.

•Support for alternate extensions in Cisco Unity voicemail.

Server Requirements

Table 1-1 lists the minimum server system requirements for different levels of performance and scale.

Table 1-1 Server System Requirements 

Requirement Type
Minimum Requirements

System Processor

Server platform with one of the following processor configurations:

•(Up to 1,000 phones) Single Intel Pentium 4, 3.0 GHz.

•(Up to 10,000 phones) Dual-core Intel Pentium 4, 3.0 GHz.

•(Up to 30,000 phones) Two-system deployment, with the following configuration:

–Two Intel Xeon, 3.0 GHz, for the Web and application server.

–Two Intel Xeon, 3.0 GHz, for the database.

Note If you are going to have more than five operators placing concurrent orders,
two dual-core Intel Xeon processors should be used.

Other System Hardware

•Color monitor.

•CD-ROM drive.

•100 Mbps NIC

Memory (RAM)

•2 GB—Up to 1000 phones.

•4 GB—Up to 10,000 phones.

•4 GB on each system—Up to 30,000 phones.

Note Provisioning Manager will not install either the medium (up to 10,000 phones) or the large (up to 30,000 phones) configuration, if Windows 2003 reports that less than 4 GB of memory is installed. There is a known issue with Windows 2003 when working with certain hardware. Even though 4 GB of memory is installed on the system Windows 2003 reports that there is less than 4 GB of memory installed. For more details, see http://msdn2.microsoft.com/en-us/library/ms791485.aspx.

Swap File Space

Same as RAM, with a maximum size of twice that of RAM.

Available Drive Space

Note SAS or SCSI drives in a RAID configuration are recommended for servers supporting 1000 to 10,000 phones. SAS drives in a RAID (1+0) configuration are recommended for servers supporting over 10,000 phones.

•30 GB—Up to 1000 phones.

•60 GB—Up to 10,000 phones.

•Two-system configuration (up to 30,000 phones); requires the following:

–30 GB on the Web and application system.

–80 GB on the database system.

System Software1

Windows Server 2003 with Service Pack 1 or Service Pack 2, Standard or Enterprise Edition.

1 You must install Provisioning Manager on a dedicated system. Do not install Provisioning Manager on a Primary Domain Controller (PDC) or Backup Domain Controller (BDC).


Client Requirements

Table 1-2 lists the minimum client system requirements for installing Provisioning Manager.

Table 1-2 Client System Requirements 

Requirement Type
Minimum Requirements

System Hardware

•Any PC or server platform with a Pentium 4 processor greater than 1.0 GHz.

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

System Software

•One of the following:

–Windows XP with Service Pack 2.

–Windows Server 2003 with Service Pack 1 or Service Pack 2, Standard or Enterprise Edition.

•One of the following

–Internet Explorer 6.0 with Service Pack 2 or 7.0.

–Mozilla 1.7.x.

–Firefox 2.0

Memory (RAM)

1 GB recommended.

Environment

Clients must be able to access Provisioning Manager:

•From outside a firewall—Refer to the documentation for your firewall for information on 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. See Ports that Provisioning Manager Uses, page 2-10.


Additional Server Software

Provisioning Manager has undergone interoperability testing with the following software:

•Cisco Security Agent 5.0

Note Cisco Security Agent must be disabled during installation of Provisioning Manager.

•Third-party virus protection software:

–McAfee Virus Scan Enterprise 8.0

For McAfee Enterprise VirusScan 8.0, you must have patch version 11 installed. Install the McAfee VirusScan Enterprise 8.0 Patch Version 11 before installing Provisioning Manager on the system.

Note You should exclude the following from virus scanning:

•The pgsql folder (if you selected the default location during installation, it is C:\CUPM\pgsql).

•The postmaster.exe file (located in the CUPM\pgsql\bin folder).