HPE Bare Metal (BMaaS)¶

Overview¶

HPE Bare-Metal-as-a-Service (BMaaS) for HPE Morpheus Software Enterprise extends hybrid cloud management capabilities to HPE ProLiant physical servers. This integration allows the HPE Morpheus Software platform to discover, provision, and manage these servers as first-class resources. Additionally, HPE BMaaS Cloud integrates HPE ProLiant bare-metal infrastructure into cloud environments to enable cloud-based provisioning and lifecycle management.

HPE BMaaS manages the end-to-end server lifecycle, including hardware discovery, bare-metal provisioning, operating system deployment, monitoring, and metering. The HPE Morpheus Software interface centrally orchestrates these tasks. This unified approach enables organizations to manage physical infrastructure, virtual machines, and cloud resources using consistent workflows, policies, and governance controls.

Features¶

• Automated Server Discovery - Automatically imports and discovers HPE ProLiant servers

• Bare-Metal Provisioning - Provisions hardware using custom or pre-configured OS images

• Comprehensive OS Deployment - Deploys Windows and Linux with unattended installations and customizable boot parameters

• Lifecycle Management - Manages firmware and drivers using the HPE Service Pack for ProLiant (SPP)

• Flexible Networking - Supports both unmanaged and managed network integrations

• Metering and Billing - Maps discovered hardware to service plans to align metering with billing

• Logical Organization - Organizes resources into Bare Metal Clouds and Resource Pools to support multi-site environments and scalable infrastructure segmentation

HPE BMaaS improves operational visibility and server lifecycle control. It offers a scalable, automated approach to manage physical infrastructure across both greenfield (new) and brownfield (existing) environments.

Adding HPE BMaaS Integration¶

Prerequisites¶

This procedure describes how to integrate HPE BMaaS with your HPE Morpheus Software Enterprise environment.

About this task¶

To install the HPE BMaaS plugin, perform the following steps:

1. Log in to the HPE HPE Morpheus Software Enterprise Software web interface using your administrator credentials.

2. Navigate to Administration ‣ Integrations.

3. Select the Plugins tab and click Add button.

4. Drag the HPE BMaaS JAR file into the Drop Files Here area, or click Add File to select it manually.

5. Click Upload.

After a successful upload, HPE BMaaS is available for use.

Creating an HPE BMaaS Cloud¶

About this task¶

Creating an HPE BMaaS Cloud integrates physical infrastructure into the HPE Morpheus Software management plane, establishing a logical boundary for bare-metal resources to enable group-based policies and proxy configurations. This setup allows for onboarding HPE ProLiant servers for automated provisioning and lifecycle management.

To create an HPE BMaaS Cloud in HPE Morpheus Software for HPE ProLiant bare-metal operations, follow this procedure:

Procedure¶

1. Navigate to Infrastructure ‣ Clouds in the HPE Morpheus Software interface.

2. Click the + Add button.

3. Locate and select the HPE BMaaS Cloud type as HPE Bare Metal (BMaaS), and then click Next.

4. Enter the name, code, Labels, Location, and complete any additional required details for the cloud.

5. (Optional) In Provisioning Command, select a Proxy for provisioned bare metal instances if required, then click Next.

6. For the group, you may either select Use Existing or Create New:

   • To use an existing group, choose Use Existing and select the desired group from the drop-down list.

   • To create a new group, select Create New and enter a group name.

7. Click Complete to finish creating the HPE BMaaS Cloud.

After completing these steps, the HPE BMaaS Cloud appears in the Infrastructure > Clouds list and is ready to have bare-metal servers imported.

Importing HPE ProLiant Bare Metal Servers¶

About this task¶

Perform the following procedure to import HPE ProLiant Bare Metal Servers into HPE Morpheus Software.

Procedure¶

1. Navigate to Infrastructure ‣ Compute, then select the Bare Metal tab.

2. Click the + ADD button and select HPE Bare Metal Import.

3. Select the target HPE BMaaS Cloud from the drop-down list.

4. Configure the import settings:

   • iLO IP Range - Specify the iLO IP address range to scan for HPE ProLiant servers

   • Credentials - Provide the iLO credentials for server discovery

5. Click Import to begin the server discovery process.

After successful import, the discovered HPE ProLiant servers appear in the Bare Metal tab and are available for provisioning through HPE Morpheus Software.

Compute Management¶

The topic section describes how HPE HPE Morpheus Software Enterprise orchestrates on-premises and HPE BMaaS Cloud resources. It covers the end-to-end lifecycle for physical servers, including installation, cloud configuration, on-boarding, and workload migration.

Administrators perform the following tasks:

• Define a Bare Metal Cloud

• Configure unmanaged networks and resource pools

• Import

• HPE

• ProLiant servers for centralized visibility

• Manage greenfield (new) and brownfield (existing) server deployment

• Convert Pre-Provisioned servers into managed

• HPE

• Morpheus instances

Administrators use these procedures to enable consistent provisioning, lifecycle management, and governance for HPE ProLiant infrastructure within HPE Morpheus.

Creating Resource Pools¶

This section describes how to create a resource pool within your HPE ProLiant Bare Metal Cloud in Morpheus. Resource pools help you organize and allocate servers for provisioning and management.

1. Navigate to

2. Navigate to Infrastructure > Clouds. Select the cloud and click the

3. Resources

