Node Alias wont release upon server failure

What your setup?

Node name, node ip
What alias setup?

Does you check your node alias registered at domain controller, some time we need to manual deleted it before other node can register those alias.

I had opened a case with support and they stated that if the box reboots AAM doesn't see the node as completely offline as it is still responding in some fashion. Once the box completely rebooted on node1 the reset name script ran and all resources were moved over to node2.

If I turned the box off the resource group successfully failed over to node2.

I seem to be having a similar problem. When I pull the NIC cable to simulate a switch that failed, the resource group fails over to the second node. Then I pull the cable back in and get the first node talking again and happy in the cluster. Next I pull the cable on the second node, which is now the active node, and all that happens is it takes the resource group offline. It will not fail back to the first node.

I have set up on a production system and on a test system and both behave the same way. Has anyone else run into this or have any suggestions?

Thanks,
Alan

Are you testing 'Isolation'?

It doesn't move correctly even if the failover is done by using the function of Isolation.

Because the bug has been found by the function of Isolation.

Bug ID:LGTpa89426

EMC does this correction.

I believe there is the option to "auto failback to first node"

Try that Alan.

Message was edited by:
Joshua McGowan