This guide provides instructions on how to connect your Proxmox instance to your FlashArray as a central FC LVM device that provides shared storage for a datacenter cluster.
Note:
-
For instructions on how to connect Proxmox to the FlashArray using iSCSI, follow this guide.
-
For instructions on how to connect Proxmox to the FlashArray using NFS, follow this guide.
-
For instructions on how to connect Proxmox to the FlashArray using NVMe-TCP, follow this guide.
Pre-requisites
This guide assumes that you have already completed the following:
-
Install Multipath tools on all of your Proxmox nodes:
To ensure high availability and load balancing for your iSCSI storage, install the multipath tools on each Proxmox host:
apt update
apt install multipath-tools
-
Identify the Pure Storage WWID using the following command:
root@proxmox1:~# cat /sys/class/fc_host/host*/port_name
0x20000025b51a0032
0x20000025b51b0032
-
Create the Proxmox hosts on the FlashArray and add the WWNs to the hosts:
-
Go to .
-
Click the + icon.
-
In the pop-up window, give your host a name and under personality select none.
-
Configure the Proxmox host WWN under the Host Ports section:
-
Create a host group and add the Proxmox hosts into it:
-
Go to .
-
Click the + icon.
-
Click Create Host Group. In the pop-up window, give your host group a name:
-
Add the Proxmox hosts to the host group:
-
Create a volume/LUN for your datastore:
-
Go to .
-
Click the + icon.
-
In the pop-up window, give your volume a name and size and add your newly created host group to this volume/LUN.
-
Verify that you can see the LUN on the Proxmox nodes using the command
-l /dev/disk/by-path:
Note:
Note the LUN number is 254:
-
Configure Multipath:
-
Create the
multipath.conf file in /etc/multipath.conf with the following content (If it doesn't already exist). This configuration blacklists all devices and sets the correct exceptions for Pure Storage:
Important:
-
Blacklists will vary based on your setup. In this example, there is one local drive for the "boot" device. If you boot from SAN, your blacklist configuration will be different.
-
If you are using other storage vendors, you will need to change your blacklist exceptions to accommodate them as needed.
defaults {
find_multipaths off
}
blacklist {
device {
vendor ".*"
product ".*"
}
}
blacklist_exceptions {
device {
vendor "PURE"
product ".*"
}
}
-
Start the multipath service:
systemctl start multipathd
systemctl restart multipathd
multipath -r
-
Verify that the multipath device is correctly configured and active:
The output should show the Everpure device with its paths active and ready:
3624a9370730d187406c14775008ef137 dm-5 PURE,FlashArray
size=100G features='0' hwhandler='1 alua' wp=rw
-+- policy='service-time 0' prio=50 status=active
|- 33:0:0:1 sdb 8:16 active ready running
|- 34:0:0:1 sdc 8:32 active ready running
|- 35:0:0:1 sde 8:64 active ready running
- 36:0:0:1 sdd 8:48 active ready running
Important: This step will need to be performed on all hosts in the cluster.
-
Create shared storage (LVM):
To use the storage as a shared resource for all Proxmox nodes, create an LVM datastore. Perform these steps on only one Proxmox host:
pvcreate /dev/mapper/<DEVICE_NAME>
vgcreate VG_NAME /dev/mapper/<DEVICE_NAME>
After these steps, the shared LVM storage will be available to add in the Proxmox GUI. Head to . Give your volume a name and choose the new volume group you created. Below is a screenshot of what the setup should look like:
Below is a screenshot of how it looks in the WebUI:
Test high availability by creating virtual machines on this volume and turning off a host. If your setup is correct, you should see it reboot on another host after a couple of minutes.