Administrator Guide

An error message is displayed in the command line when the utility cannot distinguish between the following:
• Source virtual disk and snapshot virtual disk—for example, if the snapshot virtual disk has been removed.
• Standard virtual disk and virtual disk copy—for example, if the virtual disk copy has been removed.
Unidentified devices
An unidentified node or device occurs when the MD Storage Manager cannot access a new storage array. Causes for this error include
network connection problems, the storage array is turned off, or the storage array does not exist.
NOTE: Before beginning any recovery procedure, make sure that the Host Context Agent software is installed and
running. If you started the host before the host was connected to the storage array, the Host Context Agent software is
not able to find the storage array. If so, make sure that the connections are tight, and restart the Host Context Agent
software.
• If a storage array is managed by using both out-of-band management and in-band management using the same host, a management
network connection problem may prevent direct communication with the storage array. However, you may still be able to manage the
storage array over the in-band connections. The opposite situation can also occur.
• If a storage array is managed through more than one host, it is possible that the storage array may become unresponsive to
communication over the connections given by one host. However, you may still be able to manage the storage array over the
connections provided by another host.
Recovering from unidentified storage array
To recover from an unidentified storage array:
1. Make sure that the network connection to the storage management station is functional.
2. Make sure that the controllers are installed and that the power to the storage array is turned on. Correct any existing problems before
continuing.
3. If you have an in-band storage array, use the following procedure. Click Refresh after each step to check the results:
a. Make sure that the Host Context Agent software is installed and running. If you started the host before the host was connected to
the controllers in the storage array, the Host Context Agent software is not able to find the controllers. If so, make sure that the
connections are tight, and restart the Host Context Agent software.
b. Make sure that the network can access the host by using the ping command in the following syntax: ping <host-name-or-
IP-address-of-the-host>
If the network can access the host, continue to step c. If the network cannot access the host, skip to step d.
c. Remove the host with the unresponsive status from the MD Storage Manager, and add that host again.
If the host returns to optimal status, you have completed this procedure.
d. Make sure that the power to the host is turned on and that the host is operational.
e. If applicable, make sure that the host bus adapters have been installed in the host.
f. Examine all external cables and switches or hubs to make sure that you cannot see any damage and that they are tightly
connected.
g. If you have recently replaced or added the controller, restart the Host Context Agent software so that the new controller is found.
If a problem exists, make the appropriate modifications to the host.
4. If you have an out-of-band storage array, use the following procedure. Click Refresh after each step to make sure of the results:
a. Make sure that the network can access the controllers by using the ping command. Use the following syntax: ping
<controller-IP-address>
If the network can access the controllers, continue to step b. If the network cannot access the controllers, skip to step c.
b. Remove the storage array with the unresponsive status from MD Storage Manager, and add that storage array again.
If the storage array returns to optimal status, you have completed this procedure.
c. Make sure that you cannot see any damage and that they are tightly connected by examining the Ethernet cables.
d. Make sure that the applicable network configuration tasks have been done—for example, the IP addresses have been assigned to
each controller.
5. Make sure that the controller firmware is compatible with MD Storage Manager on your management station. If the controller
firmware was upgraded, the MD Storage Manager may not have access to the storage array. A new version of MD Storage Manager
may be needed to manage the storage array with the new version of the controller firmware.
If this problem exists, see Getting Help.
166
Storage array software