Make sure your iSCSI network connections do NOT have Default Gateways
configured. I'd also verify the configuration of the iSCSI target device as
well as ensuring the path is clear between the iSCSI NICs and the
device...firewalls, ports opened, etc.
Hope this helps,
--Ryan
--
Ryan Sokolowski
MVP - Clustering
MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFP
"PaulS" <reply@xxxxxx> wrote in message
news:O3s3ZtDnJHA.4652@xxxxxx
Quote:
> Today I attempted my first 2-node Hyper-V cluster and quickly ran into
> problems. I followed best practice with dedicated LAN network cards on a
> 10.10.1.x and dedicated iSCSI network cards 192.168.1.x. However, I was
> unable to get the iSCSI initiator on either node to recognise the shared
> storage device. I finally gave up and moved the iSCSI device on to the
> same network cards as the LAN and everything worked perfectly. Of course
> this is not best use of network bandwidth and in a live environment I
> would like to know what I had done wrong. I assume that there is some way
> to force the iSCSI connection over a specific network adapter, if so I
> couldn't find it. In addition, the iSCSI network kept returning to
> "Public" even though I set it as "Private" many many times. This prevents
> all network connections to other devices on the network. I understand
> where it is useful but I was in the server room not an Internet cafe! Any
> suggestions on the two problems I encountered would be much appreciated.
> Thanks.