Multipath Configuration - Revision history

Qadmin: Rewrite from the product: correct multipath.conf example (product not model; regex not glob), replace the obsolete hand-edit procedure with QuantaStor's automatic configuration, document the Multi-path Device Configurator dialog, device naming and the encryption layer, INQUIRY MultiP detection, and shared-JBOD HA behaviour (QSTOR-12352)

2026-09-03T21:18:34Z

Rewrite from the product: correct multipath.conf example (product not model; regex not glob), replace the obsolete hand-edit procedure with QuantaStor's automatic configuration, document the Multi-path Device Configurator dialog, device naming and the encryption layer, INQUIRY MultiP detection, and shared-JBOD HA behaviour (QSTOR-12352)

Show changes

Qadmin: /* Configuring the /etc/multipath.conf File */

2019-05-30T20:07:51Z

Configuring the /etc/multipath.conf File

← Older revision		Revision as of 20:07, 30 May 2019
Line 6:		Line 6:
	For systems with SAS HBAs there are some additional steps required to setup the QuantaStor system for multipath access. Specifically, you must add entries to the /etc/multipath.conf file then restart the multipath services.		For systems with SAS HBAs there are some additional steps required to setup the QuantaStor system for multipath access. Specifically, you must add entries to the /etc/multipath.conf file then restart the multipath services.
	==== Configuring the /etc/multipath.conf File ====		==== Configuring the /etc/multipath.conf File ====
	QuantaStor ~~being~~ Linux based uses the DMMP (Device Mapper Multi-Path) driver to manage multipathing. The multipath service can be restarted at any time at the command line using the command 'service multipath-tools restart'. Configuration of this service is managed via the configuration file located at /etc/multipath.conf which contains a set of rules indicating which devices (identified by Vendor / Model) should be managed by the multipath service and which should be ignored. The base configuration is setup so that no multipath management is done for SAS devices as this is the most common and simplest configuration mode. To enable multipath management you must add a section to the 'blacklist_exceptions' area of the file indicating the vendor and model of your SAS devices. The vendor model information for your SAS devices can be found using this command 'grep Vendor /proc/scsi/scsi'. To summarize:		QuantaStor is Linux based and uses the DMMP (Device Mapper Multi-Path) driver to manage multipathing. The multipath service can be restarted at any time at the command line using the command 'service multipath-tools restart'. Configuration of this service is managed via the configuration file located at /etc/multipath.conf which contains a set of rules indicating which devices (identified by Vendor / Model) should be managed by the multipath service and which should be ignored. The base configuration is setup so that no multipath management is done for SAS devices as this is the most common and simplest configuration mode. To enable multipath management you must add a section to the 'blacklist_exceptions' area of the file indicating the vendor and model of your SAS devices. The vendor model information for your SAS devices can be found using this command 'grep Vendor /proc/scsi/scsi'. To summarize:

	* grep Vendor /proc/scsi/scsi		* grep Vendor /proc/scsi/scsi

Qadmin at 14:24, 17 April 2019

2019-04-17T14:24:39Z

