Cluster service was terminated as requested by Node 2

Exchange 2007 cluster went down.  Cluster service was down.
System event log on the server shows "Cluster service was terminated as requested by Node 2".  The Source is called:  ClusNet.  The Event ID is :  1118.

Node 2 of the exchange server was the passive node at the time.  Node 1 was the active node.
Not sure why Node 2 would request the cluster service to terminate.

Thanks in advance for any assistance with this issue.
syoungbloodAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

65tdRetiredCommented:
sounds like it was preventing split brain, must have lost heart beat network.

Is the public network configured as mixed to carry both heartbeat traffic as well as application traffic?
0
syoungbloodAuthor Commented:
yes
0
Fundamentals of JavaScript

Learn the fundamentals of the popular programming language JavaScript so that you can explore the realm of web development.

syoungbloodAuthor Commented:
I found another error in the system event log :

Cluster service is shutting down because the membership engine failed to arbitrate for the quorum device. This could be due to the loss of network connectivity with the current quorum owner.  Check your physical network infrastructure to ensure that communication between this node and all other nodes in the server cluster is intact.

then just after that, this error:

Cluster service was halted to prevent an inconsistency within the server cluster. The error code was 5892.

0
65tdRetiredCommented:
Have the network connections (TCP/IP setting) been reviewed and pinged on each network (public and private)?
0
65tdRetiredCommented:
Could also review the cluster log on C:windows\cluster\cluster.log on both nodes.
0
pml_raviCommented:
If a node which does not have the quorum online, and only can communicate with the "quorum" over the network to the other node, and it looses its network connections.
In the regroup it will check that it has at least one active network, if not, it will terminate itself (stop cluster service). If it does have an active network then it will try to arbitrate (using scsi reserve) for the quorum disk. As long as the other node is fully functional, it will loose this arbitration and it will terminate itself (again stop cluster service).
0
syoungbloodAuthor Commented:
this was a switch and/or port issue - moved network cable to new port and switch.  this fixed the issue.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.