Guide Summary/shortcuts

This multipart guide will walk through the process to deploy 2x hyperconverged Proxmox VE nodes utilizing SvSAN virtualized block storage and a lightweight witness node, such as a Raspberry Pi.

https://support.stormagic.com/hc/en-gb/articles/17158984245789-Deploying-a-2x-node-witness-Proxmox-and-SvSAN-HA-cluster-Part-0-5-Creating-nested-VMs-for-Proxmox-on-VMware

https://support.stormagic.com/hc/en-gb/articles/15088839377053-Deploying-a-2x-node-witness-Proxmox-and-SvSAN-HA-cluster-Part-1-Installing-Proxmox

https://support.stormagic.com/hc/en-gb/articles/15567317393181-Deploying-a-2x-node-witness-Proxmox-and-SvSAN-HA-cluster-Part-2-Preparing-the-Hosts

https://support.stormagic.com/hc/en-gb/articles/16198574072733-Deploying-a-2x-node-witness-Proxmox-and-SvSAN-HA-cluster-Part-3-Creating-the-Proxmox-Cluster

https://support.stormagic.com/hc/en-gb/articles/16204170204061-Deploying-a-2x-node-witness-Proxmox-and-SvSAN-HA-cluster-Part-4-VSA-Deployment

https://support.stormagic.com/hc/en-gb/articles/16343256511261-Deploying-a-2x-node-witness-Proxmox-and-SvSAN-HA-cluster-Part-5-Storage-Provisioning

https://support.stormagic.com/hc/en-gb/articles/16347739183005-Deploying-a-2x-node-witness-Proxmox-and-SvSAN-HA-cluster-Part-6-Create-Guests-and-Enable-HA

https://support.stormagic.com/hc/en-gb/articles/27437315756573-Deploying-a-2x-node-witness-Proxmox-and-SvSAN-HA-cluster-Part-7-Enabling-healthy-login-and-cluster-restart

This next step/setup ensures that iSCSI storage provided by SvSAN virtual appliances is reconnected at boot and that all required Proxmox HA resources are properly configured to start automatically, in the event of a cluster down scenario.

Note: The following configuration needs to be done on every pve cluster member.

The below script will check the path count and login to paths if not the expected number.

Modify the $count value to your expected number of paths.

nano /root/iscsi_login.sh

#!/bin/bash
#check Multipath
#set -x
/usr/sbin/iscsiadm -m session
ret=$?
if [ $ret -ne 0 ]; then
/usr/sbin/iscsiadm -m node -l
else
for i in `/usr/sbin/multipath -ll | grep StorMagc | awk '{print $1}'`
do
count=`/usr/sbin/multipath -ll $i | grep sd | wc -l`
        echo $count
#modify count to expected number of sessions e.g. 2 or 4 usually
        if [ $count = 2 ]
        then echo "ALL OK"
        else
        echo "rescan iSCSI login targets"
        /usr/sbin/iscsiadm -m node -l
        fi
done
fi

Next chmod the script file to enable the execute bit

root@edgeline01:~# chmod +x /root/iscsi_login.sh

Set the script to run via crontab using the -e for edit switch

crontab -e

If this is the first time running you will be prompted for an editor - choose option1

root@edgeline01:~# crontab -e
no crontab for root - using an empty one
Select an editor.  To change later, run select-editor again.
  1. /bin/nano        <---- easiest
  2. /usr/bin/vim.tiny

Add the below lines to the crontab

*/5 * * * * /root/iscsi_login.sh > /dev/null 2>&1
@reboot /root/iscsi_login.sh

Such that it looks like:

# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').
#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h  dom mon dow   command
*/5 * * * * /root/iscsi_login.sh > /dev/null 2>&1
@reboot /root/iscsi_login.sh

See Also