cant connect to Sun Storage 7000

Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics), iSCSI accelerator and RAM disk

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
nazarianin
Posts: 5
Joined: Sun Apr 25, 2010 1:31 pm

Mon Apr 26, 2010 8:34 am

Hello all
I use Starport 5.5 on Windows 7. I have error when connect to Sun Storage 7000 running in VirtualBox. Error "Failed to connect to remote server. Server may be refused network conections. You may need to check firewall settings". I also try in XP and have error too. I send logs to support, they replied that I wrote here. Microsoft initiator work good.
Constantin (staff)

Mon Apr 26, 2010 8:59 am

iSCSI initiator requires port 3260 to be open. MS iSCSI Initiator creates such rule in firewall for itself during first run. Try to create another one rule specially for StarPort.
nazarianin
Posts: 5
Joined: Sun Apr 25, 2010 1:31 pm

Mon Apr 26, 2010 9:55 am

I turned off firewall. I try coonect with telnet to port 3260 , it work fine.
I have this in starport log file
4/26 15:53:50.546 >> CStarPortAPI::GetTargets(dwIPAddress=0xC0A8C82D, DWORD dwPort=3260, listTargets=...)
4/26 15:53:50.552 CStarPortAPI::GetTargets: Calling STARPORT_IOCTL_GET_TARGETS
4/26 15:53:50.556 CStarPortAPI::GetTargets: Input buffer:
4/26 15:53:50.561 CStarPortAPI::GetTargets: ServerAddress = #iscsi:192.168.200.45:3260
4/26 15:53:50.566 CStarPortAPI::GetTargets: Parameter[0] = InitiatorName=iqn.2003-06.com.starwindsoftware.starport:pc03
4/26 15:53:50.577 CStarPortAPI::GetTargets: Session failed, status == 31 !
4/26 15:53:50.579 CWPPiSCSIDeviceCreate::GetTargetsList: Exception caught: Driver failure.
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Fri Apr 30, 2010 8:40 am

Is there any way for you to catch Sun-side logs or run Wireshark on the Windows box to capture network traffic for us?
nazarianin wrote:I turned off firewall. I try coonect with telnet to port 3260 , it work fine.
I have this in starport log file
4/26 15:53:50.546 >> CStarPortAPI::GetTargets(dwIPAddress=0xC0A8C82D, DWORD dwPort=3260, listTargets=...)
4/26 15:53:50.552 CStarPortAPI::GetTargets: Calling STARPORT_IOCTL_GET_TARGETS
4/26 15:53:50.556 CStarPortAPI::GetTargets: Input buffer:
4/26 15:53:50.561 CStarPortAPI::GetTargets: ServerAddress = #iscsi:192.168.200.45:3260
4/26 15:53:50.566 CStarPortAPI::GetTargets: Parameter[0] = InitiatorName=iqn.2003-06.com.starwindsoftware.starport:pc03
4/26 15:53:50.577 CStarPortAPI::GetTargets: Session failed, status == 31 !
4/26 15:53:50.579 CWPPiSCSIDeviceCreate::GetTargetsList: Exception caught: Driver failure.
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
nazarianin
Posts: 5
Joined: Sun Apr 25, 2010 1:31 pm

Tue May 04, 2010 9:28 am

see log1.txt in log1.zip. This is wireshark log filter for port 3260. 192.168.56.1 - my system with windows 7 x32, 192.168.56.2 - remote Sun storage 7000 in virtualbox.
Attachments
log1.zip
(6.96 KiB) Downloaded 837 times
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Tue May 04, 2010 10:26 am

Got the logs, checking what's wrong. We'll keep you updated as soon as we'll have developer's feedback. Thank you!
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
Val (staff)
Posts: 496
Joined: Tue Jun 29, 2004 8:38 pm

Tue May 04, 2010 10:36 am

nazarianin wrote:see log1.txt in log1.zip. This is wireshark log filter for port 3260. 192.168.56.1 - my system with windows 7 x32, 192.168.56.2 - remote Sun storage 7000 in virtualbox.
Hi,

Could you upload the logs in the pcap format?

Thank you in advance.
Best regards,
Valeriy
nazarianin
Posts: 5
Joined: Sun Apr 25, 2010 1:31 pm

Tue May 04, 2010 11:49 am

Val (staff) wrote:Could you upload the logs in the pcap format?
yes, of course.
Attachments
log2.zip
(1.59 KiB) Downloaded 807 times
Val (staff)
Posts: 496
Joined: Tue Jun 29, 2004 8:38 pm

Tue May 04, 2010 3:31 pm

Thank you!

From the last log I saw that StarPort repeatedly tried to negotiate its DefaultTime2Wait=5, but the target each time answered with DefaultTime2Wait=2 and so on until StarPort given up its attempts.

According to the iSCSI specs the DefaultTime2Wait is a "max number value", so the target must use the value proposed by the initiator (5) in its replies.
It looks like the target's implementation of the iSCSI specs is not correct.

Is there any way to set the DefaultTime2Wait=5 on the target side?
This should solve the problem...
Best regards,
Valeriy
Post Reply