[iscsictl] connection to invalid target

[Edward Tomasz Napierała]

On 0701T1527, RA H wrote:
> Thanks for the suggestion. Based on the debug log it looked like the
> problem was with the SAN, and in fact it is. Apparently it's not considered
> a pressing issue because most initiators will only attempt to connect to
> targets returned by a discovery session...

So basically it's not a FreeBSD bug?

> I'm using another workaround for the target validation which works fine,
> but it's more complicated than my initial plan, nevermind simply parsing
> the output of a discovery session eg. "iscontrol -dt <target address>".
> Since I have your attention, is there any chance of such a thing being
> implemented with iscsictl?

The problem here is that the discovery is performed by iscsid; the way
to implement it would be to make iscsictl add the discovery session, wait
for iscsid to finish discovery but not connect to the targets, report
targets, and then remove them.  So basically pretty much what you are
doing anyway.

> Thanks again.
> 
> On Tue, Jun 30, 2015 at 3:45 PM, Edward Tomasz Napierała <trasz at freebsd.org>
> wrote:
> 
> > On 0629T1458, RA H wrote:
> > > I have a SAN with four iSCSI targets,
> > > eui.000B56007135B1B0 through eui.000B56007135B1B3
> > >
> > > I need to validate target names entered manually by a user.
> > > Normally, I would do this is by searching the output of a discovery
> > > session. Since iscsictl doesn't allow doing discovery *only*, the only
> > > way I can think of to validate a target is to connect, then parse the
> > > output of "iscsictl -L". Unfortunately, attempting to connect to certain
> > > invalid targets results in connection to a valid target:
> > >
> > > # iscsictl -Ad 192.168.3.111
> > > # iscsictl -L
> > > Target name                          Target portal    State
> > > eui.000B56007135B1B0                 192.168.3.111    Connected: da0
> > > eui.000B56007135B1B1                 192.168.3.111    Connected: da2
> > > eui.000B56007135B1B2                 192.168.3.111    Connected: da1
> > > eui.000B56007135B1B3                 192.168.3.111    Connected: da3
> > > # iscsictl -Ra
> > > # iscsictl -A -p 192.168.3.111 -t eui.000B56007135B1A1
> > > # iscsictl -L
> > > Target name                          Target portal    State
> > > eui.000B56007135B1A1                 192.168.3.111    Connected: da0
> > > # dmesg
> > > ...
> > > da0: Serial Number 000B56007135B1B10000
> > > ...
> > >
> > > As the Serial Number indicates, iscsictl actually connected to
> > > target eui.000B56007135B1B1.
> >
> > That's weird.  Could you paste the iscsid debug log when this happens?
> > (Basically do "pkill iscsid; while :; do iscsid -d; done" in a separate
> > shell and capture the output).
> >
> >
> _______________________________________________
> freebsd-scsi at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe at freebsd.org"