Hi Mike and Shivam,
During the time of the power off testing there were no nodes in the DDNA membership. The hex code after the DDNA (and other memberships for that matter) tell you what nodes are in that membership. In this case, 0x0 indicates that no node is in that specific membership at that time.
During the reboot of the powered off node, you can see that DDNA membership changes to 0x2. To decode this, convert the number from hex to binary. When in binary the position of the 1's indicate which node ID are in that membership. Each node takes up 1 bit and the node ID's start at 0 (going from right to left for node IDs.) So in this case hex 0x2 equials 0010 in binary and the second position that the 1 is in corrasponds to the node ID 1.
I'm not sure why the http group is not being marked as "Faulted" at the 18:54:49 timeframe. However, the group "ClusterSerivce" is a special group that the cluster takes extra precautions to keep online and failover when other groups do not.
During your statup of the node, I see that the cluster goes into Jeopardy. Jeopardy is that you are down to a single heartbeat. Jeopardy will prevent the cluster from failing over all service groups other than the ClusterService group.
Here is what I would recommend:
1. Increase the ShutdownTimeOut value to 300 on all servers. This is a per server setting but can be set for all servers from a connection to a single node. Be sure the save and close the cluster configuration when done with making this change.
2. Ensure that the cluster is not in Jeopardy membership prior to running the power off/shutdown test.
3. Perform the power off/shutdown test again.
Let us know how your tesitng goes.
Thank you,
Wally