From b981ef1b292a05ccc456a56c4bcf75455d8ca182 Mon Sep 17 00:00:00 2001 From: Dmitrii Gilev Date: Mon, 15 Jun 2026 12:54:20 +0200 Subject: [PATCH] m SAN generic setup update high-level info Signed-off-by: Dmitrii Gilev --- .../product/cluster_configuration/lvm/generic_guide.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/product/cluster_configuration/lvm/generic_guide.md b/content/product/cluster_configuration/lvm/generic_guide.md index 3b0660629..77727a0c6 100644 --- a/content/product/cluster_configuration/lvm/generic_guide.md +++ b/content/product/cluster_configuration/lvm/generic_guide.md @@ -7,11 +7,11 @@ weight: "4" ### Hosts SAN Configuration -The abstraction required to access LUNs consists of block devices. This means that there are -several ways to set them up, although it usually involves using a network block protocol such as -iSCSI or Fibre Channel, as well as some way to make it redundant, like DM Multipath. +The abstraction required to access LUNs consists of block devices. This means that there are several ways to set them up, although it usually involves using a network block protocol such as iSCSI or Fibre Channel, as well as some form of path redundancy, such as DM Multipath. -Here is a sample session for setting up access via iSCSI and multipath: +Hypervisor hosts acting as SCSI initiators must be configured according to the storage vendor's documentation and recommended best practices. The exact implementation may vary depending on the storage platform, access protocol (iSCSI or Fibre Channel), and multipathing requirements. Vendor-specific guidance should always take precedence over generic operating system configuration procedures. + +The following example illustrates a generic iSCSI and DM Multipath configuration on Linux hosts and is provided for reference purposes only. ``` # === ISCSI ===