← Older revision		Revision as of 14:24, 17 April 2019
Line 4:		Line 4:
	If you are using a RAID controller it will internally manage the multiple paths to the device automatically so there is no additional configuration required except to make sure that you have two cables connecting the controller to the SAS expander.		If you are using a RAID controller it will internally manage the multiple paths to the device automatically so there is no additional configuration required except to make sure that you have two cables connecting the controller to the SAS expander.
	=== Multi-path Configuration with HBAs ===		=== Multi-path Configuration with HBAs ===
	For ~~appliances~~ with SAS HBAs there are some additional steps required to setup the QuantaStor ~~appliance~~ for multipath access. Specifically, you must add entries to the /etc/multipath.conf file then restart the multipath services.		For systems with SAS HBAs there are some additional steps required to setup the QuantaStor system for multipath access. Specifically, you must add entries to the /etc/multipath.conf file then restart the multipath services.
	==== Configuring the /etc/multipath.conf File ====		==== Configuring the /etc/multipath.conf File ====
	QuantaStor being Linux based uses the DMMP (Device Mapper Multi-Path) driver to manage multipathing. The multipath service can be restarted at any time at the command line using the command 'service multipath-tools restart'. Configuration of this service is managed via the configuration file located at /etc/multipath.conf which contains a set of rules indicating which devices (identified by Vendor / Model) should be managed by the multipath service and which should be ignored. The base configuration is setup so that no multipath management is done for SAS devices as this is the most common and simplest configuration mode. To enable multipath management you must add a section to the 'blacklist_exceptions' area of the file indicating the vendor and model of your SAS devices. The vendor model information for your SAS devices can be found using this command 'grep Vendor /proc/scsi/scsi'. To summarize:		QuantaStor being Linux based uses the DMMP (Device Mapper Multi-Path) driver to manage multipathing. The multipath service can be restarted at any time at the command line using the command 'service multipath-tools restart'. Configuration of this service is managed via the configuration file located at /etc/multipath.conf which contains a set of rules indicating which devices (identified by Vendor / Model) should be managed by the multipath service and which should be ignored. The base configuration is setup so that no multipath management is done for SAS devices as this is the most common and simplest configuration mode. To enable multipath management you must add a section to the 'blacklist_exceptions' area of the file indicating the vendor and model of your SAS devices. The vendor model information for your SAS devices can be found using this command 'grep Vendor /proc/scsi/scsi'. To summarize:
Line 32:		Line 32:
	=== Troubleshooting Multipath Configurations ===		=== Troubleshooting Multipath Configurations ===
	* Only Single Path		* Only Single Path
	** If you only see one path to your device but the multipath driver is recognizing your device by displaying it in the output of 'multipath -ll' then you may have a cabling problem that is only providing the ~~appliance~~ with a single path to the device.		** If you only see one path to your device but the multipath driver is recognizing your device by displaying it in the output of 'multipath -ll' then you may have a cabling problem that is only providing the system with a single path to the device.
	* No Paths Appear		* No Paths Appear
	** If you don't see any devices in the output of 'multipath -ll' then there's probably something wrong with the device entry you added to the multipath.conf file into the blacklist_exceptions for your particular vendor/model of SAS device. Double check the output from 'cat /proc/scsi/scsi' to make sure that you have a correct rule added to the multipath.conf file.		** If you don't see any devices in the output of 'multipath -ll' then there's probably something wrong with the device entry you added to the multipath.conf file into the blacklist_exceptions for your particular vendor/model of SAS device. Double check the output from 'cat /proc/scsi/scsi' to make sure that you have a correct rule added to the multipath.conf file.

Qadmin at 02:19, 21 March 2019

2019-03-21T02:19:53Z

← Older revision		Revision as of 02:19, 21 March 2019
Line 1:		Line 1:
			[[Category:admin_guide]]
	If your storage system has multi-path capable (dual ported) SAS media connected via a SAS JBOD or internal SAS expander QuantaStor will try to automatically enable multipath support for your devices. Multipath devices appear in the system with the dm-uuid-mpath prefix. Multipathing improves redundancy, fault-tolerance and in some cases improves performance.		If your storage system has multi-path capable (dual ported) SAS media connected via a SAS JBOD or internal SAS expander QuantaStor will try to automatically enable multipath support for your devices. Multipath devices appear in the system with the dm-uuid-mpath prefix. Multipathing improves redundancy, fault-tolerance and in some cases improves performance.
	=== Multi-path Configuration with RAID Controllers ===		=== Multi-path Configuration with RAID Controllers ===

Qadmin: /* Internal SAS Device Multi-path Configuration */

2019-03-21T02:19:29Z

Internal SAS Device Multi-path Configuration

← Older revision		Revision as of 02:19, 21 March 2019
Line 1:		Line 1:
	~~== Internal SAS Device Multi-path Configuration ==~~
	If your ~~appliance is dual~~-path connected to a SAS JBOD or ~~has an~~ internal SAS expander with ~~SAS disks you have~~ the ~~option of setting up multiple paths to the SAS devices for~~ redundancy and in some cases ~~improved~~ performance~~. If you are not familiar with ZFS or using the Linux shell utilities we strongly recommend getting help with these steps from customer support~~.		If your storage system has multi-path capable (dual ported) SAS media connected via a SAS JBOD or internal SAS expander QuantaStor will try to automatically enable multipath support for your devices. Multipath devices appear in the system with the dm-uuid-mpath prefix. Multipathing improves redundancy, fault-tolerance and in some cases improves performance.
	=== Multi-path Configuration with RAID Controllers ===		=== Multi-path Configuration with RAID Controllers ===
	If you are using a RAID controller it will internally manage the multiple paths to the device automatically so there is no additional configuration required except to make sure that you have two cables connecting the controller to the SAS expander.		If you are using a RAID controller it will internally manage the multiple paths to the device automatically so there is no additional configuration required except to make sure that you have two cables connecting the controller to the SAS expander.

