HP-UX Server

Application Version Details

Introduction

HP UX is a closed source operating system provided by HP Enterprise. It is a Unix-like operating system based on the Unix System V design. It is primarily designed for HP computers, and its target system is a server. It is one of five commercial operating systems with versions certified to the open group’s UNIX 03 standard. It has a monolithic kernel with dynamically loadable modules and the preferred proprietary license.

Prerequisites

• OpsRamp Classic Gateway 14.0.0 and above.
• OpsRamp Nextgen Gateway 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.
• Provided IP Address/Host Name, Credentials should work for SSH communication.
• Users need to add path /usr/sbin against path variables in the .profile file to achieve NETWORK related metrics. Example:

(hpux_server_network_interface_OutTraffic, hpux_server_network_interface_InDiscards, hpux_server_network_interface_OutPackets, hpux_server_network_interface_OutErrors, hpux_server_network_interface_OutDiscards, hpux_server_network_interface_InPackets, hpux_server_network_interface_InErrors, hpux_server_network_interface_Collisions, hpux_server_network_interface_Status, hpux_server_network_interface_InTraffic).

cat .profile
# Set up the search paths:
        PATH=$PATH:/usr/bin:/usr/sbin:/etc:/usr/local/bin:.

• Users should have a tmp folder, the application will use it to store top command output in order to retrieve CPU and memory utilization metrics.

Commands using tmp folder
top -f /tmp/topoutput.txt

cat /tmp/topoutput.txt

rm /tmp/topoutput.txt

• Users who want to use log file monitoring must have a home directory on the system where the script will be run.

pwd

[content@centos-node1 ~]$ pwd
/home/content

Application Migration

1. Check for the gateway version as a prerequisite step - classic gateway-12.0.1 and above.
   Notes:

   • You only have to follow these steps when you want to migrate from sdk 1.0 to sdk 2.0.
   • For first time installation below steps are not required.
     • Application name should be the same.
     • Disable all installed integrations configurations for that application. This is to make sure no discovery and monitoring requests are processed.
     • Install and Add the configuration to that sdk 2.0 application.
     • During the migration from SDK 1.0 to SDK 2.0, ensure that you uncheck the Bypass Resource Reconciliation checkbox.
       Note: refer to Configure and Install the HP UX Server Integration & View the HP UX Server Details sections of this document.

2. Once all discoveries are completed with the sdk 2.0 applicaion, follow any one of the approaches.

   • Direct uninstallation of the sdk1.0 adaptor application through the uninstall API with skipDeleteResources=true in the post request

End-Point: https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/{installedIntgId}

Request Body:

{
    "uninstallReason": "Test",
    "skipDeleteResources": true
}

• Delete the configuration one by one through the Delete adaptor config API with the request parameter as skipDeleteResources=true

End-Point: https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/config/{configId}?skipDeleteResources=true.

• Finally, uninstall the adaptor application through API with skipDeleteResources=true in the post request.

End-Point:

https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/{installedIntgId}

Request Body:

{
    "uninstallReason": "Test",
    "skipDeleteResources": true
}

Default Monitoring Configurations

HP UX Server has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. Users can customize these default monitoring configurations as per their business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommends doing this activity before installing the app to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of HP UX Server. You can find those Device Management Policies at Setup > Resources > Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: hp-ux-server HP UX Server - 2 (i.e, appName = hp-ux-server, nativeType = HP UX Server, version = 2)

2. Default Global Templates

   OpsRamp has a Global template for each Native Type of HP UX Server. You can find those templates at Setup > Monitoring > Templates, search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex : hp-ux-server HP UX Server Template - 2 (i.e, appName = hp-ux-server, nativeType = HP UX Server, version = 2)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. We can find those monitors at Setup > Monitoring > Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: HP UX Server Monitor hp-ux-server HP UX Server 2(i.e, monitorKey = HP UX Server Monitor, appName = hp-ux-server, nativeType = HP UX Server, version = 2)

Configure and Install the HP UX Server Integration

1. From All Clients, select a client.
2. Go to Setup > Account.
3. Select the Integrations and Apps tab.
4. The Installed Integrations page, where all the installed applications are displayed.
   Note: If there are no installed applications, it will navigate to the ADD APP page.
5. Click + ADD on the Installed Integrations page. The Available Integrations and Apps page displays all the available applications along with the newly created application with the version.
   Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.

6. Click ADD in the HP UX Server tile.
7. From the Configurations page, click + ADD.
8. Enter the below mentioned BASIC INFORMATION:

Notes:

• 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.
  • Log File Monitoring: The Log File Configuration is part of the additional configuration, configure the values for below fields as per your log file monitoring use case:
    • Log File Configuration: {“Name”:"",“File Name”:"",“Rotated File Name”:"",“Expression”:"",“Check Type”:"",“Threshold”:"",“Severity”:""}
• Ip Address/Host Name and Port should be accessible from Gateway.

9. Select the below mentioned 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. Click NEXT
14. Below are the optional steps you can perform on the Installation page.

• 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.

  Notes:

  • If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.
  • During the migration from SDK 1.0 to SDK 2.0, ensure that you uncheck the Bypass Resource Reconciliation checkbox.

• Click +ADD to create a new collector by providing a name or use the pre-populated name.

15. Select an existing registered profile.

16. 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 the HP UX Server application.

View the HP UX Details

Navigate to Infrastructure > Resources > Server, with Native Resource Type as HP UX Server. You can go to the Attributes tab to view the discovery details and click the Metrics tab to view the metric details for HP UX Server.

View resource attributes

The discovered resource(s) are displayed under Attributes. In this page you will get the basic information about the resources such as: Resource Type, Native Resource Type, Resource Name, IP Address etc.

View resource metrics

To confirm HP-UX Server 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

HP UX Server 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

Customize the alert subject and description with below macros then it will generate alerts based on customization.
Supported macros keys:

Supported Metrics

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure notifications for below two cases when user enables App Failure Notifications in configuration:
  • Connectivity Exception
  • Authentication Exception
• Application uses the provided IpAddress/hostname, Credentials for SSH communications.
• Application will send duplicate/repeat failure alert notification for every 6 hours.
• Application cannot control monitoring pause/resume actions based on above alerts
• Metrics can be used to monitor HP UX Server resources and can generate alerts based on the threshold values.
• OpsRamp has provided 22 as default SSH Port value for connecting to HP UX end devices via SSH. Users can modify this value from the application configuration page at any point of time if required.
• No support of showing activity log and applied time.
• Full discovery support requires gateway version 15.0.0 or above.
• This application supports both Classic Gateway and NextGen Gateway.
• Currently we do not have monitoring support for below things
  • Hardware metrics
  • Programmable Resource Monitoring
  • Processes (We provided one metric for each process RunningStatus. i.e, hpux_server_process_RunningStatus)
• For log monitoring, we expect the 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 1: C:\Program Files (x86)\Vistara\Agent\log\Age.?t.log
    Matches: Agent.log, Ageat.log ,..
  • “Rotated File Name” is similar to filename 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 a 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":""
  }
]

• We do not process logs of size greater than 1GB.
• We do not process logs for the first request, since it leads to performance issues due to huge data. We will consider the latest logs ( logs generated between first and second polls) from the second request and process accordingly.
• No recovery alerts are generated for expression related alerts. We will get recovery only for file not found alerts.