diff --git a/docs/partners/suse_harvester/img/support.png b/docs/partners/suse_harvester/img/support.png
new file mode 100644
index 00000000..11fe1a97
Binary files /dev/null and b/docs/partners/suse_harvester/img/support.png differ
diff --git a/docs/partners/suse_harvester/index.md b/docs/partners/suse_harvester/index.md
index f81c3a90..934e8ee8 100644
--- a/docs/partners/suse_harvester/index.md
+++ b/docs/partners/suse_harvester/index.md
@@ -34,9 +34,44 @@ Ancillary network configuration of Harvester nodes is managed as a post-install
 
 - [Update Harvester Configuration After Installation](https://docs.harvesterhci.io/v1.3/install/update-harvester-configuration)
 
+#### Example iSCSI Configuration
+
+In a typical setup the IP addresses are assigned by DHCP on the NIC directly without any bridges, VLANs or bonds. The updates that needs to be done to `/oem/90_custom.yaml` on each compute node to reflect this configuration are described below.
+
+Insert the block after the management interface configuration and replace the interface names `ens224` and `ens256` with the actual interface names on your compute nodes. List the available interfaces on the compute node prompt with `ip link`.
+
+```text
+            ...
+            - path: /etc/sysconfig/network/ifcfg-ens224
+              permissions: 384
+              owner: 0
+              group: 0
+              content: |
+                STARTMODE='onboot'
+                BOOTPROTO='dhcp'
+                DHCLIENT_SET_DEFAULT_ROUTE='no'
+              encoding: ""
+              ownerstring: ""
+            - path: /etc/sysconfig/network/ifcfg-ens256
+              permissions: 384
+              owner: 0
+              group: 0
+              content: |
+                STARTMODE='onboot'
+                BOOTPROTO='dhcp'
+                DHCLIENT_SET_DEFAULT_ROUTE='no'
+              encoding: ""
+              ownerstring: ""
+              ...
+```
+
+Reboot the node and verify that IP addresses have been assigned to the NICs by running `ip addr show dev <interface name>` on the compute node prompt.
+
 ## Installing HPE CSI Driver for Kubernetes
 
-The HPE CSI Driver for Kubernetes is installed on Harvester by using the standard procedures for installing the CSI driver with Helm. Helm require access to the Harvester cluster through the Kubernetes API. You can download the Harvester cluster KubeConfig file by visiting the dashboard on your cluster and click "support" in the lower left corner of the UI.
+The HPE CSI Driver for Kubernetes is installed on Harvester by using the standard procedures for [installing the CSI driver with Helm](../../csi_driver/deployment.md#helm). Helm require access to the Harvester cluster through the Kubernetes API. You can download the Harvester cluster KubeConfig file by visiting the dashboard on your cluster and click "support" in the lower left corner of the UI.
+
+![](img/support.png)
 
 !!! note
     It does not matter if Harvester is managed by Rancher or running standalone. If the cluster is managed by Rancher, then go to the Virtualization Management dashboard and select "Download KubeConfig" in the dotted context menu of the cluster.