Cisco Prime Collaboration Deployment

Cisco dCloud
Cisco Prime Collaboration Deployment 11.6 Lab v1

dCloud: The Cisco Demo Cloud
Last Updated: 17-AUGUST-2017
About This Lab

This lab covers the new Cisco Prime Collaboration Deployment (PCD) tool. Participants will go through, in detail, the many
features of this tool. Once the features of PCD are covered in the lab, the participant will complete a migration from an 8.6 cluster
(Unified CM and Presence) to 11.5. The same migration can then be applied to older clusters going back to version 6.
 Requirements
 About This Solution
 Topology
 Session Users
 Get Started
 Scenario: Cisco Prime Collaboration Deployment
 Appendix A: Server Setup
 Appendix B: VMware Configuration
 Appendix C: Deploy and Install PCD
 Appendix D: Reference Materials
Requirements
The table below outlines the requirements for this preconfigured lab.
Table 1. Requirements
Required Optional
● Laptop ● Second laptop
© 2017 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 39
Cisco dCloud
About This Solution

Cisco Prime Collaboration Deployment (PCD) is an application designed to assist in the management of Unified Communication
applications. It allows the user to perform tasks such as migration, of old clusters to new virtual machines, fresh installs, and
upgrades on existing clusters. Cisco Prime Collaboration Deployment has four primary, high-level functions:
 Migrate an existing cluster of Unified Communication (UC) servers to a new cluster (MCS to virtual or virtual to virtual)
 Perform Upgrade, Switch version, and Restart operations on existing clusters (8.6.1 or higher)
 Change IP addresses or hostnames on existing 10.0 or 11.0 clusters
 Fresh install a new Unified Communication clusters
For additional information about Cisco Prime Collaboration Deployment, view the PCD administration guide here.
Topology
This content includes preconfigured users and components to illustrate the scripted scenarios and features of the solution. Most
components are fully configurable with predefined administrative user accounts. You can see the IP address and user account
credentials to use to access a component by clicking the component icon in the Topology menu of your active session and in the
scenario steps that require their use.
Figure 1. dCloud Topology
Cisco dCloud
Figure 2. Server Details
Application Version URL Username Password

