Installation Guide for Cisco Unity Connection Release 10.x
Overview of Mandatory Tasks For Installing Unity Connection 10.x
Downloads: This chapterpdf (PDF - 388.0KB) The complete bookPDF (PDF - 641.0KB) | Feedback

Table of Contents

Overview of Mandatory Tasks for Installing a Cisco Unity Connection 10.x System

Version 10.x Installation Scenarios

Requirements for Installing Unity Connection 10.x

Important Considerations for Installing Version 10.x

Version 10.x Pre-Installation Tasks

Frequently Asked Questions About the Version 10.x Installation

How Much Time Does the Installation Require?

What User Names and Passwords Do I Need to Specify?

What Is a Strong Password?

Which Servers Does Cisco Support for this Installation?

Create the Virtual Machine Using vSphere Client

May I Install Other Software on the Server?

Browser Requirements for Version 10.x

Changing the Boot Order of the Unity Connection 10.x Virtual Machine

Changing Reservations on Virtual Machines When Running with E7 Processors

Changing Reservations on Virtual Machines When Running with E5440 Processors

Verifying DNS Registration for the 10.x Installation

Gathering Information for an 10.x Installation

Migrating to Unity Connection on a Virtual Machine

Version 10.x Installation Scenarios

Unity Connection 10.x has the following installation options:

  • Standard Installation- This option allows you to install Unity Connection10.x from the

installation disc.

  • Unattended Installation- This option allows you to use a pre-configured virtual floppy image in

addition to the installation disc.


Note Unity Connection 10.0(1) and later can only be installed on virtual machines.


For Standalone (single) server installation, follow the given steps:

Standard Installation

Unattended Installation

For High Availability (Two Nodes) or Cluster Setup, follow the given steps:

Standard Installation

Unattended Installation


Caution If you are installing both the publisher and subscriber servers on virtual machines, you must use the same VMware configuration for both servers.


Note When you install Unity Connection 10.x in a standalone configuration, the ELM server also gets installed on the same system. Similarly, in a co-resident configuration, the ELM server gets installed with the Unity Connection 10.x and call manger on the same system. The username and password for the ELM server is same as the username and password of Cisco Unity Connection Administration. For more information on the ELM server, refer to ELM user guide at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/elmuserguide/9_0_1/CUCM_BK_E596FD72_00_enterprise-license-manager-user-90.html.


Requirements for Installing Unity Connection 10.x


Note If you are installing Unity Connection 10.x as part of Cisco Unified Communications Manager Business Edition 6000, all content in the Unity Connection 10.x documentation set applies to Business Edition 6000 except the following:

• Content that references Connection version 10.x only.

• Content that references Cisco Unified Communications Manager Business Edition only.


 

1. Verify the following requirements:

a. System requirements for the Unity Connection 10.x system. See System Requirements for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html .


Caution To determine whether your virtual machine requires a memory upgrade, see the link below: http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unity_Connection.

b. Requirements for integrating the phone system(s). See the “Requirements” section of the applicable Cisco Unity Connection integration guide(s) at http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.html .

2. If you are using languages other than English-United States: Download the additional Unity Connection language files for the installation. See the “Version 10.x Post-Installation Tasks” section in the “Post- Installation Tasks and Installing Additional Languages on the Unity Connection 10.x Server” chapter of this guide. (This task list alerts you when to install the language files later in the installation.)

3. Installing Unity Connection on a virtual machine:


Note Information on downloading a VMware OVA template appears in the Release Notes for Cisco Unity Connection for versions 10.x.


  • Provision the physical host on which virtual machine will be created for installing Unity Connection, according to the “Requirements for Installing a Cisco Unity Connection Virtual Machine” section in System Requirements for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html .
  • Deploy the template, which creates a virtual machine and configures it.
  • In the VMware vSphere client, configure the virtual disks that are assigned to Unity Connection virtual machine in independent- persistent mode. This provides the best storage performance.
  • On the virtual machine, change the BIOS setting so the virtual machine boots first from the DVD virtual device, then from the virtual hard disk. See the “Changing the Boot Order of the Unity Connection 10.x Virtual Machine” section.

