Cisco: Hyperflex PowerPack Release Notes, version 105

Version 105 of the Cisco: Hyperflex PowerPack updates the silo_api_support library from version 0.1.2 to 0.1.4 to support Aurora 3.

  • Minimum Required SL1 Version: 12.1.2

Before You Install or Upgrade

Ensure that you are running version 12.1.2 or later of SL1 before installing "Cisco: HyperflexPowerPack version 105.

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.

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

  • Updated the silo_api_support library from version 0.1.2 to 0.1.4 to support Aurora 3.

Known Issues and Workarounds

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

  • This PowerPack is designed for Hyperflex clusters with HX appliance types. UCS appliance types are not fully supported. While overall collection will work when these types exist in the environment, some Dynamic Applications may not function correctly.

  • When upgrading the PowerPack directly from version 102 to 104, or from version 102 to 103 to 104, the "Cisco: Hyperflex Device Class Realignment" run book action policy may display an event error and fail to assign a device class to a device. To work around this issue, delete the event from the Events tab in the Device Summary. The run book action policy will execute and assign the corresponding device class in the next collection cycle.

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