![]() ![]() I figured out and fixed my issue sitting half day long! And I am able to telnet Starwind node from other 2 nodes on 172.168.0.1:3261, with a result Both Nodes have a second virtual LAN installed with IP 172.16.0.2 and 172.16.0.3 to talk to Starwind iSCSi target (both nodes are Windows firewall turned off, Multipath I/O and failover cluster features installed)ģ.I am able to successfully ping from Starwind node to other 2 nodes and vice versa. Other Node 1 and Node 2 are domain members with IP 10.0.0.7 and 10.0.0.8. The Starwind storage Node is in workgroup with IP 172.16.0.1, windows firewall is turned off, Multipath I/O feature installed.Ģ. I properly logged on and configured a 2GB basic virtual HDD image file device on Starwind server.ġ. In the same lab I have another 2 Windows Server 2008 Ent SP1 nodes, domain members, with Microsoft iSCSI initiator service enabled to connect to target Starwind node. I have a Microsoft Virtual PC 2007 lab where I installed Starwind iSCSi SAN Software 5.4 Ent 30 days trial on a Windows Server 2008 Ent SP1 workgroup node. I recently discovered Starwind software and it's capbilities of being virtual SAN storage. StarWind Virtual Tape Library (VTL) OEM.StarWind Virtual Tape Library Appliance (VTLA).StarWind HyperConverged Appliance (HCA). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |