Un saludo. David Ruiz Estefanía Administrador de Sistemas Centro de Alta Disponibilidad Correo: cad.ext@xxxxxxxxxxxxx Teléfono: 941 298 000 - Ext. 84743 Móvil: +34 669 432 808 > -----Mensaje original----- > De: Nicholas A. Bellinger [mailto:nab@xxxxxxxxxxxxxxx] > Enviado el: jueves, 22 de agosto de 2013 19:57 > Para: CAD > CC: Fernando Arconada Oróstegui; target-devel > Asunto: Re: LIO FC Target > > On Wed, 2013-08-21 at 08:05 +0000, CAD wrote: > > Hi. > > > > I'm Fernando's coworker who's trying to configure the Windows server > > to work with LIO disks. > > > > Hi David, > > Re-adding the list CC', and it's likely something that other folks have > having a problem with as well. > > Comments are below. > > > We already tried all the mpclaim and MPIO configurations at MSDN (and > > other web that we googled) before asking. > > > > We have a Windows Server 2012 Standard with a LIO disk presented. The > > disk it's shown as two different disks, one online and the other > > offline, as you can see on screen capture I've attached > > "disknomultipath.png". But this is the expected behavior as multipath > > it's not configured. > > > > When we try to execute mpclaim commands, this is the results we obtain: > > C:\Users\Administrator>mpclaim -v mpclaim.txt > > C:\Users\Administrator>type mpclaim.txt > > > > MPIO Storage Snapshot on Wednesday, 21 August 2013, at 08:51:22.714 > > > > Registered DSMs: 1 > > ================ > > +--------------------------------|--------------------|----|----|---- > |---|-----+ > > |DSM Name | Version |PRP | RC | RI > |PVP| PVE | > > |--------------------------------|--------------------|----|----|---- > |---|-----| > > |Microsoft DSM > |006.0002.09200.16384|0020|0003|0001|030|False| > > +--------------------------------|--------------------|----|----|---- > |---|-----+ > > > > > > Microsoft DSM > > ============= > > No devices controlled by this DSM at this time! > > > > > > > > MSDSM-wide default load balance policy: N\A > > > > No target-level default load balance policies have been set. > > > > > ====================================================================== > ========== > > > > C:\Users\Administrator>mpclaim -e > > > > "Target H/W Identifier " Bus Type MPIO-ed ALUA Support > > ---------------------------------------------------------------------- > --------- > > "LIO-ORG " Fibre NO Implicit and > Explicit > > > > > ====================================================================== > ========== > > > > C:\Users\Administrator>mpclaim -s -d > > > > No MPIO disks are present. > > > > > ====================================================================== > ========== > > > > So, we tried to configure the MPIO using the gui administration, so we > > opened the "MPIO Properties". In the "MPIO Devices" tab the "Device > > Hardware Id" list was empty, but in the "Discover Multi-Paths" tab the > > "SPC-3 compliant" "Device hardware list" shows a "LIO-ORG" device. We > > tried to add manually a "MPIO device" for LIO disks with the above > > target identifier, but after a reboot the system still shows two disks > > and not only one as expected. > > > > Thanks for the detailed report, and verifying this piece. > > One immediate thing that could be having an effect here is a bug that > was fixed wrt to the INQUIRY vendor+model strings, for which the empty > spaces at the end of the string where not being filled with ASCII space > characters. > > This was causing another multipath stack to have problems (FalconStor), > so I'm wondering if the same issue may be at work here as well..? > > The patch is currently in target-pending.git/master here, and will be > heading to v3.11-rc7 shortly. > > target: Fix trailing ASCII space usage in INQUIRY vendor+model > https://git.kernel.org/cgit/linux/kernel/git/nab/target- > pending.git/patch/?id=ee60bddba5a5f23e39598195d944aa0eb2d455e5 > > Would it be possible for you to test this patch against your MSFT FC > MPIO client setup..? > > > At this point, we tried several things (like undoing a redoing the > > manual configuration with other parameters), but it didn't work at > > all. > > > > That's why we think that there's some DSM driver related problem with > > LIO disks, because we've noticed that a DSM driver it's installed when > > multipath on other SAN server (HP EVA, 3PAR, NetApp, etc) it's used. > > > > Thanks for confirming that as well. > > --nab > > > I'm going to put here the LIO configuration too, just in case the > > problem it's on the LIO side (I don't think so as the multipath worked > > like a charm on ESXi host, but just in case): > > [root@azrael ~]# cat /etc/centos-release > > CentOS release 6.4 (Final) > > [root@azrael ~]# uname -a > > Linux azrael.larioja.org 3.10.5-1.el6.elrepo.x86_64 #1 SMP Sun Aug 4 > 13:26:20 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux > > [root@azrael ~]# lsmod > > Module Size Used by > > tcm_qla2xxx 25649 13 > > autofs4 32659 3 > > iscsi_target_mod 230634 1 > > qla2xxx 530836 1 tcm_qla2xxx > > target_core_iblock 17592 2 > > target_core_file 13295 0 > > target_core_pscsi 17539 0 > > target_core_mod 239947 27 > tcm_qla2xxx,iscsi_target_mod,target_core_iblock,target_core_file,target_core_ > pscsi > > configfs 30974 3 iscsi_target_mod,target_core_mod > > bnx2fc 98857 0 > > cnic 64023 1 bnx2fc > > 8021q 24297 0 > > uio 19286 1 cnic > > garp 14313 1 8021q > > fcoe 27778 0 > > stp 12976 1 garp > > libfcoe 59333 2 bnx2fc,fcoe > > llc 14552 2 garp,stp > > libfc 117983 3 bnx2fc,fcoe,libfcoe > > sunrpc 241588 1 > > p4_clockmod 29397 0 > > freq_table 14264 1 p4_clockmod > > speedstep_lib 13095 1 p4_clockmod > > ipt_REJECT 12576 2 > > nf_conntrack_ipv4 19787 2 > > nf_defrag_ipv4 12729 1 nf_conntrack_ipv4 > > iptable_filter 12810 1 > > ip_tables 27263 1 iptable_filter > > ip6t_REJECT 12609 2 > > nf_conntrack_ipv6 18380 2 > > nf_defrag_ipv6 33794 1 nf_conntrack_ipv6 > > xt_state 12578 4 > > nf_conntrack 95633 3 > nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state > > ip6table_filter 12815 1 > > ip6_tables 27293 1 ip6table_filter > > ipv6 361012 44 > cnic,ip6t_REJECT,nf_conntrack_ipv6,nf_defrag_ipv6 > > iTCO_wdt 13521 0 > > iTCO_vendor_support 13718 1 iTCO_wdt > > gpio_ich 13419 0 > > ipmi_si 53639 0 > > ipmi_msghandler 45945 1 ipmi_si > > hpilo 17464 0 > > hpwdt 14178 0 > > bnx2 85392 0 > > coretemp 13603 0 > > kvm 430632 0 > > microcode 117144 0 > > serio_raw 13253 0 > > pcspkr 12718 0 > > sg 36725 0 > > lpc_ich 17060 0 > > i5k_amb 13189 0 > > i5000_edac 17542 0 > > edac_core 62509 2 i5000_edac > > shpchp 37141 0 > > ext4 523289 2 > > jbd2 112720 1 ext4 > > mbcache 14855 1 ext4 > > sr_mod 22520 0 > > cdrom 47420 1 sr_mod > > pata_acpi 13038 0 > > ata_generic 12910 0 > > ata_piix 35165 0 > > hpsa 63752 0 > > cciss 114448 4 > > scsi_transport_fc 64202 5 tcm_qla2xxx,qla2xxx,bnx2fc,fcoe,libfc > > scsi_tgt 19987 1 scsi_transport_fc > > radeon 868741 1 > > ttm 88394 1 radeon > > drm_kms_helper 44288 1 radeon > > hwmon 12967 3 coretemp,i5k_amb,radeon > > dm_mirror 22147 0 > > dm_region_hash 20848 1 dm_mirror > > dm_log 18481 2 dm_mirror,dm_region_hash > > dm_mod 89073 14 dm_mirror,dm_log > > [root@azrael ~]# targetcli > > targetcli shell version v2.1.fb28 > > Copyright 2011-2013 by Datera, Inc and others. > > For help on commands, type 'help'. > > > > /> ls > > o- / > ............................................................................. > ............................................ [...] > > o- backstores > ............................................................................. > ................................. [...] > > | o- block > ............................................................................. > ..................... [Storage Objects: 2] > > | | o- disco1 > ......................................................... > [/dev/vg_datos1/lv_prueba1 (10.0GiB) write-thru activated] > > | | o- disco2 > ......................................................... > [/dev/vg_datos1/lv_prueba2 (20.0GiB) write-thru activated] > > | o- fileio > ............................................................................. > .................... [Storage Objects: 0] > > | o- pscsi > ............................................................................. > ..................... [Storage Objects: 0] > > | o- ramdisk > ............................................................................. > ................... [Storage Objects: 0] > > o- iscsi > ............................................................................. > ............................... [Targets: 0] > > o- loopback > ............................................................................. > ............................ [Targets: 0] > > o- qla2xxx > ............................................................................. > ............................. [Targets: 2] > > | o- naa.2100001b321269e8 > ............................................................................. > ................ [gen-acls] > > | | o- acls > ............................................................................. > ............................... [ACLs: 1] > > | | | o- naa.500110a000195932 > ............................................................................. > ...... [Mapped LUNs: 1] > > | | | o- mapped_lun0 > ............................................................................. > ..... [lun0 block/disco1 (rw)] > > | | o- luns > ............................................................................. > ............................... [LUNs: 2] > > | | o- lun0 > ......................................................................... > [block/disco1 (/dev/vg_datos1/lv_prueba1)] > > | | o- lun1 > ......................................................................... > [block/disco2 (/dev/vg_datos1/lv_prueba2)] > > | o- naa.2100001b321280dd > ............................................................................. > ................ [gen-acls] > > | o- acls > ............................................................................. > ............................... [ACLs: 1] > > | | o- naa.500110a000195930 > ............................................................................. > ...... [Mapped LUNs: 1] > > | | o- mapped_lun0 > ............................................................................. > ..... [lun0 block/disco1 (rw)] > > | o- luns > ............................................................................. > ............................... [LUNs: 2] > > | o- lun0 > ......................................................................... > [block/disco1 (/dev/vg_datos1/lv_prueba1)] > > | o- lun1 > ......................................................................... > [block/disco2 (/dev/vg_datos1/lv_prueba2)] > > o- vhost > ............................................................................. > ............................... [Targets: 0] > > /> exit > > Global pref auto_save_on_exit=true > > Last 10 configs saved in /etc/target/backup. > > Configuration saved to /etc/target/saveconfig.json > > > > Thanks in advanced. > > > > David Ruiz Estefanía > > Administrador de Sistemas > > Centro de Alta Disponibilidad > > > > Correo: cad.ext@xxxxxxxxxxxxx > > Teléfono: 941 298 000 - Ext. 84743 > > Móvil: +34 669 432 808 > > > > > ________________________________________ > > > De: Nicholas A. Bellinger [nab@xxxxxxxxxxxxxxx] > > > Enviado el: lunes, 19 de agosto de 2013 22:36 > > > Para: Fernando Arconada Oróstegui > > > Cc: target-devel > > > Asunto: Re: LIO FC Target > > > > > > Hi Fernando, > > > > > > (Adding a CC' to target-devel) > > > > > > On Mon, 2013-08-19 at 11:05 +0000, Fernando Arconada Oróstegui wrote: > > > > Hello > > > > > > > > I'm considering to serve a FC LUN via LIO driver to be consummed with > > > > a Windows 2008/2012 Server. Do I need to load any kind of driver to > > > > enable the multipath on Windows? I've tried it but W2K8/12 only > > > > manages one path. > > > > I have read the RTS-OS Administrator's manual v3.6 pag, 79 13.1 said > > > > "Instructions for Fibre Channel and Infiniband will be added in the > > > > future" > > > > > > Yes, I believe you need to install a separate MPIO driver as described > > > here: > > > > > > http://technet.microsoft.com/en-us/library/ee619752%28v=ws.10%29.aspx > > > > > > and here: > > > > > > http://technet.microsoft.com/en-us/library/ee619778%28WS.10%29.aspx > > > > > > Also, I seem to recall that you'll need to mpclaim to determine the > > > LIO-ORG vendor ID (VID) and product ID (PID) for adding to the Add > > > Devices tab under MPIO Devices. > > > > > > Please let the list know your progress following the above instructions, > > > as I'd like to include this onto the wiki. > > > > > > Thanks, > > > > > > --nab > > > > > > > > > > > > ________________________________ > > > > > > GOBIERNO DE LA RIOJA > > > AVISO LEGAL: La información contenida en este mensaje es confidencial y > está > > > destinada a ser leída sólo por la persona a la que va dirigida. Si Ud. no > es > > > el destinatario señalado le informamos que está prohibida, y puede ser > > > ilegal, cualquier divulgación o reproducción de este mensaje. > > > Antes de imprimir este e-mail piense bien si es necesario hacerlo. > > > > ________________________________________ > > > > GOBIERNO DE LA RIOJA > > AVISO LEGAL: La información contenida en este mensaje es confidencial y > está destinada a ser leída sólo por la persona a la que va dirigida. Si Ud. > no es el destinatario señalado le informamos que está prohibida, y puede ser > ilegal, cualquier divulgación o reproducción de este mensaje. > > Antes de imprimir este e-mail piense bien si es necesario hacerlo. > ________________________________ GOBIERNO DE LA RIOJA AVISO LEGAL: La información contenida en este mensaje es confidencial y está destinada a ser leída sólo por la persona a la que va dirigida. Si Ud. no es el destinatario señalado le informamos que está prohibida, y puede ser ilegal, cualquier divulgación o reproducción de este mensaje. Antes de imprimir este e-mail piense bien si es necesario hacerlo. ��.n��������+%������w��{.n����j� ����{ay� ʇڙ���f���h������_�(�階�ݢj"��������G����?���&��
