>>> Charles DeVoe <cdevo...@nycap.rr.com> schrieb am 01.12.2011 um 21:53 in Nachricht <b0766ff2-4558-4619-91ee-cbd50e9da...@n35g2000yqf.googlegroups.com>: > I am now getting the target data > > [root@node1 ~]# iscsiadm -m discovery -t sendtargets -p > 172.16.1.200:3260 > 172.16.1.200:3260,1 iqn.2001-05.com.equallogic: > 0-8a0906-8eb96420a-186000000244e00b-volume1 > 172.16.1.200:3260,1 iqn.2001-05.com.equallogic: > 0-8a0906-91896420a-760000000274e00b-volume2 > 172.16.1.200:3260,1 iqn.2001-05.com.equallogic: > 0-8a0906-95696420a-5100000002a4e00b-volume3 > 172.16.1.200:3260,1 iqn.2001-05.com.equallogic: > 0-8a0906-98d96420a-9580000002d4e00b-volume4 > > However, when I do an fdisk -l the drives are not there. What am I > missing?
AFAIK, you see a target once you see "LUN 0" (the controllers). Maybe you forgot to export/present a LUN for that initiator? > > Using - iscsi-initiator-utils.x86_64 6.2.0.872-12.fc16 > > > > On Dec 1, 3:25 pm, Mike Christie <micha...@cs.wisc.edu> wrote: > > On 12/01/2011 09:30 AM, Charles DeVoe wrote: > > > > > This was a clean install. I went to F16 because F15 would not install > > > on the Dell servers for some reason. > > > > Ok. Make sure that new initiator name is in your target's ACLs if that > > is needed. Send me a tcpdump or wireshark trace of the discovery to make > > sure iscisadm is not messing something up. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
