Date: Thu, 03 Jul 2014 17:06:29 -0300 From: =?ISO-8859-1?Q?=22F=E1bio_R=2E_Medeiros=22?= <fabior@unicamp.br> To: freebsd-net@freebsd.org Subject: [iSCSI] FreeBSD native iSCSI support don't mapping LUNs to /dev/ Message-ID: <53B5B7C5.5020004@unicamp.br>
next in thread | raw e-mail | index | archive | help
Hello there! I've got some difficult on mapping a iSCSI LUN to a /dev/xx device using the native iSCSI support on FreeBSD 10 (the iscsid and iscsictl). I using a Enhance UltraStor ES3160P4 <javascript:goHome()> storage device. I've a storage configured with one RAID0, one volume and some LUNs instances for test purposes. I can connect to storage, see the devices, but they are not mapped to LUNs into the system. Here are the issue: root@localhost:~ # iscsictl -A -p 192.168.100.100:3260 -t storage0:dev15.ctr1 -u test -s testteste12345 iscsictl: invalid iSCSI name "storage0:dev15.ctr1"; should start with either ".iqn", "eui.", or "naa." root@localhost:~ # iscsictl -L Target name Target portal State storage0:dev15.ctr1 192.168.100.100 Connected: root@localhost:~ # I now the name of storage device isn't configured as required, but I can't change it now (there are other services running on this storage). Could this be the root of the problem? --- The debug of iscsid shows all good. The last messages are these: iscsid: 192.168.100.100 (storage0:dev15.ctr1): parameter negotiation done; transitioning to Full Feature phase iscsid: 192.168.100.100 (storage0:dev15.ctr1): handing off connection to the kernel iscsid: 192.168.100.100 (storage0:dev15.ctr1): nothing more to do; exiting --- The FreeBSD handbook shows the LUN mapped to /dev/da0 device it's mapped: Target name Target portal Stateiqn.2012-06.com.example:target0 10.10.10.10 Connected: da0 Am I forgetting anything? -- Fábio Rocha Medeiros Administrador de Redes Instituto de Biologia - UNICAMP http://www.ib.unicamp.br
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53B5B7C5.5020004>