Make sure to account for any growth that has occurred since initial system configuration.
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 7.x.
You must enter identical passwords when configuring the replacement server. You cannot retrieve these passwords from the server.
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.
Obtain and store COP files for any locales that are installed on the server. You need to reinstall locales after doing the replacement.
Do not change computer names or IP addresses, or add more nodes to the cluster.
Verify the integrity of your software downloads and DVDs.
Perform the following tasks:
Check the MD5 checksum of downloaded software against the published value to verify that it downloaded properly.
Verify that the DVD is readable by a DVD drive.
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.
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.
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.
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.
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.
If you have a service release, you need media for the base release and the service release.
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.
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.
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.
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.
Table 1 Password and Accounts Configuration Data
The user ID that you use for secure shell access to the CLI, for logging into Cisco Unified Communications Manager Administration, and for logging into the Disaster Recovery System.
The password that you use to log into the Administrator ID account.
Application User Name
The default Application User name for applications that are installed on the system, including Cisco Unified Communications Manager and Cisco Unified Serviceability.
In 5.x releases, the Application User Name is set automatically during installation to CCMAdministrator.
In 6.x releases, you choose the Application User Name during installation.
Application User Password
The password that is used as the default password for applications that are installed on the system, including Cisco Unified Communications Manager Administration and Cisco Unified Serviceability.
The security password that Cisco Unified Communications Manager servers in the cluster use to communicate with one another.
You must enter the same password for all nodes in the cluster.
Record network configuration settings
Follow this procedure to record network configuration settings.
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.
In Cisco Unified Communications Operating System Administration, navigate to Show > Network.
Record all network configuration settings, including those described in the following table.
Table 2 Network Configuration Information
Parameter and Your Entry
Dynamic Host Configuration Protocol status.
If DHCP is not enabled, you must enter a hostname, IP Address, IP Mask, and Gateway.
When DNS is not enabled, you should only enter IP addresses (not hostnames) for all network devices in your Cisco Unified Communications network.
The IP address of the primary DNS server that Cisco Unified Communications Manager contacts first when it attempts to resolve host names.
Consider this setting as required if DNS is enabled.
The IP address of the secondary DNS server that Cisco Unified Communications Manager will attempt to connect if the primary DNS server fails.
The name of the domain in which this machine is located.
Consider this setting as required if DNS is enabled.
The IP address of the default gateway, which is a network point that acts as an entrance to another network. Outbound packets get sent to the gateway that will forward them to their final destination.
If you do not have a gateway, you must still fill in this field by setting it to 255.255.255.255. Not having a gateway may limit you to communicating only with devices on your subnet.
A name that represents an alias that is assigned to an IP address to identify it.
Consider this setting as required if DHCP is disabled.
The IP address of this machine. It uniquely identifies the server on this network. Ensure that another machine in this network is not using this IP address.
Consider this setting as required is DHCP is disabled.
The IP subnet mask of this machine. The subnet mask together with the IP address defines the network address and the host address.
The speed of the server network interface card (NIC) in megabits per second.
The duplex setting of the server NIC.
Maximum transmission unit (MTU): the largest packet, in bytes, that this host will transmit on the network.
The hostname or IP address of the NTP server with which you want to keep time synchronization.
Consider this setting as required if you enabled the system to be an NTP client.
Record the 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 both NIC and switch port settings to Auto/Auto; do not set hard values.
If you are using Network Fault Tolerance, the Network Fault Tolerance configuration gets lost during the replacement. You will need to configure it on each server after the upgrade.
Enable PortFast on all switch ports that are connected to Cisco Unified Communications Manager servers. With Portfast enabled, the switch immediately brings a port from the blocking state into the forwarding state by eliminating the forwarding delay (the time that a port waits before changing from its Spanning-Tree Protocol (STP) learning and listening states to the forwarding state).
Record SMTP settings
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.
In Cisco Unified Communications Operating System Administration, navigate to Settings > SMTP.
Record IP address or hostname of the SMTP server.
Record the hostname and timezone
Follow this procedure to record the hostname and timezone settings.
In Cisco Unified Communications Operating System Administration, navigate to Show > System.
Record the settings in the following fields:
Host Name - The unique host name of the server
Time Zone - The local time zone and offset from Greenwich Mean Time (GMT)
Verify DNS registration
If you use DNS, verify that all servers to be replaced are registered in DNS properly.
Open a command prompt.
To ping each server by its DNS name, enter:
To look up each server by IP address, enter:
Determine registration counts
Record the number of registered devices, including the numbers of registered phones and gateways, by using the Cisco Unified Communications ManagerReal Time Monitoring Tool (RTMT).
Download and install the Cisco Unified Communications ManagerReal Time Monitoring Tool (RTMT) by choosing Application > Plugins 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 ManagerReal 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 ManagerReal Time Monitoring Tool-Linux.
Perform one of the following tasks:
In the Quick Launch Channel, click the CallManager tab, click the View tab, click the Device category, and click the Device icon.
Choose CallManager > Monitor > Device Summary.
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 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 Serviceability, choose Tools > CDR Management.
The CDR Management Configuration window displays.
Record the General Parameters and the Billing Application Server Parameters.
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:
CTI route points
In Cisco Unified Communications Manager Administration, access the windows for each item that you want to count and click Find without entering any search parameters. Some examples follow:
Find and List Phones (Device > Phone)
Find and List Gateway (Device > Gateway)
Find and List Trunks (Device > Trunk)
Find and List Route Patterns (Call Routing > Route/Hunt > Route Pattern)
Find and List Users (User Management > End Users)
Find and List Application Users (User Management > Application Users)
Record the number of each of the items (devices, route patterns, and users).