Cisco Base Pack PowerPack Release Notes, version 212

Version 212 of the Cisco Base Pack PowerPack includes new Device Classes, new Dynamic Applications, and addresses a number of issues.

  • 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 Base Pack" PowerPack version 212.

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

Installing or Upgrading the PowerPack

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 (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.

For more information about using this PowerPack, see the Monitoring Switches, Routers, and Firewalls with SNMP manual.

Features

This release includes the following features:

  • Dynamic Applications that collect CPU, environmental status, memory, and basic configuration data for Cisco devices
  • Event Policies that are triggered when Cisco devices meet certain status criteria
  • Device Classes for each type of Cisco device monitored
  • Sample Credentials for discovering Cisco devices using SNMP
  • A device Dashboard that displays host resource, interface, and topology information for Cisco devices

Enhancements and Issues Addressed

The following enhancements and addressed issues are included in version 212 of the "Cisco Base Pack" PowerPack:

  • The "Cisco: VRF BGP Peers" Dynamic Application was added to the PowerPack.
  • The following asset links were added to the PowerPack (in the format Dynamic Application/Collection Object/Asset Link):
  • Cisco: FEX Configuration/Serial Number/Serial Number
  • Cisco: FRU Control Configuration/Model Name/Model
  • Cisco: FRU Control Configuration/Serial Number/Serial Number
  • Device Software Version/IOS Version/Operating System
  • 781 new device classes were added to the PowerPack.
  • All Dynamic Applications in this version of the PowerPack have been updated to have Collector Affinity set to Assigned collector.
  • "Cisco: Fan Configuration" is a new Dynamic Application that will report fan operational status as a percentage of total fans operational instead of individual fans as in the "Cisco: Environmental Status" Dynamic Application. To avoid duplicate events, we suggest disabling the fan status collection objects in the "Cisco: Environmental Status" Dynamic Application if the "Cisco: Fan Configuration" Dynamic Application is enabled.
  • The "Cisco: Environmental Entity Status" Dynamic Application was added to the PowerPack.
  • The "Cisco: Router IOS Version" Dynamic Application was renamed to the "Device Software Version" Dynamic Application.
  • A number of guideline issues were fixed, such as guide text added to presentation objects, added threshold values, and adding missing descriptions to objects in the PowerPack.
  • The "Discovery " collection object in the "Cisco: Environmental Status" Dynamic Application was updated to properly align the Dynamic Application to devices with environmental monitor OIDs.
  • The Summarization State was set to Enabled for all presentation objects in the "Cisco: IPSEC Global Ph1 Performance" and "Cisco: Fibre Channel Performance" Dynamic Applications.
  • All collection objects (except Active Tunnels) for the "Cisco: IPSEC Global Ph1 Performance" Dynamic Application were updated from Performance Gauge to Performance Counter.
  • The "Cisco: FRU Control Configuration" Dynamic Application was updated to address an issue in which extra, incorrect, and missing data was occurring for the "Module Status," "Power Status," "Fan Status," and "Power Information" collection groups.
  • The device class for "ciscoC68xxVirtualSwitch" was updated to address an issue in which it was incorrectly classified as "UCS EN 120S".
  • The following issues were addressed with the "Cisco: Temperature Sensor Performance" Dynamic Application:
  • The overall performance of the Dynamic Application was improved.
  • The Dynamic Application was updated to address an issue in which the SNMP walk was showing results but the Dynamic Application was not showing data.
  • The Dynamic Application was updated to fix an issue with spikes in temperature values collected from devices.

Known Issues

The following known issues affects this version of the PowerPack:

  • The "Cisco: Environmental Entity Status" Dynamic Application does not use any precise conversion for collected data values.

  • The "Cisco: Environmental Entity Status" Dynamic Application does not align automatically when the PowerPack is upgraded from earlier versions of this PowerPack. Nightly discovery is needed to align it, but if you need to align the Dynamic Application immediately, re-run the discovery session.
  • A known issue with versions 8.6.2.3, 8.7.0, and 8.8.0 of the ScienceLogic platform is causing false events to be triggered when configuration Dynamic Applications attempt to collect data that is not available.