Modifications to the NTP. Cisco does not support these modifications. Step 2 Double-click the Network Time Protocol service. Step 3 In the Startup type field, choose Disabled.
Step 4 Click Stop. Step 5 Click OK. If you are joining the server to a Microsoft Windows 4. Cisco strongly recommends that you do not configure any server in the cluster as a Domain Controller.
If you configure any server in the cluster as a Domain Controller, you cannot upgrade Cisco CallManager on the server. Cisco does not support upgrades through Terminal Services. Cisco supports ILO for remote management and configuration tasks only. If you encounter problems during the installation, Cisco recommends that you take the following actions:. During the installation if you receive an error message that displays in a dialog box, see the "Analyzing Error Messages" section and perform the recommended corrective action.
Be aware that not all error messages that display in the log file are catastrophic. MSI generates error messages in the log file for many reasons; for example, attempts to access a service that is not used by Cisco CallManager. This section contains information about the procedures that are used to complete the Cisco CallManager installation.
The section includes the following topics:. For preinstallation tasks that you must complete before the installation, see Table 2. Determine how many Cisco CallManager servers the cluster will contain, which server will house the publisher database, and where backup tasks will be performed. If you have hot-swappable drives, make sure that you inserted the appropriate drives into the server and ensure that the drives are functional.
Remove any additional hard drives that are in the server. Make sure that you installed the operating system version Before you perform the upgrade, be sure to read the operating system readme information that is posted on the operating system cryptographic software page.
The operating system service releases post on the voice products operating system cryptographic software page. You can navigate to the site from the Cisco CallManager software page. If your server supports the Cisco Media Convergence Server Network Teaming Driver, you can install and configure this driver, if you choose to do so.
You must disable and stop all third-party, Cisco-verified, and Cisco-provided, coresident applications that are installed on your server. Cisco strongly recommends that you do not install any Cisco-verified applications until you have completed the installation on every server in the cluster.
See the "Gathering Configuration Information" section. You can distribute the call-processing load for your system across mult i ple Cisco CallManagers as a single cluster. A cluster comprises a set of Cisco CallManagers that share the same database. At a minimum, you should determine how many Cisco CallManager servers the cluster will contain, which server will house the publisher database, and where backup tasks will be performed.
Additional planning should include a strategy for distributing the devices such as phones or gateways among the Cisco CallManagers in the cluster to achieve the type of distribution that you want. Periodically, Cisco CallManager automatically updates the subscriber copies of the database from the publisher database. If you are installing a dedicated server, locate the Cisco CallManager product key in this document. If you are installing Cisco CallManager on a coresident server, refer to the specific Cisco IP telephony application installation documentation for the coresident product key.
Step 2 Click the Network Identification tab. Step 3 Click the Properties button. Step 6 When prompted to do so, reboot the server. Step 7 Log in using the Administrator password. Step 8 Perform this procedure on every server in the cluster that exists in the NT Domain. Before you begin the installation, make sure that you connect your server to the network.
When you connect the server to the network, use the NIC connector that is listed in the table because the other NIC is automatically disabled during the installation. Note You can implement NIC teaming on servers that support the network teaming driver.
Before you perform Cisco CallManager installation procedures, you must disable and stop all Cisco-approved McAfee antivirus services. You can enable and start all antivirus services after you complete the procedures. You can enable and start the services after the installation.
Use the following procedure to disable third-party applications, antivirus services, or security agents:. Step 2 Locate the third-party application, antivirus service, or security agent that you want to stop, right-click Cisco Security Agent, and choose Properties. Step 3 In the Properties window, click the General tab.
Step 4 In the Service Status area, click Stop. Step 5 From the Startup type drop-down list box, choose Disabled. Step 6 Click OK. Table 4 shows the information that is required for installing Cisco CallManager on your server. Complete all fields unless otherwise noted. Gather this information for each Cisco CallManager server that you are installing in the cluster.
Make copies of this table and record your entries for each server in a separate table. Note If you change any security or account policies from the default setting, the installation may fail. For more information on security and account policies, refer to Microsoft documentation. For the publisher database server, the installation takes 45 to 90 minutes, depending on the server type.
Use the following procedure to perform the installation. Note Critical third-party components that are required and installed by Cisco CallManager may require multiple reboots during installation, and you may need to manually restart the installation program and reenter the configuration data.
Step 1 After you install the operating system and log in to the server by using the Administrator account and password, obtain the Cisco CallManager Installation, Upgrade, and Recovery Disk 1 of 2 and insert it into the drive.
Note Follow the instructions in the dialog box. On most windows, you can choose Next to proceed with the installation.
When prompted to enter a password, remember to record your entry. Step 3 To confirm that you may be prompted to reboot the server and reenter configuration data multiple times for Cisco CallManager to install critical third-party components, click OK. Step 4 The installation program must update the configuration and restart the server. To proceed with installation, click OK. Note If you click Cancel , Cisco CallManager will not be installed on your server, and the installation program will not make any changes to your system.
Step 5 Log in to the server by using the Administrator account and password. Step 6 When the Installation Welcome window displays, click Next.
Step 7 Accept the Cisco CallManager license agreement by clicking the I accept the terms in the license agreement radio button; then, click Next. Step 8 In the Customer Information window, the User Name and Organization that you entered during the operating system installation automatically display.
Cisco automatically populates the product CD key fields with the product key that you entered during the operating system installation. Click Next.
Cisco requires that you install Cisco CallManager on the publisher database server first, so authentication can occur between the publisher database and subscriber servers.
Note The publisher database server serves as the master database for all servers in the cluster. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database server. If you are configuring a subscriber database server, make sure that the server that you are installing can connect to the publishing database server before the installation can continue.
The installation process necessitates this connection, so the publisher database server can be copied to the local drive on the subscriber server. To make sure that a good connection exists between the servers, issue a ping command from the subscriber server to the publisher database server before you try to authenticate to it. If the ping command is not successful, you must exit the installation program, fix the problem, and begin the installation process again.
Step 11 In the Administrator password window, enter the local Windows administrator password. Step 12 Enter the Private Password Phrase for the cluster; confirm the private password phrase, and click Next. The private password phrase contains 1 to 15 characters. Press the Tab key. To confirm the password, enter the password again; then, click Next.
Step 14 In the Cisco Directory Password window, perform the following procedure:. Enter the Directory Manager password. Step 15 Now that the Cisco CallManager and other included software are ready to be installed, click Install. The Cisco CallManager installation takes about 30 to 45 minutes, depending on your server type. Note The progress of the status bar may reset as each software package is being installed and as the installation program configures your machine.
You may see the installation program reset the status bar multiple times. Do not reboot the server unless the installation prompts you to do so. The installation program continues to install files on your server. Continue to wait while the installation completes. Note Do not use Cisco CallManager Installation, Upgrade, and Recovery Disk 1 of 2 on another server until you complete the installation process on this server.
Before you complete the installation, the installation program prompts you to reinsert Cisco CallManager Installation, Upgrade, and Recovery Disk 1 of 2. Step 19 To restart the server, click Yes. Note You cannot install Cisco CallManager on a subscriber server until you reboot the publisher server.
Step 20 After the server reboots, remove the disk from the drive. Step 21 Log in to the server by using the Administrator password. If you are not installing Cisco CallManager on the subscriber server s , go to "Performing Postinstallation Tasks" section. Note You cannot add a subscriber server to a cluster by installing a previous version of Cisco CallManager and then upgrading the subscriber server to the same version that is running on the publisher server.
After you install Cisco CallManager on the publisher database server, you install the application on the subscriber database servers. For each subscriber database server, the installation takes 45 to 90 minutes, depending on the server type. Step 3 To confirm that you might be prompted to reboot the server and re-enter configuration data multiple times in order for Cisco CallManager to install critical third-party components, click OK.
Cisco automatically populates the product key fields with the product key that you entered during the operating system installation.
Note The publisher database server functions as the master database for all servers in the cluster. If you are configuring a subscriber database server, make sure that the server that you are installing can connect to the publishing database server, so the installation can continue. To make sure a good connection exists between the servers, issue a ping command from the subscriber server to the publisher database server before you try to authenticate to it.
In the status of the ping command, verify that the IP address displayed is the IP address of the publisher database server. You do not need to enter a user name and password.
Mapping to the drive without entering a user name and password ensures that the passwords on the publisher and subscriber servers match.
If the subscriber database server cannot access the publisher server, you must exit the installation program, fix the problem, and begin the installation process again on the subscriber server. Step 9 The Complete radio button is chosen; click Next. Step 10 In the Server Type window, perform the following procedure:. Click the Subscriber radio button.
Enter the computer name of the publisher database server. This password must match the Windows administrator password that is used on the publisher database server. Step 12 Enter the Private Password Phrase for the cluster; confirm the private password phrase and click Next. This private password phrase must match the Private Password Phrase that you entered on the publisher database server. This password must match the SA password that is used on the publisher database server.
Step 14 Now that the Cisco CallManager and other included software are ready to be installed, click Install. This part of the installation takes about 30 to 45 minutes, depending on your server type. Step 18 To restart the server, Click Yes. Step 19 After the server reboots, remove the disk from the drive.
Step 20 Log in by using the Administrator account and password. After installing Cisco CallManager on your server, you must set some configuration parameters for Cisco CallManager and perform other post-installation tasks before you can begin using it. Perform these tasks for each server that you install and complete them before or after the other servers in the cluster are installed. For post-installation tasks that you must complete after the installation, see Table 5.
Activate Cisco CallManager services that you want to run on each server in the cluster. To manage your system, install the latest service release and hotfixes that are available on CCO. If you want to do so, you can configure the F: drive on the higher end servers with four hard drives such as the MCS for trace file collection. Click the following URL to obtain the locale and the installer documentation:.
Cisco strongly recommends that you install one of the following security agent to protect your servers against unauthorized intrusion. If you want to use Norton AntiVirus, install the application and perform post-installation tasks. If you disabled any third-party application, antivirus services, or security agents prior to installing Cisco CallManager, you must reenable it.
If necessary, you can add a subscriber server to the cluster after the installation. You cannot add a subscriber server to a cluster by installing a previous version of Cisco CallManager and then upgrading the subscriber server to the same version that is running on the publisher server.
MSJVM installed by default in all client workstation versions of the current Windows operating systems, except for the following versions:. Even though all Cisco CallManager services install on each server in the cluster, you must manually activate the services that you want to run on each server in the cluster.
To do this, access Cisco CallManager Serviceability by following this procedure:. Step 4 Click on a server to select it. Step 5 Check the Service Names check boxes for the services to be activated.
Step 6 Click Update. Step 4 Click Properties. Step 5 Click Advanced. Step 6 Click the DNS tab. Step 10 Click OK. Step 11 Perform this procedure on every server in the cluster that has Cisco CallManager installed.
The Cisco CallManager database contains information and parameters that relate to the system as a whole, to connected devices, and to individual users.
In Cisco CallManager Serviceability, activate the services that you want to run on each server in the cluster. Configure system-level settings, such as Cisco CallManager Groups. Design and configure your dialing plan.
Configure media resources for conferences, Music On Hold, and so on. Install and configure your chosen voice-messaging system. Install and configure the gateways. Enable computer telephony integration CTI application support; then, install and configure the desired CTI applications. Configure the users. Configure and install the phones; then, associate users with the phones. To obtain this document, see Table 1.
After you install this version of Cisco CallManager on all servers in the cluster, Cisco strongly recommends that you install the latest Cisco CallManager service release on all servers in the cluster.
These service releases provide additional bug fixes for your system. Be aware that Cisco CallManager service releases are cumulative. Cisco rolls bug fixes into the next Cisco CallManager release. Tip Make sure that you install the same version of the service release on every server in the cluster. To obtain the latest Cisco CallManager service release, perform the following procedure:. Step 3 Locate and download the readme document for the service release.
The readme file provides procedures, caveats, and descriptive information for installing the files. Step 4 Using the readme file as a reference, install the Cisco CallManager service release on every server in the cluster where Cisco CallManager is installed. Step 5 Perform other post-installation tasks. The mcsver.
Be aware that Cisco does not report the actual Cisco CallManager version through this program. Most of these components, run from the installation disks during the initial installation, no longer exist on the system. The version for OS Image equals your operating system disk version number. Cisco offers two security agent options. Both of these agents control system operations by using policies that allow or deny specific system actions before system resources are accessed. CSA for Cisco CallManager provides a standalone agent and security policy that is designed to be used on all servers in the voice cluster.
The policy that is included with this agent, which is configured specifically for Cisco CallManager and Customer Response Applications CRA , cannot be updated or viewed. If you want to add, change, delete, or view rules and policies that CSA for Cisco CallManager includes, or if you want to add support for non-Cisco approved, third-party applications, you must purchase and install the fully managed console, CSA MC.
CSA MC requires a separate, dedicated server to be used as the management center. This management center allows you to create agent kits that are then distributed to agents that are installed on other network systems and servers. When you install Cisco CallManager on your server, a default music on hold sample automatically installs for customer use. Use the following procedure to reenable third-party applications, antivirus services, or security agents:.
Step 2 Locate the third-party application, antivirus service, or security agent that you want to start, right-click the service, and choose Properties. Step 4 From the Startup type drop-down list box, choose Automatic. Step 6 In the Services window, right-click the application or service and click Start. Install the operating system on the subscriber server s by using the Cisco-provided operating system disks and the operating system documentation.
Make sure that you enter the publisher database server name correctly, so authentication to the publisher database server can occur. Upgrade to the version of Cisco CallManager that currently runs in the cluster. Reboot all nodes in the cluster. Install the operating system and the Cisco CallManager software as if it were a new installation by using the Cisco-provided operating system disks and the operating system documentation. Upgrade to the version of the Cisco CallManager that you want to restore.
If necessary, reinstall the Cisco IP telephony applications, plugins, and service releases to the version that is compatible with the restored version of Cisco CallManager. Restore the backup data to the new server and reboot the server. To restore the data, you must have backup data stored on tape or on a network directory, not on the local directory of the existing or failed server.
Verify that the data was restored to the new server. If you are replacing a server with four drives, Cisco recommends that you set the trace directory path on the server to the default C: drive before you backup your server. If your server has four drives, you can configure the trace drive for trace file collection. MSJVM installed by default in all client workstation versions of the current Windows operating systems, except for the following version:.
If your client machine runs MSJVM, you can continue to use the existing configuration to browse into the Cisco CallManager Administration windows and perform administration tasks. In addition, you must configure the browser security to be Java-enabled. You would then have two Java Runtime Environments installed and running on your machine. If you use Windows as your operating system, you must obtain a separate compression utility such as WinZip to store and access zip files.
Step 4 Double-click the installation executable file on the client PC. Note The exact file name of the installation executable file changes with each version as the new version number is incorporated into the name. If the connections between the publisher database server and the subscribers within a cluster are broken for any reason, you cannot copy the database to the subscribers. To determine whether the connections between the publisher database server and the subscribers within a cluster are broken, wait 35 minutes after you have installed the last subscriber in the cluster.
If a red X icon appears next to the subscription, it indicates that the subscription is broken. If you determine that one or more subscription connections are broken, as indicated by the red X icon next to the subscriptions, reinitialize the subscriptions and start the replication snapshot agent on the publisher database server. Step 3 In the main window, right-click the subscription name and choose Reinitialize all Subscriptions.
Click Yes to confirm. Step 5 Right-click the publication name that matches the database name that you are configuring; then, click Start. In rare cases, the reinitialization of the subscriptions may not work. This section includes information about resolving error messages and other failures. The following messages may display in dialog boxes not the log file during the installation. During the installation process, you may be prompted possibly multiple times to reboot the server to install a critical component.
Note You may need to re-enter your data in order to resume the installation. You must provide the Computer Name of the publisher server. IP addresses or fully qualified DNS names are not allowed. You must not enter periods. This error message displays when you install Cisco CallManager on the subscriber server and do not provide the publisher database server name.
See this document for the Cisco CallManager product key. This message displays when you do not enter a password, but the application requires a password for the installation to occur.
This error message displays when you enter a password more than one time, but the password that you enter does not match the password on the server. You must enter a phrase from 1 to 15 characters in length. The installation has detected pending file operations. You must reboot the server before continuing. The installation will now abort. You must log in by using local Administrator user name and password to install Cisco CallManager. You did not log into the server with the local Administrator user name and password.
You do not have administrator privileges. You must have administrator privileges to install Cisco CallManager. Windows Server is not installed. Upgrade to Windows Service Pack 4 or later is not installed.
Review the Cisco CallManager installation logs to determine cause of failure, take appropriate action. For more information refer, to the Cisco CallManager installation documents. Uninstall this version of JRE from the server and rerun the installation. To continue the installation, you must disable or stop any anti-virus protection, intrusion detection software, and other third-party applications, and then rerun the installation program.
Installation detected a version of JRE that is not compatible or a version that may not have all necessary components installed. Cisco CallManager requires the server to be rebooted to continue the installation. If you have installed intrusion detection or anti-virus protection software, you must stop and disable these applications from the Services Control console before you continue with the Cisco CallManager installation.
All other installed third-party applications must be uninstalled before proceeding with the Cisco CallManager installation. Failure to follow these directives could result in un-recoverable errors. Would you like to proceed? Use the ccmsetup. The installation detected that the server exists in a domain.
When a server exists in a domain, authentication between servers may fail, or the non-default domain security policies may be so restrictive that the Cisco CallManager installation cannot build critical NT Accounts during an upgrade. If server is not removed from the domain and added to a workgroup, upgrade errors, upgrade failures, or a total system failure, which includes a loss of data and a complete reinstallation of Cisco CallManager, could result. Before you continue the installation, Cisco strongly recommends that you remove all servers in the cluster from the domain.
This release of Cisco CallManager is not supported on this server model. The installation program does not have enough disk space on the C drive to complete the installation. The installation program requires that you have 3.
Make at least 3. You do not have enough disk space on the C drive of your server to install Cisco CallManager. This setting interferes with the Cisco CallManager installation. Please disable this setting using the Local Security Policy utility, reboot, and rerun the Cisco CallManager installation. Disable this setting by using the Local Security Policy utility, reboot, and rerun the Cisco CallManager installation.
This package is for upgrades of existing Cisco CallManager installations only. Use the disks that came with the software kit to install Cisco CallManager. This message displays when you attempt to install a previous version of Cisco CallManager after a successful installation of a later version.
Cisco CallManager install did not complete successfully. Review the log file for more information. You did not copy all the files that came with the Cisco CallManager installation package to the server.
Copy the complete installation package to the server, and rerun the Cisco CallManager installation. This message displays if you encounter a media problem; insert the disk again. This message displays when you attempt to install the same version of Cisco CallManager again after a successful installation. Aborting Cisco CallManager installation. This error only occurs if you have manually modified this value.
Current OS version does not meet minimum requirements. Aborting Cisco CallManager install. This version of Cisco CallManger requires Cisco-provided operating system version Refer to Cisco Compatibility Matrix to review which versions are compatible for installation.
Install will now abort. Cisco does not support Terminal Services for Cisco CallManager installations, upgrades, or configuration tasks. Failure occurred during the Cisco Directory installation. Failure occurred during the Cisco CallManager installation. Please look at the Cisco CallManager installation log file for details. The Cisco CallManager installation detected an error while copying files.
Stop all platform agents and Cisco-verified applications and restart the installation. For more information, refer to the Upgrading Cisco CallManager document. Stop all platform agents and Cisco-verified applications, and restart the installation. For more information, see the "Performing Preinstallation Tasks" section. During the subscriber server installation, one of the following errors occurred:. The password of [X] does not match the password on the publisher [servername].
For details, review the log file [Z]. Whether you will install all cluster nodes in a single location, or if you will install your nodes in separate geographic sites connected via a WAN in order to provide geographic redundancy. Refer to the following table for a description of each option. The IM and Presence cluster shares a platform and many of the same services as the telephony cluster.
This option requires a 1x1 mapping of telephony clusters to IM and Presence clusters. For touchless installations, you can install all Unified Communications Manager and IM and Presence Service cluster nodes in a single process. The IM and Presence Service central cluster is installed separately from your telephony cluster and may be located on completely different hardware servers. This deployment removes the 1x1 mapping requirement between telephony clusters and IM and Presence clusters.
This allows you to scale your telephony deployment and IM and Presence deployment separately. Install a local Unified Communications Manager publisher node in the central cluster. This node is not a part of your telephony deployment.
The node handles functions like database and user provisioning for the central cluster. For touchless installations, you can install your local Unified Communications Manager publisher node and your IM and Presence Service central cluster in a single process. However, your telephony cluster must be installed separately. The following sections provide information about the requirements that your system must meet, and limitations that apply when you install or upgrade Unified Communications Manager or IM and Presence Service serivce.
The IM and Presence Service Service upgrade process automatically updates these entries on the Unified Communications Manager cluster during the final stages switch version of the upgrade process. For upgrades from Release 8. If such failures occur, you must restart the entire upgrade process for both Unified Communications Manager and IM and Presence Service Service clusters.
If you upgrade Unified Communications Manager which has IPsec configured using a certificate-based authentication with self-signed certificate, then the upgrade fails. To perform a successful upgrade, you have to reconfigure the IPsec policy with a CA-signed certificate. Ensure that the security password length is minimum 14 characters before you upgrade to FIPS, Common Criteria, or Enhanced Security mode on the cluster.
Update the password even if the prior version was FIPS enabled. Unified Communications Manager The Simplified Upgrade Cluster upgrade, reboot, and switch version feature is supported only in Unified Communications Manager version 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. A complete collaboration solution relies on DNS in order to function correctly for a number of services and thus requires a highly available DNS structure in place. You must configure the server to use static IP addressing to ensure that the server obtains a fixed IP address.
Using a static IP address also ensures that Cisco Unified IP Phones can register with the application when you plug the phones into the network. Note the following requirements:. Mixed-mode DNS deployments not supported—Cisco does not support mixed-mode deployments. Ensure that you configure your firewall so that connections to port 22 are open, and are not throttled.
During the installation of IM and Presence subscriber nodes, multiple connections to the Unified Communications Manager publisher node are opened in quick succession. Throttling these connections could lead to a failed installation. In this release, you cannot install or run Unified Communications Manager and the IM and Presence Service directly on server hardware; you must run these applications on virtual machines. Before you can install or upgrade the software on a virtual machine, you must:.
This section provides information about the platform requirements that you must meet before you can deploy Unified Communications Manager and the IM and Presence Service on virtual machines. IM and Presence Service Service A version mismatch is not supported.
However, the telephony cluster that the central cluster connects to does not have to be running a You cannot install or use third-party or Windows-based software applications.
The system can upload and process only software that Cisco Systems approves. You must perform all software installations and upgrades using Cisco Unified Communications Operating System Administration.
During the installation, you must specify the following usernames and passwords:. Administrator Account user name and password.
You use the Administrator Account user name and password to log in to the following areas:. To specify the Administrator Account user name and password, follow these guidelines:. Administrator Account user name—The Administrator Account user name must start with an alphabetic character and can contain alphanumeric characters, hyphens and underscores. Administrator Account password—The Administrator Account password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.
You can change the Administrator Account password or add a new Administrator account by using the command line interface. When you install Unified Communications Manager, you must enter an Application User name and password.
You use the Application User name and password to access applications that are installed on the system, including the following areas:. To specify the Application User name and password, follow these guidelines:.
Application User username - The Application User username must start with an alphabetic character and can contain alphanumeric characters, hyphens, and underscores. Application User password - The Application User password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.
Do not use the system application name as the Application User name. Using a system application name causes the installation to fail with an unrecoverable error during the installation of the database. You can change the Application User name and password by using the command line interface. During the installation, you must specify a security password.
Unified Communications Manager systems use this password to authorize communications between nodes in the cluster, including IM and Presence Service nodes. This password must be identical on all nodes in the cluster. The Security password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.
The installation wizard ensures that you enter a strong password. To create a strong password, follow these recommendations:. Remember that longer passwords are stronger and more secure than shorter ones. Avoid the following types of passwords:.
Do not use recognizable words, such as proper names and dictionary words, even when combined with numbers. Do not use word or number patterns, such as aaabbb, qwerty, zyxwvuts, , and so on. Do not use recognizable words from other languages. Do not use personal information of any kind, including birthdays, postal codes, names of children, or pets, and so on. The entire installation process, excluding pre- and post-installation tasks, takes 45 to 90 minutes, depending on your server type.
The entire IM and Presence installation process, excluding pre- and post-installation tasks, takes approximately 45 to 90 minutes per server, depending on your server type. 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. 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:. When you install either Unified Communications Manager or the IM and Presence Service on a server, the installation process requires you to provide specific information. You can provide this information manually during the installation process or you can provide it using an answer file.
For each server that you install in a cluster, you must gather this information before you begin the installation process. The following table lists the information that you must gather before you begin the installation. Because some of the fields are optional, they may not apply to your configuration.
For example, if you decide not to set up an SMTP host during installation, the parameter still displays, but you do not need to enter a value. You cannot change some of the fields after the installation without reinstalling the software, so be sure to enter the values that you want. The last column in the table shows whether you can change a parameter after installation, and if you can, it provides the appropriate menu path or Command Line Interface CLI command.
We recommend that you make copies of this table and record your entries for each server in a separate table, even if you are planning to use the DMABackupInfo. Administrator Credentials. Specifies the name that you want to assign to the Administrator account.
After installation, you can create additional administrator accounts, but you cannot change the original administrator account user ID. CLI: set password user admin. Application User Credentials. Specifies the user ID for applications installed on the system. Servers in the cluster use the security password to communicate with one another. Set this password on the Unified Communications Manager publisher node, and enter it when you install each additional node in the cluster, including IM and Presence nodes.
You can change the security password on all nodes in the cluster using the following command:. CLI: set web-security [orgunit] [orgname] [locality] [state] [country]. CLI: set web-security [orgunit] [orgname] [locality] [state]. Specifies the name of the SMTP host that is used for outbound email. You must fill in this field if you plan to use electronic notification.
If not, you can leave it blank. NIC Interface Settings. Virtual machines do not support this command. The MTU setting must be the same on all nodes in a cluster. The maximum transmission unit MTU represents the largest packet, in bytes, that this host will transmit on the network. The value must not exceed the lowest MTU size that is configured on any link in your network.
CLI: set network mtu [size]. Yes; for Unified Communications Manager nodes, choose one of the following:. CLI: set network hostname. The subnet mask together with the IP address defines the network address and the host address. The subnet mask must use the following format: CLI: set network dns primary [address].
CLI: set network dns secondary [address]. Represents the name of the domain in which this machine is located.
0コメント