4. In case of cluster, install the publisher server following the above steps. Once the publisher sever has been completely setup, install the subscriber server. From now on, the information and settings that you enter on the publisher server are replicated to the subscriber server.

5. If you are using languages other than English-United States: Install the additional Unity Connection language files. See the “Installing Unity Connection 10.x Language Files” section in the “Post- Installation Tasks and Installing Additional Languages on the Unity Connection 10.x Server” chapter of this guide.

If you installed Japanese and you want Cisco Unity Connection Administration to be localized: Download and install the Cisco Unified Communications Manager Japanese locale. See the “Locale Installation” section in the “Software Upgrades” chapter of the applicable Cisco Unified Communications Operating System Administration Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html .


Note If you are installing Japanese language for Unity Connection, then install, uc-locale-ja_JP-10.0.1-xx.cop.sgn, the default Japanese cop file. However, if you are installing Japanese language for Unity Connection SRSV, then make sure to install, uc-locale-SRSV-ja_JP-10.0.1-xx.cop.sgn, the SRSV specific Japanese cop file.


6. If you want to install Cisco Unity Connection Survivable Remote Site Voicemail (SRSV) server: Run the CLI command utils cuc activate CUSRSV to convert standalone Unity Connection server to Unity Connection SRSV server.


Note The unrestricted version of Unity Connection SRSV works only with the unrestricted version of Cisco Unity Connection (central) server.



Caution All manually added database entries are lost after running the above CLI command.

Warning After installing Unity Connection SRSV , you can not revert to Unity Connection.

If you installed additional languages and you want the Cisco Personal Communications Assistant to be localized: Download and install the corresponding Cisco Unified Communications Manager locales. See the “Locale Installation” section in the “Software Upgrades” chapter of the Cisco Unified Communications Operating System Administration Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html .

7. Configure the browser(s) on administrator workstations to access Cisco Unity Connection web applications. See the “Configuring the Browser on a Cisco Unity Connection 10.x Administrator Workstation” chapter of the System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/administration/guide/10xcucsagx.html .

8. Download and install the Real-Time Monitoring Tool software on administrator workstations. See the “Installing and Configuring Real-Time Monitoring Tool” chapter of the Cisco Unified Real-Time Monitoring Tool Administration Guide at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.


Note Cisco Unity Connection SRSV can not be installed on a cluster, therefore, a branch can only be made on a Unity Connection without a cluster. For more information, see SRSV guide at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/srsv/guide/10xcucsrsv020.html.


9. For specific features to be configured on Unity Connection, see the following guides:

10. If any users will use an IMAP email client to access or send Unity Connection messages: Configure settings for IMAP client access to the Unity Connection server. See the “Configuring IMAP Settings in Cisco Unity Connection 10.x” chapter of the System Administration Guide .

11. If any users will have access to the Unity Connection web tools or will use an IMAP email client to access or send Unity Connection messages: If you have not done so already as part of Task 10. , secure Cisco PCA and IMAP access to Unity Connection. See the “Securing Cisco PCA and IMAP Email Client Access to Cisco Unity Connection” section in the “Configuring SSL in Cisco Unity Connection 10.x” chapter of the System Administration Guide .

12. If any users will be configured for unified messaging features: Configure unified messaging. See the applicable chapters in the Unified Messaging Guide for Cisco Unity Connection . Unified messaging features include:

  • Access to Exchange email by using text to speech (TTS).
  • Access to Exchange calendar and contacts.
  • Synchronization of Unity Connection and Exchange mailboxes (single inbox).
  • Announcements of MeetingPlace meetings.
  • MeetingPlace scheduling and joining.

SpeechView transcription, also a component of unified messaging, is discussed in a later task.

13. If any users will have access to calendar information or to Exchange contacts: Configure the integration. See the “Creating Calendar and Contact Integrations in Cisco Unity Connection” chapter of the System Administration Guide .

