Hi,
Welcome back![Smile :)]()
Make also sure that the IscsiDiscoveryInterfaces is set to 1.
1. Make sure HA devices are synchronized.
2. Make sure they are connected over iSCSIl.
3. Stop the starwind-virtual-san.service
4. Edit StarWind.cfg accordingly.
5. Start starwind-virtual-san.service.
6. Wait for fast sync to complete.
7. Repeat for the remaining VM.
In general, please review the setting in CVM StarWind.cfg and make sure sync is over.
Welcome back

Make sure the storage is synchronized and reachable over iSCSI. Make sure no firewall. Also, make sure iSCSI IPs are supplied correctly.One of the final remaining issues we have is that our windows iSCSI initiators often return 'Target Error' when trying to make a new connection/session to VSAN.
Make also sure that the IscsiDiscoveryInterfaces is set to 1.
1. Make sure HA devices are synchronized.
2. Make sure they are connected over iSCSIl.
3. Stop the starwind-virtual-san.service
4. Edit StarWind.cfg accordingly.
5. Start starwind-virtual-san.service.
6. Wait for fast sync to complete.
7. Repeat for the remaining VM.
Yes, the storage was not synchronized during the first test.After several attempts and sometimes after leaving a given windows initiator node for a few hours, we can get at least one connection/session to each VSAN node for a given target, but getting a session on each of the 4x paths per target can take a lot of attempts (luckily we're using powershell).
Please be careful with this specific timeout.I noticed they seem to timeout after 5 seconds, so tried changing the 'TcpRecvTimeout' setting in StarWind.cfg to "-20" but that just seemed to lengthen the time it took to fail (I think).
In general, please review the setting in CVM StarWind.cfg and make sure sync is over.
Statistics: Posted by yaroslav (staff) — Tue Sep 24, 2024 11:44 am