NetAppDocs · netapp-driley · Jan 20, 2026 · Nov 6, 2025
diff --git a/config-linux/iscsi-configure-host-side-network-task.adoc b/config-linux/iscsi-configure-host-side-network-task.adoc
@@ -89,7 +89,7 @@ IPV6_FAILURE_FATAL=no
 IPV6_ADDR_GEN_MODE=eui64
 ----
 +
-*Red Hat Enterprise Linux 9 (RHEL 9)*
+*Red Hat Enterprise Linux 9 and 10 (RHEL 9 and RHEL 10) and SUSE Linux Enterprise Server 16 (SLES 16)*
 +
 Use the `nmtui` tool to activate and edit a connection. The tool will generate a `<NIC port>.nmconnection` file within `/etc/NetworkManager/system-connections/`.
 +

diff --git a/config-linux/iser-ib-configure-network-attached-hosts-task.adoc b/config-linux/iser-ib-configure-network-attached-hosts-task.adoc
@@ -23,7 +23,7 @@ Make sure you have the following:
 
 . Enable and start iSCSI services on the host(s):
 +
-*Red Hat Enterprise Linux 8 and 9 (RHEL 8 and RHEL 9)*
+*Red Hat Enterprise Linux 8, 9 and 10 (RHEL 8, RHEL 9 and RHEL 10)*
 +
 ----
 
@@ -33,7 +33,7 @@ Make sure you have the following:
 # systemctl enable iscsid
 ----
 +
-*SUSE Linux Enterprise Server 12 and 15 (SLES 12 and SLES 15)*
+*SUSE Linux Enterprise Server 12, 15 and 16 (SLES 12, SLES 15 and SLES 16)*
 +
 ----
 

diff --git a/config-linux/nvme-fc-access-physical-targets-concept.adoc b/config-linux/nvme-fc-access-physical-targets-concept.adoc
@@ -68,6 +68,8 @@ defaults {
 }
 ----
 
+NOTE: This will no longer work on RHEL 10. It works on RHEL 9 and earlier and SLES 16 and earlier.
+
 Example output:
 
 ----

diff --git a/config-linux/nvme-fc-create-filesystems-sles-15-task.adoc b/config-linux/nvme-fc-create-filesystems-sles-15-task.adoc
@@ -4,12 +4,12 @@ sidebar: sidebar
 keywords: file systems, express linux configuration, software configuration, linux host, E2800, E5700, EF300, EF600, E-Series, eseries
 summary: For RHEL 8 and SLES 15, you create a filesystem on the native nvme device and mount the filesystem.
 ---
-= Create filesystems in E-Series - Linux RHEL 8, RHEL 9, and SLES 15 (NVMe over FC)
+= Create filesystems in E-Series - Linux RHEL 8, RHEL 9, RHEL 10, SLES 15 and SLES 16 (NVMe over FC)
 :icons: font
 :imagesdir: ../media/
 
 [.lead]
-For RHEL 8, RHEL 9, and SLES 15, you create a filesystem on the native nvme device and mount the filesystem.
+For RHEL 8, RHEL 9, RHEL 10, SLES 15 and SLES 16, you create a filesystem on the native nvme device and mount the filesystem.
 
 .Steps
 

diff --git a/config-linux/nvme-fc-setup-failover-host-task.adoc b/config-linux/nvme-fc-setup-failover-host-task.adoc
@@ -20,7 +20,7 @@ You must install the required packages on your system.
 
 .About this task
 
- SLES 12 use Device Mapper Multipath (DMMP) for multipathing when using NVMe over Fibre Channel. RHEL 8, RHEL 9, and SLES 15 use a built-in Native NVMe Failover. Depending on which OS you are running, some additional configuration of multipath is required to get it running properly.
+ SLES 12 use Device Mapper Multipath (DMMP) for multipathing when using NVMe over Fibre Channel. RHEL 8, RHEL 9, RHEL 10, SLES 15 and SLES 16 use a built-in Native NVMe Failover. Depending on which OS you are running, some additional configuration of multipath is required to get it running properly.
 
 == Enable Device Mapper Multipath (DMMP) for SLES 12
 By default, DM-MP is disabled in SLES. Complete the following steps to enable DM-MP components on the host.
@@ -94,4 +94,4 @@ Native NVMe Multipathing is disabled by default in RHEL 8 and must be enabled us
 .. If the command output is `N`, then Native NVMe Multipathing is still disabled.
 .. If the command output is `Y`, then Native NVMe Multipathing is enabled and any NVMe devices you discover will use it.
 
-NOTE: For RHEL 9 and SLES 15, Native NVMe Multipathing is enabled by default and no additional configuration is required.
+NOTE: For SLES 15, SLES 16, RHEL 9 and RHEL 10, Native NVMe Multipathing is enabled by default and no additional configuration is required.
diff --git a/config-linux/nvme-ib-access-physical-targets-concept.adoc b/config-linux/nvme-ib-access-physical-targets-concept.adoc
@@ -66,6 +66,8 @@ defaults {
 }
 ----
 