14. If any users will use text to speech to access their Exchange email messages: Configure access to Exchange. See the “Configuring Text-to-Speech Access to Exchange Emails in Cisco Unity Connection 10.x” chapter of the System Administration Guide .

15. If any users will have access to the SpeechView voice message transcription feature: Configure the transcription service. See the “Configuring Transcription (SpeechView) in Cisco Unity Connection 10.x” chapter of the System Administration Guide .

16. If any users will be using HTML, SMTP, or SMS message notification devices: Enable the system to send SMTP or SMS notification messages. See the “Setting Up HTML, SMTP, and SMS (SMPP) Message Notifications in Cisco Unity Connection 10.x” chapter of the System Administration Guide .

17. If any users will have access to their Unity Connection voice messages through a Cisco Unified client application: Configure the applicable client:

18. If any users will have access to faxes: Configure the Cisco Fax Server integration. See the “Creating a Cisco Fax Server Integration in Cisco Unity Connection 10.x” chapter of the System Administration Guide .

19. If any administrators or users will have access to the Cisco Unity Connection Broadcast Message Administrator: Set it up. See the “Setting Up Broadcast Messaging in Cisco Unity Connection 10.x” chapter of the System Administration Guide .

20. If any administrators or users will need access to the Cisco Unity Greetings Administrator to manage greetings over the phone: Set it up. See the “Setting Up the Cisco Unity Greetings Administrator” section in the “Managing Recorded Greetings and Recorded Names in Cisco Unity Connection 10.x” chapter of the System Administration Guide .

21. For any additional features and functionality that you have not yet provided, customize individual user account settings as needed. See the “Setting Up Features and Functionality That Are Controlled by User Account Settings in Cisco Unity Connection 10.x” and “Setting Up Features and Functionality That Are Controlled by Class of Service in Cisco Unity Connection 10.x” chapters of the User Moves, Adds, and Changes Guide .

22. Set up networking, if applicable. See the “Overview of Networking Concepts in Cisco Unity Connection 10.x” chapter of the Networking Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/networking/guide/10xcucnetx.html .

23. Set up access to the Cisco PCA. See the “Setting Up Access to the Cisco Personal Communications Assistant in Cisco Unity Connection 10.x” chapter.

24. Set up Media Master playback and recording devices. See the “Setting Up Playback and Recording Devices for the Media Master in Cisco Unity Connection 10.x” chapter.

25. Set up ViewMail for Outlook. See the applicable documentation:

26. Set up Cisco Unity Connection ViewMail for IBM Lotus Notes. See the applicable Release Notes for Cisco Unity Connection ViewMail for IBM Lotus Notes at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .

27. Set up the email client to view images in the HTML-based email notifications. See the "Configuring Cisco Unity Connection 10.x for HTML-based Message Notification” section.

28. Set up the access to Cisco Unity Connection Mini Web Inbox. See the “Configuring Cisco Unity Connection 10.x for Cisco Unity Connection Mini Web Inbox” section.

29. Set up IMAP email accounts to access Unity Connection voice messages. See the “Configuring an Email Account to Access Cisco Unity Connection 10.x Voice Messages” chapter.

30. Confirm that users are able to access and use the Unity Connection features that have been enabled for them.

31. See the Disaster Recovery System Administration Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/drs_administration/guide/10xcucdrsag.html .


Note Third-party backup applications are not supported.


32. Train users, operators, and support desk personnel to use the Cisco Unity Connection system. See the “User Orientation in Cisco Unity Connection 10.x” and “Operator and Support Desk Orientation in Cisco Unity Connection 10.x” chapters of the User Workstation User Setup Guide .

Important Considerations for Installing Version 10.x

Before you proceed with the installation, consider the following requirements and recommendations:


Note Unity Connection 10.0(1) and later can only be installed on virtual machines.


  • Be aware that when you install on an existing server, the hard drive gets formatted, and all existing data on the drive gets overwritten.
  • Ensure that you connect each Cisco Unity Connection server to an uninterruptible power supply (UPS) to provide backup power 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 Cisco Unity Connection software on the publisher server first and then on the subscriber server.

