HPE: Edge Connect (Silver Peak) PowerPack Release Notes Version 101

Version 101 of the HPE: Edge Connect (Silver Peak) PowerPack contains multiple updates to the "HPE: Edge Connect Appliance Alarms" Dynamic Application, adds a new example credential for API key authentication, and all PowerPack components have been renamed to reflect the HPE: Edge Connect acquisition of Silver Peak.

Before You Install or Upgrade

Ensure that you are running version 11.2.0 or later of SL1 before installing "HPE: Edge Connect (Silver Peak)" PowerPack version 101.

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

Installation and Upgrade Process

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.

Features

This release includes the following features:

  • Discovers all HPE: Edge Connect SD WAN orchestrators, appliances, and groups
  • Collects and stores key metrics such as alarms and performance data in the SL1 data lake
  • Monitors alarms, availability, performance, bandwidth, and utilization of HPE: Edge Connect devices and tunnels
  • Models relationships between all HPE: Edge Connect SD WAN devices

The initial release of the PowerPack also includes the following features:

  • The following Dynamic Applications that discover and collect data from Silver Peak Orchestrator, along with its groups and appliances:
    • HPE: Edge Connect Appliance Discovery
    • HPE: Edge Connect Group Discovery
    • HPE: Edge Connect Root Group Discovery
    • HPE: Edge Connect Appliance Configuration
    • HPE: Edge Connect Appliance Tunnel Configuration
    • HPE: Edge Connect Appliance Alarms
    • HPE: Edge Connect Appliance Alarm Summary Stats
    • HPE: Edge Connect Interface Performance
    • HPE: Edge Connect Orchestrator Configuration
    • HPE: Edge Connect Orchestrator Alarms
    • HPE: Edge Connect Orchestrator Alarm Summary Stats
    • HPE: Edge Connect Orchestrator Performance
  • Device Classes for each type of monitored HPE: Edge Connect device:
    • Unity Orchestrator
    • Group
    • EC-V
    • EC-XS
    • EC-US
    • EC-S-SR
    • EC-S-LR
    • EC-S
    • EC-M-B
    • EC-M-P
    • EC-SFP-SR
    • EC-SFP-LR
    • EC-L-B
    • EC-L-P
    • EC-L-B-NM
    • EC-L-P-NM
    • EC-CL-B
    • EC-XL-P
    • EC-XL-B-NM
    • EC-XL-P-NM
  • Event Policies and corresponding alerts that are triggered when HPE: Edge Connect devices meet certain status criteria
  • A sample Credential for discovering HPE: Edge Connect devices
  • A Device Template for Silver Peak Unity Orchestrator
  • Dashboards that display key metrics for the Orchestrator and for each appliance

Enhancements and Issues Addressed

  • The PowerPack and all of its components (Dynamic Applications, Device Classes, Event Policies, etc.) have been renamed to reflect the HPE: Edge Connect acquisition of Silver Peak.

  • Updated events generated by the "HPE: Edge Connect Appliance Alarms" Dynamic Application to include the data in the Source column from Silver Peak Unity Orchestrator.

  • Addressed an issue with the "HPE: Edge Connect Appliance Alarms" Dynamic Application that caused a "Healthy" event to be raised before the original event condition was actually cleared. As part of the fix, the "HPE: Edge Connect Appliance Alarms" Dynamic Application was updated to raise an alert if a request fails to retrieve data from the device. Existing alerts will not be cleared prematurely. (Support Case: 00351508)

  • Added a new snippet section to the "HPE: Edge Connect Appliance Alarms" Dynamic Application to allow the user to modify the appliance alarm API query parameters. For more information on configuring the snippet, see the "HPE: Edge Connect (Silver Peak)" manual. Default values have been updated for the following:

    • Max alarms = 200 (increased from 50 in version 100)
    • View = active (unchanged from version 100)

  • Added a new example credential for API key authentication. In order for the new example credential to function, you need to update the host URL and include the Orchestrator API key in the relevant HTTP header.

    ScienceLogic encourages you to use an API Key for authorization instead of any other method. API key authorization is more efficient and resilient. If you have existing authentication issues, ScienceLogic suggests switching to use an API key authorization. If you need to collect with both Cookie (username/password) AND API key methods, ScienceLogic recommends separating the methods into separate SL1 credentials to avoid confusion.

  • Addressed an issue that caused Dynamic Applications to report 401 authentication errors due to a database lock. (Support Case: 00363500)

  • Updated the description of the "HPE: Edge Connect Orchestrator Alarms" Dynamic Application to say "This Dynamic Application collects both open and closed Orchestrator alarms, and does not trigger events by default."

If you want SL1 to show events for alarms collected from the Orchestrator device, create an event policy for each severity you want to alert on to match the alert policies defined in the "HPE: Edge Connect Orchestrator Alarms" Dynamic Application.

Known Issues

The following known issues affect version 101 of the HPE: Edge Connect (Silver Peak) PowerPack:

  • The following Device Dashboards of the HPE: Edge Connect (Silver Peak) PowerPack are not linked to any device class of this PowerPack:

    • HPE: Edge Connect Appliance

    • HPE: Edge Connect Group

    • HPE: Edge Connect Orchestrator

  • The error message "[REST-PACK]: Critical - AID 2224: Unable to communicate with API: 401 Client Error: Unauthorized. App Name: Silver Peak: Root Group Discovery" occurs when executing the "Silver Peak: Root Group Discovery" Dynamic Application. Silver Peak has a default setting enabled called "Enforce CSRF Token Check" that requires a token in the headers of the API request that SL1 makes to the orchestrator, but version 100 of the Silver Peak PowerPack does not support this. For information on troubleshooting this issue, see the Troubleshooting the SilverPeak PowerPack section in the Monitoring SilverPeak manual.