Configuration and Discovery

This section describes how to monitor Cisco CloudCenter Suite services in SL1 using the Dynamic Applications in the "Cisco CloudCenter Suite" PowerPack.

Configuration and Discovery for Standard Cisco CloudCenter Suite Deployments

The "Cisco CloudCenter Suite" PowerPack lets you discover and collect configuration and performance data about CloudCenter Suite deployments and their components. The following sections describe the configuration and discovery steps for monitoring standard CloudCenter Suite deployments.

Prerequisites for Monitoring CloudCenter Suite Deployments

To align RabbitMQ with your Remote Cloud, you must install the "Docker" PowerPack discover the swarm. You must also have the "AMQP: RabbitMQ" PowerPack installed.

Creating a Basic/Snippet Credential for Standard Deployments

To configure SL1 to monitor a CloudCenter Suite deployment, you must first create a Basic/Snippet credential. This credential allows the Dynamic Applications in the "Cisco CloudCenter Suite" PowerPack to communicate with your CloudCenter Suite.

The PowerPack includes an example Basic/Snippet credential (Cisco CloudCenter EXAMPLE) that you can edit for your own use.

To configure a Basic/Snippet credential to access CloudCenter Suite:

1. Go to the Credential Management page (System > Manage > Credentials).
2. Locate the Cisco CloudCenter EXAMPLE credential, and then click its wrench icon (). The Edit Basic/Snippet Credential modal appears.
3. Enter values in the following fields:

• Credential Name. Type a name for the CloudCenter Suite credential.
• Username. Type the User ID for a CloudCenter Suite user that has root tenant administration privileges. This account must be an API user, not a UI user.
• Password. Type the API key for the user you entered in the Username field.

4. Leave all other fields set to the default values. Click the Save As button.

Discovering the CloudCenter Suite Root Tenant

To discover CloudCenter Suite, perform the following steps:

1. On the Devices page () or the Discovery Sessions page (Devices > Discovery Sessions), click the Add Devices button. The Select page appears:

2. Click the Unguided Network Discovery button. Additional information about the requirements for discovery appears in the General Information pane to the right.

3. Click Select. The Add Devices page appears:
4. Complete the following fields:

• Name. Type a unique name for this discovery session. This name is displayed in the list of discovery sessions on the Discovery Sessions tab.
• Description. Optional. Type a short description of the discovery session. You can use the text in this description to search for the discovery session on the Discovery Sessions tab.
• Select the organization to add discovered devices to. Select the name of the organization to which you want to add the discovered devices.

5. Click Next. The Credentials page of the Add Devices wizard appears:

6. On the Credentials page, locate and select the Basic/Snippet credential you created for the CloudCenter Suite root tenant.

7. Click Next. The Discovery Session Details page of the Add Devices wizard appears:

8. Complete the following fields:

• List of IPs/Hostnames. Enter the IP address for the CloudCenter Suite root tenant.

• Which collector will monitor these devices?. Select an existing collector to monitor the discovered devices. Required.
• Run after save. Select this option to run this discovery session as soon as you click Save and Close.

In the Advanced options section, click the down arrow icon () to complete the following fields:

• Discover Non-SNMP. Enable this setting.

9. Click Save and Close to save the discovery session. The Discovery Sessions page (Devices > Discovery Sessions) displays the new discovery session.
10. If you selected the Run after save option on this page, the discovery session runs, and the Discovery Logs page displays any relevant log messages. If the discovery session locates and adds any devices, the Discovery Logs page includes a link to the Device Investigator page for the discovered device.

Discovering the CloudCenter Suite Root Tenant in the SL1 Classic User Interface

To discover CloudCenter Suite, perform the following steps:

1. Go to the Discovery Control Panel page (System > Manage > Classic Discovery or System > Manage > Discovery in the classic user interface).
2. In the Discovery Control Panel, click the Create button.

3. The Discovery Session Editor page appears. In the Discovery Session Editor page, define values in the following fields:

• IP Address/Hostname Discovery List. Enter the IP address for the CloudCenter Suite root tenant.

• Other Credentials. Select the Basic/Snippet credential you created for the CloudCenter Suite root tenant.
• Discover Non-SNMP. Select this checkbox.

4. Optionally, you can enter values in the other fields on this page. For more information about the other fields on this page, see the Discovery & Credentials section.
5. Click the Save button to save the discovery session and then close the Discovery Session Editor window.
6. The discovery session you created appears at the top of the Discovery Control Panel page. Click its lightning-bolt icon () to run the discovery session.
7. The Discovery Session window appears. When the device is discovered, click the device icon () to view the Device Properties page for the device.

Verifying Discovery and Dynamic Application Alignment

To verify that SL1 automatically aligned the correct Dynamic Applications during discovery:

• From the Device Properties page for the CloudCenter Suite root device, click the Collections tab. The Dynamic Application Collections page appears.
• All applicable Dynamic Applications for CloudCenter Suite are automatically aligned during discovery.

It can take several minutes after the discovery session has completed for Dynamic Applications to appear in the Dynamic Application Collections page.

The following Dynamic Applications should be aligned to the device:

• Cisco: Cloud Center Suite Component Counts
• Cisco: Cloud Center Suite Action Orchestrator Discovery
• Cisco: Cloud Center Suite CCM Discovery
• Cisco: Cloud Center Suite Cost Optimizer Discovery
• Cisco: Cloud Center Suite Tenant Discovery
• Cisco: Cloud Center Suite Tenant Parent Relationships

If the listed Dynamic Applications have not been automatically aligned during discovery, you can align them manually. To do so, perform the following steps:

1. Click the Action button and then select Add Dynamic Application. The Dynamic Application Alignment page appears.
2. In the Dynamic Applications field, select the Dynamic Application you want to align.
3. In the Credentials field, select the Basic/Snippet credential you created for CloudCenter Suite.
4. Click the Save button.
5. Repeat steps 1-4 for the other unaligned Dynamic Applications.

Discovering Multiple Tenants for Standard Deployments

The "Cisco CloudCenter Suite" PowerPack can be used to monitor a CloudCenter Suite cluster that includes multiple tenants. To discover multiple tenants, you must follow the steps in the following sections for each tenant in order (in other words, parents must be discovered before their children):

• Creating a Credential for a CloudCenter Suite Tenant
• Discovering an additional CloudCenter Suite Tenant

For each tenant, you must use the administrator account for that tenant when you create the credential.

Creating a Credential for a CloudCenter Suite Tenant

To configure a Basic/Snippet credential to access an additional CloudCenter Suite tenant:

1. Go to the Credential Management page (System > Manage > Credentials).
2. Locate the credential you used to discover the root tenant, then click its wrench icon (). The Edit Basic/Snippet Credential modal appears.
3. Enter values in the following fields:

• Credential Name. Enter a new name for the CloudCenter Suite tenant credential.

• Username. Enter the User ID for a CloudCenter Suite user that is an administrator for the tenant you want to discover.

  The account specified must be an API user, not a GUI user.

• Password. Enter the API key for the user you entered in the Username field.

4. Leave all other fields set to the default values. Click the Save As button.

Discovering an Additional CloudCenter Suite Tenant

To discover an additional tenant:

• From the Device Properties page for the CloudCenter Suite root device, click the name of the CloudCenter Cluster device that appears in the Root Device field.
• Click the Collections tab. The Dynamic Application Collections page appears.

3. Select the checkbox for the "Cisco: CloudCenter Tenant Discovery" Dynamic Application.
4. In the Select Action drop-down list, select the credential you created for the tenant.
5. Click Go.

Viewing CloudCenter Suite Component Devices

You can view CloudCenter Suite component devices in the following places in the user interface:

• The Device Investigator Map page (click Map in the Device Investigator page) displays a map of a particular device and all of the devices with which it has parent-child relationships. Double-clicking any of the listed devices reloads the page to make the selected device the primary device.
• The Device Components page (Devices > Device Components) displays a list of all root devices and component devices discovered by SL1. The Device Components page displays all root devices and component devices in an indented view, so you can easily view the hierarchy and relationships between child devices, parent devices, and root devices. To view the component devices associated with CloudCenter Suite, find the CloudCenter Suite root device and click its plus icon (+).
• The Component Map page (Classic Maps > Device Maps > Components) allows you to view devices by root node and view the relationships between root nodes, parent components, and child components in a map. This makes it easy to visualize and manage root nodes and their components. SL1 automatically updates the Component Map as new component devices are discovered. The platform also updates each map with the latest status and event information. To view the map for CloudCenter, go to the Component Map page and select the map from the list in the left NavBar. To learn more about the Component Map page, see the section on Maps.

