Cisco: Meeting Server PowerPack PowerPack Release Notes, version 101

Version 101 of the Cisco: Meeting Server PowerPack includes updates to Dynamic Application alerts and addresses collection issues.

  • Minimum Required SL1 Version: 8.7.0

Before You Install or Upgrade

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

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

Installation 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:

  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:

  • Dynamic Applications to discover and monitor Cisco Meeting Server devices
  • 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 this release of the "Cisco: Meeting Server" PowerPack:

  • The following alerts in the "Cisco: Meeting Server Alarms Configuration" Dynamic Application were updated to include a check to see if their corresponding unhealthy alert is active:
  • Cisco: Meeting Server RTT Absent
  • Cisco: Meeting Server Packet Loss Absent
  • Cisco: Meeting Server Jitter Absent
  • The "Cisco: Meeting Server System Configuration" Dynamic Application was updated to continue to collect data from all caches, even if one cache does not respond.
  • The following Dynamic Applications were updated to address a collection issue:
  • Cisco: Meeting Server Alarms Configuration
  • Cisco: Meeting Server CoSpaces Cache
  • Cisco: Meeting Server System Status Cache
  • Cisco: Meeting Server Tenants Cache
  • Users no longer need to list the port number next to the IP address in the Hostname/IP field when setting up the Basic/Snippet credential for the API interface. All API requests now use the port set in the Port field.
  • An issue was addressed in the "Cisco: Meeting Server Alarms Configuration" Dynamic Application in which the 'numberOfSysAlarms' exception kept occurring.
  • The "Cisco: Meeting Server Alarms Configuration" Dynamic Application was updated to address an issue where the Cisco: Meeting Server Packet Loss Absent alert was not getting triggered.
  • The "Cisco: Meeting Server System Performance" and "Cisco: Meeting Server System Configuration" Dynamic Applications were updated to address an issue that was causing them to not auto-align during nightly discovery.
  • An alert was added to the "Cisco: Meeting Server System ID Cache" Dynamic Application discovery snippet that triggers the "Cisco: Meeting Server Application Alignment" run book action to manually align the "Cisco: Meeting Server System Configuration" Dynamic Application.
  • An alert was added to the "Cisco: Meeting Server System Status Cache" Dynamic Application discovery snippet that triggers the "Cisco: Meeting Server Application Alignment" run book action to manually align the "Cisco: Meeting Server System Performance" Dynamic Application.

Known Issues

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

  • 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.