HPE Serviceguard

Introduction

HPE Serviceguard ensures the resilience of mission-critical applications by organizing multiple nodes into an enterprise cluster. Specifically designed for Linux environments and ProLiant servers, it protects against software and hardware failures by monitoring server health and responding swiftly. Serviceguard for Linux allows clustering of HP ProLiant server products with shared storage solutions, enabling configurations from 2-node SCSI to 2 to 16-node Fibre Channel setups.

Key benefits

• It Discovers HPE Serviceguard components.
• Publishes relationships between resources for a topological view and ease of maintenance.
• Provides metrics related to job scheduling time and status.
• Generates concern alerts for each metric to notify administrators of resource issues.

Prerequisites

• OpsRamp Classic Gateway 15.0.0 and above.
• OpsRamp Nextgen Gateway 15.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.
• All Serviceguard nodes must use the same credentials.
• Jetty-Sgmgr.Service must enabled on all the Serviceguard nodes.
• To monitor the HPE Serviceguard we are using the Serviceguard Rest API (SGRAPI).
• To utilize the Serviceguard Rest API (SGRAPI) for monitoring HPE Serviceguard, the following conditions must be met:
  • Installation of Serviceguard for Linux A.15.XX.XX is required.
  • Ports 5511, https port (default port is 5522, if not configured during installation or upgrade), and 5301 must be available for SGRAPI usage.
  • Access to HPE Serviceguard necessitates valid IP address/hostname, API credentials, and SSH credentials.
• If the primary node is down, Jetty-Sgmgr.Service must be enabled on the secondary nodes in order to perform API calls to it.
• For non-root users: Update the following lines in “etc/sudoers” file to provide access for non-root user to execute the ServiceGuard Node Serial Number , Product Name and System UUID commands. Cmnd_Alias DMIDECODE_CMDS = /bin/cat /sys/class/dmi/id/product_serial, /bin/cat /sys/class/dmi/id/product_name, /usr/sbin/dmidecode -s system-uuid

{username} ALL=(ALL) NOPASSWD: DMIDECODE_CMDS

Example for opsramp non-root user: opsramp ALL=(ALL) NOPASSWD: DMIDECODE_CMDS

Hierarchy of HPE Serviceguard

    · HPE Serviceguard Cluster
            · HPE Serviceguard Node
                  · HPE Serviceguard Node Interface
            · HPE Serviceguard Package
                  · HPE Serviceguard Package Dependency
                  · HPE Serviceguard Volume Group
                          · HPE Serviceguard File System

Supported Metrics

Default Monitoring Configurations

HPE Serviceguard has default Global Device Management Policies, Global Templates, Global Monitors and Global Metrics in OpsRamp. You can customize these default monitoring configurations as per your business requirement by cloning respective Global Templates and Global Device Management Policies. It is recommended to clone them before installing the application to avoid noise alerts and data.

1. Default Global Device Management Policies

   You can find the Device Management Policy for each Native Type at Setup > Resources > Device Management Policies. Search with suggested names in global scope:

   {appName nativeType - version}

   Ex: hpe-serviceguard HPE Serviceguard Cluster - 1(i.e, appName = hpe-serviceguard, nativeType = HPE Serviceguard Cluster , version = 1)

2. Default Global Templates

   You can find the Global Templates for each Native Type at Setup > Monitoring > Templates. Search with suggested names in global scope. Each template adheres to the following naming convention:

   {appName nativeType 'Template' - version}

   Ex: hpe-serviceguard HPE Serviceguard Cluster Template- 1(i.e, appName = hpe-serviceguard, nativeType = HPE Serviceguard Cluster, version = 1)

3. Default Global Monitors

   You can find the Global Monitors for each Native Type at Setup > Monitoring > Monitors. Search with suggested names in global scope. Each Monitors adheres to the following naming convention:

   {monitorKey appName nativeType - version}

   Ex: HPE Serviceguard Cluster Monitor hpe-serviceguard HPE Serviceguard Cluster 1 (i.e, monitorKey =HPE Serviceguard Cluster Monitor , appName = hpe-serviceguard, nativeType = HPE Serviceguard Cluster, version = 1)

Configure and Install the HPE Serviceguard Integration

