Problem connecting to remote target

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
morristownperson
Posts: 4
Joined: Sun Jun 12, 2011 9:16 pm

Sun Jun 12, 2011 9:20 pm

Server is in my Data Centre

ISCSI device behind firewall on FIOS. Port forwarding enabled


so the software initiator picks up the ISCSI targets name ( so it connects to x.y.z.222)

so the target name is XXXXXXXXX


but it will not connect . I think it is trying to use the internal IP address on remote lan (eg 192.168.x.x) which it cannot find

thanks
john
User avatar
anton (staff)
Site Admin
Posts: 4010
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Sun Jun 12, 2011 9:28 pm

Both size logs (initiator and target) are required to proceed.

P.S. And I'm not sure iSCSI is OK to work thru the NAT which TCP forwarding really is.
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
morristownperson
Posts: 4
Joined: Sun Jun 12, 2011 9:16 pm

Mon Jun 13, 2011 12:40 pm

yes i think you are correct
i attach the log from the windows server


what i did was
1. made sure the Target was NOT on remote lan
tried to connect , and could not pick up the remote target name
2. then made sure Target was ON remote lan

and now it can see the remote target name , but not connect as I think the local remote 192.x.x.x ip is not seen
and this is reflected in the error log as towards the end


I will try and dig up file from remote Device , but think I will try and OUTBOUND NAT on my Vyetta(if I can figure this out)



John
User avatar
anton (staff)
Site Admin
Posts: 4010
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Mon Jun 13, 2011 1:51 pm

Really sorry but no log attached :) Neither initiator nor target side.
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
morristownperson
Posts: 4
Joined: Sun Jun 12, 2011 9:16 pm

Mon Jun 13, 2011 2:39 pm

here is initiator log

the target device is a seagate black armour and I am struggling finding a lg

the problem is I cannot attach file. this system seems to dis allow all extension !!!


here is the bit where I have enabled the device and it has found the target , but then wont talk


i think you are correct for the NAT


Also the server is on my RS farm , so it has a PIX which we run through a CP


I can use the Vyetta at another of our farms

john


6/13 07:32:15.856 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:16.184 CStarPortAPI::InsertiSCSIDevice: Session failed, status == 121 !
6/13 07:32:16.184 >> CStarPortAPI::~CStarPortAPI()
6/13 07:32:16.184 CWPPiSCSITargetSelection::CreateDevice: Exception caught: The semaphore timeout period has expired.
6/13 07:32:16.184 CWPPiSCSITargetSelection::CreateDevice: Failed to connect to create iSCSI device using TargetName=iqn.1992-09.com.seagate:douglas1, IP:0xC0A8010C, Port:3260
6/13 07:32:16.184 CWPPiSCSITargetSelection::CreateDevice: Creation of the iSCSI device failed with all the addresses supplied by the server.
6/13 07:32:16.184 CWPPiSCSITargetSelection::CreateDevice: Exception caught: Creation of the iSCSI device failed with all the addresses
supplied by the server.
6/13 07:32:16.262 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:16.668 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:17.073 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:17.479 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:17.884 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:18.290 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:18.696 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:19.101 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:19.507 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:19.912 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:20.318 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
6/13 07:32:20.724 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
User avatar
anton (staff)
Site Admin
Posts: 4010
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Mon Jun 13, 2011 2:44 pm

Again nothing... Could you please zip it and send to support@starwindsoftware.com alias.

P.S. And give a try to MS initiator as well. Just in case (c) ...
morristownperson wrote:here is initiator log

the target device is a seagate black armour and I am struggling finding a lg
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
morristownperson
Posts: 4
Joined: Sun Jun 12, 2011 9:16 pm

Mon Jun 13, 2011 4:36 pm

thanks

have sent this and assigned case no 00004345
User avatar
anton (staff)
Site Admin
Posts: 4010
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Tue Jun 14, 2011 9:13 am

OK, let us check the logs before we'll go. Thank you!
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
Post Reply