Cisco Unified Communications Manager Administration Guide, Release 9.1(1)
Server setup
Downloads: This chapterpdf (PDF - 1.14MB) The complete bookPDF (PDF - 9.6MB) | Feedback

Server setup

Server setup

This chapter provides information about server configuration.

See also Internet Protocol Version 6 (IPv6) in Cisco Unified Communications Manager Features and Services Guide and Changing the IP Address and Host Name for Cisco Unified Communications Manager.

About server setup

In Cisco Unified Communications Manager Administration, use the System > Server menu path to add and configure a server.

Use the Server Configuration window to specify the address of the server where Cisco Unified Communications Manager or Cisco Unified Communications Manager IM and Presence Service is installed.

Server setup tips

Before you configure a server, review the following information:

  • Make sure that you only add each server once in the Server Configuration window. If you add a server by using the hostname and add the same server again by using the IP address, Cisco Unified Communications Manager cannot accurately determine component versions for the server after a Cisco Unified Communications Manager upgrade. If you have two entries in Cisco Unified Communications Manager Administration for the same server, delete one of the entries before you upgrade.
  • When you perform a fresh installation of Cisco Unified Communications Manager, you must define any subsequent servers (nodes) in the Server Configuration window using Cisco Unified Communications Manager Administration before you can install Cisco Unified Communications Manager or IM and Presence Service on each subsequent server. To define a subsequent node, click Add New and proceed to configure the server. After you add the subsequent server, you can then install the Cisco Unified Communications Manager or IM and Presence Service software on that server.
  • If you use IPv4 in your network, you must update the DNS server with the appropriate Cisco Unified Communications Manager name and address information before you use that information to configure the Cisco Unified Communications Manager server.

Caution


If your network supports IPv6 or IPv4 and IPv6 in dual-stack mode, you can provision your DNS server for IPv6 prior to upgrading from Cisco Unified Communications Manager Release 7.0(x) to Release 8.5(1). However, do not configure the DNS records for Cisco Unified Communications Manager for IPv6 until after you upgrade to Release 8.5(1). Configuring the DNS records for Cisco Unified Communications Manager for IPv6 prior to upgrading to Release 8.5(1) causes the upgrade to fail and causes your system to become nonfunctional after you reboot.


  • For DNS, make sure that you map the IP addresses of all servers, including dummy nodes, to the host names on the DNS server. If you do not perform this task, Cisco Unified Communications Manager generates alarms that inform you that the License Manager service is down.
  • Cisco Unified Communications Manager Administration does not prevent you from updating the Host Name/IP Address field under any circumstances.
  • When you attempt to change the IP address in the Server Configuration window, the following message displays after you save the configuration: "Changing the host name/IP Address of the server may cause problems with Cisco Unified Communications Manager. Are you sure that you want to continue?" Before you click OK, make sure that you understand the implications of updating the Host Name/IP Address field; for example, incorrectly updating this setting may cause Cisco Unified Communications Manager to become inoperable; that is, the database may not work, you may not be able to access Cisco Unified Communications Manager Administration, and so on. In addition, updating this field without performing other related tasks may cause problems for Cisco Unified Communications Manager.
  • Changes to the server configuration do not take effect until you restart Cisco Unified Communications Manager. For information about restarting the Cisco CallManager service, see the Cisco Unified Serviceability Administration Guide.
  • For additional information on changing the IP address or host name, see the document Changing the IP Address and Host Name for Cisco Unified Communications Manager.
Related References

Server deletion

This section describes how to delete a server from the Cisco Unified Communications Manager database and how to add a deleted server back to the Cisco Unified Communications Manager cluster.

In Cisco Unified Communications Manager Administration, you cannot delete the first node of the cluster, but you can delete subsequent nodes. Before you delete a subsequent node in the Find and List Servers window, Cisco Unified CM Administration displays the following message: "You are about to permanently delete one or more servers. This action cannot be undone. Continue?". If you click OK, the server gets deleted from the Cisco Unified CM database and is not available for use.


Tip


When you attempt to delete a server from the Server Configuration window, a message that is similar to the one in the preceding paragraph displays. If you click OK, the server gets deleted from the Cisco Unified CM database and is not available for use.