4. tab.

5. Click the

6. • Add Resource Pool.

7. Enter a name and complete any additional required details for the resource pool and then click

8. Next.

9. Click

10. Save Changes

11. to finalize resource pool creation.

Image Management¶

The topic describes about image catalog and uploading various images.

Image Catalog¶

This section describes how to upload Bare Metal (BM) operating system images into Morpheus using a configurable image repository.HPE Morpheus supports multiple backend storage options, allowing administrators to centrally manage OS images and reuse them across bare metal provisioning workflows.

Uploaded images are registered underLibrary>Virtual Imagesand are made available for bare metal instance provisioning.

Supported OS Image Sources HPE Morpheus supports uploading Bare Metal OS images from the following storage backends:

• Local storage on the

• HPE Morpheus appliance

• S3-compatible object storage

• CIFS (Samba) file shares

• NFS (v3) file shares

Each backend option is configured as a File Share or Storage Bucket and referenced during image upload.

Uploading OS Images¶

Prerequisites

• Image upload and deployment performance depend on network bandwidth and storage backend performance.

• File permissions on shared storage must allow Morpheus read access.

• OS images must be bootable and compatible with the target bare metal hardware.

• Server reboots and virtual media behavior depend on hardware management interfaces (for example, iLO).

Uploading OS Images Using Local Storage¶

Prerequisites

• Ensure that Morpheus-app user owns the storage directory.

• Ensure that Morpheus-app user has access to the storage path.

Local storage allows OS images to be uploaded directly to the Morpheus appliance filesystem and is suitable for smaller environments or evaluation use cases.

1. Configure a Local Storage file share under

2. Infrastructure

3. >

4. Storage

5. >

6. File Shares.

7. Upload the OS ISO using

8. Library

9. >

10. Virtual Images

11. >

12. Add

13. >

14. ISO.

15. Verify the image status is

#. Active. Uploading OS Images Using S3 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

-Compatible Object Storage

S3-compatible object storage (such as MinIO) provides scalable and durable storage for OS images.

1. Configure an S3 storage bucket under

2. Infrastructure

3. >

4. Storage

5. >

6. Buckets.

7. Provide access credentials with read/write permissions.

8. Upload the OS ISO using

9. Library

10. >

11. Virtual Images

12. >

13. Add

14. >

15. ISO.

16. Confirm successful upload and activation.

Uploading OS Images Using CIFS¶

(Samba) CIFS (Samba) allows OS images to be stored on a shared Windows or Linux file server.

1. Configure a CIFS file share under

2. Infrastructure

3. >

4. Storage

5. >

6. File Shares.

7. Provide valid credentials for the Samba share.

8. Upload the OS ISO through

9. Library

10. >

11. Virtual Images

12. >

13. Add

14. >

15. ISO.

16. Verify the image is accessible for provisioning.

Uploading OS Images Using NFS¶

NFS allows OS images to be stored on a shared Linux file server.

1. Configure an NFSv3 file share under

2. Infrastructure

3. >

4. Storage

5. >

6. File Shares.

7. Provide valid credentials for the NFS share.

8. Upload the OS ISO through

9. Library

10. >

11. Virtual Images

12. >

13. Add

14. >

15. ISO.

16. Verify the image is accessible for provisioning.

Windows OS Imaging¶

This section provides guidance and requirements for deployingWindows Server on bare metalusing HPE Morpheus Software Enterprise. It covers required virtual image settings, Windows-specific boot considerations, current licensing limitations, and high-level troubleshooting guidance for failed installations.

The following Windows distributions are supported for deployment:

• Windows Server 2019

• Windows Server 2022

• Windows Server 2025

Virtual Image Configuration

When adding a Windows ISO to theMorpheus Virtual Images Library, the following settingsmustbe configured:

• Is Cloud Init Enabled: Unchecked

• Cloud Guest Customization: Checked

• Sysprepped / Generalized Image: Checked

• Install Agent: Checked

• Advanced - VM Tools Installed: Checked

Windows Install Image Index

By default, Morpheus installs Image Index 2, which typically corresponds to Windows Server Standard (Desktop Experience).

To deploy a different Windows edition:

1. Navigate to

2. Library

3. >

4. Operating Systems.

5. Add a new Operating System entry with

6. Platform = Windows.

7. Specify the desired

8. Windows Install Index.

9. Complete the required fields (Vendor, OS Version, Category, OS Name, Codename, OS Family).

10. Associate the Windows Virtual Image with this Operating System.

You can use the existing Windows Operating System as reference templates.

Boot Prompt Configuration¶

Unmodified Microsoft Windows Server ISOs display aPress any key to boot CD/DVD…prompt, which will interrupt unattended bare metal deployments.

Two approaches are supported:

• Option 1: Use a Modified ISO (Recommended)

• Option 2: Manual Console Interaction

Option 1: Use a Modified ISO (Recommended)

Use a Windows ISO with the boot prompt removed. A script to generate such an ISO is available athttps://github.com/HewlettPackard/hpegl-metal-os-windows-iso

Only the resulting ISO is required. A prebuilt Windows Server 2022 Evaluation ISO with this modification is also available and suitable for testing environments.

Option 2: Manual Console Interaction

If using an unmodified ISO:

1. Create the instance as usual.

2. When the instance enters provisioning, open the Remote Console.

