Get Started


Contact your Cisco partner to submit a Cisco Webex Cloud-Connected UC (CCUC) order for you or complete an order through Cisco Commerce Workspace (CCW).

For information on how to order CCUC, refer to the Cisco Collaboration Flex Plan Ordering Guide at:

https://www.cisco.com/c/en/us/products/collateral/customer-collaboration/guide-c07-740917.html

The first time that you set up CCUC, a wizard guides you on how to set up an agent file and cluster group. When you create more agent files and cluster groups after the first time, this wizard doesn’t appear.

Create First Agent File and Cluster Group

Create an Agent Cisco Operations Package (COP) file in the Control Hub. Then install it on all nodes of a Unified CM or IM&P cluster that you wish to connect to the Control Hub. After installing the agent file, sign back into the Control Hub to verify the server cluster connections and then assign them to a cluster group.


After you install the Agent COP file, there is no need for a server or cluster reboot.

Before you begin

1

From the customer view in Cisco Webex Control Hub, go to Services. In the UC Management card, click Get Started.


 

The Get Started button remains enabled until you create an agent file and a cluster group.

2

Click Next.

3

Name the agent file and provide a description.

The maximum length for a filename is 200 characters and the description is 1000 characters.

4

Enter the proxy information that can be used to connect the nodes to internet, and then click Save to create the agent file.


 
  • The proxies added to an agent installer file determine the data center where you can use the file. If you have multiple data centers, we recommend that you create a single agent file having the proxy information about all them.

  • The agent file can take up to a minute to generate.

5

Click Download.

You created and downloaded your first agent file. After the first agent file is created, Add Agent Install File appears on the screen. Use this button to create multiple agent install files.

Continue with the setup wizard to create your first cluster group. Cluster groups are just like folders. They're a logical construct that allows you to group your clusters to manage them together. Enter a name for the cluster group that makes sense for your deployment. For example, you can name cluster groups based on geographic regions or release environments.

6

Click Next.

7

Enter a name for the cluster group and a description, then click Save.

You can create multiple cluster groups. After you're done creating the cluster groups you require, proceed to the next step.

8

Click Next, and then Finish to close the wizard.

Now you have an agent file and a cluster group. Install the agent file on the nodes that you want to monitor. Then, return to Control Hub to verify the nodes in a cluster and assign them to a cluster group.

After installing the agent on a node, a verification code shows up at the end of the install log file. For more information about how to install an agent cop file, refer to the respective documentation, depending on whether you have a Unified CM node, or IM and P node, listed below.

For a Unified CM or IM and P node, refer to Installation Guide for Cisco Unified Communications Manager and the IM and Presence Service based on your Unified CM release at:

https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-installation-guides-list.html


You can get the verification code from the admin cli using the utils ucmgmt agent status command. This code is similar to a serial number and makes it easy for you to identify each node uniquely. When you accept a node into the inventory, ensure that the verification code on the node matches what is displayed in Control Hub. Thus, you're certain that you’re working with the correct node.

Verify and Assign Clusters

1

From the customer view in Cisco Webex Control Hub, go to Services.In the UC Management card, click Inventory.

2

If any of the cluster groups shows the Needs Verification status, click Resolve next to the cluster group.

3

Click Verify next to a cluster.

4

Click the Cluster Group drop-down list and choose the cluster group to which you want to assign a cluster.

After you assign a cluster to the cluster group, all the nodes belonging to that cluster get assigned to the selected cluster group.

5

Click check next to the node that you want to assign to the cluster group, or X to remove the node.

6

Click Save.


 

After the cloud agent COP file installation, it would take up to one and half hours for the UC Analytics service to be up and running.

Each agent installer file can have zero to any number of HTTP proxies defined in it. If you must add more HTTP proxies after you create an agent installer file, create a new agent installer file with the requisite proxies. When you install the agent installer file on a node, the node cycles through all the proxies defined in the file until it can reach the cloud service. If you include all your proxies in a single agent file, the same file can be used in all your data centers.

You can also create multiple cluster groups to organize your clusters.


This procedure is applicable only if you're not going through the setup wizard.

