2 * Text: "%s is not a valid SCSI device\n"
5 * @1: device specification
7 * The specification for an initial SCSI device provided with the 'zfcp.device'
8 * kernel parameter or with the 'device' module parameter is syntactically
9 * incorrect. The specified SCSI device could not be attached to the Linux
12 * Correct the value for the 'zfcp.device' or 'device' parameter and reboot
13 * Linux. See "Device Drivers, Features, and Commands" for information about
18 * Text: "Registering the misc device zfcp_cfdc failed\n"
21 * The zfcp device driver failed to register the device that provides access to
22 * the adapter access control file (ACL tables). The device driver
23 * initialization failed. A possible cause for this problem is memory
26 * Free some memory and try again to load the zfcp device driver. If the zfcp
27 * device driver has been compiled into the kernel, reboot Linux. Consider
28 * assigning more memory to your LPAR or z/VM guest virtual machine. If the
29 * problem persists, contact your support organization.
33 * Text: "The zfcp device driver could not register with the common I/O layer\n"
36 * The device driver initialization failed. A possible cause of this problem is
39 * Free some memory and try again to load the zfcp device driver. If the zfcp
40 * device driver has been compiled into the kernel, reboot Linux. Consider
41 * assigning more memory to your LPAR or z/VM guest virtual machine. If the
42 * problem persists, contact your support organization.
46 * Text: "%s: Setting up data structures for the FCP adapter failed\n"
49 * @1: bus ID of the zfcp device
51 * The zfcp device driver could not allocate data structures for an FCP adapter.
52 * A possible reason for this problem is memory constraints.
54 * Set the FCP adapter offline or detach it from the Linux system, free some
55 * memory and set the FCP adapter online again or attach it again. If this
56 * problem persists, gather Linux debug data, collect the FCP adapter
57 * hardware logs, and report the problem to your support organization.
61 * Text: "%s: The FCP device is operational again\n"
62 * Severity: Informational
64 * @1: bus ID of the zfcp device
66 * An FCP device has been unavailable because it had been detached from the
67 * Linux system or because the corresponding CHPID was offline. The FCP device
68 * is now available again and the zfcp device driver resumes all operations to
75 * Text: "%s: The CHPID for the FCP device is offline\n"
78 * @1: bus ID of the zfcp device
80 * The CHPID for an FCP device has been set offline, either logically in Linux
83 * Find out which CHPID corresponds to the FCP device, for example, with the
84 * lscss command. Check if the CHPID has been set logically offline in sysfs.
85 * Write 'on' to the CHPID's status attribute to set it online. If the CHPID is
86 * online in sysfs, find out if it has been varied offline through a hardware
87 * management interface, for example the service element (SE).
91 * Text: "%s: The FCP device has been detached\n"
94 * @1: bus ID of the zfcp device
96 * An FCP device is no longer available to Linux.
98 * Ensure that the FCP adapter is operational and attached to the LPAR or z/VM
103 * Text: "%s: The FCP device did not respond within the specified time\n"
106 * @1: bus ID of the zfcp device
108 * The common I/O layer waited for a response from the FCP adapter but
109 * no response was received within the specified time limit. This might
110 * indicate a hardware problem.
112 * Consult your hardware administrator. If this problem persists,
113 * gather Linux debug data, collect the FCP adapter hardware logs, and
114 * report the problem to your support organization.
118 * Text: "%s: Registering the FCP device with the SCSI stack failed\n"
121 * @1: bus ID of the zfcp device
123 * The FCP adapter could not be registered with the Linux SCSI
124 * stack. A possible reason for this problem is memory constraints.
126 * Set the FCP adapter offline or detach it from the Linux system, free some
127 * memory and set the FCP adapter online again or attach it again. If this
128 * problem persists, gather Linux debug data, collect the FCP adapter
129 * hardware logs, and report the problem to your support organization.
133 * Text: "%s: ERP cannot recover an error on the FCP device\n"
136 * @1: bus ID of the zfcp device
138 * An error occurred on an FCP device. The error recovery procedure (ERP)
139 * could not resolve the error. The FCP device driver cannot use the FCP device.
141 * Check for previous error messages for the same FCP device to find the
142 * cause of the problem.
146 * Text: "%s: Creating an ERP thread for the FCP device failed.\n"
149 * @1: bus ID of the zfcp device
151 * The zfcp device driver could not set up error recovery procedure (ERP)
152 * processing for the FCP device. The FCP device is not available for use
155 * Free some memory and try again to load the zfcp device driver. If the zfcp
156 * device driver has been compiled into the kernel, reboot Linux. Consider
157 * assigning more memory to your LPAR or z/VM guest virtual machine. If the
158 * problem persists, contact your support organization.
162 * Text: "%s: ERP failed for unit 0x%016Lx on port 0x%016Lx\n"
165 * @1: bus ID of the zfcp device
169 * An error occurred on the SCSI device at the specified LUN. The error recovery
170 * procedure (ERP) could not resolve the error. The SCSI device is not
173 * Verify that the LUN is correct. Check the fibre channel fabric for errors
174 * related to the specified WWPN and LUN, the storage server, and Linux.
178 * Text: "%s: ERP failed for remote port 0x%016Lx\n"
181 * @1: bus ID of the zfcp device
184 * An error occurred on a remote port. The error recovery procedure (ERP)
185 * could not resolve the error. The port is not available.
187 * Verify that the WWPN is correct and check the fibre channel fabric for
188 * errors related to the WWPN.
192 * Text: "%s: Attaching the name server port to the FCP device failed\n"
195 * @1: bus ID of the zfcp device
197 * The zfcp device driver could not attach the name server port of the fibre
198 * channel fabric to an FCP device. A possible cause of this problem is
199 * memory constraints.
201 * Set the FCP device offline, free some memory, then set the FCP device online
202 * again. If this does not resolve the problem, reboot Linux and try again to
203 * set the FCP device online.
207 * Text: "%s: Registering unit 0x%016Lx on port 0x%016Lx failed\n"
210 * @1: bus ID of the zfcp device
214 * The Linux kernel could not allocate enough memory to register the SCSI
215 * device at the indicated LUN with the SCSI stack. The SCSI device is not
218 * Free some memory then detach the LUN and attach it again.
222 * Text: "%s: Registering port 0x%016Lx failed\n"
225 * @1: bus ID of the zfcp device
228 * The Linux kernel could not allocate enough memory to register the
229 * remote port with the indicated WWPN with the SCSI stack. The remote
230 * port is not available.
232 * Free some memory and trigger the rescan for ports.
236 * Text: "%s: A QDIO problem occurred\n"
239 * @1: bus ID of the zfcp device
241 * QDIO reported a problem to the zfcp device driver. The zfcp device driver
242 * tries to recover this problem.
244 * Check for related error messages. If this problem occurs frequently, gather
245 * Linux debug data and contact your support organization.
249 * Text: "%s: A QDIO protocol error occurred, operations continue\n"
252 * @1: bus ID of the zfcp device
254 * The zfcp device driver detected a missing flag in a QDIO queue. The device
255 * driver tries to keep the FCP device operational.
257 * Check for related error messages. If this problem occurs frequently, gather
258 * Linux debug data, collect the FCP adapter hardware logs, and report the
259 * problem to your support organization.
263 * Text: "%s: Setting up the QDIO connection to the FCP adapter failed\n"
266 * @1: bus ID of the zfcp device
268 * The zfcp device driver failed to establish a QDIO connection with the FCP
271 * Set the FCP adapter offline or detach it from the Linux system, free some
272 * memory and set the FCP adapter online again or attach it again. If this
273 * problem persists, gather Linux debug data, collect the FCP adapter
274 * hardware logs, and report the problem to your support organization.
278 * Text: "%s: The FCP adapter reported a problem that cannot be recovered\n"
281 * @1: bus ID of the zfcp device
283 * The FCP adapter has a problem that cannot be recovered by the zfcp device
284 * driver. The zfcp device driver stopped using the FCP device.
286 * Gather Linux debug data, collect the FCP adapter hardware logs, and report
287 * this problem to your support organization.
291 * Text: "%s: There is a wrap plug instead of a fibre channel cable\n"
294 * @1: bus ID of the zfcp device
296 * The FCP adapter is not physically connected to the fibre channel fabric.
298 * Remove the wrap plug from the FCP adapter and connect the adapter with the
299 * fibre channel fabric.
303 * Text: "%s: Access denied to unit 0x%016Lx on port 0x%016Lx\n"
306 * @1: bus ID of the zfcp device
310 * The Linux system is not allowed to access the SCSI device at the indicated
313 * Update the access control table of the FCP device to grant the Linux
314 * system access to the LUN or remove the LUN from the Linux system.
318 * Text: "%s: FCP device not operational because of an unsupported FC class\n"
321 * @1: bus ID of the zfcp device
323 * The FCP adapter hardware does not support the fibre channel service class
324 * requested by the zfcp device driver. This problem indicates a program error
325 * in the zfcp device driver.
327 * Gather Linux debug data, collect the FCP adapter hardware logs, and report
328 * this problem to your support organization.
332 * Text: "%s: 0x%Lx is an ambiguous request identifier\n"
335 * @1: bus ID of the zfcp device
338 * The FCP adapter reported that it received the same request ID twice. This is
339 * an error. The zfcp device driver stopped using the FCP device.
341 * Gather Linux debug data, collect the FCP adapter hardware logs, and report
342 * this problem to your support organization.
346 * Text: "%s: QTCB version 0x%x not supported by FCP adapter (0x%x to 0x%x)\n"
349 * @1: bus ID of the zfcp device
350 * @2: requested version
351 * @3: lowest supported version
352 * @4: highest supported version
355 * The queue transfer control block (QTCB) version requested by the zfcp device
356 * driver is not supported by the FCP adapter hardware.
358 * If the requested version is higher than the highest version supported by the
359 * hardware, install more recent firmware on the FCP adapter. If the requested
360 * version is lower then the lowest version supported by the hardware, upgrade
361 * to a Linux level with a more recent zfcp device driver.
365 * Text: "%s: The FCP adapter could not log in to the fibre channel fabric\n"
368 * @1: bus ID of the zfcp device
370 * The fibre channel switch rejected the login request from the FCP adapter.
372 * Check the fibre channel fabric or switch logs for possible errors.
376 * Text: "%s: The FCP device is suspended because of a firmware update\n"
379 * @1: bus ID of the zfcp device
381 * The FCP device is not available while a firmware update is in progress. This
382 * problem is temporary. The FCP device will resume operations when the
383 * firmware update is completed.
385 * Wait 10 seconds and try the operation again.
389 * Text: "%s: All NPIV ports on the FCP adapter have been assigned\n"
392 * @1: bus ID of the zfcp device
394 * The number of N_Port ID Virtualization (NPIV) ports that can be assigned
395 * on an FCP adapter is limited. Once assigned, NPIV ports are not released
396 * automatically but have to be released explicitly through the support
399 * Identify NPIV ports that have been assigned but are no longer in use and
400 * release them from the SE.
404 * Text: "%s: The link between the FCP adapter and the FC fabric is down\n"
407 * @1: bus ID of the zfcp device
409 * The FCP adapter is not usable. Specific error information is not available.
411 * Check the cabling and the fibre channel fabric configuration. If this
412 * problem persists, gather Linux debug data, collect the FCP adapter
413 * hardware logs, and report the problem to your support organization.
417 * Text: "%s: Access denied to port 0x%016Lx\n"
420 * @1: bus ID of the zfcp device
423 * The Linux system is not allowed to access the remote port with the specified
426 * Update the access control table of the FCP device to grant the Linux
427 * system access to the WWPN or remove the WWPN from the Linux system.
431 * Text: "%s: The QTCB type is not supported by the FCP adapter\n"
434 * @1: bus ID of the zfcp device
436 * The queue transfer control block (QTCB) type requested by the zfcp device
437 * driver is not supported by the FCP adapter hardware.
439 * Install the latest firmware on your FCP adapter hardware. If this does not
440 * resolve the problem, upgrade to a Linux level with a more recent zfcp device
441 * driver. If the problem persists, contact your support organization.
445 * Text: "%s: The error threshold for checksum statistics has been exceeded\n"
448 * @1: bus ID of the zfcp device
450 * The FCP adapter has reported a large number of bit errors. This might
451 * indicate a problem with the physical components of the fibre channel fabric.
452 * Details about the errors have been written to the HBA trace for the FCP
455 * Check for problems in the fibre channel fabric and ensure that all cables
456 * are properly plugged.
460 * Text: "%s: The local link has been restored\n"
461 * Severity: Informational
463 * @1: bus ID of the zfcp device
465 * A problem with the connection between the FCP adapter and the adjacent node
466 * on the fibre channel fabric has been resolved. The FCP adapter is now
473 * Text: "%s: Access denied according to ACT rule type %s, rule %d\n"
476 * @1: bus ID of the zfcp device
477 * @2: access rule type
480 * A rule in the access control table (ACT) for the FCP device denies access
481 * to a remote port or a LUN.
483 * Examine the access control tables for the FCP device to see if the
484 * specified rule is correct.
488 * Text: "%s: The mode table on the FCP adapter has been damaged\n"
491 * @1: bus ID of the zfcp device
493 * This is an FCP adapter hardware problem.
495 * Report this problem with FCP hardware logs to IBM support.
499 * Text: "%s: The adjacent fibre channel node does not support FCP\n"
502 * @1: bus ID of the zfcp device
504 * The fibre channel switch or storage system that is connected to the FCP
505 * channel does not support the fibre channel protocol (FCP). The zfcp
506 * device driver stopped using the FCP device.
508 * Check the adjacent fibre channel node.
512 * Text: "%s: The FCP adapter does not recognize the command 0x%x\n"
515 * @1: bus ID of the zfcp device
518 * A command code that was sent from the zfcp device driver to the FCP adapter
519 * is not valid. The zfcp device driver stopped using the FCP device.
521 * Gather Linux debug data, collect the FCP adapter hardware logs, and report
522 * this problem to your support organization.
526 * Text: "%s: There is no light signal from the local fibre channel cable\n"
529 * @1: bus ID of the zfcp device
531 * There is no signal on the fibre channel cable that connects the FCP adapter
532 * to the fibre channel fabric.
534 * Ensure that the cable is in place and connected properly to the FCP adapter
535 * and to the adjacent fibre channel switch or storage system.
539 * Text: "%s: The WWPN assignment file on the FCP adapter has been damaged\n"
542 * @1: bus ID of the zfcp device
544 * This is an FCP adapter hardware problem.
546 * Report this problem with FCP hardware logs to IBM support.
550 * Text: "%s: The FCP device detected a WWPN that is duplicate or not valid\n"
553 * @1: bus ID of the zfcp device
555 * This condition indicates an error in the FCP adapter hardware or in the z/VM
558 * Gather Linux debug data, collect the FCP adapter hardware logs, and report
559 * this problem to IBM support.
563 * Text: "%s: The fibre channel fabric does not support NPIV\n"
566 * @1: bus ID of the zfcp device
568 * The FCP adapter requires N_Port ID Virtualization (NPIV) from the adjacent
569 * fibre channel node. Either the FCP adapter is connected to a fibre channel
570 * switch that does not support NPIV or the FCP adapter tries to use NPIV in a
571 * point-to-point setup. The connection is not operational.
573 * Verify that NPIV is correctly used for this connection. Check the FCP adapter
574 * configuration and the fibre channel switch configuration. If necessary,
575 * update the fibre channel switch firmware.
579 * Text: "%s: The FCP adapter cannot support more NPIV ports\n"
582 * @1: bus ID of the zfcp device
584 * N_Port ID Virtualization (NPIV) ports consume physical resources on the FCP
585 * adapter. The FCP adapter resources are exhausted. The connection is not
588 * Analyze the number of available NPIV ports and which operating system
589 * instances use them. If necessary, reconfigure your setup to move some
590 * NPIV ports to an FCP adapter with free resources.
594 * Text: "%s: The adjacent switch cannot support more NPIV ports\n"
597 * @1: bus ID of the zfcp device
599 * N_Port ID Virtualization (NPIV) ports consume physical resources. The
600 * resources of the fibre channel switch that is connected to the FCP adapter
601 * are exhausted. The connection is not operational.
603 * Analyze the number of available NPIV ports on the adjacent fibre channel
604 * switch and how they are used. If necessary, reconfigure your fibre channel
605 * fabric to accommodate the required NPIV ports.
609 * Text: "%s: 0x%x is not a valid transfer protocol status\n"
612 * @1: bus ID of the zfcp device
613 * @2: status information
615 * The transfer protocol status information reported by the FCP adapter is not
616 * a valid status for the zfcp device driver. The zfcp device driver stopped
617 * using the FCP device.
619 * Gather Linux debug data, collect the FCP adapter hardware logs, and report
620 * this problem to your support organization.
624 * Text: "%s: Unknown or unsupported arbitrated loop fibre channel topology detected\n"
627 * @1: bus ID of the zfcp device
629 * The FCP device is connected to a fibre channel arbitrated loop or the FCP adapter
630 * reported an unknown fibre channel topology. The zfcp device driver supports
631 * point-to-point connections and switched fibre channel fabrics but not arbitrated
632 * loop topologies. The FCP device cannot be used.
634 * Check the fibre channel setup and ensure that only supported topologies are
635 * connected to the FCP adapter.
639 * Text: "%s: FCP adapter maximum QTCB size (%d bytes) is too small\n"
642 * @1: bus ID of the zfcp device
643 * @2: maximum supported size
644 * @3: requested QTCB size
646 * The queue transfer control block (QTCB) size requested by the zfcp
647 * device driver is not supported by the FCP adapter hardware.
649 * Update the firmware on your FCP adapter hardware to the latest
650 * available level and update the Linux kernel to the latest supported
651 * level. If the problem persists, contact your support organization.
655 * Text: "%s: The FCP adapter only supports newer control block versions\n"
658 * @1: bus ID of the zfcp device
660 * The protocol supported by the FCP adapter is not compatible with the zfcp
663 * Upgrade your Linux kernel to a level that includes a zfcp device driver
664 * with support for the control block version required by your FCP adapter.
668 * Text: "%s: The FCP adapter only supports older control block versions\n"
671 * @1: bus ID of the zfcp device
673 * The protocol supported by the FCP adapter is not compatible with the zfcp
676 * Install the latest firmware on your FCP adapter.
680 * Text: "%s: Not enough FCP adapter resources to open remote port 0x%016Lx\n"
683 * @1: bus ID of the zfcp device
686 * Each port that is opened consumes physical resources of the FCP adapter to
687 * which it is attached. These resources are exhausted and the specified port
690 * Reduce the total number of remote ports that are attached to the
695 * Text: "%s: LUN 0x%Lx on port 0x%Lx is already in use by CSS%d, MIF Image ID %x\n"
698 * @1: bus ID of the zfcp device
700 * @3: remote port WWPN
701 * @4: channel subsystem ID
702 * @5: MIF Image ID of the LPAR
704 * The SCSI device at the indicated LUN is already in use by another system.
705 * Only one system at a time can use the SCSI device.
707 * Ensure that the other system stops using the device before trying to use it.
711 * Text: "%s: No handle is available for LUN 0x%016Lx on port 0x%016Lx\n"
714 * @1: bus ID of the zfcp device
718 * The FCP adapter can only open a limited number of SCSI devices. This limit
719 * has been reached and the SCSI device at the indicated LUN cannot be opened.
721 * Check all SCSI devices opened through the FCP adapter and close some of them.
725 * Text: "%s: SCSI device at LUN 0x%016Lx on port 0x%016Lx opened read-only\n"
726 * Severity: Informational
728 * @1: bus ID of the zfcp device
732 * The access control tables in the FCP adapter allow read-only access for the
733 * LUN. Write access is not permitted for your Linux instance. The SCSI
734 * device has been opened successfully in read-only access mode.
736 * None if read-only access is sufficient. If you require write access, change
737 * the access control tables in the FCP adapter.
741 * Text: "%s: Exclusive read-only access not supported (unit 0x%016Lx, port 0x%016Lx)\n"
744 * @1: bus ID of the zfcp device
748 * The access configuration specified in the access control tables of the FCP
749 * adapter is not valid. The SCSI device at the indicated LUN cannot be
752 * Change the access control tables in the FCP adapter.
756 * Text: "%s: Shared read-write access not supported (unit 0x%016Lx, port 0x%016Lx)\n"
759 * @1: bus ID of the zfcp device
763 * The access configuration specified in the access control tables of the FCP
764 * adapter is not valid. The SCSI device at the indicated LUN cannot be
767 * Change the access control tables in the FCP adapter.
771 * Text: "%s: Incorrect direction %d, unit 0x%016Lx on port 0x%016Lx closed\n"
774 * @1: bus ID of the zfcp device
775 * @2: value in direction field
779 * The direction field in a SCSI request contains an incorrect value. The zfcp
780 * device driver closed down the SCSI device at the indicated LUN.
782 * Gather Linux debug data and report this problem to your support organization.
786 * Text: "%s: Incorrect CDB length %d, unit 0x%016Lx on port 0x%016Lx closed\n"
789 * @1: bus ID of the zfcp device
790 * @2: value in length field
794 * The control-data-block (CDB) length field in a SCSI request is not valid or
795 * too large for the FCP adapter. The zfcp device driver closed down the SCSI
796 * device at the indicated LUN.
798 * Gather Linux debug data and report this problem to your support organization.
802 * Text: "%s: Oversize data package, unit 0x%016Lx on port 0x%016Lx closed\n"
805 * @1: bus ID of the zfcp device
809 * A SCSI request with too much data has been sent to the SCSI device at the
810 * indicated LUN. The FCP adapter cannot handle data packets of this size and
811 * the SCSI device driver closed down the SCSI device.
813 * Gather Linux debug data and report this problem to your support organization.
817 * Text: "%s: Opening WKA port 0x%x failed\n"
820 * @1: bus ID of the zfcp device
821 * @2: destination ID of the WKA port
823 * The FCP adapter rejected a request to open the specified
824 * well-known address (WKA) port. No retry is possible.
826 * Verify the setup and check if the maximum number of remote ports
827 * used through this adapter is below the maximum allowed. If the
828 * problem persists, gather Linux debug data, collect the FCP adapter
829 * hardware logs, and report the problem to your support organization.
833 * Text: "%s: The name server reported %d words residual data\n"
836 * @1: bus ID of the zfcp device
837 * @2: number of words in residual data
839 * The fibre channel name server sent too much information about remote ports.
840 * The zfcp device driver did not receive sufficient information to attach all
841 * available remote ports in the SAN.
843 * Verify that you are running the latest firmware level on the FCP
844 * adapter. Check your SAN setup and consider reducing the number of ports
845 * visible to the FCP adapter by using more restrictive zoning in the SAN.
849 * Text: "%s: A port opened with WWPN 0x%016Lx returned data that identifies it as WWPN 0x%016Lx\n"
852 * @1: bus ID of the zfcp device
856 * A remote port was opened successfully, but it reported an
857 * unexpected WWPN in the returned port login (PLOGI) data. This
858 * condition might have been caused by a change applied to the SAN
859 * configuration while the port was being opened.
861 * If this condition is only temporary and access to the remote port
862 * is possible, no action is required. If the condition persists,
863 * identify the storage system with the specified WWPN and contact the
864 * support organization of the storage system.