Introduction

The HP-UX Cluster delivers high availability (HA) by providing fault tolerance, enabling scalability, and supporting disaster recovery for mission-critical applications. It uses HPE Serviceguard developed by Hewlett-Packard developed to implement this clustering solution specifically for the HP-UX operating system.

The HP-UX Cluster primarily ensures continuous service availability by detecting hardware, software, or network failures, failing over resources to alternate nodes with in the cluster.

Key components of HP-UX Cluster

The architecture of an HP-UX cluster comprises various essential components that work together to provide high availability and resource management.

Cluster Nodes- These are individual servers running the HP-UX operating system. Each node can host applications and resources or act as a failover node. Nodes are assigned roles such as active (primary) and standby (secondary) for specific applications, ensuring continuity in case of failure.

Cluster Software (Serviceguard)- This is the core clustering software responsible for managing communication between nodes and handling failovers. It primarily monitors the health of nodes and services, manages cluster resources such as applications, IP addresses, and storage, and orchestrates failover during node or service failure.

Package (Service Group)- This is a group of resources that defines an application or service that can run on one or more nodes. It typically includes floating IP addresses, applications, and shared storage. If the primary node hosting a package fails, the package can move to another node to maintain service availability.

Shared Storage- This is accessible by multiple nodes in the cluster and is used for hosting application data or shared filesystems. It is managed using volume management tools like LVM (Logical Volume Manager) and primarily ensures data consistency during node failovers.

Key Features of HP-UX Clusters

High Availability- HP-UX clusters reduce downtime. If a node fails, another takes over automatically.
Scalability- You can add more nodes or resources as needed.
Disaster Recovery- Clusters can be set up across locations.
Flexible Resource Allocation- Applications or services can run on any node.

Use Cases

Discovery

• It discovers the HP-UX cluster (Running cluster software as Serviceguard) components.
• Publishes relationships between resources to have a topological view and ease of maintenance.
• For more information on Heirarchy of HP-UX resource structure, see Resource Hierarchy

Monitoring

• Provides metrics related to job scheduling time and status and so on.
• Generates concern alerts for each metric to notify the administrator regarding the issue with the resource.
• For a complete list of supported metrics and details on the default monitoring configurations, see Supported Metrics and Default Monitoring Configuration

Supported Target Versions

• HP-UX Cluster: Installed Cluster Software
  Serviceguard Manager version: B.03.00
  Serviceguard version: A.11.20.00
  
• HP-UX OS Version: HP-UX rxb10u02 B.11.31 U ia64 3148622491 unlimited-user license

Resource Hierarchy

The following is the resource hierarchy for HP-UX Cluster.     • HP UX Cluster
          • HP UX Server
          • HP UX Resource Group

The following is the resource hierarchy for HP-UX Server.     • HP UX Server

Prerequisites

Before configuring the integration, ensure that your environment meets the following requirements related to gateway versions, credentials, and connectivity.

• OpsRamp Classic Gateway (Linux) version 14.0.0 or later.
• OpsRamp NextGen Gateway version 14.0.0 or later.
• OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes and enhancements.
• Customer need to provide HP-UX Cluster IpAddress and SSH login credentials (This credentials must be same for all nodes)
• HP-UX Cluster nodes should be reachable from the gateway and SSH access must be opened.
• The assigned SSH credentials should have privileges to execute CLI commands.

• This SDK app applicable to HP-UX Cluster environment (which is running on Serviceguard Cluster Software).
• Ensure that the provided IP address/host name, port, and credentials are valid and accessible for successful integration.
  Verify network connectivity from the gateway using:
  ping <IP Address/Host Name>
  Check port accessibility using:
  telnet <IP Address/Host Name>
  Validate SSH access using the provided credentials:
  ssh -p @<IP Address/Host Name>

Supported Metrics

Default Monitoring Configurations

HP UX Cluster provides default monitoring components that include:

• Global Device Management Policies
• Global Templates
• Global Monitors

These configurations are applied automatically upon installation. You can customize them for your environment by cloning the global versions and modifying thresholds or alerting behaviour.