Set Up Agent File

Before you begin

1

From the customer view in Cisco Webex Control Hub, go to Services, and in the UC Management card, click Agent Install Files.

2

Click Add File to create an agent installer file containing zero or more proxies.

3

Name the agent file and provide a description.

The maximum length for a filename is 200 characters and the description is 1000 characters.

4

Enter the proxy information, and then click Save to create the agent file.


 
  • The proxies added to an agent installer file determine the data center where you can use the file. If you have muliple data centers, we recommend that you create a single agent file having the proxy information about all of them.

  • The agent file can take up to a minute to generate.

5

Click Download.

Add Cluster Groups

Add cluster groups to the Control Hub to enable you to assign clusters to them. A cluster group is a place to logically group clusters so that they can be managed together. For example, you can create cluster groups based on geographic regions or release environments. You can rename cluster groups, move clusters from one cluster group to another, and so on.

1

From the customer view in Cisco Webex Control Hub, go to Services. In the UC Management card, select Inventory.

2

Click Add Cluster Group.

3

Enter a name and description, then click Save.

The following table lists the different statuses of a cluster group with a brief description about each.

Cluster Group Status

Brief Description

Needs Verification

Cluster must be verified by the customer administrator.

No Clusters

No clusters are present in the cluster group.

Misconfigured

One or more nodes in the cluster group are configured incorrectly.

No Agent running

If no agents are running on the node, the agent process might have stopped.

No Publisher

  • Ensure that the platform API web service is enabled and running on the machine. For more information, refer to the Platform Administrative Web Service section in Cisco Unified Serviceability Administration Guide.

  • Node is down or proxies are offline.

Offline

One or more nodes in the cluster group have their agent offline. The agent process might have stopped and requires consideration.

The following table lists the different statuses of a node with a brief description about each. For details on how to fix an issue that is related to either a cluster group status or a node status, see Troubleshoot CiscoWebex Cloud-Connected UC.

Node Status

Brief Description

Needs Assignment

The node must be assigned to a cluster.

Needs Verification

Node must be verified by the customer administrator.

Unsupported

Node is onboarded but is not supported by CCUC. For example, Unity, CER, and so on.

Offline

The node is not reachable.

Online

The node is onboarded and the agent is verified.

Misconfigured

Node is configured incorrectly.

No Agent running

If no agents are running on the node, the agent process might have stopped.

No Publisher

One or more clusters in the clusters under that cluster have no Publisher. This is a rare scenario.

The following table lists the different statuses of a node in the analytics inventory with a brief description about each.

Analytics Status

Brief Description

Starting

The telemetry service has been started by the administrator.

Stopping

The telemetry service has been stopped by the administrator.

Stopped by user

The telemetry service has been stopped by the user.

Waiting for installation

Installation in progress.

Online

The module is online and running with the latest cop file.

Offline

The module is offline.

You can redownload and delete agent files and change the name and descriptions of cluster groups.

Edit Names or Descriptions of Cluster Groups

1

From the customer view in Cisco Webex Control Hub, go to Services. In the UC Management card, select Inventory.

2

Click Details next to the cluster group that you want to edit.

3

Click on the text field that you want to edit.

Download or Delete Agent Files

After you create an agent installer file, you can’t edit it. If any file produces an error during its installation or you wish to add more proxy information to a file, you can create a new agent install file and choose to delete the old file that is no longer needed.

1

From the customer view in Cisco Webex Control Hub, go to Services. In the UC Management card, and click Agent Install Files.

2

Click on an agent file, and then select Download or Delete.

You can start or stop the telemetry module based on your requirement. Once you disable this service, no cloud operations occur on the node, including upgrade.


Once you disable the service, no cloud operation (including upgrade) can take place on the node.

1

From the customer view in Cisco Webex Control Hub, go to Services.In the UC Management card, click Inventory.

2

Click on any of the node entries in the list.

A pane appears on the right. You can view more details about the node and the agent.

3

Click Disable Analytics Service to disable the telemetry service.

4

Click Enable Analytics Service to enable the telemetry service..