Fibre Channel is a high-speed data transfer protocol that provides reliable and secure delivery of raw block data. It supports point-to-point connection between devices as well as connection via switched fabric (via Fibre Channel switches). Fibre cChannel (FC) is used to build a dedicated network used for storage connectivity between shared storage and servers (SAN).
While FC provides fast and secure connection to block storage, StarWind delivers High Availability by replicating the storage between the nodes. By combining StarWind Virtual SAN for vSphere with FC, users effectively eliminate single points of failures in their storage infrastructure.
This guide is intended for experienced system administrators and IT professionals who would like to have StarWind Virtual SAN Highly Available devices shared via Fibre cChannel protocol..
A full set of up-to-date technical documentation can always be found here, or by pressing the Help button in the StarWind Management Console.
Make sure that the prerequisites for deploying FC on StarWind Virtual SAN for vSphere are met:
- StarWind Virtual SAN virtual machines are is installed on the ESXi host.
- Networks are configured and the required amount of storage is provisioned to StarWind VMs.
- Qlogic Fibre Channel adapters are installed in storage hosts.
- Fibre Channel adapter is passed through to StarWind Virtual SAN virtual machine.
In order to install StarWind Virtual SAN for vSphere and configure the networks, please refer to the following guide: https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-vsphere-installation-and-configuration-guide
StarWind Virtual SAN for vSphere system requirements can be found here:
1. Log in to StarWind Virtual SAN for vSphere using the following default credentials:
2. Navigate to the Terminal tab and list the available disks, run the following command to install Linux mainline kernel:
sudo yum –enablerepo=elrepo-kernel install kernel-ml
3. After successful installation, edit grup grub to boot from the kernel-ml:
sudo vi /etc/default/grub
Look for the line containing GRUB_DEFAULT=X, and change it to GRUB_DEFAULT=0
Save the configuration file.
4. Recreate the kernel configuration using the following command:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Reboot the VM:
5. Check kernel version after reboot:
6. By default, FC HBA QLogic starts in the initiator mode., iIt has to be turned to the target mode during the initiation. To do this, create a file /etc/modprobe.d/qla2xxx.conf with the parameter listed below, rebuild initrd and reboot.
cat <<EOF >> /etc/modprobe.d/qla2xxx.conf
options qla2xxx qlini_mode=disabled
dracut -f; reboot
7. Check HBA mode after restart:
8. Install targetcli
sudo yum install targetcli -y
sudo systemctl enable target.service
sudo systemctl start target.service
Configure StarWind Device
9. Create StarWind standalone device. Please refer to the following page:
10. Discover and connect StarWind device via loopback (127.0.0.1)
iscsiadm -m discovery -t st -p 127.0.0.1
iscsiadm -m node -T iqn.2008-08.com.starwindsoftware:sw-sed-vsa-fc-01.starwind.local-vtl -p 127.0.0.1 -l
11. Check that StarWind device was successfully connected:
sudo iscsiadm -m node
Configure Fibre Channel Target
1. Get HBA Port wwn for target and initiator VM:
NOTE. X – number of FC HBA.
2. Create block backstore for StarWind device:
backstores/block create dev=/dev/sdc name=test
3. Create a target with wwn = 5001438018756d08 (FC HBA wwn on the target machine)
/qla2xxx create naa.5001438018756d08
4. Create lun
/qla2xxx/naa.5001438018756d08/luns create /backstores/block/test
5. Create an ACL, with wwn = 21000024ff2f061e FC HBA wwn on the initiator machine)
6. Check the device connection on the initiator side.
Device can be formatted and used as a raw-block storage.