Hello Roland, Thank you for you reply. By "_" i realy means "_" and not spaces and thats the problem. We are using FalconStor NSS cluster and there is setup file for alua storages where you must put this ID, but it cant contains _ char. I see SCST like this: Hardware ID "SCST_BIOssd01-cnc -ff0f49e4-6666306634396534-00" Hardware ID "SCST_BIOssd02-cnc -cbb3823e-6362623338323365-01" Etc.. When i use same T10 and LIO, its looks like this: Hardware ID "LIO-ORG_IBLOCK_________-ff0f49e4-6666306634396534-00" Hardware ID "LIO-ORG_IBLOCK_________-cbb3823e-6362623338323365-01" Each LUN looks same. In falconstor you editing file certified_alua_storage.conf to have fully supported ALUA storage and there you put Line like this: LIO-ORG_IBLOCK_________ FalconStor support said its problem of _ at the end. But it can be also bad setup of ALUA also. But in Win2k8 R8, Linux or esxi LIO target works Ok and with round robin multipath. In falconstor it said it doesnt support this feature and it use only one path Active, all others passive/stand by. Can you check it my settings are correct? #### ALUA Logical Unit Groups #### Parameters for TCM subsystem plugin storage object reference tcm_node --establishdev iblock_0/LSC-Veeam /dev/archive-lsc/FCoE-LSC-Veeam tcm_node --setunitserialwithmd iblock_0/LSC-Veeam 8efae176-a87f-4fff-ab5f-6c450e0ab6cd #### ALUA Target Port Groups tcm_node --addaluatpgwithmd iblock_0/LSC-Veeam default_tg_pt_gp 0 echo 3 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/alua/default_tg_pt_gp/alua _access_type echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/alua/default_tg_pt_gp/pref erred echo 100 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/alua/default_tg_pt_gp/nono p_delay_msecs echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/alua/default_tg_pt_gp/tran s_delay_msecs #### Attributes for /sys/kernel/config/target/core/iblock_0/LSC-Veeam echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/unmap_granularity_a lignment echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/unmap_granularity echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/max_unmap_block_des c_count echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/max_unmap_lba_count echo 128 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/queue_depth echo 640 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/optimal_sectors echo 8192 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/fabric_max_sectors echo 512 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/block_size echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/emulate_rest_reord echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/is_nonrot echo 1 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/enforce_pr_isids echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/emulate_tpws echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/emulate_tpu echo 1 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/emulate_tas echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/emulate_ua_intlck_c trl echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/emulate_write_cache echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/emulate_fua_read echo 1 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/emulate_fua_write echo 0 > /sys/kernel/config/target/core/iblock_0/LSC-Veeam/attrib/emulate_dpo And also iam not good in programming, maybe can you tell in which file to look for changing this settings? Thanks a lot for your help S pozdravom / Best regards Tomas Molota Chief Technology Officer Parickova 18, 821 08 Bratislava, Slovakia e-mail: tomas.molota@xxxxxxxxxxxxx web: www.lightstorm.sk phone: +421 2 32 400 011 cell phone: +421 903 788 100 -----Original Message----- From: Roland Dreier [mailto:roland@xxxxxxxxxxxxxxx] Sent: Wednesday, July 24, 2013 6:37 PM To: Tomas Molota Cc: target-devel Subject: Re: FCoE Target naming - help On Wed, Jul 24, 2013 at 8:11 AM, Tomas Molota <tomas.molota@xxxxxxxxxxxxx> wrote: > Hello, iam trying to use LIO as FCoE ALUA target and i have problem > with naming which LIO shows to initiators. What i see: > Vendor ID : LIO-ORG_ > Product ID: IBLOCK__________ > And our system has problem with "_" which are not allowed as name of > storage and its shows me error with this LUN as not supported device. > Is it possible somehow to change this option? Do you mean spaces where you write "_"? What do mean by "show to initiators"? If you mean the data in the INQUIRY response, then that's what the SCSI spec mandates. In SPC-4, for example, the vendor field is specified as: "The T10 VENDOR IDENTIFICATION field contains eight bytes of left-aligned ASCII data (see 4.3.1) identifying the vendor of the logical unit." where 4.3.1 says: "ASCII data fields described as being left-aligned shall have any unused bytes at the end of the field (i.e., highest offset) and the unused bytes shall be filled with ASCII space characters (20h)." Similarly for the product id fields. so according to the SCSI standards, padding those fields with spaces is required. What is you system that doesn't accept that? In any case if you want to experiment it is pretty easy to edit the source to change those strings. - R. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
