steve_carlose wrote:
Hi Schmoog
I talked with HP. they want to charge us for new controller but I think the problem it's not from the controller . be honestly I fixed the first problem in node 2.before when I got a console of node 2 I saw a node 1 but now it's working and when I got a console of node 2 I saw node 2.I think the problem is from The IO in some our shelf. I need more time. I'll let you know as soon as possible my friend. I'm in Armenia now.
Steve,
I'm a big believer in that the reason for an error message is to tell you what is wrong.
Therefore, if the error says "remote node mismatch", then the problem is that the remote node is mismatched. Plain and simple. Unless there's a different error message, I'm not seeing anything for you to base the belief that the problem stems from shelf IO on.
Anyway, HP's advice is not without merit. The reason is that while you didn't complete the initialization before this error was made, you initialized it enough for the nodes to pair with each other. Replacing the node with a brand new node will allow the new node to pair correctly. It's a bit of a lazy way to fix the issue IMO based on the evidence that you've presented before us, but it would get the job done.
What we really need is the error message from each node, labeled by node position. So for instance:
Node 0 position - <ERROR MESSAGE HERE>
Node 1 position - <ERROR MESSAGE HERE>
Node 2 position - <ERROR MESSAGE HERE>
Node 3 position - <ERROR MESSAGE HERE>