3. Press Enter when prompted to boot from the installation media. Windows Licensing Considerations

At present, Windows licensing is not supported during bare metal provisioning.

Only Evaluation editions or versions that do not require a Product Key in AutoUnattend.xml can be deployed.

The modified Windows Server 2022 ISO referenced above is an Evaluation edition and is suitable for testing.

Linux OS Imaging¶

This section describes the supported Linux distributions and guides for deploying Linux on bare metal using Morpheus. It includes validated OS versions, required virtual image settings, boot loader configuration for unattended installation, and troubleshooting steps for common deployment issues (see Section Troubleshooting for more details).

The following Linux distributions have been validated for deployment:

• Red Hat Enterprise Linux (RHEL) and derivatives

  • RHEL 9.5

  • Oracle Linux 8.10

  • Oracle Linux 9.5

• Ubuntu Server

  • Ubuntu Server 22.04.5 LTS

  • Ubuntu Server 24.04.3 LTS

Virtual Image Configuration

When adding a Linux ISO toLibrary>Virtual Images, ensure the following settings:

• Operating System: Select the appropriate OS (e.g., RHEL 9, Oracle Linux 9, Ubuntu 22.04, Ubuntu 24.04)

• Is Cloud Init Enabled: Checked

• Advanced

  • VM Tools Installed: Checked

Boot Prompt Configuration - RHEL and Oracle Linux

Unmodified RHEL and Oracle Linux ISOs include a default boot menu entry:Test this media & install OS.

This entry performs afull media verificationbefore installation.

NOTE

• The media check does not cause installation failure.

• It can, however, delay deployment by 30–60 minutes, particularly in remote or virtual media environments.

• Skipping the media check is recommended to reduce installation time. Supported Options

• Preferred: Modify the ISO - Adjust the ISO boot loader to remove or bypass the media check from the default boot entry. - Ensures faster, fully unattended deployment.

• Alternative: Manual Boot Selection - At boot: Select - Install OS - (without media test). - Do NOT select - Test this media & install OS - .

• Reference - Grub menu example (for clarity): - 0 → Install Red Hat Enterprise Linux 9.5

  • 1 → Test this media & install Red Hat Enterprise Linux 9.5

  • Default entry index

  • 1

  • triggers the media check.

• Changing the default to

• 0

• or manually selecting

• Install OS

• skips verification.

Boot Prompt Configuration - Ubuntu Server

Ubuntu Server requires kernel boot parameters to enable unattended installation using cloud-init autoinstall.

Unmodified ISOs do not automatically perform unattended installation.

Required Manual Step (Unmodified ISO)

At the GRUB boot menu:

• Highlight the default Ubuntu entry.

• Press

• e

• to edit.

• Append the following kernel parameters:

• autoinstall ds=nocloud

• Boot with the modified entry.

• Example Boot Entry:

• menuentry "Ubuntu" {

• set gfxpayload=keep

• linux /casper/vmlinuz quiet autoinstall ds=nocloud —

• initrd /casper/initrd

• }

  This enables cloud-init–based unattended installation.

Provisioning a New Server¶

Provisioning a new server allows onboarding new, unmanagedHPE ProLiant servers into a Bare Metal Cloud environment, enablingHPE Morpheus to manage their lifecycle, including automated OS deployment and hardware monitoring.

Importing HPE ProLiant Bare Metal Servers¶

ImportingHPE ProLiant Bare Metal Servers Perform the following procedure to importHPE ProLiant Bare Metal Servers:

1. Navigate to

2. Infrastructure

3. >

4. Compute

5. , then select the

6. Bare Metal

7. tab.

8. Click the

9. • Bare Metal

10. button, then select

11. HPE

12. Server.

13. Select the

14. Group

15. you created earlier from the drop-down list and click

16. Next.

17. Enter a Name for the server and click

18. Next.

19. Enter the following iLO (Integrated Lights Out) details for the server:

• iLO IP Address

• iLO Username (typically "Administrator")

• iLO Administrator Password

1. Leave the Pre-Provisioned Server option unselected, then click

2. Next.

3. Click

4. Next

5. to review your host configuration details.

6. Click

7. Complete

8. to finalize the host creation.

9. The below image shows list of clouds available.

Results

the HPE ProLiant Bare Metal plugin automatically discovers and records all hardware details from the server using its Integrated Lights Out (iLO) management interface. This discovery process may take a few minutes, depending on the server and network conditions. After completion, the server becomes available (STATUS =available) in Morpheus for further provisioning and lifecycle operations.

Provisioning an Instance¶

Perform the following steps to provision an instance:

1. Navigate to

2. Provisioning

3. >

4. Instances.

5. Click the

6. • ADD.

7. In the

8. TYPE

9. tab, select the

10. Instance Type

11. as

12. HPE

13. Bare Metal (ILO) SERVER.

14. In the

15. GROUP

16. tab, complete the Instance Summary fields.

17. In the

18. CONFIGURE

19. tab, complete the Configuration Options:

0. Layout

1. : Select the appropriate layout from the drop-down list (for example, Single iLO Server).

2. Plan

3. : Choose one of the following:

• Generic Plan

• : Any iLO

• Specific Plan

• : For example, DL360.Gen10Plus.1-32C.129-256GiB

4. Resource Pool

5. : Select the required resource pool from the drop-down list.

6. Volumes

