McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 11

↗ View in doc context
page
11
source
cucm/v15/install-guide/install-guide.md
chunk_id
cucm::v15::install-guide::install-guide::4

For more information, see "Cisco Collaboration Solutions Design Guidance" at http://www.cisco.com/go/ ucsrnd. Publisher Nodes and Subscriber Nodes Within a cluster, there is a database publisher for each type of node that you install. When you install Unified Communications Manager, the installation wizard prompts you to specify whether the node you are installing is the first node in the cluster. The first Unified Communications Manager node that you install becomes the publisher node, because it publishes the voice and video database to the other Unified Communications Manager nodes in the cluster. All subsequent nodes in the cluster are called subscriber nodes. Each subscriber node must be associated with the publisher node. You must set up all subscriber nodes in the system topology on the publisher node before you install the software on the subscriber nodes. When you install IM and Presence nodes, the first node that you install functions as the server for the IM and Presence database. Because this node publishes the database for all of the IM and Presence nodes in the cluster, it is referred to as the IM and Presence database publisher; however, you must install this and all other IM and Presence nodes as subscribers of the Unified Communications Manager publisher node. As with other subscriber nodes, you must add these in the system topology before you install the software. Topology Options When installing your cluster, you must decide on the topology that you want to deploy. For example: • The number of cluster nodes required. • Whether you will install all cluster nodes in a single location, or if you will install your nodes in separate geographic sites connected via a WAN in order to provide geographic redundancy. For more information on scalability, see Megacluster. Supported Versions for Intra-cluster versions Unified Communications Manager and the IM and Presence Service nodes in the same cluster must be running the supported builds as mentioned in the Release Notes for Cisco Unified Communications Manager and the IM and Presence Service. This release offers two main deployment options for this release of Unified Communications Manager and the IM and Presence Service: • Standard Deployments of IM and Presence Service—Both Unified Communications Manager and the IM and Presence Service must be running the supported versions for your deployment. A version mismatch is not supported. • Centralized Deployments of IM and Presence Service—If you have the Centralized Deployment option configured on the IM and Presence Service, then within the IM and Presence Service central cluster, both the Unified Communications Manager instance and the IM and Presence Service must be running the same version. However, the telephony cluster that the central cluster connects to does not have to be running the same version. The Centralized IM and Presence Service cluster requires a Unified CM publisher node, for a total of seven servers in the cluster: three IM and Presence Service sub-cluster pairs (six servers) + the Unified CM publisher node. Note Installation Guide for Cisco Unified Communications Manager and the IM and Presence Service, Release 15 and SUs 5 Planning the Installation Topology Options