KAPL05003-I
|
The HDLM driver (filter component) was successfully attached to Disk (aa...aa), Partition (bb...bb).
|
- Details
The path corresponding to disk aa...aa and partition bb...bb was successfully registered in the core logic.
aa...aa: Disk sequence number (decimal number)
bb...bb: Fixed at 0 (decimal number)
- Action
None.
|
KAPL05008-E
|
Could not allocate memory. (aa...aa:bb...bb) Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility.
|
- Details
aa...aa: File ID, line number, (hexadecimal number)
bb...bb: Memory capture size (hexadecimal number)
- Action
Execute the utility for setting HDLM driver option (dlmsetopt) and increase the number of retries for allocating memory. For details on the dlmsetopt utility, see dlmsetopt utility for setting HDLM driver options. Increase system memory. Stop any unnecessary processes. If the problem is not solved, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras utility for collecting HDLM error information.
|
KAPL05011-E
|
Could not attach the HDLM driver (filter component) to Disk (aa...aa), Partition (bb...bb). (cc...cc:dd...dd) Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility.
|
- Details
The path corresponding to the disk aa...aa and partition bb...bb could not be registered in the core logic.
aa...aa: Disk sequence number (decimal number)
bb...bb: Partition number (decimal number)
cc...cc: Error code (hexadecimal number)
dd...dd: Filter driver management table address (hexadecimal number)
- Action
Check whether the HDLM driver has started normally. If it has not started or contains an error, contact your HDLM vendor or the maintenance company, if there is a maintenance contract for HDLM, and report the error and detail code.
|
KAPL05014-I
|
The device object (aa...aa) was registered as the path (bb...bb).
|
- Details
The HDLM filter driver was successfully attached and registered as a path.
aa...aa: Address of table for managing the HDLM filter driver (hexadecimal number)
bb...bb: Path ID (hexadecimal number)
- Action
None.
|
KAPL05018-W
|
The FO processing in the path (aa...aa) failed. (bb...bb:cc...cc) Check the connection status of the path aa...aa. If there is no problem with the connection status, execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility.
|
- Details
An attempt at FO processing for path aa...aa has failed.
aa...aa: Core logic path identifier for the failed FO (hexadecimal number)
bb...bb: Error code (hexadecimal number)
cc...cc: 0 (fixed)
- Action
The I/O being processed is discarded. Check the status of the device path and resolve the problem accordingly. If there is no problem with the connection status of the path, execute the DLMgetras utility for collecting error information, and then contact the HDLM vendor or the maintenance company if you have a maintenance contract for HDLM.
|
KAPL05019-I
|
The FO processing in the path (aa...aa) finished. The I/O request was processed in the path (bb...bb).
|
- Details
A failure was detected from a lower layer of HDLM during an I/O request. As a result, processing to fail over the path was performed, and the I/O request to the alternative path was successful. I/O requests was processed in the path bb...bb.
aa...aa: Path ID (hexadecimal number)
bb...bb: Path ID (hexadecimal number)
- Action
None.
|
KAPL05020-I
|
Processing of IOCTL(aa...aa) will now start.
|
- Details
An IOCTL request was received.
aa...aa: IOCTL code (hexadecimal number)
- Action
None.
|
KAPL05021-I
|
Processing of IOCTL(aa...aa) completed normally.
|
- Details
The processing for the requested IOCTL operation was successful.
aa...aa: IOCTL code (hexadecimal number)
- Action
None.
|
KAPL05023-E
|
Could not process the IOCTL(aa...aa). (bb...bb:cc...cc) Check the message of the HDLM command or the HDLM manager, and then take the appropriate action. If you do not know the appropriate action, execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company. Refer to the HDLM User's Guide for instructions how to execute the DLMgetras utility.
|
- Details
An attempt to process the requested IOCTL call has failed.
aa...aa: IOCTL code (hexadecimal number)
bb...bb: Error code (hexadecimal number)
cc...cc: Thread ID of the process that issued the I/O
- Action
Check the following. After the check, if the problem is not solved, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM, and then report the error and detail code. For details on the DLMgetras utility, see DLMgetras utility for collecting HDLM error information.
Make sure that the command is executed by a user with root permission.
The memory size is insufficient. Stop the unnecessary process.
Make sure that the IOCTL is not issued to the device management file (/dev/dlm/sddlmfdrv0).
To check whether the error will have any effect on the application, check the application that sent the IOCTL system call.
|
KAPL05701-I
|
HDLM version aa...aa Build bb...bb cc...cc dd...dd ee...ee
|
- Details
The version of HDLM is shown.
aa...aa: HDLM version (character string)
bb...bb: HDLM build number (decimal number)
cc...cc: Days-and-months A.D (character string)
dd...dd: Time in seconds (character string)
ee...ee: Internal code (hexadecimal number) (This is information required for the investigation at the time the problem was generated.)
- Action
None.
|
KAPL05704-E
|
The LDEV information for an HDLM device has changed. HCTL value = aa...aa bb...bb cc...cc dd...dd
|
- Details
The LDEV information for the HCTL value corresponding to an HDLM device has changed.
LDEV information (storage system model name, serial number, and LU number, separated by period)
aa...aa: Host ID (host port number) (decimal number)
bb...bb: Channel number (bus number) (decimal number)
cc...cc: Target ID (target ID) (decimal number)
dd...dd: LUN (host LU number) (decimal number)
- Action
Please perform the following steps.
Note down the HCTL values of the SCSI device as shown in the error messages.
Obtain the corresponding HDLM device name for the HCTL value noted in step 1 by using
the following command:
# dlmcfgmgr -v
Unregister the HDLM devices by using the following command:
# dlmcfgmgr -u logical-device-file-name-of-the-HDLM-device
Reconfigure the HDLM by using the following command:
# dlmcfgmgr -r
|
KAPL05708-E
|
The system retried to allocate memory aa...aa times, but the retries failed. (bb...bb:cc...cc)
|
- Details
aa...aa: Memory allocation retry count (decimal number)
bb...bb: File ID, line number (hexadecimal number)
cc...cc: Memory allocation size (hexadecimal number)
- Action
Execute the utility for setting HDLM driver option (dlmsetopt) and increase the number of retries for allocating memory. For details on the dlmsetopt utility, see dlmsetopt utility for setting HDLM driver options. Increase system memory. Stop any unnecessary processes. If the problem is not solved, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMgetras utility for collecting HDLM error information.
|
KAPL05709-I
|
The system will retry to allocate memory aa...aa times.
|
- Details
aa...aa: Memory allocation retry count (decimal number)
- Action
None.
|
KAPL05711-I
|
The timeout value and retry count of SCSI INQUIRY has been set. (timeout value = aa...aa, retry count = bb...bb)
|
- Details
aa...aa: SCSI INQUIRY timeout value
bb...bb: SCSI INQUIRY retry count
- Action
None.
|
KAPL05713-I
|
The registration status of the reservation key will now be checked.
|
- Details
The registration status of the reservation key will now be checked.
- Action
None.
|
KAPL05714-I
|
The registration status of the reservation key was checked.
|
- Details
The registration status of the reservation key was checked.
- Action
None.
|
KAPL05732-I
|
The I/O of status (aa...aa) and flag (bb...bb) was processed by using path (cc...cc).
|
- Details
aa...aa: I/O status (hexadecimal number) (8 digits starting from 0x, reasons for determining an I/O error)
bb...bb: Flag (hexadecimal number) (16 digits starting from 0x) that was set for the I/O
cc...cc: ID (hexadecimal number) (8 digits starting from 0x) of the path where the I/O was processed
- Action
None.
|
KAPL05819-I
|
Data for maintenance: aa...aa bb...bb cc...cc dd...dd.
|
- Details
The filter driver outputs this message for maintenance.
aa...aa: Maintenance information (hexadecimal number)
bb...bb: Maintenance information (hexadecimal number)
cc...cc: Maintenance information (hexadecimal number)
dd...dd: Maintenance information (hexadecimal number)
- Action
None.
|