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.
Cisco Prime Collaboration manages the following clusters:
If you are using more than one Cisco TelePresence Manager (CTS-Manager), or Cisco TelePresence Management Suite (TMS) in your network, you must configure these applications in a cluster for the Cisco Prime Collaboration application to manage; that is, Cisco Prime Collaboration cannot manage two standalone CTS-Manager, or TMS.
Cisco Prime Collaboration monitors only the application servers. It does not monitor the database instances. Health polling is performed for all the CTS-Manager, or Cisco TMS application servers in the clusters.
For CTS-Manager, or TMS clusters, the conference details are imported from the primary CTS-Manager, or Cisco TMS as defined on the Manage Clusters page.
If you have deployed Cisco Prime Collaboration in MSP mode, you can manage a CTX cluster also. Cisco Prime Collaboration 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.
Before discovering Cisco TelePresence Manager, Cisco TMS, or Cisco TelePresence Exchange (CTX) 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 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 wiki. |
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 uses the cluster details, along with the device credentials ( ) and discovers the management applications.
To manage Cisco TelePresence Manager, Cisco TMS or Cisco TelePresence Exchange (CTX) clusters:
Step 1 | Choose
.
For Cisco Prime Collaboration Release 11.5 and later Choose |
Step 2 | From the Inventory Management
page, click
Manage
CTS-MAN/TMS Cluster.
If you have
deployed Cisco Prime Collaboration 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 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 CTS-MAN cluster: Enter
the IP addresses of the primary, secondary, hot standby, and the load-balancer
servers. (The Primary Server IP address and hot standby or secondary are
mandatory; only load-balancer server is optional.)
For a CTX cluster: Enter the
IP address of the primary and secondary admin server.
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. |