Customize this prior to the installation of application to avoid unnecessary alerts and noise.

1. Default Global Device Management Policies available Device Management Policy for each Native Type are available at
   Setup -> Resources -> Device Management Policies.
   Search with suggested names in global scope. Each Device Management Policy follows below naming convention: {appName nativeType - version - Type} Example: hp-ux-server HP UX Cluster - 4 - HP-UX Cluster (i.e, appName = hp-ux-server, nativeType = HP UX Cluster, version = 4, Type = HP UX Cluster)

2. Default Global Templates available Templates are available at
   Setup -> Monitoring -> Templates
   Search with suggested names in global scope. Each template follows below naming convention : {appName Type nativeType ‘Template’ - version} Example: hp-ux-server HP-UX Cluster HP UX Cluster Template - 4 (i.e, appName = hp-ux-server, Type = HP-UX Cluster, nativeType = HP UX Cluster, version = 4)

3. Default Global Monitors available Monitors are avilable at
   Setup -> Monitoring -> Monitors
   Search with suggested names in global scope. Each Monitors follows below naming convention : {monitorKey appName nativeType - version} Example: HP UX Cluster Monitor hp-ux-server HP UX Cluster 4(i.e, monitorKey = HP UX Cluster Monitor, appName = hp-ux-server, nativeType = HP UX Cluster, version = 4)

Configure and Install the HP UX Cluster Integration

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select the HP UX Cluster application.

Discover Resources in HP UX Cluster

Resource Filter Input Keys

HP UX Cluster application Resources are filtered and discovered based on below keys:
Note: You can filter the resources with the discoverable keys only.

Supported Alert Custom Macros

Customise the alert subject and description with below macros then it will generate alert based on customisation.

Risks, Limitations & Assumptions

• App can handle Critical/Recovery failure alert notifications for:
  • Connectivity Exception
  • Authentication Exception
• Duplicate/repeat failure alert notifications are sent every 6 hours.
• App cannot control monitoring pause/resume actions based on alerts.
• Metrics can monitor HP-UX Cluster resources and generate alerts based on threshold values.
• Minimum supported version for Latest snapshot metric: nextgen-14.0.0
• Full discovery support requires gateway version 15.0.0 or above.
• App is not compatible with Cluster Gateway.
• Default SSH Port: 22 (modifiable from configuration page)
• Component-level thresholds can be configured per resource.
• Template Applied Time is shown only if collector profile version is 18.1.0 or higher.
• Currently unsupported monitoring features:
  • Hardware metrics
  • Programmable Resource Monitoring
  • Processes (We provided one metric for each process RunningStatus. i.e, hpux_server_process_RunningStatus)
• Log File Monitoring is supported only for HP-UX Server type.
• For log monitoring, we expect below JSON payload as input.
  • "Name" can be any string used to identify individual log configuration.
  • "File Name" is a combination of folder path and file name. Folder path should contain the exact path for the file as prefix. File name can be any valid string or regular expression. In case of file not found with specified file name, alert will be generated with the severity specified by the user.
    • Example: C:\Program Files (x86)\Vistara\Agent\log\Age.?t.log
    • Matches: Agent.log, Ageat.log, ...
  • "Rotated File Name" is similar to file name field but specifying the rotated file. This field is optional.
  • "Expression" can be any valid string or regular expression used to specify the search string. It's a mandatory field.
  • "Check Type" can be either "exists" or "not exists" (case insensitive).
  • "Threshold" can be any valid integer. Alert will be generated in case of specified threshold breach happens.
  • "Severity" used to specify the alert type to be created in case of expression found. Possible values are CRITICAL, WARNING, INFO and OK (case insensitive).
Log File Configuration


[
  {
    "Name": "",
    "File Name": "",
    "Rotated File Name": "",
    "Expression": "",
    "Check Type": "",
    "Threshold": "",
    "Severity": ""
  }
]

• Logs larger than 1GB are not processed.
• First request logs are skipped to avoid performance issues; processing starts from second poll.
• No recovery alerts for expression-based alerts; recovery only for file-not-found alerts.

Version History