+NOTE: This will no longer work on RHEL 10. It works on RHEL 9 and earlier and SLES 16 and earlier.
+
 Example output:
 
 ----

diff --git a/config-linux/nvme-ib-create-filesystems-sles-15-task.adoc b/config-linux/nvme-ib-create-filesystems-sles-15-task.adoc
@@ -4,12 +4,12 @@ sidebar: sidebar
 keywords: file systems, express linux configuration, software configuration, linux host, E2800, E5700, EF300, EF600, E-Series, eseries
 summary: For RHEL 8 and SLES 15, you create a filesystem on the native nvme device and mount the filesystem.
 ---
-= Create filesystems in E-Series - Linux RHEL 8, RHEL 9, and SLES 15 (NVMe over InfiniBand)
+= Create filesystems in E-Series - Linux RHEL 8, RHEL 9, RHEL 10, SLES 15 and SLES 16 (NVMe over InfiniBand)
 :icons: font
 :imagesdir: ../media/
 
 [.lead]
-For RHEL 8, RHEL 9, SLES 15, you create a filesystem on the native nvme device and mount the filesystem.
+For RHEL 8, RHEL 9, RHEL 10, SLES 15 and SLES 16, you create a filesystem on the native nvme device and mount the filesystem.
 
 .Steps
 

diff --git a/config-linux/nvme-ib-set-up-failover-task.adoc b/config-linux/nvme-ib-set-up-failover-task.adoc
@@ -22,7 +22,7 @@ NOTE: Refer to  https://mysupport.netapp.com/matrix[NetApp Interoperability Matr
 
 .About this task
 
- SLES 12 use Device Mapper Multipath (DMMP) for multipathing when using NVMe over Infiniband. RHEL 8, RHEL9, and SLES 15 use a built-in Native NVMe Failover. Depending on which OS you are running, some additional configuration of multipath is required to get it running properly.
+ SLES 12 use Device Mapper Multipath (DMMP) for multipathing when using NVMe over Infiniband. RHEL 8, RHEL 9, RHEL 10, SLES 15 and SLES 16 use a built-in Native NVMe Failover. Depending on which OS you are running, some additional configuration of multipath is required to get it running properly.
 
 == Enable Device Mapper Multipath (DMMP) SLES 12
 By default, DM-MP is disabled in SLES. Complete the following steps to enable DM-MP components on the host.
@@ -93,4 +93,4 @@ Native NVMe Multipathing is disabled by default in RHEL 8 and must be enabled us
 
 .. If the command output is `Y`, then Native NVMe Multipathing is enabled and any NVMe devices you discover will use it.
 
-NOTE: For SLES 15 and RHEL 9, Native NVMe Multipathing is enabled by default and no additional configuration is required.
+NOTE: For SLES 15, SLES 16, RHEL 9 and RHEL 10, Native NVMe Multipathing is enabled by default and no additional configuration is required.
diff --git a/config-linux/nvme-ib-setup-host-side-task.adoc b/config-linux/nvme-ib-setup-host-side-task.adoc
@@ -13,13 +13,13 @@ Configuring an NVMe initiator in an InfiniBand environment includes installing a
 
 .Before you begin
 
-You must be running the latest compatible RHEL 8, RHEL 9, SUSE Linux Enterprise Server 12 or 15 service pack operating system. See the https://mysupport.netapp.com/matrix[NetApp Interoperability Matrix Tool^] for a complete list of the latest requirements.
+You must be running the latest compatible RHEL 8, RHEL 9, RHEL 10, SLES 12, SLES 15 or SLES 16 service pack operating system. See the https://mysupport.netapp.com/matrix[NetApp Interoperability Matrix Tool^] for a complete list of the latest requirements.
 
 .Steps
 
 . Install the rdma, nvme-cli, and infiniband packages:
 +
-*SLES 12 or SLES 15*
+*SLES 12, SLES 15 or SLES 16*
 +
 ----
 
@@ -28,7 +28,7 @@ You must be running the latest compatible RHEL 8, RHEL 9, SUSE Linux Enterprise
 # zypper install nvme-cli
 ----
 +
-*RHEL 8, or RHEL 9*
+*RHEL 8, RHEL 9 or RHEL 10*
 +
 ----
 
@@ -163,7 +163,7 @@ IPV6INIT=no
 NAME=ib1
 ONBOOT=yes
 ----
-*RHEL 9*
+*RHEL 9, RHEL 10 or SLES 16*
 +
 Use the `nmtui` tool to activate and edit a connection. Below is an example file `/etc/NetworkManager/system-connections/ib0.nmconnection` the tool will generate:
 +

diff --git a/config-linux/nvme-roce-access-physical-targets-concept.adoc b/config-linux/nvme-roce-access-physical-targets-concept.adoc
@@ -66,6 +66,8 @@ defaults {
 }
 ----
 
+NOTE: This will no longer work on RHEL 10. It works on RHEL 9 and earlier and SLES 16 and earlier.
+
 Example output:
 
 ----