Viewing CloudCenter Suite Component Devices in the SL1 Classic User Interface

In addition to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface), you can view CloudCenter Suite component devices in the following places in the user interface:

• The Device View page displays a map of a particular device and all of the devices with which it has parent-child relationships. Double-clicking any of the devices listed reloads the page to make the selected device the primary device:

• The Device Components page (Devices > Device Components) displays a list of all root devices and component devices discovered by SL1 in an indented view, so you can easily view the hierarchy and relationships between child devices, parent devices, and root devices. To view the component devices associated with CloudCenter Suite, find the CloudCenter Suite root device and click its plus icon (+):

• The Component Map page (Classic Maps > Device Maps > Components) allows you to view devices by root node and view the relationships between root nodes, parent components, and child components in a map. This makes it easy to visualize and manage root nodes and their components. SL1 automatically updates the Component Map as new component devices are discovered. The platform also updates each map with the latest status and event information. To view the map for CloudCenter Suite, go to the Component Map page and select the map from the list in the left NavBar. To learn more about the Component Map page, see the section on Views.

Manually Aligning Cisco CloudCenter Suite to a MongoDB on a Docker Swarm

If you want to monitor your MongoDB instance, you must have both the "Docker" and "Cisco CloudCenter Suite" PowerPacks installed. You must also have the Docker Swarm discovered and the component tree for it built out before doing the following steps to align the MongoDB Status Dynamic Application to your MongoDB instance.

To manually align the MongoDB Status Dynamic Application:

1. Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface).

2. Locate the Docker Service where your MongoDB instance resides, and then click its wrench icon (). The Device Properties page appears.
3. Click the Collections tab. The Dynamic Application Collections page appears.
4. Click the Actions button and select Add Dynamic Application from the menu.

5. In the Dynamic Application Alignment modal:

• In the Dynamic Applications field, select MongoDB Status.
• In the Credentials field, select the credential that you used to discover the Docker Swarm.

6. Click Save to align the Dynamic Application with the Docker Service. The Dynamic Application begins collecting data at its default polling interval.

Manually Aligning RabbitMQ to the Remote Cloud

If you want to monitor your remote cloud using RabbitMQ, you must have both the "Docker" and "AMQP: RabbitMQ" PowerPacks installed. You must also have the Docker swarm (remote cloud) discovered and the component tree for it built out before doing the following steps to align RabbitMQ with your remote cloud.

1. Open the Device Components page (Devices > Device Components and locate your remote cloud (Docker swarm).

2. Edit the swarm by clicking its wrench icon ().

3. Click on the Collections tab.

4. Add the following RabbitMQ Dynamic Applications to the collection.

• AMQP: RabbitMQ Configuration
• AMQP: RabbitMQ Performance

  1. Click [Actions] and select Add Dynamic Application.

     The Dynamic Application Alignment page appears.

  2. In the Dynamic Applications field, select one of the RabbitMQ Dynamic Applications.

  3. In the Credentials field, select the Basic/Snippet credential you created for RabbitMQ.

     When adding these Dynamic Applications to the remote cloud, you must select the RabbitMQ API credential to use. The API credentials are the same as UI credentials for RabbitMQ. For more information, see "Creating a Credential for RabbitMQ" in the Monitoring RabbitMQ manual.

  4. Click [Save].
  5. Repeat steps a - d for the other unaligned Dynamic Application for RabbitMQ.

Relationships Between Component Devices

SL1 can automatically build relationships between CloudCenter component devices and other associated devices:

• If you discover an ACI system using the Dynamic Applications in the "Cisco: ACI PowerPack" version 106 or later, SL1 will automatically create relationships between CloudCenter Applications and ACI Application Network Profiles.
• If you discover an AWS account using the Dynamic Applications in the "Amazon Web Services" PowerPack version 103 or later, SL1 will automatically create relationships between CloudCenter Applications and AWS EC2 Instances.
• If you discover an Azure account using the Dynamic Applications in the "Microsoft: Azure" PowerPack version 103 or later, SL1 will automatically create relationships between CloudCenter Applications and Azure Virtual Machines.
• If you discover a vCenter device using the Dynamic Applications in the "VMware: vSphere Base Pack" PowerPack version 207 or later, SL1 will automatically create relationships between CloudCenter Applications and VMware Virtual Machines.