Ray, >Where is the SCSI logout/PRLO coming from? One of your tapes? I would be more than happy if I would know that ;-) Currently we have FC protocol analysers attached in the path to four tape drives to get more information.
>PRLI/PRLO are usually sent from initiator to target... It appears that there is at least one situation where a target sends PRLO, that is if an initiator sends a TPRLO (Third Party Process Logout) with Global Bit = 1. (See http://www.t10.org/ftp/t10/document.04/04-383r0.pdf) Yesterday we've found out that we have some windows hosts with Emulex LP8000 adapters installed where a vendor recommended to change the setting of ResetTPRLO parameter from default (=0) to 2, which means that the adapter uses TPRLO with Global Bit = 1. We currently are not sure if that is our problem or in which situation the Emulex adapter uses this setting. Andreas Mayer Telekom Austria -----Original Message----- From: Raymond Higgs [mailto:[EMAIL PROTECTED] Sent: Monday, November 26, 2007 3:31 PM Subject: Re: zfcp - ELS Process Logout Linux on 390 Port <[email protected]> wrote on 11/25/2007 11:26:11 AM: > Hello, > > we are using FCP attached tape devices on SLES 9 s390x SP3 for TSM for > over one year now, in the last weeks we've added other tape models from > same vendor. > > After getting syslog message "kernel: zfcp: warning: unknown incoming > ELS 0x21100014 for adapter 0.0.c108" we have troubles with some to all > tape devices on this fcp adapter. > On another fcp adapter on the same system a second set of the same tape > devices is working without problems. > > If we try to reset the fcp adapter with chccwdev -d/-e, IO's on the tape > devices are working for some time, but after message "kernel: zfcp: > warning: unknown incoming ELS 0x21100014 for adapter 0.0.c108" the tape > devices stop working again. > > Extended Link Services (ELS) 0x21100014 appears to be PRLO (Process > Logout). > I did search for some more information in the internet, did find some > issues if scsi initiator does not login again to target after PRLO ? > > Currently I'm trying to get more information by looking at fcp trace > data produced while testing with TSM mttest command. > In the trace I see that the target port and unit is reopened (and a soft > error is returned to the application ?): > zfcp: zfcp_erp_port_forced_reopen_internal(499): forced reopen of port > 0x500104f000752a69 on adapter 0.0.c108 > zfcp: zfcp_fsf_send_fcp_command_task_handler(4162): Setting > DID_SOFT_ERROR and SUGGEST_RETRY > zfcp: zfcp_fsf_send_fcp_command_task_handler(4333): scpnt->result > =0x100b0000 > zfcp: zfcp_fsf_open_unit_handler(3317): unit 0x0000000000000000 on > remote port 0x500104f000752a69 on adapter 0.0.c108 opened, port handle > 0x516 > > Does anyone have an idea what's going on here or why the zfcp driver > doesn't handle PRLO ? > > Thank You ! > > Andreas Mayer > Telekom Austria > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 Andreas, Where is the SCSI logout/PRLO coming from? One of your tapes? PRLI/PRLO are usually sent from initiator to target... Thanks, Ray Higgs System z FCP Development Bld. 706, B24 2455 South Road Poughkeepsie, NY 12601 (845) 435-8666, T/L 295-8666 [EMAIL PROTECTED] ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