When you enter the Security password on the publisher server, write it down and save it. You must enter the same password on the subscriber server.

After both servers in the cluster have been installed, confirm that the subscriber server can connect to the publisher server.

Install the software during off-peak hours or a maintenance window to avoid impact from interruptions.

Both servers in the cluster must run the same release of Cisco Unity Connection. The only exception is during a cluster software upgrade, during which a temporary mismatch is allowed.

  • Configure the server by using static IP addressing to ensure that the server obtains a fixed IP address.
  • Do not attempt to perform any configuration tasks during the installation.
  • Do not install any Cisco-verified applications until you complete the installation.
  • Be aware that directory names and filenames that you enter while you are running the installation program are case-sensitive.
  • Carefully read the information that follows before you proceed with the installation.

Version 10.x Pre-Installation Tasks

Table 1-1 contains a list of pre-installation tasks that you need to perform to ensure that you can successfully install Cisco Unity Connection.

Table 1-1 Version 10.x Pre-Installation Tasks

Task
Important Notes

Step 1

Read this entire document to familiarize yourself with the installation procedure.

Step 2

Verify the integrity of any new server hardware (such as hard drives and memory) by running any manufacturer-provided utilities.

Step 3

Ensure that your servers are listed as supported hardware and sized appropriately to support the load of the cluster.

For information about the capacity of server models, see the Cisco Unity Connection 10.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/supported_platforms/10xcucspl.html .

Make sure to account for any growth that has occurred since initial system configuration.

Step 4

Create the Virtual Machine using the correct OVA template

For more information, see Create the Virtual Machine Using vSphere Client

Download the OVA template from:

http://software.cisco.com/download/release.html? mdfid=283062758&flowid=31846&softwareid=

282074348&release=OVA-9.1&relind=AVAILA

BLE&rellifecycle=&reltype=latest

Step 5

For a Unity Connection cluster, if you are getting the system time from an NTP server, verify that the publisher server can synchronize with the NTP server before you install the subscriber server.

To verify the NTP status of the publisher server, log into the Command Line Interface on the publisher server and enter the following command:

utils ntp status

For more information, see the Command Line Interface Reference Guide for Cisco Unified Solutions .


Caution If the publisher server fails to synchronize with an NTP server, installation of a subscriber server can also fail.

Step 6

For a Unity Connection cluster, do not run Network Address Translation (NAT) or Port Address Translation (PAT) between the publisher and subscriber servers.

Step 7

Record the network interface card (NIC) speed and duplex settings of the switch port to which you will connect the new server.

You should configure the same NIC settings on the server and on the switch port. For GigE (1000/FULL), you should set NIC and switch port settings to Auto/Auto; do not set hard values.

Enable PortFast on all switch ports that are connected to Cisco servers. With Portfast enabled, the switch immediately brings a port from the blocking state into the forwarding state by eliminating the forwarding delay [the amount of time that a port waits before changing from its Spanning-Tree Protocol (STP) learning and listening states to the forwarding state].

Step 8

If you use DNS, verify that all servers on which you plan to install Cisco Unity Connection are properly registered in DNS.

For more information, see the “Verifying DNS Registration for the 10.x Installation” section.

Step 9

Obtain a Cisco Unity Connection license file.

For more information, see the “Managing Licenses in Cisco Unity Connection 10.x” chapter of the System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/
connection/10x/administration/guide/10xcucsagx.html
.

Step 10

Record the configurations settings for each server that you plan to install.

To record your configuration settings, see Table 1-1 .

Step 11

Configure a Unity Connection cluster on the publisher server before you install the second (subscriber) server.

For more information, see the “Configuring a Cisco Unity Connection 10.x Cluster” chapter of the Cluster Configuration and Administration Guide for Cisco Unity Connection at http://www.cisco.com/
en/US/docs/voice_ip_comm/connection/10x/
cluster_administration/guide/10xcuccagx.html
.

Frequently Asked Questions About the Version 10.x Installation

