Cisco: UC VOS Applications PowerPack Release Notes, version 109

Version 109 of the Cisco: UC VOS Applications PowerPack includes updates to Dynamic Applications, new device class icons, and adds support for PAWS-based discovery in a NAT environment.

  • Minimum Required SL1 Version: 8.14.0

Before You Install or Upgrade

Ensure that you are running version 8.14.0 or later of SL1 before installing "Cisco: UC VOS Applications" PowerPack version 109.

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

Installation or Upgrade Process

To install version 109 of the Cisco: UC VOS Applications PowerPack, perform the following steps:

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.

To install this PowerPack:

  1. Familiarize yourself with the Known Issues for this release.
  2. See the Before You Install or Upgrade section. If you have not done so already, upgrade your system to the 8.14.0 or later release.
  3. Download the "Cisco: UC VOS Applications" version 109PowerPack from the Support Site to a local computer.
  4. Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the Actions menu and choose Import PowerPack. When prompted, import "Cisco: UC VOS Applications" version 109.
  5. Click the Install button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.

See the manual Monitoring Cisco Voice Operating System (VOS) Applications for instructions on using the new PowerPack.

Features

This release includes the following features:

  • Dynamic Applications and Run Book Actions that discover, model, and collect data from all VOS applications and their component devices
  • Event Policies and corresponding alerts that are triggered when VOS applications and devices meet certain status criteria
  • Device Classes for each of the VOS applications and devices monitored
  • Sample credentials for discovering VOS applications and devices

Enhancements and Issues Addressed

The following enhancements and addressed issues are included this release of the "Cisco: UC VOS Applications":

  • Versions 8.x and 9.x of the Cisco products monitored by this PowerPack are no longer supported. Supported releases are now 10.x and above.
  • The Collector Affinity setting in all Dynamic Applications in the PowerPack was updated to Root device collector by default.
  • The "Cisco: IM&P XCP Auth Component" Dynamic Application was updated to add "%M" to the event message for the "Cisco: % SASL Plain Failures Exceeded Threshold" event policy.
  • Event policy names in the "Cisco: IM&P XCP Auth Component" Dynamic Application were updated to meet content standards.
  • The Cisco content library was updated to support PAWS-based discovery in a NAT environment, and to use the default cipher for communication between the Data Collector and target devices.
  • New SVG Icons were added to the Device Classes in the PowerPack for the new user interface. NOTE: This update does not impact the classic SL1 user interface prior to SL1 version 10.1.0. SL1 version 10.1.0 and later will allow PowerPacks with SVG icons to be installed.

Known Issues and Workarounds

The following known issues affect version 109 of the Cisco: UC VOS Applications PowerPack:

  • The PowerPack will not install on MUD systems prior to SL1 version 10.1.0.
  • If you have a NAT environment, collection by the "Cisco: VOS Processor Performance" Dynamic Application can take up to 24 hours after upgrading the PowerPack. To start collection for this Dynamic Application right away after upgrading the PowerPack, you will need to refresh the session key by running the following query on the Data Collector:

DELETE FROM cache.dynamic_app WHERE 'key' in (app_<VOS Processor Performance ID>_did_<device ID>)

  • The "Cisco: PAWS Services Configuration" Dynamic Application might display some blank fields for older Cisco Unified Communications products because the PAWS API does not provide the applicable data. This issue does not affect newer Cisco Unified Communications products.
  • Cisco Unified Communications products under high CPU load may return HTTP 401 Unauthorized to API requests. This will display in SL1 as "Failed to query VOS object - authentication issue. Response code:401." This message typically indicates an issue with the credential's username and password or the permissions of the associated account. It can also indicate the Cisco Unified Communications product is too busy to process and respond to the API request.