From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 4E4F51FF0E1 for ; Mon, 10 Aug 2026 14:39:36 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 53933217F8; Mon, 10 Aug 2026 14:38:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=feliscatus.org; s=s1-ionos; t=1785861716; x=1786466516; i=zzservers@feliscatus.org; bh=0yD3Nz+M3J3BBu8lh4G1hZuvESzZE1nwFCtdCHgnfAM=; h=X-UI-Sender-Class:From:To:References:In-Reply-To:Subject:Date: Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:cc: content-transfer-encoding:content-type:date:from:message-id: mime-version:reply-to:subject:to; b=hAVqRP+tnDsYYZaSCmlQRjuIlfzTWkaAmGhX5SLzaOcb9/NxKpE6vJ3BlIpoxETi s/DvfTuI3uB2QOkwMZ6I+XqvW6l8T/t1morL1i7FR3GRHcplUJSnwAAstmw2M3c6D e69VMz6oZk8KsjKTuQRRXW1yov8xm+CKjX4HXtLPPvPdJ1leSd7FYw2nWmiC+6lal iYr6p/YLvmcrXN3lPDrlmJEnFgLwmHj2OBjuSwaunq8f9w5M7qY7o4oiOBvR7PF6B CmqyEVKvIw8bXBz1yrPnMTjRSO5V3PfTB34nt+5Y+igPsLiek9wTFKSI0qgHgng8X unv46kQ0JwFg9OG+tQ== X-UI-Sender-Class: 55c96926-9e95-11ee-ae09-1f7a4046a0f6 From: To: References: <178549200314.1150.11530987597426240448@lists.proxmox.com> In-Reply-To: <178549200314.1150.11530987597426240448@lists.proxmox.com> Subject: Proxmox VE stretched cluster with NetApp MetroCluster over Fibre Channel Date: Tue, 4 Aug 2026 11:36:41 -0500 Message-ID: <035901dd242f$6ea0aeb0$4be20c10$@feliscatus.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: Ad0kL2ylBJfHmwJkR6qnu6LtQztziQ== Content-Language: en-us X-Provags-ID: V03:K1:UFL+e5yX8/EofzbQFF+G+aLU3vv8BbXZO6nP0wL0YENEzuWr2WQ AbBDQeG8J+OiQWtQD2L8xAjWnHj0CuO2StbUt3ebIxdG1JVq6iX0Ys//kZDHJsIDI85IIeb rFcwfLtBXAm+wlVhuzbw5oReLhOu1icTB3N1mne5zRvtXUGK9t4P7Kl3ZMZXVi75EJGZJeY e7U4QeaCP/Bn7unadHXPA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:zCOhNQYFUuw=;5WRZg9tnPcc16Ko6ZPYZmbGpnF4 nJxsW3NczP7wSqWBF+W2tF4ChKMCXf5mcPfvd3vMjiqVyZT2N+oXLi1KJzlcmZxCM1+h5+ZFk G5E2gz3Gr+NDuO66XNieP67mNbgvOf0FaXsTiWl/9rIwh0pgcJYf6+x4oxY5S1I97m61o6CQZ AbBsr7sb6a2SA/lueoCyfpa0PlTNRu8saBMeYV10qTOQAg9HAxGsCUzf2H3JaZM7KH9TOmUvJ CVL84oMlPib7cFTJuadoMcElO8YxGbe/BGtwIgrbPhht2uOCcbz2FjB4mW68x2r1VgbxrKSVO JvHK9NrzdIONymdHPb25SUQsbsLT3Hhq3F8NsGasR3XDFPy1PTHh6cKu1A8VktlD9YywqqN+d zel8+uI6sY/09eNBDJ4Z4UEALg4QDM05WYCl+FTCaHHuVIjJXBFefiP4qW73qRJr76aTXil+K 0hJsps4iz2wzPZTIG64Y+m5UY2OIYwoPy2DxelWfukEamffWplH2JReDNq0qF837VTsgoOSZm H6AZc4zQ9Vo3TN2ELYhAxASvRgE8uV0KgFKmpdudmdGhPj+hMahnalKCueAxsNvHesws6VFda cbqDcXYGAgkVLBevy+rlLXqsRL3VlVSIr4oDTTQVA4Gm+7bRETgGtGPKzNjU70Ggw7UnsofnT uNiW8c7G9KWrd5nTLGJIeVh7pHVOvn0LvTkXzZDSsXGwQelykUqc9SjnCKQLCCZDtquTlUQfg JtOI8DTCPOW+gp+ngyOJS4DoDRDaQug4/zJQmEi7qOtBOqdfjmxg9/rbWSfpKdQLsQDgm0Mkq lmjjVKmhq/8UBvG9jiq7xCWca59NV/1XIzOShRJ0wdD+HjXlkWvmXgV0VnvvDD18p2/LE4/wa USuFHG98P1sZTrDz4xRy5Ls6MQG6OUou2clvV/BPxbEOO9il65YI5TY60r8Zlcpa5uoN6B5at BQP3RqZYPv9bwXs0sakZeLWCwqi3PiJG1U48jIFzX7WFpbmhgnSkxTShvywCVbxUcL7T2V1JM THAvb/GydLqBw9WUFbyznrJOVG/P61UrJMqok2thrUgYtPOKizLCueB8An2uN6Oo26th1fuV+ hgZaCa/aKTYAKkoebJu3L1M6V6JkXMjxkJgDr2HxpIv/yby0fLjzr/FYsLxWxIf42sQXXVukS 1FhktZc1DgsHYLw7gQASfvle/wL+H1VHRj0/7kAGqZHpc7L5YOcvqKy7NZgPB9QgND378zx44 wlG1DNpoRg/9Maa5Zevpx8o5U94wfa8l+yKMEptPNS3SUpMfi4LIsWfnZrJSHNqn7fgKV7dvi PBc/WdleUfd5Jbb+u7ur5Z7W9VjxSoz0p02tbS8oegiEnfDQ1EzcrUc4LbltdkdRClTcKZYS1 T93WM8qE43ChKM7FMYEjiVXOHPZliLGTx12sTEk5kHPbN+blXinfH6W29KsJdjbwP2rLTmABB 1UjrBoXQCpM0O19/YYIEESyNOhf5LmOt0r8Lf5bkieTW+JBfxMJcCpeqfWaGDCOVsD7dRvQhX 9XVXqTzsCxD9SVEP59lf6JjhxmKw6MoOfw/d+q5CjG77ktdX5QK4H2BsX9O5r2uiwnO1ukN1i AwwnXSRIeeEpEE2wzvsCdQiZYMK3ElytW/h1DfKwAAW1x1e3kIB4bucQ4P5yZorOkHWXrIh/2 M2YTvQ5Q0GWm20/W9OKfVkv6zEhpQIBgg7Ae2gjpXAa6p/hkZTtYd4sCO8DrTGj8wc6hp7qeF p+mxin/5ESmBWrrCfF8zvkGqkCq214XohFSZz15GpkLY3phl/Qwscmo3HPqB9XUa2B70T8GfP 2xQK3E01yMm4JWUd84ANWtlO6kM7xXHWYect9Ro7hoSVPsNQTMuc7sIpuYOckG88XSQU6RFhi 7M8PZ+MEK8ZTLrJjkIhei1YcOQVWf5aY3azFZE= X-SPAM-LEVEL: Spam detection results: 0 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust RCVD_IN_MSPIKE_H3 -0.01 Good reputation (+3) RCVD_IN_MSPIKE_WL -0.01 Mailspike good senders SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record X-MailFrom: zzservers@feliscatus.org X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation Message-ID-Hash: ZXQ7OPB6G23VMGJHHNO7O3ESCLQOHYBP X-Message-ID-Hash: ZXQ7OPB6G23VMGJHHNO7O3ESCLQOHYBP X-Mailman-Approved-At: Mon, 10 Aug 2026 14:38:42 +0200 X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE user list List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Message: 1 Date: Thu, 30 Jul 2026 15:42:20 +0000 From: Iv=C3=A1n M=C3=A9ndez Cair=C3=B3s Subject: Proxmox VE stretched cluster with NetApp MetroCluster over Fibre Channel To: Proxmox VE user list Message-ID: Content-Type: text/plain; charset=3D"iso-8859-1" Hello, We are evaluating the replacement of an existing VMware vSphere = infrastructure with Proxmox VE and would like to confirm the feasibility = and support considerations of the proposed architecture. The current environment is distributed across two data centers and uses = a NetApp MetroCluster storage system. The new design would consist of: * One Proxmox VE cluster distributed across both data centers. * Approximately 12 Proxmox nodes per site. * NetApp MetroCluster providing synchronously replicated shared = storage. * Fibre Channel connectivity between the Proxmox hosts and NetApp. * Two independent FC fabrics based on Brocade G720 switches. * Dual-port FC HBAs in each Proxmox host. * Linux multipath/ALUA configured on every host. * Shared LVM storage on top of the FC LUNs. * Proxmox HA enabled for the virtual machines. * Redundant Corosync links between both sites, with latency below 5 = ms. * A QDevice located in a third failure domain. NetApp documentation explicitly lists MetroCluster support for Proxmox = VE using SAN protocols, including Fibre Channel: https://docs.netapp.com/us-en/netapp-solutions-virtualization/proxmox/pro= xmox-ontap-architecture.html#solution-architecture However, we would like to confirm the following points from the Proxmox = side: 1. Is a stretched Proxmox VE cluster using shared FC storage provided = by NetApp MetroCluster considered a supported and recommended = configuration? 2. Is shared LVM over a multipath FC device the appropriate storage = configuration for this design? 3. Are there any specific multipath, ALUA or LVM configuration = requirements for NetApp ONTAP/MetroCluster? 4. During a MetroCluster switchover, SAN I/O may be temporarily = interrupted. Are there any Proxmox, multipath or HA timeout parameters = that should be adjusted to tolerate this process and prevent unnecessary = fencing or VM failures? 5. In the event of a complete site failure, would Proxmox HA be able = to restart the affected VMs on the surviving site once the MetroCluster = switchover has completed and the FC LUNs are accessible again? 6. Is the proposed QDevice design sufficient to preserve quorum if = communication between the two data centers is lost? 7. Are there any known reference architectures, deployment guides or = production experiences involving Proxmox VE and NetApp MetroCluster over = Fibre Channel? We understand that the exact server, HBA, switch, ONTAP and firmware = versions must also be validated through the corresponding vendor = interoperability matrices. Any recommendations or experiences with a similar architecture would be = greatly appreciated. Best regards, Iv=C3=A1n M=C3=A9ndez ------------------------------ This is free, peer support. You know, three mini-PCs in a HomeLab. For professional usage, you should be working with a knowledgeable VAR. -----Burton