7. : Configure storage volumes as required. Refer to the Storage section for details.

• Enter the name of the volume in the first field.

• Select the volume type from the drop down list.

• NOTE

• When you select any other option apart from RAID, the system shows additional field to specify storage capacity. Enter the required storage. Ensure that you configure more than 16 GB storage. You cannot specify more than one volume for Windows environment.

8. Networks

9. : Configure network settings as required. Refer to the Networking section for details.

10. Image

11. : Select the Bare Metal OS image from the drop-down list.

12. Baremetal Host(s)

13. : Select the target Bare Metal host(s) from the drop-down list if specific server(s) are desired.

1. In the

2. AUTOMATION

3. tab, select the appropriate options, then click

4. Next.

5. In the

6. REVIEW

7. tab, verify the configuration summary and click

#. Complete. Post-Provisioning ^^^^^^^^^^^^^^^^^

After provisioning the instance:

• The new instance appears under

• Provisioning

• >

• Instances

• .

• To monitor provisioning progress, select the instance from the list.

• Once provisioning completes successfully, review the tabs as required.

• To access the instance console, click the

• Console

• tab

• After successful provisioning, verify that the instance and its corresponding bare metal host are listed in: - Under - Provisioning - > - Instances - .

  • Under

  • Infrastructure

  • >

  • Bare Metal

  • .

  • Go to the Instances page to view the instance Status, Health, CPU, Memory, and Storage details.

Importing Pre-Provisioned Server¶

Importing a Pre-Provisioned server enables administrators to bring existing physical servers and associated resources (networks and storage) into HPE Morpheus. This is the initial step in migrating an existing workload cluster into Morpheus management. It is completed in two phases: * Import * : Import existing servers as Pre-Provisioned resources.

• Convert to Managed

• : Convert imported servers into managed instances, creating Morpheus instances with associated network and storage attachments.

This process is performed one workload cluster at a time, and each cluster can contain one or more servers. Once the initial server is converted, additional imported servers can be added to the same instance using theAdd Nodeoperation.

Import Pre-Provisioned Servers¶

Perform the following to add a bare metal server:

1. Navigate to

2. Infrastructure

3. >

4. Compute

5. >

6. Bare Metal.

7. Click

8. Add Bare Metal Server.

9. Select the

10. Pre-Provisioned

11. server.

12. Complete the remaining server details and click

13. Save.

14. NOTE

15. For Windows

16. : When importing a Pre-Provisioned Windows server, select Windows OS. This is required because some import operations are specific to Windows.

17. During import, the

18. HPE

19. BMaaS validates the association between the provided iLO IP and OS IP by executing commands on the host OS. The supplied OS credentials must have elevated privileges:

• Linux OS

• : The user must have sudo privileges.

• Windows OS

• : The user must be in the Administrators group.

Results

Once the server is imported, it should be ready to be converted into a fully provisioned node.

Convert to Provisioned Node¶

Perform the following to convert to Managed or create a new instance:

1. After the server is imported, go to

2. Infrastructure

3. >

4. Compute

5. >

6. Bare Metal.

7. Select the imported server.

8. Click

9. Convert to Managed.

10. Confirm the server details and click

11. Execute.

12. NOTE

13. Use the same OS credentials that were provided during the import step. Results

TheConvert to Managedaction creates a new instance, makes the selected server a fully provisioned node, and adds it to the new instance. It creates the association of this server with networks and volumes inHPE Morpheus, as present in the network switches and the storage array, respectively. In addition, it creates the association of the VLAN interfaces with the IP addresses on the host OS on the server.

Add Additional Nodes¶

to the Instance To convert a Pre-Provisioned server into a fully provisioned node, and to make it part of an existing instance, the Add Node action is used, from the context of the Instance to which it is desired to be added.

Once an instance is created with the first converted node, you can add other imported servers to the same instance:

1. Navigate to

2. Provisioning

3. >

4. Instances.

5. Select the newly created instance.

6. Click

7. Add Node.

8. Select

9. Pre-Provisioned.

10. Choose the imported server and provide the required details.

11. Click

12. Execute

13. . Results

This converts the selected imported server into a managed node and adds it to the existing instance.

Firmware and Driver Lifecycle Management¶

Starting with HPE BMaaS version 1.0.0,HPE HPE Morpheus Software Enterprise supports firmware and driver updates for HPE ProLiant bare-metal servers using preloaded tasks and workflows. This capability enables administrators to centrally manage server firmware and driver compliance using HPE Service Pack for ProLiant (SPP) images, executed directly from the HPE Morpheus appliance.

Firmware and driver updates are performed through Jobs and Workflows in HPE Morpheus and can be run in Dry Run (inventory)or Deploy modes. Updates can target firmware only, drivers only, or both, depending on operational requirements. The update process supports multiple servers per job and provides detailed execution logs for auditing and troubleshooting.

Prerequisites

Before performing firmware and driver updates, ensure the following:

• HPE

• BM Plugin version 1.0.0 or later is installed.

• An appropriate

• HPE

• SPP ISO is available for each server generation (for example, Gen10 and Gen11 require different SPP ISOs).

• The

• HPE

• Morpheus appliance has access to the SPP ISO, either through:

  • A locally downloaded ISO file, or

  • A URL accessible without authentication.

