Redfish - Server

Application Version Details

Introduction to HPE iLO

Integrated Lights-Out (iLO) is a proprietary management technology built into HPE products, which enables remote control access to ProLiant servers, even without a connection to the organization’s main network. The ‘Lights Out’ designation originates from its ability to provide out-of-band management facilities. The iLO software can remotely perform most functions that would otherwise require a physical visit to the servers in the data center, computer room, or remote location.

This Redfish integration supports various HPE servers, including Apollo systems, Blade systems, OneView, ProLiant servers, ProLiant DL servers, Rack servers, Synergy servers, and more. As of now, we have completed an analysis on HPE ProLiant servers.

HPE Proliant DL Series

HPE ProLiant servers are engineered with a fundamental security approach to defend against increasingly complex threats. Protect your infrastructure, workloads, and data with our newest HPE ProLiant Gen11 servers or our full portfolio of both rack and tower servers.

The following diagram illustrates the HPE ProLiant DL380 Gen11 model.

Adaptable for diverse workloads and environments, the secure 2P 2U HPE ProLiant DL380 Gen11 delivers world-class performance with the right balance of expandability and scalability. Designed for supreme versatility and resiliency, and backed by a comprehensive warranty, it is ideal for multiple environments, from Containers to Cloud to Big Data. Standardize on the industry’s most trusted compute platform.

Key Use Cases

Discovery Use Cases:

• Provides resource visibility to the administrator to view and manage resources available (Ex: Manager, Chassis, Systems, Network Adapters, PCIe Devices and PCIe Functions, Power, Thermals) under different resource types.
• Publishes relationships between resources to have a topological view and ease of maintenance.

Monitoring Use Cases:

• Provides metrics related to CPU Utilization, Memory Utilization, Performance Utilization and Health Monitoring and so on for different resources.
• Concern alerts will be generated for each metric to notify the administrator regarding the issue with the resource.

Prerequisites

• OpsRamp Classic Gateway version 14.0.0 and above.
• OpsRamp Nextgen Gateway version 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc..

Resource Hierarchy

Redfish Server →
      → Manager
            → Network Interfaces
        → Chassis
                → Compute System
                            → Ethernet Interfaces
                            → Processors
                            → Drives
                            → Volumes
                            → Memory
                → Devices
                → NetworkAdapters
                → Power Supplies
                → Fans
                → Temperature Sensors

Default Monitoring Configurations

iLO Redfish have 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 application to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of iLO Redfish. 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: ilo-redfish iLO Redfish Chassis - 1 (i.e, appName = ilo-redfish, nativeType = iLO Redfish Chassis, version = 1)

2. Default Global Templates

   OpsRamp has a Global template for each Native Type of iLO Redfish. 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: ilo-redfish iLO Redfish Chassis Template - 1 (i.e, appName = ilo-redfish, nativeType = iLO Redfish Chassis, version = 1)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. You 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: ilo-redfish iLO Redfish Chassis Monitor ilo-redfish iLO Redfish Chassis 1(i.e, monitorKey = iLO Redfish Chassis, appName = ilo-redfish, nativeType = iLO Redfish Chassis, version = 1)

Configure and Install the Redfish - 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 Redfish - Server application.
7. In the Configurations page, click + ADD. The Add Configuration page appears.
8. Enter the below mentioned BASIC INFORMATION:

Notes:

• By default the Is Secure checkbox is selected.
• IP Address/Host Name and Port Should be accessible from Gateway.
• App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.

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.

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

• 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 Redfish - Server application.

View the Redfish - Server Details

To discover resources for Redfish - Server, you have two options:

Option 1:

Navigate to Infrastructure > Resources > Others, with Native Resource Type as Redfish Server. You can go to the Attributes tab to view the discovery details.

Option 2:

1. Navigate to Infrastructure > Search > COMPUTE > Redfish - Server.
2. The REDFISH - SERVER page is displayed, select the application name.
3. The RESOURCE DETAILS 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.

• Click the Metrics tab to view the metric details for Redfish - Server.

View resource metrics

To confirm Redfish - 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

iLO Redfish application Resources are filtered and discovered based on below keys:

Supported Alert Custom Macros

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

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
• Using metrics for monitoring the resources and generating alerts when the threshold values are breached.
• Application cannot control monitoring pause/resume actions based on above alerts.
• Application is not compatible with Cluster Gateway.
• Tested redfish-server integration with ProLiant DL380 Gen11 and HPE Cray XD220v. As per the configurations and model of the target device resources will be discovered.
• For few PowerSupply resources getting name as empty or null from the api response, So we are providing powersupply name as a combination of string “PowerSupply” and Id.Eg : PowerSupply_0