Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 416
  • Last Modified:

iSCSI iniator

Hi,
I have a storage server which i connect my domain controller to using iSCSI. When i first set it up it all went smoothly but recently i have found iSCSI link dropping out. I can log back on to the target but the volumes do not appear exposed by the target. In the past a few reboots seem to have done the trick but that isnt really a very convenient solution. I know the initiator side is working correctly because that machine also connects to another iSCSI target.

I have reassigned the target to the virtual disk on the iSCSI software target and even used IP addresses instead of the IQN but still no difference.

Any suggestions gratefully received
0
chrisryan43
Asked:
chrisryan43
  • 6
  • 5
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Software iSCSI is dependent upon good networking, so it you are losing connection with the iSCSI target, do you have issues with the network interface in this computer?
0
 
chrisryan43Author Commented:
I believe the networking is good (they are physically located next to each other and go through the same switch, pinging reliably etc)

The reason the connection was lost was because the RAID array on the target fell over. HP believe it was a firmware issue on the controller which has now been updated so hopefully shouldnt happen again

I have since rebooted both machines once which didnt resolve the issue and because everything else is working fine i am reluctant to try any more reboots and cause further disruption to the users.

Do you have any other thoughts?

Thanks for your time on this
Chris
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Since you had difficulties, establishing this connection, after a storage outage, I would remove it, and setup again.

iSCSI connections, should re-connect correctly and establish themselves, if storage is available.
0
2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

 
Radhakrishnan RITCommented:
Hi,

This can be caused when the iSCSI initiator service is not started before the server service.

Is the server service started at the time of issue? if not, start it and see it appears fine. If it works, you need to add a multi-string value for iSCSI  as depends on service  in server service.
0
 
chrisryan43Author Commented:
Hi,
I had attempted to restart the service but still no joy but i  had some windows updates to apply so gave the server a restart and still nothing. I'm nervous about doing too much on the server side in case i inadvertently erase the RAID. I'm currently in the process of backing everything up elsewhere so that i can play a bit more
0
 
chrisryan43Author Commented:
Hi,

So this is where i am at.....

I created a new 'Test' virtual disk on the storage server and this then connected fine with the iSCSI initiator. So i then deleted the virtual disk for the one i am having issues with (just within iSCSI software target - not the .vhd file). I also deleted the cbm file just  in case it helped. I then reimported the vhd file back into the software target and it still wont be be seen by the iSCSI initiator. The virtual disk mounts locally fine so i am happy that the file system is  all ok. I am really starting to run out of ideas now
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I would escalate a support call to Microsoft on this issue.
0
 
chrisryan43Author Commented:
*UPDATE* - i just realised that i hadn't added the domain controller back as a device target after reimporting the virtual disk. I have now done it and all is  working. So the delete/import of  the virtual disk (and deleting the cbm file) seems to have fixed it.

Thanks for your time and suggestions on this
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Glad it's all working again.
0
 
chrisryan43Author Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for chrisryan43's comment #a39647452

for the following reason:

Closing the question
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If my Answers have aided you in this solution, please assign points.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
3. Accept http:#a39642022
0

Featured Post

Automating Your MSP Business

The road to profitability.
Delivering superior services is key to ensuring customer satisfaction and the consequent long-term relationships that enable MSPs to lock in predictable, recurring revenue. What's the best way to deliver superior service? One word: automation.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now