• For driver inventory and updates within a deployed operating system:

  • iSUT (Integrated Smart Update Tools) and AMS (Agentless Management Service) must be installed and running on the target servers.

  • ESXi hosts are expected to already have iSUT installed.

Adding HPE SPP to Virtual Image Library¶

AddingHPE SPP to the Virtual Image Library This procedure describes how to add an HPE Service Pack for ProLiant (SPP) ISO to the Morpheus Virtual Images library for use in firmware and driver update workflows.

1. Obtain the appropriate

2. HPE

3. SPP ISO for the target ProLiant server generation.

4. NOTE

5. A separate ISO is required for each server generation (for example, Gen10 and Gen11).

6. In the Morpheus appliance, navigate to

7. Library

8. >

9. Virtual Images.

10. Click

11. Add

12. >

13. SPP.

14. Enter a name for the image (for example,

15. HPE

16. Gen10 SPP 2025.09.00

17. ).

18. From the

19. Operating System

20. drop-down list, select the appropriate

21. HPE

22. SPP for Gen…

23. entry.

24. Add the SPP ISO using one of the following methods:

• Upload the locally downloaded ISO file, or

• Select

• URL / PATH

• and paste the full URL for the ISO.

1. Leave all other properties at their default values.

2. Click

3. Save Changes.

4. NOTE

5. When uploading a local file, wait for the upload to complete.

6. In the

7. Virtual Images

8. list, wait until:

• Source

• shows

• Uploaded

• Status

• shows

• Active

1. Record the

2. ID

3. of the Virtual Image entry. This ID is required when creating the update job.

Installing iSUT on Deployed Instances¶

(Optional) To enable driver inventory and updates within the operating system, iSUT and AMS must be installed on each deployed instance.

1. Navigate to

2. Provisioning

3. >

4. Instances.

5. Select the target instance.

6. NOTE

7. Since the workflow requires iLO credentials, only one instance can be selected at a time. Multiple instances cannot be targeted for a single iSUT/AMS install.

8. Click

9. Actions

10. >

11. Run Workflow.

12. Select the appropriate workflow:

0. Download and Install iSUT and AMS (Linux), or

1. Download and Install iSUT and AMS (Windows)

1. Enter the

2. iLO credentials

3. for the targeted bare metal server.

4. NOTE

5. These are iLO credentials, not OS credentials.

6. Click

7. Execute.

8. Monitor progress from the

9. History

10. tab until the workflow completes.

Creating and Running an SPP Update Job¶

This procedure describes how to create and execute aHPE Morpheus Job to perform firmware and driver updates using an HPE SPP image.

1. Navigate to

2. Provisioning

3. >

4. Jobs.

5. Click

6. Add.

7. Enter a name for the job.

8. NOTE

• Separate jobs are required for different server generations (for example, Gen10 vs Gen11).

• Create separate jobs for

• Dry Run

• and

• Deploy

• executions.

1. Select

2. Workflow Job

3. as the

4. Job Type

5. and click

6. Next.

7. Select

8. Deploy SPP

9. as the

10. workflow.

11. Enter the

12. SPPVIRTUALIMAGE

13. value using the ID of the Virtual Image created earlier.

14. Select a

15. DEPLOYMODE

16. :

• DryRun

• : Performs inventory only

• Deploy

• : Applies firmware and/or driver updates

1. For

2. SPP Deploy Content

3. , choose one of the following:

• Firmware only

• Drivers only

• Firmware and Drivers

NOTEDriver inventory and updates require iSUT and AMS to be running on the target servers. #. In the #. Nodes #. field, enter the iLO details for each target server in JSON format (minimum 1 server, maximum 30 servers). For example: #. [

1. {

2. "ilo_ip":"1.2.3.4",

3. "ilo_user":"user1",

4. "ilo_password":"password1"

5. },

6. {

7. "ilo_ip":"1.2.3.5",

8. "ilo_user":"user2",

9. "ilo_password":"password2"

10. }

11. ]

12. Optional:

13. Create a schedule, or leave the job as

14. Manual.

15. Select

16. Run Now

17. if you want to execute the job immediately.

18. Click

19. Next

20. , review the settings, and click

21. Complete.

22. If the job was not run immediately, click the

23. gear icon

24. next to the job and select

#. Execute. Monitoring and Completion ————————-

1. Monitor job progress from the

2. Job Executions

3. tab.

4. Execution time may range from

5. 15 minutes to over one hour

6. , depending on:

0. Number of servers

1. Deploy mode

2. Selected content

3. Firmware and driver versions on the target servers

1. Upon completion, detailed logs are available in the

2. Job Executions

3. tab.

• Do not enter any values in

• Custom Config

• .

• Servers are not automatically rebooted as part of the update process. - If a reboot is required to complete updates, it must be performed manually at a time appropriate for the hosted services.

Post-SPP Firmware Update Cold Power Cycle¶

Post-SPP Firmware Update - Mandatory Cold Power Cycle After applying an HPE Service Pack for ProLiant (SPP) on Gen11 and Gen12 servers, a full cold power cycle is required to ensure proper initialization of updated firmware components.

An iLO reset or standard operating system reboot is not sufficient after an SPP update.

Failure to perform a cold power cycle may result in:

• Inconsistent Redfish storage inventory

• Smart Array controller desynchronization

• Missing or stale drive objects

• Management platform initialization failures

• Incomplete firmware activation Perform the following steps for cold power cycle:

