Cisco: Meeting Server PowerPack PowerPack Release Notes, version 100

Version 100 of the Cisco: Meeting Server PowerPack is an upgrade to version 0.5 of the Acano: MCU PowerPack. It includes Dynamic Applications, a Device Class, and Event Policies for monitoring Acano devices.

  • Minimum Required SL1 Version: 8.7.0

Before You Install

Ensure that you are running version 8.7.0 or later of SL1 before installing "Cisco: Meeting Server" PowerPack version 100.

For details on upgrading SL1, see the relevant SL1 Platform Release Notes.

Installing the PowerPack

To install this PowerPack:

  1. Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
  2. In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
  3. Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
  4. Click Browse and navigate to the PowerPack file from step 1.
  5. Select the PowerPack file and click Import. The PowerPack Installer modal displays a list of the PowerPack contents.
  6. Click Install. The PowerPack is added to the PowerPack Manager page.

Features

This release includes the following features:

  • The following Dynamic Applications to discover and monitor Cisco Meeting Server devices:
  • Cisco: Meeting Server Alarms Configuration
  • Cisco: Meeting Server CoSpaces Cache
  • Cisco: Meeting Server Network Interface Cache
  • Cisco: Meeting Server NTP Cache
  • Cisco: Meeting Server System Configuration
  • Cisco: Meeting Server System ID Cache
  • Cisco: Meeting Server System Performance
  • Cisco: Meeting Server System Status Cache
  • Cisco: Meeting Server Tenants Cache
  • A Device Class for Cisco Meeting Server devices
  • Event policies that are triggered when Cisco Meeting Server devices meet certain status criteria

Enhancements and Issues Addressed

The following enhancements and addressed issues are included in version 100 of the "Cisco: Meeting Server" PowerPack:

  • The PowerPack, Dynamic Applications, Alerts, and Events were renamed to reflect the branding change from "Acano" to "Cisco: Meeting Server".
  • The "Cisco Meeting Server Example" sample credential was added to the PowerPack. For customers where the API and SSH respond on separate IP addresses, they will need to create separate credentials. Steps for creating these credentials are provided in the Monitoring Cisco: Meeting Server manual.
  • All Dynamic Applications in the PowerPack were updated to prevent the password from being displayed in the debug output.
  • The API-based snippets in the following Dynamic Applications were updated to include the timeout setting from the credential:
  • Cisco: Meeting Server Alarms Configuration
  • Cisco: Meeting Server CoSpaces Cache
  • Cisco: Meeting Server System Status Cache
  • Cisco: Meeting Server Tenants Cache
  • The SSH-based snippets in the following Dynamic Applications were updated to include the timeout setting from the credential:
  • Cisco: Meeting Server Network Interface Cache
  • Cisco: Meeting Server NTP Cache
  • Cisco: Meeting Server System ID Cache
  • An issue was addressed in the following Dynamic Applications that was causing an exception to be raised during discovery:
  • Cisco: Meeting Server Network Interface Cache
  • Cisco: Meeting Server NTP Cache
  • Cisco: Meeting Server Tenants Cache
  • Several alerts and thresholds were removed from the "Cisco: Meeting Server Alarms Configuration" Dynamic Application. A number of new alerts and a new collection object were added.
  • Several alerts were updated in the "Cisco: Meeting Server Jitter Absent" Dynamic Application.
  • Several issues were addressed in the "Cisco: Meeting Server System Configuration" Dynamic Application that were causing errors to appear in the system log during debugging.
  • An issue was addressed in the "Cisco: Meeting Server System ID Cache" Dynamic Application where the unsupported "serial" command was being collected.
  • An issue was addressed in the "Cisco: Meeting Server Alarms Configuration" Dynamic Application in which the alarm type and failure reason were not properly appearing in the alert formula.
  • An issue was addressed in the "Cisco: Meeting Server System ID Cache" Dynamic Application in which it was erroneously auto-aligning non-Cisco Meeting Server devices.

Known Issues

The following known issues affect version 100 of the Cisco: Meeting Server PowerPack:

  • The following Dynamic Applications might not auto-align until nightly discovery:
  • Cisco: Meeting Server System Configuration
  • Cisco: Meeting Server System Performance
  • The Port field is not being used in the credential that connects to the API. Instead, you must add the port to the Hostname/IP field (for example, %D:445 or 10.0.0.2:445).
  • Some of the Dynamic Applications use the Paramiko library for SSH connections. This library is not Federal Information Processing Standards (FIPS)-compliant. Therefore, the PowerPack will not work on FIPS-compliant systems.