Troubleshooting
See the following tables for troubleshooting information for Universal Volume Manager.
General troubleshooting
Check the following table for the problem. After resolving an error, retry the operation. If you cannot resolve the issue, contact customer support.
Symptom |
Possible causes and troubleshooting steps |
Hitachi Device Manager - Storage Navigator cannot access an external volume. |
|
An external volume cannot be mapped. |
|
An external path is blocked. |
|
Action is required for a path status in the View External LUN Properties dialog box. | |
The volume in the external system cannot be found even after port discovery or volume discovery was performed. |
Follow any instructions given in the error message or messages and then retry the operation. If the problem persists, see Troubleshooting port and volume discovery problems . |
The external volume is blocked. |
|
The status of the external volume is Blockade. |
When errors occur in all external paths, the local storage system changes the status of the external volume to Blockade.
|
The ? sign displays in the LUN ID (Highest Priority) column of the Discovered External Volumes table in the Add External Volumes window. |
A corresponding external volume was not found for the external path with the highest priority. Look for problems with the connection to the external system that failed during volume discovery. Fix any problems, and perform the operation again. |
External volume discovery was not completed because of failure. |
Look for problems with the connection to the external system; also verify that the external volume is correctly configured in the external system. Fix any problems, and then perform the operation again. |
After reconnecting an external volume or system, 10 minutes have passed but the status has not change from Checking. |
Click Refresh on the Device Manager - Storage Navigator main window. If the status remains Checking, perform the reconnect operation again. |
After disconnecting an external volume or system, the status does not change. |
Click Refresh on the Device Manager - Storage Navigator main window. Note that the time required for write processing from cache to the external volume depends on volume capacity. More time is required for larger volumes. Processing speed is about 20 MB/s. However, the processing speed also depends on the performance and status of the external storage system. |
Troubleshooting external path status
After you select External Storage from the Storage Systems tree in Storage Navigator, 'Warning' is displayed in the Status field of the External Storage window when there is an abnormal mapping path in the external volume group of the corresponding external storage. You can check details about the abnormal mapping path in the View External LUN Properties window.
The following table shows path statuses in the View External LUN Properties window. Descriptions and corrective actions you can take are provided.
Also, see Troubleshooting path errors for specific storage systems. If you cannot resolve the issue, contact customer support.
Status |
Description |
Corrective action |
Unknown |
The path status cannot be determined. |
Contact customer support. |
Blockade |
The external port is blocked. |
The port is blocked because of firmware replacement, package replacement, or other factor. Check the status of the local storage system. |
External device setting changed |
An external system setting has changed. For example, the path definition was deleted, or the external system itself was replaced by another device. |
The port of the external system is recognized. See your device manufacturer's documentation to verify that the settings on the volumes in question have not changed. |
LDEV size reduced |
The external volume capacity was reduced. |
Check the external volume capacity. If the LDEV is smaller than expected, delete the external volume, and then remap to it. |
Not ready |
The reply of the external system was NOTREADY. Either the drive is spinning up or the system is being formatted. |
The path cannot be used to access the external system. Check the status of the external system. |
Illegal request |
The reply of the external system was ILLEGALREQUEST. The command cannot be run on the external system. Data protection might be set on the external system. |
The external system port is recognized. Check the external system settings and correct any problems. |
Command aborted |
The reply of the external system was ABORTEDCOMMAND. An error might have occurred on the external system side. |
The external system port is recognized. Check external system settings and the physical connection to the external system (cables and switches) and correct any problems. |
Busy |
The external system is in the BUSY status. |
The external system port is recognized. Check whether the external system configuration causes excessive load on the system. If the load is excessive, lower the load. |
Response error |
The external system is in blocked status caused by an abnormal reply (Response). You might not be able to access the system, or data protection might be set. |
The external system port is recognized. Check the settings and status of the external system and fix any problems. |
Initiator port |
The port attribute of the external system has been changed to "initiator". |
Set the port attribute of the external system to "target". |
Destage Failed |
The writing of data from cache memory to the external volume failed. |
Reconnect the external volume or system. When status is Normal, disconnect the volume or system. You might need to try this multiple times. |
Unknown port |
The port attribute of the external system is unknown. |
The external system port is recognized. Check external system settings and the physical connection to the external system (cables and switches), and fix any problems. When alternate paths are configured for the external system, the following conditions might cause the unknown port status. If that is the case, verify the path configuration and add the required paths, if any.
|
Cannot detect port |
The external path has been removed or the external system port cannot be found. Possible causes are:
|
If you cannot restore the path after checking the possible causes, contact customer support. |
Internal error |
A program error occurred, or there is a logical contradiction. |
Contact customer support. |
Timeout |
Processing was retried after an abnormal reply. However, processing stopped because of a timeout. |
The external system port is recognized. Check external system settings and the physical connection to the external system (cables and switches). |
Device check error |
An external volume is mapped, but you cannot access the volume in the external system. |
Check the status of the volume in the external system and take any necessary corrective action. Format the volume if it is not formatted. |
Medium error |
The external volume has become inaccessible. |
Check the status of the volume in the external system and take any necessary corrective action. Format the volume if it is not formatted. |
Troubleshooting path errors for specific storage systems
The following types of error messages include storage-system-specific recovery information, external device setting changed, illegal request, cannot detect port. If you cannot resolve the issue, contact customer support.
Virtual Storage Platform G200, G400, G600, G800, Virtual Storage Platform F400, F600, F800, Virtual Storage Platform G350, G370, G700, G900, Virtual Storage Platform F350, F370, F700, F900
Path Status |
Description and corrective actions |
External device setting changed |
|
Illegal request or Response error |
|
Cannot detect port |
|
Hitachi Virtual Storage Platform G1x00 and Hitachi Virtual Storage Platform F1500
Path Status |
Description and corrective actions |
External device setting changed |
|
Illegal request or Response error |
|
Cannot detect port |
|
Unified Storage VM, Virtual Storage Platform, and Universal Storage Platform V/VM
Path Status |
Description and corrective actions |
External device setting changed |
|
Illegal request or Response error |
|
Cannot detect port |
|
Universal Storage Platform or TagmaStore NSC
Path Status |
Description and corrective actions |
External device setting changed |
|
Illegal request or Response error |
|
Cannot detect port |
|
Lightning 9900 V
Path Status |
Description and corrective actions |
External device setting changed |
|
Illegal request or Response error |
|
Cannot detect port |
|
Lightning 9900
Path Status |
Description and corrective actions |
External device setting changed |
|
Illegal request or Response error |
|
Cannot detect port |
|
Thunder 9500V
Path Status |
Description and corrective actions |
External device setting changed |
|
Illegal request or Response error |
|
Cannot detect port |
|
HUS/AMS/WMS
Path Status |
Description and corrective actions |
External device setting changed |
|
Illegal request or Response error |
|
Cannot detect port |
|
SVS200
Path Status |
Description and corrective actions |
External device setting changed |
|
Illegal request or Response error |
|
Cannot detect port |
|
Troubleshooting port and volume discovery problems
The following table shows corrective actions you can take for port and volume discovery problems. If you cannot resolve the issue, contact customer support.
Problem |
Corrective action |
The port on the local storage system and port on the external system are not connected. |
Connect the External port of the local system and the external system port. |
The cable for the switch is not connected correctly, or the switch's port is blocked. |
Connect the cable to the correct port on the switch. Or change the port status to the normal status. |
Zoning for the switch is not set appropriately. |
Make sure the zoning configuration allows the External port of the local system to communicate with the external system port. |
External volume returned RESERVATION CONFLICT. |
Release the reserved state of the external volume. |
Port security is set on the external system. |
Cancel the port security setting or change the security of the external system so that the local system can access the port of the external system. |
No LU is configured on the external system port. |
Configure an LU on the port. |
External volume capacity is less than the supported capacity for Universal Volume Manager. |
Perform one of the following:
|
The external volume is configured as a management LU. |
If a management LU, such as Universal Xport LU, is configured on the external system port, perform one of the following:
|
Remote command devices of the external system are cascaded. |
Perform one of the following:
|
External system information retrieved by port discovery is not found in the profile information. |
Perform one of the following:
|
Login to the external system failed. |
Perform one of the following:
|
The external volume is not in Normal status, or a failure or error occurred in retrieving information from the external system. |
Make sure that the status of the external system or the external volume is Normal. |
If none of the actions suggested in the table provide volume discovery, remove the cable connection between the local and external storage systems, and then reconnect the storage systems. After 30 seconds, retry the operation.
Contacting customer support
If you need to contact customer support, provide as much information about the problem as possible, including:
- The circumstances surrounding the error or failure
- The content of any error messages displayed on the host systems
- The content of any error messages displayed on Device Manager - Storage Navigator
- The Device Manager - Storage Navigator configuration information. Use the Dump Tool to get this information.
- The service information messages (SIMs), including reference codes and severity levels, displayed by Device Manager - Storage Navigator
The Hitachi Vantara customer support staff is available 24 hours a day, seven days a week. If you need technical support, log on to the Hitachi Vantara Support Portal for contact information: https://support.hitachivantara.com/en_us/contact-us.html