The following section contains information about commonly asked questions and responses. Review this section carefully before you begin the installation.

How Much Time Does the Installation Require?

The entire installation process, excluding pre- and post-installation tasks, takes 45 to 90 minutes, depending on your server type.

What User Names and Passwords Do I Need to Specify?


Note The system checks your passwords for strength. For guidelines on creating a strong passwords, see the “What Is a Strong Password?” section.


During the installation, you must specify the following user names and passwords:

  • Administrator Account user name and password
  • Application User name and password
  • Security password

Administrator Account User Name and Password

You use the Administrator Account user name and password to log in to the following areas:

  • Cisco Unified Communications Operating System Administration
  • Disaster Recovery System
  • Command Line Interface

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. For more information, see the Command Line Interface Reference Guide for Cisco Unified Solutions .

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:

  • Cisco Unity Connection Administration
  • Cisco Unified Serviceability
  • Cisco Unified Real-Time Monitoring Tool

To specify the Application User name and password, follow these guidelines:

  • Application User name—The Application User name 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.

You can change the Application User name and password by using the command line interface. For more information, see the Command Line Interface Reference Guide for Cisco Unified Solutions .


Note • Make sure you do not use the following application usernames as this will generate an error:

CCMSysUser

WDSysUser

CCMQRTSysUser

IPMASysUser

WDSecureSysUser

CCMQRTSecureSysUser

IPMASecureSysUser

TabSyncSysUser

CUCService

Security Password

When clustering is configured, the system uses this password to authorize communications between the publisher and subscriber servers; you must ensure that this password is identical on both servers.

The Security password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.

What Is a Strong Password?

The installation wizard checks to ensure that you enter a strong password. To create a strong password, follow these recommendations:

  • Mix uppercase and lowercase letters.
  • Mix letters and numbers.
  • Include hyphens and underscores.
  • 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 invert recognizable words.
  • Do not use word or number patterns, like aaabbb, qwerty, zyxwvuts, 123321, 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.

Which Servers Does Cisco Support for this Installation?

For information about supported servers, see the Cisco Unity Connection 10.x Supported Platforms List at http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unity_Connection


Note Unity Connection 10.0(1) and later can only be installed on virtual machines.


Create the Virtual Machine Using vSphere Client

Download the OVA templates to create virtual machines from the link given below:

http://software.cisco.com/download/release.html?mdfid=283062758&flowid=31846&softwareid=28204348&release=OVA-9.1&relind=AVAILABLE&rellifecycle=&reltype=latest

Use the following procedure to create the VM:


Step 1 To deploy the OVA template in vSphere client. Go to file> deploy OVF template.

Step 2 Next, select the OVA template from the URL or file.

Step 3 Follow the deployment instructions to create virtual machine in vSphere client.

May I Install Other Software on the Server?

You must do all software installations and upgrades by using Cisco Unified Communications Operating System Administration. The system can upload and process only software that Cisco approved. You cannot install or use unapproved third-party or Windows-based software applications.

Browser Requirements for Version 10.x

You can access Cisco Unified Serviceability, Cisco Unified Communications Operating System Administration, and Disaster Recovery System by using the following browsers:

  • Microsoft Internet Explorer version 6.x or version 7.x
  • Netscape Navigator version 7.1 or later

For current browser requirements for accessing Cisco Unity Connection Administration and Cisco Unity Connection Serviceability, see the “Software Requirements—Administrator Workstations” section of System Requirements for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html .

Changing the Boot Order of the Unity Connection 10.x Virtual Machine

Do the following procedure to change the BIOS setting so the virtual machine boots first from the DVD virtual device, then from the virtual hard disk.

To Change the Boot Order of the Cisco Unity Connection 10.x Virtual Machine


Step 1 In VMware vSphere Client, power off the virtual machine on which you deployed the OVA template.

Step 2 In the left pane of vSphere Client, right-click the name of the virtual machine, and select Edit Settings .

Step 3 In the Virtual Machine Properties dialog box, select the Options tab.

