Hi I have a simple query, I am in the process of configuring a "Test/Dev" Hyper-V failover cluster so i have two cluster nodes 01 & 02 that each have multiple NIC's The problem is that once i have configured the LAN NIC i have full LAN & Internet access but when i try configure the SAN Fabric "second" NIC i cant ping the iSCSI Target or the other Cluster Nodes SAN Fabric NIC that is on the same range? For example i have ClusterNode01 & ClusterNode02 ClusterNode01 is as follows NIC1 LAN = 172.16.10.10 Static IP 255.255.255.0 172.16.10.254 GW 172.168.10.5 DNS NIC2 SAN Fabric = 192.168.100.20 255.255.255.0 I didnt configure a GW or DNS as I just want it to connect directly to Nodes on the 192.168.100.x range ie the iSCSI Target but i cant pint the iSCSI Target 192.168.100.10 ? ClusterNode02 is as follows NIC1 LAN = 172.16.10.11 Static IP 255.255.255.0 172.16.10.254 GW 172.168.10.5 DNS NIC2 SAN Fabric = 192.168.100.21 255.255.255.0 I have read that static routes using NETSH route add are required but i tried it and no joy maybe my syntax is incorrect as i didnt know what to put as the GW as im not using one on that NIC? This is a Server 2008 R2 networking issues not really a cluster issue as when i have connectivity the cluster wizard will validate Thanks in advance Spudney

R u connecting this to a real SAN fabric or ur storage is also in a virtual env ? http://www.virmansec.com/blogs/skhairuddin

Just to add i have disabled the NIC 1's and turned off the firewall on both nodes so NIC 2's are the only NIC's enabled but I still cant ping 192.168.100.20 or vice versa? Just tried this in Server 2003 and it all works fine? What am i missing its obviously someting to do with routing, tracert tells me nothing either? also its a simple netgear 5 port switch that connects both nodes Spudney

Hi The san fabric is a seperate physical server with 2008 R2 (2 NICs for MPIO) running and Microsoft iSCSI Software Target 3.3 for server 2008 R2 so yes i guess its a real SAN fabric but its not a san issue its just a simple networking issue, dont you think? Spudney

I would suggest u to enable routing on one of servers (RIP v2) and add the both the interfaces. that should solve the problem.I assume this testlab running in virtual Environment.Gopi Kiran |Facebook| This posting is provided AS IS with no warranties,and confers no rights.

hi no its physical, no virtual can u explain ur solution a bit more? how come in server 2003 this works? what has changed in server 2008 Spudney

ah makes sense "In Microsoft Windows Server 2008, there are a number of IP routing changes that you need to be aware of. With the removal of OSPF, we are left with static routing or dynamic routing with RIPv2." http://www.windowsnetworking.com/articles_tutorials/how-configure-windows-2008-server-ip-routing.html Spudney

RIPv2 didnt work? It looks like the two motherboard NICs work but the 4 pci-e NIC cards dont work? but if i use one of the PCI-E nics with the same LAN config as one of the on board NICs it does work anyone any ideas?Spudney

Hi Spudney , Thank you for your post. 1.Please first post the "route print" result to us. 2.If you disable NIC1, does the NIC2 works to ping iSCSI target 192.168.100.x? If there are more inquiries on this issue, please feel free to let us know. Regards, Rick Tan TechNet Community Support