Qadmin: Created page with "== Internal SAS Device Multi-path Configuration == If your appliance is dual-path connected to a SAS JBOD or has an internal SAS expander with SAS disks you have the option of..."

2019-03-21T02:16:14Z

Created page with "== Internal SAS Device Multi-path Configuration == If your appliance is dual-path connected to a SAS JBOD or has an internal SAS expander with SAS disks you have the option of..."

New page

== Internal SAS Device Multi-path Configuration ==
If your appliance is dual-path connected to a SAS JBOD or has an internal SAS expander with SAS disks you have the option of setting up multiple paths to the SAS devices for redundancy and in some cases improved performance. If you are not familiar with ZFS or using the Linux shell utilities we strongly recommend getting help with these steps from customer support.
=== Multi-path Configuration with RAID Controllers ===
If you are using a RAID controller it will internally manage the multiple paths to the device automatically so there is no additional configuration required except to make sure that you have two cables connecting the controller to the SAS expander.
=== Multi-path Configuration with HBAs ===
For appliances with SAS HBAs there are some additional steps required to setup the QuantaStor appliance for multipath access. Specifically, you must add entries to the /etc/multipath.conf file then restart the multipath services.
==== Configuring the /etc/multipath.conf File ====
QuantaStor being Linux based uses the DMMP (Device Mapper Multi-Path) driver to manage multipathing. The multipath service can be restarted at any time at the command line using the command 'service multipath-tools restart'. Configuration of this service is managed via the configuration file located at /etc/multipath.conf which contains a set of rules indicating which devices (identified by Vendor / Model) should be managed by the multipath service and which should be ignored. The base configuration is setup so that no multipath management is done for SAS devices as this is the most common and simplest configuration mode. To enable multipath management you must add a section to the 'blacklist_exceptions' area of the file indicating the vendor and model of your SAS devices. The vendor model information for your SAS devices can be found using this command 'grep Vendor /proc/scsi/scsi'. To summarize:

* grep Vendor /proc/scsi/scsi
** Returns the vendor / model information for your SAS devices
* nano /etc/multipath.conf
** Add a section to the blacklist_exceptions area for your SAS device, example (note the use of a wildcard '*') :

device {
vendor "SEAGATE"
model "ST33000*"
}

* service multipath-tools restart
** Restarts the multipath service
* multipath -ll
** Shows your devices with multiple paths to them

=== Pool Configuration ===

Once all the above is done you'll need to go into the QuantaStor web management interface and choose 'Scan for Disks' to make the new device mapper paths appear. If you have already created a storage pool using standard paths rather than the /dev/mapper/mpath* paths then you'll need to run a zpool export/import operation to re-import the pool using the device mapper paths. To do this you will need to first do a 'Stop Storage Pool' then at the command line / console you'll need to run these commands:
* zpool export qs-POOLID
* zpool import -d /dev/mapper qs-POOLID
Note that you must replace qs-POOLID with the actual ID of the storage pool. You can also get this ID by running the 'zpool status' command.

=== Troubleshooting Multipath Configurations ===
* Only Single Path
** If you only see one path to your device but the multipath driver is recognizing your device by displaying it in the output of 'multipath -ll' then you may have a cabling problem that is only providing the appliance with a single path to the device.
* No Paths Appear
** If you don't see any devices in the output of 'multipath -ll' then there's probably something wrong with the device entry you added to the multipath.conf file into the blacklist_exceptions for your particular vendor/model of SAS device. Double check the output from 'cat /proc/scsi/scsi' to make sure that you have a correct rule added to the multipath.conf file.