Configuration and Discovery

The following sections describe how to configure and discover HPE: Edge Connect (Silver Peak) services for monitoring by SL1 using the HPE: Edge Connect (Silver Peak) PowerPack:

Prerequisites for Monitoring HPE: Edge Connect (Silver Peak)

To configure the SL1 system to monitor Silver Peak Unity Orchestrator and edge devices using the HPE: Edge Connect (Silver Peak) PowerPack, you must have the following information about the Unity Orchestrator that you want to monitor:

The IP address or URL of your Orchestrator
The username and password for the administrator account on your Orchestrator

Enabling Legacy API Support

Version 9.3.0 of HPE: Edge Connect updated 3 APIs which caused issues with existing Dynamic Applications:

HPE: Edge Connect Appliance Alarms
HPE: Edge Connect Orchestrator Alarms Summary Stats
HPE: Edge Connect Appliance Config

If you are using version 9.3.1 or newer of HPE: Edge Connect (Silver Peak), enable the enableLegacyApisSupport setting in the HPE: Edge Connect user interface. Additionally, be sure to follow the steps below and add the Accept-Encoding:identity HTTP Header to your credentials to support HPE: Edge Connect Orchestrater versions 9.3.1 and newer.

Version 9.3.0 of HPE: Edge Connect is not supported by the HPE: Edge Connect (Silver Peak) PowerPack. ScienceLogic recommends updating to version 9.3.1 or later.

Creating a Credential for HPE: Edge Connect (Silver Peak)

To configure SL1 to monitor HPE: Edge Connect (Silver Peak), you must create a credential. This credential allows the Dynamic Applications in the HPE: Edge Connect (Silver Peak) PowerPack to communicate with your HPE: Edge Connect (Silver Peak) Unity Orchestrator.

Starting with version 200 of the HPE: Edge Connect (Silver Peak) PowerPack, you must use an API key credential for authorization. Cookie-based authentication is not supported, and failure to switch to API key authentication will cause monitoring to break.

Creating an API Credential for HPE: Edge Connect (Silver Peak)

As of version 200, an example universal credential that you can edit for your own use is included in the PowerPack. To configure a universal credential to access the Orchestrator:

Go to the Credentials page (Manage > Credentials).
Locate the HPE: Edge Connect API Key Example (UCF) sample credential, click its Actions icon () and select Duplicate. A copy of the credential, called HPE: Edge Connect API Key Example (UCF) copy appears.
Click the Actions icon () for the HPE: Edge Connect API Key Example (UCF) copy credential and select Edit. The Edit Credential page appears:
Supply values in the following fields:
- Name. Type a new name for the HPE: Edge Connect credential.
- All Organizations. Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the What organization manages this service? drop-down field to align the credential with those specific organizations.
- Timeout (ms). Time, in milliseconds, after which SL1 will stop trying to communicate with the device from which you want to retrieve data.
- URL. Enter the URL or IP address for the Orchestrator.
- API Key. Enter the API Key to use for authentication.
Click Save & Close.

Creating a SOAP/XML Credential for HPE: Edge Connect (Silver Peak)

To configure a SOAP/XML credential to access the Orchestrator:

Go to the Credential Management page (System > Manage > Credentials).
Locate the HPE: Edge Connect API Key Example credential, and then click its wrench icon (). The Edit SOAP/XML Credential modal appears.

Enter values in the following fields:

Basic Settings

Profile Name. Enter a new name for the credential.

URL. Enter the URL or IP address for the Orchestrator

As of version 9.2 of the Orchestrator, the API user for the credential in SL1 must be a "non-RBAC" user with read-only permissions and no user role applied.

Soap Options

Embedded Password. Enter the API Key to use for authentication in the format of X-Auth-Token:<api_key>.

Add the following HTTP Headers:

content-type: application/json
Accept-Encoding:identity

For all other fields, use the default values.
Click the Save As button.

The "Accept-Encoding:identity" HTTP Header is needed to support HPE: Edge Connect Orchestrater versions 9.3.1 and newer. Be sure to create a different credential for each orchestrator you want to discover.

Creating a Virtual Device for the Orchestrator

To configure SL1 to monitor HPE: Edge Connect (Silver Peak), you must create a virtual device to represent your Orchestrator. The PowerPack includes a Device Class (HPE: Edge Connect Orchestrator) for the Orchestrator.

To create a virtual device, you must complete the following tasks:

Go to the Device Manager page (Devices > Device Manager).

From the Actions menu, select Create Virtual Device.
The Create Virtual Device modal appears.

Supply a value in each of the following fields:

Device Name. Name of the virtual device. Can be any combination of alphanumeric characters, up to 32 characters in length.
Organization. Organization to associate with the virtual device. Select from the drop-down list of all organizations in SL1.
Device Class. The device class to associate with the virtual device. Select HPE: Edge Connect Orchestrator from the drop-down list of device classes.
Collector. Specifies which instance of SL1 will perform auto-discovery and gather data from the device. Can also specify a "virtual" poller. Select from the drop-down list of all collectors in SL1.

Select the Add button to save the new virtual device.

For more information about virtual devices, see Virtual Devices.

Aligning the Virtual Device with the Device Template

