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.
This section describes that tasks that you should perform before you begin the server or cluster replacement.
Step 1 | Verify the integrity of the new server hardware by running any manufacturer-provided utilities. |
Step 2 | Make sure that
the new servers are listed as supported hardware and sized appropriately to
support the load of cluster.
Refer to the following documentation for information about the capacity of server models:
Make sure to account for any growth that has occurred since initial system configuration. |
Step 3 | Verify that links between servers meet the delay requirements and that you have enough bandwidth to support database replication. For more information, refer to Cisco Unified Communications SRND Based on Cisco Unified Communications Manager. |
Step 4 | Record all
system passwords and account IDs.
See the Account Names and Passwords Record. You must enter identical passwords when configuring the replacement server. You cannot retrieve these passwords from the server. |
Step 5 | Make sure that you have a copy of all custom ring files, phone backgrounds, and music on hold sources. Consider this actions as precautionary because the restore is designed to restore these items. |
Step 6 | Obtain and store COP files for any locales that are installed on the server. You need to reinstall locales after doing the replacement. |
Step 7 | Do not change computer names or IP addresses, or add more nodes to the cluster. |
Step 8 | Verify the
integrity of your software downloads and DVDs.
Perform the following tasks: |
Step 9 | If your firewall is not in the routing path, disable the firewall between nodes, if possible. Also, increase the firewall timeout settings until after you complete the installation. It is not always sufficient to temporarily allow network traffic in and out of the nodes (for example, setting the firewall rule for these nodes to IP any/any). The firewall might still close necessary network sessions between nodes due to timeouts. |
Step 10 | Perform any system tests that you intend to perform after the replacement before the replacement also, to verify that the tests pass before you do the replacement. Document these tests, so you can perform them identically after doing the replacement. |
Step 11 | If you use DNS,
verify that all servers that are to be replaced are configured in DNS properly.
All nodes in the cluster must either use DNS or not use it.
See the Verify DNS Registration. |
Step 12 | Do not run Network Address Translation (NAT) or Port Address Translation (PAT) between Cisco Unified Communications Manager nodes. |
Step 13 | Record all the
registration information by using the
Cisco Unified Communications
Manager
Real Time Monitoring
Tool (RTMT).
See the Determine Registration Counts. You cannot perform this task if your old server is not working. |
Step 14 | Record all the
critical services and their activation status by using the
Cisco Unified Communications
Manager
Real Time Monitoring
Tool (RTMT).
See the Record Critical Services. You cannot perform this task if your old server is not working. |
Step 15 | Using the Syslog
viewer in the
Cisco Unified Communications
Manager
Real Time Monitoring
Tool (RTMT), locate any events that have a severity of Error or
higher.
Perform this task to ensure that no system-affecting errors exist on your system. See the Locate System Errors. You cannot perform this task if your old server is not working. |
Step 16 | Record the
details of all Trace and Log Central jobs.
See the Record Trace Log Job Details. You cannot perform this task if your old server is not working. |
Step 17 | Record CDR
Management configuration and destinations, if applicable.
See the Record CDR Management Configuration. You cannot perform this task if your old server is not working. |
Step 18 | From
Cisco Unified Communications
Manager Administration, determine the number of specific items that
are configured on the server.
See the Record System Configuration Counts. You cannot perform this task if your old server is not working. |
Step 19 | From
Cisco Unified Communications
Manager Administration, record all the phone loads and device types
that display on the Firmware Load Information window.
See the Record Firmware Information. If you have custom device types that do not ship with Cisco Unified Communications Manager, make sure that you have the appropriate COP files. You need to reinstall the devices types after performing the replacement. You cannot perform this task if your old server is not working. |
Step 20 | Record all
network configuration settings and other configuration settings that are
described in the sections that are referenced in the Important Notes column for
each server to be replaced.
See the following sections: You cannot perform this task if your old server is not working. |
Step 21 | Compare the
system version on each node in your cluster by using
Cisco Unified
Communications Manager Administration. Verify that you have DVDs with
that version.
See the Record System Version. If you have a service release, you need media for the base release and the service release. |
Step 22 | If your cluster is running in secure mode, make sure that you have USB eToken devices and CTL Client plug-in utility installed on a computer that is running the Windows operating system. For information about performing these tasks and about Cisco Unified Communications Manager security, refer to the Cisco Unified Communications Manager Security Guide. |
Step 23 | Perform a DRS
backup on the publisher server to a remote SFTP server and verify that the
backup succeeds. Record the DRS backup location and schedule information, if
applicable.
To verify that your SFTP is working, use an SFTP client on a computer on the same subnet as the servers that are being restored and download the backup to that computer. Ensure that all cluster nodes that you will replace or reinstall are online and registered as a node. DRS backs up only registered and online nodes. You cannot perform this task if your old server is not working. See the Create Backup. |
Before replacing or reinstalling a server, you must have the information that is described in this section. The information that is provided must match before and after the restore or reinstall. In the case of a server replacement, this information must match on both the original server and its replacement.
Gather this information for each Cisco Unified Communications Manager server that you are replacing or reinstalling in the cluster. You may not need to obtain all the information; gather only the information that is pertinent to your system and network configuration.
Record all system passwords and account IDs, including those described in the following table. You cannot retrieve these passwords from the server.
Caution | You must enter identical passwords and account IDs when you configure the replacement server. |
If you replace a server that was previously upgraded from an older product release, your passwords might get denied by the Cisco Unified Communications Manager installation program. This happens because the password validation rules might get stronger in the new product release, but passwords do not get re validated during an upgrade. But when you perform a fresh installation on the server that you are replacing, the new, stronger password validation occurs.
If this happens, choose new passwords that the installation program will accept. For more information about passwords, see the document Installing Cisco Unified Communications Manager.
Follow this procedure to record network configuration settings.
Caution | You must enter identical network settings when you configure the replacement server. Do not attempt to change network settings on the replacement server. The only exceptions are the NIC speed and duplex settings, which you should configure as described in this section. |
Follow this procedure to record the SMTP server setting, which specifies the hostname or IP address of the SMTP host that is used for outbound e-mail.
Follow this procedure to record the hostname and timezone settings.
If you use DNS, verify that all servers to be replaced are registered in DNS properly.
Record the number of registered devices, including the numbers of registered phones and gateways, by using the Cisco Unified Communications Manager Real Time Monitoring Tool (RTMT).
Step 1 | Download and
install the
Cisco Unified Communications
Manager
Real Time Monitoring
Tool (RTMT) by choosing
from
Cisco Unified Communications
Manager Administration, clicking
Find, and clicking the
Download link next to the appropriate RTMT
installer.
If you are planning to install the RTMT tool on a computer that is running the Microsoft Windows operating system, click the Download link for the Cisco Unified Communications Manager Real Time Monitoring Tool-Windows. If you are planning to install the RTMT tool on a computer that is running the Linux operating system, click the Download link for the Cisco Unified Communications Manager Real Time Monitoring Tool-Linux. |
Step 2 | Open RTMT. |
Step 3 | Perform one of the following tasks: |
Step 4 | For each Cisco Unified Communications Manager node, record the number for each device type that is displayed, including the numbers of registered phones, FXS, FXO, T1Cas, PRI, MOH, MTP, CFB, XCODE, and H323 Gateways. |
Record all the critical services and their status by using the Cisco Unified Communications Manager Real Time Monitoring Tool (RTMT).
Using the Syslog viewer in the Cisco Unified Communications Manager Real Time Monitoring Tool (RTMT), locate any events that have a severity of Error or higher.
Step 1 | Open RTMT and perform one of the following tasks: |
Step 2 | From the Select a Node drop-down list box, choose the server where the logs that you want to view are stored. |
Step 3 | Double-click the Application Logs folder. |
Step 4 | Locate events with a severity of Error or higher. |
Step 5 | Review each log to locate system-affecting errors. |
Record CDR Management configuration and destinations, if applicable.
You use the CDR Management Configuration window to set the amount of disk space to allocate to call detail record (CDR) and call management record (CMR) files, configure the number of days to preserve files before deletion, and configure up to three billing application server destinations for CDRs. The CDR repository manager service repeatedly attempts to deliver CDR and CMR files to the billing servers that you configure on the CDR Management Configuration window until it delivers the files successfully, until you change or delete the billing application server on the CDR Management Configuration window, or until the files fall outside the preservation window and are deleted.
From Cisco Unified Communications Manager Administration, obtain counts of each of the items that are configured on the system that you want to verify after the replacement. Some examples of items to count follow:
Record all of the phone loads and device types that display on the Firmware Load Information window.
Step 1 | In
Cisco Unified Communications
Manager Administration, choose
.
The Firmware Load Information window displays. | ||
Step 2 | Record all the
phone loads and device types that display.
|
Compare the system version on each node in your cluster by using Cisco Unified Communications Operating System Administration.
Verify that you have DVDs with that version. If you have a service release, you need media for base image and the service release.