Before you delete a server, consider the following information:

  • Cisco Unified Communications Manager Administration does not allow you to delete the first node in the cluster, but you can delete any subsequent node.
  • Cisco recommends that you do not delete any node that has Cisco Unified Communications Manager running on it, especially if the node has devices, such as phones, registered with it.
  • Although dependency records exist for the subsequent nodes, the records do not prevent you from deleting the node.
  • If any call park numbers are configured for Cisco Unified Communications Manager on the node that is being deleted, the deletion fails. Before you can delete the node, you must delete the call park numbers in Cisco Unified Communications Manager Administration.
  • If a configuration field in Cisco Unified Communications Manager Administration contains the IP address or host name for a server that you plan to delete, update the configuration before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server; for example, if you enter the IP address or host name for a service parameter, enterprise parameter, service URL, directory URL, IP phone service, and so on, update this configuration before you delete the server.
  • If an application GUI, for example, Cisco Unity, Cisco Unity Connection, and so on, contains the IP address or host name for the server that you plan to delete, update the configuration in the corresponding GUIs before you delete the server. If you do not perform this task, features that rely on the configuration may not work after you delete the server.
  • The system may automatically delete some devices, such as MOH servers, when you delete a server.
  • Before you delete a node, Cisco recommends that you deactivate the services that are active on the subsequent node. Performing this task ensures that the services work after you delete the node.
  • Changes to the server configuration do not take effect until you restart Cisco Unified Communications Manager. For information on restarting the Cisco CallManager service, see the Cisco Unified Serviceability Administration Guide.
  • To ensure that database files get updated correctly, you must reboot the cluster after you delete a server, Presence, or application server.
  • After you delete the node, access Cisco Unified Reporting to verify that Cisco Unified Communications Manager removed the node from the cluster. In addition, access Cisco Unified Reporting, RTMT, or the CLI to verify that database replication is occurring between existing nodes; if necessary, repair database replication between the nodes by using the CLI.

Add node to cluster before install

Use Cisco Unified Communications Manager Administration to add a new node to a cluster before installing the node. The server type you select when adding the node must match the server type you install.

You must configure a new node on the first node using Cisco Unified Communications Manager Administration before you install the new node. To install a node on a cluster, see the Cisco Unified Communications ManagerInstallation Guide.

For Cisco Unified Communications Manager Video/Voice servers, the first server you add during an initial installation of the Cisco Unified Communications Manager software is designated the publisher node. All subsequent server installations or additions are designated as subscriber nodes. The first Cisco Unified Communications Manager IM and Presence node you add to the cluster is designated the IM and Presence Service database publisher node.


Note


You cannot use Cisco Unified Communications Manager Administration to change the server type after the server has been added. You must delete the existing server instance, and then add the new server again and choose the correct server type setting.


