|Attention: DocWiki has reached EOL and will be decommissioned January 25, 2019.|
Prime Collaboration FAQ
(→After a PCD migration, I see under PLM and CUCMadmin the old version listed??)
|Line 183:||Line 183:|
Go to [[Prime Collaboration FAQ#top|Prime Collaboration FAQ Content Table]]
Go to [[Prime Collaboration FAQ#top|Prime Collaboration FAQ Content Table]]
== Prime License Manager ==
== Prime License Manager ==
Revision as of 16:42, 11 September 2018
Back to Unified Communications FAQ
- Cisco Prime Collaboration Provisioning Deployment and Best Practices - LTRUCC-3305
- Simplifying Collaboration Deployments with Prime Collaboration - BRKCOL-2017
- Cisco Prime Collaboration Provisioning v11.x Brownfield Deployment Tech Talk
Prime Collaboration Deployment
I cannot find the PCD bootable on cisco.com, how do I get it??
Bootable media for PCD is not available on cisco.com, in order to get the bootable image of PCD you need to order the media kit for 10.x (or the applicable product version) via PUT
What are the ESXi licensing requirements for PCD
Virtualization Software License Types
Cisco Prime Collaboration Deployment is not compatible with all license types of VMware vSphere ESXi, as some of these licenses do not enable required VMware APIs.
The following are compatible with Cisco Prime Collaboration Deployment:
- Cisco UC Virtualization Foundation (appears as “Foundation Edition” in vSphere Client)
- VMware vSphere Standard Edition, Enterprise Edition, or Enterprise Plus Edition
- Evaluation mode license
The following are NOT compatible with Cisco Prime Collaboration Deployment:
- Cisco UC Virtualization Hypervisor (appears as “Hypervisor Edition” in vSphere Client)
- VMware vSphere Hypervisor Edition
However, you need to be aware of something, if you wish to use PCD in Evaluation mode license, you DO NOT have TAC support. If you want to try it in your lab, go ahead, but if you want Cisco support for PCD issues, you forcefully require any of the other two options.
Do I only need the proper ESXi licensing on the server where ESXi is?? or in all the servers I will use??
You need the right ESXi licensing scheme in ALL the servers you wish to use PCD with, including the server where PCD is installed, if it's a separate server.
What is the difference between a migration, and an upgrade??
I'll work under the assumption you already know how to perform a regular CUCM upgrade, if not, read Upgrades and migrations.
So, how is a PCD upgrade different from a manual upgrade??
The only difference is that instead of you loading the upgrade ISO directly to the VM, and clicking OK/proceed in the wizard a few times, PCD will do this for you. Oh, and you can schedule it to happen at a certain time. That's it. The rest of the leg work required for any upgrade (installing pre-req COPs, making sure enough space is available, changing the VM settings after the upgrade, etc.) is the same manual process. Not many benefits unless you want to schedule it, and I would assume someone would still to monitor the process.
What about a migration?? How does that work??
This is the real reason you would want PCD to start with. This is where the magic happens. I'll cover the steps in another question, I'll just explain the high level process here.
During the migration process, PCD will connect to your production CUCM servers, and will pull out all the configuration from it (NOTE this is not the same as a DRS backup, there is some confusion about this) and will store that within the PCD server, then, it will proceed to use the blank OVAs you created for the target cluster, and will start the CUCM installation of the PUB, once it's installed, PCD will then push the configuration from your production cluster into the new PUB, once it's done and the PUB fully comes up, and then the rest of the servers will be migrated. If there is CUPS / IM&P being migrated, the next server to be installed will be the IM&P PUB, then followed by the remaining CUCM / IM&P SUBs
Do I need to install COP files for CUCM / IM&P migrations??
No, you will not need to install manually any COP files for a migration, the only COP file that is required (ciscocm.ucmap_platformconfig.cop) will be installed automatically by PCD during cluster discovery. If you have reviewed upgrade documentation, you might have found other COP files mentioned, like ciscocm.version3-keys.cop.sgn or ciscocm.refresh_upgrade_version.cop.sgn. None of those are required due to the migration process not being the same as an upgrade.
Do I need to install COP files for a CUCM / IM&P / CUC upgrade??
That depends on the upgrade path you're using, read What COP files do I need??, as explained in What is the difference between a migration, and an upgrade??, PCD won't do any of that leg work for you if you're just using it for a regular upgrade.
Where can I find the ciscocm.ucmap_platformconfig.cop file??
You can follow the same set of instruction to open a connection to the SFTP repository that PCD uses, and you will find it under the /cop directory. I personally prefer to use FileZilla for this.
Can I use PCD with a CUCM BE 5K??
No, you cannot use if for BE 5K
Cisco Prime Collaboration Deployment features are supported for specific software versions. See Supported Releases for more information about software versions that are compatible with each Cisco Prime Collaboration Deployment feature. Regardless of the software version, Cisco Prime Collaboration Deployment does not support Cisco Unified Communications Business Edition 5000 servers.
What does the migration process migrates??
PCD will migrate all the CUCM DB and settings to the new VM, as well as the contents of your TFTP (ringtones, background images, locales, etc.)
Be aware there is a related bug to moving the TFTP files: CSCus01744 Files have incorrect permission after migration to 10.5
EDIT: The above bug seems to be corrected in the 10.5(3) release of PCD
Recommendations prior to a migrations
- Make sure to DRS your original cluster before the migration
- If possible, remove all the CDR/CAR data to avoid timeouts during the migration procedure
- Make sure replication is working fine
Do I really need to use the root user/password for PCD??
PCD has only been tested using root user/pwd, the permissions the user would require are:
- NFS mount
- Powering on VM’s
- Powering off the VM’s
- Attaching the selected iso to the datastore
As far as we know, only root can do this. Not being ESXi gurus, I cannot tell you if there is a way to create a separate user with those permissions. If there is, you would need to try it in a lab before doing that in a production environment.
For Cisco support purposes, we'll stick to Yes, we require root user/password
This is more of an informative question when you have to deal with another team handling ESXi and they push back about giving you the information.
The discovery process is not finding all my servers, what can I check??
There might be several reasons for that, I'll keep adding info here.
A common reason is that the install of ciscocm.ucmap_platformconfig.cop got stuck, you can check that by issuing this CLI command
utils system upgrade status if you see that it's still on going, you try and cancel the install, and try a manual install.
What is the procedure to perform a migration??
I'll assume PCD is already installed and working, and connectivity exists to the servers.
The procedure in high level steps is:
- Discover the source cluster Inventory -> Clusters -> Discover Cluster -> Fill in the blanks, remember you require OS credentials, not CUCMadmin
- Add the target ESXi host Inventory -> ESXi hosts -> Add ESXi Host
- Deploy the CUCM OVA for the target servers via vCenter / vSphere, just deploy the blank VMs, PCD will install the images.
- Upload the bootable CUCM and IM&P images to the PCD SFTP, see SFTP repository
- Inventory -> Clusters -> Define Migration Destination Cluster
- Choose the Source Cluster from your discovered clusters
- Type in the name for the Destination cluster
- If you wish to maintain the IP / Hostname, choose Use the source node network settings for all destination nodes, if you wish to change it, choose Enter new network settings for one or more destination nodes
- Click Next
- Task -> Migrate -> Add Migration Task
- Choose the Source UC cluster and the Destination Cluster
I show the procedure in this video, the steps are pretty much the same across any PCD version and CUCM/IM&P versions.
Why is PCD not recognizing my ISO files for new cluster, or migration??
The bootable images from Cisco have a certain name format, if you change the format, not only will PCD not recognize them, but also the product would not recognize them.
For instance, a CUCM bootable image name would be something like: Bootable_UCSInstall_UCOS_10.5.2.10000-5.sgn.iso, whereas an upgrade image would be: UCSInstall_UCOS_10.5.2.10000-5.sgn.iso
If you happened to change the name of the image when downloading it, if you know exactly which release it was, you can go to the downloads site at Cisco.com and simply copy the name of the file that is published there.
Will PCD migrate my signed certificates??
The answer to this question (and just to be clear, I'm talking about a migration), depends on whether you're changing the hostname, or not. If you want to change the hostname during the migration, the answer is YES the certificates will be regenerated as self-signed certificates, during my testing migrating from a 9.1 to an 11.x cluster, the only cert that was kept, was CAPF on this scenario. If you're NOT changing the hostname, but just changing the IP of the server, all the certs will be migrated as they are, HOWEVER we did find something that changed during this procedure, and that is related to the ITL certificate, which does change. See here Certificates FAQ
Can I use the images from a remote SFTP for a fresh install/migration??
No, for some reason those images will not show up for either option, they can only be used for upgrade procedures
Will PCD migrate my licenses??
Yes, during my testing of a 9.1 migration to 11.x, PLM did retain my license files, however, since they were 9.x licenses, they're not recognized for the new 11.x version. This will require you reaching out to the licensing team in order to have them rehosted. Remember that you have 60 days for any issue related to licensing.
The information you need to send to licensing is obtained from PLM
Log in to Cisco Prime License Manager.
From the Licenses -> Fulfillment page, select Generate License Request from the drop-down list under Other Fulfillment Options.
The License Request and Next Steps window appears. Copy the selected text to your clipboard or click Save it to a file on your PC (as a text file).
With CUCM 12.x the answer remains the same, as now you need to use CSSM or SSMS for Smart Licensing, your PLM licenses will need to be migrated to Smart Licensing and PCD will not assist in that procedure.
I explain how licensing works in CUCM 12.x here:
I'm having problems to migrate to CUCM 10.x using PCD 18.104.22.16800-6, what can I do??
This is most likely due to bug:
- CSCuv40722 PCD: Migrations to 10.x CUCM fail when using 22.214.171.12400-6
The possible options are to use PCD 10.5(3) for the migration, or upgrade to PCD version 11.0(1a) [126.96.36.19900-2] which has the fix
After a PCD migration, I see under PLM and CUCMadmin the old version listed??
This is just a cosmetic issue, it's most likely caused by a custom logon message that was configured in the old release.
Just go to the OS Admin Page -> Software Upgrade -> Customized Logon Message -> delete whatever you have in there.
Once you logout and login again, it should be gone.
Prime License Manager
Need to change MAC settings to static MAC upon install
This is an FYI as the procedure for PLM install has been changed from the original settings when it was released back in 10.0, newer releases require the MAC to be set as static, the PLM install guide outlines the procedure (I'll just outline the related steps):
- Using the vCenter Client, choose Edit virtual machine settings > Network adapter 1 > MAC Address .
- Select the Manual option and enter a unique MAC address.
For a standalone installation of Cisco Prime License Manager, only static MAC addresses are supported on the virtual machine.
- From the vCenter Client, open the console of your virtual machine.
- Power on the virtual machine. The installation begins automatically.
How long do I have to fix any licensing issue??
You get a 60 days period on which you can fix any licensing / PLM issue to make sure you're compliant and avoid losing administration capabilities on the products.
How can I reach licensing for assistance??
The Cisco Licensing Team can be contacted several ways:
- Open a service request online using the TAC Service Request Tool, and enter “licensing” as your problem code. The TAC Service Request Tool is located here: https://tools.cisco.com/ServiceRequestTool/scm/mgmt/case
- Call the appropriate technical support phone number for your region. Find the tech support phone numbers associated with your region by referencing the Cisco Worldwide Contacts page, located here: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html
- Requesting licensing support or by emailing email@example.com. See also What information should I include when requesting Licensing support?
The whole Licensing FAQ can be found here: Cisco Global Licensing Operations (GLO): Frequently Asked Questions
How do I upgrade a standalone ELM / PLM??
The procedure can be performed in two ways, via GUI, which is similar to a CUCM upgrade, or via CLI, which uses the same commands and interface as CUCM.
- Log into PLM, go to Administration -> Install/Upgrade -> Click on the Install/Upgrade Software... button
- You'll get the same options as CUCM, via DVD or SFTP, choose either, click Next
- You will see the available files for the upgrade (assuming there are any), choose the one you want, click Start Installation/Upgrade
- You'll be prompted to Confirm Upgrade/Installation, click Continue
- You will see an Upgrade in Progress message / page
- Once it's done, you will be logged out from PLM
- You can verify the upgrade was successful by going to Administration -> Install/Upgrade and seeing the Active / Inactive versions listed
If you're upgrading from ELM 9.x to PLM 10.x, you will require two COP files:
- elm_Elm_v9_1_1_PlmUpgrade.cop.sgn COP file provides the means for a 9.1(1)standalone EnterpriseLicense Manager server installation to upgrade to 10.x or greater standalone Cisco Prime License Manager software. README
- ciscocm.version3-keys.cop.sgn COP file has the RSA keys that are required to validate the upgrade.
Missing RSA-3 keys will, for example, result in status errors in the Software Installation/Upgrade window. README
ALWAYS make sure to review the documentation prior to attempting an upgrade for any system:
- Cisco Prime License Manager User Guide, Installation and Upgrade
- Release Notes for Cisco Prime License Manager Release 10.5(2)
Can I remove / disable the co-res PLM??
This feature was added in 10.5(2), you can find the instructions here:
Remove Cisco Prime License Manager
If at any point you wish to re-enable PLM, you will need to contact Cisco TAC for this.
Back to Unified Communications FAQ
Any comments, questions, suggestions, contributions, etc. please send them to firstname.lastname@example.org. Please make sure the subject is formatted "UC FAQ <anything else>" as I'll have rules in my mail to match them, otherwise, they'll end up in my spam folder.