1. Power OFF the server

2. :Shut down gracefully through the operating system or iLO interface. Confirm the server is completely powered off.

3. Disconnect AC Power

4. : Physically remove all power cables from the server power supplies.

5. Wait for 60 Seconds

6. : Allow sufficient time for residual power to drain. This clears controller cache and resets hardware state.

7. Reconnect Power

8. : Reattach all power cables securely.

9. Power ON the Server

10. : Boot the system normally. A full AC power removal forces:

• Smart Array controller re-enumeration

• PCI bus reinitialization

• Storage firmware reload

• Redfish object tree regeneration

• Hardware state synchronization This process resolves the majority of post-SPP Redfish storage inconsistencies observed on Gen11 and Gen12 platforms.

HPEstrongly recommends performing a full cold power cycle after major firmware bundle updates to ensure all updated components are fully initialized.

Network Management¶

At a high level, there are two network modes in which a cloud can be configured to operate: - Unmanaged network mode ( - Unmanaged - ).

• Managed network mode (

• ArubaCX-Int

• ).

Network modes are created during cloud creation.

Unmanaged Networks¶

The unmanaged Network mode is used when the network infrastructure is not managed by HPE Morpheus.

In this case, there is a minimal configuration that is created as default when the cloud gets created with the network mode set to Unmanaged network. This minimal configuration includes a default Resource Pool that can be used to associate compute servers with, and a default unmanaged network that is available during instance provisioning to attach with compute servers.

The default unmanaged network is configured as an untagged network with DHCP as the IP allocation method. This allows a compute instance provisioned to come up with network connectivity without any specific network configuration required from the user.

The unmanaged network assumes:

• The network infrastructure to be configured correctly for the untagged network to work correctly.

• A DHCP server stood up in the infrastructure for that network.

  Users can create other networks (VLANs) if required, in addition to the default unmanaged network, and use them in their BM instance. NOTE

• If the

• ALLOW IP OVERRIDE

• checkbox is selected (allows selection of DHCP or static IP or IP Pool), ensure that the

• CIDR

• and

• GATEWAY

• fields are configured correctly.

• At present, only one physical interface is supported for the unmanaged network mode.

The network consumption by an instance is the same as for managed networks.

Managed Networks¶

The managed network mode is used when the network infrastructure is to be managed by Morpheus. In this case, the user can selectArubCX-Intduring the cloud creation.

AddingHPE ArubaCX Plugin

In the managed network mode, the Aruba CX switches are supported as managed switches. To enable that, the ArubaCX plugin needs to be loaded.

You can load the ArubaCX plugin jar using theAdministration>Integrations.

Creating ArubaCX Network Integration¶

The network integration allows the user to specify the switch information. It is expected that there are 2 switches per rack acting as the top-of-rack (ToR) switches. You need to specify information for a switch pair for a rack. If there are more than 1 rack, then information for the switch pair for each rack is required.

1. Log in to the

2. HPE

3. HPE Morpheus Software Enterprise Software web interface using your administrator credentials.

4. Navigate to

5. Infrastructure

6. >

7. Network

8. >

9. Integrations.

10. Click the

11. Add

12. to add a new integration.

13. Select

14. HPE

15. Aruba CX Switches

16. under the

17. Networking

18. section.

19. Enter the following details for the network integration:

• Name

• for network integration

• Username/Password

• for the switches

• Switch pair IP Addresses

• for each pair of switches

1. Click the

2. Add Network Integration

3. to create the Network Integration.

Networks Configuration¶

Once the network integration is created, networks can be created using the specific network integration that was created. Networks essentially define the VLAN that they represent along with other attributes such as the subnet’s IPv4 prefix, IP address allocation method, gateway address, DNS, etc. The screenshot below shows those details.

TheVLAN Trunksspecifies the trunk VLANs to be added when this network is consumed by an instance. TheVLAN IDfield represents the primary VLAN for this network. This VLAN is configured as the untagged VLAN when this network is consumed by an instance.

TheNetwork Servicecorresponds to the network integration that was created. This specifies that the network is to be created in the infrastructure (switches) specified in the network integration selected.

ThePrivatecheckbox specifies that the network is a private network. By default, all networks are public. If private is selected, the primary VLAN in this network is not configured on the uplink connection. This would render them unreachable from outside of the cloud infrastructure. This is typically used for workload networks that are used to communicate between only the workload servers and other infrastructure within the private cloud.

The configuration of a network will result in the primary VLAN in that network being provisioned on the network switches. The server ports are configured when those networks are consumed during the provisioning of a compute instance.

Creating Network Using ArubaCX¶

Creating Network Using the ArubaCX Integration Prerequisites

Before starting to create networks using integration, ensure that a Bare metal cloud is created with the ‘Network Mode’ set to the integration. If the Bare metal cloud already exists then ensure that ‘Network Mode’ is set to integration.

Perform the following to create the network:

1. Log in to the

2. HPE

3. HPE Morpheus Software Enterprise Software web interface using your administrator credentials.

4. Navigate to

5. Infrastructure

6. >

7. Network.

8. Click the

9. Add

10. to add a new integration.

11. Enter the following details for the network:

• Group

• for the network

• Network Service

• specifies the Network Integration to use

• Name

• for the network

• Gateway, DNS

• information if required

• CIDR

• for the subnet

• Primary

