Re: iscsi multipath fails when cluster service is started

Tech-Archive recommends: Fix windows errors by optimizing your registry

i'm already in contact with the storage/server/network/iscsi vendor. it's dell.
but it seems to be a simple windows problem.

i've configured a virutal machine with windows server 2003 under esx4 to
test the behavior of the network inferfaces.
both interfaces are in the same subnet with no gateway.
i've started a ping to a reachable host. when i disable the network
connection of the vm, i only got 2 timeouts and then it goes on.

when i do the same procedure on my physical server with installed cluster
services, the ping stops and the host is isolated even though the second
interface still has a connection.
is this a common behavior under windows server 2003 enterprise x64 with
cluster service?
i think the problem is that the interfaces are in the same subnet.
there is only one of two interfaces in the cluster administrator under
"networks" and the missing interfaces causes the problem.


"John Toner [MVP]" wrote:

I'd recommend dropping down to a single iSCSI connection and removing any
multipathing software and see if the same behaviour occurs. If so, you will
probably need to open a ticket with MSFT to troubleshoot this further.

If dropping down to a single path resolves this issue, you'll want to work
with your network/iSCSI vendor to resolve this issue.

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner

"MarkusN" <MarkusN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1E5BB2EC-6F1C-457C-B4FF-AB4A3A2C525F@xxxxxxxxxxxxxxxx
the initiator is configured fine and i can see the connections on the host
and on the storage site.
the problem is that the whole ip stack colapses, when i pull one
interface.
(but only the interface that is not listed in the cluster admin network.
there is listed only one interface, because of the same subnet.)
the host is completely isolated from the iscsi network.

when i disable the interface in the windows network connections, the
failover works fine.



.

Relevant Pages

  • Re: Failover on public network failiure?
    ... There are a number of ways the cluster service checks the state of the ... If the network interface is determined to be failed then any ... the IP address on the current node the groupwill failover to another ...
    (microsoft.public.windows.server.clustering)
  • Re: Heartbeat question
    ... Without fully knowing how this Cluster server is configured, ... 286342 Network failure detection and recovery in Windows Server 2003 ... > I followed all MS recommendations for heartbeat config. ...
    (microsoft.public.windows.server.clustering)
  • Re: Cluster in IBM Bladecenter HS20
    ... > fails the whole cluster becomes unavailable. ... >> then you public network). ... >>> configuration is certified by the Windows Server Catalog. ...
    (microsoft.public.windows.server.clustering)
  • Re: Strange HACMP config error
    ... > had a full network blackout yesterday. ... The cluster was instable after ... > First one IP interface is gone. ... network switch logs can show routing problems if you have access to them. ...
    (comp.unix.aix)
  • Cluster Help?
    ... I am having an issue with my second node of an active/passive cluster. ... in cluster administrator both of the network cards are ... contexts for node 1. ... interface 1f387670-01f2-4fb1-b728-95b03d9321c2 ...
    (microsoft.public.windows.server.clustering)