diff --git a/config-linux/nvme-roce-create-filesystems-sles-15-task.adoc b/config-linux/nvme-roce-create-filesystems-sles-15-task.adoc
@@ -4,12 +4,12 @@ sidebar: sidebar
 keywords: file systems, express linux configuration, software configuration, linux host, E2800, E5700, EF300, EF600, E-Series, eseries
 summary: For SLES 15, you create a filesystem on the native nvme device and mount the filesystem.
 ---
-= Create filesystems in E-Series - Linux RHEL 8, RHEL 9, and SLES 15 (NVMe over RoCE)
+= Create filesystems in E-Series - Linux RHEL 8, RHEL 9, RHEL 10, SLES 15 and SLES 16 (NVMe over RoCE)
 :icons: font
 :imagesdir: ../media/
 
 [.lead]
-For RHEL 8, RHEL 9, and SLES 15, you create a filesystem on the native nvme device and mount the filesystem.
+For RHEL 8, RHEL 9, RHEL 10, SLES 15 and SLES 16, you create a filesystem on the native nvme device and mount the filesystem.
 
 .Steps
 

diff --git a/config-linux/nvme-roce-setup-failover-host-task.adoc b/config-linux/nvme-roce-setup-failover-host-task.adoc
@@ -22,7 +22,7 @@ NOTE: Refer to the https://mysupport.netapp.com/matrix[NetApp Interoperability M
 
 .About this task
 
-SLES 12 use Device Mapper Multipath (DMMP) for multipathing for NVMe over RoCE. RHEL 8, RHEL 9, and SLES 15 use a built-in Native NVMe Failover. Depending on which OS you are running, some additional configuration of multipath is required to get it running properly.
+SLES 12 use Device Mapper Multipath (DMMP) for multipathing for NVMe over RoCE. RHEL 8, RHEL 9, RHEL 10, SLES 15 and SLES 16 use a built-in Native NVMe Failover. Depending on which OS you are running, some additional configuration of multipath is required to get it running properly.
 
 == Enable Device Mapper Multipath (DMMP) for SLES 12
 By default, DM-MP is disabled in SLES. Complete the following steps to enable DM-MP components on the host.
@@ -94,4 +94,4 @@ Native NVMe Multipathing is disabled by default in RHEL 8 and must be enabled us
 .. If the command output is `N`, then Native NVMe Multipathing is still disabled.
 .. If the command output is `Y`, then Native NVMe Multipathing is enabled and any NVMe devices you discover will use it.
 
-NOTE: For RHEL 9 and SLES 15, Native NVMe Multipathing is enabled by default and no additional configuration is required.
+NOTE: For SLES 15, SLES 16, RHEL 9 and RHEL 10, Native NVMe Multipathing is enabled by default and no additional configuration is required.
diff --git a/config-linux/nvme-roce-setup-host-side-task.adoc b/config-linux/nvme-roce-setup-host-side-task.adoc
@@ -13,21 +13,21 @@ NVMe initiator configuration in a RoCE environment includes installing and confi
 
 .Before you begin
 
-You must be running the latest compatible RHEL 8, RHEL 9, SUSE Linux Enterprise Server 12 or 15 service pack operating system. See the https://mysupport.netapp.com/matrix[NetApp Interoperability Matrix Tool^] for a complete list of the latest requirements.
+You must be running the latest compatible RHEL 8, RHEL 9, RHEL 10, SLES 12, SLES 15 or SLES 16 service pack operating system. See the https://mysupport.netapp.com/matrix[NetApp Interoperability Matrix Tool^] for a complete list of the latest requirements.
 
 .Steps
 
 . Install the rdma and nvme-cli packages:
 +
-*SLES 12 or SLES 15*
+*SLES 12, SLES 15 or SLES 16*
 +
 ----
 
 # zypper install rdma-core
 # zypper install nvme-cli
 ----
 +
-*RHEL 8, and RHEL 9*
+*RHEL 8, RHEL 9 or RHEL 10*
 +
 ----
 
@@ -122,7 +122,7 @@ REMOTE_IPADDR=
 STARTMODE='auto'
 ----
 +
-*RHEL 9*
+*RHEL 9, RHEL 10 or SLES 16*
 +
 Use the `nmtui` tool to activate and edit a connection. Below is an example file `/etc/NetworkManager/system-connections/eth4.nmconnection` the tool will generate:
 +

diff --git a/config-linux/srp-ib-configure-network-connections-task.adoc b/config-linux/srp-ib-configure-network-connections-task.adoc
@@ -71,7 +71,6 @@ systemctl start rdma
 
 . Enable the SRP daemon.
 +
-*SLES 12 or greater*
 
  ** To enable the SRP daemon to start on boot:
 +
-Original file line number
+Diff line change
@@ Expand Up / @@ -68,6 +68,8 @@ defaults { @@
     }
     ----
+    NOTE: This will no longer work on RHEL 10. It works on RHEL 9 and earlier and SLES 16 and earlier.
     Example output:
     ----
@@ Expand Down @@