• VLAN ID

• for the network

• Check the

• Private

• checkbox if a private network

• VLAN trunks

• for the network (optional)

• Choose

• Network Pool

• to be one of the IP pools configured

1. Click

2. Save Changes

3. to create the network.

Network Usage¶

Networks are attached to interfaces on a compute server. The interfaces can be the physical ports themselves or bond interfaces that combine two physical ports into an aggregated pipe. Bond interfaces provide the benefits of aggregated bandwidth on a single interface and also high availability by providing port-level redundancy.

Once the decision is made on what kind of interfaces to use, networks can be chosen from the preconfigured list to attach to the network interfaces. This determines which VLANs are configured on which switch ports (or LAGs). As mentioned earlier, the primary VLAN is provisioned as an untagged VLAN, and the trunk VLANs are provisioned as tagged VLANs on the server ports.

The supported bond types are:

• Static Bond: This uses an L2+L3-based hash on the server OS and a static LAG on the switches.

• LACP Bond: This uses the LACP mode on the server OS and LACP LAG on the switches.

• Switch Independent Bond: This uses the balance-tlb mode on Linux servers and the switch-independent mode on Windows. The switch is configured as independent physical ports.

Specifying Network Usage¶

Perform the following to specify networks used during instance provisioning:

1. Log in to the

2. HPE

3. HPE Morpheus Software Enterprise Software web interface using your administrator credentials.

4. Navigate to

5. Provisioning

6. >

7. Instances.

8. Select

9. HPE

10. Bare Metal (ILO) Server

11. as the type.

12. Click

13. Next.

14. Specify a

15. Group

16. ,

17. Cloud

18. , and a

19. Name

20. for the Instance.

21. Click

22. Next.

23. Select a

24. Network.

25. Select an

26. interface type

27. (Bond/Physical).

28. Specify any required

29. virtual interface.

30. Click

31. Next

32. and complete.

33. For physical interfaces, the interfaces represent the physical ports in their display order. Virtual networks specify that tagged networks under the primary network specified are to be configured on the server OS with an IP interface. If any of those tagged networks are not required to be configured on the server OS as an IP interface, do not specify a virtual interface for those.

Storage Management¶

There are two types of storage that are available for an instance to consume. One is the local storage available on the compute server used to create an instance. The other is the remote storage (SAN), using the Alletra MP storage array.

At present, there is no support for the management of the local storage throughHPE Morpheus. They are used to install the OS image, and any storage available beyond that is up to the user to configure and use. They cannot be managed fromHPE Morpheus.

The remote storage is fully manageable. The user can create/update/delete volumes and manage their attachment to compute servers.

Boot Volume Selection¶

During Instance Creation for Local Storage

During Morpheus instance creation, the provisioning workflow will delete existing logical volumes,create a boot volume, and then identify the correct disk deviceusing the device’s unique identifier (UID).

The boot volume is determined by matching the device UID found in the storage controller to the corresponding Linux device path.

Finding the Device Path

Once the device UID is known (from the storage controller), the provisioning script searches for the matching device in/dev/disk/by-id/

The script looks for thefirst entry that contains the UID(or a stripped version of the UID). These entries arestable identifiersthat point to the actual Linux block device.

Once a match is found, the script resolves the symbolic link to determine the real boot device path, which will be in the form:/dev/sdX

This/dev/sdXpath is then used for OS installation.

Remote Storage¶

Remote storage enables lifecycle management of volumes on supportedHPE Alletra storage arrays(includingAlletra MPandAlletra 9000, where supported) and allows compute instances to attach to or detach from those volumes. These operations can be performed during instance provisioning or post-provisioning through the reconfigure workflow. The currently supported transport protocol isFibre Channel.

To get started with using remote storage, first, the storage plugin for Alletra needs to be loaded, and a storage server added. This allows the user to specify the URL where the management interface of the storage array is available, along with the user credentials to manage the storage array.

There is also a concept of a datastore, which is used to represent a container for a set of volumes. A datastore is associated with a storage server and also a resource pool. The resource pool is used to represent a site or a location, which is useful when storage HA is being used with datastores associated with different sites.

AddingHPE AlletraStorage Integration

You can add the Allertra Storage plugin JAR using the Upload plugin method.

Creating a Storage Server¶

This procedure guides you through creating a storage server.

1. Log in to the

2. HPE

3. HPE Morpheus Software Enterprise Software web interface using your administrator credentials.

4. Navigate to

5. Infrastructure

6. >

7. Storage

8. >

9. Servers.

10. Click the

11. Add.

12. Provide a

13. Name

14. , select

15. HPE

16. Alletra Block Storage HVM

17. for type, specify the URL for the storage array, and the credentials.

18. Click the

19. Save Changes

20. to create the storage server.

Results

The added storage server appears under Servers.

Creating a Datastore¶

This procedure guides you through creating a Datastore. The datastore acts as a container for volumes and must be created before volumes can be created.

1. Log in to the

2. HPE

3. HPE Morpheus Software Enterprise Software web interface using your administrator credentials.

4. Navigate to

5. Infrastructure

6. >

7. Storage

8. >

9. DataStores.

10. Click the

11. Add.

12. Provide a

13. Name

14. , select

15. HPE

16. Alletra Block Storage Baremetal

17. for type, select your

18. cloud

19. , the

20. storage server

21. previously created,

