Cisco Cisco Unified Provisioning Manager 8.5 Livre blanc
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 28 of 71
●
For each site or location, what classes of services are required?
●
For each site or location, what device pools, phone protocols, voice mail templates, common device
configuration, locations, and partitions are required?
●
For each site or location, which devices will support that location?
◦
These questions will dictate the number of service areas that will be created in Provisioning Manager for
that domain. Service areas point to unique combinations of call processors and message processors
(example: Cisco Unified Communications Manager and Cisco Unity). They also contain policy
information on calling privilege, like calling search spaces within the Cisco Unified Communications
Manager to be used for the service area. Directory number blocks can also be defined in service areas.
●
Is a single Cisco Unified Communications application (example: Cisco Unified Communications Manager)
shared across these groupings of subscribers and locations?
◦
This question will dictate how basic synchronization rules are set within Provisioning Manager. For
example, will Cisco Unified Provisioning Manager need to place subscribers into domains automatically
at synchronization time based on the department code in the Cisco Unified Communications Manager,
or can it put all users it finds into a Cisco Unified Communications Manager single domain?
Best practice
●
It is recommended that the initial deployment of Provisioning Manager focus on defining the correct
domains and service areas, provisioning attributes against these, and the basic rules covered in the
section “Usage by Problem to Be Solved.”
●
Try to avoid flat domain/service area design; for example, having one domain with a thousand or hundreds
of domains with one service area per domain is not good design.
●
Domains can be designed based on delegation needs or geographic location.
●
It is recommended to calculate the service areas needed for each domain beforehand. By default, the
number of service areas needed will be the permutation and combination of six or seven attributes in the
service area setup (class of service, device pool, phone protocols, voice mail templates, common device
configuration, location, partition). If the number of service areas needed for a domain exceeds 100,
consider breaking into two domains for easier manageability and optimal usability.
●
It is easier to create multiple domains and remove some later, consolidating subscribers into fewer
domains, than it is to create a small number of domains and later split subscribers into more domains.
●
Consider the use of subscriber types, advanced rule settings, and other configuration parameters after
these concepts are well understood.
Installing Cisco Unified Provisioning Manager
How to Select Hardware
There are several things to consider in selecting hardware (also see Table 6):
●
Platforms: Cisco Unified Provisioning Manager does not require special Cisco hardware, but it is tested on
various Cisco 7835 (2 GB RAM) and 7845 (4 GB RAM) server platforms. The Cisco Unified
Communications network to be managed is mission critical, so serious consideration should be used in
choosing a platform for management applications. The platform chosen must meet the published
requirements as listed below. The recommendations below are provided as guidelines when you are not
sure how much performance is really needed to provide a good administrator experience.