Cant connect to Server

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
Mareo
Posts: 18
Joined: Tue May 21, 2024 11:35 am

Mon Nov 04, 2024 12:13 pm

Hello all,

I am writing this cause I've hit a dead end.

I've come across an issue which I can't resolve for the past few weeks. The whole thing is operational and all so I can't devote my time to tinker on production server, etc.

In the picture below, you will see that I can't connect to the other server and same thing is with that other server. They are connected to themselves, but I cannot establish a connection between them. iSCSI targets are connected(can provide a pic if necessary), but I would like to reconnect them but I am not sure how and where to begin with or what would be the issue so I quite don't know where to start.

Image

Thanks in advance, and I remain at your full disposal if you have further questions.

Kind regards,
Mario
yaroslav (staff)
Staff
Posts: 3424
Joined: Mon Nov 18, 2019 11:11 am

Mon Nov 04, 2024 12:27 pm

Hi,

Try removing that server from the management console and try a different IP address.
but I would like to reconnect them
Do you mean the targets or the server in the management console?
Mareo
Posts: 18
Joined: Tue May 21, 2024 11:35 am

Mon Nov 04, 2024 12:30 pm

Hi,

I did try removing the server and add it again, but it did not help. I also tried different ways of adding it and it still can't connect.
Do you mean the targets or the server in the management console?

The server in the management console.

EDIT: not that I would like to get them connected, I NEED them connected :D
yaroslav (staff)
Staff
Posts: 3424
Joined: Mon Nov 18, 2019 11:11 am

Mon Nov 04, 2024 2:41 pm

Does any other IP work?
If no, restart StarWindService. If that still does not help, stop the StarWindService on the "affected" node (follow the restart precautions (https://knowledgebase.starwindsoftware. ... installed/)) -> go to C:\Program Files\StarWind Software\StarWind\NotifyDB -> Move all the contents from there to elsewhere. -> start StarWindService -> try again.
Mareo
Posts: 18
Joined: Tue May 21, 2024 11:35 am

Fri Nov 08, 2024 7:22 am

Hi Yaroslav,

first of all, thank you so much for your support and help.

Secondly, kind of an informative question. I tried reading the log files, but I could not understand where to look for the "which node has the most recent data", in case something drops out.

Where would I look for the data or what parameters do I need to look for? If necessary, I can provide the logs(assuming its not a security risk for us... or something.

Thanks again in advance and thank you for your kind understanding!
yaroslav (staff)
Staff
Posts: 3424
Joined: Mon Nov 18, 2019 11:11 am

Fri Nov 08, 2024 8:44 am

No worries ;) My pleasure to help.
You can look through the logs to find which node went not-synchronized first. This node SHOULD NOT be marked as not synchronized. Look for "to 3 from 1" both for partner and local node.
Ideally, one node should mark the partner as not synchronized while another marks itself as not synchronized.
If you are not sure, leave only one node running, bring up the VMs, and see if the VMs have up-to-date data. If they do, bring it up and let sync running. If they don't, bring down that side, mark another as synchronized, and check again.
I hope this helps!
Post Reply