Quote:
Originally Posted by
Koen87
[...]Still getting the same error. It's driving me crazy. I've set up a new cluster perfectly without the assistent using this configuration, why won't the assistant do it?
The reason for the Config Assistant was/is that many admins found/find configuring a cluster from the SMIT panels confusing if not difficult. So IBM tried to make this a lot easier by offering to "configure a PowerHA cluster by just answering 5 questions..." However, the price is that the Config Assistant for the basic two-node cluster is limited in both the type of cluster that is being configured and the prereqs it expects. If anything during first node discovery fails (that is where you are at the moment) the Assistant stops.
You probably checked that a hundred times by now but there still is something in the communication between the nodes that causes a problem. Some differences in the serves configuration are difficult to find. Try to let the cluster nodes discover the setup from both sides and look at the messages to find where information is missing/blocked.
Btw what I usually do when installing basic clusters from scratch with the Installation Assistant is that I install a single node plus the PowerHA software. Then I clone this node with mksysb to the secondary node. At that moment I have two nodes which are identical save hostname, uname and addresses.
However, if you can configure a working cluster with the PowerHA SMIT panels you should not need to worry about whether the Assistant works for you or not. In this case you are much more flexible already.