1. From All Clients, select a client.
2. Navigate to Setup > Account.
3. Select the Integrations tab.
4. The Installed Integrations page, where all the installed integrations are displayed. Click + ADD on the Installed Integrations page.
5. If you do not have any installed applications, you will be navigated to the Available Integrations page. The Available Integrations page displays all the available applications along with the newly created application with the version.
   Note: Search for the application using the search option available. Alternatively, use the All Categories option to search.
6. Click ADD in the HPE Serviceguard application.
   Note: Select the version from the drop down menu.
7. In the Configurations page, click + ADD. The Add Configuration page appears.
8. Enter the following BASIC INFORMATION:

Notes:

• By default the Is Secure checkbox is selected.
• Ip Address/Host Name and Port should be accessible from Gateway.
• Select the following:
  • App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.
  • Alert Configuration: map alert configuration for third party alerts into OpsRamp.
  • Alert On Root Resource: Checking this will generate event polling alerts on root resource.
    • Below are the default values set for:
      • Alert Severity: Possible values of Alert Severity filter configuration property are [“CRITICAL”,“ERROR”,“WARNING”,“DEGRADED”]
      • Alert Severity Mapping: Provides alert severity mapping configuration. Default values for Alert Severity Mapping configuration are {“DEGRADED”:“Critical”,“CRITICAL”:“Critical”,“ERROR”:“Warning”,“WARNING”:“Warning”}.

9. Select the following Custom Attribute:

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

10. In the RESOURCE TYPE section, select:
    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.
11. In the DISCOVERY SCHEDULE section, select recurrence pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
12. Click ADD.

Now the configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.

13. Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.

    Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

14. Click NEXT.

15. (Optional) Click +ADD to create a new collector. You can either use the pre-populated name or give the name to your collector.

16. Select an existing registered profile.

17. Click FINISH.

The integration is installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed integration.

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select HPE Serviceguard.

View the HPE Serviceguard Details

To discover resources for HPE Serviceguard:

1. Navigate to Infrastructure > Search > HIGH AVAILABILITY > HPE Serviceguard. The HPE Serviceguard page is displayed
2. Select the application on the HPE Serviceguard page
3. The RESOURCE page appears from the right.
4. Click the ellipsis (…) on the top right and select View Details.

5. Navigate to the Attributes tab to view the discovery details.

6. Click the Metrics tab to view the metric details for HPE Serviceguard.

View resource metrics

To confirm HPE Serviceguard monitoring, review the following:

• Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
• Alerts: Alerts are generated for metrics that are configured as defined for integration.

Resource Filter Input Keys

HPE Serviceguard application resources are filtered and discovered based on below keys.

Supported Alert Custom Macros

Customize the alert subject and description with the following macros so that it can generate alerts accordingly.
Supported macros keys:

Risks, Limitations And Assumptions

• The integration can manage critical/recovery failure alerts for the following two scenarios when the user activates App Failure Notifications in the settings:
  • Connectivity Exception
  • Authentication Exception
• HPE Serviceguard will send any duplicate/repeat failure alert notification for every 6 hours.
• HPE Serviceguard can control monitoring pause/resume actions based on above alerts. Metrics can be used to monitor HPE Serviceguard resources and can generate alerts based on the threshold values.
• HPE Serviceguard Event/Alert polling will be started only if the user enables Event Polling in configuration. Possible values of Alert Severity Filter configuration are “DEGRADED”,“WARNING”,“CRITICAL”,“ERROR”. Based on these values alerts will be filtered and user can customize this at any point of time.
• We have given default mappings to map Serviceguard alerts Severity with OpsRamp Severities as part of Alert Severity Mapping configuration. User can modify them as per their use-case at any point of time from application configuration page. Possible Severities are Critical, Warning. Provided below default severity mapping in configuration {“DEGRADED”:“Critical”,“WARNING”:“Warning”,“CRITICAL”:“Critical”,“ERROR”:“Warning”}
• In Alert polling, by default alert will be raised on root resource. User can make the alert populated on its actual resource by unchecking the checkbox(Alert on root Resource).
• We have provided 5522 and 22 as default Port for API and SSH respectively. Users can modify this value from configuration page if requires.
• Component level thresholds can be configured on each resource level.
• No support of showing activity logs.
• The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
• The minimum supported version for the option to get the latest snapshot metric and Full discovery is Nextgen-15.0.0.
• HPE Serviceguard supports both Classic Gateway and NextGen Gateway.

Version History

References

HPE Serviceguard REST API Reference Guide