Cisco Unified Communications Server 8.6/11.5 http://198.18.133.3 admin C!sc0123
Cisco Unified IM and Presence Server 8.6/11.5 http://198.18.133.4 admin C!sc0123
Cisco Prime Collaboration Deployment Server 11.6 http://198.18.133.255 admin C!sc0123
VMware ESXi Deployment Server 5.5 http://198.18.133.31 labroot C!sc0123
Workstation 1 Windows 7 Pro http://198.18.133.36 ckent C!sc0123
Workstation 2 Windows 7 Pro http://198.18.133.37 llane C!sc0123
Session Users
The table below contains details on preconfigured users available for your session.
Table 2. User Details
User Name User ID Password Endpoint Devices
Clark Kent ckent C!sc0123  Workstation 1 (http://198.18.133.36)
Lois Lane llane C!sc0123  Workstation 2 (http://198.18.133.37)
Get Started
BEFORE DEMONSTRATING
We strongly recommend that you go through this process at least once, before presenting in front of a live audience. This will
allow you to become familiar with the structure of the document and the lab.
PREPARATION IS KEY TO A SUCCESSFUL CUSTOMER PRESENTATION.
Follow the steps below to schedule your lab and configure your lab environment.
1. Initiate your dCloud session. [Show Me How]
NOTE: It may take up to 45 minutes for your session to become active.
2. For best performance, connect to the workstation with Cisco AnyConnect VPN [Show Me How] and the local RDP client on
your laptop. [Show Me How]
NOTE: You can also connect to the workstation using the Cisco dCloud Remote Desktop client [Show Me How]. The dCloud
Remote Desktop client works best for accessing an active session with minimal interaction. However, many users experience
connection and performance issues with this method.
 Workstation 1 – IP Address: 198.18.133.36, Username: dc\ckent, Password: C!sc0123
Cisco dCloud
a. Cisco Jabber should automatically open and log in. If it does not, use the same credentials used to access the
lab workstation. Accept any certificate warnings and continue.
 Workstation 2 – IP Address: 198.18.133.37, Username: dc\llane, Password: C!sc0123 dCloud: The Cisco Demo Cloud
a. Optional: If you are using a second laptop for this lab, connect it to Workstation 2 as shown above
b. Cisco Jabber should automatically open and log in. If it does not, use the same credentials used to access the
lab workstation. Accept any certificate warnings and continue.
Cisco dCloud
Scenario: Cisco Prime Collaboration Deployment

This scenario illustrates how an end customer can perform basic tasks within the Prime Collaboration Deployment (PCD)
application. It will also show how to set up a migration from a version 8 cluster to a version 11 cluster using Cisco Prime
Collaboration Deployment, including changing the IP addresses of the applications during the migration.
Deploying PCD is a very simple process because it is installed inside an OVA file, which you must deploy on a VMware ESXi
server. Those steps were completed for you, but the complete list of steps can be seen in the appendix of this lab guide. The first
task once PCD is deployed is to log on to PCD and discover your old UC clusters.
Lab Steps
STEP TALKING POINTS ACTIONS
1 Cluster Discovery On Workstation 1 (as Clark Kent):
Hi, my name is Clark Kent, IT systems  Launch Firefox and browse to 198.18.133.255, the location of
administrator at Acme Corporation. I have the PCD Server.
been given the task of upgrading our cluster
 Click the Cisco Prime Collaboration Deployment link.
from version 8.0 to version 11.0 using Cisco
Prime Collaboration.  Log in with the following credentials:
The first step I need to take is to log into the o Username: admin
Cisco Prime Collaboration Deployment o Password: C!sc0123
(PCD) application and discover the existing
Cisco Prime Collaboration cluster, importing it NOTE: You will see several Info or Getting Started popups in the
into the PCD tool. application. Click X if you wish to close them. If you would like to
After entering the cluster information, the PCD bring them back for a page, click the [ ] or [ ] icons.
tool discovers the cluster and imports it into
the application. This takes a few minutes to
 Click and select Inventory > Clusters menu.
gather the information from the cluster. The
columns in the box start to fill out. I look at the  Click Discover Cluster.
information gathered after all systems in the  Enter the following information:
cluster have been contacted successfully.
o Nickname: UCM-v86-cluster
o Hostname/IP of Pub: 198.18.133.3
o OS Admin Username: admin
o OS Admin Password: C!sc0123
 Click Next.
NOTE: This action may take some time to complete. It is not a

problem with the lab.
Cisco dCloud

2 I now have the option to assign functions to Click Edit Settings. dCloud: The Cisco Demo Cloud
each node so I can keep track of which node

 Check the boxes for Music on Hold, Primary Call
handles which role. Once I get to the
Processing, and Primary TFTP to assign them to the Cisco
upgrades or migrations, I can use those
UCM publisher. Notice Publisher is greyed out already because
designations to determine the task order for
PCD knows that it is the publisher.
each node later on. I will set these up now.
 Click Next Node.
NOTE: If you had subscribers in the cluster, you would assign the
roles to each node.
 Check Primary Presence for cup and then click OK.
 Click Finish.
Cisco dCloud

3 ESXi Host Discovery and VM creation Open the VMware vSphere Client using theThe
dCloud: desktop shortcut.
Cisco Demo Cloud
The next thing that needs to be completed is  Log in with the following credentials:
to discover the ESXi host that will have the
o IP address: 198.18.133.31
empty v11 virtual machines (VMs) deployed
on it. o User name: labroot
In this lab, the ESXi host has already been o Password: C!sc0123
installed. This server will house the empty  Click Ignore to proceed past the Security Warning if one
VMs that I will use later to do a migration. appears.
The process of installing ESXi and deploying
an OVA template is straightforward. It is an  Click File > Deploy OVF Template from the main menu.
important part of PCD and needs to be  Click Browse.

completed before I can do any migration
 Choose the file cucm_11.5_vmv8_v1.1.ova from the
tasks.
Workstation 1 Desktop.
NOTE: For more information on installing  Click Open and then Next twice.
ESXi v5.5 go to the following link:
 Click the Name and Location tab and enter ucm11.5pub.
http://kb.vmware.com/selfservice/microsites/s
Click Next.
earch.do?cmd=displayKC&docType=kc&exter
nalId=2052439&sliceId=1&docTypeID=DT_K
B_1_1&dialogID=278304599&stateId=0%200
%20278314115.
Before discovering the ESXi host, I need to

first deploy the empty VMs that will host the
Unified CM and IM & Presence servers. I will
deploy the VM to use for Unified CM first.  In the Configuration drop down menu, choose CUCM 150
user node (BE6K only) and click Next.
For those who are new to VMware ESXi, here
are the definitions of the disk format types:
 Thin Provisioning creates the VMDK with

just the header information, but it does
not allocate or zero blocks. This  Choose Thin Provision for the Disk Format.
provisions the fastest and takes up the
 Click Next and then Finish.
least amount of physical drive space.
 Click Close when the VM deploys successfully.
 Thick (Lazy) creates the VMDK and
allocates all the blocks but does not write
zeroes to them.
 Thick (Eager) creates the VMDK,

allocates and zeros all the blocks. This
offers the best performance.
Cisco dCloud

4 Next, I will create the blank VM for the Cisco Click File > Deploy OVF Template from theThe
dCloud: main menu.
Cisco Demo Cloud
IM & Presence server on the same VMware

 Click Browse.
vSphere Client that I used for the first VM.
 Choose the file cucm_im_p_11.5_vm8_v1.2.ova from the
Workstation 1 Desktop.
 Click Open and then Next twice.
 Click the Name and Location tab and enter imp11.5pub. Click
Next.
 In the Configuration drop down menu, choose CUCM IM and

Presence 500 UC users and click Next.
 Choose Thin Provision for the Disk Format.
 Click Close when the VM deploys successfully.

5 I now have two blank VMs that are ready for Go to the Firefox window and click Inventory > ESXi Hosts.
use. I go back to the PCD webpage and add
 Click Add ESXi Host and enter the following information:
this ESXi host with the blank VMs I just
created. o Hostname / IP address: 198.18.133.31
o User name: labroot
o Password: C!sc0123
 Click OK and then click OK again on the pop-up window.
NOTE: While adding the ESXi host, PCD will mount an NFS
datastore on the ESXi host. The name of the NFS datastore will be
pcdhostname_NFS. This datastore will map to the fresh_install
directory on the PCD server. This directory is where you SFTP your
ISO files on PCD. PCD will use the ISO’s in this datastore to map to
the virtual machine’s CD/DVD drive during install/upgrade tasks. If
you delete the host from PCD, it will remove this mounted datastore.
To view this drive you can go back into vSphere and highlight the
server, and then choose the Configuration tab. Next, click the
Storage link to see the new datastore.
Cisco dCloud

6 The cluster is ready to upgrade to version Click Task > Upgrade > Add Upgrade Task.
11.0. I continue in the PCD application to start

this upgrade process. I choose the application NOTE: On the pop up box notice that you can choose which cluster
to upgrade and the files are already uploaded you want to upgrade and choose the product on that cluster. If you
to my datastore for usage. click the drop down next to Product, you can see what application
upgrades are supported on this version of PCD.
After setting up the upgrade process, I can
see the number of steps that PCD will  Uncheck the box next to cup and click Next.
complete by clicking the Actions icon.
 Click Browse. If there are two Browse buttons then you did not
I set the process to start manually and choose uncheck the box next to cup in the previous step. PCD is now
the option to pause after each task completes. searching for the upgrade directory.
This allows me to validate the steps as they
 In the Choose the Upgrade file window, click the radio button
are completed.
next to the ciscocm.refresh_upgrade_v1.5.cop file.
Optional: Uploading ISOs to the datastore
 Click the Choose File button.
There is already software uploaded to PCD.
This was done to save time. Here is more info
on how to upload software to the application:
There are two directories for you to upload

software: /upgrade and /fresh_install. Put
upgrade files in the upgrade directory and  Click Next.
new installs and migrations in the
 Click Start Task Manually and then click Next.
fresh_upgrade directory.
 Click the pencil icon [ ] next to cucmpub to list the upgrade
You will need to use an SFTP client such as
steps.
Filezilla to do this. Connect to the server with
the client and log in as adminsftp with the  Check the box Pause task after step completes and click OK.
PCD admin account password.
 Click Next. Verify the Start Time is Manual, and click Finish.
You can view all the files uploaded to PCD by
choosing Inventory > SFTP Servers and
Datastore from the main menu in PCD.
Filezilla is installed on Workstation 1. Use the

following steps to connect:
 Open Filezilla using the desktop shortcut.
 Use the drop down arrow next to the site

manager icon and choose PCD.
 In bottom right window, you can see the

file structure of PCD. View the two upload
folders, fresh_install and upgrade. Close
Filezilla when finished.
Cisco dCloud

7 I have the option to switch to another Click Task > Switch Versions. dCloud: The Cisco Demo Cloud
application version if I needed to do this as

 Click Add Switch Version Task.
well. I will not do this today, but I can see how
this would be done.
In the Switch Version task, there are no other

versions in the datastore at this time. If there
was, I could use the drop down box to each
product and choose the switch version. Right
now, it has Do Not Switch because there is
not anything installed in the Inactive  Click Cancel.
Partition.

8 Server Restart Task Click Task > Server Restart.
A server restart is a simple task that most  Click Add Server Restart Task.
people can do on their own either via
 Ensure the box next to the cup server ONLY is checked.
command line or through the OS administrator
Uncheck the box next to cucmpub and click Next.
page. So why would you want to use PCD
versus the previous method?  Click Start task manually and click Next.
I can schedule a restart to happen at a certain  If you had multiple servers, you can change the restart order
time, such as late at night when you do not here or pause after each one completes.
want to be up that late. Another is that you  Click Next.
can set restarts for multiple servers at once.
Then, with a simple click, start them when you  Click Finish.
want in a single page versus logging in to  The new task appears in the window. From here, you can view
each server individually and kicking off a the details, validate, start, or cancel the task. We will leave this
restart. task alone for now because we need the cup server up and
ready for a later task.
Cisco dCloud

9 Readdress Task Click Task > Readdress. dCloud: The Cisco Demo Cloud
Readdressing your UC servers can be a  Click Add Readdress Task and click Next.
simple task IF you follow the correct steps in
 Click OK on the pop-up warning. Right now only Unified CM
the correct order. If not, you may be unable to
can be readdressed.
log in to the system with a Database
Communications Error. PCD saves you from  Click on the Edit link for cucmpub and change the hostname
these potential problems by giving you the and/or ip address information. Any value will be ok. Click OK.
ability to change IP addresses with the  Click Next.
readdress task. This capability is only
available on servers that are on version 10 or  Click OK on the warning.
above. Right now, we only have 8.6 systems  You cannot complete the readdress task, so click Cancel to
but we can still go through part of the process exit.
to see how it would work.
Cisco dCloud

10 Install Task Click Inventory > Clusters. dCloud: The Cisco Demo Cloud
Now to the more complicated tasks, to which  Click Define New UC Cluster.
PCD adds automation and makes much
 Enter UCM-new-v11.5-cluster as the nickname and click Next.
easier. These complicated tasks are the install
and migrate tasks. The first one we will cover  Click Add Node.
is the install task. This task allows you to  Keep Static IP Address selected and enter the following:
create a brand new cluster, almost completely
automatically, using PCD. Once the pub is o Hostname: ucm11pub
installed, you can have PCD install multiple o IP Address: 198.18.134.1

subs at the same time.
o Subnet Mask: 255.255.192.0
First, we need to create the new install cluster
o Gateway: 198.18.128.1
in PCD. I define the settings for both the Cisco
UCM and IM & Presence VMs. o Product Type: Unified CM
o Check the boxes for: Music On Hold, Primary Call

Processing, Primary TFTP, and Publisher
 Click the radio button next to the VM ucm11.5pub and click

OK.
 Click Add Node.
 Keep Static IP Address selected and enter the following:
o Hostname: imp11pub
o IP Address: 198.18.134.2
o Subnet Mask: 255.255.192.0
o Gateway: 198.18.128.1
o Product Type: Unified IM and Presence
o Check the box for: Primary Presence, Publisher
 Click the radio button next to the VM imp11pub and click OK.
 Verify the table that appears matches the image below then
click Next.
Cisco dCloud

11 Next, I need to enter the information for the Enter the following settings for the cluster:
cluster that will host these virtual machines.

o ALL Username boxes: admin
I can see our new cluster in the Clusters list.
o ALL Password boxes: C!sc0123
The next thing to do is creating the task to
start the cluster install. o Organization: News
o Unit: Daily Planet
o Location: Metropolis
o State: NY
o Country: United States of America
 Click Next twice.
 Assign the NTP Server 1 address of 198.18.133.1 and click

Next.
 Click Next to skip NIC settings.
 Change the dropdown for Time Zone to America/New York.
 Check the box next to all systems and click Apply to Selected
then click Finish.
Cisco dCloud

12 I will create the task to install a new cluster. Click Task > Install. dCloud: The Cisco Demo Cloud
The ISO files have already been uploaded to

 Click Add Install Task.
the fresh_install directory so we can complete
this task quickly.  You should see the new cluster you just created. Click Next.
 Click Browse next to the Unified CM Installation file box.
 Click the radio button next to the install ISO and click Choose
File.
 Click Browse next to the Unified IM and Presence

Installation file box.
 Click the radio button next to the install ISO and click Choose
File.
 After you have both ISO’s attached, click Next.
 Click Start task manually and then click Next.

13 Now you will see the task created on the No actions for this step.
page. Since the lab had you choose to start
manually, the task will be there until you are
ready to start it. However, do not start the task
in this lab because you will not be able to
complete the next task, Cluster Migration.
Cisco dCloud

14 Cluster Migration Task No actions for this step. dCloud: The Cisco Demo Cloud
The last task in this lab is the migration task.

This is the most popular feature of PCD.
Migrations can be a very time-consuming
process. This task can also have the cluster
down for long periods. With PCD, as long as
the old cluster is at a supported version, then
you should not have to take much downtime,
if any, to migrate to v11.
You can do a simple migration or network

migration with PCD. If you want to change the
IP address information, then you will do a
network migration. A simple migration keeps
this information the same.
Cisco dCloud

15 Simple Migration No actions for this step. dCloud: The Cisco Demo Cloud
With a simple migration, you keep the same

IP address information on your destination
cluster. Because the source and destination
has the same IP address, they cannot be up
at the same time. PCD takes each server,
pulls the information off, shuts down the
server, installs the new server, and restores
the information to it. Then it moves to the next
server in the PCD task list. This means no
downtime in clusters that have at least one
publisher and subscriber, both doing call
processing. For example, if all the phones are
registered to the publisher as the primary call
processor, then PCD backs up the information
and shuts down the publisher to install the
new v11 publisher. By design, Cisco Unified
CM has redundancy with CM groups. Devices
registered to the pub will automatically switch
over to the next server in the CM group and
register with it. After the v11 publisher server
is installed and the data restored, the devices
will re-register automatically with the pub
again.
As long as you pre-loaded the new v11 phone

firmware on the phones prior to the upgrade
as best practice states, then the failover is
instantaneous.
If you are single threaded, having only one

publisher and still want no downtime or are
trying to move off the source network and
onto a brand new one, then you may want to
choose a network migration.
Cisco dCloud

16 Network Migration Click Task > Install. dCloud: The Cisco Demo Cloud
A network migration allows you to keep your  You will see the UCM-new-v11.5-cluster task you created
source cluster and destination cluster running previously. Click the box next to this task.
at the same time. You will be installing the
 On the install task list, click the Delete link under Actions.
destination cluster with new IP addresses.
Because each new server is configured with a
different IP address, there is no need to shut
down the old server. Both clusters can be up
and running at the same time. The phones are  Click Delete.
moved when you are ready to move them.
To make a seamless switchover, you must

update the certificate trust list (CTL) and initial
trust list (ITL).
 Click the Inventory > Clusters menu.
We have already completed the following
initial tasks required for the Network  Click the Delete link next to the new cluster (UCM-new-v11-
Migration: cluster) you defined earlier.
 Install an ESXi server WARNING: DO NOT delete the v86 cluster that you discovered at
 Deploy blank virtual machines (VMs) the beginning of the lab. If you do, then you will have to rediscover
for each server in the new cluster the cluster before you can move on to creating the migration task.
from OVA templates  Click Yes on the pop up.
 Discover the source cluster with PCD
 Discover the ESXi server with new

VMs with PCD
In the next step, we will clean up the PCD

server of the empty VMs we created earlier in
this lab.
Cisco dCloud

17 Now that PCD is cleaned up, we can start the Click Define Migration Destination Cluster.
migration.
 From the Source UC Cluster drop down menu, choose UCM-
First, we need to define the new cluster. v86-cluster.
 For Destination Cluster Nickname enter UCM-migration-v11-

cluster.
 Choose Enter new network settings for one or more

destination nodes and click Next.
 Click Assign Destination Cluster Nodes.
 In the Virtual Machines section, choose ucm11.5pub.
 Choose Enter New Network Settings from the Network drop

down menu.
 Change the hostname to ucm11pub.

 Change the IP address to 198.18.134.1.
 Click Next Node.
 Choose imp11.5pub
 Change the Network drop down to Enter New Network

Settings.
 Change the hostname to imp11pub.
 Change the IP address to 198.18.134.2.
 Click Done.
 Click Next.
 Leave the NTP settings as is and click Next.
 Leave the DNS settings as is and click Finish.
Cisco dCloud

18 Next, we need to define and start the Click Task > Migrate. dCloud: The Cisco Demo Cloud
migration.
 Click Add Migration Task.
 Choose UCM-v86-cluster for the Source UC Cluster.
 Choose UCM-migration-v11-cluster for the Destination

Cluster.
 Click Next.
 Click Browse on each application and choose the bootable ISO

as you did earlier in the install task.
 Once you have both ISO’s highlighted, click Next.
NOTE: If you are running this lab during peak hours, you may get an
error stating the migration is “Paused due to errors”. If you are
running during peak hours, in the next bullet we recommend
scheduling a later time to run the migration rather than choosing
“Start task immediately”.
 Choose Start task immediately upon completion of the

wizard and click Next.
Cisco dCloud

19 On the screen, you will see a Forced Pause No actions for this step. dCloud: The Cisco Demo Cloud
step. The reason the pause is there is to give

you the opportunity to deal with ITL and CTL
files.
ITL Files
ITLs were first introduced in Unified CM v8.0.

These files are downloaded to every phone
and need to be installed in order for a phone
to be able to register to a cluster. They
contain certificates for your cluster. Because
in this example we are doing a network
migration and changing the address
information, you are moving a phone from one
cluster to another and the phone needs to be
told this and install the correct certificates. If
this were a simple migration with no IP
address/hostname changes, then the ITL
would be migrated and nothing would need to
be done. Anytime you move from one cluster
to another you have to consider the ITL file.
This pause gives you time to complete a Bulk
Certificate Export or use a setting on Unified
CM to clear the certificates on the old cluster.
You can find more about these procedures at
http://bit.ly/ITLMigration.
Read the latest PCD administrator guide to

get more details on when this would be
required. If it is not required, then you can
resume the task and continue, unless you
have to also work with CTL files.
Cisco dCloud

20 Certificate Trust List or CTL is another file No actions for this step. dCloud: The Cisco Demo Cloud
you may need to migrate. This file is used in

clusters that are running security in secure or
mixed mode. One way to verify the mode your
cluster is running is going to the Enterprise
Parameters on Unified CM and looking for the
parameter Cluster Security Mode. If it is 0
then you are running in non-secure mode.
Anything else means you will need to work
with CTLs.
If you are running an Unrestricted version of

Unified CM, then you are in non-secure mode
and you do not have to work with CTLs.
Unrestricted versions of Unified CM do not
have any encryption, so it has no secure or
mixed modes. If you determine that your
cluster is in secure or mixed mode then you
will have to run through the procedures in the
latest Unified CM Security Guide and update
the new destination cluster. It is the same
procedure you follow if you change a
hostname or IP address of a server in your
cluster. You will need to run the CTL client
along with the source cluster eTokens in order
to update the new v11 cluster.
Cisco dCloud
21 Final Considerations dCloud: The Cisco Demo Cloud

NOTE: It is highly recommended that you update the phones to the
You will also need to take into consideration latest firmware BEFORE the migration starts. This will prevent
any gateways or servers that connect to the multiple phones from moving over to the new cluster and starting a
source cluster via IP. These systems must be firmware download, putting extra load on the servers.
updated to match the new IP addresses of
 Click Next.
your v11 servers. After that, you can switch
the phones over to the new servers while the  Review the task and click Finish.
task is still paused. When the pause happens
both the source and destination servers are NOTE: Migration times vary by environment. The size of the
running. The phones will still be registered to cluster database, network speed, and disk read/write speed can
the source cluster. Normally the TFTP affect the install and migration times. In this lab, the new v11
addresses are pushed out with DHCP using applications are being installed on a SAN with hundreds of other
the option 150 parameter. This will need to be demo sessions running simultaneously. This slows down the
changed from the source cluster IPs to the migration process significantly. If you were running this same lab on
destination cluster IPs and the phones dedicated ESXi servers with local storage, the migration would go
restarted. If your phones are set statically, much faster. During testing, it was found that it could take between 4
then you will need to change the phone IPs to 6 hours to complete the full migration. Please plan accordingly by
manually. Once the phones successfully extending your session time, if needed, to complete the lab.
register with the destination cluster, you can
 You can check the status of this task by navigating to Task >
click Resume on the PCD task to shut down
Migrate > View Details.
the source cluster.

22 Monitoring Register your IP phones and Cisco Jabber with
Communications Manager before moving forward in this
Using the Monitoring option, I can see the
scenario.
migration task is scheduled and will be
running soon. You can check the status of the  Click the Monitoring button.
task by expanding the steps and checking the
 Click the Resume task button as needed during the migration.
logs as each one starts and completes.
Because of the Forced Pause step, you will
need to click Resume on the task.
Cisco dCloud
23 Reconfigure Jabber and Cisco IP On Workstation 1 dCloud: The Cisco Demo Cloud
Communicator
 Open Cisco IP Communicator (CIPC) from the desktop
In the lab, I can do these tasks while the shortcut.
migration is happening. They should be  Right click on the CIPC window and choose Preferences.
completed before hitting the Resume button
after the initial activities have completed.  Click the Network tab.
Remember, in a live production environment  Change the TFTP Server 1 address to 198.18.134.1 and click
this would normally be completed during the OK.
Pause step, as stated above in step 21.
 Sign out of Cisco Jabber.
First, I will update Cisco IP Communicator
 Click File > Change connection settings.
with the new UC server cluster address.
 Change the Server address to 198.18.134.2 and click Save.
Then, I will exit Jabber and log back in to the
application. I will update its server address to  Log in as ckent with password: C!sc0123.
the new UC cluster and restart.
NOTE: If the CIPC application opens with an error about audio
Licensing:
drivers, you will need to restart Workstation 1. Follow the steps
After any migration/upgrade your Cisco UCM below to do this.
cluster will need to be licensed. You have 60
 Double click the Restart Workstation batch file on the desktop.
days to fulfill your license requirements.
These can be completed either electronically  Wait a minute or two and then RDP back into the workstation.
or manually. Due to some configuration
 Repeat the tasks in this step with Workstation 2. Log in with
situations and the uniqueness of every install,
username: dc\llane and password: C!sc0123.
a pre-generated license cannot be made for
this lab, which means you will not be able to
license this new v11 cluster in the lab.
However, if you would like to follow the
Operation section of the Prime License
Manager v11 End User Guide found here,
you can go through the process of adding
Cisco UCM as a product instance and see
how you would fulfill your license
electronically or manually.
Cisco dCloud
Appendix A: Server setup – CIMC and RAID Configurations

Configuring the CIMC dCloud: The Cisco Demo Cloud
1. Connect to the server by using the video/mouse/keyboard ports in the back or using the KVM dongle.
2. Power on the server.
3. Press F8 at the BIOS splash screen.
4. Once you have clicked F8, the screen will update to indicate you have pressed F8.
Cisco dCloud
5. Change the IP information to match what is needed at your site.
6. Once complete, press F10 to save changes.
7. Press Esc to exit.
RAID Configuration
Depending on the type of server you are installing the UC apps on the RAID configuration may need to be different. Verify from the
following page how you need to setup the server you have for RAID.
http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#Table_1_-_UC_on_UCS_TRCs
After determining how your RAID should be configured, reference the Cisco UCS Servers RAID Guide here:
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/raid/configuration/guide/RAID_GUIDE.html
Cisco dCloud
Appendix B: VMware Configurations

In this appendix, you will find everything you will need to do in VMware. This includes Disabling LRO, NIC Teaming (optional),
Virtual Machine Creation, Mounting the UC install ISO, and Installing VMware Tools.
Configuring ESXi for the first time

Installing ESXi is straightforward, just like any operating system. Boot off the installation media and follow the setup screens. Once
you have it installed, you need to configure ESXi to allow management. The next steps will help you configure ESXi once it is
installed.
1. First, to log in press F2 and use the root username and password you configured during the install of ESXi 5. With ESXi 4 you
were not required to set a password during install, so the login would be root with no password. With ESXi 5 you are now
required to set a password.
2. Arrow down to Configure Management Network and press Enter.
3. Arrow down to VLAN (optional) and press Enter.
Cisco dCloud
4. Change the VLAN ID to what is needed for your network.
Normally with setting up a server with multiple VLANs you would set up a trunk between the server and the switch to which it is
connecting. The VMs would probably be assigned a different network/VLAN than the ESXi server. This VLAN Id would match the
vlan of the network you are assigning this ESXi server.
5. Arrow down to IP Configuration and press Enter.
6. Arrow down to Set static IP address… and press the Space Bar to select it.
7. Arrow down to set your IP address, Subnet Mask, and Default Gateway and press Enter.
This IP address would match the network of the VLAN you see in the earlier step.
8. Press the Esc key.
Cisco dCloud
9. Press Y to apply changes and restart management network.
10. Press the Esc key to log out.
11. The configuration below is what should be configured on the connecting Cisco switch to setup the trunk. If you have a different
vendor’s switch, your configuration may look different. Also, note your port number will probably be different as well. This
configuration only sets up a single NIC. If you are interested in seeing what it takes to set up NIC teaming, look further down in
this section for the instructions.
 interface FastEthernet1/0/1
 switchport trunk encapsulation dot1q
 switchport mode trunk
 switchport nonegotiate
 spanning-tree portfast trunk
Disable LRO
After installing/upgrading the ESXi host to 5.0 and upgrading the VMs to VMware Tools 5.0, you may experience slow TCP
performance on VMs running on the 5.0 ESXi host. You can address this situation by disabling Large Receive Offload (LRO) on
the ESXi host. If you are running UC apps that use the RHEL 5+ OS then this should not be an issue and these settings do not
have to be changed. Each of the apps used in this lab guide are running this version of RHEL, so you do not need to complete
these steps. See this link for more information about when to change these settings http://docwiki.cisco.com/wiki/Disable_LRO.
1. From within vSphere or vCenter, click on the server ip to highlight it.
2. Click the Configuration tab.
3. Click Advanced Settings, located in the Software box.
Cisco dCloud
4. Click Net and scroll down slightly more than half way.
5. Set the following parameters from 1 to 0:

 Net.VmxnetSwLROSL
 Net.Vmxnet3SwLRO
 Net.Vmxnet3HwLRO
 Net.Vmxnet2SwLRO
 Net.Vmxnet2HwLRO
Depending on the version of ESXi, these settings may not be together. They are usually listed alphabetically.
6. Reboot the ESXi host to activate these changes.
NIC Teaming
1. Log in to your vSphere client and connect to the UCS server.
2. Click Inventory.
3. Highlight your server and click the Configuration tab.
Cisco dCloud
4. Click Networking.
5. Click Properties for vSwitch0.

6. Click the Network Adapters tab.
7. Click Add.
8. Check the box next to the Unclaimed Adapter vmnic and click Next.
9. Ensure both adapters are Active and click Next.
10. Click Finish.
11. Click the Ports tab.
12. Ensure vSwitch is highlighted and click Edit.
13. Click the NIC Teaming tab.
14. Change the Load Balancing method to Route based on IP hash.
Cisco dCloud
15. Click OK.
16. Highlight Management Network and click Edit.

17. Repeat steps 11 – 15 for the second NIC.
18. Click Close.
NOTE: Contrary to “common knowledge” not all Cisco switches use a load-balancing algorithm of src-dst-ip by default, especially
the lower end models. This switch is a c3750 series and uses src-mac by default. The command port-channel load-balance src-
dst-ip configuration was required. Since this is a communal switch and this command can only be applied globally, this step was
already done for you.
It is important to note that only one load-balancing algorithm can be applied at a time on the switch. This means that any and all
EtherChannels on this switch MUST be configured to support the selected load-balancing algorithm. This means the other ends of
those EtherChannels also need to be doing the same algorithm. All switches interconnected via EtherChannels will be required to
do the same load-balancing algorithm.
19. The configuration below is what you will need on your connecting Cisco switch. Again, if you have another vendor’s switch
then your configuration may be different. Also, note that your port numbers and channel-group will probably be different as will.
 interface range f1/0/1-2
 switchport trunk encapsulation dot1q
 switchport mode trunk
 switchport nonegotiate
 spanning-tree portfast trunk
 channel-group 1 mode on
VLAN Configuration for the UC Virtual Machines

If you are using a C-Series server to install your UC apps in this lab, you will need to configure some VLANs for your applications.
Chances are they will be on a particular network. You should have ESXi installed and a trunk configured between the server and
the switch. In order to assign each VM the proper VLAN it must be created first. This example is using the vSwitch that comes with
ESXi. There are other ways of creating a virtual switch, like using the Nexus 1000v. To read more about the 1000v, see the
following page: http://www.cisco.com/en/US/products/ps9902/index.html.
1. With vSphere open, choose the server you want to use to create the VLANs.
2. Once selected, click the Configuration tab.
Cisco dCloud
3. On the Configuration tab, click the Networking link.
4. Click the vSwitch Properties...

5. Within the window that comes up, click Add.
6. Leave Virtual Machine selected and click Next.
7. Give your VLAN a name in the Network Label box. It does not matter what this is as long as it makes sense to you.
8. For VLAN ID, assign the correct VLAN that your UC apps need to be assigned.
9. Click Next.
10. Click Finish.
11. Add any more VLANs if needed or click Close.
Now you can go into each of your VM’s setting and assign the VLAN to the Network adapter. You can assign this in the VM
creation as well. In the lab, you just left as the default VM Network VLAN.
VMware tools install

1. Right click on the VM and choose from the menu Guest > Install/Upgrade VMware Tools.
2. Choose the Automatic Tools Upgrade and press OK.
Cisco dCloud
3. The process will take a few minutes. Once complete, you can click the Summary tab when the VM is selected to view the
status. The VMware tools will read Running (Current) when complete.
In some UC applications, the automatic tools upgrade will not work. Use this link for other ways to install VMware tools:
http://docwiki.cisco.com/wiki/VMware_Tools.
Cisco dCloud
Appendix C: Deploy and Install PCD

For the sake of time, all of the UC applications including PCD were preinstalled. The following steps walk through the VMware
deployment and installation screens.
1. Log in to your ESXi server using the vSphere client.
2. Click File > Deploy OVF Template.
3. Click Browse.
4. Go to the location of where you downloaded the pcd-vapp ova file and click it.
5. Click Next.
6. Click Next again.
7. Give the virtual machine a name or leave as default.
8. Click Next.
9. Choose the datastore to which you wish to install the VM files.
10. Click Next.
11. Keep Thick Provisioned Lazy Zeroed selected.
12. Click Next.
13. Choose the network you wish to assign PCD. This is normally a VLAN assignment based off your local network setup. See the
Appendix B section on creating VLANs.
14. Click Next.
15. Click Finish.
16. Wait for PCD to deploy.
17. Click Close once the VM is finished deploying successfully.
18. Right click on your newly deployed PCD VM and choose Power > Power On from the menu.
19. Highlight the PCD VM and choose the Console tab, or you can click the console button to open in a new window.
Cisco dCloud
20. You should eventually see the system booting or see the following screen:
21. Hit the Enter key to Continue.
One you click into the console your mouse will be caught within the window. To release your cursor, press the CTRL+ALT keys
together.
22. Press Enter to Proceed.
23. Press Enter to Continue.
Cisco dCloud
24. Arrow up/down and choose your time zone, then tab to OK and press Enter.
25. Press Enter to Continue.
26. If you need to change the MTU size, you can now. Typically, this does not need changed. If not leave No selected and press
Enter.
27. Normally, you will use a static IP address, if not choose Yes. More than likely you will choose No here and press Enter to
continue.
Cisco dCloud
28. Enter your IP address information and tab to OK and press Enter to continue.
29. If you are going to use DNS, keep Yes selected and enter the info on the next screen. If not, tab to No and press Enter to
continue.
30. Enter the Administrator Login information and when complete, tab to OK and press Enter.
31. Enter your Certificate information and when complete, tab to OK and press Enter.
Cisco dCloud
32. Enter your NTP server information and tab to Proceed and press Enter.
33. Enter your Security password then tab to OK and press Enter.
34. If you want to setup SMTP now choose Yes, otherwise choose No and press Enter.
35. Keep OK selected and press Enter to start installation.
36. The installation is complete when you see a login screen similar to the one shown here:
Cisco dCloud
Appendix D: Reference Materials

Below is a list of reference materials for lab users who would like more information about Cisco Prime Collaboration Deployment
and its associated products, including the Cisco Unified Communications architecture.
 Prime Collaboration Deployment Admin Guide: http://bit.ly/PCD10-0Admin
 CUCM 10.x Security Guide: http://bit.ly/CUCM10Security
 Admin Guide for Unified Communications Manager: http://bit.ly/CUCM10Admin
 Cisco Unified Communications System 10.x SRND: http://bit.ly/CUCM10SRND
 New and Changed Info for Cisco Unified Communications Manager, Release 10.0(1):
http://bit.ly/NewandChangedCUCM10
 Unified Communications in a Virtualized Environment Wiki: http://bit.ly/VirtualUCWiki
 Cisco Unified Communications Manager on virtualized servers: http://bit.ly/UCMonVirtualServers
 OVA/OVF Template info and downloads: http://bit.ly/UCOVATemplates
 Partner Community Licensing Forum: http://bit.ly/LicForum
 Migration Central: http://bit.ly/MigCentral

Cisco Prime Collaboration Deployment

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cisco Prime Collaboration Deployment

Hochgeladen von

Copyright:

Verfügbare Formate

Cisco dCloud

Cisco Prime Collaboration Deployment 11.6 Lab v1

About This Lab

 About This Solution

 Scenario: Cisco Prime Collaboration Deployment

 Appendix A: Server Setup

 Appendix B: VMware Configuration

 Appendix C: Deploy and Install PCD

 Appendix D: Reference Materials

● Laptop ● Second laptop

About This Solution

 Change IP addresses or hostnames on existing 10.0 or 11.0 clusters

 Fresh install a new Unified Communication clusters

Figure 1. dCloud Topology

Figure 2. Server Details

Application Version URL Username Password

Cisco Unified IM and Presence Server 8.6/11.5 http://198.18.133.4 admin C!sc0123

Cisco Prime Collaboration Deployment Server 11.6 http://198.18.133.255 admin C!sc0123

VMware ESXi Deployment Server 5.5 http://198.18.133.31 labroot C!sc0123

Workstation 1 Windows 7 Pro http://198.18.133.36 ckent C!sc0123

Workstation 2 Windows 7 Pro http://198.18.133.37 llane C!sc0123

Table 2. User Details

User Name User ID Password Endpoint Devices

Clark Kent ckent C!sc0123  Workstation 1 (http://198.18.133.36)

Lois Lane llane C!sc0123  Workstation 2 (http://198.18.133.37)

PREPARATION IS KEY TO A SUCCESSFUL CUSTOMER PRESENTATION.

1. Initiate your dCloud session. [Show Me How]

NOTE: It may take up to 45 minutes for your session to become active.

 Workstation 1 – IP Address: 198.18.133.36, Username: dc\ckent, Password: C!sc0123

Scenario: Cisco Prime Collaboration Deployment

STEP TALKING POINTS ACTIONS

1 Cluster Discovery On Workstation 1 (as Clark Kent):

o OS Admin Username: admin

o OS Admin Password: C!sc0123

NOTE: This action may take some time to complete. It is not a

STEP TALKING POINTS ACTIONS

each node so I can keep track of which node

 Check Primary Presence for cup and then click OK.

STEP TALKING POINTS ACTIONS

important part of PCD and needs to be  Click Browse.

Before discovering the ESXi host, I need to

 Thin Provisioning creates the VMDK with

 Thick (Eager) creates the VMDK,

STEP TALKING POINTS ACTIONS

IM & Presence server on the same VMware

 Click Open and then Next twice.

 In the Configuration drop down menu, choose CUCM IM and

 Choose Thin Provision for the Disk Format.

 Click Next and then Finish.

 Click Close when the VM deploys successfully.

o User name: labroot

 Click OK and then click OK again on the pop-up window.

STEP TALKING POINTS ACTIONS

11.0. I continue in the PCD application to start

There are two directories for you to upload

Filezilla is installed on Workstation 1. Use the

 Open Filezilla using the desktop shortcut.

 Use the drop down arrow next to the site

 In bottom right window, you can see the

STEP TALKING POINTS ACTIONS

application version if I needed to do this as

In the Switch Version task, there are no other

STEP TALKING POINTS ACTIONS