Procedure
    Step 1   Select System > Server.

    The Find and List Servers window displays.

    Step 2   Click Add New.

    The Server Configuration - Add a Server window displays.

    Step 3   From the Server Type drop-down list box, choose the server type that you want to add, and then click Next.
    • CUCM Video/Voice
    • CUCM IM and Presence
    Step 4   In the Server Configuration window, enter the appropriate server settings.

    For server configuration field descriptions, see topics related to server settings.

    Step 5   Click Save.

    Related References

    Add deleted server back in to cluster

    If you delete a subsequent node (subscriber) from Cisco Unified Communications Manager Administration and you want to add it back to the cluster, perform the following procedure.

    Procedure
      Step 1   In Cisco Unified Communications Manager Administration, add the server by choosing System > Server.
      Step 2   After you add the subsequent node to Cisco Unified Communications Manager Administration, perform an installation on the server by using the disk that Cisco provided in your software kit.
      Tip   

      For example, if you have a version 8.5(1) disk, perform a 8.5(1) installation on the node. If you have a disk with a compatible version of 6.1(3) on it, for example, use the disk to install Cisco Unified CM on the subsequent node; during the installation, choose the Upgrade During Install option when the installation displays the options.

      Make sure that the version that you install on the subsequent node matches the version that runs on the first node (publisher) in the cluster.

      If the first node in the cluster runs Cisco Unified Communications Manager 8.5(1) version and a service update (or engineering special), you must choose the Upgrade During Install option when the installation displays the installation options; before you choose this option, ensure that you can access the service update (or engineering special) image on DVD or a remote server. For more information on how to perform an installation, see the installation documentation that supports your version of Cisco Unified Communications Manager.

      Step 3   After you install Cisco Unified CM, configure the subsequent node, as described in the installation documentation that supports your version of Cisco Unified CM.
      Step 4   Access the Cisco Unified Reporting, RTMT, or the CLI to verify that database replication is occurring between existing nodes; if necessary, repair database replication between the nodes.

      Server settings

      The following table describes the Cisco Unified Communications Manager voice/video server configuration settings.

      Table 1 Cisco Unified Communications Manager voice/video server settings

      Field

      Description

      Server Information

      Host Name/IP Address

      If your network uses DNS that can map to IPv4 addresses, you can enter the host name of the Cisco Unified Communications Manager server. Otherwise, you must enter the full IPv4 address of the server.

      Tip   

      To avoid errors, Cisco recommends that you add a server to the system with a name that has less than 47 characters. Then, update the server name to the target length.

      Tip   

      If your network supports IPv6 (or IPv4 and IPv6), configure the IPv6 Name field in addition to the Hostname/IP Address field.

      Note   

      You must update the DNS server with the appropriate Cisco Unified Communications Manager name and address information before you enter that information in this field.

      IPv6 Name

      This field supports IPv6. If your network uses DNS that can map to IPv6 addresses, you can enter the host name of the Cisco Unified Communications Manager server. Otherwise, enter the non-link-local IP address of the Cisco Unified Communications Manager server; for information on how to obtain the non-link local IP address, see the Cisco Unified Communications Manager Features and Services Guide.

      This field, which gets included in the TFTP configuration file, gets used by phones that run SCCP to retrieve the IPv6 address of the Cisco Unified Communications Manager server, so phone registration occurs.

      Tip    Remember to update the DNS server with the appropriate Cisco Unified Communications Manager name and address information.
      Caution   

      If your network supports IPv6 or IPv4 and IPv6 in dual-stack mode, you can provision your DNS server for IPv6 prior to upgrading from Cisco Unified Communications Manager Release 7.0(x) to Release 8.5(1). However, do not configure the DNS records for Cisco Unified Communications Manager for IPv6 until after you upgrade to Release 8.5(1). Configuring the DNS records for Cisco Unified Communications Manager for IPv6 prior to upgrading to Release 8.5(1) causes the upgrade to fail and causes your system to become nonfunctional after you reboot.

      Tip    In addition to configuring the IPv6 Name field, you must configure the IP Address/Hostname field, so Cisco Unified Communications Manager can support features/devices that use IPv4 (or IPv4 and IPv6).

      MAC Address

      This field is optional. It exists only to give you a place to note the server MAC address. It does not impact the system at all.

      Enter the media access control (MAC) address of the network interface card (NIC) in the Cisco Unified Communications Manager server. The MAC address specifies the permanent hardware address of the NIC.

      Tip    If you plan to move the server periodically to different locations on the network, you must enter the MAC address, so other devices on the network can always identify the server. If you do not plan to relocate the server, consider entry of the MAC address as optional.

      Description

      Consider this entry as optional.

      Enter a description of the server. The description can include up to 50 characters in any language, but it cannot include double-quotes ("), percentage sign (%), ampersand (&), back-slash (\), or angle brackets (<>).

      Location Bandwidth Management Information

      LBM Intercluster Replication Group

      Select an LBM Intercluster Replication Group from the drop-down list. You may also click View Details to display the settings for this LBM Intercluster Replication Group.

      Related Information

      View Presence Server Status

      Use Cisco Unified Communications Manager Administration to view the status of critical services and self-diagnostic test results for the IM and Presence Service node.

      Procedure
        Step 1   Select System > Server.

        The Find and List Servers window appears.

        Step 2   Select the server search parameters, and then click Find.

        Matching records appear.

        Step 3   Select the IM and Presence server that is listed in the Find and List Servers window.

        The Server Configuration window appears.

        Step 4   Click on the Presence Server Status link in the IM and Presence Server Information section of the Server Configuration window.

        The Node Details window for the server appears.