HP XP20000XP24000 Disk Array - Manual (Page 190)

7-2 Troubleshooting
Hitachi USP V Cross-OS File Exchange User’s Guide
Troubleshooting
For general troubleshooting information on the TagmaStore USP and NSC
subsystems, please refer to the Hitachi TagmaStore Universal Storage
Platform User and Reference Guide
(MK-94RD231) or Hitachi TagmaStore Network Storage Controller User and
Reference Guide (MK-95RD279).
The FAL/FCU software is not expected to fail in any way. When errors are
detected, error codes and messages are displayed and/or logged. Appendix C
lists the FAL and FCU error codes and provides instructions for resolving the
error conditions.
If you have a problem with the FAL/FCU software, first make sure that the
problem is not being caused by other open-system software or hardware, and
try rebooting the open-system server.
For FCU operations, make sure that the FX volume definition file and FCU
initiation parameters are correct. Table 7-1 lists potential error conditions in
FAL/FCU and provides instructions for resolving each condition.
If you are still unable to resolve an error condition, please ask your Hitachi
Data Systems representative for help, or call the Hitachi Data Systems
Support Center for assistance (see section Error Codes and Messages).
Table 7-1 Troubleshooting
Error Condition Recommended Action
UNIX files in non- TagmaStore USP and
NSC subsystem could not be accessed. Make sure that the devices have been mounted. If mounting is done
during an FCU operation, the results cannot be guaranteed because
error information may not be reported to FCU.
Solaris system reports an error indicating
libXm.so.xx is not found. Define a path to the Xmlibrary as follows:
1. For C shell, add the following line to the .cshrc file in the home directory:
setenv LD_LIBRARY_PATH /usr/dt/lib:$LD_LIBRARY_PATH
2. For non-C shell, add the following two lines to the .dtprofile file in the home directory:
LD_LIBRARY_PATH=/usr/dt/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
Windows 2000/2003/Windows NT systems
only:
FCU reports errors when accessing an FCU
parameter definition file.
Remove all space lines from the FCU parameter definition files. FCU
versions 01-01-24 and earlier supported space lines when run without
the GUI. FCU versions 01-01-36 and later do not support space lines.
FCU reports code conversion table errors. If you specified your own code conversion table, make sure that the
file name and path are correct. FCU may also report code conversion
table errors when the FX volume definition file contains both
mainframe and OPEN-xFX volumes. Keep the FXoto volume definition
file separate from the FXmto/otm volume definition file.