Fujitsu RX300 S7 with FC storage Eternus DX90 S2

[krupecek]

Hello,
I'm a beginner in proxmox so maybe I'm doing something wrong or misunderstood.
I have a problem with 2xnodes Fujitsu RX300 S7 with connected 2x Fibre Channel to each node by Emulex Lightpulse to storage Eternus DX90 S2.
I want to do HA cluster - I have on other machine - Dell R620 installed Proxmox - this Dell will be working like a master of this 2xnodes Fujitsu.
In Proxmox on 2xnodes Fujitsu i can see /dev/sdb, /dev/sdc, /dev/sdd , /dev/sde - each connection of Fibre Channel to nodes but i cant add LVM in Proxmox Web Config.
I have in Eternus Dx90 s2 created 2x LUN and i dont know which Host Response need to use(screen).

 

[krupecek]

Disks on both nodes

 

[krupecek]

I've created Multipath.conf and added these disks wwids (from Proxmox instruction https://pve.proxmox.com/wiki/ISCSI_Multipath)
I have right now after command fdisk -l /dev/mapper/mpatha and /dev/mapper/mpathb but i cant mount this disks to proxmox :/

 

[LnxBil]

You need to create a physical volume on the disks before and then create on top the volume group like it is described here. Although, I'd skip the partition creation, this can lead to read/write amplification if the block size do not match, so in your case:

pvcreate /dev/mapper/mpatha
pvcreate /dev/mapper/mpathb

then create the diskgroup as described in the linked article.

 

[krupecek]

Thanks, right now works like a charm

 

[vmwombat]

Hello all.

I'm currently evaluating various hypervisors as an alternative to vmware. At the moment, the SAN/FC connection to Proxmox is stopping me from putting PM VE on the favorites list. I would have no problem familiarizing myself with configuring multipath on Debian. However, it should be ensured that these adjustments are retained and functional after an upgrade. Is there any official documentation from Proxmox on this topic? Or is an integration into Proxmox planned? Thanks!

ich evaluiere gerade verschiedene Hypervisoren als Alternative zu VMware. Im Moment hält mich der Punkt SAN/FC Anbindung an Proxmox noch davon ab PM VE auf die Favoritenliste zu setzen. Ich hätte kein Problem mich in die Konfiguration von Multipath auf Debian einzuarbeiten. Allerdings sollte sicher gestellt sein, dass diese Anpassungen nach einem Upgrade auch erhalten und funktionstüchtig bleiben. Gibt es irgendeine offizielle Dokumentation seitens Proxmox zu diesem Thema? Oder ist eine Integration in Proxmox geplant? Danke!

PS: Wir haben hier Fujitsu Eternus DX und Nimble Storages im Einsatz. Alles mit FC-Anbindung.

 

[LnxBil]

Is there any official documentation from Proxmox on this topic?

Any documentation from RHEL, Debian and storage vendors is fine. Multipath is not that hard and there are no choices with respect to the used storage technology. FC-based SAN in a supported PVE cluster has to be thick LVM.

Or is an integration into Proxmox planned?

No. Proxmox stressed multiple times, that FC-based SAN is a dying technology in the realy of hypervisors and there are not may posts on the forum, so maybe it's just very straight-forward or no one uses it.

PS: Wir haben hier Fujitsu Eternus DX und Nimble Storages im Einsatz. Alles mit FC-Anbindung.

We're running PVE for years sucessfully on DX100 and afterwards on DX200. We're running FC-based multipathing on Linux on various distributions for almost two decades and it has not changed much.

 

[vmwombat]

Any documentation from RHEL, Debian and storage vendors is fine. Multipath is not that hard and there are no choices with respect to the used storage technology. FC-based SAN in a supported PVE cluster has to be thick LVM.



No. Proxmox stressed multiple times, that FC-based SAN is a dying technology in the realy of hypervisors and there are not may posts on the forum, so maybe it's just very straight-forward or no one uses it.



We're running PVE for years sucessfully on DX100 and afterwards on DX200. We're running FC-based multipathing on Linux on various distributions for almost two decades and it has not changed much.

Thanks LnxBil! I will give it a try in a test environment. Thick LVM is another topic to invest.

 

[bbgeek17]

Thick LVM is another topic to invest

Its a Volume Manager that thickly allocates space on volume create and does not maintain metadata that can be used for snapshots or clones. Its a way to allow multi-write disk access for multiple hosts without them stepping on each other. Its not the best way, but it works for your purpose.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[LnxBil]

Its not the best way, but it works for your purpose.

Is there a better and supported way with the hardware given?

 

[bbgeek17]

Is there a better and supported way with the hardware given?

No, there isnt. It is the best for given infrastructure. I meant it that LVM Thick is not the best storage technology to use with virtualization in general.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[LnxBil]

No, there isnt. It is the best for given infrastructure. I meant it that LVM Thick is not the best storage technology to use with virtualization in general.

Thank you for clarifying and sadly, yes.