Cisco Prime Collaboration Assurance - Advanced and Analytics Guide, 12.1 Service Pack 2

Bias-Free Language

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.

Book Contents
Find Matches in This Book

Results

Updated:
July 8, 2020

Chapter: Set Up Clusters

Set Up Clusters

This section provides information on the following:

Set Up Clusters

Cisco Prime Collaboration Assurance manages the following clusters:

  • Cisco TMS

  • Cisco VCS

  • Cisco Unified CM

If you are using more than one Cisco TelePresence Management Suite (TMS) in your network, you must configure these applications in a cluster for the Cisco Prime Collaboration Assurance application to manage; that is, Cisco Prime Collaboration Assurance cannot manage two standalone TMS.

Cisco Prime Collaboration Assurance monitors only the application servers. It does not monitor the database instances. Health polling is performed for all the Cisco TMS application servers in the clusters.

For TMS clusters, the conference details are imported from the primary Cisco TMS as defined on the Manage Clusters page.

If you have deployed Cisco Prime Collaboration Assurance in MSP mode, you can manage a CTX cluster also. Cisco Prime Collaboration Assurance cannot manage more than one CTX cluster. Health polling is performed for the CTX admin server in the cluster. For CTX clusters, the session details are imported from the primary admin server.

Manage Cisco TelePresence Manager or Cisco TMS Clusters

Before discovering Cisco TelePresence Manager or Cisco TMS clusters, you must enter the cluster details in the Manage Cluster page. During the discovery of Cisco TelePresence Manager or Cisco TMS, Cisco Prime Collaboration Assurance uses the cluster details, along with the device credentials (Device Inventory > Inventory Management > Manage Credentials) and discovers the management applications.


Note

For adding CTX clusters, ensure that you create a new user with API role in the primary CTX admin server. For information on this procedure, see the Setting up Devices for Prime Collaboration Assurance.

For Cisco Prime Collaboration Release 11.5 and later


Note

Cisco TelePresence Manager and Cisco TelePresence Exchange (CTX) clusters are not supported.

Before discovering Cisco TMS clusters, you must enter the cluster details in the Manage Cluster page. During the discovery of Cisco TMS, Cisco Prime Collaboration Assurance uses the cluster details, along with the device credentials (Inventory > Inventory Management > Manage Credentials) and discovers the management applications.

To manage Cisco TMS clusters:

Procedure

Step 1

Choose Device Inventory > Inventory Management.

For Cisco Prime Collaboration Release 11.5 and later

Choose Inventory > Inventory Management

Step 2

From the Inventory Management page, click Manage CTS-MAN/TMS Cluster.

If you have deployed Cisco Prime Collaboration Assurance in MSP mode, click Manage CTS-MAN/TMS Cluster.

For Cisco Prime Collaboration Release 11.5 and later

From the Inventory Management page, click Manage TMS Cluster.

If you have deployed Cisco Prime Collaboration Assurance in MSP mode, click Manage TMS Clusters.

Step 3

In the Manage Cluster window, enter the cluster name and choose an item from the Cluster Type drop-down list.

Step 4

For a TMS cluster: Enter the IP address of the primary active server, and the secondary active or passive server.

For Cisco Prime Collaboration Release 11.5 and later

For a TMS cluster: Enter the IP address of the primary active server, and the secondary active or passive server.

Step 5

Click Add to add a new cluster.

Perform logical discovery to discover these clusters. For information on logical discovery, see Device Discovery Methods. When you are discovering clusters for the first time in your network, you can enter primary, secondary, hot standby and load-balancer server details for CTS-MAN and TMS clusters. Later, to update inventory or rediscover, you can provide only the primary server details of CTS-MAN and TMS clusters.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco