Vista - hyper-v and iscsi san

This is probably question for storage vendor but I figured I'll try here. I
have iSCSI storage that officially does not support Win 2008 server OS,
though my testing shows no problem with exception when Hyper-V is enabled and
used. Here is what's happening after hyper-v is enabled and VMs are stored on
iSCSI LUN. Exactly every 30 minutes each of connected 2008 servers with
hyper-v to iscsi storage is logging/verifying that LUN is still accessible
(this is my assumption) I learned about this because our iscsi storage
creates log of "iscsi login attempt" and number of this login attempts is
growing over the time starting from them moment when hyper-v is started, my
problem is that when this number of "iscsi login attempts" reach a magic
number X iscsi storage will crash and needs to be reset, then all starts
again. If I disconnect 2008 servers with hyper-v or simply stop hyper-v
services this "login attempts" is no longer growing and our iscsi storage
works well. So here is my question is there a setting somewhere in registry,
config files or any other place related to hyper-v that checks
drives/vol/luns every 30 minutes?
If there is I'd like to adjust this and see if I can extend uptime of our
iscsi storage with 2008/hyper-v servers attached

On Oct 13, 9:42*am, RW <R...@newsgroup> wrote:You may want to go into the Properties:Advanced Policies of your
Volume cluster resource and change the Basic and Advanced Resource
Health Check Intervals and see if that effects your logs. You could
probably tune these up pretty high without much risk as I assume if
your disk is unavailable, the Virtual Machine resource will also fail.

It sounds like you are on pretty shaky ground to begin with, you
should probably read my blog post on iSCSI storage and clusters for
some more information.

http://clusteringformeremortals.word...-link-goodbye/