Use the information in the following table to determine which SFTP server solution to use in your system. These servers are third party provided and third party tested. Version compatibility depends on the third party test. The number of Unified Communications Manager subscriber nodes in a cluster cannot exceed 4 subscriber nodes and 4 standby nodes, for a total of 8 subscribers. The total number of servers in a cluster, including the Unified Communications Manager publisher node, TFTP server, and media servers, cannot exceed The maximum number of IM and Presence Service nodes in a cluster is 6.
If you are using a bit IP subnet mask, ensure that you use the following format: Do not use the format Although We recommend that you change the format before you begin an upgrade to avoid possible problems.
Other formats are supported for subnet masks and this limitation applies to bit subnet masks only. This section refers to application software requirements for Cisco Unified Communications Manager and the IM and Presence Service upgrades and migrations. Ensure that the device name for the Cisco Unified Mobile Communicator device contains 15 or fewer characters. If the device name contains more than 15 characters for the Cisco Unified Mobile Communicator, the device does not migrate during the upgrade.
After you install an unrestricted release, you can never upgrade to a restricted version. A fresh install of a restricted version on a system that contains an unrestricted version is also not supported. All nodes within a single cluster must be in the same mode. For example, Unified Communications Manager and IM and Presence Service in the same cluster must either all be in unrestricted mode or all be in restricted mode. IP phone security configurations are modified to disable signaling and media encryption including encryption provided by the VPN phone feature.
Be aware that after you install an unrestricted release, you can never upgrade to a restricted version. You are not allowed to perform a fresh installation of a restricted version on a system that contains an unrestricted version.
Cisco Unified CM Administration. Upgrades from Unified Communications Manager version 9. If you have a SIP Profile with any of these names, you need to rename or delete it before proceeding with the upgrade. If you are using the utils system upgrade CLI command to upgrade IM and Presence Service nodes, you must use the default OS admin account, as opposed to a user with administrator privileges.
Otherwise, the upgrade will not have the required privilege level to install essential services, thereby causing the upgrade to fail. The account must have privilege level 4. Also note that this limitation may be fixed for newer ISO files. For-up-to date information on this limitation, see CSCvb If you are upgrading from the This is required due to API changes in this release that were not a part of the Your upgraded system will not be able to send troubleshooting logs to the Cisco Cloud unless you disable Push Notifications and then follow the onboarding process for this release.
This is required due to enhanced data type support in this release. If you don't migrate your database, schema verification failure will occur on the existing SQL Server database and services that rely on the external database, such as persistent chat, will not start. Contact Cisco TAC to obtain a copy. Create a new empty SQL Server database. Run the System Troubleshooter to confirm that there are no errors with the new database.
Verify that no errors appear in the External Database Troubleshooter section. Under IM and Presence Services , select the following services:. Confirm that the external database is running and that all chat rooms are visible from a Cisco Jabber client. Delete the old database only after you're confident that the new database is working. If you have either of these features deployed with Release The following section provide information about the upgrades from Hence, the IM and Presence Service Refresh upgrade from Unified Communications Manager Perform any one of the following procedures before you upgrade to Unified Communications Manager Release Delete the previously configured IPsec policies and perform the upgrade.
After the upgrade is complete, reconfigure the IPsec policies with DH groups 14— If you attempt to upgrade Unified Communications Manager with IPsec configured to use certificate-based authentication with self-signed certificates, the upgrade fails.
You must reconfigure the IPsec policy to use a CA-signed certificate. The IM and Presence Service supports intercluster peers to clusters that are running different software versions. Before you upgrade to Release If required, change VM resources to ensure that your upgraded deployment provides the best performance.
If you are upgrading or migrating from Release 9. This issue exists if any of the following CUCM combined network locales have been installed:. This issue can also occur if the following CUCM locales are installed together in the same cluster:. To ensure that your upgrade does not fail, update your Unified Communications Manager and phone locale installation to use a locale that is dated after August 31, as this issue does not exist for any locale file issued after that date.
After you update your locale installation, you can begin the upgrade or migration. An issue exists with refresh upgrades of Unified Communications Manager to specific destination releases.
After the timezone data populates, you may see a blue transition screen appear for 30 minutes or more. The upgrade will continue to run even while the blue screen displays. The blue screen will clear itself after approximately 30 minutes. This issue affects refresh upgrades of Unified Communications Manager where the destination version falls within the range in the below table.
This range includes SU and ES versions that lay within the range. This issue does not occur for upgrades to older or newer versions that do not fall within the range, or for upgrades of the IM and Presence Service. For additional details, see CSCvs The following sections provide information about the licensing requirements for Unified Communications Manager and the IM and Presence Service.
As of Unified Communications Manager Release Smart Licensing requires you to have a Smart Account created and configured before you upgrade or migrate the Unified Communications Manager server.
Direct— Unified Communications Manager sends usage information directly over the internet. No additional components are needed. Proxy Server— Unified Communications Manager sends usage information over the internet through a proxy server. Cisco Smart Software Licensing is a new way of thinking about licensing.
It adds flexibility to your licensing and simplifies it across the enterprise. It also delivers visibility into your license ownership and consumption. Cisco Smart Software Licensing helps you to procure, deploy, and manage licenses easily where devices self-register and report license consumption, removing the need for product activation keys PAK. It pools license entitlements in a single account and allows you to move licenses freely through the network, wherever you need them.
It is enabled across Cisco products and managed by a direct cloud-based or mediated deployment model. Cisco Prime License Manager is no longer used as of Release If you have enabled the mixed-mode prior to upgrade and have not registered to Cisco Smart Software Manager or Cisco Smart Software Manager satellite then,. The system is currently running Mixed mode. If you are eligible to upgrade to the Smart Licensing version of the product, then you are able to initiate the migration through the License Registration Portal or Cisco Smart Software Manager.
The following section provide information about the upgrades from Hence, the IM and Presence Service Refresh upgrade from Unified Communications Manager If you attempt to upgrade Unified Communications Manager with IPsec configured to use certificate-based authentication with self-signed certificates, the upgrade fails. You must reconfigure the IPsec policy to use a CA-signed certificate. The IM and Presence Service supports intercluster peers to clusters that are running different software versions.
Before you upgrade to Release If required, change VM resources to ensure that your upgraded deployment provides the best performance. The following sections provide information about the licensing requirements for Unified Communications Manager and the IM and Presence Service.
As of Unified Communications Manager Release Smart Licensing requires you to have a Smart Account created and configured before you upgrade or migrate the Unified Communications Manager server. Direct— Unified Communications Manager sends usage information directly over the internet. No additional components are needed. Proxy Server— Unified Communications Manager sends usage information over the internet through a proxy server. Cisco Smart Software Licensing is a new way of thinking about licensing.
It adds flexibility to your licensing and simplifies it across the enterprise. It also delivers visibility into your license ownership and consumption. Cisco Smart Software Licensing helps you to procure, deploy, and manage licenses easily where devices self-register and report license consumption, removing the need for product activation keys PAK. It pools license entitlements in a single account and allows you to move licenses freely through the network, wherever you need them.
It is enabled across Cisco products and managed by a direct cloud-based or mediated deployment model. Cisco Prime License Manager is no longer used as of Release If you have enabled the mixed-mode prior to upgrade and have not registered to Cisco Smart Software Manager or Cisco Smart Software Manager satellite then,. The system is currently running Mixed mode. If you are eligible to upgrade to the Smart Licensing version of the product, then you are able to initiate the migration through the License Registration Portal or Cisco Smart Software Manager.
You can self-initiate this process by downloading and installing the Smart Licensing version of the software and registering the device to a Smart Account using a Registration Token. The migration of any entitlements tracked by Cisco automatically migrates to the Customers Smart Account. You will also be able to initiate the migration of unused classic PAKs to Smart Accounts for future consumption by products in Smart Mode. Unified Communications Manager 9.
Partial Conversion supports mixed environment of older and Unified Communications Manager Unified Communications Manager Pre 9. Beyond this, they would have to buy additional new licenses. Specific License Reservation SLR allows the customer to reserve licenses from their virtual account, tie them to a devices UDI and use their device with these reserved licenses in a disconnected mode.
The customer reserves specific licenses and counts for a UDI from their virtual account. The following options describe the new functionality and design elements for Specific Reservation. Use this command to cancel the reservation process before the authorization code is installed. Use this command to install the license reservation authorization-code generated on the Cisco Smart Software Manager.
Use this command to remove the license reservation authorization code that is installed and list of reserved entitlements. The device transitions back to an unregistered state. Use this command to remove the license reservation authorization code that is entered by the user.
If you are upgrading from If you are upgrading the However, you must assign users and enable the IM and Presence Service Service for each assigned user. With the Jabber for Everyone offer, no end user licenses are required to enable IM and Presence functionality. You can assign IM and Presence Service on a per user basis, regardless of the number of clients you associate with each user. When you assign IM and Presence Service to a user, this enables the user to send and receive IMs and availability updates.
If users are not enabled for IM and Presence Service , they will not be able to log in to the IM and Presence Service server to view the availability of other users, send or receive IMs, and other users will not see their availability status. You can enable a user for IM and Presence Service using any of the following options:.
The following documents contain additional supporting information that will help you to upgrade in specific cases. Refer to Cisco Collaboration on Virtual Servers in order to set up your virtualized platform. These documents also contain information that may help you to plan and size your upgraded system:. Skip to content Skip to search Skip to footer. Book Contents Book Contents.
Find Matches in This Book. PDF - Complete Book 2. Updated: November 17, Chapter: Upgrade Planning. Upgrade Methods The following table explains the types of upgrades that you can complete with Cisco Unified Communications Manager and the IM and Presence Service and the upgrade tools that you can use to complete the upgrade. Upgrade Type Description Upgrade Tools Direct Standard Upgrade A standard upgrade is a direct upgrade where you need to upgrade the application software, but not the underlying operating system.
Example : Upgrades from Note For standard upgrades where the preupgrade release is It's used in the following cases: The desired upgrade requires you to change the infrastructure hardware and platform. The following tool is used to complete migrations: PCD Migration Migration from legacy releases A legacy release is a release that is so old that no direct upgrade or direct migration path exists to the current release.
Take Record of Your Current System Before you begin the upgrading, take a record of the versioning within your current system setup. From Release Supported Upgrade and Migration Paths The following table highlights supported upgrade paths to upgrade to Note Unless indicated otherwise, each release category includes the SU releases within that category.
For example, In addition, releases like Table 2. Direct upgrade and migration is not supported. Do the following: Upgrade to 6. Version switching supported for upgrades, but not for migrations Unified CM Do the following: Direct upgrade to 8.
Version switching supported for upgrades, but not supported for migrations. IM and Presence During the following step you will have to configure your administrative login configuration, while in the next one you will have to give the details for the local Ceftifficate Authority:. And the next one is regarding the NTP configuration.
Always be using NTPs! If your clocks are not set correctly then you cannot rely on your logs! After that you will have to give a password which is important of course and you will need it in case of intercluster configuration.
The same password will be used to encrypt your archives as well. By selecting OK on the following screen the installation process will begin and it is unreversable:. During the installation process the system may restart few times and it is usual to see some messages like the following one:. The whole installation process can take up to one hour or even more if you are installing it on some slow hardware. However, if everything was fine during the installation process in the end you should get the following screen which is confirming the successful installation:.
Disclaimer: This site is in not affiliated with Cisco Systems, Inc. The reason for this site is to help you with your Cisco certification by covering the essentials you need in order to pass the CCNA exams. Note that the latest file may have a different filename and version. Select Select all Services on all servers and click Next.
Click Finish and Close. Double click on Install and select the file which you require and download. If the subscriber nodes have the previously configured SFTP software location settings available and the Use download credentials and software location from Publisher check box is disabled, the local subscriber configurations take precedence during a simple upgrade and will not use the SFTP software location settings defined in the publisher node.
This option is not available if the From version is pre From the Source drop-down list, select the option that matches where the upgrade file is saved:. Optional To receive an email notification when the upgrade is complete, enter the SMTP Server address and an Email Destination so that you can be emailed when the upgrade completes. Check the continue with upgrade after download if you want the upgrade to commence automatically once the upgrade file is downloaded.
If you don't check this check box, you will need to manually initiate the upgrade later using Local filesystem as the Source. Check the switch-version cluster after upgrade valid only for ISO check box if you want to switch over to the upgraded version immediately after upgrade.
Otherwise, the upgraded version remains inactive and you will need to switch versions manually later. Select the upgrade version that you want to install, and click Next. During cluster wide upgrade, make sure to have the first 3 digits common between the selected Unified Communications Manager and IM and Presence Service upgrade files. Run the utils system upgrade cluster CLI command and follow the prompts.
When prompted, enter whether to proceed with the upgrade automatically after the upgrade file downloads. If you are prompted to start the installation, enter Yes. If you haven't already configured the reboot sequence, use the sliders to edit the reboot sequence and click Save. Switch Versions Manually.
If you did not switch versions automatically during the upgrade, use this procedure to switch versions manually. After the upgrade, run the post-upgrade COP file to guage the post-upgrade health of your system. The following table displays the recommended node by node upgrade sequence for clusterwide Refresh Upgrades. Upgrade the IM and Presence database publisher node in parallel with the Unified Communications Manager subscriber nodes.
Switch the software version on the publisher node and reboot it. The new software is active. Switch the software version on the secondary subscriber nodes in parallel and reboot them. Switch the software version on the database publisher node and reboot it.
Switch the software version on the primary subscriber nodes in parallel and reboot them. Switch the software version on the subscriber nodes in parallel and reboot them.
Ensure that database replication is complete and functioning between the publisher node and all subscriber nodes before proceeding. Ensure that database replication is complete and functioning between the publisher node and all subscriber nodes. From the Source drop-down box, select the option that matches where the upgrade file is saved:. To receive an email notification when the upgrade is complete, enter the SMTP Server address and an Email Destination so that you can be emailed when the upgrade completes.
Run the utils system upgrade initiate CLI command and follow the prompts:. If you are upgrading a subscriber node, and you have previously upgraded this node, indicate whether you want to use the publisher node credentials for the upgrade the default is yes. When prompted to start the installation, enter Yes. Click Switch Version s to switch versions and restart the node.
To switch a cluster back to a previous version, complete these high-level tasks:. Switch back all backup subscriber nodes.
Switch back all primary subscriber nodes. If you are reverting to an older product release, reset database replication within the cluster. Log in to the management software for the node that you are upgrading:. Click the Switch Versions button. After you verify that you want to restart the system, the system restarts, which might take up to 15 minutes.
To verify that the version switch was successful, follow these steps:. Log in again to the management software for the node that you are upgrading. The Version Settings window displays. Verify that the correct product version is now running on the active partition. Verify that all activated services are running. Verify that you can log in and that your configuration data exists. Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book 2.
Updated: November 17, Chapter: Upgrade Tasks. Note Complete Refresh Upgrades during a maintenance window as the upgrade requires several reboots and the system doesn't process traffic during upgrade.
0コメント