Continue with Step 4. To disable automatic negotiation, select No. Continue with Step 3. If you select to disable automatic negotiation, manually select the appropriate NIC speed and duplex settings now and select OK to continue. The maximum transmission unit MTU represents the largest packet, in bytes, that is transmitted by this host on the network.
If you are unsure of the MTU setting for your network, use the default value. To accept the default value bytes , select No.
Static IP addresses are recommended. The installation process attempts to verify network connectivity. If you want to configure static IP addresses for the server, select No.
The Static Network Configuration window displays. After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays. Enter the location and login information for the remote file server. The system connects to the remote server and retrieves a list of available upgrade patches. If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path.
If the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax, including:. The Install Upgrade Patch Selection window displays. Select the upgrade patch to install.
The system downloads, unpacks, and installs the patch and then restarts the system with the upgraded software version running. After the system restarts, the Pre-existing Configuration Information window displays. To continue the installation, select Proceed. The Platform Installation Wizard window displays.
To continue the installation, select Proceed or select Cancel to stop the installation. If you select Proceed , the Apply Patch window displays. Continue with Step If you select Cancel , the system halts, and you can safely power down the server. Select Continue in the window to install the software version on the DVD or configure the pre- installed software and move to Step 7 of the Installing the Publisher Server section.
Before you can upgrade from a local disk, you must download the appropriate patch file from Cisco. When the Local Patch Configuration window displays, enter the patch directory and patch name, if required, and select OK.
The window displays the patch file that is available on the DVD. To update the system with this patch, select Continue. The system installs the patch, then restarts the system with the upgraded software version running.
After the system restarts, the Preexisting Configuration Information window displays. Continue with Step 6. After the installation application has finished, the new server displays its hostname and the administration account login prompt.
Log in with the administration account user name and password. Verify that server network services are running:. At the CLI prompt, enter the command utils service list. It might take a few minutes for all services to start completely.
During this time, you might notice that services might be listed as [Starting]. Repeat the utils service list command until all network services are listed as [Started]. In particular, the Cisco Tomcat service must be started before you can proceed to the next verification step.
Open a web browser on a personal computer that has network access to the server. Login to Cisco Unified OS Administration using the administrator user name and password specified during the installation. Use the Show menu to check:. Cluster : displays the IP address, hostname, alias, server type, and database replication status of the single server or both the server in case of cluster. Hardware : platform type, serial number, hardware, and other options.
Network : current network interface configuration, status, and packets. Software : current active and inactive software partitions. The Cisco Unity Connection Administration window opens. Select Cisco Unity Connection Serviceability from the navigation pane.
Login using the application user name and password specified during the installation. It lists the server status of either single server or both the servers in case of cluster. For a standalone server deployment, the server shows Primary status whereas in case of cluster, one of the server shows Primary status and the other shows Secondary status. All the existing Unity Connection configurations are lost after running the conversion.
After installing Unity Connection on your server, you should perform the following additional tasks before configuring the system for your application:. Obtain the licenses for the Unity Connection server. For more information, see the Managing Licenses chapter. You can change the passwords using either the Cisco Unity Connection Administration web application, or you can log into the server and run the CLI command.
If you require additional languages, install them. Optional : You can configure RTMT to send alert notifications through emails to the specified email address.
Configure the backup settings. Follow the steps in this section to troubleshoot issues faced during installation.
To obtain a list of install log files from the command line, enter. To view the log file from the command line, enter. For more information on troubleshooting installation issues, see the Troubleshooting Guide for Cisco Unity Connection Release Skip to content Skip to search Skip to footer.
Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book 2. Updated: July 1, Chapter: Installing Cisco Unity Connection. Note Unity Connection Methods of Installation You can use either of the following methods to install standalone or cluster server: Standard Installation: Allows you to manually specify the installation information, such as hostname and IP address using installation wizard.
Note You can also perform fresh installation of Unity Connection For a Unity Connection cluster: Install the Unity Connection software first on the publisher server and then on the subscriber server applicable to only standard installation scenarios. Pre-Installation Tasks Before installing a Unity Connection server, you need to understand all the pre-installation steps as well.
Table 1. Pre-Installation Tasks Task Important Notes Step 1 Ensure that your servers are listed as supported hardware and sized appropriately to support the load of the cluster. Step 2 Create the virtual machine using the correct OVA template. Caution If the publisher server fails to synchronize with an NTP server, installation of a subscriber server can also fail.
Step 5 Record the network interface card NIC speed and duplex settings of the switch port that connects to the new server. Step 6 Record the configurations settings for each server that you plan to install. Step 7 Download the signed. Step 3 Follow on-screen instructions to create the virtual machine. Step 2 In the left pane of VMware client, right-click the name of the virtual machine, and select Edit Settings.
Step 7 Power on the virtual machine. In such cases, the administrator needs to change the reservation number of the virtual machine manually using the steps mentioned in Changing Reservation Numbers Additionally, based on the lab tests, we see that the 2.
Step 3 Power off the virtual machine on which you deployed the OVA template Step 4 In the left pane of vSphere Client, right-click the name of the virtual machine and select Edit Settings. Step 7 Under Resource Allocation, enter the new reservation value in the Reservation textbox.
Step 9 Power ON the virtual machine. Gathering Information for Installation Use the Table to record the information about your server. Table 2. Caution In a cluster, you must set the subscriber server to the same time zone as the publisher server. Caution Make sure not to use ciscounity in the hostname of the server else enterprise replication gets broken. Note Unity Connection enables the use of a domain name server to locate other Cisco Unity servers and devices.
Note Ensure the password is at least six characters long; it can contain alphanumeric characters, hyphens, and underscore. Login: No. Tip To enter more than one business unit name, separate the entries with a comma. Table 4. Note If you select media check and it fails, either download another copy from Cisco. Step 3 In the Proceed with Install window, select Yes to continue the installation. Caution If you select Yes on the Proceed with Install window, all existing data on your hard drive gets overwritten and destroyed.
Step 4 In the Platform Installation Wizard window, select the applicable option: If you want to perform a standard installation, select Proceed , and continue with this procedure. Step 5 If you select Proceed in the previous window, the Apply Patch window appears: Select Yes to upgrade to a later Service Release of the software during installation and follow the process mentioned in the Applying a Patch section.
Step 6 In the Basic Install window, select Continue to install the software version or configure the pre- installed software. Step 7 In the Timezone Configuration window, select the appropriate time zone for the server and then select OK. Caution In a cluster, the subscriber server must be configured to use the same time zone as the publisher server. Caution If you configure the MTU size incorrectly, your network performance can be affected. Step 11 In the Static Network Configuration window, enter the static network configuration information.
Step 13 Enter the administrator login and password. The Certificate Information window appears. Step 14 Enter your certificate signing request information and select OK. Step 15 In the First Node Configuration window, select the applicable option: Select Yes to configure this server as the publisher server or as a standalone server and continue this procedure. Note Cisco recommends that you use an external NTP server to ensure accurate system time on the publisher server.
Step 17 In the Security Configuration window, enter the security password. Note The system uses this password to authorize communications between the publisher and subscriber servers; you must ensure this password is identical on the two servers. Step 19 In the Application User Configuration window: Enter the Application User name and password and confirm the password by entering it again. Note Do not use the system application name as the Application User name.
Step 21 When the installation process completes, you are prompted to log in using the Administrator account and password. Step 22 Complete the post-installation tasks listed in the Post-Installation Tasks section. Step 2 Expand System Settings and select Cluster. Step 6 In the Description field, enter a description for the second server and select Save.
Installing the Subscriber Server To install the subscriber server, follow the steps of installing publisher server until the First Node Configuration window appears and then continue the following procedure. Step 2 During installation of a subscriber server, the system checks to ensure that the subscriber server can connect to the publisher server. Step 3 Enter the connectivity information for the publisher server and select OK.
Note If the network connectivity test fails, the system stops and allows you to go back and re-enter the parameter information. Step 5 Select OK to start installing the software. Step 6 When the installation process completes, you are prompted to log in using the Administrator account and password. In case of Unity Connection cluster: You need to generate separate answer files for publisher and subscriber servers. Task List for Unattended Installation Task List for Unattended Installation You need to perform the following tasks to generate answer file and create floppy image for unattended installation.
Step 2 Enter details in the Clusterwide Configuration section. Step 3 Enter details for the primary node in the Primary Node Configuration section. Step 4 Optional If you want to enable Dynamic Cluster Configuration, enter a value in the Dynamic-cluster-config-timer field. Note Step 4 is mandatory when you are using Dynamic-cluster-configuration process for Touchless installation.
Step 5 Enter details for the secondary node in the Secondary Node Configuration section. Step 7 Click Generate Answer Files. Step 8 In the Communications Answer File Generator dialog box, follow the download instructions, and then click the Download File button to download the answer files to your computer. Configuring the Publisher Server Procedure Step 1 Log in to the virtual machine to start the cluster installation.
Step 3 From the available hardware list, select Floppy drive 1. Step 4 In the Device Type section, select Use the existing floppy image in the database, and then click Browse to navigate to the floppy image.
Step 5 Click OK. The floppy image is attached. Step 7 Optional If you want to test the media before the installation, click OK in the Disc Found message box, or select Skip to skip testing the media before the installation. Configuring the Subscriber Server Procedure Step 1 You can install the subscriber only after the publisher is installed. Touchless Installation for Virtual Machine Touchless installation is an enhancement of the existing unattended installation, which promotes simplified cluster installation.
Automatic Sequencing of Touchless Server dynamic-cluster-configuration In automatic sequencing feature, subscriber gets configured dynamically along with the publisher during the installation. Task List for Touchless Installation You need to perform the following tasks to generate answer files and create floppy image for Touchless installation.
Note In case you are using dynamic-cluster-configuration method of installation, then you just need to enable dynamic-cluster-configuration option in the AFG tool and follow the step1. The installation of subscriber continues if: You enable the dynamic-cluster-configuration timer.
The clusterConfig. Step 3 You can use show network cluster CLI to check the entries in the processnode table. Applying a Patch You must obtain the appropriate upgrade file from Cisco. Note You can upgrade to any supported higher release if you have a full patch of the release not an Engineering Special ES. You may use one of these servers, but you must contact the vendor for support: Open SSH for Unix systems.
Step 2 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card NIC using automatic negotiation. 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, Chapter: Upgrading Cisco Unity Connection. The following are the two ways to switch to the new version: Automatic Switching: Allows you to automatically switch to the new version of Unity Connection as part of the upgrade process.
Table 1. Refresh Upgrade RU Examples of supported paths: You need the following COP files in same sequence as mentioned below before performing this upgrade: ciscocm. Examples of supported paths: Level 2 L2 You need the following COP file before performing this upgrade: ciscocm. Note If you are upgrading Unity Connection to 14 and later, then after completion of successful upgrade, you must reinstall the set of available locales that are compatible with the upgraded version.
Status of Unity Connection Cluster During an Upgrade When a Unity Connection cluster is upgraded, the publisher server is completely disabled for the entire duration of upgrade but the subscriber server continues to provide services to users and callers. However, the performance of the cluster is affected in the following ways: If the phone system is routing calls to the subscriber server, outside callers and Unity Connection users can leave voice messages but the messages are not immediately delivered to user mailboxes.
Duration of Upgrade Under ideal network conditions, an upgrade process takes approximately two hours to complete on each server. Tip You can reduce the duration of upgrade process by asking users to permanently delete items in the deleted items folder before starting the upgrade. Prerequisites for Upgrade Before beginning the upgrade process, you must consider the following points for a successful upgrade: Ensure that you have a good network connection to avoid service interruptions during upgrade.
Update the following virtual machine settings on both publisher and subscriber server through VMware vSphere client: Change the Guest Operating System version to match the requirements of Unity Connection Follow the given steps to confirm the server status in a cluster: Sign in to Cisco Unity Connection Serviceability.
Expand Tools and select Cluster Management. Check the server status in a cluster. In addition to this, confirm the running state of database replication using the CLI command show cuc cluster status. Note After confirming the status of publisher server as Primary and subscriber server as Secondary, start the upgrade process first on publisher server and then on subscriber server.
Caution For successful upgrade of Unity Connection from If you are upgrading Unity Connection to Release 14 with FIPS enabled and IPse configured, then you must perform any one of the given procedure for successful upgrade to Unity Connection 14 Delete the previously configured IPsec policies and perform the upgrade. Task list to Upgrade to Unity Connection Shipping Version 14 Do the following tasks to upgrade an Unity Connection server: If you are running the current version of Unity Connection on a physical server then you must replace it with a virtual server.
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: utils iothrottle disable If you are upgrading during a maintenance window, you can speed up the upgrade by disabling the throttling.
Caution You cannot disable throttling during the upgrade process. If you want to disable the throttling process, you must first stop upgrade, disable throttle, and restart the Unity Connection server. Once the server is active again, begin the upgrade process.
For more information, see the Migrating Licenses section. Follow the upgrade process on the standalone server: RU upgrades only Upgrade the server by performing the steps mentioned in the Upgrading the Unity Connection section. In particular, the Cisco Tomcat service must be started before you can proceed to the next verification step.
Step 3 Verify the server details:. Open a web browser on a personal computer that has network access to the server. Login to Cisco Unified OS Administration using the administrator user name and password specified during the installation. Use the Show menu to check:. Step 4 Verify the server status:. The Cisco Unity Connection Administration window opens.
Select Cisco Unity Connection Serviceability from the navigation pane. Login using the application user name and password specified during the installation. It lists the server status of either single server or both the servers in case of cluster. For a standalone server deployment, the server shows Primary status whereas in case of cluster, one of the server shows Primary status and the other shows Secondary status.
After installing Unity Connection on your server, you should perform the following additional tasks before configuring the system for your application:. For more information, see the Managing Licenses chapter. You can change the passwords using either the Cisco Unity Connection Administration web application, or you can log into the server and run the CLI command.
Optional : You can configure RTMT to send alert notifications through emails to the specified email address. Follow the steps in this section to troubleshoot issues faced during installation. To obtain a list of install log files from the command line, enter. For more information on troubleshooting installation issues, see the Troubleshooting Guide for Cisco Unity Connection Release Skip to content Skip to search Skip to footer. Book Contents Book Contents.
Find Matches in This Book. Updated: March 8, Chapter: Installing Cisco Unity Connection. Cluster Deployment: Involves the installation of same version of two Unity Connection servers in an active-active or high availability mode. During the installation of Unity Connection as a cluster, the first server is referred to as publisher server and the second server as the subscriber server. For more information on cluster configuration, see the Configuring Cisco Unity Connection Cluster chapter.
Methods of Installation You can use either of the following methods to install standalone or cluster server: Standard Installation: Allows you to manually specify the installation information, such as hostname and IP address using installation wizard.
Unattended Installation: Allows you to install Unity Connection using an installation disk and a pre-configured answer file floppy diskette. The answer file has all the information required for unattended installation. With Unity Connection The subscriber installation continues when the publisher is successfully installed. This type of unattended installation is Touchless Installation.
The answer file supports only fresh installs and does not support upgrades. Be aware that when you install on an existing Unity Connection server, the hard drive gets formatted and all existing data on the drive gets overwritten.
Ensure that you connect each Unity Connection server to an uninterruptible power supply UPS to provide power backup and protect your system. Failure to do so may result in damage to physical media and require a new installation. For a Unity Connection cluster: — Install the Unity Connection software first on the publisher server and then on the subscriber server applicable to only standard installation scenarios.
Do not perform any configuration changes during the installation. Be aware that the directory names and filenames that you enter during the installation are case-sensitive. Pre-Installation Tasks Before installing a Unity Connection server, you need to understand all the pre-installation steps as well. Table Pre-Installation Tasks Task Important Notes Step 1 Ensure that your servers are listed as supported hardware and sized appropriately to support the load of the cluster. Step 2 Create the virtual machine using the correct OVA template.
Caution If the publisher server fails to synchronize with an NTP server, installation of a subscriber server can also fail. Step 5 Record the network interface card NIC speed and duplex settings of the switch port that connects to the new server. Step 6 Record the configurations settings for each server that you plan to install. Step 7 Download the signed. The virtual machine will boot into the BIOS menu. Step 3 Power off the virtual machine on which you deployed the OVA template Step 4 In the left pane of vSphere Client, right-click the name of the virtual machine and select Edit Settings.
Gathering Information for Installation Use the Table to record the information about your server. Caution In a cluster, you must set the subscriber server to the same time zone as the publisher server. Caution Make sure not to use ciscounity in the hostname of the server else enterprise replication will break. Login: No. Tip To enter more than one business unit name, separate the entries with a comma. For entries that already contain a comma, enter a backslash before the comma that is included as part of the entry.
Caution If you select Yes on the Proceed with Install window, all existing data on your hard drive gets overwritten and destroyed.
The Platform Installation Wizard window appears. Step 4 In the Platform Installation Wizard window, select the applicable option: If you want to perform a standard installation, select Proceed , and continue with this procedure. If you want to perform an unattended installation, select Skip. Connect the answer file image on a virtual floppy diskette and select Continue. The installation wizard will read the configuration information during the installation process and then follow the steps mentioned in the Post-Installation Tasks section.
Step 5 If you select Proceed in the previous window, the Apply Patch window appears: Select Yes to upgrade to a later Service Release of the software during installation and follow the process mentioned in the Applying a Patch section.
Select No to skip this step and the Basic Install window appears. Caution In a cluster, the subscriber server must be configured to use the same time zone as the publisher server. The replication will not work if the timezone is not same. Caution If you configure the MTU size incorrectly, your network performance can be affected.
The network restarts and the Administrator Login Configuration window appears. Select No to configure a static IP address for the server and continue with this procedure. The Static Network Configuration window appears. The Certificate Information window appears. The First Node Configuration window appears. Step 15 In the First Node Configuration window, select the applicable option: Select Yes to configure this server as the publisher server or as a standalone server and continue this procedure.
Select No to configure this server as the subscriber server. Step 19 In the Application User Configuration window: a. Installing the Subscriber Server To install the subscriber server, follow the steps of installing publisher server until the First Node Configuration window appears and then continue the following procedure. To pause the installation after the system successfully verifies network connectivity, select Yes.
To continue the installation, select No. The system checks for network connectivity. In case of Unity Connection cluster: You need to generate separate answer files for publisher and subscriber servers. You are not required to enter details of the publisher server manually on the subscriber server during subscriber server installation. Task List for Unattended Installation You need to perform the following tasks to generate answer file and create floppy image for unattended installation.
Touchless Installation for Virtual Machine Touchless installation is an enhancement of the existing unattended installation, which promotes simplified cluster installation. Automatic Sequencing of Touchless Server dynamic-cluster-configuration In automatic sequencing feature, subscriber gets configured dynamically along with the publisher during the installation.
Task List for Touchless Installation You need to perform the following tasks to generate answer files and create floppy image for Touchless installation. The installation of subscriber continues if: You enable the dynamic-cluster-configuration timer. The clusterConfig. Applying a Patch You must obtain the appropriate upgrade file from Cisco. Skip to the Upgrading from a Remote Server section. Continue with the Upgrading from a Local Disk section. You may use one of these servers, but you must contact the vendor for support: Open SSH for Unix systems.
To enable automatic negotiation, select Yes. To disable automatic negotiation, select No. Continue with Step 3.
To accept the default value bytes , select No. The installation process attempts to verify network connectivity. If you want to configure static IP addresses for the server, choose No. The Static Network Configuration window displays.
The Platform Installation Wizard window displays. Upgrading from a Local Disk Before you can upgrade from a local disk, you must download the appropriate patch file from Cisco. Verifying the Installation After the installation application has finished, the new server displays its hostname and the administration account login prompt.
To Verify the Installation Step 1 Log in with the administration account user name and password. The server opens a command line interface. Step 2 Verify that server network services are running: a. Step 3 Verify the server details: a. Use the Show menu to check: — Cluster: displays the IP address, hostname, alias, server type, and database replication status of the single server or both the server in case of cluster.
Caution All the existing Unity Connection configurations are lost after running the conversion. Post-Installation Tasks After installing Unity Connection on your server, you should perform the following additional tasks before configuring the system for your application: Obtain the licenses for the Unity Connection server. Optional Change the application passwords.
You can change the passwords using either the Cisco Unity Connection Administration web application, or you can log into the server and run the CLI command utils cuc reset password If you require additional languages, install them.
Activate Unity Connection feature services. Configure the backup settings. Troubleshooting Installation Issues Follow the steps in this section to troubleshoot issues faced during installation. Examine the log files if you encounter problems during installation.
Use the following commands in Command Line Interface to view log files. Was this Document Helpful? Yes No Feedback.
0コメント