Has anyone experienced this error? I have no firewall, no SELinux
running, etc. The iSCSI target should be fine as windows clients were
able to utilize the sanfly targets before (or ones like it).
Is there a howto or directions I can follow? Can I not do a discovery
and just connect to it
Regarding MujZeptu's post on the unexpected opcode, we have identified an
issue with sanFly when using open-iscsi in discovery sessions. This was not
seen in testing with other iSCSI initiators. A patch for sanFly will be
released once tested in-house.
Steve Marfisi
emBoot Inc.
On Wed, May 28, 2008 at 09:56:38AM -0700, [EMAIL PROTECTED] wrote:
Has anyone experienced this error? I have no firewall, no SELinux
running, etc. The iSCSI target should be fine as windows clients were
able to utilize the sanfly targets before (or ones like it).
Well, the error is just
[EMAIL PROTECTED] wrote:
As the title says, I get this error when I try to find iscsi targets.
I cannot for the life of me get open-iscsi to work and always get this
error. I am trying to connect to a working sanfly iscsi target from
either RHEL 5.1 client or the latest ubuntu.
What
As the title says, I get this error when I try to find iscsi targets.
I cannot for the life of me get open-iscsi to work and always get this
error. I am trying to connect to a working sanfly iscsi target from
either RHEL 5.1 client or the latest ubuntu.
