Did you try the below?.
cluster res "ResourceName" /priv IsAliveTimeout=900000:DWORD
RegardsVinothFrom: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Praveen Ramaswamy
Sent: Friday, May 11, 2007 2:35 PM
Subject: [ExchangeList] Re: Cluster: failover issue
Vinoth,I do have a separate hub for heart beat, but still i have this problem.How do i solve this issue. I thought i sould change the failover time for public interface.RegardsPraveen R
Vinoth Prabhu G <ecrgvp@xxxxxxxxxxx> wrote:Praveen:
You should use a separate hub/switch/direct cross cable for the heart beat network which is separate from the enterprise network. If yes, these rare conditions can be avoided.
Any way for your case, use the following command to change the failover to occur after 900 seconds?.
cluster res "ResourceName" /priv IsAliveTimeout=900000:DWORDRegardsVinothFrom: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Praveen Ramaswamy
Sent: Thursday, May 10, 2007 12:11 PM
Subject: [ExchangeList] Cluster: failover issue
Hi,I have a three node exchange 2003 SP2 cluster on windows 2003 SP1, I have two virtual exchange server running on two separate nodes. Issue is, when ever there is network port issue on a particular node which is hosting exchange virtual server, it immediately tries to failover to other node. I know this is the right thing to do but I want this to fail over only after waiting for 900 seconds. Suppose network port comes back to normal within this time then there wont be any inconsistency. I have made all NIC port on the servers to 100 MBs /full duplex instead of auto neg.Right now I have made IP resource threshold : 3 period: 900 secs. But still it immediately fails over .Can any body help me on this.Regards
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games.