The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Before you begin the installation, review the following information:
Make sure that the subscriber nodes that you are installing can connect to the publisher node server during the installation.
Make sure that all Cisco Unified Communications Manager servers in a cluster have the same software version. Make sure that all IM and Presence servers in a cluster have the same version of the released software. The only exception is during a cluster software upgrade, during which a temporary mismatch is allowed. If you are installing IM and Presence nodes, Cisco Unified Communications Manager and IM and Presence Service software versions must have the same major and minor release number.
Do not attempt to perform any configuration tasks during the installation.
Be aware that directory names and filenames that you enter while you are running the installation program are case-sensitive.
For a short period of time after you install Cisco Unified Communications Manager or switch over after upgrading to a different product version, settings changes made by phone users might get reset. Examples of phone user settings includes call forwarding and message waiting indication light settings. This can occur because Cisco Unified Communications Manager synchronizes the database after an installation or upgrade, which can overwrite phone user settings changes.
For instructions on how to navigate within the installation wizard, see the following table.
To Do This |
Press This |
---|---|
Move to the next field |
Tab |
Move to the previous field |
Alt-Tab |
Choose an option |
Space bar or Enter |
Scroll up or down in a list |
Up or down arrow |
Go to the previous window |
Space bar or Enter to choose Back (when available) |
Get help information on a window |
Space bar or Enter to choose Help (when available) |
Use the procedures in this section to begin the software installation.
To start the installation, follow this procedure.
Follow this procedure if you have a server that has the product pre-installed, or if you installed the product earlier but chose Skip in the Platform Installation Wizard window to configure the server at a later time.
Step 1 | After the system restarts, the Preexisting Installation Configuration window displays. | ||
Step 2 | If you have
preexisting configuration information that the Answer File Generator created,
that is stored on a USB key, insert the USB key now and choose
Continue. The installation wizard will read the
configuration information during the installation process.
The Platform Installation Wizard window displays. | ||
Step 3 | To continue with the Platform Installation Wizard, choose Proceed. | ||
Step 4 | In the Apply Additional Release window, choose one of the following installation types: | ||
Step 5 | In the Basic Install window, choose Continue. Perform the configure basic installation procedure to configure the basic installation. |
This option is available when you install Unified Communications Manager nodes. It is not available for IM and Presence nodes.
If you choose Yes in the Apply a Patch window, the installation wizard installs the software version that is on the DVD or ISO image first, and then restarts the system. You must obtain the appropriate upgrade file from Cisco.com before you can upgrade during installation.
Note | You can upgrade to any supported higher release, so long as you have a full patch, not an ES or an SR, in which case you can only upgrade to a later service release within the same maintenance release. |
For information about supported upgrades, see the Release Notes for your product release and the Cisco Unified Communications Manager Compatibility Matrix at http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html.
You can access the upgrade file during the installation process from an ISO image on a data store, a local disk (DVD), or from a remote FTP or SFTP server.
Step 1 | The Install Upgrade Retrieval Mechanism Configuration window displays. |
Step 2 | Choose the
upgrade retrieval mechanism to use to retrieve the upgrade file:
|
Before you can upgrade from a local source, you must download the appropriate patch file from Cisco.com. You must create an ISO image from the upgrade file and then either place it on a DVD or in the DVD drive of a virtual machine.
Step 1 | When the
Local
Patch Configuration window displays, enter the patch directory and
patch name, if required, and choose
OK.
The Install Upgrade Patch Selection Validation window displays. |
Step 2 | The window displays the patch file. To update the system with this patch, choose Continue. |
Step 3 | Choose the
upgrade patch to install. 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. |
Step 4 | To continue the
installation, choose
Proceed.
The Platform Installation Wizard window displays. |
Step 5 | To continue the
installation, choose
Proceed or choose
Cancel to stop the installation.
If you choose Proceed, the Apply Patch window displays. Continue with the next step. If you choose Cancel, the system halts, and you can safely power down the server. |
Step 6 | When the Apply Patch window displays, choose No. |
Step 7 | The Windows Upgrade window displays. |
Step 8 | Choose No and perform the procedure to configure the basic installation. |
Use this procedure to upgrade Unified Communications Manager nodes from a remote server. This option is not available for IM and Presence nodes.
Before you can upgrade Unified Communications Manager from a remote server, you must download the appropriate patch file from Cisco.com to an FTP or SFTP server that the server can access.
Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified version of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to http://www.cisco.com/pcgi-bin/ctdp/Search.pl. For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to http://www.globalscape.com/gsftps/cisco.aspx.Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:
Note | For issues with third-party products that have not been certified through the CTDP process, contact the third-party vendor for support. |
If you chose to upgrade through an FTP or SFTP connection to a remote server, you must first configure network settings so that the server can connect to the network.
Step 1 | Configure the
auto negotiation setting.
| ||
Step 2 | If you chose to
disable automatic negotiation, manually choose the appropriate NIC speed and
duplex settings now and choose
OK to continue.
The MTU Configuration window displays. | ||
Step 3 | In the
MTU
Configuration window, you can change the MTU size from the operating
system default.
The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value.
The DHCP Configuration window displays. | ||
Step 4 | For network configuration, you can choose to either set up static network IP addresses for the node and gateway or to use Dynamic Host Configuration Protocol (DHCP). Static IP addresses are recommended. If you use DHCP, use static DHCP. | ||
Step 5 | If you chose not
to use DHCP, enter your static network configuration values and choose
OK.
The DNS Client Configuration window displays. | ||
Step 6 | To enable DNS,
choose
Yes, enter your DNS client information, and choose
OK.
After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays. | ||
Step 7 | 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. For example, if the upgrade file is in the patches directory, you must enter /patches 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. | ||
Step 8 | Choose 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 Preexisting Configuration Information window displays. | ||
Step 9 | To continue the
installation, choose
Proceed.
The Platform Installation Wizard window displays. | ||
Step 10 | To continue
the installation, choose
Proceed or choose
Cancel to stop the installation.
If you choose Proceed, the Apply Patch window displays. Continue with the next step. If you choose Cancel, the system halts, and you can safely power down the server. | ||
Step 11 | In the
Apply
Patch window displays, choose
No.
The Windows Upgrade window displays | ||
Step 12 | Choose No and perform the configure basic installation procedure to configure the basic installation. |
Use the procedures in this section to configure the servers and complete the installation.
Step 1 | In the
Timezone Configuration window, choose the appropriate
time zone for the server and then choose
OK.
The Auto Negotiation Configuration window displays. | ||
Step 2 | The installation
process allows you to automatically set the speed and duplex settings of the
Ethernet network interface card (NIC) by using automatic negotiation. You can
change this setting after installation.
| ||
Step 3 | If you chose to
disable automatic negotiation, manually choose the appropriate NIC speed and
duplex settings now and choose
OK to continue.
The MTU Configuration window displays. | ||
Step 4 | In the
MTU
Configuration window, you can change the MTU size from the operating
system default.
The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value, which is 1500 bytes.
The DHCP Configuration window displays. | ||
Step 5 | For network configuration, you can choose to either set up a static network IP address for the node or to use Dynamic Host Configuration Protocol (DHCP). Static IP addresses are recommended. If you use DHCP, use static DHCP. | ||
Step 6 | If you chose not
to use DHCP, enter your static network configuration values and choose
OK.
The DNS Client Configuration window displays. | ||
Step 7 | To enable DNS,
choose
Yes, enter your DNS client information, and choose
OK.
The network restarts by using the new configuration information, and the Administrator Login Configuration window displays. | ||
Step 8 | Enter your
Administrator login and password.
The Certificate Information window displays. | ||
Step 9 | Enter your
certificate signing request information and choose
OK.
The First Node Configuration window displays. | ||
Step 10 | You can
configure this server as either the publisher node in a
Cisco Unified Communications
Manager cluster or as a subscriber node.
|
Follow this procedure to configure the first server where you install Cisco Unified Communications Manager software as the publisher node for the cluster. Perform this procedure after you have completed the basic installation and configured the basic installation.
Note | You can configure Smart Call Home on the publisher node only. For more information on Smart Call Home, refer to Smart call home section in the Cisco Unified Serviceability Administration Guide. |
Step 1 | The
Network
Time Protocol Client Configuration window appears.
Cisco recommends that you use an external NTP server to ensure accurate system time on the publisher node. Subscriber nodes in the cluster will get their time from the first node. | ||
Step 2 | Choose whether
you want to configure an external NTP server or manually configure the system
time.
The Database Access Security Configuration window appears. | ||
Step 3 | Enter the
Security password from Required Installation Information.
The SMTP Host Configuration window appears. | ||
Step 4 | If you want to
configure an SMTP server, choose
Yes and enter the SMTP server name. If you do not
want to configure the SMTP server, choose
No, which redirects to Smart Call Home page. To go
to previous page, choose
Back and to see the information about the SMTP
configuration, choose
Help.
| ||
Step 5 |
Choose
OK. The
Smart
Call Home Enable window appears.
| ||
Step 6 | On the Smart
Call Home Enable Page, perform one of the following.
| ||
Step 7 | Choose OK. The Application User Configuration window appears. | ||
Step 8 | Enter the Application User name and password from and confirm the password by entering it again. | ||
Step 9 | Choose OK. The Platform Configuration Confirmation window appears. | ||
Step 10 | To continue with
the installation, choose
OK; or to modify the platform configuration, choose
Back.
The system installs and configures the software. The server reboots. When the installation process completes, you are prompted to log in by using the Administrator account and password. |
Use the following procedure to configure a subscriber node in the cluster.
Before you configure subscriber nodes, you must associate each of the subscriber nodes in the cluster with its publisher node.
For more information, see the Cisco Unified Communications Manager Administration Guide.
Step 1 | If you
configured Network Time Protocol on the publisher node, ensure that it is
synchronized with an NTP server before you install a subscriber node. From the
Command Line Interface on the publisher node, enter
utils
ntp status. Ensure that the output indicates that the node is
synchronized with an NTP server.
| ||
Step 2 | On the First
Node Configuration window, read the Warning and make sure you have correctly
configured the first node as the publisher node. To continue with the
installation of the subscriber node, click
OK.
The Network Connectivity Test Configuration window displays. | ||
Step 3 | During
installation of a subscriber node, the system checks to ensure that the
subscriber node can connect to the publisher node.
The First Node Access Configuration window displays. | ||
Step 4 | Enter the
publisher node connectivity information and choose
OK.
The system checks for network connectivity. If you chose to pause the system after the system successfully verifies network connectivity, the Successful Connection to First Node window displays. Choose Continue.
The SMTP Host Configuration window displays. | ||
Step 5 | If you want to
configure an SMTP server, choose
Yes and enter the SMTP server name.
The Platform Configuration Confirmation window displays. | ||
Step 6 | To start installing the software, choose OK, or, if you want to change the configuration, choose Back. | ||
Step 7 | When the installation process completes, you get prompted to log in by using the Administrator account and password. |