PVE 如何查詢 FC HBA WWPN、連接外部 SAN Storage，並將儲存空間提供給 VM

[Gary_F]

Hello everyone,

I am currently learning how to connect external SAN storage to Proxmox VE (PVE) using Fibre Channel (FC), and I would appreciate some guidance on the complete configuration process.

I have some limited experience with FC SAN storage in PVE, but I am still learning how to configure and manage it properly.

I would prefer to use the Web GUI whenever possible. If certain configurations can only be performed through the CLI, I would appreciate example commands along with explanations of what they do.

1. Checking the WWPN of the PVE Host​

1. Is it possible to view the WWPN of an FC HBA directly through the PVE Web GUI?
2. If the WWPN cannot be viewed through the GUI, which Linux commands should I use?
3. How can I verify that PVE has correctly detected the FC HBA and check the connection status of each FC port?
4. After obtaining the WWPN, should I provide it to the SAN storage administrator for host mapping and LUN mapping?

2. Connecting PVE to External SAN Storage​

1. After LUN mapping has been configured on the SAN storage system, how can I verify that PVE has successfully detected the assigned LUNs?
2. Is it necessary to perform a SCSI rescan? If so, can this be done through the Web GUI?
3. If multiple FC paths are available between PVE and the SAN storage, how should I configure multipathing?
4. Is there a GUI available for managing multipath configurations in PVE? If CLI configuration is required, could someone provide an example?
5. How can I verify that PVE is successfully connected to the SAN storage and check the LUN capacity and multipath status?

3. Using SAN Storage for Virtual Machines​

1. Once PVE has successfully detected an external SAN LUN, how can I add it as storage through the PVE Web GUI?
2. If I want to use the SAN LUN to store VM virtual disks, should I use LVM, LVM-thin, or another storage configuration?
3. After adding the SAN storage to PVE, how can I select it as the storage location when creating a new VM?
4. If I set up a PVE cluster with multiple hosts in the future, can they share the same SAN LUN?
5. If I want to support VM live migration between PVE hosts, which SAN storage configuration would be recommended?

What I Am Looking For​

I would greatly appreciate a practical, step-by-step guide covering the entire process:

Check WWPN → Configure SAN LUN Mapping → Detect LUNs in PVE → Configure Multipath → Add SAN Storage to PVE → Create a VM Using SAN Storage

If anyone could share GUI screenshots, CLI command examples, official documentation, or tutorials, that would be extremely helpful.

My current environment:

• Hypervisor: Proxmox VE 9.2.2
• Storage connection: Fibre Channel (FC)
• Storage type: External SAN Storage
• Preferred management method: Web GUI, with CLI instructions when necessary

Thank you in advance for your help and guidance!

 

[fabian]

This forum (except for the sections explicitly marked as German) are in English only, please translate before posting!

 

[bbgeek17]

Hi @Gary_F ,
In many cases the FC mapping is vendor dependent. Given that PVE is using Linux as the underlying OS, you should grab your SAN vendor's Linux configuration guide and follow that.

Once you have the basics done, you can use our guide here for general guidance: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/
While it uses iSCSI as the protocol, it's a very similar process for FC.

---

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

 

[Bu66as]

Hi @Gary_F, to add a few concrete bits to what @bbgeek17 said: there's no WWPN view in the GUI, and no multipath GUI either. You'll need the shell for that part.

cat /sys/class/fc_host/host*/port_name
cat /sys/class/fc_host/host*/port_state
cat /sys/class/fc_host/host*/speed

port_state should say Online. Yes, hand the WWPNs to your SAN admin for zoning/host mapping. Once the LUNs are mapped, run rescan-scsi-bus.sh (from sg3-utils) or simply reboot, then check with lsblk / lsscsi. For multipath: apt install multipath-tools, add the WWID with multipath -a /dev/sdX and check paths with multipath -ll. Your array vendor usually has a recommended device section for multipath.conf, so use that. The PVE wiki article on multipath is a good reference too.

Then, still on the shell and on one node only: pvcreate + vgcreate on the /dev/mapper device. After that it's GUI: Datacenter > Storage > Add > LVM, choose the VG and tick "Shared". In a cluster all nodes then see the same LUN, and live migration just works. Stick with thick LVM, not thin—thin won't work safely on shared LUNs. IIRC since PVE 9 there's also snapshot support on shared thick LVM as a tech preview. Before that, snapshots were the big downside of FC/iSCSI with LVM.