Timeline of events

Example:

• HSC script times out on node A
• Node A failover to node B
• Server running node A reboot
• Node B fail back to node A

Host Information

Refer to the following article to collect information for Microsoft Windows-based OS: Windows Server Configuration (wingetconfig).

• In addition collect all events logs from the server event logs around the time of the failure (system and application):
  
  %SYSTEMROOT%\system32\config.
  
  

Refer to the following article to collect information for VMware ESXi Environments: Collecting Diagnostic Information for VMware ESXi Server Problems.

Config files

Collect the HSC Config Files and a copy of the script

%SYSTEMROOT%\*.conf

Where * is the resource name of HSC in the cluster.

Cluster logs

Obtain the cluster logs from the previous owning node and the failover node. This log is located on each node.

C:\%SYSTEMROOT%\cluster\cluster.log.

Pair Displays

From the CCI executable directory (usually C:\HORCM\etc), review the current pair status of the cluster volumes. From both the previous owning node and the failover node, run:

pairdisplay -g -CLI -fc

Use -l if the remote node is not available. Collect screenshots from the output of the above commands.

CCI

Gather the HORM TC Configuration and log files, for more information refer to the following solution: CCI Data Collection.

Switch Data Collection

Collect the switch logs based on the network infrastructure:

• For Brocade switches, refer to the article: Brocade Data Collection
• For Cisco switches, refer to the article: Show tech-support

Subsystem Logs

Collect the logs for the backend storage:

• For Midrange (DF): Midrange Hardware Data Collection
• For Enterprise (RAID): Enterprise Data Collection

Current Status

Gather information about the current status of the cluster, mention if the cluster is down, stable or if there is any impact to the service or the environment.

Time Offset

Specify the current time zone, and time delta between all hosts and arrays involved.