Cisco: UCS Director PowerPack Release Notes, version 105

Version 105 of the Cisco: UCS Director PowerPack includes updates to many of the PowerPack's Dynamic Applications.

  • Minimum Required SL1 Version: 8.7.1.2

Before You Install or Upgrade

Ensure that you are running version 8.7.1.2 or later of SL1 before installing "Cisco: UCS Director" PowerPack version 105.

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

Installation or Upgrade Process

To install version 105 of the Cisco: UCS Director 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.7.1.2 or later release.
  3. Download the "Cisco: UCS Director" version 105PowerPack 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: UCS Director" version 105.
  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 UCS Director for instructions on using the new PowerPack.

Features

This release includes the following features:

  • Dynamic Applications that enable the ScienceLogic platform to discover, model, and monitor Cisco UCS Director devices
  • Event Policies that are triggered when Cisco UCS Director component devices meet certain status criteria
  • Device Classes for each type of Cisco UCS Director component device monitored
  • A sample Credential for discovering Cisco UCS Director component devices

Enhancements and Issues Addressed

The following enhancements and addressed issues are included this release of the "Cisco: UCS Director":

  • The Run Book Actions included in the PowerPack were updated to authenticate API requests using SHA256 hashing. This method is required when running a Federal Information Processing Standard (FIPS)-compliant installation of the ScienceLogic platform and is supported in versions 8.4.2 and later of the platform.

NOTE: The platform still supports OpenSSL MD5 hashing for non-FIPS-compliant installations.

NOTE: For more information about authenticating API requests using SHA256 or MD5 hashing, see the Using the ScienceLogic API manual.

  • The following Dynamic Applications were updated to address exceptions that were appearing after the discovery of Cisco Hyperflex systems or CloudCenter devices:
  • Cisco: UCSD ACI APIC Account Mapping Cache
  • Cisco: UCSD Bare Metal Server Discovery
  • Cisco: UCSD Cluster Discovery
  • Cisco: UCSD IP/Subnet Pool Policy Stats
  • Cisco: UCSD License Counts
  • Cisco: UCSD Root Device Configuration
  • Cisco: UCSD Service Monitoring
  • Cisco: UCSD Service Requests
  • Cisco: UCSD Site Discovery
  • Cisco: UCSD Vitals
  • The "Cisco: UCSD Application Container Discovery" Dynamic Application was updated to support the APIC container type.

  • The "Cisco: UCSD Container Application Configuration" Dynamic Application was updated to collect and display configuration data for the APIC, VSG, and Fabric container types included on UCS Director 6.5.

  • The "Cisco: UCSD Cloud Discovery" Dynamic Application was updated to address an issue that was causing "NoneType" exceptions to appear in the device log.
  • The "Cisco: UCSD POD Performance" Dynamic Application was updated to ensure that all data collected is correct and displayed in the performance report.
  • The "Cisco: UCSD Service Monitoring" Dynamic Application was updated to ensure that database information is collected correctly and that no empty rows appear in the device log for the "Cisco: UCSD Service Status in error state" alert.
  • An issue was addressed that was causing the "DR Enabled" collection object in the "Cisco: UCSD Application Container Configuration" Dynamic Application to appear blank due to a missing API call.
  • An issue was addressed that was causing exceptions to appear in the system log for the "Cisco: UCSD Application Container Counts" Dynamic Application after the UCS Director system had been discovered.
  • An issue was addressed that was causing exceptions to appear in the system log for the "Cisco: UCSD Application Container Discovery" Dynamic Application when attempting to discover dCloud in UCS Director version 6.0.
  • An issue was addressed that was causing the data collected by the "Cisco: UCSD Vitals" Dynamic Application to not match the top values that are collected and displayed in the performance report.
  • An issue was addressed that was causing the "UCS Director Device Class Realignment" Run Book Action to not reclassify the UCS Director root device after discovery.
  • An issue was addressed that was preventing the appropriate Dynamic Applications from aligning to Pod component devices. This issue was also preventing the cloud component devices under the Pods from being discovered.

Known Issues

This release has no known issues.