About attaching SAN volumes to a server profile

Volumes are associated with server profiles through volume attachments. Attaching a volume to a server profile gives the server hardware assigned to the server profile access to storage space on a storage system.

As you create or edit a server profile, you can attach an existing volume or dynamically create a new volume to attach.

The storage system does not provide access to the volumes until the server profile is assigned to a server.

Permanent volumes

Newly created volumes can be marked as permanent so that they continue to exist after they are removed from the profile or if the profile is deleted. Otherwise, a nonpermanent volume is deleted when the server profile is deleted.

SAN volume attachments

You can create and edit SAN volume attachments through the server profile. For example, you can enable and disable storage paths from the server to the SAN storage.


If you modify the server profile template that the server profile is associated with, the appliance attempts to map existing SAN storage volumes to the associated server profile template volumes. Shared volumes are mapped based on the matching URI. Private volumes configured with explicit LUN values are generally mapped, but private volumes configured as AUTO LUN require manual mapping to the equivalent volume attachments in the server profile template.

Storage target ports

Within a server profile, storage target ports for volume attachment can be assigned automatically or you can manually assign available ports. The target ports that are assigned automatically will belong to the same port group. Target ports that you assign manually can belong to the same or different port groups. Port groups are created when you add a storage system to HPE OneView.

If you assign the target ports manually to a server profile, changing the ports back to automatic assignment requires you to first manually select all the unselected target ports.

LUN designation

The LUN for a SAN storage volume can be generated automatically when a server profile is created (Auto setting) or manually specified.

When manually specifying a LUN, note that operating systems do not accept and cannot boot from volumes using values greater than 254 (255 for Linux). Similarly, some storage network mezzanine adapters have similar limits where using values greater than 254 can cause the Apply operation for a server profile to fail.

For supported adapters, consult the HPE OneView Support Matrix to locate known LUN limits.

Existing HPE 3PAR volumes

This applies to Fiber Channel (direct attach, fabric attach, and FCoE) only.

On 3PAR StoreServ Storage systems, a host sees VLUN allows only a specific host to see a volume and a matched set VLUN allows only a specific host on a specific port to see the volume.

To reuse a host sees configuration in HPE OneView when adding an existing 3PAR volume to a profile, you must enter the exact LUN value as configured on the 3PAR array.

In HPE OneView, use the Manual LUN option to add the exact LUN value in the Add Volume dialog. To reuse end-to-end connectivity for the volume, manually specify the following:

  • LUN value (matching the LUN on the 3PAR storage system)

  • Target ports

Also, to attach (export) a 3PAR volume as host sees, all storage paths to that volume must be enabled or disabled together. Some paths cannot be enabled while some are disabled. For more information, download the HPE 3PAR StoreServ Storage Concepts Guide from the HPE Storage Information Library http://www.hpe.com/info/storage/docs.

HPE StoreVirtual volumes (iSCSI only)

On StoreVirtual Storage systems, there are two volume types:
  • Single LUN per Target (SLPT)

    SLPT volumes have LUN 0 in the server profile, and the Target in the attachment path designates the explicit volume on the storage system.

  • Multiple LUN per Target (MLPT)

    MLPT volumes each have a unique LUN value in the server profile.

HPE Nimble (Fibre Channel and iSCSI)

HPE Nimble currently supports MLPT only.