Problems creating bridged device

[rhs]

Hello,

i tried iStorage Server on Windows XP with Version 1.55 in trial mode. However when creating a bridged SCSI Tape
and using it under Suse Linux Enterprise 10 SP2 as initiator it will be displayed as normal disk drive (see picture).

Anybody has a hint what goes wrong here ?? Starwind did the job right, but unfortunately instable

Greetings
Ralf

[Aldrich]

It maybe a display problem in the management tool, is it also a disk drive in your Suse Linux Enterprise 10 SP2 ?

[rhs]

Unfortunately it is not only a management problem:

scsi0 : iSCSI Initiator over TCP/IP
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 00
sda : READ CAPACITY failed.
sda : status=1, message=00, host=0, driver=08
sd: Current: sense key: Illegal Request
Additional sense: Invalid command operation code
sda: Write Protect is on
sda: Mode Sense: 00 00 80 00
sda: cache data unavailable
sda: assuming drive cache: write through
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
Loading iSCSI transport class v2.0-724.
iscsi: registered transport (tcp)

Normally it should be showing up as a tape drive... but it shows up as a disk. And it's the same with Suse Linux Enterprise 11, it is not a specific version problem of Suse Linux Enterprise.

Any clues ?

Greetings
Ralf

[Aldrich]

We will test for this case, I will get back here soon...

[Aldrich]

After a day tested, unfortunately, we haven't reproducted the problem in our environment, it works in OpenSUSE 11 x86_86 version. But there is indeed a display problem in iStorage Server Management Console.

ec 27 07:53:10 linux-ej5e kernel: Loading iSCSI transport class v2.0-870.
Dec 27 07:53:10 linux-ej5e kernel: iscsi: registered transport (tcp)
Dec 27 07:53:10 linux-ej5e kernel: iscsi: registered transport (iser)
Dec 27 07:53:10 linux-ej5e iscsid: iSCSI logger with pid=6354 started!
Dec 27 07:53:11 linux-ej5e iscsid: transport class version 2.0-870. iscsid version 2.0-870
Dec 27 07:53:11 linux-ej5e iscsid: iSCSI daemon with pid=6356 started!
Dec 27 07:53:29 linux-ej5e kernel: scsi3 : iSCSI Initiator over TCP/IP
Dec 27 07:53:29 linux-ej5e kernel: scsi 3:0:0:0: Sequential-Access IBM ULT3580-TD4 5400 PQ: 0 ANSI: 5
Dec 27 07:53:29 linux-ej5e kernel: scsi 3:0:0:0: Attached scsi generic sg2 type 1
Dec 27 07:53:29 linux-ej5e kernel: st: Version 20080504, fixed bufsize 32768, s/g segs 256
Dec 27 07:53:29 linux-ej5e kernel: st 3:0:0:0: Attached scsi tape st0
Dec 27 07:53:29 linux-ej5e kernel: st 3:0:0:0: st0: try direct i/o: yes (alignment 1 B)
Dec 27 07:53:29 linux-ej5e kernel: osst :I: Tape driver with OnStream support version 0.99.4

It may be a compatibility issue with our product or the operation system, in order to better solve the problem, can you do me a faver and sent us a wireshark log (during the log on phase)?
You can download the free wireshark from http://www.wireshark.org, and send the log to [email protected]
thank you very much.