on 08-20-2007 11:09 AM
I have a couple of clusters producing unexpected behaviour. The problem is the same for both.
Two nodes in the cluster, all resources are on Node A. SAP section of the cluster fails over to Node B for no apparent reason, SQL stays on A.
Node A and Node B can see each other no problem. However, users cannot connect to the B Node, only A.
Node B doesn't failback and if you try to make it by using Move Group it fails and switches back to Node B.
To make it move back you have to shut SAP on Node B and Node A. It will then let you move it back.
Any help or advice much appreciated.
David
Thank you the quick response.
Following some greater investigation into the Event logs I think this may not be a SAP issue after all but rather a Windows/Cisco issue with the Shares timing out.
David
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
that are two problems:
1. unexpected failover
2. move back to A did not work
I need a little more information for getting the right answers.
- SAP release
- what did you find in the system log (event viewer, system)
- assuming you are running on 2003 output of tasklist.exe on A before you move the resource back to A.
peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First response question: What do the windows logs say?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.