F5 BIG-IP PowerPack Release Notes, version 101

Version 101 of the F5 BIG-IP PowerPack includes new Dynamic Applications to collect additional configuration and performance data from F5 BIG-IP devices, plus several additional enhancements.

  • Minimum Required SL1 Version: 8.7.0

Before You Install or Upgrade

Ensure that you are running version 8.7.0 or later of SL1 before installing F5 BIG-IP version 101.

For details on upgrading SL1, see the appropriate Release Notes.

Installation or Upgrade Process

To install version 101 of the F5 BIG-IP PowerPack, perform the following steps:

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.0 or later release.
  3. Download the "F5 BIG-IP" version 101PowerPack 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 "F5 BIG-IP" version 101.
  5. Click the Install button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.

Features

Version 101 of the F5 BIG-IP  PowerPack includes the following features:

  • Dynamic Applications that collect configuration and performance data about F5 BIG-IP devices.
  • An SNMP credential template.
  • Device classes for all F5 BIG-IP devices are included in the PowerPack.
  • Event policies that are triggered when F5 BIG-IP devices meet certain status criteria.

Enhancements and Issues Addressed

The following enhancements and addressed issues are included in version 101 of the F5 BIG-IP PowerPack:

  • The following Dynamic Applications were added to the PowerPack:
  • F5: Viprion Chassis Slot Status
  • F5 BIG-IP: vCMP VM Configuration
  • F5 BIG-IP: Cluster Status
  • The following Dynamic Applications were updated to include the root device name in alert messages:
  • F5 BIG-IP LTM: Virtual Server Configuration
  • F5 BIG-IP LTM: Pool Configuration
  • F5 BIG-IP LTM: Pool Member Configuration
  • F5 BIG-IP LTM: Node Configuration
  • The Dynamic Application "F5 BIG-IP LTM: Component Counts" will now only align with Local Traffic Managers (LTM) and not Global Traffic Managers (GTM).
  • An issue was addressed in the Dynamic Application "F5 BIG-IP: Performance" that was causing an erroneous Net-SNMP alert about a memory issue to appear. Metrics were added to provide greater accuracy for F5 devices.
  • An issue was addressed in the Dynamic Application "F5 BIG-IP: Node Discovery" where the enabled state and availability state were showing up incorrectly.
  • An issue was addressed in the Dynamic Application "F5 BIG-IP LTM: Pool Discovery: Virtual Server Default Pools" where the enabled state was appearing incorrectly.
  • All physical device classes have been updated with a device tier of 3, component device classes have been changed to tier 1, and BIG-IP LTM device classes are now tier 6.
  • The Dynamic Applications "F5 BIG-IP LTM: Service Discovery" and "F5 BIG-IP LTM: Component Counts" no longer auto-align to Viprion chassis devices.
  • Alert messages now include component names so users can more easily identify which device or server is having the issue.
  • An issue was addressed in the "F5 BIG-IP LTM: Pool Member Discovery" Dynamic Application where incorrect OIDs were specified in a Dynamic Application snippet.
  • The Dynamic Application "F5 BIG-IP LTM: Virtual Server Configuration" changed the names of some configurations to more clearly reflect the metrics being collected.
  • An issue was addressed where some virtual servers and pools were erroneously reporting a state of "Healthy".

Known Issues

The following known issues affect version 101 of the F5 BIG-IP PowerPack:

  • The PowerPack is not backwards compatible for deprecated OIDs. If you are using a system that is outdated, it may fail to collect some data.
  • There is no maximum threshold for number of F5 components. Collectors should be able to handle up to 3500 components but discovering more than 3500 components would slow the system significantly.