Step 4 In the Settings column, under Advanced, select Boot Options .

Step 5 Under Force BIOS Setup, check the The Next Time the Virtual Machine Boots, Force Entry into the BIOS Setup Screen check box.

Step 6 Click OK to close the Virtual Machine Properties dialog box.

Step 7 Power on the virtual machine.

The virtual machine will boot into the BIOS menu.

Step 8 Navigate to the Boot menu and change the boot device order so the CD-ROM device is listed first and the Hard Drive device is listed second.

Step 9 Save the change and exit BIOS setup.


 

Changing Reservations on Virtual Machines When Running with E7 Processors

With 8.6(2) and later releases, the CPU reservations are now included in OVA’s. The reservation numbers for CPU are based on the Xeon 7500 processor. If the customer chooses to run on the E7 processor, the CPU reservation numbers are higher than available cycles on 1 virtual CPU.

Based on the lab tests, we know that the 2.4 GHz E7 processor has the same performance as a 2.53GHz Xeon 7500 processor. Therefore, it is fine to change the reservation numbers on the virtual machine manually when running them on the E7 processors for 5000, 10,000, or 20,000 deployment options.

For more on the reservations for the E7 processor, see the docwiki available at http://docwiki.cisco.com/wiki/OVA_Template_Details_for_Unity_Connection_Release_8.6.2 .

To Change the Reservation Value of the Cisco Unity Connection 8.6(2) or Later Virtual Machine


Step 1 In VMware vSphere Client, select the host on which virtual machine is created.

Step 2 Click the Summary tab, under CPU chores, note the available CPU cycles for 1 virtual CPU in GHz.

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 5 In the Virtual Machine Properties dialog box, select the Resources tab.

Step 6 In the Settings column, select CPU.

Step 7 Under Resource Allocation, enter the new reservation value in the Reservation textbox. The new reservation value will be calculated as number of CPUs multiply by the 1 virtual CPU cycles in GHz (from step 2).

Step 8 Click OK to close the Virtual Machine Properties dialog box.

Step 9 Power on the virtual machine.


 

Changing Reservations on Virtual Machines When Running with E5440 Processors

With 8.6(2) and later releases, the CPU reservations are now included in OVA's. The reservation numbers for CPU are based on the Xeon 7500 processor. If the customer chooses to run on the E5440 processor, the CPU reservation numbers are higher than available cycles on 1 virtual CPU.

Based on the lab tests, we see that the 2.4 GHz reservation on E5540 processor has the same performance as a 2.53GHz Xeon 7500 processor. Therefore, it is fine to change the reservation numbers on the virtual machine manually when running them on the E5440 processors for 5000, 10,000, or 20,000 deployment options.

For more on the reservations for the E5440 processor, see the docwiki available at

http://docwiki.cisco.com/wiki/OVA_Template_Details_for_Unity_Connection_Release_8.6.2 .

To Change the Reservation Value of the Cisco Unity Connection 8.6(2) or Later Virtual Machine


Step 1 In VMware vSphere Client, select the host on which virtual machine is created.

Step 2 Power off the virtual machine on which you deployed the OVA template

Step 3 In the left pane of vSphere Client, right-click the name of the virtual machine, and select Edit Settings

Step 4 In the Virtual Machine Properties dialog box, select the Resources tab.

Step 5 In the Settings column, select CPU.

Step 6 Under Resource Allocation, enter the new reservation value in the Reservation textbox. The new reservation value will be calculated as number of CPUsX2.4GHz.

Step 7 Click OK to close the Virtual Machine Properties dialog box.

Step 8 Power on the virtual machine.


 

Verifying DNS Registration for the 10.x Installation

If you use DNS, verify that all servers to be added are registered in DNS properly by performing the following actions:

Procedure


Step 1 Open a command prompt.

Step 2 To ping each server by its DNS name, enter ping DNS_name .

Step 3 To look up each server by IP address, enter nslookup IP_address .


 

Gathering Information for an 10.x Installation

