In extensive systems of clusters with several clusters and resources, the administration can be a little tricky, even more using iManager.
At the time to work with the cluster resources there are different variables that can cause that the resource reports Comatose state: duplicate IP addresses, failures in the access to the SAN, errors in the script of loading or unloading, problems with the eDirectory, SLP issues, etc. The experience and the knowledge of the operation of the cluster helps to detect the cause of the failure.
However, sometimes, when you need quick actions to solve the problem can be extremely useful a message much more near or as accurate of the probable cause of the failure. This message could be displayed in the iManager as in the console of the node where the resource reported the comatose state.

Comments