Troubleshooting

When an error occurs, check the status of Spectrum Virtualize Family, VMware ESX servers, vCenter servers, and SANs.

Managing DiscoverArrays failure

Verify the following items when you encounter a failure during Array Manager operation:

Check that the IP address is correct and in the correct format. For example, the format can resemble: 192.168.10.1:5989.
Check that the user name and password are correct.
Check to see whether the SAN Volume Controllers are paired.

Managing DiscoverDevices failure

Important: Relationship and consistency group status typically is consist_synchronized or consistent_copying for Global Mirror with Cycling Mode.

Troubleshooting remote copies with the SRA Check Tool

Note: The SRA Check Tool does not support review of IBM SVC Stretched Cluster or IBM HyperSwap.

You can troubleshoot remote copy problems from within the configuration utility tool. The troubleshooting service from within the SRA Check Tool reviews every remote copy that is included in the most recent SRM operation.

Complete the following steps to run the SRA Check Tool:

Open the configuration utility tool by clicking the IBM Spectrum Virtualize Family SRA Configuration Utility.exe shortcut on the desktop.
Click Check.
Enter a user name and password for the local and the peer array.
Figure 1. IBM SRA Check Tool
Select Troubleshooting from the SRA Check Tool menu and click Check.
When the utility finishes, click Close.
Enter a file name and click Save to save the log file.

The log file is saved to the hard drive where it can be retrieved for troubleshooting help.

Managing recovery failure

For environments that are not pre-configured, ensure that the following items are checked or corrected:

Recovery, after you switch from pre-config without rescan SRA.
CIM user privilege problem, administrator required.
After disaster recovery, it is necessary to wait a few minutes and then refresh the devices in the SRM Array Managers on both sites. This step is necessary to ensure that there is no error before the plan is reprotected.

For environments that are pre-configured, ensure that the following items are checked or corrected:

FlashCopy® was not created.
Corresponding fcmap consistency group was not created.
The Remotecopy target volume is not mapped to the recovery site.

Managing Test failure

For environments that are not preconfigured, ensure that the following are checked or corrected:

CIM user privilege problem, administrator required.
Not enough space in the mdisk group.
Switching from pre-configured without rescan SRA.
The Mdiskgroup and volume type is not set for Spectrum Virtualize Family SRA.

For environments that are preconfigured, ensure that the following items are checked or corrected:

FlashCopy not created.
FlashCopy target volume is not mapped to host.
Corresponding FlashCopy consistency group not created.
FlashCopy target volume that is mapped to the host are shown as Mounted in Hosts and Clusters/Configuration/Storage/Devices.

Managing SRM procedures

Refresh the devices in the SRM array managers. If there are no errors, go to step 3. Otherwise, continue to step 2.
Check all the previously related remote copies in the SRA-STATUS file in the SRA installation directory. For example, C:\Program Files \VMware\VMware vCenter Site Recovery Manager\storage\sra\IBMStorwize. The format of the SRA-STATUS file is shown in the following example:
```
[ArrayID]|[LunID]=* [ArrayID] + "|CG;" + 
[RemoteCopyConsistencyGroupName]=*
```
A sample of the content of the SRA-STATUS file can be seen in the following example:
```
000002006E814E66|2=CREATEVOLUME@4;
60:05:07:68:01:BA:05:39:98:00:00:00:00:00:00:2C 
TESTFAILOVER@4;
60:05:07:68:01:BA:05:39:98:00:00:00:00:00:00:2C
```
This example shows that the standalone remote copy (target volume id:[2]) in the array [000002006E814E66] was in testfailover status. Spectrum Virtualize Family SRA created a FlashCopy for the remote copy target [2] and the FlashCopy target volume id is [4]. The UUID is 60:05:07:68:01:BA:05:39:98:00:00:00:00:00:00:2C.
Refresh the devices in the SRM array managers again to ensure that there are no errors.

Collect log files

If the problem cannot be resolved by following any of the troubleshooting tips, collect the SRM log files and contact IBM® support.