Search found 4 matches

by LudoEXEC
Tue Nov 18, 2014 5:45 pm
Forum: StarWind Virtual SAN (VSAN) [+Free], HCI Appliance (HCA), Virtual HCI Appliance (VHCA) [+Free], StarWind x Proxmox VE SAN Integration Services
Topic: iSCSI 127.0.0.1 not connected first on host reboot
Replies: 13
Views: 20122

Re: iSCSI 127.0.0.1 not connected first on host reboot

Thanx very much !
Honnestly, are the two backup iSCSI networks (iSCSI Data1 and iSCSI Data 2) really necessary ?
Can I live with 127.0.0.1 on each hosts and the two 10Gbs Sync1 and Sync2 links for Starwind ?

regards
by LudoEXEC
Tue Nov 18, 2014 3:12 pm
Forum: StarWind Virtual SAN (VSAN) [+Free], HCI Appliance (HCA), Virtual HCI Appliance (VHCA) [+Free], StarWind x Proxmox VE SAN Integration Services
Topic: iSCSI 127.0.0.1 not connected first on host reboot
Replies: 13
Views: 20122

Re: iSCSI 127.0.0.1 not connected first on host reboot

[quote=
As for now maybe you could write some PoSh script that would set 127.0.0.1 address as the active path in initiator after the reboot.[/quote]

Thank you for that good idea !
Any quick examples / web links on how to do that kind of Powershell ?

Thanx Anatoly
Best regards
by LudoEXEC
Tue Nov 18, 2014 10:42 am
Forum: StarWind Virtual SAN (VSAN) [+Free], HCI Appliance (HCA), Virtual HCI Appliance (VHCA) [+Free], StarWind x Proxmox VE SAN Integration Services
Topic: iSCSI 127.0.0.1 not connected first on host reboot
Replies: 13
Views: 20122

iSCSI 127.0.0.1 not connected first on host reboot

Hello, I am facing a problem with a Windows 2008R2 2 nodes Hyper-V cluster and Starwind v8. Each time I reboot one of the two nodes, the loopback is not set active first in the iSCSI connections. The initiator takes one of the two iSCSI backup networks and leave the other one and loopback on standby...