The FSCSI error number is located in the AAAA AAAA Field of the Sense data
Detail Data SENSE DATA NOTE: Below is a portion of the AIX 5.3 and AIX 6.1 error templates. Click here to see full error template
AIX Version 5.3 and below
RRRR RRRR AAAA AAAA BBBB BBBB CCRR RRRR RRRR YYYY LLLL LLLL LLLL LLLL FFFF FFFF
QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ GGGG GGGG OOOO OOOO OOOO OOOO EEEE EEEE
EEEE EEEE VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV
VVVV VVVV TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT
...continued...
AIX Version 6.1 and above
hhhh hhhh AAAA AAAA BBBB BBBB CCtt vvvv YYYY YYYY LLLL LLLL LLLL LLLL FFFF FFFF
QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ
QQQQ QQQQ
GGGG GGGG pppp pppp OOOO OOOO OOOO OOOO EEEE EEEE EEEE EEEE ssss
ssss ssss ssss
wwww wwww wwww wwww nnnn nnnn nnnn nnnn nnnn qqqq qqqq qqqq
rrrr rrrr rrrr rrrr
MMNN PPSS UUWW XXZZ 11RR 2222 3333 3333 4444 4444 5555
5555 6666 6666 RRRR RRRR
7777 7777 8899 aabb cccc cccc dddd dddd eeee eeee
ffgg iijj mmnn ooRR JJJJ uuuu
%%%% %%%% %%%% %%%% &&&&
&&&& **** **** :::: :::: xxxx yyyy IIII IIII IIII IIII
VVVV
.... continued....
.
| Error number AAAA AAAA |
AIX 5.3 and below | AIX 6.1 and above | Description | Meaning |
|
FSCSI 4 |
FCP_ERR4 |
Command Time-out in SCIOLINQU. dev_info information is included. |
This is seen at device configuration time and the end device is not responding | |
|
FSCSI 4 |
FCP_ERR4 |
Command Time-out in SCIOLSTUNIT. dev_info information is included. |
A LUN in the SAN has not responded to a SCSI start unit command. | |
| 0000 0003 |
FSCSI 4 |
FCP_ERR4 |
Command Time-out in Test Unit Ready IOCTL. dev_info information is included. |
The end device is not responding to a test unit ready command |
|
FSCSI 4 |
FCP_ERR4 |
Command Time-out in Read Block Ioctl. dev_info information is included. |
An SAN end device has not responded to a read block command. | |
| 0000 0005 |
FSCSI 6 |
FCP_ERR6 |
An unexpected SC_Q_CLR buf with no SCSI command was received in strategy. dev_info information is included. |
The AIX FC protocol driver strategy routine has received a clear queue request with no associated SCSI command. |
|
FSCSI 6 |
FCP_ERR6 |
An unknown IOCB type was received in our interrupt handler. |
The AIX protocol driver command completion processor has received an IOCB that it does not know how to process. | |
|
FSCSI 2 |
FCP_ERR2 |
A cancel command failed. The cancel command is included in the error log. |
A cancel command has failed. | |
|
FSCSI 4 |
FCP_ERR4 |
Invalid cmd type for cancel completed. Neither device nor target cancel. target_info information is included |
The AIX protocol driver has detected an issue processing a cancel command, | |
|
FSCSI 4 |
FCP_ERR14 |
Name Server request for all FCP N_Port IDs (SCIOLNMSERV ioctl) was rejected by Name Server. The Name Server's reason code is included. |
A request to the fabric switch name server has been rejected by the name server. | |
|
FSCSI 4 |
FCP_ERR14 |
Name Server request for the N_Port ID of a World Wide Name (SCIOLQWWN ioctl) was rejected by Name Server. The Name Server's reason code is included. |
A request to the fabric switch name server has been rejected by the name server. | |
|
FSCSI 4 |
FCP_ERR14 |
Name Server request for a query of the valid FC classes of an N_Port ID was rejected by Name Server. The Name Server's reason code is included. |
A request to the fabric switch name server has been rejected by the name server. | |
|
FSCSI 4 |
FCP_ERR14 |
FC Classes returned for an N_Port ID are not valid with this adapter. The class mask of this device is returned.is returned in the "BBBB BBBB" field |
The fibre channel class returned is not supported. | |
|
FSCSI 6 |
FCP_ERR6 |
Only logged when debug is turned on. A SCSI_VERSION_1 ioctl call was made with world_wide_name set but with node_name not set. |
This is an informational debug message logged with debug has been turned on. | |
|
FSCSI 6 |
FCP_ERR6 |
A SCSI_VERSION_1 ioctl call was made, and the node_name supplied in the ioctl structure does not match the node_name in the target_info for this device. |
A SCSI version does not match the SCSI version of the target device. | |
|
FSCSI 4 |
FCP_ERR4 |
Only logged when debug is turned on. An LUN reset (SCIOLRESET) ioctl call failed with EINVAL, most likely because LUN reset is not supported for this device, so a target reset was issued instead. |
LUN reset rejected with "invalid argument" | |
| 0000 0011 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_initiate_dyntrk(). | An error was found in an AIX control structure |
| 0000 0012 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_pdisc(). | An error was found in an AIX control structure |
| 0000 0013 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_init_dev_finish(). | An error was found in an AIX control structure |
|
FSCSI 6 |
FCP_ERR6 |
Error on either a SCIOLHALT or SCIOLRESET. cmd element is included The error is the due to non-zero status returned by FCS adapter driver. |
The IOCTL command was rejected by the AIX device driver. | |
|
FSCSI 6 |
FCP_ERR6 |
Error on either a SCIOLHALT or SCIOLRESET. cmd element is included The error is the due to an error reported by the FCS adapter. |
The IOCTL command was returned with an error reported by the adapter | |
|
FSCSI 6 |
FCP_ERR6 |
Error on a interrupt level task management. cmd element is included The error is the due to non-zero status returned by FCS adapter driver. |
Task management command was returned with an error from the adapter | |
|
FSCSI 6 |
FCP_ERR6 |
Error on either a interrupt level task management. cmd element is included The error is the due to an error reported by the FCS adapter or FCP device |
Task management command was returned with an error from the adapter or from the end device. | |
|
FSCSI 6 |
FCP_ERR6 |
Error on issuing a device cancel to the FC adapter driver when trying to retry a SCSI Abort Task Set to a device. dev_info information is included. |
The AIX device driver returned an error when attempting to retry a SCSI Abort Task set to a device. | |
|
FSCSI 6 |
FCP_ERR6 |
output routine failed to accept a SCSI Abort Task that is being retried from the interrupt level.The return code is included. dev_info information is included. |
The AIX device driver has failed to accept the SCSI Abort Task. | |
|
FSCSI 6 |
FCP_ERR6 |
Error on issuing a device cancel when trying to retry a Clear ACA to a device. dev_info information is included. |
The AIX protocol driver received an error issuing a device cancel when trying to retry a SCSI clear ACA to the target device. | |
|
FSCSI 6 |
FCP_ERR6 |
output routine failed to accept a SCSI Clear ACA that is being retried from the interrupt level.The return code is included.dev_info information is included. |
The AIX device driver would not accept from the AIX protocol driver a SCSI Clear ACA for the target device. | |
|
FSCSI 6 |
FCP_ERR6 |
This is an unknown task management request (i.e. not a target reset, abort, nor clear ACA) received by the interrupt handler. cmd is included. |
The AIX protocol driver received an unknown task management request form the AIX interrupt handler. | |
|
FSCSI 6 |
FCP_ERR6 |
A Target reset command that timed out has just been flushed to the FC SCSI Protocol driver. However either a Abort Task Set or Clear ACA is still pending and the cancel command to flush them back has failed.dev_info information is included. |
A target reset command to a device in the SAN has not completed within the time-out period and the cancel command to flush a target abort task or SCSI Clear ACA has failed. | |
|
FSCSI 6 |
FCP_ERR6 |
This is a time-out for unknown task management request (i.e. not a target reset, abort, nor clear ACA). cmd is included |
An unknown task management request has timed out. | |
|
FSCSI 4 |
FCP_ERR4 |
Data overrun reported in FCP response information unit from FCP device, cmd element included |
The end device is indicating that is has more data to send than requested. | |
|
FSCSI 6 |
FCP_ERR6 |
Timeout for an unopen device. N_Port ID is not valid. |
The AIX protocol driver has received a time out for a device that was not open and the N_Port ID is not valid. | |
|
FSCSI 6 |
FCP_ERR6 |
Timeout for an unopen device. N_Port ID/LUN is not valid. target_info information is included. |
The AIX protocol driver has received a time out for a device that was not open and the N_Port/LUN ID is not valid. | |
|
FSCSI 6 |
FCP_ERR6 |
A command completed before it was to be timed out (i.e. the command completed within milliseconds of timing-out). |
The command completed with in milliseconds of the timer expiration. This is an informational only message. | |
|
FSCSI 6 |
FCP_ERR6 |
Timeout for command that is not active. dev_info information is included. |
The AIX protocol driver has received a time out for a command that is not active. | |
|
FSCSI 6 |
FCP_ERR6 |
The cancel for the SCSI abort (due to normal I/O time-out) failed to be issued. dev_info information is included. |
The AIX protocol driver has sent a SCSI abort to the AIX device driver and the cmd failed due to normal I/O time-out. | |
|
FSCSI 6 |
FCP_ERR6 |
The adapter driver's output routine failed when the protocol driver issue a SCSI abort (due to normal I/O time-out)to it. The return code is included.dev_info information is included. |
The AIX protocol driver sent a SCSI abort to the AIX device driver and the SCSI abort failed due to a normal IO time out | |
|
FSCSI 4 |
FCP_ERR4 |
A device cancel timed-out. There are still commands active at the adapter, which were not flushed back. dev_info information is included. |
The protocol driver attempted device cancel has timed out, and commands are still active for the device. | |
|
FSCSI 6 |
FCP_ERR6 |
A device cancel timed-out and the retry of the cancel failed. dev_info information is included. |
The AIX protocol driver received an error when attempting to retry a cancel to a device on SAN | |
|
FSCSI 4 |
FCP_ERR4 |
A target cancel timed-out. target_info information is included. |
The AIX protocol driver has sent a target cancel and it has timed out. The target device information is included in the sense data. | |
|
FSCSI 4 |
FCP_ERR4 |
A relogin issued to the adapter driver's cmd entry point timed out. target_info information is included. |
The AIX protocol driver attempted to re-establish a connection with device in the SAN and the attempt timed out | |
|
FSCSI 4 |
FCP_ERR4 |
A process login (PRLI) or a Port Discover (PDISC) timed-out. target_info information is included. |
The AIX protocol driver has attempted to login into or discover info on a device in the SAN and this attempt has timed out. The N_Port ID of the target device is include in the sense data. | |
|
FSCSI 4 |
FCP_ERR4 |
Proc level task management function (SCIOLRESET) timed-out. command is included |
An AIX Protocol driver task management reset command has timed out. | |
|
FSCSI 4 |
FCP_ERR4 |
Interrupt level task management function (Target Reset) timed-out. command is included |
The AIX protocol driver sent a target reset and a response has not been received from the target. | |
|
FSCSI 6 |
FCP_ERR6 |
Unknown time out id. |
Contact AIX Support | |
|
FSCSI 4 |
FCP_ERR4 |
Data underrun detected by adapter, the command is included. |
The end device is returning less data than the device indicated | |
|
FSCSI 4 |
FCP_ERR4 |
A cancel command timed out, and a reset ring was issued. |
An abort device command has time-out | |
|
FSCSI 2 |
FCP_ERR2 |
Async status received from adapter indicates a complete adapter failure |
Async status received for the AIX device driver indicates that the device driver can no long communicate with the adapter. | |
|
FSCSI 2 |
FCP_ERR2 |
Only logged when debug is turned on. Async status received from adapter driver indicating link is down |
In debug mode, the AIX device driver is indicating that the adapter link is down | |
|
FSCSI 4 |
FCP_ERR4 |
Only logged when debug is turned on. Async status received from adapter driver indicating link is up. |
In debug mode, the AIX device driver is indicating that the adapter link is down | |
|
FSCSI 4 |
FCP_ERR4 |
Only logged when debug is turned on. Async status received from adapter driver indicating a LOGO was received for a device. target_info information is included |
In debug mode, the AIX adapter driver has indicated that the target device has logged out. | |
|
FSCSI 4 |
FCP_ERR4 |
Only logged when debug is turned on. Async status received from adapter driver indicating a PRLO was received for a device. target_info information is included |
In debug mode the AIX device driver has indicated that a device in the SAN has sent a process login request. | |
|
FSCSI 4 |
FCP_ERR4 |
Only logged when debug is turned on. Async status received from adapter driver indicating either a LIP or a global SCN (i.e. segments of the fabric have change status) was received. |
In debug mode the AIX device driver has indicated that a LIP (Loop Initialization Primitive) or a SCN(state Change Notification) was received. (Something has changed in the SAN). | |
|
FSCSI 6 |
FCP_ERR6 |
Unknown async status returned from adapter driver |
The AIX device driver has returned an unknown status. | |
|
FSCSI 4 |
FCP_ERR4 |
Only logged when debug is turned on. Async status received from adapter driver indicating a State Change Notification was received. target_info information is included. |
In debug mode the AIX device driver has indicated that a State Change Notification was received from a device in the SAN | |
|
FSCSI 2 |
FCP_ERR2 |
Only logged when debug is turned on. Async status received from adapter driver indicating link is dead. |
In debug mode the AIX device driver has indicated that the adapter link is down and attempts to bring up the link have failed. | |
|
FSCSI 4 |
FCP_ERR4 |
Only logged when debug is turned on. Async status received from adapter driver indicating a Group or Domain State Change Notification was received. target_info information is included. |
In debug mode the AIX device driver has indicated that it received notification that something has changed in the SAN. | |
|
FSCSI 4 |
FCP_ERR4 |
Only logged when debug is turned on. A target_info was found within the group or domain for which the Group or Domain SCN was received. |
In debug mode the AIX protocol driver has found the target info relating to a change in the SAN. | |
|
FSCSI 2 |
FCP_ERR2 |
Only logged when debug is turned on. The adapter has been halted. |
In debug mode the AIX device driver has indicated that the adapter has been halted by the AIX device driver. | |
|
FSCSI 2 |
FCP_ERR2 |
Only logged when debug is turned on. The adapter has been resumed after being halted. |
In debug mode the AIX device driver has indicated that the adapter has been resumed by the AIX device driver Following being halted by the AIX device driver. | |
|
FSCSI 6 |
FCP_ERR6 |
Ioctl call failed due to the target_info having a stale scsi_id. target_info information is included. |
An command request was failed because the scsi_id used was not current (the scsi_id has changed for the device. scsi_id are controlled by the fabric (switch) in the SAN).. | |
|
FSCSI 6 |
FCP_ERR6 |
Mixed SCIOLSTART version policy. A version 0 SCIOLSTART failed because this target already has at least one LUN started with a version 1 SCIOLSTART. |
The IOCTL version policy of 0 requested does not match the version policy of 1 for the target device.. | |
|
FSCSI 6 |
FCP_ERR6 |
Exclusive SCIOLSTART version policy. A version 0 SCIOLSTART failed because this target already has at least one LUN started with a version 1 SCIOLSTART OR a version 1 SCIOLSTART failed because this target already has at least one lun started with a version 0 SCIOLSTART. |
The IOCTL version policy requested does not match the version policy of the target device | |
|
FSCSI 2 |
FCP_ERR2 |
Adapter dd detected error that indicates HOST IO BUS ERROR. cmd element included |
The AIX device driver has indicated that it has detected a system IO BUS ERROR. | |
|
FSCSI 2 |
FCP_ERR2 |
Adapter dd detected error that indicates adapter hardware failure. cmd element included. |
The AIX device driver has indicated that it has detected an adapter hardware error. | |
|
FSCSI 4 |
FCP_ERR4 |
Adapter dd detected error that indicates adapter software failure. cmd element included. |
AIX has detected an internal software failed. | |
| 0000 0043 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_fail_scsi(). | An error was found in an AIX control structure |
|
FSCSI 4 |
FCP_ERR4 |
Adapter dd detected an unknown error status from the adapter driver.cmd element included. |
The AIX device driver is indicating that it has received and error status that it is not coded to handle. | |
|
FSCSI 4 |
FCP_ERR4 |
Adapter detected an Intermediate Response IOCB entry. cmd element included |
The adapter has received a intermediate response from the target (device on the SAN). | |
|
FSCSI 4 |
FCP_ERR4 |
Adapter reporting an invalid IOCB. cmd element included |
The Adapter has indicated that is has received an invalid IO command from the AIX device driver. | |
|
FSCSI 4 |
FCP_ERR14 |
Adapter reporting either a LS_RJT or BA_RJT from the device for this IOCB. cmd element included |
The adapter has reported that it has received a LS_RJT (link service reject) or a BA_RJT (Basic reject) from a device in the SAN. | |
|
FSCSI 2 |
FCP_ERR2 |
Adapter reporting a DMA error. cmd element included |
The adapter is reporting that it has detected a DMA (direct memory Access) error. | |
|
FSCSI 4 |
FCP_ERR4 |
Adapter reporting an invalid IOCB local status. cmd element included |
The adapter is returning a status the AIX is not coded to handle, If the local status can be found in (local status codes), then open an issue with SAN AIX. . | |
|
FSCSI 4 |
FCP_ERR4 |
Adapter reporting a local status indicating an error was seen on command on the link. |
The adapter has detected damaged or invalid frame from the SAN | |
|
FSCSI 4 |
FCP_ERR4 |
Adapter reporting an unknown IOCB status (status field in IOCB is invalid). cmd element included |
The adapter has detected damaged or invalid frame from the SAN | |
|
FSCSI 2 |
FCP_ERR2 |
Only logged when debug is turned on. Adapter reporting a BSY status. |
In debug mode, the adapter is reporting that it is busy. | |
|
FSCSI 2 |
FCP_ERR2 |
Adapter reporting an undocumented adapter reply status. |
The adapter is returning a status that the AIX device driver is not coded to handle, If the local status can be found in (local status codes), then open an issue with SAN AIX. . | |
|
FSCSI 6 |
FCP_ERR6 |
SCIOLSTART failed because the world_wide_name and/or node_name provided by the caller does not match the world_wide_name/node_name returned from the PLOGI. target_info information is included. |
An application or Hdisk/tape drive has attempted connection to a device and is using an incorrect world name or node-name for the device | |
|
FSCSI 4 |
FCP_ERR4 |
A GEN_REQ IOCB timed out. |
A GEN_REQ that has been sent to the AIX device driver has time-out | |
| 0000 0050 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_cmd_recv(). | An error was found in an AIX control structure |
|
FSCSI 6 |
FCP_ERR6 |
Could not issue Cancel for above failing command which has not received an interrupt. dev_info information is included. |
The AIX device driver has returned an error for a Cancel command sent by the AIX protocol driver.. | |
| 0000 0052 | FSCSI 5 | FCP_ERR6 | WWN of the target has changed and we are in delayed failed mode. | The WWN (World Wide Name) for a device has changed. on the SAN. |
| 0000 0053 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_scsi_elem(). | An error was found in an AIX control structure |
| 0000 0054 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_cancel_elem(). | An error was found in an AIX control structure |
| 0000 0055 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_relogin(). | An error was found in an AIX control structure |
| 0000 0056 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_relogin(). | An error was found in an AIX control structure |
| 0000 0057 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_relogin(). | An error was found in an AIX control structure |
| 0000 0058 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_relogin(). | An error was found in an AIX control structure |
| 0000 0059 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_prlog_elem(). | An error was found in an AIX control structure |
| 0000 005A | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_prlog_elem() | An error was found in an AIX control structure |
| 0000 005B | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_task_mgm_cmd(). | An error was found in an AIX control structure |
| 0000 005C | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_task_mgm_to(). | An error was found in an AIX control structure |
| 0000 005D | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_process_adapter_error(). | An error was found in an AIX control structure |
| 0000 005E | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_timeout(). | An error was found in an AIX control structure |
| 0000 005F | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_watchdog(). | An error was found in an AIX control structure |
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
Call to adapter driver's control entry point failed to accept N_Port Login for a device. The return code is included. cmd element included |
The AIX device driver has failed a request from the AIX protocol driver. | |
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
The device and SCSI protocol adapter do not support the same FC class, the device's FC class mask is included in the rc field. target_info information included |
The device does not support the AIX Protocol driver requested FC class. | |
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
output routine failed to accept PRLI IOCB for a device during an SCIOLSTART. The return code is included. dev_info information included. |
The AIX device driver failed a process login request from the AIX protocol driver. | |
| 0000 0063 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() with status code NDD_HARD_FAIL | An error was found in an AIX control structure |
| 0000 0064 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() with status code NDD_STATUS. | An error was found in an AIX control structure |
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
output routine failed to accept SCIOLHALT IOCB for a device. The return code is included. dev_info information included. |
The AIX device driver failed a device halt from the AIX protocol driver | |
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
output routine failed to accept SCIOLRESET IOCB for a device. The return code is included. dev_info information included. |
The AIX device driver failed a device reset request from the AIX protocol driver. | |
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
output routine failed to accept Clear ACA IOCB (SC_CLEAR_ACA in strategy) for a device. The return code is included. dev_info information included. |
The AIX device driver failed a device Clear ACA request from the AIX protocol driver. |
|
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
output routine failed to accept Abort IOCB (SC_Q_CLR in strategy)for a device. The return code is included. dev_info information included. |
The AIX device driver failed an abort request from the AIX protocol driver | |
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
output routine failed to accept Clear ACA IOCB (SC_Q_RESUME|SC_CLEAR_ACA in strategy) for a device. The return code is included dev_info information included. |
The AIX device driver failed a device Clear ACA request from the AIX protocol driver |
|
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
output routine failed to accept normal I/O SCSI IOCB for a device. The return code is included. command is included |
The AIX adapter device driver has rejected a protocol driver request | |
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
output routine failed to accept device Cancel IOCB for a device. The return code is included. dev_info information included. |
The AIX adapter device driver has rejected a Cancel request for the AIX protocol driver. | |
|
FSCSI 6 |
FCP_ERR6 |
output routine failed to accept target Cancel IOCB for a device. The return code is included. target_info information included. |
The AIX adapter device driver has rejected a Cancel form the AIX protocol driver. | |
|
FSCSI 6 |
FCP_ERR6 |
output routine failed to accept process login IOCB for a device. The return code is included. cmd included |
The AIX adapter device driver has rejected a process login request from the AIX protocol driver. | |
|
FSCSI 6 |
FCP_ERR6 |
output routine failed to accept target reset IOCB for a device. The return code is included. target_info is included. |
The AIX adapter device driver has rejected a target reset request from the AIX protocol driver | |
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
output routine failed to accept cancel IOCB for a target. The return code is included. target_info is included. |
The AIX adapter device driver has rejected a target Cancel request from the AIX protocol driver. | |
|
FSCSI 2 |
FCP_ERR2 |
We timed out waiting for link to come up. |
The AIX protocol driver received a time-out waiting for notification that the link has been established. | |
|
FSCSI 2 |
FCP_ERR2 |
We timed out waiting for the adapter to resume. |
The AIX protocol driver has received a time-out waiting for notification that the adapter is ready to resume. | |
| 0000 0072 | FSCSI 6 | FCP_ERR6 | The IOCB's io_tag does not match the ctl_elem's io_tag | The io tag the AIX protocol driver used in the IOCB does not match the io tag in the AIX ctl_elem structure. This is a corrupted IOCB. a corrupted AIX ctl_elem structure. |
| 0000 0073 | FSCSI 6 | FCP_ERR6 | Unsolicited IOCB received | The AIX protocol driver has received and IOCB that was not requested. |
| 0000 0074 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() | An error was found in an AIX control structure |
| 0000 0075 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() | An error was found in an AIX control structure |
| 0000 0076 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() | An error was found in an AIX control structure |
| 0000 0077 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() | An error was found in an AIX control structure |
| 0000 0078 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() | An error was found in an AIX control structure |
| 0000 0079 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() | An error was found in an AIX control structure |
| 0000 007a | FSCSI2 | FCP_ERR2 | Only logged when debug is turned on. The FC adapter driver is indicating the adapter was reset. | In debug mode, the AIX device driver has indicated that it has reset the adapter. This is a debug informational only message |
| 0000 007b | FSCSI2 | FCP_ERR2 | Only logged when debug is turned on. The FC adapter driver received a FARP (FC ARP) from the SCSI ID specified in the error number field. | In debug mode, the AIX device driver has indicated that it has received and FC ARP (Fibre Channel Address Resolution Protocol) request from the SAN. This is a debug informational only message |
| 0000 007C | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() | An error was found in an AIX control structure |
| 0000 007D | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() | An error was found in an AIX control structure |
| 0000 007E | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat() | An error was found in an AIX control structure |
|
FSCSI 4 |
FCP_ERR4 or FCP_ERR6 |
output routine failed to accept lun reset. The return code is included. target_info is included. |
The AIX device driver has rejected a lun reset request from theAIX protocol driver. | |
| 0000 0080 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_async_stat(). | An error was found in an AIX control structure |
| 0000 0081 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_add_dev_scsi(). | An error was found in an AIX control structure |
| 0000 0083 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_ioctl_setup(). | An error was found in an AIX control structure |
| 0000 0084 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_ioctl_setup(). | An error was found in an AIX control structure |
| 0000 0085 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_ioctl_setup(). | An error was found in an AIX control structure |
| 0000 0086 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for cmd_elem in routine efsc_stale_target(). | An error was found in an AIX control structure |
| 0000 0087 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for cmd_elem in routine efsc_process_scsi_elem(). | An error was found in an AIX control structure |
| 0000 0088 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_initiate_dyntrk(). | An error was found in an AIX control structure |
| 0000 0089 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_dyntrk_failed(). | An error was found in an AIX control structure |
| 0000 008A | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_stale_target(). | An error was found in an AIX control structure |
| 0000 008B | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_plogi(). | An error was found in an AIX control structure |
| 0000 008C | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for cmd_elem in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 008D | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_send_prlog(). | An error was found in an AIX control structure |
| 0000 008E | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_send_prlog(). | An error was found in an AIX control structure |
| 0000 008F | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_send_prlog(). | An error was found in an AIX control structure |
| 0000 0090 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_send_prlog(). | An error was found in an AIX control structure |
| 0000 0091 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_send_prlog(). | An error was found in an AIX control structure |
| 0000 0092 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for cmd_elem in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 0093 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for cmd_elem in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 0094 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_send_target_reset(). | An error was found in an AIX control structure |
| 0000 0095 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_semd_target_reset(). | An error was found in an AIX control structure |
| 0000 0096 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_fail_scsi(). | An error was found in an AIX control structure |
| 0000 0097 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for scsi_info in routine efsc_strategy(). | An error was found in an AIX control structure |
| 0000 0098 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_strategy(). | An error was found in an AIX control structure |
| 0000 0099 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_strategy(). | An error was found in an AIX control structure |
| 0000 009A | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_start(). | An error was found in an AIX control structure |
| 0000 009B | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_cancel_elem(). | An error was found in an AIX control structure |
| 0000 009C | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_cancel_elem(). | An error was found in an AIX control structure |
| 0000 009D | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_pdisc(). | An error was found in an AIX control structure |
| 0000 009E | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_pdisc(). | An error was found in an AIX control structure |
| 0000 009F | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_pdisc(). | An error was found in an AIX control structure |
|
FSCSI 4 |
FCP_ERR12 |
A command entry point command was returned from the adapter with an error. This command was for an IOCTL N_Port Login. target_info is included |
The AIX device driver has rejected a login to a device in the SAN. | |
|
FSCSI 4 or |
FCP_ERR12 or FCP_ERR6 |
A command entry point relogin command was returned from the adapter with an error. This relogin was issued from the interrupt level as part of error recovery. target_info is included |
The AIX device driver has rejected a request to re login to a device in the SAN. | |
|
FSCSI 4 |
FCP_ERR14 |
A command entry point relogin command returned successfully, but the device at this N_Port ID is different (i.e a different port name or node name) target_info is included |
The successful response for the device in the SAN to a re-login show a different N_Port_ID from the last login. | |
|
FSCSI 4 |
FCP_ERR4 |
A Reset Ring on the SCSI IOCB ring failed |
The adapter has failed a reset ring. | |
|
FSCSI 6 |
FCP_ERR6 |
Unknown cmd was sent from the adapter driver to protocol driver |
The AIX device driver has sent a command to the AIX protocol driver that the AIX protocol driver is not coded to handle. | |
|
FSCSI 6 |
FCP_ERR12 |
Send Sequence failed, The cmd is included. |
The AIX device driver has retuned with an error a send sequence request from the AIX protocol driver. | |
|
FSCSI 4 |
FCP_ERR4 |
Only displayed with debug driver, indicates someone has asked to restart this device. Target info is included |
In debug mode the AIX protocol driver has received a request to restart a device. This is an information debug message. | |
|
FSCSI 4 |
FCP_ERR4 |
Only displayed with debug driver, indicates target reset has been issued. Target info is included |
In debug mode the AIX protocol driver has been requested to reset a target. This is an information debug message. | |
|
FSCSI 4 |
FCP_ERR4 |
Only displayed with debug driver, indicates lun reset has been issued. Target info is included |
In debug mode, the AIX protocol driver has received a lun reset request. This is an information debug message. | |
|
FSCSI 6 |
FCP_ERR6 |
Only displayed with debug driver, indicates that the attempt to xmalloc the internal global trace table failed. Size of attempted xmalloc is in BBBB BBBB field. |
In debug mode, an AIX to get system memory for a trace table has failed. | |
|
FSCSI 4 or |
FCP_ERR12 or FCP_ERR6 |
A command entry point GEN_REQ command was returned from the adapter with an error. This GEN_REQ was issued from the interrupt level as part of error recovery. target_info is included. |
The AIX device driver has returned a with a an error a request from the protocol driver for a Gen _request to a device in the SAN | |
|
FSCSI 6 |
FCP_ERR6 |
The GID_PN response buffer was not big enough to return the N_Port ID. |
The buffer provided for a GID_PN was not large enough to return the N_Port ID | |
|
FSCSI 4 |
FCP_ERR4 |
A GID_PN or GPN_ID name server query initiated during an ioctl call failed. Reason code and explanation included. |
A GID_PN or GPN_ID name sever request (a request sent to the SAN switch Name Server) was rejected by the SAN switch name server. | |
|
FSCSI 4 |
FCP_ERR12 |
A dynamic tracking operation, either a GID_PN, PLOGI, PDISC, relogin with the name server, failed. Failing this iteration of dynamic tracking or fast fail error recovery. target_info is included. |
A GID_PN, PLOGI, or PDISC request from AIX dynamic tracking has been returned
from the SAN switch Name Server with an error. NOTE: This error stores an errno value in the BBBB BBBB field |
|
|
FSCSI 4 |
FCP_ERR14 |
An interrupt-level GID_PN, part of dynamic tracking or fast fail error recovery, was rejected by the name server, most likely because the device is not on the fabric. Reason code/explanation and target_info included. |
A GID_PN request from AIX dynamic tracking has been returned from the SAN switch Name Server with an error. | |
|
FSCSI 6 |
FCP_ERR6 |
Adapter driver's cmd entry point rejected a reset ring. |
The AIX device driver has rejected a ring reset from the AIX protocol driver. | |
|
FSCSI 4 or |
FCP_ERR4 or FCP_ERR6 |
Adapter driver's cmd entry point rejected a relogin (PLOGI) operation. target_info is included. |
The AIX device driver has rejected a relogin request from the AIX protocol driver. | |
|
FSCSI 4 or FSCSI 6 |
FCP_ERR4 or FCP_ERR6 |
Adapter driver's cmd entry point rejected a pdisc. target_info is included. |
The AIX device driver has rejected a n_port discovery request from the AIX protocol driver. | |
|
FSCSI 6 |
FCP_ERR6 |
Dynamic Tracking is enabled, and the scsi_buf passed in from the head driver did not set the kernext_handle field. |
With AIX dynamic tracking enabled, the scsi buffer passed to the AIX protocol driver indicates that the target device is not set up to support dynamic tracking | |
|
FSCSI 4 or FSCSI 6 |
FCP_ERR4 or FCP_ERR6 |
Adapter driver's cmd entry point rejected a move_login. target_info is included. |
The AIX device driver has rejected a move login request from the AIX protocol driver. | |
|
FSCSI 4 or FSCSI 6 |
FCP_ERR4 or FCP_ERR6 |
A relogin (PLOGI) with the name server failed and the relogin retry count has been exceeded. |
An AIX protocol driver login request to the SAN switch Name Server has failed. | |
|
FSCSI 4 or FSCSI 6 |
FCP_ERR4 or FCP_ERR6 |
Adapter driver's cmd entry point rejected a send sequence. |
The AIX device driver has rejected an AIX protocol driver send sequence request. | |
|
FSCSI 6 |
FCP_ERR4 or FCP_ERR6 |
Adapter driver's cmd entry point rejected a gen_req. target_info is included. |
The AIX device driver has rejected a target device get_req request from the AIX protocol driver. | |
|
FSCSI 6 |
FCP_ERR6 |
Unable to sync up target_infos and dev_infos after a dynamic tracking event because the new alt_scsi_id value field in the target_info is set to 0. |
Following an AIX dynamic tracking event, the AIX target information and AIX device information are out of sync. | |
|
FSCSI 6 |
FCP_ERR6 |
Only logged when debug is turned on. The old and new scsi_id values after a dynamic tracking event are the same. Most likely cable moved back to original place on fabric during a given dynamic tracking iteration. |
In debug mode, Following an AIX dynamic tracking event, the AIX scsi old and new id values are the same. This is debug informational only message. | |
|
FSCSI 4 |
FCP_ERR14 |
A GID_PN response from the name server claims to have succeeded but returned an N_Port ID of 0 for this world wide name. |
The SAN switch Name Sever has responded to the AIX protocol driver with an N_Port_ID of 0 on a GID_PN request. | |
|
FSCSI 6 |
FCP_ERR6 |
An SCN was received while a move_login operation was in progress OR world_wide_name and/or node_name returned from the move_login does not match those of this target_info. target_info included. |
While process an AIX move login, the AIX protocol driver has received a State Change Notification from the SAN or the World Wide Name from the move login does not match the AIX target information. (Something has changed in the SAN). | |
|
FSCSI 4 or FSCSI 6 |
FCP_ERR4 or FCP_ERR6 |
A move_login operation was failed by the adapter driver. Error status and target_info included. |
The AIX device driver has failed a move login request from the AIX protocol driver. | |
|
FSCSI 6 |
FCP_ERR6 |
Adapter driver returned good status for a move_login operation but the rpi returned is set to 0. |
The rpi returned for a move_login operation was 0. | |
|
FSCSI 6 |
FCP_ERR6 |
The world_wide_name and/or node_name fields of the target_info and scsi_sciolst structures after an SCIOLSTART do not match. |
Following a AIX protocol start request, the World Wide Name and/or node name fields in the AIX target information and the AIX scsi IO list structure.do match. | |
|
FSCSI 2 |
FCP_ERR2 |
PRLI failed. command is included. |
A process login from the AIX Protocol driver to a device in the SAN has failed. | |
|
FSCSI 6 |
FCP_ERR6 |
The scsi_id of this target has changed and either a non-SC_DEV_RESTART was received or dynamic tracking is not enabled for this target. rc field contains scsi_buf flags setting. |
The SAN target device scsi id (N_Port ID) has changed. and dynamic tracking is not enabled or a non restart cmd to the device has been received by the AIX protocol driver. | |
|
FSCSI 6 |
FCP_ERR6 |
Only logged when debug is turned on. A target_info was found with a stale scsi_id after the completion of a GID_PN, GPN_ID, PLOGI or move_login. |
In debug mode, the AIX target info had a scid_id that was not current Following a move login, get ID, get PN or port login completion. | |
|
FSCSI 6 |
FCP_ERR6 |
Attempt to add a target_info to the hash tables during an SCIOLSTART, but there is already a target_info in our hash tables with this world_wide_name. |
An attempt to add a AIX target info to an AIX hash table found the target info already in the table. | |
|
FSCSI 6 |
FCP_ERR6 |
Only logged when debug is turned on. A heuristic match was made for the dev_info lookup during an ioctl call, most likely due to stale target_infos/dev_infos for devices that could not be tracked after dynamic tracking events. |
In debug mode,A heuristic match was made in a device info lookup. This was most likely due to a change in the SAN on a device that does not support dynamic tracking, This is a debug informational only message. | |
|
FSCSI 6 |
FCP_ERR6 |
Multiple matches for dev_info lookup during an ioctl call, and a unique match could not be made. |
There were multiple AIX matched for AIX device info lookup in AIX structure and a unique match could not be made | |
|
FSCSI 6 |
FCP_ERR6 |
Tried to perform dynamic tracking operations during an ioctl call for a target_info that is not dynamic tracking capable. |
AIX dynamic tracking was invoke for a SAN device that does not support dynamic tracking | |
|
FSCSI 6 |
FCP_ERR6 |
An attempt to issue a move_login from the ioctl thread failed. |
A request to move a login for a device in the SAN was sent to the AIX protocol driver and has failed | |
|
FSCSI 6 |
FCP_ERR6 |
Dynamic tracking operation that ioctl thread was sleeping on failed. |
An AIX dynamic tracking operation has failed. | |
|
FSCSI 6 |
FCP_ERR6 |
The world_wide_name and/or node_name fields passed in the ioctl structure and those in the target_info do not match after a dynamic tracking event. |
Following a dynamic tracking event. an AIX request was received by the AIX protocol driver and the requested world wide name and/or node name fields did not match the info in the AIX target info. (Following a change in the SAN, and a dynamic tracking operation to handle the change, not all AIX structures have been updated). | |
|
FSCSI 6 |
FCP_ERR6 |
Only logged when debug is turned on. An ioctl thread has been woken up from sleeping on a dynamic tracking event, and a name server query is still needed. A retry is suggested if retry count has not been exceeded. |
In debug mode, the program thread waiting on a dynamic operation has resumed. This is a debug informational only message. | |
|
FSCSI 4 |
FCP_ERR4 |
A GID_PN was issued and completed for a target that had an outstanding MOVE_LOGIN operation. As such, the GID_PN results were ignored. |
A Get ID request to the SAN switch name server has completed for a target device that is in the process of having the device login moved. This is an informational only message. | |
|
FSCSI 6 |
FCP_ERR6 |
Ioctl call failed because internal ioctl_setup_info structure fields are not set up consistently. This is a driver programming error. |
A AIX request to the AIX protocol driver has failed due to setup info structure inconsistencies. | |
|
FSCSI 6 |
FCP_ERR6 |
The world_wide_name and/or node_name returned from the PLOGI during an SCIOLSTART do not match those of the target_info or of the scsi_sciolst structure passed in by the caller. |
An N Port login, (login to a device in the SAN) returned with the world wide name and/or node name that does match the information in the AIX target info or the scsi io list structure. (Something has changed in the SAN). | |
|
FSCSI 6 |
FCP_ERR6 |
Only logged when debug is turned on. A target_info was found with a stale scsi_id after the completion of a GID_PN, GPN_ID, PLOGI or move_login. |
In debug mode, AIX target info was found to be out of sync Following a
Get ID, Get port name or move login, (Something has changed in the SAN) |
|
|
FSCSI 6 |
FCP_ERR6 |
A scsi_id change was detected during an ioctl call that did not have world_wide_name set, yet no dynamic tracking events occurred. This is a driver programming error. |
A scsi id (N_Port ID) change was detected on an AIX request to the AIX protocol driver to set the whorl wide name. | |
|
FSCSI 6 |
FCP_ERR6 |
Strategy received a scsi_buf with no scsi command length and it is not a queue error recovery command. |
The AIX protocol driver received an AIX scsi buffer without a command length specified. | |
|
FSCSI 6 |
FCP_ERR6 |
Interrupt handler received an interrupt for an inactive command. The command is logged. |
The AIX protocol driver received a interrupt for a command that was not active | |
|
FSCSI 6 |
FCP_ERR6 |
The kernext_handle passed in with this scsi_buf is invalid. |
An AIX scsi buffer was passed to the AIX protocol driver with a kernext handle field that had an invalid value. | |
|
FSCSI 10 |
FCP_ERR10 |
Dynamic Tracking is enabled and a legacy version 0 ioctl call was made
to the protocol driver. Should consider: |
With Dynamic tracking enabled, the AIX protocol driver received a request for a device that does not support dynamic tracking. | |
|
FSCSI 6 |
FCP_ERR6 |
An SC_DEV_RESTART scsi_buf was sent by head driver and either the SC_Q_CLR flag was not set or a scsi_command was included in the scsi_buf, neither of which is valid. |
An AIX disk driver sent a request to the AIX protocol driver fields in the request were not set or were invalid. | |
|
FSCSI 6 |
FCP_ERR6 |
A move_login is in progress for a target_info but the scsi_id is not marked as stale. This is a dynamic tracking programming error. |
A move login was sent to the AIX protocol driver with a error in the AIX target info structure. | |
|
FSCSI 6 |
FCP_ERR6 |
Attempt to issue a PDISC failed because the scsi_id is stale for this target_info. |
An N Port discover command failed due to a N port ID that is not current. (Something has changed in the SAN). |
|
|
FSCSI 6 |
FCP_ERR6 |
An RSCN was received and no dynamic tracking operations were in progress, but the GID_PN delay timer id was set. target_info included. |
An AIX timer has been started for a dynamic tracking event, but no dynamic events are in progress. | |
|
FSCSI 6 |
FCP_ERR6 |
An Domain or Group SCN was received and no dynamic tracking operations were in progress, but the GID_PN delay timer id was set for a target_info. target_info included. |
While processing a State Change Notification, a dynamic tracking timer was set, but not dynamic tracking operations were in progress. | |
|
FSCSI 10 |
FCP_ERR10 |
Dynamic Tracking or Fast Fail is enabled, but the adapter firmware or the SAN configuration does not support these features. |
The AIX Dynamic Tracking and Fast Fail features are enabled , but the adapter firmware or devices in the SAN do not appear to support these functions. | |
|
FSCSI 6 |
FCP_ERR6 |
An LOGO was received and no dynamic tracking operations were in progress, but the GID_PN delay timer id was set. target_info included. |
While processing a logout a dynamic tracking timer was set, but not dynamic tracking operations were in progress. | |
|
FSCSI 6 |
FCP_ERR6 |
Attempt to issue a relogin failed because the scsi_id is stale for this target_info. |
An AIX request to re login to a device in the SAN failed because the scsi id ( n port ID ) was not current. (Something has changed in the SAN) | |
|
FSCSI 6 |
FCP_ERR6 |
Only logged when debug is turned on. An SC_DEV_RESTART scsi_buf was sent by head driver but the scsi_id for this target is not stale. |
in debug mode, a restart device command was received for a target and the scis_id appears to be current. | |
|
FSCSI 6 |
FCP_ERR6 |
Tried to search target_infos for those with a stale scsi_id, but don't have either scsi_id or world_wide_name information for comparison. |
A AIX search target request was made, but the required AIX search info was not provided. | |
| 0000 00de | FSCSI 6 | FCP_ERR6 | The func that iodones a dev_restart command was called with NULL dev_restart. | The AIX protocol driver received an AIX request without a device restart command. |
| 0000 00df | FSCSI 6 | FCP_ERR4 | The SCN is received from the name server. | The SAN switch name server sent a state change notification. (something has changed in the SAN) this is an informational only messages. |
| 0000 00e0 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_ioctl_setup(). | An error was found in an AIX control structure |
|
FSCSI 6 |
FCP_ERR6 |
Only logged when debug is turned on. An ioctl call was made using scsi_id and not world_wide_name, and the scsi_id for the target_info initially looked up has changed. Retry tracking operations in this ioctl thread if retry count has not been exceeded. target_info included. |
In debug mode, An request from AIX was made with a scsi_id and a lookup has of the target info indicates that the scsi_id has changed. This is a debug informational only message. | |
|
FSCSI 4 or FSCSI 6 |
FCP_ERR4 or FCP_ERR6 |
Adapter driver's cmd entry point rejected a send els. |
The AIX device driver rejected a send extend link service command, | |
| 0000 00e3 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for target_info in routine efsc_ioctl_setup(). | An error was found in an AIX control structure |
|
FSCSI 4 |
FCP_ERR4 |
Too many dynamic tracking attempts during this ioctl call. |
The were too many path recovery attempts while servicing a IOCTL, this indicates instability in the SAN. | |
|
FSCSI 6 |
FCP_ERR6 |
Only logged when debug is turned on. The scsi_id for this SCIOLSTART and the scsi_id we have recorded for this adapter are the same, so we fail the SCIOLSTART if dynamic tracking is turned off. |
In debug mode, The start command is starting a device with a SCSI id that is already started., the cmd is failed if dynamic tracking is turned off. This is a debug informational only message. | |
| 0000 00e6 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_pdisc(). | An error was found in an AIX control structure |
| 0000 00e7 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_relogin(). | An error was found in an AIX control structure |
| 0000 00e8 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_relogin(). | An error was found in an AIX control structure |
| 0000 00e9 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_relogin(). | An error was found in an AIX control structure |
| 0000 00ea | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_prlog_elem(). | An error was found in an AIX control structure |
| 0000 00eb | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_prlog_elem(). | An error was found in an AIX control structure |
| 0000 00ec | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_prlog_elem(). | An error was found in an AIX control structure |
| 0000 00ed | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_prlog_elem(). | An error was found in an AIX control structure |
| 0000 00ee | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_gid_req(). | An error was found in an AIX control structure |
| 0000 00ef | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_gid_pn(). | An error was found in an AIX control structure |
|
FSCSI 6 |
FCP_ERR6 |
Strategy received an unsupported scsi_buf. dev_info information is included. |
The AIX protocol driver has received a request from an AIX hdisk driver that had an unsupported scsi buffer. | |
| 0000 00f1 | FSCSI 4 | FCP_ERR4 | Couldn't get resources for event buffer. xmalloc failed. | The AIX protocol driver was unable to get AIX memory for and AIX event buffer. |
| 0000 00f2 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_gid_pn(). | An error was found in an AIX control structure |
| 0000 00f3 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_gid_pn(). | An error was found in an AIX control structure |
| 0000 00f4 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_task_mgm_cads(). | An error was found in an AIX control structure |
| 0000 00f5 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_task_mgm_to(). | An error was found in an AIX control structure |
| 0000 00f6 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_process_task_mgm_to(). | An error was found in an AIX control structure |
| 0000 00f7 | FSCSI 6 | FCP_ERR6 | the adapter has reported underrun error. | The adapter has received less data from a device on the SAN than expected |
| 0000 00f9 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_clenup_target_cancel(). | An error was found in an AIX control structure |
| 0000 00fa | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_dyntrk_failed(). | An error was found in an AIX control structure |
| 0000 00fb | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 00fc | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 00fd | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 00fe | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 00ff | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 0101 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 0104 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 0106 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_async_stat(). | An error was found in an AIX control structure |
| 0000 0107 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_hash_dev(). | An error was found in an AIX control structure |
| 0000 010a | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_move_devs(). | An error was found in an AIX control structure |
| 0000 010b | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_dump_write(). | An error was found in an AIX control structure |
| 0000 010d | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_issue_prlog(). | An error was found in an AIX control structure |
| 0000 010f | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for dev_info in routine efsc_issue_prlog(). | An error was found in an AIX control structure |
| 0000 0120 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for scsi_info in routine efsc_strategy(). | An error was found in an AIX control structure |
| 0000 0121 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for scsi_info in routine efsc_cmd_recv(). | An error was found in an AIX control structure |
| 0000 0122 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for scsi_info in routine efsc_efsc_recv(). | An error was found in an AIX control structure |
| 0000 0123 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for scsi_info in routine efsc_async_timeout(). | An error was found in an AIX control structure |
| 0000 0124 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for scsi_info in routine efsc_watchdog(). | An error was found in an AIX control structure |
| 0000 0125 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for scsi_info in routine efsc_async_stat(). | An error was found in an AIX control structure |
| 0000 0126 | FSCSI 5 | FCP_ERR5 | The eyecatcher test failed for scsi_info in routine efsc_cdt_func(). | An error was found in an AIX control structure |
| 0000 01e0 | N/A | FCP_ERR6 | One of the routines to initialize live dump failed. Live dump may not work or may not be complete | An AIX live dump routine completed with an error |
| 0000 01e1 | N/A | FCP_ERR6 | Routine to configure live dump failed. Live dump will not be taken | An AIX live dump configuration routine has completed with an error. |
| 0000 01e3 | N/A | FSCSI 10 | An SCIOLSTOP is being done by an application that still has an active SCIOLSTART associated with a kernel extension. Information about the process that is doing this is logged. | This would be a software defect. Collect detailed traces Component Traces from the device drivers using FC (e.g., disk driver, tape driver, etc) and collect any logs from the application that made the STOP request (identified by PID in the SENSE DATA). |
| 0000 01e6 | N/A | FCP_ERR10 | A stop initiator ioctl is being done by an application, but the original start initiator was done by a kernel extension. Information about the process that is doing this is logged. | |
| 0000 0200 | N/A | FCP_ERR6 | An attempt to register the npiv_getfcn failed. | |
| 0000 0201 | N/A | FCP_ERR6 | An attempt to unregister the npiv_getfcn failed. | |
| 0000 0300 | N/A | FCP_ERR6 | When attempting to send a SCSI command on behalf of an NPIV client, we found that it's opcode was invalid (apparently altered after it was issued to the driver). | |
| 0000 0301 | N/A | FCP_ERR6 | A request received in the npiv_scsi entry point has an invalid opcode. | |
| 0000 0302 | N/A | FCP_ERR4 or FCP_ERR6 | A request received in the npiv_scsi entry point is being failed by the adapter drivers output entry point. | |
| 0000 0320 | N/A | FCP_ERR2 | A SCSI request from an NPIV client has failed with a HOST_IO_BUS error. | |
| 0000 0321 | N/A | FCP_ERR2 | A SCSI request from an NPIV client has failed with an adapter hardware error | |
| 0000 0322 | N/A | FCP_ERR6 | A SCSI request from an NPIV client has failed with an adapter software error. | |
| 0000 0323 | N/A | FCP_ERR6 | A SCSI request from an NPIV client has been failed from the adapter driver with an unknown status. | |
| 0000 0324 | N/A | FCP_ERR4 | A SCSI request from an NPIV client has been failed by the adapter with an Intermediate Response Error | |
| 0000 0325 | N/A | FCP_ERR2 | A SCSI request from an NPIV client has been failed by the adapter because of a DMA error | |
| 0000 0326 | N/A | FCP_ERR4 | A SCSI request from an NPIV client has been failed by the adapter. | See reply IOCB for exact reason |
| 0000 0327 | N/A | FCP_ERR4 | A SCSI request from an NPIV client has been failed by the adapter. | See reply IOCB for exact reason |
| 0000 0328 | N/A | FCP_ERR6 | A SCSI request from an NPIV client has been failed by the adapter with an unknown local reject parameter field. | |
| 0000 0329 | N/A | FCP_ERR6 | A SCSI request from an NPIV client has been failed by the adapter with an unknown status value. | |
| 0000 032a | N/A | FCP_ERR6 | When callin the cmd_done function for an NPIV SCSI request, it was failed. | |
| 0000 032b | N/A | FCP_ERR6 | An NPIV SCSI request did not have a non-null cmd_done function address. | |
| 0000 0330 | N/A | FCP_ERR4 or FCP_ERR6 | When attempting to send a request from the npiv_admin entry point to the adapter driver's cmd entry point, it was failed. | |
| 0000 0335 | N/A | FCP_ERR6 | An npiv_admin completed with an unknown local reject parameter field. | |
| 0000 0340 | N/A | FCP_ERR6 | When callin the cmd_done function for an NPIV ADMIN request, it was failed. | |
| 0000 0341 | N/A | FCP_ERR6 | An NPIV admin request did not have a non-null cmd_done function address. | |
| 0000 0349 | N/A | FCP_ERR6 | When an EFC_MOVE_LOGIN or EFC_RELOGIN request built on behalf of an npiv_admin request completes it does not have a valid target_info. | |
| 0000 0350 | N/A | FCP_ERR6 | An invalid option[0] status was received for an NPIV client | |
| 0000 0351 | N/A | FCP_ERR6 | An invalid statblk->code was received for an NPIV client. | |
| 0000 0360 | N/A | FCP_ERR6 | An attempt to send async status back to the NPIV client was failed. | |
| 0000 0a30 | N/A | FSCSI_6 | A cancel for the command entry point failed with the status logged here. | |
| 0000 0b01 | N/A | FSCSI_6 | Sending an EFC_CANCEL request to the adapter driver's command entry point was failed. | |
| 0000 0d01 | N/A | FCP_ERR5 | A stop initiator ioctl is being done for an NPIV/initiator without a valid eyecatcher. This most likely indicates this NPIV is already stopped. | |
| 0000 0d02 | N/A | FCP_ERR6 | An UPDATE_VPORT operation completed but does not have a valid initiator specified. | |
| 0000 0d03 | N/A | FCP_ERR4 or FCP_ERR6 | An UPDATE_VPORT operation completed with an error | |
| 0000 0d04 | N/A | FCP_ERR6 | An UPDATE_VPORT completed with an error, but one of the associated targets for the specified initiator_info/NPIV has an invalid eyecatcher. | A software defect. Collect detailed Component Trace of the Fibre Channel
drivers. |
| 0000 0d05 | N/A | FCP_ERR5 | An Update vport completed successfully and either fast fail or dynamic tracking is on for this NPIV, but one of the associated targets for the specified initiator_info/NPIV has an invalid eyecatcher. | A software defect. Collect detailed Component Trace of the Fibre Channel drivers. |
| 0000 0d06 | N/A | FCP_ERR6 | An UPDATE_VPORT completed successfully and either fast fail or dynamic tracking is on for this NPIV, but for some reason this target is not indicating that is running fast fail or dynamic tracking. | |
| 0000 0d07 | N/A | FCP_ERR6 | An attempt to issue an UPDATE_VPORT is failed because a valid initiator_info was not specified. | |
| 0000 0d08 | N/A | FCP_ERR4 or FCP_ERR6 | An UPDATE_VPORT was failed by the command entry point of the adapter driver. | |
| 0000 0d09 | N/A | FCP_ERR5 | An UPDATE_VPORT was failed by the command entry point of the adapter driver and attempts to recover have found an associated dev_info without a valid eyecatcher. | A software defect. Collect detailed Component Trace of the Fibre Channel drivers. |
| 0000 0d0a | N/A | FCP_ERR6 | An UPDATE_VPORT operation timed out, but there is no associated initiator_info | |
| 0000 0d0b | N/A | FCP_ERR4 | An UPDATE_VPORT operation time out | |
| 0000 0d0c | N/A | FCP_ERR5 | An UPDATE_VPORT operation timed out and when doing error recovery an associated target_info did not have a valid eyecatcher. | A software defect. Collect detailed Component Trace of the Fibre Channel drivers. |
| 0000 0d0d | N/A | FCP_ERR5 | When processing a link event for an NPIV, its associated target_info did not have a valid eyecatcher. | A software defect. Collect detailed Component Trace of the Fibre Channel drivers. |
| 0000 0d0e | N/A | FCP_ERR5 | When looking for an initiator_info from our hash table via it's N_Port ID, we found it had an invalid eyecatcher. | A software defect. Collect detailed Component Trace of the Fibre Channel drivers. |
| 0000 0d0f | N/A | FCP_ERR5 | When looking for an initiator_info from our hash table via it's world wide name, we found it had an invalid eyecatcher. | A software defect. Collect detailed Component Trace of the Fibre Channel drivers. |
| 0000 a102 | N/A | FCP_ERR5 | An SCIOLSTOP is being done for an initiator/NPIV which has an invalid eyecatcher. | A software defect. Collect detailed Component Trace of the Fibre Channel drivers. |
| 0000 a110 | N/A | FCP_ERR2 | An attempt to flush an command back to an NPIV client was failed by the specified cmd_done routine. | This would be a software defect. Collect detailed Component Traces from the NPIV and Fibre Channel driver |
| 0000 0BFF | N/A | FCP_ERR6 | Emulex stack, usually means that an application has requested an SCIOLPAYLD ioctl() and has specified a >4K response buffer. AIX logs an informational error. | Contact AIX Software support for more on this informational message |
| 0000 0401 | N/A | FCP_ERR10 | Errors of category type ADAPTER is recovered. Threshold counters and error time info is passed on row 8,10 (Current errs, Total errs, and the time first error occured) for all 4 type of the operation (Nameserver,SCSI,ELS and RECOVERY operations in that order). | |
| 0000 0402 | N/A | FCP_ERR10 | Errors of category type LINK is recovered. Threshold counters and error time info is passed on row 8 thru 11 as above. | |
| 0000 0403 | N/A | FCP_ERR10 | Errors of category type TARGET is recovered. Threshold counters and error time info is passed on row 8 thru 11 as above. | |
| 0000 0404 | N/A | FCP_ERR10 | Errors of category type Target Mode is recovered. Threshold counters and error time info is passed on row 8 thru 11 as above. |