Back to Contents Page
Overview
• Unable
to connect to an array server or timeout connecting to an array server
This appendix describes how to troubleshoot problems that may occur when you run Data Supervisor.
It lists problems and suggests actions the may help resolve or isolate the problem.
Make sure that the following conditions are met:
- Data Agent is running on the server connected to the array you are trying to manage and the correct
device name for the array is entered in the Data Agent configuration file.
- Fibre channel cabling between the server and the array is connected correctly.
- Server can perform I/O operations to the array.
- Ping the server. If you cannot ping the server, check the network configuration as follows:
- .Determine how the network is configured by running IPCONFIG/ALL.
- .If the network uses DNS or WINS for name resolution, ping the DNS or WINS server to make sure
it is reachable over the network.
If the DNS or WINS server is not reachable, and you want to manage locally attached arrays only (that
is, Data Supervisor and Data Agent both on the array server), you can enter localhost instead of the
hostname in the Host Administration window. You can temporarily manage arrays on any server that you
can ping by entering its IP address in the hosts file on the management station. If you are using
DHCP, remove any server IP addresses you added to the hosts file as soon as you configure their
arrays. The default directory for the hosts file is c:\system32\drivers\etc.
Dual board unbind error
Make sure that the configuration file for Data Agent on the server for the array has a path to the
SP that currently owns the LUNs that you are trying to unbind. For information on the Data Agent
configuration file, see the Data Agent manual.
Caller not privileged
Make sure that the configuration file for Data Agent on the serer for the array has a privileged
user entry for the user account on the Data Management station that started the Data Supervisor
session. For information on the Data Agent configuration file, see the Data Agent manual.
LUNs appear in the Unowned LUNs section of the Array Configuration window
Being unowned is an abnormal state for any LUN except a hot spare. If you have an unowned LUN that
is not a hot spare, go to the section below for the appropriate LUN type.
For any unowned LUN - Do the following:
- Make sure that the default SP for the LUN is present in the array and has a host connection.
- Make sure the Data Agent configuration file has the correct path to the LUN's default SP.
- If the LUN is a redundant RAID group, check its Equipment View window for failed CRUs. If it has
more than one failed CRU, follow these steps:
- Replace the failed CRUs.
- Unbind and then rebind the LUN.
- Restore the data on the LUN from a backup copy.
- If the LUN is a non-redundant RAID group, check its Equipment View window for failed CRUs. If it
has any failed CRUs, follow these steps:
- Replace the failed CRUs.
- Unbind and then rebind the LUN.
- Restore the data on the LUN from a backup copy.
Non-RAID 3 LUN - Make sure that mixed mode is enabled for the array with the LUN.
RAID 3 - Check the SP event log for an entry stating "Can't Assign. No R3 Memory"
for the array. If you see this error, allocate at least 32
Mbytes of array memory to the RAID 3 partition.
Back to Contents Page
