Software-based VM-centric and flash-friendly VM storage + free version
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
-
atonti
- Posts: 2
- Joined: Mon Sep 06, 2010 1:31 pm
Mon Sep 06, 2010 1:58 pm
Hello
I just downloaded the free trial of StarWind for testing.
My configuration is:
- StarWind installed on a Win2008 server VM hosted on VMware server 2.0.
- Solaris 10 iSCSI initiator on another VM on the same VMware server.
I' m using SendTargets device discovery method in my Solaris VM, but I can't see the targets.
The logs on /var/adm/messages on Solaris shows:
iscsi: [ID 867852 kern.warning] WARNING: iscsi connection(12) protocol error - received an unsupported opcode:0x1b
iscsi: [ID 158826 kern.warning] WARNING: iscsi connection(12) login failed - failed to receive login response
I' m able to telnet the StarWind San without any problem:
telnet 172.16.20.130 3261
Trying 172.16.20.130...
Connected to 172.16.20.130.
Escape character is '^]'.
StarWind iSCSI SAN Software v5.4.0 (Build 20100805, [SwSAN], Win64)
Copyright (c) StarWind Software 2003-2010. All rights reserved.
Could be a incompatibility between the Solaris iSCSI initiator and StarWind software protocol implementations ?
Regards
-
anton (staff)
- Site Admin
- Posts: 4021
- Joined: Fri Jun 18, 2004 12:03 am
- Location: British Virgin Islands
-
Contact:
Mon Sep 06, 2010 7:07 pm
Could be... Please provide StarWind log from the Windows box (and be ready to send Wireshark log on request as well). In this case we'd be ready to solve the issue pretty fast... Thanks!
Regards,
Anton Kolomyeytsev
Chief Technology Officer & Chief Architect, StarWind Software
-
atonti
- Posts: 2
- Joined: Mon Sep 06, 2010 1:31 pm
Mon Sep 06, 2010 8:24 pm
anton (staff) wrote:Could be... Please provide StarWind log from the Windows box (and be ready to send Wireshark log on request as well). In this case we'd be ready to solve the issue pretty fast... Thanks!
Anton
Thank you very much for your quick answer.
I discovered that the port on the initiator had to be 3260 an not 3261 !
Now is working fine.
Regards
Andrès
-
anton (staff)
- Site Admin
- Posts: 4021
- Joined: Fri Jun 18, 2004 12:03 am
- Location: British Virgin Islands
-
Contact:
Tue Sep 07, 2010 10:27 am
LOL
Nice to know it's THAT simple and you're fine now
Thanks!
atonti wrote:anton (staff) wrote:Could be... Please provide StarWind log from the Windows box (and be ready to send Wireshark log on request as well). In this case we'd be ready to solve the issue pretty fast... Thanks!
Anton
Thank you very much for your quick answer.
I discovered that the port on the initiator had to be 3260 an not 3261 !
Now is working fine.
Regards
Andrès
Regards,
Anton Kolomyeytsev
Chief Technology Officer & Chief Architect, StarWind Software
