![]() In this document, 172.16.10.x subnet is used for iSCSI/StarWind heartbeat traffic, while 172.16.20.x subnet is used for the Synchronization traffic.Ĥ. In order to allow iSCSI Initiators to discover all StarWind Virtual SAN interfaces, the StarWind configuration file (StarWind.cfg) should be changed after stopping the StarWind service on the node where it will be edited. This can be done through the Server Manager (Add Roles and Features) menu item.ģ. Configure network interfaces on each node to make sure that Synchronization and iSCSI/StarWind heartbeat interfaces are in different subnets and connected according to the network diagram above. NOTE: Please follow the recommendation in KB article on how to place a DC in case of StarWind Virtual SAN usage.Ģ. Install Failover Clustering and Multipath I/O features, as well as the Hyper-V role on both servers. Make sure that a domain controller is configured and the servers are added to the domain. ![]() The network interconnection diagram is demonstrated below:ġ. Pre-configuring the Windows Server 2012 R2 Hosts
0 Comments
Leave a Reply. |