Version 105 of the Cisco: Cloud Center PowerPack includes the ability to monitor high-availability (HA) Cloud Center deployments.This version also includes several new Dynamic Applications, Device Classes, Event Policies, Run Book Actions and Automation Policies, and a new sample SOAP/XML Credential to support this enhancement.
Additionally, the PowerPack has been updated to create dynamic component map relationships between Cisco Cloud Center Applications and Cisco ACI Application Network Profiles, to align Dynamic Applications from the Linux Base Pack PowerPack to Cloud Center components, and to discover a new CCO folder (region) component.
- Minimum Required SL1 Version: 8.7.1.2
Before You Install or Upgrade
Ensure that you are running version 8.7.1.2 or later of SL1 before installing " Cisco: Cloud Center" PowerPack version 105.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
Installing or Upgrading the PowerPack
If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.
To install this PowerPack:
- Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
- In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
- Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
- Click and navigate to the PowerPack file from step 1.
- Select the PowerPack file and click . The PowerPack Installer modal displays a list of the PowerPack contents.
- Click . The PowerPack is added to the PowerPack Manager page.
By default, installing a new version of a PowerPack will overwrite all content in that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent the new version of the PowerPack from overwriting local changes for some commonly customized fields.
If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.
For more information about using the PowerPack, see the Monitoring Windows Systems with PowerShell manual.
Features
This release includes the following features:
- Dynamic Applications to discover and monitor Cloud Center devices
- Device classes for each type of Cloud Center device that SL1 monitors
- Event policies and corresponding alerts that are triggered when Cloud Center devices meet certain status criteria
- Sample Credentials you can use as templates to create your own Credentials to monitor Cloud Center deployments
- Run Book Actions that automate some aspects of the device discovery and creation process
Enhancements and Issues Addressed
The following enhancements and addressed issues are included this release of the " Cisco: Cloud Center" PowerPack:
- The PowerPack was updated to enable monitoring for high-availability (HA) Cloud Center deployments. Specifically, the PowerPack can monitor HA modes for the following CloudCenter components:
- Cisco Cloud Manager (CCM) servers and load balancers
- PostgreSQL database servers and load balancers
- Cisco Cloud Center Health Monitors
- AMQP (RabbitMQ) servers and load balancers
- Cisco Cloud Orchestrator (CCO) and load balancers
- The PowerPack was updated to align Dynamic Applications from the Linux Base Pack PowerPack with components on a discovered HA Cloud Center cluster, for users who are runningVersion 105 of the Cisco: Cloud Center PowerPack and version 101 or greater of the Linux Base Pack PowerPack.
- The following Dynamic Applications were added to the PowerPack:
- Cisco: Cloud Center CCC MongoDB Config
- Cisco: Cloud Center CCC Port Monitoring Config
- Cisco: Cloud Center CCC Postgress Config
- Cisco: Cloud Center CCC Process Monitor
- Cisco: Cloud Center CCM Load Balancer Health
- Cisco: Cloud Center HA Discovery
- The following new Device Classes were added to the PowerPack:
- Cloud Center Load Balancer
- Cloud Center Monitor
- Cloud Center PostGres
- Cloud Center RabbitMQ Load Balancer
- A new sample SOAP/XML Credential, "Cisco Cloud Center - HA Example", was added to the PowerPack.
For instructions on using the new Credential, see the Monitoring Cisco Cloud Center manual.
- The following new Event Policies were added to the PowerPack:
| Event Policy Name | Event Source | Severity |
|---|---|---|
| Cisco: Cloud Center Align Process Monitor Dynamic Apps | API | Notice |
| Cisco: Cloud Center CCC Postgres DA Alignment | API | Notice |
| Cisco: Cloud Center CCC Process Monitor Process Not Running | Dynamic | Major |
| Cisco: Cloud Center CCC Process Monitor Process Running | Dynamic | Healthy |
| Cisco: Cloud Center CCM API Disable | API | Major |
| Cisco: Cloud Center CCM API Enable | API | Healthy |
| Cisco: Cloud Center CCM Load Balancer API Disable | API | Critical |
| Cisco: Cloud Center CCO Mongo DA Alignment | API | Notice |
| Cisco: Cloud Center Device Now Available | API | Notice |
| Cisco: Cloud Center Device Unavailable Vanish Timer Update | API | Notice |
| Cisco: Cloud Center Linux Base Pack Alignment | API | Notice |
| Cisco: Cloud Center MongoDB Node Health Unreachable | Dynamic | Major |
| Cisco: Cloud Center MongoDB Node Healthy | Dynamic | Healthy |
| Cisco: Cloud Center Postgres Node Disconnected | Dynamic | Major |
| Cisco: Cloud Center Postgres Node Status Healthy | Dynamic | Healthy |
| Cisco: Cloud Center Postgres Process Status Healthy | Dynamic | Healthy |
| Cisco: Cloud Center Postgres Process Status Not Running | Dynamic | Major |
| Cisco: Cloud Center RabbitMQ Align Dynamic Apps | API | Notice |
| Cisco: Cloud Center RabbitMQ LB Classification | API | Notice |
| Cisco: Cloud Center Vanish Timer Update | API | Notice |
- The following new Run Book Action and Automation Policies were added to the PowerPack:
| Run Book Automation Policy | Run Book Action(s) | Description |
|---|---|---|
| Cisco: Cloud Center Applications Thresholds | Cisco: Cloud Center Applications Thresholds | Sets the thresholds for device vanishing and device purge for the Application Instance components. |
| Cisco: Cloud Center CCC Postgres Dynamic App Alignment | Cisco: Cloud Center Postgres DA Alignment | Aligns the "Cisco: Cloud Center CCC Postgres Config" Dynamic Application. |
| Cisco: Cloud Center CCC Process Monitor Dynamic App Alignment | Cisco: Cloud Center CCC Process Monitor DA Alignment | Aligns the "Cisco: Cloud Center CCC Process Monitor" Dynamic Application. |
| Cisco: Cloud Center CCO Mongo Dynamic App Alignment | Cisco: Cloud Center Orchestrator Mongo DA Alignment | Aligns the "Cisco: Cloud Center CCC MongoDB Config" Dynamic Application. |
| Cisco: Cloud Center Device Available | Cisco: Cloud Center Restored Component | Removes events that set timers for device vanish and device purge for unavailable components. |
| Cisco: Cloud Center Linux Base Pack Alignment | Cisco: Cloud Center Linux Base Pack Alignment | Aligns the Linux Base Pack PowerPack to Cisco Cloud Center HA components. |
| Cisco: Cloud Center Linux Base Pack Status | Informs the Data Collector of the Linux Base Pack PowerPack alignment status. | |
| Cisco: Cloud Center RabbitMQ Dynamic App Alignment | Cisco: Cloud Center RabbitMQ Dynamic App Alignment | Aligns the RabbitMQ Dynamic Applications to Cisco Cloud Center RabbitMQ instances. |
| Cisco: Cloud Center RabbitMQ Load Balancer Classification | Cisco: Cloud Center RabbitMQ Load Balancer Classification | Reclassifies the Cloud Center RabbitMQ Load Balancer. |
| Cisco: Cloud Center Vanish Timer Reset | Cisco: Cloud Center Vanish Timer Reset | Sets the correct timer for device vanish for Application components. |
- The "Cisco: Cloud Center Application Configuration" Dynamic Application was updated to create dynamic component map relationships between Cisco Cloud Center Applications and Cisco ACI Application Network Profiles, for users who are running Version 105 of the Cisco: Cloud Center PowerPack and version 106 or greater of the Cisco: ACI PowerPack.
- The "Cisco: Cloud Center Application Resource Usage" Dynamic Application was updated to collect the following additional metrics:
- Estimated Hourly Cost
- Estimated Monthly Cost
- Estimated Monthly Savings
- Estimated Savings Percentage
- The "Cisco: Cloud Center Region Discovery" and "Cisco: Cloud Center Region Configuration" Dynamic Applications were updated to discover a new CCO folder (region) component, under which CCO component devices now appear in the device tree.
- The "Cisco: Cloud Center Vanish Timer Update" Run Book Action was updated to extend the vanish and purge timer of Cloud Center devices.
- An issue was addressed that was causing the "Cisco: Cloud Center Cloud Discovery" Dynamic Application to generate an exception in the system log if the Cloud Center system did not have any tenant configured.
Known Issues and Limitations
The following known issues affect version 105 of the Cisco: Cloud Center PowerPack:
- When monitoring a high-availability deployment, the use of Basic/Snippet credentials will cause RabbitMQ Dynamic Applications to align to RabbitMQ devices, but those Dynamic Applications will not collect data. This is because SL1 discovers the RabbitMQ load balancer devices as the RabbitMQ components, rather than the actual RabbitMQ components themselves. This means that, even if you manually discover the RabbitMQ components, the PowerPack has no way of linking them with the load balancers. If you would like to collect data for the non-load balancer RabbitMQ components, you can manually align the appropriate credentials.
-
The current implementation of the AMQP: RabbitMQ PowerPack has a known issue where the data comes only from the first node in the cluster, leading to one of the nodes having incorrect data. This issue will be addressed in version 101 of the AMQP: RabbitMQ PowerPack.
- All devices associated with a Cisco Cloud Center instance must be monitored by the same Data Collector.
- If you delete a Cisco Cloud Center device and subsequently want to re-discover the same Cisco Cloud Center device, you must execute the following database query on the Data Collector or All-In-One Appliance that monitored the Cisco Cloud Center device:
DELETE FROM cache.dynamic_app WHERE key LIKE %ccc%;