Configuring Attachments to Ultra High Performance Volumes
When you attach a volume configured for the Ultra High Performance level, to achieve the optimal performance, the volume attachment must be multipath-enabled.
The Block Volume service attempts to enable the attachment for multipath when the volume is being attached. If not all of the prerequisites have been addressed, the volume attachment will not be multipath-enabled.
The maximum number of ultra high performance block volume attachments is 32.
Multiple ultra high performance volumes are supported on instances with Oracle Cloud Agent version 1.39 or later. Check the version with one of the following
commands:
Oracle Linux: yum info
oracle-cloud-agent
Ubuntu: snap info
oracle-cloud-agent
If an ultra high performance volume is already attached before using the
multiple ultra high performance volumes feature, then we recommend that you
reattach the volumes to achieve best performance. If you don't reattach the
volumes, then you will not achieve best performance.
If an ultra high performance volume is attached to the instance, and if Oracle Cloud Agent is upgraded to version 1.39, or later, for the first time, then we
recommend that you reboot the instance to achieve best performance. If you
don't reboot the instance, then you will not achieve the best maximum
performance per instance.
The compute instance must have either a public IP address or a service gateway for
the Block Volume Management plugin to be able
to connect to Oracle services, see Service gateways or public IP addresses.
Permissions must be configured to allow the Block Volume Management plugin to
report the iSCSI setup results for multipath-enabled iSCSI attachments, see
Configure Permissions.
You can use oci-utils or oci-iscsi-config when configuring and
working with iSCSI attached volumes, however you should ensure that you don't
use both at the same time. If you've started using one of these tools to work
with a volume, you should continue to use the same tool with that volume, and
not switch to using the other tool. If you use both, you could encounter the
behavior described in Volume Attachment Incorrectly Reported as Multipath-Enabled.
Supported Images for Multipath-Enabled iSCSI Attachments 🔗
For multipath-enabled attachments, the attached instance must be running a Linux-based image.
Note
Multipath-enabled attachments are not supported for Windows instances or
Oracle Autonomous Linux instances.
Required Custom Image Configuration to Support Multipath-Enabled iSCSI Attachments
For a custom image to support multipath-enabled iSCSI attachments, the Unbreakable
Enterprise Kernel (UEK) version must be UEK6U1 or higher. The UEK6U1 UEK is associated
with the kernel major release version 5.4.17-2036, released in November, 2020.
After you have verified that the custom image UEK version is one that supports multipath-enabled attachments, you need to update the Storage.Iscsi.MultipathDeviceSupported property for the image to true. For more information, see Configuring Image Capabilities for Custom Images.
Supported Compute Shapes for Multipath-Enabled iSCSI Attachments 🔗
This section identifies the Compute shapes that support multipath-enabled iSCSI attachments. For more details, such as performance characteristics and maximum number of attachments, see Performance Details for Shapes.
Current VM shapes configured for 16 cores or more support multipath-enabled attachments.
See VM Shapes for iSCSI and Paravirtualized Attached Volumes for
performance characteristics of volumes attached to VMs with iSCSI attachments. To verify
that a shape supports multipath-enabled attachments look for the value Yes in
the Supports Ultra High Performance (UHP) column in the VM Shapes table.
All current bare metal shapes support multipath-enabled iSCSI attachments. See for more
information Bare Metal Shapes for
performance characteristics of block volumes attached to bare metal instances.
Multipath-Enabled Paravirtualized Attachments 🔗
The section describes the prerequisites and steps required to configure multipath-enabled
paravirtualized volume attachments.
Prerequisites 🔗
Following is a list of prerequisites and requirements for multipath-enabled
paravirtualized attachments.
If an ultra high performance volume is already attached, then we recommend that you reattach the volumes to achieve best performance. If you do not reattach the volumes, then you will not achieve best maximum performance per instance.
Supported Images for Multipath-Enabled Paravirtualized Attachments 🔗
For multipath-enabled attachments, the attached instance must be running one of the following images or a custom image based on one of these images:
Oracle Linux
Ubuntu
CentOS
Windows
Note
Multipath-enabled attachments are not supported for Oracle Autonomous
Linux instances.
Supported Compute Shapes for Multipath-Enabled Paravirtualized Attachments 🔗
Current VM shapes configured for 16 cores or more support multipath-enabled attachments.
See VM Shapes for iSCSI and Paravirtualized Attached Volumes for
performance characteristics of volumes attached to VMs with paravirtualized attachments.
To verify that a shape supports multipath-enabled attachments look for the value
Yes in the Supports Ultra High Performance (UHP) column in the VM
Shapes table.
Note
Multipath-enabled attachments to bare metal instances only support iSCSI
attachments.
For more details, such as performance characteristics and maximum number of attachments,
see Performance Details for Shapes.