Page 1 of 1

Clustered storage is not connected to the node

Posted: Tue Aug 13, 2019 12:51 am
by InphinitePhractals
Hi,

I recently attempted to apply CHAP using this as a guide:

https://www.starwindsoftware.com/resour ... tocol-chap

I applied it only at the server level, from what I read, thinking that applying it to CSV or HAImage# was only needed if you wanted to apply it more granularly. Turns out that wasn't the case when the disks became desynchronized. I then applied it at the HAImage level and the Witness and CSVs did a full resync.

While everything seems to be okay in StarWind again, all my CSVs and Witness show as Offline. Attempting to bring them back online returns the messages, "Failed to bring the resource 'WITNESS' online." and "Clustered storage is not connected to the node."

Please advise. Thank you.

-IP

Re: Clustered storage is not connected to the node

Posted: Thu Aug 15, 2019 10:31 pm
by InphinitePhractals
This is resolved.

I had to apply the credentials to each of the Targets in the iSCSI Initiator, as laid out in the "Configuring CHAP in Hyper-V" section here:

https://www.starwindsoftware.com/blog/s ... n-protocol

Re: Clustered storage is not connected to the node

Posted: Fri Aug 16, 2019 5:02 pm
by Michael (staff)
Thank you for the update.
Glad to know that our documentation helped you with the issue resolution.