When SL1 discovers a device, SL1 applies some default configuration settings to that device. You can edit these settings or use a device template to edit the settings for one or more devices. In this step, you will use the "HPE: Edge Connect Orchestrator Template" to apply a configuration to your HPE: Edge Connect (Silver Peak) Unity Orchestrator.

To use a device template to change the configuration of one or more devices:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface).
In the Device Manager page, select the checkbox for your Orchestrator virtual device.

In the Select Actions field, in the lower right, select the option Modify by Template. Click the Go button.
The Bulk Device Configuration page appears.

In the Template field, select "HPE: Edge Connect Orchestrator Template".
Save When Applied & Confirmed. From the Bulk Device Configuration page, you can edit the value in any of the fields in any of the tabs of the device template.

If you select this field, any changes you make to fields in the Bulk Device Configuration page will be saved to the template.
If you don't select this field, you can edit the values in any of the fields, and the edited values won't be saved in the device template, but will be applied to the device group.

Click the [Apply] button to apply the device template and any changed field values to the selected device.
The Device Setting Confirmation page appears.

In this page, you can view any settings in the device template that are different from SL1 default settings.
You can click a field to disable it. When you disabled a field, its value will not be applied to the selected device group or selected devices.
You can also view a list of devices to which the device template will be applied.

To approve the changes and the device list, click the Confirm button in the Device Setting Confirmation page.
The device template will be applied to the selected device.

Verifying Discovery and Dynamic Application Alignment

To verify that SL1 has automatically aligned the correct Dynamic Applications during discovery:

After discovery has completed, click the device icon for the HPE: Edge Connect (Silver Peak) Unity Orchestrator. From the Device Properties page for the Orchestrator, click the Collections tab. The Dynamic Application Collections page appears.
All applicable Dynamic Applications for the service are automatically aligned during discovery.

It can take several minutes after the discovery session has completed for Dynamic Applications to appear in the Dynamic Application Collections page.

You should see the following Dynamic Applications aligned to the HPE: Edge Connect (Silver Peak) service:

HPE: Edge Connect Appliance Alarms
HPE: Edge Connect Orchestrator Alarm Summary Stats
HPE: Edge Connect Orchestrator Performance
HPE: Edge Connect Orchestrator Alarms
HPE: Edge Connect Orchestrator Configuration
HPE: Edge Connect Root Group Discovery

If the listed Dynamic Applications have not been automatically aligned during discovery, or you want to align more Dynamic Applications, you can align them manually. To do so, perform the following steps:

Click the Action button, and then select Add Dynamic Application. The Dynamic Application Alignment page appears:
In the Dynamic Applications field, select the Dynamic Application you want to align. You can narrow the search, as shown in the example above.
In the Credentials field, select the credential specified in the table.
Click the Save button.
Repeat steps 1-4 for any other unaligned Dynamic Applications.

Configuring the HPE: Edge Connect Appliance Alarms Dynamic Application

The get-alarm-rest snippet in the "HPE: Edge Connect Appliance Alarms" Dynamic Application can be customized to modify the appliance alarm API query parameters.

To modify the get-alarm-rest snippet:

Go to the Dynamic Applications Manager page (System > Manage > Applications).
Search for the "HPE: Edge Connect Appliance Alarms" Dynamic Application and then click its wrench icon ().
Select the Snippets tab.
In the Snippet Registry pane, find the get-alarm-rest snippet and select its wrench icon () get-alarm-rest.
In the Snippet Code field, locate the # SET APPLIANCE ALARMS QUERY CUSTOMIZATIONS HERE # section.
The following values can be edited:
- CUSTOM_VIEW_FILTER_VALUE
- CUSTOM_SEVERITY_FILTER_VALUE
- CUSTOM_ORDER_BY_SEVERITY_FILTER_VALUE
- CUSTOM_MAX_ALARMS_FILTER_VALUE
Click the Save button.

If the Orchestrator experiences a high volume of alarms, you can raise the "max alarm" value in the API call that fetches alarms to avoid missing alarms. Be advised, this will increase the load on both the orchestrator and the collector. How far the limit can be raised depends on network latency and the workload of the orchestrator. You can also consider configuring webhooks or email alerts to push alarms into SL1 instead of polling for alarms. For more information, see the section on Using Webhooks to Generate Events in the SL1 Events manual.

Viewing HPE: Edge Connect (Silver Peak) Devices

In addition to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface), you can view the HPE: Edge Connect (Silver Peak) Unity Orchestrator and all connected devices in the following places in the user interface:

The Device Components page (Registry > Devices > Device Components) displays a list of all root devices and component devices discovered by SL1 in an indented view, so you can easily view the hierarchy and relationships between child devices, parent devices, and root devices. To view the component devices associated with the Orchestrator, find the Orchestrator and click its plus icon (+):

The Component Map page (Classic Maps > Device Maps > Components) allows you to view devices by root node and view the relationships between root nodes, parent components, and child components in a map. This makes it easy to visualize and manage root nodes and their components. SL1 automatically updates the Component Map as new component devices are discovered. The platform also updates each map with the latest status and event information. To view the map for the Orchestrator, go to the Component Map page and select the map from the list in the left navigation pane. To learn more about the Component Map page, see the section on Views.