Note You need to restart Cisco Tomcat service after you have installed language file from a disk. However, you can use the navigation controls in the administration interface. Expand Tools menu and select Service Management.
Step 4 In the Source list, select Remote Filesystem. Step 5 In the Directory field, enter the path of the folder that contains the language file on the remote system. If the language file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the folder path. Step 6 In the Server field, enter the server name or IP address.
Step 7 In the User Name field, enter your user name on the remote server. Step 8 In the User Password field, enter your password on the remote server. Step 9 In the Transfer Protocol list, select the applicable option. Step 10 Select Next. Step 11 Select the language that you want to install, and select Next. Step 12 Monitor the progress of the download. Note If you loose your connection with the server or close your browser during the installation process, you may see the following message when you try to access the Software Upgrades menu again:.
Warning: Another session is installing software, click Assume Control to take over the installation. If you are sure you want to take over the session, select Assume Control. Step 13 If you want to install another language, : Select Install Another , and repeat all the above steps. Step 14 If you are finished with installing languages: Restart the services:. Step 1 Sign in to the command line interface as a platform administrator.
Note Make sure to stop Connection Conversation Manager and Connection Mixer services before uninstalling the languages. Step 2 Run the show cuc locales CLI command to display a list of installed language files. Step 3 In the command results, find the language that you want to remove, and note the value of the Locale column for the language. When the command completes, the following information appears:. Skip to content Skip to search Skip to footer. Book Contents Book Contents.
Find Matches in This Book. Updated: March 8, Download and deploy the OVA template to create a new virtual machine. For more information, see the Creating a Virtual Machine section. Migrating the Unity Connection server on the virtual machine. If Unity Connection is installed as a standalone server, restore the software component from the physical server to the virtual machine for which you have taken the back up. Optional Install new languages on the replaced server if required or remove the existing languages already installed on the server.
Replacing a Publisher Server While you are upgrading the publisher server in a Unity Connection cluster, the subscriber server continues to provide services to the users and callers. On the Cluster Management page, from the Server Manager menu, locate the subscriber server and check the following: If the subscriber server status is Primary, skip the remaining steps in this procedure.
If the subscriber server status is Secondary, select Make Primary. If the subscriber has Deactivated status, change the status to Secondary and then select Activate. When prompted to confirm changing the server status, select OK. After successful activation of the subscriber server, change the status to Primary selecting Make Primary option. Step 2 Manually change the status of publisher server to Deactivated: a.
Return to the Cluster Management page of Cisco Unity Connection Serviceability and do any one of th following: If no voice messaging ports are currently handling calls for the publisher server, move to the next Step 3. If there are voice messaging ports that are currently handling calls for the publisher server, on the Cluster Management page, in the Port Manager column, select Stop Taking Calls for the publisher server and then wait until RTMT shows that all the ports for the publisher server are idle.
Step 4 Configure the cluster on the replaced publisher server: a. On the Cluster Management page, from the Server Manager menu, locate the publisher server and check the following: If the publisher server status is Primary, skip the remaining steps in this procedure.
If the publisher server status is Secondary, change the status by selecting Make Primary. If the publisher has Deactivated status, change the status to Secondary and select Activate. A prompt appears to confirm the changing of the server status, select OK. After successful activation of the publisher server, change the status to Primary by selecting Make Primary option.
Step 2 Manually change the status of subscriber server to Deactivated: a. If no voice messaging ports are currently handling calls for the server, skip to the next step.
If there are voice messaging ports that are currently handling calls for the subscriber server, on the Cluster Management page, in the Change Port Status column, select Stop Taking Calls for the subscriber server and then wait until RTMT shows that all ports for the server are idle.
Recreate the virtual machine. Restore the software. Replace the Publisher server, see the Replacing a Publisher Server section. Replace the publisher server, see Installing the Publisher Server section. Restore the software components on the physical machine. Configure cluster on the publisher sever: — Replace the subscriber server, see the Installing the Subscriber Server section.
When you change the IP address or hostname of the Unity Connection server, make sure to apply the same changes on all the associated components that refer the Unity Connection server by IP address or hostname: 2.
Bookmarks on client computers to the following web applications: Web applications, such as Cisco Personal Communications Assistant and Cisco Unity Connection Administration. Caution If associated components reference the Unity Connection server by IP address and if you do not change the IP address as applicable, the components will no longer be able to access Unity Connection. Unity Connection provides the delete dns, set network dns, and set network dns options commands that you can use to modify DNS settings.
Step 2 Check the server status: a. Caution Re-adding a server to a Unity Connection site can be a time consuming process. Step 7 Applicable only when you change the IP address or Hostname of a standalone server or a cluster defined by an IP address Change the IP addresses of a standalone server or the publisher server in Connection Administration: a.
Caution In case of a cluster, you must sign in to the publisher sever and select subscriber server to change the IP address or Hostname of a subscriber server. Select Save Step 8 On the standalone or publisher server, change the IP address, Hostname, and default gateway if applicable : a. Then download the certificate signing request to the server on which you installed Microsoft Certificate Services or another application that issues certificates, or download the request to a server that you can use to send the certificate signing request to an external certification authority CA.
In case of SSL certificates created and installed on renamed server Upload the root certificate and the server certificate to the standalone or publisher server. Caution After saving the page, node services will restart automatically. If Unity Connection is installed as a cluster and subscriber is not functioning. Install the subscriber server, see the Installing the Subscriber Server section.
If both the servers are not functioning in a cluster. Replace the publisher server, see Installing the Publisher Server section. Restore the software components on the physical machine. Configure cluster on the publisher sever:. Replace the subscriber server, see the Installing the Subscriber Server section. Check the cluster status using CLI command show cuc cluster status. Synchronize MWIs on each phone system. Before changing the IP address of a standalone Unity Connection server or a cluster, you need to determine whether the server is defined by hostname or IP address.
You can also use Cisco Prime Collaboration Deployment for readdressing. You need to select Cluster even if you want to change the IP address or hostname of a standalone server. Select Find to locate the server of which you need to change the IP address or hostname:. When you change the IP address or hostname of the Unity Connection server, make sure to apply the same changes on all the associated components that refer the Unity Connection server by IP address or hostname:.
Bookmarks on client computers to the following web applications:. If associated components reference the Unity Connection server by IP address and if you do not change the IP address as applicable, the components are no longer be able to access Unity Connection. Do not change the IP address or hostname of a Unity Connection server during business hours. Instead, you must do one of the following:.
To change the IP address or hostname of a Unity Connection cluster, follow the steps mentioned in the Changing the IP Address or Hostname of a Unity Connection Server section first on the publisher server and then on the subscriber server. In case of a cluster, follow the steps first on the publisher server and then on the subscriber server.
Sign in to the standalone server or the publisher server using Real-Time Monitoring Tool. In the Systems tab, make sure the ServerDown is black. If ServerDown is red, then resolve all the problems and change it to black. On the Cluster Management page, check whether server status is Primary or Secondary. If there is any other status value then resolve the problem. Backup the database using Disaster Recovery System.
Re-adding a server to a Unity Connection site can be a time consuming process. Update both the forward A and reverse PTR records. Applicable only when you change the IP address or Hostname of a standalone server or a cluster defined by an IP address or Hostname Changing the IP addresses or Hostname of a standalone server or the publisher server in Connection Administration:.
In case of a cluster, you must sign in to the publisher sever and select subscriber server to change the IP address or Hostname of a subscriber server. On the standalone or publisher server, change the IP address, Hostname, and default gateway if applicable :. If you want an alternate hostname for the server, run the set web-security CLI command.
In the Hostname, change the hostname of the server. Enter a certificate signing request. Then download the certificate signing request to the server on which you installed Microsoft Certificate Services or another application that issues certificates, or download the request to a server that you can use to send the certificate signing request to an external certification authority CA.
In case of SSL certificates created and installed on renamed server Upload the root certificate and the server certificate to the standalone or publisher server. If you are moving the server to a different subnet that requires a new default gateway address, change the value of the Default Gateway field in the Gateway Information. After saving the page, node services will restart automatically.
Restarting services ensures the proper update for the changes to take effect. Do not perform any action on the server until the services are up and running.
To check the status of the services, run utils service list CLI command. If you change the IP address or Hostname of a standalone server, skip to Step Sign in to Real-Time Monitoring Tool and confirm that the server is available and running. For the cluster, repeat Step 1 to Step 9 on subscriber server also. After installing a new server or on an existing server, you may need to add some new language s and remove some already installed languages depending on the user requirement.
Languages are not licensed and Unity Connection However, the more languages you install, the less hard disk space is available for storing voice messages. Do the following tasks to download and install languages in addition to English United States :. Download the Unity Connection languages that you want to install and do the following steps:.
Sign in as a registered user on the following Cisco. On the Select a Release page, select the applicable Unity Connection version. The download links for the languages appear on the right side of the page. Select the name of a file to download. On the Download Image page, note down the MD5 value and follow the on screen prompts to complete the download. Make sure that the MD5 checksum matches the checksum that is listed on Cisco. If the values do not match, the downloaded file is damaged.
Do not attempt to use a damaged file to install software as the results is unpredictable. If the MD5 values do not match, download the file again until the value for the downloaded file matches the value listed on Cisco. Unity Connection cluster only Make sure that the subscriber server status is Primary and the publisher server status is Secondary in order to install the Unity Connection languages.
Follow the given steps:. If you are using additional languages because you want the Cisco Personal Communications Assistant to be localized: Download and install the corresponding Unity Connection locales on the publisher server. Unity Connection cluster only Change the publisher server status to Primary and follow the same steps on subscriber server to install the same Unity Connection languages that were installed on publisher server.
However, you can use the navigation controls in the administration interface. Expand Tools menu and select Service Management. In the Source list, select Remote Filesystem. In the Directory field, enter the path of the folder that contains the language file on the remote system. If the language file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the folder path. In the Server field, enter the server name or IP address.
In the User Name field, enter your user name on the remote server. In the User Password field, enter your password on the remote server. In the Transfer Protocol list, select the applicable option. If not renamed the mentioned notification templates gets replaced with default notification templates of release Before upgrading to Unity Connection Release 14, make sure the display name of default notification devices is not changed for any of the user.
If changed then update notification devices to the default name. To check the users whose default notification device name is changed, execute below query:. Initiate a pre upgrade test before starting the upgrade process using the CLI command. For successful upgrade of Unity Connection from The Exchange , , , is end of support now. Therefore, it is recommended to delete the Unified Messaging Service configured with Exchange or or or while upgrading to Unity Connection Release 14 or later.
Now, create a new Unified Messaging Service with supported Exchange version or to avoid any issues while using Unified Messaging Services. If you are performing upgrade with FIPS enabled Unity Connection Release to 14 and later, you must consider the below limitations for a successful upgrade:. 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 are upgrading Unity Connection which has IPsec configured using a certificate-based authentication with self-signed certificate, then you must reconfigure the IPsec policy with a CA-signed certificate foe a successful upgrade.
NTLM web authentication mode is no longer supported. Do the following tasks to upgrade an Unity Connection server:. If you are already running the current version on a virtual server, make sure it is compatible with the upgraded version. If you are upgrading during non business hours, run the following command on the standalone server or the publisher server to speed up the upgrade process:.
If you are upgrading during a maintenance window, you can speed up the upgrade by disabling the throttling. This decreases the time required to complete the upgrade but affects Unity Connection performance. Upgrade the subscriber server following the steps mentioned in the Upgrading the Unity Connection Server section. The server automatically switches to the new version after completing the upgrade.
Switch to the upgraded software first on the publisher server and then on the subscriber server following the steps mentioned in the Switching to the Upgraded Version of Unity Connection Software section. Confirm that publisher server has Primary status and subscriber server has Secondary status. If you are performing an upgrade from a FIPS enabled Unity Connection Release to Unity Connection 14, make sure to follow the steps for regenerating certificates before using any pre-existing telephony integrations.
Verify that the value entered in X. In case of a cluster, you must configure the HTTPS ciphers on publisher server and restart the Tomacat service on each node to reflect the changes. SLO does not close all the running sessions at the same time.
The COP file will run a series of tests to check the pre-upgrade health and connectivity of your system. If the COP file highlights issues that need to be addressed, fix them before proceeding with the upgrade. After sucessful upgrade it is recommended to run Post Upgrade COP file to verify the configuration of system. Applicable to In the Source field, select any one of the following:.
Remote Filesystem : Select this option to upgrade from remoter server and follow this procedure. In the Directory field, enter the path of the folder that contains the upgrade file. In the Server field, enter the server name or IP address. In the User Name field, enter the alias that is used to sign in to the remote server. In the User Password field, enter the password that is used to sign in to the remote server. In the Transfer Protocol field, select the applicable transfer protocol.
Select the upgrade version that you want to install and select Next. The upgrade file is copied to the hard disk of the Unity Connection server. When the file is copied, a screen displaying the checksum value appears.
Warning: Another session is installing software, click Assume Control to take over the installation. To continue monitoring the upgrade, select Assume Control. During the initial phase of upgrade, the Installation Log text box in Cisco Unified Operating System Administration is updated with the information on the progress of the upgrade. To confirm the completion of upgrade, open the console of the Unity Connection server and make sure that a message indicating the completion of upgrade appears on the screen along with the login prompt.
The upgraded Unity Connection version is in the inactive partition and old version is in the active partition. This command should display the message for successful upgrade along with the upgraded version. After completing the upgrade process, you need to manually switch over to the upgraded version of Unity Connection. For a single Unity Connection server, you can select either manual switch version or automatic switch version. You can perform the switch version running the CLI command utils system switch-version.
The system automatically reboots after the switch version. If you select not to automatically switch to the upgraded partition at the end of the upgrade, do the following procedure when you are ready to switch partitions.
From the Settings menu, select Version. On the Version Settings page, select Switch Versions , to start the following activities:. Data from the active partition is copied to the inactive partition.
Note that the messages are stored in a common partition, therefore they are not copied. The Unity Connection server restarts and switches to the newer version. Copy the Cisco Option Package. If you are upgrading the subscriber server in a Unity Connection cluster, type the following address to access Cisco Unified Operating System Administration:. In the Directory field, enter the path to the folder that contains the.
If the. For example, if the. In the Transfer Protocol field, select the applicable transfer protocol and select Next. When the file is copied, a screen displays the checksum value. During the upgrade, the value of the Status field is Running. When the upgrade process is complete, the value of the Status field changes to Complete.
After upgrading the Unity Connection version, you can rollback to the software version that was running before the upgrade by switching to the software version on inactive partition. You can revert a single Unity Connection server or a cluster to the version on inactive partition. To rollback a Unity Connection cluster, you should rollback both the servers, first the publisher and then the subscriber.
After the successful rollback of both the publisher and subscriber servers, reset the replication between the two servers running the following CLI commands:. Stop the replication on subscriber server with the CLI command utils dbreplication stop. Stop the replication on publisher server with the CLI command utils dbreplication stop.
Reset the replication running the CLI command utils dbreplication reset all on the publisher server. After the reset of replication between the two servers, check the cluster status running the CLI command show cuc cluster status utils system restart on both publisher and subscriber.
From the Settings menu, select Version and the Version Settings window displays. Select the Switch Versions option. After you confirm that you want to restart the system, the system restarts that might take up to 15 minutes. Follow the given steps to confirm that the switch version is successful:.
Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book 2. Updated: October 27,
0コメント