Search found 3 matches

by Peter-s7
Tue Mar 05, 2019 10:32 am
Forum: StarWind Virtual SAN (VSAN) [+Free], HCI Appliance (HCA), Virtual HCI Appliance (VHCA) [+Free]
Topic: Node after reboot inaccessable
Replies: 3
Views: 4857

Re: Node after reboot inaccessable

Solution: - Disconnect 2nd Node as a replication partner for all HA Volumes - Re-Install Starwind on Node_2 - Delete all legacy valumes, first from Management Console, Second from Disks - Re-Add the 2nd Node as a Replication Partner for the HA-Volumes Now it's working, even after a reboot. Don't kno...
by Peter-s7
Mon Mar 04, 2019 2:49 pm
Forum: StarWind Virtual SAN (VSAN) [+Free], HCI Appliance (HCA), Virtual HCI Appliance (VHCA) [+Free]
Topic: Node after reboot inaccessable
Replies: 3
Views: 4857

Re: Node after reboot inaccessable

Additional Info: Node_1 netstat-na TCP 172.16.44.24:139 0.0.0.0:0 LISTENING TCP 172.16.44.24:3260 0.0.0.0:0 LISTENING TCP 172.16.44.24:3261 0.0.0.0:0 LISTENING TCP 172.16.44.24:3261 172.16.44.24:60230 ESTABLISHED Node_2 netstat-na TCP 172.16.44.25:139 0.0.0.0:0 LISTENING TCP 172.16.44.25:3260 0.0.0....
by Peter-s7
Mon Mar 04, 2019 12:17 pm
Forum: StarWind Virtual SAN (VSAN) [+Free], HCI Appliance (HCA), Virtual HCI Appliance (VHCA) [+Free]
Topic: Node after reboot inaccessable
Replies: 3
Views: 4857

Node after reboot inaccessable

Hi guys, i did a fresh install with Version 8.5 on two Windows Server 2019 machines. After setup both nodes and creating 2 HAImages, i did a failovertest. I did a restart of the second node. After the reboot was completed, the HAImages shown as synchronized, but i am no longer able to configure the ...