22. FC

23. as the protocol type, and the

24. Resource Pool

25. that applies to this storage server.

26. Click the

27. Save

28. to create the DataStore.

Results

The added data store appears under Data Store.

Volume Management¶

Volume life cycle management can be performed under theInfrastructure>Storage>Volumestab. It allows the user to perform create/resize/delete operations.

Adding Volume¶

Perform the following procedure to create a new volume:

1. Navigate to

2. Infrastructure

3. >

4. Storage

5. >

6. Volumes.

7. Click the

8. Add

9. button.

10. Select the

11. storage server

12. to create the volume in and click

13. Next.

14. Select the required volume type, unreplicated, CPP replicated, or APP replicated, and click

15. Next.

16. On the

17. Configure

18. screen, specify the volume name, size, datastore in which the volume needs to be created, shared/unshared. You can optionally specify the server/instance to export the volume, depending on whether it is unshared/shared.

19. Click

20. Complete

21. to finish adding the volume.

Deleting Volume¶

This procedure allows the users to delete a volume. A volume can be deleted only after it is detached from all the servers.

1. Navigate to

2. Infrastructure

3. >

4. Storage

5. >

6. Volumes.

7. Click the

8. Actions

9. pulldown on the right and select

10. Delete

11. for the volume to be deleted.

12. Click the

13. Delete

14. on the confirmation screen.

Resizing Volume¶

This procedure allows the user to resize a volume. Volume size can only be increased. A rescan is required on the server OS to see the increased size.

1. Navigate to

2. Infrastructure

3. >

4. Storage

5. >

6. Volumes.

7. Click the

8. Actions

9. pulldown on the right and select

10. Resize

11. for the volume to be deleted.

12. Specify the new size and click

#. Resize. Reconfiguring Volume ^^^^^^^^^^^^^^^^^^^^

Reconfiguration allows the user to make changes to volumes consumed by a compute instance post-provisioning. This is achieved through theReconfigureaction on the instance.

New volumes can be created and attached to the compute instance. These can be shared or unshared volumes. Any volume attached to the compute instance can be resized to increase the size of the volume. Any attached volume can be detached. However, volumes cannot be deleted from the Reconfigure action. Volumes can be deleted only from the infrastructure management section.

All these operations work in the context of a compute instance and are not specific to a compute server within the instance.

1. Navigate to

2. Provision

3. >

4. Instance.

5. Click on the compute instance you want to reconfigure and access the details of the instance.

6. Click on

7. Actions

8. and select

9. Reconfigure.

10. In the

11. Reconfigure

12. wizard, make the changes desired to add a new volume, resize an existing volume or click the trash icon to detach a volume from the instance.

13. Click on

#. Reconfigure. Volume Consumption ——————

Consumption of volume is typically done through compute instance provisioning, where the user can specify volumes to attach to, whether existing volumes or new volumes to be created. It can also be done using the reconfigure action.

Instance Provisioning

During instance provisioning, the user can specify volumes to be attached to the servers within the instance. There are various types of volumes user can specify.

Sharing

Volumes can be shared or unshared (attached to a specific server only). Specifying a shared volume means a single volume is attached to all the servers within that instance. Specifying an unshared volume means a volume is created for each server within the instance and exported to the corresponding server.

Existing vs New

The user can specify a new volume to be created or specify to attach to an existing volume. Existing volume is applicable only to shared volumes.

Replicated vs Unreplicated

When creating new volumes, the user can specify that the volume is unreplicated or replicated. Depending on the storage array deployed and the HA configuration, replicated volumes can be specified as CPP (classic peer persistence) or APP (active peer persistence).

Using Volume¶

Perform the following to use the configured volume:

1. Navigate to

2. Provisioning

3. >

4. Instances.

5. Click

6. Add.

7. After selecting the

8. HPE

9. BareMetal ILO server for type and specifying the cloud, group, and a name for the instance, click

10. Next

11. to advance to the

12. Configure

13. section.

14. Click on the

16. sign next to Volumes to add a volume to this instance.

17. Specify a name for the volume, desired size, volume type to indicate whether it is a replicated volume or not, the datastore to create it in, and whether it’s a shared volume.

Troubleshooting and Diagnostics¶

This section provides a structured approach to diagnose and resolve common issues encountered during compute, OS imaging, networking, and storage operations.

Use the following details to obtain the accurate troubleshooting details:

• Identify the symptom: locate the closest match in the table or subsection.

• Confirm the likely cause: check the listed items using the provided tools and logs.

• Apply the suggested fix: perform the recommended actions.

• Collect diagnostic information: if the issue persists, gather logs and screenshots for support escalation. When reporting an issue, you require the following diagnostics details:

• System Details - Hostname / Device ID - OS version and build - BIOS/Firmware version

• Event Details - Date and time of failure - Step at which failure occurred - Any error messages or codes

• Logs - Relevant log files for the failed component - Screenshots of errors (if applicable)

Compute¶

Compute

The topic describes troubleshooting procedures for compute.

OS Imaging¶

OS Imaging

Firmware Lifecycle¶

Firmware and Driver Lifecycle Management

Networking¶

Storage¶

Storage

The topic describes troubleshooting procedures for storage.

Local Boot Volume¶

Local Storage - Boot Volume Selection During Instance Creation

Remote Storage¶

Known Limitations and Operational Considerations¶