NetApp Base PackPowerPack Release Notes, version 109

Version 109 of the "NetApp Base Pack" PowerPack adds Python 3.11 compatibility and updates the security protocol used by the PowerPack's sample credentials.

  • Minimum Required Skylar One (SL1) Version: 12.3.1

Before You Install or Upgrade

Ensure that you are running version 12.3.1 or later of Skylar One before installing the "NetApp Base PackPowerPack.

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

Installation and Upgrade Process

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.

To install this PowerPack:

  1. Search for and download the PowerPack from the PowerPacks page at the ScienceLogic Support Center (Skylar One > PowerPacks).
  2. In Skylar One (formerly 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.

Enhancements and Issues Addressed

The following enhancements are included in the PowerPack:

  • Updated the PowerPack, its execution environment, and Dynamic Applications for Python 3.11 compatibility.

  • Added support for Transport Layer Security (TLS) version 1.3, and updated the sample NetApp credentials to use TLS version 1.2 by default.

  • Updated the "NetApp: SVM Logical Interface Config C-Mode" Dynamic Application to retrieve vserver cache data after normal logical interface (LIF) collection, and added two new collection objects to record the vserver's operational and administrative state on a per-LIF basis.

  • Resolved an issue where disk failure alerts were not triggered for NetApp C-Mode devices due to the "NetApp: Disk Config C-Mode" Dynamic Application failing to collect data when certain expected keys were missing from the XML response. Now, the Dynamic Application handles missing keys by using default values instead of raising an exception, ensuring data collection continues and disk failure events are correctly reported. (Case: 00602207)

  • Updated lxml dependency from 4.9.2 to 4.9.4 to support Python 3.11 compatibility. (Case: 00602207)

Known Issues

The following known issues affect version 109 of the "NetApp Base Pack" PowerPack:

  • Due to increased security restrictions on Security Technical Implementation Guide (STIG)-compliant systems, users might see unexpected behavior when attempting to discover and collect data from a NetApp system. The symptoms include a failure to auto-align Dynamic Applications during discovery and SSL errors during collection after manual alignment.
  • The PowerPack defaults to using SSL (port 443) for connections to the NetApp storage devices. However, Federal Information Processing Standard (FIPS)-compliant systems require TLS and the Certificate Authority (CA) for security. If Skylar One is running in FIPS-compliant mode, the user will need to either:
  • Use the "NetApp w/SSL Option Off" credential that is included in the PowerPack as an example, which directs the PowerPack to use HTTP (port 80) for connections.

OR

  • Use the "NetApp w/SSL/TLS Option" credential that is included in the PowerPack as an example, which directs the PowerPack to use TLS.