HPE-UX Server

Introduction

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

Pre-requisites

• Users must have either OpsRamp Classic Gateway 10.0.
• Ensure that “adapter integrations” add-on is enabled in client configuration. Once enabled, go to Setup > Integrations > Adapter to see HPE-UX Server integration.
• 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

Install the Integration

1. From All Clients, select a client.
2. Go to Setup > Integrations and Apps.
3. 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.

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

5. Click ADD in the HPE UX Server tile.
6. The Install HPE UX Server Integration popup appears.
   Note: Ensure that Adapter addon is enabled at client and partner levels.

7. Enter the following information:

• Name: Name of the integration
• Upload Logo: Optional logo for the integration.
• GateWay Profiles: Select a gateway management profile to associate with the client.

8. Click Install. The Integration page displays the installed integration.

Configure the integration

1. In CONFIGURATION section, click +Add.

2. On Create Adapter Configuration, enter:
   • Name: Configuration name.
   • IP Address/Host Name: IP address or host name of the target.
   • Additional Configurations: Add additional configuration details, such as file system, process, and so on. The Log File Configuration is part of the additional configuration, configure the values for below fields as per your log file monitoring use case:
     • Name
     • File Name
     • Rotated File Name
     • Expression
     • Check Type
     • Threshold
     • Severity
   • Notification Alerts: Select TRUE or FALSE.
     Notes:
     • By default False is selected.
     • If you select TRUE, application will handle Critical/Recovery failure alert notifications for Connectivity, Authentication Exceptions.
3. From the Credential section, select Custom and enter the Username and Password.
4. From the Resource Types & Metrics section, select the metrics and configure for availability and alert conditions, for Cluster & Server.
5. In the Discovery Schedule section, configure how frequently the discovery action should trigger. Select Recurrence Pattern to add one of the following patterns:
   • Minutes
   • Hourly
   • Daily
   • Weekly
   • Monthly
6. In the Monitoring Schedule section, configure how frequently the monitoring action should trigger.

8. Click Save.
9. After saving the integration, HP-UX resources are discovered and monitoring is enabled as specified by the configuration profile.

The configuration is saved and displayed on the page. You can perform the actions manually, like Discovery, Monitoring or even Disable the configuration.

Resource information

1. To view the resource information, go to Infrastructure > Resources > Server.
2. Use the search function to find your resource and then click on it.

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.

Supported metrics

Resource Type: Server

Risks, Limitations & Assumptions

• We are not supporting below monitorings as of now:
  • Hardware metrics
  • Programmable Resource Monitoring
  • Processes (we provided one metric for each process RunningStatus. i.e, hpux_server_process_RunningStatus).
• Need below json payload as input for log monitoring:
  • Name: This can be any string used to identify individual log configuration.
  • File Name: It 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.
  • Rotated File Name: It is similar to file name field but specifying the rotated file. This is a optional field.
  • Expression: This can be any valid string or regular expression used to specify the search string. It is a mandatory field.
  • Check Type: This can be either “exists” or “not exists”(case insensitive).
  • Threshold: This can be any valid integer. Alert will be generated in case of specified threshold breach happens.
  • Severity: It is used to specify the alert type to be created in case of expression found. Possible values are CRITICAL, WARNING, INFO, and OK (case insensitive).
  • The availability is shown unknown for few resources even if it is enabled on the respective resource metrics. This is because of the presence of multiple native type resources under the same resource type.

Log file configuration:

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

• We do not process logs for the first request because it creates performance issues due to a large amount of data. We will process the second request based on the most recent logs (logs generated between the first and second polls).
• No recovery alerts are generated for expression related alerts. We will get recovery only for file not found alerts.
• lication can handle Critical/Recovery failure alert notifications for below two cases when user enables Notification Alerts in configuration:
  • Connectivity Exception
  • Authentication Exception
• Application will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
• Application cannot control monitoring Pause/Resume actions based on above alerts.
• Component level threshold configuration is not possible
• Resource level metric threshold customization and frequency setting are not possible
• Usability issues in appapplication configuration page while adding/editing
• Optional configuration parameters cannot be defined
• Application upgrade is manual process without version change
• We do not process logs of size greater than 1GB.