Use Table 1-1 to record the information about your server. Gather this information for a Unity Connection server that is not in a Unity Connection cluster, or for each Unity Connection server that you are installing in a cluster. You may not need to obtain all the information; gather only the information that is pertinent to your system and network configuration. You should make copies of this table and record your entries for each server in a separate table.


Note Because some of the fields are optional, they may not apply to your configuration. For example, if you choose not to set up an SMTP host during installation, the parameter still displays, but you do not need to enter a value.



Caution You cannot change some of the fields after 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 field after installation, and if you can, it provides the appropriate Command Line Interface (CLI) command.


Caution If you are installing Cisco Unity Connection on a virtual machine, changing some of the values listed in Table 1-1 after installation will require you to obtain updated licenses. For more information, see the “Managing Licenses in Cisco Unity Connection 10.x” chapter of the System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/administration/guide/10xcucsagx.html.

 

Parameter
Description
Can Entry Be Changed After Installation?

Administrator ID

This field specifies the administrator account user ID that you use for secure shell access to the CLI, for logging into Cisco Unified Communications Operating System Administration and for logging into the Disaster Recovery System.

No, you cannot change the entry after installation.

Note After installation, you can create additional administrator accounts, but you cannot change the original administrator account user ID.

Your entry:

Administrator Password

This field specifies the password for the Administrator account, which you use for secure shell access to the CLI, for logging into Cisco Unified Communications Operating System Administration and for logging into the Disaster Recovery System.

Ensure the password is at least six characters long; it can contain alphanumeric characters, hyphens, and underscore.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set password user admin

Your entry:

Application User Name

You use the Application User name as the default user name for applications that are installed on the system, for example, Cisco Unity Connection Administration and Cisco Unity Connection Serviceability.

Yes, you can change the entry after installation by using Cisco Unity Connection Administration.

Your entry:

Application User Password

You use the Application User password as the default password for applications that are installed on the system, for example, Cisco Unity Connection Administration and Cisco Unity Connection Serviceability.

Yes, you can change the entry after installation by using the following CLI command:

CLI > utils cuc reset password

Your entry:

Country

From the list, choose the appropriate country for your installation.

No, you cannot change the entry after installation.

Your entry:

DHCP

If you want to use DHCP to automatically configure the network settings on your server, choose Yes .

If you choose Yes , you do not get prompted for DNS or static configuration settings.

If you choose No , you must enter a hostname, IP Address, IP Mask, and Gateway.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set network dhcp

Your entry:

DNS Enable

A DNS server resolves a hostname into an IP address or an IP address into a hostname. If you do not have a DNS server, enter No.

If you have a DNS server, Cisco recommends that you enter Yes to enable DNS.

Note When DNS is not enabled, you should only enter IP addresses (not host names) for all network devices.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set network dns

Your entry:

DNS Primary

Enter the IP address of the DNS server that you want to specify as the primary DNS server. Enter the IP address in dotted decimal format as ddd.ddd.ddd.ddd.

Consider this field mandatory if DNS is set to yes (DNS enabled).

Yes, you can change the entry after installation by using the following CLI command:

CLI > set network dns

Your entry:

DNS Secondary (optional)

Enter the IP address of the DNS server that you want to specify as the optional secondary DNS server.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set network dns

Your entry:

Domain

This field represents the name of the domain in which this machine is located.

Consider this field mandatory if DNS is set to yes.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set network domain

Your entry:

Gateway Address

Enter the IP address of the network gateway.

If you do not have a gateway, you must still set this field to 255.255.255.255. Not having a gateway may limit you to only being able to communicate with devices on your subnet.

If DHCP is set to No, consider this field mandatory.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set network gateway

Your entry:

Hostname

Enter a host name that is unique to your server.

The host name can comprise up to 64 characters and can contain alphanumeric characters and hyphens. The first character cannot be a hyphen.

If DHCP is set to No, consider this field mandatory.

Yes, you can change the entry after installation.

For information, see the “Renaming Cisco Unity Connection 10.x Servers” chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/
voice_ip_comm/connection/10x/
upgrade/guide/10xcucrugx.html
.

