Cisco Cisco Unified Provisioning Manager 8.5 White Paper

Page 35 of 71

To upgrade from UPM 1.3.1 to 8.6, users must upgrade from 1.3.1 to 2.0 first, then upgrade to 2.1 and then from

2.1 to 8.6. Users must have a 2.x image license and must have all of the old 1.3.1 licenses to convert. Users must

also have B upgrade licenses as required to recover the old 1.3.1 phone license counts to use in UPM 2.x - the

1.3.1 plus B upgrade licenses are used to get entitlement out of the old 1.3.1 licenses. Users can purchase more

B add-on licenses to increase support.

All MAC addresses in the licenses must match the server MAC addresses.

During fresh installations of Cisco Unified Provisioning Manager 8.6, users should select the image (K9) license

file when prompted. Add-on license files must be copied to <install dir>/license when the install completes.

During upgrades from 1.3.1 to 2.0 (to get to 2.1), old 1.3.1 licenses, image licenses, and upgrade licenses should

be put in a temporary directory, which UPM will ask for during installation. The installer will display license

entitlement based on licenses in the temporary directory. UPM will then copy all licenses into the license directory.

Total phone licenses are calculated as follows:

2.x image license must be present + new add-on phone licenses + ((1.x base licenses + total 1.x add-on licenses)

∩

total 2.x add-on upgrade licenses) = total phone licenses.

At least one image license must be present. Feature counts within the image licenses are cumulative. These may

be phones, call processors, and message processors.

A “B” in the license PID means this license is good for the 2.x family of releases.

Basic Task Flow

●

Set up devices

◦

Add call processors (Cisco Unified Communications Manager publishers only, when using Cisco Unified

Communications Manager clusters) and message processors to Cisco Unified Provisioning Manager as

devices with capabilities assigned

◦

Configure call processors and message processors

◦

Perform infrastructure synchronization

◦

Perform subscriber synchronization

●

Set up domain deployment

◦

Create domains and assign call processors and message processors

◦

Create service areas

◦

Configure rules

◦

Perform domain synchronization

◦

For preexisting call processors and message processors, verify that subscribers get created

●

Provision network

◦

Create and push templates to configure Cisco Unified Communications Manager

◦

Or sync current provisioning configurations from existing deployment

●

Set up deployment

◦

Create new service areas, as needed, for each domain, typically one per class of service

◦

Assign subscriber types to each service area