In a MSCS cluster, an admin of one of our higher profile client machines failed over from one machine (OLALPHA) back to other (OLBRAVO) after BRAVO crashed this morning.
Since I've been having a devil of a time with a MSCS cluster resource that serves as the scheduler for the cluster drive on BRAVO not coming up. To begin with, it posted ANS1835E, ANS1025E, ANS1570E, all of which point to authentication problems. I updated the node password, issued a 'q ses -optfile...', and it would authenticate fine. When I try to bring the cluster resource back online, it stays up from a few seconds, fails, and when I check the registry, the passwords has disappeared! What in the world? It has also posted ANS1029E and ANS2050E since I've been playing around trying to get the cluster resource to work, and also the base client (to back up C/D/system state) has been issuing ANS1977E with the "ccCreateTimerFile: Unable to create timer file" and "errno=13 error: Permission denied". Huh? God bless you!!! Chip Bell Network Engineer I IBM Tivoli Certified Deployment Professional (ITSM 5.2) Baptist Health System Birmingham, AL ----------------------------------------- Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