Your entry:

IP Address

Enter the IP address of your server.

If DHCP is set to No, consider this field mandatory.

Yes, you can change the entry after installation.

For information, see the “Changing the IP Addresses of Cisco Unity Connection 10.x Servers” chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/
voice_ip_comm/connection/10x/
upgrade/guide/10xcucrugx.html
.

Your entry:

IP Mask

Enter the IP subnet mask of this machine.

If DHCP is set to No, consider this field mandatory.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set network ip eth0

Your entry:

Location

Enter the location of the server.

The system uses this information to generate certificate signing requests (CSRs), which are used to obtain third-party certificates.

You can enter any location that is meaningful within your organization. Examples include the state or the city where the server is located.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set web-security

Your entry:

MTU Size

The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network.

Enter the MTU size in bytes for your network.

The MTU size that you configure must not exceed the lowest MTU size that is configured on any link in your network.

Default: 1500 bytes

The MTU setting must be the same on both servers in a cluster.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set network mtu

Your entry:

NIC Duplex

Choose the duplex mode for the network interface card (NIC), either Full or Half.

Note This parameter only displays when you choose not to use Automatic Negotiation.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set network nic

Your entry:

NIC Speed

Choose the speed for the NIC, either 10 megabits per second or 100 megabits per second.

Note This parameter only displays when you choose not to use Automatic Negotiation.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set network nic

Your entry:

NTP Server

Enter the hostname or IP address of one or more network time protocol (NTP) servers with which you want to synchronize.

You can enter up to five NTP servers.

Note To avoid potential compatibility, accuracy, and network jitter problems, the external NTP servers that you specify for the primary node should be NTP v4 (version 4). If you are usingIPv6 addressing, external NTP servers must be NTP v4.

Yes, you can change the entry after installation by using the Cisco Unified Communications Operating System:

Settings > NTP Servers

Your entry:

Organization

Enter the name of your organization.

Tip You can use this field to enter multiple organizational units. To enter more than one organizational 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. Note The value you enter gets used to generate a Certificate Signing Request (CSR).

Yes, you can change the entry after installation by using the following CLI command:

CLI > set web-security

Your entry:

Security Password

Servers in the cluster use the security password to communicate with one another.

The password must contain at least six alphanumeric characters. It can contain hyphens and underscores, but it must start with an alphanumeric character.

Note Save this password. For a Cisco Unity Connection cluster, you will be asked to enter the same security password for both the publisher and subscriber servers.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set password user security


Caution When a Unity Connection cluster is configured, to avoid losing communications between the publisher and subscriber servers, you must change the Security password on both servers and reboot both servers. For more information, see the description of this command in the Command Line Interface Reference Guide for Cisco Unified Solutions.

Your entry:

SMTP Location

Enter the hostname or IP address for the SMTP server that is used for outbound e-mail.

The hostname can contain alphanumeric characters, hyphens, or periods, but it must start with an alphanumeric character.

Note You must fill in this field if you plan to use electronic notification.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set smtp

Your entry:

State

Enter the state where the server is located.

Note The value you enter gets used to generate a Certificate Signing Request (CSR).

Yes, you can change the entry after installation by using the following CLI command:

CLI > set web-security

Your entry:

Time Zone

This field specifies the local time zone and offset from Greenwich Mean Time (GMT).

Choose the time zone that most closely matches the location of your machine.


Caution In a cluster, the subscriber server must be configured to use the same time zone as the publisher server.

Yes, you can change the entry after installation by using the following CLI command:

CLI > set timezone

Your entry:

Unit

Enter your unit.

Note The value you enter gets used to generate a Certificate Signing Request (CSR).

Yes, you can change the entry after installation by using the following CLI command:

CLI > set web-security

Your entry:

Migrating to Unity Connection on a Virtual Machine

For information on migrating to Cisco Unity Connection on a virtual machine, see the “Migrating from a Cisco Unity Connection Physical Server to a Connection 10.x Virtual Machine” chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrugx.html .