HP StorageWorks XP48 Disk Array - Manual (Page 161)

Troubleshooting 161
Table 11-12 Troubleshooting Information: Transaction Log Status (continues on the next pages)
Problem Cause Action required
device file when the host OS
is Linux, raw device
recognition must be released
through manual settings. action, such as executing the following command or
restarting:
echo “scsi remove-single-device a b c
d” > /proc/scsi/scsi
• a: Host ID (host port number)
• b: Channel number (bus number)
• c: Target ID
• d: Lun (host LU number)
Whether VERITAS™ Volume
Manager is used or not, you
are trying to delete a file
system or device file in a
Solaris™ host that is using
Dynamic Link Manager. Whether VERITAS™ Volume Manager is used or
not, if a Solaris™ host is using Dynamic Link
Manager, see the manual for Dynamic Link
Manager, and update the configuration definition file
by executing the
/opt/DynamicLinkManager/bin/
dlmsetconf command and rebooting the system.
If other factors contribute to interruption, remove
them and then resume the setup operation.
To delete a file system or
device file on an HP-UX host,
raw device recognition must
be released through manual
settings. See the OS documentation to execute the ioscan
command.
An automatic setup operation that
had been interrupted in the
background failed. The interruption time limit
accepted by the setup
operation was exceeded. Manually continue the operation that has failed. If
necessary, change the time limit in the Provisioning
Manager property file.
11-3 Troubleshooting Method
If a problem occurs in Provisioning Manager, take the necessary action by following the procedure described
below.
1. Check the problem status. Check the operation status when the problem occurred, and the message that
has been output.
If a dialog is displayed with an error message, follow the corrective action indicated for the message. For
details on the messages, see section
11-6 .
2. When a Device Manager agent error message such as KARF15000-E is output, check the Device
Manager agent error log.
A Device Manager agent error message such as KARF15000-E might be output when an error occurs in
the host. In the message text of such a message, a message ID is not attached. In such a case, view the
Device Manager agent error log (error.log) to identify the message ID, and then investigate the error
cause and troubleshooting. For details on obtaining error log information and investigating the error
cause, see section
11-3-1 .
3. Collect information, such as log information, for investigating the cause.
If the problem cannot be resolved in step 2, use the error information batch collection tool to collect all the
following types of information:
• Error information on the server side
• Error information on the host side
• Information on the state of the host when the error occurred
For information on the error information batch collection tool, see section 11-3-2 .
4. Check the collected information and analyze the problem.
Investigate the error cause based on the collected information. If you cannot correct the problem,. contact
the Support Center.