Cisco: Hyperflex PowerPack Release Notes, version 103

Version 103 of the Cisco: Hyperflex PowerPack updates collections to continue to work after the deprecation of REST APIs in version 4.5 of the Cisco HyperFlex API.

  • Minimum Required SL1 Version: 10.1.0

Before You Install or Upgrade

Ensure that you are running version 10.1.0 or later of SL1 before installing "Cisco: Hyperflex" PowerPack version 103.

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

NOTE: The Cisco: Hyperflex PowerPack supports only HyperFlex version 4.0 and later.

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:

  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.

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:

  • An example credential you can use to create SOAP/XML credentials to connect to HyperFlex data clusters
  • Dynamic Applications to discover and monitor HyperFlex data clusters
  • A Device Class for HyperFlex data clusters
  • Event Policies and corresponding alerts that are triggered when HyperFlex data clusters meet certain status criteria
  • A Run Book Action and Policy to ensure that HyperFlex devices are classified to the appropriate Device Class

Enhancements and Issues Addressed

The following enhancements and addressed issues are included this release of the "Cisco: Hyperflex" PowerPack:

  • Dynamic Applications have been updated to continue to work after the deprecation of REST APIs in version 4.5 of the Cisco HyperFlex API.
  • All Dynamic Applications have been updated to use the SL1 snippet framework.
  • The Expiry Delay setting for event policies in the PowerPack was updated according to content standards.
  • Alerts in the "Cisco: Hyperflex Cluster Configuration" Dynamic Application were updated to check for a status of "NORMAL" instead of "normal". (Case: 00153817; Jira ID: SOL-13093)
  • Improved event messages to include the device ID and Application ID.
  • Updated the "Cisco: Hyperflex Node Capacity Usage High" alert formula in the "Cisco: Hyperflex Disk Configuration" Dynamic Application to prevent unnecessary alerts. (Case: 00154068; Jira ID: SOL-11619)
  • Updated the "Cisco: Hyperflex Controller VM Not Ready" alert formula to address an issue in which ready states were not being reported for healthy non-compute nodes. (Case: 00133555; Jira ID: SOL-12568)
  • The "Cisco: Hyperflex CLI Cache" Dynamic Application has been disabled and will no longer be used by the "Cisco: Hyperflex Cluster Performance" and "Cisco: Hyperflex Relationships" Dynamic Applications.
  • The Collector Affinity field has been set to Assigned collector by default in all Dynamic Applications.
  • The severity of the "Cisco: Hyperflex Disk Offline" event was changed from Minor to Major.

Known Issues

The following known issues affect version 103 of the Cisco: Hyperflex PowerPack:

  • The "Cisco: Hyperflex Service Configuration" Dynamic Application will stop collecting data when the "/rest/services" endpoint is deprecated.
  • In SL1 version 8.10.0, the following Minor events are displayed for the "Cisco: Hyperflex Resiliency Stats" Dynamic Application:

78:StorageProc1: Non-digits in oid with object id: 18882, did:4 in dynamic app:1625 when updating performance value (val:NA)

78:StorageProc1: Non-digits in oid with object id: 18876, did:4 in dynamic app:1625 when updating performance value (val:NA)